New Feat: Added Embedding Callbacks

Added new callbacks:
handleEmbeddingStart: called before embedding is called. It passes serialized embedding class instance and array of texts to the callback function. It passes an array of texts because embedDocuments accepts multiple documents at once. As such, it also passes the single piece of text from embedQuery as an array with length 1.
handleEmbeddingEnd: called after embedding. It passes an array of vectors to the callback function.
handleEmbeddingError: called if there's an error during embed call.
Moreover, there are also some changes that needed to be made to implement these:
Changed Embeddings class such that now child classes implements _embedDocuments and _embedQuery functions since embedDocuments and embedQuery calls handle the callback calls.
Embedding classes are serializable, and added their secrets and aliases.
Moved BaseRetriever into its own file from schema to prevent circular dependency.
Added unit tests for the new callback.

Looks solid to me - I know we're waiting on some other things but excited to have this merged!

I see that there's a new commit that changes how callback manager works (e.g. adding metadata, use BaseCallbackConfig, etc). Should I merge those changes to this pull request or should I wait?

I see that there's a new commit that changes how callback manager works (e.g. adding metadata, use BaseCallbackConfig, etc). Should I merge those changes to this pull request or should I wait?

Yupp good to rebase!

@ppramesi Would it be possible to include not only the vector into the callback payload, but also the token usage? If in doubt, just the complete API response?
I'm only working with OpenAI models at the moment, there the token usage is returned with the API call. I don't know if other embedding models have this too.
However, it would be nice if we could get from the API call not only the pure result, but also the token usage. Having this transported via the callbacks allows the embedding models methods to stay streamlined with their signature, only retrieving the vectors.

@the-powerpointer hmmm I'll have to take a look at the code first. I'll get back to you as soon as I can.

Any news on this? Tracking embeddings token usage is very important, and this PR seems like the viable way to it.

Still delayed unfortunately - will reraise internally!

I was just investigating the usage of embedding models, happy to found this PR. Hope you'll merge it soon, this is much needed 🙏🏼

Would be great if this can be merged. We are currently keep track of each embedding done by different models so if we can somehow get the usage from the vendor itself then it would be amazing.


Error: You must specify options.format

Hello,
I am upgrading the npm dependencies of a project that I have not touched for a while and am getting the following error:
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: You must specify options.format, which can be one of 'amd', 'cjs', 'es', 'iife' or 'umd'
    at error (C:\node_modules\rollup\dist\rollup.js:185:14)
    at checkOutputOptions (C:\node_modules\rollup\dist\rollup.js:10175:3)
    at Object.generate (C:\node_modules\rollup\dist\rollup.js:10237:5)
    at C:\node_modules\rollup-stream\index.js:68:21

I am invoking rollup-stream thusly:
gulp.task('scripts', () =>
    rollupStream({
        input: './js/main.js',
        plugins: [
            rollupBabel({
                exclude: ['node_modules/**', 'gulp/**']
            }),
            nodeResolve({ jsnext: true, main: true }),
            commonjs({ include: 'node_modules/**' })
        ],
        sourcemap: true
    }).pipe(source('main.js', '/.js'))
     .pipe(buffer())
// etc.

I tried adding the output.format key to the config option but that didn't change anything. I am using the following versions:
    "rollup-plugin-babel": "3.0.2",
    "rollup-plugin-commonjs": "8.2.1",
    "rollup-plugin-node-resolve": "3.0.0",
    "rollup-stream": "1.24.1",

Thanks very much!

I tried adding the output.format key to the config option but that didn't change anything.

Could you show me what your gulpfile looked like with this change?

Sure:
gulp.task('scripts', () =>
    rollupStream({
        input: './js/main.js',
        output: {
            format: 'cjs'
        },
        plugins: [
            rollupBabel({
                exclude: ['node_modules/**', 'gulp/**']
            }),
            nodeResolve({ jsnext: true, main: true }),
            commonjs({ include: 'node_modules/**' })
        ],
        sourcemap: true
    }).pipe(source('main.js', '/.js'))
        .pipe(buffer())
       // etc.

rollup-stream interfaces with Rollup's JavaScript API, which doesn't function quite like its config files. I hope to make things more compatible in that respect in a future version. For now, replace output: { format: 'cjs' } with a simple format: 'cjs', like this:
gulp.task('scripts', () =>
    rollupStream({
        input: './js/main.js',
        format: 'cjs',
        plugins: [
            rollupBabel({
                exclude: ['node_modules/**', 'gulp/**']
            }),
            nodeResolve({ jsnext: true, main: true }),
            commonjs({ include: 'node_modules/**' })
        ],
        sourcemap: true
    }).pipe(source('main.js', '/.js'))
        .pipe(buffer())
       // etc.

See here for the available options: https://rollupjs.org/#big-list-of-options


Relational Operators are flagged red in highlighter

Using the example script here: https://gist.github.com/kindlich/9840f695dce5a4b78f78599ff6c1232c in lines 113 and 122, the use of the relational operators seems to mark them red falsely, most likely thinking it's an IItemStack.

Could you add a screenshot of what you mean?

https://imgur.com/a/Vdptn

fixed in 4d4f6c28ddcd9c29950409e37505a5bf29389132


Remove stray line

Looks like the cat may have stepped on the keys Gyypx just prior to commit. :)

Bruh XD
I legit didn't noticed haha! Thanks :+1:

ah dammit
I clicked close instead of merge, ok holup, lemme see if i can reopen it

There we go!


92 brand link component

closes #92
Hi, let me know if you require any changes.
for example may need to:

change example logo
add Brand component on more examples in docs
add title attribute on img
add custom class on img
change naming

This looks really good! Thanks for submitting this.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


InstanceGenerator does not support Q objects in limit_choices_to.

autofixture.generators.InstanceGenerator fails when you defined your model with a Q object in limit_choices_to.  InstanceGenerator assumes that limit_choices_to is always a dictionary.
It looks like InstanceSelector has the same issue.

Closing this due to inactivity. Comment here again if you still have questions about this.


Only for Android API 23 and above

Isn't that less than 1% of Android sharing?
Shouldn't be compatible with API 14 or so?

+1, was trying like crazy to make it work on 19, never managed to work, at least on 21, it kinda work, i can make some basic post


Bump Dependencies #145

Bumps dependencies for product-is.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jenkins-is-staging seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

https://github.com/wso2/product-is/pull/6384


Add prisma2 studio to CLI help/docs

In reference to https://github.com/prisma/prisma2/issues/657
When running prisma2 cli, it does not show prisma2 studio as one of the possible commands in help. It may need to be added there.

Internal Note: Dropping from current sprint, and picking up later.

Internal Note: Dropping from current sprint, and picking up later.

studio is now listed:
λ prisma2 --help --experimental

Prisma is a modern DB toolkit to query, migrate and model your database (https://prisma.io)

Usage

  $ prisma2 [command]

Commands

            init   Setup Prisma for your app
      introspect   Get the datamodel of your database
        generate   Generate artifacts (e.g. Prisma Client)
         migrate   Migrate your schema (experimental)
          studio   Run Prisma Studio (experimental)


Update README.md

Added gitter.im info
Updated capabilities summary and areas that need contribution

merged.


Prefilled text fields aren't working well

What RMWC Version are you using [major.minor.patch]:

6.1.0

Name your build system [Webpack, Rollup...]:

Default setup that Next.js uses (pretty sure it's webpack).

Describe the bug with as much detail as possible:

Your fix to #601 was awesome, but it doesn't look like it's working properly:

And I'm not referring to the label not floating after the text field is filled. I'm referring to the notch not closing up again when the label isn't floating.
You can see the basic recreation here.

What happened, and what was supposed to happen:

The notch should close and the placeholder should no longer be width constricted when floatLabel is false.

FYI @jamesmfriedman this is the project that your component library has been put so hard to work on (if you're curious)! Feel free to send me any feedback on it.

Looks great! Hopefully the good has outweighed the issues you’ve hit.

Any fix on this yet @jamesmfriedman? I'm waiting on it to push to production.


Understand how Stream Analytics sends data to Service Bus

I noticed that there are three formats that Stream Analytics can use to send data to service bus - but even when selecting JSON there is some sort of serialization wrapper around the data when it's extracted from a Service Bus Queue. The body is NOT pure JSON. I can find no docs on what the specific format is.

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

ID: 2896ae0e-a559-64c7-1782-14ef1c83f509
Version Independent ID: fdc01b78-9222-6231-f85e-68defe4eafa9
Content: Understand outputs from Azure Stream Analytics
Content Source: articles/stream-analytics/stream-analytics-define-outputs.md
Service: stream-analytics
GitHub Login: @JasonWHowell
Microsoft Alias: jasonh

        using (var ms = new System.IO.MemoryStream(message.Body))
        {
            using (var reader = XmlDictionaryReader.CreateBinaryReader(ms, new XmlDictionaryReaderQuotas()))
            {
                var bf = new DataContractSerializer(typeof(string));
                var obj = bf.ReadObject(reader);
            }
        }

@AdamPliska Thanks for the feedback! We are currently investigating and will update you shortly.

@JasonWHowell Any insights on this?

@AdamPliska was the previous suggestion helpful to resolve your issue? Are you still blocked?

@AdamPliska We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Fix TypeScript lint errors

Pull Request Description
Should fix TypeScript lint errors.
These errors do not show up locally as the imports point to built assets.
Important Notes
None
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

opening as draft to confirm whether the fixes actually work

not quite sure whether this actually works. lint is green, however it's entirely possible it's because this runner already has the relevant build artifacts from a previous run. (i don't know how exactly the CI runners work around here)

This PR does make this change for consistency:
To make sure that it does the same thing, I'm running ide watch which imports content-config via content/index.ts. To test it I think making sure option parsing still works should be sufficient.
-import * as linkedDist from '../../../../../target/ensogl-pack/linked-dist/index'
+import * as linkedDist from '../../../../../target/ensogl-pack/linked-dist'

https://github.com/enso-org/enso/blob/27bbfe1030dff1c4b26532003843d1af07d4401e/app/ide-desktop/lib/content-config/src/index.ts#L5

status update: wasm failed to build with the classic:
 INFO ide_ci::program::command: npx⚠ ▲ [WARNING] "import.meta" is not available with the "cjs" output format and will be empty [empty-import-meta]
 INFO ide_ci::program::command: npx⚠
 INFO ide_ci::program::command: npx⚠     pkg.js:4214:39:
 INFO ide_ci::program::command: npx⚠       4214 │         input = new URL('pkg_bg.wasm', import.meta.url);
 INFO ide_ci::program::command: npx⚠            ╵                                        ~~~~~~~~~~~
 INFO ide_ci::program::command: npx⚠
 INFO ide_ci::program::command: npx⚠   You need to set the output format to "esm" for "import.meta" to work correctly.
 INFO ide_ci::program::command: npx⚠
 INFO ide_ci::program::command: npx⚠ ✘ [ERROR] Could not resolve "env"
 INFO ide_ci::program::command: npx⚠
 INFO ide_ci::program::command: npx⚠     pkg.js:16:29:
 INFO ide_ci::program::command: npx⚠       16 │ import * as __wbg_star3 from 'env';
 INFO ide_ci::program::command: npx⚠          ╵                              ~~~~~
 INFO ide_ci::program::command: npx⚠
 INFO ide_ci::program::command: npx⚠   You can mark the path "env" as external to exclude it from the bundle, which will remove this error.
 INFO ide_ci::program::command: npx⚠
 INFO ide_ci::program::command: npx⚠ ▲ [WARNING] The CommonJS "exports" variable is treated as a global variable in an ECMAScript module and may not work as expected [commonjs-variable-in-esm]
 INFO ide_ci::program::command: npx⚠
 INFO ide_ci::program::command: npx⚠     snippets/ensogl-text-msdf-a35c812d6b3d67d9/msdfgen_wasm.js:1:940548:
 INFO ide_ci::program::command: npx⚠       1 │ ...f(typeof exports==="object"){exports.ccall=ccall;exports.getValu...
 INFO ide_ci::program::command: npx⚠         ╵                                 ~~~~~~~
 INFO ide_ci::program::command: npx⚠
 INFO ide_ci::program::command: npx⚠   This file is considered to be an ECMAScript module because of the "export" keyword here:
 INFO ide_ci::program::command: npx⚠
 INFO ide_ci::program::command: npx⚠     snippets/ensogl-text-msdf-a35c812d6b3d67d9/msdfgen_wasm.js:2:2:
 INFO ide_ci::program::command: npx⚠       2 │ ; export { ccall, getValue, _msdfgen_getKerning, _msdfgen_setVariat...
 INFO ide_ci::program::command: npx⚠         ╵   ~~~~~~
 INFO ide_ci::program::command: npx⚠
 INFO ide_ci::program::command: npx⚠ 2 warnings and 1 error

Oh, I understand this is fixing the CI errors we have now? If so, few questions:

Why did we merge a PR to develop which is breaking the CI? Was the CI working on the merged PR? How did it happen?
You've written These errors do not show up locally as the imports point to built assets. - but the CI is doing exactly the same things what you do locally, it is just running the ./run script, so how the results could be different?

As this fixes CI, Im merging it, but let's continue the discussion about the points above here please @somebody1234 .

why did we merge a PR that broke the CI?

afaict, CI was working. still not sure why it breaks sometimes

the CI is doing exactly the same things what you do locally

i'm guessing the issue only appears on a fresh runner, which doesn't have build.json and ensogl-pack/linked-dist, so when TS tries to find the files, it can't find anything

why did we merge a PR that broke the CI?

afaict, CI was working. still not sure why it breaks sometimes

the CI is doing exactly the same things what you do locally

i'm guessing the issue only appears on a fresh runner, which doesn't have build.json and ensogl-pack/linked-dist, so when TS tries to find the files, it can't find anything

Ah, gotcha! Ok, that makes sense. Would you be so nice and also take a look at my code comment above? :)


Max button appears only after typing something on the input

For tokens != XLM , Max should appear immediately and use all balance
for XLM, it should use available balance (not user XLM balance), simulate networkFees with trustlineWallet


[Feature Request] Add File type like PDF and CBZ

Checklist

[X] This issue contains only one feature request. I will open one issue for every feature I want to request.
[X] I checked, but didn't find any duplicates (open OR closed) of this issue in the repo.
[ ] This feature is merely an UI/UX update.
[X] This feature is not going to conflict with many of the existing features/options.

Is your feature request related to a problem? Please describe.
It doesn't have an option to add PDF or CBZ file types.
Describe the solution you'd like
I need this feature to add and read PDF or CBZ related books.
How will you/everyone benefit from this feature?
Most people download PDF or CBZ type so they can easily add the file directly to the app and read. by that downloading people will be increased.
Additional context
it's one of the features most people like.

Myne is not built to be a PDF/CBZ reader; it was primarily built as a client for the Gutenberg library. The app didn't even have the ability to import external EPUB files a few versions ago. However, many people have requested this feature, and since we already had an EPUB parser in place to parse internal (Gutenberg) books for the inbuilt ebook reader, I thought it wouldn't hurt to allow users to import their external EPUB files as well. This way, they can be parsed with the same EPUB parser. So, in the last few versions, I have mostly worked on improving the EPUB parser to better support various types of EPUB files. However, parsing PDF/CBZ is a whole different story, as it was never designed to handle those formats and seems totally out of scope for the app's intended functionality.


Localization:  Add tutorial for map generation && fix some scripts.

Please check: 1)In preparation part, localization data from [Apollo Data Open Platform] should be specified. Because there are so many datasets on the page. 2)The "Multi-Sensor Fusion Localization Data" can't be downloaded successfully either from US or China. 3)Why is the dataset "US only"? Even in the Chinese tutorial?

Please check: 1)In preparation part, localization data from [Apollo Data Open Platform] should be specified. Because there are so many datasets on the page. 2)The "Multi-Sensor Fusion Localization Data" can't be downloaded successfully either from US or China. 3)Why is the dataset "US only"? Even in the Chinese tutorial?

The name of localization data has been specified.
The data is stored on a server in Hong Kong from Baidu Cloud. Maybe it will be slow if downloaded from the US.
The demo data is collected from US, it contains high-precision map data. There may be some legal risks if we do not limit the open area. The Chinese document is for native Chinese speakers living in the US.


:arrow_up: Update colors dependency

No breaking changes.
It might be a good idea to prefer explicit over implicit though (colors.green('hello') instead of 'hello'.green). I guess this is a matter of taste, but extending prototype does not sound clean to me.

Yeah, definitely, given the fact that this is a library, it is not a good practice to extend prototypes.


address additional comments from pr #10259

https://github.com/kubernetes/website/pull/10422 merged into 1.12 branch.
Picking into master
cc @soltysh

A rebase is needed to resolve the conflicts, otherwise this one looks good to me.

@tengqm Thanks, rebased PR

/lgtm
/approve


[ADDON] - Grafana Promtail

Add support for Grafana Promtail as an add-on.
https://github.com/grafana/helm-charts/tree/main/charts/promtail

Closed in #898


GBIF participant page (i.e. country pages)

To replace the current country pages, simplifying them into a single page.
Most likely with less repetition than the current design, but capturing all the key information.  Likely to contain a toggle to select data about (default) vs. data from.
Likely to make use of cards and links to search results rather than repeating the same info in various wells.

@kcopas
I'd like to propose that we add a section to the Participant page aimed at publishers that explains how the Participant supports publishing and data hosting withing their country/network.
Background:
The BID data hosting quick guide encourages publishers to try and discover "whether the national GBIF node offers a data hosting solution." Sadly the guide will most likely leave publishers hanging at this step: the guide directs publishers to the GBIF participants list and after opening the GBIF Participant page they won't find any information about how that Participant offers a data hosting solution.
A list of Country Participants and how they support publishing and data hosting can currently be found on the list of  Trusted IPT Hosting Centres. This information would make a valuable addition to the Participant page. If a Participant has no data hosting solution this should also be make clear. If a Participant such as France provides data hosting solutions to a number of other countries, this should be apparent not only from France's page but from each of the countries' pages that they support.

In principle, yes—but this would most likely be a node function per se, rather than a participant one. I'd like to hear what @burkeker says about the prospect of adding another chunk of additional content to what I think is already a bit of a creaky content model. Propose no regression for EOY release, but additions only after careful consideration.

I like the idea, but it doesn't sound like something to model in Drupal. It sounds more like a registry thing. sounds like the api need to be expanded to do this in a nice way. Currently all IPT stats are static. It would be nice to have them dynamic and would be nice to have them searchable by coverage. this installation covers these countries. these countries are covered by these installations belonging to these participants.
There might already be a way, but no good one I can come up with of the top of my head. What you say @kbraak , what would be the best way to do this in your opinion? You know the APIs and content better than I.

Another +1 for the idea. Of course, I'm useless w.r.t. the implementation.
Is this content for the EOY release? Either way, an excellent new
requirement ;-)
=====
Kyle Copas
Niels W. Gades Gade 55
2100 Copenhagen Ø
(+45) 28 75 14 75 | skype kylecopas
On Wed, Nov 2, 2016 at 1:32 PM, MortenHofft<EMAIL_ADDRESS>wrote:

I like the idea, but it doesn't sound like something to model in Drupal.
It sounds more like a registry thing. sounds like the api need to be
expanded to do this in a nice way. Currently all IPT stats are static. It
would be nice to have them dynamic and would be nice to have them
searchable by coverage. this installation covers these countries. these
countries are covered by these installations belonging to these
participants.
There might already be a way, but no good one I can come up with of the
top of my head. What you say @kbraak https://github.com/kbraak , what
would be the best way to do this in your opinion? You know the APIs and
content better than I.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gbif/portal16/issues/70#issuecomment-257851357, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALzkZHQ2Y4QXYu_qOcel6fJ6atVhaMBrks5q6ILSgaJpZM4KUDNP
.

https://demo.gbif.org/country/AU/summary
Please create an new issue if there are important missing in the implementation


Add experimental tests script

Part of #3607

Proposed Changes

Add a experimental-tests script which runs experimental tests after configuring the experimental features.

/cc @creydr @pierDipi

Closing as per discussion with @pierDipi we will just enable eventtype autocreate in all tests, and re-evaluate if we see more failures in the tests


Create a new release to update netty to 4.1.48.Final

We are using 5.2.2.RELEASE of lettuce, which has a dependency on netty 4.1.45. Netty fixed CVE-2020-11612 in the latest 4.1.48.Final release. Lettuce already contains the 4.1.48.Final in the master branch, is it possible to publish a new release?

This is a duplicate of #1264 and #1194. In the meantime, feel free to upgrade dependencies on your side.


Modify: Python.Python.3.6 version 3.6.4

This pull request is automatically generated by 🥟 Dumplings
Microsoft Reviewers: Open in CodeFlow

/AzurePipelines run


📃: Diagrams or Graphics

:red_circle: Title : Diagrams or Graphics:
:red_circle: Aim: Adding diagrams, flowcharts, or images to illustrate project structure or workflows can help visual learners and improve engagement.
:red_circle: Brief Explanation: Incorporating diagrams, flowcharts, or images into project documentation is an effective way to enhance understanding and engagement, especially for visual learners. These visual aids can simplify complex information by breaking it down into more digestible components. Flowcharts can illustrate workflows, showing step-by-step processes and decision points, while diagrams can depict project structures, relationships, or hierarchies. This not only makes the information more accessible but also helps maintain the audience's attention, making presentations or reports more interactive and impactful. By combining visuals with textual information, you create a richer learning experience that caters to diverse learning styles.
Screenshots 📷

N/A

:white_check_mark: To be Mentioned while taking the issue:

Full name:  alolika bhowmik
What is your participant role? (Mention the Open Source Program name. Eg. GSOC, GSSOC, SSOC, JWOC, etc.) contributor (GSSOC EXT 24)

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

add labels gssoc- ext 24 and hacktoberfest and assign this work to me.

Uppada Pavitra Manaswini Reddy
GSSoC24' Extended Contributor
Im interested to contribute please assign me. But i would like to discuss more about it once assigned.

Uppada Pavitra Manaswini Reddy
GSSoC24' Extended Contributor
Im interested to contribute please assign me. But i would like to discuss more about it once assigned.

Sorry @Pavitra-s-Workspace this issue has already been assigned, so you can raise another issue. Thank you .

@UTSAVS26  can close the issue?


Recommended HTTP extension not valid for debugging

I installed the recommended HTTP extension (REST Client by Huachao Mao) but when I try to debug VS Code shows an error message
"You don't have an extension for debugging HTTP. Should we find a HTTP extension in the Marketplace?"
This triggers an extension search for "@category:debuggers HTTP"
I have tried the "HTTP Client by Marcel J. Kloubert" extension as well.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 5cf135d8-01d5-f633-d8b6-0e91385799d4
Version Independent ID: 381ff893-11c7-c60c-8eb9-317fee8fc3aa
Content: Debug Azure API Management policies in Visual Studio Code
Content Source: articles/api-management/api-management-debug-policies.md
Service: api-management
GitHub Login: @dlepow
Microsoft Alias: danlep

It was due to the debugger throw a 401 error so it triggered VS Code to look for another debugger

@darren-kay
It looks like your issue is resolved since you closed this thread.
If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


Assets API list & get/raw & readonly the "name" object is not returned.

With the latest merging branch the 'name' object for raw & readonly assets is not returned, it was working with the previous build.
This is the output of assets/list/raw:
{
"result": [
{
"status": "ACTIVE",
"owner": "b7fa11647c02a3a65a72970d8e703d8804eb127c7e7c41d565c3514a4d3fdf13",
"version": 1,
"created":<PHONE_NUMBER>,
"modified":<PHONE_NUMBER>,
"type": "RAW",
"form": "ASSET",
"data": "This is a raw asset with name which has been updated from the demo for testing",
"address": "86Wn3qkkMS3LuFhRaUDx1QK8EF9NcwhrmXfBj99S3DTTkxhTVNS"
},
{
"status": "ACTIVE",
"owner": "b7fa11647c02a3a65a72970d8e703d8804eb127c7e7c41d565c3514a4d3fdf13",
"version": 1,
"created":<PHONE_NUMBER>,
"modified":<PHONE_NUMBER>,
"type": "RAW",
"form": "ASSET",
"data": "This is raw test data",
"address": "85xkfRM7dkRNVhgSQjmNuqEAa1ALinpGDccRoCyUhYtKGX1CFzm"
}
],
"info": {
"method": "assets/list",
"status": "active",
"address": "<IP_ADDRESS>:12002",
"latency": "1.108375 ms"
}
}
This is the output of assets/get/raw:
{
"result": {
"status": "ACTIVE",
"owner": "b7fa11647c02a3a65a72970d8e703d8804eb127c7e7c41d565c3514a4d3fdf13",
"version": 1,
"created":<PHONE_NUMBER>,
"modified":<PHONE_NUMBER>,
"type": "RAW",
"form": "ASSET",
"data": "This is a raw asset with name which has been updated from the demo for testing",
"address": "86Wn3qkkMS3LuFhRaUDx1QK8EF9NcwhrmXfBj99S3DTTkxhTVNS"
},
"info": {
"method": "assets/get",
"status": "active",
"address": "<IP_ADDRESS>:23296",
"latency": "0.159290 ms"
}
}

I've tested this just now and I get name records for created RAW or READONLY assets, is this your own private network? Have you tried to restart wiping the _API folder, do you have state I can check against? Is this testnet? Without these details, it is hard to see whether this was a user mistake such as forgetting name record wasn't submitted, or if it's a configuration issue, or if it's a newly introduced bug.

I've just tested this and get name records for both RAW and READONLY assets, have you made sure you are using a clean build and are on the newest codebase? Also, if you are testing on testnet, please privnote me the credentials you use and post that username when reporting bugs like this, otherwise it's hard to tell if it was a bug, user mistake, or configuration issue. This will make the debugging process go much smoother.

Closing this for inactivity, if you still encounter an issue for newest core please submit another issue.


Fix a typo in a documentation

Hi Marco,
here is PR for a little typo.
Marian

@MarianMacik Thanks! Unfortunately, this repository is my private jBPM repository. Would you mind submitting a PR to https://github.com/droolsjbpm/jbpm ?
Thanks!


TCVP-1442 fix mime type logic

Description
This PR includes the following proposed change(s):

Replaces the 3rd party mime type detection library with custom code

Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactoring / Documentation
[ ] Version change

if your change is a breaking change, please add breaking change label to this PR
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Does the change impact or break the Docker build?

[ ] Yes
[ ] No

If Yes: Has Docker been updated accordingly?

[ ] Yes
[ ] No

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] New and existing unit tests pass locally with my changes

Going to re-create after rebase against develop


Release 1.3.1

https://github.com/manuvarkey/kanboard-plugin-telegram/releases/download/v1.3.1/Telegram.zip
Your release file still shows 1.3.0:
public function getPluginVersion()
    {
        return '1.3.0';
    }

Corrected in new release 1.3.2


Restoration 2024 September

Bump all dependencies to the latest Sep 2024 and refactored deprecated code;
Removed 3.8. Added python 3.9-3.12.
Removed experimental aws settings.
LazyUrl is still just like workaround, thinking about getting rid of that with making simpler solution;
Bump lib version to 0.3.0

Project kick off


chore: fix conda installs

removes the defaults channel to avoid conda install timeouts
uses mamba instead of conda

So the renv template does not build. Not because of this change though - or at least I think not:
Step 7/15 : RUN bash .renv_install.sh
 ---> Running in 181ef48e0461
Installing renv
renv.lock file detected
Installing package into ‘/usr/local/lib/R/site-library’
(as ‘lib’ is unspecified)
trying URL 'https://cran.r-project.org/src/contrib/00Archive/renv/renv_0.15.5.tar.gz'
Error in download.file(p, destfile, method, mode = "wb", ...) :
  cannot open URL 'https://cran.r-project.org/src/contrib/00Archive/renv/renv_0.15.5.tar.gz'
In addition: Warning message:
In download.file(p, destfile, method, mode = "wb", ...) :
  URL 'https://cran.r-project.org/src/contrib/00Archive/renv/renv_0.15.5.tar.gz': status was 'Couldn't resolve host name'
installed renv v0.15.5
Removing intermediate container 181ef48e0461
 ---> a22dc1e7adfe
Step 8/15 : COPY renv.lock /home/rstudio/renv.lock
 ---> f6a734ffc9b9
Step 9/15 : COPY install.R /tmp/
 ---> [385](https://gitlab.dev.renku.ch/tasko.olevski/test-project-30/-/jobs/365489#L385)2af64fa03
Step 10/15 : RUN R -f /tmp/install.R
 ---> Running in dbc974a7b173
R version 4.2.0 (2022-04-22) -- "Vigorous Calisthenics"
Copyright (C) 2022 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)
R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.
  Natural language support but running in an English locale
R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.
Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.
> # The renv library will be located on the docker image, in the /home/rstudio directory,
> # yet it will use the renv.lock file located in the project's main directory to determine which dependencies to install.
> setwd('/home/rstudio')
> options(renv.consent = TRUE)
> write("options(renv.consent = TRUE)", file="/home/rstudio/.Rprofile", append = TRUE)
> renv::init(force = TRUE)
Error in loadNamespace(x) : there is no package called ‘renv’
Calls: loadNamespace -> withRestarts -> withOneRestart -> doWithOneRestart
Execution halted
The command '/bin/bash -c -o pipefail R -f /tmp/install.R' returned a non-zero code: 1
Cleaning up project directory and file based variables
00:01
ERROR: Job failed: exit code 1

I will approve because the error in the renv template is in the bash script that installs r packages with renv not in the stuff we changed.

Thanks @olevski - @RichardJActon would you be able to have a look at this error?

@rokroskar yes - I'll take a look.
The log suggests it's trying to download renv from an incorrect url ...00Archive... not ...Archive...- not sure why that would have changed but I'll see if I can reproduce it and fix the script

Thank you!!


manncodes

Satisfying Perlin noise( spherical 3-manifold) blob using Isocahedron buffer in Three.js:sparkles:
Thankful for WebGL for allowance to overkill using realtime manipulation using GUI.:zap:

[X] I have read the Code Of Conduct.
[X] I have followed all the steps of submission properly.

Thanks, @manncodes , for opening the pull request! 👏
Star ⭐  this project and tweet about your contributions and tag @clubgamma.
Also join the Discord Server
We are ready to merge your PR!!!


fix: Download SRS using one URL

resolves #1747
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

This is also done in the circuits.js file -- I'll make the change there too


App connecting via Cloud only

Since the last update (2.0.4) the app suddenly started to connect via the Cloud only, meaning that most functions cannot be used anymore. I am able to connect via the µGateway interface, so there is no connection issue.
I have restarted the gateway using the REST API and also force-closed the app, deleted the cache and restarted it several times. What else can I do to reestablish the connection?

Sorry about that 🙈!
Something seems to have gone wrong during the migration. If you check the following URL 'http://<µGW-IP>/api/site' do you see the same entries as the example below, or is something missing on your end?
{
  "data": {
    "enduser_claimed": null,
    "date": null,
    "city": "Entenhausen",
    "address": "Blumenstrasse 13",
    "create_time": "2024-10-11T21:54:12",
    "type": 1,
    "name": "Donald Duck",
    "rooms_order": [
      2406,
      2407,
      2408,
      2409,
      2410,
      2411
    ],
    "floor": null,
    "installer_finalized": true,
    "postal_code": "8810"
  },
  "status": "success"
}

Thanks for your reply. This is what I get:
{
    "data": {
        "enduser_claimed": true,
        "date": "2021-10-19",
        "city": "xxx",
        "address": "xxx",
        "create_time": "2021-10-19T12:38:26",
        "type": 1
        "name": "Imhof",
        "rooms_order": [
            31,
            32,
            33,
            34,
            35,
            36
        ],
        "floor": null,
        "installer_finalized": true,
        "postal_code": "xxx",
        "automatedVacation": false,
        "guest_secret": "xxx",
    },
    "status": "success"
}```

Okay, that looks good and doesn't seem to be the issue. I once had a case where this was the problem when something went wrong in this area.
Have you deleted the "Anlage" from the APP and then added it again? You shouldn't lose anything because everything is stored on the µGW. By doing this, the APP refers a new secret (token). It’s possible that the token is stored incorrectly in the APP.

Strange enough: I tried to tcpdump the traffic to check for a wrong token or something similar. On Android, this can be done by redirecting the traffic through a VPN. When the VPN was active, the connection worked fine.
I then noticed that suddenly the name of my home has been changed to "singleFamilyHome" or something similar. So I decided to re-add the installation, without prior deletion, because I did not want to lose the favourites etc. That solved it partially.
I can now connect to the gateway as long as I am using the same access point as the gateway itself. If I go upstairs and connect to another access point, the connection still drops sometimes.

Thank you for sharing your insights with us.
Are your access points connected to multiple cascaded switches?

No, they are both connected to the same switch and the network does not have separate segments or VLANs.

Hello everyone,
I also had this problem in the Wiser Home iOS app after the update. Since I reset the system anyway to restart with the Gateway 2, it fixed it for me. So it could well be due to the migration to the new app version. Otherwise, I only noticed the error with the color selection for the DALI dimmers in the new app, which I also wrote to you by email (@woodworm).
Have a nice weekend!

I have a suspicion, but I am not sure about it: AFAICS, the app connects and opens a persistent websocket connection. When I go upstairs, the network connection breaks and is re-established. Now probably the WS should be re-initialized, but the app does not realise that, because it did not register the change in connectivity while in the background.
It then tries to push stuff through the old WS channel and that obviously does not work.

Actually, a WebSocket connection should be able to tolerate a brief network interruption... but it's true that the server (µGW) closes the connection after a certain time, and the client (app) needs to re-establish it. Do you have a µGWv1 or v2?

OK, thanks. I just noticed that if my notebook goes to sleep mode with an open wsdump session, I get a Connection reset by peer after waking up and sending something.
I have a µGWv1 with API 5.1 (v5.1.28)

thank you very much for the info.... I will look into it

Thanks. I have another hint, that might help: if I block the connection to the cloud, the app connects to the gateway (status = green) immediately and I can switch loads normally.
As soon as I unblock access to the cloud, status becomes orange again and no connection is possible anymore.


AddPlanarSrf() should throw an exception if provided with a list

AddPlanarSrf() expects a non-list. If it is provided with a list, it fails with no errors. It will be quite helpful if it failed with an error message.

http://mcneel.myjetbrains.com/youtrack/issue/RH-30072


Support for Python 3.5?

While trying to run tlsenum with Python 3.5 I received the following error.
Traceback (most recent call last):   File "/home/michael/venv3/bin/tlsenum", line 7, in <module>     from tlsenum import cli   File "/home/michael/venv3/lib/python3.5/site-packages/tlsenum/__init__.py", line 7, in <module>     from construct import UBInt16 ImportError: cannot import name 'UBInt16'
Possible related? https://github.com/mitmproxy/mitmproxy/issues/2739

or even python 3.7 now?

Switched to maintained project: https://github.com/nabla-c0d3/sslyze


Example Notebook Clarifications/Suggestions

The example notebook is really helpful for learning about the tool! A few suggestions to make it even clearer:

When using the api.radial_search() method I had to get an error message to figure out what the options are for the units parameter. A sentence stating these three options and what they correspond to would be great.
In the "Obtain measurements over a given time range" section there is the following sentence: "The returned pd.DataFrame will match the format explored earlier, with one key difference. The station_id is now included as a column in addition to the other features.". It looks like ‘station’ is a mulit-index, not a column. If that's true this sentence can be updated.
I like the paragraph in "Check the API's supported data formats" that gives some context about modes, since modes seems to be a level of organization unique to NDBC. Some pieces of info that I would add to this paragraph (assuming I've understood correctly) are 1) the data variables that are available at a station depends on which modes the station is operating in 2) a station can be operating in multiple simultaneous modes 3) you can't search by data variable, you can only search by mode. If there is a way for people to figure out what data variables correspond to each node that may also be helpful. Maybe consider a table displaying the information from the top of section 8 in the NDBC data guide which gives a plain language description of the mode codes (ex. stdmet -> Standard Meteorological data)
Your example notebook has a really nice flow, but it feels like it gets interrupted in the middle with the api.available_realtime() and api.available_historic() methods. As far as I can tell those methods weren't important for me getting data into pandas, they were sort of just bonus methods to generate access links to the raw data in case I wanted to download the files. I would suggest moving these methods to the end of the notebook to keep the workflow that I would guess is most likely to be used together(find a station -> access station metadata -> access station data).
In the notebook as it is I don't actually see how a user would figure out which modes are available at a station. The api.available_historical() method gives the plain language description of the mode, but not the code. I realized later that the api.get_modes() method accepts a station key. Do you think showing users how to use .get_modes() would be a more streamlined way of showing users how to get the station code?

Feel free to disagree with me here, these are just some thoughts after reading through the example notebook with fresh eyes. Please don't hesitate to ask follow ups if anything is unclear!
https://github.com/openjournals/joss-reviews/issues/7406

Thank you again for your review and feedback @rwegener2; I've updated the overview notebook and some of the method docstrings based on these suggestions.
The inclusion of the available_historical and available_realtime methods in the overview notebook is intended to answer question 5 above. Without speculatively making an API call, the easiest way to determine what modes are available at a given station is to use one of these two methods for the station of interest based on the time period required. The responses do include the mode indicators, but only through URLs.
I believe that adding either a get_modes(station_id=...) or refactoring the response of these two methods will help make this more intuitive and fit-for-purpose.
One of these two will be included as a feature in the next release, along with updates to the flags and keywords across some of the data retrieval methods and possibly the inclusion of station metadata in opendap data response.
All other changes were made in #58 . If you would prefer to see these changes expediated, please feel free to re-open this issue. Thank you again and have an excellent rest of your day.

All sounds good. I see you added a sentence explaining how that the indicator is in the url, ("In the response above, the modes which are available for station "tplm2" are reported in plain text. Their indicators (stdmet, cwind) are also specified as the suffix of the URLS for the data files.") , which is super helpful. I think one of those two more in-depth options you listed will really help your users in the next release!


rethinkdb://asgard.gamecult.games:28015

how to get sample db?

Would you recommend rethink for a massive social network system? I’m currently using fire base but afraid of incoming costs

I landed on Rethink specifically because I was looking for something similar to Firebase (especially the "real-time" features) which can be self-hosted. It's certainly possible to scale with it, as it supports clustered deployments and replication.

Thx


Add 'is pilot?' prop to project list

Unify data structure for projects and pilot projects, adding a new prop

Signed-off-by: Tomás Castillo<EMAIL_ADDRESS>

I'll close this PR because #40  is in a way an upgrade of this feature


Module 2 - New Azure Portal Key Vault permissions model default prevents completion of lab steps

Module: Module 2 - Developing AI Apps with Cognitive Services
Lab/Demo: Manage Cognitive Services Security
Task: Secure key access with Azure Key Vault / Create a key vault and add a secret
Step: 2
Our team at Skillable has identified a content issue within the above-referenced module while investigating a user report. It is our understanding that the Key Vault resource created at the above-referenced step has recently become subject to a new default setting in Azure portal: the permission model of "Azure role-based access control" is now selected by default rather than the old default of "Vault access policy". In our testing, we determined that this lab module cannot be successfully completed under the "Azure role-based access control" (RBAC) permission model setting.
At under the task "Create a service principal", the az keyvault set-policy command in step 3 fails with error message "Cannot set policies to a vault with '--enable-rbac-authorization' specified" when the RBAC permission model is set.
Additionally, earlier in the lab under the "Create a key vault and add a secret" task, creation of a new secret at step 5 fails with the RBAC permission model set, unless additional RBAC permissions are assigned to the lab Azure user.
In our testing, selecting the "Vault access policy" Permission model setting on the Access configuration tab of the Create a key vault page when performing the step referenced at the top of this issue, rather than leaving that setting at its default, worked around all issues and allowed all subsequent lab steps to be completed.


docs: update ares-device syntax

This fixes an error:
ares-device-info ERR! [Tips]: This command is deprecated. Please use "ares-device" instead of "ares-device-info"

Am wondering if it's worth including a note to show the old command. The version of the CLI on my machine, for example, does not have ares-device.

Do you know when ares-device-info was removed from the webos SDK?

I have no idea. Installed mine with npm install -g @webos-tools/cli. Instructions from https://webostv.developer.lge.com/develop/tools/cli-installation.
I might need the older version though? I am trying to get my LGTV to work with appium commands, but I get this error:
WebDriverException: Message: An unknown server-side error occurred while processing the command. Original error: Could not find a driver for automationName 'webos' and platformName 'lgtv'. Have you installed a driver that supports those capabilities? Run 'appium driver list --installed' to see. (Lower-level error: Ensure the "LG_WEBOS_TV_SDK_HOME" environment variable
is set; see https://webostv.developer.lge.com/sdk/command-line-interface/installation/
for more information)

Although I have LG_WEBOS_TV_SDK_HOME set to /usr/local/lib/node_modules/@webos-tools

Seems like ares-device-info was removed from 3.0.0 on:   https://github.com/webos-tools/cli/blob/17f173a6a6263ed4110ecdb636fd1f33bfadc293/README.md?plain=1#L165

Could there be a possibility to update this driver to be compatible with the newest version of webos cli?

Yes, we should look into that. cc @KazuCocoa

I see... This package is based on https://webostv.developer.lge.com/develop/tools/cli-installation 's webOS TV CLI Version: 1.12.4-j27 as the comment. So some code needs to be updated to the latest one.
https://webostv.developer.lge.com/develop/tools/cli-release-notes is the changelog to v3.
ares-extended-dev also removed.

Caution: webOS TV CLI Deprecation
We decided to no longer support webOS TV CLI from March, 2024. We recommend that you use the webOS CLI instead.

https://webostv.developer.lge.com/develop/tools/webos-tv-cli-release-notes

Created a ticket -> https://github.com/headspinio/appium-lg-webos-driver/issues/58
So far, this driver requires old CLI
https://webostv.developer.lge.com/develop/tools/webos-tv-cli-installation
webOS_TV_CLI_linux_1.12.4-j27.tgz

I have also addressed the cli version in https://github.com/headspinio/appium-lg-webos-driver/blob/main/README.md
Thank you for this notice. I'll close this issue for now. https://github.com/headspinio/appium-lg-webos-driver/issues/58 should cover this update as well.


Question: Using DataTables features that are not in the library

I will use this library in a project but I am not sure about a few things:

Does this library/repository cover all the features in the current version of DataTables?
If no, is it possible to add and use features that are not available in the library? In other words, is it flexible or can it be injected?

For example;
As far as I can see, I did not see the FixedColumns extension feature in the library. If not, can I use this FixedColumns extension in DataTables with this library?

Yes, "most" of the latest features are supported including the premium Editor library. Aside from the server-side Search Builder, can't remember any feature that did not work on my use case. Also, I think there is an issue here it GitHub that has a working solution for server-side search builder.
FixedColumns is a client-side feature but is also supported via HTML builder.
Also, the package is open for contributions if ever there are features that are not yet supported.
Thanks!

Thank you so much! 💛


Clean up code related to currentIntervention, social distancing, and stay-at-home.

This PR should have no functionality changes (with the exception of a slight performance improvement from only downloading 2 intervention API endpoints) and is mostly just deleting code that is no longer necessary.
In particular:

We no longer use the current state intervention anywhere, so I deleted STATE_TO_INTERVENTION and the interventions.json file (actually I moved it to covid-data-public here).
I removed the filter-by-intervention functionality from CompareModels (the /compare page).
We no longer use social-distancing or stay-at-home projections, so I deleted code / constants that deal with them.
Projections always include an inference projection, so we no longer need isInferred and can delete any code paths that deal with not having inference projections.
I simplified Projection.getDataset() to just return the data instead of a {data, label} tuple, since we never use the label.
We didn't use the StateSelector, CountySelector, or Status components so I deleted them.
ModelChart.style.js had a bunch of unused chart styles, so I deleted them.

It may be easier to review the commits individually.

 Remove all code dealing with: isInferred (everything is inferred now). currentIntervention (and the checked-in interventions.json file too). The  “social distancing” projection (we don’t show it on any graphs anymore).

i am soooo excited


Health Probe?

I have heard that you can access the health probe via https://:8081/healthprobe. I also see a reference to this in the following past commit:
https://github.com/MicrosoftDocs/azure-docs/commit/dd0848914c6474c787d771da88ae7b141dfa6384
However, that information is currently missing from this document, so it's not clear what is involved in "Go to the health probe." Can that be added back in to clarify? Or, if that's not the correct step any more, please specify how to get to the health probe.

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

ID: 089a64fa-6ccb-6c2c-9d32-9a1a1fd04d1d
Version Independent ID: 657867e8-d7ae-b091-81b7-5b65f61ccd45
Content: Troubleshoot an Azure site-to-site VPN connection that cannot connect
Content Source: articles/vpn-gateway/vpn-gateway-troubleshoot-site-to-site-cannot-connect.md
Service: vpn-gateway
GitHub Login: @chadmath
Microsoft Alias: genli

@dcbrown16 Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@dcbrown16， thank you for the feedback, I will add the link of health probe into the article.

The article is updated:
https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-troubleshoot-site-to-site-cannot-connect
#Please-close

Great, thanks @genlin !


[BUG]: Installation of the COE in GCC High - Nurture Component

Describe the bug
A clear and concise description of what the bug is.
Component (please tell us which flow or app you are experiencing issues with):

Solution - Nurture
Version - 1.51
App or Flow - Import

To Reproduce
I am working in a GCC High environment and it appears the Nurture component requires Excel Online (Business).  Can you provide a previous version that doesn't require Excel Online (Business)?  The documentation I've found states the connector is not available.  If I'm incorrect please tell me how to implement the component.

My ultimate goal is to use the Maker Assessment app.  Can I do so in GCC High without access to the Excel Online (Business) connector?

We have moved to a new dedicated repository for the CoE Starter Kit, and issues here will no longer receive attention. Please raise your issues here from now on:
https://github.com/microsoft/coe-starter-kit/issues


Release the image with apache 2.4.62

Critical issue have been fixed but has been months without a new release of this container.
The latest tag "owasp/modsecurity-crs:apache" still uses 2.4.59

Glad that you asked! Release 20240730 in the bake!


Add options for distributing horizontally/vertically

Feature suggestion in the image below. It would enable you to bind keyboard shortcuts to distribute horizontally/vertically, instead of having to use the radio buttons all the time.

PS. Thanks for a great plugin! DS.

Thanks for those kind words!
The latest version of the plugin works exactly as you suggest. Time to upgrade? 🤠

Great minds, etc. Thanks!


Can't get a simple synchronous server to work

Version of Beast
306
Steps necessary to reproduce the problem
Just try to run a server with the file https://www.boost.org/doc/libs/develop/libs/beast/example/http/server/sync/http_server_sync.cpp
Hello,
I'm new with ASIO and beast. I need to make a simple HTTP server for sending images from a client.
Thing is ,I can't even make the example work (http_server_sync.cpp here).
I just run the server on <IP_ADDRESS> port 8080 and do curl localhost:8080. What I get is a server that stops without any error message and without response... Seems that te problem come from the "send" call in handle_request, but I cannot figure out why...
It's been a while I didn't do C++ so if somebody can help me with that I would be grateful...

What was the exact curl command line you entered?
Was there any output to stdout or stderror?

Hi,
Thanks for your answer.

Just a curl http://localhost:8080
I get warning when I build (seems normal), but don't have any out or error, even when running the server

Are you pointing the server to a directory with HTML files? And an index.html ?

Yes, I do with the commande line ./SyncServer.exe <IP_ADDRESS> 8080 . in the directory which contains both the SyncServer.exe and the index.html file

Last thing before I try it locally.
If you enable debug output from curl, what do you get?

With verbosity -v:
C:\Users\pserre>curl -v localhost:8080                                                                                * Rebuilt URL to: localhost:8080/                                                                                *   Trying ::1...                                                                                * TCP_NODELAY set                                                                                *   Trying <IP_ADDRESS>...                                                                                * TCP_NODELAY set                                                                                * Connected to localhost (<IP_ADDRESS>) port 8080 (#0)                                                                     > GET / HTTP/1.1                                                                                > Host: localhost:8080                                                                                > User-Agent: curl/7.55.1                                                                                > Accept: */*                                                                                >                                                                                * Recv failure: Connection was reset                                                                                * Closing connection 0                                                                                curl: (56) Recv failure: Connection was reset
With --trace :
C:\Users\pserre>curl --trace - localhost:8080                                                                           == Info: Rebuilt URL to: localhost:8080/                                                                                == Info:   Trying ::1...                                                                                == Info: TCP_NODELAY set                                                                                == Info:   Trying <IP_ADDRESS>...                                                                                == Info: TCP_NODELAY set                                                                                == Info: Connected to localhost (<IP_ADDRESS>) port 8080 (#0)                                                              => Send header, 78 bytes (0x4e)                                                                                0000: 47 45 54 20 2f 20 48 54 54 50 2f 31 2e 31 0d 0a GET / HTTP/1.1..                                                  0010: 48 6f 73 74 3a 20 6c 6f 63 61 6c 68 6f 73 74 3a Host: localhost:                                                  0020: 38 30 38 30 0d 0a 55 73 65 72 2d 41 67 65 6e 74 8080..User-Agent                                                  0030: 3a 20 63 75 72 6c 2f 37 2e 35 35 2e 31 0d 0a 41 : curl/7.55.1..A                                                  0040: 63 63 65 70 74 3a 20 2a 2f 2a 0d 0a 0d 0a       ccept: */*....                                                    == Info: Recv failure: Connection was reset                                                                             == Info: Closing connection 0

The http-server-sync example works for me, with this command line :
http-server-sync.exe <IP_ADDRESS> 8080 C:\Users\vinnie\src\www

This is version 310

I have Visual Studio 2019 with  C++17, could be a problem ?

I used Visual Studio 2019. Should not be a problem.

Since it doesn't work on my side, I'm going to work with websocket which is enough in my case.
I have now the same issue as #2014 (don't know if i'm gonna have an example working one day..)., but with VS2019... Hasn't this bug fixed previously ?

What happens if you make it /std:latest ?

I'm going to work with websocket which is enough in my case.

You need to figure out why it isn't working, otherwise you will be unable to explain or diagnose your program(s) if it happens again. Unsolved mysteries have no place in computer science.


not possible to pass data as buffer

it seems that when passing a Buffer in const options = { data: Buffer.from('foo') }, centra would handle it as json since typeof Buffer resolves to object.
I see two solutions here:

default sendAs to 'raw', which would become a breaking change (since currently 'json' is assumed
add options.buffer and leave options.data as is. When options.buffer is used, call req.body(options.buffer, 'raw')

Thoughts? Happy to provide PR after discussion about suggested options

Thanks for submitting the issue, @benkroeger!
Patch 3.2.1 has resolved the issue as now buffers are sent in their intended form: as binary data!
This patch is now available on NPM. :)


Retire "Ecosystem" page in favour of datasette.io/plugins and /tools

https://docs.datasette.io/en/stable/ecosystem.html is no longer needed.

I'll leave the page there but change it into more of a blurb about the existence of the plugins and tools directories.

I'll leave the page there but change it into more of a blurb about the existence of the plugins and tools directories.

It can talk about Dogsheep too.

It can talk about Dogsheep too.

https://docs.datasette.io/en/latest/ecosystem.html

https://docs.datasette.io/en/latest/ecosystem.html


go/doc: enable grouping of functions with common names and suffix N

Suggested by @griesemer in another proposal: https://github.com/golang/go/issues/18616#issuecomment-275761203.
An example of the proposed before and after output, for a series of functions called TrailingZeros with integer sizes "N" as a suffix:
Before:
// TrailingZeros16 returns the number of trailing zero bits in x.
// The result is 16 if x == 0.
func TrailingZeros16(x uint16) uint

// TrailingZeros32 returns the number of trailing zero bits in x.
// The result is 32 if x == 0.
func TrailingZeros32(x uint32) uint

// TrailingZeros64 returns the number of trailing zero bits in x.
// The result is 64 if x == 0.
func TrailingZeros64(x uint64) uint

After:
// TrailingZerosN returns the number of trailing zero bits in a uintN value x for N = 16, 32, 64.
// The result is N if x == 0.
func TrailingZeros16(x uint16) uint
func TrailingZeros32(x uint32) uint
func TrailingZeros64(x uint64) uint

Seems like a big usability improvement, and would be useful in at least sync/atomic as it exists now in the stdlib: https://golang.org/pkg/sync/atomic/.  Would also be useful for some of the proposed APIs for a math/bits as discussed here: https://github.com/golang/go/issues/18616

My questions/concerns are:

would have to modify golint and tools like that in addition to godoc/go doc/gddo
how to model it in the go/doc package?
Seems like it only benefits a small number of packages
Where to draw the line? Does it work for types, vars, consts? Can the suffix be the empty string (to group patterns like X, XString)? What about shared prefixes? What if the declarations are in different files? What if they're methods attached to different types?

(as for modelling in go/doc the simplest way would just be to copy the doc string into each Func, but it would be hard to discover the grouping and the decl containing the actual comment without an additional field or method for retrieving the decl with the comment)
I'm not opposed to this change, and I could see it being a benefit, but I'm not convinced it justifies its complexity yet.

@jimmyfrasche Some (possible) answers:

The go/doc model could expose an additional field per function/method that ties those together that are part of a "group". The additional field would be the *Group.
Whether it is beneficial enough is to been seen. May still be worthwhile.
Types, vars and consts can be grouped already (n the langugae). Go/doc already has some heuristics about which comment to choose (group comment vs individual comment).


Update CSharpProxyTemplate.tt

I discovered that calls to HttpClient.GetAsync in the WebApiProxy.generated.cs file were returning a 404 after I added an additional directory to my Web API path, eg, http://localhost/AdditionalDirectory/api/Values.  I was able to use the API (with the additional directory) from a web browser. When I examined the request Uri, it was http://localhost/api/Values, rather than http://localhost/AdditionalDirectory/api/Values.  I verified MyWebApiProxyBaseAddress was set correctly.  In my effort to figure out what was going on, I cam across this SO question/answer, http://stackoverflow.com/a/23438417/640326.  I manually added a slash to the end of MyWebApiProxyBaseAddress, and everything worked as expected.  It looks like adding a slash just before the last quote in CSharpProxyTemplate.tt, line 38 should work?

Hi @gregmulvihill, thanks for your contribution!
What will happen if there are also a trailing slashes in the configuration? Should it matter, because we don't want something resolving to http://myapi/mydir//
It's maybe wise to unify these slashes somehow.

@faniereynders, good point.  OK, I retract my previous suggestion and offer this instead.
In WebApiProxy\WebApiProxy.Server\MetadataProvider.cs, change line 83 to this:
Host = System.Web.VirtualPathUtility.AppendTrailingSlash(host);
I will create a pull request.


Serverless VLLM Runpod deploying facebook/opt-125m model on its own.

I am trying to deploy meta-llama/Llama-3.1-70B-Instruct using serverless VLLM in runpod, I have correctly added "HuggingFace Model" and "Hugging Face Token" with vllm version "0.6.3(latest)" .
But it always shows and deploys facebook/opt-125 instead.

Thanks @kunalchamoli  for calling it out. this is fixed.


Remove use of assert.equal from the code

The code base currently uses a mixture of assert.strictEqual and assert.equal for mocha testing. However, assert.equal is deprecated meaning overtime it may break or cease to work. We also see ugly strike throughs in many of our tests. See https://nodejs.org/api/assert.html#assert_assert_equal_actual_expected_message for more info on the deprecation.
Proposal
My suggestion is that we make an effort to remove all assert.equal use cases from our code base since it's been deprecated since version 9.9 of node. We currently have 3,697 uses of assert.equal.

First PR went in for this, still additional deprecations to resolve. See comment on #120125 for more details

@lramos15 What about notEqual, deepEqual, notDeepEqual etc?

I finished all the extensions. @roblourens if you could finish your few files we could close this out this milestone :)


self contained example for ask and tell

+self contained
+enough budget for writing something significant
Types of changes

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

Motivation and Context / Related issue

How Has This Been Tested (if it applies)

Checklist

[x] The documentation is up-to-date with the changes I made.
[x] I have read the CONTRIBUTING document and completed the CLA (see CONTRIBUTING).
[x] All tests passed, and additional code has been covered with new tests.

@brockho


Chatterbot responding very slowly if I have too many files in my corpus

Hey!
Awesome project. Sooo chatterbot works perfectly if my corpus contains files with short length conversations (similar to what you have in the examples).
I then tested it with files containing facebook conversations I have had throughout the years and it works....but it runs super slowly. It will basically give me a response after a minute of "thinking".. Is it something I'm doing? or can it not handle that magnitude of files?
I'm training it with the list trainer as such:
files = os.listdir("corpus/")
for f in files:
    data = open('corpus/' + f,'r').readlines()
    nouf.train(
        data
    )

Thank you!

+1
@gunthercox I observing the same issue. The response time is increasing as the statement sets grow and also the length of the statement text increases.
The bot is really good. But do you have any suggestion or best practices for performance gains, mainly in improving in response time?

I've introduced additional filtering in https://github.com/gunthercox/ChatterBot/tree/1.0.0a1, https://github.com/gunthercox/ChatterBot/tree/1.0.0a2, and https://github.com/gunthercox/ChatterBot/tree/1.0.0a3 that decreases the size of the result set before a response if processed.
These changes improve the response time significantly for large data sets. I'm going to continue work to improve the overall response time, but I think this ticket should be safe to close off. Please let me know if you have any questions.


K8s content restructure

Content must go through a pre-merge checklist.
Pre-Merge Content Checklist
This documentation has been checked to ensure that:

[x] The title, template, and date are all set
[x] Does this PR have a new menu item (anywhere in templates/*.hbs files) that points to a document .md that is set to publish in the future? If so please only publish the .md and .hbs changes in real-time (otherwise there will be a menu item pointing to a .md file that does not exist)
[x] File does not use CRLF, but uses plain LF (hint: use cat -ve <filename> | grep '^M' | wc -l and expect 0 as a result)
[x] Has passed bart check

✅ content/spin/v2/spinkube.md
✅ content/spin/v2/spin-in-pods-legacy.md
Tested locally:

[x] Has been manually tested by running in Spin/Bartholomew (hint: use PREVIEW_MODE=1 and run npm run styles to update styling)

[x] Headings are using Title Case
[x] Code blocks have the programming language set to properly highlight syntax and the proper copy directive
[x] Have tested with npm run test and resolved all errors

[x] Relates to an existing (potentially outdated) blog article? If so please add URL in blog to point to this content.

Closes https://github.com/fermyon/developer/issues/1169

The CI failure is some weird and alarming NPM error (not the exepcted "URL that is not yet on GitHub is not yet on GitHub" link checker.  Not sure what's going on there but probably bears investigating since it means the link checker is not running as far as I can tell?

Looking at the CI error it may think the lockfiles are out of sync with the package.json files.  I'm not sure how to fix this but it might be worth trying reverting the lockfiles.  Not sure how it's working locally for you although clearly it is...!  Anyway the rest looks great!

Thanks @itowlson
I reverted the package-lock.json files as the final step before merging.
Thanks for the review.


Atom fails to render this emoji --> ▶ (U+25B6)

It displays as a blank box, and also counts as two characters. Other emojis seem to render fine and only count as one character.
on osx 10.11.3
atom version 1.3.3 (and version 1.4)
the two character problem is perhaps related to https://github.com/atom/atom/issues/8974
Can anyone else reproduce this?

I cannot reproduce this using Atom v1.3.3 on Mac OS X 10.11.2. Since OS X 10.11.3 at this point is still in Beta, I'm reluctant for us to spend time investigating this yet. I'm going to leave this open for now though.

I am not able to reproduce it on Atom v1.3.3 on XUbuntu 14.04 LTS.
Here is a screen shot on my system:

I am unable to reproduce using Arch Linux x86_64 and Atom 1.5.0-beta0.

Yep, looks like it is a problem specifically with the OS X beta. @tennysonholloway you may want to report this to Apple. Going to close this for now until it shows up on a released version.

Yep, looks like it is a problem specifically with the OS X beta. @tennysonholloway you may want to report this to Apple. Going to close this for now until it shows up on a released version.

I'm experiencing the same issue w/ stable version of OSX 10.11.4 and Atom 1.6.0
eg. ❤ renders as the image attached

@lee-dohm: Reproduced this on 10.10 and atom 1.6.0
Re-opening... 😬

Hmmmm ... exploring further, it seems some emoji render properly and some don't. Copying and pasting the play button or heart emoji from this Issue renders the box. If I directly enter the Unicode character codes using the Unicode Hex Input on OS X, I get the black-and-white versions:

But if I use the Emoji Input in OS X, I get the box for both of them. Also, I can't enter the emoji for the grinning face (:grinning:) using the Unicode Hex Input mode, but when I use the Emoji Input it works and renders fine.
Unicode for the play button is U+25B6 as mentioned above and for the heart is U+2764. See the Full Emoji Data chart.


Negative patterns in .gitignore make all files ignored

It works with any negative patterns, the one who matches nothing !* and the one who matches anything !inexisting.

Can you give an example of a .gitignore you're trying to use?

Just ran into this. Probably a better way to write this but here's what I had.
!*/db
db

Ignore /db, but don't ignore say, /lib/db.

@matthewmueller you can simply write /db which ignore the db entry in the directory where the .gitignore is.
@feross I can show you a trivial example but any valid gitignore should be correctly interpreted.
dist/*
!dist/.keepme

<EMAIL_ADDRESS>removed support for .gitignore until we can make it work more reliably.


Licence

Hi,
Is this project licenced under a MIT licence?
Is there any documentation for this project?
Thanks

I just added the documentation and the licence now.


Goa project IDE

Hey team, can you suggest steps to open and build the application using an IDE like Android Studio or XCode?

@ankitk20 Did Chimple's comment at https://community.xprize.org/learning/discussion/260/chimple-goa-project-setup#latest resolve this issue?


css settings

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #XXXXX

Hello,
Is this related to an open issue? If not, can you explain the reasoning for this change?


docs(samples): adds samples from documentation with correct region tags

Adds samples from DevSite documentation. Region tags included in added/updates files are correct.
The following additions are needed before merging:

Samples updated to sample rubric standards
File names changed to match region tags
Tests added

Requested changes are limited to samples in the scope of this PR.
Ideally, another PR will update content and metadata of the other existing samples.

[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #369 ☕

Ref PR #392

Samples are added in https://github.com/googleapis/java-datacatalog/pull/392. Hence, closing this duplicate PR.


ARTEMIS-1781 Connector parameters not backward compatible

https://issues.apache.org/jira/browse/ARTEMIS-1781
https://issues.jboss.org/browse/ENTMQBR-1034
Fixing backward compatibility with HornetQ:

Translate transport parameters to dash notation instead of camel-case when talking to legacy clients.
Do not add passwordCodec parameter unless maskPassword is true.

It would be nice to have a compatibility test added.

@clebertsuconic could you point me to where you keep similar tests? So far I have a deal with EAP QE that they would create it for EAP.

@TomasHofman  Kudos.. really nice...
i have done some tweaking though.. I'm removing TransportConstantsV2 and adding those properties directly on the Utility.. the TransportConstantsV2 name would be confusing and people would think that's the newest version to be used...
I have also split your commit into 2.. one for the tests and one for the fix... but I kept you the authorship.
I'm merging these myself as I don't see a point on going back and forth asking you to make these chagnes as I have them already...
I will apologize in advance as I'm pushing I change I made into your commit (removing the V2 class) but the github would be simpler if I amended my change into yours.. consider it like I have asked you to make the change and it's been done..
I'm merging it now.. but please check if you see anything wrong after I merged it.

the only reason I splitted into two commits is because it would be simpler to verify the fix.
Again.. thanks a lot for this.


ov7670

hi
how work with ov7670 without fifo

I have yet finished it

thanks for answering
goodluck

I ported this project to the idf version 4.1 dev. Replace the camera component for the esp_idf/components/esp32-camera  that support the ov7670 and hhtp_server for esp_idf/components/esp_https_server
I added a conversion function for pgm of 8 bits to RGB bitmap og 24 bits.
Now the WIFI_SSID and WIFI_PASSWORD are configured in the example connection menu.
https://github.com/jjsch-dev/ESP32_CAMERA_QR/

@jjsch-dev Thank you ,but I tried your demo,but lack something

How can I help you?

@jjsch-dev I fixed the demo last night.But you can try to suppport  more cameras,such as ov5640

I don't have this sensor, if you send me one I will try to add it to the esp camera sensor driver.


File read buffer not copied when reading a slice larger than the bytes in the buffer

When you read bytes from a file that is less than the buffer size and you follow by reading bytes that exceed the remaining bytes in the buffer, then the bytes in the old buffer are not prepended to the new buffer
https://carc.in/#/r/qa8

The docs for IO#read(Slice(UInt8)) say:

Reads at most slice.size bytes from this IO into slice. Returns the number of bytes read.

That means that less bytes could be read, even if there is more data available. You should always check read's return value.
In this case, IO::Buffered#read only reads once from the underlying IO. I guess we could change it to read as much as possible to fill the given slice (maybe more intuitive).

If you are waiting that many bytes to be read from the IO, then just use IO#read_fully.
Let's say you're reading from a socket. If IO::Buffered#read continued reading until it filled as much data as possible, it might happen that the client doesn't have more data to send and is already waiting for a reply. In this case a deadlock would occur. We could make the second underlying read in IO::Buffered non blocking, but in any case you cannot trust that the read call will fill the entire buffer (maybe the next packed didn't arrive yet) and you always must check the returned number of bytes.

The reason I expected it to be filled was because the slice size is specified.
I see your point when reading from a socket and you don't know the size.
Would it be easier to have a method that fully fills the slice if you specifically ask for it? In my use case i do know the size of the bytes that should be read. It can raise if it can't be filled.

That's what I said. Use IO#read_fully in that case :wink:

Haha I'm sorry. It's Friday and I'm in a pub having a beer trying to look smart ;-)

:beers:


Feature: Expose Rekor entry ID through API

If we can expose the Rekor entry for a scorecard-action run in api.securityscorecards.dev, an end-user would be able to tie back a scorecard run to the scorecard-action run that produced it, instead of trusting that it came from the cron. We could also add the scorecard-action job/run information for transparency.

@raghavkaul A good idea. We also serve the results from CRON. Do you have any suggestions for those results?


fix nobs_features reshape error

Hi @Dominique-Yiu, thanks for submitting this PR. Why is my current implementaiton "x[:,:To,...]" incorrect?

Hi, @cheng-chi. I apologize for the misunderstanding in my previous submission. The conflict arises between x[:,:To,...] in line 257 and reshape(B, T, -1) in line 260. In this context, I believe that reshape(B, T, -1) should be replaced with reshape(B, To, -1) instead of removing [:,:To,...].

Hi @Dominique-Yiu Thanks, this is indeed a bug. I will fix it in a seperate PR.


Remove version: DominikReichl.KeePass version <IP_ADDRESS>

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://sourceforge.net/projects/keepass/files/KeePass 2.x/2.47/KeePass-2.47.msi/download
Status Code: 200
(Automated message - build 897)

Close with reason: Package still available.;


Facing issues in building windows flutter app.

@d-uzlov I am getting below error when trying to build flutter based windows app.
Can you please have a look once if you have come across it earlier or any suggestions to try out?
fatal error C1083: Cannot open compiler generated file: '': Invalid argument
error.txt

I can't be 100% sure, but I think I encountered this same issue when I was building the app with too long username.
The path to the file in your log is 188 symbols long, but I believe that Visual Studio compiler composes file path and a relative include path in the file, and the resulting path exceeds ~260 path length limit. Or something like this.
I got this solved by just renaming the user in the docker container I was using.
It could probably be solved by just manually pointing --output_user_root bazel startup arg to a shorter path.

In case this helps, enabling long paths in Win10:
https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=cmd

Thanks Danil and Relja. I was able to resolve the issue.
Facing a new issue now when trying to build qtibackend.
The SNPE for windows library produces dynamic libraries. But when we enable dynamic libraries flag for libqtibackend, it throws some linking error for tflite.
On trying out the same change in mobile_back_tflite, i.e., to dynamically link tflite, get the same error as above.
Any way that you may be aware of to dynamically link tflite?

I never tried to build libraries with dynamic linking using bazel on Windows.

On trying out the same change in mobile_back_tflite, i.e., to dynamically link tflite, get the same error as above.

@mohitmundhragithub, could you provide more into about changes you've made? I don't see any places where adding linkshared = 1 in the tflite build file would make sense. Are you talking about some other flag, or are there some bigger changes in build configs?

https://github.com/mlcommons/mobile_app_open/blob/master/mobile_back_tflite/cpp/backend_tflite/BUILD#L26
Add a field, "linkstatic=0" in the cc_library bazel construct.
https://docs.bazel.build/versions/main/be/c-cpp.html#cc_library
BTW, I tried by using tflite v2.7 as well... but it didn't help :(

When I tried adding linkstatic=0 to the cc_library { name = "tflite_c" } rule I didn't get any errors.
Judging by Bazel documentation this is to be expected:

The linkstatic attribute has a different meaning if used on a cc_library() rule. For a C++ library, linkstatic=True indicates that only static linking is allowed, so no .so will be produced. linkstatic=False does not prevent static libraries from being created. The attribute is meant to control the creation of dynamic libraries.

I used the following commands to test:

bazel build --config windows //mobile_back_tflite/cpp/backend_tflite:libtflitebackend.dll
bazel build --config windows //mobile_back_tflite/cpp/backend_tflite:tflite_c

However, I did get an error file 'mobile_back_tflite/cpp/backend_tflite/quantization_util.dll' is generated by these conflicting actions when I added linkstatic=0 to cc_binary( name = "libtflitebackend.dll".
Did you mean cc_binary rule, or are there some other changes?

I was able to resolve the above issue. Earlier, I was missing one one important point, that Qualcomm needs to build the app for windows_arm64 and not windows_x64. The current windows app is built only for x64. When i switched to windows_arm64, then compilation of few of the helper libraries itself fails. I will close this issue, and create a new one for adding support for windows_arm64.


Make PrunedLiveness ownership-friendly

This establishes a sound foundation for building optimizer support for OSSA.
This includes functional changes because the APIs are now rigorous about recognizing and propagating information about reborrows and pointer escapes. These are the two areas that aren't handled correctly in our current suite of OSSA utilities.
This set of commits are included in a single PR primarily for testing purposes.
This includes new infrastructure for unit testing liveness analysis.
This also includes the fix for rdar://99874173: unreachable assert "No user in LiveWithin block"
I couldn't resolve all the liveness issues in one PR. Changing fundamental utilities means carefully auditing all the clients to make sure they handle the new behavior. So a verifier test is disabled and utilities will still bail-out in many situations where they shouldn't need to.
The next step is to add an OSSALiveness layer that handles "extended" live ranges. OSSA live ranges can be extended across copies or reborrows.
Then we'll gradually start enabling features in OwnershipOptUtils that were disabled because of bugs. And finally, we can replace most of the ad-hoc logic with a more principled approach.
The headline commit is:
Redesign PrunedLiveness APIs, introducing live ranges
First restore the basic PrunedLiveness abstraction to its original
intention. Move code outside of the basic abstraction that polutes the
abstraction and is fundamentally wrong from the perspective of the
liveness abstraction.
Most clients need to reason about live ranges, including the def
points, not just liveness based on use points. Add a PrunedLiveRange
layer of types that understand where the live range is
defined. Knowing where the live range is defined (the kill set) helps
reliably check that arbitrary points are within the boundary. This
way, the client doesn't need to be manage this on its own. We can also
support holes in the live range for non-SSA liveness. This makes it
safe and correct for the way liveness is now being used. This layer
safety handles:

multiple defs
instructions that are both uses and defs
dead values
unreachable code
self-loops

So it's no longer the client's responsibility to check these things!
Add SSAPrunedLiveness and MultiDefPrunedLiveness to safely handle each
situation.

@swift-ci test

@swift-ci benchmark

@swift-ci smoke test

I'd like to merge this soon because it looks like we're getting new bug reports that it will resolve.

@swift-ci test

@swift-ci benchmark

LGTM

@swift-ci test

@swift-ci benchmark

@swift-ci smoke test and merge


Adds schema basic implementation

Description
This PR adds a proof of concept for the Apollo schema that will be used in the API. Now, to make requests to the API, you'll need to provide a Github token generated by Github App authentication, as it was implemented by @jadsonluan. This token is passed via authentication header, as illustrated bellow.

This schema contains a user type, which contains id, login and totalRepos fields. We can add more data, it's just a demo for the API, as the sprint requested.
The only query is me, which returns data from the logged in user. Here, you can see an example of usage:

Fixes #10 and #9
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

I'll resolve the conflicts and then it'll be ready for review!


Snapshot test with coverage flag

When tested using Jest snapshots i observe different behaviour  when I run the tests with --coverage flag or without.
With coverage flag i get Component in first child

Without coverage flag i get true React component ModalHeader

jest configuration:
jest version = 16.0.0
test framework = jasmine2
config = {
"collectCoverageFrom": [
"app/*/.{js,jsx}",
"!app/app.js",
"!app/routes.js"
],
"moduleDirectories": [
"node_modules",
"/Users/romario/Projects/work/imtm/app"
],
"moduleNameMapper": [
[
"..css$",
"/Users/romario/Projects/work/imtm/mocks/cssModule.js"
],
[
"..jpg|..png$",
"/Users/romario/Projects/work/imtm/mocks/image.js"
]
],
"setupTestFrameworkScriptFile": "/Users/romario/Projects/work/imtm/internals/testing/test-bundler.js",
"testRegex": "tests/..test.js$",
"rootDir": "/Users/romario/Projects/work/imtm",
"name": "-Users-romario-Projects-work-imtm",
"setupFiles": [
"/Users/romario/Projects/work/imtm/node_modules/babel-polyfill/lib/index.js"
],
"testRunner": "/Users/romario/Projects/work/imtm/node_modules/jest-jasmine2/build/index.js",
"scriptPreprocessor": "/Users/romario/Projects/work/imtm/node_modules/babel-jest/build/index.js",
"usesBabelJest": true,
"automock": false,
"bail": false,
"browser": false,
"cacheDirectory": "/var/folders/zb/cdw729m57bg8thqz6f863w3c0000gn/T/jest",
"clearMocks": false,
"coveragePathIgnorePatterns": [
"/node_modules/"
],
"coverageReporters": [
"json",
"text",
"lcov",
"clover"
],
"globals": {},
"haste": {
"providesModuleNodeModules": []
},
"mocksPattern": "mocks",
"moduleFileExtensions": [
"js",
"json",
"jsx",
"node"
],
"modulePathIgnorePatterns": [],
"noStackTrace": false,
"notify": false,
"preset": null,
"preprocessorIgnorePatterns": [
"/node_modules/"
],
"resetModules": false,
"testEnvironment": "jest-environment-jsdom",
"testPathDirs": [
"/Users/romario/Projects/work/imtm"
],
"testPathIgnorePatterns": [
"/node_modules/"
],
"testURL": "about:blank",
"timers": "real",
"useStderr": false,
"verbose": null,
"watch": false,
"cache": true,
"watchman": true,
"testcheckOptions": {
"times": 100,
"maxSize": 200
}
}

Hi @KyKyPy3! Thanks for raising the issue, I will have a look as soon as I can.
Can you tell me which version of enzyme-to-json you are using? I wouldn't be surprised if this happens in v1.1.2 but I think I fixed most of these in the latest v1.1.3 version.

I try to use 1.1.3 and version build from master branch.

@KyKyPy3 any news? Are you trying the latest version?

Yes, the situation has not changed

Looks like the issue is related to this one
https://github.com/airbnb/enzyme/issues/611

I'm running into the same problem, see here: https://github.com/airbnb/enzyme/issues/640#issue-184439634

Is this in any way related to https://github.com/thejameskyle/pretty-format/commit/9214857d3db17872ed50e37dd3e49b5736970248 ?

@ryanewing I updated to<EMAIL_ADDRESS>and it didn't fix the issue for me.

Is it possible for someone to create a small repo which replicates this issue?

I've tried, but I'm not able to replicate the issue currently. If I run into it again I'll create an example repo.

Ok, I was able to replicate it. The snapshots were created with jest --watch (and then u to update the snapshots). If I then run jest --coverage it fails in this manner:
  ● <Root /> › renders correctly

    expect(value).toMatchSnapshot()

    Received value does not match stored snapshot 1.

    - Snapshot
    + Received

    <BrowserRouter>
    -   <App />
    +   <Component />
      </BrowserRouter>

      at Object.<anonymous> (src/containers/__tests__/Root.test.jsx:13:82)

Results are the same locally and remotely.

CI build here: https://gitlab.com/ismay/enzyme-to-json-example/builds/6074425
Example repo here: https://gitlab.com/ismay/enzyme-to-json-example

i have the same issue on my current project. I identified it, as being a miss recognition on component written with lambda (example bellow) that has been instrumented by Istanbul.
 const Root = () =>
   (<Router>
     <App />
   </Router>);

It can be solved by writing using the following syntaxe.
 function Root () {
   return (<Router>
     <App />
   </Router>);
}

But i would prefer if we could fix it.
Is there someone working on it? should i give it a try (may be this week end)?

Thanks for your reports! I'll have a look when I have time

For what its worth it appears to effect https://github.com/rogeliog/jest-serializer-enzyme as well, so I guess the fix should be somewhere upstream but I don't know where. Would be great to have a fix :|

Anyone have an idea what's causing this? Enzyme wraps react-addons-test-utils, which does not support refs for shallow testing:
Shallow testing currently has some limitations, namely not supporting refs.

Could that be it?

Hi! I'm very late on this issue! I tried running @ismay's example repo, but as far as I can see, it's not related to enzyme-to-json. A quick way to find out is that I tried running:
console.log(wrapper.debug());

in the test and it shows the same component name as the Snapshot:
Debug output:
<BrowserRouter>
  <Component />
</BrowserRouter>

Snapshot:
exports[`<Root /> renders correctly 1`] = `
<BrowserRouter>
  <Component />
</BrowserRouter>
`;

The thing is that I'm just using Enzyme wrappers here to generate snapshots but I can't do more than Enzyme, if the output of .debug() is wrong, enzyme-to-json will be wrong too and it's more likely to be an issue with Enzyme, or Jest, or Istanbul in this case. As @ismay pointed out here, the issue only occurs when the coverage flag is on.

Yeah it's actually a problem with istanbul: https://github.com/adriantoine/enzyme-to-json/issues/19#issuecomment-266056074

Until there is a fix on this issue from istanbul...
I found this problem occurs with stateless functional components. You can get the same results with or without coverage in your snapshot tests by setting the .displayName property on stateless functional components.
const myComponent = () =>

myComponent.displayName = "myComponent"

@ismay: Yeah it's actually a problem with istanbul:

Exactly!
I've recently encountered this issue and I tried to fix it on the istanbul side. I forked babel-plugin-istanbul to fix this, and I put my discovery in here:
https://github.com/istanbuljs/babel-plugin-istanbul/issues/125
Could you folks let me know what you think about my proposal?