Add NoRecording Span

Originates from https://github.com/open-telemetry/opentelemetry-js/pull/99#issuecomment-513325536

We have decided to go with solution 1: Use three different types of spans.
NoopSpan - Singleton, all the operations are no-op. (low allocation)
NoRecordingSpan - all the operations are no-op except context propagation.
RecordingSpan - all real operations (context propagation and recording).
Action items:

Make current NoopSpan as singleton instance.
Add NoRecording Span.


Disclose possible conflict of interest that is raised in regard to owner of the website

Issue
The website is run by a person (Arthur Edelstein) who is affiliated and works for Brave Software; This raises a conflict of interest, as Brave is a company that competes with other browser vendors. This can be verified by searching online of said person and reading in written words that he is employed by Brave Software.
Impact
The conflict of interest could lead to biased reporting on the website. The site might be more likely to publish positive content about Brave and negative content about its competitors, for example by disabling privacy or security features for its rivals, not disclosing this, and tanking the trust of rival browsers like Firefox, Safari, DuckDuckGo, etc. (FWIW, I use IceCat.)
Proposed Solution

Add an easily visible notice or disclosure that while the website is not directly related or created by Brave itself, that it maintained or ran by someone who now works for Brave Software. This will help ensure the website is trustworthy and that the people behind it are not using it for the benefit of their employer, especially after the employee joined the company after the website was up for a while.

@SocietasEvanescentes Thank you for your suggestion. I understand why you made this proposal and I have considered the approach.
First I should mention that there is already a disclosure on the website, which you may have seen: https://privacytests.org/about.html. Readers can reach it by clicking the "About" link on the homepage. This disclosure was posted when I first joined Brave.
It's true that some casual readers may not see this disclosure. On the other hand, I don't think a focus on my employment would be particularly helpful to readers. Regardless of my employment status, the rightness or wrongness of the test results depends primarily on what is being tested and how the tests are implemented. Fortunately it is possible to evaluate those things directly by examining the list of tests, reading the code, running the code, etc. That kind of careful examination is going to be far more meaningful than speculating about the effects of my employment status.
So while I have no desire to hide the fact that I work for Brave, I also think putting it as the primary content "above the fold" on the website would distract from the information the website is designed to convey.

@arthuredelstein
Thank you for your feedback about the disclosure of your employment status on the privacytests.org website. I appreciate your concern for transparency, and I understand your point of view.
However, I respectfully disagree with your assessment of the situation. I believe that the disclosure of your employment status is important for several reasons.
First, it is significant for users to be aware of any potential conflicts of interest. As you have acknowledged, your employment with Brave could potentially bias the results of the tests. By disclosing your employment status, you are giving users the opportunity to factor this information into their assessment of the tests. In the current version of the website, a user must click about and scroll about three or four paragraphs to find the disclosure; I believe making this more visible either by moving it to the top of the about page, or adding a banner somewhere on the front page ensures good will, which leads me to below.
Second, the disclosure of your employment status helps to build trust with users. When users know that you are transparent about your affiliations, they are more likely to trust the results of the tests, and ensures your credibility as a person and should reduce or remove future claims of bias made by people; This is especially influential for a website that is designed to help users protect their privacy.
Finally, the disclosure of your employment status is simply good practice. It is standard practice for websites to disclose any potential conflicts of interest, and I believe that the privacytests.org website should follow this practice as well. This appears in many forms of different products, news, etc.; take the Washington Post which discloses that it is owned by Jeff Bezos, but doesn't endorse or hold the view of Amazon.
I do use this website for helping family members pick a browser that has either what they are looking for, or just the right mix of privacy and features; I myself should state that in no way am I trying to undermine the website as I find it an indispensable and trustworthy site for people who want a quick glance of what their browser does, doesn't do, etc. and only want to see the website get better.

Hi @SocietasEvanescentes -- many thanks for your reply. I completely agree with all your points about the benefits of disclosure. Those benefits are indeed why I included the disclosure on the "about" page.
I also take your point that the disclosure is currently a little hard to find. I will think about how to make it more prominent; I like your latest suggestions.
I truly appreciate the feedback! I will leave this ticket open until I have come up with a solution.


addFrame with is_imageData=true makes Chrome hang up

I'm now try separating jsgif process to Web Worker. This needs to pass the image data, not the whole of context.
So I used addFrame(ctx.getImageData(0,0,100,100), true) but this makes Chrome hang... Can you confirm this issue?
Thanks in advance.

+1 me too

It looks like there’s a typo of sizeSet (accidentally written as sizeset) in the addFrame function


Can switch normal scene <-> path traced scene?

I try my question but something weird
canvas1 -> A WebGLRenderer
canvas2 -> B WebGLRenderer with cloned scene of canvas1
A & B WebGLRenderer is different instance and has own canvas element
first time of canvas1 -> 2 goes good also 2->1(because 2 -> just switch canvas 2 to 1 and reset & dispose about pathtracer
and then canvas 2 -> 1's do looks weird. number of Samples go up but nearly enhance it's quality

Sorry it's not clear what issue you're running in to. Can you make a live example like a JSFiddle showing the problem?


makes youtube lag and load very slow

i believe youtube is trying to patch this and that is what is causing the lag

Revert to v8 for now...
Mark as solution if this helps :)

Update to 2.4 here https://github.com/TheRealJoelmatic/RemoveAdblockThing/raw/main/Youtube-Ad-blocker-Reminder-Remover.user.js it should fix the issue

Update to 2.4 here https://github.com/TheRealJoelmatic/RemoveAdblockThing/raw/main/Youtube-Ad-blocker-Reminder-Remover.user.js it should fix the issue

ok thanks


Token importation not working

Following the installation guide I ran (with python 3.6.7) :
python3 Discline.py --store-token
I'm getting this error :
Traceback (most recent call last):
  File "Discline.py", line 27, in <module>
    from client.serverlog import ServerLog
  File "/home/Discline/client/serverlog.py", line 1, in <module>
    from discord import Server, Channel
ImportError: cannot import name 'Server'

Are you on python 3.7? If so, use 3.6 or older and try again

Also getting this error in Python 3.7

I'm also getting this issue.

Also getting this error in Python 3.7

python 3.7 won't work. That being said, I'm using 3.6 and getting the same error as Beau

Well, I got it to work, but I had to downgrade a few packages quite a bit:
sudo python3.6 -m pip install async_timeout==2.0.1 aiohttp==1.0.0 discord==0.16.12

Let me know if there's any way to get this working with newer versions of these.

I got this error too.

Any update on the issue?


Shell-unsafe characters in .netrc file are not escaped

Originally reported as https://github.com/gondor/docker-volume-netshare/issues/18:

If I have a password with characters such as $ or % in my .netrc file, docker-volume-netshare does not correctly provide the password to mount.cifs command. I've found that I need to backslash-escape the characters in the .netrc file so that they are safe in the mount command.

docker-volume-netshare uses netrc, and the author responded:

Do you mind filing this with the maintainer of the netrc library? If they are inactive about fixing this I will bring in something else or write our own. Let me know.

I think this can be closed now as #6 was merged :)


iOS

Might be a simple question, but I haven't found this anywhere. Does this work both on Android and iOS? thanks!

Hey @dimitri320,
Yes, it works on both platforms!


This shouldn't be hardcoded, thanks Keenan...

It's from https://github.com/ManageIQ/manageiq/pull/18106#discussion_r229737376.
Mea maxima culpa.

@miq-bot add_label hammer/yes

Hammer backport details:
$ git log -1
commit d615be12f24d8ba641f00f87938e3680f320a9fc
Author: Keenan Brock<EMAIL_ADDRESS>Date:   Wed Oct 31 16:41:22 2018 -0400

    Merge pull request #18153 from d-m-u/fixing_hardcoded_admin_in_retirement_mixin

    This shouldn't be hardcoded, thanks Keenan...

    (cherry picked from commit 89adf4149f5759b06028a6ee0ad7dc270986e12e)


Verify no ADAL dependencies

Verify if ADAL is in use via some out-of-date dependency outside SDK.  That is, we recently switched to ADAL in SDK auth code.  But it's possible that some other SDK dependency is bringing it in and needs to be updated.

Hi @tracyboehrer,
The only reference left to ADAL is in Microsoft.Bot.Connector. It's being used by Microsoft.Azure.Services.AppAuthentication package.
We marked all the methods and classes as deprecated in PR#6605 but didn't remove them to avoid breaking changes.
Unfortunately, Microsoft.Azure.Services.AppAuthentication package's latest version is still using this dependency, so updating it won't solve the problem.
Should we assume the breaking changes and completely remove ADAL?

Adding more information to keep it on the radar.
The Bot.Connector classes using references to ADAL are the following:

AdalAuthenticator (Used in the other classes obsolete methods)
CertificateAppCredentials (Obsolete methods)
MicrosoftAppCredentials (Obsolete methods)
JwtTokenProviderFactory (Obsolete class)
ConstantHttpClientFactory (Internal class)

We can't remove them because it will represent a breaking change.

Hi @tracyboehrer ,
Do you have any suggestions about this?
I got a Component Governance Alert for the dependencies for Microsoft.IdentityModel.Clients.ActiveDirectory.
I need to fix it ASAP.
Thanks a lot.

Hi @tracyboehrer and @ceciliaavila ,
Are there any updates on this? We are also seeing component governance bugs for ADAL dependency which is going to start breaking out production builds soon if not fixed and we can not fix this ourselves as its transient dependency coming just from Microsoft.Bot.Builder 4.20.1 which is the latest version of bot builder package.
Nilay

@wshxj123 & @mit2nil  What is the root dependency of the alerts?

@wshxj123 & @mit2nil What is the root dependency of the alerts?

I pinged you on Teams just now.
The root dependency is Microsoft.IdentityModel.Clients.ActiveDirectory.
I will try to upgrade the SDKs when the new release is ready.

Code merge with https://github.com/microsoft/botbuilder-dotnet/pull/6687


feat(meta): support drop creating materialized views for v2 backend

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Closes #14471
Notify catalog to fe in the following places:

[x] start create ddl (all ddl catalog)
[x] start create ddl (all internal tables)
[x] Cancel for all ddls.
[x] Delete for all ddls.
[x] Clean dirty jobs.
[x] Change add to update for finish jobs.

Similar to https://github.com/risingwavelabs/risingwave/pull/17484. See that PR's description for further details.
Main difference between v1 and v2 is that in v2 we report all catalogs to fe. Because all catalogs are immediately committed.
But we don't do the same for v1 yet, since for v1, only MVs' catalogs are immediately committed.

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Bump

Bump


Update build and license notices

Pull request to resolve #5
Submitted by: zanerock
Instructions
Review all code changes. Verify the submitter attestations belowe, checking off each statement to indicate that you have reviewed the statement and it is true to the best of your knowledge. If you do not agree with or are unsure of a statement, then add a comment describing your questions or concerns and contact the submitter @zanerock for clarification.
QA files

Lint record
Unit test record

Submitter attestations
To be verified by reviewer.

Do the changes implement all concrete TODOs in the change ticket? y (CHANGES_IMPLEMENT_ALL_TODOS=true)
Are there other changes not described in the original work description? n (CHANGES_HAS_ADDITIONAL_CHANGES=false)
Are there any QA exceptions which need to be addressed? n (CHANGES_HAS_QA_EXCEPTIONS=false)
Do the changes add or involve connections, authentication, or queries to a database or any third-party service? n (CHANGES_THIRD_PARTY_SERVICES_MODIFIED=false)
Has all debug, hard coded test data, and hard coded authentication data been removed? y (CHANGES_DEBUG_REMOVED=true)
[ ] I have reviewed and verified the above are true to the best of my knowledge.

QA links broken.


Feature request: option to configure a AWS_PROFILE in the provider config

what?
The commonfate terraform provider uses the AWS credentials to get access to the commonfate API.
But does not allow to pass a profile to use, like AWS_PROFILE=....
Ideally, the provider should support a config profile = similar to the aws provider itself https://registry.terraform.io/providers/hashicorp/aws/latest/docs#profile
workaround
the workaround is to set the env var AWS_PROFILE=... before calling terraform
But cons:

this might interfere with other tools/providers.
you cannot have multiple aliased providers of commonfate pointing to different AWS accounts in the same project

Also, support for assume-role


AppImage crashes with segmentation fault

Describe the bug
Hi, I have recently met this issue when trying to run the client's AppImage on my computer. Whenever it launches, it crashes and throwing an error
[1]    <process id> segmentation fault (core dumped)
To Reproduce
Whenever launch it with files manager or terminal, it still crashes.
Expected behavior
I just expected it to launch and work normally.
Screenshots
It crashes and left nothing to capture.
Desktop (please complete the following information):

OS: openSUSE Tumbleweed

Additional context
Note: I don't know why this issue happens only with me, other people with the same distro with me still using it normally. The manager one still working fine for me.

Hey there, sorry you're running into this issue.  Did you build the client yourself or is it our production binary?  Have you tried building yourself and seeing if it works?

I tried both latest version and pre-release of binary. I don't have much time to build it myself but I will try to do so and report as sooon as possible.

Interesting, sorry this has been an issue.  Shooting in the dark, do you know what libc and POSIX toolset you're using?  I did a few quick Google searches to see what could cause a segfault from an electron app and a few people reported some issues with their glibc versions being the culprit (https://github.com/electron/electron/issues/13972 for example)

I searched about how electron struggle up with glibc and yes, my distro has the latest version of glibc 2.31 so things struggled up right here

So far I can't force my package manager to downgrade glibc, also dmesg printed these two lines:
[ +20.048764] outline-client[10366]: segfault at 0 ip<PHONE_NUMBER>01e754 sp 00007fff686641a0 error 4 in outline-client[559614e3b000+53ac000]
[  +0.000007] Code: 41 54 53 48 83 ec 48 49 89 f7 49 89 fe 48 8d 35 ea 12 69 fd 48 8d 7d c0 e8 39 cf d5 ff bf 70 00 00 00 e8 2f a7 db ff 49 89 c4 <41> 8b 06 89 45 d4 41 c7 06 00 00 00 00 4c 8b 6d c0 4d 85 ed 74 06

And sorry, POSIX is a new thing to me then.

interestingly, I saw the initialisation UI at first launch as the terminal output indicates the program is checking update and generating uid, then it crashed with segfault. Further attempts always crash instantly even if I clear the ~/.config/Outline Manager/ directory. Are there some config data store in somewhere else?

Considering all distros are working fine with the client, I'm going to close this issue, feel free to reopen this if the issue is still happening on your system!

Considering all distros are working fine with the client, I'm going to close this issue, feel free to reopen this if the issue is still happening on your system!

I have same problem on ubuntu 2020.04

I have same problem on ubuntu 2020.04

@alonek1 is this still occurring on the latest version of the Outline Client?


Destroying all resources fails because of the ARM template deployments

When running terraform destroy we get an error because some of the sample data is deployed with an ARM script. When destroying that resource, only the reference to the deployment is destroyed and not the resources themselves. As one of the deployed resources has a reference to a resource that is not in the ARM script, destroying currently fails.
It's probably a good idea to work on adding these resources to the official Terraform azurerm provider so that we don't have to use the ARM script anymore.

We could probably do something like this: https://medium.com/@charotamine/terraform-azure-terraform-destroy-6bc0151fe0bd


19.00-git-201710092120 is showing update notice from 18.40-18.49

When i press the i button

it will show this information

The only thing i did was to update to Webmin 1.860.

That's not a problem. When Webmin was installed it kept some files from previous install, while shipping old version of the theme.
We'll ship the new one as soon as it's fully tested. You can go to settings and upgrade to the latest 19.00 version.

I also need to do two refresh to get your theme visible after the Webmin update...

It's browser's cache. No issue here.


use semver.lt instead of semver.gt in install-npm

Fixes https://github.com/workshopper/how-to-npm/issues/115
Refs https://github.com/npm/node-semver#usage

opps, it looks right logic then...


Problems with MvcSiteMapProvider_AttributesToIgnore

I'm not sure if this has been asked yet. I couldn't find anything.
Anyhow, I have two custom attributes that I am using in my sitemap:
     <add key="MvcSiteMapProvider_AttributesToIgnore" value="featuredLinkLocation" />     <add key="MvcSiteMapProvider_AttributesToIgnore" value="featuredLinkText" />
My site uses Areas heavily (I'm not sure that matters though). For the links that utilize these attributes the featuredLinkLocation is hidden as expected, however the featuredLinkText is still defined as a route perameter. In my view model the links are displayed using the typical:
 @Html.DisplayFor(m => child)
A node that uses these attributes is:
    <mvcSiteMapNode title="About Us" area="About" controller="Home" action="Index" featuredLinkLocation="About" featuredLinkText="Learn about Chemical Bank" >
and the link produced by the above node is: /About/Home?featuredLinkLocation=About
I can't find anything that I've done to explain why this route value is being displayed. From the above can you see anything that I've done wrong?
Thank you so much for your help!
Eric

You just need to define both attributes in the same (singular) MvcSiteMapProvider_AttributesToIgnore element, separated by commas.
<add key="MvcSiteMapProvider_AttributesToIgnore" value="featuredLinkLocation,featuredLinkText" />

Ahh, thank you so much. Sorry for such a rookie mistake.

REMARK: if you are using an external DI container, instead of using an appSetting, you should configure this during the DI container configuration, as explained here:

If using an external DI container, this setting can be found on the constructor of the ReservedAttributeNameProvider in a parameter named "attributesToIgnore", which is type IEnumerable<string>.


Reimplement nether portal breaking sound

Currently when destroyed through several means, the portal just silently stops existing, rather than the characteristic shatter produced by vanilla's nether portal blocks.
Perhaps this sound event could be a separate thing from a "block breaking" sound so it can be customized independently by resource packs to create an independent "portal shutdown/failure" sound, while still pointing to vanilla glass breaking sound files by default.

It's being considered


A user is unable to fold the code in the editor using keyboard

.NET Online REPL  is having the following accessibility issue.  Please see this issue . I have also included the details below

Environment Details
https://docs.microsoft.com/en-us/dotnet/csharp/quick-starts/hello-world?tutorial-step=4User
Browser: Edge (41.16299.402.0)
Chrome (67.0.3396.87)
Additional Details:
MAS Violated: MAS2.1.1
Repro steps:
Hit the URL https://docs.microsoft.com/en-us/dotnet/csharp/quick-starts/hello-world?tutorial-step=4User
Tab till “Enter focus mode” and press enter
Write a Sample program
Now press F1 and tab till Fold and press enter
Verify Fold action is getting performed or not.
Actual Result:
A user is unable to fold the code in the editor using keyboard
Expected Result:
A user should be able to fold the code using either shortcut or navigating to Fold in command Palette
User Impact:
A disabled user wouldn't be able to avail the functionality.
MAS Reference:
https://microsoft.sharepoint.com/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={8492c4eb-c179-40ae-8777-cd044ed725a2}
A User is unable to fold the code in the editor.pptx

This functionality is actually now present for keyboard users. Upon entering the code editor, the screen reader (NVDA and Narrator) announces to press Alt+F1 for accessibility options. That leads to lots of accessibility help including how to open the Command Palette (F1 in Chrome/Edge and Alt+F1 in IE). In the command palette there many several keyboard shortcuts for folding and unfolding.

I think this ticket needs to be closed.


Any progress in supporting promise/async handler? Please!

Any progress in supporting promise/async handler? Please!
I've viewed many post, PR related to this topic, but what is the progress?
https://github.com/pillarjs/router/pull/32
https://github.com/pillarjs/router/pull/26
https://github.com/pillarjs/router/pull/25
https://github.com/expressjs/express/pull/2763

I don't believe anything has changed, but I'll bring it up in our next meeting. Perhaps we can get something prepared in the router project.

Did this get resolved?  Is Async now supported?


Implement sendReaction Method

https://core.telegram.org/method/messages.sendReaction
Allows bots to react to messages, useful to display that the bot understood a message and did something with it
Just checked, not yet available in official bot api:
https://github.com/tdlib/telegram-bot-api/issues/260

It's already in bot api
https://core.telegram.org/bots/api#setmessagereaction
Any plans on getting this available?

Implemented in #641


UI: decrease api request frequency

@gregjhogan does this get us outside the rate limit? It's not great that the prime widget won't be as responsive, but maybe we should athena write that.

We do have the billing server call an athena endpoint now, so we could use that to trigger a widget update somehow.


analyzer: The revision in VCS processed may be wrong for NPM packages

Reproduce

Create an empty directory and add the below package.json

{
    "name": "@some/test",
    "version": "1.0.0",
    "description": "a",
    "repository": "https://github.com/a/b",
    "license": "MIT",
    "dependencies": {
      "@babel/plugin-proposal-nullish-coalescing-operator": "7.8.3"
    }
  }

Generate the corresponding lockfile: npm i --package-lock-only
Analyze the directory with latest ORT
find master as revision in the analyzer result under vcsProcessed

         - metadata:
        id: "NPM:@babel:plugin-proposal-nullish-coalescing-operator:7.8.3"
        purl<EMAIL_ADDRESS>        declared_licenses:
        - "MIT"
        declared_licenses_processed:
          spdx_expression: "MIT"
        description: "Remove nullish coalescing operator"
        homepage_url: "https://babel.dev/docs/en/next/babel-plugin-proposal-nullish-coalescing-operator"
        binary_artifact:
          url: ""
          hash:
            value: ""
            algorithm: ""
        source_artifact:
          url<EMAIL_ADDRESS>          hash:
            value: "e4572253fdeed65cddeecfdab3f928afeb2fd5d2"
            algorithm: "SHA-1"
        vcs:
          type: "Git"
          url: "https://github.com/babel/babel/tree/master/packages/babel-plugin-proposal-nullish-coalescing-operator"
          revision: "a7620bd266ae1345975767bbc7abf09034437017"
          path: ""
        vcs_processed:
          type: "Git"
          url: "https://github.com/babel/babel.git"
          revision: "a7620bd266ae1345975767bbc7abf09034437017"
          path: "packages/babel-plugin-proposal-nullish-coalescing-operator"
      curations: []
    - metadata:
        id: "NPM:@babel:plugin-syntax-nullish-coalescing-operator:7.8.3"
        purl<EMAIL_ADDRESS>        declared_licenses:
        - "MIT"
        declared_licenses_processed:
          spdx_expression: "MIT"
        description: "Allow parsing of the nullish-coalescing operator"
        homepage_url: ""
        binary_artifact:
          url: ""
          hash:
            value: ""
            algorithm: ""
        source_artifact:
          url<EMAIL_ADDRESS>          hash:
            value: "167ed70368886081f74b5c36c65a88c03b66d1a9"
            algorithm: "SHA-1"
        vcs:
          type: "Git"
          url: "https://github.com/babel/babel/tree/master/packages/babel-plugin-syntax-nullish-coalescing-operator"
          revision: ""
          path: ""
        vcs_processed:
          type: "Git"
          url: "https://github.com/babel/babel.git"
          revision: "master"
          path: "packages/babel-plugin-syntax-nullish-coalescing-operator"

Compare the package.json files

{
  "name": "@babel/plugin-proposal-nullish-coalescing-operator",
  "version": "7.8.3",
  "description": "Remove nullish coalescing operator",
  "repository": "https://github.com/babel/babel/tree/master/packages/babel-plugin-proposal-nullish-coalescing-operator",
  "license": "MIT",
  "publishConfig": {
    "access": "public"
  },
  "main": "lib/index.js",
  "keywords": [
    "babel-plugin"
  ],
  "dependencies": {
    "@babel/helper-plugin-utils": "^7.8.3",
    "@babel/plugin-syntax-nullish-coalescing-operator": "^7.8.0"
  },
  "peerDependencies": {
    "@babel/core": "^7.0.0-0"
  },
  "devDependencies": {
    "@babel/core": "^7.8.3",
    "@babel/helper-plugin-test-runner": "^7.8.3"
  },
  "gitHead": "a7620bd266ae1345975767bbc7abf09034437017"
}

{
  "name": "@babel/plugin-syntax-nullish-coalescing-operator",
  "version": "7.8.3",
  "description": "Allow parsing of the nullish-coalescing operator",
  "repository": "https://github.com/babel/babel/tree/master/packages/babel-plugin-syntax-nullish-coalescing-operator",
  "license": "MIT",
  "publishConfig": {
    "access": "public"
  },
  "main": "lib/index.js",
  "keywords": [
    "babel-plugin"
  ],
  "dependencies": {
    "@babel/helper-plugin-utils": "^7.8.0"
  },
  "peerDependencies": {
    "@babel/core": "^7.0.0-0"
  },
  "devDependencies": {
    "@babel/core": "^7.8.0"
  }
}

Expected
The package plugin-syntax-nullish-coalescing-operator lacks the revision in its metadata.
The URL is master because it is derived from the repository URL.
Should we say repository URL is wrong but the behavior is correct?
@bennati can you double check please if this issue really just popped up of if it existed already for a while?

Hi Frank, I backtraced the ORT version in which the revision is correctly detected in the package.json. The revision is 88d1633e2e

@fviernau could you maybe invest some time to check whether this issue is still present?


Warning: Failed to download action 'https://api.github.com/repos/microsoft/powerplatform-actions/zipball/0c80aacb61f9bfdcb930b880febc420ec4ef2f3e'. Error: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.

I have started seeing this error repeatedly over the past several days across a number of my workflow calls into this repo:
Warning: Failed to download action 'https://api.github.com/repos/microsoft/powerplatform-actions/zipball/0c80aacb61f9bfdcb930b880febc420ec4ef2f3e'. Error: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.
and then it repeatedly fails before erroring out my entire workflow run.  Sometimes the retry succeeds, but other times it continues to fail.  The other actions from external repos (actions/checkout, some internal ones i have in my customer's org, etc.) all seem to be working just fine.
I am using v0 (e.g. - uses: microsoft/powerplatform-actions/import-data@v0   )

I've seen this issue occur intermittently in one of our own workflows.   It usually would fail less than once a day, but that's been increasing lately.
The failure itself occurs during the "Set up job" step, which is an autogenerated step created by GitHub Actions itself

so there's nothing apparent that we can do to affect that ourselves.
I've opened up a support ticket with GitHub to see if they will assist.

This makes sense.  I had opened a ticket here because it seems to only happen when I call actions from this repo.  Other actions (from other repos) don't seem to have this same issue.

It is happening to me as well.
Just when using
repos/microsoft/powerplatform-actions

No word back from GitHub support on the ticket since Friday.
Our current hypothesis is that this has been occurring more frequently due to the steady size increase of our action's tarball/zipball, as each version of PAC is larger than the last, and those are checked in via git-lfs into the repo.   Reducing the size of that should lead to fewer timeouts, which might just occur during periods when GitHub has higher server load?
#424 is an option to do just that - remove PAC from the repo and install via Nuget at action execution time.   If we go this route, it will be a breaking change with a major version bump, as all Jobs would need a new install step.

Correct.
New releases would have their version numbers in the v1.X.Y range instead of the current v0.X.Y, the tag v0 would point to the last v0.X.Y release, and the tags v1 and latest would point to the most recent v1.X.Y release.

@tehcrashxor
Thank you for looking into this issue. My organization's applications rely on these actions for deployment, and we are concerned that our production rollouts will be unstable until this issue is resolved. One of our deployments this week failed 4 times over the course of 2.5 hours before succeeding on the 5th try. I don't have any additional information to add, but I am adding this comment in case it helps the teams prioritize this higher.

Our current plan is to release new version next week.

We heard back from GitHub on our support ticket - they're still looking into why the download speed within the Set up job step drops so drastically, but recommended what we're already doing via #424 by reducing the size of tarball/zipball downloaded by the actions runner.
Preliminary findings from that tinkering is that the tarball's size has been cut from 53 MB down to 5.2 MB, and the Set up job step usually takes 10 seconds or less.  However I've seen at a couple of runs which have taken closer to 3 minutes, triggering the 100 second timeout, but succeeding on the retry before failing the entire job.   Hopefully GitHub will be able to resolve that download issue entirely, but at the very least this should reduce the number of job failures.

Do you need the LFS files in your archive?

Yep, the Node code is just a thin shim to read the parameters passed in the users YAML to the binaries stored in LFS.
Even with our plans for the upcoming version switching to downloading those from Nuget first instead of storing the LFS, we can't disable the LFS archive inclusion as that would break all previous versions of our Actions.

Released new version as v1.0.0, which should alleviate most of the "Set up job" failures as the tarball/zipball is significantly smaller.
As noted in the release notes, this pipelines upgrading to the new version will need both to update the @v0 version specifier to @v1, and will need the actions-install step added prior to any other of our actions to handle grabbing PAC from nuget.org at runtime.

No word back from GitHub support on the ticket since Friday.
Our current hypothesis is that this has been occurring more frequently due to the steady size increase of our action's tarball/zipball, as each version of PAC is larger than the last, and those are checked in via git-lfs into the repo. Reducing the size of that should lead to fewer timeouts, which might just occur during periods when GitHub has higher server load?
#424 is an option to do just that - remove PAC from the repo and install via Nuget at action execution time. If we go this route, it will be a breaking change with a major version bump, as all Jobs would need a new install step.

HI, this method won't work for my clients. Many large and highly regulated company do not allow direct access to nuget. Their runners are behind firewalls and security won't open access to nuget given the risk. So they would be stuck using v0 and with this timeout issue.
Can you look at Github reply on this: https://github.com/microsoft/powerplatform-actions/issues/416#issuecomment-1686151576 and see if that's a possible fix long term? Since many of my client's production deployment is heavily impacted.
Also consider not going through the nuget route.

Some highly regulated companies use self hosted GitHub runners.

I'm seeing these timeout error more often than I'm not seeing them. I've moved to v1

Our monitoring job showed a fair number of v1 timeouts over Sunday and Monday, but it's still failing significantly less often for us than the v0 runs.  We've updated our GitHub support ticket with that info, and we know of at least one large customer that has their own opened as well to investigate the timeouts, but haven't had anything further from GitHub yet.

HI, this method won't work for my clients. Many large and highly regulated company do not allow direct access to nuget hence grabbing Nuget on runtime would be a deadend for them.

We're looking into updating the actions-install step to support taking the package from either internal feeds or directly from a .nupkg file already on the box, so that such customers can obtain the package and provide it on the build agent / action runner without a direct call to nuget.org
Obtaining PAC another way and installing into the expected location that actions-install/index.ts uses and setting an environment variable named POWERPLATFORMTOOLS_PACINSTALLED to true is sufficient to get the other v1 actions running without our own actions-install step, though is a bit hacky and shouldn't be necessary after we update the install step.

We have a monitoring job that runs every hour, which runs four jobs to check that the actions are downloading and running on the agent correctly.  These jobs are two v0 who-am-i jobs (one Windows, one Ubuntu), and another two jobs consisting of v1 actions-install followed by who-am-i (also one Windows, one Ubuntu.
In the last week, we've only seen a single failure of one v0 job failing, so it looks like the process is working better now.
GitHub Support suggests that this resolved incident https://www.githubstatus.com/incidents/frdfpnnt85s8 was likely a fix for the download slowness and failure, but we're not 100% convinced as it was Resolved on September 5th, but there were a series of failures after that on September 8th through September 10th.

GitHub Support elaborated that the incident marked Resolved on Sept 5th wasn't fully remediated until Sept 10th, explaining the failures we saw from the 8th - 10th.
As we've only had a single failure in the monitoring job for the last week, it looks like they may well have fixed the issue.  We'll monitor for further failures and reopen this issue and our GitHub Support Ticket if we see it start to fail again.


Grapheditor example: sidebar.js has incomplete description for some shapes

Version: 3.9.6
The shapes "Ellipse", "Circle", "Triangle" and "Diamond" from the "General"-palette appear as rectangles.
The reason is an incomplete description in sidebar.js in lines 929, 931, 933 and 936:

this.createVertexTemplateEntry('shape=...

The bold descriptor should be added in each line.

These are defined in styles/default.xml, are you loading that file?


Defi App

Project title
A decentralised Finance Buy me a coffee dApp
Project Description
(Describe the project over here)
Buy me a coffee is found on various websites but you need a credit card for doing it. The idea is to take it on the blockchain and ease the effort
Domain

[x] Solidity
[x] JavaScript

Are you contributing under any open-source program ?
SSOC22

// @Vikash-8090-Yadav Pls get me assigned :)

ok so I just found that there is a smart contract already https://github.com/Vikash-8090-Yadav/Solidity-Pathshala/pull/30 merged
So should i work on frontend and then integrating it with the contract ?

Open new issue in the web3.0-world repo ..

@legendarykamal  close this issue

OK


Optimization when doing many Adlibs

What kind of change does this PR introduce?
This PR adds an optimization for the situation where many adlibs are played while staying in one part.
This is fixed by adding a filter in Core that removes old-and-stopped-adlibs after a while, making calculations and timeline to run faster.
What is the current behavior?
System slows down to a crawl after 15-30 adlibs (we experienced this when cutting between cameras)
What is the new behavior?
Adds the property "definitelyEnded" to pieces to allow for efficient trimming of pieces that no longer need to be evaluated to calculate the current state, increasing performance.

@nytamin I think this PR should also contain https://github.com/olzzon/tv-automation-server-core/commit/786d478ac96a49cba22673853430d45d2a0e2c14

@nytamin Also, I think olzzon@9cc4abcb3ffff8ac787371d49a0c585552ac4598 should be included here as well.


Partially incorrect data for how to reach Diagnostics Settings pane

While you can get to Diagnostics Settings pane via the Diagnostics logs pane, this is only true for the first time/when Diagnostics are not yet configured.
If you, like me, enabled diagnostics and then wanted to update settings.... You will not be able to find the Diagnostic Settings pane again. Turns out its hiding under the Metrics pane, you will find a Diagnostics Settings button there.

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

ID: e5f080ad-843f-d7be-eba6-2837993d052b
Version Independent ID: b6f75acf-e3ed-f6c3-a29e-8f440eb0a9dd
Content: Monitor access logs, performance logs, back-end health, and metrics for Application Gateway
Content Source: articles/application-gateway/application-gateway-diagnostics.md
Service: application-gateway
GitHub Login: @amitsriva
Microsoft Alias: amitsriva

@iyerusad
Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.


Migration for Dynamic Memory Demand Pressure

11/08/2018 15:41:22 : [INFO ] ~~~~~TEST END : DYNAMIC-MEMORY-DEMAND-PRESSURE
11/08/2018 15:41:22 : [INFO ] CURRENT - PASS    - 1
11/08/2018 15:41:22 : [INFO ] CURRENT - FAIL    - 0
11/08/2018 15:41:22 : [INFO ] CURRENT - ABORTED - 0
11/08/2018 15:41:22 : [INFO ] Job77 is running.
11/08/2018 15:41:23 : [INFO ] Checking background cleanup jobs..
11/08/2018 15:41:23 : [INFO ] Removed 0 context files.
11/08/2018 15:41:23 : [INFO ] Cycle Finished.. TC-33539

Another two test cases (DYNAMIC-MEMORY-MAX-MEMORY-HONORED and DYNAMIC-MEMORY-MIN-MEMORY-HONORED) are added to the PR.
11/11/2018 21:24:49 : [INFO ] ~~~~~TEST END : DYNAMIC-MEMORY-MIN-MEMORY-HONORED
11/11/2018 21:24:49 : [INFO ] CURRENT - PASS    - 2
11/11/2018 21:24:49 : [INFO ] CURRENT - FAIL    - 0
11/11/2018 21:24:49 : [INFO ] CURRENT - ABORTED - 0
11/11/2018 21:24:49 : [INFO ] Checking background cleanup jobs..
11/11/2018 21:24:49 : [INFO ] Removed 0 context files.
11/11/2018 21:24:49 : [INFO ] Cycle Finished.. TC-76833
11/11/2018 21:24:49 : [INFO ]
Test Results Summary
ICA test run on 11/11/2018 21:03:36
VHD under test Centos_7.5_x64.vhd
ARM Image under test  :  :  :
Total Executed TestCases        2 (       2 Pass,        0 Fail,        0 Abort)
Total Execution Time(dd:hh:mm) 0:0:21
XML file: TestConfiguration
#Sr. Test Name : Test Result : Test Duration (in minutes)

DYNAMIC-MEMORY-MAX-MEMORY-HONORED : PASS : 14.59
DYNAMIC-MEMORY-MIN-MEMORY-HONORED : PASS : 6.62

11/16/2018 09:59:35 : [INFO ]
Test Results Summary
ICA test run on 11/16/2018 09:50:27
VHD under test vss_tests.vhd
ARM Image under test  :  :  :
Total Executed TestCases        2 (       2 Pass,        0 Fail,        0 Abort)
Total Execution Time(dd:hh:mm) 0:0:9
XML file: TestConfiguration
#Sr. Test Name : Test Result : Test Duration (in minutes)

DYNAMIC-MEMORY-MIN-MEMORY-HONORED : PASS : 9.09
DYNAMIC-MEMORY-DEMAND-PRESSURE : PASS : 10:25
============================================================================================
Test Results Summary
ICA test run on 11/16/2018 10:11:20
VHD under test vss_tests.vhd
ARM Image under test  :  :  :
Total Executed TestCases        1 (       1 Pass,        0 Fail,        0 Abort)
Total Execution Time(dd:hh:mm) 0:0:33
XML file: TestConfiguration

#Sr. Test Name : Test Result : Test Duration (in minutes)

DYNAMIC-MEMORY-MAX-MEMORY-HONORED : PASS : 33.59
===========================================================================

@mboitei please fix the conflict and I will sync with Adrian to approve this & merge.

@mboitei please fix the conflict and I will sync with Adrian to approve this & merge.

I have resolved the conflict, please merge.


[Feature Request]  Add an extra argument is_duplicated to scatter_sub/* Ops and make the kernel to multi-thread for speedup.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
ubuntu 16.04
TenorFlow installed from (source or binary):
source
TensorFlow version (use command below):
v1.3.0-rc2
Python version:
2.7
Bazel version (if compiling from source):
0.5.2
CUDA/cuDNN version:
8.0/5.1.10
GPU model and memory:
nvidia M40
CPU
32-cores

Describe the problem
I profile the embedding_lookup_sparse on single machine with tfprof, in which i put the params on cpu. So the gather and scatter_sub Op are also put on cpu.
Profiling result shows gather and scatter_sub Op takes so much time, the former takes about 33%, the latter takes about 43%. Making the gather op kernel to multi-thread gain about 10x speedup, relate to PR and 11709.
Follow the same thought, I want to make the scatter_sub to be multi-thread.

If there is no duplicate index, we can realize lock-free code which could gain about 10x speedup too.
If there are duplicate indices, use lock which can gain little speedup.

So, I think an extra argument is_duplicated is a good choice to divide the two situation.
Here is some profiling result:
tfprof
# orignial
ScatterSub                   8589.93MB (65.56%, 32.67%),       45.63ms (62.09%, 43.75%),            0us (45.25%, 0.00%),       45.63ms (62.90%, 45.87%)
# with lock
ScatterSub                   8589.93MB (65.56%, 32.67%),       38.10ms (86.95%, 54.44%),            0us (48.97%, 0.00%),       38.10ms (89.98%, 58.78%)
# without lock
ScatterSub                   8589.93MB (65.56%, 32.67%),        4.22ms (73.05%, 12.58%),            0us (48.86%, 0.00%),        4.22ms (76.99%, 14.63%)

Code
embedding_lookup_sparse

/CC @alextp

Since the indices Tensor is much smaller than the values Tensor I think it's possible to check for duplicates cheaply before doing the multi-threaded code, to make it appropriately lock-free. I'd prefer that over an argument we'd need to plumb across the entire interface.

@alextp Yes, this way just need little change, I got about 2x speedup. If neccessary, I'll send a PR. by the way thanks for your advice.

After some tests, we found another way whose performance is close to the lock-free code. Declare a mutex array with the size equals to the indices size, then use hash to get the mutex and lock every element's update. lock is cheap and contention is expensive.


Add documentation

Documentation will be needed for anyone trying to use the project.
A more extensive README and adding a github wiki is in order for this. Not only something to document the source code itself but getting started with a project using this as a template.

Is there any documentation on this project yet? I want to use this movement system for an idea in a game and recreate midair anime fight. So I wonder if there's going to ever be a guide video or Documentation on how setup this project.


feat: Fixed footerUI , added twitter link

Describe your changes
Made the footer better looking , added twitter link to @EmmaDawsonDev. fixed responsiveness of footer for mobile/Ipads.
Screenshots -

Link to issue
closes #288
Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] Followed the repository's Contributing Guidelines.
[x] I ran the app and tested it locally to verify that it works as expected.
[] I have checked my code with an automatic accessibility tool such as Axe Dev Tools or Wave
and it shows no errors.

@EmmaDawsonDev Makes sense, thanks for the review. Will be posting a mockup soon


Test with Shenango threads

This PR works with https://github.com/saubhik/caladan/pull/8.

Passes RunInThread test but with 2 threads and 3 ops per thread and removing the timeout assertion. TerminateLoopSoon is registered with EventBase but doesn't terminate the loop and instead wait for the timeout event.

Passes RunInEventBaseThreadAndWait test with 4 event bases, otherwise hangs. Maybe because I am testing with 4 kthreads?
With std::threads, I had to reduce 256 event bases to 64 due to user limits on file descriptors in linux.


Correct the link of sswg-security at SECURITY.md

Motivation:
Correct the link of sswg-security at SECURITY.md. Currently it is showing "Not Found".
Modifications:

https://github.com/swift-server/sswg/blob/main/process/incubation.md#security-best-practices => https://www.swift.org/sswg/security/

Result:
Correct the link of sswg-security

Thanks!


Replace video/playlist links to relative website urls instead of Youtube links

Wrote a script to update Coding Train youtube links in the metadata into website links (if that video is present on the website).

Some questions regarding this: (@shiffman)

Pendulum Simulation: https://www.youtube.com/watch?v=9iaEqGOh5WM

Should this be updated to https://thecodingtrain.com/tracks/the-nature-of-code-2/159-simple-pendulum
linked from Double Pendulum

Pixels!: https://www.youtube.com/watch?v=EmtU0eloTlE

Should this be updated to : https://thecodingtrain.com/tracks/p5-tips-and-tricks/more-p5/pixel-array
linked from Photo Mosaic, Langton's Ant, Dithering

Deleting objects with splice: https://www.youtube.com/watch?v=HXOD_XDA-KU

Should this be updated to : https://thecodingtrain.com/tracks/code-programming-with-p5-js/code/7-arrays/5-removing-elements
linked from Evolutionary Steering Behaviors

Trigonometry and Polar Coordinates: https://youtu.be/znOBmOrtz_M

Should this be updated to : https://thecodingtrain.com/tracks/the-nature-of-code-2/noc/3-angles/4-polar-coordinates
linked from: Butterfly Generator

ml5.js: Sound Classification: https://www.youtube.com/watch?v=cO4UP2dX944&list=PLRqwX-V7Uu6YPSwT06y_AEYTqIwbeam3y&index=19

This video is not on the website. Is this intentional?
linked from: Chrome Dino Game

Angles and Angular Motion: https://youtu.be/qMq-zd6hguc

Should this be updated to: https://thecodingtrain.com/tracks/the-nature-of-code-2/noc/3-angles/1-angles-and-rotation
linked from: LOGO interpreter

Very cool!

Amazing!

@shiffman any preference/suggestions for the above questions? https://github.com/CodingTrain/thecodingtrain.com/pull/1097#issuecomment-1575072094

@shiffman any preference/suggestions for the above questions? #1097 (comment)

Oh, sorry I missed those!
I think the answer is yes for linking to the most recent / relevant video on the topic!
Regarding the sound classification video, I think that's just a mistake I can't remember any reason it would not be included!

The sound classification video wasn't in the playlist on the old website and I used that as a guide for what to add.  Should I add it now?  I also think we could add the ml coding challenges to the track as well, correct?

Merging this, thank you for working on it @dipamsen it's amazing!


Turning trails to seed lists view doesn't have line breaks between each seed

should be a trivial fix.

On which browser? Safari?

of course :)

Yeah, so basically safari is refusing to read "\n" characters. I honestly don't know if its worth fixing.

Meh, let's punt to 0.5


Store more shadows per quadrant for 3D point lights

This has several benefits:

Performance increases noticeably, especially when lights with shadows are moving, or when objects move close to point lights that have shadows.
Point light shadows look less sharp and more consistent with directional shadows' default appearance. Previously, point light shadows had a tendency to look overly sharp compared to directional shadows in most scenes.
Up to 16 lights with shadows can be placed in a scene until shadow quality degrades, instead of just 4. It's not always obvious for people why the quality degrades in this case, so it's good to have this happen as late as possible (and ideally never in some projects).

This closes https://github.com/godotengine/godot/issues/61747.
Testing project: test_omni_spot_shadow_performance.zip
Press Space to start/pause the animation.
Preview
OS: Fedora 36
GPU: NVIDIA GeForce GTX 1080
Screen resolution: 2560×1440
The scene has 2 OmniLights with shadows and 1 SpotLight with shadows. Most complex scenes will have more lights with shadows than that, on top of having more complex meshes. This means the real world performance difference is likely greater than what demonstrated here.
Static scene
Since this is a simple scene and the shadow atlas doesn't need to be updated every frame, the performance difference is small.

Before
After

Scene with moving object
The shadow atlas needs to be updated every frame in this scenario, leading to a much more pronounced performance difference.

Before
After

just changing the quadrants to 16 16 64 256 would do, especially as there are up to 512 clustered elements right now. with 128 however, 16 16 64 64 makes more sense, not to mention at too low resolutions the lights (omni especially) turn into a mess, so 64 should be the most a quadrant should have for 4k, or 16 for 2k..

Can you try benchmarking the performance difference when keeping the shadow atlas size to 4096 but tweaking the quadrants as you mentioned?

i3 10105f (4.2 GHz 4c/8t), GTX 1050 Ti, W11
1024x600 (ran a couple of times, consistent output)
2k 4,4,16,64 - ~705/~622 FPS
4k 16,16,64,256 - ~750/~645 FPS
1920x1080 (ran once)
2k 4,4,16,64 - ~239/~230 FPS
4k 16,16,64,256 - ~240/~230 FPS
This first result surprised me a little, I didn't expect more FPS from the higher resolution with more quadrants (for same effective shadow resolution) but my guess is that having shadows in different quadrants is slightly less efficient, and it's unclear what the bottleneck is, as the GPU is running at 60% and CPU is using like 7-8% during the test in the 1st scenario

This first result surprised me a little, I didn't expect more FPS from the higher resolution with more quadrants (for same effective shadow resolution) but my guess is that having shadows in different quadrants is slightly less efficient, and it's unclear what the bottleneck is, as the GPU is running at 60% and CPU is using like 7-8% during the test in the 1st scenario

If your GPU isn't maxed out then FPS is not a good measure of time it takes to do something on the GPU unfortunately. GPUs do all kinds of throttling, underclocking etc. in order to save power and heat when they are not fully needed. It may be the case that the GPU dedicated more resources to shadow rendering when using the 4K texture because it expected to do more work, while in the 2nd scenario it was already close to max so it didn't change between 2K and 4K.
Overall, are we sure the decrease in quality is worth the performance gain here? To me, the shadows in the "after" images look significantly worse.

That explanation makes sense.. I think the lower resolution look fine, but instead of lowering to 2k, I'd opt for more shadows. 16 16 16 64 or 16 16 64 64 probably makes the most sense, as it gives 12 omni lights or 24 spot lights for the 1st option, and 24 additional omni lights (36 total increase) or 48 spot lights (for 72 total increase) with the second option.
This increase in Lights with shadows would go hand in hand with FCR's main advantage (plenty of lights) out of the box, and the decrease in memory usage with 2k instead of 4k shadow map is just non-existent for even the more memory limited systems, as if like a few dozen megabytes of VRAM make or break the memory budget, you've probably got other things to worry about.
As keeping the resolution wouldn't hurt performance, unless using the added light shadows, I'd go with the extra lights.
Furthermore I agree with the reduction in Default effective Shadow Resolution for general lights, to keep them inline with the appearance of the same resolution of the default Directional Shadows

After doing testing in scenes with dozens of point lights, I can say that decreasing the default point light shadow atlas isn't a good idea – shadows will be very blurry and full of acne. Tweaking the number of lights in each shadow quadrant is still worth a try though.

Redone based on @mrjustaguy's feedback. This benefits framerate just as much (if not more) than the previous solution, while allowing scenes to contain more point lights with shadows before quality degrades.

The point of this feature is quality, not performance. Sure you can get a bit more performance but quality sucks. I think this should be left as-is.

@reduz seems against it and Clay tends to agree. I also find that the quality loss in the provided example isn't justified by a 0.1 ms perf gain.


Removed Twitter feed and moved "Meet the Team" to under the team's pi…

Removed twitter feed from Homepage and moved the meet the team text and link to below the Team's image

We went for a different solution


Error starting Docker image named "engineerbetter/worker-image"

Kindly help out with the possible root cause of the following error.
The rufus scheduler is part of a Docker image that I am trying to run. The said Docker image was pulled locally from https://hub.docker.com/r/engineerbetter/worker-image
$ docker image pull engineerbetter/worker-image
--
$ winpty docker run -it --rm engineerbetter/worker-image bash                                                                                recording status                                                                                { 11997600 rufus-scheduler intercepted an error:                                                                                11997600   job:                                                                                11997600     Rufus::Scheduler::EveryJob "10s" {}                                                                                11997600   error:                                                                                11997600     11997600                                                                                11997600     StorageError                                                                                11997600     No URL set                                                                                11997600       /worker/lib/people_data_service.rb:25:in `rescue in people'                                                                                11997600       /worker/lib/people_data_service.rb:20:in `people'                                                                                11997600       /worker/lib/status_manager.rb:19:in `record_random_status'                                                                                11997600       /worker/lib/app_scheduler.rb:15:in `block in run'                                                                                11997600       /usr/local/bundle/gems/rufus-scheduler-3.3.4/lib/rufus/scheduler/jobs.rb:234:in `do_call'                                                                                11997600       /usr/local/bundle/gems/rufus-scheduler-3.3.4/lib/rufus/scheduler/jobs.rb:278:in `trigger_now'                                                                                11997600       /usr/local/bundle/gems/rufus-scheduler-3.3.4/lib/rufus/scheduler/jobs.rb:320:in `block (3 levels) in start_work_thread'                                                           11997600       /usr/local/bundle/gems/rufus-scheduler-3.3.4/lib/rufus/scheduler/jobs.rb:323:in `block (2 levels) in start_work_thread'                                                           11997600       /usr/local/bundle/gems/rufus-scheduler-3.3.4/lib/rufus/scheduler/jobs.rb:309:in `loop'                                                                                11997600       /usr/local/bundle/gems/rufus-scheduler-3.3.4/lib/rufus/scheduler/jobs.rb:309:in `block in start_work_thread'                                                                      11997600   tz:                                                                                11997600     ENV['TZ']:                                                                                11997600     Time.now: 2019-10-20 20:41:43 +0000                                                                                11997600     local_tzone: #                                                                                11997600   scheduler:                                                                                11997600     object_id: 17793920                                                                                11997600     opts:                                                                                11997600       {}                                                                                11997600       frequency: 0.3                                                                                11997600       scheduler_lock: #                                                                                11997600       trigger_lock: #                                                                                11997600     uptime: 10.227404832839966 (10s227)                                                                                11997600     down?: false                                                                                11997600     threads: 2                                                                                11997600       thread: #                                                                                11997600       thread_key: rufus_scheduler_17793920                                                                                11997600       work_threads: 1                                                                                11997600         active: 1                                                                                11997600         vacant: 0                                                                                11997600         max_work_threads: 28                                                                                11997600       mutexes: {}                                                                                11997600     jobs: 1                                                                                11997600       at_jobs: 0                                                                                11997600       in_jobs: 0                                                                                11997600       every_jobs: 1
--

{ 11997600 rufus-scheduler intercepted an error:
  11997600     Rufus::Scheduler::EveryJob "10s" {}
  11997600   error:
  11997600     StorageError
  11997600     No URL set
  11997600       /worker/lib/people_data_service.rb:25:in `rescue in people'
  11997600       /worker/lib/people_data_service.rb:20:in `people'
  11997600       /worker/lib/status_manager.rb:19:in `record_random_status'
  11997600       /worker/lib/app_scheduler.rb:15:in `block in run'

Hello,
this is not a rufus-scheduler issue. Rufus-scheduler is simply reporting an error in your application. StorageError "No URL set".
I guess (I can only guess) that you've misconfigured your app and forget to set some URL config for your storage. Set that and rufus-scheduler will stop passing the error to you.
Closing the issue as it does not belong here. Rufus-scheduler is merely the messenger.
Best regards.


[Issue][unplugin-imagemin] Plugin is not working

ref : https://github.com/nksaraf/vinxi/issues/44
repro :  https://github.com/qlaffont/test-cmp

> test-cmp@ build /home/quentin/Documents/dev/test/test-cmp
> vinxi build

vinxi 0.0.60
start {
  appRoot: './src',
  ssr: false,
  islands: false,
  server: { base: undefined },
  solid: {}
}
vinxi Found vite.config.js with app config

┌────────────────────────────┐
│ ⚙  Building your app...    │
└────────────────────────────┘
removing /home/quentin/Documents/dev/test/test-cmp/.vinxi/build/ssr
removing /home/quentin/Documents/dev/test/test-cmp/.vinxi/build/client
removing /home/quentin/Documents/dev/test/test-cmp/.vinxi/build/server-fns

┌───────────────────────────────┐
│ 📦 Compiling ssr router...    │
└───────────────────────────────┘
vinxi building router ssr in handler mode
vite v4.5.0 building SSR bundle for production...
"createHandler" is imported from external module "h3" but never used in "node_modules/.pnpm/vinxi@0.0.60_rollup<EMAIL_ADDRESS>✓ 40 modules transformed.
.vinxi/build/ssr/manifest.json                   1.40 kB
.vinxi/build/ssr/assets/index-fb87c914.css      46.63 kB
.vinxi/build/ssr/_...404_.js                     0.74 kB
.vinxi/build/ssr/about.js                        0.96 kB
.vinxi/build/ssr/assets/components-86ea9901.js   1.20 kB
.vinxi/build/ssr/index.js                        3.61 kB
.vinxi/build/ssr/ssr.js                          6.50 kB

[unplugin-imagemin] 📦 📦 Process start with Mode sharp
✓ built in 743ms
✔ build done                                                                                7:01:06 AM

┌──────────────────────────────────┐
│ 📦 Compiling client router...    │
└──────────────────────────────────┘
vinxi building router client in build mode
[
  '#vinxi/handler/client',
  '/home/quentin/Documents/dev/test/test-cmp/src/routes/[...404].tsx?pick=default&pick=$css',
  '/home/quentin/Documents/dev/test/test-cmp/src/routes/about.tsx?pick=default&pick=$css',
  '/home/quentin/Documents/dev/test/test-cmp/src/routes/index.tsx?pick=default&pick=$css'
]
plugin-legacy overrode 'build.target'. You should pass 'targets' as an option to this plugin with the list of legacy browsers to support instead.
vite v4.5.0 building for production...
virtual:#vinxi/handler/client (1:106) "default" is not exported by "src/entry-client.tsx", imported by "virtual:#vinxi/handler/client".
✓ 115 modules transformed.
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[Error: ENOENT: no such file or directory, open '/home/quentin/Documents/dev/test/test-cmp/.vinxi/build/client/_build/assets/_...404_-legacy-ca63b2ec.js'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/home/quentin/Documents/dev/test/test-cmp/.vinxi/build/client/_build/assets/_...404_-legacy-ca63b2ec.js'
}

Node.js v18.17.1
 ELIFECYCLE  Command failed with exit code 1.```

Will take a look!

@saihaj any update ?

@nksaraf any update ?

Haven't been able to give this one time. It could take me a bit longer. @edivados do you think you could help out on this one?

[!NOTE]
The following is just what I observed. I have not invested a lot of time into this so some things may not be accurate.

The image in the example is small and vite will inline it so the plugin doesn't pick it up.
beforeBundle: true seems to work,

In vinxi public files are not handled by vite and the plugin seems to have two issues when publicDir is set to false.
1. outDir does not exist when generateBundle hook runs
When publicDir is set to false the outDir doesn't exist yet and the write here fails.
https://github.com/unplugin/unplugin-imagemin/blob/d0ec2cbf5fd4d312452507f96d5d1a53781f119c/src/core/context.ts#L644
I don't know much about vite/unplugin so I am not sure if writing to disk here is just wrong or it should not rely on the outDir to exist.
2. Plugin relies on publicDir to construct paths?
When publicDir is false it receives/uses an empty string and the paths it builds here don't exist.
https://github.com/unplugin/unplugin-imagemin/blob/d0ec2cbf5fd4d312452507f96d5d1a53781f119c/src/core/sharp.ts#L62-L64

In my opinion the issue is with the plugin because even with publicDir set to false I would expect it to process assets and ignore public files.

Okay so public dir needs to be set to true for this plugin to work. Can we set it in userland for when this plugin is used. Or we dedupe all assets server and client and public and that way we get all the assets

@nksaraf Played around a bit more with it and updated my previous message. See point 3.

Can we set it in userland for when this plugin is used.

A user could do that. I did this while testing. Not sure what issues this could cause with the public router. Maybe you would have to remove it in this case to prevent unprocessed files from being copied.
In my opinion this plugin has two things that should be fixed.

Writing files to disk in generateBundle using fs. I doubt plugins are responsible for writing to disk here if they will be written by the bundler later anyway. Changing the source should be enough I would think.
Not handling publicDir: false. This is a valid setup where you have no public files but eventually static assets.

Or we dedupe all assets server and client and public and that way we get all the assets

If the plugin didn't have the mentioned issues I could also imagine the static router being a vite build too and making something like this eventually possible.
[
    {
        name: "public",
        mode: "static",
        dir: "./public",
        base: "/",
        plugins: [ imagemin ] // no static assets but public files
      },

      {
        name: "ssr",
        plugins: [ imagemin ] // no public files but static assets
      }
]

So what I need to do or did I need to create issue (and where) ? 😅

@qlaffont It's time to get creative for a short term solution. 🤣 This is what I could come up with. I am making use of the fact that the plugin seems to process assets but not public files with beforeBundle: true and later manually use the plugin to process the public files.
import {defineConfig} from "@solidjs/start/config";
import legacy from "@vitejs/plugin-legacy";
import devtools from "solid-devtools/vite";

import imagemin from "unplugin-imagemin/vite";
import { cpSync, rmSync, mkdirSync } from "fs";
import { join } from "vinxi/lib/path";

function createImageminPlugin(beforeBundle) {
  return imagemin({
    mode: 'sharp',
    beforeBundle,
    // Default configuration options for compressing different pictures
    conversion: [
      { from: 'jpeg', to: 'webp' }
    ],
    compress: {
      jpg: {
        quality: 50,
      },
      jpeg: {
        quality: 10,
      },
      png: {
        quality: 70,
      },
      webp: {
        quality: 70,
      },
    },
  });
}

const app = defineConfig({
  start: {
    ssr: true
  },
  plugins: () => [
    legacy({
      targets: ["defaults","not IE 11"],
    }),
    devtools({
      /* features options - all disabled by default */
      autoname: true, // e.g. enable autoname
      locator: true,
    }),
    createImageminPlugin(true),
  ],
});

app.addRouter({
  mode: "static",
  name: "solid-start-cmp",
  dir: "node_modules/solid-start-cmp/public",
  base: "/",
});

let publicFilesHandler;

app.hooks.hook("app:build:nitro:assets:copy:start", ({ nitro }) => {
  // temporarily remove public files handler to prevent nitro from copying files.
  publicFilesHandler = nitro.options.publicAssets.shift();
});

app.hooks.hook("app:build:nitro:assets:copy:end", async ({ nitro }) => {
  // add public files handler back to the top
  nitro.options.publicAssets.unshift(publicFilesHandler);
  const publicBuildDir = join(nitro.options.buildDir, "public");
  rmSync(publicBuildDir, { recursive: true, force: true });
  mkdirSync(publicBuildDir, { recursive: true });
  cpSync("public",  publicBuildDir, { recursive: true, force: true });
  const plugin = createImageminPlugin(false);
  await plugin.configResolved({
    publicDir: "public",
    build: {
      assetsDir: "assets",
      outDir: nitro.options.buildDir,
    }
  });
  await plugin.closeBundle.handler();
  cpSync(publicBuildDir,  nitro.options.output.publicDir, { recursive: true, force: true });
})

export default app;

Thanks @edivados ! I will try to use it. I will link this issue to the other issue : https://github.com/unplugin/unplugin-imagemin/issues/100
@ErKeLost :wave:

Oh interessting I will have to read through it. Maybe using beforeBundle: true doesn't cover some things.

The resources loaded by src in beforeBundle cannot be parsed as a module. I haven't perfected this part yet. I'm sorry I don't have any extra time to maintain this package because of my work.

Ok I see. Thank you.

Can we just fork it and patch it for now and release it under @vinxi namespace .. this image optimizations stuff is probably important enough

I think it will be perfect ! We need to see with 我认为这将是完美的！我们需要看看@ErKeLost

This looks great. I will study whether the current problem can be solved perfectly.


Comparator vs Comparable

Hellooo, as far as I know, comparator is used for sorting in a list? whereas comparable is used for comparing the current object to the other object of the same type.
Can I check for which scenarios we should use comparator and comparable?

nvm, I found the explanations in lecture 2 wiki page


Redesign the interface for creating a new project

This PR redesigned the project setup stage for creating a new project.
Step 1: Fill in project details

Step 2: Providing data

Add dataset from file

Add dataset from URL

Add dataset from benchmark datasets

Add prior knowledge by searching for relevant records or getting a random one

Search for records (empty)

Search for records

Get a random record

Get a random record (reminder after labeling 5 irrelevant records)

Enough prior knowledge to continue the setup

Complete step 2, ready to go to the next step

Step 3: Select model

Finish setup, start training model

Project is ready

Wonderful work! 110/100!


Tweak name/symbol display in Wallet

Refer to https://github.com/AlphaWallet/alpha-wallet-android/issues/2000

@hboon i am trying to resolve this issue. Prepared sample function  but i am not sure if its will works right
func shortTitleInPluralForm(withAssetDefinitionStore assetDefinitionStore: AssetDefinitionStore) -> String {
        let xmlHandler = XMLHandler(token: self, assetDefinitionStore: assetDefinitionStore)

        func _compositeTokenName(fallback: String = "") -> String {
            let localizedNameFromAssetDefinition = xmlHandler.getNameInPluralForm(fallback: fallback)
            return compositeTokenName(forContract: contractAddress, fromContractName: name, localizedNameFromAssetDefinition: localizedNameFromAssetDefinition)
        }

        let localizedNameFromAssetDefinition = _compositeTokenName()
        let symbol = self.symbol(withAssetDefinitionStore: assetDefinitionStore, localizedNameFromAssetDefinition: localizedNameFromAssetDefinition)

        if localizedNameFromAssetDefinition.isEmpty {
            let tokenName = _compositeTokenName(fallback: name)
            if tokenName.isEmpty {
                return symbol
            } else {
                if symbol.count > tokenName.count {
                    return tokenName
                } else {
                    let myStrippedString = tokenName.components(separatedBy: CharacterSet.alphanumerics.inverted).joined(separator: " ")
                    let acronyms = tokenName//myStrippedString.getAcronyms(joinedSeparator: "")
                    if acronyms.isEmpty {
                        return symbol
                    } else {
                        let daiSymbol = "DAI\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}\u{0}"
                        //We could have just trimmed away all trailing \0, but this is faster and safer since only DAI seems to have this problem
                        if daiSymbol == symbol {
                            return "\(acronyms) (DAI)".uppercased()
                        } else {
                            return "\(acronyms) (\(symbol))".uppercased()
                        }
                    }
                }
            }
        } else {
            return localizedNameFromAssetDefinition
        }
    }

not pretty understood these steps:
When picking *1 (long name):

Use TokenScript name if available.
Use Token name if longer than Token symbol.
Use Token symbol.

When picking *2 (short name):

Use shortest of name and symbol, but abbreviate to 5 characters or less and capitalise.

let localizedNameFromAssetDefinition = _compositeTokenName() - here we got name from token script if understand right.
then if its non empty, return it. otherwise get token' name let tokenName = _compositeTokenName(fallback: name) and check it.

Hi @vladyslav-iosdev I think you have the correct understanding. Token pluralisation (which may or may not be defined in the TokenScript file) should be done in the TokenScript engine, check with @hboon.

Yeah, approving since James says it sounds about right :)


[Bug]: LLM Chat does not render messages; displays structured JSON

Details
Occurs with claude 3.5 w/ computer use case
🔎 Describe the Bug

🤝 Contribution

[ ] Yes, I'd be happy to submit a pull request with these changes.
[X] I need some guidance on how to contribute.
[X] I'd prefer the AgentOps team to handle this update.

Does this still occur? @thaddavis


[Firebase Database] DatabaseReference.set() causes an exception on iOS

Steps to Reproduce
After updating firebase_database plugin to to 2.0.1+1 DatabaseReference.set() causes an exception on iOS, on Android it works fine... Before the update I was using an older version of the plugin (firebase_database: ^1.0.5). Now I have downgraded to this version and it works fine on iOS.
Logs
[VERBOSE-2:ui_dart_state.cc(148)] Unhandled Exception: PlatformException(Error 0, null, null)
#0      StandardMethodCodec.decodeEnvelope
#1      MethodChannel.invokeMethod
<asynchronous suspension>
#2      DatabaseReference.set
#3      LoginPageState._saveUserToDatabase.<anonymous closure>.<anonymous closure>
#4      _asyncThenWrapperHelper.<anonymous closure> (dart:async/runtime/libasync_patch.dart:77:64)
#5      _rootRunUnary (dart:async/zone.dart:1132:38)
#6      _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#7      _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#8      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#9      Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#10     Future._complete (dart:async/future_impl.dart:473:7)
#11     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#12     _rootRunUnary (dart:async/zone.dart:1132:38)
#13     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#14     _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#15     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#16     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#17     Future._completeWithValue (dart:async/future_impl.dart:483:5)
#18     Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:513:7)
#19     _rootRun (dart:async/zone.dart:1124:13)
#20     _CustomZone.run (dart:async/zone.dart:1021:19)
#21     _CustomZone.runGuarded (dart:async/zone.dart:923:7)
#22     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
#23     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#24     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)

[✓] Flutter (Channel master, v1.2.3-pre.6, on Mac OS X 10.14.2 18C54, locale en-US)
    • Flutter version 1.2.3-pre.6 at /Users/mt/Documents/flutter
    • Framework revision ea4cffde60 (2 hours ago), 2019-02-22 08:38:02 -0800
    • Engine revision cb0f7ece1f
    • Dart version 2.2.0 (build 2.2.0-dev.2.1 c92d5ca288)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/mt/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = /Users/mt/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.1, Build version 10B61
    • ios-deploy 1.9.4
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 32.0.1
    • Dart plugin version 182.5124
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[✓] VS Code (version 1.31.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 2.23.1

[✓] Connected device (1 available)
    • iPhone de M • bcdfc8d068fb4c41827d8a741f2134c31447cab6 • ios • iOS 12.1.2

This issue was fixed by https://github.com/flutter/plugins/pull/1274. If any related issue is found, please feel free to reopen the issue ticket with more details.

@madtocc
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/421. Any further collaboration will be done there.


Clarify installation requirements for CUDA vs ROCm

See this ONNX Runtime issue for more info:
https://github.com/microsoft/onnxruntime/issues/14821

I see this has been addressed. Closing this.


src: possible to ignore version ranges

Coverage decreased (-1.5%) to 91.736% when pulling 45308b5eed865f4631dbc5d5edadf19fbe8a5c69 on helio-frota:licenser-68 into d0121d07d7b5397aa2047ba779056de6f1ab93e3 on bucharest-gold:master.


[Feature]Be able to load the config file from a remote location

User story
Would like to be able to store the Swagger-Promote config json in a source repository with the API definition.  Swagger-Promote would then provide the remote address to the config file when passing in the -c option.  So, would like our command to look like `./scripts/run-swagger-import.sh -a https://bitbucket/repository/service-swagger.json -c https://bitbucket/repository/service-config.json’.
Additional context
This would allow us to NOT store the config files locally to our CI/CD process that Jenkins is running to accomplish these promotes.

@soaErikNord, reading from a remote location is prepared - as the new CLI is now using distinct Adapters for different formats & sources. One source, could be the use-case you raised internally.
Is this use-case described in this issue still valid and important to you?


[BUG] SQL query doesn't support different date formats without date casting

What is the bug?
Getting below error for user defined date format
"{\n  \"error\": {\n    \"reason\": \"Invalid SQL query\",\n    \"details\": \"date:03-Jan-24 in unsupported format, please use 'yyyy-MM-dd'\",\n    \"type\": \"SemanticCheckException\"\n  },\n  \"status\": 400\n}"

How can one reproduce the bug?
Steps to reproduce the behavior:
PUT testindex
{
  "mappings" : {
    "properties" :  {
      "release_date" : {
        "type" : "date",
        "format" : "dd-MMM-yy"
      }
    }
  }
}

PUT testindex/_doc/21
{
  "release_date" : "03-Jan-24"
}

POST _plugins/_sql
{
"query":"select release_date from testindex where release_date='03-Jan-24'"
}

What is the expected behavior?
Query should work without date casting
What is your host/environment?

OS: [e.g. iOS]
Version [e.g. 22]
Plugins

Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.

We have one more similar issue reported from users when date in timestamp format in the SQL query is erroring out due to  mismatch in the timestamp format between field mapping and the request query -
Sample query:
select count(*) from ami where State = 'available' and  Public = 'true' and CallerVersion = "2016-11-15 00:00:00";

select count(*) from ami where State = 'available' and  Public = 'true' and CallerVersion < "2016-11-15 00:00:00";

Error -
[INFO] 10f0cef3-4159-4c39-84e1-f4ba8b88be97 (Bobcat-29) com.amazonaws.fleetinsightsopensearchcommons.helper.ResponseConvertor: Original SQL response : {
  "error": {
    "reason": "Error occurred in OpenSearch engine: all shards failed",
    "details": "Shard[0]: OpenSearchParseException[failed to parse date field [2016-11-15 00:00:00] with format [strict_date_optional_time||epoch_millis]: [failed to parse date field [2016-11-15 00:00:00] with format [strict_date_optional_time||epoch_millis]]]; nested: IllegalArgumentException[failed to parse date field [2016-11-15 00:00:00] with format [strict_date_optional_time||epoch_millis]]; nested: NotSerializableExceptionWrapper[date_time_parse_exception: Failed to parse with all enclosed parsers];\nShard[1]: OpenSearchParseException[failed to parse date field [2016-11-15 00:00:00] with format [strict_date_optional_time||epoch_millis]: [failed to parse date field [2016-11-15 00:00:00] with format [strict_date_optional_time||epoch_millis]]]; nested: IllegalArgumentException[failed to parse date field [2016-11-15 00:00:00] with format [strict_date_optional_time||epoch_millis]]; nested: NotSerializableExceptionWrapper[date_time_parse_exception: Failed to parse with all enclosed parsers];\nShard[2]: OpenSearchParseException[failed to parse date field [2016-11-15 00:00:00] with format [strict_date_optional_time||epoch_millis]: [failed to parse date field [2016-11-15 00:00:00] with format [strict_date_optional_time||epoch_millis]]]; nested: IllegalArgumentException[failed to parse date field [2016-11-15 00:00:00] with format [strict_date_optional_time||epoch_millis]]; nested: NotSerializableExceptionWrapper[date_time_parse_exception: Failed to parse with all enclosed parsers];\nShard[3]: OpenSearchParseException[failed to parse date field [2016-11-15 00:00:00] with format [strict_date_optional_time||epoch_millis]: [failed to parse date field [2016-11-15 00:00:00] with format [strict_date_optional_time||epoch_millis]]]; nested: IllegalArgumentException[failed to parse date field [2016-11-15 00:00:00] with format [strict_date_optional_time||epoch_millis]]; nested: NotSerializableExceptionWrapper[date_time_parse_exception: Failed to parse with all enclosed parsers];\nShard[4]: OpenSearchParseException[failed to parse date field [2016-11-15 00:00:00] with format [strict_date_optional_time||epoch_millis]: [failed to parse date field [2016-11-15 00:00:00] with format [strict_date_optional_time||epoch_millis]]]; nested: IllegalArgumentException[failed to parse date field [2016-11-15 00:00:00] with format [strict_date_optional_time||epoch_millis]]; nested: NotSerializableExceptionWrapper[date_time_parse_exception: Failed to parse with all enclosed parsers];\n\nFor more details, please send request for Json format to see the raw response from OpenSearch engine.",
    "type": "SearchPhaseExecutionException"
  },
  "status": 400
}

Root cause -
Currently for response JDBC format, when term/range query has timestamp field in the sql query, by default we are converting timestamps to epoch time in milliseconds when building query for Opensearch DSL which is causing the above exceptions. Instead for timestamp query string in epoch, we should send parsed formatted timestamp string as it is as part of the query similar to Date format.
Fixing this issue as part of this PR https://github.com/opensearch-project/sql/pull/2765


Replacement of "compile" with "implementation"

As "compile" is going to be deprecated end-2018, this PR replaces with "implementation" that is the new usage.

Replacement of "compile" with "implementation"


Add nominee: Altinn

Add nominee: Altinn

Altinn needs to clarify the primary organization or maintainer before we can complete the nomination. @lacabra I have got in touch with the project contact person and will update once we are satisfied with their reply.

Hi @nathanbaleeta,
Altinn is owned and maintained by the Norwegian Digitalisation Agency (digdir) on behalf of the Altinn co-operation, consisting of over 60 Norwegian government bodies.

Requesting one small change, otherwise it looks good. Modified website in previous commit

Resolved in commit 159d1f6


add conditional compilation and ability to check target platform and architecture

When an if statement is analyzed, the condition is checked for constant expression evaluation. If the condition is available at compile time, then this if statement becomes a conditional compilation construct. Combine this with a compiler function which checks compile information, and we're already almost done:
fn f() {
    if (#compile_var("os") == "linux") {
        // ...
    } else {
        // ...
    }
}

#compile_var() can look up a string in a table of variables defined at compile time. A compile variable might be any type.
Usually, if an if condition's "then" expression or "else" expression is unreachable because the condition is constant, it will generate an "unreachable code" error. However, we can annotate the constant expression with a value indicating that it can differ depending on compile time variables. When this annotation is present, the "unreachable code" error is not generated.
So, conditional compilation is perfectly integrated into the language's syntax within a function. Let's look at outside a function:
const foo : i32 = if (#compile_var("release")) 1234 else 5678;

Global constants and variables can use full expression syntax for their initializers, so this works here too.
How about a global initialized list of things (example), of which the length of the list is dependent on compile time variables?
In C we have:
static const enum SoundIoBackend available_backends[] = {
#ifdef SOUNDIO_HAVE_JACK
    SoundIoBackendJack,
#endif
#ifdef SOUNDIO_HAVE_PULSEAUDIO
    SoundIoBackendPulseAudio,
#endif
#ifdef SOUNDIO_HAVE_ALSA
    SoundIoBackendAlsa,
#endif
#ifdef SOUNDIO_HAVE_COREAUDIO
    SoundIoBackendCoreAudio,
#endif
#ifdef SOUNDIO_HAVE_WASAPI
    SoundIoBackendWasapi,
#endif
    SoundIoBackendDummy,
};

In Zig we take advantage of void array elements being removed from the array:
const available_backends = [
    if (#compile_var("have_jack")) SoundIoBackend.Jack else void,
    if (#compile_var("have_pulse_audio")) SoundIoBackend.PulseAudio else void,
    if (#compile_var("have_alsa")) SoundIoBackend.Alsa else void,
    if (#compile_var("have_core_audio")) SoundIoBackend.CoreAudio else void,
    if (#compile_var("have_wasapi")) SoundIoBackend.Wasapi else void,
    SoundIoBackend.Dummy,
];

Note that technically the else void could be omitted since an if statement with no else defaults to else void. It may be that void is the wrong type for this, but this construct is powerful and so if void is the wrong type then we may introduce a "deleted array item" type.
Next problem. Anything that you can export, you might want to not export it. So, for any top level declaration for which export is valid - this currently includes functions, global variables, enums, and structs, we will also define a directive, let's call it #condition() which accepts a boolean expression which decides if the top level declaration is included in the compilation. If the top level declaration is not included, then calling it or otherwise depending upon it is a compile time error. Example:
#condition(#compile_var("os") == "win32")
export fn trace_win32() {
     const err = get_last_win32_error();
     print_win32_error(err);
}

fn f1() {
    if (#compile_var("os") == "win32") {
        trace_win32(); // OK, since const expression eval ensured this didn't actually run when trace_win32 is not exported
    }
    trace_win32(); // error when building with compile var "os" == "win32": trace_win32 symbol not defined
}

Finally the only problem left is the syntax that we use to import C .h files. We don't yet have a syntax for directly importing a C .h file, but it's planned. We would need to conditionally import some .h files and not others depending on compile variables. I'll defer figuring out how that will work until we actually have that construct. But I will mention that it's probably planned that the best use of the auto C .h file importing feature is to limit it to a single invocation that would declare the order in which preprocessor defines are defined and what their values are as well as the order of (virtual) #includes. So, one could associate preprocessor defines with expressions and #includes with boolean expressions.

This all works now.