FastJson 1.2.37 parsing overlow long value issue

Give class:
    public static class LongVal {
        private long v;
        public void setV(long v) {
            this.v = v;
        }

        @Override
        public String toString() {
            return String.valueOf(v);
        }
    }

Give the following code to call fastjson:
        BigInteger n = new BigInteger(String.valueOf(Long.MAX_VALUE)).add(new BigInteger("1"));
        Map<String, BigInteger> map = new HashMap<>();
        map.put("v", n);
        String strBad = JSON.toJSONString(map);
        System.out.println(JSON.parseObject(strBad, LongVal.class));

Expected behavior: raise NumberFormatException
found it print out -9223372036854775808
Screenshot:

The full source code the reproduce this issue:
https://gist.github.com/greenlaw110/e906970a13921fc30adada704468c63f

thank you, bug has been fixed and added several tests.

bug fixed, please try the last version. https://github.com/alibaba/fastjson/releases/tag/1.2.38


added the new our team section

Related Issue
added the new our team section
Closes: #206
Describe the changes you've made

Type of change
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Mention any unusual behaviour of your code (Write NA if not)
Any unusual behaviour of your code
Additional Info (optional)
Any additional information you want to give
Checklist:

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly whereever it was hard to understand.
[x] My changes generate no new warnings.
[ ] Any dependent changes have been merged and published in downstream modules.

https://user-images.githubusercontent.com/55352601/118589826-cd3e1800-b7be-11eb-9576-840e77f507fb.mp4
@adarshvulli @ankitapuri  this  is the new our team section i was working on :)


use Azure::Core::ETag for ETag type

closes https://github.com/Azure/azure-sdk-for-cpp/issues/1484
Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.

[x] C++ Guidelines
[x] Doxygen docs
[x] Unit tests
[x] No unwanted commits/changes
[x] Descriptive title/description

[x] PR is single purpose
[x] Related issue listed

[x] Comments in source
[x] No typos
[x] Update changelog
[x] Not work-in-progress
[x] External references or docs updated
[x] Self review of PR done
[x] Any breaking changes?

/azp run cpp - storage

/azp run cpp - storage

@katmsft Please enbale DataLake and file serivce

@katmsft Please enbale DataLake and file serivce

/azp run cpp - storage

/azp run cpp - storage


Repository Not Found for url: https://huggingface.co/api/models/runwayml/stable-diffusion-inpainting/revision/fp16

I can't run the image editting task:
Registering COLORPOP step
Registering BGBLUR step
Registering REPLACE step
Couldn't connect to the Hub: 401 Client Error. (Request ID: Root=1-66e26e75-170a15a05078be685e693c57;e6b93512-3f07-4fa0-84d9-82802dc4a2f5)

Repository Not Found for url: https://huggingface.co/api/models/runwayml/stable-diffusion-inpainting/revision/fp16.
Please make sure you specified the correct `repo_id` and `repo_type`.
If you are trying to access a private or gated repo, make sure you are authenticated.
Invalid username or password..
Will try to load from local cache.
---------------------------------------------------------------------------
HTTPError                                 Traceback (most recent call last)
[/usr/local/lib/python3.10/dist-packages/huggingface_hub/utils/_errors.py](https://localhost:8080/#) in hf_raise_for_status(response, endpoint_name)
    303     try:
--> 304         response.raise_for_status()
    305     except HTTPError as e:

12 frames
HTTPError: 401 Client Error: Unauthorized for url: https://huggingface.co/api/models/runwayml/stable-diffusion-inpainting/revision/fp16

The above exception was the direct cause of the following exception:

RepositoryNotFoundError                   Traceback (most recent call last)
RepositoryNotFoundError: 401 Client Error. (Request ID: Root=1-66e26e75-170a15a05078be685e693c57;e6b93512-3f07-4fa0-84d9-82802dc4a2f5)

Repository Not Found for url: https://huggingface.co/api/models/runwayml/stable-diffusion-inpainting/revision/fp16.
Please make sure you specified the correct `repo_id` and `repo_type`.
If you are trying to access a private or gated repo, make sure you are authenticated.
Invalid username or password.

The above exception was the direct cause of the following exception:

OSError                                   Traceback (most recent call last)
[/usr/local/lib/python3.10/dist-packages/diffusers/pipelines/pipeline_utils.py](https://localhost:8080/#) in download(cls, pretrained_model_name, **kwargs)
   1534             else:
   1535                 # 2. we forced `local_files_only=True` when `model_info` failed
-> 1536                 raise EnvironmentError(
   1537                     f"Cannot load model {pretrained_model_name}: model is not cached locally and an error occurred"
   1538                     " while trying to fetch metadata from the Hub. Please check out the root cause in the stacktrace"

OSError: Cannot load model runwayml/stable-diffusion-inpainting: model is not cached locally and an error occurred while trying to fetch metadata from the Hub. Please check out the root cause in the stacktrace above.

Is there any URL to replace?

the same issue with @Kobe972


Cannot reference undefined label 'xyz'

dartanalyzer gives the error message "Cannot reference undefined label" depending on what comes just after the label in question. The following sample code is quite meaningless, but if I remove the print line just after "whynot:", then the error message goes away.
void strange() {
whynot:
  print("Why does this line cause _Cannot reference undefined label 'whynot'_?");
  for (int i = 0; ;) {
    break whynot;
    print("$i");
  }
}

void main() { print("whynot?"); }

I'm using Dart VM version: 1.12.2 (Wed Oct 21 06:56:12 2015) on "macos_x64".

The only purpose for labels is to be used in a break or continue statement. The break and continue statements can only transfer control to a do, for, while or switch statement. Therefore, labels on any other statement can never be referenced. The error message clearly needs to be improved, but the error is real.
Change your main to invoke strange() and try running the code. The VM will report:
'file:.../test.dart': error: line 20 pos 5: label 'whynot' not found
    break whynot;
    ^


Why no softmax for prediciton (eg: Notebook: 3)

prediction = self.fc_out(torch.cat((output, weighted, embedded), dim = 1))
Shouldn't here we also use softmax ?

The loss function used, CrossEntropyLoss, does both the softmax and the loss calculation.
See: https://pytorch.org/docs/stable/generated/torch.nn.CrossEntropyLoss.html

Thanks. Closing the issue


pgvector-haystack cannot be installed from psycopg on 3.1.20

pgvector-haystack depends on psycopg[binary] but psycopg-binary can't be installed with M1 CPU starting from 3.1.20. Instead, psycopg[c] works, which is the "local installation", which is also recommended:

This is the preferred way to install Psycopg for a production site.

Is this something you'd consider changing?

A workaround for people encountering this is to override the dependency spec of pgvector-haystack using the uv package manager:
[project]
name = "foo"
version = "0.0.1"
description = "bar"
readme = "README.md"
requires-python = ">=3.12"
dependencies = [
    "pgvector-haystack==1.2.0",
]

[[tool.uv.dependency-metadata]]
name = "pgvector-haystack"
version = "1.2.0"
requires-dist = ["haystack-ai", "pgvector", "psycopg[c]==3.2.3"]


No way to specify location?

The location drop-down menu is grayed out for me. Is this expected?

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

ID: 8cb1c7ba-83cb-e32a-85bd-3260bdefaee2
Version Independent ID: a5229c23-ac2d-3972-6b54-d4e70db5c046
Content: Quickstart - Create an Azure CDN profile and endpoint
Content Source: articles/cdn/cdn-create-new-endpoint.md
Service: azure-cdn
GitHub Login: @mdgattuso
Microsoft Alias: magattus

Yes, since CDN is a global resource it should be grayed out and set to Global. From taking a look it seems it's defaulted to Central US. is that what you're seeing? We can update this, and update the doc to reflect the change.

I'm seeing West US, but good to know. Thank you!

@mdgattuso Thanks for the quick response. :+1:


ioctl(self.fd, I2C_RDWR, ioctl_data) OSError: [Errno 22] Invalid argument

Raspberry Pi Zero W
Linux raspberrypi 4.14.98+ #1200 Tue Feb 12 20:11:02 GMT 2019 armv6l GNU/Linux
Traceback (most recent call last):
  File "LinuxProject4.py", line 55, in <module>
    device = ssd1327(serial)
  File "/usr/local/lib/python3.5/dist-packages/luma/oled/device/__init__.py", line 651, in __init__
    nibble_order=1, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/luma/oled/device/greyscale.py", line 36, in __init__
    self.clear()
  File "/usr/local/lib/python3.5/dist-packages/luma/core/mixin.py", line 46, in clear
    self.display(Image.new(self.mode, self.size))
  File "/usr/local/lib/python3.5/dist-packages/luma/oled/device/greyscale.py", line 118, in display
    self.data(list(buf))
  File "/usr/local/lib/python3.5/dist-packages/luma/core/device.py", line 46, in data
    self._serial_interface.data(data)
  File "/usr/local/lib/python3.5/dist-packages/luma/core/interface/serial.py", line 106, in data
    self._bus.i2c_rdwr(self._i2c_msg_write(self._addr, [self._data_mode] + data))
  File "/home/pi/.local/lib/python3.5/site-packages/smbus2/smbus2.py", line 497, in i2c_rdwr
    ioctl(self.fd, I2C_RDWR, ioctl_data)
OSError: [Errno 22] Invalid argument

Have you followed ALL the pre-requisites here: https://luma-oled.readthedocs.io/en/latest/hardware.html#i2c ?
What is the output of i2cdetect -y 1 ?

 Obviously, as you can see, there is something on 0x3C (this is the usual address for OLED displays).
What is the output of pip list | grep luma ?
Also, can you share a bit more of your code, specifically the bit where you initialize the serial device?

I'd seen that error before, and from what I remember it gets generated when a device doesn't respond on a particular address. Obviously, as you can see, there is something on 0x3C (this is the usual address for OLED displays).
What is the output of pip list | grep luma ?

pi@raspberrypi: $ pip3 list | grep luma
DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning.
luma (0.9.6)
luma.core (1.9.0)
luma.oled (3.2.1)

Also, can you share a bit more of your code, specifically the bit where you initialize the serial device?

from luma.core.interface.serial import i2c, spi
from luma.core.render import canvas
from luma.oled.device import ssd1327
serial = i2c(port=1, address=0x3C)
device = ssd1327(serial)

When I run an SSD1306 via I2C on the latest versions of luma.core and luma.oled I don't experience any errors, but when I tried the SSD1327 I got exactly the same problem as you described.
If I downgrade to luma.core 1.8.3 (sudo pip install luma.core==1.8.3) then ithe SSD1327 display works as expected. I would recommend downgrading to the earlier viersion  in the meantime, until we can get to the bottom of the issue.
I think this regression is caused by this commit: https://github.com/rm-hull/luma.core/commit/3502326a48886d2340e713b31de061d1f376ca84 ... @Gadgetoid - are you able to shed any light on this at all?

When I run an SSD1306 via I2C on the latest versions of luma.core and luma.oled I don't experience any errors, but when I tried the SSD1327 I got exactly the same problem as you described.
If I downgrade to luma.core 1.8.3 (sudo pip install luma.core==1.8.3) then the SSD1327 display works as expected. I would recommend downgrading to the earlier version in the meantime, until we can get to the bottom of the issue.
I think this regression is probably caused by this commit: rm-hull/luma.core@3502326 ... @Gadgetoid - are you able to shed any light on this at all?

Okay, thank you, after downgrading it works.

[Will keep this open until bug is fixed]

Reading the docs for ioctl (the method call that actually fails) it seems like there is a 1024 buffer limit, so I'm betting that this is the cause of this error.

Luma.core 1.10.1 released with the fix for this issue. Use sudo pip install luma.core -U to update to latest.


Avoided unnecessary call to sync validation

Fixes #2583.

Codecov Report

Merging #2584 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master   #2584   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files          66      66
  Lines        1367    1371    +4
======================================
+ Hits         1367    1371    +4

Impacted Files
Coverage Δ

src/reduxForm.js
100% <100%> (ø)
:white_check_mark:

Continue to review full report at Codecov.

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

Published in v6.6.0.

@erikras can you please look into @stream7 referenced issue its breaking for multiple people

I'll second that, @KatFishSnake.
@erikras, issue #2971 is a critical failure of the reset function and @stream7 seems to have tracked it down to this PR. I'm not in any position right now to rollback/build/test but when you get a chance could you please take a look?

Anyone have a workaround to fix this? Still doesn't work in 7.0.3


Add stable version for Data Share

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

This PR mostly consists of changes which have already been signed off on in azure-rest-api-specs-pr. I'm signing off on the introduction of new stable version + additional "sourceShareLocation" field.

@erich-wang  please merge this PR when you get a chance. thanks.


MM-48072 - Calls: Implement recording permissions and UI

Summary

Implement the participant's view of the recording UI flow: ask for permissions when:

joining a call with a recording ongoing (permissions alert will appear immediately in the channel)
joining a call and then a recording starts, while in a non-call-screen state (permissions alert will appear)
joining a call, entering the call screen, and then a recording starts (permissions alert will appear)

If the participant choses to Leave, they will exit the call.
If the participant chooses Okay, they will see the recording UI.
Host indicator added

Designs: https://www.figma.com/file/9HL2HADCQ0lLmn1RBOBGGV/Calls%3A-Recording?node-id=48%3A126049&t=Uv577vDmME1omM3R-0
@tanmay-des I made slight tweaks to the rec and host badge and text, please let me know if it looks good.
Ticket Link

https://mattermost.atlassian.net/browse/MM-48072

Checklist

[x] Added or updated unit tests (required for all new features)
[x] Has UI changes
[x] Includes text changes and localization file updates
[ ] Have tested against the 5 core themes to ensure consistency between them. N/A

Device Information

Android: 13, Pixel 6
iOS: 15.7, iPhone 7 plus

Screenshots

Release Note
Calls: Added recording permissions and UI indicating when recordings are active

@tanmay-des Thanks, that looks better:


The you tube videos referenced on this page have been set to private and so are no longer visible

Issue description

Feedback Type (Optional)
linking
Page Title on SAP Help Portal (prefilled)
Working with a Message Implementation Guideline
Page URL on SAP Help Portal (prefilled)
https://help.sap.com/docs/integration-suite/sap-integration-suite/working-with-message-implementation-guideline?locale=zh-CN%3Flocale%3Dzh-CN

Hi @katansapdevelop
Thank you for your feedback, we will look into it and get back to you.

Hi @katansapdevelop ,
This issue has been resolved.


installing ESXi VIB (release 0.8.1) does not work on Photon Platform ESXi host

hi
I tried to installed vmware-esx-vmdkops-0.8.1.vib on an ESXi host prepared with Photon Platform and I got the following message:
root@localhost:/tmp] esxcli software vib install --no-sig-check -v /tmp/vmware-esx-vmdkops-0.8.1.vib
[DependencyError]
VIB VMware_bootbank_photon-controller-agent_v1.0.0-c8a0db0's acceptance level is community, which is not compliant with the ImageProfile acceptance level partner
To change the host acceptance level, use the 'esxcli software acceptance set' command.
Please refer to the log file for more details.
[root@localhost:/tmp]
is there a way to force the vmware-esx-vmdkops-0.8.1.vib VIB software acceptance level to CommunitySupported ?
thanks in advance

note: using the --force option works
[root@localhost:/tmp] esxcli software vib install --no-sig-check -v /tmp/vmware-esx-vmdkops-0.8.1.vib --force
Installation Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: VMWare_bootbank_esx-vmdkops-service_0.8.1-0.0.1
VIBs Removed:
VIBs Skipped:
[root@localhost:/tmp]

@guillierf vSphere Docker Volume Service is NOT supported on Photon Platform. We are actively exploring options to integrate with Photon Platform. Is there specific use case you have in mind?
CC/ @govint @AlainRoy  @asomaiah

Photon Platform support is tracked in different forum.


How to set log level to debug

Hey guys,
Thanks for the awesome work !
I'm not sure this is the right place to ask, but I cannot for the life of me get my log messages logged using log::debug! to display. I tried modifying my sdkconfig file as well as using the set_target_level() method, but to no avail.
Any clue ?
Thanks !

What did you add to your sdkconfig file? Log level changes are in a specific format (output from menuconfig). See here: https://github.com/esp-rs/esp-idf-template/issues/215#issuecomment-2172912235
Note: be careful increasing log verbosity globally, IIRC esp-idf logs a lot at debug level.

Note: be careful increasing log verbosity globally, IIRC esp-idf logs a lot at debug level.

Indeed ... and most often than not causes stack overflows.


Result type is dependent on

(Original issue 1176 created by None on 2015-11-27T20:32:09.078183+00:00)
Room to Read and Pledge 1%
Room to Read is a wonderful charity whose goal is to help communities in developing countries rise out of poverty through education. By partnering with them, we’ve reached more than 250,000 children! Learn more about the Atlassian foundation.
Pledge 1% is a movement dedicated to making the world a better place by inspiring, fostering, and celebrating early stage corporate philanthropy. In December of 2014, we came together with Salesforce and Rally based on our shared passion for giving back and co-founded the Pledge 1% movement. We set a goal of getting 500 companies to pledge 1% equity, employee time, or product by this December and… we’re at 500 pledges today! That’s 500 companies that have pledged their commitment to share their success with their communities.
And today, 10 more companies joined the Pledge 1% movement. Thank you so much for your commitment to making the community a key stakeholder in your businesses. We are proud to partner with you.
We’re listening
Atlassian is about the power of teams. You, our customers, are an integral part of our team and we want you to know we’re listening. We receive 15,000 pieces of feedback per month… and we want more. Keep talking to us. We’re on this journey together and your input is invaluable to our products and our mission.

The post 6 call-outs from the Summit 2015 keynote address appeared first

(Original issue 1176 last updated on 2016-01-16T11:24:35.022379+00:00)
(Issue automaticaly closed due to status in Bitbucket: invalid)


types: Don't require finish-args

Fixes #187

We should maybe use a parser that checks the ensures non-undefined values are actual non-undefined, and throw a more useful error, instead of not showing the manifest. But out of scope of the PR, just mentioning


Add no connected endpoints message for kubernetes dashboard page

Old issue, k8s icon is not shown if there is no connected k8s


Missing CMake config files

Issue:
Unable to use from CMake through
find_package(doctest CONFIG)
target_link_libraries(mytest PRIVATE doctest::doctest)

Please take https://github.com/zhihaoy/cpp-doctest-feedstock a look.

@zhihaoy Can you test?

@zhihaoy Can you test?

Tested on all three platforms.  Thank you so much!


read().splitlines() -> readlines()

splitlines() does not work as what we expect here for bert-base-chinese because there is a '\u2028' (unicode line seperator) token in vocab file. Value of '\u2028'.splitlines() is ['', ''].
Perhaps we should use readlines() instead.

Codecov Report

Merging #860 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master    #860   +/-   ##
======================================
  Coverage    78.9%   78.9%
======================================
  Files          34      34
  Lines        6192    6192
======================================
  Hits         4886    4886
  Misses       1306    1306

Impacted Files
Coverage Δ

pytorch_transformers/tokenization_bert.py
93.2% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Great, thanks!


Allow the download of partially downloaded playlists

[x] If a playlist is partially downloaded, on playlist download button click, pop up a modal asking the user if they want to download the playlist as is or try to download the remaining tracks
This is mainly for spotdl since sometimes it can't find the song at all or mistakenly downloads a different song

Done in main https://github.com/UnGerardo/Yotify/commit/228cfcbad10eb2af3e2b031739fbfc5bc4af0734 to https://github.com/UnGerardo/Yotify/commit/dcf98388eb98daa4fa42e167309ff41e1e267bd3


The delay of R300

I use R300 to run a positioning system. I receive position produced by R300 and Optitrack at the same time. I use highly dynamic moving curves to align and calculate the delay between R300 and Optitrack. I find the delay of R300 relative to Optitrack could be 100~150 ms.
Using the same system, I changed to another camara. It's only 20 ms. So I am sure the 100 ms delay does not come from my position program. I use ARUCO which runs fast.
Why is the image collect delay is so big?
Does Realsense does some calculation before output the image? For instance, software focus.

Hi,
There is no significant software processing steps like you mentioned.
The pipeline for generating depth is considerably longer then usual the one on a web-cam. It still should not reach the values you'r reporting.
150ms at 30 FPS means 5 frames are being queued somewhere:

the camera itself does not have the memory to hold them
the uvc-driver and the relevant framework (Media Foundation on Windows and V4L on Linux) do maintain internal frame-queues. On a fast PC with low CPU consumption, these should be empty at most times. What is the configuration that you are using? Can you give it a try on a different setup.
librealsense does minimal image conversions on the frames. If you are running on Intel architecture, this code is well optimized and tested to take less then 2 ms.
librealsense also maintains an internal frame-queue when you are working with wait_for_frames API. This function is trying to synchronize between color and depth streams, causing extra latency (usually less then 15 ms) On the development branch we provide frame callbacks that let you be the first one to know about a new frame. You can give that a try.

Could you please specify what exact camera model you are using (as displayed in the device manager)?
Also, what kind of streaming do you enable? (color, depth, color+depth) At what resolution and FPS?

Required Info

Camera Model
SR300

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 14.04

Kernel Version (Linux Only)
4.4.0-040400-generic

Build System
Makefile

I use V4L currently. resolution: 640*480, fps=30HZ.

Hi @xuyongzhi,
I have a quick question, how did you manage to use SR300 in the presence of MoCap system ?
I'm using OptiTrack Prime 13W that emit  850nm and using them with SR300 which's projector emits 860nm IR pattern has a huge interference and makes it impossible to use.
Using R200 will suppress the the interference a lot (thanks to it's stereo IR), however I need the minimum range that SR300 offers.


Plots generated by plot_circuit_layout need to be more readable for multi-register circuits

What is the expected enhancement?
Plots generated by plot_circuit_layout display the qubits indices only. For multi-register circuits, this is not enough.
For example, if we have the circuit
qr1 = QuantumRegister(2, 'q')
qr2 = QuantumRegister(3, 'a')
qr3 = QuantumRegister(2, 'lengthy register name')

circ = QuantumCircuit(qr1, qr2, qr3)
circ.ccx(qr1[0], qr1[1], qr2[0])
circ.ccx(qr3[0], qr3[1], qr2[2])
circ.ccx(qr2[0], qr2[2], qr2[1])

And we use plot_circuit_layout to draw the virtual layout
backend = FakeTokyo()
qc3 = transpile(circ, backend, basis_gates = ['u','cx'])
plot_circuit_layout(qc3, backend)

The result will be

You can easily see that, it is hard to figure out which qubit belongs to which register.
We need to distinguish between the qubits which belong to different registers. We can display register name (above or below the circles represent the qubits). Or use different colors for different registers as shown below:

I'm not sure what you mean by "transpile flattens to a single register", but the register names are already there in plot_circuit_layout.
Actually, I generated the image that uses different colors for different registers by adding a few lines of code to this method.
And the currently generated images have a very limited value in case of multi-register circuits.


Use simplecov

As we're at it, remove dead spec code that was revealed by the coverage report
@jcarres-mdsol @ykitamura-mdsol @ssteeg-mdsol

Cool, thanks!


Add new theme: Mango

[x] Read the theme publishing doc or plugin publishing doc.

@mango-tree
Thank you for your contribution :)


Improvements to notification service message logs admin

NS-161.

Search with report text or user email
Show more columns in list view
Filter with message status and created at date

Notification service branch is deployed to platta: https://kuva-notification-service-pr60.api.dev.hel.ninja :rocket::rocket::rocket:

Notification service branch is deployed to platta: https://kuva-notification-service-pr60.api.dev.hel.ninja :rocket::rocket::rocket:

Notification service branch is deployed to platta: https://kuva-notification-service-pr60.api.dev.hel.ninja :rocket::rocket::rocket:

LGFM

Notification service branch is deployed to platta: https://kuva-notification-service-pr60.api.dev.hel.ninja :rocket::rocket::rocket:


Throwing 403 forbidden on first load

Something is causing a 403 forbidden error message  when you first load the hosted app (even before searching)

Hello, I'd like to work on fixing this issue. Please assign it to me.

Hello, I'd like to work on fixing this issue. Please assign it to me.

Cool! You're good to go!

The fix is not working, you probably are getting ratelimited by github api


Add curand

should probably use rand and rand_distributions, other option is just create/gen_x/destroy

The host api says it's not compatible with driver api. https://docs.nvidia.com/cuda/curand/host-api-overview.html#host-api-overview . This could be a good reason to swap. To test if it's compatible should first generate some random numbers using cudart, then generate them into a cuda device buffer, and see if they are the same (assuming seed is the same)

cuRAND does seem to work with driver api


CORS Issue

Please check the following instructions before submitting a bug :

Make sure you are using the latest version.
Make sure you read installation, integration, and upgrade document.

And provide the followings :

Operating system :
Laravel version :
Package version :
Steps to reproduce your issue :
Screenshots of browser console :

I have issue when I use the file manager on other domain.
I get this issue when I try to select picture from the file manager:
Uncaught DOMException: Blocked a frame with origin "http://<IP_ADDRESS>:8000" from accessing a cross-origin frame.
at useTinymce4AndColorbox (http://<IP_ADDRESS>:8000/laravel-filemanager?field_name=mceu_44-inp&type=Images:600:12)
at useFile (http://<IP_ADDRESS>:8000/laravel-filemanager?field_name=mceu_44-inp&type=Images:638:7)
at HTMLDivElement.onclick (http://<IP_ADDRESS>:8000/laravel-filemanager?field_name=mceu_44-inp&type=Images:1:1)

@darko-vukadinovski Did you find a solution?
I have the same problem. Can't figure out why.
It used to work, be we haven't used the file manager for a while, so it is hard to find what changed that got it broken.
Tried to turn off all security (even https) in nginx.conf, no luck.
I found this, but that is for TinyMCE3
I checked the domains and protocols with the developer tools, they all seem to come from the same domain.
The iframe for TinyMCE does not have a document, so no origin?
The iFrame for the laravel-filemanager loads from the same domain.
Only the laravel-filemanager containes some js/css from cdn (cloudflare, bootstrapcdn)
And now I'm stuck...

Hi @darko-vukadinovski, this most likely is not an issue with the file manager. If you use an API on a different domain you should add the appropriate CORS headers so your client can consume the remote API. Check out barryvdh’s package

@gwleuverink This did not work for me.
As I see it, This is the hierarchy:
- top Window -> Document (top)
|   |-> Textarea field (text)
|   |   |-> iFrame replaced (no origin, since the frame is filled from js). (text_ifr)
|   |-> Insert/edit image button (#mceu_??-button)
|
|-> Edit Dialog (.mce-floatpanel)
    |-> iFrame Laravel filemanager (lfm)

Seems like lfm needs to write to a field in the .mce-floatpanel (#mceu_123-inp) and then close.
But that is not possible:
Firefox:
SecurityError: Permission denied to access property "document" on cross-origin object laravel-filemanager:600
	useTinymce4AndColorbox https://mysite.local/laravel-filemanager:600:5
	useFile https://mysite.local/laravel-filemanager:638:7
	<anoniem> https://mysite.local/laravel-filemanager:406:3
	dispatch jquery.js:4664:14
	add/r.handle jquery.js:4333:5

or (Chromium):
laravel-filemanager?field_name=mceu_59-inp&type=Images:600 Uncaught DOMException: Blocked a frame with origin "https://mysite.local" from accessing a cross-origin frame.
    at useTinymce4AndColorbox (https://mysite.local/laravel-filemanager?field_name=mceu_59-inp&type=Images:600:12)
    at useFile (https://mysite.local/laravel-filemanager?field_name=mceu_59-inp&type=Images:638:7)
    at HTMLDivElement.<anonymous> (https://mysite.local/laravel-filemanager?field_name=mceu_59-inp&type=Images:406:3)
    at HTMLDocument.dispatch (https://cdnjs.cloudflare.com/ajax/libs/jquery/1.11.2/jquery.min.js:3:8549)
    at HTMLDocument.r.handle (https://cdnjs.cloudflare.com/ajax/libs/jquery/1.11.2/jquery.min.js:3:5252)

Not sure what the source of the problem is.
No browser Developer tools shows me  the frame name/id with corresponding domain/port/protocol.
Not sure if the problem is with TinyMCE, LFM, or simply a browser update.
Please point me in the right direction?

Is the window with the filemanager you are opening on a different domain than where you are filling the input field on?

No. Everything should be on the same.
References are relative.
TinyMCE filebrowser Callback:
file_browser_callback: function(fieldName, url, type, win) {
    var x = window.innerWidth ||
        document.documentElement.clientWidth ||
        document.getElementsByTagName('body')[0].clientWidth;
    var y = window.innerHeight ||
        document.documentElement.clientHeight ||
        document.getElementsByTagName('body')[0].clientHeight;

    var cmsURL = config.path_absolute + 'laravel-filemanager?field_name=' + fieldName;
    if (type == 'image') {
        cmsURL += '&type=Images';
    } else {
        cmsURL += '&type=Files';
    }

    tinyMCE.activeEditor.windowManager.open({
        file: cmsURL,
        title: 'Filemanager',
        width: x * 0.8,
        height: y * 0.8,
        resizable: 'yes',
        close_previous: 'no',
    });
},

on which the config.path_absolute is '/'.

Swapped LFM for RFM
Same CORS Error.
So this seems to be an error not/less with the FileManager.
Remains: nginx (config?), Laravel, tinyMCE.
Same error on both Production Server (Ubuntu 16.04 LTS) as Docker Development environment (nginx:alpine, phpdockerio/php7-fpm)
Simular error texts in Firefox 61 & Chromium 67
I would very much like to know where I made my mistake...

@gwleuverink Willem?
Any Idea's?
Anybody else?

Hey sorry for the late reply. I've been racking my brain about this but it is a really hard problem to debug. CORS errors have caused me my share of pain in the past. One thing I noticed, are you serving your development environment over https? I see https in your error output but not many people serve their dev domain over https so i'm wondering if that might be it. It's a long shot though

Yes. I set the dev to self-signed Https
Browsers keep bugging me about that every now and then, but I'm gives me the opportunity to debug protocol issues.
I tried changing to http also, same problem. It still could be a problem in nginx (settings), but it is not just Https.
Is there a browser that gives the right error on the right lines of code?
This problem does give me headaches.

Your opinion on work-arounds:
Loose the iframe
Would it be possible to load the file manager inside a div instead of an iframe?
That way, we don't have the CORS issue, right?
Load everything same-host
PHP Scripts should already be on the same-host, so maybe the initiating code is from a CDN-served JS? Would it be an idea to load those through a (php) proxy of the same origin?
That way everything should come from the same protocol, host, port.
I know that would only account for the filemanager, not the client code (i.e. not TinyMCE, or initiating code)

Found it!
I set the document.domain flag elsewhere in code in order to communicate between cms and shop.
It needs to be on your parent (top) window, on the iFrame AND on the file manager.

Found it!
I set the document.domain flag elsewhere in code in order to communicate between cms and shop.
It needs to be on your parent (top) window, on the iFrame AND on the file manager.

Can you show me what files i need document.domain? I have a same issue when using vuejs with laravel-filemanager. I'm using window.open instead of iframe. Thank you.

Good evening , i have same problem can any one share the solution for us please

Can you show me what files i need document.domain? I have a same issue when using vuejs with laravel-filemanager. I'm using window.open instead of iframe. Thank you.


Add GraalVM to the PR build matrix

Motivation:
Native image compatibility is fragile and breaks easily, so we need a PR build to tell us when this happens.
Modification:
Add a graalvm-based build to the PR build matrix.
Result:
Every PR is now also tested on Graal.
These changes were extracted from #11163

@chrisvest thanks !


Address logged during script execution is different from the actual address deployed

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (fbad377 2024-06-04T00:17:42.494712000Z)
What command(s) is the bug in?
forge script
Operating System
macOS (Apple Silicon)
Describe the bug
We are noticing some weird behavior whereby when we log the address computed and returned by the ComposableStablePoolFactory using console2.log, the actual deployed address deployed and emitted in the pool creation event is different.
Here's a video replicating the issue:
https://asciinema.org/a/EJNtfBkOVtlD3OdLUHgOh5e4t
We also prepared this repo that we used replicating the issue above:
https://github.com/0xAplki/foundry_bug_replication
For extra context, the PoolFactory seems to be computing the address using a salt:
   bytes32 someBytes32 = keccak256(
            abi.encode(address(this), vm.getNonce(ANVIL_PUB_KEY))
        ); // salt

   address csp = IComposableStablePoolFactory(cstFactory).create(
            _name,
            _name,
            tokens,
            200,
            TokenArrays.createTwoTokenArray(address(0), address(0), true),
            TokenArrays.createValueList(10800, 10800),
            false,
<PHONE_NUMBER>00000,
            makeAddr("asdf"),
            someBytes32 // salt
        );

it utilized in two ways:
during pool creation: https://github.com/balancer/balancer-v2-monorepo/blob/36d282374b457dddea828be7884ee0d185db06ba/pkg/pool-utils/contracts/factories/BasePoolFactory.sol#L92
in their code splitting mechanism here:
https://github.com/balancer/balancer-v2-monorepo/blob/master/pkg/solidity-utils/contracts/helpers/BaseSplitCodeFactory.sol

This is happening because internally ComposableStablePoolFactory is using values affected by block.timestamp when constructing CREATE2 salt for pool deployment:

here pauseWindowDuration is calculated in getPauseConfiguration function which does the following:

when simulating script transactions, we don't know what will the block.timestamp value be once transactions land, and because of that there is mismatch between addresses in logs vs on-chain

@klkvr thanks a lot for digging and finding the root cause of this issue!
Logging the pool address before the vm.stopBroadcast() call still outputs what seems to be the pool address computed during the simulation (even with the --skip-simulation flag set); with the skip simulation flag set I would have thought that any console.log in between start/stop broadcast is based of TX data that has been broadcast (mined?).
I don't understand the internals of how forge works so this assumption might be off the mark

In fact forge does not collect and display actual on-chain logs at all.
Script execution is performed in 3 steps:

A single call to run performed on a fork, which collects transactions which should be broadcasted.
(that one is being skipped by --skip-simulation) All collected transactions are being simulated separately with cheatcodes disabled to ensure correctness and estimate gas usage.
If step 2 was succesful, transactions are getting broadcasted.

I can see how showing the actual execution logs could be helpful, however, it is pretty expensive operation (try cast run on a massive tx), so I believe it'd have to be disabled by default

ok this is great info @klkvr
happy to have this ticket closed since Foundry / Forge behaves as designed


Update dependency ID

PromisePlugin changed its plugin id. Thus, install via cordova CLI of aerogear fails. This commit fixes the dependency.

:+1:  looks good,  thanks for the pR


pr-labels job is failing on CI

Our "PR label bot" hasn't been commenting on PRs for a bit. Looks like it's broken https://github.com/pytorch/vision/actions/workflows/pr-labels.yml
Run mshick/add-pr-comment@v1
  with:
    message: Hey @NicolasHug!

  You merged this PR, but no labels were added. The list of valid labels is available at https://github.com/pytorch/vision/blob/main/.github/process_commit.py

    allow-repeats: false
  env:
    pythonLocation: /opt/hostedtoolcache/Python/3.12.1/x64
    LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.12.1/x64/lib
    GITHUB_TOKEN: ***
Error: Resource not accessible by integration

(Note that https://github.com/pytorch/vision/pull/8221 is related but the pr-labels action was broken before this was merged)

CC @pmeier in case this is something you have time looking into - but no worries if not

Hi @NicolasHug, is this a beginner friendly issue? If yes, can I work on this?

Hi @Bhavay-2001 unfortunately no, this isn't really beginner friendly

Hi @NicolasHug, it would be great if you could suggest me some beginner friendly issues to start with.
Thanks


CLI note

This PR moves the CLI Note on the main index page below the hero image. While this rendered fine locally and on stage, I think the hero may be in a <div> which is suppressing the note.

issue seems to have resolved itself


Write about Sprint 4 in the Rust Gamedev newsletter for May 2021

Deadline: June 6.
Keep an eye on https://github.com/rust-gamedev/rust-gamedev.github.io/issues/640 and prepare to submit the newsletter before the publication deadline: June 6 (BEFORE the end of our sprint, June 12). Helped wanted!

Done: https://github.com/rust-gamedev/rust-gamedev.github.io/pull/667


Make sort case-sensitive

Currently, isort ignores case when sorting modules. This behavior conflicts with some stricter sorting styles, like i.e. "cryptography" style. This style requires sorting to put upper-case starting modules first, lower-case modules second.
This PR fixes this issue by removing an unnecessary coercion to .lower() in isort's core modules sorting routine.

Oops, someone already fixed that ))


fix external deps

This isn't exactly pretty, but it fixes this problem:
echo 'import * as tea from "https://raw.github.com/teaxyz/lib/v0.3.0/mod.ts"' >foo.ts && deno check --unstable foo.ts
error: Relative import path "is-what" not prefixed with / or ./ or ../
    at https://raw.githubusercontent.com/teaxyz/lib/v0.3.0/src/utils/semver.ts:1:35

echo 'import * as tea from "../tea/lib/mod.ts"' >foo.ts && deno check --unstable foo.ts
Check file:///Users/jacob/foo/foo.ts

Basically, import maps don't externalize, meaning any consumer needs to provide our deps... that part seems deeply incorrect.

Looking at the tests... I'm not actually sure how it worked before...

I don't think it's unreasonable that consumers of the deno portion are expected to add our deps to their import map.
So this isn’t so much a fix as an opinion on how we should expect deno users to use libtea.

Looking at the tests... I'm not actually sure how it worked before...

the import map is in deno.json

quite possibly we should just do this.
one reason I am hesitant is it allows eg. tea/cli to define which version of eg. is-what is used rather than potentially having multiple.

It was an unexpected outcome for me, certainly. I don't know off the top of my head of another Deno dep that requires side dependencies in this way.

I don't know off the top of my head of another Deno dep that requires side dependencies in this way.

yeah good point. ugh.


Buffers do not get restored when nerd tree is open when saving the session, and the current working directory is ~

I don't have time to create a minimal vimrc file at the moment, I will try to get around to that sometime in the future (no guarantees when). But these are the replication steps:

Open Vim in your home directory
Open two files (i.e. buffers)
Open nerd tree
Save the session with vim-session
Close Vim
Reopen Vim. Only one of the two files is restored

I can repro, will try to fix. No need for minimal vimrc.

This looks like a special interaction between vim-session and Nerdtree. During the session load of Nerdtree, vim-session does some extra steps to restore Nerdtree, which in turn destroys the wintabs session. This wouldn't happen if you use :mksession and :so. So I'm afraid I can't fix this issue completely.
One way to mitigate the issue is that: when this happens, call :WintabsAllBuffers. This should be able to restore your buffers from last session.

I'm closing this since it cannot be fixed since vim-session does a lot of extra stuff with nerdtree and disrupts normal wintabs buffer restore.


Exercise's view: The buttons are not adapted to the same size.

Describe the bug
Just the Iris button has a correct height

To Reproduce

Go to any programming exercise as an isntructor and check that you can see the same as the screenshot!

Expected behavior
all buttons should keep the same height. None of them are double-line
Screenshots

Which version of Artemis are you seeing the problem on?
6.7.5
What browsers are you seeing the problem on?
Chrome
Additional context
No response
Relevant log output
No response

Duplicate of #7879.


Document minimal neovim version for Copilot

Why:
Closes #21725
What's being changed (if available, include any code snippets, screenshots, or gifs):
Adds information about the minimum Neovim version for Copilot. This is based on the current code
Check off the following:

[ ] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[ ] For content changes, I have completed the self-review checklist.

@Kixunil Thank you for opening a PR and linking it to your issue! ✨
I'll get this triaged for review ⚡


CSS not always 'require'd in dev mode

Webpack in production mode correctly collects all the css, but not in dev mode.
I'm running webpack like cd ./src/app && NODE_ENV=dev /usr/bin/env node node_modules/webpack/bin/webpack.js -d --watch --progress --config webpack-dev.config.js and its configuration is:
// webpack-dev.config.js
var shared = require('./webpack-shared.config');
var webpack = require('webpack'),
    path    = require('path'),
    ExtractTextPlugin = require("extract-text-webpack-plugin"),
    nodeModulesDir = path.resolve(__dirname, 'node_modules');
var config = shared({
  devtool: "eval-source-map", // https://webpack.github.io/docs/build-performance.html
  resolve: {
    alias: {}
  },
  module: {
    noParse: [],
  },
  plugins: [
    new ExtractTextPlugin("./styles.css"),
    new webpack.optimize.CommonsChunkPlugin('./js/commons.js', ['app', 'index'])
  ]
});
module.exports = config;

// file that includes shared options
var _ = require('./js/lib/underscore'),
    webpack = require('webpack'),
    path    = require('path'),
    nodeModulesDir = path.resolve(__dirname, 'node_modules'),
    ExtractTextPlugin = require("extract-text-webpack-plugin");

module.exports = function(overrides) {
  return _.merge({
    entry: {
      './js/index': './js/index', // start page
      './js/app': './js/app', // actual app
      /*'app-common': [
        'react',
        'react-router',
        'jquery',
        'moment'
      ]*/
    },
    output: {
      path: path.resolve(__dirname, '..', '..', 'build', 'app'),
      filename: '[name].js', // consider hashing?
      sourceMapFilename: '[file].map',
      chunkFilename: "[id].js"
    },
    devtool: 'source-map',
    module: {
      // load logary-js source maps into published source maps
      preLoaders: [
        {
          test: /(logary\..+|client)\.js$/,
          loader: "source-map-loader"
        }
      ],
      loaders: [
        { test: /\.js$/, loader: 'jsx-loader?harmony', exclude: [nodeModulesDir] },
        { test: /\.css$/, loader: ExtractTextPlugin.extract("style-loader", "css-loader") },
        //{ test: /\.css$/, loader: 'file-loader?name=[path][name].[ext]?[hash]&context=.' },
        { test: /\.(png|jpg|jpeg|gif|woff)$/, loader: 'url-loader?limit=8192' },
        { test: /\.(otf|eot|ttf)$/, loader: "file-loader?prefix=font/" },
        //{ test: /\.(otf|eot|ttf)$/, loader: "file-loader?name=[path][name].[ext]?[hash]&prefix=font/" },
        { test: /\.svg$/, loader: "file-loader" },
      ]
    }
  }, overrides);
};

There's a ReactJS component, saveDetails.js, with saveDetails.css. When I compile with production:
var shared = require('./webpack-shared.config');
var webpack = require('webpack'),
    path    = require('path'),
    ExtractTextPlugin = require("extract-text-webpack-plugin");

module.exports = shared({
  plugins: [
    new ExtractTextPlugin("./styles.css"),
    new webpack.optimize.CommonsChunkPlugin('./js/commons.js', ['app', 'index']),
    new webpack.optimize.DedupePlugin(),
    new webpack.optimize.UglifyJsPlugin()
  ]
});

it all works. But not when I have the dev server running; then saveDetails.css is never inserted into the final css file, styles.css.
All that's in saveDetails.js is require('./saveDetails.css'.
"webpack": "1.9.10",  "css-loader": "^0.14.4" doesn't work.
Also,
   "devDependencies": {
-    "css-loader": "^0.14.4",
-    "extract-text-webpack-plugin": "0.8.1",
+    "css-loader": "^0.15.4",
+    "extract-text-webpack-plugin": "0.8.2",
     "file-loader": "*",
     "imports-loader": "^0.6.4",
     "jsx-loader": "*",
-    "react-hot-loader": "^1.2.7",
+    "react-hot-loader": "^1.2.8",
     "source-map-loader": "^0.1.5",
     "style-loader": "0.12.3",
     "url-loader": "*",
-    "webpack": "1.9.10"
+    "webpack": "1.10.1"
   },

doesn't work.

I'm closing this issue because of inactivity. Feel free to comment, and we can always re-open it again.

Sure; closing is OK if you want to. I don't use the css loader like this any longer, due to problems like this.


Take focus from game during calls on iOS

Closes ppy/osu#4565
Split from https://github.com/ppy/osu-framework/pull/6449

Again, this is not normal behaviour of any iOS app, as incoming calls have recently been acting more like a glorified notification than a full-screen overlay. However, as a rhythm game, exclusive access to the audio is required for the game to function appropriately, therefore we have to observe for incoming calls and cut focus from the game in order to be aware that it should not remain operating (i.e. send to pause screen).
The framework may not be exclusively for rhythm games, but I think it's simple to have this anyway until we get a report about it from other framework consumers.

To clarify, this is avoiding the game becoming unusable when a phone call arrives? Because your description sounds like this is an optional change, and not having it would just mean that the phone call notification shows on top of the game.
Maybe you could show a video of what happens with/without this to clarify.

I briefly mentioned it in https://github.com/ppy/osu-framework/pull/6449#issue-2727329289 but forgot to mention here. This change is mandatory for osu!, otherwise when someone receives a call the beatmap freezes and osu! thinks the audio system is at fault and excludes the score from submission.


feat: add the @digir/create-tokens CLI tool

Resolves #2084
Example run

The output of that run can be found in this repository

We'll probably move this in under cli and expose it as an init command (or/and @designsystemet/create-tokens)

Yes, I was thinking that this was probably a good idea, with a thin wrapper for use with npm init if you want it. But the difference between npm init @digdir/tokens and npx @digdir/designsystemet create-tokens or whatever is pretty insignificant, both need to be discovered in documentation anyway.

I see we also have to find a good way to keep our template updated 🤔

Agreed! It would be nice to have a source of truth for the token structure (for the theme builder, this tool, and the template repo -- possibly other tools as well?). As a stopgap, you could conceivably regenerate the template repo using this tool 🤔 The output will be slighly different, as the themes will be named "Theme" and "Theme2". If you add some CLI parameters which skip interactive questions, it could be automated in a Github workflow.

I see we also have to find a good way to keep our template updated 🤔

Agreed! It would be nice to have a source of truth for the token structure (for the theme builder, this tool, and the template repo -- possibly other tools as well?). As a stopgap, you could conceivably regenerate the template repo using this tool 🤔 The output will be slighly different, as the themes will be named "Theme" and "Theme2". If you add some CLI parameters which skip interactive questions, it could be automated in a Github workflow.

Yeah, we are still exploring this field. Them same goes for output in terms of transformed tokens to say css variables. Styled Dictionary came out with a new feature (exportPlatform) 2-3 weeks ago actually that will make the latter much easier for sharing the logic between tools!

@mimarz I moved the code into packages/cli, adding an init command, while keeping packages/create-tokens. You can decide if you want to keep the latter or not :)

@mimarz I moved the code into packages/cli, adding an init command, while keeping packages/create-tokens. You can decide if you want to keep the latter or not :)

Wicked, thanks! This will help a lot.
Yeah, I haven't had the time to look at it yet, since theres been a lot of new edge-cases to solve with multiple typography and "dimensions" support.
Not sure if we'll make it ready for tomorrows demo, but we can always save it for the next one! We have quite a lot of new stuff prepared for tomorrow :)


Improve Get started with .NET Core experience

Topic: https://docs.microsoft.com/en-us/dotnet/core/get-started
The page is a bit overwhelming for a new .NET Core developer. We should simplify it.

This is a high priority, but there is quite a bit of work to break this up and not lose the information that is part of the current topic.

What about splitting it up into Windows/Linux/macOS tabs?  Do we use tabs in the DotNet docs?  Here's an example of what I'm talking about.
Also, it seems to me the Hello World tutorial should be made a bit more prominent.

I've done some work in conjunction with sites like wikiHow to improve articles and to make them more readable/welcoming for new users. If someone covers the technical stuff, I can go through and do some work on the wording to encourage new users. I'm not sure if I'd be able to do that much due to time restrictions but still....

How about just using this page as a landing page with links to individual pages for each operating system?
Eventually, the individual pages for each OS will probably be linked up and accessed directly most times. There is really no reason to have Windows, Linux, and MacOS all in one page.

@ricardodsanchez - That's why I mentioned the tabs - That way the URL doesn't change, and we still simplify the page for the user.  Also, DocFx (the documentation platform) is going to have the capability to automatically select the tab relevant for the user's OS sometime in the near future (if it's not there already).


Failed  : python 3.8, torch1.8.0+cu111, ubuntu18.06

Error to compile with both master & torch1.6 branches, anybody help me?

oh， my device is TRX 3080

this doesn't support old torch, it just support latest pytorch, read readme first. for old version switch branch.


Crash while export

Hello,
This project is great (y), but I faced with few crashes on my application:

*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '***
-[AVAssetWriterInput appendSampleBuffer:] Must start a session (using -[AVAssetWriter startSessionAtSourceTime:) before appending sample buffers'

*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '***
 -[AVAssetWriterInput markAsFinished] Cannot call method when status is 0'

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '***
-[AVAssetReader initWithAsset:error:] invalid parameter not satisfying: asset != ((void *)0)'

Config is:
    SDAVAssetExportSession *session = [[SDAVAssetExportSession alloc] initWithAsset:composition];
    session.videoComposition = videoMix;
    session.audioMix = audioMix;
    session.videoSettings = @{
        AVVideoCodecKey : AVVideoCodecH264,
        AVVideoWidthKey : @640,
        AVVideoHeightKey : @640,
        AVVideoCompressionPropertiesKey : @{
            AVVideoAverageBitRateKey : @2000000,
            AVVideoProfileLevelKey : AVVideoProfileLevelH264Baseline31,
        }
    };
    session.audioSettings = @{
        AVFormatIDKey : @(kAudioFormatMPEG4AAC),
        AVNumberOfChannelsKey : @2,
        AVSampleRateKey : @44100,
        AVEncoderBitRateKey : @64000,
    };

    session.outputURL = [[NSURL alloc] initFileURLWithPath:outPath];
    session.outputFileType = AVFileTypeMPEG4;
    session.shouldOptimizeForNetworkUse = YES;

Plus I'm using custom videoComposition and audioMix
They happens rarely - hard to reproduce, but.. any thoughts why this happens? Recommendations?

I had a similar issue that rarely occurred and nearly drove me mad. Turns
out it was due to the rare case that input video had 0 audio tracks. (Think
of 4x video filmed in an iOS device, for example. Apple removes the audio
tracks from the video asset).
On Tue, Feb 10, 2015 at 11:00 AM, Aleksey Garbarev<EMAIL_ADDRESS>
wrote:

Hello,
This project is great (y), but I faced with few crashes on my application:

*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '***
-[AVAssetWriterInput appendSampleBuffer:] Must start a session (using -[AVAssetWriter startSessionAtSourceTime:) before appending sample buffers'

*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '***
-[AVAssetWriterInput markAsFinished] Cannot call method when status is 0'

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '***
-[AVAssetReader initWithAsset:error:] invalid parameter not satisfying: asset != ((void *)0)'
Config is:
SDAVAssetExportSession *session = [[SDAVAssetExportSession alloc] initWithAsset:composition];
session.videoComposition = videoMix;
session.audioMix = audioMix;
session.videoSettings = @{
    AVVideoCodecKey : AVVideoCodecH264,
    AVVideoWidthKey : @640,
    AVVideoHeightKey : @640,
    AVVideoCompressionPropertiesKey : @{
        AVVideoAverageBitRateKey : @2000000,
        AVVideoProfileLevelKey : AVVideoProfileLevelH264Baseline31,
    }
};
session.audioSettings = @{
    AVFormatIDKey : @(kAudioFormatMPEG4AAC),
    AVNumberOfChannelsKey : @2,
    AVSampleRateKey : @44100,
    AVEncoderBitRateKey : @64000,
};

session.outputURL = [[NSURL alloc] initFileURLWithPath:outPath];
session.outputFileType = AVFileTypeMPEG4;
session.shouldOptimizeForNetworkUse = YES;

Plus I'm using custom videoComposition and audioMix
They happens rarely - hard to reproduce, but.. any thoughts why this
happens? Recommendations?
—
Reply to this email directly or view it on GitHub
https://github.com/rs/SDAVAssetExportSession/issues/21.

@axpence Thanks for response
I figured out that crash #3 was my fault - (AVAsset was nil). But others are still here.
Let's see If I can found the reason..
Also I have AVPlayer which plays my composition, videoComposition and audioMix at same time during export. (Could it is be a reason? Probably not)

@alexgarbarev
How do you solve

@longhongwei17 solved my removing that library from my project and using standard AVAssetExportSession.

I'm also having the issue (using Swift 4) that happens maybe 1/20 times. I can barely find any info online about it. It crashes when I end the recording. It shows nothing in my code where it crashed, except in assembler in "libsystem_kernel.dylib`__pthread_kill:", but it appears that it crashes on endSession(atSourceTime:).

Did anyone find a solution for this? @alexgarbarev did was it a big job to swap out and use the standard AVAssetExportSession?

Check the AVAssetWriterStatus before call "appendSampleBuffer:(CMSampleBufferRef)sampleBuffer".
Sometimes the session will be cancel / failed by system.


the install script should ignore pre-releases

If there are releases like v0.1.17-prerelease-002 - the install script that lives here will still try to install them

This can cause problems if the signature file is not uploaded as part of the pre-release
Let's make the install script only pay attention to actual releases

How hard core should we be? I feel like the regex /^v([0-9]+).([0-9]+).([0-9]+)$/ is good for me

I don't have push permissions to https://github.com/bacalhau-project/get.bacalhau.org so here is a "PR" until I can get those:
the static/install.sh -> getLatestRelease function needs to be this:
getLatestRelease() {
    local bacalhauReleaseUrl="https://api.github.com/repos/${GITHUB_ORG}/${GITHUB_REPO}/releases"
    local latest_release=""

    if [ "$BACALHAU_HTTP_REQUEST_CLI" == "curl" ]; then
        latest_release=$(curl -s $bacalhauReleaseUrl | grep \"tag_name\" | grep -E -i '^v[0-9]+\.[0-9]+\.[0-9]+$' | grep -v rc | awk 'NR==1{print $2}' |  sed -n 's/\"\(.*\)\",/\1/p')
    else
        latest_release=$(wget -q --header="Accept: application/json" -O - $bacalhauReleaseUrl | grep \"tag_name\" | grep -E -i '^v[0-9]+\.[0-9]+\.[0-9]+$' | grep -v rc | awk 'NR==1{print $2}' |  sed -n 's/\"\(.*\)\",/\1/p')
    fi

    ret_val=$latest_release
}

which will apply grep -E -i '^v[0-9]+\.[0-9]+\.[0-9]+$' which ensures that we are only looking for releases for the form v0.1.18


fix: rust impl new fn for Boxed values

Description
I upgraded to 1.0.0-next.30 and noticed Rust's new() function implementation is broken for any schema with a $ref to another schema.
Schema where I first noticed this issue: https://github.com/bitsy-ai/printnanny-asyncapi-schema/blob/main/2.4.0/printnanny-os.yml
Edit: I also noticed indentation is off by 4 spaces in struct implementation fns. I fixed that as well: https://github.com/asyncapi/modelina/pull/1013/commits/0db9d9f09f90c5d2ad2fec1a4360571a186f929d
Related issue(s)
closes issue #1012

/rtm


Go samples Migration to fabric-gateway

For a single feature we typically like to see a single commit in the main commit history.
Here are instructions for squashing your commits into a single commit:
https://hyperledger-fabric.readthedocs.io/en/latest/github/github.html#updating-a-pull-request
In the future it may be easier to use the git commit --amend approach that is described instead of creating new commits.

For a single feature we typically like to see a single commit in the main commit history.

I definitely agree with having a single commit for the merged PR, but we can get regardless of whether multiple commits are pushed to the PR using Squash and merge. Pushing a new commit to address review comments does make it much easier to see what changed after the last review, whereas always squashing commits makes it impossible.


toolchain updates with *-hid-sections.cmake

For default hidden visibility with function-sections + data-sections flags for more granular library stripping:
include("${CMAKE_CURRENT_LIST_DIR}/flags/function-sections.cmake")
include("${CMAKE_CURRENT_LIST_DIR}/flags/data-sections.cmake")
include("${CMAKE_CURRENT_LIST_DIR}/flags/hidden.cmake")

Also, .gitignore emacs files!

Applied with the few cleanups and fix.

Thank you.


Consuming Hermes from source in a React Native app

Bug Description
My goal is to make use of a custom build of hermes running in a react native app. Following the docs works fine for me until I have to run the command below.
– The only thing that comes to mind is that I had to add ANDROID_SDK_ROOT to my environment, I made it the same as ANDROID_SDK. Also ANDROID_SDK_ROOT is deprecated.
$ ninja github-cli-release
ninja: error: unknown target 'github-cli-release'

[ ] I have run gradle clean and confirmed this bug does not occur with JSC

Hermes version: 0.12.0
React Native version (if any): 0.72.3
OS version (if any): N/A
Platform (most likely one of arm64-v8a, armeabi-v7a, x86, x86_64):
Steps To Reproduce

Run the commands below to build a release version of Hermes:
cmake -S hermes -B build_release -G Ninja -DCMAKE_BUILD_TYPE=Release
cmake --build ./build_release
Run the command below to package CLI binaries for the current platform
cd $HERMES_WS_DIR/build_release && ninja github-cli-release

Produces error "ninja: error: unknown target 'github-cli-release'"
code example:
N/A
The Expected Behavior
Command ninja github-cli-release should run successfully.

@carlosalmonte04 to unblock yourself, I would just comment out the Flipper initialization on MainApplication.java:60

at com.awesomeproject072.MainApplication.onCreate(MainApplication.java:60)

Finally got it working! Gosh, that took some time to build. Thanks @cortinico. I don't even know where to start from or what usages I can have have with this power. Thanks again.

Great thanks for reporting back 👍

How can I accomplish this same task on iOS?

Hi @carlosalmonte04, I haven't test it and right now I really can't, but if you install pods with:
BUILD_FROM_SOURCE=true bundle exec pod install

It should take the commit of Hermes we are using for the version of react native and build it from source.
Beware, it will take some time to build.

hermes-utils.rb
hermes-engine.podspec

Thanks @cipolleschi. In addition to that I also had to change the git url in hermes-utils.rb to point to my fork of hermes.
That url should probably be an environment variable, similar to Android's REACT_NATIVE_OVERRIDE_HERMES_DIR variable.
Thanks again for responding even though the issue was already closed.
😃


Husky precommit error when using Gitpod

Describe the bug
Husky precommit fails with Gitpod whenever I'm making a commit.
Give the steps to reproduce

Open repository in Gitpod
Make sure the initial Yarn run completes succesfully
Edit a file, and save changes in VSCode
Create a new commit with `git commit -m "message"
Husky runs and fails to complete successfully:

yarn run v1.22.15
$ /workspace/octoclairvoyant/node_modules/.bin/lint-staged
✔ Preparing...
✔ Running tasks...
✔ Applying modifications...
✔ Cleaning up...
Done in 1.73s.
.husky/pre-commit: 12: Syntax error: "(" unexpected (expecting "then")
husky - pre-commit hook exited with code 2 (error)

What browsers are you seeing the problem on?
Bug is not about browser
Have you thought of a possible solution?
No
If you have thought of a solution, please tell us about it!
No response
Do you want to help fix the bug?
Yes
Is there anything else we need to know?
I don't know what's causing this problem, it might be something specific to our Gitpod setup, like a incorrect version of node/yarn/whatever. It might be a limitation of Gitpod that it does not work with husky correctly.
Maybe you can try to debug what's going wrong? I assume it works on your local workstation just fine?

No idea about this to be honest, and I'm afraid I don't have time to take a look at it. I'd create an issue in gitpod repo instead so they can take a look at it.


[PE-D][Tester A] DG Model Component has Diagram with no explanation

There is an unexplained diagram in the Model Component. Since there is no explanation it is quite confusing. In AB3 there was an explanation that this diagram represents an alternative implementation, but here the explanation is missing.

Labels: type.DocumentationBug severity.Medium
original: AbdulrahmanAlRammah/ped#24

Put explanation back from AB3

delete

DG Page 6


Request new module: cp-watson-knowledge-catalog

Related user story
https://github.ibm.com/gsi-labs/industry-cloud-planning/issues/542
Type of module
gitops
If requesting a terraform module, what is the target cloud platform?
ibm
What is the purpose of the module?
Gitops module to install Watson Knowledge Catalog on Cloud Pak for Data
What is the category of the module?
service

/displayName CP Watson Knowledge Catalog

/softwareProvider ibm-cp


Add east-west and IPv4 load balancing

Reworks the load balancing code and makes most of the code available for reuse.
Adds the following capabilities:

Balancing between containers on the same node
Balancing between containers on different nodes
Balancing from and to arbitrary IPs
IPv4 support (limited)

IPv4 limitations:

This does not include any work to carry the reverse NAT index in the packet from node to node. Reverse translation with IPv4 currently only works on the same node.

Example config, L3 load balancer based on L4 hash:
SVC_IP6="f00d::1:1"
LB_PORT=0
REVNAT=222
sudo cilium lb create-services-map
sudo cilium lb update-service $SVC_IP6 $LB_PORT 0 2 $REVNAT :: $LB_PORT
sudo cilium lb update-service $SVC_IP6 $LB_PORT 1 2 $REVNAT $SERVER1_IP $LB_PORT
sudo cilium lb update-service $SVC_IP6 $LB_PORT 2 2 $REVNAT $SERVER2_IP $LB_PORT
sudo cilium lb create-rev-nat-map
sudo cilium lb update-rev-nat $REVNAT $SVC_IP6 $LB_PORT

In general it looks much cleaner and simpler to use. Have a few comments inline. Thanks.

Aside my comments LGTM, waiting for @mchalla

I will merge this since this is well tested by now.


Google Chrome deactivated my extension and won't allow me to activate it again

Guys, what happened? I can not activate it again. Chrome says it may be unsafe and deactivated it automatically.

@ChromeCanary  thanks. enabling extension api worked for me.

Terrible


An ATL can view all expected results for a C4 Tests

A new link on a product test, "View Expected Result Patients", allows an ATL to view expected results for C4 Tests with the same depth as the "View Patients" link.
Totals for populations also now appear at the footer of a table for a measure and test.
Submitter:

[x] This pull request describes why these changes were made.
[x] Internal ticket for this PR: https://jira.mitre.org/browse/CYPRESS-110
[x] Internal ticket links to this PR
[x] Code diff has been done and been reviewed
[x] Tests are included and test edge cases
[x] Tests have been run locally and pass

Reviewer 1:
Name: Robert Clark

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[x] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

It may be good to have some cucumber tests which at least navigate to the by_filter_task page in order to catch errors like the one I was experiencing before in this code in the future.

Should vendors be allowed to see expected patient results or just ATL/Admin roles?

Just ATL/Admin, when we're not ignoring roles.

@ljades I would agree with @rbclark here that we should write some Cucumber tests for this.

Lets change the name from "View Expected Result Patients" to "View Expected Result"
Remove the original "Expected Patient Records (1)" section (on the Category I page)


fix: keep the release iso cached

This does not rename the release iso so that it will picked up in subsequent runs.
Fixes #50

Looks good, thanks!


implemented new footer design

What does this PR do?

redesigns the footer to fit new design

Description of Task to be completed?

How should this be manually tested?

npm start

What are the relevant Trello Card stories?  Trello Card Item

Pull Request Type (check one)

[ ] Feature
[ ] Bug Fixes
[ ] Chore

Developer Checklist

[ ] New code has been scanned for ESlint issues
[ ] I have tested my code locally
[ ] I made sure that there are no other pull requests that solve for this issue
[ ] My code follows the same structure within the guidelines

Screenshots (if appropriate)

Could you resolve the conflicts? @iamcristos

Can you change SAY THEIR NAME to SAY THEIR NAMES?

Could you change SAY THEIR NAME to SAY THEIR NAMES in Our Mission?

Could you update this branch so we can get it merged in?
Nice work!


Easy method of adding a margin?

Hi Peter,
Just started using the writer.py to go hand-in-hand with a large epaper screen I'm working on.
I noticed upon first use that the text of the first line begins at (x,y) = (0,0), which makes it a little unpleasant to look at and can sometimes be impractical.
I've read through the writer.py and to me, it seems that there isn't an easy method of setting horizontal and vertical margins. Is that correct?
If so, what would be the easiest way to add variable/s that would allow margins but still retain all the word wrap functionality?
Thanks,
Thomas

There isn't a built-in way to do this. I guess you'd need an inner rectangle with size smaller than the physical display with text logically constrained to that. Rendering would be to the outer physical rectangle. This is a new request so is not something I've considered.
I want to keep the Writer class minimal so would prefer to see functionality added by subclassing, but if you submitted a PR based on that approach I would certainly consider it.

Okay, no worries. When you say subclass, do you mean a separate file entirely? If so, I think I'll look into writing a writer_extended.py that is a little less lightweight but has some features that I think are important for rendering text to screens (such as margins, line start coords, etc.). I'm not sure if you'll be particularly interested in adding it to your repo but I'll be developing that sort of driver anyways for my project.

I meant to write a class derived from Writer. One option is to consider modifying the CWriter class. This keeps Writer lightweight. Another option is a subclass in a separate file. This has a couple of advantages. It keeps the API for the existing classes unchanged and avoids any extra overhead compiling writer.py.
The best solution rather depends on how much code is added, and without detailed study I haven't really got a handle on that.

I see. I'll take a look into building up a subclass in a separate file and get back to you when I'm done with a pr. Thanks!


Cell Simulation Script

A script to generate test mutation matrices.
Generat random mutation trees possibly with networkX and sample cell attachment to create perfect or optionaly noisy mutation matrices and store tree, perfect and noisy mutation matrix.

Also, I could not think of any useful unit tests to write for this script. - Any suggestions?


Core Validation: Misleading error reported at dispatch call time

I came across the following debug call-back reported at vkCmdDispatch() call time:
DS ... encountered the following validation error at draw time: ..
"Dispatch time" should be used instead for improved clarity.

Fixed in PR #878 .


Question: What is const getAppSubState = get('app'); storing exactly in store/app/selectors.js line 4

I am trying to manipulate code to create a interest page for myself. I am not sure lodash/fp "get" is doing here.  When I look at the docs https://lodash.com/docs/4.17.10#get, it specifically states the get  function takes two arguments. You the get function in store/app/selectors.js and components/resume/index.jsx like this. What are you storing in these variables using the get function, and how are you only using one argument.

Below codes will same as comment.
import fp from 'lodash/fp';
// import _ from 'lodash';

const resume = fp.get('markdownRemark')(data);
// const resume = _.get(data, 'markdownRemark');
// it can also be, const resume = fp.get('markdownRemark', data);

And I recommend two pages to read.

Ducks modula redux
10 Tips for Better Redux Architecture
some of the practice is applied on this repository.

and about lodash.
_ and fp are different. fp is wrapped and it can help user to curry easily.
You can refer this page.
https://github.com/lodash/lodash/wiki/FP-Guide
FYI. it explains what is currying
/* not curried function */
function sumOfThreeThings(x, y, z) {
  return x + y + z;
}

sumOfThreeThings(1, 2, 3); // 6

/* curried function */
const sumOfThreeThings = x =>
  y =>
    z =>
      x + y + z;
sumOfThreeThings(1)(2)(3); // 6


Tooltip not being displayed in ObjectStatus

OpenUI5 version: 1.120.21
Browser/version (+device/version):Chrome
Any other tested browsers/devices(OK/FAIL):Edge
URL (minimal example if possible): https://sdk.openui5.org/entity/sap.m.ObjectStatus with tooltip
Steps to reproduce the problem:

Create a new object status Object in a toolbar view
The tooltip property should be in the constructor object
In the browser, hover on top of the created object status

What is the expected result? A tooltip should be displayed with the text provided during the creation of the object status Object
What happens instead? Nothing is being displayed
Code example:
return new Toolbar({
          content: [
            vBox,
            new ObjectStatus({
              text: "Sample text",
              state: "Information",
              tooltip: "Tooltip text"
            }
          ]
        })

Generates the following XML

Sample text
Tooltip text
Informative entry

This issue happens only in the latest version of 1.120.1
When testing with version 1.120.20 the tooltip is visible correctly, the xml output is also different

Sample text

Hello @tangirmiah ,
Thank you for sharing this finding. I've created an internal incident DINC0303694. The status of the issue will be updated here in GitHub.
Regards,
Petya Markova.
(UI5 Dispatcher)

Hello @tangirmiah ,
This issue is already fixed and the fix will be available in 1.120.22 version. It is also fixed for the latest versions of SAPUI5.
Best Regards,
Gery

Was fixed by: https://github.com/SAP/openui5/commit/2432140a388455a9a368c709f1b8639d0eee137c
Downport to 1.120: https://github.com/SAP/openui5/commit/672bd474354102c9b9c9435f7003fdfc96c14812


Run tests in CI

Thanks for this package!
It looks like currently Travis CI only build this crate without running tests. It would be nice if tests were also run.

Good idea!
I've added running the tests in cb01fbaef.


507 responses with "exceeded request buffer limit while retrying upstream"

This issue is a: (mark with an x)

[x] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
We have several (4) applications deployed as Container Apps, all sharing same Environment. Since Dec 1st, we started to experience 507 return codes with "exceeded request buffer limit while retrying upstream"
We are not aware of any significant change on our side, the traffic is generally the same.
AFAICS the error is coming from istio, so my assumption is that it's some new configuration being deployed on ACA side.
At one point I thought that the problem might come from the fact that our applications are sharing the Environment. So I created new Environments so I have a situation with 1-1 mapping for some (not all) applications. However the error is still there, even for those application that have unique environment.
Expected behavior [What you expected to happen.]
No 507 errors getting from my services.
Actual behavior [What actually happened.]
From time to time (like 1 in 100 requests, but that's not exact measure), we get 507 that we weren't used to get before Dec 1.

Just to update on this. @jsuchome I'm assuming you're using the auto authentication feature, right? There was a race condition introduced between when the application is ready vs when the auth service is ready. The sometimes the app gets ready before the auth service, and this causes the first couple of requests on activation (or scale out) to maybe reach an auth service that's not yet ready. This should be fixed in the next release.

@ahmelsayed , thanks for response! Yes, we're using authentication set up from Container Apps dashboard.
So you're saying this is happening during the scale out, when I am contacting the new replica(s)?
When can we expect new release?

this should be deployed now.

On aug 2023 at 9 20 pm UTC and aug 31 2023 on 12 29 am ist received this error code in our container app which runs fastapi
Kindly analyse this issue and avoid it in future


[OCaml] ols can't parse .mli file

Information
VIM version
NVIM v0.3.0                                                                                │~
Build type: Release
Operating System: MacOS
:ALEInfo
Current Filetype: ocaml
Available Linters: ['ols']
Enabled Linters: ['ols']
Suggested Fixers:
'remove_trailing_lines' - Rem
What went wrong
I write a type signarue in the .mli file, which cause a error in compiler, but ale doesn't check the mli file.
Reproducing the bug

create a test.mli file and type: val add : int -> int -> int
create a test.ml file and type: let add x y = x +. y

no error in ale but compiler throw an error

Does it work for other file extensions? I don't know too much about OCaml.

@w0rp you can understand like I write a definition in cpp's .h file and I write a function in .cpp file which doesn't match the definition, but ale doesn't check that.

Ah, I see. What's the value of &filetype for both files? Does it work if you save the file, close Vim, and re-open all of the files? If the filetypes are the same and it still doesn't work, it sounds like a bug with ols.

@w0rp They are both ocaml in vim. It doesn't work for all the operation. I think it's a bug with ols.I checked in vscode and it still have is issue. Thank you for your reply.

Okay, thank you for the information.


Poisson-binomial lpmf, lcdf, lccdf, rng

Summary:
Provide full implementation of Poisson-binomial for inclusion in Stan.
Description:
See the algorithm discussion on Discourse and Wikipedia article.
Analytic gradients would be a bonus, but a templated dynamic programming algorithm is a reasonable place to start.

If it's okay with you all, I'd like to take this on as my intro-to-stan-dev project. It might take a while in between job market prep so let me know if it's urgent + someone else would like to push on it.

Thanks, @shoshievass.  I had also mentioned this issue to @rayleigh as something he might work on.
As I mentioned in writing up the issue, there are two ways to go here:  (1) write a templated implementation that just follows the algorithm I wrote in Stan, or (2) write a version with analytic gradients for reverse mode.  For (1), you could start with the output from the Stan compiler---you can look at the C++ class generated for the Stan code implementing the lpmf.
You could also do (1) and then later replace with (2).  Either way, all the relevant tests will have to be written.  The best thing to read on Stan's reverse-mode autodiff framework is the arXiv paper.

It’s all yours! If you need help, post on discourse.
On Thu, Jun 21 2018 at 4:42 PM<EMAIL_ADDRESS>wrote:

If it's okay with you all, I'd like to take this on as my
intro-to-stan-dev project. It might take a while in between job market prep
so let me know if it's urgent + someone else would like to push on it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/math/issues/869#issuecomment-399237051, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAZ_F1Km4TY9FAF6Zxzip31Wv7a6K5l2ks5t_AVHgaJpZM4UJAH6
.

Just curious - has any progress been made on this? I have a problem I'm working on that I think would be appropriate to model with a poisson-binomial distribution.

Not that I kow of.  We just kicked off another project with @shoshievass, so maybe it'll come up again.

Hello, I would love to help contributing to Stan and found this issue as "good first issue". If you are interested I could have a look into this?
Cheers,
Simon

Totally fine on my end!
-Shosh
On Jun 7, 2020, 12:05 PM -0700, Simon Dirmeier<EMAIL_ADDRESS>wrote:

Hello, I would love to help contributing to Stan and found this issue as "good first issue". If you are interested I could have a look into this?
Cheers,
Simon
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Cool, I'll give it a try

Feel free to comment here if you have any questions about adding distributions/functions, always good to have more contributors on board!

You don't have to specify the gradients if you don't want to (although it can help with performance). If you just write the function to return the right log-probability, Stan's autodiff will take care of figuring out the gradients (this is how the ordered probit distribution is coded, for example).
If you do want to calculate the gradients, you want to code it so that the calculations are only done in cases where the gradients are actually needed. The  if (!is_constant_all<T_prob>::value) block is specifying that the gradients should only be calculated when the input variable is a type that contains gradient information (i.e., a var or fvar)

Closed via https://github.com/stan-dev/math/pull/1938


Console error message shows memory leak

Describe the bug
When running booster in development, right after launching the app and being presented with the iModel Selection screen, I see this error appearing in the console.

A similar error then appears again after selecting an iModel

To Reproduce

Run the booster app from VS Code.
After the app launches, open the chrome devTools (Mac: Command + Option + I, Windows/Linux: F12 or Control + Shift + I)
You'll see in the console the error message appearing

Expected Behavior
I'm expecting the console to not have any errors thrown.
Screenshots
No response
Desktop (please complete the applicable information)

OS: MacOS
iTwin Studio for Developers: Version 1.0.60 (<IP_ADDRESS>)
iTwin.js AppUI Version:   @itwin/appui-react": "4.12.0"

Additional context
No response

Could you provide the specific iModel which you open to reproduce the second warning? I can reproduce the first one just fine but I don't get the second one.

I looked into the issue. Seems like the warning is coming from studio's code and it is thrown by iTwinUI. I could not reproduce the second warning message but I got some another similar warning (component from another iTwin repository). However, the question is: is this issue urgent for you? This is not even an error but a warning and everythings seems to work just fine. Besides that this warning is removed in React 18 (and studio are already planning on upgrading) because it produces mostly false positives and the workarounds make the code worse (admitted by React developers). Link from the React documentation about this topic: https://react.dev/blog/2022/03/08/react-18-upgrade-guide#react (third entry, also has a link to the PR with examples and justification). Would you mind waiting for React 18 upgrade or do you need this fixed now?

I think this issue is safe to close, because it happens only in React 17 and only during development when using Strict Mode. We could add workarounds, but since this warning doesn't happen in the latest React version and it does not cause any real issues, it's not worth adding extra code.
In Strict Mode, React unmounts/remounts the components, which results in iTwinUI's setState call executing after the component is unmounted. As explained by React core team member, this is a false positive — setState called on an unmounted component gets simply ignored. There is no memory leak because we aren't setting up any subscriptions.

thanks for looking into it. It's definitely not a blocker and not urgent for me. I was just pointing it out in case this was causing memory leak in the app and since its a false positive and the error is expected to be fixed with a React update then lets wait for that.


Fix copy citation button

In addition to the fix at #164, we have another issue. When visiting https://topology.pi-base.org/spaces one can edit the search parameters, and it appears to update the citation for that page. However, those updates aren't reflected in the copied text from the Markdown button. We should fix this.

I believe https://github.com/pi-base/web/pull/157 has a hint on what we might need to do (use #key to force the component to rerender given new values for the text to be copied).

Has #164 done anything?  It used to be that the Copy: Markdown link button on the Explore page would copy something that would display the current search.  But that behavior became broken at some point.  And that it still broken, even with #164.  What we get is just:
[π-Base, Explore](https://topology.pi-base.org/spaces)

I think it fixed the front page button, but there's still work to do on the explore page.

Closed by #170


Add spec conformance tests for multiplicative expression contating int varref with other numeric operands

Description:
support for int varref with other numeric operands in a multiplicative expression is added via #35616. Need to add spec conformance tests.

Spec: https://github.com/ballerina-platform/ballerina-spec/issues/261

We are closing this issue due to inactivity. If you need further assistance or have additional input, feel free to reopen it. Thank you for helping us maintain a relevant and focused issue list!


Reconnect sometimes times out on v2

Check existing issues

[X] I checked there isn't already an issue for the bug I encountered.

Describe the bug
On initial page load the useAccount hook fails to reconnect on slow devices.
I refresh the page and expect the previously connected wallet to be connected instead it ends up being disconnected.
I added some logging and observed useAccount returns the connected account address with status "reconnecting". Normally the status changes to "connected" after a little bit, but on slow devices it instead changes to "disconnected" and the account address becomes undefined. When this happens the autoreconnect does not complete. I can reproduce this consistently in my dapp by setting cpu throttling to 4x. I simulated a slow device by adding additional work to my minimal repro.
I added the following code to the getting started set up to reproduce:
const [x, setX] = useState(0);
useEffect(() => {
if (x < 100) {
setX(x + 1);
}
}, [x]);
console.log("account:", account);
if (x > 10) {
for (let i = 0; i < 10; i++) {
(async () => {
for (let j = 0; j < 1000; j++) {
console.log("Random number: ", Math.random());
}
})();
}
}
It was a little finicky, so you might need to change some constants based on your processor. I reproduced without any CPU throttling.
Link to Minimal Reproducible Example
https://stackblitz.com/edit/new-wagmi-nknyne?file=src%2FApp.tsx
Steps To Reproduce
Connect a wallet (I tested using Rabby). Wait until the page shows connected. Refresh the page, observe that the page shows reconnecting and then disconnected.
What Wagmi package(s) are you using?
wagmi
Wagmi Version
2.9.5
Viem Version
2.12.0
TypeScript Version
5.1.6
Anything else?
No response

Haven't been able to reproduce. This is also an older Wagmi version. Please try to create a consistent minimal reproduction with the latest Wagmi version (2.9.12 at time of writing).

I can reproduce on 2.9.12 as well. new.wagmi.sh defaults to 2.0.1, but I just updated it to 2.9.12 and ran pnpm install.
As I said the reproduction is a bit finicky since it depends on your machine. If you have too much extra work for your processor the page doesn't load, and if you have too little work than it finishes reconnecting before timing out. You should be able to tune the constants to work for your machine.

We were able to reproduce both on a 2021 MacBook Pro with an Apple M1 and a Surface laptop with 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz   3.00 GHz which is a pretty wide range, so I'm a little surprised you are unable to reproduce. What do you observe when following the reproduction steps and what type of machine/processor did you use? Also which wallet are you using to connect?

I was able to repro, the reconnecting status keeps there like ~10sec and shows as disconnected

Would love to hear your thoughts on https://github.com/wevm/wagmi/pull/4042


add schedules graphs

add four schedules graphs, one for each new metric
add namespace filters to a couple graphs that didn't have it
resize things for no reason (I didn't do this on purpose and I don't believe this will impact anything)

are the following metrics exposed?

they are, there are just very few accounts for which it's ever happened, so they're not visible. these things aren't automatically 0 if they've never happened.


ttnn.upsample inconsistent interface

ttnn.upsample scale_factor parameter is inconsistent with both TF and Torch. If we are only supporting 2D upsampling (which is also case with TF) it only makes sense that scale_factor is int for uniform scaling or (int, int) for scaling factors of H and W respectively. Will scale factors for N and C ever make sense, because I can't see a use case for them in upsampling. Regardless of that, (int, int) case should always be scale factors for H and W, current situation where it's interpreted as factors for W and C (where C is only asserted to equal 1) is totally counter-intuitive.
Also citing documentation scale_factor (int or tt::tt_metal::Array2D or tt::tt_metal::Array3D or tt::tt_metal::Array4D) – multiplier for spatial size. Has to match input size if it is a tuple., sentence Has to match input size if it is a tuple. looks out of place.
FYI @sdjordjevicTT @nvukobratTT

@prajaramanTT @nkpatel-tt @mywoodstock do you have any update regarding this issue? We want to support this op in the TT-MLIR compiler, hence we are seeking some updates regarding this.

@sdjordjevicTT  I will start looking into it now.

Thank you, @nkpatel-tt. If you need any assistance or further clarification, please feel free to contact us.


Misleading warning in FlowLog while generating Operators using TypeConverters

DBFlow Version: 4.1.2
Issue Kind : Question
Description:
When generating SQL involving an Operator with a TypeConverter, for example:
SQLite.select().from(Log.class).where(Log_table.insertTime.greaterThan(yesterday))
a warning message is generated in the FlowLog which details a ClassCastException with full stack trace, via
Operator.convertObjectToString(Object object, boolean appendInnerParenthesis)
The appearance of the stack trace caused me to spend some time believing that some error had occurred, whereas the final output of the method is actually correct in this case.
Would it be possible to change the log record to not include the stack trace in this instance?

Its just giving you an idea of a possible problem.
                // if object type is not valid converted type, just use type as is here.

the comment should have helped you or at least seeing through debugging why it happened should explain it.
For reference, what is the type of insertTime and what is the value/type of yesterday

I am not suggesting that  the warning is removed (although this is reporting the internal default behaviour, which in this case is the desired outcome), which is perfectly valid, but that the log need not contain a stack trace as it is only a warning and not an error as such. The warning could still show relevant details at that point.
The example above is just an example, not a real case, but would have been a String representation of a LocalDateTime.  The resulting SQL was exactly as it should have been.

ill move it up to Level.I info and put it as not a stack trace, but as the actual purpose of what is happening.

in develop.