Exposure of usernames via User ID Guessing in URL

Description
I recently discovered a potential security flaw that allows users to access other users' usernames by manipulating user IDs. When navigating to a profile URL such as https://jellyseerr.example.com/users/[UserID], changing the UserID parameter in the URL to an arbitrary number reveals the corresponding username of that user. This could lead to privacy issues particularly for Jellyseerr/Jellyfin users who use email addresses as usernames.

Reproduce as end user
End user has only permissions to the request function:

Steps

Log in to Jellyseerr
Go to "Requests"
Click on the username at the "Modified" date
Change the UserID in the URL bar of the browser

To reproduce for testing just open the URL: https://jellyseerr. yourdomain.com /users/2
Desired Behavior
Protect the user pages for users and only allow access to admins.
Additional Context
Version:
Stable 1.7.0
Code of Conduct

[X] I agree to follow Jellyseerr's Code of Conduct

Apparently that is the intended behavior https://github.com/sct/overseerr/pull/3695#issuecomment-1817827774
In your case, you can set a display name on those people using the emails. The display name will be what will appear for others


⛰[EPIC]: Distributed GNN Example

### Example development
- [ ] https://github.com/NVIDIA/modulus/issues/358
- [x] Verify the model produces accurate results

### Distributed computing
- [ ] Enable distributed GNNs on single-level mesh
- [x] Enable distributed GNNs on multi-level mesh
- [ ] Enable distributed I/O

### Documentation
- [x] Add README

PR: https://github.com/NVIDIA/modulus/pull/400


l have a question to ask for you,please answer my question

hello,l want to know the version of your cuda, canyou tell me?

Cuda compilation tools, release 10.2, V10.2.89

@wolf212121j Are you training this model? What was the result?

@wolf212121j Are you training this model? What was the result?

sorry, l can not training it successfully,l have a problem that l can not solve it yet,can you help me solve it?

@wolf212121j what problem？my email is<EMAIL_ADDRESS>


Clicking right-hand side number in number entry panel appends "undefined" to it.

Closed in 5518d35f36d95b1a91a7c6ee5a8384239a55afd8


(proposal) : DRCs

In the spirit of competitive programming (CP), we propose a new type of competition specifically for developers.
This event will focus on building the most scalable, sound, and resilient systems.
Objective
Participants will compete to design and implement systems that demonstrate exceptional scalability, robustness, and resilience. The goal is to create solutions that can handle high loads, recover gracefully from failures, and maintain high performance under stress.
Phases

Common Topic: All participants will work on a predefined topics. This ensures a level playing field and direct comparability of solutions.

Development Phase: Participants will have a set period to design, develop, and test their systems. They will be required to use best practices in software architecture, error handling, and performance optimization.

Presentation: Each team will present their system, demonstrating its features, design choices, and how it meets the competition's criteria.

We can also keep a cute little name of this ,like DRC: developers resiliency cup
Original idea by : @majorbruteforce
CC: @punitkr03 @majorbruteforce

I would have said I second it but since it isy idea, letssgooo

What sounds better than CP? CP for development... Let's do this 🚀🚀🚀

Lets discuss this in a general meeting after everyone comes back in college.🎉


fixture 'aiohttp_client' not found

Hello,
I'm not able to run the unittest and I don't understand why. Here is what happens:
==================================== ERRORS ====================================
______________________ ERROR at setup of test_get_payload ______________________
file /tmp/aiohttp-jwt-0.1.1/tests/test_middleware.py, line 13
  async def test_get_payload(create_app, aiohttp_client, fake_payload, token):
      async def handler(request):
          assert request.get('payload') == fake_payload
          return web.json_response({'status': 'ok'})
      routes = (('/foo', handler),)
      client = await aiohttp_client(create_app(routes))
      response = await client.get('/foo', headers={
          'Authorization': 'Bearer {}'.format(token.decode('utf-8')),
      })
      assert response.status == 200
E       fixture 'aiohttp_client' not found
>       available fixtures: cache, capfd, caplog, capsys, capturelog, cov, create_app, doctest_namespace, event_loop, event_loop_process_pool, fake_payload, fast, loop, monkeypatch, pytestconfig, raw_test_server, record_xml_property, recwarn, secret, shorttmpdir, test_client, test_server, tmpdir, tmpdir_factory, token, unused_port, unused_tcp_port, unused_tcp_port_factory
>       use 'pytest --fixtures [testpath]' for help on them.

Thanks in advance for your support

Hello, it is because this fixture available only in aiohttp >= 3.0. Previously it was named test_client. Seems like you ran tests against older version of aiohttp.

Yes absolutely, 2.2.x.
Is there any way to detect this ?

I guess, you can create proxy fixture like
@pytest.fixture
def aiohttp_client(test_client):
    return test_client

and add it conftest file.
But i am wondering why do you want to run tests on older version? Also note that middleware works only with aiohttp >= 2.3.5

Okay, I got your point. Could you please tell how did you build .deb package? I actually tested it locally with aiohttp 2.2.3 and with latests pytest-aiohttp it works fine.


Stay in Workspace

Issue Type: Feature Request
When in the Explorer pane and add a folder to a Workspace the focus is changed to the Servers view. This is niether desired or helpful.
Please fix this ridiculous behaviour and maintain the same focus!
Azure Data Studio version: azuredatastudio 1.5.2 (f74080c96310354bc92211f1826c0fdce78ca2f6, 2019-03-22T06:25:26.627Z)
OS version: Windows_NT x64 10.0.18356

This is related to the Startup: Always Show Servers View setting which is set to true by default but can be disabled.

The shell reload when opening a folder is inherited from VS Code and would need to be fixed upstream.  Though I agree in this particular shell reload scenario we maintain focus in the File Explorer viewlet.


geemap.dynamic_world_timeseries method adds zero class instead of nan

Environment Information
Please run the following code on your computer and share the output with us so that we can better debug your issue:
Python 3.10.6 on WSL Ubuntu 22.04.1
import ee
from utils import get_bounding_box
import geojson
from geojson import dump
import numpy as np
import geemap
Description
I downloaded  a series of images from GEE using
images_time_series = geemap.dynamic_world_timeseries(poly, start_date, end_date, frequency=frequency, return_type=return_type)
and exported the data to my Google Drive as tif files.
The return_type was "class" so the output was a single band tif file, with the band representing LULC classification.
Analyzing the class distribution, I found the class zero (0 = water Estimated probability of complete coverage by water.) to be overrepresented
For example, analyzing 10 periods over the same AOI, counting pixel classes zero with:
for z in range(times_series_trans.shape[0]):
res = 0
res += np.count_nonzero(times_series_trans[z,:,:] == 0)
which yielded:
125190
125293
125533
241012
125881
125556
125399
125652
125661
270874
checking images 4, 7, 10 yields:
show(times_series_trans[3,:,:])
show(times_series_trans[6,:,:])
show(times_series_trans[9,:,:])

This clearly is a case of missing data, stemming - most likely - from cloud coverage over the AOI.
Thus, missing data should be classified as nan, not zero.
Or am I missing something here?

This is not really a geemap issue. When exporting integer data, GEE will assign zero to background pixels. If it confuses with other pixel value, you should set the background pixel values to something else before exporting data, such as image.unmask(-999). In this way, background pixels will be -999 rather than 0.

The ee_export_image() and download_ee_image() has the unmask_value parameter for this.
https://geemap.org/common/#geemap.common.ee_export_image
https://geemap.org/common/#geemap.common.download_ee_image

Hi Mr. Wu!
Thank you for your swift reply.
Setting the unmask value parameter worked smoothly!
Best,
Matthias Sammer

From: Qiusheng Wu @.>
Sent: Friday, 23 December 2022, 16:30
To: giswqs/geemap @.>
Cc: Matthias  Sammer @.>; Author @.>
Subject: Re: [giswqs/geemap] geemap.dynamic_world_timeseries method adds zero class instead of nan (Issue #1373)
The ee_export_image() and download_ee_image() has the unmask_value parameter for this.
https://geemap.org/common/#geemap.common.ee_export_image
https://geemap.org/common/#geemap.common.download_ee_image
—
Reply to this email directly, view it on GitHubhttps://github.com/giswqs/geemap/issues/1373#issuecomment-1364046755, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUZZKWV5GYAWMUFZRWLFUV3WOXASFANCNFSM6AAAAAATH3AW54.
You are receiving this because you authored the thread.Message ID: @.***>


Packing Add Dup Validation

Changes Unknown when pulling 86451a78d463b9a8669ad7d0fc5b63af1ea1cf83 on jackyrusly:dev into ** on danliris:dev**.


Fix langtool config for Linux

Fixes https://github.com/hlissner/doom-emacs/issues/2072.
I have left the mac portion alone as I don't have a mac handy to test this.

Thanks!


Namespaced loggers

Enables finer-grained logging configuration. If I want to suppress e.g. https://github.com/django-silk/silk/blob/6f8a5741115640dc752ef95951058b420d55dbe8/silk/profiling/profiler.py#L106 but not other warnings, with this patch I can change the logging level for `"silk.profiling.profiler" independently.

@aehlke Thanks for the contribution. Could you add some documentation on the different types of logger namespaces on the README?
I know the build is failing but it is for unrelated reasons. Given that knowledge I have merged this in.

@avelis I have a couple other PRs I need to make first but I'll look into README!


JBPM-5374 - Process instance doesn't exit an Embedded SubProcess in a…

…n AdHoc process

Test case

closing this one as https://github.com/droolsjbpm/jbpm/pull/646 includes the test case and the fix. thanks @tkobayas


optimize get_sig

Codecov Report

Merging #360 (5a39b0a) into master (b6a0cb9) will decrease coverage by 0.15%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #360      +/-   ##
==========================================
- Coverage   85.84%   85.68%   -0.16%
==========================================
  Files          11       11
  Lines        2296     2285      -11
==========================================
- Hits         1971     1958      -13
- Misses        325      327       +2

Impacted Files
Coverage Δ

src/analyzers/optanalyzer.jl
90.52% <ø> (ø)

src/abstractinterpret/inferenceerrorreport.jl
88.05% <100.00%> (-0.12%)
:arrow_down:

src/JET.jl
70.43% <0.00%> (-0.76%)
:arrow_down:

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 b6a0cb9...5a39b0a. Read the comment docs.


missing information in README.md

Add Hyperlink to the Visual studio marketplace.
Add short description about the prerequisites of the extension (need to use Tags, how to use WI association to commits / pull requsts)
Add link to the github master on the marketplace description page.

Added Hyperlink  and more details.
Thanks for the feedback.


Any chance you want to rename it to not cause confusion with ansible.com?

ansible.com is an open source server orchestration/automation product from redhat.  Like Puppet &  Chef.
https://docs.ansible.com/#project

Hello @pdebruic, we knew about Redhat's ansible, but after discussing it for a while, we agreed it was a great name for him!
Being a small project within a tight community, we assessed that the probability of confusion would be zero. We're open to change it, did we miss something in our evaluation?
Thanks!

🤷♂
Primarily, aesthetically it seems like there are enough words in the world to give a thing its own name.
But I would guess the US trademark holders for the term won't mind because it won't be confusing to a layperson that you're not really doing the same thing and they won't have to pressure you to stop using their term if/once they discover your use of it on their own. See these records:
http://tmsearch.uspto.gov/bin/showfield?f=toc&state=4803%3A36daug.1.1&p_search=searchss&p_L=50&BackReference=&p_plural=yes&p_s_PARA1=&p_tagrepl~%3A=PARA1%24LD&expr=PARA1+AND+PARA2&p_s_PARA2=ansible&p_tagrepl~%3A=PARA2%24COMB&p_op_ALL=AND&a_default=search&a_search=Submit+Query&a_search=Submit+Query
And this overview: https://en.wikipedia.org/wiki/United_States_trademark_law
I think because its on github that makes it US jurisdiction too.
But IANAL and may be wrong about all of the above.
What did your evaluation come up with about the trademark issue?

On May 6, 2020, at 4:18 PM, Francisco Ortiz Peñaloza<EMAIL_ADDRESS>wrote:
Hello @pdebruic, we knew about Redhat's ansible, but after discussing it for a while, we agreed it was a great name for him!
Being a small project within a tight community, we assessed that the probability of confusion would be zero. We're open to change it, did we miss something in our evaluation?
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

And to be clear I don't care what you name it just thought I'd raise the issue that you named it the same as something else in the event you didn't know.

On May 7, 2020, at 4:44 PM, PAUL DEBRUICKER<EMAIL_ADDRESS>wrote:
🤷♂
Primarily, aesthetically it seems like there are enough words in the world to give a thing its own name.
But I would guess the US trademark holders for the term won't mind because it won't be confusing to a layperson that you're not really doing the same thing and they won't have to pressure you to stop using their term if/once they discover your use of it on their own. See these records:
http://tmsearch.uspto.gov/bin/showfield?f=toc&state=4803%3A36daug.1.1&p_search=searchss&p_L=50&BackReference=&p_plural=yes&p_s_PARA1=&p_tagrepl~%3A=PARA1%24LD&expr=PARA1+AND+PARA2&p_s_PARA2=ansible&p_tagrepl~%3A=PARA2%24COMB&p_op_ALL=AND&a_default=search&a_search=Submit+Query&a_search=Submit+Query
And this overview: https://en.wikipedia.org/wiki/United_States_trademark_law
I think because its on github that makes it US jurisdiction too.
But IANAL and may be wrong about all of the above.
What did your evaluation come up with about the trademark issue?

On May 6, 2020, at 4:18 PM, Francisco Ortiz Peñaloza<EMAIL_ADDRESS>wrote:
Hello @pdebruic, we knew about Redhat's ansible, but after discussing it for a while, we agreed it was a great name for him!
Being a small project within a tight community, we assessed that the probability of confusion would be zero. We're open to change it, did we miss something in our evaluation?
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

We take a look at the trademark and we think the scope of this project is different to the trademarked one, and that no confusion with Ansible, the provisioning platform is possible. It's a tiny open source project, Smalltalk related specifically with no intention of expanding from this scope.
We're trying to keep a metaphor regarding all the network service projects naming them in the spirit of space-related sci-fi things. And the inspiration for this one is https://en.wikipedia.org/wiki/Ansible.


Code coverage generation

Using c8 lib added code-coverage report generation functionality.

Tests would pass, after https://github.com/apache/netbeans/pull/7271 is merged

Added in #258


Add location helpers in JctFileManager

Add methods such as .getClassOutputGroup() for all StandardLocation members.

Codecov Report

Merging #338 (9fefb00) into main (856ff77) will increase coverage by 0.09%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@            Coverage Diff             @@
##             main     #338      +/-   ##
==========================================
+ Coverage   79.21%   79.31%   +0.09%
==========================================
  Files          90       91       +1
  Lines        2718     2731      +13
  Branches      227      227
==========================================
+ Hits         2153     2166      +13
  Misses        506      506
  Partials       59       59

Impacted Files
Coverage Δ

...ithub/ascopes/jct/filemanagers/JctFileManager.java
100.00% <100.00%> (ø)


beta CustomResourceDefinition API (apiextensions.k8s.io/v1beta1) to be removed in 1.22

Current installation uses apiextensions.k8s.io/v1beta1 which is about to be expired in upcoming K8s release 1.22

duplicated with https://github.com/Altinity/clickhouse-operator/issues/762


microsoft teams updates

📦 Published PR as canary version: Canary Versions

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

@seanspeaks added a commit:
update manager to correctly support code and client_credentials style auth in processAuthorizationCallback
update manager getInstance to correctly retrieve the tenant_id stored on the externalId of the related entity
update tests for the above, as well as correct the reference to the redirect_ui in the .env

conversation reference creation requires coordination of the sub-apis that is now handled by main class

:rocket: PR was released in<EMAIL_ADDRESS>:rocket:


when increased scrape_interval for slow target it is not reverted back to global value

What did you do?
when I increased scrape_interval for 1 of my slow target (90s) and it worked but when I revert that then default/global value (15s) is not applied
What did you expect to see?
when removed scrape_interval from the slow target then it should be scrapped at the same interval as other targets
What did you see instead? Under which circumstances?
Environment

System information:
Linux 4.14.171-136.231.amzn2.x86_64 x86_64

Prometheus version:
2.30.0

Prometheus configuration file:

global:
  scrape_interval: 15s
  scrape_timeout: 10s
  evaluation_interval: 15s
  external_labels:
    cluster: qa
    replica: "0"
scrape_configs:
- job_name: app metrics
  honor_timestamps: true
  scrape_interval: 15s
  scrape_timeout: 10s
  metrics_path: /prometheus
  scheme: http
  sample_limit: 50000
  follow_redirects: true
  relabel_configs:
  - source_labels: [__address__]
    separator: ;
    regex: (.*)
    target_label: metrics_endpoint
    replacement: $1
    action: replace
  metric_relabel_configs:
  - separator: ;
    regex: aws_autoscaling_groupName|aws_cloudformation_logical_id|aws_cloudformation_stack_id|aws_cloudformation_stack_name|elasticbeanstalk_environment_id
    replacement: $1
    action: labeldrop
  file_sd_configs:
  - files:
    - /etc/prometheus/application_instance.yml
    refresh_interval: 1m

Logs:

insert Prometheus and Alertmanager logs relevant to the issue here

I believe this happens because we exempt the scrape interval and timeout labels from the target hash: https://github.com/prometheus/prometheus/blob/08011925a10c14f05cce6f3204cb9a2d68d5851b/scrape/target.go#L152-L153
A temporary fix could be to not use the __scrape_interval__ label directly in the service discovery file and instead set it in a relabel config.


release as preminor is not increasing the version

In my project we have set the releaseAs=preminor but is not increasing the version of the application. If you see the changelog the previous version and next version are same. I have tried making changes in the dependent lib and the app itself in both cases it doesn't work.
Here is the project config:
"version": {
      "executor": "@jscutlery/semver:version",
      "options": {
        "preset": "angular",
        "push": true,
        "commitMessageFormat": "chore({projectName}): release version ${version} [skip ci]",
        "baseBranch": "HEAD:develop",
        "noVerify": true,
        "postTargets": ["file-delivery:gitlab", "file-delivery:publish"],
        "releaseAs": "preminor",
        "preid": "beta"
      }
    },

I have reproduce the issue in this example repo:--
https://github.com/ak274/semver
if you make a change for a app and commit and then try to run the version target it will calculate the same tag and throw error tag already exists

@edbzn Any idea why this config always calculating same version for preminor releases?

Any help would be great. Why preminor release not incremental


feat: Support memory freeing

WIP

The vast majority of use cases won't need a huge number of buckets.
So we could keep the header as a single page, store each bucket in the linked list as 2 bytes, and if additional buckets are needed, we use the unused space in the header to point to where the subsequent buckets are defined.
Maybe these follow on buckets are defined as 3 bytes, and at the end of the page is a pointer to the next page of buckets, and so on.
That way the number of buckets is pretty much unbounded, the header remains small in most use cases, and we wouldn't need to move the existing data in the first memory page after the header.

Having thought about this a bit more I think my idea to store bucketIds as 3 bytes is wrong.
If we support spreading buckets onto more pages, then storing them as 3 bytes is an unnecessary storage optimisation at the expense of code complexity. I think storing buckets as u32s is the way to go.
The first page could then store something like 8192 buckets in the last 32768 bytes (using the format I introduced in this PR where each bucket points to the following bucket in the linked list).
Follow on pages used to store buckets could then store 16384 per page.
The first page then just needs to somehow store where the additional pages are.


Some problem with radium library

Hi!
I'm actually a newbie, so sorry for this question.
I can't install radium library for this webpack, I have something like this in terminal:
npm WARN<EMAIL_ADDRESS>requires a peer of styled-components@>= 2 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^15.0.0 but none is installed. You must install peer dependencies yourself.
Then I'm trying to install styled-components and have the same warn.
What should I do?
I used radium for my react app and everything was fine.
I need this lib to manage inline styles on some elements.
Can you help me, please?

Did you manage to solve this, @NasKadir123 ?


forced to use symfony.dev ?

I don't think it makes sense to force the use of symfony.dev. It's quite restrictive for example if you want to run multiple of this build on a server, you need to edit the config of each containers. In my opinion, the virtualhost filtering should be done by a reverse proxy, not by this container.
I would propose to

rm /etc/nginx/site-available/default.conf and
make symfony.conf default_server

if we want to keep this feature, it should be at least a parameter in .env

UP

I'm not sure this repo is still managed..

@yohancourbe  ah ok, thank you

Hiya @devDzign  @yohancourbe,
This issue was already raise few month ago (see #6). Unfortunately, after some testing, I never find a way to do it properly. By 'properly', I mean without makesfiles&co.
If you got a good way to implement it, feel free to open a pull request! I'd be more than happy to approve this!
Cheers.
@yohancourbe it is still maintained, I'm just running out of time theses days 😉

Yesterday I was forced to change the domain name because Chrome is forcing .dev domains to https.
I suggest to use symfony.localhost by default.  I mapped port 3000 for first docker-compose on nginx and 3100 on the second but I get some sort of load balancing no matter the port, on a refresh response switches between first and second


Question wrt to scraping a list of all symbols

Is there a way to scrape all symbols? I was not able to identify this feature in yfinance after some research; in case it's available, kindly advise - otherwise I hope this can be a valid feature request.
Desired output should be a sorted dictionary, similar to: {"AAPL", "ACME", ..... "ZZZ"}
What I could find so far, there is a standalone script which however as of today can't overcome the cookie accept form on the site. Side question - how does yfinance manage this?

Original project, as it seems
Most recent version I could find with symbols list as of 2023-12-31

Workaround: use Selenium in Docker to accept the cookies form and scrape the page.
Something like the following:
driver = webdriver.Chrome()
driver.get(url)
accept_button = WebDriverWait(driver, 10).until(
        EC.element_to_be_clickable((By.XPATH, '//button[text()="Accept all"]'))
    )
accept_button.click()
element = WebDriverWait(driver, 10).until(
    EC.presence_of_element_located((By.ID, 'lookup-page'))
)

html_content = driver.page_source

yf already uses cookies


Week 04

Before

[x] HW
[x] rubrics (PL & Canvas)
[x] HW solutions
[x] Quiz
[x] Lab(s)
[x] index.md
[x] prep notebook
[x] in class notebook
[x] data links
[x] lecture
[x] canvas week page: reading links/video links
[x] help channel(s) in Slack for assessments
[x] PL link in Canvas assessments
[x] extension request tool

After

[x] video posted
[x] HW extensions processed
[x] grades uploaded

HW1 grades posted, HW2 is next week


[Schema Registry] Enable min/max testing

This PR does the following:

moves the test suite into a new directory called public to enable min/max testing. @KarishmaGhiya is there anything else I need to do?
removes testEnv and uses env instead to reference environment variables inside tests.

/azp run js - schema-registry - tests

If you have a tests.yml - remove these lines -
     MatrixFilters:
        - DependencyVersion=^$
    ```

/azp run js - schema-registry - tests

/check-enforcer reset

/check-enforcer override

/azp run js - schema-registry - tests

/azp run js - schema-registry - tests

/azp run js - schema-registry - tests


Integrate dask masked array support (just code changes, no tests fix)

This is pointing at the dask_mask_array feature branch.
This contains just the code changes that I think require to be done to integrate the dask masked array support into Iris.
This will obviously break a bunch of tests but we can address that later.

I'm pretty happy with the handling of fill value:
>>> x = ma.masked_array([1,2,3,4], mask=[0,1,0,0], fill_value=10)
>>> dx = da.from_array(x, chunks=(2,), asarray=False)
>>> cdx = dx.compute()
>>> print cdx.fill_value
10

Combining two daskified masked arrays was interesting though:
>>> x = ma.masked_array([1,2,3,4], mask=[0,1,0,0], fill_value=15)
>>> y = ma.masked_array([1,2,3,4], mask=[0,1,0,0], fill_value=32, dtype=np.float64)
>>> dx = da.from_array(x, chunks=(2,), asarray=False)
>>> dy = da.from_array(y, chunks=(2,), asarray=False)
>>> dxy = dx * dy
>>> cdxy = dxy.compute()
>>> print cdxy.fill_value
15.0

@lbdreyer Just noticed that we should be purging the use of the following _lazy_data functions:

[ ] nan_array_type

[ ] fileformats/netcdf.py - imported but not used
[ ] _lazy_data.py - definition

[ ] array_masked_to_nans

[ ] fileformats/grib/message.py - imported but not used
[ ] fileformats/netcdf.py - I don't think that we should be using this here
[ ] fileformats/pp.py - imported but not used
[ ] _lazy_data.py - definition

[ ] convert_nans_array

[ ] fileformats/grib/__init__.py - revert usage back to 1.13 ?
[ ] fileformats/netcdf.py - imported by not used
[ ] tests/unit/lazy_data/test_as_concrete_data.py - we can nuke these tests
[ ] tests/unit/lazy_data/test_convert_nans_array.py - we can remove all these tests
[ ] _lazy_data.py - definition

@lbdreyer We should remove the DataManager.replace method and associated Cube.replace method, and retrospectively use datamanager.data = data and cube.data = data instead ...

[ ] analysis/__init__.py, line 566
[ ] cube.py, lines 2912-2922
[ ] tests/test_analysis.py, lines 132, 138, 147
[ ] tests/test_basic_maths.py, line 42
[ ] tests/test_cdm.py, line 1033, line 1039
[ ] tests/test_concatenate.py, line 521, line 542
[ ] tests/test_interpolation.py, line 46
[ ] tests/unit/analysis/regrid/test_RectilinearRegridder.py, line 1266
[ ] tests/unit/cube/test_Cube.py, assorted lines
[ ] tests/unit/fileformats/pp/test_as_pairs.py, line 54
[ ] tests/unit/data_manager/test_DataManager.py, assorted lines
[ ] _data_manager.py, line 193, line 374

@lbdreyer Just missed one case of replace on line 194 in _data_manager.py

We have agreed to keep this PR to just code changes so I am going to back out all the test fixes.
I am hoping to keep this PR to just code changes, and then when it gets merged, squash it to a single commit, so in the commit history there will be a single commit with the code changes and then subsequent commits with fixes to the tests that fall out from the code changes.

@bjlittle  I have now addressed all your comments (except for the fill_value at saving to pp and netcdf time which we have #2703 and #2704 to address)

@lbdreyer Okay, I'll take a final look through the updates ...


Update AWS and linux install instructions

Proposed changes
Updated EE instructions:

AWS instructions enhanced to help with cloudformation setup
Linux instructions now point to EE install instructions instead of CS engine install instructions

Thanks for looking @JimGalasyn. Updated.


Add additional overloads for mtimes (with handling for self-adjoint)

I'm open to different names for the enum that controls what to assume for the properties of the matrix.

I moved what I did with dot into mtimes so that it would be similar to the original lubeck API.
There is some stuff in those original lubeck mtimes functions for handling the case where the kind isn't Contiguous that isn't getting handled here. It doesn't look like it's being tested though.

@9il I think this is in good shape now if you have time to review.

Could it be new function names instead then extending API for the existing one?

@9il I can make that change.
This PR also includes the addition of functionality from the original lubeck API to handle matrix-vector and vector-matrix and vector-vector multiplication. For the general matrix case, can I keep that as part of this PR? (i.e. just splitting off the selfAdjoint stuff to separate functions).

@9il No rush, but when you have a chance can you push a new tag. I don't think I have permissions to do that on this repository.


Missing @decorate export in src/core-decorators.js

@decorate is not being exported in src/core-decorators.js

Wow...it must have been amatuer hour. Sorry bout that. Thank you much! Fixed and published as<EMAIL_ADDRESS>

Thanks a ton man!!


flaky test: test_operator.test_dropout

http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/PR-12311/1/pipeline
======================================================================

FAIL: test_operator.test_dropout

----------------------------------------------------------------------

Traceback (most recent call last):

  File "/usr/local/lib/python3.5/dist-packages/nose/case.py", line 198, in runTest

    self.test(*self.arg)

  File "/work/mxnet/tests/python/unittest/common.py", line 172, in test_new

    orig_test(*args, **kwargs)

  File "/work/mxnet/tests/python/unittest/test_operator.py", line 5844, in test_dropout

    check_dropout_ratio(0.0, shape)

  File "/work/mxnet/tests/python/unittest/test_operator.py", line 5788, in check_dropout_ratio

    assert exe.outputs[0].asnumpy().min() == min_value

AssertionError:

-------------------- >> begin captured logging << --------------------

common: INFO: Setting test np/mx/python random seeds, use MXNET_TEST_SEED=119185068 to reproduce.

--------------------- >> end captured logging << ---------------------

Created a PR to disable test: https://github.com/apache/incubator-mxnet/pull/13057

I investigated this issue. The dropout symbol implementation calls a function BernoulliGenerate when MKL and OpenMP flags are on. This is where the flakiness comes from.
BernoulliGenerate uses multithreading and calls MKL library function viRngBernoulli to populate a mask vector. https://github.com/apache/incubator-mxnet/blob/master/src/operator/nn/dropout-inl.h#L82
When p=1.0, it is supposed to populate the mask vector r of length n with all 1s. But for a few values of seed internally generated, mask vector has n-1 1s and a 0 (located at a different index for a different flaky seed), which causes the error.
Also, the error only occurs when multi-threading used. It is not reproduced when single thread used.
I suspect that viRngBernoulli is not thread-safe.
@TaoLv @pengzhao-intel @ZhennanQin @xinyu-intel Can you please take a look? Would really like your inputs on the same. Thanks!

@mseth10 thanks for the deep dive. I will look into the case and back to you soon.

@pengzhao-intel Apparently, the issue is not with viRngBernoulli, it is with the streams being generated. In the present code, different seed is passed to vslNewStream for different threads. Making the seeds constant fixes the flaky issue. Please review. Fix in #13276 .


[NEW] Added Chat Room Information

@RocketChat/android

Closes #835

PR Info
Adds the capability of viewing a chat room's information. This works for both subscribed and unsubscribed rooms.
Information that can be viewed:

Topic
Description
Announcement
Read-Only Status (Only shown if the room is read-only)

Information that can be edited

Name
Topic
Description
Announcement
Room Type
Read-Only Status
Archived Status

To be implemented in the future

Join Code (Didn't implement, need to discuss security around it first)
Deleting Messages from the room

Additonals

Added observation abilities to the Room Repository to be able to update UI as a room gets changed

Prerequisties

Needs Kotlin SDK's #114
Still need to add Hindi and Proteguese Language Strings

Screenshots of WIP

@leonardoaramaki Added changes but only commit after Kotlin SDK's #111.

@rafaelks @leonardoaramaki This is ready to be re-reviewed. Sorry it took so long. Last month of school has been tough so I wasn't able to put in a lot of time all at once to get this done quickly.

Just to update, will try and fix conflicts for this PR in during the next two weeks

@thiagosanchz Let's discuss about the details of this screen please.

Guys, we can discuss that, but one important thing is using the same features, labels, and button as a desktop/web app to keep product decision aligned. But we can do a better job in the layout.

@samrmur Can you please fix the conflicts and the code? Because it's not compiling (and there are some conflicts inside the code that was commited).

Closing the PR for now, let me know if you still want to have this one merged @samrmur, than we can reopen it.

@rafaelks This PR is finally ready to be merged


Add "Removing plugins from your project" section to Plugin Management doc

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2317
Originally created by @DouweM on 2020-08-28 16:13:07

Let's make it explicit that removing the entry from meltano.yml is usually sufficient, but that traces will remain in .meltano and the system database.

View 4 previous comments from the original issue on GitLab


Add explicit lifetime to RowIter in Store::scan_data

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

19 of 19 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.268%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
53456

Relevant Lines:
54398

💛  - Coveralls


Grandchild states do not correctly see dynamic vars added to parent state

Describe the bug
Adding a variable to a parent state via add_var after defining some child state does not allow the variable to work in a subsequently defined grandchild state.
To Reproduce
import pynecone as pc

class S(pc.State):
    pass

class SS(S):
    pass

S.add_var("foo", type_=str, default_value="")

class SSS(SS):
    @pc.var
    def bar(self) -> str:
        return self.foo

state = S()
substate = state.substates[SS.get_name()]
subsubstate = substate.substates[SSS.get_name()]
state.foo = "bar"
print(subsubstate.bar)

Expected behavior
it should print bar
instead it prints {s.foo}
** Specifics (please complete the following information):**

Python Version: 3.11.2
Pynecone Version: main
OS: macOS 13.2.1
Browser (Optional): N/A

Additional context

State.inherited_vars is a direct link to parent_state.vars (set in __init_subclass__)
State.vars is a copy (combination) of vars from a few sources, and doesn't get updated when parent state adds dynamic vars.

Adding to the bottom of State.add_var seems to have the desired effect.
        # let substates know about the new variable
        for substate_class in cls.__subclasses__():
            substate_class.vars.setdefault(name, var)

(Note: can't use State.get_substates() because it's lru_cache'd)

While this did get fixed recently as part of #852, i discovered that the exact same problem also occurs for dynamic args (in a route).
A general solution is needed for handling the common bookkeeping that occurs for vars and event handlers in init_subclass. Assigning new functions, descriptors, and vars to a state class should automatically update var and dependency tracking for the State and substates where appropriate.


Changelog in README.md is getting large

What about moving it into a separate file, e.g. CHANGELOG.md?

That's something we might want consider in the future (especially for old versions whose changelogs are not really relevant anymore), however right now I'd like it to be big and visible so that anyone will be well aware of the (many) changes that are coming.
Thanks for the suggestion!


Backup item action modifications to an item's namespace/name aren't saved in the file path in the tarball

A backup item action can update an item's namespace/name. If this happens, the resulting JSON file in the tarball will have the updated name, but the JSON file path in the tarball will not have the updated namespace/name.  This is because we get the original namespace/name here: https://github.com/heptio/velero/blob/master/pkg/backup/item_backupper.go#L120-L121 and then we construct the file path here: https://github.com/heptio/velero/blob/master/pkg/backup/item_backupper.go#L239-L243 without considering that the namespace/name may have changed during item action execution.

Unit test case demonstrating the bug: https://github.com/heptio/velero/blob/master/pkg/backup/backup_new_test.go#L961


[nodejs lambda layer] no metrics is exported to cloudwatch logs

name: Bug report
about: Create a report to help us improve
title: ''[nodejs lambda layer] no metrics is exported to cloudwatch logs"
labels: bug
assignees: ''

Describe the bug
A clear and concise description of what the bug is.
I have added the adot layer in the lambda
adotInstrumentation: {
      layerVersion: AdotLayerVersion.fromJavaScriptSdkLayerVersion(AdotLambdaLayerJavaScriptSdkVersion.LATEST),
      execWrapper: AdotLambdaExecWrapper.REGULAR_HANDLER,
    },

everything else is just default
I'm able to see tracing in xray so the setup is correct
I then add the metrics collector in the source code of the lambda
import { metrics } from '@opentelemetry/api';
const meter = metrics.getMeter('default');

// other code

// in the handler
        const counter = meter.createCounter('mymetric');
        counter.add(1, { success: true });

I can see surrounding logs around this code so the code has bee executed.
In cloudwatch, I do not see this metric.
Steps to reproduce
If possible, provide a recipe for reproducing the error.
What did you expect to see?
A clear and concise description of what you expected to see.
In cloudwatch, I should see this metric as a log
What did you see instead?
A clear and concise description of what you saw instead.
Only surrounding logs
What version of collector/language SDK version did you use?
Version: (e.g., v0.58.0, v1.11.0, etc)
latest layer
What language layer did you use?
Config: (e.g., Java, Python, etc)
nodejs/typescript
Additional context
Add any other context about the problem here.
### Tasks

Not stale

Not stale


Add UST (University of Science & Technology) domain

PR Description
Summary
This Pull Request adds the UST (University of Science & Technology, Korea) domain to the project, allowing users with @ust.ac.kr email addresses to register and use the service.
Background
I am a student at UST, Korea, and I noticed that our domain was not included in the list of supported educational domains. This PR aims to rectify that by including UST’s email domain in the project.

@hoangqnguyen I am sorry, the domain ust.ac.kr is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Release PR #662 failed with errors

A release job failed.
Release PR: #662
Commit: https://github.com/open-telemetry/opentelemetry-ruby/commit/6777495dcfcd82c3478b99b9fe319e4cbe3e205e

Release job completed with errors.
Failed to release opentelemetry-instrumentation-lmdb 0.16.0:
Remmote repo is open-telemetry/opentelemetry-ruby.git, expected open-telemetry/opentelemetry-ruby
Failed to release opentelemetry-instrumentation-http 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-graphql 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-http_client 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-api 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-sdk 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-common 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-exporter-jaeger 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-exporter-otlp 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-active_model_serializers 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-all 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-concurrent_ruby 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-dalli 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-delayed_job 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-ethon 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-excon 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-faraday 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-mongo 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-mysql2 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-net_http 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-rack 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-rails 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-redis 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-restclient 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-ruby_kafka 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-sidekiq 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-instrumentation-sinatra 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-propagator-b3 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-propagator-jaeger 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-propagator-ottrace 0.16.0:
Aborting because initial setup previously failed.
Failed to release opentelemetry-resource_detectors 0.16.0:
Aborting because initial setup previously failed.

This is a local failure when I tried to run toys release retry --yes --verbose 662. The specific failure was:
[2021-03-18 11:26:57  INFO]  Verifying git repo identity ...
[2021-03-18 11:26:57  INFO]  ["git", "remote", "get-url", "origin"]
Remmote repo is open-telemetry/opentelemetry-ruby.git, expected open-telemetry/opentelemetry-ruby
Aborting because initial setup previously failed.


Unable to register custodial account

For "Terminal Lightning" when I'm trying to create a "custodial" session, I get this error:
Unable to register custodial account
proxy error with context lit: invalid macaroon: permission denied
What am I doing wrong?  I was able to successfully create an Admin session with this same lightning node.

Where do I export the relevant logs?
Brendan
Sent from Proton Mail mobile
-------- Original Message --------
On May 15, 2023, 12:03 PM, levmi wrote:

Are you able to grab and share any logs to help us de-bug this issue for you?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

I think this is what you need?
Brendan
Sent from Proton Mail mobile
-------- Original Message --------
On May 15, 2023, 12:16 PM, Brendan wrote:

Where do I export the relevant logs?
Brendan
Sent from Proton Mail mobile
-------- Original Message --------
On May 15, 2023, 12:03 PM, levmi wrote:

Are you able to grab and share any logs to help us de-bug this issue for you?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

You can take a look at how to grab the relevant logs in the litd Troubleshooting Guide, but feel free to let me know if any further questions about how to grab it!

We can dig in more when we get those logs, but in the meantime, this is likely due to a macaroon issue and you could fix it by following this comment: https://github.com/lightninglabs/lightning-terminal/issues/463#issuecomment-1338099650

I don't know how to delete my admin.macaroon. I'm not that technical 🤣
Can I delete the app and reinstall it?
Brendan
Sent from Proton Mail mobile
-------- Original Message --------
On May 15, 2023, 4:32 PM, levmi wrote:

We can dig in more when we get those logs, but in the meantime, this is likely due to a macaroon issue and you could fix it by following this comment: #463 (comment)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

No worries! Understandable, can try to get you more detailed instructions. What OS are you using for your node? Umbrel?

I have the latest version of Umbrel
Brendan
Sent from Proton Mail mobile
-------- Original Message --------
On May 15, 2023, 4:37 PM, levmi wrote:

No worries! Understandable, can try to get you more detailed instructions. What OS are you using for your node? Umbrel?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

I think this email thread went cold. I believe you were going to send instructions for how to reset some macaroons or something?
Thanks for your help!
Brendan
Sent from Proton Mail mobile
-------- Original Message --------
On May 15, 2023, 4:38 PM, Brendan wrote:

I have the latest version of Umbrel
Brendan
Sent from Proton Mail mobile
-------- Original Message --------
On May 15, 2023, 4:37 PM, levmi wrote:

No worries! Understandable, can try to get you more detailed instructions. What OS are you using for your node? Umbrel?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Hiya, thank you for the bump on this. Bad news is that we don't have ready-made instructions for this. Good news is that I was able to scrounge around and find the pieces that should make it work. Better news is that, thanks to feedback from users like yourself, with a coming release of Terminal, this should no longer be an issue as we'll check macaroons and regenerate without any user action if needed on update/restart (https://github.com/lightninglabs/lightning-terminal/issues/540).
Okay, onto the good stuff... To delete and regenerate the macaroons on an Umbrel, you should start by:

SSH into the Umbrel node. The password is the same one you use to login to the Umbrel website. ssh<EMAIL_ADDRESS>This command works on Mac & Linux. If you are using a Windows computer, you'll need to use an app like PuTTY to SSH into the Umbrel node.
Once logged in, your terminal prompt should say umbrel@umbrel:~ $
Run bash inside the lightning-terminal docker container docker exec -it lightning-terminal_web_1 bash When inside the container, your terminal prompt should say bash-5.1$
Delete the macaroon in ~/umbrel/app-data/lightning-terminal/data/.lit/mainnet/ titled lit.macaroon
Restart Lightning Terminal

To quit the SSH session, just enter the exit command twice
For more guidance, you can also refer to the below issues which have some similarities, but some differences. You can also reach out to the Umbrel Community to ask for more guidance as that forum is normally pretty helpful (https://community.getumbrel.com/).
https://github.com/lightninglabs/lightning-terminal/issues/545
https://github.com/lightninglabs/lightning-terminal/issues/181#issuecomment-783499465
If you don't feel comfortable with this level of technical configuring on the CLI, I can also flag for you when the Terminal release comes out with the regeneration built in, should be relatively soon (weeks). Then, you can update to that and it should automagically work.

Good morning,
Any idea when the Lightning Terminal update that will fix this macaroon issue will come out? I'm really looking forward to being able to segregate lightning wallets for each of my kids.
Thanks,
Brendan
Sent from Proton Mail mobile
-------- Original Message --------
On May 23, 2023, 4:35 PM, levmi wrote:

Hiya, thank you for the bump on this. Bad news is that we don't have ready-made instructions for this. Good news is that I was able to scrounge around and find the pieces that should make it work. Better news is that, thanks to feedback from users like yourself, with a coming release of Terminal, this should no longer be an issue as we'll check macaroons and regenerate without any user action if needed on update/restart (#540).
Okay, onto the good stuff... To delete and regenerate the macaroons on an Umbrel, you should start by:

SSH into the Umbrel node. The password is the same one you use to login to the Umbrel website. ssh @.***
This command works on Mac & Linux. If you are using a Windows computer, you'll need to use an app like PuTTY to SSH into the Umbrel node.
Once logged in, your terminal prompt should say @.***:~ $
Run bash inside the lightning-terminal docker container docker exec -it lightning-terminal_web_1 bash When inside the container, your terminal prompt should say bash-5.1$
Delete the macaroon in ~/umbrel/app-data/lightning-terminal/data/.lit/mainnet/ titled lit.macaroon
Restart Lightning Terminal

To quit the SSH session, just enter the exit command twice
For more guidance, you can also refer to the below issues which have some similarities, but some differences. You can also reach out to the Umbrel Community to ask for more guidance as that forum is normally pretty helpful (https://community.getumbrel.com/).
#545
#181 (comment)
If you don't feel comfortable with this level of technical configuring on the CLI, I can also flag for you when the Terminal release comes out with the regeneration built in, should be relatively soon (weeks). Then, you can update to that and it should automagically work.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Hey Brendan, thanks for the follow up! With Lightning Terminal v0.10.1, this issue should hopefully be fixed. So, update to that version and it should work. Let us know if not!
P.S. Love that you're using custodial accounts to give your kids Lightning wallets! So cool!


[WIP] Add MSBuild Project SDK

Add a new project that creates an MSBuild Project SDK package that can be used to automatically add the required packages and build-time MSBuild targets to the immediately downstream project. The downstream project is also packaged up as an MSBuild Project SDK so that NuGet-packaged code generators can automatically pull in the CodeGeneration.Roslyn dependencies with a single  reference to the generator project.
For example, the generator project will look like this:
<Project Sdk="Microsoft.NET.Sdk">

  <Sdk Name="CodeGeneration.Roslyn.Sdk" Version="0.4.89" />

</Project>

And projects consuming that generator will look like this:
<Project Sdk="Microsoft.NET.Sdk">

  <Sdk Name="MyGenerator" Version="1.0.0" />

</Project>

In both cases, package references, dotnet tool references, targets, and properties will be automatically included without additional configuration.
Things left to do:

[ ] Simplify the targets and properties (there's a lot of repetition)
[ ] Add (integration?) tests for the end-to-end flow

[ ] Consuming the CodeGeneration.Roslyn.Sdk package in immediately downstream projects (generators)
[ ] Consuming generator Project SDKs in grandchild downstream projects

I very much like the idea! I wanted to do something similar :) Tests would be great.

@AArnott For these tests, I will need NuGet packages to be generated before test execution starts. Do you want to update your Azure Pipelines configurations to handle that or should I make packing the solution's NuGet packages part of the test arrange phase?

Sorry it's taken slow long to get to this. But I'm super excited at the prospect. I haven't looked at your code change yet.

I will need NuGet packages to be generated before test execution starts. Do you want to update your Azure Pipelines configurations to handle that or should I make packing the solution's NuGet packages part of the test arrange phase?

I would expect all of the build to be done before tests start, including build of packages. This is already in place:
https://github.com/AArnott/CodeGeneration.Roslyn/blob/95003217cec33f70f5a127e6da389b285ac63c59/azure-pipeline.yml#L44
Can you clarify what's missing?

I would expect all of the build to be done before tests start, including build of packages. This is already in place:
Can you clarify what's missing?

Ah, I guess I didn't look closely enough at the pipeline config and was going off of my local development experience. That should work.

Sorry it's taken slow long to get to this. But I'm super excited at the prospect. I haven't looked at your code change yet.

That's alright; I've been busy with a number of other things and still need to work on the tests. I'm going to switch to using Buildalyzer since getting the (in-process) Roslyn build setup with Microsoft's NuGet packages is difficult and brittle.


Make flask-continuum depend on sqlalchemy_continuum

pip install flask-continuum
does not install sqlalchemy_continuum
which results in:
<IP_ADDRESS> - - [28/Apr/2020 16:28:13] "GET / HTTP/1.1" 500 -
Traceback (most recent call last):
  File "/Users/volker/PycharmProjects/verivinum-core-api/app.py", line 25, in <module>
    from flask_continuum import Continuum
  File "/Users/volker/PycharmProjects/verivinum-core-api/venv/lib/python3.7/site-packages/flask_continuum/__init__.py", line 11, in <module>
    from .mixins import VersioningMixin      ## noqa
  File "/Users/volker/PycharmProjects/verivinum-core-api/venv/lib/python3.7/site-packages/flask_continuum/mixins.py", line 11, in <module>
    from sqlalchemy_continuum import changeset, count_versions, is_modified
ModuleNotFoundError: No module named 'sqlalchemy_continuum'

Installing flask-continuum with pip should automatically install sqlalchemy_continuum

Thanks for the heads up! I'll fix the issue and re-release as 0.1.7.


Keep GitHub Actions up to date with GitHub's Dependabot

Short description

Keep GitHub Actions up to date with GitHub's Dependabot
Proposed changes

https://docs.github.com/en/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot
https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#package-ecosystem

Also,
% black .  # to format files for black stable style 2024.  This adds one blank line to nine Python files.  😃
Resolved issues

Fixes: The warnings at the bottom right of:

https://github.com/sphinx-doc/sphinxcontrib-django/actions/runs/8039199482

@timobrembeck Your review, please.

Generated:

#67


Prune old table version for incremental models.

Follow up from https://github.com/dbt-athena/dbt-athena/pull/522
When using incremental models, specifically iceberg, we want to give the users the possibility to prune old table versions.
Each new operation in an iceberg table lead to have a new snapshot and a new table version, therefore is really easy to reach the max amount of versions for a specific table.
Requirements
As done for ha tabes let's use:

versions_to_keep (default to 4)
versions_to_keep is added to incremental models

Notes
This is definitely relevant for iceberg models for hive models might be relevant only if there are many schema changes, therefore can be used for both.
For incremental models delete_s3 inside expire_glue_table_versions must be set to False, otherwise actual data will be dropped.

Resolved by https://github.com/dbt-athena/dbt-athena/pull/533


add user friendly api

See https://github.com/TakesxiSximada/syaml/issues/9

Thanks!! This pull request is merged.
Until the new version 1.2.dev0 is released, please wait for a while. https://github.com/TakesxiSximada/syaml/pull/11


Feat/vmss upgrade policy

Description

Type of Change

[ ] Non-module change (e.g. CI/CD, documentation, etc.)
[x] Azure Verified Module updates:

[ ] Bugfix containing backwards compatible bug fixes

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[x] Feature update backwards compatible feature updates.
[ ] Breaking changes.
[x] Update to documentation

Checklist

[x] I'm sure there are no other open Pull Requests for the same update/change
[ ] My corresponding pipelines / checks run clean and green without any errors or warnings
[ ] I did run all  pre-commit checks

fixes #101

@microsoft-github-policy-service agree company="Singtel"


Standardize unique_key for incremental models

Many incremental models were developed before we had access to detector_id, so they were configured to use both station_id and lane to merge in new records. We now have some models using detector_id and some models using the prior method. This can lead to issues due to (potentially invalid) metadata updates. Wherever possible, these unique_key values should be updated to use detector_id, ideally. Part of this task is determining if this strategy will work correctly.
List of files under transform/models currently specifying any unique_key:
intermediate/clearinghouse/int_clearinghouse__detector_agg_five_minutes_with_missing_rows.sql
intermediate/clearinghouse/int_clearinghouse__detector_g_factor_based_speed.sql
intermediate/clearinghouse/int_clearinghouse__detector_agg_five_minutes.sql
intermediate/imputation/int_imputation__detector_agg_five_minutes.sql
intermediate/imputation/int_imputation__global_coefficients.sql
intermediate/imputation/int_imputation__detector_imputed_agg_five_minutes.sql
intermediate/imputation/int_imputation__local_regional_regression_coefficients.sql
intermediate/diagnostics/int_diagnostics__constant_occupancy.sql
intermediate/diagnostics/int_diagnostics__no_data_status.sql
intermediate/diagnostics/int_diagnostics__detector_status.sql
intermediate/diagnostics/int_diagnostics__samples_per_detector.sql
intermediate/db96/int_db96__detector_agg_five_minutes.sql
intermediate/performance/int_performance__station_metrics_agg_hourly.sql
intermediate/performance/int_performance__bottlenecks.sql
intermediate/performance/int_performance__detector_metrics_agg_five_minutes.sql
intermediate/performance/int_performance__station_metrics_agg_five_minutes.sql
intermediate/performance/int_performance__detector_metrics_agg_hourly.sql
marts/imputation/imputation__detector_summary.sql
staging/db96/stg_db96__vds30sec.sql

I agree James, there are several incremental models that have unique keys set that are not at the most unique / lowest level of grain, which leaves us open to potential CI issues with duplicates when detectors move to different lanes, etc.

However, defining the unique keys properly will still not completely eliminate the risk of failures if data comes in weird -- if the unique key is set to detector_id + sample_date, but the detector moves lanes in the middle of a day, it might show up with two different [volume] values for the same date with different time stamps in one of the diagnostics tables for the same time period -- [], so in addition to the unique key changes listed below, we should also build uniqueness tests so that we are being alerted properly when duplicates do slip through. There's already a ticket for me for that. :)

When reviewing all of our incremental models, I found they fell into the following categories:

Category 1 - model's unique keys are already set at the detector_id level [no action needed]
Category 2 - model's unique keys are at the station_id level, which is the correct strategy for that model [no action needed]
Category 3 - model's unique keys are at the station_id + lane level, which should be changed to detector_id, and detector_id is already an output of the model [unique key config should be changed]
Category 4 - model's unique keys are the station_id + lane level, which should be changed to detector_id, but detector_id is not yet present in the output of the model [code for the model should be changed and unique key config should be changed]
Category 5 - model is not currently set to be incremental, but we might want to change that, in which case we would need to define the appropriate unique keys

I have listed all incremental models that fall into each of these categories below. The next step in this ticket will be to make the changes to models where appropriate.

Category 1:  UNIQUE KEY = DETECTOR_ID + TIME -- no action needed
intermediate/clearinghouse/int_clearinghouse__detector_agg_five_minutes_with_missing_rows.sql
intermediate/clearinghouse/int_clearinghouse__detector_g_factor_based_speed.sql
intermediate/clearinghouse/int_clearinghouse__detector_agg_five_minutes.sql
intermediate/diagnostics/int_diagnostics__detector_status.sql
intermediate/performance/int_performance__detector_metrics_agg_five_minutes.sql
intermediate/diagnostics/int_diagnostics__no_data_status.sql
intermediate/performance/int_performance__detector_metrics_agg_hourly.sql

Category 2: UNIQUE KEY = STATION_ID + TIME but model is at the station level -- no action needed
(The bottleneck models all seem to be based on station ID, not detector ID, so I would keep these as is):
intermediate/performance/int_performance__station_metrics_agg_five_minutes.sql
intermediate/performance/int_performance__station_metrics_agg_hourly.sql
intermediate/performance/int_performance__bottleneck_delay_metrics_agg_daily
intermediate/performance/int_performance__bottleneck_delay_metrics_agg_five_minutes.sql
intermediate/performance/int_performance__bottleneck_delay_metrics_agg_hourly.sql

note: this model has a unique key at the station_id, lane, sample_date level, and both upstream and downstream models are merged at the detector id level, so it's possible we want to expand this model to be at that level as well, but because of where it is in the lineage, it didn't seem to me that this model needed a change -- curious what you think @JamesSLogan :
intermediate/diagnostics/int_diagnostics__constant_occupancy.sql
Category 3: UNIQUE KEY = STATION ID + TIME and model has upstream/downstream models with an incremental merge strategy that relies on detector ID -- UNIQUE KEY CONFIG NEEDS CHANGE
note: I think the whole imputation journey should be updated to merge uniquely on the detector_id level, just as the non-imputed journey is.
intermediate/diagnostics/int_diagnostics__samples_per_detector.sql
marts/imputation/imputation__detector_summary.sql
intermediate/imputation/int_imputation__detector_agg_five_minutes.sql
intermediate/imputation/int_imputation__detector_imputed_agg_five_minutes.sql
intermediate/imputation/int_imputation__local_regional_regression_coefficients.sql

Category 4:  UNIQUE KEY = STATION ID + LANE + ETC but code / output columns does not currently join in detector IDs BUT the data grain is at the detector level (using station id + lane) --  UNIQUE KEY SHOULD BE UPDATED but CODE NEEDS UPDATING FIRST
intermediate/db96/int_db96__detector_agg_five_minutes.sql
staging/db96/stg_db96__vds30sec.sql
intermediate/imputation/int_imputation__global_coefficients.sql

Category 5: MODELS ARE NOT INCREMENTAL but maybe they should be -- evaluate if unique key would be worth configuring
These are models that are not set to be incremental, probably because these are mostly aggregate models, so we expect them to be small enough where the unique key constraint isn't necessary. But if we are looking for performance gains in CI, it may be worth configuring these as incremental.
models/intermediate/performance/int_performance__detector_metrics_agg_monthly.sql
models/intermediate/performance/int_performance__detector_metrics_agg_weekly.sql
models/intermediate/performance/int_performance__station_aadt_with_K_value.sql
models/intermediate/performance/int_performance__station_metrics_agg_weekly.sql
models/intermediate/performance/int_performance__detector_metrics_agg_daily.sql
models/intermediate/performance/int_performance__station_metrics_agg_daily.sql
models/intermediate/performance/int_performance__station_metrics_agg_monthly.sql
models/intermediate/performance/int_performance__bottleneck_delay_metrics_agg_monthly.sql
models/marts/imputation/imputation__detector_imputed_agg_five_minutes.sql

I am open to any feedback on this analysis! In the meantime, I'll open some PRs to deal with each category where action is called for. @ian-r-rose @jkarpen

Thanks for the excellent, thorough analysis @summer-mothwood! Regarding int_diagnostics__constant_occupancy, I think it should be changed to use detector_id throughout instead of station_id+lane. This will bring the joins in its downstream model into alignment, as you alluded to. Maybe that puts it into category 4?

That all sounds correct to me @summer-mothwood.
One note on your category 4: there is a bit of history here, where many of the basal tables start out at the station+lane level, and don't have the metadata included. We've gone back and forth a bit on when we should try to join them so that these extra data are attached (see #214 and linked). One of the reasons it's a bit tricky is that with the large tables the join is quite expensive, so it wasn't always obvious at what stage we absolutely needed to do it.
All of this is to say, there may be good performance-related reasons to not join detector ID in for some of those large category 4 tables. Or maybe it's not a huge deal, but it's something to keep an eye out for.

This ticket is now done -- I split this work out into 3 PRs, mostly because several of these involved schema changes to models that had downstream dependencies, which made building and testing very annoying to do all together!
PR 1: https://github.com/cagov/caldata-mdsa-caltrans-pems/pull/470

transform/models/intermediate/diagnostics/int_diagnostics__samples_per_detector.sql
transform/models/intermediate/imputation/int_imputation__detector_agg_five_minutes.sql
transform/models/intermediate/imputation/int_imputation__detector_imputed_agg_five_minutes.sql

PR2: https://github.com/cagov/caldata-mdsa-caltrans-pems/pull/474

transform/models/intermediate/diagnostics/_diagnostics.yml
transform/models/intermediate/diagnostics/int_diagnostics__constant_occupancy.sql
transform/models/intermediate/diagnostics/int_diagnostics__detector_status.sql

PR3: https://github.com/cagov/caldata-mdsa-caltrans-pems/pull/481

transform/models/intermediate/imputation/int_imputation__detector_agg_five_minutes.sql
transform/models/intermediate/imputation/int_imputation__global_coefficients.sql
transform/models/intermediate/imputation/int_imputation__local_regional_regression_coefficients.sql
transform/models/marts/imputation/imputation__detector_summary.sql


Implement a simple task list

Implement a simple tasklist which prints the tasks to console.

Implemented in classe ConsoleTaskList


fix code doc torotationmatrix

forum issue: https://forum.babylonjs.com/t/unexpected-quaternion-torotationmatrix-behavior/44361

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/14338/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14338/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14338/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14338/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14338/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14338/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14338/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14338/merge#BCU1XR#0


[bug] Cannot startup clean docker image -- "Cannot read property 'logEnabled' of undefined

Version
Build/Run method

[X] Docker
[ ] PKG
[ ] Manually built (git clone - npm install - npm run build )

zwavejs2mqtt version: 1.2.3
Describe the bug
Upon a first-time install of the current docker image the docker image cannot start (either with docker-compose or just docker). It exits with the following error:

|___  /                      ()   |__ \                | | | |
/ /      ____ ___   _____ _ ___   ) |_ __ ___   __ | || |_
/ /\ \ /\ / / \ \ / / _ \ / __| / /| '_ _ \ / ` | __| |
/ /\ V  V / (| |\ V /  _/ _ / /| | | | | | (| | || |_
/|_/_/ _,| _/ _| |/|| || ||_, |_|_|
/ |                      | |
|__/                       ||
2020-12-28 21:04:46.146 WARN STORE: settings.json not found
2020-12-28 21:04:46.212 WARN STORE: scenes.json not found
2020-12-28 21:04:46.213 WARN STORE: nodes.json not found
/bin/sh: git: not found
2020-12-28 21:04:47.835 INFO APP: Version: 1.0.0-alpha.1
2020-12-28 21:04:47.836 INFO APP: Application path:/usr/src/app
TypeError: Cannot read property 'logEnabled' of undefined
at setupLogging (/usr/src/app/app.js:43:31)
at startGateway (/usr/src/app/app.js:56:3)
at start (/usr/src/app/app.js:38:3)
at /usr/src/app/bin/www:98:5
at tryCatcher (/usr/src/app/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/usr/src/app/node_modules/bluebird/js/release/promise.js:547:31)
at Promise._settlePromise (/usr/src/app/node_modules/bluebird/js/release/promise.js:604:18)
at Promise._settlePromise0 (/usr/src/app/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/usr/src/app/node_modules/bluebird/js/release/promise.js:729:18)
at _drainQueueStep (/usr/src/app/node_modules/bluebird/js/release/async.js:93:12)
at _drainQueue (/usr/src/app/node_modules/bluebird/js/release/async.js:86:9)
at Async._drainQueues (/usr/src/app/node_modules/bluebird/js/release/async.js:102:5)
at Immediate.Async.drainQueues [as _onImmediate] (/usr/src/app/node_modules/bluebird/js/release/async.js:15:14)
at processImmediate (internal/timers.js:461:21)
To Reproduce
Steps to reproduce the behavior:

Pull docker image
Start the image using "docker run --rm -it -p 8091:8091 --device=/dev/ttyACM0 --mount source=zwavejs2mqtt,target=/usr/src/app/store zwavejs/zwavejs2mqtt:latest"
Error

Expected behavior
The docker image should start...
Additional context
Docker version: 20.10.1, build 831ebea
OS: Raspbian, 32 bit (armv7l)

@blhoward2 have you used dev tag?

No, I pulled the latest image and ran the docker command straight from the readme.

Cloning and building a custom docker image starts fine. Bad build?

So you used latest tag, try to pull dev tag. I think that was a problem we have fixed some weeks ago

I had the same problem and using a dev tag instead of latest works. Alternative would be probably to create a dummy settings.json file:
{"mqtt":{},"gateway":{},"zwave":{}}
By the way - is it possible to disable storing d8d2dd23.values.jsonl on disk? Constant disk writes add wear to storage for embedded devices...

node values are not stored on disk, there is a store handled by zwave-js, I dunno if writes can be reduced, need to ask to @AlCalzone that is the author of zwavejs

@t00 I have created https://github.com/zwave-js/node-zwave-js/issues/1255 So I can close this one


[10.x] Improve DX for defining custom Eloquent builders

Improvement in this PR
This pull request is an attempt at slightly improving the DX of using custom Eloquent builders in models.
Currently, to get proper IDE support using a custom builder, a model should have the following two methods overridden:
public static function query(): ChirpBuilder
{
    return parent::query();
}

public function newEloquentBuilder($query)
{
    return new ChirpBuilder($query);
}

The first one is to get IDE autocompletion using Model::query, and the second one is to actually create the correct builder in all queries.
With this PR, the second method no longer needs to be overridden because the builder is guessed thanks to query's return type:
public static function query(): ChirpBuilder
{
    return parent::query();
}

Performance
Since newEloquentBuilder now uses Reflection under the hood, naturally we could ask whether this implies performance penalties. I ran this benchmark with and without the changes, and the result is 0.009ms in both situations on my Macbook M1.
Benchmark::dd(static function () {
    Chirp::query();
}, 20_000);

This could technically be a breaking change, not sure if this should target master then?

I don't understand well this PR. You currently can define custom Eloquent Builders supported by IDE.
For example, this is one of my models using custom Query Builder (and custom Collection):
<?php declare(strict_types=1);

namespace App\Domains\Country\Model;

use Illuminate\Database\Eloquent\Factories\HasFactory;
use App\Domains\Country\Model\Builder\Country as Builder;
use App\Domains\Country\Model\Collection\Country as Collection;
use App\Domains\Country\Test\Factory\Country as TestFactory;
use App\Domains\SharedApp\Model\ModelAbstract;

class Country extends ModelAbstract
{
    use HasFactory;

    /**
     * @var string
     */
    protected $table = 'country';

    /**
     * @const string
     */
    public const TABLE = 'country';

    /**
     * @const string
     */
    public const FOREIGN = 'country_id';

    /**
     * @param array $models
     *
     * @return \App\Domains\Country\Model\Collection\Country
     */
    public function newCollection(array $models = []): Collection
    {
        return new Collection($models);
    }

    /**
     * @param \Illuminate\Database\Query\Builder $query
     *
     * @return \App\Domains\Country\Model\Builder\Country
     */
    public function newEloquentBuilder($query): Builder
    {
        return new Builder($query);
    }

    /**
     * @return \App\Domains\Country\Test\Factory\Country
     */
    protected static function newFactory(): TestFactory
    {
        return TestFactory::new();
    }
}

Well, Sublime's PHP support is better than Visual Studio Code's then. 😅

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Move two global variables to subs.js.

Move recenter_pointer_on_display and suppress_scroll_pointer_update to subs.js.
Issue: https://github.com/zulip/zulip/issues/610

Automated message from Dropbox CLA bot
@hackerkid, it looks like you've already signed the Dropbox CLA. Thanks!

I think these don't really belong in subs.js ; they have to do with managing the pointer, but subscriptions.  Can we put them in a new pointer.js module?  I think fast_forward_pointer, furthest_read, and server_furthest_read will belong in such a module as well.

@timabbott Sure. I will send another pr for this.

OK; FYI from my perspective, rather than closing the PR and opening a new one, it'd be better to just update the existing PR with the new version of the code (you can update the PR title above) so that the discussion around what to do here all stays in one place.

@timabbott I have updated the PR.

@hackerkid this looks great, I posted one comment on where pointer.js should sit in settings.py.
Also, due to unfortunate timing, you're going to need to fix some merge conflicts with a rebase, since I just merged a refactoring conflicts with this.

@timabbott I have fixed the conflicts.

Merged, after a couple small tweaks:

Fixed the extra whitespace left near the variables moved out of zulip.js
Fixed the comma having been deleted after bot_data.js in zproject/settings.py

Thanks for doing this @hackerkid!


Revert some emoji back to narrow width

Summary of the Pull Request
A couple of codepoints, namely the card suites, male and female signs, and white and black smiling faces were changed to have a two-column width as part of #5795 since they were specified as emoji in Unicode's emoji list v13.01.
These particular glyphs also show up in some of the most fundamental code pages, such as CP4372 and WGL43. We should not be touching the width of the glyphs in these codepages, as suddenly changing a long-time-running narrow glyph to use two-columns all of a sudden will surely break (and has already broken) things.

PR Checklist

[x] Closes #5822
[x] CLA signed.

Validation Steps Performed

1 https://www.unicode.org/Public/13.0.0/ucd/emoji/emoji-data.txt
2 https://en.wikipedia.org/wiki/Code_page_437
3 https://en.wikipedia.org/wiki/Windows_Glyph_List_4

Yeah, this looks like it covers all the ones I was concerned about. I'm still a little worried that we may not be in sync with other terminals, but we'll see how that goes.

@msftbot merge this in 1 minutes


Create BestTimeToSellAndBuyStock.java

Created BestTimeToSellAndBuyStock and included test cases as well.

@anurags10 Please add problem statement and approach for this.

@indrakishore added problem statement and approach for this. Please let me know if anything else required.


juliabox.org gives 500 error code

For the last couple of hours after signing in with OAuth the response is '500: Internal Server Error"

Should be fixed now. Thanks for reporting.
Corrected a misconfiguration that probably broke auto-scaling.


Revert "Documentation on how to write unit tests using auto-generated mocked stubs."

Reverts grpc/grpc#10982

Sanity broke

We need to list all the md files in the doxyfile...
On Wed, May 10, 2017, 9:44 PM Nicolas Noble<EMAIL_ADDRESS>wrote:

@nicolasnoble approved this pull request.
How did that break sanity ? Oo
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/pull/11079#pullrequestreview-37482495, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJpudZ14SUR2ztvO5-raOy2_vdwxZBvZks5r4pIWgaJpZM4NXgch
.


How to execute a stored procedure?

Hi! i have a stored procedure called sp_Insert_xxxx, it receives 12 parameters. How can i do to execute it?

db.QueryContext(ctx, exec sp_Insert_xxxx @Q1 @Q2 ..., Named("Q1", v1), Named("Q2", v2))


esp_wifi_80211_tx() crashes when sending custom data frames (IDFGH-5526)

Environment

Development Kit: ESP-WROOM-32 NodeMCU
Module or chip used: ESP32-WROOM-32
IDF version: v4.3 (c9646ff0beffc86d2c6d1bfbad34da16e328e0e3)
Build System: idf.py
Compiler version: xtensa-esp32-elf-gcc (crosstool-NG esp-2020r3) 8.4.0
Operating System: Linux
Using an IDE?: No
Power Supply: USB

Problem Description
There is a regression in the esp_wifi_80211_tx() function causing it to crash the program with a LoadProhibited exception.
I need to send custom raw data packets. For that, I build a custom packet, filling all the required fields (Frame Control data, addresses, LLC data and payload) and send it using esp_wifi_80211_tx(). This was working with commit 0bbc721a633f9afe4f3ebe648b9ca99e2f2f6d5f, but I have updated the SDK to v4.3 tag and now when the esp_wifi_80211_tx() function is called, the device crashes.
I have been debugging the problem, and I have discovered that the crash does not happen if I set the raw packet to transmit as a Beacon frame (setting the very first byte of the raw data packet to value 0x80). But if the packet is configured as a data frame (with the very first byte set to value 0x08), the program crashes immediately after calling esp_wifi_80211_tx().
Expected Behavior
After calling esp_wifi_80211_tx(), the raw data packet is sent and the program continues working normally.
Actual Behavior
After calling esp_wifi_80211_tx(), the program crashes with a LoadProhibited exception.
Steps to reproduce

Build a custom data frame (the first byte must have value 0x08).
Send the frame using esp_wifi_80211_tx() function.

Debug Logs
When the crash happens, the following backtrace is printed to the log:
Guru Meditation Error: Core  1 panic'ed (LoadProhibited). Exception was unhandled.

Core  1 register dump:
PC      : 0x40092987  PS      : 0x00060a30  A0      : 0x80090e02  A1      : 0x3ffc0b50
0x40092987: rcUpdateTxDone at ??:?

A2      : 0x00000000  A3      : 0x3ffbaf50  A4      : 0x00000000  A5      : 0x00000000
A6      : 0x00000001  A7      : 0x3ffb2238  A8      : 0x3ffb75c0  A9      : 0x00000000
A10     : 0x3ffb2238  A11     : 0x3ffbaf3c  A12     : 0x3ffb2580  A13     : 0x00060623
A14     : 0x00000001  A15     : 0x00000001  SAR     : 0x00000020  EXCCAUSE: 0x0000001c
EXCVADDR: 0x0000000b  LBEG    : 0x4000c2e0  LEND    : 0x4000c2f6  LCOUNT  : 0xffffffff

Backtrace:0x40092984:0x3ffc0b50 0x40090dff:0x3ffc0b70 0x4009107d:0x3ffc0ba0 0x40144ccf:0x3ffc0be0 0x401454c8:0x3ffc0c10 0x40092682:0x3ffc0c50 0x4008d139:0x3ffc0c80
0x40092984: rcUpdateTxDone at ??:?

0x40090dff: lmacTxDone at ??:?

0x4009107d: lmacEndFrameExchangeSequence at ??:?

0x40144ccf: lmacProcessTxSuccess at ??:?

0x401454c8: lmacProcessTxComplete at ??:?

0x40092682: ppTask at ??:?

0x4008d139: vPortTaskWrapper at /home/esp/dev/esp-idf/components/freertos/port/xtensa/port.c:168

ELF file SHA256: a4d23a070ff95f53

Rebooting...

Thanks for reporting, we had a fix under internal reviewing. The issue will be closed automatically once the fix is available on GitHub. Thanks.

Thanks for reporting, fix on master is at https://github.com/espressif/esp-idf/commit/5578909ffba70eca3973f1303109b9077ad4cbf0, we are back porting the fix to release/4.3, will keep updated.

That's great news, thanks!

Thanks for reporting, fix on master is at 5578909, we are back porting the fix to release/4.3, will keep updated.

The fix is already in v4.3 of esp32-wifi-lib https://github.com/espressif/esp32-wifi-lib/commit/0bbc969738fac352a6bce8261f0130403d0078d9.
But the esp-idf needs to update sub-modules.
I'm wondering is it safe for users to manually checkout v4.3 branch of esp32-wifi-lib to verify the fix

Fix for release/4.3 by 1fd8fdcf7de7b25f9980e7cc973da2953784c273.

Thanks for reporting and updates, feel free to reopen.

I know its old issue and most likely solved, so i dont want to open new issue.
Currently i have not much time to confirm it with any newer version, but it happen with this commit (arduino v2.0.0):
https://github.com/espressif/esp-idf/tree/1cb31e50943bb757966ca91ed7f4852692a5b0ed
when i call esp_wifi_80211_tx before wifi connect to AP in STA mode then it crash with no backtrace. Wifi is properly configured, just AP is not available. When AP is available and esp32 is connected then i dont see crash, even after disconnecting from AP, but there has to be at least initial connection some time in the past.
If this can be confirmed by someone else thats good, if not thats fine, because i cant update to anything further, so i dont expect any fix.
Thanks


[MM-38047] Use mattermost-server/v6

Summary
This PR updates the dependency on github.com/mattermost/mattermost-server from v5 to v6.
Most changes are straight forward. On noticeable is the removal of model.AppError from model.Client4. Hence I've also removed it from ClientPP. Now a generic error is returned.
model.PossibleAtMentions not longer exists, so I copied the code over.
Please note that the plugin still works against v5 servers as the E2E test ensures.
Ticket Link
https://mattermost.atlassian.net/browse/MM-38047

Any idea why this PR has such a smaller diff in go.sum than https://github.com/mattermost/mattermost-plugin-starter-template/pull/157/files?

@mickmister I suspect it's because the version bump in the starter template is much higher (5.32 -> v6.0) then in this plugin.

Codecov Report

Merging #241 (60beb0f) into master (3b5697e) will increase coverage by 0.19%.
The diff coverage is 57.14%.

@@            Coverage Diff             @@
##           master     #241      +/-   ##
==========================================
+ Coverage   24.77%   24.96%   +0.19%
==========================================
  Files          52       52
  Lines        3257     3268      +11
==========================================
+ Hits          807      816       +9
- Misses       2373     2374       +1
- Partials       77       78       +1

Impacted Files
Coverage Δ

apps/app.go
100.00% <ø> (ø)

apps/subscription.go
0.00% <0.00%> (ø)

server/proxy/bindings.go
79.67% <ø> (ø)

server/proxy/expand.go
11.56% <ø> (ø)

server/proxy/install.go
0.00% <ø> (ø)

server/proxy/list.go
0.00% <ø> (ø)

server/proxy/service.go
0.00% <ø> (ø)

utils/utils.go
0.00% <0.00%> (ø)

server/store/service.go
85.24% <25.00%> (ø)

server/proxy/proxy.go
42.12% <84.61%> (+1.94%)
: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 3b5697e...60beb0f. Read the comment docs.

Heads up that I've sneaked in a fix for https://mattermost.atlassian.net/browse/MM-38116 into this PR. 92887c7 contains it. The return type of KVSet is not interface{} but only a single bool that indicates if the value changed. We can return a proper struct in the future, if we want. The changes are in 92887c7e3a1e88165da7e2776cd62006c076038b.

@DHaussermann I don't think there is any function testing applicable here. I've smoke tested it myself. Is there anything you want to look into? Otherwise I would just merge it.

@DHaussermann Heads up that I'm merging this PR without further QA testing.


Accept user emails as well as user IDs

Currently when doing anything with users, with the exception of invites, we must specify their ID, e.g. auth0|abc123 in order to reference them. It would be far nicer from a UX point of view if we could also use their emails as an alternative.
There are cases where multiple users will have the same email address. In situations like these, we should warn the user and force them to input an ID instead.

Affected commands:

org:accounts:add
org:accounts:edit
org:accounts:remove
projects:accounts:edit

It probably won't be possible to implement emails for org:accounts:add as the only way to get the user ID from an email is to look through the list of users on an organisation.


How to programing Cancel Order feature in my own strategy?

I know i can create my own strategy and define buy / sell signal base on whatever indicators i want. But how can i programing something like "Refusing to buy at ..." ?
I can't place cancelOrder() function at onPeriod: function (s, cb) {...}

It looks like everything necessary to cancel the order is contained within the "s" variable that is passed into the calculate and onPeriod methods.  There is a reference to the Exchange object as well as all of the past orders with their IDs.  However, I do not know the ramifications of doing so as I have no way of testing except when doing live trading.  Also, this seems rather risky as the "engine" will probably not be aware of the cancellation and still try to handle the pending sale.
It seems if a buy signal is sent, but there is still a pending sale that the engine should cancel for the pending order.  Is this something that zenbot already is supposed to do, but is not working?

It is working. When you see buying/selling signal, you may press 'c' to cancel.

Sorry, I may not have been clear @nedievas.
Using the manual controls, it works just fine.  However, when using the paper trade and the status is stuck in "buying" due to market conditions and then a "sell" signal is given, Zenbot continues to try to buy.
I only had this condition once, but it did raise a concern that a buy signal is essentially committed to unless a manual "c" is used.
Should Zenbot be canceling the open buy order when the signal goes from buying to sell or from selling to buy?

Dear issue reporter,
We have slightly changed our github issue policy and would now kindly request folks that have questions that they ask them in our zenbot subreddit.
You can find it here: https://reddit.com/r/zenbot
This issue will be closed, but if you disagree with your ticket being marked as a question feel free to leave a comment defending your case.
Thanks for contributing time and effort!
Greetings,
🤖


IP address assignment to device with no interface

**Python version: 3.4
**NetBox version: 2.0.9
When you create IP address within API, and then create device with that IP as primary IP, with not providing interface id you can see IP address in device view, but you don't see device attached in IP address view.

Looks related to #1285. Could you please see if you can recreate the issue under v2.1-beta1 (or the develop-2.1 branch)?

Same behavior is in 2.1 beta version

API requests with which i did that.
`curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'Authorization: Token xxxxxxx' -d '{ "address": "<IP_ADDRESS>/24", "tenant": "1" }' 'http://xxxxx/api/ipam/ip-addresses/'
echo
read -p "Provide id of ip:" ip_id
echo ${ip_id}
curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'Authorization: Token xxxxxxx' -d '{ "serial": "xxxx", "device_role": "4", "tenant": "1", "site": "24", "name": "test-device", "primary_ip4": "'$ip_id'", "device_type": "139" }' 'http://xxxxxx/api/dcim/devices/'
`


Strip out DirectClient implementors following load of Pac4jUser

Because vertx-web offers the UserSessionHandler, which auto saves the routing context's user in the session, it is impossible (short of disabling UserSessionHandler for specific paths, which will not work if there is a desire to use Direct/Indirect clients on the same path) to avoid saving DirectClient implementors in the standard vert.x user.
Given that we want to stay as close as possible to vert.x idioms, we should make the SecurityHandler strip out any DirectClient implementors from the Pac4jUser (if present) following the vert.x autoload of the user from the session.

This affects index.html in vertx-pac4j-demo where we want to be able to show IndirectClients stored in the session but also have an AnonymousProfile present when we connect to index.html (but not allow that to permit use of the URLs which require authentication).

(and yes, I know it's a workaround, but telling anyone wanting to use vertx-pac4j that we won't stick to vert.x idioms is not helpful).

Failing test defined for this, now need to apply a fix.


Audit default Builder options

Prior to marking hyper 1.0, it would be wise to audit all the default options in the various connection Builders. While changing them would be a compilation breaking change, it would be a behavioral change. (We could add a note that default options are not meant to be relied upon, that setting them explicitly is better, and thus reserve the ability to change defaults?)
This issue balances two of hyper's tenets: Correct vs Flexible. The existence of an option fulfills flexible, but as that tenet description points out, we should favor the default being safer, since Correct is more important.
I know some of the options that should probably include defaults are slightly tricky: timeouts. They only work if a impl Timer is provided, otherwise they can't set any timeouts. But we can discuss here how best to handle that: default on but only enabled if a timer is provided, warn if a timer is not provided, or require a timer be provided.
Action Items

[ ] Document that builder defaults are subject to change and not considered "stable"
[ ] Pick a default for HTTP/2 server max concurrent streams

One thing I was thinking about was that the defaults, whatever they are, shouldn't be relied upon. I'd like to document that, since we could want to either (a) add a new option with a default, or (b) adjust a default, with the goal of protecting the most people. There's a couple things now that are documented separately about stability, so I'd probably also add a # Stability section the main doc page. But it would also be good to add more details to each Builder docs.
I've added an action item.


Remove duplicate GitHub Actions workflow runs in PRs

Removes the duplicate CI pipeline runs during pull requests.

This works by configuring the workflows on push to only happen on the main branch.

LGTM


Plugin should use CordovaInterface.getThreadPool()

Hello everyone! Only in versions 6 and higher, to call the function "getPictures ()" is returning the following message:
THREAD WARNING: exec() call to ImagePicker.getPictures blocked the main thread for 23ms. Plugin should use CordovaInterface.getThreadPool().
More errors details:
FATAL EXCEPTION: AsyncTask #2
Process: com.imobsoft.imobvistoriaNew, PID: 1792
java.lang.RuntimeException: An error occurred while executing doInBackground() at android.os.AsyncTask$3.done(AsyncTask.java:309) at
java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354) at
java.util.concurrent.FutureTask.setException(FutureTask.java:223) at
java.util.concurrent.FutureTask.run(FutureTask.java:242) at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113) at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588) at
java.lang.Thread.run(Thread.java:818) Caused by: java.lang.SecurityException: Permission Denial: reading com.android.providers.media.MediaProvider uri content://media/external/images/media from pid=1792, uid=10060 requires android.permission.READ_EXTERNAL_STORAGE, or grantUriPermission() at android.os.Parcel.readException(Parcel.java:1599) at
 android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:183) at
android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135) at
 android.content.ContentProviderProxy.query(ContentProviderNative.java:421)  at
 android.content.ContentResolver.query(ContentResolver.java:491) at

Thanks for plugin and hope to be helping.

Hi, i have the same issue when i use media plugin to recording audio =s
04-05 15:44:29.143: D/AudioPlayer(30885): stopping recording
04-05 15:44:29.144: D/AudioPlayer(30885): size = 1
04-05 15:44:29.144: D/AudioPlayer(30885): renaming /storage/emulated/0/tmprecording-1491399868142.3gp to /storage/emulated/0/men_audio/my_sound.3gp
04-05 15:44:29.145: E/AudioPlayer(30885): FAILED renaming /storage/emulated/0/tmprecording-1491399868142.3gp to /storage/emulated/0/men_audio/my_sound.3gp
04-05 15:44:29.145: W/PluginManager(30885): THREAD WARNING: exec() call to Media.stopRecordingAudio blocked the main thread for 44ms. Plugin should use CordovaInterface.getThreadPool().
cordova v6

After intense debugging I managed to extract the following error log:
W/PluginManager: THREAD WARNING: exec() call to UniversalAnalytics.startTrackerWithId blocked the main thread for 34ms. Plugin should use CordovaInterface.getThreadPool().
    2018-09-09 22:13:56.522 22133-22233/com.myhurryapp.mbc W/CordovaPlugin: Attempted to send a second callback for ID: UniversalAnalytics******
        Result was: "Invalid action"
    2018-09-09 22:13:56.595 22133-22233/com.myhurryapp.mbc W/PluginManager: THREAD WARNING: exec() call to OneSignalPush.init blocked the main thread for 64ms. Plugin should use CordovaInterface.getThreadPool().
    2018-09-09 22:13:59.354 22133-22200/com.myhurryapp.mbc W/libEGL: EGLNativeWindowType 0x71c7a38010 disconnect failed
    2018-09-09 22:14:02.350 22133-22200/com.myhurryapp.mbc W/libEGL: EGLNativeWindowType 0x71c7a37010 disconnect failed

Now my concern and what I think is causing the app to crash are the following:
THREAD WARNING: exec() call to UniversalAnalytics.startTrackerWithId blocked the main thread for 34ms. Plugin should use CordovaInterface.getThreadPool().
and
THREAD WARNING: exec() call to OneSignalPush.init blocked the main thread for 64ms. Plugin should use CordovaInterface.getThreadPool().
I wonder what could be causing the freezing and Not Responding of the app and a possible work around to this issue?
Thanks