Make all Telemetry Objects into SCO's

The OS Threat aim is to blend the OCA extensions, with the existing Stix Incident Management extensions and Identity Contact extensions we currently support.
We think its a perfect match, the Stix Incident Management extensions are focused on providing a single layer, at the Sightings Level, where, provenance for each of the 8 different types of evidence can be gathered, thus evidence can be weighted and the decision process semi-automated (e.g. Assessment of Competing Hypotheses), all in Stix. Stix 21 Evidence Model v8.pptx
Behaviours are just a 9th type of evidence, with a well -defined provenance and much higher weighting. They are the next step up from a basic Sighting Analytic, or OCSF Alert in terms of signal quality and weighting, as they are based on a series of deductions made on telemetry, either a prior-discovered pattern or perhaps as the result of a Hunt. Behaviours are less likely to be a false positive and should be able to generate a call to a CACAO server, to run a CACAO workflow from the library (easy if they are using our OS Threat app).
On the other hand, I can't help but feel that the specificity of the Behaviour SDO, and some of the other great ones (x-oca-detection, x-oca-detector, x-coa-playbook etc.) is diminished by being associated with objects with clearly ambiguous meanings which are purely derived from fixed rules and telemetry. They are observables and should be taken in context:

x-ibm-finding Is this simply the summary OCSF record? An SCO, with refs to other SCO's? Is this observed based on rules?
x-ibm-tagging Should this be weighted as highly or differently to the assignment of a TTP by a human?
x-oca-event, how can this be similar to the Event SDO in Incident Stix extension?? Human decision vs telemetry?
x-oca-geo Is the telemetered location of the same or different value to a human-assigned location??

We found these objects inside the examples I edited, inside an Observed Data object, so they are clearly telemetry.
In our view:

Observables contained within an Observed Data object must form a DAG (Directed Acyclic Graph) -> Stix Best Practices
In the original examples, the above objects are each connected to other SCO's in a DAG, perfect for a single observation (i.e. a simple decomposition process for a composite OCSF object)
Telemetry is fundamentally different to externally assigned evidence.
The report from the inside is different to the external derived report, and the data they hold is often different, although with overlaps (e.g. where would the Asset Registry ID be found, vs the CPU ID? Telemetry Asset SCO, or Asset SDO?
SCO's seem the best objects for holding telemetry, SDO's seem best for human-assigned objects, stored patterns (Behaviours), or known facts (e.g. the current asset list, SBOM's, installed defences (D3FEND), user identities etc)

You guys are the first to innovate by integrating live telemetry into Stix (i.e. Stix-Shifter, Kestrel, Behaviours), and thus you guys are the cutting edge for integration of Stix with OCSF, 3rd-party detection tools and Kestrel hunts.
Thus we are in new territory and need to set the rules.. We believe the basic rule should be that since telemetry is observed, then all telemetry must be SCO's, even when it is a summary object, such as x-ibm-finding, If they are made into SDO's, then it is not clear which data is automatically generated versus, setup through human observation, rules or patterns

At the moment STIX-Shifter is already using many of those fields as SCO's, but if there are changes it makes sense to post an issue on https://github.com/opencybersecurityalliance/stix-shifter/issues so it can be known that there may be differences.

Counter Argument that Says the 4 Objects Should Remain SDO's, and Sightings are Required
The above argument relies on the assertion that the core defining feature of an Observable is the source of the object, So if it is actually observed via telemetry, then one must classify it as an Observable, and it can be contained within the `object_refs' field of an Observed Data object.
But is this conclusion correct? Is the object type classification dependent solely on the object source? Is this the best plan for an Alert, that everything in the Alert is an SCO? IT certainly makes it easier since that is how the code is written presently.
An alternative view might say that Observables are defined as non-termporal objects that exist without a timestamp, whereas an Alert is a temporal object, and thereby x-oca-ibm-finding is a machine-driven SDO, as  is x-oce-event. What matters most in the definition of an Observable is the type of thing being observed being time-independent, and the temporal aspects of an Alert must be handled as SDO's, and Alert telemetry must be modelled as a machine-driven Sighting.
Summary
The key question is how best to classify all of the objects in an Alert.
There are two answers, and each one has merit.
What do you say?

Conclusions - All Telemetry Objects are SCO
After some thought, my conclusion is that:

If there is no clear rule established, or there seems to be conflict in the rules, then we should try to find the strongest and most clearly delineated logic to apply
The simplest logic appears to be, all telemetry is observable, so all telemetry objects must be SCO's
The logic that all data derived from telemetry must become an SCO, also sharply delineates the group, there is no ambiguity in the definition
Making those Stix-Shifter objects SCO's makes it simple for everyone, including that the existing system does not need to change, keep sending everything from Stix shifter as an SCO in an Observed Data object
It has the advantage of dealing formally with these new, more complex observable objects that may be summary records, or describe concepts not currently in Stix
It enhances the reasoning power over the data as the provenance of stix objects is more clearly defined, which is very important

In my simple, non expert viewpoint the picture looks like the below image, and everything delivered from Stix-Shifter should then be an SCO. Consider this simple image about an Alert

If that image is realistic, then my conclusion is that all of those objects should be SCO's


Crash decrypting image

I'm seeing this immediately after pairing a new device on its first attempt to fetch an image. What's weird is that I'm getting this after forgetWifiCredentials() and reset().
Mounting flash filesystem...
I (803) wifi:wifi driver task: 3ffc670c, prio:23, stack:3584, core=0
I (843) wifi:wifi firmware version: 44aa95c
I (843) wifi:config NVS flash: enabled
I (843) wifi:config nano formating: disabled
I (843) wifi:Init dynamic tx buffer num: 32
I (843) wifi:Init data frame dynamic rx buffer num: 32
I (853) wifi:Init management frame dynamic rx buffer num: 32
I (853) wifi:Init management short buffer num: 32
I (863) wifi:Init static rx buffer size: 1600
I (863) wifi:Init static rx buffer num: 10
I (873) wifi:Init dynamic rx buffer num: 32

NodeMCU ESP32 build unspecified powered by Lua 5.1.4 on SDK IDF
Decrypting image number 1...
202688  12      538
Reading encrypted image from 14 len=8677
Decrypting data...
Decrypted data len=8629
ERROR:  network.lua:74: assertion failed!
stack traceback:
        [C]: in function 'assert'
        network.lua:74: in function 'writeFile'
        main.lua:543: in function 'decryptImage'
        boot_next:1: in function 'fn'
        main.lua:174: in function <main.lua:170>
> for k,v in pairs(file.list()) do print(k,v) end
init.lua        90
root.pem        1261

This is running the #327, but it does't really seem that far from what we've got on main.

We've made significant changes to the firmware (upgraded to a new IDF amongst other things) since this was raised; closing as invalid and we can re-raise or re-open if we encounter this issue again.


Can you make this library available in maven repository?

Actually it already is there. You should be able to find it by searching for "pushover" in netbeans but if you are doing it manually Robert Hunt has an example in another issue thread.
https://github.com/sps/pushover4j/issues/5#issuecomment-62642901


Unable to compile a SEQUENCE consisting of CLASS members

Hi,
I am using the latest asn1c compiler (0.9.29) and am unable to compile a SEQUENCE consisting of CLASS members.
A minimum schema to reproduce the issue is attached. ItsRpArea.asn.txt
Below is the compiler output of asn1c -gen-autotools -fcompound-names -Wdebug-compiler -pdu=all ItsRpArea.asn
DEBUG: Compiling Int1 at line 8
DEBUG: expr constraint checking code for Int1
DEBUG: emit tag vectors for Int1 0, 1, 1
DEBUG: Compiling CddLatitude at line 13
DEBUG: Compiling fillBit at line 13
DEBUG: Compiling lat at line 14
DEBUG: member constraint checking code for fillBit
DEBUG: member constraint checking code for lat
DEBUG: Compiling CddLongitude at line 19
DEBUG: expr constraint checking code for CddLongitude
DEBUG: emit tag vectors for CddLongitude 0, 1, 1
DEBUG: Compiling ITS-RParea at line 28
asn1c: asn1_buffer.c:132: abuf_vprintf: Assertion ret >= 0 failed.

Any pointers what is the issue here?

As a broader context, this is an extract from the ISO 17419:2018 standard for ITS Globally Unique Identifiers. The ASN.1 schema is publicly available at https://standards.iso.org/iso/17419/ed-1/en/

This means the compiler ran out of memory.


Azure Functions Create in Python - Add Recommended Tag

For the workflow of creating a new Azure Function in VS Code using the v2 programming model for Python, add a 'Recommended' tag for the option of adding the new function to the main file.

Please file this against the azure functions extension


Implement RedbValue and RedbKey for char

Just noticed that key value impls for char were missing, so I added them.

Merged. Thanks!


Upgrading bootstrap-daterangepicker-rails to the latest version

Old version of DateRangePicker included in this theme has this bug.
So I have upgraded DateRangePicker to the latest version and also moved moment.js to be loaded first before daterangepicker.js as it is needed.
I have upgraded the version of theme to 0.1.11

@JiProchazka Nicely done.  Thanks!
I have released the gem with your changes.

I thanks! Will use it right away!


Hide Properties of header

The form of this title attribute feels a bit strange; what does it look like in VS Code?


Cannot return any type except IMessageActivity from context.Forward()

System Information

SDK Language: .NET

Issue Description
I cannot return any type except IMessageActivity to the ResumeAfter handler of a call to context.Forward. If I try to return any other type, I receive the error: "invalid type: expected Microsoft.Bot.Connector.IMessageActivity, have Boolean"
I want to combine my root LuisDialog and my QnAMakerDialog so that all messages go through Luis first, and if the intent is None, to forward the question to QnA maker, and if the result of the QnAMakerDialog is false, to give them the option to contact a human. I want to keep this routing logic in my LuisDialog, so while I could handle the contact piece inside the QnAMakerDialog, I don't think it makes sense. If there are no results from QnAMaker I want to return context.Done(false) and handle that result in my ResumeAfterFAQ handler.
If I am misunderstanding how context.Forward is designed, please let me know, but it seems like it could handle more use cases if it were more flexible.
Code Example
From my LuisDialog:
        public async Task NoIntent(IDialogContext context, LuisResult result)
        {
            await context.Forward(new FAQDialog(), ResumeAfterFAQ, context.Activity, new CancellationToken());
        }

        private async Task ResumeAfterFAQ(IDialogContext context, IAwaitable<object> result)
        {
             try
            {
                var qnaResult = (bool)await result;

                if (!qnaResult)
                {
                    // Give user option to contact a human
                }
            }
            catch (Exception ex)
            {
                await context.PostAsync($"Failed with message: {ex.Message}");
            }
            finally
            {
                context.Wait(this.MessageReceived);
            }
        }

QnAMakerDialog:
public class FAQDialog : QnAMakerDialog
   {
       protected override async Task DefaultWaitNextMessageAsync(IDialogContext context, IMessageActivity message, QnAMakerResults results)
       {
           if(results.Answers.Count > 0)
           {
               await base.DefaultWaitNextMessageAsync(context, message, results);
           }
           else
           {
               // return false because there were no results
               context.Done(false));
           }
       }
   }

As the error message says it does not work like that.  Your best bet is to call Context.done and handle the handoff to a human based on results >0 or not in your luis dialog or something along those lines.  closing this for now, feel free to reopen if you have any more questions.


Replace nodejs util deprecate

Description
Replace nodejs util deprecate
this function is not supported in edge api

noted that need to handle types in a better way, fixning

following Aviad's feedback, I will think how to implement it on build time instead, though this may take some investigation


Open the quickfix window in NotifierReplay!

NotifierReplay! with a bang should open the quickfix window. In this way it will be analogous to :messages, letting users read the error messages in the replay at their leisure.

Seems to be a good idea, I'll implement that now !


chore: chain naming

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[x] Bugfix

Context

[x] Closes #9855

Did your issue had any of the "$" label on it?

[x] My DOT address: Payout

Copilot Summary
copilot:summary
copilot:poem

thanks!
pay 20 usd

😍 Perfect, I’ve sent the payout
💵 $20 @ 8.92 USD/DOT ~ 2.242 $DOT
🧗 16SjUbGKSdjCdWTy3NNT3JxbRVGGqD4mwkHpc6BD9U2Rp29Z
🔗 0xc1f0861bbcaad7c521b896a8fa24670889dddc85cc0ff48b2980112a65719fac
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Fix the --sync option of sourcekit-lsp

We were waiting for the semaphores outside of the messageHandlingQueue, which means that we didn’t actually block the message handling queue until the previous request received a result, effectively rendering --sync useless.

@swift-ci Please test

@swift-ci Please test Windows


[Bug] simple inheritance

Is there any way to do this?
@Codable
class A {
   var name : String
}
@Codable
class B : A {
   var location : String
}

@Codable
class Container {
    var elements[A] = [ B() ]
}

How do I annotate this so that when Container is decoded the correct instances of A/B are instantiated?
I got dynamic coding with a protocol working but I'd rather not use that. It seems it only works with protocols and enums?
I could code it by hand to work, but it seems the purpose of MetaCodable is to make something like this easy.

I got dynamic coding with a protocol working but I'd rather not use that. It seems it only works with protocols and enums?

@robaho I am assuming you are talking about MetaProtocolCodable, you can use enums without having to use the MetaProtocolCodable. MetaCodable by itself provides untagged, external, internal and adjacent tagging enum decoding functionality. For your use case, it could look something like:
@Codable
struct Container
  let elements: [AOrB]

  @Codable
  @UnTagged
  enum AOrB {
    case b(name: String, location : String)
    case a(name: String)
  }
}

Please use discussion to ask these kind of queries. And use the proper templates when creating issues.


Verify oVirt TLS certificates

This patch adds to the oVirt provider support for checking the TLS
certificates of the server, using the recently introduced
certificate_authority column of the endpoints table.

@Fryguy please review.
/cc @cben

This pull request needs also a change in the ovirt gem, which was included in version 0.15.0. The requirement is updated in ManageIQ/manageiq-gems-pending#67.

Rebased.

 SSL host verification - finilizing

@Fryguy, @blomquisg any objection to merge this?

@Fryguy, @blomquisg note that the existing oVirt/RVH providers will most probably stop working when this is merged, and there will be no way to make them work using the UI till the UI part is merged as well.

To be clear, my ongoing comments are not an objection to merge.  They concern a corner case, and this is strictly more secure than the current situation.

I've opened a docs issue discussing this situation so that we can craft appropriate documentation for users impacted by this change:  https://github.com/ManageIQ/manageiq_docs/issues/244


Allow repo regex to match existing FTP:// entries

Fixes #7

This fix matches the first group of the regex (http://|ftp://).  To fix this issue with regex, what we'd want is the second group.


Update versions of azure-cli azure-cli-core

View a preview at https://prompt.ws/r/Azure/azure-cli/5654
This is an experimental preview for @microsoft users.


Add instructions for using BasicProjector

Obsolete from solution of https://github.com/MadryLab/trak/issues/21.


Fixed LinkedIn links

The LinkedIn hyperlinks on the team page don't point to LinkedIn correctly, which I fixed.
I also noticed that @trappmartin's LinkedIn username wasn't set, so I updated it. Martin, you can delete the linkedin line from the members.yml file if you don't want your LinkedIn to show up on the site.
This will also fix #1161.

Thanks. @phipsgabler could you please add your details.

@trappmartin There's nothing more to add -- I neither have LinkedIn nor a website.

But you are on the list?

Ah sorry, didn't see that. :D


Get HTTP status code in ErrorLink

Our GraphQL backend is built to respond with 403 on authentication error. In that case I would like the Flutter app to throw away the old API token and redirect to a sign in screen. I tried to do this with ErrorLink, and it does catch the error. But I've not found a way to extract the HTTP status code from the ErrorResponse. Is there any way to do that?

Ran into exactly the same problem.
Going beyond the original question, what's the best way to implement token renewal and general retry for gateway failures in graphql 3.1.0?

To answer half of my question, https://github.com/felangel/fresh/tree/master/packages/fresh_graphql seems to work well for token renewal.

In v4 you should be able to get HttpLinkResponseContext from the response, which has the status code


Can't connect to elastic as standalone.

Hello, redacted site's elastic search is available in browser on port 9200.
{
"status" : 200,
"name" : "redacted",
"cluster_name" : "redactedes",
"version" : {
"number" : "1.6.0",
"build_hash" : "cdd3ac4dde4f69524ec0a14de3828cb95bbb86d0",
"build_timestamp" : "2015-06-09T13:36:34Z",
"build_snapshot" : false,
"lucene_version" : "4.10.4"
},
"tagline" : "You Know, for Search"
}
The tool claims following:
[2015-09-21 14:02:16] Error executing request:
[2015-09-21 14:02:16] {"method":"GET","transformRequest":[null],"transformResponse":[null],"url":"http://redacted:9200/","data":{},"params":{},"headers":{"Accept":"application/json, text/plain, /"}}
[2015-09-21 14:02:16] REST API output:

could you describe your setup please?

is kopf installed on elasticsearch, or are you running that directly from somewhere else?
which version of kopf?

in the meanwhile, could you check the Network tab on your browser and see if this request might be failing because CORS is not enabled on elasticsearch?

Yes. I am sorry. I had setup CORS on other node. So I am not sure this was the issue since I was trying several nodes.
I am using it standalone version from my Linux Mint desktop.
After I run npm install, it works just fine.
Thanks for the response.


[HELD 39725] [Wave Collect] [Xero] [Import Flow] Create the main screen (XeroImportPage)

You need to build the main screen for Xero which is called XeroImportPage, following the steps outlined here.
This will be worked on by SWM engineers, see Slack discussion here.
Until the Xero authorization flow (NewDot issue)  is done (which entails NewDot, Web-E and IS changes), we won't be able to work on this yet.

Reviewing now!

Wahoo thanks @filip-solecki!

Same status

Rushat will handle the C+ work here

Nice one!

Deployed to prod two days ago.

@rushatgabhane can you help with the payment summary here for Dylan please?

uno reverse? 😂

Dylan, can you upload your Upwork profile please?

I was being serious 🤠 you know the best whet should be paid for on this issue 😂

I think 500 would be great!

Actually wait, I'm asking for a flat price for all issues combined for @hungvu193 @mananjadhav and me.

So with that, I think we can close this out right?

yes, good to close


Learning curves in IB

Hi,
i am executing benchmark scripts with IB datasets and I am not getting any results. The picture corresponds to the running of BCQ with the IB-Low-100 dataset. Each 10 training epochs I run 100 validation episodes and obtain its mean reward, the result is an horizontal line, no learning takes place.
Thank you for all you answers!

Hi, we run BCQ with IB-Low-100 and found the same trend, even in other level of the IB datasets.
After checking the code and the internal output of the policy, we found the change of the policy (derived from the Q-net where the action is generated by VAE) in IB env is very slow. The latent z in VAE is clipped to (-0.5, 0.5) and sent to the decoder net, and finally activated by tanh. We found z are clipped to -0.5 or 0.5 for most of its dimensions, so that the output actions are nearly the same in the "early" training phase. Maybe the interval (-0.5, 0.5) is narrow and should be expanded on IB, currently, we just follow the originally BCQ implementation.


24.03 QG Update Documentation on Arc42

Issue Description

Problem: Update Documentation

Product Information

Repository Link: vas-country-risk

Tasks

[x] Reformat Arc42: Ensure that the documentation about the App is updated for the QG 24.03 with EDC implementation
[x]  Reformat MD for Converting to PDF: Ensure that the bottom line is not showing when converting
[x] Reformat Images: Ensure that the PDF contain the Images of the docs folder

Quality Gate Done


Operator signature is occasionally 'null'

From Incident #1159:

2014-08-31 18:43, El Weso:
request for rangers at rampart from blackrock.
2014-08-31 18:44, (null):
Rangers to retrieve an anxious participant from rehab room 7

In this example (null) should be El Weso.

I never really figured out how this happened, but the server has been changed to reject any report entry data without an associated user and the client is all new and doesn't appear to exhibit such nasty tendencies, so I think we're good now.

Note that when running the client against a test server using last years' data, the username will obviously still be missing, since it's in the source data.  But no new data should go in like this.

Please verify with [Incidents 3.0a1] (https://github.com/burningmantech/ranger-ims-mac/releases/tag/v3.0a1).


Instructions for replicating font settings

In case anyone else wants to get the font rendering as close to VSCode as possible, these are the settings I arrived upon that I found matched closest:
"ui_font_size": 16,
"buffer_font_size": 13.7037024497986,
"buffer_font_family": "Droid Sans Mono",
"buffer_font_weight": 100,
"buffer_line_height": {
    "custom": 1.35
},

And I made sure to install the Droid Sans Mono font on my system and restart Zed to get it to pick it up. For Linux:
mv DroidSansMono.ttf ~/.local/share/fonts/
rm -r ~/.cache/fontconfig/
fc-cache -r

Yeah. @2zqa Curious, do you think no line highlight is better than having a very subtle line highlight color like that used in the new proposed colors?
Personally I think having a really subtle background color change for the line highlight feels similar to VSCode's top and bottom thin line indicators.

That's a good one, I didn't even consider that option. Good idea.

Perhaps we can add this to the README.md. @MatthewScholefield, do you want to create a PR for this?


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-27-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4158

Questions ?
Please refer to the Backport tool documentation


Add CI pipeline

Try to get basic CI pipeline with ESLint in place to prevent release of code with simple errors or improper formatting

This isn't working yet, the CI run failed on my own fork

Thanks @0xAurelius I went and added prettier to all 3 packages, and integrated it into the build step.
I also integrated eslint in the lib package (its already running on the other 2).

See my recent commits on staging.
Closing this PR-- In the future it will be great to have some github actions for running tests, or for automating regular releases, creating changelogs, etc. But let's keep it lean with just this vercel pipeline, until the upcoming ux overhaul is done!


"show fixes" should behave like suggestion/intellisense with regards to position and mouse

When using "Show Fixes" a popup window might open under the current mouse position, leading to preselection of the item at the mouse position.

It would be nice if the show fixes popup behaves like the auto suggestion/intellisense popup, not preselecting an item because of a mouse hover.

Duplicate of #110594


Attribute "dividerSize" has already been defined

I'm using your horizontalpicker together with weekdatepicker and this error shows up
Error:(218) Attribute "dividerSize" has already been defined

any update,..

I'll add prefix to attributes and I'll try to doit by the end of weekend.

so? I need this for my project

Version 1.1 is available that prefixes all attributes with wdp_. This should fix your problem.


doc update of GovernanceActions and PParams

Description
This PR updates the GovernanceActions and PParams documentation to use macros for consistency of typesetting Agda tokens.
Checklist

[X] Commit sequence broadly makes sense and commits have useful messages
[X] Code is formatted according to CONTRIBUTING.md
[X] Self-reviewed the diff

@Soupstraw , would you be comfortable reviewing this?
@WhatisRT - sorry I clicked the 'request review' button by mistake!

@WhatisRT Can we get this merged?


Sdk3

I wrote this morning on Homey forum.
Here there is the code that add support for a power strip socket made by another manifacturer but same productId and support for Woox R7060.

Hi @rdl987, thanks for your pull request.
I will add the new manufacturerName for the power strip to the code and I will implement support for the smart irrigator using your code/images with some modification to have the code consistent in the app. Eg. I will not merge your code but rather add it manually to the app.
Your help with translation to Italian is very appreciated, I will however add this in a separate update so it will not be part of next update. I hope to have it added asap. Great work!
Credits will be given. :)


chart_title doesn't title subplots

Description
In the server-side Python API, deephaven.plot.figure.Figure.chart_title() does not title a chart. Rather, it titles a figure. It does what I'd expect figure_title() to do.
Steps to reproduce
from deephaven.plot.figure import Figure
from deephaven import read_csv

insurance = read_csv("https://media.githubusercontent.com/media/deephaven/examples/main/Insurance/csv/insurance.csv")

insurance_by_region = insurance.view(formulas=["region", "expenses"]).avg_by(["region"])
insurance_by_sex = insurance.view(formulas=["sex", "expenses"]).avg_by(["sex"])
insurance_by_children = insurance.view(formulas=["children", "expenses"]).avg_by(["children"]).sort(order_by=["children"])
insurance_by_smoker = insurance.view(["smoker", "expenses"]).avg_by(["smoker"])

insurance_cat_plots = Figure(rows=2, cols=2).\
    new_chart(row=0, col=0).\
    plot_cat(series_name="Region", t=insurance_by_region, category="region", y="expenses").\
    chart_title(title="Average charge ($) by region").\
    new_chart(row=0, col=1).\
    plot_cat(series_name="Sex", t=insurance_by_sex, category="sex", y="expenses").\
    chart_title(title="Average charge ($) by sex").\
    new_chart(row=1, col=0).\
    plot_cat(series_name="Children", t=insurance_by_children, category="children", y="expenses").\
    chart_title(title="Average charge ($) per number of children").\
    new_chart(row=1, col=1).\
    plot_cat(series_name="Smoker", t=insurance_by_smoker, category="smoker", y="expenses").\
    chart_title(title="Average charge ($) smokers vs nonsmokers").\
    chart_legend(visible=False).\
    show()

Expected results
A figure with four subplots, one with each title that's given in the code.
Actual results
A figure with four subplots, but only one title atop the figure itself. The first title is the one displayed, while the other three are not visible.
Additional details and attachments

Versions

Deephaven: 0.30.3
OS: OS X
Browser: Chrome
Docker: 20.10.13

The figure_title issue will be fixed with a fix for #1674. The individual chart titles will be a bit trickier, as we need to add annotations to the layout (there is no "chart title" attribute in plotly js as far as I can tell). E.g.:
layout: {
  annotations: [
    {
      "text": "Chart Title",
      "xref": "x domain", // Can reference any xaxis, e.g. x2 domain, x3 domain, etc
      "x": 0.5,  // Center it in the middle
      "y": 1.1,  // Needs to be shown above the chart
      "yref": "y domain",
      "showarrow": false,
      "align": "center"
    }
  ],
  ...
}


Non-asyncio socket read

Add read_socket method that can be used by sockets not managed by asyncio. This should also work with gevent sockets.

Fixed by https://github.com/icgood/proxy-protocol/pull/20.
I decided against a built-in implementation, but it is now possible to build your own PROXY protocol header reader for any byte-stream transport.
Simply parse and handle thrown ProxyProtocolWantReader exceptions, repeating until none are thrown. See ProxyProtocolReader as a reference implementation.


feat: output all packages resulting from split in version 1.31.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Reset the build number to 0 (if the version changed)
[ ] Ensured the license file is being packaged.

In solara version 1.31.0, the package was split into different parts:

The pytest plugin became pytest-ipywidgets
Solara itself was split into solara-ui and solara-server

These packages are all in the widgetti/solara repository, so it makes sense to output them all from here. This should output all packages, and ensure correct interdependency.

@dhirschfeld we spend quite some time understanding why this recipe fails with:
export PREFIX=/home/conda/feedstock_root/build_artifacts/solara_1713540897963/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold
export SRC_DIR=/home/conda/feedstock_root/build_artifacts/solara_1713540897963/test_tmp
import: 'solara_assets'
import: 'solara_assets'
+ pip check
solara-assets 1.31.0 requires solara, which is not installed.
WARNING: Tests failed for solara-assets-1.31.0-pyhca7485f_0.conda - moving package to /home/conda/feedstock_root/build_artifacts/broken
TESTS FAILED: solara-assets-1.31.0-pyhca7485f_0.conda

Can you check this out, if you maybe understand what is going on?
cheers,
Maarten

I'm happy to take a look, though I doubt I have any greater insight on the issue. I probably can't get to it until the weekend though.

We are lost right now, so a fresh look might help, 🙏

It seems that it's just pip check which is failing. It's complaining that solara isn't installed when it quite clearly is:
+ pip check
solara-assets 1.31.0 requires solara, which is not installed.

...but the solara conda pacakage is installed:
    sniffio:                   1.3.1-pyhd8ed1ab_0         conda-forge
    solara:                    1.31.0-pyhd8ed1ab_0        local
    solara-assets:             1.31.0-pyhca7485f_0        local
    solara-server:             1.31.0-pyhca7485f_0        local
    solara-ui:                 1.31.0-pyhd8ed1ab_0        local
    stack_data:                0.6.2-pyhd8ed1ab_0         conda-forge

IMO pip check can be a nice safety net when it works, but IME it reasonably often fails to understand conda packaging.
My view is that it's a tool designed for a different ecosystem and if it works, great - it provides a sense check on your deps, but if it fails for obviously spurious reasons then I just comment it out.
My recommendation here is to just comment out pip check for solara_assets.

xref: https://github.com/pypa/pip/pull/11159#issuecomment-1931983211

I think given that solara-assets is pretty simple, we could skip it indeed. Thanks for this!


Fixing broken UI tests for Text ExplorerTests

Added test functions to searchbar to help fix offscreen elements not being found by automationId
After filtering we then expand all descendants, multiple times to for child dataItems to load
Renamed some test functions to work around test explorer bug where they shorten the function name if it contains the classname.
Change the test function name compare to use "Contains" instead of equals because now test explorer is appending strings like "Not Run" to the test name.

Fix #5693

Reminder to squash commits when merging.


Ontology refactoring

Many classes, properties and individuals from the core namespace are put into content, matching, and ext/demo.
A number of properties that were used in the webapp but never defined have been added to the appropriate ontologies. A few names were changed as well:

won:hasSearchString -> match:searchString
won:hasFile -> con:file
won:hasPetriNet -> con:petriNet
won:hasBpmnWorkflow -> con:bpmnWorkflow
won:hasImage -> con:image
won:hasText -> con:text
won:suggestPostUri -> con:suggestedAtom
won:responseToUri -> con:inResponseTo
won:forResource -> con:feedbackTarget

The won:location property was deleted
EDIT: fixed SearchString -> searchString and cnt:feedbackTarget -> con:feedbackTarget

cnt:feedbackTarget also trying to figure out what cnt means i know con: means content but not sure about the cnt... anyhow i am not sure if the owner webapp changes are all valid, e.g. occurences of won:image and won:file, can you provide us with an actual list of changed attributes (it seems like the one in the pr description is not representing all the renamings) just so we can make sure if any of the old names is still referenced via hardcoded string or referenced from a won.js constant, we had trouble with the GroupSocket in the last renaming cycle as not every occurence was changed from won.WON.GroupFacet to won.SOCKET.GroupSocket it only changed to won.WON.GroupSocket, so maybe there is a problem if the renaming involves both the prefix and name... (e.g afaik won:hasFile should turn into con:file but in the webapp it is only renamed to won:file)

also why is match:SearchString starting with a upper case letter but con:bpmnWorkflow for example isnt, i get that classes/types start with upper case but afaik this isnt one

Oops.. that line should have read

won:forResource -> con:feedbackTarget

Here are the replacements:
won:Bad --> con:Bad
won:BinaryRating --> con:BinaryRating
won:BoundingBox --> con:BoundingBox
won:DirectResponse --> con:DirectResponse
won:Feedback --> con:Feedback
won:Good --> con:Good
won:ServiceBot --> con:ServiceBot
won:binaryRating --> con:binaryRating
won:boundingBox --> con:boundingBox
won:hasBpmnWorkflow --> con:bpmnWorkflow
won:feedback --> con:feedback
won:forResource --> con:feedbackTarget
won:hasFile --> con:file
won:geoSpatial --> con:geoSpatial
won:hasImage --> con:image
won:responseToUri --> con:inResponseTo
won:northWestCorner --> con:northWestCorner
won:hasPetriNet --> con:petriNet
won:southEastCorner --> con:southEastCorner
won:suggestPostUri --> con:suggestedAtom
won:tag --> con:tag
won:textMessage --> con:text
won:travelAction --> con:travelAction
https://w3id.org/won/core#Bad --> https://w3id.org/won/content#Bad
https://w3id.org/won/core#BinaryRating --> https://w3id.org/won/content#BinaryRating
https://w3id.org/won/core#BoundingBox --> https://w3id.org/won/content#BoundingBox
https://w3id.org/won/core#DirectResponse --> https://w3id.org/won/content#DirectResponse
https://w3id.org/won/core#Feedback --> https://w3id.org/won/content#Feedback
https://w3id.org/won/core#Good --> https://w3id.org/won/content#Good
https://w3id.org/won/core#ServiceBot --> https://w3id.org/won/content#ServiceBot
https://w3id.org/won/core#binaryRating --> https://w3id.org/won/content#binaryRating
https://w3id.org/won/core#boundingBox --> https://w3id.org/won/content#boundingBox
https://w3id.org/won/core#hasBpmnWorkflow --> https://w3id.org/won/content#bpmnWorkflow
https://w3id.org/won/core#feedback --> https://w3id.org/won/content#feedback
https://w3id.org/won/core#forResource --> https://w3id.org/won/content#feedbackTarget
https://w3id.org/won/core#hasFile --> https://w3id.org/won/content#file
https://w3id.org/won/core#geoSpatial --> https://w3id.org/won/content#geoSpatial
https://w3id.org/won/core#hasImage --> https://w3id.org/won/content#image
https://w3id.org/won/core#responseToUri --> https://w3id.org/won/content#inResponseTo
https://w3id.org/won/core#northWestCorner --> https://w3id.org/won/content#northWestCorner
https://w3id.org/won/core#hasPetriNet --> https://w3id.org/won/content#petriNet
https://w3id.org/won/core#southEastCorner --> https://w3id.org/won/content#southEastCorner
https://w3id.org/won/core#suggestPostUri --> https://w3id.org/won/content#suggestedAtom
https://w3id.org/won/core#tag --> https://w3id.org/won/content#tag
https://w3id.org/won/core#textMessage --> https://w3id.org/won/content#text
https://w3id.org/won/core#travelAction --> https://w3id.org/won/content#travelAction
WON.Bad --> WONCON.Bad
WON.BinaryRating --> WONCON.BinaryRating
WON.BoundingBox --> WONCON.BoundingBox
WON.DirectResponse --> WONCON.DirectResponse
WON.Feedback --> WONCON.Feedback
WON.Good --> WONCON.Good
WON.ServiceBot --> WONCON.ServiceBot
WON.binaryRating --> WONCON.binaryRating
WON.boundingBox --> WONCON.boundingBox
WON.hasBpmnWorkflow --> WONCON.bpmnWorkflow
WON.feedback --> WONCON.feedback
WON.forResource --> WONCON.feedbackTarget
WON.hasFile --> WONCON.file
WON.geoSpatial --> WONCON.geoSpatial
WON.hasImage --> WONCON.image
WON.responseToUri --> WONCON.inResponseTo
WON.northWestCorner --> WONCON.northWestCorner
WON.hasPetriNet --> WONCON.petriNet
WON.southEastCorner --> WONCON.southEastCorner
WON.suggestPostUri --> WONCON.suggestedAtom
WON.tag --> WONCON.tag
WON.textMessage --> WONCON.text
WON.travelAction --> WONCON.travelAction
WON.BadCompacted --> WONCON.BadCompacted
WON.BinaryRatingCompacted --> WONCON.BinaryRatingCompacted
WON.BoundingBoxCompacted --> WONCON.BoundingBoxCompacted
WON.DirectResponseCompacted --> WONCON.DirectResponseCompacted
WON.FeedbackCompacted --> WONCON.FeedbackCompacted
WON.GoodCompacted --> WONCON.GoodCompacted
WON.ServiceBotCompacted --> WONCON.ServiceBotCompacted
WON.binaryRatingCompacted --> WONCON.binaryRatingCompacted
WON.boundingBoxCompacted --> WONCON.boundingBoxCompacted
WON.hasBpmnWorkflowCompacted --> WONCON.bpmnWorkflowCompacted
WON.feedbackCompacted --> WONCON.feedbackCompacted
WON.forResourceCompacted --> WONCON.feedbackTargetCompacted
WON.hasFileCompacted --> WONCON.fileCompacted
WON.geoSpatialCompacted --> WONCON.geoSpatialCompacted
WON.hasImageCompacted --> WONCON.imageCompacted
WON.responseToUriCompacted --> WONCON.inResponseToCompacted
WON.northWestCornerCompacted --> WONCON.northWestCornerCompacted
WON.hasPetriNetCompacted --> WONCON.petriNetCompacted
WON.southEastCornerCompacted --> WONCON.southEastCornerCompacted
WON.suggestPostUriCompacted --> WONCON.suggestedAtomCompacted
WON.tagCompacted --> WONCON.tagCompacted
WON.textMessageCompacted --> WONCON.textCompacted
WON.travelActionCompacted --> WONCON.travelActionCompacted
won:CounterpartSpecification --> match:CounterpartSpecification
won:Flag --> match:Flag
won:NoHintForCounterpart --> match:NoHintForCounterpart
won:NoHintForMe --> match:NoHintForMe
won:UsedForTesting --> match:UsedForTesting
won:WhatsAround --> match:WhatsAround
won:WhatsNew --> match:WhatsNew
won:doNotMatchAfter --> match:doNotMatchAfter
won:doNotMatchBefore --> match:doNotMatchBefore
won:flag --> match:flag
won:matchingContext --> match:matchingContext
won:searchString --> match:searchString
won:seeks --> match:seeks
won:sparqlQuery --> match:sparqlQuery
https://w3id.org/won/core#CounterpartSpecification --> https://w3id.org/won/matching#CounterpartSpecification
https://w3id.org/won/core#Flag --> https://w3id.org/won/matching#Flag
https://w3id.org/won/core#NoHintForCounterpart --> https://w3id.org/won/matching#NoHintForCounterpart
https://w3id.org/won/core#NoHintForMe --> https://w3id.org/won/matching#NoHintForMe
https://w3id.org/won/core#UsedForTesting --> https://w3id.org/won/matching#UsedForTesting
https://w3id.org/won/core#WhatsAround --> https://w3id.org/won/matching#WhatsAround
https://w3id.org/won/core#WhatsNew --> https://w3id.org/won/matching#WhatsNew
https://w3id.org/won/core#doNotMatchAfter --> https://w3id.org/won/matching#doNotMatchAfter
https://w3id.org/won/core#doNotMatchBefore --> https://w3id.org/won/matching#doNotMatchBefore
https://w3id.org/won/core#flag --> https://w3id.org/won/matching#flag
https://w3id.org/won/core#matchingContext --> https://w3id.org/won/matching#matchingContext
https://w3id.org/won/core#searchString --> https://w3id.org/won/matching#searchString
https://w3id.org/won/core#seeks --> https://w3id.org/won/matching#seeks
https://w3id.org/won/core#sparqlQuery --> https://w3id.org/won/matching#sparqlQuery
WON.CounterpartSpecification --> WONMATCH.CounterpartSpecification
WON.Flag --> WONMATCH.Flag
WON.NoHintForCounterpart --> WONMATCH.NoHintForCounterpart
WON.NoHintForMe --> WONMATCH.NoHintForMe
WON.UsedForTesting --> WONMATCH.UsedForTesting
WON.WhatsAround --> WONMATCH.WhatsAround
WON.WhatsNew --> WONMATCH.WhatsNew
WON.doNotMatchAfter --> WONMATCH.doNotMatchAfter
WON.doNotMatchBefore --> WONMATCH.doNotMatchBefore
WON.flag --> WONMATCH.flag
WON.matchingContext --> WONMATCH.matchingContext
WON.searchString --> WONMATCH.searchString
WON.seeks --> WONMATCH.seeks
WON.sparqlQuery --> WONMATCH.sparqlQuery
WON.CounterpartSpecificationCompacted --> WONMATCH.CounterpartSpecificationCompacted
WON.FlagCompacted --> WONMATCH.FlagCompacted
WON.NoHintForCounterpartCompacted --> WONMATCH.NoHintForCounterpartCompacted
WON.NoHintForMeCompacted --> WONMATCH.NoHintForMeCompacted
WON.UsedForTestingCompacted --> WONMATCH.UsedForTestingCompacted
WON.WhatsAroundCompacted --> WONMATCH.WhatsAroundCompacted
WON.WhatsNewCompacted --> WONMATCH.WhatsNewCompacted
WON.doNotMatchAfterCompacted --> WONMATCH.doNotMatchAfterCompacted
WON.doNotMatchBeforeCompacted --> WONMATCH.doNotMatchBeforeCompacted
WON.flagCompacted --> WONMATCH.flagCompacted
WON.matchingContextCompacted --> WONMATCH.matchingContextCompacted
WON.searchStringCompacted --> WONMATCH.searchStringCompacted
WON.seeksCompacted --> WONMATCH.seeksCompacted
WON.sparqlQueryCompacted --> WONMATCH.sparqlQueryCompacted
won:genre --> demo:genre
won:instrument --> demo:instrument
won:AfterParty --> demo:AfterParty
won:Breakfast --> demo:Breakfast
won:Complaint --> demo:Complaint
won:ConsortiumOffer --> demo:ConsortiumOffer
won:ConsortiumSearch --> demo:ConsortiumSearch
won:HandleComplaint --> demo:HandleComplaint
won:Interest --> demo:Interest
won:Meetup --> demo:Meetup
won:Musician --> demo:Musician
won:PaymentServiceRequest --> demo:PaymentServiceRequest
won:PersonalTransportSearch --> demo:PersonalTransportSearch
won:PhdPosition --> demo:PhdPosition
won:PhdPositionSearch --> demo:PhdPositionSearch
won:PostDocPosition --> demo:PostDocPosition
won:PostDocSearch --> demo:PostDocSearch
won:RealEstateRentDemand --> demo:RealEstateRentDemand
won:RealEstateRentOffer --> demo:RealEstateRentOffer
won:RehearsalRoomRentDemand --> demo:RehearsalRoomRentDemand
won:RehearsalRoomRentOffer --> demo:RehearsalRoomRentOffer
won:SightSeeing --> demo:SightSeeing
https://w3id.org/won/core#genre --> https://w3id.org/won/ext/demo#genre
https://w3id.org/won/core#instrument --> https://w3id.org/won/ext/demo#instrument
https://w3id.org/won/core#AfterParty --> https://w3id.org/won/ext/demo#AfterParty
https://w3id.org/won/core#Breakfast --> https://w3id.org/won/ext/demo#Breakfast
https://w3id.org/won/core#Complaint --> https://w3id.org/won/ext/demo#Complaint
https://w3id.org/won/core#ConsortiumOffer --> https://w3id.org/won/ext/demo#ConsortiumOffer
https://w3id.org/won/core#ConsortiumSearch --> https://w3id.org/won/ext/demo#ConsortiumSearch
https://w3id.org/won/core#HandleComplaint --> https://w3id.org/won/ext/demo#HandleComplaint
https://w3id.org/won/core#Interest --> https://w3id.org/won/ext/demo#Interest
https://w3id.org/won/core#Meetup --> https://w3id.org/won/ext/demo#Meetup
https://w3id.org/won/core#Musician --> https://w3id.org/won/ext/demo#Musician
https://w3id.org/won/core#PaymentServiceRequest --> https://w3id.org/won/ext/demo#PaymentServiceRequest
https://w3id.org/won/core#PersonalTransportSearch --> https://w3id.org/won/ext/demo#PersonalTransportSearch
https://w3id.org/won/core#PhdPosition --> https://w3id.org/won/ext/demo#PhdPosition
https://w3id.org/won/core#PhdPositionSearch --> https://w3id.org/won/ext/demo#PhdPositionSearch
https://w3id.org/won/core#PostDocPosition --> https://w3id.org/won/ext/demo#PostDocPosition
https://w3id.org/won/core#PostDocSearch --> https://w3id.org/won/ext/demo#PostDocSearch
https://w3id.org/won/core#RealEstateRentDemand --> https://w3id.org/won/ext/demo#RealEstateRentDemand
https://w3id.org/won/core#RealEstateRentOffer --> https://w3id.org/won/ext/demo#RealEstateRentOffer
https://w3id.org/won/core#RehearsalRoomRentDemand --> https://w3id.org/won/ext/demo#RehearsalRoomRentDemand
https://w3id.org/won/core#RehearsalRoomRentOffer --> https://w3id.org/won/ext/demo#RehearsalRoomRentOffer
https://w3id.org/won/core#SightSeeing --> https://w3id.org/won/ext/demo#SightSeeing

does not work:

first trial failed when creating needs, claiming that the "con" prefix is unknown, happens when trying to create any atom whose usecase generates a query -> probably because prefixesInPath doesn't contain the "con" prefix,

Fix this please:

probably fixed when looking for prefixesInPath (within the usecase definitions) and adding the missing/new ontology prefixes


Add build options for protocols

https://docs.brew.sh/Formula-Cookbook#adding-optional-steps
https://github.com/d99kris/nchat/blob/master/FLAGS.md

Hi @hybras - thanks for contributing! The patch looks good to me from a quick look. I'll just need to take a closer look and probably try it out on my side before merging. I'll likely get to it in the weekend.

I've merged this now, thanks again for contributing 👍


为毛搜索不到设备，android的却可以 代码是在哪设置？ (IDFGH-3277)

固件版本esp-idf-v3.3，试过各种手机与系统

@AdwardWong  Thanks for reporting, for "how" questions and third party issues, please help raise a post on our forum at https://esp32.com, thanks.

https://github.com/EspressifApp/EspBlufiForiOS/issues/15

Hi @AdwardWong
Sorry, I cannot understand your question, please use proper language and manage your words properly.
Thanks
Weitianhaua

Hi @AdwardWong
I gave it a try, and it works with both Android and ios(iPad(Seventh generation)). I don't know why you can't, would you please help provide more details to help me debug further or you can just close this issue.

No debugging for now


Very sad to know that it will be unsupported

I'm a heavy user of continuation plugin. It's the soul of my own lib erla.
erla makes akka Actor with erlang style.
    val actorB = system.actorOf(Props(new Actor {
      def receive = {
        case x =>
          sender !("got it", x)
          println("actor B reply " + x)
      }
    }))

    val actorA = system.actorOf(Props(new ErlActor {
      def act() = {
        println("actor A started")
        val msg = "hello"
        import akka.pattern.ask
        val replied = await(actorB ? msg)
        println(replied)
        replied match {
          case ("got it", `msg`) =>
            println("works")
          case x =>
            println("wrong: " + x)
        }
      }
    }).withDispatcher("erla"))

Thanks all your works!
I wish I could maintain this amazing plugin, I think there must be some lib/projects need continuation but not just scala-async. But I don't think I have enough skill to do this.
I wish someone could take over it soon.
I love this plugin!
IL

@iron9light https://github.com/jedesah/computation-expressions


Minor fixes to textile ontology

The textile ontology is missing a few documentation properties. E.g.:
<..>
  dcterms:creator "Eva Blomqvist" ;
  dcterms:contributor "Robin Keskisärkkä" ,
                      "Huanyu Li" ,
                      "Mikael Lindecrantz" ;
  dcterms:created "2024-01-18"^^xsd:string ;
  dcterms:description "Textile Use-Case Ontology" ;
  dcterms:license "https://creativecommons.org/licenses/by/4.0/"^^xsd:string ;
  dcterms:title "Circular Economy Ontology Network (CEON) - Textile Ontology"^^xsd:string ;
  vann:preferredNamespacePrefix "textile"^^xsd:string ;
  vann:preferredNamespaceUri "http://w3id.org/CEON/ontology/textile/"^^xsd:string ;
  rdfs:seeAlso <https://github.com/LiUSemWeb/CEON> ;
  owl:versionInfo "0.1" .

The base should probably updated to the ontology prefix:
@base <http://www.semanticweb.org/evabl45/ontologies/2023/8/untitled-ontology-98/> .

Finally, pylode has problems properly splitting URI:s where last part of the name is not a proper qualified name (https://www.w3.org/TR/rdf-syntax-grammar/#section-Serialising), i.e., where it starts with a numer. For example, http://w3id.org/CEON/ontology/textile/75to95Perc could perhaps be renamed as http://w3id.org/CEON/ontology/textile/_75to95Perc or similar?

I think I fixed all the URIs already yesterday. did not add annotations yet, and I can fix the numbers issue of course

(I am btw in a branch called something with textile updates...)


Add Moonlight Sonata 3rd Movement by Beethoven

Song Name
Moonlight Sonata 3rd Movement
Artist Name
Beethoven
Source
Youtube
Youtube Link
6unwFFeNTjQ
Direct File Link
No response
Song ID
624882
Start Offset [ms]
6000
Extra
Created from Auto Nong.
Created for level: 9145341
Downloaded: Yes

please accept

please accept

They're going to take a long time, I think.


Terminology changes in bazel scripts

Quite a few functions in TF bazel scripts can be used on both CUDA and ROCm
platform. In this commit rename them to more generic term:

tf_cuda_* -> tf_gpu_*
cuda_py_* -> gpu_py_*

@yifei, @gunan I think this requires some copybara changes as well?

Thanks @whchung and @rmlarsen. Agree that the naming is confusing now. We also have a bunch of internal targets of those two types as well though. WDYT is the best thing we should do here @gunan?

I do not think this is as straightforward as just renaming. There are some non-opensource google projects which started using these. As soon as this gets submitted, hundreds of internal targets will be broken.
I think this either needs to be done internally, or we need separate targets for rocm and cuda.
It may be tied to the discussion in #20277, so I would like @jlebar to weigh in here as well.

What I did last time I had a renaming change that also affected internal targets was, do the review externally, approve it, import it, and then continue the renaming internally before committing the change.
So it should be possible.  That's separate from the question of whether it's desirable.
@Artem-B might have more concrete thoughts.  To me it seems like you may want a level of indirection between how you spell things in BUILD files and the actual BUILD targets.  Just like we have xla_test(foo) which expands into foo_gpu and foo_cpu (and you could imagine changing this so it expands into :foo_nvgpu, :foo_amdgpu, :foo_cpu), maybe you want tf_gpu_lib that expands into cuda and rocm variants.  Then if you have a tf_rocm mega-library, it can glob together all of the rocm build targets (you can glob based on build tags, not just on name).
So in that sense this CL sort of seems to me like it's going in the right direction.  But again I'd want to know what @Artem-B thinks.

Nagging Assignee @rmlarsen: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @rmlarsen: It has been 29 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Hi @rmlarsen - Just wanted to re-engage on this PR and to discuss the next steps we should take.  In summary, it sounds like there's support for the PR, but there are some non-open source projects that may be affected.
Any thoughts on @jlebar's previously used approach?

do the review externally, approve it, import it, and then continue the renaming internally before committing the change

Hi @thirupalanisamy - Just wanted to check if there are any updates from your side regarding @gunan's comment last week.  Let us know if there's anything we can do to help move this forward.

Thanks fro the ping.
Update: We are started an internal discussion re the scope of work, will
keep you posted.
On Thu, Sep 6, 2018 at 1:58 PM Jeff Poznanovic<EMAIL_ADDRESS>wrote:

Hi @thirupalanisamy https://github.com/thirupalanisamy - Just wanted to
check if there are any updates from your side regarding @gunan
https://github.com/gunan's comment last week. Let us know if there's
anything we can do to help move this forward.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/pull/20996#issuecomment-419238021,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYSlZwk6FwD6vZsn5ZKU_3_WP8m1vxh_ks5uYYyPgaJpZM4VYRW9
.

Nagging Assignee @rmlarsen: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Just wanted to ping this PR with an acknowledgement.  We'll be working on this PR with Gunan's offline suggestions:

rename from tf_cuda* to tf_gpu*
tf_cuda* must remain operational
create new tf_cuda* rules that simply call tf_gpu* rules

@whchung can we close this PR?

The plan is to simplify this PR with the details provided above.

@parallelo OK, I see.
@whchung can you rebase this PR, if you intend to continue working on it?a

FYI - To simplify the process, I just created a replacement PR.  (#22747)


support nested forAll in Gen

A few observations:

Prop is essentially a named Gen[Unit]

The type of Prop.forAll is Gen[T] -> (U -> Boolean) -> Prop

The first two observations suggest: Prop.forAll has type: Gen[T] -> (U -> Boolean) -> Gen[Unit]

A Gen[Unit] is a bit artificial because the test framework halts execution (presumably with an exception) when a counter-example is found. I instead prefer that Prop.forAll has type: Gen[T] -> (U -> Boolean) -> Gen[Boolean]

Now Prop.forAll has the same type as Gen.flatMap[Boolean]

It seems the difference between forAll and flatMap is that forAll conceptually preforms a product operation while flatMap performs a sampling. However, I think they are, in reality, the same operation: sampling.
The implementation for GenProp3 looks like:
for (i <- 0 until p.count) {
  val v1 = g1(p)
  val v2 = g2(p)
  val v3 = g3(p)
  val r = f(v1, v2, v3)
  if (!r) {
    println(s"! ${prefix}Falsified after $i passed tests.")
    println(s"> ARG_0: $v1")
    println(s"> ARG_1: $v2")
    println(s"> ARG_2: $v3")
    assert(r)
  }
}

Which could be re-written as:
for (i <- 0 until p.count) {
  for (v1 <- g1
    v2 <- g2
    v3 <- g3) {
    if (!r) {
      println(s"! ${prefix}Falsified after $i passed tests.")
      println(s"> ARG_0: $v1")
      println(s"> ARG_1: $v2")
      println(s"> ARG_2: $v3")
      assert(r)
    }
  }
}

The primary difference between flatMap and forAll seems to be in error
reporting. So gen is currently a Reader monad on Parameters. If we add a
"forAll stack" to Parameters we could implement forAll as:
def forAll[T,U](gt: Gen[T], gu: T -> Gen[U]): Gen[U] =
  for (t <- gt; u <- local(pushQuantified(t), gu(t)) yield u

def pushQuantified(x: Any)(Parameters p): Paramters =
  new Parameters(p.rng, p.size, p.count, (x :: p.quanitifed))

We'd need to add the local operation to Gen complete the Reader monad:
// in class Gen
def local(modify: Parameters -> Parameters, gu: Gen[U]): Gen[U] =
  Gen { p => gu(modify(p)) }

Finally, the check method can access this stack of quantified variables to provide a useful error message.
Thoughts?

Check is implemented something like:
for (i <- 0 until p.count) {
  (for (successP <- g;
    vars <- getTheForAllStack) {
    if (!successP) {
      printTheVariableStack(vars)
      assert(false)
    })(p)
}

This isn't quite right. The check method will have no way to inspect the context of a sampled value (particularly, the sampled boolean from a proposition).
I think Gen[T] should probably be a Reader[Parameters, (Seq[Any], T)] where the Seq[Any] are the witnesses for each universally quantified variable.

And we can get an implementation of Reader from a library calls cats which provides the Kleisli class. So we'd want to alias Gen[T] as Kleisli[Id, Parameters, T].

Options for nested forAll:
toProp(for (
  j <- forAll(Gen.choose(0, 10000));
  k <- forAll(Gen.choose(0, 10000));
) yield {
  val gt = if (j < k) GTPair(j, k) else GTPair(k, j)
  Genotype.gtPair(Genotype.gtIndex(gt)) == gt
}).check()

forAll(Gen.choose(0, 10000)) { (j: Int) =>
  forAll(Gen.choose(0, 10000)) { (k: Int) =>
    val gt = if (j < k) GTPair(j, k) else GTPair(k, j)
    Genotype.gtPair(Genotype.gtIndex(gt)) == gt
  }
}.check()

I think I can ditch the toProp on the do notation with an implicit conversion.


Copr: Add day_name, day_of_month, day_of_week, day_of_year

Signed-off-by: koushiro<EMAIL_ADDRESS>What have you changed? (mandatory)
implement builtin_time - day_name, day_of_month, day_of_week, day_of_year
What are the type of the changes? (mandatory)

Improvement

How has this PR been tested? (mandatory)
unit test
Does this PR affect documentation (docs/docs-cn) update? (mandatory)
no
Does this PR affect tidb-ansible update? (mandatory)
no
Refer to a related PR or issue link (optional)
#3725

@ice1000 PTAL

Can you extract this error handling code as well?
            return Error::handle_invalid_time_error(
                ctx,
                Error::incorrect_datetime_value(&format!("{}", t)),
            ).map(|_| None);

@ice1000 Done. PTAL again.


Intention is shown if the cursor is placed end of line

if you place the cursor end the of line the Intention is showed when press "ctrl + j"

Exception exception = exchange.getException();<caret>

What intention is shown?
Its a good idea to paste screenshots as it help explain the problems

Dont we want Camels everywhere ;)

No problem with me :-)


fix version check error for minor versions >= 10; fixes #8040

Was hoping to use the semver package but realised this gets run before npm install, so instead just converted the minor versions to numbers before comparing.
I tested it on a bunch of different node versions and it now seems to create the correct output for each version (ie it now accepts 6.10.0).
cheers,
Pete

Thanks 👍


Implement the JavaScript Token Introspection Client

Created by: @marvinkite Jul 15 2020 at 17:56 CET
Last updated: Jul 07 2021 at 09:28 CET
ClickUp ID: IK-49
Write the Client operation to introspect the token by calling the Identity gRPC API.
// TokenIntrospect ...
rpc TokenIntrospect(TokenIntrospectRequest) returns (TokenIntrospectResponse){
option (google.api.http) = {
post: "/identity/token/introspect"
body: "*"
};
}
Service definition:
https://github.com/indykite/jarvis-proto/blob/develop/proto/identity/v1/identity_management_api.proto
SDK acceptance criteria

[x] Documentation is added
[x] Test and/or benchmark are included
[x] Lint check are included (https://www.ictshore.com/javascript/what-is-javascript-linting/)
[x] License can included
[x] Test coverage above 50%

Closed: Apr 13 2021 at 13:37 CET


Invariant Violation: Native module cannot be null. with "preset": "react-native",

Repo: https://github.com/jcollum/kishar-nine/tree/05-testing
Related (closed) https://github.com/facebook/jest/issues/2208
$ versions
npm 3.10.8
node v6.9.1
OS:
ProductName:	Mac OS X
ProductVersion:	10.11.6
BuildVersion:	15G31

$ cat package.json

    "react-native": "~0.39.1",
...
 "jest": {
    "preset": "react-native",
    "testRegex": "./test/.*.js$"
  },
  "devDependencies": {
...
    "jest": "~18.0.0",

$ npm test

><EMAIL_ADDRESS>test /Users/collumj/research/kishar-nine
> jest

 FAIL  test/index.android.js
  ● Test suite failed to run

    Invariant Violation: Native module cannot be null.

      at invariant (node_modules/fbjs/lib/invariant.js:38:15)
      at Linking.NativeEventEmitter (node_modules/react-native/Libraries/EventEmitter/NativeEventEmitter.js:32:1)
      at new Linking (node_modules/react-native/Libraries/Linking/Linking.js:119:141)
      at Object.<anonymous> (node_modules/react-native/Libraries/Linking/Linking.js:191:16)
      at Object.get Linking [as Linking] (node_modules/react-native/Libraries/react-native/react-native.js:91:22)
      at Object.<anonymous> (node_modules/react-native-experimental-navigation/NavigationRootContainer.js:15:36)

The test is pretty simple:
$ cat test/index.android.js
import 'react-native';
import React from 'react';
import Index from '../index.android.js';

// Note: test renderer must be required after react-native.
import renderer from 'react-test-renderer';

it('renders correctly', () => {
  const tree = renderer.create(
    <Index />
  );
});

Steps to reproduce:

git clone https://github.com/jcollum/kishar-nine.git k9fresh
cd k9fresh/
git checkout 05-testing && npm install && npm test

The tests work on the 00 branch but since upgrading react and jest they fail and in a very cryptic way. They don't appear to be actually running.

Did they fail because of the react or because of the Jest update?

$ gd b1d14..041841 package.json
diff --git a/package.json b/package.json
index 030296e..1b7a9f7 100644
--- a/package.json
+++ b/package.json
@@ -20,16 +20,12 @@
   },
   "jest": {
     "preset": "react-native",
-    "globals": {
-      "__DEV__": true
-    },
-    "testRegex": "./test/.*.js$",
-    "rootDir": "."
+    "testRegex": "./test/.*.js$"
   },
   "devDependencies": {
     "babel-jest": "17.0.2",
     "babel-preset-react-native": "1.9.0",
-    "jest": "17.0.3",
+    "jest": "~18.0.0",
     "react-test-renderer": "15.4.1"
   }
 }

Looks like jest. That stuff in there with globals and rootDir made no difference, still failing.

Have you tried using babel-jest v18?

Yes, just did:
$ cat node_modules/babel-jest/package.json | grep version
        "type": "version"
    "type": "version"
  "version": "18.0.0"

collumj@por-collumj-m ~/research/kishar-nine (05-testing) 12:02:12
$ npm test

><EMAIL_ADDRESS>test /Users/collumj/research/kishar-nine
> jest

 FAIL  test/index.ios.js
  ● Test suite failed to run

    Invariant Violation: Native module cannot be null.

      at invariant (node_modules/fbjs/lib/invariant.js:38:15)

Did a full wipe of node_modules, install and test with this package.json:
"dependencies": {
    "lodash": "~4.17.2",
    "react": "15.4.1",
    "react-native": "~0.39.1",
    "react-native-router-flux": "~3.37.0",
    "react-redux": "~4.4.6",
    "redux": "~3.6.0",
    "redux-thunk": "~2.1.0"
  },
  "jest": {
    "preset": "react-native",
    "testRegex": "./test/.*.js$"
  },
  "devDependencies": {
    "babel-jest": "~18.0.0",
    "babel-preset-react-native": "1.9.1",
    "jest": "~18.0.0",
    "react-test-renderer": "15.4.1"
  }

Same result.

Are you sure your tests works on Jest 17?
I've just checkout your branch, check Jest 18 and 17 and both throw the same error.

Did you downgrade RN at the same time? I think that may be where the problem lies:
$ rm -rf node_modules/ && git checkout 02-routing && npm install --quiet && npm test

All tests pass.
Do the same with 03-redux-counter and both tests fail for the Invariant error. Diff the package.json between the two and you see:
$ git diff 02-routing...03-redux-counter package.json
...
-    "react-native": "0.38.0"
+    "react-native": "~0.39.1",

So, should I close this and open it on RN?

Nope, no changes besides Jest. I think RN repo will be a better place to tackle this. Thanks!


Automated cherry pick of #6319: do not close worker chan

Cherry pick of #6319 on release/2.13.
#6319: do not close worker chan

/lgtm

/approve


Unable to read saved model from SMB directory

I am using Tensorflow GPU version 1.1.0, my model can run well if I save it to computer 's hard drives. However, if I save checkpoint files to a samba network drive, I can not restore it and here are the logs.
2017-11-08 17:25:27.795833: I tensorflow/core/common_runtime/gpu/gpu_device.cc:977] Creating TensorFlow device (/gpu:0) -> (device: 0, name: GeForce GTX 1070, pci bus id: 0000:01:00.0)
2017-11-08 17:26:13.335734: W tensorflow/core/framework/op_kernel.cc:1152] Unavailable: /path/to/network/drive/runs/1510129519/checkpoints/model-100.index
2017-11-08 17:26:13.339605: W tensorflow/core/framework/op_kernel.cc:1152] Unknown: /path/to/network/drive/runs/1510129519/checkpoints/model-100.index; Input/output error
2017-11-08 17:26:13.361089: W tensorflow/core/framework/op_kernel.cc:1152] Unavailable: /path/to/network/drive/runs/1510129519/checkpoints/model-100.index
[[Node: save/RestoreV2_2 = RestoreV2[dtypes=[DT_INT32], _device="/job:localhost/replica:0/task:0/cpu:0"](_recv_save/Const_0, save/RestoreV2_2/tensor_names, save/RestoreV2_2/shape_and_slices)]]
^C^C^C^C^C^C2017-11-08 17:26:58.362630: W tensorflow/core/framework/op_kernel.cc:1152] Unavailable: /path/to/network/drive/runs/1510129519/checkpoints/model-100.index
Many thanks

This question is better asked on  StackOverflow since it is not a  bug or feature request. There is also a larger community that reads questions there. Thanks!


AB#3223 Cypress tests for HO Portal

@omendram Apparently I've changed this PR from Draft to a real one... :/ 😨
Apart from the installation-instructions to set-up Cypress on the local dev-environment, this looks good to me. 👍


Add Elasticsearch integration tests

This is heavy WIP (i.e. DO NOT MERGE ATM) but I would love to get more feedback and possibly hints on areas where I am not sure how to move forward. Please read on... (contains questions).
--
General idea
Enable real automated Elasticsearch cluster integration tests for openshift-elasticsearch-plugin. This means automatic ES cluster setup and start before the tests. And ES tear down in the end.
Implementation

[x] Use Elasticsearch test framework (already implemented)
[ ] Generate SSL certificates before each test and point SG configuration to it
[ ] Provide enough HTTP mock services to workaround Kubernetes

The benefits

No need to setup ES manually
Easier understanding of SG and Kibana configuration changes (when doing stack upgrades or more common data model changes)

The following are some questions I would love to discuss more:
Jar Hell
I had to do some simple exclusion work in pom.xml to pass Elasticsearch Jar Hell check.
Security manager issue
Currently, when running from command line or from IDE I need to make sure Java security manager is turned off:
mvn -Dtests.security.manager=false clean test

With security manager I am running into errors like:
access denied ("java.io.FilePermission" "/Users/lvlcek/projects/lukas-vlcek/openshift-elasticsearch-plugin/src/test/resources/elasticsearch/config/admin.jks" "read")

and I do nut fully understand why. Based on this comment it seems this should be doable. I need to investigate this further. May be you have some ideas?
Generate SSL certificates on the fly
Right now, I point SG to jks files in src/test/resource/elasticsearch/config/. At this moment those files are just empty text files and my tests are failing due to this (this is expected). However, my question would be, do you think we will be able to generate these files on the fly or use some other mechanism (ideally maven friendly) to provide SSL certificates and point SG to them?
Mocking Kubernetes
If there will be need to interact with Kubernetes service during tests I hope to be able to implement mock for it (do you see any issues with this?). Heads up remined is that we might need to switch from Mockito to securemock.

@lukas-vlcek This plugin depends upon fabric8 implementation of kubernetes-client/openshift-client which uses okhttp. Additionally, they provide a mock library to be used for testing.  I have not used it, but I believe that would allow you to mock out the back end.  @jimmidyson can you point @lukas-vlcek to examples?

We provide mocks for pretty much everything. Examples in the test cases in the client itself, e.g. https://github.com/fabric8io/kubernetes-client/tree/master/openshift-client/src/test/java/io/fabric8/openshift/client/mock & https://github.com/fabric8io/kubernetes-client/tree/master/kubernetes-tests/src/test/java/io/fabric8/kubernetes/client/mock

ATM I still need to figure out how to configure Java security manager for integration tests. It seems Elastic developers run into the same problem. Let's see if their solution can help us.

closing in favor of #105


chore: add release_please action

Description
Add release-please-action in the release workflow
Related issue
https://github.com/isotope-rs/isotope/issues/1

@AlexsJones could you please take a look and share some feedback?
I was curious to try implementing this enhancement. I configured the release-please-action for one of my toy projects (the pipeline could be found here and made it work in the fist approximation.
Also noticed that release-please doesn't work with ncipollo/release-action@v1 (the latter complains about the "this release already exists"), that's why I had to replace it with a similar action softprops/action-gh-release@v1.
Anyway please let me know what do you think?


Sporadic failure of TestRPCBytes2B

Actual usage of RPC is three times than expected.

Root cause:
https://github.com/hanzezhenalex/raft/blob/master/src/raft/replication.go#L203
heartbeat message contains one command

After I removed command in the heartbeat message, still got this error:

=== RUN   TestRPCBytes2B
Test (2B): RPC byte count ...
test_test.go:185: too many RPC bytes; got 228270, expected 165000
--- FAIL: TestRPCBytes2B (2.81s)

We need to reduce more.
In the current code, we need at least one message for matching. If it's been copied, we only need its term & index.


Inside~ID include machine kaliakair}(„mobile/pull ex2 home_{} Textile#'|Transworld Swift_[S]_School & college ideal

Chaild Care hospital,-īīī-, Saudi Sand/407 pick up~]/``-children_/Energ,_O⟩-WY care,-,-chest#'|New version~2024HAMS GARME”}pro 1055CT·-MA,ī-ī,TV RET-/airport,tongi,konabari, Chandra

★[Stars motor &bettery]:·:#'|\madina///


Fix Scheduler MemorySlot mapping (issue #2704)

Summary
Closes #2704
Details and comments

[x] Remove extra measurement pulses if the circuit doesn't have measures on those qubits

[x] Map acquisitions to the memory slots specified by the circuit

[x] ~Update the condition provided for raising an PulseError when len(acquires) != len(mem_slots) to len(acquires) < len(mem_slots)~

[x] write tests

[x] ~write reno release notes~

Is this ready to go @lcapelluto? It looks good to me.

Fixed in another PR (due to release)

Thank you for the hard work on this, @SooluThomas !


Fix generate script after new snippets

Happy to close if duplicate work

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

(unrelated) there seems to be an issue with "conversational" image-text-to-text snippet where requests is imported and API_URL and headers are defined but not used. I double checked and we are correctly sending the "conversational" tag to getPythonInferenceSnippet. Not sure where this issue comes from 🤔

(unrelated) there seems to be an issue with "conversational" image-text-to-text snippet where requests is imported and API_URL and headers are defined but not used. I double checked and we are correctly sending the "conversational" tag to getPythonInferenceSnippet. Not sure where this issue comes from 🤔

For non-conversational image-text-to-text, we're using the conversational image-text-to-text snippet, this is why we have this weird combination. I will merge this PR but we should fix this by adding image-text-to-text task inputs here to have a proper requests-based snippet when the VLM is not conversational. Note: all warm models in the Inference API are currently conversational VLMs.


VMware Data Disk Supported Size

Upper sections of the article list 8TB as the supported size for data disks,   "Azure VM requirements" section at the bottom lists 4,095 GB.

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

ID: 57139c50-3254-d78a-486c-bea6cbd5885d
Version Independent ID: 6e1a0226-4bea-f720-08cd-77e6dadac264
Content: Support for VMware migration in Azure Migrate - Azure Migrate
Content Source: articles/migrate/migrate-support-matrix-vmware-migration.md
Service: azure-migrate
GitHub Login: @rayne-wiselman
Microsoft Alias: raynew

@bgh00 Thanks for bringing this to our attention. We will review this information with the content/product owner and get back to you shortly.

@bgh00 The supported data disk size is 8 TB. Will fix the documentation.
Pull request reference - https://github.com/MicrosoftDocs/azure-docs-pr/pull/121887


Move random variable outside RandomColorString() method.

Fixes https://github.com/mariusmuntean/ChartJs.Blazor/projects/3#card-28659459.

Actually while you're at it, would you like to fix the Random usage in PointUtil as well? You would rename it to s_rand there too and put a lock around the two NextDouble statements in GetRandomPoint. You could rename this PR to Fix Random usages in utility classes and kill two birds with one stone.
You don't have to, just an idea :)

You would rename it to s_rand there too and put a lock around the two NextDouble statements in GetRandomPoint.

Do you mean to put the lock around the two statements or just around the calls to s_rand?
Like this?
lock(s_rand)
{
    var x = minX + (s_rand.NextDouble() * (maxX - minX));
    var y = minY + (s_rand.NextDouble() * (maxY - minY));
}

Or like this?
lock(s_rand)
{
    var x = minX + (lock(s_rand){s_rand.NextDouble()} * (maxX - minX));
    var y = minY + (lock(s_rand){s_rand.NextDouble()} * (maxY - minY));
}

A single lock around the two NextDouble. You'll have to move the two variables x and y outside the lock of course.
Like this:
int x;
int y;
lock (s_rand)
{
    x = minX + (s_rand.NextDouble() * (maxX - minX));
    y = minY + (s_rand.NextDouble() * (maxY - minY));
}

A single lock around the two NextDouble. You'll have to move the two variables x and y outside the lock of course.

I already assumed that :) Ok, changes will be there soon.

But the variables need to be of type double, I would say

Of course, my bad. I edited my comment but I was a little bit too late I guess :)
Looks good but I have a nitpick. We're not using ColorString inside RandomColorString for whatever reason. When trying to figure out why not, I realized it's because of byte conversion. So here's how I would implement it now. I don't have write access to the fork so I'll post it here like this. The improved method is faster and doesn't use the hardcoded string again but instead delegates it to ColorString to get the same result (I tested it). If you can replace the RandomColorString method body with this, I'll merge it :)
byte[] rgb = new byte[3];
double alpha;
lock (s_rand)
{
    s_rand.NextBytes(rgb);
    alpha = s_rand.NextDouble();
}

return ColorString(rgb[0], rgb[1], rgb[2], alpha);

It's changed now :)

Just an FYI
I wanted to back up by claim that my method was faster and did some extensive benchmarks. It's actually a little bit slower. The difference is almost invisible (~5 ms on 5 million iterations/2.6s). However it does consume a bit less memory (~30mb on 5 million interations/1.3gb).
I don't really know what's better but I came back to this because I thought allocating an array each time might be bad so I tested it. The best option would be to use stackalloc and Span<byte> which seems to allocates less memory (~200mb on 5 million iterations/1.3gb) and is pretty much the same speed as the original method (even less of a difference than the array one).
This is extreme microoptimization and we really shouldn't focus on that but I was curious so there you go.
Maybe I'll put it in but only to satisfy myself, it doesn't do anything for the library except force the dependency on .netstandard 2.1 because of span 😅
Span<byte> rgb = stackalloc byte[3];
double alpha;

lock (s_rand)
{
    s_rand.NextBytes(rgb);
    alpha = s_rand.NextDouble();
}

return ColorString(rgb[0], rgb[1], rgb[2], alpha);

Haha, ok :) Yes, that's micro optimization, but if it uses less memory, why not 😄


hosting our data on self server

Hi,
I am very interested in your services. I have a question, As far as I have understanding of your project that to use your javascript library we have to had an api. It is free. But we must upload or map on your services.is there any way that we host our data ourself?

Hello,
Thank you for your question.  The options for data hosting are discussed in detail here and apply equally to The eeGeo JavaScript API, our Objective C API and our C++ API:
https://github.com/eegeo/eegeo-indoor-maps-api/issues/2

I hope that clarifies things.  Please let us know if you have any further questions.
-John

@johnbell84 thanks for your answer,
But in fact to have a 3d map it is a must to use your API right?and any our application is highly depends into existence of your API ?

With our standard pricing, you are dependent upon our API and our hosting to use our indoor maps.
With our enterprise pricing, you can have on premesis hosting, but you would still be dependent upon our API to use our indoor maps.
I hope this clarifies! Closing issue but please reopen if you need further details.


#451 uses jtag serial feature for println at esp32c6

Thanks! Probably getting https://github.com/esp-rs/esp-println/issues/86 is the best solution

Ok. I close this one then.


Declare Java 8 support deprecated

If we declare Java 8 support deprecated in/before Pekko 1.1.0, we give ourselves the option to remove it in Pekko 1.2.0 (in the spirit of https://pekko.apache.org/docs/pekko/current/common/binary-compatibility-rules.html#when-will-a-deprecated-method-be-removed-entirely).
Depending on feedback we might still decide to keep supporting Java 8 in 1.2.0, but I think deprecating it sends the right message, and it's good to have the option.

Maybe after 1.2.0 ? IIRC, @mdedetrich said they are using Java 8.
We can starting remove deprecated things in 1.2.0 and drop Java 8 （Scala 2.12) support in 1.3.0

The original idea was to drop Java 8 support in 2.0.x, as it is both considered a breaking change and there are also some significant users of Pekko that rely on it.
We can bring it up again on the mailing list, but last time we did it we got pushback

I don't know much about others, but at my company, there is only 13% on Java 11, so we have to publish our internal libraries with <release>8</release>.

The original idea was to drop Java 8 support in 2.0.x, as it is both considered a breaking change and there are also some significant users of Pekko that rely on it.
We can bring it up again on the mailing list, but last time we did it we got pushback

Could you link to this pushback on<EMAIL_ADDRESS>or similar? I searched but couldn't find this thread.

Could you link to this pushback on<EMAIL_ADDRESS>or similar? I searched but couldn't find this thread.

https://lists.apache.org/thread/83xmcls29opo3o8q3mwdhdpqc6bvf69c

small sidebar/rant: I notice that in Pekko it seems relatively common for people to make statements like "it was already decided that X", without linking to the place where that decision was made or documented. I like to think that I'm following Pekko relatively closely, but even for me that makes things hard/frustrating to follow - like now I'm digging through email archives again and none of<EMAIL_ADDRESS><EMAIL_ADDRESS>or<EMAIL_ADDRESS>seem to have particularly relevant hits for 'semver'. I think it would be really good, both for future maintenance and for attracting/retaining new/casual contributors, to make more of a habit of adding relevant links to such statements.

Agreed and apologies for being part of the habit. For me personally I am not that fond/used of mailing lists as a form of discussion as its very hard to search/organize/link (as is evidenced) and so I take the lazy way out. I personally have a preference for doing such discussions using github issues/discussions as you can do things like make a checklist/wiki of relevant discussions so we can easily refer to big decision topics (such as SemVer, dropping JDK8 etc etc)
The issue is that it then it becomes unclear as to whether a discussion should occur on a mailing list or not (as far as I can tell any non trivial decision should occur on mailing list as a vote but I may be wrong here). We can also explore creating a PIP (Pekko Improvement Proposal) process so design guidelines/goals are centralized in one spot with a clear sense of direction rather than discussions being made in various places

apologies for being part of the habit

No problem of course, not trying to point fingers :)

doing such discussions using github issues/discussions

Yeah, references to issues/PRs/discussions/wikis/etc are also useful - while those media have their advantages, none of them are particularly easy to find :)


Drag and drop task card

Drag and drop functionality for tasks that can be moved from one list to another.

Reference:- https://www.w3schools.com/html/tryit.asp?filename=tryhtml5_draganddrop

working on it.

This is completed.


Optional installation of v8js in php-fpm container

Allowing for optional installation of the V8Js extenstion in the php-fpm container.
This is commonly used to facilitate Server Side Rendering (SSR), amongst other purposes.
The V8 binaries were compiled using the following Dockerfile: https://gist.github.com/4c0n/f5aad7f37faee2764418d9793e75401b
(Using the same base image as the official PHP-FPM image that is used to build the laradock php-fpm image).
I completed the 3 steps below:

[x] I've read the Contribution Guide.
[x] I've updated the documentation. (refer to this for how to do so).
[x] I enjoyed my time contributing and making developer's life easier :)

Hi @4c0n
sorry for not response.
if you are still willing send PR.
please rename V8 to V8JS. (Like workspace container ARG: WORKSPACE_INSTALL_V8JS)
and do not add v8.tar.gz, use pecl install v8js.

Hope this will be merged soon or later.
Meanwhile, @bestlong  please can you attach an example of how this will work with pecl?

Hi
i think debian 10 base use pecl install v8js is not good solution.
i will try https://github.com/phpv8/v8js/blob/php7/README.Linux.md
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
不含病毒。www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
CDNRocket<EMAIL_ADDRESS>於 2019年9月10日 週二 上午7:56寫道：

Hope this will be merged soon or later.
Meanwhile, @bestlong https://github.com/bestlong please can you attach
an example of how this will work with pecl?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/laradock/laradock/pull/1772?email_source=notifications&email_token=AA6WMZNWAVPADUDQ6NFSJFTQI3PBVA5CNFSM4FRUXERKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6JMBLY#issuecomment-529711279,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6WMZMBWGOTTPZDZ3CHQPDQI3PBVANCNFSM4FRUXERA
.

--
Yu-Lung Shao 邵玉龍
http://blog.bestlong.idv.tw
http://www.bestlong.idv.tw


fix: hashing empty buffer

i.e. a zero byte file.

in node.js environment, if read a empty file or new Buffer('')
spark-md5 will crash, throw this error:
TypeError: s.substring is not a function
    at md51 (/Users/nos/Documents/GitHub/js-spark-md5/spark-md5.js:177:15)
    at Function.SparkMD5.hashBinary (/Users/nos/Documents/GitHub/js-spark-md5/spark-md5.js:570:20)
    at Function.SparkMD5.hash (/Users/nos/Documents/GitHub/js-spark-md5/spark-md5.js:558:25)
    at Object.<anonymous> (/Users/nos/Documents/GitHub/js-spark-md5/devil.js:3:5)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12)
    at Function.Module._load (module.js:409:3)
    at Function.Module.runMain (module.js:575:10)

it's a problem in here
if the content in buffer does not contain non-ascii charaters, toUtf8 will return str as it was (Buffer(object) in this case).  and there is the bug.
but i can not figure out a way to write test case for this :/
any idea about the spec?
thanks.

below is the devil.js:

const md5 = require('.');

md5.hash(new Buffer(''));


Add a without hash/fragment utility

Describe the feature
Hi :)
This is somewhat related to #190 but I'd like a utility function to remove the hash/fragment from a URL (usually to get info from fragment and redirect afterwards).
I could eventually think of proposing a PR for that if the feature can be considered :)
Additional information

[ ] Would you be willing to help implement this feature?

The withFragment function that I made a PR already supports this if you pass it an empty string (or undefined or null).

withoutFragment will be added to next release as well.


How to send input text to a method, which returns the results into the array to be displayed

My situation is that when the user types in more than 4 characters in the input field, the text needs to be sent to a server by axios, and the resulting list/array has to be shown as the selection list. Currently I'm doing a very roundabout way without any library.

This component doesn't support a lazy/ajax list, but you can make it work with a few custom implementations in your code.
Using the onInput event to fetch the list and bind it to the component. Something like this:
<template>
    <vue3-simple-typeahead:items="list" @onInput="onInput" :minInputLength="4" />
</template>

<script>
import Vue3SimpleTypeahead from<EMAIL_ADDRESS>export default {
    components: {
        Vue3SimpleTypeahead,
    },
    data(){
        list: []
    },
    methods: {
        onInput(event) {
            if (event.input.length > 3) {
                axios
                  .get(`https://api.get/list/${event.input}`)
                  .then(response => (this.list= response));
            } else {
                this.list= [];
            }
        }
    }
};
</script>

I know is not the desired way, but it should work. Let me know if this helps or you need further assintance.


fix(schema): Add missing export for the ForwardGroups decorator

Information

Type
Breaking change

Fix
No

Description
Add missing export for the ForwardGroups decorator to schema.
Usage example
Example to use your feature and to improve the documentation after merging your PR:
import { ForwardGroups } from "@tsed/schema";

Todos

[x] Tests
[ ] Coverage
[ ] Example
[ ] Documentation

Thanks a lot @klotztech ;)

:tada: This PR is included in version 6.43.1 :tada:
The release is available on:

v6.43.1
GitHub release

Your semantic-release bot :package::rocket:


[+] add optional params to verify_credentials

Why did you include your changes to the package.json in your pull request? Can you remove that commit from this pull request so I can merge it?

Sorry, made a new pull request without package.json - https://github.com/reneraab/node-twitter-api/pull/27
Please update when u do npm publish


bug: POST/server/name returns HTTP 500 if input is not valid JSON

Steps to reproduce
POST /server/name with request body that isn't (valid) JSON, like {{{{{.
Current behavior
POST /server/name responds with a 500 internal server error.
Expected behavior
POST /server/name should respond with some kind of invalid request error.

It looks like POST /server/ssh_keys might have the same problem.


Found every instance of the 'asio' namespace, and qualified them unambiguously.

LGTM
Awesome stuff @glynos -- thanks for doing this!
Fixes #634


[BUG] YAMLParseError in statistics

Describe the bug
The statistics are not shown. Instead, I get this (for example):
YAMLParseError: Tabs are not allowed as indentation at line 2, column 1:

	type: bar
	labels: [0,1,2,3,4]
^

To Reproduce
Not sure how to reproduce it. It just shows in my statistics panel.
Expected behavior
Showing the statistics in graph form.
Versions (please complete the following information):

OS: macOS 11.4
Obsidian version: 0.13.5
Plugin version: 1.6.2

Yes I am getting this aswell
not sure if it’s the chart plugin or this plugin at fault

I am getting this error as well.
PS. Is the owner of this project inactive? :frowning_face:

This has been fixed (#351), fix will be available after I'm done with tests.

Should be fixed in v1.7.0

Should be fixed in v1.7.0


Reduce the size of the npm package by limiting the included files

Looks like the files property (https://docs.npmjs.com/files/package.json#files) is not used in package.json to specify the included files, nor is the .npmignore file (https://docs.npmjs.com/misc/developers#keeping-files-out-of-your-package) is being used for blacklisting unwanted files, for the package published to npm.
Would you consider adding either the files property or the .npmignore file, so that the resulting package file would have smaller size?
The current size can be seen when executing the command npm pack (https://docs.npmjs.com/cli/pack).

This issue was create via tawata

$ npm pack
npm notice
npm notice 📦<EMAIL_ADDRESS>npm notice === Tarball Contents ===
npm notice 878B  package.json
npm notice 38B   .travis.yml
npm notice 1.5kB index.js
npm notice 1.1kB LICENSE
npm notice 659B  README.md
npm notice 1.3kB test/index.js
npm notice === Tarball Details ===
npm notice name:          json-buffer
npm notice version:       3.0.1
npm notice filename:      json-buffer-3.0.1.tgz
npm notice package size:  2.6 kB
npm notice unpacked size: 5.4 kB
npm notice shasum:        ad87dcf0a5f46808908afabb9a78f56b6c7f9ef4
npm notice integrity:     sha512-ux2QqRZk3J6u9[...]gDOlnlPyWvTIg==
npm notice total files:   6
npm notice
json-buffer-3.0.1.tgz

After specifying files:
$ npm pack
npm notice
npm notice 📦<EMAIL_ADDRESS>npm notice === Tarball Contents ===
npm notice 911B  package.json
npm notice 1.5kB index.js
npm notice 1.1kB LICENSE
npm notice 659B  README.md
npm notice === Tarball Details ===
npm notice name:          json-buffer
npm notice version:       3.0.1
npm notice filename:      json-buffer-3.0.1.tgz
npm notice package size:  2.1 kB
npm notice unpacked size: 4.1 kB
npm notice shasum:        89e404f3f212488a2fcdff7b413692e256323bc6
npm notice integrity:     sha512-0Oae90UrQ0OZE[...]ZDG+oyjcdJNUw==
npm notice total files:   4
npm notice
json-buffer-3.0.1.tgz


Updated the package description to use the slogan

Coverage remained the same at 99.531% when pulling b10bb36ddd216057584d3793d7e2b5471f98af56 on taras-patch-1 into 0778e0220b227e0730091f41cd83a8ca1bd43988 on master.

Coverage remained the same at 99.531% when pulling b10bb36ddd216057584d3793d7e2b5471f98af56 on taras-patch-1 into 0778e0220b227e0730091f41cd83a8ca1bd43988 on master.

Coverage remained the same at 99.531% when pulling b10bb36ddd216057584d3793d7e2b5471f98af56 on taras-patch-1 into 0778e0220b227e0730091f41cd83a8ca1bd43988 on master.


Improve Issue Finder speed

Description
The Issue Finder was perceived to be slow because of two fetch requests being made and their responses being parsed before the UI could be loaded. This logic has been reordered, enabling the UI to become visible near instantly, while it continues to be hydrated by making requests and parsing responses.
Technical details
Also, the side effect is the reduction of globals and variables scoped to window, so 🎉 !
Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main or master).
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@kgodey this isn't the Lektor-built static page solution that you suggested, but changing the order of rendering does solve most of the performance issues that you pointed out.


File name too long error

Hi,
I'm testing buck on a multi-module project where I'm implementing a micro-service aproach for a system I'm writing.  I've configured okbuck 0.4.10 for my build but when I start to launch it, I get the following error, possibly because it's trying to create a file with concatenated dependency names: -

/Users/nebo/dev/stash/obg2/.okbuck/common_deps/authentication_ui__common_core__app_phoenix__global_ui__authentication_client__content_ui__common_ioc__app_sverigeautomaten__authentication_service__whitelabel_wrapper__common_ui__global_test__content_service__global_core__app_norgesautomaten__content_client/BUCK (File name too long)

The okbuck configuration I'm using is the following: -
okbuck {
target "android-23"
signConfigName "release"
overwrite true
resPackages = [
'App.Phoenix': 'com.phoenix',
'App.Norgesautomaten': 'com.norgesautomaten',
'App.Sverigeautomaten': 'com.sverigeautomaten',
'Global.Core': 'obg.global.core',
'Global.Ui': 'obg.global.ui',
'Global.Test': 'obg.global.test',
'Common.Core': 'obg.common.core',
'Common.Ui': 'obg.common.ui',
'Common.IoC': 'obg.common.ioc',
'Authentication.Client': 'obg.authentication.ioc',
'Authentication.Service': 'obg.authentication.ioc',
'Authentication.Ui': 'obg.authentication.ioc',
'Content.Client': 'obg.content.client',
'Content.Service': 'obg.content.service',
'Content.Ui': 'obg.content.ui'
]
}

Oh, that's because you have some dependencies shared by too much module.
From log you provided, modules are: Authentication.Ui, Common.Core, App.Phoenix, Global.Ui, Authentication.Client... and because OkBuck will create a directory to put these shared dependencies, with all modules name concatenated, in such case, the directory will have a super long name which cause the error.
Now I'm rewriting OkBuck for version 1.0, and I don't want to do too much modification on current version, so my fix may come after a week or two.
Sorry about that :(

@nbthinkful Hi, I just release v1.0.0-beta3, which solve this problem, please try it out!

Tested and I confirm that it solved the problem. I am looking forward for buck to support android databinding so that I can utilise okbuck - buck to the full. Well done, you've done a great job.


Configure view size to allow animation to start at center of view.

Sometimes users want the animation to begin at the middle of the screen instead of at the bottom. Or they want the animation to end early before the element leaves the view. See react-scroll-parallax #157
To allow this an option can be added to scale the view size (the portion of the scroll area where the element animates).
The new option viewportSize should accept pixels or percent values via the box model. Percent would be based off the view size.
viewportSize: [top, right, bottom, left]
Examples
To configure an element to start animating at the middle of the screen the bottom of the view is adjusted to half the view size:
viewportSize: [0, 0, 50%, 0]
To configure an element to end animating at the middle of the screen the top of the view is adjusted to half the view size:
viewportSize: [50%, 0, 0, 0]

Fully support!