Test deployment of PASS in EC2 to validate startup procedures outside of JHU

Launch the PASS application in AWS in as simple a manner as possible. This will very likely be tied to JHU data/integration points initially. As those integration points are replaced with mocks/stubs this environment will be an initial testing ground for deploying those changes to ensure they work.
As the Eclipse deployment is built, this environment will provide a reference point. If the application in the Eclipse Kubernetes environment is not working, but it is working in this simplified deployment, that will provide a resource for comparison and analysis.
This deployment is not intended to be used for PASS long-term. It is a stepping point to get us from the JHU environment to the Eclipse environment.
Definition of Done

A deployment of the latest version of the PASS application is running in AWS
This deployment can be shut down and brought back up quickly and consistently

Setup an EC2 instance.
Make sure instance locked down, not accessible to public.
Make "public" assets image available
Attempt to deploy PASS using pass-docker
Think about security and test users

Created #217 to record fact that pass-docker currently requires docker-compose version 1.

PASS is up and running on https://sandbox.pass.library.jhu.edu. I was able to login as a test user and successfully deposit to the included DSpace.
I created a branch in pass-docker, https://github.com/eclipse-pass/pass-docker/tree/200-test-deployment-of-pass-in-ec2-to-validate-startup-procedures-outside-of-jhu which I used record how the stack was modified.
I avoided building new images by bind mounting configuration files into the existing images. This was needed for files in httpd-proxy, sp, and idp. See the docker-compose.yml for the changed files. The httpd-proxy had to have certificates overridden because the host was different. The other images just needed changes to environment variables in .env.  A global string replace of pass.local -> sandbox.library.jhu.edu was sufficient.


Fix base_hierarchical_route_installation_test

e9998a03-b0d3-41bb-9763-a56212034668

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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 72.677%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1314

Relevant Lines:
1808

💛  - Coveralls

/gcbrun

This PR is not required and we have a correct expectation in the test. Hence closing it.
For context: https://github.com/openconfig/public/pull/691#discussion_r948156896


Professionalize newflasher and prepare for Debian

For Sony Xperia XA2 devices, newflasher plays an indispensable role in installing LineageOS, because the stock firmware of XA2 has a critical bug: When it is booted in SYSTEM_B, several sub systems like wifi and bluetooth don't work, meaning that after installation, the first OTA update of LineageOS (switching between SYSTEM_A and SYSTEM_B) makes the device unusable. Currently, the only known solutions are to either always install 2 updates in a row (which becomes annoying quickly over time), or to reflash parts of the firmware via newflasher. So if we want LineageOS to be installable long-term on XA2, we need to make newflasher long-term available.
This is why I would like to professionalize newflasher to reach a level of quality that it is acceptable by the Debian project. I plan to volunteer for the role as Debian maintainer for this package, but wouldn't be unhappy if somebody else wants to do that job. ;-) I already contacted the Debian AndroidTools team and they agreed to review and upload a Debian package for newflasher as soon as it meets their standards. They also performed a first quick review on this repository and provided lots of valuable hints about what should be improved. I'll try to fix each of those hints in the following issues and pull requests.
@munjeni Since you wrote in #3 that you are "not active here" anymore, may I propose that you create a new GitHub organization newflasher and transfer this repository over there? That way, you could add some trusted people as admins and establish a maintenance team, where each member could continue this project even if all others gets stuck in daily-life obligations.

Hi, first of all thanks for contributing and for idea about newlasher on Debian distro. To be honest, I am bussy with private life, I spent a lot of time on xda and I simply have no more that free time for that hoby anymore, "I'm not active here" mean I'm not that active like before but that not mean I'm not active, I have some free time for example to accept some pull reguests but I have no free time for testing each, and I have no free time for making new organization, everybody is free to clone newflasher and start working on it on its own git accepting @c from newflasher.c . So if you need GitHub organization called newflasher you can do it.

@munjeni Thanks for accepting the first batch of my pull requests.
I hope you did not get my proposal to create an organization wrong. Since you confirmed that your time is very limited, which is perfectly okay, it is even more important to create an organization now rather than in a year or two. My intent was not to put additional work on you. I just wanted to ensure that you can stay in full control over the whole process if you want. Since you don't, I took the freedom to create the newflasher organization myself, and of course I invited you to become a member with "owner" privileges of it.
There's one thing I can't do for you, though, which is the transfer of this project to the new organization. This is essentially just 3 clicks and 2 textfields for you, see also:

https://help.github.com/en/articles/transferring-a-repository#transferring-a-repository-owned-by-your-organization

Of course I could fork newflasher into the new organization at any time, but a clean transfer would have several advantages:

The organization project would receive an official "blessing" by the original author.
People will not be confused about which one is the "correct" repository, in particular, it will be clear whose issue tracker to use.
GitHub will redirect https://github.com/munjeni/newflasher to https://github.com/newflasher/newflasher, so people coming from e.g. an old link in the XDA forum would be redirected automatically.

Again, thanks for having created this great tool!

@munjeni Thanks a lot for your trust and for moving this repository to the new organisation!

You will need to update readme too?

@munjeni If you refer to PR #17: Yes, I plan to update the README, too. But I believe the current README is still correct after #17, because the README doesn't say anything about what happens when "make" is called without parameters, and all "make" invocations mentioned in the current README still work ("make newflasher.exe", "make newflasher.x64", etc.)

Sorry I see see now. To let you know do not wait me for revision, if you need to merge something just do it but please test it before you merge since whole newflasher is prety harcoded for for so meny diferent Sony devices!

@munjeni Okay, in case I'm running into time pressure, I'll merge pull requests on my own, and/or commit directly. Nevertheless, I value your review very much, even if it's just a superficial plausibility check ... of course, only as long as your time allows for that.

Hi, almost 6 months gone, any progress?

All tickets fixed and closed except this one, can you finaly make debian package?

Will do. Sorry for the long delay. Meanwhile, I added a minor pull request.

I added some final preparation steps, and confirmed that I can build a proper Debian package once those are applied.
It would be great if you could create a new version 30 based on those changes.

Here is a preview of the manpage provided with pull request #32:

newflasher_1.pdf

Alas, GitHub is unable to preview manpages on their own.

Hi, thanks! I'm done some correction to man page https://github.com/newflasher/newflasher/commit/a73ff5582c9fb81798493a248582953768d9d004 and updated version to 30

I just notices that I need to add a custom "make dist" as well. The standard ".tar.gz" download by GitHub is insufficient, because it is too large as it contains that 4 MiB lib/ directory.

Thanks for your work!
Tracking addition to Debian at https://github.com/newflasher/newflasher/issues/9

Ok, I just created a release tag "30":

https://github.com/newflasher/newflasher/releases/tag/30

And uploaded a relatively small (2.6 MiB) source package there (produced by "make dist").

https://github.com/newflasher/newflasher/releases/download/30/newflasher-30.txz

Great, thanks! I'm just checked responses from xda, seems everything is working great

I think you need to exclude win32 stufs from https://github.com/newflasher/newflasher/commit/56cb1f6775314f983fd29309db27f12adf869aab , gordongate header is windows installer , rc files... etc

Thanks for the hint!
I'll fix that, and I propose to create a new release 31 to avoid confusion.
I also propose to clearly mark the "Optional step 1" as "Windows only", because instructions like "double click on the exe" would be confusing on Debian, especially when Newflasher is installed via package manager to a proper system location. Moreover, "Optional step 1" installs that flash driver that isn't needed for Debian at all (and wouldn't run there, anyway).

Finished pull request.
If you create version 31, would you mind to create the corresponding Git tag "31" as well? I did that for releases 29 and 30, but I believe it should better be done by yourself, as part of your release routine.
At the Git command line, the whole release process would be:
EDIT files  # same as before
git commit ...  # same as before
git push # same as before
git tag 31
git push --tags

Note that in theory, you could leave out the third step, as the last command would push your commit as well as the tag. However, I recommend to first push your commit, just in case you were not up to date. You would then notice, fix your commit (e.g. merge or rebase) and finally tag the fixed commit.

Thanks, ok I will try

I'm done release 31, one problem trought this commit https://github.com/newflasher/newflasher/commit/5b08e9eb6d803277f833ed714c5d6de7dd70c959 is not seen between 30 & 31 , do you have idea why? I'm deleted first atempt for tag 31 and probably that the cause?

Okay, I'll have a look at this.

Hi,
In the tag '31' I also see the binary file newflasher-30.txz added to the repo. See https://github.com/newflasher/newflasher/commit/f866ad3a5eb99de4581dda4ac8d035ae7c38fcf7
Is that intentional? If not, maybe it should be added to .gitignore

That's definitely a mistake from my side.

I'll force-push a fixed commit, so this won't increase the history size.

Oh sorry I'm done allready, Recreated tag 31 https://github.com/newflasher/newflasher/releases/tag/31 , still one commit https://github.com/newflasher/newflasher/commit/5b08e9eb6d803277f833ed714c5d6de7dd70c959 is missing between tag 30 and tag 31, can it be bug?

Tag 30 shows as: https://github.com/newflasher/newflasher/commit/56cb1f6775314f983fd29309db27f12adf869aab
Tag 31 shows as: https://github.com/newflasher/newflasher/commit/f866ad3a5eb99de4581dda4ac8d035ae7c38fcf7
'31' still has that newflasher tar xz.
If you go to https://github.com/newflasher/newflasher/commits/master , you will see the tag 30 commit, "Add "make dist" (#9)"
However, the tag 31 commit is not seen, and even the tag says: "This commit does not belong to any branch on this repository. ", which is because of the force-push.
Solution:
Recreate tag one last time, and this time it should be commit https://github.com/newflasher/newflasher/commit/4161eaa4426aa911ac715036442dba810d7aef02

Sorry, using tags for the first time, solved with:
git reset --hard fa83521967f9e57af5d9fa18561a506929eef6c0
git push -f
git tag -d 31
git push -f
git push --delete origin 31
than done commits from beggining, than:
git tag 31
git push
git push --tags
I'm unsure if what I done is right but the result seems ok now?

@vog why we need newflasher-xx.txz at all? Because of size of the archive? If it was a problem I can try to remove those libs and do similar change like this https://github.com/newflasher/newflasher/commit/3e15d1380b91d27fce928986e74e04ae7266ce30 for other cross blobs so it will not contain those prebuil libs.

@munjeni yes looks ok to me now.
https://github.com/newflasher/newflasher/releases/tag/31 is https://github.com/newflasher/newflasher/commit/29ab0839ac34e3c682c183dba7490fb29fec359c which is what I see at the top of https://github.com/newflasher/newflasher/commits/master right now.

Ok thanks!

@munjeni Looks fine to me as well. I also verified that your uploaded newflasher-31.txz is correct and contains all files in their correction version.
@chirayudesai I'll try to provide an answer to the question by @munjeni. Please correct me if I made some mistake.

why we need newflasher-xx.txz at all? Because of size of the archive? If it was a problem I can try to remove those libs and do similar change like this https://github.com/newflasher/newflasher/commit/3e15d1380b91d27fce928986e74e04ae7266ce30 for other cross blobs so it will not contain those prebuil libs.

It is partially about the archive size, but not in the sense that Debian wouldn't have those resources, it would just be a waste of those resources. We are talking about 4.9 MiB versus 24 KiB.
Moreover, there is the potential security danger that we, by accident, statically link to one of the provided pre-built libraries. This can't happen if those aren't in the source package in the first place.
And there is the potential licensing issue by distributing the GordonGate Windows installer binary (packaged into GordonGate.h). I didn't do any check here, I'm just noting that this is most easily solved by not having that file in the source package in the first place.
But again, @chirayudesai please correct me if I'm wrong.

Ok, I agree, doing one more step (make dist) is not problem at all. In the time I will try to remove prebuilts and gordongate header and give link for download instead.

I think it is much easier than need for make dist. Is this ok?

This looks very good to me!
However, I think that the "cross_blob" is going too far. I propose to just unpack it back to the directory. There was nothing wrong with the ".rc", ".ico" and ".mk" files. I just excluded them from "make dist" because they are unneeded for Unix systems, which was perhaps not a good decision from my side in the first place.

Ok, I'm done it.

Yes, please do so.

It's done https://github.com/newflasher/newflasher/releases/tag/32 Looks better now :)

@vog For Debian we can still just exclude anything we don't want in debian/copyright.
See https://salsa.debian.org/android-tools-team/newflasher/-/blob/3c94a06aae54db4bdc7585414ef0ce669920d2d2/debian/copyright#L5 (this was for version 30/31)
32 looks good, thanks for the update, will switch to that.

This is a great progress! Thanks a lot to @munjeni and @chirayudesai for making this all possible.
@munjeni Just for clarity, you might have noticed that an important organizational change happened a few days ago. The future Debian maintainer for the Newflasher Debian package will not be myself, but instead the Debian Android Tools Team. This is great news, and this is why @chirayudesai is so involved here. It means that the fate of the Newflasher Debian package is not determined by a single person (like myself), but by a group of people who also maintains quite a lot of other Android development related tools for Debian.

Thats great! nw life for a newflasher! :)

And thank you too for initiating all that!

@chirayudesai can you please import version 36, its latest stable version and I'm believing will not need update for a long time

Anybody mind to update Ubuntu repository?

@chirayudesai As far as I can see, there is no initial newflasher package yet in Debian, not even in Debian/unstable or Debian/experimental. Is there anything I can do to assist or support you with that?

Hi, but what about this? -> https://salsa.debian.org/android-tools-team/newflasher
Its too old I see. I would be need to move back newflasher to my acoount (remove from organisation)

I'm done that and thats a final decision without need for explaining anything. CLosing this ticket.

@munjeni As a final clarification, please note that the GitHub organization is in no way related to the Debian packaging. It's just a best practice, just like the many code improvements. Following such best practices makes it easier for distros to package newflasher, but is in no way mandatory.

I'd still recommend to recreate the "newflasher" organization, even if it's just with yourself as the only admin/owner. But that's of course your decision.

To be honest I don't care about distributions. And tw yars is gone, even its hard getting reply from android team, so tool is back in my own account.


docs: framework usage clarification

This clarifies Framework usage, aims to recommend DX from SDKs
Closes #144

Hi @WavyWalk would this documentation serve the purpose?

That will work perfectly, thanks!


github enterprise 401 bad credentials

Hi there
I'm new to hub and I'm trying to get it working against my github enterprise appliance.
I've followed the man page for setting hub.host to the hostname of my appliance & I've set hub.protocol to https
I created a personal access token and set that value to the environment var GITHUB_TOKEN
Yet when I run my hub create command it still attemps to auth me to github.com

Anyone able to give me a steer
I'm running
git version 2.16.2.windows.1
hub version 2.2.9

on windows 10.
Thanks
Gary

Hi, when running hub create and hub clone (i.e. commands that are not in a context of an existing git repo that has remote configuration already set up), hub doesn't really know whether you intend to communicate with github.com or with your Enterprise instance. It defaults to github.com. If you want to default to your enterprise host, you should set HUB_HOST environment variable. From the man page:
The default host for commands like init and clone is still github.com, but this can be affected
with the GITHUB_HOST environment  variable:

    $ GITHUB_HOST=my.git.org git clone myproject


Rename option for FailureList formatter to "failures"

The name was not matching case statement in formatters.rb and it is much
simplier to have an argument with that name.
Discussion:

https://github.com/rspec/rspec-core/pull/2624/files#r284776400

Thanks


Newer versions of perl have trouble with require 'eds-methods.pl' with strict on

The result is that eds-methods.pl won't load, as . isn't in @inc.

to replicate, you'll probably need Debian 9

Hi Liz,
We found this as well on a Debian 9 machine and running Koha 18.11.x branch. We have found adding ./ to the start of the filename in the require line in  eds-detail.pl, eds-ac.pl, eds-cite.pl, eds-raw.pl, eds-search.pl, pfi-search.pl fixes this issue so I have submitted a pull request with these fixes in it:
https://github.com/ebsco/edsapi-koha-plugin/pull/67
We also found that the line: $self->go_home(); which was removed in the Koha EDS master branch is required otherwise a 500 error is shown upon saving the Koha EDS configuration page.
Now with this aforementioned fix after saving the config form you are redirected back to the Tools > Tool plugins page in the Koha intranet.
Cheers,
Alex

#68 should close this issue

This looks to be resolved with the 19.05 release to master, but please feel free to reopen if you install the new release and still see this issue.


Build static library with fvisibility=hidden.

There were several reports of Anaconda's MKL interfering with extensions that links against fftw in unexpected ways.
https://github.com/pyFFTW/pyFFTW/issues/40
https://github.com/openjournals/joss-reviews/issues/1340
MKL runtime overrides fftw* dynamic symbols exported by the extension module. If the symbols in the .a archive are not marked as hidden, then they will be exported as dynamic symbols in the generated so file. Therefore with the current visibility setting even if a downstream extension links against the static version of the fftw library, MKL can still intervene and break the extensions.
With this PR, if a downstream extension links against the static fftw libraries, then MKL will not break them.

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@jakirkham can you look at this one? It is related to an issue you commented on for pyFFTW

This needs a rerender @rainwoodman.

How do I do that? -- the rerender page is a broken link.

@conda-forge-admin please rerender

How do I do that? -- the rerender page is a broken link.

I just did it for you via the conda-forge-admin bot (see prior comment for future reference)

I was not familiar with this flag, but the changes look reasonable to me based on the description and what little I read about it.
I can test it locally now with the existing pyFFTW recipe and make sure it is not going to cause any problems there.

Thanks for the comment. I use a similar trick in pfft-python:
https://github.com/rainwoodman/pfft-python/blob/master/setup.py#L16
I will also test this on my local mpi4py-fft and let you know.

I tested pyFFTW with this locally (on linux) and all seems well.

Did you try with and without mkl?

Yeah, I did test both ways. However, I think all of the tests were already passing prior to this change as well. I was unable to reproduce any MKL failures using a couple of examples from the issues cited above.

Let's see how it goes for @rainwoodman mpi4py-fft because I think he just recently had the issue there with the existing build.

I wonder what workaround pyfftw uses? There seems to be a lot of code in setup.py.
The only other fix I can think of is to notify the linker to only export the init* function of the module. But on this track, a fix will take a much longer time to propagate -- the initial authors of distutils decided not to support export_symbols argument on Unix, so we'll need to fix it there.
The symbolic binding workaround mentioned on the pyfftw thread seems to be very fragile and didn't work for me.

I can confirm this and https://bitbucket.org/mpi4py/mpi4py-fft/pull-requests/7/prefer-using-a-libraries-to-hide-fftw/diff
creates a mpi4py-fft that passes the fftw tests on a MKL enabled anaconda.

Also, I wonder what @mingwandroid thinks about visibility settings of library archives?

Given that this does not seem to break anything and resolves an issue for @rainwoodman, I am in favor of merging.

I am in general in favour of hiding symbols.

Given that this does not seem to break anything and resolves an issue

Well, hiding symbols is going to break other things once this is released. One of those "publish and be damned" scenarios (though conda-build is learning about library exports used to help with this kind of thing in future).

Whelp then let's ship this. Who wants to do the honors?

Is there an easy way to see which downstream libraries depend on this and might need to be rebuilt due to the hidden symbols?
I know pyFFTW links to the static libs, but I'm not sure what other packages do.

We can examine the dependent recipes in the conda forge bot graphs, but it won't say how those deps use the package (e.g. dynamic or static linking, etc.)

but it won't say how those deps use the package (e.g. dynamic or static linking, etc.)

I don't know anything about the bot graphs, but static vs dynamic can be determined (or guessed at pretty accurately) at the recipe level by whether the dep ends up in the run section or not (vs appearing in host or build only). This is because we mark static libs usage with ignore_run_exports.

There are a few dozen dependencies, but as far as I can tell all of them except pyfftw include fftw in the runtime dependencies as well.

They may not be doing that correctly. The deps are sometimes over linked.

And sometimes people don't add the ignore run exports correctly.

And sometimes people don't add the ignore run exports correctly.

Then that is an error that conda-build will detect and report, so long as you use --error-overlinking and --error-overdepending.

Ahhh cool. I am not sure CF uses those yet.


No way to set a sequence option on the command line

Steps to reproduce the problem:

Create a file /tmp/example.py with the following text:

import typing
from mitmproxy import ctx

class Example:

    def load(self, loader):
        loader.add_option(name='myoption', typespec=typing.Sequence[str],
                          default=[], help='')

    def response(self, flow):
        ctx.log.info(repr(ctx.options.myoption))

addons = [Example()]

Run mitmdump -s /tmp/example.py --set myoption=foo --set myoption=bar
Run a request through it: curl -sx http://localhost:8080 http://httpbin.org/get
Observe that ['bar'] is printed, meaning that myoption is set to a sequence of one element — the last one passed on the command line, with the first one ignored.

Any other comments? What have you tried so far?
Looking at the code, I’m not immediately sure why the multiple --set don’t work as I expected them to.
System information
Mitmproxy: 4.0.0 (79fc4e8)
Python:    3.5.2
OpenSSL:   OpenSSL 1.1.0h  27 Mar 2018
Platform:  Linux-4.4.0-116-generic-x86_64-with-Ubuntu-16.04-xenial

Thanks for the concise example, this looks like a bug!

I will take a look at this :)

To solve this properly, we will have to define a format for sequences of strings, and teach the parse_setval function to know about it. @madt1m mad a valiant attempt to avoid doing this, but I don't think it works. ;)

@cortesi could something in line with the good ol' $PATH-like format do the trick? Changing the --set myopt="opt1;opt2;..."

That's tricky because it's plausible to have any of those delimiters in e.g. a regex pattern. I'm afraid we have to go the strenuous route and add an additional "temp dict" argument to parse_setval.

I don't want there to be any ambiguity about set on the command-line or in the command prompt: if you set an option, you over-write what was there before in toto. So no book-keeping between --set options, please.
I suggest we do two things:

Teach --set to know about delimited strings. I think ; or , are both fine, and add backslash escaping. This gets complicated in the presence of a shell, but users are familiar with this from all sorts of contexts, and it's bearable.
I'd be happy to have an --append command-line option and matching command that appends a value to a sequence option. This can be used where we don't mind if update is called after every append. We also might need a better name than "append" which is a bit over-loaded.

I'll manage to allocate some time in this weekend for this. I'll try to come up with a feasible solution :)

Just to chime in: This bug / limitation has bit me, as well. I'm going to have to use a string option instead with a custom delimiter and hand-parse it myself to upgrade from MITMProxy 2 (where I just used argparse) to 4.

I'm having the same issue, but with server_replay_use_headers. There doesn't seem to be a command-line argument to add such headers and using --set server_replay_use_headers headera,headerb or --set server_replay_use_headers=headera --set server_replay_use_headers=headerb doesn't work correctly.

Is there any way to circumvent this limitation? I tried adding an inline script to do something, but it doesn't seem to work.
I.e.
from mitmproxy import ctx

ctx.options.server_replay_ignore_params = [
    "one",
    "two"
]

It looks correct in mitmproxy, but it does not seem to actually do anything.

I'm trying to set multiple --modify-body options from the command line.
My first assumption was that I would simply supply --modify-body multiple times to perform multiple replacements, but that doesn't work. It seems to just take the last option and ignore the others. Is this issue about this problem?
My next thought was that I somehow needed to supply a sequence of patterns to --modify-body, but I couldn't for the life of me figure out how I might do that.

I'm trying to set multiple --modify-body options from the command line.
My first assumption was that I would simply supply --modify-body multiple times to perform multiple replacements, but that doesn't work. It seems to just take the last option and ignore the others. Is this issue about this problem?
My next thought was that I somehow needed to supply a sequence of patterns to --modify-body, but I couldn't for the life of me figure out how I might do that.


Git repo missing source files

Description
I cloned this repo to try and build the plugin but found its missing
ServerSideExtension.cs
ServerSideExtensionGrpc.cs
from the project ServerSideExtension
What I suspect happened is someone added the files to their project and didn't add them to Git so when the push happened the updated solution file was pushed without the files.
Steps to Reproduce

Clone repo  https://github.com/qlik-oss/sse-r-plugin.git
Open solution in C sharp directory using Visual Studio

Hi,
Those files are actually autogenerated and intentionally not committed to the git repo. The project should be setup so that the files are created when you build it, but if something has gone wrong you may need to run csharp/ServerSideExtension/generate_SSE_Stubs_from_proto.bat manually. (For more details about the setup, see @sam-sla's comment in https://github.com/qlik-oss/sse-r-plugin/issues/3 )
Let us know if you have any more trouble. You can also contact Qlik Support which usually has a quicker response time than we do.
Good luck, and hope you have fun using R in Qlik!


Unicode Encoding will cause error in assemble_header.

When a response header contains the Content-Disposion field, it may contains some none ascii character, and as a result causing the assemble_header failed.
We need to deal with this kind of condition.

The root cause of this issue is that http-parser will return unicdoe string for all header field and as a result, when formating a string into byte string it will cause the problem.
Currently, we can just add enocde("utf8") after every header field to solved this issue.

Is it work if we add the b before the string like this:
http_header_query_str = b"{0} {1} HTTP/{2}".format(self.method, self.url, self.version)
http_header_fields = [ b"{0}: {1}".format(key, self.header[key]) for key in self.header ]
http_header_list = [http_header_query_str]
http_header_list.extend(http_header_fields)
return b"{0}\r\n\r\n".format("\r\n".join(http_header_list))

Unfortunately, it will still raise the same exception.
The problem is that self.header[key] is a unicode string, and the format method will encode the unicode string into the string type.

Note that, in python 2 the byte string is basically the same as a normal string. But in python3, the default string type is unicode.

The root cause for this issue is that http-parser will help us encode the headers into unicode. And we have no idea what is the original encoding method, that is the root cause.
I may need to dig further into http-parser, or survey more about the pycohttpparser since pycohttpparser will return the byte string to us and is more suitable for our need.

Got it!
BTW,
I had seen http-parser source code.
It just so str(data) in python 2.7
I m not sure that this will help or not, haha

Commit ec8f151 fix this issue.


Support maps

I'm not sure if this can easily be done. Unlike slices, maps don't seem to have a simple pointer to all their data. Perhaps we can iterate through the map and build a frozen version from its elements. At any rate, it seems like a tricky problem.

This is looking to be difficult, if not impossible. Freezing the map's entries should be doable (though inefficient), but freezing the map itself is another story. This is because the map type (as defined in runtime/hmap.go) may modify internal state during reads. So far, I have discovered two places where this happens. One is to allocate an overflow field; we can get around this by pre-allocating it before freezing. But the second is much trickier: one bit of the flags field is used for signaling, in order to enable concurrent reads.
I don't see an easy way around this. Ideally, there would be some way to freeze only one field of the hmap object, but I haven't yet found a way to accomplish this. It is tantalizing because only one field needs to be frozen (count), and it is the first defined field. Perhaps if there were some way of allocating the map's bytes across a page boundary, and then calling mprotect on only one of the pages...

This is implemented now, but it could be done more efficiently. Freezing the map's bmap instead of using the page boundary trick to freeze only its count seems promising.

Implemented in 6d9879bab6d398a756e41a8239661ffd6f2fbf3a


Incorrect CS hold time in ENC28J60 example using ESP32S2 (IDFGH-6077)

Environment

Development Kit:   ESP32-S2-Saola-1
Kit version (for WroverKit/PicoKit/DevKitC): N/A
Module or chip used:  ESP32S2-WROVER
IDF version : v4.4-dev-2875-g5f38b766a8
Build System:  CMake
Compiler version: xtensa-esp32s2-elf-gcc.exe (crosstool-NG esp-2021r1) 8.4.0
Operating System:  Windows
(Windows only) environment type: ESP Command Prompt
Using an IDE?:  Yes Eclipse with IDF Plugin
Power Supply: external 5V

Problem Description
When using the ENC28J60  example the CS hold time is not enough and causes failure reading/write phy registers.
This is issue is related to https://github.com/espressif/esp-idf/issues/7156. The fix provided don't seems to work for ESP32S2 (I don't have a ESP32 to test).
I'm using the following config:
SPI Host: 2
SCLK GPIO: 12
MOSI GPIO: 11
MISO GPIO: 13
CS GPIO: 10
Clock: 8Mhz
Interrupt GPIO: 14
Expected Behavior
The value for cs_ena_posttrans calculated by the function enc28j60_cal_spi_cs_hold_time for 8Mhz is 2 but the hardware seems not to hold the CS for 2 cycles (I would expect 2 cycles to be 250ns) but only 1.
Actual Behavior
A value of 1 in cs_ena_posttrans generates a CS hold of ~13ns, 2 generates ~134ns and 3 ~263ns
Attached is the scope capture of the communication (showing clock and CS only).
cs_ena_posttrans = 2:

cs_ena_posttrans = 3:

Possible fix
Since cs_ena_posttrans seems to start with 2 I changed enc28j60_cal_spi_cs_hold_time to account for that:
static inline uint8_t enc28j60_cal_spi_cs_hold_time(int clock_speed_mhz)
{
    if (clock_speed_mhz <= 0 || clock_speed_mhz > 20) {
        return 0;
    }
    int temp = clock_speed_mhz * CS_HOLD_TIME_MIN_NS;
    uint8_t cs_posttrans = temp / 1000;
    if (temp % 1000) {
        cs_posttrans += 1;
    }

    return cs_posttrans+1;  //<<
}

Debug Logs
I (288) gpio: GPIO[14]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (298) enc28j60: revision: 6
E (308) enc28j60: enc28j60_init(307): wrong chip ID
E (308) esp_eth: esp_eth_driver_install(222): init phy failed
ESP_ERROR_CHECK failed: esp_err_t 0xffffffff (ESP_FAIL) at 0x40027644

@NorbertoNorbs just FYI, the SPI driver fix is currently in internal review...

@kostaond Thanks for the update, when ready I will test again with the same setup.

Thanks for reporting, the fix on master is https://github.com/espressif/esp-idf/commit/d500c8205ea4a00ca5ed79c0d0230361f71e6d4c, we are back porting the fix until release/4.2, will update further when the fixes sync to GitHub.

v4.4:<PHONE_NUMBER>45f8bc737f51c78b799c11299072e0
v4.3: b3c51e74c821aca1a69b97e6e68e4b9bd6dc9e8b
v4.2: ca6636c33e409e3a4e5e187d980ab05d05656a1d
This can be closed.

Thanks for reporting and sharing the updates, feel free to reopen if the issue still happens, thanks.


expect documentation link

I don't understand but this can't be the documentation : http://chaijs.com/api/
It appear in node_modules folder that 3.4 use chai 3.5.0.
I really don't know for which version is this documentation, I need to convert this :
expect(css).toNotContain('undefined').toNotContain('null');

Not that I am looking for a string not a type (this for styled-components that allow props to be rendered has undefined or null)
.toNotContains is undefined since 3.4 update, using the documentation wasn't helpful.
I have tried to log the expect object but it is even more confusing : http://pastebin.com/f6dDsa2N
This would work:
expect(css).not.toContain('undefined');
expect(css).not.toContain('null');

I just wan't to know what documentation should I look at.

I think you should look into the Jest documentation: https://facebook.github.io/jest/docs/api.html#writing-assertions-with-expect, unless you're importing something from chai directly (import { assert } from 'chai';), so now I have a dumb question: do we even need chai and chai-enzyme? Using Jest with Enzyme guide states that enzyme work fine without any additional library and we don't use chai assertions.

Well, I just removed chai and chai-enzyme, commented out related imports in internals/testing/test-bundler.js, deleted node_modules, ran yarn and npm test.
All tests pass 😁

Chai is also mentioned in the new docs/general/introduction.md

@kopax, I'll assume that your question was answered.

Chai is also mentioned in the new docs/general/introduction.md

Not anymore in #1441


Add haskey-btree, haskey and haskey-mtl

Checklist:

[x] Meaningful commit message - please not Update build-constraints.yml
[x] At least 30 minutes have passed since Hackage upload
[x] On your own machine, ...

xxhash-ffi (not present) depended on by:
- [ ] haskey-<IP_ADDRESS> (>=<IP_ADDRESS> && < 1). No maintainer. @haskell-haskey. Used by: library

We cannot merge this until xxhash-ffi is added to Stackage too (or no longer a dependency for you)

Thank you, I missed this, see #3509


Update ReadME.md

to be updated with .

to be updated.

Not related to the project; includes personal details.


Error "Unable to open 'workspaceTrustEditor':" when clicking on Manage in Restricted Mode notification

Issue Type: Bug
Open VSCode
Restricted Mode blue notification appeared
Click on Manage hyperlink
Full error message:
Unable to open 'workspaceTrustEditor': Unable to resolve resource vscode-workspace-trust:workspaceTrustEditor.
Reinstalling VSCode doesn't help
VS Code version: Code 1.57.1 (507ce72a4466fbb27b715c3722558bb15afa9f48, 2021-06-17T13:28:07.755Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: Yes

System Info

Item
Value

CPUs
AMD Ryzen 9 5950X 16-Core Processor             (32 x 3400)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
63.93GB (18.45GB free)

Process Argv
--crash-reporter-id 41c965e2-e445-40cd-ab15-6845975b6c90

Screen Reader
no

VM
0%

Extensions: none
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
pythonvspyt551cf:30311713
vspre833:30321513
pythonptprofiler:30281270
vshan820:30294714
pythondataviewer:30285071
vscus158:30321503
vscorehovct:30309550
vscod805cf:30301675
binariesv615cf:30321889

@nerzhulart, I have tried to reproduce this issue without much luck so I was wondering if these is any further information that you could provide that could help me track down the root cause of this bug. Could you please answer the following questions:

Have you modified any of the workspace trust settings?
When you say "Open VSCode", are you opening a folder/workspace, or a loose file?
Are you able to reproduce this issue every time you open VS Code?

@lszomoru Hi! Thanks for the answer!

I didn't make any changes inside "workspace trust" (I even don't know where they're located)
I open a single file (several log files actually)
Yep. It shows an error to me every time I open VSCode.

@nerzhulart, thanks for getting back to me. Are you opening these files using the CLI (ex: code file1 file2 file3) or are you starting VSCode and them opening the files using the File -> Open menu?

@nerzhulart, thanks for getting back to me. Are you opening these files using the CLI (ex: code file1 file2 file3) or are you starting VSCode and them opening the files using the File -> Open menu?

I open them using Windows Shell associations (so I guess it works the same way if to open with command line)

@nerzhulart can you try opening code with (note the username to replace)
 code --user-data-dir C:\Users\<user>\Desktop\user1 --extensions-dir C:\Users\<user>\Desktop\ext1 and see if the issue repros?

Looks a lot like https://github.com/microsoft/vscode/issues/124386 which should be fixed in insiders.

@nerzhulart can you try opening code with (note the username to replace)
 code --user-data-dir C:\Users\<user>\Desktop\user1 --extensions-dir C:\Users\<user>\Desktop\ext1 and see if the issue repros?

Seems it helped! The action Manage Workspace trust works now. So AIU I need to clean my VSCode profile folder, right?

@nerzhulart my guess is you have something like {'*': 'default'} in your settings.json and that's the issue. If you remove that everything should be fixed.

@lszomoru I

Closing this as duplicate of #124386.


Null pointer

/root/jsonapi-server/lib/routes/relationships.js:47
sanitisedData = sanitisedData.relationships[request.params.relation].data;
^
TypeError: Cannot read property 'relationships' of null
at /root/jsonapi-server/lib/routes/relationships.js:47:38
at fn (/root/jsonapi-server/node_modules/async/lib/async.js:746:34)
at /root/jsonapi-server/node_modules/async/lib/async.js:1213:16
at /root/jsonapi-server/node_modules/async/lib/async.js:166:37
at /root/jsonapi-server/node_modules/async/lib/async.js:706:43
at /root/jsonapi-server/node_modules/async/lib/async.js:167:37
at Immediate._onImmediate (/root/jsonapi-server/node_modules/async/lib/async.js:                                              1206:34)
at tryOnImmediate (timers.js:534:15)
at processImmediate [as _immediateCallback] (timers.js:514:5)

This occurs when the data coming out of your handler doesn't validate against your schema.
For example, if your Joi schema for a resource says There will be a "body" attribute, but the data in a database somewhere doesn't enforce the same requirement and someone inserts a row without a body, then you try and fetch that resource via the API.
I'm opening a PR in to provide an error saying "Sorry, this resource exists, but its fundamentally broken. We can't provide you with the resource because it won't conform to your expectations."

Fixed in v1.11.0


Plural: If no translation existing add empty msgstr[] entries

This is required to be a valid po file for some validators

Could you point out to some of those validators?

The first coming to my mind is integrated in php-storm...
I'm not sure with poedit and qt-linguist...


fix: can not delete embed blots on android

fix https://github.com/slab/quill/issues/1985
the reason of this issue
the cursor focus between the contentNode of the embed and the rightGuard of the embed which is a zero-width space
in this case, the native selection range is like
{
 start:{
   node: rightGuard,
   offset: 0,
 }
}

until now, everything is fine
but when quill normalize this range, it goes the wrong way, because offset is 0.

the final range we get is the position before our embed
so when you backspace
you can't delete the embed
you just delete the previous sibling

This is the same fix as I proposed in my pull request https://github.com/slab/quill/pull/4464
Would be good if a maintainer could have a look at it.


Discussion around Credential/SSL Pinning/Invalid SSL Handling.

I've been digging a bit deeper into the handling of credentials/ssl pinning, and invalid ssl handling, specifically looking at it from a testing perspective and what can be done to make that code more testable with the good work @blakewatters is doing in #985. I've found some interesting behavior here, and wanted to make a few suggestions as well as ask a question about unusual behavior I am seeing.
cc'ing @OliverLetterer, who originally implemented the pinning code.
Issue 1: Clean Up
The docs for connection:willSendRequestForAuthenticationChallenge state the following:

"This method allows the delegate to make an informed decision about connection authentication at once. If the delegate implements this method, it has no need to implement connection:canAuthenticateAgainstProtectionSpace:, connection:didReceiveAuthenticationChallenge:, connectionShouldUseCredentialStorage:. In fact, these other methods are not invoked."

The last comment is interesting, meaning that those methods are not even invoked if connection:willSendRequestForAuthenticationChallenge is implemented, which in AF's case, is true when _AFNETWORKING_PIN_SSL_CERTIFICATES_ is defined. Also note that when _AFNETWORKING_PIN_SSL_CERTIFICATES_ is defined, the other three methods are still implemented, even though they will never be called.
With that being said, I think that at a minimum those methods should only be implemented if _AFNETWORKING_PIN_SSL_CERTIFICATES_ is not defined, which would mean we need to add an #elseif to only implement those in that condition. (And potentially only expose the callback blocks in that same condition)
Additionally, I know that the reason we have that macro is because there was no way to detect if the Security Framework was added dynamically. I understand the original intent of this (as well as MobileCoreServices and SystemConfiguration) was to support easy library integration, and not require developers to have to link to other frameworks to get started. However, with the booming popularity of CocoaPods, I wonder if its time to leverage CocoaPods as the official means of integrating AFNetworking into your project, and drop support for dynamic framework linking. We could of course include manual install instructions, and require linking against the three frameworks there, but I think that will improve the readability of the codebase, and make it more maintainable going forward.
If we go down that route, then I think we can get rid of connection:canAuthenticateAgainstProtectionSpace:, connection:didReceiveAuthenticationChallenge:, connectionShouldUseCredentialStorage: entirely, as well as their callback blocks, since they are not invoked if connection:willSendRequestForAuthenticationChallenge is implemented.
Potential Outcome:
Remove the optional links to MobileCoreServices, SystemConfiguration, and Security. Move to CocoaPods as official install mechanism. Delete unneeded NSURLConnectionDelegate callback methods and blocks.
Issue 2: How do we Clear Credentials?
I've ran into interesting issue making this code more testable. Specifically, I can't find a way to remove a NSURLCredential for a NSURLProtectionSpace after it has been used once.
This actually has some subpar behavior. Specifically, if you set allowsInvalidSSLCertificate to YES once, that credential is set, it is automatically applied for every request with that host going forward, regardless of whether or not allowsInvalidSSLCertificate is set to NO. There is similar behavior for the pinning options as well. From a testing perspective, we'll need to be able to reset those states and ensure code is being handling correctly.
I've tried peeking into NSURLCredentialStorage, but there is no credential stored there, which seems wrong to me but I'm still feeling my way around trying to understand where that credential is actually being stored. Note that the method we are using to create the credential (credentialForTrust) is the only method that doesn't support passing a NSURLCredentialPersistence as a parameter, so I don't know how it's being persisted under the hood.
Additionally, I'm blasting away all cookies to ensure they aren't applied either, so that's not causing the problem.
Essentially, I'm trying to find a way to force connection:willSendRequestForAuthenticationChallenge: to be called again in the future for the same NSURLAuthenticationChallenge, but I can't get it to work. @OliverLetterer, any ideas?

connection will send request methos it is not call

For anyone still running into TLS caching issues, Apple has updated the technical QA1727 on Aug 19 2015 with a note about NSURLSession:

Important: This solution can better be achieved by adopting the NSURLSession API. Using this framework, you can created two NSURLSessions, one for each desired connection. Since NSURLSession maintains it's own TLS session cache, the second connection will avoid consulting the first cache, and will return the authentication challenge.

@robmaceachern  it is not true. Credentials are cached in TLS session for 10 minutes for different NSURLSession instances

@Koshub you're right. According to Quinn on the dev forums:

this feature got broken at some point (I think with iOS 8) and wasn’t fixed until iOS 9

Sigh
https://forums.developer.apple.com/message/49334

@robmaceachern Thanks indeed.

@robmaceachern  Same thing on iOS 9.2


Automate adding the new-language label

Resolves #371

Note: use bash process substitution?
command <(echo "file 1") <(echo "file 2")


When using advance search on file manager and page search, filters' setting doesn't work as it should be

On file Manager and page Search pop-up window, you can add the same page type as filters repeatedly now.
We believe that the same page type should not be able to be selected.
Also, when you add more than two kinds of page type as filters, only page type added at last works.
The other page types are ignored.
If you can set more than two kinds of page type, all page type selected should be used as filters.

Agreed. We should make it so that you can't choose the same criteria more than once.


NOISSUE - Use .enr vars in docker-compose

Signed-off-by: Manuel Imperiale<EMAIL_ADDRESS>

Codecov Report

Merging #770 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #770   +/-   ##
=====================================
  Coverage      85%    85%
=====================================
  Files          69     69
  Lines        4469   4469
=====================================
  Hits         3799   3799
  Misses        444    444
  Partials      226    226

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 204aec6...e193ca6. Read the comment docs.

@manuio There is a .env already in docker/ can you move everything there or pull everything out?


Maria trial

Merge only the following:
WDI-Complete code.ipynb
WDI-Data extraction.ipynb
WDI-Data integration.ipynb
WDI-Data normalization.ipynb

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


the version in code-server is still 0.0.50.

The version for vs-code is 0.0.78, the latest.
why is this?


https://raw.githubusercontent.com/MicrosoftLearning/PL-400_Microsoft-Power-Platform-Developer/master/Instructions/Labs/LAB[PL-400]_Lab09_Azure.md

A recent QA has noted the following issues:
Exercise 5/Task 5.2/Step 4 -- The UI has changed; the "Delete" option is now located at the bottom, rather than at the top as shown in the instructions.

Exercise 6/Task 6.1/Step 4 --  Primary Table is now called Primary Entity

Exercise 6/Task 6.2/Step 1 -- QA was unable to follow the steps suggested in the instructions to navigate to the Webhook App Insights logs. To access the logs, QA followed these steps:
1. Ensured was on the Function App overview page.
2. Selected "WebHookTrigger" from the Functions tab.
3. Clicked on "Logs" tab.
4. Noted that App Insights logs are already selected by default.

Updated screenshot for Function App output
Corrected Primary Table back to Primary Entity in PRT

To Do: Verify steps for Webhook App Insights logs


Tweak lightmapper warning message to mention Rosetta emulation on macOS

See https://github.com/godotengine/godot/issues/48082.

Might be worth mentioning it in the https://godotengine.org/article/godot-3-3-has-arrived#lightmapper and release notes as well.

We should remember to revert this once embree-aarch64 is integrated :)

Thanks!

Cherry-picked for 3.3.1.

I added a mention to it in the blog post:

We should remember to revert this once embree-aarch64 is integrated :)

Done with 0a4eb472cfe0d02e11ee02bc741e4c03f7a34e0f.


Merge Development Branch Into Master Branch

What does this PR do?
It extends the feature of the app to cover multiple file selection, error modals and multiple file searches.
Description of Task to be Completed
Make the project to be able to handle multiple file selections and create appropriate index, show error modals for empty files, files that are not valid json objects, or ill-formated json files. It also remodels the ui component placements for ease of usage.
How Should this be manually tested?
npm start

PR was closed because I made a mistake in using development branch as the base branch instead of master, hence github was seeing it like I want to merge the changes from master into development instead of from development into master.


Headlamp does not show restart/edit/scale buttons on resources with sufficient permissions

Describe the bug
The bug title says it all. I gave permissions to restart, scale, edit the deployment but the button with the option to restart and scale the deployment does not appear. These are sufficient permissions because I tested using kubectl.
kubectl rollout restart deployment gotify -n default
According to the documentation the buttons should appear
https://headlamp.dev/docs/latest/faq/#headlamp-is-not-showing-deleteeditscale-buttons-in-a-resource-why-is-that
To Reproduce
Create Deployment
apiVersion: apps/v1
kind: Deployment
metadata:
  name: gotify
  namespace: default
spec:
  selector:
    matchLabels:
      app: gotify
  replicas: 1
  template:
    metadata:
      labels:
        app: gotify
    spec:
      containers:
        - name: gotify
          image: gotify/server
          env:
            - name: GOTIFY_SERVER_PORT
              value: "81"
          ports:
            - containerPort: 81
          readinessProbe:
            httpGet:
              path: /health
              port: 81
            initialDelaySeconds: 5
            periodSeconds: 10
          livenessProbe:
            httpGet:
              path: /health
              port: 81
            initialDelaySeconds: 10
            periodSeconds: 20

Create SA with secret
apiVersion: v1
kind: Secret
metadata:
  name: cluster-developer
  namespace: default
  annotations:
    kubernetes.io/service-account.name: cluster-developer
type: kubernetes.io/service-account-token
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: cluster-developer
  namespace: default

Create custom RBAC with sufficient permissions.
kind: ClusterRole
metadata:
  name: custom-role
rules:
  - apiGroups: [ "" ]
    resources: [ "pods" ]
    verbs: [ "get", "delete" ]
  - apiGroups: [ "" ]
    resources: [ "pods/portforward" ]
    verbs: [ "get", "create", "delete" ]
  - apiGroups: [ "" ]
    resources: [ "pods/exec" ]
    verbs: [ "get", "create" ]
  - apiGroups: [ "" ]
    resources: [ "configmaps" ]
    verbs: [ "get" ]
  - apiGroups: [ "apps" ]
    resources: [ "deployments/scale" ]
    verbs: [ "get", "patch" ]
  - apiGroups: [ "apps" ]
    resources: [ "deployments" ]
    verbs: [ "get", "patch" ]

---

# ClusterRoleBinding for granting the custom-role to the service account
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: cluster-developer-binding
subjects:
  - kind: ServiceAccount
    name: cluster-developer
    namespace: default
roleRef:
  kind: ClusterRole
  name: custom-role
  apiGroup: rbac.authorization.k8s.io

---

# ClusterRoleBinding for granting the 'view' role to the service account
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: cluster-developer-view-binding
subjects:
  - kind: ServiceAccount
    name: cluster-developer
    namespace: default
roleRef:
  kind: ClusterRole
  name: view
  apiGroup: rbac.authorization.k8s.io

Environment (please provide info about your environment):

Installation type: Windows-Winget
Headlamp Version: v0.26.0

Are you able to fix this issue?
No. I work as devops :(
Additional Context

Excepted result

Additionally, after pressing the actions button the bubble has weird formatting.

Hi, thanks for submitting this issue!
Do the buttons also not appear at the top when you click on the deployment?

Tried to test this locally (app in WSL and browser) and I see this on both:

Thanks for the reply
After clicking on the deployment object I see this.

Do you use correct kubeconfig? On the last photo you have a visible delete button. My custom RBAC does not contain delete verb which removes deployment object. You should use kubeconfig with limited access. Use all the roles I used and generate kubeconfig.

interesting, would you be able to provide your kubeconfig? (feel free to redact any sensitive information)

Sure. You get the certificate-authority-data and token value from a secret. In my case, it's a secret called cluster-developer.
kind: Config
clusters:
  - name: k3d-multiagent
    cluster:
      server: 'https://host.docker.internal:6445'
      certificate-authority-data: >-
        LS0tLS1CRUdJTiBDRVJUSUZJQ0FUR...
users:
  - name: cluster-developer
    user:
      token: >-
        eyJhbGciOiJSUzI1NiIsImtpZC...
contexts:
  - name: k3d-multiagent-cluster-developer
    context:
      user: cluster-developer
      cluster: k3d-multiagent
      namespace: default
current-context: k3d-multiagent

Awesome ty, I matched up the kubeconfigs and I'm seeing what you're seeing now. Will take a look into this

I see that you see the scale button for the deployment when you click on it (on the right side here)

but you don't see the edit or restart buttons. Both of these actions require permission to "update", so if you add "update" to deployments and deployments/scale and refresh you should see them. Although they aren't showing up in the table row actions, working on this now


Error when using ppp code on yolov8n model

I have issue similair to this. I am trying to add pre-post processing steps to finetuned yolov8n, model in onnx attached in the archive. I am using code from here. It works with default pretrained yolov8n, but fails on inference test with finetuned yolo with error:
onnxruntime.capi.onnxruntime_pybind11_state.RuntimeException: [ONNXRuntimeError] :
6 : RUNTIME_EXCEPTION : Non-zero status code returned while running Split node.
Name:'post_process_14' Status Message: D:\a\_work\1\s\onnxruntime\core\framework\op_kernel.cc:83 onnxruntime::OpKernelContext::OutputMLValue status.IsOK() was false.
Tensor shape cannot contain any negative value

What i can do to resolve this?
yolov8n_sku110k_10_epoch.zip

@skottmckay, can you help with that?

The code was tested with the default yolo v8 and expects there to be 80 classes. Does the 'finetuned' version only emit 1 class, resulting in the output being {1, 5, 8400} instead of the expected {1, 84, 8400}?
If so, you could try adding , num_classes=1 to the call to yolo_detection here.

Thank you for your answer. I converted model to onnx and add pre\post processing steps to it. In the attached images you can see results of original model (many bboxes) and results of model with ppp steps (1 bbox). Are the boxes inside the model filtered somehow? If so, how can i manage confidence, etc.?

Another question, is there an API to add another output chanel to a model, with standart bboxes, scores, classes?

These are questions for the model author. I don't know what the 'finetuned' version is. It seems to only produce a single result, but how it determines that is internal to the model. i.e. the onnxruntime post-processing is not involved in selecting the single result.
Same with adding new outputs to the model.
Basically we're not changing the original model - we're adding pre-processing and post-processing to the original model as-is.

As far as I understand, the results (number of results) of the model before and after adding ppp steps should not differ, correct? Provided that in the first case, preprocessing was performed by the native ultralytics framework, and the preprocessing steps added to the model must correspond to it.
In my example you can see that the model results before adding ppp steps and after are different. Seems like the source of this should be the added steps

The SelectBestBoundingBoxes post-processing step has a score_threshold argument you can set for the minimum threshold. You could try setting that to a lower value than the (arbitrary) default of 0.67.
Set the value here by adding an argument to the call (e.g. SelectBestBoundingBoxesByNMS(score_threshold=0.1). You can modify the python file in the onnxruntime_extensions package directly.
There are other configurable values for the ONNX NonMaxSupression as well. That is used to select the best bounding boxes from the results by removing overlapping ones or ones with low scores.

Everything is resolved with the thresholds, thank you. Regarding the model outputs: I removed 274-280 lines from here to get the post-processed coordinates of the bboxes instead of bitmap image. Seems like coords not quite match the original image:

Can you guide me towards what step is missing to match coords with the original image?

Are you using the correct co-ordinate format to draw the bounding boxes? There are a few different ones as mentioned here:
https://github.com/microsoft/onnxruntime-extensions/blob/4f6e12579cfd190e5810d4c8ba901ca5c767be7a/onnxruntime_extensions/tools/pre_post_processing/steps/vision.py#L629-L640
As you can see from the code you removed the format is CENTER_XYWH for YOLO.

I was drawing it from corner, now problem is resolved. Thank you


Counting up

What about counting up instead of down with the timer (for an infinite amount of time, where you simply can stop it to get the passed time)?

I have the same question. Would be a quite useful addition.

Needs an option to count up instead of down.

does anyone know how to implement this ?


docs: include Polars in docs.rs build

Closes #1948

#1949  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Shoeboxam and the rest of your teammates on  Graphite


After upgrading if you open a new window you just get a blank window

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
Version: 1.94.0 (Universal)
Commit: d78a74bcdfad14d5d3b1b782f87255d802b57511
Date: 2024-10-02T13:08:12.626Z (1 day ago)
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 23.6.0
OS Version: macOS Sonoma 14.7

Steps to Reproduce:

Wait for upgrade
Open a new window
Observe a blank screen

This happened to me and a few of my teammates after the upgrade

user a: "everytime i try to open a new window or do anything in vscode it just grey screens me. is there any way to resolve this other than completing quitting and restarting? i dont want to lose all my windows"
user b: "oh yeah this happened to be earlier today. Thought I was going insane"

(workaround is to cmd + q to quit all windows, but this is disruptive, and confusing when this happens)

In that new window when it has focus, can you select "Toggle Developer Tools" from the "Help" menu and see what is printed in the "Console"?


Document that a specific version of meteor is required on Windows

On Windows, it appears that meteor version 2.1 is required. Installing a newer version results in errors about NODE_MODULE_VERSION incompatibilities with native addons. The documentation should mention this and explain how to install a specific version of meteor.

I believe this was fixed by https://github.com/nrkno/tv-automation-server-core/commit/d8b519d1d36b3cd54ee0eae1ce028396ab9ce703 and that installing the latest system Meteor is fine on Windows now. I tested it on my laptop with Meteor 2.5.1 and Sofie was able to install all of its dependencies without issue.


feat: useFetchDispatcher()

Motivation

Fetching unknown number of items? Never fear, this lets you use one hook with many different fetches!
We'll be using this for our fetch-as-render SSR + concurrent mode routing architecture.
Solution

SSR Concept
This hook is always mounted.
import { dispatchFetch } from 'rest-hooks';
import { useLocale } from 'i18n';

function useRouteContext() {
  const locale = useLocale();
  const dispatchFetch = useFetchDispatcher();
  return { locale, dispatchFetch };
}

Each of these routes resolveData will be run on navigation even stack.
const routes = [
  {
    path: '/home',
    modulePath: 'Home',
    resolveData: ({ dispatchFetch, locale }) => {
      return dispatchFetch(
        AssetResource.listShape(),
        {
          locale: locale?.currency,
          localeCode: locale?.localeCode
        }
      );
    },
  },
  {
    path: '/careers/:position-id',
    modulePath: 'Careers',
    resolveData: (({ dispatchFetch, params: { positionId })) => {
      return dispatchFetch(PositionResource.detailShape(), { positionId });
    },
  },
]

This design allows for multiple, variable number and types of endpoints to fetch without any re-renders.
Open questions

Should this be the new default, or simply supplement useFetcher()? It doesn't add verbosity really and is more powerful.

oh i really like this


findutils: 4.6.0 -> 4.7.0

See https://lists.gnu.org/archive/html/info-gnu/2019-08/msg00009.html
for release information

Motivation for this change
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
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 nix-review --run "nix-review wip"
[X] 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)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Notify maintainers
cc @

@GrahamcOfBorg build findutils

Tested on x86_64, built rustc and ghc, haven't found any issue, also helps #66528
Thx!

built successfully on linux.


Support running async cleanup operations when an async_generator is destroyed early

@ericniebler's recent blog entry, Ranges, Coroutines, and React: Early Musings on the Future of Async in C++, contained the following code-snippet that showed how async_generator<T> could be used to read a file in chunks:
auto async_file_chunk( const std::string& str ) -> async_generator<static_buf_t<1024>&>
{
  static_buf_t<1024> buffer;

  fs_t openreq;
  uv_file file = co_await fs_open(uv_default_loop(), &openreq, str.c_str(), O_RDONLY, 0);
  if (file > 0)
  {
    while (1)
    {
      fs_t readreq;
      int result = co_await fs_read(uv_default_loop(), &readreq, file, &buffer, 1, -1);
      if (result <= 0)
        break;

      buffer.len = result;
      co_yield buffer;
    }
    fs_t closereq;
    (void) co_await fs_close(uv_default_loop(), &closereq, file);
  }
}

Unfortunately, this snippet contains a flaw in that if the consumer stops consuming the elements of the async_generator before it reaches the end() of the sequence then the file handle will never be closed.
Currently, when the async_generator object is destructed it calls coroutine_handle<>::destroy() which destroys the coroutine frame and any object that was in-scope at the co_yield statement where the producer coroutine last produced a value. The coroutine does not get a chance to execute any code to clean up resources other than via running destructors. This allows you to perform synchronous cleanup operations via usage of RAII types but it means you can't perform any async cleanup operations (like the async fs_close example above, or gracefully shutting down a socket connection).
What if, instead of destroying the coroutine frame when the async_generator is destroyed we resume the generator coroutine but instead make the co_yield expression return an error-code (or throw a generation_cancelled exception)? This would then allow the coroutine to respond to the cancellation request and perform any cleanup operations.
For example, if the co_yield expression were to return an enum value of generator_op:::move_next or generator_op::cancel then the main-loop of the above snipped could have been modified thus:
auto async_file_chunk( const std::string& str ) -> async_generator<static_buf_t<1024>&>
{
  static_buf_t<1024> buffer;

  fs_t openreq;
  uv_file file = co_await fs_open(uv_default_loop(), &openreq, str.c_str(), O_RDONLY, 0);
  if (file > 0)
  {
    while (1)
    {
      fs_t readreq;
      int result = co_await fs_read(uv_default_loop(), &readreq, file, &buffer, 1, -1);
      if (result <= 0)
        break;

      buffer.len = result;

      // The next two lines are the only ones that have changed.
      generator_op yieldResult = co_yield buffer;
      if (yieldResult == generator_op::cancel) break;
    }
    fs_t closereq;
    (void) co_await fs_close(uv_default_loop(), &closereq, file);
  }
}

If the coroutine subsequently tried to execute another co_yield expression after it had been cancelled then the co_yield expression would complete immediately again with the generator_op::cancel result.
There are a couple of issues with this approach, however:

The first is that the syntax for writing a correct producer coroutine is now more complicated (you need to check return-value of co_yield expression).
This could be somewhat alleviated by either throwing an exception (which I'm also not liking that much since I don't like to use exceptions for expected/normal control-flow)
Or it could be an opt-in behaviour (eg. by constructing some scoped object on the stack, or otherwise communicating with the promise that you want to continue after a cancellation request)
The continued execution of the coroutine now represents a detached computation that you cannot synchronise against, or otherwise know when it will complete. eg. If it is closing a file asynchronously I may still want to know when the file has been closed so that I can delete it or open it again once the file lock has been released.

The second issue is perhaps the greater one here.
This could possibly be mitigated by requiring the caller to explicitly start the production of the generator by awaiting a task<> returned by the async_generator<T>::produce() member function.
With such a task, the generator would not start executing until both the produce() task and the task returned by begin() had been awaited. The caller would need to use something like when_all() to concurrently execute both tasks.
The producer task would not complete until the generator coroutine has run to completion.
The consumer task is free to destroy the async_generator and complete early without consuming the entire sequence. This would send a cancel request to the producer task so it can terminate quickly.
There are potential issues with composability of such an async_generator that I haven't yet worked through.

This could possibly be mitigated by requiring the caller to explicitly start the production of the generator by awaiting a task<> returned by the async_generator<T>::produce() member function.
With such a task, the generator would not start executing until both the produce() task and the task returned by begin() had been awaited. The caller would need to use something like when_all() to concurrently execute both tasks.

What is produce() and how is it different from begin()?

The idea behind produce() is that it returns a task that represents the execution of the generator coroutine body. ie. the producer task.
The coroutine body will not start until both the producer task is awaited AND the begin() awaitable is awaited. This ensures that there is an async continuation already attached that will wait for async cleanup before the generator even starts, which is required to be able to guarantee that there is no dangling threads of execution.
This is thinking about the async_generator as two tasks (a producer and consumer) synchronising such that only one of them is running at a time. However, once the consumer requests cancellation of the sequence by destructing the async_generator the two tasks diverge and run concurrently.
An example to show the concept (I'm not that happy with syntax yet):
async_generator<static_buffer_t<1024>> async_file_chunk(const std::string& str);

task<> consumer(async_generator<static_buffer_t<1024>> fileChunks)
{
  for co_await (auto& chunk : fileChunks)
  {
     // Might terminate early
     if (someCond) break;
  }
}

task<> usage()
{
  auto chunks = async_file_chunk("/path/to/file");

  // Get the task that produces the
  task<> producerTask = chunks.produce();
  co_await when_all(producerTask, consume(std::move(chunks)));
}


hackbot should lock reposted link threads and post link to old thread

My proposed changes here cover this: https://github.com/kern/hackbot/issues/9

Facebook's ToS doesn't let apps post as the app itself on groups, but it can post on behalf of the authenticated user. This could be implemented by scanning the link fields of the post object, normalizing them, and comparing.
Even if this isn't automatic, /redirect should be an alias of /thread so we can post links to the relevant subgroup/original topic. That's a quick fix.

This is getting implemented in #11.


Plugin` configuration doesnt depend on config changes

Once plugin configuration was changed in bramble.json file, file watcher handles event and reload config in case of CREATE or CHANGE. But, for example auth plugin doesn`t depend on this reload process, as this object is constructed at the moment of starting Bramble (i tried to change Role section, bramble triggered event changes, but auth plugin was working under old role model)

I re-checked the process of auth plugin hot reload and figured out that the issue is during unmarshall data json.RawMessage in case role was removed from Roles config

Thanks for spotting the bug @ITheCorgi, would you like to make a PR of the change?

@pkqk Yeah, sure


[admin] Add a human readable value for empty org selection

When the organization selection is optional, it means that leaving it empty makes that object available for all the organizations in the system.
Right now, this is not intuitive at all. We could use some admin form magic to replace the empty string with something like: Shared systemwide (no organization).

When the organization selection is optional, it means that leaving it empty makes that object available for all the organizations in the system.
Right now, this is not intuitive at all. We could use some admin form magic to replace the empty string with something like: Shared systemwide (no organization).

@nemesisdesign I setup the project locally by following instructions. But I don't think that the organisation selection is optional. Can you please look into this again and elaborate the issue?

When the organization selection is optional, it means that leaving it empty makes that object available for all the organizations in the system.
Right now, this is not intuitive at all. We could use some admin form magic to replace the empty string with something like: Shared systemwide (no organization).

@nemesisdesign I setup the project locally by following instructions. But I don't think that the organisation selection is optional. Can you please look into this again and elaborate the issue?

@devkapilbansal I've been working on this issue and I'm pretty close to a patch :smile: however, I didn't claim this so that's on my part. Would you like to leave this? For your question, yes, the sample app we're using currently has 2 models: Book and Shelf, and these both have mandatory organization field.

Okay @Purhan you can take this up. But if the organisation field is not optional, then does this issue makes sense?

Okay @Purhan you can take this up. But if the organisation field is not optional, then does this issue makes sense?

Yes, because there may be other modules relying on openwisp-users where some models have it optional.


updating image_id description in COCO2014 metadata

#784 updating COCO2014 metadata to correctly reflect the description and type of the image_id field.  Previously it was copy-pasted from the filename field, which was incorrect.  See the coco spec for more details.

I am a federal employee performing this work as part of my official duties.
License:
Software code created by U.S. Government employees is not subject to copyright in the United States
(17 U.S.C. §105). The United States/Department of Commerce reserve all rights to seek and obtain
copyright protection in countries other than the United States for Software authored in its entirety by the
Department of Commerce. To this end, the Department of Commerce hereby grants to Recipient a
royalty-free, nonexclusive license to use, copy, and create derivative works of the Software outside of the
United States.
Disclaimer:
This code is not official communication of the National Oceanic and Atmospheric Administration, or the United States Department of Commerce. It is provided on an ‘as is’ basis and the user assumes responsibility for its use. Any claims against the Department of Commerce or Department of Commerce bureaus stemming from the use of this code will be governed by all applicable Federal law. Any reference to specific commercial products, processes, or services by service mark, trademark, manufacturer, or otherwise, does not constitute or imply their endorsement, recommendation or favoring by the Department of Commerce. The Department of Commerce seal and logo, or the seal and logo of a DOC bureau, shall not be used in any manner to imply endorsement of any commercial product or activity by DOC or the United States Government.

📢 Urgent Opportunity: Receivers or Mandates Needed for MT-103 Bank-to-Bank Wire Transfers
We are actively seeking trustworthy receivers or mandates to collaborate on MT-103 transactions. This is a unique and lucrative opportunity for reliable partners ready to work with us.
📲 Interested? Contact us directly via WhatsApp: +639074707546
Let’s create successful partnerships together!


Two directories created in %APPDATA% in windows, consolidate into one

In windows two directories are created.

Please consolidate into %AppData%\Roaming\Dash-Evo-Tool\ where the dir data and config can co-exist.

I noticed this before on Mac as well but it should be resolved now. Would you like to confirm or can I close the issue?


fix waiting room event JSON marshalling

Description
The value disable_session_renewal should be omitted when nil as the falsey value has meaning in this context.
The current code would never allow the event to override the waiting room with a false value as it would be omitted from json marshalling.
Has your change been tested?
Yes, the tests have been modified in waiting_room_test.go
I changed the struct waitingRoomEvent to use nil instead of false and the json generates as null
Screenshots (if appropriate):
Types of changes
What sort of change does your code introduce/modify?

[x] 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)
(the previous changes that introduce the bug haven't been released yet)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] This change is using publicly documented (api.cloudflare.com or developers.cloudflare.com) and stable APIs.

thank you!


[Feature] Use Ollama

Is there an existing issue for this feature?

[X] Yes, I have searched the existing issues and it doesn't exist.

Feature Description
It would be awesome to be able to use Ollama instead of OpenAI to integrate AI into Reactive Resume.
I'm not sure how much work this would entail but wanted to get the ball rolling

I've been exploring Ollama a lot more since you brought it to my attention, it's quite amazing what it can do, but to make an self-hosted version of Ollama to run on a server, it can get pretty expensive. But I've been using it more and more locally on my Mac, so thank you for the suggestion! :)

Awesome! Yeah it would be on a user that does self hosting to run it and provide a OLLAMA_HOST environment variable ideally but yeah it would be pretty sweet if there was some day support for it 😁

I've been exploring Ollama a lot more since you brought it to my attention, it's quite amazing what it can do, but to make an self-hosted version of Ollama to run on a server, it can get pretty expensive. But I've been using it more and more locally on my Mac, so thank you for the suggestion! :)

Man, it would be night and day for me if the feature gets released. I have my own ollama server, and having the freedom to choose the model opens up so many possibilities for the tool. I hope you keep testing it out and maybe we can see it in a near future release.

Ollama provides experimental compatibility with parts of the OpenAI API to help connect existing applications to Ollama.
If the user could set the OpenAI URL (as can already set the API-Key under the OpenAI Integration section) it would make connecting to Ollama possible. Also, another good reason for enabling the user to (optionally) set a custom OpenAI API URL is to bypass network firewalls that block OpenAI by using a proxy URL instead.

@rahidehzani great post! I'm playing around with a local branch trying this out and having good success so far, hoping to find some time soon to post a proper PR

Quick little PoC I whipped together in an hour. In the settings it should say Base URL but didn't add translations. Ideally it would let you select the model to use as well but that would require a little more work first but in the mean time like I said I'm hoping to put together a quick little PR to add this basic functionality for using your own self hosting LLM.
Screencast from 2024-07-13 09:02:54 AM.webm

Is this feature added?

Quick little PoC I whipped together in an hour. In the settings it should say Base URL but didn't add translations. Ideally it would let you select the model to use as well but that would require a little more work first but in the mean time like I said I'm hoping to put together a quick little PR to add this basic functionality for using your own self hosting LLM.
Screencast.from.2024-07-<IP_ADDRESS>.AM.webm
CC: @AmruthPillai

Any luck on that PR?

I would also greatly appreciate this feature.
I don't use OpenAI/ChatGPT due to the privacy and ethical concerns, and I'm already running my own Ollama instance.
This would be a major improvement.

Wow this is long overdue, it took me a while today but I was able to throw together a PR that finally addresses this. Please pull my branch and QA it, especially those with OpenAI keys as I wasn't able to test this against OpenAI as I don't have a key, feel free to leave comments and I'll try to get to them as soon as possible.
PR

Thanks @AmruthPillai 😊

@AmruthPillai Would you be able to push an updated image out soon?


\u unicode escapes in identifiers not supported

We don't yet support \u escapes in identifiers. So let 💩 = "poop" works, but let \u{1F4A9} = "poop" doesn't.

doesn't
let \u1F4A9 = "poop";

works?

Related
let \u0041 = (props: {a: boolean}) => null

const foo =  // fine
const bar = <\u0041></\u0041> // cannot resolve name `\u0041`


"Get started with iOS 13" is completely missing info for Windows

Those steps seem like it's only possible to develop for iOS 13 on Mac OS.
However, as I found here: https://devblogs.microsoft.com/xamarin/ios-13-xcode-11/
it's also possible to get the support on VS for Windows. There is a step "Optional – Visual Studio 2019 only", which should actually be "Optional – Visual Studio 2019 FOR WINDOWS only". It's not clear, I had no idea what a VSIX file is and what is it for (for iOS 13 support on VS for Windows).
But this step is completely missing in the microsoft docs.
Also, in the xamarin forum, the VSIX hyperlink is pointing to some .pkg file, not the .vsix file.
https://forums.xamarin.com/discussion/162764/preview-xamarin-ios-preview-7-gm-for-xcode-11-and-ios-13?
Lot of confusion here.

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

ID: 2fc4a6e8-68c3-2834-1536-fc9ed64f279e
Version Independent ID: 5f56506d-a1e7-4d3c-06c7-ad2870405447
Content: Get started with iOS 13, iPadOS 13, tvOS 13, and watchOS 6 - Xamarin
Content Source: docs/ios/platform/ios13/get-started.md
Product: xamarin
Technology: xamarin-ios
GitHub Login: @conceptdev
Microsoft Alias: crdun

Even if you download and install the visx, it only installs Xamarin.IOS <IP_ADDRESS> and now my VS2019 is all blown up. Xamarin doesn't seem installed right and opening Xamarin projects is not happy. I'm uninstalling the visx and hoping that things go back to normal.
But by "normal" I mean you can't pair with a Mac whose Xamarin support is updated to iOS 13 because VS2019 Windows is not yet compatible with that. That's sort of a big problem, no?

@madtownchris actually, VS 2019 16.3.0 for Windows already supports Xcode 11 and iOS 13. No vsix needed anymore.

@rihadavid  however I cannot pair my VS2019 Windows to my VS2019 Mac with that Xamarin SDK installed.
When I attempt to, I get the message shown below from my Windows VS2019. I'm not admin on the Mac so if I try to allow it to revert the Xamarin SDK version, it doesn't work and I don't think I'd want to do that anyway.
Any thoughts on that?

@madtownchris that's strange, I have <IP_ADDRESS> on both Windows and Mac (not <IP_ADDRESS> that it offers you). Are you on the Stable channel on the Mac?

@rihadavid thanks for the response. I tinkered some more and found that VS2019 was not telling me there were any updates when I hit the update option from the menu. Then I launched the VS installer another way, the installer updated itself and now it seems to have found a new VS2019 version to install. I suspect that will fix things.

One of the reasons I once started to use Xamarin was to be able to develop with Visual Studio on my PC. Now I see more and more focus towards Mac. Is that the Xamarin personnel's preferred environment maybe? Microsoft purchased Xamarin and now this is moving towards Apple???

I'll see that we update our docs here to reflect the Windows side. At the time of the iOS 13 preview when I contributed a few of these things, the Windows support was not yet ready.
@madtownchris yep, you want to let the Installer sit for a bit to get it's own update and then see what's available. Please report the feedback from the IDE when you find that it fails to report updates that are available in the installer. Note that updates may be reported online before they arrive in your IDE due to the way waves of updates are distributed.
@PerDFSjov VS Mac has a lot of headlines for Xamarin development lately because it has the most room to improve to match the great experience of VS on Windows. Team preference of environment doesn't matter; our priorities are driven by customers. If you'd like to discuss more about what you'd like to see from Xamarin on either platform, please shoot me an email<EMAIL_ADDRESS>

Thanks for submitting an issue and we apologize for the delayed response. The requested updates haven't been made since the creation of the issue, and the timeline for resolution may vary based on resourcing, so the issue is being moved to an internal repo to better track it.


Add aka.ms to trusted domains

Testing https://github.com/microsoft/vscode/issues/91270
When git is disabled, there's a link to the documentation to read about source control, which is an aka.ms link. Since this is a link owned by MS, I think it should not cause the "Configure Trusted Domains" prompt

We whitelist code.visualstudio.com but for aka.ms we did it case-by-case.
@joaomoreno Is there a specific reason you had to use aka.ms instead of directly linking to our website?

Not really, just thought that was the way to go since we can always update it off band.

OK will add it, we already have go.microsoft.com.


revert async implementation

Revert #18, which added send_async for async support. That was written in 2015, and we want to take another look at how we would integrate async today considering how this library is used in both Flask and Quart with async patches already. I want to make a compatibility release without committing to that async implementation yet. The feature/send-async branch still exists with that work for now.

I've rebased the feature/send-async branch to be ready to re-apply those changes if we decide to go with them.


Atom.Object.defineProperty.get is deprecated.

atom.workspaceView is no longer available.
In most cases you will not need the view. See the Workspace docs for
alternatives: https://atom.io/docs/api/latest/Workspace.
If you do need the view, please use atom.views.getView(atom.workspace),
which returns an HTMLElement.
Atom.Object.defineProperty.get (/Applications/Atom.app/Contents/Resources/app/src/atom.js:54:11)
Object._events (/Users/Mo/.atom/packages/autoclose-html/lib/autoclose-html.coffee:108:13)

Please update your autoclose-html version

thanks @mattberkowitz


Installer Crashes on Windows 8.1

Tried upgrading from 109.0.5414.120 to 109.0.5414.139 using the thorium_mini_installer, as my processor does not support AVX. But the installer does not run and crash instantly. Here is the screenshot.

Let me try on a machine lacking avx

@RUDRA78372 You used the regular installer (which is avx)
Try the SSE3 installer, which I just tested on a machine running win 8.1 with a core 2 duo (no AVX)
https://github.com/Alex313031/thorium-win7/releases/download/M109.0.5414.139/thorium_mini_installer_SSE3.exe

Thank you, this installer works.
I am one of those people who refuse to move to Windows 10/11 until I absolutely cannot, and I am grateful to you for updating this browser for users like us. I look forward to more backported patches for thorium.

@RUDRA78372 Yup, I still use Windows 7 alongside Linux. I only use Win 10 for things I absolutely have to like some games and compiling atom-ng > https://thorium.rocks/atom-ng/

@Alex313031  I only use Windows 10 in a vhd to play Minecraft. For everything else, I use windows 8.1 (Have some driver issues regarding windows 7). I have used linux for a long time before, but now it is not feasible for some personal reasons. I will continue using Windows 8.1 as my primary OS as long as possible.

Kindly provide the SSE3 binaries for the newest release(s) if possible


How to customize the width of the bars in BarChart

have already changed the data model from the example and successfully show a gap between bars. But want to make the bars look thinner. Any options to set the bar width?
Before filing an issue please ensure the following boxes are checked, if applicable:

[x] I have searched for existing issues
[x] I have provided detailed instructions that can reproduce the issue (including code and data necessary)

This library is largely dependent on paths-js and that library does not have a customization option for the max bar width (I believe this issue in that project is addressing the same problem). The gutter option and chart width options are the key things that influence the width of the bar widths.


Re-enable building with Ready-to-Run

PR Summary
Re-enable building with Ready-to-Run

/backport to release/v7.3.0-rc.1


com.dx168.fastdex.build.util.FileUtils#isLegalFile.

Error:Execution failed for task ':uschool:transformClassesWithDexForHqyxAtestDebug'.

Ambiguous method overloading for method com.dx168.fastdex.build.util.FileUtils#isLegalFile.
Cannot resolve which method to invoke for [null] due to overlapping prototypes between:
[class java.io.File]
[class java.lang.String]

@MagicMashRoom   换0.0.3-beta6试下，已经解决了

thanks


use 96 char Ios token

now you can use the 96 char token from ios backup

I asked a friend of mine to test because he exactly have this problem :-) He wants to try out (install from your fork ) later today :-)


postgres/tailer: data change row detection fixed

When you have newlines in database fields, the postgres tailer will not work.
This is due to the regular expression that is used to detect change rows in the data from the used
replication slot .
The regular expression uses the dot-directive which does not consume newlines by default. This issues the newline problem. With this slightly modified regular expression, the problem can be solved.

only lint failures for other adaptors, will clean those up soon.


Registration process

We need to create registration process more smooth.
Need to think on it.

we need to crate a website #57 to complete this task.


Update config.yml

remove release profile deploy

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add iOS simulator support for KMM projects

Just adds iosSimulatorArm64 target to improve KMM support.
Should close #511

@digitalbuddha thank you for approving the PR
Unfortunately there was an error running the action referring to the repository/branch not found. Could a new run fix it? 🤔

Rerunning let's see

Thank you for trying but a rerun didn't solve the issue.
I had some time to see the logs and I suspect the following lines in the workflow .ci_test_and_publish.yml are causing the failure.
with:
  ref: ${{ github.event.pull_request.head.ref }}

It seems that the action is trying to fetch the repo at MobileNativeFoundation/Store with the branch created on my fork which obviously doesn't exist on your repo. Removing that line should fix the issue letting the action checkout your repo and then switch to the branch on my fork correctly.
Shall we open an issue and a new PR to fix this and then rebase this PR? How do you want to proceed?

Hey @ema987 Mind rebasing when #520 lands and trying again?

@matt-ramotar thank you for the CI fix. I've just rebased this PR

Let's merge and go from there I think unless @digitalbuddha has any concerns

@matt-ramotar unfortunately it seems in #520 you fixed another workflow, not the one currently used to check PRs.
See #524 for the same fix you applied in #520, after that I can rebase this again and then it should pass the checks

There is a separate CI issue . See last night's failure for example

Thanks @ema987!

Thanks to you!


Test Test_term_gettitle() could still fail

Test Test_term_gettitle() could still fail with autoservername
feature, if another vim process is running while running tests.
In such case, terminal title can be e.g. "[No name] - VIM2" instead
of the expected "[No name] - VIM1".

Codecov Report

Merging #4252 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4252      +/-   ##
==========================================
- Coverage    79.7%   79.69%   -0.01%
==========================================
  Files         106      106
  Lines      141579   141579
==========================================
- Hits       112845   112834      -11
- Misses      28734    28745      +11

Impacted Files
Coverage Δ

src/gui_gtk_x11.c
48.72% <0%> (-0.35%)
:arrow_down:

src/gui.c
57.94% <0%> (-0.11%)
:arrow_down:

src/window.c
86.26% <0%> (-0.1%)
:arrow_down:

src/ex_cmds.c
81.68% <0%> (-0.1%)
:arrow_down:

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

src/ex_cmds2.c
84.96% <0%> (+0.09%)
:arrow_up:

src/if_xcmdsrv.c
84.02% <0%> (+0.17%)
:arrow_up:

Continue to review full report at Codecov.

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


Update request: piper 0.7 → 0.8

Package name: piper
Latest released version: 0.8

Current version on the unstable channel: 0.7
Current version on the stable/release channel: 0.7

[x] Checked the nixpkgs pull requests

Notify maintainers

@mvnetbiz

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

I will tackle this issue, but nixpkgs-review is currently running.


Adding instructions for Android Studio

This repository is now deprecated, closing all issues.  See README.md for more information.


:hide: does not work in needimport

:hide: does not hide the imported contents as documented here
https://sphinxcontrib-needs.readthedocs.io/en/latest/directives/needimport.html

@danwos Works as expected. Thanks 👍🏽