datmo task run should designate environment being used

First line of task run should be messaging that tells the user the location of the dockerfile/env or the environment ID that is being run.
If a user does a task run with no environments setup, it uses the docker file from the repository if available. In this case, you should also write a line that says that you created a datmo environment for the user that will automatically be used in future runs. This is important because if the user is unaware of this, and they do task runs after editing the Dockerfile that they brought, these changes are not automatically tracked by datmo, since datmo prioritizes the copy made in the datmo_environments directory.

This is related to #194. In order to do this we will need to add a files attribute to the environment entity. This will then allow any command that uses environments to list the exact paths to the files that make up the environment that are being used. In this way the user can locate, update, or view the environment files that make up the running environment

Closing this issue and creating a new one that is more up to date


Fixed Typo in QuickStart-GettingStarted.md

Thanks for submitting a pull request! Please provide enough information so that others can review your pull request:
Fixed typo.

By analyzing the blame information on this pull request, we identified @JoelMarcey and @hramos to be potential reviewers.

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

@denniske Once you sign the CLA, I will accept and land this. Thanks.

@JoelMarcey Signed it. Do I have to upload the PDF here?

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

@denniske Nope. All good.

@denniske Actually, we want this to go into master, not 0.27-stable. Can you make this PR be merged into master?


[CSPM Content Collections] for 24.6.1 by AN.

This PR contains updates for -
[CDEM Documentation] Update documentation for Regex snooze feature
[CDEM Documentation] - Update Vulnerability sidecar & Top Risks widget

Please always provide the [GitHub issue(s)](../issues) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #
Test URLs:

Before: https://main--prisma-cloud-docs--hlxsites.hlx.page/
After: https://--prisma-cloud-docs--hlxsites.hlx.page/
Worker: https://prisma-cloud-docs-production.adobeaem.workers.dev/?branch=
RLP-140581

Thanks for the review @jenjoe22 .
I can see the image in the preview link. Not sure why it didn't load for you.
Regarding your question about the abbreviation CDEM, there is no "Cloud" mentioned on our PC console. To retain consistency btw the UI and docs. So, I decided to drop the word "cloud" in CDEM topics. I even asked the PMs about changing the abbreviation to DEM; they were not open to it and wanted CDEM.


use defmt logging

Quote @japaric from internal chat:

right now the workshop uses the log crate + core::fmt (uncompressed, uncolored logs).
because the workshop also demoes cargo-embed and cargo-flash (which don't support defmt) the board support crate in the workshop material needs to support both log and defmt. I think adding a Cargo feature to the dk board support crate to switch between log and defmt would be the way to go here.

(+1 to that)

a blocker here is char support in defmt; that type is used in the beginner workshop. Support for core::time::Duration would also be nice to have.
defmt 0.1.x doesn't support formatting the char type. defmt 0.2.0 will, though.

a blocker here is char support in defmt; that type is used in the beginner workshop. Support for core::time::Duration would also be nice to have.
defmt 0.1.x doesn't support formatting the char type. defmt 0.2.0 will, though.


Serializing/Deserialzing Large Arrays - Length header size is larger than buffer size

Please consider the following code, which crashes upon deserialization with the message: "MemoryPack.MemoryPackSerializationException: 'Length header size is larger than buffer size, length: 100000.'"
[MemoryPackable(GenerateType.VersionTolerant)]
public partial class Tester2
{
    [MemoryPackOrder(0)]
    public double[] Vs { get; set; }

    public static void Test()
    {

        var t2 = new Tester2();
        t2.Vs = new double[100_000];

        byte[] bytes;
        using (var writer = new MemoryStream())
        {
            var mp = MemoryPackStreamingSerializer.SerializeAsync(writer, 1, new[] { t2 });
            mp.GetAwaiter().GetResult();
            bytes = writer.ToArray();
        }
        using (var reader = new MemoryStream(bytes))
        {
            var mp = MemoryPackStreamingSerializer.DeserializeAsync<Tester2>(reader, options: MemoryPackSerializerOptions.Utf8);
            var result = mp.ToBlockingEnumerable().First();

            if (!result.Vs.SequenceEqual(t2.Vs))
            {
                throw new Exception();
            }
        }

    }
}

What am I missing?

thanks, it is about MemoryPackStreamingSerializer's window size.
StreamingSerializer allocate buffer in default bufferAtLeast = 4096, int readMinimumSize = 8192.
This large array's single block size is 800000 so require to expand window size.
var mp = MemoryPackStreamingSerializer.DeserializeAsync<Tester2>(reader, bufferAtLeast: 810000, readMinimumSize: 1600000, options: MemoryPackSerializerOptions.Utf8);.

Thanks @neuecc - the problem with this is that in production, I don't know the size of the data in advance - so I don't know what size to put for bufferAtLeast or readMinSize.
For example, a user may have serialized something that's 20 doubles long - or 200,000k doubles long - and I want it to work for either case without penalizing the 20-double user.
At the moment I'm deserializing the entire Stream to byte[], and then calling MemoryPackSerializer.Deserialize - but this means reading the entire object graph (which may have many large arrays) into a huge byte[]. So upon deserialization, I have a byte[] version and a deserialized object graph version, for about double the memory.
Ideally the deserializer would be able to resize/allocate a larger buffer as necessary based on the data coming in. This would minimize the peak memory usage.
Did I explain the scenario properly? Is there another way to accomplish this?

While double[] is easy and its size can be calculated, some data structures have unknown block sizes.
You need to decide the maximum capacity of a single item.

Ah I'm so sorry - I was using the wrong method. I should have been using MemoryPackSerializer.DeserializeAsync(Stream). I really shouldn't have been using MemoryPackStreamingSerializer in my scenario.
Thank you so much for this incredible library!


Improve error message when pdftotext is missing

Currently, when pdftotext is not installed, we get this error:
% python -m invoice2data.main ~/new_boite/pdf-invoices/test/sfr-facture.pdf
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/home/alexis/new_boite/dev/invoice2data/invoice2data/main.py", line 96, in <module>
    main()
  File "/home/alexis/new_boite/dev/invoice2data/invoice2data/main.py", line 84, in main
    res = extract_data(f.name, templates=templates)
  File "/home/alexis/new_boite/dev/invoice2data/invoice2data/main.py", line 23, in extract_data
    extracted_str = pdftotext.to_text(invoicefile).decode('utf-8')
  File "invoice2data/pdftotext.py", line 13, in to_text
    stdout=subprocess.PIPE).communicate()
  File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1340, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory

But this error message doesn't give a clue about the cause of the problem. We should try to improve that if possible I think.

I was thinking if we could use imp to check if the package is installed in the system?

img seems to deal with Python packages, rather than binaries. So using shutil.which seems more appropriate. I'll add it when I do my next batch of accounting in a few weeks.

Thought I'd fix this in the old year.


tt-rss

Make multi-arch
generate env variables automatically for chart
provide standalone version

Hi @angelnu do you plan on creating a chart?

ohh - sorry, I intend to create new charts. This issue was for my own repo - sorry that it got pushed here @onedr0p . Cleaning up...


Don't make assumptions about page size

We currently assume the page size to be 4096 bytes, which is reasonable. However, the kernel itself is mapped using huge pages, which is obviously larger than 4KiB.
While there haven't been any observed effects from assuming the page size, even more dangerous is the fact that we modify PAGE_HUGE when mapping over an existing mapping, possibly destroying the existing kernel mapping.

The rationale for this no longer holds true. Originally the kernel was mapped using huge pages, but we no longer do that (or even support huge pages).
At this time, I do not have plans to support huge pages. I do not anticipate Quark needing to run applications that require huge pages such as certain databases or compute-intensive programs in the forseeable future, so there is very little point in putting in the time for that when there are waaaaay too many other issues to deal with.
So, for now closing this issue, reopen if this ever becomes needed.


Tests for  WFFHCOHORT-6

These are the test tweaks for  WFFHCOHORT-6.
The MeasureCLI output format changed  in my PR, so I updated existing tests. I  also  added in a test  to run  multiple  measures in a single call and tested out the ability to overwrite the Measurement Period using parameters.

Related to update in https://github.com/Alvearie/quality-measure-and-cohort-service/pull/34

Rebased these test changes onto the latest version of my main branch. My plan is to include these changes in my main branch/PR once folks get a change to look these over.

Rebased these test changes onto the latest version of my main branch. My plan is to include these changes in my main branch/PR once folks get a change to look these over.


Defense NPCS Agent Closes Randomly

I have a Python script where I train a multi-agent reinforcement learning model in the HFO environment, with two model controlled offensive agents, and one hardcoded goalie. In the script, two separate processes are launched which control the individual agents. At random times, the goalie (using the default Agent2D team) crashes giving the following error:
Something necessary closed (defense_npc_1), [exiting]
From what I see this error is thrown when HFO checks to see if all processes are live.
Prior to this there are no errors, and everything appears to work. I have had this occur randomly, sometimes after 10 episodes, sometimes after 1000. The specific HFO launch command is
./bin/HFO --headless --frames-per-trial=500 --untouched-time=500 --fullstate --offense-agents=2 --defense-npcs=1 --no-logging

For each team, there is a player.conf file. Inside that file, there is a setting called "server_wait_seconds". The default value for that setting is 5. That's why the agent will close if your single move takes more than 5 seconds. Set a larger value will resolve this problem. BTW, the files related to teams are under bin/teams/.

Ok so I tried using offense-npcs and there was no error. One thing I am noticing is that the error usually appears when my agents take a while to make a move (for example when the policy is being updated). Is it the case that if the environment is not stepped for ~5 seconds, that the defensive agent might close?

Hi Suraj, for each team, there is a player.conf file. Inside that file, there is a setting called "server_wait_seconds". The default value for that setting is 5. That's why the agent will close if your single move takes more than 5 seconds. Set a larger value will resolve this problem. BTW, the files related to teams are under bin/teams/.


Change from ExpressRoute to AS Path is not working

Seems simple enough, but it doesn't work.  I have a S2S and ER connection to a VWAN Hub.  I want to take the VPN to be the best path to the on-premise network.  I AS-prepended prefixes advertised to the ExpressRoute so it would have a longer AS Path vs. the S2S VPN.  I looked at the Effective Routes table and it still has the ExpressRoute as the next-hop.  I checked the BGP learnedRoutes table and the hub receives both prefixes and the S2S next-hop has indeed a shorter AS Path. While I'm working with support, I may just switch the preference to VPN.

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

ID: a41b5bee-87c0-f641-1849-a16b8f4622b9
Version Independent ID: a627358e-fad1-1d01-aeff-4c81775f67a8
Content: Configure virtual hub routing preference: Azure portal - Azure Virtual WAN
Content Source: articles/virtual-wan/howto-virtual-hub-routing-preference.md
Service: virtual-wan
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

@charyampgonia
Thank you for reaching out. Can you please share the support ticket number with us? As we primarily monitor this channel for documentation update and based on the resolution we will determine if any documentation update can be made. Thank you!

@charyampgonia
Just following up. Can you please share the support ticket number with us?

@charyampgonia
Since we did not hear back from you. We will now proceed to close this issue out. Please tag me in your response and we will gladly continue with our discussion. Thank you!


[Enhancement] modify start and stop scripts for cn gracefully exit

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Add graceful option for stop_cn.sh
Make starrocks run as pid 1 in container, let CN handle signal from container manager.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[x] I have added user document for my new feature or new function

run starrocks_admit_test

@Mergifyio backport branch-2.4

@Mergifyio backport branch-2.3


Bump go to 1.23.1

Fixes tests that require 1.23.1

Assuming it gets merged, we should revert https://github.com/replicate/cog/pull/1953 as part of this PR.

I have no idea why golangci-lint is exploding under go 1.23 and not 1.22. For the moment #1953 has got main releasable again, but we should understand and fix this at some point.


Update Readme

Codecov Report

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

@@           Coverage Diff           @@
##           master       #3   +/-   ##
=======================================
  Coverage   69.72%   69.72%
=======================================
  Files          16       16
  Lines         109      109
  Branches       11       11
=======================================
  Hits           76       76
  Misses         31       31
  Partials        2        2

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 dc82bbc...37285e3. Read the comment docs.


fix handling of wildcard routes

this should fix an issue where an error would be thrown when handling any wildcard route, due to them not having a match method

Any chance you could throw a test in there?


Add AWS Network Firewall

Add new Feature -> AWS Network Firewall – New Managed Firewall Service in VPC

Just saw that you already had it in your list, might have missed a reload on my end ;-)


what's the structure of AAlbert's classifier?

Hi,
Now I want to reproduce the experimental results of AAlbert and Mockingjay, but the detailed structure of the classifier after feature extraction has not been introduced in detail in the paper.
In the source code of Mockingjay, I found two classifier structures:
if self.model_type == 'linear':
self.classifier = LinearClassifier(input_dim=input_dim,
class_num=self.dataloader.dataset.class_num,
task=self.task,
dconfig=self.config['downstream']['linear'],
sequencial=False).to(self.device)
elif self.model_type == 'rnn':
self.classifier = RnnClassifier(input_dim=input_dim,
class_num=self.dataloader.dataset.class_num,
task=self.task,
dconfig=self.config['downstream']['rnn']).to(self.device)
The structure of AAlbert's classifier is only briefly introduced in the paper:

To measure the phonetic information, we train 2-layer phoneme classifiers,
2.Then, we obtain the force-aligned phoneme sequences, which contains 72 possible phone classes, with Montreal Forced Aligner
Besides, the model here is a linear classifier with a mean-pooling layer.

But I still can't know the specific structure. Could you please tell me the specific structure in the paper of AAlbert, or where I can find it? Thank you!

Hi,
I can answer the questions regarding Mockingjay.
In the Mockingjay paper, a feed-forward classifier is used for phoneme classification.
Its implementation can be found here, and we use these parameters.
In a latter work, we present a more standard setting for linear phoneme classification of Mockingjay. This setting considers a 1-layer linear classifier, on a phone set of 41 possible phone classes (proposed and used in the CPC paper written by DeepMind).
We evaluate TERA, Mockingjay and also Audio-ALBERT with this linear phoneme classification setting (Phoneme - LibriSpeech, linear, column):

You can also find the above result on IEEE Early Access (The arXiv of TERA is not updated yet with the above results).
IMO this latter setting will be easier to reproduce, since we support this task in our repo.
If you consider this setting, I believe it will also resolves your Audio ALBERT related questions.
I hope this helps,
Andy

Dear researcher, It turns out that the result in IEEE Early Access is much higher than the one in Arxiv. Is there any important modification being made?

Dear researcher, It turns out that the result in IEEE Early Access is much higher than the one in Arxiv. Is there any important modification being made?

Hi, in the IEEE Early Access version,
we change the input / pre-training features of TERA and Mockingjay from "fMLLR" to "80-dim log Mel",
also, on the downstream tasks we tune the learning rate (which we did not in the Arxiv version) and perform a more thorough training.

Dear researcher, thanks for the quick reply.
I also wonder how learning rate is set for different model Table 2. Did you just use a fix value, or search a best learning rate for different model thoroughly?

Hi, thanks for bringing up this question.
To clarify my previous response, I think changing from "fMLLR to 80-dim log Mel" and "perform a more thorough training" are the main contributors to performance increase, and not the learning rate tuning, as these tasks are not sensitive to the learning rate, below I will explain more.
At first, we tune the learning rate for every model,
however, we later find that these tasks we adopt are not sensitive to upstream model variations.
So in a way, you can view it as we tune the learning rate for each downstream task (rather than the upstream model).
Empirically, we believe the results we report for each model are the optimal result, given that the downstream model architecture remains the same. Training all converge to similar testing performance, despite the seed/trial/and or even learning rate, if you give the training enough update steps (what I meant by "perform a more thorough training"). Overall these tasks are very stable for training.
The tasks we considered include phone_linear, phone_1hidden, phone_linear_concat, timie_phone_linear, timit_phone_1hidden, timit_phone_linear_concat, speaker_linear_frame_libri, and speaker_linear_utter_libri, which I have set their default learning rates to the ones I found generally working well.
Andy

Thanks for your clear explanation!

Hi, sorry for the very late reply. I can answer the question for AAlbert.
The 2-layer phoneme classifiers is the same as Mockingjay paper. To clarify, The structure is here, which Andy is mentioned before.
Since we use different phoneme set for phoneme recognition tasks, so the result will be different. Please refer to Andy standard experiment. That will show more clear results to compare other models.
Then, linear classifier with a mean-pooling layer is for utterance-level speaker recognition task. The structure is here. Hope the explanation is clear.
PoHan


Plans to implement Funnel?

Feature request

Are there plans to implement support for tailscale's Funnel?
I can't actually use headscale, as the whole reason I'm using tailscale is that I can't do port forwarding, and thus, my running head scale server would be unreachable by all devices.
Using tailscale though, I find the Funnel useful, as I run a Nextcloud server, and want to share links to my files with people not on my tailnet.
It would thus be cool to have this feature in headscale, for those who can use it!

If I understand correctly one of the main Funnel features is the automatic mapping of a subdomain to an exposed service with automatic certificate issuing (using letsencrypt for user-provided domain).
I would certainly use such a feature if Headscale implemented it.

I guess it could be implemented via 3rd party services like ngrok. My favorite is cloudflare tunnel. It is free, cloudflared is open source and all you really need is a domain on cloudflare.

Yes, I want something like you mentioned @rallisf1 , but hosted on my own server, not a third-party service, that's why I'm actually using headscale instead of tailscale.

Yes, I want something like you mentioned @rallisf1 , but hosted on my own server, not a third-party service, that's why I'm actually using headscale instead of tailscale.

This would require a reverse proxy and a dns server. Reverse proxy is easy, I already run headscale behind caddy. You'd need some form of integration with headscale though to generate the config for the Funnels. The DNS server must be public facing, be set as the designated nameserver for the domain you own (different than the magicDNS domain) and also integrated with headscale. Most registrars require at least 2 nameservers though, plus it's hell of a lot easier to just use a 3rd party DNS service that provides an API, like cloudflare...

Reverse proxy, dns server, and a certificate manager (for https support) - all this should ideally be integrated into a single application. btw, the domain used for forwarding could be a 2nd level domain (or even deeper) so it should not be a problem to have only one NS for that.

Reverse proxy, dns server, and a certificate manager (for https support) - all this should ideally be integrated into a single application.

I am strongly against this. There are battle tested open source packages that will do a better job than any 1st party implementation, plus I bet there is no capacity to even consider that. Integration, docs and a docker-compose.yml for the lazy is all that it takes.

btw, the domain used for forwarding could be a 2nd level domain (or even deeper) so it should not be a problem to have only one NS for that.

true but that means exposing your internal domains to the internet and frankly I'd never do that, even when they point to 100.x.x.x IPs.

I just partially understand and accept your opinion - using proven tools is a good way, but nevertheless, we need a manager program that will

accept and store requests for exposing internal services
create subdomain records in the dns server
create a config section in the reverse proxy configuration
issue a new certificate for the subdomain created
monitor and keep updated all this stuff

It doesn't look like a trivial thing from my point of view.

I suggest to run Tailscale exit nodes on servers with public static IP-adresses.
Headscale would just push the necessary firewall rules for opening and forwarding ingress ports to the Tailscale exit node.
Lego can be used by Headscale to configure the primary DNS-server of your domain provider.
That way one only needs to rent a small VPS (1 vCPU, 512 MB RAM, 1 GB storage) to run an "Funnel" node.
For security reasons I suggest to run the TLS-server on your application servers instead of the tailscale exit node (in my opinion the Tailscale exit node is not a secure host because the server provider has access).

I am also interested in this feature.
While I am an IT person, I only have very basic networking knowledge (mostly just IPv4 basics).
We have a tech-related non-profit (NPO) - promoting/pushing Open Source Hardware - which rents a (virtual) server.
Personally I have a low-power-consumption mini server at home, behind a CGNAT. I need it to be publicly reachable, providing web-serving, SSH server, email-server and things like that, at some point. Most importantly though, I want to use it for "hosting" distributed services nodes, like Tor, IPFS and such. This same setup should then be used by others that are part of the NPO.
It would be nice to be able to host Headscale ourselfs, and allow all our members (for now me, for testing) to have their own public server at home, providing both fail-safety and backups within the organization in a distributed manner, as well as (probably most important) build consciousness amongst the members for what distributed means, what the benefits are, that it is possible to some extend already, and what is missing.
I understand maybe 50% of the conversation in this issue. I personally would like to have a section somewhere in the docu of Headscale, that deals with this topic, explaining that the exact feature "funnel" as it is in Tailscale does not exist, but ... "you can build something similar in different ways, for example ...".
What do you think?
I'd be happy to dummy-test such a section.

@hoijui it's not so much a technical problem as an economic one. For Funnels to work you either need a server with a public IP (2 of them if you want to host your own private nameservers) or 3rd party services (DNS + Proxy). Let's say you want to self-host everything. Although running a DNS and proxy is dirt cheap on resources, traffic is not and that's gonna be double than a normal web/application server because of tunelling remote connections. Economically it makes more sense to just host the damn thing you need in a VPS altogether and skip the VPN.
Tailscale (meaning the SaaS) makes money and can afford this service, most of us cannot.
Should there be a guide about it for those who don't care about the cost? Sure, but there are a gazzilion ways to accomplish this, thus there will still be people who want help with e.g. Apache and GoDaddy instead of Caddy and Cloudflare, and it will still not be an integration.

I understand that it is an economical problem, and thus Headscale can not provide it for its community. My NPO though, could provide it for its members, as we are a small community, and people accessing our servers would also be fairly limited .. meaning: in total, I could imagine it would not be a huge load on our server(s), to establish the incoming connections for our NATed server from our hosted server with the static IP.
If you say it is not possible/makes no sense to document how to do it anyway, because too complex/too many options, then.. well.. it is so. :-)

I propose an example "funnel" with my own stack, using Tailscale nodes and a TCP proxy to route traffic from a VPS towards a HTTPS reverse proxy on a Pi behind NAT. Traefik is said reverse proxy in both cases.
I also set the Pi to use the VPS as an exit node, so outgoing requests can also come from the VPS itself and not from my residential IP.
With the right DNS records and routings, this should allow you to host webservices. Automating this stack to spin up any service from any node in the tailnet is a harder story though... I'm not sure its aptness for the TOR/IPFS use case as @hoijui mentioned. Feel free to contact me for more discussions

ehh cool, thanks you for the article, @skedastically !

@skedastically FYI link times out for me right now.


[Core] In-memory cache with sliding window and capacity controls

As the number of features using the database is increasing, caching some entities might be worth it compared to exeuting a lot of queries (especially concurrently accessing the same data).
Implement a caching mechanism similar to .Net's MemoryCache with the ability to control entity expiration using a sliding window and per-instance capacity control. This way frequently retrieved entities would be kept in the memory for faster access.
When introducing the usage of this new cache, make sure that cache invalidation is also taken care of where necessary (such as commands modifying certain entities should require the associated cache(s) to reload the relevant data).

Implemented as part of #234 (#235).


post-handshake authentication implicit enablement breaks existing applications

With openssl 1.1.1pre8 the post-handshake authentication is explicitly enabled by openssl when
certificate callbacks are set according to SSL_CTX_set_verify manpage. That's an unexpected behavior for existing TLS1.2 applications (in this particular case it breaks python) which fail because:

server-side assumes that SSL_CTX contains information about client certs directly after the handshake and before any application data is exchanged.
client applications that only know to handle client cert auth during the handshake, but not when they are sending/receiving application data.
client applications that assume that OpenSSL asks for client cert password during the handshake.

A backwards compatible alternative (for tls1.2 apps) would be for applications to explicitly enable
post-handshake authentication via flag in SSL_CTX. That way applications written for tls1.2 will work as intended under tls1.3, while applications which can take advantage of post-handshake authentication will still do, but after explicitly enabling it.

I could see the SSL_VERIFY_POST_HANDSHAKE flag being repurposed for the client-side, but I'm thinking that might be a bad idea (unless I can be convinced otherwise).

I'm working on a patch that renames SSL_force_post_handshake_auth() to SSL_set_post_handshake_auth(), and it must be called if you want to do PHA, whether or not you have supplied a cert.

@nmav - will #6938 fix it?

@mattcaswell @nmav I verified Python's ssl module with PR #6938. PHA extension is no longer send and TLS client cert is available on the remote side.

I realized I replied on the PR instead. In case you were waiting for my reply, it looks good to me, and @tiran above verified that python's test suite works well with it!

Do I understand this change to mean that all clients which previously (automatically) allowed post-handshake client cert exchange will now have to explicitly enable that support?

Almost right. Previously all clients that had a certificate configured at the time of sending the ClientHello, automatically configured post-handshake certificate support.  Now they have to explicitly enable that support.

So even if SSL_CTX_set_client_cert_cb() is used on the client side - which kind of implicitly signals support for PHA, "I can provide a client cert on demand"  - you don't get PHA?

Correct. It doesn't really signal support for PHA - that function has existed for a very long time: well before TLSv1.3. So having PHA implicitly enabled may result it in being called at unexpected times.

Correct. I designed it to be implicit, based on existing configuration; but this caused more trouble than it's worth with existing applications (i.e. they broke), and for ABI compatibility, it was disabled by default.. Since this is a new feature 1.1.1, you have to explicitly turn it on. Remember, all previous 1.1.1 releases were beta releases, so the behavior of new features can change until the latest release.

I'm not concerned about the behaviour within 1.1.1, but compared to the current API.  I would say that a major use case of SSL_CTX_set_client_cert_cb() has always been on-demand provision on client certs in HTTPS configurations where they are not required on initial handshake, so it looks like a major API break.

I would say that a major use case of SSL_CTX_set_client_cert_cb() has always been on-demand provision on client certs in HTTPS configurations where they are not required on initial handshake, so it looks like a major API break.

Post-handshake authentication (PHA) has never been a feature - and this opt-in only applies to PHA. In handshake authentication can be done with TLSv1.2, and of course can happen with a renegotiation. But renegotiation is not possible in TLSv1.3. The real change here is the change from the TLSv1.2 way of doing this to the TLSv1.3 way of doing things.
The least breaking way of implementing this IMO is to have it an opt-in.

@notroj I was one of the developers who requested to change PHA for TLS 1.3. PHA broke several tests in CPython's test suit as well applications code. Tests and application relied on the fact that client certs are available after the handshake, when mandatory TLS client cert authentication has been enabled.
@mattcaswell 's change makes TLS client cert auth compatible with TLS 1.2. The new explicit opt-in for PAH makes it possible to use OpenSSL 1.1.1 and TLS 1.3 in application, that haven't been designed for TLS 1.3. IMHO it's a good thing.

Disabling PHA support in all clients by default still looks like a major error to me.  Disabling this support will break the relatively common HTTPS configuration for sites using client cert auth, where per-location (URI-path-based) authentication is required.  This is true unless and until we go around and re-enable it again in every HTTPS client, i.e. reverse this default the very hard way.  So far as I can tell, enabling PHA by default is completely harmless in HTTPS clients which configure certificates via SSL_CTX_use_certificate*.
Nobody seems willing to explain exactly what broke in Python here, but if "my test suite" broke is sufficient motivation for changing the default, then I'm unhappy to report that "my test suite also broke" - the Apache httpd test suite relies heavily on doing client cert auth post-initial handshake (since it is a complex and important mod_ssl feature) - and is thoroughly broken because of this change.  More details here<EMAIL_ADDRESS>

If those test suites were added for TLSv1.3 support in 1.1.1, then I don't think you can make the argument that this update broke those tests; as they were invalid once 1.1.1 (and TLSv1.3) was officially released.
PHA is a new feature on TLSv1.3, and while I'd personally prefer that it be "automatic", I'll deal with it not being on by default. In TLSv1.2 you had to explicitly start a new handshake/renegotiate in order to do certificate authentication based on URL, and many clients had broken TLS stacks that did not support secure renegotiation. Yes, secure renegotiation is not possible TLSv1.3 (one could argue that removing this broke those unit tests), and something else, TLSv1.3-specific, will have to be done.

Agreed, the reference point for comparisons here should be OpenSSL 1.1.0, not 1.1.1preN.

Let me chime in since I recommended making pha opt-in; I'm not very familiar with the code base so I'll be a little abstract. Openssl handles tls1.x (x<=2) authentication (rehandshake) transparently and servers could rely on openssl clients re-authenticating when asked. When going to TLS1.3 that re-authentication via PHA will not be transparent for existing clients (I guess browsers will be updated, but I believe Joe worries about other clients like curl, etc.)
What was the issue with the transparent PHA used in 1.1.1pre releases? The python issue was because the previous behavior made clients send their certificate during the session (post-handshake) but not during handshake. That meant that clients (in test suites) which were expected to be authenticated during handshake were seeing an unauthenticated session instead. That was solved by making PHA being opt-in for client apps.
One question is whether both concerns can be addressed, so both apache and clients are happy (on the high level it looks probable, by the pre-behavior and sending certificate during handshake if requested). However, what I think is the main question raised by Joe, is mainly whether the transparent re-authentication for clients is something worth of retaining. The benefit is that clients support re-authentication even under TLS1.3 the same way as before; the drawback is enabling an unwanted feature to clients who may never use it.
(IMHO having transparency is a good thing as it simplifies clients, though it enables a feature they may have never asked which has proven to be problematic in the past; my recommendation was mainly driven by the latter concern, however the transparency benefits were not obvious to me at the time)


Add recommendation for go 1.7.1

Closes #205
Signed-off-by: Bill Farner<EMAIL_ADDRESS>

Current coverage is 74.23% (diff: 100%)

Merging #226 into master will not change coverage

@@             master       #226   diff @@
==========================================
  Files            16         16
  Lines          1110       1110
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            824        824
  Misses          207        207
  Partials         79         79

Powered by Codecov. Last update 5f2239c...692a28a


Updated readme

Corrected the branch mistakes from #1767
Updated the readme for Dogecoin!
This can be used for consideration as it felt really outdated and less doge.
Changes:

Removed dead image links.
Updated Travis ci badge link to direct to the master branch and the new Travis website url.
Added Emojis to headers for clarity and to get the feel of dogecoin for newcomers.
Bolded some sub headers for clarity. e.g. block reward sections.
Code formatting.

We've merged the preceding PR, could you please rebase off 1.14.3-dev instead now and resolve the merge conflict?
Thanks!

I have cherry-picked your work and sanitized it manually in #1774 to not make this block release. Have used your original commit as a baseline and retained attribution to you.
Thank you for this contribution, we appreciate it! I will close this PR in favor of the sanitized one.


Does sidetiq work with Rails 4 and ruby 2 ?

I have the following worker:
class Updater
  include Sidekiq::Worker
  include Sidetiq::Schedulable

  recurrence backfill: true do
    daily
  end

  def perform(*args)
   ###
  end
end

When running Updater.perform_async, an exception fires:
NoMethodError: undefined method `recurrence' for Updater:Class

what's the wrong here?

+1 I did a fresh bundle and I got version 0.1.2


UnityException FindObjectsOfType

UnityException: FindObjectsOfType is not allowed to be called from a MonoBehaviour constructor (or instance field initializer), call it in Awake or Start instead. Called from MonoBehaviour 'EazySoundManager' on game object 'GameManager'.

Line 68 in EazySoundManager script
instance = (EazySoundManager)FindObjectOfType(typeof(EazySoundManager));

@LAVendeta @rameshporeddy Sorry for the delay, it was an extremely busy month and I could not work on it.
I will take a look into the issue and update you very soon.

any update on this?

Also waiting for update on this. On the meanwhile I just commented that line as I can't perceive any case where variable instance can be set to null while an instance of EZ is still there, and seems to be working without problems.

any update on this?

Restarting Unity makes the error go away. It started when I added Soundmanager to a GameObject to test something, after deleting it, it seems Soundmanager isnt properly destroyed.

The problem still persists


'id_loss' doesnt reduce at all

I am training hrnet-32 model from scratch on the BDD100k MOT dataset, but the id_loss doesn't reduce at all. It stays around 11 even after 10 epochs. Does anyone have any idea why?

reID is a classification task in this work. So it is difficult to reduce id_loss, especially with so many different IDs in a driving scene, which is the case in BDD100k MOT dataset.

Got it, reID is a crossentropy loss. Thanks !


Autocomplete is cluttered with uninstalled plugins

I raised this question in the chat before:

When I type fisher <tab> here's what I see:
aquaman  (Prompt)  help           (Show help)  ls              (List what's installed)  rm  (Remove plugins)  update  (Upgrade and update plugins)

Choices  (Plugin)  install  (Install plugins)  ls-remote  (List what can be installed)  theme-eden  (Prompt)

are these plugins/themes supposed to be there? I've tried them at some point, but then removed (so they don't appear in `fisher ls`)

@bucaran:

fisher should show you what plugins you can install, the same as fisher install.
Notice those plugins are plugins not currently installed.

First, fisher install <Tab> shows only the plugins that were installed and then removed, not just "plugins you can install" (which would be, for example fisher ls-remote's cached list).
Secondly, if I uninstalled some plugins, I don't want to use them and therefore I don't want to see them in autocomplete. Besides, I think autocomplete after typing just fisher  is useful only if it shows the available commands and doesn't mix it with some plugin names. I think it's against autocomplete-discoverability, especially for new users that may install and delete a lot of plugins to try them and then never find some of the cool fisherman commands through autocomplete.
And the last, what is the right way to cleanup the cache to remove these plugins completely?

@laughedelic Autocomplete shows you the plugins you can install (it learns these from stuff you have installed previously). If you install aquaman, and later uninstall it, fisher install <TAB> will aquaman will be in the autocomplete.

#257

Uninstalling a plugin does not necessarily mean I will never install it again

Sure, but these uninstalled plugins shouldn't have priority over other plugins that haven't been installed yet. In the old fisherman, I think there was a concept of disabled plugins — it was also confusing for me, but at least there was a clear distinction..

we could generate fisher [install]  completions from ls-remote's output instead of the current behavior

👍

fisherman follows the XDG spec

OK. ( To be honest, I haven't heard about XDG before I encountered fisherman "_ )

fisher [install]
fisher -h shows you all the cool commands you can use

I, personally, think that this implicit default install command is rather confusing and makes interface non-uniform.


WindGL

Hi,as a rookie ,I know less about WebGL, make a introduction for WindGL is prefect, I want to know the process  of frame

I'll do a blog post about how this works in the coming weeks.


Support for delta feeds (RFC3229+feed)

The If-None-Match header combined with the A-IM: feed header instructs
compatible servers to only send the feed entries that have been added or
changed since the feed was last updated. (As determined using the ETag sent
by the server which is later returned by the If-None-Match header.)
No other changes required than adding this header. Supported by ExpressionEngine, Textpattern, and Liferea. I’m working on adding support to all the major open source feed readers, and will submit patches to WordPress as well.

Interesting! Will merge once checks complete. Thanks!

Coverage increased (+0.006%) to 30.414% when pulling b4f6d79f4e81448c742a5f63f6c33cb5833ec647 on Aeyoun:patch-2 into c1f03a41e2c54be478a7359f17270cbe4cb5fe02 on akrennmair:master.

Coverage increased (+0.006%) to 30.414% when pulling b4f6d79f4e81448c742a5f63f6c33cb5833ec647 on Aeyoun:patch-2 into c1f03a41e2c54be478a7359f17270cbe4cb5fe02 on akrennmair:master.

Coverage increased (+0.006%) to 30.414% when pulling b4f6d79f4e81448c742a5f63f6c33cb5833ec647 on Aeyoun:patch-2 into c1f03a41e2c54be478a7359f17270cbe4cb5fe02 on akrennmair:master.

@Aeyoun hello! Do you have a link to any documentation about that standard? I'm supporting my own tiny RSS library in my blog, and I'm interested in any relevant standards (because, tiny or not, I'd like to support that kind of caching).


Use a non-alpha tagged defaultBaseImage image for ko builds

Tekton is currently using cgr.dev/chainguard/static as our defaultBaseImage. This recently has caused us problems as apparently in the 0.46 Tekton release the /etc/alpine-release is set to 3.18_alpha20230208 which is leading out security team to think this image contains alpha packages.
We are in a really awkward situation here as we cannot even rebuild easily as apparently the tags are not available outside of an agreement with Chainguard so without deep thought can only rebuild with "latest".
My ask here is...

Can we work with Chainguard so for "static" Tekton (and anyone) can use tags and stop use of "latest" without an agreement.
Can we use a tag that is non-alpha

Hey, thanks for raising this. Sorry I didn't see this earlier. I'm not sure why the /etc/alpine-release points to alpha, I'll look into that.
Secondly, there's currently no need for an agreement between Chainguard and Tekton to pull any available tag of static. There are currently 500+ tags for cgr.dev/chainguard/static, all of which should be accessible to anybody. I'm not sure where you got the impression that they weren't.
If you can identify a date that this last worked for you, you can pin to cgr.dev/chainguard/static:latest-20230301 (or whatever date) and that should work fine. You can also pin to any previous digest, if a previous digest worked for you.
I'll look into when alpine-release changed, and in the meantime you should be able to pin to an older version to unblock releases.

It looks like the change was made some time in early Feb:
# Cat file in image
function ccat() {
  crane export $1 --platform ${3:-linux/amd64} - | tar -Oxf - $2
}

$ ccat cgr.dev/chainguard/static:latest-20230207 etc/alpine-release
3.17.0
$ ccat cgr.dev/chainguard/static:latest-20230208 etc/alpine-release
3.18_alpha20230208

This happens because cgr.dev/chainguard/static tracks Alpine's edge repository (configured here), and I suspect around Feb 7/8 they cut a new release branch for 3.18 which edge tracks.
These Alpine-based Chainguard Images are a bit of a weird bird, since they depend on Alpine's packages and release schedules. This is a good example of where we don't have as much control/visibility as we'd like, and where changes outside our control can cause confusion downstream. I'm sorry about that.

Thanks @imjasonh -- skopeo list-tags docker://cgr.dev/chainguard/static indeed shows many tags we can use.
The pre-amble in the README here -- https://github.com/chainguard-images/images/tree/main/images/static -- led me to think we could only use "latest".

The pre-amble in the README here -- https://github.com/chainguard-images/images/tree/main/images/static -- led me to think we could only use "latest".

That's helpful to know. The intention of that wasn't to indicate that older tags aren't available for static, but that tags for older versions of "real" images (e.g., python, nginx) might be available by contacting sales.
Since static doesn't really contain any particular software in it by design, this isn't really appropriate. I'll remove that warning for static: https://github.com/chainguard-images/images/pull/412

/reopen
@imjasonh @afrittoli @pritidesai -- sorry to flag but really need help here
This is still causing us grief (and now an escalated version of grief) as it was never fixed. Could we please switch to using an image version with an alpine release instead of alpha. I'd create a PR but I've tried to look at the tags cgr.dev/chainguard/static and have no idea what I'm looking at and also don't understand how these images are getting built.

/remove-lifecycle rotten -- more housekeeping -- we really need this addressed.

/lifecycle frozen

@imjasonh @skaegi is this something we could fix for now by pinning a specific version of the static image on Tekton side and making a new patch release?

Yes, what is trigger the problem is the contents of /etc/alpine-release and /etc/os-release. The scanner that is giving us grief is clair based so this might also eventually be relevant -- https://github.com/quay/claircore/issues/923
... but I think even if clair had support we would still get flagged because of using an alpha release...
/tmp # STATIC_ID=$(docker create cgr.dev/chainguard/static:latest sh) && docker export $STATIC_ID | tar -xC /tmp/static
/tmp # cd /tmp/static
/tmp/static # cat etc/alpine-release
3.19_alpha20230901
/tmp/static # cat etc/os-release
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.19_alpha20230901
PRETTY_NAME="Alpine Linux edge"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://gitlab.alpinelinux.org/alpine/aports/-/issues"

Using
curl -H "Authorization: Bearer $tok" \
  https://cgr.dev/v2/chainguard/static/_chainguard/history/latest | jq

The last five releases of static:
    {
      "updateTimestamp": "2023-07-11T20:32:40.602Z",
      "digest": "sha256:6b35c7e7084349b3a71e70219f61ea49b22d663b89b0ea07474e5b44cbc70860"
    },
    {
      "updateTimestamp": "2023-08-10T17:44:41.743Z",
      "digest": "sha256:67a1b00e0134e2b3a614c7198a26f7deed9d11b7acad4d52c79c0cfd47a2eae7"
    },
    {
      "updateTimestamp": "2023-09-02T00:27:17.261Z",
      "digest": "sha256:a432665213f109d5e48111316030eecc5191654cf02a5b66ac6c5d6b310a5511"
    },
    {
      "updateTimestamp": "2023-09-28T00:23:34.6Z",
      "digest": "sha256:ef5add7fd46cf1ce7d33d6de517833ac5c7e749db9b15249f9c472a772f3af27"
    },
    {
      "updateTimestamp": "2023-10-30T23:01:43.037Z",
      "digest": "sha256:d3465871ccaba3d4aefe51d6bb2222195850f6734cbbb6ef0dd7a3da49826159"
    }

Checking the alpine version for each of them:
curl -H "Authorization: Bearer $tok" \
  https://cgr.dev/v2/chainguard/static/_chainguard/history/latest | jq -r | grep digest | awk '{ print $2 }' | sed 's/"//g' | while read aa; do \
echo "${aa}: $(crane export cgr.dev/chainguard/static@${aa} --platform linux/amd64 - | tar -Oxf - etc/alpine-release)"; done

I see that the switch to edge happened in September:
sha256:6b35c7e7084349b3a71e70219f61ea49b22d663b89b0ea07474e5b44cbc70860: 3.18.0
sha256:67a1b00e0134e2b3a614c7198a26f7deed9d11b7acad4d52c79c0cfd47a2eae7: 3.18.0
sha256:a432665213f109d5e48111316030eecc5191654cf02a5b66ac6c5d6b310a5511: 3.19_alpha20230901
sha256:ef5add7fd46cf1ce7d33d6de517833ac5c7e749db9b15249f9c472a772f3af27: 3.19_alpha20230901
sha256:d3465871ccaba3d4aefe51d6bb2222195850f6734cbbb6ef0dd7a3da49826159: 3.19_alpha20230901

We should pin Tekton builds to sha256:67a1b00e0134e2b3a614c7198a26f7deed9d11b7acad4d52c79c0cfd47a2eae7 instead of latest, and backport to LTS and rebuild as well.

This is required too for a full fix https://github.com/tektoncd/pipeline/pull/7366

As of yesterday, the default base is Wolfi-based, so this shouldn't be an issue.


Cache pod labels to minimize etcd writes

Looks fine now.  We can resolve the get_endpoint() issue later.


Home renaming

Coverage decreased (-3.1%) to 82.958% when pulling ceb94f834c1840d865f76f17d2e4c795cfff5287 on home-renaming into f1c666c9b51f2004fbff886e95f3b29beaef3bbe on master.


wait until finished translating process using load event

https://github.com/eggplants/deepl-cli/blob/ff3c7f4b6c204c2e628a9153f29b1bf6d9ae0814/deepl/deepl.py#L122
https://github.com/eggplants/deepl-cli/blob/ff3c7f4b6c204c2e628a9153f29b1bf6d9ae0814/deepl/deepl.py#L123

for i in range(r:=1000):
  if elm.loaded:
    break
  elsif i == r-1:
    raise err
  sleep(0.1)


NameError: name 'flash_attn_func' is not defined

When I execute the command python long_context_example.py, I encounter the following error: NameError: name 'flash_attn_func' is not defined.

I encounter the following error: NameError: name 'flash_attn_func' is not defined.

I can run it on my server. What is your transformer and flash-attn version? Did you follow the instruction in "Setup" of README?


Closing a web socket while in the process of connecting

Hi, I've recently run into a problem where I need to close the web socket before it has finished connecting.  Looking at the code in Websocket.disconnect() reveals this:
        switch (mStateManager.getState())
        {
            case CREATED:
                finishAsynchronously();
                return this;

            case OPEN:
                break;

            default:
                // - CONNECTING
                //     It won't happen unless the programmer dare call
                //     open() and disconnect() in parallel.
                //
                // - CLOSING
                //     A closing handshake has already been started.
                //
                // - CLOSED
                //     The connection has already been closed.
                return this;
        }

What I'm doing currently is to get the raw socket and call close() on it, which generally works, but sometimes doesn't.  Waiting for the OPEN to occur is another option, but if the network is really slow, it's really not ideal for my purposes.  Can we add some behavior to cancel the connection if it's in progress?

Isn't WebSocketFactory.setConnectionTimeout(int) applicable to your case?

Not in this case, because sometimes I have to immediately shut down all connections in response to other input.

Calling close() on the raw socket closes the raw socket. What does "sometimes doesn't (work)" mean? What do you expect to happen after close()? I'm sorry I don't understand well what behavior you expect yet.

Ah, sorry, when calling close(), the WebSocket object will sometimes continue to open (perhaps the socket hasn't been opened yet), and sometimes will fail to send a CLOSING and CLOSED state.

Thank you. I understood what you meant. Let me give some time to think about it.

@TakahikoKawasaki
So did you think about it since that day? 😉

Any progress on this?
Why can't we close the connection while the state is CONNECTING? Is there any reason I don't understand yet?


[Popover] Unable to remove overlay from popover

[X] The issue is present in the latest release.
[X] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

I'm trying to add the ability to add other functionality to occur before the popover closes. The Popover component adds an overlay which detects any clicks then triggers the setAnchorEl method (updates the state to null.
I have a close button which I want to perform some behavior prior to the popover closing.
Expected Behavior 🤔

I expect there to be some flag on the popover api like: hideOverlay, similar to the Menu component. This would allow me to trigger the handleClick related to the close button before setting anchorEl to null.
Steps to Reproduce 🕹

Here is a basic repl which simply console.logs the order of operations.
Steps:

open popover
click close button
notice the order in which the logs are performed

Context 🔦

Your Environment 🌎
https://codesandbox.io/s/759bb?file=/demo.tsx

Thanks for the feedback.
Could you be more specific what you mean by

before setting anchorEl to null.

You can handle all sorts of behavior in onClose. It's unclear what problem can't be solved with the current API.

@eps1lon , the onClose will close the dropdown. In the repl above, if the popover has a set value(that can be cleared), and I click on the close button, the popover will close, but the value will not be reset. I believe this is due to the overlay that gets added to the page when the popover is open.
I want to be able to simultaneously reset the value of the field and close the popover, when the close button is clicked. Any suggestions on how I can do that with the current Popover API? If it's not possible with the Popover api, what other Material UI component should I utilized for this sort of user experience?

I want to be able to simultaneously reset the value of the field and close the popover, when the close button is clicked.

What field do you mean? Could you highlight in your codesandbox what the "field" and its value is?

I updated the codepen
Here are the steps:

click on the blue popover
select an age in the select dropdown
click on the close button
the popover will close, but the age will not be reset.

Is there a way for me to both reset the age and close the popover with one click?

Is there a way for me to both reset the age and close the popover with one click?

You are controling the state of the value. All you have to do is:
 const handleClose = () => {
   // console.log("closing popover . . .");
   setAnchorEl(null);
+  setAge("")
 };

@eps1lon that will reset age every single time that the user clicks away. I only want to reset age, when the user click the close buttone. However, this doesn't seem possible as the Popover api adds a backdrop that overlays the entire screen.
Ultimately, I'm looking for a way to prevent the backdrop from overlay the entire screen when the popover is open. I have not seen anything in the material-ui documentation about how go about solving this issue.

@maksimgm Any solution?

Hey. I came across this issue while resolving quite a similar problem. I haven't found any solution using Popover, but you can achieve this with Popper.


Bug fix for resizable columns and draggable columns

This PR contains the following fixes:

Fix for making draggable columns work properly when there is a scroll offset on the table (ex: a table with 20 columns where one scrolls to the right to see columns).
Fix for resizable columns when certain columns are hidden. Also implements a better fix for selectableRows="none" (which was put into 3.3.0).

Coverage decreased (-0.5%) to 83.777% when pulling 7bc85ad2a04486ebbce25e357cf9bfdec830cbb5 on dragScrollFix into 3426f8d855e74127dde2b9260795c0ca7ca60958 on master.


Separate componenet and air trace writers.

This change is

#646
#644
#642
#639
#638
#637
#636
#651  👈
dev

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

Join @alonh5 and the rest of your teammates on  Graphite

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.49%. Comparing base (bedd93e) to head (cb15009).

Additional details and impacted files
@@            Coverage Diff             @@
##              dev     #651      +/-   ##
==========================================
+ Coverage   92.24%   92.49%   +0.25%
==========================================
  Files          69       69
  Lines        9050     9025      -25
  Branches     9050     9025      -25
==========================================
  Hits         8348     8348
+ Misses        629      604      -25
  Partials       73       73

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Settings not opening

Microsoft PowerToys version
0.55.2
Running as admin

[X] Yes

Area(s) with issue?
Settings
Steps to reproduce
Right click on the tray icon and click Settings.
✔ Expected Behavior
Settings window opening
❌ Actual Behavior
Settings window not opening
Other Software
No response

ERROR: 10:17:50.7064311
    [Method]: LoadProfile [Class]: KeyboardManagerViewModel
    Exception encountered when loading Keyboard Manager profile
Object reference not set to an instance of an object.
Inner exception:

Stack trace:
   at Microsoft.PowerToys.Settings.UI.Views.KeyboardManagerPage.CombineRemappings(List`1 remapKeysList, UInt32 leftKey, UInt32 rightKey, UInt32 combinedKey)
   at Microsoft.PowerToys.Settings.UI.Views.KeyboardManagerPage.FilterRemapKeysList(List`1 remapKeysList)
   at Microsoft.PowerToys.Settings.UI.Library.ViewModels.KeyboardManagerViewModel.LoadProfile()

cc: @yuyoyuppe FYI. Seems like #11000 #11718

This is fixed with 0.57.0. Please head over to https://aka.ms/installpowertoys


The database is the field where oracle partition_cloumn (id) is NUMBER; Size, scale 0, restapi submit-job error

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
{
"status": "fail",
"message": "ErrorCode:[API-01], ErrorDescription:[Configuration item validate failed] - PluginName: jdbc, PluginType: source, Message: org.apache.seatunnel.connectors.seatunnel.jdbc.exception.JdbcConnectorException: ErrorCode:[COMMON-06], ErrorDescription:[Illegal argument] - The current field is DecimalType containing decimals: 18 Unable to support"
}
SeaTunnel Version
2.3.3
SeaTunnel Config
{
	"env": {
		"parallelism": 4,
		"job.mode": "batch",
		"checkpoint.interval": 10000
	},
	"source": [{
		    "plugin_name": "jdbc",
			"url": "jdbc:oracle:thin:@xxx.xxx.11.181:1521:orcl",
			"driver": "oracle.jdbc.OracleDriver",
			"connection_check_timeout_sec": 100,
			"user": "xxx",
			"password": "xxx",
			"query": "select * from  table1",
			"partition_column": "id",
			"split.size": 10000

	}],
    "transform": [{
        "plugin_name": "Copy",
        "source_table_name": "xxxxx",
         "result_talbe_name": "xxxx2",
          "fields": {
               "id" : "xxxxx"
          }

    }

    ],
		"sink": [{
		"plugin_name": "Jdbc",
			"url": "jdbc:postgresql://xxx.xxx.11.xxx:5432/ptest",
			"driver": "org.postgresql.Driver",
			"user": "test",
			"password": "test",
			"generate_sink_sql": true,
			"database": "ptest",
			"table": "public.xxxx2",
			"schema_save_mode": "CREATE_SCHEMA_WHEN_NOT_EXIST",
			"data_save_mode": "APPEND_DATA",
			"primary_keys": ["id"]

	}]
}

Running Command
{
	"env": {
		"parallelism": 4,
		"job.mode": "batch",
		"checkpoint.interval": 10000
	},
	"source": [{
		    "plugin_name": "jdbc",
			"url": "jdbc:oracle:thin:@xxx.xxx.11.181:1521:orcl",
			"driver": "oracle.jdbc.OracleDriver",
			"connection_check_timeout_sec": 100,
			"user": "xxx",
			"password": "xxx",
			"query": "select * from  table1",
			"partition_column": "id",
			"split.size": 10000

	}],
    "transform": [{
        "plugin_name": "Copy",
        "source_table_name": "xxxxx",
         "result_talbe_name": "xxxx2",
          "fields": {
               "id" : "xxxxx"
          }

    }

    ],
		"sink": [{
		"plugin_name": "Jdbc",
			"url": "jdbc:postgresql://xxx.xxx.11.xxx:5432/ptest",
			"driver": "org.postgresql.Driver",
			"user": "test",
			"password": "test",
			"generate_sink_sql": true,
			"database": "ptest",
			"table": "public.xxxx2",
			"schema_save_mode": "CREATE_SCHEMA_WHEN_NOT_EXIST",
			"data_save_mode": "APPEND_DATA",
			"primary_keys": ["id"]

	}]
}

Error Exception
{
    "status": "fail",
    "message": "ErrorCode:[API-01], ErrorDescription:[Configuration item validate failed] - PluginName: jdbc, PluginType: source, Message: org.apache.seatunnel.connectors.seatunnel.jdbc.exception.JdbcConnectorException: ErrorCode:[COMMON-06], ErrorDescription:[Illegal argument] - The current field is DecimalType containing decimals: 18 Unable to support"
}

Zeta or Flink or Spark Version
Zeta
Java or Scala Version
java 1.8
Screenshots
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

What is the id field type for table1 ?   is number(18,0) ?

What is the id field type for table1 ? is number(18,0) ?
@hawk9821  thanks
The ID field of the table is of type number(0,0)

Problems with oracle data type conversion ， A conversion logic error caused the oracle number type to be converted to Decimal(38,18). The expectation should be Long

Problems with oracle data type conversion ， A conversion logic error caused the oracle number type to be converted to Decimal(38,18). The expectation should be Long
@hawk9821  thanks

Oracle table field ID number type size and precision set to 0, should not be converted to decimal(38,18), why is it converted to this, what special requirements, if this is limited, that  the column name for split data ,it  can  not be processed("partition_column": "id")

The oracle number data type can store float data without specifying the precision, so seatunnel is treated as float and converted to Decimal(38,18).   Change table field ID data type to number(x,0)


Fix breaking changes in FastBoot 1.0

The current ember-cli-fastboot releases (1.0.0-rc.1 and above) introduce breaking changes. These will most likely break your current FastBoot implementation.
See https://github.com/ember-fastboot/ember-cli-fastboot/issues/387 for more information and a guide on how to fix your addon. Also you may want to visit the -fastboot Slack channel to get help from other users.
Note: this issue has been created automatically, by searching for certain patterns in your code. If you think this has been falsely created, feel free to close!

Hi, I've been using this addon happily with fastboot for some time but I'm now seeing this error.
It comes from here https://github.com/mike-north/ember-phoenix/blob/master/vendor/phoenix.js#L1025. Is it an older version of this? https://github.com/phoenixframework/phoenix/blob/master/assets/js/phoenix.js — not sure if this can be fixed by updating this vendor import.
'ReferenceError: ActiveXObject is not defined\n    at Function.request (/Users/oskar/Sites/xxx/player/tmp/broccoli_merge_trees-output_path-LSftJmM8.tmp/assets/vendor/phoenix.js:1025:1)\n    at LongPoll.poll (/Users/oskar/Sites/xxx/player/tmp/broccoli_merge_trees-output_path-LSftJmM8.tmp/assets/vendor/phoenix.js:953:1)\n    at new LongPoll (/Users/oskar/Sites/xxx/player/tmp/broccoli_merge_trees-output_path-LSftJmM8.tmp/assets/vendor/phoenix.js:919:1)\n    at Socket.connect (/Users/oskar/Sites/xxx/player/tmp/broccoli_merge_trees-output_path-LSftJmM8.tmp/assets/vendor/phoenix.js:697:1)\n    at Class.connect (/Users/oskar/Sites/xxx/player/tmp/broccoli_merge_trees-output_path-LSftJmM8.tmp/assets/addon-tree-output/phoenix/s

Also related to fix fastboot support: https://github.com/mike-north/ember-phoenix/pull/80


[TP]: Add missing message length for frame chunk callback

This PR is bugfix for messages being transported by data chunk callbacks using any transport protocol. Their message length was recognized as 0 due to the removal of CANLibManagedMessage in #255.
Changes:

Add frameChunkCallbackMessageLength to all transporting protocol session classes
Add utility function get_message_data_length to all transporting protocol session classes to determine the correct message length considering both data chunk callbacks and the normal copied message data.
Also changed the message length/indexes in CANMessage from size_t to uint32_t as it can't exceed the maximum message length of ETP: 117440505

Seems to throw an assertion for an out of range vector access here:

Seems to be because this for loop expects to add all the 0xFF bytes to the received message, but the message size is 9, not 14. 9 Is the correct length, so might need to add an additional check to this loop

gwndaan-10f89a0-TP_ETPHotfix.patch
@GwnDaan Here's a patch that should fix the noted issue

If you are busy, since this is a fairly high impact issue, I can merge this in and submit a fix on top of it


Upgrade plugin regarding of CVE-2021-44228

Can't  upgrade Elasticsearch to 7.16.1 as recommended by https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476, if this plugin is installed. Please upgrade the plugin.

Plugin upgraded


Add task to clean npm dependencies

make task for https://github.com/elastic/elasticsearch-specification/pull/990

Alternate suggestion: should setup-env automatically do this since they're no-ops on the initial setup?

@sethmlarson good call, I added the task to setup-env.
@delvedor , removed the deletion of lockfiles


socket.gaierror: [Errno 11001] getaddrinfo failed

Everything worked fine a week ago, but all of a sudden the audio pipe doesn't seen to be able to connect to discord.
socket.gaierror: [Errno 11001] getaddrinfo failed

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

Traceback (most recent call last):
  File "discord\client.py", line 558, in connect
  File "asyncio\tasks.py", line 442, in wait_for
  File "discord\gateway.py", line 305, in from_client
  File "discord\http.py", line 917, in get_gateway
  File "discord\http.py", line 185, in request
  File "aiohttp\client.py", line 1117, in __aenter__
  File "aiohttp\client.py", line 521, in _request
  File "aiohttp\connector.py", line 535, in connect
  File "aiohttp\connector.py", line 892, in _create_connection
  File "aiohttp\connector.py", line 1011, in _create_direct_connection
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host discord.com:443 ssl:default [getaddrinfo failed]
2021-02-07 20:58:38 Error on main
Traceback (most recent call last):
  File "main.pyw", line 136, in main
  File "discord\client.py", line 661, in start
  File "discord\client.py", line 561, in connect
  File "discord\gateway.py", line 587, in poll_event
discord.errors.ConnectionClosed: Shard ID None WebSocket closed with 4004

From what I can see, socket 4004 = Authentication Failed. On thing you could try is to regenerate a new token for your bot, and make sure there aren't any newlines and spaces at the end of the token, (i'll have to strip those out in a future release).

I regenerated the token, and made sure there aren't any newlines or whitespaces after it in the token.txt file. Does it matter if I previously kicked the bot from a voice channel?

The bot is failing to log in at all, so I don't think kicking the bot from one voice channel is causing the issue. Are you using the .exe or the source code? I have run into getaddrinfo failed before with #11 source code only, and updating to the latest discord.py with pip solved that issue.
But the strange thing is you've mentioned that it was working before. Try running:
curl https://discord.com/api/v8/gateway/bot -H "Authorization: Bot <Token>"
in a terminal and replace <Token> with your bot token. This will tell you if you've hit some rate limit.
If that doesn't work, the only other thing I can think of is that something changed with your firewall, and its blocking discord.com

This is what I got from curl:
{"url": "wss://gateway.discord.gg", "shards": 1, "session_start_limit": {"total": 1000, "remaining": 1000, "reset_after": 0, "max_concurrency": 1}}

I'm dumb. I had to add the bot to the server again via the OAuth URL. Derp. Got it working now, thank you for this awesome project!


Option.when() null confusion

shell> Option.when(true, () -> null)
$2 ==> None

That may be what we want (is it?). If it is what we want, maybe we should improve the apidoc, which currently states "Creates Some of suppliers value if condition is true, or None in other case".

Hi, thanks for the hint! The apidoc is ok, it was a bug. The current SNAPSHOT is already fixed. I will close this ticket.
(Behavior relates to #1180 and #1197)

Fixed here: #1272


File 'app/models/belief_disposition.rb' is automatically edited during setup

I am confused as to what part of the project would edit a schema comment on a model ruby file, but here's the diff
-#  id          :integer          not null, primary key
-#  is_public   :boolean
-#  belief_id   :integer          not null
-#  user_id     :integer          not null
-#  location_id :integer
-#  created_at  :datetime         not null
-#  updated_at  :datetime         not null
-#  is_filed_in :boolean
-#  disposition :string(255)      not null
+#  id           :integer          not null, primary key
+#  is_supported :boolean
+#  is_public    :boolean
+#  belief_id    :integer
+#  user_id      :integer
+#  location_id  :integer
+#  created_at   :datetime         not null
+#  updated_at   :datetime         not null
+#  is_trashed   :boolean
+#  is_filed_in  :boolean

Who made the change and when was it made?  Perhaps my notes / emails will help to explain it?

This is the last commit to touch the file I am referencing
https://github.com/Likeminded/Likeminded/commit/c67c39572818c6c8202cfeb2d9b8e78b0d21fdba


[proposal] Add a Link to install Sails.js Framework with Nginx as a Reverse Proxy on Ubuntu 20.04

[proposal] Add step by step instruction guide on "How to Install Sails.js Framework with Nginx as a Reverse Proxy on Ubuntu 20.04"

Hi @S-Stephen
I have added a Link to install Sails.js Framework with Nginx as a Reverse Proxy on Ubuntu 20.04, Please check it and merge the pull request.


Fix end to end tests

New behavior introduced by #150 requires end to end tests to be reworked.

https://github.com/halkyonio/operator/pull/157


Add some documentation

Show to use the system with some documentation or possibly a tour.

https://github.com/michaelmior/relational-playground/pull/402 resolved here


Add minimal tests, so CI will be meaningful

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@227ca5d). Click here to learn what that means.
The diff coverage is 0%.

@@           Coverage Diff            @@
##             master      #6   +/-   ##
========================================
  Coverage          ?   5.43%
========================================
  Files             ?       3
  Lines             ?      92
  Branches          ?       0
========================================
  Hits              ?       5
  Misses            ?      87
  Partials          ?       0

Impacted Files
Coverage Δ

public.go
0% <0%> (ø)

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 227ca5d...efe760c. Read the comment docs.


missing characters are treated as punctuation

some texts use glyphs like □ (WHITE SQUARE, U+25A1) to indicate locations where characters are missing, obscured or damaged. since glyphs like this are technically not alphabetic in the general sense, they are being treated as punctuation currently, which means matches can extend "through" them. using two of the sample fixtures:
$ dphon tests/fixtures/郭店/老子丙.txt tests/fixtures/郭店/老子乙.txt

shows:
天下。故 (老子丙: 3)
天下□□□□□□□□□□□家 (老子乙: 8)

presumably we want to handle □ (and maybe other glyphs) as a special case when forming initial matches.

added the CHAR_MARKERS global to keep track of glyphs that can be used for this purpose, and updated get_initial_ngrams() to take it into account. matches should no longer be made that contain any CHAR_MARKERS.


Add when context: isLastGroup / isFirstGroup / editorGroupIndex / isLeftGroup / isRightGroup / isTopGroup / isBottomGroup

This PR addresses #22755 by adding several context keys to support the configuration of keyboard shortcuts based on which editor group is currently active.

 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.:x: jaydenwindle sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

It is worth noting that in the current implementation, the isFirstGroup and isLastGroup context key values do not always correspond to the leftmost and rightmost editor groups visually. For example, when stacking groups vertically, the isLastGroup context key is set when the last opened editor group is active, instead of when the leftmost editor group is active.
For example:

In a similar vein as the context keys implemented in this PR, isLeftGroup and isRightGroup context keys would be very helpful for the originally mentioned use case. I would love any input on how those could be implemented as well.

Update: I've added an (albeit hacky) implementation for isLeftGroup and isRightGroup  context keys, as well as for isBottomGroup and isTopGroup.
Currently it works for the editor group configurations I've tested (see demo attached), but type casting to get access to the IEditorGroupView and then doing raw element getBoundingClientRect calculations seems much less than ideal. I'd love some tips on how to do this in a cleaner way.
Also, I haven't found a good way to write unit tests for these changes since there are some fairly complex editor setups that need to be tested. Any advice on how to proceed there would be amazing.
Demo: https://cl.ly/f0cdf8af9bc7

Thanks for the work but I ended up implementing this a bit different given some new support that I added recently. See https://github.com/microsoft/vscode/commit/406b1f385a54caca5b829b2b9c8f2617f0fff48f


Provide feedback on correct/incorrect answers

Hi,
This is a very nice extension! I'd like to provide feedbacks to my students if they check an incorrect answer to explain why they are mistaken (and ideally for correct answers as well, to give a bit more details), but I'm not familiar with revealjs plugins.
I guess that we could add attributes to spans, e.g., [Answer which is correct]{.correct explanation="This is correct"} and [Incorrect answer]{explanation="No because (...)"}, and then show them somewhere when an answer is clicked.
If you like this idea and can point me in the right direction, I will try to make a quick PR.
Thanks!

Thanks for the suggestion! The feature was pretty easy to implement, so I just went ahead and added it in.
I've added a data attribute called data-explanation and updated the README. Please let me know if  you have any issues.

Nice, thank you for the quick update! I can confirm it works perfectly.
(Plus, because the explanation replaces the "Correct!" / "Incorrect!" label, this opens up the way for Internationalization)

Note that I added defaultCorrect and defaultIncorrect settings you can use to change the change default correct and incorrect messages. The README is updated with how you can use those.


disable network for RUN; use only ADD to get network things, use advanced syntax for cases that need ADD git

Second part of #2861 now that #2911 is in.
This removes network access for RUN commands in all packages except for pkg/kernel, pkg/new-kernel, pkg/acrn-kernel, as those take a very long time, so should be in their own PRs (coming once this one is in).
Runs all of the package builds with --network=none, causing any network installs to use ADD. Since this is predictable and consistent, we can scan it for network dependencies with ease, building our bill of materials.

I am afraid that I do not understand the eden errors.

The error from the app instance error from network instance: can't run meta-data server on eth0: no bridgeIP looks strange. But I am not sure that it is related.


lightGallery hash url doesn't work

If you use the shared url like https://websitebase.github.io/#lg=1&slide=0 the plugin doesn't open properly.
The error is:
TypeError: b.core.$outer.find is not a function

I think is because the slide function only works when the gallery is already loaded.

This was caused because the "destroy" function was initialized on document ready. Now the destroy function is loaded only on ajax start event.


The id is not given to UMD package.

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => https://github.com/ngxs/store/blob/master/CONTRIBUTING.md
[x] Other... Please describe:

Current behavior
Regarding the distributed files of the npm package.

https://www.npmjs.com/package/@ngxs-labs/emitter

<EMAIL_ADDRESS>
(function (global, factory) {| (function (global, factory) {
    typeof exports === 'object' && typeof module! == 'undefined'? factory (exports, require ('@ ngxs / store'), require ('@ angular / core'), require ('rxjs / operators') typeof exports === 'object' && typeof module! == 'undefined'? factory (exports, require ('@ ngxs / store'), require ('$
    typeof define === 'function' && define.amd? define (['exports', '@ ngxs / store', '@ angular / core', 'rxjs / operators'], factory): | typeof define === 'function' && define.amd? define (['exports', '@ ngxs / store', '@ angular / core', 'rxjs / operators'] $
    (global = global || self, factory ((global ['ngxs-labs'] = global ['ngxs-labs'] || {}, global ['ngxs-labs']. emitter = {}), global. ngxs.store, global.ng.core, global.rxjs.operators)); | (global = global || self, factory ((global ['ngxs-labs'] = global ['ngxs-labs'] || { }, global ['ngxs-labs']. emitter = $
} (this, function (exports, store, core, operators) {'use strict';

The ID that recognizes package is not passed when defining with define function. For this reason, the following error occurs when launching a bundled application in Angular with AOT compilation (ngxs-labs-emitter.umd.min.js works correctly)
Current state:

define (['exports', '@ ngxs / store'...

Expected state:

define ('@ngxs-labs/emitter', ['exports', '@ ngxs / store'....

From browser console error:

Uncaught Error: Mismatched anonymous define() module: function (exports, store, core, operators) { 'use strict';

The umd file is created from the github code using the yarn emitter: build command, the ID is correctly assigned, so there may be some problem in the package upload process.

What is your moduleResolution in tsconfig.json?

moduleResolution is node
I'm developing ngx app with based on Angular 8.3.14.
We are developing with a template using bazel created with the following command.

ng new --collection=@angular/bazel

$ cat tsconfig.json {   "compileOnSave": false,   "compilerOptions": {     "baseUrl": "./",     "outDir": "./dist/out-tsc",     "sourceMap": true,     "declaration": false,     "downlevelIteration": true,     "experimentalDecorators": true,     "module": "esnext",     "moduleResolution": "node",     "importHelpers": true,     "target": "es2015",     "typeRoots": [       "node_modules/@types"     ],     "lib": [       "es2018",       "dom"     ]   },   "angularCompilerOptions": {     "fullTemplateTypeCheck": true,     "strictInjectionParameters": true   } }


Move files from base directory to /src directory

This will make it easier for azure devops in the next round of changes.

@RolandPheasant do this review first, it will preserve your file history and also make the other review dramatically easier.

I am happy for the files to be moved. It is only structured like it was for historic reasons


[WIP] Add tests for block and s3 pod deployments

Depends on: #285, #299, #302

This change is

Split it apart and added the tests into the block and S3 PRs as appropriate. Closing.


Does not work anymore with Chrome

With latest Chrome Version 111.0.5563.64 this great extension does not work. It shows nothing on click and no little ms number under the icon in the extension bar when a web page is finished with loading.

That's not good.  By way of contrast, I'm using Microsoft Edge 111.0.1661.41 (dev) and it appears to still be functioning correctly.

As this only happens for me on MacOS (Linux works fine) I reinstalled the extension and it is working again. Don't know why this was needed...


How discrimination can be ruled out?

 The device always stays on same location acting as static beacon in order to collect IDs of all his tenants. From time to time the landlord will conduct a test or claiming he as symptoms triggering exchange of IDs or recieving notifications of possible infected peoples on this devices.
a) how can the app prevent usage of many devices by a single user?
b) how can the app prevent abnormal usage with static positioned devices?
c) how can the app rule our discrimination of people, in this case the tenants of the landlord?
This scenario of course can be expanded to company owners tracing employees, shop owners etc.

a) it can't.
b) it can't
c) it can't
But any match the landlord would get might as well be any person walking by the house. I'm not seeing the point in these actions.

As in previous issues, it would be great if you could wait for the architecture documentation. This will explain some more details, which hopefully answer many of your questions. If they are then still open, you are, of course, free to open up this issue, again.


fluorinejs.org is down

Unable to connect https://fluorinejs.org/
isitdown http://www.isitdownrightnow.com/fluorinejs.org.html

Thanks for reporting! I'll get it back up as quickly as possible

@j4ckcyw The site should be back up now, but I'm still working on restoring the slack inviter. Thanks again for noticing


Load from url?

I don't know any "real" use case for this, but while I was creating a quick example today I wrote the following code:
import tempfile
from urllib.request import urlopen

with tempfile.NamedTemporaryFile(suffix='.msh', delete=False) as temp:
    temp.write(urlopen("https://raw.githubusercontent.com/kinnala/scikit-fem/master/docs/examples/box.msh").read())
    temp.flush()
    m = MeshTet.load(temp.name)

Then I thought why not allow loading meshes from urls directly in Mesh.load? Maybe via Mesh.load("https://...", url=True) so that it is not done by accident.

My first though was to wonder whether there wasn't already something in Python that covered this.  My second was that it might fit better upstream in meshio.read.  The other option that might be good is a buffer; like filepath_or_buffer in pandas.read_csv.
As to the use-case: yes, I definitely envisage an online repository of meshes, not necessarily specific to scikit-fem but open to any finite-element code, like the Matrix Market.  Meshzoo is nice but that's for scripts that generate meshes rather than generated meshes.

Indeed, the docstring for pandas.read_csv states:

Either a path to a file (a str, pathlib.Path, or py._path.local.LocalPath), URL (including http, ftp, and S3 locations), or any object with a read() method (such as an open file or StringIO).


K8SPXC-598 Add support for compressed backups for PITR

 ❨?❩
PITR needs information about last GTID stored in backup. This information stored in file which can be compressed by xtrabackup, so this PR add functionality that decompress needed file using xbstream tool. If file was not compressed xbstream just return its content

Test name
Status

recreate
passed

scaling
passed

haproxy
passed

upgrade-haproxy
passed

big-data
passed

storage
passed

scaling-proxysql
passed

self-healing
failed

init-deploy
passed

restore-to-encrypted-cluster
passed

security-context
passed

limits
passed

upgrade-proxysql
passed

monitoring-2-0
passed

demand-backup
passed

affinity
passed

smart-update
passed

one-pod
passed

self-healing-advanced
passed

auto-tuning
passed

pitr
passed

proxysql-sidecar-res-limits
passed

operator-self-healing
passed

users
passed

demand-backup-encrypted-with-tls
passed

upgrade-consistency
passed

tls-issue-self
passed

scheduled-backup
failed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

Test name
Status

recreate
passed

scaling
passed

haproxy
passed

upgrade-haproxy
passed

big-data
passed

storage
passed

scaling-proxysql
passed

self-healing
failed

init-deploy
passed

restore-to-encrypted-cluster
passed

security-context
passed

limits
passed

upgrade-proxysql
passed

monitoring-2-0
passed

demand-backup
passed

affinity
passed

smart-update
passed

one-pod
passed

self-healing-advanced
passed

auto-tuning
passed

pitr
passed

proxysql-sidecar-res-limits
passed

operator-self-healing
passed

users
passed

demand-backup-encrypted-with-tls
passed

upgrade-consistency
passed

tls-issue-self
passed

scheduled-backup
failed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

Test name
Status

scaling
passed

haproxy
passed

big-data
passed

storage
passed

recreate
passed

upgrade-haproxy
passed

init-deploy
passed

scaling-proxysql
passed

self-healing
passed

security-context
passed

upgrade-proxysql
passed

restore-to-encrypted-cluster
passed

limits
passed

self-healing-advanced
passed

monitoring-2-0
passed

smart-update
passed

affinity
passed

demand-backup
passed

one-pod
passed

operator-self-healing
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

pitr
passed

users
passed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

demand-backup-encrypted-with-tls
failed

tls-issue-cert-manager-ref
passed

validation-hook
passed

Test name
Status

upgrade-haproxy
passed

scaling
passed

recreate
passed

big-data
passed

storage
passed

haproxy
passed

init-deploy
passed

scaling-proxysql
passed

self-healing
passed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

limits
passed

self-healing-advanced
passed

monitoring-2-0
passed

smart-update
passed

demand-backup
passed

affinity
passed

one-pod
passed

operator-self-healing
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

pitr
passed

upgrade-consistency
failed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

scheduled-backup
failed

Test name
Status

big-data
passed

upgrade-haproxy
passed

recreate
passed

scaling
passed

storage
passed

haproxy
passed

init-deploy
passed

scaling-proxysql
passed

self-healing
passed

restore-to-encrypted-cluster
passed

security-context
failed

limits
passed

upgrade-proxysql
passed

monitoring-2-0
passed

demand-backup
passed

affinity
passed

smart-update
passed

self-healing-advanced
passed

one-pod
passed

auto-tuning
passed

operator-self-healing
passed

proxysql-sidecar-res-limits
passed

users
passed

pitr
passed

upgrade-consistency
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

scheduled-backup
failed

tls-issue-cert-manager-ref
passed

validation-hook
passed

Test name
Status

recreate
passed

big-data
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

storage
passed

pitr
passed

self-healing
passed

demand-backup-encrypted-with-tls
passed

self-healing-advanced
passed

scaling
passed

scheduled-backup
failed

operator-self-healing
passed

scaling-proxysql
passed

security-context
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring-2-0
passed

upgrade-haproxy
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

Test name
Status

upgrade-haproxy
passed

haproxy
passed

recreate
passed

storage
passed

scaling
passed

big-data
passed

self-healing
passed

init-deploy
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

limits
passed

self-healing-advanced
passed

monitoring-2-0
passed

demand-backup
passed

smart-update
passed

affinity
passed

operator-self-healing
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

pitr
passed

users
passed

upgrade-consistency
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

scheduled-backup
failed

PXC operator docker - perconalab/percona-xtradb-cluster-operator:PR-743-926bc058

Test name
Status

haproxy
passed

scaling
passed

init-deploy
passed

scaling-proxysql
passed

limits
passed

security-context
passed

monitoring-2-0
passed

affinity
passed

upgrade-haproxy
passed

one-pod
passed

recreate
passed

auto-tuning
passed

restore-to-encrypted-cluster
passed

storage
passed

proxysql-sidecar-res-limits
passed

big-data
passed

demand-backup
passed

self-healing
passed

users
passed

pitr
passed

self-healing-advanced
passed

tls-issue-self
passed

demand-backup-encrypted-with-tls
passed

operator-self-healing
passed

tls-issue-cert-manager
passed

scheduled-backup
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed


a bug in Loader.prototype._handleBaseUrl

Hello I was just studying Loader code and found a bug that is unlikely to show any effect in most practical cases.Nevertheless, I believe it should be fixed.
Loader.prototype._handleBaseUrl = function (url) {
    var parsedUrl = urlParser.parse(url);

    // absolute url, just use it as is.
    if (parsedUrl.protocol || parsedUrl.pathname.indexOf('//') === 0) {
        return url;
    }

    // if baseUrl doesn't end in slash and url doesn't start with slash, then add a slash inbetween
    if (
        this.baseUrl.length &&
        this.baseUrl.lastIndexOf('/') !== this.baseUrl.length - 1 &&
        //HERE INSTEAD
        //  url.lastIndexOf('/') !== url.length - 1
        // SHOULD BE
        url.charAt(0) !== '/'
        // so that this part  of code works like described in the comment above the 'if' statement
    ) {
        return this.baseUrl + '/' + url;
    }
    else {
        return this.baseUrl + url;
    }
};

In cases where baseUrl doesn't end with a slash, and url doesn't begin with a slash, but ends with a slash the original method would return wrong url.
console.log(new Loader('http://example.org')._handleBaseUrl('wrong/'));
would produce the following result:
http://example.orgwrong/
HTH.

 You mind putting in a PR for that?

It is too small change to create PR. It is easier for you to just fix the line. I don't need any credit for that.

Its actually much easier to click "merge" than to find the project and edit it, but thanks for pointing this out I will get around to it at some point.

Ok. I have created pull request.   My bad. It actually didn't take too much time . :blush:


Problems with double 1D complex interleaved for moderate to large sizes

What should happen
-rider should run correctly for doubles as well as floats.
What really happens
-It doesn't, for doubles.  Typically gets output[0].real() = =nan, not N.
As far as I can tell, all sizes > 2048 are broken except for powers of 2.
4096 is also broken, but gets 3.88098e-304 rather than -nan.
8192, 16384, etc. are OK.
How to reproduce

./rocfft-rider --double -o  -p 10 -x 2160

Environment

Hardware
description

GPU
device string

CPU
device string

VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580] (rev e7)

vendor_id	: AuthenticAMD

cpu family	: 23

model		: 1

model name	: AMD Ryzen 7 1800X Eight-Core Processor

stepping	: 1

microcode	: 0x8001129

Software
version

ROCK
v0.0

ROCR
v0.0

HCC
v0.0

4.11.0-kfd-compute-rocm-rel-1.6-180 #1 SMP Tue Oct 10 08:15:38 CDT 2017 x86_64 x86_64 x86_64 GNU/Linux

HCC clang version 6.0.0  (based on HCC 1.0.17412-f590a25-821e6d8-64e7fc7 )

Library
v0.0

Passed on my side
tim@tim-hsa:~/FFT/rocFFT_BUILD/clients-build/rider-build/staging
$ ./rocfft-rider --double -o -p 10 -x 2160
precision: double
transform type: complex forward
result placement: not in-place
input array type: complex interleaved
output array type: complex interleaved
dimensions: 1
lengths: 2160
batch size: 1
input offset: 0
output offset: 0
input strides: 1
output strides: 1
input distance: 2160
output distance: 2160
scale: 1
number of blocks = 2, number of threads = 126
number of blocks = 2, number of threads = 128
number of blocks = 2, number of threads = 126
number of blocks = 2, number of threads = 128
number of blocks = 2, number of threads = 126
number of blocks = 2, number of threads = 128
number of blocks = 2, number of threads = 126
number of blocks = 2, number of threads = 128
number of blocks = 2, number of threads = 126
number of blocks = 2, number of threads = 128
number of blocks = 2, number of threads = 126
number of blocks = 2, number of threads = 128
number of blocks = 2, number of threads = 126
number of blocks = 2, number of threads = 128
number of blocks = 2, number of threads = 126
number of blocks = 2, number of threads = 128
number of blocks = 2, number of threads = 126
number of blocks = 2, number of threads = 128
number of blocks = 2, number of threads = 126
number of blocks = 2, number of threads = 128
number of blocks = 2, number of threads = 126
number of blocks = 2, number of threads = 128
Execution gpu time: 0 ms
Execution wall time: 0.139732 ms
Execution gflops (wall time): 0.856139
Bandwidth GB/s (wall time): 0.494663
	Rider Test *****PASS*****

That's good to know.  Maybe I still have a configuration issue.  Was this on Ryzen + Ellesmere?  How do I check my ROCK and ROCR versions?  Maybe there's an issue there.

on Fiji Nano. it has nothing to do with the CPU.  Please try the latest develop branch.
It is ROCM 1.6.4. Your ROCK and ROCM should be good.

This is v1.6.4
$ uname -a
Linux tim-hsa 4.11.0-kfd-compute-rocm-rel-1.6-180 #1 SMP Tue Oct 10 08:15:38 CDT 2017 x86_64 x86_64 x86_64 GNU/Linux


AdminBSB >> bootstrap-material-datetimepicker >> Year disabled >> Only left and right arrows work for navigation

If I want to select 1997 I have to go through with multiple clicks. This is not correct behaviour of   bootstrap-material-datetimepicker
See this http://t00rk.github.io/bootstrap-material-datetimepicker. In first example here we can see that if we click on Year it shows list of years through which we can easily move to previous years.

@gurayyarar  Why closed?  In AdminBSB theme this is not working as expected.

Because of it is not a issue, it can be only a suggestion


Logfire announcement and example

@sydney-runkle sorry this is a bit delayed, I had some other stuff to fix 👀 .
@dmontagu I'd appreciate your suggestions today so I can get this live in the morning.

replaced by #10541.