Uncaught ReferenceError: Set is not defined

View details in Rollbar: https://rollbar.com/mrorz/rumors-site/items/61/

ReferenceError: Set is not defined
  File "https://cofacts.g0v.tw/_next/static/chunks/commons.3d6e3726d3a6a9caf962.js", line 1, in Object.push.yl30
  File "https://cofacts.g0v.tw/_next/static/runtime/webpack-035ac2b14bde147cb4a8.js", line 1, in l
  File "https://cofacts.g0v.tw/_next/static/chunks/commons.3d6e3726d3a6a9caf962.js", line 1, in Object.push.i8i4
  File "https://cofacts.g0v.tw/_next/static/runtime/webpack-035ac2b14bde147cb4a8.js", line 1, in l
  File "https://cofacts.g0v.tw/_next/static/runtime/main-3a58bff3ca12f5b3e32f.js", line 1, in Object.push.IKlv
  File "https://cofacts.g0v.tw/_next/static/runtime/webpack-035ac2b14bde147cb4a8.js", line 1, in l
  File "https://cofacts.g0v.tw/_next/static/runtime/main-3a58bff3ca12f5b3e32f.js", line 1, in Object.push.BMP1
  File "https://cofacts.g0v.tw/_next/static/runtime/webpack-035ac2b14bde147cb4a8.js", line 1, in l
  File "https://cofacts.g0v.tw/_next/static/runtime/webpack-035ac2b14bde147cb4a8.js", line 1, in t
  File "https://cofacts.g0v.tw/_next/static/runtime/webpack-035ac2b14bde147cb4a8.js", line 1, in Array.r [as push]

This is visible multiple times a day, in mobile browswers:

Request URLs that triggers the error in Rollbar logs:

https://cofacts.g0v.tw/article/5mbnrazlawc4
https://cofacts.g0v.tw/reply/O1h8LmoBFV14knB4q_dp
https://cofacts.g0v.tw/article/3mz8vovtm6z62

Seems that babel is not polyfilling Set on Android 4.4.
https://stackoverflow.com/questions/50415754/nextjs-static-build-on-android-4-4-set-is-not-defined

Can reproduce on BrowserStack using Windows 7, Chrome 33:

The root cause is
polyfill

We can play with preset-env options on next.js by configuring next/babel: https://nextjs.org/docs/advanced-features/customizing-babel-config (See source file for next/babel defaults)
Maybe it will work after we specifically set Chrome version to 33.
Documentation: https://babeljs.io/docs/en/babel-preset-env#usebuiltins

Another thing is that object rest/spread operator depends on Object.assign, which is not supported by Chrome 33 either:


Updated configs to use a new AMI that supports the m5.* instances types, where appropriate

@thedarkwriter I'm good with this.  If you are as well, feel free to merge

@thedarkwriter Ready to be merged at your convenience, all classes for this week have been started. This file is only read by vcmanager when starting classrooms and does not interfere with any running classes.


BF: Outgoing Messages were not stored in case of errors (like 180s timeout)

Remove the messages from the outgoing messages store only when we know there have been successfully sent.

LGTM


Webpack not loading browser version of npm package

Bug report
Describe the bug
Not sure if this is specific to Next.js or is just a Webpack problem.
When installing an npm package that has both a main and a browser file path in its package.json, Next.js ignores the browser version of the package. For instance, the winston logger package has both a browser and a Node version. When I add winston as a dependency and try to import it into my React app, I get an error:
[ error ] ./node_modules/winston/dist/winston/tail-file.js
Module not found: Can't resolve 'fs' in '/Users/garrett/Documents/lambda/forms/node_modules/winston/dist/winston'

To Reproduce
CodeSandbox here: https://codesandbox.io/s/helloworld-wd6nd
Or to manually reproduce:

Create new Next.js app
Run npm i winston
Add import winston from "winston"; in your React app somewhere
Run npm run dev and see error in console output

Expected behavior
I would expect webpack to detect and load the browser compatible version of the winston package.
Screenshots
If applicable, add screenshots to help explain your problem.
System information

OS: [macOS]
Version of Next.js: [latest]

Additional context
Add any other context about the problem here.

Hi, this can be handled using webpack's node option which can be set in your next.config.js.
module.exports = {
  webpack: (config) => {
    config.node = {
      fs: 'empty'
    }
    return config
  }
}


Lack css in instructions

Great lib !
You should add something in the instructions to say we also need to import the CSS from VIS ( http://visjs.org/index.html#download_install ). It can be useful to display tooltips, for example.
Thanks

Hi Juleffel,
Thank you for your valuable feedback, ill definitely add the detailed documentation in my next update.
looking forward to more suggestions


fix: prep for next-ls release

Current dependencies on/for this PR:

main

PR #132   👈

This comment was auto-generated by Graphite.


Update Static Variables

Why:

Components had statically assigned values that could benefit from dynamic assignment via variables

What:

Updated elasticsearch, bastion, alb-controller, eks, ecs-service, and snowflake components with variable input

This looks good, but the "bats" tests are failing

Can you add simple descriptions to each variable in modules/eks/eks-without-spotinst/modules/node_group_by_az/variables.tf? That's not part of this change, but it's a requirement for bats to pass

Of course! I'll add it shortly! Thanks for the heads up

Just added those descriptions and bats passed!

I can do that! Thank you for checking that out.

Thank you @aknysh! Just applied those changes and formatted everything

Should I close this PR?

I think this may have stalled. Do you want us to review/update this PR, or close this one and open a new one, or abandon these updates (they were part of batch changes targeted across many components, not something we needed per se)


Add --no-ignore flag

Add --no-ignore flag to all commands with the purpose of ignoring the contents of the [IgnoreMap] section in a Romefile

          5 Warnings

:warning:
src/Lib.hs#L603 - Found Reduce duplication

1frameworkNameWithFrameworkExtension = appendFrameworkExtensionTo f
2platformBuildDirectory = carthageBuildDirectoryForPlatform platform
3frameworkDirectory
4  = platformBuildDirectory </> frameworkNameWithFrameworkExtension
5

Why Not

1Combine with src/Lib.hs:1106:5

:warning:
src/Lib.hs#L603 - Found Reduce duplication

1frameworkNameWithFrameworkExtension = appendFrameworkExtensionTo f
2platformBuildDirectory = carthageBuildDirectoryForPlatform platform
3frameworkDirectory
4  = platformBuildDirectory </> frameworkNameWithFrameworkExtension
5

Why Not

1Combine with src/Lib.hs:1316:5

:warning:
src/Lib.hs#L603 - Found Reduce duplication

1frameworkNameWithFrameworkExtension = appendFrameworkExtensionTo f
2platformBuildDirectory = carthageBuildDirectoryForPlatform platform
3frameworkDirectory
4  = platformBuildDirectory </> frameworkNameWithFrameworkExtension
5

Why Not

1Combine with src/Lib.hs:1349:5

:warning:
src/Lib.hs#L603 - Found Reduce duplication

1frameworkNameWithFrameworkExtension = appendFrameworkExtensionTo f
2platformBuildDirectory = carthageBuildDirectoryForPlatform platform
3frameworkDirectory
4  = platformBuildDirectory </> frameworkNameWithFrameworkExtension
5

Why Not

1Combine with src/Lib.hs:1485:5

:warning:
src/Lib.hs#L603 - Found Reduce duplication

 1frameworkNameWithFrameworkExtension = appendFrameworkExtensionTo f
 2platformBuildDirectory = carthageBuildDirectoryForPlatform platform
 3frameworkDirectory
 4  = platformBuildDirectory </> frameworkNameWithFrameworkExtension
 5dSYMNameWithDSYMExtension
 6  = frameworkNameWithFrameworkExtension <> ".dSYM"
 7dSYMdirectory
 8  = platformBuildDirectory </> dSYMNameWithDSYMExtension
 9bcSybolMapPath d = platformBuildDirectory </> bcsymbolmapNameFrom d
10

Why Not

1Combine with src/Lib.hs:664:5

  Generated by :no_entry_sign: Danger


add SolanaTextToSpeechTool

Pull Request Description
Related Issue
Fixes # (issue number)
Changes Made
This PR adds the following changes:

Add text to speech tool

Implementation Details

Turn text into lifelike spoken audio

Transaction executed by agent

Example transaction:
Prompt Used

Additional Notes

Checklist

[ ] I have tested these changes locally
[ ] I have updated the documentation
[ ] I have added a transaction link
[ ] I have added the prompt used to test it

hey @zhourunlai , appreciate the PR but imo this should not come under this kit, as it more focuses on solana integrations.
it would make more sense for any developer to use TTS along with the kit, making it modular in nature
wdyt


method level aggregation on LightModel

The LightModel currently aggregates all methods using the storage function. This is not practical because some functions might return different data types, it becomes messy and we end up having if statements and such.
So try to use decorators to apply storage functions at the method level. For benchmarking purposes, this allows a reduction in the number of floating point operations used to calculate results.

From a practical perspective, people want to see different outputs from the model for different purposes (e.g. someone might everything, someone might just want the premiums and claims, so maybe a targets = [<list of methods to output>] approach might work?
(If this is embedded in the model, then users would need to change the model to change what is output, which hurts auditability)

The LightModel can memory optimize it but you don't have to. if you don't memory optimize it then you can look inside the cache and make dataframes from the cache and so on, no information is lost. The thought is moving away from storage function as a thing that is used to report or view model results interactively.
The memory optimization destroys our ability to use the cache for interactive viewing of results. The thought is that storage function should only be used for large model runs that require memory optimizations where specific quantities are being calculated.
Thought is that storage function is not commonly edited and that review of model mechanics is performed using a non-memory optimized model by reviewing the cache.
Using targets=list[...] will mean that renaming of function requires changes in two places. decorator colocates them.
I will include you on the PR and put an example notebook out there so you can see the exact workflow I am imagining. May take a couple of days

closed via #22


Timestamp on note always displays the current time

We could add this manually in noosphere (https://github.com/subconsciousnetwork/noosphere/issues/487), and it looks like Subconscious sets a last-modified header already -- we should display that

Only some notes show this issue, and it's what happens when a memo is missing the Modified header.
In our case, @justinabrahms notes authored via orb seem to be missing these headers... at least in my replication of them.

Copying here what I wrote in Discord for posterity:

Sorry, this should have occured to me. I knew we weren't setting those headers in Noosphere (though maybe we should.. created is tricky to define, though, because we currently don't have a notion of "move" and can't disambiguate an overwrite of a slug from a major adaption of its content), and I should have asked if Subconscious was setting them as added headers
orb indeed does not set these headers today
(though it could)

The UX has improved somewhat here since we started listing profile notes by querying the local SQLite index, now the timestamp will at least be the last index time. This is still not actually correct from a user POV though.


Compute nightly fluxes and uncertainties

So far we have restricted the Twinkles light curves to one visit per filter per night - but in Run 3 we will get the full DDF stream, with multiple visits per night. The rough DM plan for the DDFs seems to be "do the same as we do in WFD, wherever possible" which means that we will probably just run the same Level 2 pipeline that we already developed, and so produce a ForcedSource for every visit, and ~10 per night. I think this means we need the Monitor to be able to compute nightly fluxes by combining the measurements taken in different visits during the same night. Comments welcome, SN afficionados! @rbiswas4 @wmwv
Can the Monitor write new tables to the Pserv database, @jchiang87 ? This would save us having to sum the same fluxes over and over again. Lets postpone implementing this until we've seen how fast it is to combine fluxes on the fly, though.

@drphilmarshall - I'm not at all convinced that this is something that we want to do.  By binning, which combining measurements to get a nightly flux effectively does, we are throwing away information.  I have no idea for what kind of stochastic behavior SN exhibit on these kind of time scales, but I could imagine that AGN might have short time-scale variations, which may be useful information in time-delay measurements.

Good point: the CatSim AGN do not have short timescale variations, but the real ones may well do. Let's not bin the SL light curves then, on principle. This could be an SN-only use case.

While SNIa do not have features on this time-scale, (and so co-addition) is safe, I too prefer to not coadd the nightly fluxes, unless DM plans to treat them that way (as far as I know this is not the case). We should simulate the expected behavior as far as possible.

There's nothing particular to be gained by thinking too hard about binning points on the same night.  I would recommend just taking the lightcurves as we get them.

So, all votes for not expanding monitor capability along these lines. @drphilmarshall did you have some necessity in mind that we are missing?

Nope! If we're all OK with working with visit fluxes rathre than nightly
fluxes, we can just close this out :-)
On Thu, Aug 25, 2016 at 9:03 PM, rbiswas4<EMAIL_ADDRESS>wrote:

So, all votes for not expanding monitor capability along these lines.
@drphilmarshall https://github.com/drphilmarshall did you have some
necessity in mind that we are missing?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/DarkEnergyScienceCollaboration/Monitor/issues/51#issuecomment-242624988,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AArY98DoGK48L-YoFNQSCjzBMX8AtjvVks5qjmWsgaJpZM4JtpmK
.


Romanian subtitle provider

Could you please add http://subtitrari.regielive.ro/ and https://www.titrari.ro/ as Romanian subtitles providers ?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Can somebody please have a look if can be implemented ? I want to give some help but i don't know where to start

+1


Update server-naming-convention.md

minor tweak on alias wording as account alias is only selected when creating sub accounts.  Also correcting the account alias character count.

@mcaminiti, users can still select their account alias on the activate page. Does your change still apply?
https://activate.centurylinkcloud.com/

My change still applies.  I corrected the incorrect alias character amount.  It is still published as 2-5 characters but it is only 2-4 characters.

Closing this pull request since I submitted my change on Chris's fork.


RuntimeError: CUDA error: no kernel image is available for execution on the device when initializing CUDA for gsplat

I am working with the following:
Ubuntu 22.04.4 LTS
Nvidia driver: 555.42.06
Nvidia RTX 3080 Ti
I have multiple cuda installations in the /usr/local folder but I have added the cuda-12.1 bin to PATH and lib64 to LD_LIBRARY_PATH
I have installed the CUDA12.1 pytorch binaries using pip, which based on my online research shows that it ships with the CUDA binaries to run it without external setup.
However, if I don’t add the /usr/local/cuda-12.1/bin to the PATH and try to run the project it throws a “gsplat: No CUDA toolkit found. gsplat will be disabled”. I am assuming this is because this repository has custom CUDA kernels which are not just pure pytorch code.
After adding to PATH, I dont get this error anymore, it starts initializing but fails after a while saying “RuntimeError: CUDA error: no kernel image is available for execution on the device”
Looking at the driver compatibility, it seems that the nvidia driver version 555.42.02+ is not compatible with any other CUDA except 12.5. Is this the reason the code is not running? Do I need a different nvidia driver?
Perhaps this is why I can do basic CUDA device hosted operations in pure pytorch but it fails when trying to run this repository. Any tips would be heavily appreciated as this is all new to me.

After some tinkering, I figured going with the gsplat installation that compiled gsplat during installation instead of JIT ended up fixing it for me. I wonder why that happened for knowledge sake though!

I encountered the same error with A30 GPU with Cuda 11.8. In my case, just compiling during the installation did not solve the issue but I was able to fix it by explicitly setting the compute capability of a GPU to target by modifying the setup.py as follows.
    nvcc_flags += ["-gencode=arch=compute_80,code=sm_80", "-gencode=arch=compute_80,code=sm_80"]

So I assume that this error has something to do with targeting the proper compute capability when compiling.


7 version in compare to 6 version always add extra space

System information:

Linux Mint 19.3
DBeaver version 7.2.4

Connection specification:

Database name and version
Driver name
Do you use tunnels or proxies (SSH, SOCKS, etc)?

Describe the problem you're observing:

While writing query and select from drop down list I got extra space which I delete every time.
In 6 version I did not face into this behaviour
Steps to reproduce, if exist:
I agree this is useful when I select field name and I at WHERE or at ON condition
But when I am at SELECT or chose tablename, the space is not required
Include any warning/errors/backtraces from the logs

hI, what database do you use?

PostgreSQL

could you provide a query example?

dbeaver.mp4.zip

unfortunately, the video isn't playable for me.
What formatter do you use? probably some special settings?
it will be awesome if you'll provide a query example, it will be very helpful fo issue investigation.
Thanks in advance

Video is created by kazam on linux. Probably you lack of some codecs =(.
Query example is on first post.
Sceenshots from video:

Please try to open Properties and go to SQL Editor>Code completion and disable Insert space after table/column names. It should help.

Thank you. But now I get vice-verca behaviour: at WHERE where space was useful I do not get it (not Ok :( )
at SELECT where space was unexpected. Now is OK

Please give a query example for WHERE

select *
from document d
where d.id = 33


Nav updates, content edits

After this PR, every experimental component will have Usage content.
New side nav structure.
Grammar fixes across the board.
Edits for entire "Patterns" section (fka Utilities).

Will take a look through tomorrow, thanks @claycrenshaw

Where can I see this branch (rather than review diffs);
Are we confident that any possible impact to outside referrers has been mitigated?

When we change the URL structure for Patterns (fka Utilities) we will need to set up redirects for those pages.

Vastly prefer 'Patterns' to 'Utilities'.

Good catch on those labels! @alisonjoseph

@alisonjoseph I don't know the proper way to update that folder structure and create the redirects. . . is that something you can take care of?


scan only changes in new PR compared to main in actions flow

Is there anyway to have a github actions flow only scan for changes that are introduced in a PR as opposed to scanning the entire codebase in the PR ?

The direct integration with GitHub would report on only changed resources in a PR, is there any way this could be achieved with the checkov-action?

Hi,
As we see there’s not much engagement for this request, we aren’t planning on implementing it ourselves. However, we would be glad to receive a contribution and would happily assist.
For now, I’m closing the thread.


add hard eviction threshold docs

What this PR does / why we need it:
This PR adds docs for the --eviction-threshold flag

Thanks @pidah !


NIFI-13186 corrected required runtime dep lucene-backward-codecs and …

…updated tests

Summary
NIFI-13186
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[ ] Apache NiFi Jira issue created

Pull Request Tracking

[ ] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[ ] Pull Request based on current revision of the main branch
[ ] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[ ] Build completed using mvn clean install -P contrib-check

[ ] JDK 21

UI Contributions

[ ] NiFi is modernizing its UI. Any contributions that update the current UI also need to be implemented in the new UI.

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Validating against m2 built index (lucene 8.11.3) vs this PR.  Will share more details.

Additional code changes applied now.  Tested with a previous build generating Lucene-8 indexes with a range of content.  Verified then again post this patch and it picks up where it left off, is still queryable, and continues generating new indexes with the lucene-9 naming.  Was able to query both old and new data in the system.  Also verifed query syntax still works despite not including the queryparsers module at this point.


Support react-i18next v13

This should fix https://github.com/stevensacks/storybook-react-i18next/issues/23.
The change in v13 of react-18next was https://github.com/i18next/react-i18next/blob/master/CHANGELOG.md#1300:
13.0.0

Update types to support t function redesign https://github.com/i18next/react-i18next/pull/1615
requires i18next >= v23.0.1

Thanks! I’ll check it out and get it merged soon.


Configure Datadog CDK Construct Library to use Projen

What does this PR do?
This PR configures Projen to handle the Datadog CDK configuration files such as the package.json, .gitignore, .npmignore, etc. Projen applies some sensible defaults but can be overridden via the projenrc.js file. Configuring Projen allows the Datadog CDK to be easily maintained and in the future be compiled into other languages via JSII. Projen allows the user to easily set up JSII workflows to publish your package to multiple package managers. Projen also has other useful stuff like anti-tamper/read-only on certain files which could help maintain the DD CDK.

Motivation
Ultimately we want to publish the Datadog CDK to multiple package managers, currently we only have it on NPM. Configuring Projen will furthermore allow the DD CDK to be converted to other languages via JSII.

Testing Guidelines
I converted the existing sample application into an integration test where I asserted that the CloudFormation template matched a Jest snapshot. Additionally I ran all the existing Jest tests and manually deployed the sample application (ExampleStack) to the sandbox AWS account and asserted results.

Additional Notes
Projen expects some files to be in certain directories so some of the structure of the DD CDK may have been changed. For example the source files used to be in lib but now they are in src. Also instead of compiling the Typescript to Javascript in the dist folder, now it places to js files in the lib folder.

Tasks.json is projens way of organizing scripts
Lib directory used to be dist
Src directory used to be lib
projenrc.js controls nearly all of the config files like Package.json, npmignore, gitignore, etc.

Types of Changes

[ ] Bug fix
[x] New feature
[ ] Breaking change
[ ] Misc (docs, refactoring, dependency upgrade, etc.)

Check all that apply

[x] This PR's description is comprehensive
[ ] This PR contains breaking changes that are documented in the description
[ ] This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
[ ] This PR impacts documentation, and it has been updated (or a ticket has been logged)
[x] This PR's changes are covered by the automated tests
[ ] This PR collects user input/sensitive content into Datadog
[ ] This PR passes the integration tests (ask a Datadog member to run the tests)

This all looks good to me, you mentioned that right now there is no longer an anti-tamper check on the package.json file. Is there some way to add that back? If not, not a blocker.

It was apart of the github workflows that Projen added but we opted to leave them out, I can try to add that logic into our existing build workflow in another PR


Type 'Scope' is not assignable to type 'this'

TypeScript Version:
1.9.0-dev.20160419
1.8.7
Code
class Scope {

    constructor(private locals: string[], private parent: Scope) {
    }

    find(name: string) {
        var scope = this;
        while (scope && scope.locals.indexOf(name) === -1) {
            scope = scope.parent; // ERROR: Type 'Scope' is not assignable to type 'this'
        }
        return scope;
    }
}

let outer = new Scope(['a', 'b'], null);
let inner = new Scope(['b', 'c'], outer);
assert(inner.find('a') === outer);
assert(inner.find('b') === inner);
assert(inner.find('d') === null);

Expected behavior:

compile time:  no compile errors
runtime: all assertions pass.

Actual behavior:

compile time:  compile error as shown in code comment.
runtime: all assertions pass as expected.

If an explicit type annotation is added, the error goes away:
    ...
    find(name: string) {
        var scope: Scope = this; // NB: type annotation added here
    ...

...but that type annotation seems superfluous given that this is already known to be a Scope.

I maybe wrong, but type this !== Scope.  It if guarding against you accidentally assigning something that could not be Scope in the future (e.g. if you extended Scope).
The problem really seems to be is you can't pass this as a type for an argument.  This code works, but obviously isn't what you desire, as it won't guard against the argument:
class Scope {

	private parent: this;

    constructor(private locals: string[], parent: any) {
		this.parent = parent;
    }

    find(name: string) {
        var scope = this;
        while (scope && scope.locals.indexOf(name) === -1) {
            scope = scope.parent;
        }
        return scope;
    }
}

@kitsonk thanks for the input

It if guarding against you accidentally assigning something that could not be Scope in the future (e.g. if you extended Scope).

I don't suppose you could come up with a little example of this? I'm not really understanding the type error. Especially since the code works and is reasonably idiomatic as JavaScript, I would have thought.

Since 1.7, in classes and interfaces, there is a special this types, which is then being inferred on the assignment you are making of var scope = this.  It is useful because it allow you to operate on things knowing that their type will change in the future:
class Animal {
  walk() {
    console.log('walking...');
    return this;
  }
}

class Dog extends Animal {
  bark() {
    console.log('barking...');
    return this;
  }
}

const dog = new Dog();
dog
  .walk() // < 1.7 would have returned type Animal
  .bark(); // so you wouldn't have been able to do this

So something of type this can be narrowed to Scope but something of type Scope cannot ever be widened into type this (because who knows at runtime what type this will be?)

But even if the instance was a subclass of Scope, every operation on the scope variable in the body of the find method would still work. Perhaps it would require too much analysis for the compiler to see that?

Yes, that is why type this can be narrowed to Scope, but what your code is doing is taking something that is specifically Scope (this.parent) and assign it to something that is type this.  What you do with it afterwards is irrelevant to the compiler.  Scope will always be a subset of this and this will always be a superset of Scope and Scope will never be equal to this in the mind of the compiler.

The obvious thing to try next is to change the constructor annotations to:
    constructor(private locals: string[], private parent: this) {
    }

...but that produces another error: a 'this' type is available only in a non-static member...
Then I tried (similar to your first suggestion):
class Scope {
    private parent: this;

    constructor(private locals: string[], parent: Scope) {
        this.parent = parent; // ERROR: Type 'Scope' is not assignable to type this
    }

In the end I've just added a type assertion on the var scope line to keep the compiler happy.

Yes, I ran into the same issues you did in "fixing" it, in that you cannot type guard this in arguments, which I think has been brought up before, but I can't remember the reason why it isn't offered.  That seems like the best way.
I think though the var scope: Scope = this is the most "accurate" solution at the moment and represents the intent of your code.  It does imply though that the return type of find() will be Scope instead of polymorphic this, which sounds like in your use case is perfectly fine.

as @kitsonk explained, this is Scope but Scope is not this. I would think of this as T extends Scope.

@mhegazy why is it not allowed to do the following (the first thing I tried to fix the Scope/this mismatch):
constructor(private locals: string[], private parent: this) { }

That gives the error a 'this' type is available only in a non-static member...

issue https://github.com/Microsoft/TypeScript/issues/5863 tracks adding it.
Polymorphic this types are an instance type feature, the constructor is part of the static side of the class.

Thanks!


Bower Updates stalled

Running bower update to add new polymer packages stalls.  I added the package via dependencies in the bower.json file.

Once I tried it in the terminal, I got the error message I need to see I had a few typos.


Do not show balance when the "show zero balance = 0" setting is disable

Describe the bug
Do not show balance when the "show zero balance = 0" setting is disable

Version test: https://github.com/openbitdev/OpenBit-Wallet/blob/openbit-dev--fake-account/build-demo/build_4-18-24_15-08.zip
Validation passed


i2g.io is down

thanks - got messed up in redirect loops - possibly with the move.  Will deal with it asap once other nddocs stuff is sorted.

still down.

@wrgr is this repo dead now?


Code commenting on the Python wrapper

Created all code comments in the Python Wrapper + fixed hsv_to_rgb conversion function

@WouterPennings, I found out that the hsv_to_rgb conversion function wasn't given the expected results. So I recreated the code and commented out the old code. If I didn't do it right you can just change it back, if I did do it right then it's fixed now.


Strange Swift compiler warnings on UIScrollViewDelegate

I am running xCode 6.3.1 (6D1002) and Swift 1.2. I'm targetting iOS 7.0 and above with my app.
I am using cocoapods to install/use SlackTextViewController. I am seeing two very strange Swift compiler warnings: http://cl.ly/image/1a242j412k0u
/apps/SnapSuggest/ios/SlackTextViewController.SLKTextViewController:296:14: Parameter of 'scrollViewDidScroll' has different optionality than expected by protocol 'UIScrollViewDelegate'
/apps/SnapSuggest/ios/UIKit.UIScrollViewDelegate:2:23: Requirement 'scrollViewDidScroll' declared here
and
/apps/SnapSuggest/ios/SlackTextViewController.SLKTextViewController:295:14: Parameter of 'scrollViewShouldScrollToTop' has different optionality than expected by protocol 'UIScrollViewDelegate'
/apps/SnapSuggest/ios/UIKit.UIScrollViewDelegate:16:23: Requirement 'scrollViewShouldScrollToTop' declared here
Anyone seen this or have any ideas? Googling these errors didn't turn up anything. Thanks in advance.

@dzenbot Sadly no. I ended up commenting out the two methods (scrollViewDidScroll and scrollViewShouldScrollToTop) to remove the warnings. This is obviously not a good solution but only thing that temporarily worked for me.


Notes not updated even though 'keep updated' is selected

Support log ID:
73CZWBD3-euc
Exporter used:
Better BibLaTeX
Expected behavior:
'keep updated' and 'export notes' are selected on export:

Actual behavior:
The notes are not kept updated. For example, the latter part of this note is not updated in the .bib file that was exported as above.

Can you give 1312 a go?

I would really prefer to know whether this build fixes the problem for you before merging this into a release.

Closing for inactivity


Add known issue: MyJobs database deleted

Document the consequences and recovery steps when the Job Composer database is deleted.

https://github.com/OSC/ood-myjobs/issues/306 for instance.


Blurry text inside the editor on Windows with display scaling

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
The text inside the editor is blurry on my Thinkpad T440s with Windows 10. I'm using a display scaling of 125%. It's not blurry when starting Atom with "--force-device-scale-factor=1", but then of course the elements are too small. It seems there is a problem with the scaling from Windows and Atom.
On the attached file you can see a comparison. On the left there is the blurry font, on the right the correct without display scaling.

Steps to Reproduce

Change the display scaling of Windows (https://www.thurrott.com/windows/windows-10/4597/windows-10-feature-focus-display-scaling)
Start Atom
see the blurry font inside the text editor

Expected behavior: clear font
Actual behavior: blurry font
Reproduces how often: 100%
Versions
1.13.0 and 1.14.0-beta0
Windows 10 Pro

Those screenshots both look incredibly blurry and pixelated to me :(

Strange, maybe it's the image quality when uploading something here. On my screen it's only blurry when there is a display scaling.
In the moment I'm working with atom with -force-device-scale-factor=1 and the Atom Material theme. With this theme it's possible to set up the size of the UI easily.

This may improve when we upgrade to Electron 1.4.

Latest Windows 10 insider builds also have a brand new DPI scaling methodology we need to check out.

With the latest beta (1.15.0-beta0) the scaling is better and not quite so blurred, but not as sharp as for example Sublime.


notes on using express-winston and @elastic/ecs-winston-format

I did some exploration of using @elastic/ecs-winston-format here with the express-winston middleware package. I'll collect notes here in case they are useful for:

anyone that wants to use these two modules together; and
possible future dev work to integrate support and/or docs for this.

Currently I'm not proposing integrating docs about using express-winston with @elastic/ecs-winston-format because I don't think it is a very satisfying integration (at least not yet).

A quick first pass:
// Adapted (heavily) from https://github.com/bithavoc/express-winston#examples

const ecsFormat = require('../') // @elastic/ecs-winston-format
var express = require('express')
var expressWinston = require('express-winston')
var winston = require('winston')

var logger = winston.createLogger({
  format: ecsFormat({ convertReqRes: true }),
  transports: [
    new winston.transports.Console()
  ]
})

var app = express();

// express-winston logger makes sense BEFORE the router
app.use(expressWinston.logger({ winstonInstance: logger }))

app.get('/error', function(req, res, next) {
  return next(new Error("boom"))
});
app.get('/', function(req, res, next) {
  res.setHeader('Foo', 'Bar')
  res.write('hi')
  res.end()
});

// express-winston errorLogger makes sense AFTER the router.
app.use(expressWinston.errorLogger({ winstonInstance: logger }))

app.listen(3000, function(){
  logger.info(`listening at http://localhost:${this.address().port}`)
});

yields request log output like the following:
% node express.js  | jq .
...
{
  "@timestamp": "2021-01-15T22:19:44.467Z",
  "log.level": "info",
  "message": "HTTP GET /",
  "ecs": {
    "version": "1.5.0"
  },
  "meta": {
    "req": {
      "url": "/",
      "headers": {
        "host": "localhost:3000",
        "user-agent": "curl/7.64.1",
        "accept": "*/*"
      },
      "method": "GET",
      "httpVersion": "1.1",
      "originalUrl": "/",
      "query": {}
    },
    "res": {
      "statusCode": 200
    },
    "responseTime": 2
  }
}

That minimally matches the ECS logging spec, so could pass. The unsatisfying part of this is that express-winston puts the req / res captured data under a top-level "meta" key, which means the current ecs-winston-format transform can not capture those as ECS HTTP fields.

A quick first pass:
// Adapted (heavily) from https://github.com/bithavoc/express-winston#examples

const ecsFormat = require('../') // @elastic/ecs-winston-format
var express = require('express')
var expressWinston = require('express-winston')
var winston = require('winston')

var logger = winston.createLogger({
  format: ecsFormat({ convertReqRes: true }),
  transports: [
    new winston.transports.Console()
  ]
})

var app = express();

// express-winston logger makes sense BEFORE the router
app.use(expressWinston.logger({ winstonInstance: logger }))

app.get('/error', function(req, res, next) {
  return next(new Error("boom"))
});
app.get('/', function(req, res, next) {
  res.setHeader('Foo', 'Bar')
  res.write('hi')
  res.end()
});

// express-winston errorLogger makes sense AFTER the router.
app.use(expressWinston.errorLogger({ winstonInstance: logger }))

app.listen(3000, function(){
  logger.info(`listening at http://localhost:${this.address().port}`)
});

yields request log output like the following:
% node express.js  | jq .
...
{
  "@timestamp": "2021-01-15T22:19:44.467Z",
  "log.level": "info",
  "message": "HTTP GET /",
  "ecs": {
    "version": "1.5.0"
  },
  "meta": {
    "req": {
      "url": "/",
      "headers": {
        "host": "localhost:3000",
        "user-agent": "curl/7.64.1",
        "accept": "*/*"
      },
      "method": "GET",
      "httpVersion": "1.1",
      "originalUrl": "/",
      "query": {}
    },
    "res": {
      "statusCode": 200
    },
    "responseTime": 2
  }
}

That minimally matches the ECS logging spec, so could pass. The unsatisfying part of this is that express-winston puts the req / res captured data under a top-level "meta" key, which means the current ecs-winston-format transform can not capture those as ECS HTTP fields.

Error logging, as well, works, but includes non-JSON output and captures a lot of data (by design). E.g. with a curl localhost:3000/errors for the server above:
{
  "@timestamp": "2021-01-15T22:18:29.399Z",
  "log.level": "error",
  "message": "middlewareError",
  "ecs": {
    "version": "1.5.0"
  },
  "meta": {
    "error": {},
    "level": "error",
    "message": "uncaughtException: boom\nError: boom\n    at /Users/trentm/el/ecs-logging-js/loggers/winston/examples/express.js:35:15\n    at Layer.handle [as handle_request] (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js:95:5)\n    at next (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/route.js:137:13)\n    at Route.dispatch (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/route.js:112:3)\n    at Layer.handle [as handle_request] (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js:95:5)\n    at /Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js:281:22\n    at Function.process_params (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js:335:12)\n    at next (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js:275:10)\n    at /Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express-winston/index.js:428:9\n    at Layer.handle [as handle_request] (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js:95:5)",
    "stack": "Error: boom\n    at /Users/trentm/el/ecs-logging-js/loggers/winston/examples/express.js:35:15\n    at Layer.handle [as handle_request] (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js:95:5)\n    at next (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/route.js:137:13)\n    at Route.dispatch (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/route.js:112:3)\n    at Layer.handle [as handle_request] (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js:95:5)\n    at /Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js:281:22\n    at Function.process_params (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js:335:12)\n    at next (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js:275:10)\n    at /Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express-winston/index.js:428:9\n    at Layer.handle [as handle_request] (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js:95:5)",
    "exception": true,
    "date": "Fri Jan 15 2021 14:18:29 GMT-0800 (Pacific Standard Time)",
    "process": {
      "pid": 48552,
      "uid": 501,
      "gid": 20,
      "cwd": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples",
      "execPath": "/Users/trentm/.nvm/versions/node/v10.23.0/bin/node",
      "version": "v10.23.0",
      "argv": [
        "/Users/trentm/.nvm/versions/node/v10.23.0/bin/node",
        "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/express.js"
      ],
      "memoryUsage": {
        "rss": 46510080,
        "heapTotal": 24936448,
        "heapUsed": 15907168,
        "external": 642616
      }
    },
    "os": {
      "loadavg": [
        1.11767578125,
        1.28173828125,
        1.3310546875
      ],
      "uptime": 2094642
    },
    "trace": [
      {
        "column": 15,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/express.js",
        "function": null,
        "line": 35,
        "method": null,
        "native": false
      },
      {
        "column": 5,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js",
        "function": "Layer.handle [as handle_request]",
        "line": 95,
        "method": "handle [as handle_request]",
        "native": false
      },
      {
        "column": 13,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/route.js",
        "function": "next",
        "line": 137,
        "method": null,
        "native": false
      },
      {
        "column": 3,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/route.js",
        "function": "Route.dispatch",
        "line": 112,
        "method": "dispatch",
        "native": false
      },
      {
        "column": 5,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js",
        "function": "Layer.handle [as handle_request]",
        "line": 95,
        "method": "handle [as handle_request]",
        "native": false
      },
      {
        "column": 22,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js",
        "function": null,
        "line": 281,
        "method": null,
        "native": false
      },
      {
        "column": 12,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js",
        "function": "Function.process_params",
        "line": 335,
        "method": "process_params",
        "native": false
      },
      {
        "column": 10,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js",
        "function": "next",
        "line": 275,
        "method": null,
        "native": false
      },
      {
        "column": 9,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express-winston/index.js",
        "function": null,
        "line": 428,
        "method": null,
        "native": false
      },
      {
        "column": 5,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js",
        "function": "Layer.handle [as handle_request]",
        "line": 95,
        "method": "handle [as handle_request]",
        "native": false
      }
    ],
    "req": {
      "url": "/error",
      "headers": {
        "host": "localhost:3000",
        "user-agent": "curl/7.64.1",
        "accept": "*/*"
      },
      "method": "GET",
      "httpVersion": "1.1",
      "originalUrl": "/error",
      "query": {}
    }
  }
}
{
  "@timestamp": "2021-01-15T22:18:29.401Z",
  "log.level": "info",
  "message": "HTTP GET /error",
  "ecs": {
    "version": "1.5.0"
  },
  "meta": {
    "req": {
      "url": "/error",
      "headers": {
        "host": "localhost:3000",
        "user-agent": "curl/7.64.1",
        "accept": "*/*"
      },
      "method": "GET",
      "httpVersion": "1.1",
      "originalUrl": "/error",
      "query": {}
    },
    "res": {
      "statusCode": 500
    },
    "responseTime": 3
  }
}
Error: boom
    at /Users/trentm/el/ecs-logging-js/loggers/winston/examples/express.js:35:15
    at Layer.handle [as handle_request] (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js:95:5)
    at next (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js:95:5)
    at /Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js:281:22
    at Function.process_params (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js:335:12)
    at next (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js:275:10)
    at /Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express-winston/index.js:428:9
    at Layer.handle [as handle_request] (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js:95:5)

Error logging, as well, works, but includes non-JSON output and captures a lot of data (by design). E.g. with a curl localhost:3000/errors for the server above:
{
  "@timestamp": "2021-01-15T22:18:29.399Z",
  "log.level": "error",
  "message": "middlewareError",
  "ecs": {
    "version": "1.5.0"
  },
  "meta": {
    "error": {},
    "level": "error",
    "message": "uncaughtException: boom\nError: boom\n    at /Users/trentm/el/ecs-logging-js/loggers/winston/examples/express.js:35:15\n    at Layer.handle [as handle_request] (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js:95:5)\n    at next (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/route.js:137:13)\n    at Route.dispatch (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/route.js:112:3)\n    at Layer.handle [as handle_request] (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js:95:5)\n    at /Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js:281:22\n    at Function.process_params (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js:335:12)\n    at next (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js:275:10)\n    at /Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express-winston/index.js:428:9\n    at Layer.handle [as handle_request] (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js:95:5)",
    "stack": "Error: boom\n    at /Users/trentm/el/ecs-logging-js/loggers/winston/examples/express.js:35:15\n    at Layer.handle [as handle_request] (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js:95:5)\n    at next (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/route.js:137:13)\n    at Route.dispatch (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/route.js:112:3)\n    at Layer.handle [as handle_request] (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js:95:5)\n    at /Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js:281:22\n    at Function.process_params (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js:335:12)\n    at next (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js:275:10)\n    at /Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express-winston/index.js:428:9\n    at Layer.handle [as handle_request] (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js:95:5)",
    "exception": true,
    "date": "Fri Jan 15 2021 14:18:29 GMT-0800 (Pacific Standard Time)",
    "process": {
      "pid": 48552,
      "uid": 501,
      "gid": 20,
      "cwd": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples",
      "execPath": "/Users/trentm/.nvm/versions/node/v10.23.0/bin/node",
      "version": "v10.23.0",
      "argv": [
        "/Users/trentm/.nvm/versions/node/v10.23.0/bin/node",
        "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/express.js"
      ],
      "memoryUsage": {
        "rss": 46510080,
        "heapTotal": 24936448,
        "heapUsed": 15907168,
        "external": 642616
      }
    },
    "os": {
      "loadavg": [
        1.11767578125,
        1.28173828125,
        1.3310546875
      ],
      "uptime": 2094642
    },
    "trace": [
      {
        "column": 15,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/express.js",
        "function": null,
        "line": 35,
        "method": null,
        "native": false
      },
      {
        "column": 5,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js",
        "function": "Layer.handle [as handle_request]",
        "line": 95,
        "method": "handle [as handle_request]",
        "native": false
      },
      {
        "column": 13,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/route.js",
        "function": "next",
        "line": 137,
        "method": null,
        "native": false
      },
      {
        "column": 3,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/route.js",
        "function": "Route.dispatch",
        "line": 112,
        "method": "dispatch",
        "native": false
      },
      {
        "column": 5,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js",
        "function": "Layer.handle [as handle_request]",
        "line": 95,
        "method": "handle [as handle_request]",
        "native": false
      },
      {
        "column": 22,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js",
        "function": null,
        "line": 281,
        "method": null,
        "native": false
      },
      {
        "column": 12,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js",
        "function": "Function.process_params",
        "line": 335,
        "method": "process_params",
        "native": false
      },
      {
        "column": 10,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js",
        "function": "next",
        "line": 275,
        "method": null,
        "native": false
      },
      {
        "column": 9,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express-winston/index.js",
        "function": null,
        "line": 428,
        "method": null,
        "native": false
      },
      {
        "column": 5,
        "file": "/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js",
        "function": "Layer.handle [as handle_request]",
        "line": 95,
        "method": "handle [as handle_request]",
        "native": false
      }
    ],
    "req": {
      "url": "/error",
      "headers": {
        "host": "localhost:3000",
        "user-agent": "curl/7.64.1",
        "accept": "*/*"
      },
      "method": "GET",
      "httpVersion": "1.1",
      "originalUrl": "/error",
      "query": {}
    }
  }
}
{
  "@timestamp": "2021-01-15T22:18:29.401Z",
  "log.level": "info",
  "message": "HTTP GET /error",
  "ecs": {
    "version": "1.5.0"
  },
  "meta": {
    "req": {
      "url": "/error",
      "headers": {
        "host": "localhost:3000",
        "user-agent": "curl/7.64.1",
        "accept": "*/*"
      },
      "method": "GET",
      "httpVersion": "1.1",
      "originalUrl": "/error",
      "query": {}
    },
    "res": {
      "statusCode": 500
    },
    "responseTime": 3
  }
}
Error: boom
    at /Users/trentm/el/ecs-logging-js/loggers/winston/examples/express.js:35:15
    at Layer.handle [as handle_request] (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js:95:5)
    at next (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js:95:5)
    at /Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js:281:22
    at Function.process_params (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js:335:12)
    at next (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/index.js:275:10)
    at /Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express-winston/index.js:428:9
    at Layer.handle [as handle_request] (/Users/trentm/el/ecs-logging-js/loggers/winston/examples/node_modules/express/lib/router/layer.js:95:5)

We could start to get closer on ECS HTTP fields via express-winston's dynamicMeta, e.g.:
const ecsHelpers = require('../../../helpers')

// ...

app.use(expressWinston.logger({
  winstonInstance: logger,
  dynamicMeta: function (req, res) {
    const meta = {}
    ecsHelpers.formatHttpRequest(meta, req)
    ecsHelpers.formatHttpResponse(meta, res)
    return meta
  }
})

// ...

which yields:
{
  "@timestamp": "2021-01-15T22:37:22.267Z",
  "log.level": "info",
  "message": "HTTP GET /",
  "ecs": {
    "version": "1.5.0"
  },
  "meta": {
    "req": {
      "url": "/",
      "headers": {
        "host": "localhost:3000",
        "user-agent": "curl/7.64.1",
        "accept": "*/*"
      },
      "method": "GET",
      "httpVersion": "1.1",
      "originalUrl": "/",
      "query": {}
    },
    "res": {
      "statusCode": 200
    },
    "responseTime": 1,
    "http": {
      "version": "1.1",
      "request": {
        "method": "get",
        "headers": {
          "host": "localhost:3000",
          "accept": "*/*"
        }
      },
      "response": {
        "status_code": 200,
        "headers": {
          "x-powered-by": "Express",
          "foo": "Bar"
        }
      }
    },
    "url": {
      "full": "http://localhost:3000/",
      "path": "/",
      "domain": "localhost"
    },
    "user_agent": {
      "original": "curl/7.64.1"
    }
  }
}

But again, that unsatisfyingly adds both our dynamicMeta and that from express-winston itself.

We could start to get closer on ECS HTTP fields via express-winston's dynamicMeta, e.g.:
const ecsHelpers = require('../../../helpers')

// ...

app.use(expressWinston.logger({
  winstonInstance: logger,
  dynamicMeta: function (req, res) {
    const meta = {}
    ecsHelpers.formatHttpRequest(meta, req)
    ecsHelpers.formatHttpResponse(meta, res)
    return meta
  }
})

// ...

which yields:
{
  "@timestamp": "2021-01-15T22:37:22.267Z",
  "log.level": "info",
  "message": "HTTP GET /",
  "ecs": {
    "version": "1.5.0"
  },
  "meta": {
    "req": {
      "url": "/",
      "headers": {
        "host": "localhost:3000",
        "user-agent": "curl/7.64.1",
        "accept": "*/*"
      },
      "method": "GET",
      "httpVersion": "1.1",
      "originalUrl": "/",
      "query": {}
    },
    "res": {
      "statusCode": 200
    },
    "responseTime": 1,
    "http": {
      "version": "1.1",
      "request": {
        "method": "get",
        "headers": {
          "host": "localhost:3000",
          "accept": "*/*"
        }
      },
      "response": {
        "status_code": 200,
        "headers": {
          "x-powered-by": "Express",
          "foo": "Bar"
        }
      }
    },
    "url": {
      "full": "http://localhost:3000/",
      "path": "/",
      "domain": "localhost"
    },
    "user_agent": {
      "original": "curl/7.64.1"
    }
  }
}

But again, that unsatisfyingly adds both our dynamicMeta and that from express-winston itself.

Another potential concern is that express-winston currently says it is looking for a maintainer. I don't know if there will be a reasonable intersection of express-winston and @elastic/ecs-winston-format users.
I'm closing this for now. We can re-open if there is interest.

Another potential concern is that express-winston currently says it is looking for a maintainer. I don't know if there will be a reasonable intersection of express-winston and @elastic/ecs-winston-format users.
I'm closing this for now. We can re-open if there is interest.


create database schema if not present.

As we currently use only two tables: zipnish_annotations and zipnish_spans, it is only those two that will get created.

good for now


[Outlook] (EIT) Remove Graph clause

Docs Build status updates of commit f658a26:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/outlook/authentication.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


MINOR: doc changes for KIP-372

Documentation changes for KIP-372

Adding Grouped
Deprecating Serialized
Adding withNamed to Joined
Naming repartition topics

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@guozhangwang, @mjsax, @vvcephei
\cc @JimGalasyn

Did you check if we have code example using Serialized in the docs? If yes, we should update them to use Grouped.

@mjsax ack, updated refs

retest this please

Merged to trunk and cherry-picked to 2.1


Makefile and Flake8

Add Makefile for installing requirements/running tests and add Flake8 support.

Looks like Ben did the flake8 stuff as well and his has merged first, so let's close this.


can i import less modules in

<!--
Before you continue...

i have tried to import some less and i found that when I import here, it would not work
<style lang="less">
@import  './test.less'

but it work when i add into script

so, I can not use "  @import   'somemodule.less'   " such webpack syntax ?

@Jeromy-L hi, could you show your code to how to use @antv/g2 with vite? thanks

@Jeromy-L hi, could you show your code to how to use @antv/g2 with vite? thanks

antv/g2 has some error when you add into vite project, the error was caused by g2 add the venn.js (npm package) you should change the antv/g2
you can find that it depend the venn.js and you can also find that venn.js/src/layout.js   this file has wrote some error cod:

so if you want to add antv/g2, maybe you should change this devDependencies

alright, i see. thank you.


Basic Vulkan device initialization

Just selects & initializes the device, doesn't actually render anything yet.

I have this, even more in separate repository. If you're interested to contribute I can commit my progress and then you can take it from there?

I’d love to take a look at what you’ve got.
I’m working on this in my spare time (not part of my day job) so I’m not sure how much time I’ll be able to dedicate to it. I just wanted to contribute some framework so if someone else wanted to take a stab at it, they wouldn’t have to start from scratch.
-Brian
From: Branimir Karadžić<EMAIL_ADDRESS>Sent: Thursday, December 15, 2016 12:45 PM
To: bkaradzic/bgfx<EMAIL_ADDRESS>Cc: Brian Harris<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [bkaradzic/bgfx] Basic Vulkan device initialization (#998)
I have this, even more in separate repository. If you're interested to contribute I can commit my progress and then you can take it from there?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/bkaradzic/bgfx/pull/998#issuecomment-267407452, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACiV41c_f5x5IgxeVeNsNoK9KlMhb522ks5rIYq3gaJpZM4LOaXt.

This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

The main stumbling block is shader compiler. Extracting reflection data, removing unused data, etc. But I have 01-cubes example running.

I'll commit my progress tonight and then you can take a look. I didn't do it so far because didn't want anyone to think it's at usable state.

It's in: https://github.com/bkaradzic/bgfx/commit/e0b901a98a376a0979d4337921b69dd2e114ca37

Btw, this is code that needs nudging to get shaders working... https://github.com/bkaradzic/bgfx/blob/master/src/renderer_vk.cpp#L3493


Add back python setup.py develop

First attempt at mimicking setuptool's python setup.py develop. Currently getting one error locally.

Note that travis does not test this.

closing for now, going stale


[20.09] bambootracker: 0.4.4 -> 0.4.5

(cherry picked from commit e940b82ab7959b4d254264f6cc266a654a520119)
Motivation for this change
Simple version bump with one dropped dependency.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 103808 1

1 package built:

bambootracker


v6 crashes tsc (OOM)

Environment
System:

OS: Linux 5.15 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
CPU: (4) x64 AMD EPYC Processor
Memory: 5.66 GB / 7.57 GB
Container: Yes
Shell: 5.1.16 - /bin/bash

Binaries:

Node: 20.3.0 - ~/.nvm/versions/node/v20.3.0/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v20.3.0/bin/yarn
npm: 9.7.1 - ~/.nvm/versions/node/v20.3.0/bin/npm
pnpm: 8.6.5 - ~/.nvm/versions/node/v20.3.0/bin/pnpm

npmPackages:

styled-components: 6.0.0 => 6.0.0

Steps to reproduce
npx tsc

v5 works, v6 crashes. Tested with TypeScript v5.1.5 and v5.0.4.
Expected Behavior
No errors.
Actual Behavior
<--- Last few GCs --->

[36408:0x6e45340]    38728 ms: Mark-Compact (reduce) 1881.5 (1966.8) -> 1881.5 (1919.3) MB, 1080.72 / 0.00 ms  (average mu = 0.400, current mu = 0.000) last resort; GC in old space requested
[36408:0x6e45340]    39784 ms: Mark-Compact (reduce) 1881.5 (1919.3) -> 1881.5 (1919.3) MB, 1055.64 / 0.00 ms  (average mu = 0.243, current mu = 0.000) last resort; GC in old space requested

<--- JS stacktrace --->

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: 0xc8e4a0 node::Abort() [node]
 2: 0xb6b8f3  [node]
 3: 0xeacb10 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 4: 0xeacdf7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 5: 0x10ad8ba v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
 6: 0x1089bd6 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [node]
 7: 0x107b21c v8::internal::FactoryBase<v8::internal::Factory>::AllocateRawArray(int, v8::internal::AllocationType) [node]
 8: 0x107b384 v8::internal::FactoryBase<v8::internal::Factory>::NewFixedArrayWithFiller(v8::internal::Handle<v8::internal::Map>, int, v8::internal::Handle<v8::internal::Oddball>, v8::internal::AllocationType) [node]
 9: 0x13aa25d v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Allocate(v8::internal::Isolate*, int, v8::internal::AllocationType) [node]
10: 0x13aa303 v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Rehash(v8::internal::Isolate*, v8::internal::Handle<v8::internal::OrderedHashMap>, int) [node]
11: 0x14daf23 v8::internal::Runtime_MapGrow(int, unsigned long*, v8::internal::Isolate*) [node]
12: 0x7fa125e99ef6
Aborted (core dumped)

Im also experiencing this

I also get the problem.
I currently don't know to how to make a correct reproduction.
I tried to create new project with the following info but don't get the error:

vite and react-ts template
styled-components, stylis
a simple component use styled and css

Can you post a reproduction please? There are too many variables for a simple issue to be helpful. If you aren't already, I'd recommend enabling skipLibCheck / skipDefaultLibCheck in your tsConfig

This approach doesn't work.

The types are definitely heavier than most because of how much prop-merging we have to do internally. I'll continue trying to find ways to optimize it... it's been very challenging tbh.

I did find though that deduping React types significantly sped up local compilation. If you have v17 and v18 types coexisting for example it made things like 5x slower

We will need to start using react v18 types internally soon. Maybe will ship that as a patch

Yes, types use too much RAM. This worked:
npx --node-options="--max-old-space-size=4096" tsc

I did find though that deduping React types significantly sped up local compilation. If you have v17 and v18 types coexisting for example it made things like 5x slower

If someone with this OOM issue could try deduping their React types (using yarn resolutions or equivalent) and let me know if that helps I'd appreciate it. This issue seems to be very environment-specific.

How would one do this with PNPM, never had to do it before. Looking at the PNPM docs here https://pnpm.io/package_json

We will need to start using react v18 types internally soon. Maybe will ship that as a patch or add it to peerDependencies with a permissive range so it dedupes better.

I like this idea

How would one do this with PNPM, never had to do it before. Looking at the PNPM docs here https://pnpm.io/package_json

pnpm.overrides I think

This seems like it could work as well?

How would one do this with PNPM, never had to do it before. Looking at the PNPM docs here https://pnpm.io/package_json

pnpm.overrides I think

Let me give it a shot

If someone with this OOM behavior could try deduping their React types (using yarn resolutions or equivalent) and let me know if that helps I'd appreciate it. This issue seems to be very environment-specific.

I tried to dedupe @types/react with yarn resolutions and it didn't help.
However I found out it first appeared in version 6.0.0, version 6.0.0-rc.6 is fine even with non-deduped @types/react

Seeing crashes on this as well on CI.

Also TS is painfully slow in editor (VS Code) post 6.0.0-rc.6 release version.

I also have only one version of @types/react in my lockfile.
tsc is still taking ~30 seconds with v6 vs ~3 seconds with v5., using upwards of 6GB of RAM, and failing with OOM on CircleCI.

Just want to let everyone know I'm going to continue looking into this, I've been moving houses this weekend so busy busy!

Also TS is painfully slow in editor (VS Code) post 6.0.0-rc.6 release version.

I have noticed this as well.  Just spent 2 hours trying to understand why my TS intellisense and webpack compilation timing were horrendously slow, finally tried downgrading styled-components back to v@^5, and that fixed my issue.  Not sure what's going on in v6, but it really screws with TS.

Also TS is painfully slow in editor (VS Code) post 6.0.0-rc.6 release version.

I have noticed this as well. Just spent 2 hours trying to understand why my TS intellisense and webpack compilation timing were horrendously slow, finally tried downgrading styled-components back to v@^5, and that fixed my issue. Not sure what's going on in v6, but it really screws with TS.

That should be largely resolved in 6.0.2-onward

Also TS is painfully slow in editor (VS Code) post 6.0.0-rc.6 release version.

I have noticed this as well. Just spent 2 hours trying to understand why my TS intellisense and webpack compilation timing were horrendously slow, finally tried downgrading styled-components back to v@^5, and that fixed my issue. Not sure what's going on in v6, but it really screws with TS.

That should be largely resolved in 6.0.2-onward

Yes version 6.0.2 largely resolves the issues of slowness with TS in general. I’d say TS is still a bit less performant than it was before (I was on 5.3.2 I believe prior) so there’s probably further optimization that could be done.

I’d say TS is still a bit less performant than it was before (I was on 5.3.2 I believe prior) so there’s probably further optimization that could be done.

probably true, and there's a few outstanding bugs to be resolved. The v6 types actually do more in general than the v5 ones so it makes sense that they're somewhat slower (within reason.)

Hi there, just wanted to chip in to tell I'm also running into this issue after upgrading to v6, is this still being worked on?  This is on a large project as well.

Facing this issue as well.
<EMAIL_ADDRESS>


Generalized coordinate vector and velocity vector representation questions

Hi all,
Just a quick question regarding the orientation and frames that you're using in Pinocchio. Since you're using Featherstone notation, this allows for both the 'world' frame and 'body' frame versions of the algorithm (from what I remember).
First question is: what is the order of the quaternion for the configuration vector q: is this w, x, y, z or x, y, z, w. (Or maybe some other format?)
Second question: When passing in the configuration vectors and velocity vectors to functions (RNEA for example), I assume these are done in body frame coordinates. Is that correct?

We are following the Eigen convention for Quaternions (x,y,z,w)

Second question: When passing in the configuration vectors and velocity vectors to functions (RNEA for example), I assume these are done in body frame coordinates. Is that correct?

The joint velocity is then expressed in the local frame of the joints, as Featherstone did. But for the config vector, the translation part of the free flyer (tx,ty,tz,x,y,z,w) has two components:

the translation (tx,ty,tz) expressed in the WORLD frame
the rotational part (x,y,z,w), corresponding to the Quaternion representing the underlying free flyer orientation.

We chose to express the translation in the world frame for efficiency reasons.
I hope it will answer your question,
Justin

Hi Justin,
Thanks for that. Just to clarify, does that mean the quaternion representing the free flyer joint is in reference to free flyer frame itself?
Finally, forgot to ask; what is the angular velocity representation for the velocity vector? Is this an euler angle or some other form of representing the angular velocity?

The quaternion does any real coordinate systems quote and quote. They are then transformed as rotation to populate a SE3 element.
The angular velocity of the rotational part is nothing more than a 3D vector. So the angular velocity is expressed in the body coordinates system.
We are not relying on Euler angles and their derivatives because they own underlying singularity issues we prefer to avoid.

Okay thank you. I will close this for now since I think this answered my questions. :)


Custom Tab Scroll Buttons

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
I would like the ability to modify the default TabScrollButtons when scrollButtons are enabled. This would include the following:

The ability to change the default SvgIcon for the Scroll Buttons in the Tabs component
The ability to disable the ripple effect for the TabScrollButtons with disableRipple

Current Behavior
When scrollButtons="on", two button elements are rendered for the previous/next arrows, each with their own SVG (KeyboardArrowRight and KeyboardArrowLeft). I currently am not aware of a solution to replace those with my own SVGs and further customize their settings.
Current Code
import React from 'react';
import Tabs, { Tab } from 'material-ui/Tabs';

const TabBar = ({ tabs, activeTab, setActiveTab }) =>
  (<MaterialTabs>
    <Tabs
      value={activeTab}
      onChange={setActiveTab}
      scrollable
      scrollButtons="on"
    >
      {tabs.map(({ id, name }) =>
        (<Tab
          key={id}
          label={name}
          value={id}
          disableRipple
        />),
      )}
    </Tabs>
  </MaterialTabs>);

export default TabBar;

Your Environment

Tech
Version

Material-UI
1.0.0-beta.13

React
15.6.2

browser
Chrome version 61.0.3163.100

@kccmcck I think that the best option is to allow people providing their own TabScrollButton component implementation.

@oliviertassinari "I think that the best option is to allow people providing their own TabScrollButton component implementation." Do you mean we need to allow users to add custom icon button leftScrollButton, rightScrollButton and provide callback when clicked ?

@lawlessnut No, I was proposing adding a TabScrollButton property that accepts a component.

@oliviertassinari So, if TabScrollButton is present then it will render as scroll buttons on left and right of tabs like < ..tabs.. >. else TabScrollButton not present then it will defaulted to current behavior.

@oliviertassinari if we want to do that then we have to expose callback on TabScrollButton components that will do ability to scroll left or right...  Which is already exist inside component.. i believe we need to provide customize icons and disable/enable ripple effect as @kccmcck ask

The ability to change the default SvgIcon for the Scroll Buttons in the Tabs component
The ability to disable the ripple effect for the TabScrollButtons with disableRipple


Resolved the Gap Issue in Webpage

Hey @Soumyajit2825 Here i Resolved the Provided issue of gap between and video and Images Divs and Changed the last image as it was not present in Image Directory so Check my PR

Star our repo if u liked it.Thank u

merged. Star our repo if u liked it. Thank u
On Sat, Oct 8, 2022 at 1:17 PM Anant2961 @.***> wrote:

Hey @Soumyajit2825 https://github.com/Soumyajit2825 Here i Resolved the
Provided issue of gap between and video and Images Divs and Changed the
last image as it was not present in Image Directory so Check my PR
You can view, comment on, or merge this pull request online at:
https://github.com/Soumyajit2825/MESSI_MANIA/pull/15
Commit Summary

b917b76
https://github.com/Soumyajit2825/MESSI_MANIA/pull/15/commits/b917b76e7a46d09cecf744555fbe2daf7e7db830
Resolved the Gap Issue in Webpage

File Changes
(2 files https://github.com/Soumyajit2825/MESSI_MANIA/pull/15/files)

M home.html
https://github.com/Soumyajit2825/MESSI_MANIA/pull/15/files#diff-1b062b89d86c4bd360d644be21410ec92100adac7ed27c5e47a9a38757993f45
(2)
M style.css
https://github.com/Soumyajit2825/MESSI_MANIA/pull/15/files#diff-b78be019f1dc6d57753ea900c3805b114cd53ab7c0db836cc081836df1b99b7a
(18)

Patch Links:

https://github.com/Soumyajit2825/MESSI_MANIA/pull/15.patch
https://github.com/Soumyajit2825/MESSI_MANIA/pull/15.diff

—
Reply to this email directly, view it on GitHub
https://github.com/Soumyajit2825/MESSI_MANIA/pull/15, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AX64265VS76ONGBFT5CTY43WCERKNANCNFSM6AAAAAARAEWHC4
.
You are receiving this because you were mentioned.Message ID:
@.***>


How the backend is considered to be successful

After I deployed the backend, the backend displayed the URL, and I searched the browser for the following errors

Hi @ck1123456  you can it the health route to check the backend status


Increment lifetime counter on advertisement

Problem
The LifeTimeCounter was not following the specs, as it is not incrementing for every advertisement (BLE/MDNS)
The lifetime counter SHALL be an integer at least 16 bits in size, incremented upon each
commencement of advertising, and wrapping when the maximum value is reached.

Change overview
Incremented the lifetime counter on every advertisement
Testing
Used chip-shell to check if the lifetime counter will be increment on each advertisement (e.g. ble adv start)

@hnnajh I did some testing on nrfconnect platform and I can confirm the counter value is changing, however the behavior looks like this:

After boot and starting advertising (opening commissioning window) the counter value is equal to 3
After advertising timeout and starting it again (open commissioning window) the counter value is equal to 5
Subsequent attempts increment counter by 2 every time
I think that with current implementation you increment counter on every BLE advertising start and on every commissionable node discovery start independently, so it is incremented once on after boot (init starts commissionable discovery) and then two times on every open commissioning window. Is that behavior expected?

I don't have strong opinion on that, but I would expect the counter will be incremented once per every open commissioning window and the counter value will be kept consistent between BLE and DNS-SD advertisements. If you would agree with me on that please consider putting the following code:

#if CHIP_ENABLE_ADDITIONAL_DATA_ADVERTISING
// Increment life time counter to protect against long-term tracking of rotating device ID.
ConfigurationMgr().IncrementLifetimeCounter();
#endif

in this method: https://github.com/project-chip/connectedhomeip/blob/master/src/app/server/CommissioningWindowManager.cpp#L271. That should increment counter on every commissioning window open in a common generic way for both DNS-SD and BLE without a need of splitting the code on the two cases.


Not able to enable the Wireless Debugging option on WSA

Steps to reproduce

Open the Windows Subsystem for Android app
Go to "Advanced Settings" and enable "Developer mode"
Click on "Manage developer settings" to open "Developer Options"
Scroll down to the "Wireless Debugging" option and enable it

✔ Expected Behavior
Wireless Debugging should be enabled.
❌ Actual Behavior
Not able to enable Wireless Debugging.

Background: I have Android Studio and the development environment setup on a Mac. And WSA is running on a separate Windows 11 laptop. My goal is to connect the development environment (Android Studio) on Mac to WSA so that I can run and debug the Android app on WSA from Android Studio on Mac.
I was expecting to use the "Wireless debugging" option to connect to WSA over WIfi as suggested in the Android Developer documentation here.
Other Software
WSA version: 2311.40000.5.0
Microsoft Windows version:  22H2 (OS Build 22621.2715)
Please specify the version of Windows Subsystem for Android
WSA version: 2311.40000.5.0

womp womp

same 😕


chore(docs): remove disallowEmptySelection from tabs page

Closes #3608
📝 Description
disallowEmptySelection doesn't exist in tabs
⛳ Current behavior (updates)

Please describe the current behavior that you are modifying

🚀 New behavior

Please describe the behavior or changes this PR adds

💣 Is this a breaking change (Yes/No):

📝 Additional Information

Summary by CodeRabbit

Documentation

Updated the Tabs component documentation by removing the disallowEmptySelection property, indicating a potential change in user interaction with the tabs.

@wingkwong branch out from main since there are not packages changes

@jrgarciadev created a new one here: https://github.com/nextui-org/nextui/pull/3648


Picked: QA Steps to check breakages in CI

Let's ensure all 0.6.x updates are 100% compatible with 0.6.0.
Acceptance Criteria

The CI should run something to enforce that.
The main/0.7 tag may include breaks from 0.6. Those need to be noted in human-readable docs. Where?
We can also consider what level of automated support we can/want to use here. Document a set of test an create a collection of issues for that on the board. Should it be split from this task?

There are some questions open and need to be clarified in the refinement.


[Storage] [DataMovement] Added support for Share File to/from Blob for Single Transfer

Mainly this was ensuring that the Single Transfer Share File to/from Blob transfers maintained properties that were preservable/settable. Which just contained a lot of test updates.
One change that had to be made was ensuring that Content Language and Content Encoding property type was converted properly from object to string array to string. Since Blobs accepts these as a string while Shares accept this value as a string[]

API change check
API changes are not detected in this pull request.


show typing status on small team rows

@keybase/react-hackers
I think it is a nice touch to have typing status in the inbox view, and most other messengers have this. Here is what it looks like:

cc @cecileboucheron @adamjspooner @malgorithms for any comments/concerns.

Updated type, not sure why this would cause thrashing of any kind.

Ok moved the stuff up one function, let me know if that works.


Adding comment about storing passwords in plain text

+1
Looks great

Actually, can we link it to https://technet.microsoft.com/en-us/library/dn781430.aspx ?
We get consistent feedback from customers that they can't use documentation from blogs, especially for security-related stuff (for support and compliance reasons). If the TechNet article isn't accurate, we can and should improve it. (I know we lose syntax highlighting though, that's kind of a bummer.)

That's a good point @joeyaiello I'll use TechNet doc instead


Make getFormByStatus more efficient for scaling

https://github.com/cds-snc/platform-forms-client/blob/a47bb740957475555c0d1c1fef315b71df416623/lib/dataLayer.tsx#L198
In order to support a larger number of forms in the future we can make this function more efficient by creating a specific DB call in the lambda to support it instead of returning all forms records and then filtering through.
Will probably need to create a migration for the Database and store the publishing status outside of the form-config JSON.

@falila @craigzour Hey team! Can you please add your planning poker estimates with ZenHub


List successful tests

Hi,
I started using chaplain and I like it very much. It was very easy to get started. What I found that I'm missing now is a list of the successful tests. Here is an example below (this is sbt scala tests).

Basically, the successful tests allow you to verify that you covered all the cases (urls in this case). Also it gives you the satisfaction looking at the green colors covering your console .. hehe.
Is there any chance you can do something like that? It can be optional with a -v if you don't like it so much.

This actually was how chaplain worked at first, but I quickly found it cumbersome with a larger number of tests . But I've also used mocha with the spec reporter and 200+ tests in the past, which looks mostly like your screenshot and scrolls past too quickly to read, so it's mostly a question of taste and what you're used to :).
Let's just say this is not a high priority - most of the work until 0.4.0 will be focused on getting the test themselves as generic and easy as possible. I hope this is not a deal breaker for you.
I'll keep this issue open and deal with it some time before 0.5.0, most probably by a "reporter" system like Mocha's.

Yeah sure. It's not a big thing this one. I can do my verification by going though the configuration file. But will be good to have one day.
Indeed, when you run all the tests it's too much to output, but when you run a smaller part of it (was just going to create a new issue about it) .. let's say a controller, then the output will be smaller and very helpful (to see if you covered everything).

Not creating a new issue .. found how you can run all the tests of a certain suite (chaplain run drinks.*)


variable precedence

I think it would be useful to take a look at how variable precedence is being evaluated.
The current hierarchy seems to be: template > cli param > input file
I would suggest instead: cli param > input file > template
The suggested order would give more priority to specifically defined variables and less priority to more generally defined (template-level) vars.

It looks like this isn't really a function of jinja2-cli and more about how jinja2 handles variable scoping. To get the behavior I need I will just use {% set myvar = myvar | default("My Default Value") %}


Underline in Components/Nav not displaying correctly

Description:
The underline in the Components/Nav is not displaying correctly. This issue occurs on all browsers and devices that I have tested on.
Steps to Reproduce:
Create a new Angular project using CoreUI
Add a Navigation bar to your project using the Components/Nav component
Observe the underline of the Navigation bar
Expected Result when use ...
The underline of the Navigation bar should be a thin line of the correct color (as specified in the CSS)
Actual Result:
The underline of the Navigation bar doesn't work
Notes:
-- CoreUI version

-- screenshot of the bug

--the code snippet that is causing the issue

--work with

@davalbra variant="underline" works for the pro version only, I am afraid. We should mention it in the docs.

Now I know, I was confused because on the CoreUI-Angular web page the information did not tell me anything about it.

docs updated


CosmosDiagnostics on unexpected exceptions

This issue is to discuss on how to include the diagnostics on unexpected exceptions that are usually a result of the SDK itself having a bug like a null reference exception.

Create wrapper for each exception type. This is error prone and complex, but has no impact to users.
Create a CosmosClientException. This would wrap any exception that is not expected and include the traces.
a. Should it be internal or public?
b. Store original exception as inner exception or map the properties to the original exception while just modifying the message and ToString()?

For now it was decided to add a internal exception type that wraps the information to avoid any new public contracts.


Remove directly accessing models in migration specs.

@lpichler @jrafanie @chessbyte  Please review.
This is biting me in the configuration revamp because the Configuration model is gone in that branch.

Looks good to me.  cc @lpichler (please update your issue's list of remaining problems)

:+1: :pencil2:   https://github.com/ManageIQ/manageiq/issues/6739


whitelist: close the tracking issue when approved or rejected

I didn't implement this intentionally, let me explain my point of view:
When someone (packit service maintainers) approve account on the whitelist, this issue should be closed by the person which did the approval or rejection, to be able to track it down and in some cases maybe explain the reason.

But AFAIK that is not what the internal docs say :D hence this issue.


Completions for Tensorflow 1.12.0 missing

Microsoft/vscode-python#3515
The OP says Jedi is fine and both Jedi and LS worked fine under 1.11.0.

Seems like we got worse since #285.

I just saw the edit about the version info. If it's actually broken from 1.11 to 1.12, then I would have guessed that there was some code change there which uses some feature we don't completely support.
But looking at their repo, I don't believe that to be the case. There haven't been any changes to the nn module since August, which is before even 1.11 was released.

Per https://github.com/Microsoft/vscode-python/issues/5141, this still seems to be a problem.

I fixed this in #881; the stable channel does not have the fix yet. It be tested in the beta channel.

ah, thanks


Add UnivariateTimeTypeToContinuous transformer to builtins

Implements univariate case of TimeType transformer discussed in https://github.com/alan-turing-institute/MLJModels.jl/issues/234
I would appreciate feedback, especially recommendations on how to add tests.

Good feedback. I’ll update the PR soon.

I added the checks and I pushed the new version to the dev branch of venuur/MLJModels.jl. According to github the changes should show up here (though I don't see them yet). I'll be adding tests later in the week.

According to github the changes should show up here (though I don't see them yet). That's weird.

When I look at the commits tab up top, I see the commits in the attached screenshot.

The date doesn’t match what you are showing.

Your latest commit appears there, it seems to me.  It's at the bottom. Perhaps what's confusing you is that this tab lists the commits in the opposite order to that in the conversations tab?
Sorry I can't be more helpful.

My latest commit on my fork is https://github.com/venuur/MLJModels.jl/commit/3abaa0965d299bd22dfaff0302c781357270d082
That is not the one on this pull request, right? Or am I just reading it all wrong, which is totally possible.

No sorry, I must have been looking in the wrong place. This is quite weird. Going to close and re-open - see if that helps

Nah. Can you add # testing push at the top line of src/MLJBase.jl, commit and push, and let's see if that appears here.

Looks like it's updated finally.

Looking great! Thanks adding such detailed checks.
I think all that's needed now are some tests.

@venuur Be great to have some tests when you get a chance.

Thanks for pinging me. I haven’t forgotten about this, it’s just my workload has been heavier than usual so it may be another week or two before I can wrap this up.
I’ll definitely get to it, the timeline is just a bit pushed compared to my original plan.

No worries at all!!

Added tests and fixed a couple corner cases while writing the log tests. There's an annoying issue that the default constructor uses a step of Hour(24), but when applied to a Date, we need to convert to Day(1), which is fine, but since the constructor doesn't distinguish a user supplied step versus the default, a warning message is printed. I would rather add some extra checks to avoid the message if it's the default value, but I don't have the time right now to figure out the right logic.
Excepting the somewhat unnecessary log message, the current version should be complete. Please let me know if I'm missing anything.

Should be all good for your next review when you get a chance @ablaom

And, if you haven't noticed, there's a failure for julia 1.0. Here's an excerpt:
┌ Warning: Cannot add `TimePeriod` `step` to `Date` `zero_time`. Converting `step` to `Day`.
453└ @ MLJModels ~/build/alan-turing-institute/MLJModels.jl/src/builtins/Transformers.jl:408
454TimeTypeToContinuous: Test Failed at /home/travis/build/alan-turing-institute/MLJModels.jl/test/builtins/Transformers.jl:125
455  Expression: all(dt_continuous .== ex)
456Stacktrace:
457 [1] macro expansion at /home/travis/build/alan-turing-institute/MLJModels.jl/test/builtins/Transformers.jl:125 [inlined]
458 [2] macro expansion at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.0/Test/src/Test.jl:1083 [inlined]
459 [3] top-level scope at /home/travis/build/alan-turing-institute/MLJModels.jl/test/builtins/Transformers.jl:96
460TimeTypeToContinuous: Test Failed at /home/travis/build/alan-turing-institute/MLJModels.jl/test/builtins/Transformers.jl:134
461  Expression: all(dt_continuous .== ex)
462Stacktrace:
463 [1] macro expansion at /home/travis/build/alan-turing-institute/MLJModels.jl/test/builtins/Transformers.jl:134 [inlined]
464 [2] macro expansion at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.0/Test/src/Test.jl:1083 [inlined]
465 [3] top-level scope at /home/travis/build/alan-turing-institute/MLJModels.jl/test/builtins/Transformers.jl:96
466┌

Sounds good. I’ll make the changes you suggested and look into the Julia 1.0 error.

Okay, working on the conflicts and adding the extras referred to above ...

Thanks for following up. And sorry for disappearing. As you may guess, I haven’t had time and won’t have time for a while to work on this. I’m still happy to comment here where I can.

No worries. You put a lot a fine work into this.
Note the multivariate (table) case will be handled by https://github.com/alan-turing-institute/MLJModels.jl/issues/288 .
Closing in favour of #295.


I found some bugs using this lib

This lib is amazing, i love it, but it is not working at all
I found some bugs:
1- u can not jump/jump a wall if u are using animation that is not DEFAULT (0) [this is the most important bug (its not possible to use to use it with this bug) /]
2-
warning 213: tag mismatch: expected tag "e_RUNNING_STYLES", but found none ("_")

on:
    else if(dialogid == 530) {
      if(!response) return 1;
      Player_SetRunningStyle(playerid, listitem);
    }

3- its not working well with https://github.com/Mergevos/samp-walking-styles, if i'm walking with a custom animation and then run with a custom animation the camera break/frooze (idk how to explain it, pls test)
4- CIVIL run style isn't working (3)
5- run with space is bugged

In order to fix error number 2, you need to tag the listitem parameter, like  e_RUNNING_STYLES: listitem
What do you mean by run with space is bugged? It's not meant to run with space. It's just running with w on keyboard.
If you can, and willing to, you can record some videos and post it here.
Thanks for reporting, I'll try to fix it as soon as possible.

1
still cant jump with this lib, so who is not using the default running style, cant jump walls or even jump at all
if you manage to fix it this lib is usable
2
So 2 is my bad, fixed with your comment, ty
3
tried to reproduce it again to record the video to you, but i couldnt it may be some specific, or an error here, just ignore it, if i find it out again i tell you
4
i think civil run style is the default, so it is not bugged at all, its just like to be with no run style, right?
5
when i try to run with W+SPACE
this stop the run animation to run the custom run animation
its good to animations like: ARMED, ARMED1, CHAINSAW, ROCKET, because they are already over power run style, and it is fun to be like that, but can u fix it to the others animations?

1 still cant jump with this lib, so who is not using the default running style, cant jump walls or even jump at all if you manage to fix it this lib is usable
2 So 2 is my bad, fixed with your comment, ty
3 tried to reproduce it again to record the video to you, but i couldnt it may be some specific, or an error here, just ignore it, if i find it out again i tell you
4 i think civil run style is the default, so it is not bugged at all, its just like to be with no run style, right?
5 when i try to run with W+SPACE this stop the run animation to run the custom run animation its good to animations like: ARMED, ARMED1, CHAINSAW, ROCKET, because they are already over power run style, and it is fun to be like that, but can u fix it to the others animations?

Can you tell me which animations causes lagging to you.
By the way, thanks for reporting.


Diagnostics: Removes unused properties and reduces size

Removing starttime and id fields from diagnostics string to reduce the length of the string.
Description
This change is part of the fix for Issue 3099 . As part of this change, we are capturing all diagnostics fields but removing starttime and id of child traces in the diagnostics.Tostring(). This will reduce the string length. It is an incremental fix and a way to filter handlers is still being investigated.
Before change:

After change: Id and startimeTime removed from children traces

Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Clarifications:

Do root level start and end-time still exists?
@ealsur will it impact any automation?

@kirankumarkolli Automation does not use any of these attributes. Based on the trace files in this PR, Summary is not impacted (start time is still there), id is removed

@kirankumarkolli This PR is not removing anything from the Transport or Request information. This is just removing properties from the handlers based on the linked design and discussion