Remove developers page

I think that we can all agree that pagination for 1000+ developers is not the ideal solution. However, because Meetup has deigned it unnecessary to allow people to send them a search request that they implement as an api, it is currently impossible to display developers directly from meetup without just doing pagination with 40 people at a time. (edited)
We can display people i alphabetical order, which is the most useful for finding things, or we can display based on visited, which is probably more useful information overall but also has no possible organization, so finding someone specific would be much harder than alphabetical
My best solution was to scrap the data of name => id in ruby, generate a csv, and then send a csv along with the site. Then the CSV is parsed in the browser, and I'll give them a little search box, which will take my CSV and limit it to those searches, get the ids, then request the specific ids from meetup rather than just the group members
the problem is that that is a lot of work and stuff to send to the client for not a lot of value, so I wanted to get your guys opinion on whether or not we should just start to phase it out now, or if we made it better (and more csv heavy) then it might be worth keeping around
I think that something cool that could go in its place though is a kind of custom developers page, where we get to write about ourselves in markdown, and then we can do something similar to the blog where we render the list and then add links to the markdown file, which could be a neat way to highlight active members/members that want to be on the site.

I’ve done project similar with polling. The client side searching is super easy even with 10000 entries. And CSV is not needed if we use JSON which is not a huge ask to download asynchronously after the page loads.
However, you are correct in the value proposition. Adding a built tool to suck down the whole list would be cumbersome and having the client poll 40+ times might be mean to both the client browser and meetup. I have felt many times the developers at meetup don’t really live in this reality.
I am not apposed to removing the page. I would would also like to entertain any attempts at solving this even if nothing more than an academic exercise.

I'm in support of just scrapping it entirely. The work required to get an acceptable version of it working doesn't seem worth it to me.

Yeah to me isn't to much about could we do it so much as should we do ti.
I also don't really think that its meeting the core goal of the website, which is to give new people a place to come to learn about us and want to join the community rather than a place for current members to find other members.
I think that creating a jekyll md page similar to blog that renders a list of individuals and then links to the self hosted markdown is what I think could actually satisfy the goals of making us more than just a random organization and instead put a face to the name.
We could start to add that now if it would be helpful for you @maxx1128  and then you can copy pasta the config over, or we can leave it to you to configure for the new site and well just kind of hobble along or remove this page for now.

My vote is to remove the page. A quick poll in Slack a few weeks ago seemed to indicate that others felt the same way.
FWIW a previous iteration of the site had a self hosted developers database and we switched it to meetup.com for two reasons:

People forget it's there and don't keep it updated.
We wanted to move away from paid hosting, and at the time Heroku was clamping down on their free tier.

Sounds like a plan. I definitely think a full database is too much. I was thinking that we might use more of a "here are the officers and some other members" approach rather than "here is everyone", which makes the onus to keep it up to date not so burdensome.

@bsutt123 What were you thinking of for the "blog of individuals" page you mentioned? Would this be something an active member writes up about themselves and then is shown on the site?

@maxx1128 Well here is my thought. It may be helpful for people thinking about joining to be able to see some of the people that are actually a part of the group. Maybe we can highlight a couple of the groups officers, and then a couple of the more experienced members who are doing some talks as well as their expertise. This not only give them a chance to get to know some of us,  but also might makes it more likely that they will come to hack night or a study hall, or one of our presentations because we aren't faceless group members anymore.
The intention is not to have everyone on there, and we can be up front that this is not every member of the group, just the ones that want to be highlighted on the site. That should hopefully assuage the concerns that we would have to keep it up to date, because there isn't really any need to add people as they come in, just when you want to add yourself for whatever reason because you are doing presentations or want to be a "teacher" at study hall you can make your own markdown page and we will add it to the site.
I'm not sold that its a great idea, but if the intention of the developers page is to put a face to the name, and make us more human, i think that that is a more clear cut and effective way to do it.
If the goal was something else, or we don't like that goal in general, then I am more than happy just scrapping it. Just trying to think of what the page could be rather than what it currently is.

May I suggest as an alternative... A mentors page. Anyone willing to be a New Haven IO mentor would offer a small bio/blog/contact info to newhaven.io and they are listed on a mentor page (Jekyll makes this super easy with the _data directory).
This way people can touch base or have a face or two so when attending a meetup have a little sense of familiarity. Maybe ask questions or offer advise. I know that attending new groups it helps to have a point of contact but an organizer or MC already has way too much on their plate to also facilitate some hand holding. A (very loose and self administered) mentor program would take that burden off the MC during events.
It would also offer a more friendly perspective to the NHio website. In other words a page of people who have volunteered to be contacted by other people to help answer questions or simply direct them to the right persons.

I'm going to close this since #123 removed the developers page.
@sukima feel free to file a new issue referencing this one so we can thread conversatin about your proposal for a mentors page.


Documentation improvement on composite plugins

Expected Behavior
The documentation should provide samples that make sense for those who start building their own plugins.
It might make sense to add a real-life sample instead of project.getPlugins().apply(MyBasePlugin.class)
Hints I would like to add to the documentation:

If you consider adding optionalFeatureEnabled: Bool flag to the plugin, then consider implementing the feature in its own plugin. The user would be able to add the plugins they need so they will get only the tasks and configuration they need.
Something which is easier to understand than the current low-level as java-base for the demonstration of how splitting plugins helps in the long run. Two samples come to my mind: code coverage and Allure report. They both have gather and report parts, and they both need to handle aggregate report feature somehow. The funny part is the project that does aggregation could be a plain project without java plugin. I do not suggest to describe full implementation of allure-gradle plugin, however, I think it would be a good source for inspiration.

Current Behavior
https://docs.gradle.org/current/userguide/designing_gradle_plugins.html#capabilities-vs-conventions
The documentation does describe that it is worth separating capabilities from conventions, however, I would say that is extremely hard to understand when you start writing plugins.
I am 100% sure I have seen capabilities-vs-conventions section, however, I am 100% sure it did not click in my mind when I read it :-(
Context
I updated allure-gradle plugin, and it turned out that it was worth splitting the existing 1 plugin into 8 new plugins.
Before:

io.qameta.allure

After (see https://github.com/vlsi/allure-gradle/tree/facelift#technical-details):

io.qameta.allure (it is effectively io.qameta.allure-gather + io.qameta.allure-report)
io.qameta.allure-base
io.qameta.allure-gather-base
io.qameta.allure-gather
io.qameta.allure-download
io.qameta.allure-report-base
io.qameta.allure-report
io.qameta.allure-aggregate-report

This is still relevant


[FLINK-11069] [utils] Remove FutureUtil

What is the purpose of the change
The utility class FutureUtil contains duplicate methods and method which are not implemented optimally. I suggest to merge FutureUtil with FutureUtils and get rid of the waitForAll method.
Brief change log

Remove FutureUtil
Merge runIfNotDoneAndGet into FutureUtils
Get rid of waitForAll. Instead use FutureUtils#waitForAll
Introduce uncheck static method in SupplierWithException for the adjustment

Verifying this change
This change is a trivial rework covering by the relevant tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive):(no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

cc @tillrohrmann

Hi @TisonKun
18:26:28.316 [ERROR] Failed to execute goal com.github.siom79.japicmp:japicmp-maven-plugin:0.11.0:cmp (default) on project flink-core: Breaking the build because there is at least one incompatibility: org.apache.flink.util.function.SupplierWithException.unchecked(org.apache.flink.util.function.SupplierWithException):METHOD_ADDED_TO_INTERFACE -> [Help 1]

Thanks @yanghua.
I notice the inconsistent among util.function. With 1e6a91a3bf7e734eccdb034ce505b3775b709265 @StephanEwen mark the functional interfaces in util.function as @Public, but the following interfaces were not marked. Such a unchecked static method is proposed by @GJL.
I prefer the idea to make the interfaces final, and thus think it could be a follow up to refactor the static methods into FunctionUtils. Also remove CheckedSupplier.


pythonw fails on ARM MacOS

[ x] I read the conda-forge documentation and could not find the solution for my problem there.

Issue: the pythonw version of miniforge fails to initialize Python (path?) properly on ARM MacOS.
Note that pythonw is nearly essential to run wxpython apps.
Example:
(base) toby@bht21 ~ % pythonw
Fatal Python error: init_import_site: Failed to import the site module
Python runtime state: initialized
Traceback (most recent call last):
  File "/Users/toby/mf4.10.1/lib/python3.9/site.py", line 73, in <module>
    import os
  File "/Users/toby/mf4.10.1/lib/python3.9/os.py", line 29, in <module>
    from _collections_abc import _check_methods
  File "/Users/toby/mf4.10.1/lib/python3.9/_collections_abc.py", line 416, in <module>
    class _CallableGenericAlias(GenericAlias):
TypeError: type 'types.GenericAlias' is not an acceptable base type

(base) toby@bht21 ~ % python
Python 3.9.5 | packaged by conda-forge | (default, Jun 19 2021, 00:24:55)
[Clang 11.1.0 ] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>>

(base) toby@bht21 ~ % which pythonw
/Users/toby/mf4.10.1/bin/pythonw

(base) toby@bht21 ~ % which python
/Users/toby/mf4.10.1/bin/python
(base) toby@bht21 ~ %

Environment (conda list):

(base) toby@bht21 ~ % conda list
# packages in environment at /Users/toby/mf4.10.1:
#
# Name                    Version                   Build  Channel
backports                 1.0                        py_2    conda-forge
backports.lzma            0.0.14           py39h6167482_3    conda-forge
brotlipy                  0.7.0           py39h46acfd9_1001    conda-forge
ca-certificates           2021.5.30            h4653dfc_0    conda-forge
certifi                   2021.5.30        py39h2804cbe_0    conda-forge
cffi                      1.14.5           py39h702c04f_0    conda-forge
chardet                   4.0.0            py39h2804cbe_1    conda-forge
conda                     4.10.1           py39h2804cbe_0    conda-forge
conda-package-handling    1.7.3            py39h5161555_0    conda-forge
cryptography              3.4.7            py39h73257c9_0    conda-forge
expat                     2.4.1                hbdafb3b_0    conda-forge
gettext                   <IP_ADDRESS>          hea66d9f_1005    conda-forge
idna                      2.10               pyh9f0ad1d_0    conda-forge
jpeg                      9d                   h27ca646_0    conda-forge
libcxx                    11.1.0               h168391b_0    conda-forge
libffi                    3.3                  h9f76cd9_2    conda-forge
libiconv                  1.16                 h642e427_0    conda-forge
libpng                    1.6.37               hf7e6567_2    conda-forge
ncurses                   6.2                  h9aa5885_4    conda-forge
openssl                   1.1.1k               h27ca646_0    conda-forge
pathlib2                  2.3.5            py39h2804cbe_3    conda-forge
pip                       21.1.2             pyhd8ed1ab_0    conda-forge
pthread-stubs             0.4               h27ca646_1001    conda-forge
pycosat                   0.6.3           py39h46acfd9_1006    conda-forge
pycparser                 2.20               pyh9f0ad1d_2    conda-forge
pyopenssl                 20.0.1             pyhd8ed1ab_0    conda-forge
pypubsub                  4.0.3                      py_0    conda-forge
pysocks                   1.7.1            py39h2804cbe_3    conda-forge
python                    3.9.5           h54d631c_0_cpython    conda-forge
python.app                1.3              py39hf68e5b1_4    conda-forge
python_abi                3.9                      1_cp39    conda-forge
readline                  8.1                  hedafd6a_0    conda-forge
requests                  2.25.1             pyhd3deb0d_0    conda-forge
ruamel_yaml               0.15.80         py39h46acfd9_1004    conda-forge
setuptools                49.6.0           py39h2804cbe_3    conda-forge
six                       1.16.0             pyh6c4a22f_0    conda-forge
sqlite                    3.36.0               h72a2b83_0    conda-forge
tk                        8.6.10               hf7e6567_1    conda-forge
tqdm                      4.61.1             pyhd8ed1ab_0    conda-forge
tzdata                    2021a                he74cb21_0    conda-forge
urllib3                   1.26.5             pyhd8ed1ab_0    conda-forge
wheel                     0.36.2             pyhd3deb0d_0    conda-forge
wxpython                  4.1.1            py39h28cb02c_1    conda-forge
xz                        5.2.5                h642e427_1    conda-forge
yaml                      0.2.5                h642e427_0    conda-forge
zlib                      1.2.11            h31e879b_1009    conda-forge

Details about  conda and system ( conda info ):

(base) toby@bht21 ~ % conda info

     active environment : base
    active env location : /Users/toby/mf4.10.1
            shell level : 1
       user config file : /Users/toby/.condarc
 populated config files : /Users/toby/mf4.10.1/.condarc
                          /Users/toby/.condarc
          conda version : 4.10.1
    conda-build version : not installed
         python version : 3.9.5.final.0
       virtual packages : __osx=11.2.3=0
                          __unix=0=0
                          __archspec=1=arm64
       base environment : /Users/toby/mf4.10.1  (writable)
      conda av data dir : /Users/toby/mf4.10.1/etc/conda
  conda av metadata url : https://repo.anaconda.com/pkgs/main
           channel URLs : https://conda.anaconda.org/conda-forge/osx-arm64
                          https://conda.anaconda.org/conda-forge/noarch
          package cache : /Users/toby/mf4.10.1/pkgs
                          /Users/toby/.conda/pkgs
       envs directories : /Users/toby/mf4.10.1/envs
                          /Users/toby/.conda/envs
               platform : osx-arm64
             user-agent : conda/4.10.1 requests/2.25.1 CPython/3.9.5 Darwin/20.3.0 OSX/11.2.3
                UID:GID : 3328:1113
             netrc file : None
           offline mode : False

Sorry, @isuruf I had intended to ask if this should be in conda-forge/wxpython-feedstock rather than python-feedstock

@briantoby: This is not a wxPython issue, it does belong here in python.app.
Ideally, we could figure out how to build pythonw the way it's done with the python.org "framework" build, and then this would all "just work". but that's going to take someone with patience and autoconf experience, which we haven't found yet :-(
But if that describes you -- let us know!

I have commented on this in a number of fora over the years. I know it has been an active anaconda issue. Somehow, both homebrew and standard python dists avoid the need for a pythonw image. I wish that were true here too.
For my own work, partly out of ignorance of how the above could be made to work and also because I prefer that my app be named correctly in Mac menus (rather than be named python), I create a Mac bundle (using this script https://subversion.xray.aps.anl.gov/trac/pyGSAS/browser/trunk/makeMacApp.py).

Did you look at py2app (and py2app alias mode) -- that may have solved your problem.
Anyway, we know how to make this work -- in the "framework" builds, pythonw (and python) is a little executable that wraps the actual python interpreter. There's no reason it needs to be part of the Framework build, it's just that the build configuration isn't there to separate the two.
For someone familiar with autoconf, I don't think it would be a heavy lift, but no one has stepped up to do it.

I think this is all good now -- it's been working on ARM Mac for a while .....
So I'm going to close.


feat(ci): post comment with diff on chart PRs

Closes #54

Should result in comments looking like https://github.com/teutonet/teutonet-helm-charts/issues/54#issuecomment-1399959184


Downcompile with babel

Turns out this plugin doesn't run on older versions of Node. I get an error when running on 4.3 (actual lambda on aws version):

SyntaxError: Unexpected token =

I believe this is because the code in this plugin is only supported by newer versions of node unless you use babel. So it would be nice if you would down compile before publishing for use in older versions of node. I can try to hookup a PR tomorrow.

@justinmchase Sorry for late reply. We will support to Node.js 4.3 From now by #4.

Thanks! I did encouter this again at some point but my solution was to do the building in higher versions of node, this will be helpful thanks.


Converting MoveNet.Multipose.Lightning for use with Coral

Description
Hello, I'm attempting to use MoveNet.Multipose.Lightning with Coral but am having difficulty converting it to the proper format for Coral.
I can see that there is already a pre-converted model here, but that model is for singlepose MoveNet. What steps were taken to convert/optimize that MoveNet model to the proper format for Coral? How can I do that myself, but for the multipose model?
I've seen this page on model requirements and I understand what is needed, but I am having difficulty getting there. I've tried converting the .pb model using these steps, but it ran into a common error of Some ops are not supported by the native TFLite runtime. I tried following the solution steps listed there, but they weren't very clear. I've also tried converting the tflite model but I don't think it meets the requirements for Coral because I get this error when trying to convert it using edgetpu_compulter <model>: Attempting to use a delegate that only supports static-sized tensors with a graph that has dynamic-sized tensors..
I've also tried the solution listed here, but am getting this error:
Some ops are not supported by the native TFLite runtime, you can enable TF kernels fallback using TF Select. See instructions: https://www.tensorflow.org/lite/guide/ops_select
TF Select ops: StridedSlice

It looks like I can specify which operations I want, but I don't know which operations the model uses that are supported. All I know is that the StridedSlice operation doesn't seem to be supported.
Any help/guidance with this problem would be greatly appreciated! Thanks! 😀
Click to expand!
Issue Type
Support
Operating System
Windows 10, Linux, Ubuntu
Coral Device
USB Accelerator
Other Devices
Rapsberry Pi 4
Programming Language
Python 3.8
Relevant Log Output
No response

hello benank, hello hjonnala,
any update of the movenet multipose for coral usage?
I've seen this on the move net tensor hub website:
Initial release of the tflite MoveNet.Multipose model. Note that the current model uses dynamic shape input which makes it incompatible with accelerators, e.g. GPU. We are working on the accelerator-compatible version and will release them soon.
Do you know when will the multipose support coral?


Can i use python to create EA for MT4?

I want to create mt5 bot because mt5 is intergrated with python but the problem is that my broker doesn't have option to copy trade from mt5! So please is they any how i can create EA for mt4 using python?

I don't think this question be related to this project. take a look at ZeroMQ and https://github.com/AustenConrad/mql4zmq

I don't think this question be related to this project. take a look at ZeroMQ and https://github.com/AustenConrad/mql4zmq

Hello Mr Ahangarha thank you,
I know is not related but really look for solution on this issue


Implement HepMC3 event file format.

Implemented using pyhepmc_ng.
Also implemented the old formats HEPevt and HepMC2 with the same tool.


[folding] Option for single line collapse like in visual studio

Left VSCode right Visual Studios editor.
Could we get an option for collapsing code to single line instead of 2 lines? I understand the benefits of 2 line collapse (ex. correctly shown line numbers), but in many cases 1 line collapse is far more useful.

basically a duplicate of #24515


How do I set field value to null?

Looking to clear some columns but am not sure about the syntax. Thanks!

It appears that something like this works:  contact_note:'\N'  (so \N is what pg_dump is using as NULL)

Using '\N' works


[TACHYON-1529] Add link to the mailing list in the web ui.

https://tachyon.atlassian.net/browse/TACHYON-1529
Sample image:

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/7755/
Test PASSed.

+1 LGTM, thanks for including a sample image!


Multi-nop align is incorrect

Hi herumi,
	if (useMultiByteNop) {
		nop(size_t(getCurr()) % x);
		return;
	}

If getCurr() % 16 == 2 this would produce a 2 byte nop. This would then result in the new getCurr() % 16 being 4, which is incorrect.
This should be:
	if (useMultiByteNop) {
		if (size_t(getCurr()) % x == 0) return;
		nop(x - size_t(getCurr()) % x);
		return;
	}

Thanks.

Thank you for your quick check of my foolish bug.
I fixed it. https://github.com/herumi/xbyak/commit/d512551e914737300ba35f3c049d1b40effbe76d

Thanks very much for the fix!


Mystery Number in Julia | GSSoC'21 | Math

💥 Proposal
Mystery Number in Julia
Have you read the Contributing Guidelines on Pull Requests?
YES

/assign


Creating a new DateTime in a given time zone

Steps to reproduce
iex(3)> Timex.now("America/New_York") |> Timex.set(year: 2018, month: 10, day: 30)
#DateTime<2018-10-30 09:43:07.835523-05:00 EST America/New_York>

This came up because after daylight savings time, one of my tests broke, since I was using something like the above to generate a unix epoch to assert against.
expected_timestamp =
  Timex.now("America/New_York")
  |> Timex.set(year: 2018, month: 10, day: 30, hour: 10, minute: 0, second: 0, microsecond: {0, 6})
  |> DateTime.to_unix

The expected_timestamp value changed on me, since I didn't realize that Timex.now("America/New_York") implicitly locks you into EST vs EDT.
Description of issue
The expected results were a date time with an "EDT" offset, not "EST". I think this is related to #411, since to my mind, Oct 30 EST is an invalid date time - Daylight Savings Time is happening on that date.
I understand now from that linked issue that validating the new DateTime is not part of Timex.set's functionality, but now I don't know how to create a valid date time on that date. I would expect there to be a function something like Timex.new(naive_datetime, "America/New_York") but I'm not finding anything along those lines.

Ah, someone on the Elixir slack channel pointed me to a function that does what I'm expecting: Timex.to_datetime/2.
iex(6)> Timex.to_datetime(~D[2018-10-30], "America/New_York")
#DateTime<2018-10-30 00:00:00-04:00 EDT America/New_York>

iex(7)> Timex.to_datetime(~D[2018-11-05], "America/New_York")
#DateTime<2018-11-05 00:00:00-05:00 EST America/New_York>

The former is in EDT and the latter in EST, as expected.


can't clear all br

Select All and delete will leavebr

I would also like to ask how to solve this problem

Have you Example? Screenshot?

Select All and delete will leave
br

Everyone who came here knows this is the problem. what is the solution?

Unfortunately, there was no screenshot until now, so I would like to propose a solution that I use.The following example works very well for us. It's probably not the most elegant solution, but it solves the 'br' bug.
         <QuillTextEditor                   theme="snow"                   placeholder={'STRING'}                   value={value.replace(/�/g, '
')}                   onChange={(event) =>...}                 />

Unfortunately, there was no screenshot until now, so I would like to propose a solution that I use.The following example works very well for us. It's probably not the most elegant solution, but it solves the 'br' bug.
<QuillTextEditor theme="snow" placeholder={'STRING'} value={value.replace(/�/g, '
')} onChange={(event) =>...} />

i have this issue to and have some picture for you
on this picture I selected a empty lines contains

 and i cant delete it with Backspace button

Unfortunately, there was no screenshot until now, so I would like to propose a solution that I use.The following example works very well for us. It's probably not the most elegant solution, but it solves the 'br' bug.
<QuillTextEditor theme="snow" placeholder={'STRING'} value={value.replace(/�/g, '
')} onChange={(event) =>...} />

I cannot make that solution work.  What is that question mark character between the slashes?

Here is my hacky solution, if it helps anyone:
const updateNotes = (e) => {
	console.log({e});
	const newNotes = e === '

' ? '' : e;
	setEditingPriceList({
		...editingPriceList,
		notes: newNotes
	});
};


pct_data fields not served in format consistent with other fields

Greetings -
It looks like the fields in the pct_data group are not served like fields in other groups. specifically, the fields are not put in an array called "pct_data", as one would expect. Here's an example, where you will see that the fields in other groups (e.g., the wipos and uspcs groups) are given in an array, but pct_data fields are not:
GET http://www.patentsview.org/api/patents/query?q={"patent_number":"5116621"}&f=["patent_id","pct_102_date","pct_371_date","pct_date","pct_docnumber","pct_doctype","pct_kind","uspc_mainclass_id","uspc_mainclass_title","uspc_sequence","uspc_subclass_id","wipo_field_id","wipo_field_title","wipo_sector_title","wipo_sequence"]&o={"include_subentity_total_counts":false,"matched_subentities_only":true,"page":1,"per_page":25}&s=
{"patents":[{"patent_id":"5116621","uspcs":[{"uspc_mainclass_id":"424","uspc_mainclass_title":"Drug, bio-affecting and body treating compositions","uspc_sequence":"0","uspc_subclass_id":"424\/445"},{"uspc_mainclass_id":"424","uspc_mainclass_title":"Drug, bio-affecting and body treating compositions","uspc_sequence":"1","uspc_subclass_id":"424\/447"},{"uspc_mainclass_id":"424","uspc_mainclass_title":"Drug, bio-affecting and body treating compositions","uspc_sequence":"2","uspc_subclass_id":"424\/448"},{"uspc_mainclass_id":"424","uspc_mainclass_title":"Drug, bio-affecting and body treating compositions","uspc_sequence":"3","uspc_subclass_id":"424\/449"}],"wipos":[{"wipo_field_id":"16","wipo_field_title":"Pharmaceuticals","wipo_sector_title":"Chemistry","wipo_sequence":"0"}],"pct_data":{"pct_102_date":null,"pct_371_date":null,"pct_date":null,"pct_docnumber":null,"pct_doctype":null,"pct_kind":null,"0":{"pct_102_date":null,"pct_371_date":null,"pct_date":null,"pct_docnumber":null,"pct_doctype":null,"pct_kind":null}}}],"count":1,"total_patent_count":1}

Thanks for bringing this to our attention. This issue should be fixed now.


Unable to debug HTTP 429 response from ClusterIssuer's ACME Client.

Describe the bug:
Currently we are managing 55 let's encrypt certificate online.
But every time we try to add new certificate with clusterissuer.
ACME Client return HTTP 429 Too many request. (from let'sencrypt)
For diagnosis, we want to look at the payload of 429 response.
Increasing verbosity of cert-manager-controller (default:2, maximum: 6, now: 6) won't help.
Expected behaviour:
Developer can debug ACME client with kubectl logs -f cert-manager-...-... and verbose level 6.
Environment details::

Kubernetes version (e.g. v1.10.2):v1.15.9-gke.8
Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): GKE
cert-manager version (e.g. v0.4.0): v0.13
Install method (e.g. helm or static manifests): static (from website)

/kind bug

/area acme
/priority important-longterm

This should now be better in v1.0 as we now handle these ourselves instead of the Go library doing it.
Going to close this, feel free to /reopen if needed.
/close


CIF-2129 - remove "id" support for CIF Core Components

Description
Remove "id" support mainly used for categories for all relevant CIF Core Components. This one is huge, sorry. But it is 98% removing stuff.
Some tests have been reworked a little. "Highlights" with more than just deleted code to review:

https://github.com/adobe/aem-core-cif-components/pull/588/files#diff-f0a57b2faf7c72e55869260792116b0f26106aa776a76e30c1b993a60e209dd3
https://github.com/adobe/aem-core-cif-components/pull/588/files#diff-142d9e196ee29be35043977ebed365d585cd263ca8b168e8034ebb7a6f444c3e
https://github.com/adobe/aem-core-cif-components/pull/588/files#diff-27b27eb193ccc0105be818f374c0f1fc16e923d43c4895e67774629eeebfd26f
https://github.com/adobe/aem-core-cif-components/pull/588/files#diff-0bcf31af5cbb7c0362413cc00d3c3bbf90d29d6dd1e86b420860a3e04565caab
https://github.com/adobe/aem-core-cif-components/pull/588/files#diff-1fe2e6005a652368e24f88b713e6dd127521cd3278a2b2329cefb0ac06c0bf45

Related Issue
CIF-2129
Motivation and Context
Prepare for CIF 2.0
How Has This Been Tested?
Adjusted unit tests & ITs. UI tests did not require any adjustment.
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes and the overall coverage did not decrease.
[x] All unit tests pass on CircleCi.
[x] I ran all tests locally and they pass.

Setting the PR to draft for now as new features have been added to master branch which must be reviewed as well.

I think CommerceContentFragmentImpl was not updated yet.

@LSantha removed ID usage from CommerceContentFragmentImpl as well.


feat(SolScript): CW-7486 add delegate and undelegate script

Task linked: CW-7486 Add delegation support to coin-sol


Full Github URL isn't working always

This works:
eget https://github.com/natesales/q

# file q
q: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=mxYZfmW39jbfAoEkWt-g/OIPz-cV31mFntE2scAxz/trG6K7JTtKLLSe8ThtCp/nzp3wY8I98v7fTxDZkQz, stripped

But this not,
eget https://github.com/mr-karan/doggo

# file doggo
doggo: HTML document, Unicode text, UTF-8 text, with very long lines (18275)

I think this was recently fixed by #41 and hasn't been released yet.


Make clear all the possible classes for ffi exports in docs

Actual docs for ffi exports should be updated to take in account all possible cases:

The [export string] is optional and it can have the @static annotation or not
You can export an instance method of a new class defined in eta code subclassing an existing java interface, abstract class or nomal class

For example wai-servlet define a new network.wai.servlet.DefaultWaiServlet that extends the abstract class javax.servlet.GenericServlet and then it lets you export it implementing the abstract method service
Although the idomatic use of non static ffi exports is the previous one, you can export instance methods for non abstract classes (example here)
If you write an ffi export without the @static annotation and without [export-jwt] eta generates an instance method in the module class and it can drive to unexpected behaviour, cause it generates a static method with the same name of the function (see #710)

The ffi accepts IO [return-type] instead Java [export-jwt] [return-type] as result type

@rahulmutt Maybe the compiler should reject non static ffi exports without [export-jwt]?

@jneira Yes, definitely.

I think it can be closed, filling a new issue for the suggestion in https://github.com/typelead/eta/issues/772#issuecomment-398002748


Request Money - Copied Information Does Not Update When Changes are Made in IOU or Language Settings

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Click on the plus sign and select "Request Money."
Add the desired amount and email for the money request.
Double-click on the requested money to open the IOU.
Change the amount and currency, then go back one step.
Right-click and select "Copy" to copy the updated information.
Observe that the copied information is not updated.
Repeat the process while changing the language settings and note that the copied information still does not update

Expected Result:
The copied information should be updated accordingly when changes are made in IOU or language settings.
Actual Result:
The copied information does not update when changes are made in IOU or language settings, which can lead to confusion or errors for users.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: v1.3.61-3
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/115492554/c69a59b4-c669-4be3-97d0-3b1dd02bb02d
https://github.com/Expensify/App/assets/115492554/6f7e3b85-702e-47ad-8425-f1a7d9ae4f51
Expensify/Expensify Issue URL:
Issue reported by: @TewodrosGirmaA
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1692945253540029
View all open jobs on GitHub

I don't think this is a duplicate, so I will test soon.

I've run out of time today and will test soon.

Still on my testing list

Waiting for proposals here.

Proposal
Please re-state the problem that we are trying to solve in this issue.
Request Money - Copied Information Does Not Update When Changes are Made in IOU
What is the root cause of that problem?
ContextMenuAction does not check if there are any changes in the request money report. It goes to this block directly:
https://github.com/Expensify/App/blob/cd9e86e683ed1a6167888d758c73c74346cfd529/src/pages/home/report/ContextMenu/ContextMenuActions.js#L202-L210
What changes do you think we should make in order to solve the problem?
Check if there are any amount/currency changes in the IOU report:
if (ReportActionsUtils.isMoneyRequestAction(reportAction)) {
                    const parser = new ExpensiMark();
                    const requestMoneyReport = ReportUtils.getReport(originalMessage.IOUReportID)
                    const isRequestMoneyUpdated = (requestMoneyReport.total !== originalMessage.amount) ||
                        (requestMoneyReport.currency !== originalMessage.currency)
                    const modifyIOUMessage = `requested ${requestMoneyReport?.cachedTotal}`
                    Clipboard.setString(isRequestMoneyUpdated ? modifyIOUMessage : parser.htmlToText(content))
}

There is another problem in that when the user changes the currency, it does not update it in the IOU store.
For this, we need to correctly implement this line to the EditRequestAmountPage:
IOU.setMoneyRequestCurrency(currency)

What alternative solutions did you explore? (Optional)
N/A

fix by https://github.com/Expensify/App/pull/27142

Ok, with this feedback, I'm going to close it out.


Validations for parameters

Validates that the parameters in the post request are not null or empty strings.
Validates that the parameters that are indexed are smaller than 1500 bytes, as required by datastore.
Filtering by category by an empty string queries all.

Just brought the changes from main to check that I did not break anything with the PR


Tests for @shared components

This picks up from #1480, addressing #1400, but with different tactics as already prepared in earlier PRs:

unit tests are the default now, where every component has to have one
use a testRender method which is the bare minimum for each component
storybook stories are optional and only used for UI development, but not for automatic test runs
all the new stories in here were copied over from #1480 (thanks @EnzoVezzaro!), but source all their dummy data & dummy props from the respective component test, or from __fixtures__
mock most important hooks usage with dummy data for all tests

these hooks are working across all tests now: useWeb3(), useUserPreferences(), useMarketMetadata(), defined in .jest/jest.setup.js with dummy data defined in .jest/__fixtures__/
downside: redefining their return data in individual tests does not really work so careful which hooks to mock globally. Alternatively, things can be always mocked at beginning of individual tests.

provide pattern for mocking our @utils methods

Jest-native mocking, e.g. using<EMAIL_ADDRESS>makes Jest pick this up automatically.
Also works for mocking all dependencies, e.g. to create mocks for anything in ocean.js, create file structure<EMAIL_ADDRESS>

better separation between mocks & fixtures
NO extensive refactoring of all our components
closes #1400
closes #1480

Developing...

We should get this through already as it sets the base for writing tests and provides many patterns which can be followed already. Main reason to merge already is that I end up writing tests for everybody’s changes we ship onto main in last days/weeks to keep my PR here green. So we all need to get into the habit of writing and/or modifying tests if we add new stuff


[Snyk] Security upgrade @apollo/server from 4.9.5 to 4.11.1

Snyk has created this PR to fix 7 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):

package.json
yarn.lock

Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHTOREGEXP-7925106
  666

Asymmetric Resource Consumption (Amplification) SNYK-JS-BODYPARSER-7926860
  624

Cross-site Scripting (XSS) SNYK-JS-COOKIE-8163060
  529

Open Redirect SNYK-JS-EXPRESS-6474509
  519

Cross-site Scripting SNYK-JS-EXPRESS-7926867
  469

Cross-site Scripting SNYK-JS-SEND-7926862
  319

Cross-site Scripting SNYK-JS-SERVESTATIC-7926865
  319

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Cross-site Scripting (XSS)
🦉 Open Redirect
🦉 Regular Expression Denial of Service (ReDoS)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
103

Relevant Lines:
103

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
103

Relevant Lines:
103

💛  - Coveralls


Add the famous r/uofu CS major post to the "cs major" rule

https://www.reddit.com/r/uofu/comments/qmse1c/85_of_computer_science_students_suck_ass/

Done!


Implement support for GraphQL Schema Language

Add support for the GraphQL Schema Language described at http://graphql.org/docs/typesystem/

Introduce .graphqls schema file type and parser definition
Syntax highlighting, e.g. for schema keywords such as type, implements etc.
Enable "Find usages" and "Go to Declaration" for types and fields
Update documentation provider to use the new schema PSI

Implemented in v1.1.0


enzymes_topk_pool error

🐛 Bug

return aggr_out + self.lin(x)
The size of tensor a (1600) must match the size of tensor b (1601) at non-singleton dimension 0
To Reproduce
run enzymes_topk_pool example
Steps to reproduce the behavior:

Expected behavior

Environment

OS: Windows
Python version: 3.6.2
PyTorch version: 1.0.1
CUDA/cuDNN version: 10.1
GCC version: VS 2017
Any other relevant information:
torch-scatter 1.1.2

Additional context

Hi, I can not reproduce your error. What torch-geometric version/commit are you using?

Ah, reproducible with current torch-geometric from pip, but already fixed in master. I crafted a new bugfix release with 1.1.2. Please upgrade :)

Thank you. It works.


does not working on Genymotion

hi there
does not working on Genymotion
facebook , or twitter or instagram

i think Doesn't work on apps with ssl pinning @r0ysue what do u think ?

please paste the error message
or
TRY IT ON A  REAL PHONE ~

There is no error message there.
for exp if i try to pinterest app  i can see variables.
Pinterest doesn't use SSL pinning.
but if i try instagram, facebook, youtube etc.
does not working. without error.
If I ask, would you try one of these apps?

@r0ysue ?

Maybe the application you listed doesn't use the Android System API @gaplan

Maybe the application you listed doesn't use the Android System API @gaplan


relocate connector mocks

It makes more sense for mock data types to be
owned by the service package, not by the connector package as a whole.

Does this PR need a docs update or release note?

[x] :no_entry: No

Type of change

[x] :broom: Tech Debt/Cleanup

Test Plan

[x] :zap: Unit test
[x] :green_heart: E2E

@pandeyabs @neha-Gupta1 This is ready for review, please and thank you!


Use of this plugin causes scene update to get called 2 times before create on restart()

Phaser 3.17.0
Description:
I was having this crazy bug where if I restarted my scene (or went to scene b then back to a) it would crash in my update method for undefined items. After some digging I found that my scene was having update called BEFORE create but only after the scene had been loaded at least once.
I removed all of my code until I found the culprit.
this.load.tilemapTiledJSONExternal('map', '/assets/level1.json'); in my preload method.
class SceneLevel extends Phaser.Scene {
	constructor() {
		super({ key: 'SceneLevel' });
	}
	preload({ level = 1 } = {}) {
		console.log('preload');
		this.load.tilemapTiledJSONExternal('map', '/assets/level1.json');
	}
	update() {
		console.log('update');
	}
	create() {
		console.log('create');
		this.time.delayedCall(3000, () => this.scene.restart());
	}
}

outputs to console
[Log] preload
[Log] create
[Log] update (x184)
[Log] preload
[Log] update (x2) // here it is. Why does this plugin cause this to be called here?
[Log] create

Thanks for the issue, I'll see if I can replicate/diagnose this hopefully sometime this weekend.

Okay, I tracked this down. Details are here: https://github.com/photonstorm/phaser/issues/4629
IMO this is a Phaser-side issue (unless the devs get back and say it's my plugin's fault for a reason I don't currently know), so there's nothing to fix on our side. In the meantime, the workaround is to add a check at the start of your update method to abort running if the scene isn't active:
if (!this.sys.isActive()) {
  return;
}

Hope that helps!

I am experiencing the same thing with phaser's internal multiatlas. So if my setup is not completely messed up, it is quiet likely on phaser's side.


Links enclosed in < > not linked or rendered correctly

The following Markdown should produce a link that automatically escapes the space in the link.
[link text](</file im linking to.md>)

However, it is not possible to follow this link in the editor, and the colourising is incorrect.

This does however link correctly in the VS Code Markdown Preview.

This definition has changed in 0.29. The relevant Common Mark testcase is as follows:
  {
    "markdown": "[link](</my uri>)\n",
    "html": "
link
\n",
    "example": 486,
    "start_line": 7543,
    "end_line": 7547,
    "section": "Links"
  },

This extension only handles the grammar highlighting, not the link providing logic (but as you note the highlighting is also incorrect)
Please file the link detection issue against VS Code itself

This looks like a duplicate of #80 which provides additional detail?

Fixed by 2f9bda284d391f97982f7932ba49eb89b2ac83b1


cli: A fancier CLI

This replace the logger with a fancy cli.
See the gif:

Wow @joyeecheung, nice work.
Do you intend to do the lib/cli.js unit tests?

@alopezsanchez Not really in this PR, because those involves too much chalk-ing for me XD you can pick this one up if you want.

(I can't believe I am saying this in this repo, but here we go): CI looks green.
https://travis-ci.org/nodejs/node-core-utils/builds/300138333
https://ci.appveyor.com/project/joyeecheung/node-core-utils/build/145.${patch}

@joyeecheung okey, no prob! I'll do it.

Going to merge this mostly because I want to use it tonight...


Number Input support for numbers with a dot and no decimals

As @fredofm explains in the issue #1660, when you type:
"1," -> the component transforms this value into "1". It can make sense because as you didn't type the fractional part it will return the integer one.
"1." -> the component transforms this value into "". It can make sense but I would expect the same behaviour as "1,".
As I explained in the comments of that issue, it looks like it is a bug from the HTML <input type=" number" />, which understands the comma as a decimal number when there are no decimals at all (1,, 12,, 4483,, ...) but doesn't apply the same logic on the dotted ones.
So, the feature here is to make the component behave consistently for both scenarios since they are variants of the same use case.

I have done some research about how the HTML5 input with type="number" works and it is quite limited in all the modern browsers due to the fact that it adapts to the browser locale.
The issue that you explain can be "turned around" if you try to use the component from, for example, an "en-US" browser.
However, it is complicated to be handled to handle all the cases, I have 2 proposals:

Handle numbers as an input with type="text" and handle all the possible scenarios in code.
Add a prop "separator" (with a default value) to the NumberInputContextProps in order for the wrapped DxcTextInput component to handle the logic based on it.

If you have any other suggestion, feel free to share!


Scanning the qr code on the terminal screen with the expo go app, I get a network connection timed out error

Hi team,
I cloned the github repo https://github.com/centrehq/verite
and followed the instructions as given in the readme file.
It says it is required to use NodeJS14 and npm7 but Node14 comes with a default combination with npm6 and I can't use npm7 with Node14. I have also used higher versions of Node i.e above 14 in combination with npm7 and above. That also didn't work.
I'll be highly obliged if you suggest anything to me anything, so that I can run the sample.
I've attached the error screenshot too
Thanks.

@JayAdityaNautiyal I just did a fresh clone on a macbook with the following versions of node and npm:
Node: 16.17.0
NPM: 8.15.0
When I run npm run setup everything works fine.
Can you share the specific node version and npm version by checking node -v and npm -v?

Thanks @polluterofminds
Verite should update its documentation for the pre-requisites section and update the node and npm versions. Though I still had issues running it on windows.
So I spinned a linux machine on Azure and installed node and npm with versions used by you, and the command  npm run setup is running fine.
But when I run the npm run wallet and scan the code on screen on the expo go app, I get a network connection timed out on the expo go app for which I have attached a screenshot.
Can you please help with it?

anyone there ?
@polluterofminds
@kimdhamilton

I'm looking into this now. Because you're running on a VM, I wonder if you're hitting some firewall issues. Expo requires tunneling to run locally. Will try to replicate.

thanks @polluterofminds
I thought it was an issue with the cloud so I used local VirtualBox and started a linux machine out of it. I am getting the same error as above on the expo go app.
Maybe this issue is with the VM.
I don't have a Mac OS, can you please look into it so that how can I run the sample.
Thanks.

Yeah let's try to get this working on your windows machine @JayAdityaNautiyal!
You said:

Verite should update its documentation for the pre-requisites section and update the node and npm versions. Though I still had issues running it on windows.

What exactly were those issues on Windows? Can you share as many details as possible including the errors?

sure @polluterofminds
So the issue on running the sample on my windows machine locally was that when I was running the command "npm run setup" , I would get an error that " '.' is not recognized as an internal or external command,
operable program or batch file." I've attached it below:

Then I tried to run the commands in the ./bin/setup file, like npm install. That also threw error as :

Running it on a VM using virtual box or AZURE cloud, I could run the application and get the qr code on screen but while scanning it from the mobile app it would give "connection timed out error".
So we tried it on mac and the URL for "metro waiting on exp://*  " was different in mac(where it is running correctly). So can you also tell where in the code can we enhance these port configurations set the environment variables as I couldn't find where are the ports(like 19000) have been configured. The connection with the URL exp://<IP_ADDRESS>:19000 was not done so we can see a way of changing the configuration, and running the code on VM as well.

Looks like we might need to conditionally update the setup script for Windows. I was under the impression that we had Windows users successfully running this, but maybe not.
This thread indicates that the relative path format of the setup script is throwing things off. If you want to confirm this, you could manually go into the package.json and try updating ./bin/setup to the absolute path of that file on your machine.
https://stackoverflow.com/questions/48321639/error-is-not-recognized-as-an-internal-or-external-command-operable-program-o

Verite is set up as an npm workspace (which requires npm v7 or greater). The dependencies for all packages are installed unifiedly from the root level using npm install. As long as Node.js v14 is LTS, you can use it by upgrading the npm version to 7. (npm i -g npm@7)
Verite's CLI scripts were written in UNIX style (e.g. inline mutli-commands delimited by ; which cannot be parsed in Windows, besides finding the path of a bash script file).
In order to setup the dev environment on Windows, you have to change the UNIX style scripts into Windows style in all package.json files. It sounds a little tricky.
Alternatively, on a Windows machine, we can use WSL without changing UNIX style scripts at all. I think this is the best option.
Regarding the timedout issue in lauching wallet, tunneling application is required in Expo as long as your device isn't connected to your LAN. Once npm packages are installed, you can directly run the wallet by executing npx expo start --tunnel in the wallet folder. (In Expo SDK v45, the UI of tunneling isn't supported anymore, but only available via CLI.)
After all, the current Verite documentation is very correct and has no issue at all.
PS. To avoid the hassles due to npm workspace dependency management, you can extract the wallet as an indenpendent repo like this. Though I didn't make it up-to-date, it is cross-platform workable at least.

Hi @euj1n0ng
I tried using WSL on windows and I was able to run the command npm run setup and npm run dev.
But when I run npm run wallet and scan the qr code on the screen using the mobile app, I get the same **network response timed out ** error.
The output of npm run wallet as received in the console is :

And the error on the mobile screen is :

I also extracted the wallet from the independent repo shared by @euj1n0ng and received the same error as above  on the mobile application while scanning the qr code.
If you can please fix this from here, it will be a great help.

Hi @euj1n0ng @polluterofminds @kimdhamilton
Can you  please look into it as few of my folks tried on their windows machine as well and all had same errors!

Hi @JayAdityaNautiyal, in general we're not staffed to help with platform-specific support, but have you tried looking at guidance for similar projects? I.e., I imagine it might be common with other react projects on windows.
We're really glad you're using this project, and we'll leave this issue open in case another windows user can help

@JayAdityaNautiyal , share your challengeTokenUrl.
I am sure you're troubling with the same issue - tunneling. But, this time, not on the mobile wallet app but on the demo web app.

I have also followed the same steps (tunneling + WSL), and I am hereby sharing the challengeTokenUrl. Does anyone have an idea how to fix the issue?

I still can't repro


Merge _dev_frodo

This is mostly porting SHA3 and Frodo to the latest version of lib, but it also includes some changes to lib itself. I checked that SHA3, Frodo and lib verify. I still get errors verifying Blake2 but so I do in _dev.
I don't expect this to cause any regressions. I'll wait until the end of the day before merging to give you a chance to review the changes if interested (go to the end of the page to see the changes to lib).
Some notes I gathered that I would like to discuss:

The main point of having a single parametric type of buffers for mutable and immutable buffers is to be able to write functions that can take as argument either a mutable or an immutable buffer as long as the immutability is respected. However, even the simplest example keeps the mutability tag as an explicit argument when extracted which is very off-putting:

module Test

open FStar.HyperStack.ST
open Lib.Buffer

let uint8 = UInt8.t

val f: #t:buftype -> b:lbuffer_t t uint8 2ul -> Stack uint8
  (requires fun h -> live h b)
  (ensures  fun h0 _ h1 -> modifies (loc b) h0 h1)
let f #t b =
  b.(0ul)

let main () : St C.exit_code =
  push_frame();
  let b = create 2ul 0uy in
  let y = f b in
  pop_frame();
  C.EXIT_SUCCESS

extracts to
...
uint8_t f(Lib_Buffer_buftype t, void *b)
...
exit_code main()
{
  uint8_t b[2U] = { 0U };
  uint8_t y = f(Lib_Buffer_MUT, (void *)b);
  return EXIT_SUCCESS;
}

Ideally we would like the tags to be erased and enable things like this commit I had to revert:
https://github.com/project-everest/hacl-star/commit/7b3be54b0aaabeba06dda3d4f2fbf5a5622bc7ca

I don't understand the need for the modifies_includes and modifies_trans} in Lib.Buffer. They don't have a pattern and they don't seem to be used anywhere. They are also directly provable from lemmas in LowStar.

Why are modifies{1,2,3} restricted to lbuffer. They could be generalized to buffer.

Thanks Benjamin. My criteria for inserting/removing unfolds is that it's generally bad to unfold a term defined as a match and is generally good to unfold mere abbreviations as long as they aren't used in SMT patterns.

Looks good to me. I am seeing quite a bit of fragility in "unfold"s so would love to have a formula like yours and see if it works for most of our use cases.


Status items type documents : thumb_background_deviation

Hi,
could you please provide documentation for statuses items types? currently it's undocumented string which is hard to predict, as I've currently faced previously unknown type: thumb_background_deviation.
What is it's meaning and difference from "deviation" type?
Are there any other? Currently I know of 3:

deviation
status
thumb_background_deviation

This seems to be used for adding previews to thumbnails of a status, I think you can probably safely skip those.


Bug Fix for fail to load certificate location for KafkaTrigger

The SslCertificateLocation, SslKeyLocation and SslCaLocation attributes require the absolute path of certificate and keys respectively.  This PR makes sure that the path is absolute and fixes https://github.com/Azure/azure-functions-kafka-extension/issues/321

@krishna-kariya please resubmit this PR for review post adding the unit test case

@jainharsh98, @shrohilla have added the unit tests. Please have a look.

@krishna-kariya thanks alot for your contribution for the Kafka extension but for the test case it seems you tested esp for the private method, can we try this with the public method route and validate the data


Broken link

In this section (https://docs.microsoft.com/en-us/azure/security-center/security-center-readiness-roadmap#planning-and-operations) the video link (https://mva.microsoft.com/training-courses/hybrid-cloud-workload-protection-with-azure-security-center-18173?l=X4WqTA3jE_1106218965) still points to MVA. The page redirects to the new learning site on docs.com but doesn't go to the specific training video.

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

ID: 3f0774ca-4599-4d26-917d-6d9e5fabe5af
Version Independent ID: 64db3ee5-559b-d277-acab-3f41bdee5302
Content: Azure Security Center Readiness Roadmap
Content Source: articles/security-center/security-center-readiness-roadmap.md
Service: security-center
GitHub Login: @memildin
Microsoft Alias: yurid

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

Updated the page. Changes will go live in the next 12 hours.
Thanks for letting us know!
#please-close


Issues launchin Playnite 4k on 1440p screen

I've tried to start Playnite (in 4k) on my 1440p HDR display using Moonlight Launcher. However, when I try to do so it constantly tries to switch between 1440p resolution and 4k. As is evident by this log file:
moonlight_hdr_launcher_log.txt
These are the settings used:
gamestream_playnite.ini.txt
moonlight_hdr_launcher.ini.txt
.txt at the end is because Github does not support .ini
Is this because of some intended behaviour or just a bug?

I think this is an issue with gamestream launcher. You should try and reproduce it without MHL and file an issue there.

I think this should be closed.
Gamestream launchpad uses standard windows apis to change the resolution of the desktop and assumes that you set a resolution that works. It also sits in the background to verify the resolution doesn't get changed and then changes back to it or at least tries every 2 seconds. This is intended to clean up after games that modify the resolution and don't change it back when you return to a launcher like PlayNite or steam.  I'm actually curious if there is any flicker or anything when you say it switches back and forth between 4k and 1440p. 4k actually is a supported resolution for gamestream so you shouldn't have to use gamestream launchpad or any other tool to force it and I believe it should just work. Gamestream is doing special magic driver stuff after all, it just refuses to do that to enable hdr if your monitor isn't hdr.
As to what's happening for you my best guess is that gamestream is setting the 4k resolution you ask for then gamestream is trying to set 4k but failing and maybe falling back to 1440p then it checks to see what resolution it is and sees it isn't 4k and then tries again and again and again every 2 seconds. Personally I prefer the higher refresh rates at 1440p to 4k resolution that actually takes some work to get done seamlessly as gamestream supports 1080p and 4k but not 1440p and so that's when you need an intermediary like gamestream launchpad (or if my latest pull request is accepted moonlight_hdr_launchpad with some new ini options,) to make things work seamlessly.


[stable/rabbitmq] Fix healthchecks for non-bitnami images

What this PR does / why we need it:

The healthcheck scripts are no longer written to a file during startup. They are instead mounted from a configmap with appropriate permissions. This should make it easier to maintain the chart in the future.
The healthcheck scripts are mounted to /usr/local/sbin/ instead of /opt/bitnami/rabbitmq/sbin/. This is to accomodate images that don't have /opt/bitnami/rabbitmq/sbin/ on their path.
Instead of creating and removing a .start file, when the healthcheck is first run, it is created after the healthcheck has been run. The if statement has been negated.

Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @prydonius

Just figured out why the startup check was the way it was. Did not notice that the .start file was located in the persisted path. Will revert that commit

Hi @PaulFarver,
Thanks for the PR! It seems there are some conflicts in the stable/rabbitmq/Chart.yaml file.
Can you resolve them?

Hi @PaulFarver,
Thanks for the PR! It seems there are some conflicts in the stable/rabbitmq/Chart.yaml file.
Can you resolve them?

Of course!
Corrected in e263561

/test pull-charts-e2e

@tompizmor could you review this again? The conflict should be resolved

It seems like this pull request is stuck in approved but not ok-to-merge. Is there anything I can do to help the process, so we can get this merged? @prydonius

/unassign @prydonius
/assign @tompizmor

The lgtm label was removed after I resolved the conflict in Chart.yml. Could you take a look at it again @tompizmor ?

@tompizmor it seems we lost the track of this PR. Could you please re-review it when you have a chance?

HI @PaulFarver,
I am sorry for the late response. As juanariza says, we lost track of this PR in our internal system and we didn't realize until the stale bot added a new comment. Do you mind taking another look to the conflicts?

Hi @PaulFarver
The CI tests are failing:
I1007 08:35:55.899] Old chart version: 6.8.2
I1007 08:35:55.900] New chart version: 6.8.2
I1007 08:35:55.901] Error linting and installing charts: Error processing charts
I1007 08:35:55.901] ------------------------------------------------------------------------------------------------------------------------
I1007 08:35:55.902]  âœ–ï¸Ž rabbitmq => (version: "6.8.2", path: "stable/rabbitmq") > Chart version not ok. Needs a version bump!

It seems you need to bump the version in the Chart.yaml

Hey @juan131
I've bumped the version again. This chart is developing pretty fast ;)

/lgtm

Thanks @juan131 and @PaulFarver!


Support mention for slack notification

What this PR does / why we need it:
I add a new field named mentionedAccounts to support slack api can mention to specify accounts.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

How are users affected by this change:
Is this breaking change:
How to migrate (if breaking change):

@kentakozuka
I fixed it 🐱

@kentakozuka
Sorry, I fixed piped configuration and test.

Thanks @sivchari. Could you rebase your branch with the latest master to resolve codegen issue 🙏


fix: Multiple file uploads in Livewire v2.8

Closes #778.
In progress while I work out a fix for livewire/livewire#4239 that doesn't involve tearing it all apart 😳

All fixed!


Stopped working

Usage with typescript-generic-sdk throws the following typescript error when calling getSdk(createUrqlRequester(client)):
Argument of type '<Context, Result, Variables extends Record<string, unknown>>(document: DocumentNode, parameters?: Variables | undefined, context?: Context | undefined) => Promise<Result>' is not assignable to parameter of type 'Requester<unknown, unknown>'.
  Types of parameters 'parameters' and 'vars' are incompatible.
    Type 'V | undefined' is not assignable to type 'Record<string, unknown> | undefined'.
      Type 'V' is not assignable to type 'Record<string, unknown> | undefined'.ts(2345)
linear.generated.ts(10607, 50): This type parameter might need an `extends Record<string, unknown> | undefined` constraint.

Versions:
"urql": "^2.2.3",
"urql-generic-requester": "^0.0.2"
"@graphql-codegen/cli": "^5.0.0",
"@graphql-codegen/typescript": "^2.8.8",
"@graphql-codegen/typescript-generic-sdk": "^2.5.1",
"graphql": "^16.8.0",
"graphql-codegen-typescript-common": "0.18.2",
"typescript": "^5.1.6",

codegen.ts:
import type { CodegenConfig } from '@graphql-codegen/cli'

const config: CodegenConfig = {
  overwrite: true,
  schema: 'https://api.linear.app/graphql',
  generates: {
    './src/types/linear.generated.ts': {
      plugins: [
        'typescript',
        'typescript-operations',
        'typescript-generic-sdk',
      ],
    },
  },
  documents: ['src/operations/linear.graphql'],
  // ignoreNoDocuments: true,
}

export default config

Could you confirm if it's working with the following version?
npm i<EMAIL_ADDRESS>

Could you confirm if it's working with the following version?
npm i<EMAIL_ADDRESS>

Seems to install correctly, but I can't test it as the import fails:
Cannot find module 'urql-generic-requester' or its corresponding type declarations.
It is listed in my dependencies in package.json:

yeah the typedefs didn't get generated in the last publish, it should now work, just change the version to 0.1.0-beta.1 instead

yep, that worked! thanks for the quick fix

Glad that worked,
You can now move it up to 0.1.0 safely 😄


brew is not "${HOME}/.gitconfig" agnostic

brew config output
HOMEBREW_VERSION: 3.6.0
ORIGIN: https://github.com/Homebrew/brew
HEAD: 93ea8cb2c40e1ef25f1489b0267526bd47bc8030
Last commit: 25 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: e7fc95fc1c7171723c38ba33af6f468f1e78543a
Core tap last commit: 2 hours ago
Core tap branch: master
HOMEBREW_PREFIX: /home/linuxbrew/.linuxbrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: :0
HOMEBREW_MAKE_JOBS: 6
Homebrew Ruby: 2.6.8 => /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.8_1/bin/ruby
CPU: hexa-core 64-bit skylake
Clang: N/A
Git: 2.34.1 => /bin/git
Curl: 7.81.0 => /bin/curl
Kernel: Linux 5.15.0-47-generic x86_64 GNU/Linux
OS: Ubuntu 22.04.1 LTS (jammy)
Host glibc: 2.35
/usr/bin/gcc: 11.2.0
/usr/bin/ruby: 3.0.2
glibc: N/A
gcc@11: N/A
xorg: N/A

brew doctor output
Your system is ready to brew.

Verification

[X] I ran brew update and am still able to reproduce my issue.
[X] I have resolved all warnings from brew doctor and that did not fix my problem.

What were you trying to do (and why)?
I'm trying to setup a auto-upgrade script for homebrew in '/etc/cron.daily', that run brew update and brew upgrade as the user having installed brew.
What happened (include all command output)?
The upgrade script run as root, and using setpriv to run brew command as installing user return:
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Error: Fetching /home/linuxbrew/.linuxbrew/Homebrew failed!

The issue is that the user ${HOME}/.gitconfig file contains:
[url "git@github.com:"]
        insteadOf = https://github.com/

and that break brew update when the ssh-agent containing the private key used to log in to github is not available.
What did you expect to happen?
brew should have ignored "${HOME}/.gitconfig" and run without issue or their should be another way to cleanly run brew update.
Step-by-step reproduction instructions (by running brew commands)
The user account which installed homebrew has this ``${HOME}/.gitconfig` file:
[user]
        name = Firstname Lastname
        email =<EMAIL_ADDRESS>[url "git@github.com:"]
        insteadOf = https://github.com/
        insteadOf = https://github.com/

And this ${HOME}/.ssh/config
# github.com
Host github.com
  PreferredAuthentications publickey
  IdentityFile ~/.ssh/id_ed25519

The "${HOME}/.ssh/id_ed25519" private key is password protected and added to the user ssh-agent.
The upgrade script (named /etc/cron.daily/update-homebrew) is:
#!/bin/bash
# /etc/cron.daily/update-homebrew
# Homebrew auto-updater script.
# Author: Pierre-Yves Landuré <contact at biapy dot fr>
#
# Run 'brew update' and 'brew upgrade' as the
# user owning the  binary.

brew="/home/linuxbrew/.linuxbrew/bin/brew"

# Check if Brew is present on the system.
if ! type "${brew}" &>"/dev/null"; then
  echo "Error: unable to find 'brew' binary."

Set it as executable, and run it using sudo should reproduce the issue.

The .gitconfig automatically replace https://github.com/ by<EMAIL_ADDRESS>when git is used to access https://github.com/ URLs. This is a setup that I need for some issues, and should not be impacting brew.
First, open a root shell:
sudo --login

In the root shell, try to run brew update as the user having installed brew:
sudo --user=username --login brew update

The full output is:
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Error: Fetching /home/linuxbrew/.linuxbrew/Homebrew failed!
Fetching /home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-core failed!

The issue is that any .gitconfig in the $HOME of the user is took into account. You can call git so that it ignore global config values to be really config agnostic.

You can call git so that it ignore global config values to be really config agnostic.

This is possible, but this also breaks other things.


[todo] fix list args on Windows

making pull-request from TODO item
Patch to fix escaping of job arguments. (Yasuhiro Matsumoto, 2016 Oct 5)
Update Oct 14: https://gist.github.com/mattn/d47e7d3bfe5ade4be86062b565a4bfca

I'll add list args for term_start.

Codecov Report

Merging #1954 into master will decrease coverage by 0.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #1954      +/-   ##
==========================================
- Coverage   74.72%   74.71%   -0.02%
==========================================
  Files          77       77
  Lines      125686   125727      +41
  Branches    28123    28134      +11
==========================================
+ Hits        93924    93939      +15
- Misses      31762    31784      +22
- Partials        0        4       +4

Impacted Files
Coverage Δ

src/channel.c
82.32% <0%> (-1.66%)
:arrow_down:

src/if_xcmdsrv.c
84.44% <0%> (-2.04%)
:arrow_down:

src/os_unix.c
52.4% <0%> (-0.34%)
:arrow_down:

src/if_py_both.h
76.05% <0%> (-0.14%)
:arrow_down:

src/evalfunc.c
82.58% <0%> (-0.02%)
:arrow_down:

src/libvterm/src/screen.c
73.34% <0%> (+0.02%)
:arrow_up:

src/term.c
52.93% <0%> (+0.17%)
:arrow_up:

src/message.c
68.34% <0%> (+0.25%)
:arrow_up:

src/window.c
81.36% <0%> (+0.49%)
:arrow_up:

... and 1 more

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 8ab3c1d...c6fb01b. Read the comment docs.


Fix/package lock

What does this PR does?
Fixes package-lock.json dependencies in order to match dependencies in package.json

Using npm version >= 7 does not modify package-lock.json and install dependencies correctly, either using npm ci or npm  i


Lab 01L01, DC VM name not set during creation

Module: 1
Lab/Demo: 01L01, Prepare for deployment of Azure Virtual Desktop (AD DS)
Exercise: 2, Task: 1
Step: 1
VM name az140-dc-vm11 does not exist. The default DC VM name is: adVM.
The DC creation instruction should include the setting for VM name to overwrite the default

Hi Ning
It appears that you are not using the parameters file - as instructed. Pls make sure to follow the instructions:
On the Edit parameters blade, select Load file, in the Open dialog box, select \AZ-140\AllFiles\Labs\01\az140-11_azuredeploydc11.parameters.json, select Open, and then select Save.
rgds
Marcin


Task for coverage report should respond with total coverage info

Feature request:
Currently when the 'test' task is executed, a nice html report is generated similar to junit type test reports. In addition, the task also prints to stdout a summary. For example:
"10 test completed, 0 failed"
When the 'cover' task is executed, it also generates an html report about code coverage. However, there's no feedback on the stdout. One must open the generated html report to see the coverage info. Similar to 'test' task, it'd be nice to have an immidiate feedback on the terminal about summary/total percentage of the code covered. For example:
"Total test coverage 83%"
This is useful info when running the task that generates detailed coverage report. It can also be useful by CI/CD. For example, Gitlab CI can parse the log and capture the coverage info, which then can be displayed in a pull/merge request. Gitlab CI can also generate a coverage badge that can be included in project's readme.
https://docs.gitlab.com/ee/user/project/pipelines/settings.html#test-coverage-report-badge
https://docs.gitlab.com/ee/user/project/pipelines/settings.html#test-coverage-parsing

Closed by 0.9. Thanks for reporting!


Added: Dolphin sample [WIP]

Added the dolphin sample, still work in progress.

This PR is connected to: https://github.com/h4570/tyra/issues/12


Quickstart and Troubleshooting Docs

These were made using my own notes, going to keep slowly building documentation as I go through FDI if that's cool. :)

Oww worth noting this PR is kind of held up by: https://github.com/application-research/estuary-postgres-playbook/pull/2
As it's only relevant to that branch.


Blog Submission related to pets, pets owners etc (🎉Special prize for the best blog🎉)

Blog Submission Guidelines
We invite you to submit original, self-written blogs specifically related to Pets, Pets Owner etc. for our website https://akshitagupta15june.github.io/PetMe/blog.html.
Here’s how to participate:

Original Content: No plagiarism or AI-generated content. All blogs will be checked for originality.
One Blog per Person: Only one submission per person.
Formats: Submit your blog either as a Google Doc or a static HTML web page (HTML, CSS, JS) hosted on GitHub.
Submission: Use this link https://forms.gle/KiWNcAMAedtERfsNA to submit your blog.
Review Process: Our team will review all submissions. Accepted blogs will be published, and the best blog will win a prize.
Publication: All accepted authors will receive an email to create a pull request for adding their blog to our website.

Submission Instructions

Google Docs: Ensure sharing settings are "Anyone with the link can view" and submit the link in the form.
Static HTML Web Page: Design your blog and submit the GitHub hosted webpage or GitHub link.

Evaluation

Originality: Unique and original content.
Quality: Well-written and engaging.
Relevance: Relevant and interesting topics.
Design: For HTML submissions, a clean and user-friendly design.

Submit your blogs and share your insights! For questions, comment below.
Happy blogging!🎉
No need of assigning in this issue. Anyone can work on it.

@akshitagupta15june please assign the issue.

@akshitagupta15june please assign me the issue

@akshitagupta15june please assign me the issue under GSSOC'24.


openra-release: 20190314 - 20210321

Motivation for this change
New release was made.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I made an attempt at this before (see #96600) and it seemed like it should be a lot more work.
In this case it looks like the hash wasn't updated, so I would expect this to be just pulled from the cache and actually still be the old version.

I'm sorry. I missed the hash.
There seems to be something missing in the source repo...


Provide Ott Read Only DB access to prod replica

He needs to pull some data using Azure studio. This should be documented so other folks can use it.

Pending document

Find The steps on how to access Prod db and run queries from local env here


docs: Fixed the missing import in the chat/integrations example.

Fixed the missing import in the chat/integrations example.

AIMessage is used in these examples, but it is not imported in the documentation.
ref:

https://python.langchain.com/en/latest/modules/models/chat/integrations/azure_chat_openai.html
https://python.langchain.com/en/latest/modules/models/chat/integrations/google_vertex_ai_palm.html

Before submitting

Who can review?
Community members can review the PR once tests pass. Tag maintainers/contributors who might be interested:

@hwchase17
@agola11

thanks @tao12345666333!

@tao12345666333 thanks for the change -- importing AIMessage isn't necessary since a return type of a function. it'll automatically be loaded into context by the running code


Segmentation fault (11)

Hey I am back, so i moved the program over to a google colab. Ran this command:
!python main.py --runner sample --method F-PNDM --sample_speed 50 --device cuda --config ddim_cifar10.yml --image_path results --model_path models/ddim_cifar10.ckpt
Everything was going fine and then ->

any advice?

Maybe your system is running out of memory when trying to execute your code, which results in a segmentation fault.
I think you can change the batch_size smaller in ddim_cifar10.yml. Hope this is helpful.

Maybe your system is running out of memory when trying to execute your code, which results in a segmentation fault.
I think you can change the batch_size smaller in ddim_cifar10.yml. Hope this is helpful.


installed version 19.20-beta2, latest stable 19.19

When i was running version 19.19 i could read this in the check for updates:
In order to make this option work, git command has to be installed on your system (installed version 19.19, latest beta 19.20-beta2)

Now when i have updated to 19.20 beta 2 i can read this:
In order to make this option work, git command has to be installed on your system (installed version 19.20-beta2, latest stable 19.19)

What will happen when you release a new beta?

It will give you even more beautiful response:
(installed version 19.20-beta2, latest stable 19.19, latest beta 19.20-beta3)

:smile:


Occasional hang when closing a audio device.

To reproduce, play an ogg file with ogg123 while having the vumeter enabled. Press ctrl-c to stop playing. About 50% of the time this result in ogg123 hanging. The VU meter remains lit when this happens.

you are controlling a set of APA102 by passing data and clock continuously... if you interrupt playback arbitrarily then yes, they may remain in their state. I don't think there is any workaround but we'll try a few things.

Backtrace on the hung process:
(gdb) bt
#0  0xb6cb8b80 in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0xb635d428 in poll (__timeout=-1, __nfds=1, __fds=0xbea37530)
at /usr/include/arm-linux-gnueabihf/bits/poll2.h:46
#2  snd1_pcm_wait_nocheck (pcm=pcm@entry=0xb590fe68, timeout=timeout@entry=-1) at pcm.c:2418
#3  0xb63971d8 in snd_pcm_dmix_drain (pcm=0xb590fe68) at pcm_dmix.c:649
#4  0xb63f44a4 in ao_plugin_close () from /usr/lib/ao/plugins-4/libalsa.so
#5  0xb6ed7d14 in ao_close () from /usr/lib/libao.so.4
Cannot access memory at address 0x40240000
#6  0x00013290 in ?? ()
Cannot access memory at address 0x40240000
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)

The hang happens even if libpivumeter is not installed.

The same hang occurs with sox:
(gdb) bt
#0  0xb6ddcb80 in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0xb6bac428 in poll (__timeout=-1, __nfds=1, __fds=0xbe88c4e8)
at /usr/include/arm-linux-gnueabihf/bits/poll2.h:46
#2  snd1_pcm_wait_nocheck (pcm=pcm@entry=0xeff2b0, timeout=timeout@entry=-1) at pcm.c:2418
#3  0xb6be61d8 in snd_pcm_dmix_drain (pcm=0xeff2b0) at pcm_dmix.c:649
#4  0xb6c4092c in ?? () from /usr/lib/arm-linux-gnueabihf/sox/libsox_fmt_alsa.so

This appears to be a bug in the alsa meter PCM slave. I can't reproduce the hang after removing it from asound.conf.

I have reported this upstream: http://mailman.alsa-project.org/pipermail/alsa-devel/2017-March/118459.html

I'll close this as this seems not to be related to pivumeter.


Fix licensing config/review screen on small displays

Add scrollbar to License configuring/reviewing screens. This fixes visibility of back/next buttons on mobile chrome (or very tiny android screens?)

Merging in order to get the deployed branch


Error on port 443

What happened:As SC4k8S was configured following the documentation provided it is showing this message error
Failed to flush the buffer. retry_times=0 next_retry_time=2022-06-08 18:33:16 +0000 chunk="5e0f3ee14338933cc5520f7cef8a03c2" error_class=SocketError error="Failed to open TCP connection to https:443 (getaddrinfo: Name or service not known)"
What you expected to happen:Data flowing succesfuly
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version):
Ruby version (use ruby --version):
OS (e.g: cat /etc/os-release):
Splunk version: 8.2.x
Splunk Connect for Kubernetes helm chart version:
Others:

What are you sending in your values file? Specifically in the "splunk" stanza. From the looks of it, you need a hec.host? And is your HEC server set to listen on 443? The default is 8088.
splunk:
  hec:
    host: <FQDN of HEC Server>
    port: 8088 ## Or other HEC port
    protocol: https
    token: <HEC Token>
    indexName: main # Default index
    insecureSSL: yes
    clientCert:
    clientKey:
    caFile:
  ingest_api:
    serviceClientIdentifier:
    serviceClientSecretKey:
    tokenEndpoint:
    ingestAuthHost:
    ingestAPIHost:
    tenant:
    eventsEndpoint:
    debugIngestAPI:

@darismendyesp, can you please share the values.yaml file and full logs of pods. Also, which Kubernetes distro are you using?

Closing the issue since it is inactive for a long time. Feel free to reopen this issue or create new one.


ie8 error: The object doesn't accept property or method

Error in ie8: Object doesn't accept this property in autocomplete.init.js line 43
function initialize(element) {
        if (typeof element === 'undefined' || typeof element === 'number') {
            element = this;
        }
        // This is line 43:
        if (window.__dal__initListenerIsSet !== true || initialized.indexOf(element) >= 0) {
            return;
        }

        $(element).trigger('autocompleteLightInitialize');
        initialized.push(element);
    }
    window.__dal__initialize = initialize;

We are loading jquery 1.10.2 at the top of page.
Everything works ok in firefox and chrome.
Edit: django-autocomplete-light==3.2.10, ie8==8.0.7601

Ok, looking forward to review a pull request


Inconsistencies in PublicIPAddress in Network.json

Hi there,
This spec references an object for PublicIPAddress:
https://github.com/Azure/azure-rest-api-specs/blob/master/arm-network/2016-06-01/swagger/network.json#L6959
However there are two places in the spec where the object is not referenced:
https://github.com/Azure/azure-rest-api-specs/blob/master/arm-network/2016-06-01/swagger/network.json#L4491
And:
https://github.com/Azure/azure-rest-api-specs/blob/master/arm-network/2016-06-01/swagger/network.json#L7552
Every other mention of this field in the spec has the correct reference:
https://github.com/Azure/azure-rest-api-specs/blob/master/arm-network/2016-06-01/swagger/network.json#L7552
Is this intentional? This is currently causing some deserialization errors in the Python SDK.
https://github.com/Azure/azure-sdk-for-python/issues/786
If this is in fact the intended behaviour we will need to make modifications to the Python generator to accommodate it.
The Python SDK is currently generated from the 2016-06-01 spec, but this issue also seems to appear if the 2016-09-01 spec.
Thanks,
Anna

@amarzavery - do you know who the best person would be to contact regarding this issue in the network spec?

So the spec is correct. The issue described above is not an issue in C# or node.js sdk.
The PublicIpAddress is a sub resource a.k.a reference to the publicIP. The user can get more information about it by doing a GET on the id provided for public IP.
If the entire object is provided over there then the encompassing object (VirtualNetworkGatewayIPConfiguration) becomes lengthy.
Usually the GET operation for the resource type that one is creating has a $expand query parameter. If you provide the values that you want to expand on, (Public IP in this case) then the service should provide you the complete object rather than the reference.

Thanks @amarzavery - I'll take another look!

@DeepakRajendranMsft to close this issue

Hi @liumichelle,
Can you please add more description on why this is  to be resolved?

@salameer can this issue be closed out?

@salameer - can this issue be closed out I believe @amarzavery answered the question.

Closing


Update version to 1.1.18-6 on staging

Update version to 1.1.18-6

🚀 Deployed to staging by @OSBotify in version: 1.1.18-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by @Julesssss in version: 1.1.21-1 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Project fails to load in a browser with a cryptic error in 11.2

Describe the bug
After an upgrade to Avalonia 11.2, my wasm project stopped working, I can only see this in the console:
  | Ll | @ | invoke-js.ts:116
-- | -- | -- | --
  | Promise.then |   |
  | mo | @ | marshal-to-cs.ts:329
  | (anonymous) | @ | marshal-to-cs.ts:83
  | (anonymous) | @ | invoke-js.ts:202
  | Ll | @ | invoke-js.ts:276
  | $do_icall | @ | dotnet.native.wasm:0x63110d
  | $do_icall_wrapper | @ | dotnet.native.wasm:0x62c052
  | $mono_interp_exec_method | @ | dotnet.native.wasm:0x61df64
  | $interp_runtime_invoke | @ | dotnet.native.wasm:0x62d967
  | $mono_jit_runtime_invoke | @ | dotnet.native.wasm:0x742bcb
  | $do_runtime_invoke | @ | dotnet.native.wasm:0x70342b
  | $mono_runtime_invoke_checked | @ | dotnet.native.wasm:0x7033c5
  | $mono_runtime_try_invoke_byrefs | @ | dotnet.native.wasm:0x709ade
  | $ves_icall_InternalInvoke | @ | dotnet.native.wasm:0x6ced5f
  | $ves_icall_InternalInvoke_raw | @ | dotnet.native.wasm:0x6d7bd6
  | $do_icall | @ | dotnet.native.wasm:0x6311c6
  | $do_icall_wrapper | @ | dotnet.native.wasm:0x62c052
  | $mono_interp_exec_method | @ | dotnet.native.wasm:0x61df64
  | $interp_runtime_invoke | @ | dotnet.native.wasm:0x62d967
  | $mono_jit_runtime_invoke | @ | dotnet.native.wasm:0x742bcb
  | $do_runtime_invoke | @ | dotnet.native.wasm:0x70342b
  | $mono_runtime_try_invoke | @ | dotnet.native.wasm:0x703eab
  | $mono_runtime_invoke | @ | dotnet.native.wasm:0x706a28
  | $mono_wasm_invoke_method_bound | @ | dotnet.native.wasm:0x8d871a
  | (anonymous) | @ | dotnet.native.8.0.10.zsxk4nykel.js:936
  | ccall | @ | dotnet.native.8.0.10.zsxk4nykel.js:8977
  | (anonymous) | @ | dotnet.native.8.0.10.zsxk4nykel.js:8996
  | kr | @ | invoke-cs.ts:273
  | l.javaScriptExports.call_entry_point | @ | managed-exports.ts:60
  | Fc | @ | run.ts:44
  | (anonymous) | @ | main.js:13

To Reproduce

Clone https://github.com/BAndysc/Classic.Avalonia

cd samples/AvaloniaVisualBasic.Browser
dotnet run

See it fails to load.

You can also change versions to 11.1 in Directory.Build.props to see the same solution worked fine before:
<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <PropertyGroup>
        <AvaloniaVersion>11.1.4</AvaloniaVersion>
        <ClassicAvaloniaVersion><IP_ADDRESS></ClassicAvaloniaVersion>
        <DockVersion><IP_ADDRESS></DockVersion>
    </PropertyGroup>
</Project>

(also open TimePicker.axaml and remove line 279)
Expected behavior
No response
Avalonia version
11.2
OS
WebAssembly
Additional context
No response

@BAndysc Classic.Avalonia works for me here on https://github.com/BAndysc/Classic.Avalonia/commit/afd034b4dd45130e4cf2b5e4b01759015ee0621e commit:

Can you try to update your .NET SDK to latest stable builds? Update workloads. If you use .NET 9 SDK, you also need to install wasm-tools-net8 (or change target framework to net9, while still installing wasm-tools workload). Resetting browser cache might also work.

Thanks for the response, wow, so in the end I was able to run it.

.NET 8.0.403 (latest as of now) + <TargetFramework>net8.0</TargetFramework>
Upgrading to the latest .NET 8 didn't change anything, same error with Avalonia 11.2, no error with Avalonia 11.1.4

.NET 9.0.100-rc.2.24474.11 (latest as of now) + <TargetFramework>net8.0</TargetFramework> + workload wasm-tools-net8
The same as above.

.NET 9.0.100-rc.2.24474.11 (latest as of now) + <TargetFramework>net9.0</TargetFramework>
I had to apply this workaround, due to a bug in .NET 9, with it Avalonia 11.2 works, but Avalonia 11.1.4 stopped working with error:

marshal-to-js.ts:420 Uncaught ManagedError: One or more errors occurred. (Error: AvaloniaDOM.getGlobalThis must be a Function but was undefined
    at http://localhost:5235/_framework/dotnet.runtime.ju77aherdp.js:3:170312
    at http://localhost:5235/_framework/dotnet.runtime.ju77aherdp.js:3:170386
    at Fc (http://localhost:5235/_framework/dotnet.runtime.ju77aherdp.js:3:171742)
    at dotnet.native.wasm.do_icall (http://localhost:5235/_framework/dotnet.native.m2ecb8aszw.wasm:wasm-function[2074]:0x12b9cb)
    at dotnet.native.wasm.do_icall_wrapper (http://localhost:5235/_framework/dotnet.native.m2ecb8aszw.wasm:wasm-function[1993]:0x127e4d)
    at dotnet.native.wasm.mono_interp_exec_method (http://localhost:5235/_framework/dotnet.native.m2ecb8aszw.wasm:wasm-function[1984]:0x1191ea)
    at dotnet.native.wasm.interp_entry (http://localhost:5235/_framework/dotnet.native.m2ecb8aszw.wasm:wasm-function[2063]:0x12b014)
    at dotnet.native.wasm.interp_entry_static_0 (http://localhost:5235/_framework/dotnet.native.m2ecb8aszw.wasm:wasm-function[2107]:0x12cf1e)
    at dotnet.native.wasm.wasm_native_to_interp_System_Threading_System_Private_CoreLib_ThreadPool_BackgroundJobHandler (http://localhost:5235/_framework/dotnet.native.m2ecb8aszw.wasm:wasm-function[31277]:0x8e6eb2)
    at dotnet.native.wasm.mono_background_exec (http://localhost:5235/_framework/dotnet.native.m2ecb8aszw.wasm:wasm-function[3056]:0x16149d))
    at http://localhost:5235/_framework/dotnet.runtime.ju77aherdp.js:3:170312
    at http://localhost:5235/_framework/dotnet.runtime.ju77aherdp.js:3:170386
    at Fc (http://localhost:5235/_framework/dotnet.runtime.ju77aherdp.js:3:171742)
    at dotnet.native.wasm.do_icall (http://localhost:5235/_framework/dotnet.native.m2ecb8aszw.wasm:wasm-function[2074]:0x12b9cb)
    at dotnet.native.wasm.do_icall_wrapper (http://localhost:5235/_framework/dotnet.native.m2ecb8aszw.wasm:wasm-function[1993]:0x127e4d)
    at dotnet.native.wasm.mono_interp_exec_method (http://localhost:5235/_framework/dotnet.native.m2ecb8aszw.wasm:wasm-function[1984]:0x1191ea)
    at dotnet.native.wasm.interp_entry (http://localhost:5235/_framework/dotnet.native.m2ecb8aszw.wasm:wasm-function[2063]:0x12b014)
    at dotnet.native.wasm.interp_entry_static_0 (http://localhost:5235/_framework/dotnet.native.m2ecb8aszw.wasm:wasm-function[2107]:0x12cf1e)
    at dotnet.native.wasm.wasm_native_to_interp_System_Threading_System_Private_CoreLib_ThreadPool_BackgroundJobHandler (http://localhost:5235/_framework/dotnet.native.m2ecb8aszw.wasm:wasm-function[31277]:0x8e6eb2)
    at dotnet.native.wasm.mono_background_exec (http://localhost:5235/_framework/dotnet.native.m2ecb8aszw.wasm:wasm-function[3056]:0x16149d))
    at sn (http://localhost:5235/_framework/dotnet.runtime.ju77aherdp.js:3:26907)
    at Kt.resolve_or_reject (http://localhost:5235/_framework/dotnet.runtime.ju77aherdp.js:3:26462)
    at http://localhost:5235/_framework/dotnet.runtime.ju77aherdp.js:3:172539
    at http://localhost:5235/_framework/dotnet.runtime.ju77aherdp.js:3:172603
    at fr (http://localhost:5235/_framework/dotnet.runtime.ju77aherdp.js:3:35059)
    at Fc (http://localhost:5235/_framework/dotnet.runtime.ju77aherdp.js:3:172186)
    at dotnet.native.wasm.do_icall (http://localhost:5235/_framework/dotnet.native.m2ecb8aszw.wasm:wasm-function[2074]:0x12b9b8)
    at dotnet.native.wasm.do_icall_wrapper (http://localhost:5235/_framework/dotnet.native.m2ecb8aszw.wasm:wasm-function[1993]:0x127e4d)
    at dotnet.native.wasm.mono_interp_exec_method (http://localhost:5235/_framework/dotnet.native.m2ecb8aszw.wasm:wasm-function[1984]:0x1191ea)
    at dotnet.native.wasm.interp_entry (http://localhost:5235/_framework/dotnet.native.m2ecb8aszw.wasm:wasm-function[2063]:0x12b014)

So the latest Avalonia + latest .NET 9 combo seem to work. Is it what you used? I am not sure if Avalonia 11.2 + .NET 8 are worth further investigation.

@BAndysc no, I was able to run .NET 8 project with no changes, on .NET 9 SDK (with correct workloads).


yalc publish throws an error

I realize that this is still in development, but I'm excited about the possibility of this tool greatly improving my team's workflow. Ran into this error when giving it a spin, though.
~/dependency ᐅ yalc publish
/bin/sh: yarn.lock: command not found
(node:67368) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Command failed: yarn.lock
/bin/sh: yarn.lock: command not found

Looks like the error could be on this line? https://github.com/whitecolor/yalc/blob/master/src/index.ts#L93
And if that's it, https://nodejs.org/api/fs.html#fs_fs_existssync_path might be helpful.
yalc version 1.0.0-pre.5
yarn version 0.23.2
node version 6.9.4
os x version 10.11.6

Hi, glad that it may help, thanks for the report it was, should be fixed in the latest released!


Issue when using a text expansion tool such as alfred

When using a text expansion tool such as Alfred advanced paste inserts the following
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px 'Helvetica Neue'; color: #000000; color: rgba(0, 0, 0, 0.85)}
Just to clarify text expansion
Typing something like omw would expand to On my way!
This goes away as soon as I switch off advanced paste and restart Obsidian
Thanks

I don't know what happened in this case and I don't have a Mac to reproduce this issue.
But after Obsidian v1.3 is released, the default pasting experience of advpaste and obsidian's builtin has become quite similar.
If Enhanced Ctrl+V is causing issues for you, you can try to disable Enhanced Ctrl+V and restart obsidian so that you can still use other features provided by this plugin.


Replace buf and connect with connectrpc.com

This should be the changes required for publishing to com.connectrpc
Make a release with: https://github.com/bufbuild/connect-kotlin/pull/68 to appropriately finish the relocation.

superseded by https://github.com/bufbuild/connect-kotlin/pull/79