Map private or protected properties

It is often so,that you want to load something from the database but you want to handle it only in the class. Maybe some basic calculations or a certain way for handling with nummeric enum values that don't exist.
In this case you would use a public property that works with the private or protected field. From outside the class the db field does not have to be changed directly.
For example:
public enum MyColor{
 Red = 0,
 Blue = 1,
 Green = 2
}
[Column("StatusId")] // This won't work
private Int32 ColorValue {get; set;}

public MyColor Color {
    get{
        if(Enum.IsDefined(typeof(MyColor), ColorValue))
            return (MyColor)ColorValue;

        return MyColor.Green;
    }
    set{
        ColorValue = (Int32)value;
    }
}

I this case you are forced to make everthing public although you don't want to make it accessable directly.
I mean there could be a configuration parameter to enable private mapping or maybe protected mapping.

In your code example, you could just do this:
public enum MyColor
{
   Red = 0,
   Blue = 1,
   Green = 2
}

public class Thing
{
    [Column("StatusId")]
    public MyColor Color { get; set; }
}

Enum integer values get mapped to int values in the database, you don't need to manually convert to/from an int to the Enum value - see Data Type Mapping in the wiki.

Yes I understand, but that was only a abstract example, there are often cases where you want to hide the exact datafield in private scope to let manipulate only part of it or just not give the access to it. Let say you have a bitmask saved in an integer field. In code you would check this by boolean properties that inner access the bits.
Another case is if you save currency values in cent in your db and the user should work only with a decimal or a calculated value.
I mean there are often cases where you don't want to mirror the hole db table in to the same object structure. Databases are not always structured in the way you want them to be.

Even if you look at the example with the enum value. If an enum value is loaded that is not defined in code but a valid value, after loading it and updating it to the db, the value is overwritten with the default value. That is not what you want in this case. You would want to save the original integer value even if your code doesn't know it.

The only suggestion I have for you based upon the current capability in MicroLite is to have a data object which maps to your database and then either have a business object or view model which receives the data object via its constructor to allow you to do what you want as far as encapsulation goes.
There are some changes around mapping planned for MicroLite 7.0 which I'll be working on in the next few months which may offer you other alternatives.

Yes, that's the way I do it now, I am working with a wrapper class. Thought there could be an easier way. Thanks for the reply. Do you have some kind of road map for the version 7? Curious to see what's on the way.

Have a look at the blog, I posted something a while ago, there's also the milestone in the issues page


[Bug] No service worker detected

Hey,
Thanks for this module!
I have a question regarding the service worker as it does not seem to be registered by default.

My nuxt.config.ts
  pwa: {
    manifest: {
      name: 'Test',
      short_name: 'Test'
    },
    workbox: {
      enabled: true
    }
  },

Are you maybe using custom Nuxt  baseURL ?

I havent changed anything. My version of Nuxt is rc3, my nuxt.config.ts contains kodules declaration and publicRuntimeConfig declaration for GraphQL client. I will try to debug it today and will let you know :)

@Baroshem Let me know, and if your project is public we can debug from your repository

Hey @kevinmarrec
I tried to include the module here -> https://github.com/Baroshem/nuxt-shopify-tailwind
I added the module as per instructions and observed the issue I mentioned in the bug. I have not submitted the code with this change yet but will do that in few clicks on a separate branch

Here is the branch with added pwa module and the error appears -> https://github.com/Baroshem/nuxt-shopify-tailwind/tree/feat/pwa

@Baroshem Thanks, I'll have a closer look tomorrow.
Could you try to remove ssr: false in the meantime to see if it can be related ? Thanks !

Hey, I have actually removed all modules except for yours and whole html section and just left the pwa config and it still does not work

You can test it by basically removing everything and it will still not work. I tested it on all major browsers

Alright, thanks, I reproduced it.
It seems that this window event listener is never trigerred :
https://github.com/kevinmarrec/nuxt-pwa-module/blob/aa01db1679eee3141d8576b24a62b3779f99960e/src/runtime/workbox/plugin.ts#L8
I'm wondering what is causing this to happen, most likely it can be two things :

The event is fired before it adds the event listener
Something prevents the event to be fired

@Baroshem Even if something strange seems to happened with Nuxt 3 when opt-in the router (using pages folder), I think I need to implement the worker registration in another way to fix this.

@kevinmarrec
Sorry to bother, but I am still experiencing the same issue (even on version 0.3.0). Everything apart from the Service Worker seems to be generated correctly.

@Baroshem Could you check, in your html code on http://localhost:3000, if you can find the following injected script : https://github.com/kevinmarrec/nuxt-pwa-module/blob/30f0e61a1515715762acf211a44db1b3fcf00bb2/src/workbox.ts#L33-L38
You should find a <script> in your HTML that should register the worker.

I have it

I can see the sw.js file in the .nuxt/pwa/sw.js

But it is not available in the sources tab in browser

I have also removed all other modules in the application and it still does not work :(

@Baroshem Could you try removing pages folder if you have one, and just use app.vue ? Cause I remember of an issue where adding routing feature (enabled with presence of pages) could make this happening.

Ultimately, could you please create a repository with minimal reproduction. Just a project where the issue occurs, so I can debug from that and help you faster :)

Sure, you can try this one -> https://github.com/Baroshem/nuxt-shopify-tailwind/tree/feat/pwa
I removed the code that required some environment variables so you should be able to just clone it and run it easily.

@Baroshem Thanks, I'll have a try when I got the time.

@kevinmarrec
When I removed the pages dir it started working. But it should not be like that as majority of the Nuxt projects will have a pages directory :(

@Baroshem I see. I'll try to debug this asap.

This also works in your project branch when using yarn generate.

I have it available in Sources tab :

You are right, it won't work in dev when having pages folder, most likely cause an internal Nuxt weird behavior.
I think it's when using layouts, cause it seems to work on dev with pages folder when not using layouts, could you confirm that ?
/cc @danielroe @pi0

Thank you @kevinmarrec then! It solves my issue. Huge kudos to you for keeping up with my issues 😄

@kevinmarrec Could you confirm it's because of layouts system ? What exactly solved the issue then ?

Alright, thanks !


Question: Not proxying X-Frame-Options with Spring security + Zuul

Hey guys, I'm using Zuul from spring cloud (Finchley.SR1), and I'm seeing the http header using the default spring security, even when I overrides it.
So, for example, I've used the following property to ignore some headers, but I want to ignore spring-security's default for X-Frame-Options.
zuul.ignored-headers=X-Content-Type-Options,Strict-Transport-Security,X-XSS-Protection

I've also tried setting the securityHeaders to be false, but it none-the-less still proxy with X-Frame-Options: DENY.
zuul.ignoreSecurityHeaders=false

Any help would be appreciated, thanks!

Have you added it to zuul.ignored-headers?


PackageDeploymentManager.IsPackageReadyOrNewerAvailable() throws NotImplementedException even if IsPackageDeploymentFeatureSupported

Describe the bug
PackageDeploymentManager.IsPackageReadyOrNewerAvailable() throws NotImplementedException even though PackageDeploymentManager.IsPackageDeploymentFeatureSupported(PackageDeploymentFeature.IsPackageReadyOrNewerAvailable) returns true.
Tested on Windows 11 24H2 (26100).
Note: it would be nice if on the docs page https://learn.microsoft.com/en-us/windows/windows-app-sdk/api/winrt/microsoft.windows.management.deployment.packagedeploymentmanager.ispackagereadyorneweravailable the requirement to call PackageDeploymentManager.IsPackageDeploymentFeatureSupported would be documented, together with a minimum supported OS version where this is expected to work.
Steps to reproduce the bug
var pdm = Microsoft.Windows.Management.Deployment.PackageDeploymentManager.GetDefault();
var isSupported = PackageDeploymentManager.IsPackageDeploymentFeatureSupported(PackageDeploymentFeature.IsPackageReadyOrNewerAvailable);
if (isSupported)
{
    var isNewerAvailable = pdm.IsPackageReadyOrNewerAvailable(Package.Current.Id.FullName); // throws System.NotImplementedException
}

Expected behavior
Method does not throw and API works as expected.
Screenshots
No response
NuGet package version
Windows App SDK 1.6.1: 1.6.240923002
Packaging type
Packaged (MSIX)
Windows version
No response
IDE
Visual Studio 2022
Additional context
No response

@DrusTheAxe @manodasanW


[Bug] GitHub Gists from Medium article missing in markdown output

I tried converting this Medium article into Markdown.
But the Github Gists were missing in the markdown output.

Medium article containing the Gist:

The resultant output (with the Gist snippet missing):

The script I used:
const mediumToMarkdown = require('medium-to-markdown');
const url = "https://towardsdatascience.com/a-minimalist-end-to-end-scrapy-tutorial-part-ii-b917509b73f7";

mediumToMarkdown.convertFromUrl(url)
.then(function (markdown) {
  console.log(markdown); //=> Markdown content of medium post
});

Possible solution could be to fetch the HTML of the iframe containing the Gist and then enclose them in a code block in the markdown output.

Having this same problem, shame it's not added yet


About 1x1 convolution

Is there any idea about how to deal with 1x1 convolution for channel alignment for parameter sharing CNN? Since the size changes as the graph change.

There are issues w/ assuring compatible channel dimensions AND spatial dimensions, if you're using skip connections that add/concatenate feature maps.  I don't think it's really clear how they handled this in the original paper.
One way would be to only allow connections between layers w/ the same dimensions -- this would be reasonable inside a block in the micro search space, but (probably?) not in the macro search space.
In the paper, there is mention of using 1x1 convs to make sure the number of channels match up, but I don't know whether they were learning a 1x1 conv per layer pair or per dimension pair or whatever.

Let's say there are 4+1+4+1+4 = 14 cells for cifar10, each cell has 5 node, each node has len(conv3x3, conv5x5, sep3x3, sep5x5)=4 parameter weights. My understanding is that there are 1454=280 parameter weights in the shared pool, is it correct?
About the how to use conv1x1, you may check the following code:
You may check https://github.com/Cadene/pretrained-models.pytorch/blob/master/pretrainedmodels/models/nasnet.py
Another way to deal with it may be: for each node to be concatenated, we follow a MxN conv1x1, and for next cell input usage, we add them together, this way we can map (nM) channels to N channels.

@bkj  Could we work together on this?


[Normative] Updates #97 - passing roundingIncrement will throw an error

PR to address changes #97 - Only passing roundingIncrement will throw an error.
close #97

be aware (I am not oppose to it, just want to make it explicit) that the order of reading "roundingIncrement" will be changed by this PR in it's current form. This might be unavoidable though. Be we should be aware of such impact.

I don't know why this PR isn't merged yet. I'll hit the button.

I try to adjust v8 to implement it and it seems
test262/intl402/NumberFormat/constructor-roundingIncrement need to be changed.

Please review https://github.com/tc39/test262/pull/3732


Delete button in Code Editor

The only way to fix mistakes in code editor is using the Backspace key  (it deletes words from right to left).
This patch add the button Delete which works the other way round of Backspace.
I tested it and it's supposed to work as expected, anyways check it by yourself (I started learning Lua like 3 hours ago).
PD: this is such a great project! keep it up with the good work :D

Thanks for feedback, it would be awesome if you sent me some pics of anything you are doing with liko12


GD Library Error 500

Saw we had GD support before. I re-added it this way in php-fpm Dockerfile:
###########################################################################
# GD Library:
###########################################################################
USER root

ARG INSTALL_GD=false

RUN if [ ${INSTALL_GD} = true ]; then \
    apt-get update && apt-get install -y \
		       libfreetype6-dev \
		       libjpeg62-turbo-dev \
		       libpng-dev \
	  && docker-php-ext-install -j$(nproc) iconv \
	  && docker-php-ext-configure gd --with-freetype-dir=/usr/include/ --with-jpeg-dir=/usr/include/ \
	  && docker-php-ext-install -j$(nproc) gd \
;fi

to the php-fpm Docker file. And to.env you can add PHP_FPM_INSTALL_GD=true  and to docker-compose.yml - INSTALL_GD=${PHP_FPM_INSTALL_GD}
It however does not play nice with Image Intervention or Dropzone and results in internal server 500 errors.
NB Forge uses GD by default and does not use Imagemagick

I added
 fastcgi_intercept_errors on;

to nginx server block and then I saw this on uploading:
php-fpm_1            | [17-Feb-2019 07:26:55] WARNING: [pool www] child 12 said into stderr: "Not a JPEG file: starts with 0x89 0x50"
php-fpm_1            | <IP_ADDRESS> -  17/Feb/2019:07:26:55 +0000 "POST /index.php" 500

Saw that files that had been added for a while had been given extended attributes to work with user and group 1000, but not the newly added files of which one is used by image intervention to generate other types of files using GD. This may be the issue though Imagick is not bothered by this at all.
180 @ MacMini [jasper] $ ll
total 23560
-rw-r--r--@ 1 jasper  staff   2.6M Apr 30 10:07 1chuttersnap-1522341-unsplash.jpg
-rw-r--r--@ 1 jasper  staff   2.5K Apr 30 10:07 1chuttersnap-1522341-unsplash_thumbnail.jpg
-rw-r--r--  1 jasper  staff   2.6M Apr 30 11:58 2chuttersnap-1522341-unsplash.jpg
-rw-r--r--  1 jasper  staff   2.5K Apr 30 11:58 2chuttersnap-1522341-unsplash_thumbnail.jpg
-rw-r--r--@ 1 jasper  staff   2.6M Apr 30 09:27 chuttersnap-1522341-unsplash.jpg
-rw-r--r--@ 1 jasper  staff   2.5K Apr 30 09:27 chuttersnap-1522341-unsplash_thumbnail.jpg
-rw-r--r--  1 jasper  staff   3.7M Apr 30 10:23 lerone-pieters-1481905-unsplash.jpg
-rw-r--r--  1 jasper  staff   4.9K Apr 30 10:23 lerone-pieters-1481905-unsplash_thumbnail.jpg

Here one file with extended attributes:
180 @ MacMini [jasper] $ xattr -l 1chuttersnap-1522341-unsplash.jpg
com.docker.owner: 0:1000:1000

The newly added files do not have these yet.


BM25 Vectorizer

Hey @acalejos 👋
I get the vibe that this project is on the back burner, but wanted to throw a very untested implementation of BM25 to go along with the existing TF-IDF implementation.
I am going to throw some time (and data) at this in the next few days to A/B against some other BM25 implementations - but figured I'd share what I have sooner than later to measure interest.
BTW, Your existing work on this library was a massive help in guiding me through porting BM25 over 🙌

Hey @amokan thanks for the PR! You are correct that this library has been on the backburner, as I initially made it for the demo I wanted to do during my ElixirConfUS 2023 talk. I haven't really found the right set of things to put in this library (hence why it's not yet published on Hex), so having your BM25 vectorizer is more than welcomed!
I'm glad that you found the work in this library helpful. It was a good exercise porting over the sklearn implementations over to Elixir.
I took a brief look at your code just to see how its convention looks without looking at the details of the BM25 implementation and so far everything looks good. Let me know when you want a more thorough look as you approach finishing it!

@acalejos Haven't forgotten about this. Still thinking about the bigger picture from an NLP perspective and the rest of the ecosystem.


Add driver-facing store API for indicating source state

Similar to #9, but in the other direction. Thinking about recent manifest discussions over Skype and email, this could be very useful.
Currently, a driver uses a store's catalogue to "advertise" if a datasource is available. IMO, the sole purpose of store catalogues should be to list datasource metadata, not keep track of datasource state. At the very least, it would mean added complexity (e.g. being able to delete items when datasources disappear and adding them again with all their metadata when they reappear — see https://github.com/me-box/databox-store-blob/issues/42).
Similarly, we do need to be able to differentiate between when a datasource is inactive (e.g. turned off at the driver, or the source) and when it's active but just not streaming any data. I can think of a number of use cases where an app might need to know if a gap in data is due to a sensor being off vs. if there's just no new data.
So ideally there should be a (subscribable) store endpoint that a driver can POST sensor/datasource states to, and apps can GET (or receive subscription events of) these states from.

This would also mean that the store catalogue should list all datasources the store can expose, not is exposing, based the driver. This would mean that the store catalogue can be (and I believe should be) immutable. IMO we should remove store POST /cat entirely, and have a store's catalogue populated install-time by the CM/system. Am I correct in thinking that the only reason we had this to begin with was to allow the run-time addition of datasources (and not runtime addition of metadata on existing datasources)?
Because if so, I believe we should go one step further, and require that drivers (and apps) are packaged with a static catalogue.json. This catalogue essentially does the job of the proposed publishes manifest field — it lists what an app/driver can publish and any metadata about it. We can use catalogue item metadata to directly match consumers with publishers.
Every conjugate in the elements of a manifest's consumes array would essentially be a search string (with some special support for semver constraints and path regex) for catalogue item metadata. This means that we can set standard rels (with existing or custom syntax) for things like format and type (like the TAG-VERSION syntax), or leave it open for developers to annotate their sources and sinks with their own metadata, and Databox will automatically be able to match those. Essentially repeating what I wrote in last week's email discussion, but IMO this will make the whole publishes-consumes pairing really versatile and future-proof.
Thoughts and opinions on these suggestions much appreciated as always.
P.S. We could theoretically literally replace the entire manifest with a catalogue (since "catalogue metadata" is separate from "item metadata" and the manifest can be pretty much encoded into the former) but one argument against that is that a manifest is easier to read than a catalogue.

In general i like the idea of the catalogue information being (largely) statically pre-defined and outside the driver code (e.g. so it can be audited more readily). The two exceptions I can think of are:

where the driver interfaces to an external system (e.g. hue bulbs, home kit) which has its own interfaces to add sensor metadata (e.g. names) then the driver should be able to propagate changes to these into the catalogue

drivers which support more instances being added (e.g. hue bulbs) will still need to tell the catalogue that a new one exists (e.g. giving the newly discovered mac address). (this is not about state, just about initial discovery) So the static catalogue would have to include something like a template entry to be instantiated for each individual bulb (with appropriate bulb-specific values filled in).

I would definitely keep the manifest format and the catalogue formats separate for now.

My two penn'orth:

Catalogs should be static or (at worst) templated and reified on installation as with manifest --> SLA (indeed, possibly generated from the manifest as with the SLA)
Catalogs primarily describe API endpoints; metadata about sources being present / online / idle / etc should simply be data written into the store
Catalog endpoints might themselves be template expressions per RAML allowing for the cases @cgreenhalgh notes (I think)


skipping 'AC' because it has Number=A

Hi,
When I try to load my VEP annotated vcf's into a db I get the error above. I traced this back to the code (line 656)
            if d['Number'] in "RA":
                print("skipping '%s' because it has Number=%s" % (d["ID"], d["Number"]),
                      file=sys.stderr)
                continue

Would it be possible to explain why those columns get skipped? Is there a way to force include them? The AC, AF MLEAC en MLEAF info fields are quite important, and the info fields are compliant with the VCF standard.
Thanks
M

There is a 1:1 mapping of INFO fields to database fields. When your AF value is something like 0.233,0.444 because there are multiple ALTs, we can't store that as a single float.
If you decompose your VCF and make sure the header is adjusted so that records that had Number=A are replaced with Number=1.
If you annotate with vcfanno, you could use a [[postannotation]] section and use max(AF) to get a new field and then save that in the database.
I would like to handle this more cleanly, but I haven't thought of anything that works well with RDBMS.

We always decompose and normalize with vt before we do our annotation. If I'm understanding you correctly, I can then safely edit the vcf header and replace the A by 1 and I should be good to go?
Nice, I though it was going to be more complicated! looking forward to the next release of vcf2db to bioconda!
Thanks,
M

Yes, that should work. Remember for GATK AD tag, you need to do: sed 's/ID=AD,Number=./ID=AD,Number=R/' before decompose.

thanks for the tip!
M


maatwebsite/excel[3.1.0, ..., 3.1.25] require php ^7.0 -> your php version (8.2.13) does not satisfy that requirement.

When installing this package, the following problem occurs. Does it due to the dependent package? Is it solvable by downgrading PHP only?
maatwebsite/excel[3.1.0, ..., 3.1.25] require php ^7.0 -> your php version (8.2.13) does not satisfy that requirement.

No, it definitely supports PHP8.2 in a higher version (see the repo: https://github.com/SpartnerNL/Laravel-Excel/blob/f3cce8310b94b4e5716a71da58440ae81c7afe24/composer.json#L24)
So the install is probably blocked by something else.


Rewrite Translatable/Translation to use Interfaces instead of Traits

This is PR #322 rebased on current master branch and with minor fixes. Credits go to @lemoinem
Left to do:

[ ] Update readme and upgrade guide
[ ] Implement a compatibility layer to smooth transition from trait to interface (in a separate PR)

Thanks @NiR- for the follow up and the credits. Sorry I didn't have the time to do the follow up.
I'm happy to this move forward and getting merged!

No worries, actually we were not really active on this repository in the previous months, too.

Covered by #442


Make ESP8266 build system up to date.

Readme.md is updated as well.
JerryScript-DCO-1.0-Signed-off-by: Robert Fancsik<EMAIL_ADDRESS>

Thanks for this fix. Please mention the related issue (#1375) in the commit message.

@akosthekiss Thanks for your review. During this refactoring I realized that jerry-limb is still needed, because SDK's libm is not proper. Including jerry-lib can solve it.

A separate note: this PR is a lot more now than just updating the build system of the ESP target. This is actually reviving it, build system and code base alike. Please reflect this both in the commit message and in the title of the PR.

One more note (actually a reminder): please also mention the related issue in the commit message, as @LaszloLango requested.

@akosthekiss Thanks for your review. I applied your ideas!

@rerobika Please double check. The commit still touches the mbed target.

I've forgotten to revert it. Now it's done.

Version if fixed as you requested!


flynn cluster add fails on restored cluster

17:54:46.113689 status-check status
17:55:02.494246 cluster-monitor cluster-monitor'
+ echo 'Bootstrap succeeded'
Bootstrap succeeded
+ slept=0
+ add_local_flynn_config
++ cat controller.auth_pin.txt
++ cat controller.auth_key.txt
+ flynn cluster add -p a6x8x6NmzsUE+jcv76ZJi64xy6p01ZABaU8sL3TOIoM= qa-us-east-1-cluster-2016-03-27-12-27-45 qa-us-east-1.flynn.nexus.bazaarvoice.com 62b07a2c7f6e9d12928b81a3a9726649
Error writing CA certificate: Get https://controller.qa-us-east-1.flynn.nexus.bazaarvoice.com/ca-cert: dial tcp <IP_ADDRESS>:443: connection refused

That failure continues ad infinitum. Debug-info: https://gist.github.com/b444337c583cd99f1e6c https://gist.github.com/2fc2dcd7aa02c6e52949 https://gist.github.com/b282973076ae111e685f

Another occurance: https://gist.github.com/1064d554ba615429630d https://gist.github.com/06a302325aea7eefdfa6 https://gist.github.com/e240d9a1fca7f17824b2

Another occurrence: https://gist.github.com/9118c1f68abccb8248e5a204ef00e324 https://gist.github.com/d9f807f25d6c4ef1f01c358aa97af377 https://gist.github.com/859abdeb2b8e93986c89adb24853b7d4

Another occurrence: https://gist.github.com/301d105dab0e552c542bdc8c6c1d90ff https://gist.github.com/b99fef3bbecad3e62abe55f4d211f4fc https://gist.github.com/45d50ba82734adc06ba84469cf4b3706

https://gist.github.com/4ae7d70d2a0779cfe586a48dc7f6aa0b https://gist.github.com/70acc932ce64d6dca5e97f09acc40878 https://gist.github.com/5832ff0a9b269371144a2aa77ede5642

FYI - the problem occurred again today. I accidentally tore down the stack that the problem so I wasn't able to collect the debug logs.

Another occurrence:
https://gist.github.com/aa6a75160e81ca38d0eaba0f5f2439a9
https://gist.github.com/253552c0e9bd22aec6a475e6e545b788
https://gist.github.com/46b58ac54b832d857006cec5ed4ed334

https://gist.github.com/137ad26215f81aecb8beeb02dcc617bf
https://gist.github.com/c977447bdb745b4a042337b9c71eac27
https://gist.github.com/acbbf99e669e44f5438feeb923ce14fb
https://gist.github.com/2f5d5909d1c89d714792c0900e2eee1c
https://gist.github.com/7ab6f52e4662cc1d97e1cd28b924e7aa

Has this happened recently?

I don't believe so: I'll close it for now, and reopen if it does come back.


GuardedBy and volatile

I guess this is more a question than an issue, but it needs clarification at least.
In our project we have several instances of a pattern where we have a field annotated with @GuardedBy, that field is volatile and we exploit that last fact to optimize reads.
It is used in places where the object referred by this field is not mutable (or at least not mutated), but the value of the reference may change. The updates are (usually) synchronized on the lock declared by @GuardedBy, but most reads just rely on the fact that the field is volatile and they do not need to acquire the lock.
This is where Error Prone comes in, as it flags those volatile reads.
The question is: is this correct?
And the supposition is: this should be allowed.
Please advise.

this is still an issue on latest ErrorProne 2.20.0, this is the same is the same bug as this was in IDEA https://youtrack.jetbrains.com/issue/IDEA-167633


Create an intro

Add an intro about yourself: who are you, what is your strength, why are you here.

Intro is created and merged tio Main branch

Issue can be closed now

Issue can be CLosed


Split bill -  Deselected attendees shifting to above the another user

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

Action Performed:

Go to https://staging.new.expensify.com and login
Select a group chat
Click split bill
Proceed to final confirmation page
Deselect the last attendee in the list and one above the last

Expected Result:
Deselected are expected to stay in the same position
Actual Result:
When an attendee is deselected below attendee is moving up 1 position in the list
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: 1.1.11-0
Reproducible in staging?: yes
Reproducible in production?: yes
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/139499052-a3a91d11-c038-4d34-bb7d-d6935bb05866.mp4
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
View all open jobs on GitHub

Triggered auto assignment to @tgolen (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Proposed Solution: (If considered as external)

Deselected are expected to stay in the same position

Within IOUConfirmationList.js when list rendered, we are rendering section list with WHO PAID?,  WHO WAS THERE?, and Unselected participants. i.e. Unselected participants are also rendered as separate list (but without section header). So it is not feasible/good idea to keep unselected attendees on same position because in that case it will show mix list of selected and unselected participants. Also to achieve this we need to change rendering logic so I will not suggest to go that way.
So I am proposing middle solution. i.e. when attendee deselected it shows within unselected list, but deselected attendee will not goes to bottom of the list, instead of that unselected attendee will maintain its position either begin, middle, or  bottom within unselected list, it will also looks natural and expected behaviour to human eye.
Here is Problem:
When attendee deselected via toggleOption(), we are removing that from list (line 389-391), thereafter toggle selected, and push to bottom of list (line 393-396), So deselected attendees always goes to bottom of list.
https://github.com/Expensify/App/blob/973dcf4d6ef737630eeac61b57dbd95b183a092b/src/components/IOUConfirmationList.js#L388-L398
Here is Proposed Solution:
Within App/src/components/IOUConfirmationList.js file, we have to update this.setState({ ... }) code as under, so it will toggle unselected attendee state and keep it on same position in array.
  this.setState((prevState) => {
      const newParticipants = _.map(prevState.participants, (participant) => {
          if (participant.login === option.login) {
              return {...option, selected: !option.selected};
          }
          return participant;
      });
      return {participants: newParticipants};
  });

After updates it will behave as shown under:
https://user-images.githubusercontent.com/7823358/139522441-43ac212e-73d1-4bfb-8e2e-4a8492c438cc.mov

Triggered auto assignment to @puneetlath (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

I think the proposal above is a good proposal (for when we are ready to hire for this job). 🟢

Issue reproducible during KI retests.

@PrashantMangukiya created the job here and invited you to it.

@puneetlath Submitted proposal on Upwork. Kindly accept it.

Bump @puneetlath

PR  https://github.com/Expensify/App/pull/6173 for this issue deployed to production seven days ago. But OSBotify did not updated issue title to Hold for Payment etc.


WKWebView SSO

This document states that WKWebView does not support SSO.
We have a hybrid native iOS+Android app built with Xamarin in which we have embedded WKWebViews for specific web-based features. The system browser does not match our use-case so that is not an option at this time.
We'd like to be able to SSO into those web apps and see that we can set the cookies for a WKWebView.
Can we not then request a token from MSAL and place it inside a cookie which we then set on the WKWebView to enable SSO into the embedded web apps?

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

ID: f997f743-e5b9-1aa9-ad70-29b839a68cfa
Version Independent ID: 1e77e773-ea78-e396-a844-732e6e86c35f
Content: Customize browsers & WebViews (MSAL iOS/macOS) - Microsoft identity platform
Content Source: articles/active-directory/develop/customize-webviews.md
Service: active-directory
Sub-service: develop
GitHub Login: @mmacy
Microsoft Alias: marsma

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

@mattallscripts
Thank you for your time and patience. I've reached out to our engineering team regarding this ask and will update as soon as possible.
If you have any other questions, please let me know.

@mattallscripts
Thank you for your time and patience!
The documentation states cookie sharing is required for SSO. Since WKWebView is an in-app browser that displays web content, and doesn't share cookies or web site data, it cannot support SSO.
For more information.
If you'd like to create a feature request, please feel free to leverage our User Voice forum.
Thank you again for your time and patience throughout this issue.

Hi @JamesTran-MSFT that makes sense that WKWebView doesn't share its cookies in an outgoing fashion with other webviews or apps. However I guess what we are interested is sharing the native app's cookie(s) with the WKWebView by injecting those cookies into the WKWebview. So a unidirectional share from app into the web view; that's what we're looking to confirm with you all. Thanks!

If we have time we'll do a POC and try this out, I have a feeling it'll work but in the meantime @JamesTran-MSFT if you have any insight into my clarification above that'd save us some time.


fixed resolving orphan children in external docs

@amarzavery,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Controlling Order for Widgets in Layout

Description
As per Dashboard 1.0, we should be able to control the order of the groups/widgets. This could be done at the widget config level, with a single "order" property, but would be better served at the group/page level respectively, and/or the Dashboard 2.0 side menu.
Epic/Story
No response
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate

Progress being made - have nested editable lists for page & group re-ordering in place. No collapsing of lists or editable lists of widgets just yet.
https://github.com/flowforge/flowforge-nr-dashboard/assets/99246719/80fc8aae-b405-4eb4-934b-a2ee9aec088f

Is it planned that at some point there will be a graphical drag and drop of widgets as there is in D1?

For ordering, yes, should have that working on Tuesday.
For layout, eventually, yes. We have an issue already opened for a Visual Layout Editor here.

Excellent :)


Add support ubuntu 18.04

Hi!
You are deleted support of ubuntu 14.04 LTS before end of life, soo i've added support ubuntu 18.04 LTS for amd64.
At ubuntu 18.04 we only have puppet 5.3 and we should add old directory /etc/puppet/modules as modulepath.
Pls, check this out. Feel free for feedback.

I'll try this patch and see if the bigtop packages work on Ubuntu-18.04.

Nice, could you show me how are you testing?
Today documentation is lean, or maybe i doesn't fully understood it

Basically, you need to first get packages built:
https://cwiki.apache.org/confluence/display/BIGTOP/How+to+build+Bigtop-trunk
And then deploy:
https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+Provisioner+User+Guide
If you hit any problem, feel free to post it on<EMAIL_ADDRESS>


🐛 [firebase_analytics, location ] On using firebase_analytics with location (package) Flutter wants location_web. Does anybody know why?

On using firebase_analytics with location (package) Flutter wants location_web. Does anybody know why?
When I am using the project without firebase_analytics: ^6.2.0 the project is working fine, but when I integrate the configurations for firebase_analytics I am receiving the following message:
Plugin project :location_web not found. Please update settings.gradle.
I don't need the location_web, as I am working on a mobile app.
in pubspec.yaml along with other packages I am using also:
location: ^3.0.2
firebase_analytics: ^6.2.0
settings.gradle
include ':app'

def localPropertiesFile = new File(rootProject.projectDir, "local.properties")
def properties = new Properties()

assert localPropertiesFile.exists()
localPropertiesFile.withReader("UTF-8") { reader -> properties.load(reader) }

def flutterSdkPath = properties.getProperty("flutter.sdk")
assert flutterSdkPath != null, "flutter.sdk not set in local.properties"
apply from: "$flutterSdkPath/packages/flutter_tools/gradle/app_plugin_loader.gradle"

android/build.gradle
buildscript {
    repositories {
        google()
        jcenter()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:3.5.0'
        classpath 'com.google.gms:google-services:4.3.4'
    }
}

allprojects {
    repositories {
        google()
        jcenter()
    }
}

rootProject.buildDir = '../build'
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
    project.evaluationDependsOn(':app')
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

android/app/build.gradle
def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
    localPropertiesFile.withReader('UTF-8') { reader ->
        localProperties.load(reader)
    }
}

def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
    throw new GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}

def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
    flutterVersionCode = '1'
}

def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
    flutterVersionName = '1.0'
}

apply plugin: 'com.android.application'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"

apply plugin: 'com.google.gms.google-services'

dependencies {
    // Import the Firebase BoM
    implementation platform('com.google.firebase:firebase-bom:26.1.0')

    // Add the dependency for the Firebase SDK for Google Analytics
    // When using the BoM, don't specify versions in Firebase dependencies
    implementation 'com.google.firebase:firebase-analytics'

    // Add the dependencies for any other desired Firebase products
    // https://firebase.google.com/docs/android/setup#available-libraries
}

android {
    compileSdkVersion 29

    lintOptions {
        disable 'InvalidPackage'
    }

    defaultConfig {
        // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
        applicationId "air.locationexample"
        minSdkVersion 16
        targetSdkVersion 29
        versionCode flutterVersionCode.toInteger()
        versionName flutterVersionName
    }

    buildTypes {
        release {
            // TODO: Add your own signing config for the release build.
            // Signing with the debug keys for now, so `flutter run --release` works.
            signingConfig signingConfigs.debug
        }
    }
}

flutter {
    source '../..'
}

And I have put the google-services.json in android/app.
Does anybody know why this is happening, as I don't need the location_web?
Thanks in advance
Flutter doctor
C:\Users\makar\Desktop\flutter_SDK\flutter\bin\flutter.bat doctor --verbose
[√] Flutter (Channel stable, 1.22.3, on Microsoft Windows [Version 10.0.19041.630], locale bg-BG)
    • Flutter version 1.22.3 at C:\Users\makar\Desktop\flutter_SDK\flutter
    • Framework revision 8874f21e79 (2 weeks ago), 2020-10-29 14:14:35 -0700
    • Engine revision a1440ca392
    • Dart version 2.10.3

[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at C:\Users\makar\AppData\Local\Android\sdk
    • Platform android-30, build-tools 29.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[!] Android Studio (version 4.1.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    X Flutter plugin not installed; this adds Flutter specific functionality.
    X Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[!] IntelliJ IDEA Community Edition (version 2019.3)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2019.3.4
    X Flutter plugin not installed; this adds Flutter specific functionality.
    X Dart plugin not installed; this adds Dart specific functionality.
    • For information about installing plugins, see
      https://flutter.dev/intellij-setup/#installing-the-plugins

[!] VS Code (version 1.51.0)
    • VS Code at C:\Users\makar\AppData\Local\Programs\Microsoft VS Code
    X Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[√] Connected device (1 available)
    • sdk gphone x86 arm (mobile) • emulator-5554 • android-x86 • Android 11 (API 30) (emulator)

! Doctor found issues in 4 categories.
Process finished with exit code 0

Hi @FlutterEnthusiast
Does the answers to this SO question help? Could you please provide your flutter pub deps -- --style=compact?
Thank you

Hi @markusaksli-nc
It is working now, using what you told.
Thanks very much


Feature/retry on error

TODO :

[x] add options
[x] merge + tag https://github.com/M6Web/Redis/pull/10
[x] branch on a stable tag in the component

v2.2.0


In mesop, send prompt with enter

When user presses enter prompt (or feedback) should be sent to the workflow.

probably we can wait for shortcuts to become available in Mesop:
https://github.com/google/mesop/pull/922
if not instead of Textarea, single line Input could be used.

Mesop 0.12.4 was released, and it should have support for hotkeys.


Fix the gummies.jpg sample image

This file once was named gummies.txt, and the settings in .gitattributes forced it to change line endings.
This obviously resulted in a quite broken jpg file: loading it with GD raises the following warning:
imagecreatefromstring(): gd-jpeg, libjpeg: recoverable error: Corrupt JPEG data: premature end of data segment
Let's fix this.

That's weird, was this a .txt for any reason?

That's weird, was this a .txt for any reason?

Maybe @aembler added it as .txt to be sure that the file was recognized by its content type, not by its file extension

But, maybe after git found it as modified a couple of times (because of .gitattributes), he then renamed it.

Gotcha, maybe the best of both worlds there is to have no extension at all? Anyway this looks like a good change, thanks!

maybe the best of both worlds there is to have no extension at all?

IMHO yes

I'm not at my keyboard but I think that is exactly correct
Sent from my iPhone

On Aug 30, 2016, at 12:11 PM, Michele Locati<EMAIL_ADDRESS>wrote:
But, maybe after git found it as modified a couple of times (because of .gitattributes), he then renamed it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Compress HTML per default?

The only case where it would make no sense to compress HTML is if there is some form of content modification (eg: script injection) by the web server.


Add skip entries option

This addresses #45
I created a new menu option skip_empty_entries that when set will skip over empty entries in the menu.
Skip-able entries can either be defined with empty string or as None. The new option is set to False as default, so if empty or None values or specified it will fail as it does now. But if the option is set to True it will skip the entries when iterating through the menu. This will allow for grouping menu options together visually.
I've tested it with single selection and multiselection.

Thank you very much for contributing! The changes look good to me. I have only some suggestions for minor improvements:

Declaring the type of a variable without a typing comment is "only" possible for Python >= 3.6. Some people requested Python 3.5 compatibility, so I still use the old typing comments (see the Python 3.5 compatibility check in the GitHub actions).
I think it is a good idea to both allow None and empty strings for menu separators because empty strings could also be passed from the command line interface. Since None is a special value which is invalid without your new flag, I think we could even always use None as a separator entry. This simplifies the API usage.
The pre-commit action failed because of a broken black installation... I fixed this in the latest develop, so this check should pass when you push again.
It would be great if you could add a sentence to the README.md file which describes your new flag. I use the README.md as a documentation replacement. :innocent:

Thanks for the quick review and reply.
I'm happy to address them, probably towards the end of the weekend :)

@IngoMeyer441 I've updated the PR now:

Added type comments to the declared variables
Only use None as the separator
Updated the README.md with an example
Also in the first version I forgot to add the command line argument for the new constructor parameter, that is included as well now

I had issues running the black commit hook. I kept getting the following error
Traceback (most recent call last):
  File ".cache/pre-commit/repootteniip/py_env-python3/bin/black", line 8, in <module>
    sys.exit(patched_main())
  File ".cache/pre-commit/repootteniip/py_env-python3/lib/python3.10/site-packages/black/__init__.py", line 1423, in patched_main
    patch_click()
  File ".cache/pre-commit/repootteniip/py_env-python3/lib/python3.10/site-packages/black/__init__.py", line 1409, in patch_click
    from click import _unicodefun
ImportError: cannot import name '_unicodefun' from 'click' (.cache/pre-commit/repootteniip/py_env-python3/lib/python3.10/site-packages/click/__init__.py)

I updated the hook to the latest version of black and that resolved the issue

Thanks for your changes and your contribution. I tested your code and works fine!
I applied some minor improvements to your PR:

Always consider None as an empty menu entry (independently from skip_empty_entries)
Consider empty strings as empty menu items if skip_empty_entries is
set to True
Do not require preview functions to accept a None value
Replace Union[None, x] with Optional[x]
Sort constructor parameters and cli switches
Update the documentation of command line switches

I pushed a new commit to the svartkanin-skip-empty-entries branch in this repository. You can apply (and review) the changes with:
git fetch https://github.com/IngoMeyer441/simple-term-menu.git svartkanin-skip-empty-entries
git cherry-pick FETCH_HEAD

If the changes are ok for you, simply push the commit to this PR and I will merge it. Otherwise, please let me know. I am always open for discussion. :slightly_smiling_face:
Thanks again and have a nice weekend! :beers:

@IngoMeyer441 thanks for the updates, I've tested things and it seems to work as expected :+1:


typing route in URL bar

I did the basic install and linkTo worked fine as did the back button. But when I typed into the url bar of the browser I get a "The requested URL ... was not found on this server. What would I need to do to get that functionality in a modern browser
import {bootstrap}    from '@angular/platform-browser-dynamic'
import { provideRouter, Routes } from '@ngrx/router';
import {AppComponent} from './app.component'
import {HelpComponent} from './help/help.component'
import {AboutComponent} from './about/about.component'
const routes: Routes = [
  { path: '/', component: AboutComponent },
  { path: '/about', component: AboutComponent },
  { path: '/help', component: HelpComponent }
]
bootstrap(AppComponent, [provideRouter(routes)]);

@mckennatim This normally depends on your server setup. The default is HTML5 mode, which requires that your server be setup to return your index.html file for all requests that would result in a 404. If you don't want the additional requirement, you can use the HashLocationStrategy instead.

thanks, provide(LocationStrategy, { useClass: HashLocationStrategy }) works.
But you would think that webpack-dev-server would support HTML5 mode. Is there some flag to set that you know of?

adding this to webpack.config.js
devServer: {
  contentBase: "/wamp/www/ng2/sb/ng2-js-webp-broke-rt",
  historyApiFallback: true
},

does two things

causes page refresh if you type in the url bar
forgets to remove the prior path when you go back to linkTo buttons

localhost:6100/about
then press linkTo button for /help and you get
localhost:6100/about/help instead of localhost:6100/help
Oy I guess I need to go back to #

When setup correctly, webpack-dev-server handles HTML5 mode works fine. You may need to add the outputPath to your webpack config.

Even then localhost WAMP doesn't work, and who knows if NGINX will.  I'll use hash routing til HTML 5 mode is easier. Thanks


[BUG REPORT] CircleCI not running

Please Describe Your Issue
When PRs are created, CircleCI should run according to the config file in /.circleci, it currently isn't set up on the new repo
How to Reproduce

Create PR
See status check go from working to error or success.

Expected behavior
CircleCI should run and report a status

Should work for new PRs now.


Error: invalid signature while downloading stylua binary

Trying to download stylua fails with the following error:
[coc.nvim]: Uncaught exception: Unhandled error. (Error: invalid signature: 0x4f44213c
    at /Users/diegof/.config/coc/extensions/node_modules/coc-stylua/lib/index.js:8130:29
    at tryCatcher (/Users/diegof/.config/coc/extensions/node_modules/coc-stylua/lib/index.js:1324:21)
    at Promise2._settlePromiseFromHandler (/Users/diegof/.config/coc/extensions/node_modules/coc-stylua/lib/index.js:5788:32)
    at Promise2._settlePromise (/Users/diegof/.config/coc/extensions/node_modules/coc-stylua/lib/index.js:5842:16)
    at Promise2._settlePromise0 (/Users/diegof/.config/coc/extensions/node_modules/coc-stylua/lib/index.js:5885:12)
    at Promise2._settlePromises (/Users/diegof/.config/coc/extensions/node_modules/coc-stylua/lib/index.js:5953:16)
    at Async._drainQueue (/Users/diegof/.config/coc/extensions/node_modules/coc-stylua/lib/index.js:1906:12)
    at Async._drainQueues (/Users/diegof/.config/coc/extensions/node_modules/coc-stylua/lib/index.js:1915:10)
    at Async.drainQueues (/Users/diegof/.config/coc/extensions/node_modules/coc-stylua/lib/index.js:1803:13)
    at processTicksAndRejections (node:internal/process/task_queues:96:5))

I performed a quick investigation.
It seems that trying to download the binary from download.fastgit.org hits a Cloudflare DoS page and unzipper errors out.
That doesn't happen when I trigger the same request against github.com.
I assume that is related to the location from where I am executing the request?
I got around the problem by manually installing stylua binaries and using the stylua.styluaPath COC setting.
Is there a way to prevent this issue? Maybe adding a stylua.downloadMirror setting?
Thanks

Also, notice I am asked to download the latest Stylua version even if I am using stylua.styluaPath option

The same thing happened to me, came here for the solution. Any possible updates?

I'll refactor the code in a few days.


Fix inconsistency of the data returned by the API

This PR is to resolve (partially) this issue https://github.com/adoptium/dash.adoptium.net/issues/385
There is some inconsistency in data returned by the API.
Two endpoints do not return same data because they do not filter values in the same way.
Filter is             .filter { it.release_type == ReleaseType.ga }
line 67 getTotalDownloadStats()
:warning:  do not have the filter
and
line 93 getTotalDownloadStatsForTag()
:heavy_check_mark:  have a filter
:arrow_right: I have added the filter to both function. Maybe I should remove the filter from the second, let me know.
Checklist

[x] You added tests to cover the change
[x] mvn clean install build and test completes
[ ] You changed or added to the documentation

Note that this PR will not fix the difference of counts returned by https://api.adoptium.net/v3/stats/downloads/total/
It will be in another PR.

code change looks OK but @johnoliver to check on the semantics here

@johnoliver Note that I have found that in the following method, data are NOT filtered to compute the Total.
We can talk about that on Slack when your are available.
In GitHubDownloadStatsCalculator, line 55
        return repos             .repos             .values             .map { featureRelease ->                 val total = featureRelease                     .releases                     .getReleases()                     .filter { it.vendor == Vendor.getDefault() }                     .sumOf {                         it.download_count.toInt()                     }

We chose to add as a parameter the list of types we want to include releaseTypes: List<ReleaseType>? . By leaving the filter on “ga” by default as before.
To fix the related issue  (https://github.com/adoptium/dash.adoptium.net/issues/385), we have to modify calls from the dashboard to retrieve all releaseTypes to compute drilldowns.
In api.tsx:
https://api.adoptium.net/v3/stats/downloads/total/${jdkVersion}?release_types=ga&release_types=ea


Add missing comma in reqargs.lua

@thomasbacklund, Great, thanks! Shouldn't be making hot fixes ;-).

@bungle One day, I'm sure we'll all learn from our mistakes :)


Visual Studio 2015 (update 3) hang out when select to this.WhenAll

Please file a Connect bug

@lyquocnam I have already reported this exact issue to Microsoft and provided them with a crash dump. I did it via the MVP email list, so I don't have a direct link for you. However, I will update this thread as I receive more info.

@lyquocnam Install this update to fix the Intellisense freeze issue:


feat: use built-in exec instead of execa with execGit

Ping @okonet do you have any opinion on reducing the number of dependencies? This Draft MR is a trial on whether current fresh Node.js LTS versions would allow us to drop execa and just directly use spawn(). Looks like there's plenty of improvements and the syntax is quite nice.
Hoping that Windows tests pass.... 🤞

I'm fine with it. Looks nice indeed. Why are user tasks need still to be wrapped with execa? Can they use this wrapper?

This was easier to test with, thus the draft PR. For user tasks it will still need:

shell support
support for aborting, possibly with a signal
some refactoring because current code passes the execa result object around (mostly unnecessary)

That makes sense. I'm wondering if it then worth the change if we keep the dependency in place.
Can these missing bits be done just with Node?

Should be possible. I'll keep this as a draft until it's done.


Select all filtered results checkbox not getting checked With Group By

Select all filtered results checkbox not getting checked with Group By of list feature.
Throwing below mentioned error in console.
ERROR TypeError: Cannot read property 'forEach' of undefined

I believe this is a duplicate of issue #334.  Unfortunately, there is no resolution yet.

Fixed. ix available in 4.5.0


Please update the server part..

Hello, friend!
I found your project on the github and find it very interesting because of it's simple and clear description.
I have compiled the client part (android) with no problems.
However the server part requirements are outdated.
Running it on the Nodejs 10 with Mysql Community Server 8 (latest by default for Linux Mint) not working and produces errors.
Trying to override defaults to make the MySQL Community Server v5.6.35 appear is the path of pain and potential vulnerabilities.
Please be so kind to update the server sources to the current versions of the software used!
Regards,

Thanks for the interest! However currently I have few time to update this project, so I would appreciate if you can try to make it compatible with latest softwares and fire a PR for that :)


Add support for the Query Metrics

When a request takes more time/RUs than expected, Query Metrics are very useful to have an idea of the problem.
https://docs.microsoft.com/en-us/azure/cosmos-db/optimize-cost-queries#metrics-for-troubleshooting
Would it be possible to add support for Query Metrics like there was in the SDK v2?
I've seen it in the SDK codebase but I can't seem to find any plublic API to access it.

@simplynaveen20 do we have an issue for this? PR  is currently in progress

We will track this  here  https://github.com/Azure/azure-cosmos-dotnet-v3/issues/645


Stoneblock 3 throws unable to locate the installed FTB server jar error

Describe the problem
Not sure if FTB is broken or the me, but it won't work.
The minecraft-data folder:
config
defaultconfigs
eula.txt
ftb-installer
jre
kubejs
libraries
log4jfix
minecraft_server.1.18.2.jar
mods
resourcepacks
run.bat
run.sh
user_jvm_args.txt
version.json

Container definition
version: "3.8"

services:
  mc:
    image: itzg/minecraft-server
    ports:
      - 25566:25566
    environment:
      EULA: "TRUE"
      TYPE: "FTBA"
      FTB_MODPACK_ID: "100"
      MEMORY: 4G
    tty: true
    stdin_open: true
    restart: unless-stopped
    volumes:
      # attach a directory relative to the directory containing this compose file
      - ./minecraft-data:/data

Container logs
[init] ERROR unable to locate the installed FTB server jar
minecraft_server.1.18.2.jar

I am just realy stupid. I forgot to pull the latest docker image. 😓


Properly declare task input for processTestResources task

Fixes #6780

Warnings

:warning:
This PR is approved with no milestone set. If merged, it won't appear in the detekt release notes.

  Generated by :no_entry_sign: dangerJS against 72850188bf69552b3a6e8a43317f970edbfe4930


PSPs: add annotation to allow seccomp profiles

Towards https://github.com/giantswarm/giantswarm/issues/27522

Tested on a WC on Gremlin :+1:


Skinned mesh bounding box gets screwed up sometimes.

http://prntscr.com/ll5z3s
I assume it's from copying skinned mesh from other ava., 0.5b was used.
BB looks kinda the same on all borked ones - at the bottom of feet.

This was caused by the root bone being incorrectly assigned (it generally shouldn't have even been changed). Should be fixed.


Diamondhands review

Current dependencies on/for this PR:

feature/proof-of-stake

PR #578

PR #671

PR #744   👈
PR #703

PR #704

PR #700

PR #701

PR #702

PR #689
PR #676
PR #673
PR #672

This comment was auto-generated by Graphite.


version

Hi,
thanks for your work.
I will try the eventbus, but I dont`t know which version I should use.
Can you give me a hint, which version is most stable?
best regards

We have merged all the clients to Vertx GitHub repo. Please find the updated versions here.
https://github.com/vert-x3/vertx-eventbus-bridge-clients


Moving to Jsdelivr compliance

Adding bower and consistent file naming.
All that is left is tagging the release in Github.  Then it can be submitted to jsdelivr.

I am about to push another commit with lots of changes, so I'll update the filenames with that commit, if that's okay.

@jevy Can you take a look and let me know what else I need to do to the current repo for this? Thanks!


Only generate single contract bindings for ts

+Remove versioning support from contract shims

I have never had to use multiple versions, but it does seem like this could break something in the future. @giuseppecrj @tak-hntlabs wdyt?

I have never had to use multiple versions, but it does seem like this could break something in the future. @giuseppecrj @tak-hntlabs wdyt?

Serge, G and I are going to catch up tomorrow.

I have never had to use multiple versions, but it does seem like this could break something in the future. @giuseppecrj @tak-hntlabs wdyt?

Serge, G and I are going to catch up tomorrow.

The idea (correct me if I'm wrong) is that we will not break the current api of our diamond contracts, we will only add new apis and maybe tweak the underlying behavior of existing apis.
If we ever export new ABIs and our code stops compiling, this should be a red flag.
If we add new features, we should add the ability to query the current contract and get back a feature set (Brian is going to build this right? :) )

If we ever export new ABIs and our code stops compiling, this should be a red flag.

Doesn't happen as often but still happens

we discussed it in the online meeting, in agreement to pick it up


React Component lose context with seq.map

I believe this issue fits best here (although it's also related to React and fluxible).
React Components lose context when used within a seq.map. Possibly due to lazy evaluation.
{Immutable.fromJS([1,2]).toSeq().map(_ =>
    <NavLink routeName="foo">bar</NavLink>)}

This fails with Failed Context Types: Required context getStore was not specified in RouteHandlerStoreConnector.
{Immutable.fromJS([1,2]).toSeq().map(_ =>
    <NavLink routeName="foo">bar</NavLink>)
 .toArray()}

When resolving the sequence explicitly, like above, it works.
Is this expected behavior? My understanding is that converting Immutables to sequences is the recommended procedure before passing them to React.

I highly recommend you open this issue in the React repo. toSeq() produces an iterable, and that iterable is iterated over by the React internals at some point. It's up to React to determine how to do that iteration in a way that guarantees any assumptions it makes about context.
I'm closing this here since it's unsolvable from Immutable.js's point of view, but please reference this issue when you open it on React.


Fix Typedefs for ConsumerGroupStreamOptions

Fixes a mistake in https://github.com/SOHU-Co/kafka-node/pull/1022 where I extended the wrong base interface

test failures were due to travis


add PR title to metadata

@itsdalmo You were the last active on this repository. Would be great if you could help here 🙏

@mjdouble can you follow-up with a rebase? Would be happy to use your fork to utilize this until it is merged into here.
This will be helpful for using commitlint against the PR title to ensure a squash merge will publish packages correctly using lerna.


fix: add user patch and put endpoints

This is needed so that admins can actually modify users to have or not have access to the default resource pool.
We forgot to add these endpoints when we were adding the initial functionality.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

29 of 41 (70.73%)  changed or added relevant lines in 4 files are covered.
19 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 87.298%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

components/renku_data_services/crc/db.py
11
12
91.67%

components/renku_data_services/crc/blueprints.py
10
21
47.62%

Files with Coverage Reduction
New Missed Lines
%

components/renku_data_services/crc/blueprints.py
19
74.67%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
2488

Relevant Lines:
2850

💛  - Coveralls

@mohammad-alisafaee this is ready now


Some minor tweaks to the end game

One consistent end game screen (on finishing a puzzle and navigating back later)
Makes share links show up all the time
Puzzle solution is only shown when you click Reveal (on failure)
Button width is kept consistent so they don't shift on clicking show/reveal

Closes #115

It's a little unsatisfying not to see the whole progression at first when you're done, but overall I like it 😄

For the loss state, it may not be clear you can see the answer. I guess we could put something like. "Nice try! The answer was..." and then fill it on reveal

It's a little unsatisfying not to see the whole progression at first when you're done, but overall I like it 😄

It's easy to show the progression, but I was constrained by wanting to hide the answer by default for failed games. I wanted to keep the fail/success end game consistent and not add another button for showing/revealing the answer. This felt the cleanest. Happy to consider other options if you have ideas.


refactor: restructure code

Codecov Report

Merging #1214 (a743350) into master (d5cd830) will decrease coverage by 0.34%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##           master    #1214      +/-   ##
==========================================
- Coverage   67.87%   67.52%   -0.35%
==========================================
  Files          57       61       +4
  Lines        7247     7299      +52
==========================================
+ Hits         4919     4929      +10
- Misses       2123     2153      +30
- Partials      205      217      +12

Flag
Coverage Δ

unittests
67.52% <50.00%> (-0.35%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

hrp/internal/builtin/utils.go
0.00% <0.00%> (ø)

hrp/step_thinktime.go
0.00% <0.00%> (ø)

hrp/step_transaction.go
22.22% <22.22%> (ø)

hrp/step_api.go
37.83% <37.83%> (ø)

hrp/step_request.go
38.87% <38.87%> (ø)

hrp/step_testcase.go
42.10% <42.10%> (ø)

hrp/step_rendezvous.go
42.71% <42.71%> (ø)

hrp/testcase_config.go
44.85% <44.85%> (ø)

hrp/runner.go
61.18% <62.71%> (+1.40%)
:arrow_up:

hrp/boomer.go
66.15% <66.66%> (-15.10%)
:arrow_down:

... and 11 more

Continue to review full report at Codecov.

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


add WebSocket Client implementation

This PR adds implementation of WebSocketClient based on Swift-NIO

This PR implements https://github.com/IBM-Swift/Kitura-WebSocket-NIO/issues/51

@harish1992 Thanks a lot for your work on this!


Proxy does not work

Describe the bug
It seems like proxies are not working.
My config vite.config.js looks like this(proxy part is copied from the docs):
const config = {
    outDir: '../wwwroot/',
    proxy: {
      '/foo': 'http://localhost:44305/api/get',
      // with options
      '/api': {
        target: 'http://jsonplaceholder.typicode.com',
        changeOrigin: true,
        rewrite: path => path.replace(/^\/api/, '')
      },
    }
};

export default config;

And I'm testing it with following calls:
fetch('/foo');
fetch('/api/test/get')

And both requests are issued to the dev server, http://localhost:3000/ in my case.
Reproduction

Create a blank project with vite
Add 1vite.config.js1 with proxies from the doc
Issue request to /foo or 1/api/anything1 using fetch
Observe that requests are still sent to the dev server, http://localhost:3000/ in my case.

System Info

required vite version: ^1.0.0-rc.9
required Operating System: Windows 10
required Node version: v12.18.1
Optional:

yarn version: 1.22.4
Installed vue version: ^3.0.2
Installed @vue/compiler-sfc version: ^3.0.2

Logs (Optional if provided reproduction)

Run vite or vite build with the --debug flag.
Provide the error log here.

vite v1.0.0-rc.9
vite:config env mode: development +0ms
vite:config env: {} +1ms
vite:config config resolved in 84ms +1ms
vite:optimize Hash is consistent. Skipping. Use --force to override. +0ms
Port 3000 is in use, trying another one...
vite:optimize Hash is consistent. Skipping. Use --force to override. +103ms
Dev server running at:

Network:  http://<IP_ADDRESS>:3001/
Local:    http://localhost:3001/

vite:server server ready in 471ms. +0ms
vite:hmr         / imports /src/main.js +0ms
vite:rewrite (skipped) / +0ms
vite:rewrite /src/main.js: rewriting +40ms
vite:rewrite     "vue" --><EMAIL_ADDRESS>+1ms
vite:hmr         /src/main.js imports<EMAIL_ADDRESS>+41ms
vite:rewrite     "./App.vue" --> "/src/App.vue" +1ms
vite:hmr         /src/main.js imports /src/App.vue +1ms
vite:rewrite     "./index.css" --> "/src/index.css?import" +0ms
vite:hmr         /src/main.js imports /src/index.css +0ms
vite:rewrite (skipped) /vite/client +2ms
vite:resolve (optimized) vue.js -> node_modules.vite_opt_cache\vue.js +0ms
vite:sfc D:\Personal\proxyTest\src\App.vue parsed in 5ms. +0ms
vite:rewrite /src/App.vue: rewriting +22ms
vite:rewrite     "./components/HelloWorld.vue" --> "/src/components/HelloWorld.vue" +9ms
vite:hmr         /src/App.vue imports /src/components/HelloWorld.vue +33ms
vite:hmr ws client connected +2ms
vite:rewrite<EMAIL_ADDRESS>no imports found. +8ms
vite:sfc D:\Personal\proxyTest\src\App.vue parse cache hit +42ms
vite:sfc /src/App.vue template compiled in 7ms. +7ms
vite:rewrite /src/App.vue?type=template: rewriting +27ms
vite:rewrite     "vue.js" --><EMAIL_ADDRESS>+1ms
vite:hmr         /src/App.vue?type=template imports<EMAIL_ADDRESS>+34ms
vite:sfc D:\Personal\proxyTest\src\components\HelloWorld.vue parsed in 1ms. +12ms
vite:rewrite /src/components/HelloWorld.vue: rewriting +4ms
vite:rewrite     nothing needs rewriting. +11ms
vite:sfc D:\Personal\proxyTest\src\components\HelloWorld.vue parse cache hit +22ms
vite:sfc /src/components/HelloWorld.vue template compiled in 4ms. +12ms
vite:rewrite /src/components/HelloWorld.vue?type=template: rewriting +22ms
vite:rewrite     "vue.js" --><EMAIL_ADDRESS>+12ms
vite:hmr         /src/components/HelloWorld.vue?type=template imports<EMAIL_ADDRESS>+49ms
vite:rewrite (skipped) /src/index.css?import +18ms
vite:rewrite (skipped) /src/assets/logo.png +8ms
vite:proxy GET /foo proxy to -> http://localhost:4567/foo +0ms
vite:proxy GET /api/test/get proxy to -> http://jsonplaceholder.typicode.com/test/get +8ms
vite:rewrite (skipped) /favicon.ico +34ms
vite:rewrite (skipped) /test/get +66ms
vite:rewrite (skipped) /foo +2s

From logs I see that targets are resolved correctly but actual requests are sent without rewriting.

The vite:rewrite is represent the es module import path rewriting.The request proxy worked fine and you don't worry for debug logs.

I can't get my proxy working at all :(
(vite.config.js)
export default {   server: {     proxy: {       '/api': 'http://localhost:8000/'     }   } }
`><EMAIL_ADDRESS>dev

vite --debug

vite:config env mode: development +0ms
vite:config env: {} +1ms
vite:config config resolved in 110ms +1ms
vite:resolve (node_module entry) vue -> dist/vue.runtime.esm-bundler.js +0ms
vite:optimize optimizing vue (imports sub dependencies) +0ms
[vite] Optimizable dependencies detected:
vue
Pre-bundling them to speed up dev server page load...
(this will be run only when your dependencies have changed)
Dev server running at:

Local:    http://localhost:3000/
Network:  http://<IP_ADDRESS>:3000/

vite:server server ready in 1513ms. +0ms
vite:hmr         / imports /src/main.js +0ms
vite:rewrite (skipped) / +0ms
vite:rewrite /src/main.js: rewriting +128ms
vite:rewrite     "vue" --><EMAIL_ADDRESS>+2ms
vite:hmr         /src/main.js imports<EMAIL_ADDRESS>+137ms
vite:rewrite     "./App.vue" --> "/src/App.vue" +7ms
vite:hmr         /src/main.js imports /src/App.vue +1ms
vite:rewrite     "./index.css" --> "/src/index.css?import" +0ms
vite:hmr         /src/main.js imports /src/index.css +0ms
vite:rewrite (skipped) /vite/client +70ms
vite:resolve (optimized) vue.js -> node_modules/.vite_opt_cache/vue.js +0ms
vite:hmr ws client connected +87ms
vite:sfc /private/var/www/jukebox/dashboard/src/App.vue parsed in 8ms. +0ms
vite:rewrite /src/App.vue: rewriting +64ms
vite:rewrite     "./components/HelloWorld.vue" --> "/src/components/HelloWorld.vue" +0ms
vite:hmr         /src/App.vue imports /src/components/HelloWorld.vue +48ms
vite:rewrite<EMAIL_ADDRESS>no imports found. +26ms
vite:sfc /private/var/www/jukebox/dashboard/src/components/HelloWorld.vue parsed in 10ms. +65ms
vite:rewrite /src/components/HelloWorld.vue: rewriting +32ms
vite:rewrite     nothing needs rewriting. +0ms
vite:sfc /private/var/www/jukebox/dashboard/src/App.vue parse cache hit +12ms
vite:sfc /src/App.vue template compiled in 38ms. +41ms
vite:rewrite /src/App.vue?type=template: rewriting +44ms
vite:rewrite     "vue.js" --><EMAIL_ADDRESS>+0ms
vite:hmr         /src/App.vue?type=template imports<EMAIL_ADDRESS>+102ms
vite:sfc /private/var/www/jukebox/dashboard/src/components/HelloWorld.vue parse cache hit +3ms
vite:sfc /src/components/HelloWorld.vue template compiled in 17ms. +17ms
vite:rewrite /src/components/HelloWorld.vue?type=template: rewriting +20ms
vite:rewrite     "vue.js" --><EMAIL_ADDRESS>+0ms
vite:hmr         /src/components/HelloWorld.vue?type=template imports<EMAIL_ADDRESS>+19ms
vite:rewrite (skipped) /src/index.css?import +6ms
vite:rewrite (skipped) /src/assets/logo.png +32ms
vite:rewrite (skipped) /favicon.ico +106ms`
vite:history not redirecting /api/user_actions/?format=json (not accepting html) +22s   vite:rewrite (skipped) /api/user_actions/?format=json +4s   vite:history not redirecting /api/user_actions/?format=json (not accepting html) +4s   vite:rewrite (skipped) /api/user_actions/?format=json +4s   vite:history not redirecting /api/user_actions/?format=json (not accepting html) +5s   vite:rewrite (skipped) /api/user_actions/?format=json +5s
I can't understand what I am missing :(


Added two Calculator, Created in C Language and Java

Hi Dear @Rob-Tly
Great code
Thanks for your contribution......
Show your support on my youtube channel web Pixar(The institute of coding)
like , share , subscribe
Youtube - https://youtu.be/5qnQjgdpFPg
Telegram-channel - https://t.me/WebPixar
Join our telegram channel for more goodies , swag packs.
You can also join this Hackathon before 28-oct-2021  -  https://devfolio.co/signup?ref=33d4a02bef


docs: add doc for is_strict_mode flag in HttpOptions

What's Changed in this PR
add doc for is_strict_mode flag in HttpOptions
Checklist

[x] Please ensure that the content in summary.yml matches the current document structure when you changed the document structure.
[ ] This change requires follow-up update in localized docs.

Thank you!
For cross reference, this is for https://github.com/GreptimeTeam/greptimedb/pull/3638#issuecomment-2051840260.

master patch is merged.
What I'm concerned is that if we'll have a 0.7.3 release for these changes. Or if we'd release 0.8.0 directly, we may not add this to 0.7 branch ...

Thanks to @irenjj for this contribution!
@tisonkun I will confirm the version question in the next week.

Sorry for the late reply, we have added a nightly doc dictionary at docs/nightly, which is used for the v0.8 docs.
Could you please merge the main branch, and move the content in this PR to docs/nightly/en/user-guide/operations/configuration.md and docs/nightly/zh/user-guide/operations/configuration.md?
Thank you very much!


Assorted fixes

From the actual fixes here, did you identify things that we could add tests for to make sure we don't regress them?

Verifying cleanup after premature ConnectionInner drop would require exposing e.g. self.connections.len() from the high-level Endpoint, and is then straightforward (just create and immediately drop a connection!)
Close-on-drop can be tested easily by chaining onto the connection driver
Timers not getting scheduled is tricky, because reproducing it relies on arranging for a newly scheduled timeout to be the next wakeup when no other wakeup is expected
Handling of stateless reset of a locally closed connection should admit a unit test
Inducing a connection error and checking for graceful shutdown should be easy enough if we expose is_drained or similar at the high level, then check it after the connection driver completes


[#36] fix: process FormData correctly

Issue
Fixes #36
Details
When calling fetch API in xhrSham.js, pass FormData directly to fetch instead of stringifying it.
CheckList

[x] PR starts with #36
[x] Has been tested (where required) before merge to main.

Yes. I added som tests.

Could you also please publish a new version? It will help people importing the fixed version.

Morning @c0per! - Of course will publish something shortly, ended up being very busy yesterday so open source took a bit of a sideline 😅


Fix messaje -> message

Just correcting a minor spelling error :)
Project looks well polished, GJ @vasilecampeanu!

Thanks for pointing that out and glad to hear that you like the plugin!


Update README.md (im sry)

Line 102. Placed 'also' before the 'includes'.
"That includes also examples of adding popularly requested plugins." ---> "That also includes examples of adding popularly requested plugins."

NOTE
Please verify that the base repository above has the intended destination!
Github by default opens Pull Requests against the parent of a forked repository.
If this is your personal fork and you didn't intend to open a PR for contribution
to the original project then adjust the base repository accordingly.

thanks for the merge (tbh it really bothered me)


XMLMind Editor 3.5.2

Cask for XMLMind Editor 3.5.2, which is an old version but the last one that allows commercial use without purchasing a license.

Are you sure this only works with java6 and not others? Either way, that’s not the correct way to do it (java is a complex issue), and we have a depends_on :java in the works (not yet functional).
A caveat is currently the correct solution for this. Which one depends on if this only works with that version of java or not.
Also pinging @radeksimko on this, as I do with many java-related issues.

Thanks for the feedback. The app does not work with the system Java in Yosemite (1.8.0_25), produces some class conversion errors. With java6 it works fine. I have not tested with java7.
Can you suggest what would be the appropriate caveats stanza in this case? Something like this maybe?
caveats “If XMLEditor does not open files correctly, try installing the java6 cask”

On Jan 16, 2015, at 7:34 PM, Vítor Galvão<EMAIL_ADDRESS>wrote:
Are you sure this only works with java6 and not others? Either way, that’s not the correct way to do it (java is a complex issue), and we have a depends_on :java https://github.com/caskroom/homebrew-cask/issues/7993 in the works (not yet functional).
A caveat is currently the correct solution for this. Which one depends on if this only works with that version of java or not.
Also pinging @radeksimko https://github.com/radeksimko on this, as I do with many java-related issues.
—
Reply to this email directly or view it on GitHub https://github.com/caskroom/homebrew-versions/pull/683#issuecomment-70348646.

I have replaced the java6 dependency with a caveats stanza. In my testing this application does not work with Java 7 or 8, it needs Java 6.

Thank you for the contribution. It will be merged in a different pull request due to some simple recommended alterations. Your contribution is still included (and still credited to you), with the appropriate modifications, when applicable.
Changes:

Facilitated future updates.
Squashed commits.
Removed extraneous line in caveat.

Thanks!

On Jan 22, 2015, at 8:24 AM, Vítor Galvão<EMAIL_ADDRESS>wrote:
Thank you for the contribution. It will be merged in a different pull request https://github.com/caskroom/homebrew-cask/pull/696 due to some simple recommended alterations. Your contribution is still included (and still credited to you), with the appropriate modifications, when applicable.
Changes:
Facilitated future updates https://github.com/caskroom/homebrew-cask/pull/4910.
Squashed commits https://github.com/caskroom/homebrew-cask/blob/master/CONTRIBUTING.md#squashing.
Removed extraneous line in caveat.
—
Reply to this email directly or view it on GitHub https://github.com/caskroom/homebrew-versions/pull/683#issuecomment-71048150.


IntelliJ fix "create toplevel function" seems simply put local function to toplevel

Given:
JsonObject content_json = ...;
String version = meta(content_json);

Auto created:
function meta(Object content_json) => {}

function is invalid for top level function.
=> {} (top level functions more likely use a block

I can't reproduce this using the master version of the plugin. I can think of two possibilities:

you're using an old version of the plugin (like the one in this repository https://downloads.ceylon-lang.org/ide/intellij/development/updatePlugins.xml)
your project isn't set up properly (do you see errors in the Ceylon Problems view?)

After fixing #477 it now generates:
String meta(JsonObject content_json) => "";

you're using an old version of the plugin

Yes.
Updated ceylon plugin, and it works fine.


[P1] Questions on differences between paper and code

Hi pyreft team, thanks for the interesting paper and the open-source library!
We're currently working on integrating a couple of ReFT methods into our AdapterHub Adapters library (see here) and came across a few questions while studying your codebase:
1. Weight tying: In section 4.1 of the paper, the following definition for the tied and untied LoReFT variants is given:

From my intepretation of this definition, in the untied variant, a separate intervention with an independent set of parameters $\phi$ would be added for each intervened position $p$.
However, looking at the implementation, in the untied variant, there seems to be one shared intervention for all prefixes and one shared intervention for all suffixes. E.g. here:
https://github.com/stanfordnlp/pyreft/blob/3a2f19353adbdc1169f05a09ee89c70ea0d65c1b/examples/loreft/train.py#L161-L166
two interventions are created per layer, one for all prefixes and one for all suffixes if share_weights is set to False.
Is my understanding of the paper definition wrong?
2. DiReFT: In section 3.2 of the paper, DiReFT is defined as "(...) an ablation of LoReFT which removes the orthogonality constraint
and the difference operation, reducing training time".
Looking at the implementation in pyreft, two related interventions are defined:

DireftIntervention removes the subtraction of the projected states, but seems to keep the orthogonality constraint:
https://github.com/stanfordnlp/pyreft/blob/3a2f19353adbdc1169f05a09ee89c70ea0d65c1b/pyreft/interventions.py#L151-L152
NodireftIntervention removes both the subtraction and the orthogonality constraint:
https://github.com/stanfordnlp/pyreft/blob/3a2f19353adbdc1169f05a09ee89c70ea0d65c1b/pyreft/interventions.py#L191-L193
Is my understanding correct that DiReFT in the paper corresponds to NoDiReFT in the code and DiReFT in the code is different from DiReFT in the paper?

Thanks in advance for your insights!

@calpt Thanks for your questions! and thanks for integrating ReFT into your library - I haven't looked at your PR yet, but I would certainly be happy to and provide feedback if that's okay.
Here are inline responses to your questions:

Weight tying: In section 4.1 of the paper, the following definition for the tied and untied LoReFT variants ...
Re: I think your interpretation of tied and untied weights is correctly! In our paper, "tied weights" means we only have one intervention per layer. For "untied weights", we have two interventions per layer: one shared among prefix tokens, and one shared among suffix tokens. Our two definitions on pg. 6 could be a little confusing, but essentially they try to illustrate the fact that, we remove the positional dependency, and to have layer-dependent interventions.

This is minor but I also want to call out the intervention config we introduced in the paper itself is also pretty limited. One could also potentially try to tie weights among layers, or among a set of locations and layers, etc.. It would be great if your library could support that! We have limited bandwidth, but are also working towards more flexible intervention schemas.

DiReFT: In section 3.2 of the paper, DiReFT is defined as "(...) an ablation of LoReFT which removes the orthogonality constraint ...
Re: Yes! Our namings are outdated. DiReFT in the paper is actually the NodireftIntervention. We will change this soon, and rename current DireftIntervention to LodireftIntervention!

Thanks for you quick & detailed answers!

I think your interpretation of tied and untied weights is correct! In our paper, "tied weights" means we only have one intervention per layer. For "untied weights", we have two interventions per layer: one shared among prefix tokens, and one shared among suffix tokens. Our two definitions on pg. 6 could be a little confusing, but essentially they try to illustrate the fact that, we remove the positional dependency, and to have layer-dependent interventions.

Got it, this makes sense. Might be useful to correct the definitions in section 4.1 in a future version of the paper to avoid confusion.

One could also potentially try to tie weights among layers, or among a set of locations and layers, etc.. It would be great if your library could support that! We have limited bandwidth, but are also working towards more flexible intervention schemas.

These sound like sensible additional configurations to experiment with and integrate. For now, we try to cover the the essential configurations covered in the paper to make sure we have a first version ready soon. But definitely open to extend beyond this afterwards.


Feasibility study:  How can a user stop Remix /Mix

Currently user kills the app to do this in keeper

Closing as outdated


Integ test fix for testGetWithKeepAliveUpdate

Description
The window build is failing with the given below exception:
Suite: Test class org.opensearch.search.asynchronous.restIT.AsynchronousSearchRestIT
  2> Jan 18, 2023 7:36:20 AM org.opensearch.client.RestClient logResponse
  2> WARNING: request [POST https://localhost:9200/_opendistro/_asynchronous_search?keep_on_completion=true] returned 1 warnings: [299 OpenSearch-2.5.0-b8a8b6c4d7fc7a7e32eb2cb68ecad8057a4636ad "[POST /_opendistro/_asynchronous_search] is deprecated! Use [POST /_plugins/_asynchronous_search] instead."]
  2> REPRODUCE WITH: gradlew ':integTest' --tests "org.opensearch.search.asynchronous.restIT.AsynchronousSearchRestIT.testGetWithKeepAliveUpdate" -Dtests.seed=AA4C903AE61D33F9 -Dtests.security.manager=false -Dtests.locale=en-PH -Dtests.timezone=Asia/Vladivostok -Druntime.java=17
  2> java.lang.AssertionError:
    Expected: a value greater than <1674009382007L>
         but: <1674009382007L> was equal to <1674009382007L>

The problem was the keep_alive was updated with the same value. This PR fixes that issue
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

:exclamation: No coverage uploaded for pull request base (2.5@104b251). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head 09d994e differs from pull request most recent head 7eece12. Consider uploading reports for the commit 7eece12 to get more accurate results

@@          Coverage Diff           @@
##             2.5     #225   +/-   ##
======================================
  Coverage       ?   83.41%
  Complexity     ?      555
======================================
  Files          ?       61
  Lines          ?     2050
  Branches       ?      146
======================================
  Hits           ?     1710
  Misses         ?      232
  Partials       ?      108

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Fix sql query duplication

Rescue camp query set is already being fetched. No second query to the db is required to get the initial entry.
Issue Reference
This PR addresses the Issue : Fixes #519
Summarize
Fetched a single queryset. Used the first entry to be used as initial value of camped_at

@mjzac Can u resolve conflicts..

@sarath263 yep. Fixed those.

Querysets in Django are Lazy.  I don't see how this change would result in fewer queries.
https://docs.djangoproject.com/en/2.1/topics/db/queries/#querysets-are-lazy

@code-haven Here the db call results are being stored into two different variables. Thus the need to reuse result from first db call. Else even if the queryset is lazy, two calls will be triggered.


doc/getting_started.md: Where is Chapter 11?

Hi all,
I am unable to find Chapter 11 in the  Intel Architecture Instruction Set Extensions Programming Reference as stated in doc/getting_started.md.

For detailed information about Intel PT, please refer to chapter 11 of the Intel Architecture Instruction Set Extensions Programming Reference at http://www.intel.com/products/processor/manuals/.

This is the link to the pdf I refer to - https://software.intel.com/sites/default/files/managed/c5/15/architecture-instruction-set-extensions-programming-reference.pdf . There is only up to Chapter 6. Could someone kindly point me in the right direction, please? Thank you.

The link is outdated; I'll fix it.  The documentation can be found in §35 of Vol-3C in the SDM, see https://www.intel.com/sdm.


Remove empty VolumeClaims from StatefulSets

cc @metalmatze @aditya-konarde @kakkoyun
ran into the same issue as: https://github.com/openshift/telemeter/pull/72

Now we just need to rebase obvs/cfg

On it! :blush:


HELP REQUIRED, THERE IS CODE

So my cat just walked over my keyboard and stuff that looks like code appeared on the screen. Is my project still secure?

It's as secure as it was before the cat edited it. Nothing has changed.

What language was it? As per the other answer on this issue your project seems to be completely okay but you might want to delete the code, save and recompile just to make sure.
As a preventative measure regarding future incidents like this, I suggest you stealthily trick your cat into thinking there are better places to hang out on instead of your keyboard though my lack of degree in Feline Psychology suggests that that might be futile :(

@ekavroch Because the code is written by cat, I think it is LOLCODE

My snake went accross the keyboard. It resulted in python being added.

And I spilled my coffee over my keyboard. Guess what happened. Nothing! Since Java is too verbose for nocode.


Make fixed load rate controller honor the target duration

Checklist

A link to the issue/user story that the pull request relates to
[x]  How to recreate the problem without the fix
[x]  Design of the fix
[x]  How to prove that the fix works
[x]  Automated tests that prove the fix keeps on working
Documentation - any JSDoc, website, or Stackoverflow answers?

Issue/User story

When using the fixed load rate controller we did run into issues where a hanging SUT or a suden drop in the SUT's TPS caused our target duration exceeded by a factor of 50.
Steps to Reproduce

Running the benchmarks added in https://github.com/hyperledger/besu/pull/2716 with higher transaction backlogs than used in https://github.com/hyperledger/besu/pull/2716/files#diff-bbce9037b01a9a2ee863e5a760f513e416f2efa57669582a6c316a168044c310 causes this behaviour--e.g. with backlog 300 instead of the used 200. The benchmarks can be executed using cd benchmark && docker-compose -f docker-compose.yml run caliper.
Existing issues

[ ] Stack Overflow issues
[ ] GitHub Issues
[ ] Rocket Chat history

Design of the fix

The total runtime of a round is bounded by twice the target duration. Exceeding it causes aborting with an exception.
The fixed load rate controller is modified to wait indefinitely as long as the target backlog size is exceeded by a factor of more than two.

Validation of the fix

[x] Tested via unit test
[ ] Tested using the above mentioned besu benchmark suite

Automated Tests

Unit tests are adapted and added for the fixed load rate controller.
What documentation has been provided for this pull request

None.

Closing and re-opening to trigger updated CI checks

Related discussion aside, a left-over console statement fails the lint check:
https://dev.azure.com/Hyperledger/Caliper/_build/results?buildId=44734&view=logs&j=6b58850f-3858-5a05-33e2-5e41cbf03c4e&t=19b1bfe6-3af6-53e3-4680-83bf488ecd43&l=78


CASSANDRA-19341: Refactor Relation and Restriction hierachy

The goal of the patch is to simplify the code surrounding the WHERE clause predicates (called internally Restrictions) and made that code easier to extend. For example adding new operators or new type of column expressions require today far more work than should be needed and is error prone as the code need to be modified in different places (Relation, Operator, Restriction classes, StatementRestrictions, ...). The proposed patch should limit those changes to Operator for the addition of new operators and to ColumnExpressions if new expressions (like UDT fields for example) need to be implemented.
The idea behind the patch is that operators can be classified in 3 categories:

Operators that select one or multiple specific values (= and IN)
Operators that select ranges of values (currently: >, >= ,< and <=. In the future != and NOT IN)
Operator that need to be apply to the value for us to know if the value match the predicate (CONTAINS, LIKE, ...)

The combination of operators from type 2 is always producing a set of ranges and the combination of operators of type 1 and 2 is always selecting specific values or none. Operator of type 3 always need an index or filtering.
With that idea in mind it is possible to merge restrictions in a generic way and to avoid to have to hard code that logic for every operator.
The other idea of the patch is to encapsulate the different type of columns expressions (single column, multi-columns, token and map element) into a separate class rather than have a sub-class for each type of expression.
The ClusterElements class has been introducedto bridge the gap between the CQL expression and its internal representation(see javadoc).
To patch make the following changes:

Removes SingleColumnRestriction, MultiColumnRestriction and TokenRestriction. Which are now replaced by 3 new classes:

ColumnsExpression which represent the 4 type of expression supported so far (single column, multi-column, map element and partition key token)
SimpleRestriction which represent a single predicate composed of a column expression, an operator and one or multiple values (for example s CONTAINS 10 or token(pk) > ?)
MergedRestriction which represent multiple predicates on the same column expression (for example: s CONTAINS 10 AND s CONTAINS 11 or token(pk) > ? AND token(pk) <= ?)
Those new classes push some of the logic to the Operator class that has a new API that define how operator are handled by query preparation and query execution.

Removes SingleColumnRelation, MultiColumnRelation and TokenRelation. Those classes are all replaced by the Relation class, which stop being abstract, and by pushing the validation logic into ColumnsExpression and Operator.

Done a first pass. I like the slices approach a lot.

The latest code changes look good to me!

I don't have any further concerns either.


BLAKE3 in OpenCL

have you considered implementing BLAKE3 in the OpenCL language, so that high-speed parallel hashing can be run on GPUs? this might be thousands of times faster than computing the same hash on a general-purpose CPU.
would the portable C implementation be suitable for that?
you can rent NVIDIA GPUs in the Amazon cloud, so this might be quite useful for large-scale hashing applications.
https://aws.amazon.com/ec2/instance-types/p2/
the OpenCL specification is here:
https://www.khronos.org/registry/OpenCL/
how hard would it be to convert the algorithm to OpenCL?

@cesarb did some experimental work on a Vulkan implementation here: https://github.com/BLAKE3-team/BLAKE3/pull/80
I don't know enough about OpenCL to say what code might be usable as-is. The bulk of the C implementation is CPU-instruction-set-specific optimized implementations (AVX-512, AVX2, etc.), and those of course aren't going to be portable to the GPU. However the higher level C code in blake3.c might be portable (though again I don't know much about how OpenCL works). It's organized around a hash_many abstraction, which I assume will map well to how the GPU wants to do things. Even if we can't use that code directly, we'd probably take a similar approach in a rewrite.
At the end of the day though, even if we come up with a good GPU implementation, memory read speed is likely to be a bottleneck. The GPU probably won't be able to read bytes from memory as quickly as it can hash them. If you take a look at Figure 4 in the BLAKE3 paper, you can see the point where we start hitting memory bandwidth problems even on a CPU.


[FEATURE] Add MIT license

I would like the project to adopt the MIT License. This would provide clear guidelines on how the code can be used, modified, and distributed etc.

The license was there previously, but with the start of the monorepo I ended up forgetting to move it to the root. Thanks for reminding me :)


Fix issue where deleting a workspace deletes the PVC incorrectly

What does this PR do?
Fix a regression caused by commit cbd3fd11. When deleting workspaces, if
there are no non-terminating workspaces left in the namespace, we delete
the common PVC rather than running cleanup jobs. However, the way the
check was written assumed that we were counting all workspaces, and
would delete the common PVC if there were two workspaces in a namespace
and one was deleted.
What issues does this PR fix or reference?
Mentioned in review for https://github.com/devfile/devworkspace-operator/pull/846#pullrequestreview-1007392255 -- I'm not sure how I didn't catch it in the original PR; test case was likely missed by me testing

delete a single workspace
delete 3-5 workspaces at once

Closes https://github.com/devfile/devworkspace-operator/pull/871
Is it tested? How?
kubectl apply -f samples/theia-next.yaml
yq '.metadata.name="theia-next-2"' samples/theia-next.yaml | kubectl apply -f -
# wait for workspaces to enter running state
kubectl delete dw theia-next
kubectl get pvc # should not be terminating.

PR Checklist

[ ] E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)

[ ] v8-devworkspace-operator-e2e: DevWorkspace e2e test
[ ] v8-che-happy-path: Happy path for verification integration with Che

Once merged, this PR should be cherry-picked to the 0.15.x branch.

@AObuchow I had made a mistake (>= 0 vs > 0) -- should be fixed now.