[Native] Pointer capture release

Reported by forum user:
"Actually another strange blocker issue we encountered and can replicate in the sample app, is that if we use a gizmo with JSC or Hermes, mesh picking and gizmo dragging stops working immediately after dragging the camera (pan, rotate etc) for the first time, and can’t be restored without an app restart. There is no issue when using V8, which makes no sense I realise. It’s as though the native camera controls hijack drag events and won’t let go, but only when using JSC or Hermes JS engines."
and a video:
https://drive.google.com/file/d/1lfepPOMaM8IX4K5puqOGfQRf-M4dksaH/view
I could repro with his branch on Android.
After hours of debugging, I've found the buttons is undefined here:
https://github.com/BabylonJS/Babylon.js/blob/7cee15e89e995cd466e18e5a1b78e0b6432f85da/packages/dev/core/src/Inputs/scene.inputManager.ts#L937
if I change the test, everything is fine.
I've also tested on web but execution never reaches that particular line as _pointerCaptures is already false at this point: https://github.com/BabylonJS/Babylon.js/blob/7cee15e89e995cd466e18e5a1b78e0b6432f85da/packages/dev/core/src/Inputs/scene.inputManager.ts#L928
I tried to repro with BabylonNative but I can't click & drag the gizmo. Any reason for that?

The original report came from me.
I'm unsure if this needs a separate ticket but something related that I've noticed is that dragging/picking is also broken if I use hardware scaling other than 1.0 in React Native.

The original report came from me.
I'm unsure if this needs a separate ticket but something related that I've noticed is that dragging/picking is also broken if I use hardware scaling other than 1.0 in Babylon React Native.

I think this should be captured in this issue : https://github.com/BabylonJS/BabylonReactNative/issues/392

Fixed in BJS: https://github.com/BabylonJS/Babylon.js/pull/14043


wrote cpp + java programs for rupee to paise conversion

Why:
Closes #132
Closes #134
What's being changed:
Added solutions for "Rupee to Paise" in the following languages: C++ and Java.
Check off the following:

[x] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Hey @nurhaliza
Thanks for conributing to this open source project 😃
This PR will be reviewed and merged shortly.

Preview : https://codinasion--pr32-dev-s0w5cv9u.web.app/programme/rupee-to-paise/
(expires Mon, 14 Mar 2022 04:03:57 GMT)

LIVE : https://codinasion.web.app/programme/rupee-to-paise/


Add support for updating xterm title

Describe the feature
It would be cool if Doom updated the xterm frame title. Currently I do this with the following code in my config.el:
(when (featurep! :os tty)
  (add-hook! after-init :append
    (use-package! term/xterm
      :if (and (not window-system)
               (not noninteractive))
      :hook (post-command . xterm-set-window-title))))

There are probably further edge cases to handle, but it works for me in tmux and multiple terminal emulators. I think something like this should be added to the :os tty module.

As of c9056dd the :os tty module should update xterm window titles. Let me know if that isn't the case and I'll reopen it. Thanks for bringing it to my attention!


Error code 500

Error message:
Failed to get rewards - Request failed with status code 500 Execution layer rewards not available - missing data for proposer 306186, slot 8674781
Date range used 3/18/2024-2/23/2024

I've fixed some block reward indexing issues this week, looks like it also fixed this specific slot!


Bower install js compile errors

We had a new install of WP with foundationpress and make some commits and changes from the current master. However, when trying to install the theme and move databases to another WP install, the Foundation off-canvas menu does not work.
I throws this error
Tried to initialize off-canvas on an element that already has a Foundation plugin.

Any help is appreciated.

Ok? What changes did you commit form the current master?

Okay after some intensive digging after scrapping my build it appears the problem isnt with the migrations as it is with the bower installation somewhere. Upon installing a new bower component foundation compiles and tries to initialize twice or something? When I remove the init-foundation.js file the error goes away but so does the mobile nav. Any help is appreciated

Do you get any errors in console?

No console errors.

I did not get any console errors, just the original warning in the browser console

Do you have a link to a test site where I can have a look at what's going on?


Refactor/syntax into enums

Sorry @marzipankaiser & @phischu & @JonathanStarup, this is probably yet another annoying-to-rebase PR.


Scraper only getting first image.

I'm having an issue that only the image folder and the JSON are getting the first image, even with:
geomatch = session.get_geomatch(quickload=False)
My first time using this script for educational purposes so not sure/ something could be misconfigured.

I am having same issue with this script, did you already found a solution ?

I did not, I got distracted.
I noticed that the script doesn't have the same issue if it swiping through the user's profile, so probably something about the selenium commands to pick up the photo scrolling button are failing on the general list of users.


adding plugin hooks

adding possibliity to extend quetz functionality with plugins. See plugins directory for more info.
This PR implements a simple plugin to expose package's run_exports.

@wolfv ready for review


Support customTime for GCS+gRPC

I am about to add support for the customTime field in gcs::ObjectMetadata, the protos do not have it yet, so I am punting on the gRPC implementation.

How is the gRPC implementation going ? Since I currently use protos as the backend for the testbench, the conversion of REST request into protos will automatically remove the customTime field ( because protos does not have that field yet )

The gRPC implementation continues to be focused on data operations, I expect these differences will be fixed once the team refocuses on metadata operations.


[azure-core] Authorization header should be un-redacted if using NetworkTraceLoggingPolicy

https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/core/azure-core/azure/core/pipeline/policies/_universal.py#L283-L284
Guideline: https://azure.github.io/azure-sdk/python_implementation.html#python-logging-debug
According to guidelines/docs, we should expect to see sensitive information logged if opting into this policy / setting level to DEBUG.

@johanste event the authorization token? I feel nervous about that?

The intent is for the network trace to help debug issues. I understand your concern. The problem is that they way the network tracing works, we will play whack-a-mole with sensitive information unless we use the same strategy as the "normal" info level log where we have an explicit allow-list.
We can continue with that effort, but at the end of the day, we are not making guarantees that no sensitive information is ever added to logs (i.e. in the request or response body). My concerns with this is that it sort-of-kind-of looks like we are trying to redact all sensitive information that will give developers a false sense of security.
Having said that, I don't have a strong opinion on this.

#17271

#17424

Fixed.


Variant attributes should be copied as well when order is placed.

as with shipping address in https://github.com/mirumee/saleor/issues/503
I think ProductVariant's attributes should be copied.

Most stores only need the SKU to fulfil an order. I'm not sure we need to copy all attribute values by default.

It came up when I needed to display what a user bought for himself.
Some of the attributes were important enough to show.
Well I just wanted to share my thoughts.

We're open to discuss this. We have one store that also wants to show sizes as a separate field in order details (instead of part of the product's name).

@artursmet Want to share your insight?

In my opinion we should also copy the attributes. As you mentioned, there are stores that have all variants with the same names, only size or color differ.
We can implement it by the way with the fix for shipping address you mentioned above.


examples: add docker example

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Example for running nuxt app with docker

Description

This PR adds example for running nuxt app with docker. This could highly useful for nuxt community as there no proper resource available to build nuxt app with docker.

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

Codecov Report

Merging #5430 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #5430   +/-   ##
=======================================
  Coverage   96.16%   96.16%
=======================================
  Files          74       74
  Lines        2555     2555
  Branches      652      652
=======================================
  Hits         2457     2457
  Misses         82       82
  Partials       16       16

Continue to review full report at Codecov.

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

@pi0 Made the requested changes.

@UtkarshGupta-CS I didn't locally test. Can you please also confirm all changes are working fine with docker?

@pi0 Tested locally, works fine.

How to run nuxt in development mode with docker?

@tbanys This PR is related to production hosting nuxt so it could be better to discuss in Discord or an Issue.
Running a docker based development environment for nuxt, could be tricky and vary depending on OS. You can try by  creating a docker-compose file like this:
version: '3'

services:
    nuxt:
        image: node:alpine
        command: yarn dev
        volumes:
            - .:/app
        environment:
            - HOST=<IP_ADDRESS>
        working_dir: /app
        ports:
            - 3000:3000

Initialize project: (on/off command)
docker-compose run --rm nuxt yarn create nuxt-app .

Run development server:
docker-compose up nuxt

You can now access it via http://localhost:3000
 docker-compose up nuxt
Creating foo_nuxt_1 ... done
Attaching to foo_nuxt_1
nuxt_1  | yarn run v1.13.0
nuxt_1  | $ nuxt
nuxt_1  | 12:44:02 ℹ Listening on: http://localhost:3000
nuxt_1  | 12:44:03 ℹ Preparing project for development
nuxt_1  | 12:44:03 ℹ Initial build may take a while
nuxt_1  | 12:44:03 ✔ Builder initialized
nuxt_1  | 12:44:03 ✔ Nuxt files generated
nuxt_1  | webpackbar 12:44:04 ℹ Compiling Client
nuxt_1  | webpackbar 12:44:04 ℹ Compiling Server
nuxt_1  | webpackbar 12:44:08 ✔ Server: Compiled successfully in 3.38s
nuxt_1  | webpackbar 12:44:08 ✔ Client: Compiled successfully in 3.66s
nuxt_1  | 12:44:08 ℹ Waiting for file changes

@UtkarshGupta-CS
Can you explain why do you run 2 different yarn install commands and yarn build is not with production settings ?
Also why don't you use node:alpine for everything ?
Dockerfile:
FROM node:latest as builder

WORKDIR /src

COPY . .

ENV HOST <IP_ADDRESS>
EXPOSE 3000

CMD [ "yarn", "start" ]

@jjelev We used 1st yarn install for getting dependencies and devDependencies for yarn build. Then we removed all the dependencies because after the build we have all the static files we need to serve. Then we only installed dependencies (In production mode, does not install devDependencies) to serve using yarn start. The 2nd yarn install becomes quite faster as yarn get dependency from its cache.
nuxt dependency is actually quite big in size but it is required for building the app. But after the build, we can use nuxt-start (package made by nuxt team, which is immensely small compare to nuxt) to serve the static files.

package.json file

{
  "name": "docker-build",
  "scripts": {
    "dev": "nuxt",
    "build": "nuxt build",
    "start": "nuxt-start",
    "generate": "nuxt generate"
  },
  "dependencies": {
    "cross-env": "latest",
    "nuxt-start": "latest"
  },
  "devDependencies": {
    "nuxt": "latest"
  }
}

Why we didn't use node:alpine for everything because alpine OS doesn't support some native dependency like libpng and many others out of the box. User need to install it manually so it's better to use node:latest. Here we used multi staged build in which in 1st stage we build the app and generated the static files and in 2nd stage we don't need any other dependencies other than nuxt-start which works fine in node:alpine image.
You can change this dockerfile as per your need, for any standard nuxt application setup this dockerfile works just fine. Any other suggestion will be appreciated.


Automate interop client running

The interop client could be run on all the known implementations at once.
For example, we could maintain a list of urls in a yaml file, and add a cli flag to interop/src/main.rs to make it run tests against each of them, and output a list of results.
Feedback for new changes would then be a lot faster to obtain. It could also be run by the CI.

Not sure about running this in CI. Would be nice to have, though.
Can probably just stuff the list of endpoints in a const rather than having the YAML, since it's just us changing it.

Hardcoding a list of peers to test sounds like a great idea! I've gotten pretty lazy about clientside interop testing and this would make it trivial to keep up.

This was fixed by #551, right?

Yes it was!


[Coverity CID :186851] Error handling issues in /tests/bluetooth/mesh/src/microbit.c

Static code scan issues seen in File: /tests/bluetooth/mesh/src/microbit.c
Category: Error handling issues
Function: configure_button
Component: Tests
CID: 186851
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

classified as intentional in coverity


This codebase has so many errors it is completely useless and unusable

precision = "bf16-true"
is unsupported but in the code for lora-finetuning
fabric.init_module
causes a does not exist error.
with fabric.device
results in an error in full fine-tuning script
Overall very poor experience and poor documentation. Garbage

This is a very constructive feedback. Kudos 👏

I don't know about the with fabric.device but let me address the other two

precision = "bf16-true"

fabric.init_module

with more explicit warnings and suggestions via a PR shortly.

@Abecid What error are you getting with bfloat16. I think it's only supported in Ampere and newer, but it appears that it now also works on older T4's and CPU. Just tested it. Maybe it's a PyTorch version thing.
If you have time and don't mind spending a few more minutes, could you let me know the error code you are getting and PyTorch version to look into it further? I could then add a more explicit warning to save the hassle for future users.


Add back proxy support

Proxy support was disabled and not implemented in the move from node-webkit to electron. Updating the old proxy with the electron one seems straightforward. What is currently unknown is how to verify this works. For anyone who is behind a proxy, please provide a means for the core team to reproduce being behind a proxy so we can implement and QA this

For anyone looking for temporary solution:
The issue I found was that it was not able to connect through NTLM authenticated proxies. The workaround for me was to install and use Cntlm. It is a local proxy that connects to your network's proxy on your behalf. So, a proxy to your proxy. You give it the credentials to your network's proxy then just point LightTable at localhost.

I think the only way to reproduce being behind a proxy would be to be behind a proxy :)
Maybe running a simple proxy on localhost would be enough?
e.g. something like this:
http://stackoverflow.com/a/7271863/495319
or maybe this:
https://github.com/nodejitsu/node-http-proxy

I think specifically it was failing behind NTLM proxies, correct?
On Sunday, October 25, 2015, Michael Wood<EMAIL_ADDRESS>wrote:

I think the only way to reproduce being behind a proxy would be to be
behind a proxy :)
Maybe running a simple proxy on localhost would be enough?
e.g. something like this:
http://stackoverflow.com/a/7271863/495319
or maybe this:
https://github.com/nodejitsu/node-http-proxy
—
Reply to this email directly or view it on GitHub
https://github.com/LightTable/LightTable/issues/1984#issuecomment-150900177
.

--
"Simplicity is the ultimate sophistication."
--  Leonardo da Vinci

Squid might be a good candidate for something that could be setup so that a contributor could reproduce the issue(s).
@EarthCitizen Care to figure out how to setup a proxy server and reproduce the problems you described in #1895?

Does Squid support NTLM authentication?
On Wednesday, October 28, 2015, kenny-evitt<EMAIL_ADDRESS>wrote:

Squid http://www.squid-cache.org/ might be a good candidate for
something that could be setup so that a contributor could reproduce the
issue(s).
@EarthCitizen https://github.com/EarthCitizen Care to figure out how to
setup a proxy server and reproduce the problems you described in #1895
https://github.com/LightTable/LightTable/issues/1895?
—
Reply to this email directly or view it on GitHub
https://github.com/LightTable/LightTable/issues/1984#issuecomment-152045896
.

--
"Simplicity is the ultimate sophistication."
--  Leonardo da Vinci

@EarthCitizen yup

If there is a build ready, I can try it at work, which is where I had the
problem.
On Wednesday, October 28, 2015, kenny-evitt<EMAIL_ADDRESS>wrote:

@EarthCitizen https://github.com/EarthCitizen yup
—
Reply to this email directly or view it on GitHub
https://github.com/LightTable/LightTable/issues/1984#issuecomment-152068940
.

--
"Simplicity is the ultimate sophistication."
--  Leonardo da Vinci

@EarthCitizen A LT build? There's the recent 0.8.0-alpha release we just published but there haven't been any changes made for proxy support. There are binaries for Squid at the link in my previous comment but we don't need you to reproduce your issue. We need help figuring out how to setup a proxy so anyone else can reproduce it.

Squid does indeed support ntlm in conjunction with Samba. I've never tried it, though.
Here's some old documentation about setting it up:
http://wiki.squid-cache.org/ConfigExamples/Authenticate/Ntlm

I'm behind a proxy and i confirm that it doesn't work neither with the latest version 0.8.0.
You can mark me as the tester.

@EarthCitizen - How did you point LightTable to your localhost?  I have CNTLM running on my system but haven't found anything that lets me point LightTable to it?

@scelera If I remember correctly, I believe I did it with the http_proxy and https_proxy environment variables

@EarthCitizen Thanks.  Unfourtuneatly for me I already have those set and it still doesn't work.

Make sure you have both set:
http_proxy=http://localhost:
https_proxy=https://localhost:
Also,

Yup, both are set.  I've been using CNTLM for over a year now.  Works flawlessly with everything else.  I'm on LightTable 0.8.0 if that makes a difference.

The only other thing I can think of is to try the various http.proxy___ Java system properties

Thanks.  I think I got that part figured out.  I updated the tunnel.js file in \resources\app\core\node_modules\request.  Now though it's giving me this error
TypeError: lt.objs.deploy.request.get is not a function
at lt.objs.deploy.download_file (file:///C:/usryrs/lighttable-0.8.0-windows/resources/app/core/node_modules/lighttable/bootstrap.js:28950:33)
at lt.objs.plugins.download_metadata (file:///C:/usryrs/lighttable-0.8.0-windows/resources/app/core/node_modules/lighttable/bootstrap.js:29393:39)
at Function.lt.objs.plugins.__BEH__check_local_metadata_cache (file:///C:/usryrs/lighttable-0.8.0-windows/resources/app/core/node_modules/lighttable/bootstrap.js:29822:419)
at c (file:///C:/usryrs/lighttable-0.8.0-windows/resources/app/core/node_modules/lighttable/bootstrap.js:6196:14)
at a (file:///C:/usryrs/lighttable-0.8.0-windows/resources/app/core/node_modules/lighttable/bootstrap.js:6236:18)
at c (file:///C:/usryrs/lighttable-0.8.0-windows/resources/app/core/node_modules/lighttable/bootstrap.js:20446:76)
at a (file:///C:/usryrs/lighttable-0.8.0-windows/resources/app/core/node_modules/lighttable/bootstrap.js:20480:18)
at a (file:///C:/usryrs/lighttable-0.8.0-windows/resources/app/core/node_modules/lighttable/bootstrap.js:20491:34)
at b (file:///C:/usryrs/lighttable-0.8.0-windows/resources/app/core/node_modules/lighttable/bootstrap.js:20495:14)
at file:///C:/usryrs/lighttable-0.8.0-windows/resources/app/core/node_modules/lighttable/bootstrap.js:29387:28
Is this releated to the proxy problem or is this something else?

@scelera That looks new.

Same issue for me: I cannot refresh the plugins list, nor update, nor install plugins, being behind my company's proxy. I'm using LightTable 0.8.0 / Windows 7 Enterprise / Java JDK 7.
LightTable's console shows following error when trying to refresh the plugins list:
TypeError: Request path contains unescaped characters.
    at new ClientRequest (_http_client.js:51:11)
    at TunnelingAgent.exports.request (http.js:31:10)
    at TunnelingAgent.createSocket (E:\projects\lighttable\resources\app\core\node_modules\request\tunnel.js:117:25)
    at TunnelingAgent.createSecureSocket [as createSocket] (E:\projects\lighttable\resources\app\core\node_modules\request\tunnel.js:184:41)
    at TunnelingAgent.addRequest (E:\projects\lighttable\resources\app\core\node_modules\request\tunnel.js:80:8)
    at new ClientRequest (_http_client.js:133:16)
    at Object.exports.request (http.js:31:10)
    at Object.exports.request (https.js:163:15)
    at Request.start (E:\projects\lighttable\resources\app\core\node_modules\request\main.js:559:30)
    at Request.end (E:\projects\lighttable\resources\app\core\node_modules\request\main.js:1075:28)

I'm starting LightTable with this script:
@echo off
echo.

:set-java-home
SET "JAVA_HOME=…\jboss\jdk\64\1.7.0_51"
set "JAVA_CMD=%JAVA_HOME%\bin\java"
ECHO   Set JAVA_HOME to "%JAVA_HOME%" ...
ECHO   Set JAVA_CMD to "%JAVA_CMD%" ...

:set-http-proxy
SET "HTTP_PROXY=http://proxy:8080"
SET "HTTPS_PROXY=http://proxy:8080"
SET "HTTP_NO_PROXY=*.mycompany.com|localhost"
echo   Set HTTP_PROXY and HTTPS_PROXY to %HTTP_PROXY% ...
ECHO   Set HTTP_NO_PROXY to "%HTTP_NO_PROXY%" ...

:launch
echo   Launching Light Table ...
set "LTHOME=E:\projects\lighttable"
start %LTHOME%\LightTable.exe

And LightTable's Node configuration looks like this:
E:\projects\lighttable\resources\app\core\node_modules\replace>npm config list
; cli configs
user-agent = "npm/3.7.3 node/v5.9.0 win32 x64"

; userconfig C:\Users\MyUserName\.npmrc
https-proxy = "http://proxy:8080/"
proxy = "http://proxy:8080/"

; builtin config undefined
prefix = "C:\\Users\\MyUserName\\AppData\\Roaming\\npm"

; node bin location = C:\Program Files\nodejs\node.exe
; cwd = E:\projects\lighttable\resources\app\core\node_modules\replace
; HOME = C:\Users\MyUserName

Updating the request module from version 2.14 to version 2.72 (latest as of today), then restarting LightTable, solved the issue for me. I can now refresh the plugins list and install new ones, while being behind my company's proxy:
C:> cd /d E:\projects\lighttable\resources\app\core
E:\projects\lighttable\resources\app\core> npm list request
<EMAIL_ADDRESS>E:\projects\lighttable\resources\app\core
`--<EMAIL_ADDRESS>E:\projects\lighttable\resources\app\core>npm update request
[… snip snip …]
<EMAIL_ADDRESS>E:\projects\lighttable\resources\app\core
`--<EMAIL_ADDRESS>
I followed @geisi93 's suggestion in #321 (using npm update request rather than updating tunnel-agent manually in request's dependencies).

@olange If that really is all we need to do, that's fantastic!
Mind submitting a PR with that change? If you do, I'll try to get to it today.

yes, it works for me. Many thanks

Update request work for me.
Win 7. Lt launch on "git bash" command after export http_proxy & https_proxy.

I'm getting the same issue as @howardlinus after updating the request module as per @olange 's instructions. What I find is that there is a metadata_temp.tar.gz of 0 bytes in the ...\AppData\Roaming|LightTable directory (which disappears when I quite LightTable). This suggests to me that something in the proxy is still preventing the metadata file from being downloaded correctly, so the 0 byte file expands to nothing, whereas it should expand to the metadata_temp directory.
In my case I'm pretty sure that this is my work proxy that is causing the problem. I'm using a local proxy (Fiddler) which does the same thing as Cntlm (proxies requests to the real proxy using NTLM auth). I can see in the logs for the proxy that LightTable is accessing api.github.com:443 before the error occurs. My work proxy inserts it's own SSL certificate in the chain (yes, man in the middle) to be able to monitor SSL traffic (common practice in banks). This doesn't play well with a lot of services, GitHub among them. I fear that the only solution, at least in my specific case, would be a way to configure LightTable to not use SSL when communicating with GitHub.

@mluisbrown I think you're out of luck if you can't access GitHub over HTTPS:

All API access is over HTTPS, and accessed from the https://api.github.com. All data is sent and received as JSON.

Would you please create a separate issue as this issue just covers generic proxy support.

@kenny-evitt I've looked at this further, and I don't think that my work proxy is blocking SSL access to api.github.com after all (I can access it via a browser no problem). Still, for whatever reason the metadata-temp.tar.gz file that's received from GitHub is 0 bytes long, which leads to the Error: ENOENT: no such file or directory, scandir 'C:\Users\myid\AppData\Roaming\LightTable\metadata-temp' error mentioned above.
I can download https://api.github.com/repos/LightTable/plugin-metadata/tarball/master ok in my browser, so there's no reason that LightTable shouldn't be able to download it either.

More info. My work proxy is not blocking SSL access, but they are inserting their own SSL certificate in the chain in order to be able to monitor SSL traffic of employees as I mentioned above. This means that software that performs certificate verification will fail:
curl -i https://api.github.com/users/octocat/orgs fails with an SSL certificate problem. It only works if I use the --insecure option. I imagine that request also fails for the same reason. I will verify that and see if there's any option that can be passed to request for it to work in "insecure" mode.
The reason it works fine in the browsers at work is because they have been pre-configured to trust the company certificate :-)

Confirmed that it's the SSL certificate problem. The following node script:
var request = require('request');
var fs = require('fs');

request({
    url: 'https://api.github.com/repos/LightTable/plugin-metadata/tarball/master',
    strictSSL: false,
    headers: { 'User-Agent': 'Light Table'}
}).pipe(fs.createWriteStream('metadata-temp.tar.gz'));

works fine. But if I remove the strictSSL: false option (it defaults to true) then I get:
Error: self signed certificate in certificate chain and a 0 byte file is created.
To "fix" this for people in work environments like mine there would need to be some kind of config option that made calls using [request](https://www.npmjs.com/package/request) use the strictSSL: false option. The relevant code is here. I'll create a separate issue for this.
More relevant to this issue though is that @olange 's change to update the Node package [request](https://www.npmjs.com/package/request) to the latest version does fix proxy support.

Just to confirm my issue beyond all doubt, if I hack the copy of request in my LT installation to force strictSSL: false then the Plugin manager in LT works fine over the office proxy :smile:

I'm using LightTable 0.8.1 in Ubuntu 16.04 with CNTLM configured and in use by every other application on my machine. But I couldn't connect to server and get the plugins available. Reading this thread, I installed npm on my machine and checked the request version on path "lighttable-0.8.1-linux/resources/app/core:
$ npm list request
<EMAIL_ADDRESS>~/lighttable-0.8.1-linux/resources/app/core
└──<EMAIL_ADDRESS>Then configured proxy on ntm with the commands:
npm config set proxy http://<IP_ADDRESS>:3128
npm config set https-proxy http://<IP_ADDRESS>:3128
and executed the command "npm update request" and after that, the command "npm list request" showed the following output:
<EMAIL_ADDRESS>~/lighttable-0.8.1-linux/resources/app/core
└──<EMAIL_ADDRESS>After this, the Light Tabçle could connect to server and update the plugins.

@djavanci Thanks for confirming.

Being back today at my customer's site, where I encountered the issue I reported on April 17, I built LightTable from the sources this time (rather than only updating the request module within the packaged version of LightTable), behind its enterprise proxy, and could confirm that updating the request module to the latest version indeed solved the issue of updating the plugins behind a proxy:

build of LightTable 0.8.1 on Windows from sources (master branch as of today) fails refreshing the plugins list, nor update, nor install plugins;
after update of the request module from version 2.14.0 to latest 2.72.0 within folder deploy/core/, and a new build from these updated sources, the new build of LightTable.exe allowed me to refresh the plugins list and install new plugins (I installed Markdown 0.0.3, which worked fine).

I would happily submit a PR with the changes, as it seems pretty sure from all comments, that it brings back proxy support, but I'm a bit confused about what the PR should contain. Could anyone guide me?
Obviously, the PR should contain the updated deploy/core/package.json, but git status shows quite a lot of deleted, updated and untracked files in deploy/core/node_modules/. Some of them are updated dependencies of the request module, but others were already displayed by git st as being updated or untracked, just after a npm install on a clean checkout of the sources, and before updating the request module.

@olange I submitted PR #2208 already but the core team (excluding me) is not sold on merging those changes. As-of now, at least one of the core team needs to reproduce the original issue. We haven't gotten around to doing so yet.

What is keeping proxy support from being added back in?  I'm behind a proxy and some things won't connect (like extensions).
It's a simple proxy --- no authorization needed... just host:port in my browser.  Is that so complicated?
As for duplicating the env on your local machine... download squid from squid-cache.org.
It's not hard to build a basic version.   Would that duplicate the env you need?
Using a VirtualBox to create an isolated system would be another option if you need to ensure connectivity isolation...
tnx,
-linda

@Astara Try the workaround I described in my above comment of 17.04.2016. Assuming you have npm on your command-line, this recipe might solve your issue; replace ‹lighttable-dir› with the path to the folder you installed LightTable into:
> cd ‹lighttable-dir›\resources\app\core
> npm update request
[… snip snip …]
<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>

@kenny-evitt proposed a PR #2208 to solve the issue and took the time to discuss it with core developers (many thanks by the way, I forgot to answer when I first read it last year), but the request was rejected because another request of the core developers is not fulfilled yet – they'd like to be able to test the proxy support in continuous integration tests. So our user requirement is subordinated to a tooling requirement…
I feel this is well blocked. And if I might add a comment: I understand well the QA concern, but I don't get why this improvement to the user experience, that eases adoption of LightTable in corporate environments, should be blocked by another improvement of the continuous build environment.
Automating tests is very good practice – but if no one is able to setup the required tooling, then it is bad strategy to block the improvement. Users are very good at reporting issues, and we certainly would, if updating the request to its latest version had side-effects.

Olivier Lange wrote:

@kenny-evitt https://github.com/kenny-evitt proposed a PR #2208
https://github.com/LightTable/LightTable/pull/2208 to solve the
issue and took the time to discuss it with core developers (many
thanks by the way, I forgot to answer when I first read it last year),
but the request was rejected because another request of the core
developers is not fulfilled yet – they'd like to be able to test the
proxy support in continuous integration tests. So our user requirement
is subordinated to a tooling requirement…

They can setup squid and test through that -- or to really isolate a

client,
run it on a VM.
I.e. the method is there.  If they want to set it up, they can.  But

like you
say, if they aren't willing to automate the test, I'd think they weren't
that
serious about automating -- and if using that as an excuse not to fix the
bug, then its pretty obvious they don't care to fix it.
Too bad.
It's alot slower than FF, so I have a feeling the project is already

on the decline.

Given that adding QA has been blocked by upgrading Light Table's internal ClojureScript to something remotely recent for at least a year, I have no qualms about reintroducing proxy support in the meantime.

I.e. the method is there. If they want to set it up, they can. But like you say, if they aren't willing to automate the test, I'd think they weren't that serious about automating -- and if using that as an excuse not to fix the bug, then its pretty obvious they don't care to fix it.

In a sense, you are correct @Astara. None of the active maintainers are pained by the proxy issue so no one has taken care of it. The project is currently being run entirely on people's free time... of which there is often little to none. Time spent on the project is almost always something that interests or bothers the maintainers. Short of having a commercial sponsor funding a maintainer for development, this pattern will continue.
As @olange alluded to, if someone can give more specific instructions (or even a link to a good quality guide) for setting up the squid proxy then it will lessen the amount of pain to get the proxy running to test the fix... which would improve the odds of it getting tested soon.

Scott Bauer wrote:

Given that adding QA has been blocked by upgrading Light Table's
internal ClojureScript to something remotely recent for at least a
year, I have no qualms about reintroducing proxy support in the meantime.
I.e. the method is there. If they want to set it up, they can. But
like you say, if they aren't willing to automate the test, I'd
think they weren't that serious about automating -- and if using
that as an excuse not to fix the bug, then its pretty obvious they
don't care to fix it.

In a sense, you are correct @Astara https://github.com/Astara. None
of the active maintainers are pained by the proxy issue so no one has
taken care of it. The project is currently being run entirely on
people's free time... of which there is often little to none. Time
spent on the project is almost always something that interests or
bothers the maintainers. Short of having a commercial sponsor funding
a maintainer for development, this pattern will continue.

They would probably have to attract a large enough user-base for

a sponsor to see it as worthwhile.

As @olange https://github.com/olange alluded to, if someone can give
more specific instructions (or even a link to a good quality guide)
for setting up the squid proxy then it will lessen the amount of pain
to get the proxy running to test the fix... which would improve the
odds of it getting tested soon.

Do any of them run linux?  It's usually an included package in most
distros, which might be the easiest way.  I think even Cygwin (runs on
Windows) has squid in their list of offered packages.
Instructions would vary by distro to some extent.
Like Ubuntu, has a setup guide here...
https://help.ubuntu.com/lts/serverguide/squid.html
I found that by typing in "how to setup squid proxy" to google
at the top entry.  If they have a specific platform, they'd add
that onto search line.
I'm not the best person to ask for simple instructions or a guide to
set it up, as I generate my squid proxy from source and have a
custom-setup for my home network.
The website @ http://www.squid-cache.org/ has pointers
to examples, a wiki, books and more, but the best way is
go for examples for whatever platform you are running
on and google on that.
Thinking about it -- I'm wondering -- the proxy issue only came
up when I scanned for extensions/plugins.  Does that go to a website
URL?  That might be the problem -- if it is going to some absolute port
and not using http(or https) as a transport, then they might have
more luck converting the extension-plugin scanner to http and web-requests,
but w/o delving into it more, not sure exactly what the problem is.

Thinking about it -- I'm wondering -- the proxy issue only came
up when I scanned for extensions/plugins.  Does that go to a website
URL?  That might be the problem -- if it is going to some absolute port
and not using http(or https) as a transport, then they might have
more luck converting the extension-plugin scanner to http and web-requests,
but w/o delving into it more, not sure exactly what the problem is.

The problem is only with getting plugin metadata, downloading plugins and for autoupdate. The relevante code is here. It uses regular HTTPS web requests to the GitHub repo, see here
I already have an open PR to fix the proxy issues, including an option to disable strict SSL checking which is requires in some corporate environments. The PR also has detailed steps for being to able to test the fix.
In short, there are two issues:

update the NPM request package to version 2.72.2 (or higher) as proxy support in general is broken in the version that LT is using (2.14.0).
add an option to be able to disable strict SSL checking.

It is really unfortunate that a PR can be waiting to be merged for nearly a year just because QA can't test it in an automated way. Ignoring PRs is a great way to stop getting any community contributions 😞

@mluisbrown - thanks for pointing out your PR and the steps for being able to test the fix. Assuming Charles works for Windows and Linux (it should), I will give it a try this week.
I do agree it is quite unfortunate that there have been several important PRs stagnating, which is why we intend to address all outstanding PRs this year as part of Light Table's 2017 Roadmap.

Thanks @sbauer322 for merging the PRs! I believe this issue can now be closed, finally 🎉 . I already closed #2212.

Closing as PRs #2214 and #2331 have been merged and should address this.


Allow specifying the password in the server url

Some hosted services will provide a single string REDIS_URL containing both the host and password to the redis instance.
Handle those instead of requiring parsing the URL earlier.

Nevermind. This breaks the localhost:6379 (without a protocol) usage. I'll do the parsing upstream.


Add default quoted and escape characters to help text

Type of Change

[ ] Bug fix (non-breaking change, fixes # )
[ ] New feature (non-breaking change, adds functionality, fixes # )
[ ] Breaking change (effects multiple commands or functionality, fixes # )
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[X] Documentation
[ ] Build system

Purpose

Improve documentation
Approach

Lines 279 and 280 set the default values for the quote and escape characters.  This PR adds that information to the help text.

Parrrty! thanks for the PR, @MarkIannucci! will merge once the checks pass ⚡

💃🎉🎈🥳

@potatoqualitee @wsmelton , Thank you for your work here.  We're looking to use this to support or data analysis at Denver Health.  Particularly we'll be using this to support data analysis to assist fighting the opioid use disorder epidemic.

Wow, that's such important work. We're so fortunate to be a part of it 💖


Two Objects with web url fail the rendering

In the example present in readme.md, I made a small change. Added two urls, thus two objects. This fails with
2021/10/06 12:09:50 could not convert the added objects
package main

import (
	"log"
	"os"

	pdf "github.com/adrg/go-wkhtmltopdf"
)

func main() {
	// Initialize library.
	if err := pdf.Init(); err != nil {
		log.Fatal(err)
	}
	defer pdf.Destroy()

	// Create object from file.
	object, err := pdf.NewObject("https://google.com")
	if err != nil {
		log.Fatal(err)
	}
	object.Header.ContentCenter = "[title]"
	object.Header.DisplaySeparator = true

	// Create object from URL.
	object2, err := pdf.NewObject("https://google.com")
	if err != nil {
		log.Fatal(err)
	}
	object.Footer.ContentLeft = "[date]"
	object.Footer.ContentCenter = "Sample footer information"
	object.Footer.ContentRight = "[page]"
	object.Footer.DisplaySeparator = true

	// Create converter.
	converter, err := pdf.NewConverter()
	if err != nil {
		log.Fatal(err)
	}
	defer converter.Destroy()

	// Add created objects to the converter.
	converter.Add(object)
	converter.Add(object2)

	// Set converter options.
	converter.Title = "Sample document"
	converter.PaperSize = pdf.A4
	converter.Orientation = pdf.Landscape
	converter.MarginTop = "1cm"
	converter.MarginBottom = "1cm"
	converter.MarginLeft = "10mm"
	converter.MarginRight = "10mm"

	// Convert objects and save the output PDF document.
	outFile, err := os.Create("out.pdf")
	if err != nil {
		log.Fatal(err)
	}
	defer outFile.Close()

	if err := converter.Run(outFile); err != nil {
		log.Fatal(err)
	}
}

I tested with Go 1.16.4 and the sample still works for me. I'm not sure what could be the issue in your case.
It's really strange that it works with one object, but not with two or more for you. I did understand correctly, right? If you run the sample with a single object, the output PDF is generated correctly, without any errors?

Works in my vm. Seems some corrupt installation of wkhtmlpdf. Will have to clean/reinstall my OS.
Thanks for your help @adrg . And this project is going to help a lot of people get good educatioin. Seeing so much active support has really releived me.


C-d does not delete character

Per #39 C-d isn't behaving as expected on Mac.
Expected behavior: Deletes character under the cursor.
Actual behavior: Moves the cursor forward one character.
.NET version info
.NET Command Line Tools (2.1.4)

Product Information:
 Version:            2.1.4
 Commit SHA-1 hash:  5e8add2190

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.12
 OS Platform: Darwin
 RID:         osx.10.12-x64
 Base Path:   /usr/local/share/dotnet/sdk/2.1.4/

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.5
  Build    : 17373eb129b3b05aa18ece963f8795d65ef8ea54

Looks like this was simply never implemented.
I put together a failing test. 2536001f21833452cbf87d7340d9b6cfbb0bc3e5


Deploy orientDB with Ansible on a computer with no Internet

OrientDB Version: 3.0.2
Java Version: 1.8
OS: linux
Hello, I have a little question.
I'm trying to deploy multiple cluster on a hand full of computer but those computer don't have access to the internet. So when they try to Download OrientDB, the task fail.
I'm using Ansible with migibert tool ( from the doc ).
Ans this is my current playbook :
- hosts: orientdb-servers
  become: yes
  vars:
    orientdb_version: 3.0.2
    orientdb_enable_distributed: true
    orientdb_distributed:
      hazelcast_network_port: 2434
      hazelcast_group: orientdb
      hazelcast_password: orientdb
      multicast_enabled: True
      multicast_group: <IP_ADDRESS>
      multicast_port: 2434
      tcp_enabled: False
      tcp_members: []
    orientdb_users:
      - name: root
        password: root
  roles:
  - role: migibert.orientdb

What are my options ?
Thanks.

I'm going to answer to my own question as I found a quick fix working well.
In /etc/ansible/roles/migibert.orientdb/tasks/install.yml  replace the first task
- name: Download OrientDB tarball
  get_url:
    url: server URL
    dest: "/tmp/orientdb-{{orientdb_version}}.tar.gz"

by
- name: Download OrientDB tarball
  copy:
    src: /home/vagrant/Ansible/OrientDB/orientdb-{{orientdb_version}}.tar.gz
    dest: /tmp/orientdb-{{orientdb_version}}.tar.gz
    owner: root
    group: root
    mode: 0644

and make sure you have an orientDB package at the specified source.
Now ansible will grab the package from your local machine and will install it on your server.
This may result in some name changes so make sure the folder name one extracted is orientdb-community-{{orientdb_version}}.


[braviapsk.sony_bravia_psk] Invalid response:

Can't pinpoint when I started getting these errors in the log:
I am currently running 0.103 Beta
- platform: braviatv_psk
  host: <IP_ADDRESS>
  psk: '7884'
  mac: 38:18:4c:44:09:f5
  amp: True
  android: True
  name: Sony TV Theatre

2019-12-07 17:28:18 ERROR (SyncWorker_8) [braviapsk.sony_bravia_psk] Invalid response: {'auth_url': {'default': 'http://<IP_ADDRESS>:80/sony/webauth/auth_default', 'tv': 'http://<IP_ADDRESS>:80/sony/webauth/auth_tv'}, 'error': [403, 'Forbidden'], 'id': 1}
  request path: sony/avContent
  request params: {"method": "getContentList", "params": [{"source": "extInput:hdmi"}], "id": 1, "version": "1.0"}
2019-12-07 17:28:18 ERROR (SyncWorker_8) [braviapsk.sony_bravia_psk] Invalid response: {'auth_url': {'default': 'http://<IP_ADDRESS>:80/sony/webauth/auth_default', 'tv': 'http://<IP_ADDRESS>:80/sony/webauth/auth_tv'}, 'error': [403, 'Forbidden'], 'id': 1}
  request path: sony/avContent
  request params: {"method": "getContentList", "params": [{"source": "extInput:composite"}], "id": 1, "version": "1.0"}

Did you find a fix for this?

Hi Gerard,
TBH not sure what I did in the end. Consider it resolved then I guess :)

On 18 Mar 2020, at 6:44 am, Gerard<EMAIL_ADDRESS>wrote:
Did you find a fix for this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/custom-components/media_player.braviatv_psk/issues/18#issuecomment-600336580, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHJOOQWVPW4XJK27QQJG6JTRH74NDANCNFSM4JXKPPAA.


Add PLK token

Official announcement:
https://twitter.com/Planck__X/status/1548868682423549953
Team Background:
PlanckX team is a vibrant team of over 40 talented and promising entrepreneurs, geeks, and professionals. With an average age of 28 and more than half of them engineers, the team has an eye for cool and techy stuff in the gaming, crypto, and telecom industries.
Brief Introduction of Project:
PlanckX is an open and decentralised blockchain gaming platform and NFT marketplace, which provides a user-friendly and open-source platform that brings together gamers, developers, and NFT creators.
PlanckX are developing a platform on which games can be released without the stipulation that the game must use a particular coin, chain, or system. This will make it possible for blockchain gamers to congregate in a fully open environment. A platform where players may play any blockchain game without interruption, buy and sell non-fungible tokens (NFTs), and gain rewards for the endless hours they spend playing games.
It aims to make the experience straightforward and unobtrusive for everyone, making it suitable not only for blockchain gamers but also for anybody else interested in this developing market.
More about Sirius Finance:
Website: https://planckx.io/
Discord: https://discord.io/planckx
Twitter: https://twitter.com/planck__x
Telegram: https://t.me/planckxeng
Medium: https://medium.com/@planckx
Media Covers:
1)https://www.digitaljournal.com/pr/planckx-aims-to-become-the-worlds-largest-gaming-nft-transaction-community
2)https://www.asiaone.com/business/planckx-poised-upend-how-world-sees-metaverse-game-assets-2022
3)https://www.timesnewswire.com/pressrelease/planckx-a-new-generation-of-metaverse-game-asset-trading-platform-leading-the-innovation-of-game-assets/
4)https://www.digitaljournal.com/pr/planckxs-new-open-blockchain-gaming-nft-marketplace-is-about-to-launch-the-new-launch-has-a-cleaner-and-more-streamlined-interface-with-many-new-perks-for-blockchain-games-and-nft-creators
Tradeable exchanges:
Uniswap
Recommended Gas Limit (For ERC-20 project teams) for transaction: (Default is 60,000)

Missing zh description
Please modify

modify zh description，please see

done


Can’t delete games

I’m finished some games that I got and was wondering how to delete them

You should just be able to delete them from your Google Drive, and they'll disappear from Game Play Color next time you refresh the list.


Feature Request - Will you be able to add code to get artifacts for pipeline or job please?

I am using your code to integrate gitlab instance with one my automation project and its super useful, will you be able to add code to get artifacts from pipeline or job please?
It would be really great to have this option in Gitlab API client

I presume you never got an answer to this.
I am looking to down load artifacts via c#
Did you ever get a solution to this ?


chore(dep) Upgrade to markdown transform 0.9.1

Signed-off-by: Jerome Simeon<EMAIL_ADDRESS>

Coverage remained the same at 95.535% when pulling d97fc36f2f3b84600b2028eb946b561b29b18f9a on jeromesimeon:js-chore-markdown-0.9.1 into 31b7a548ce28f172f6fcb282da7a8f7c4b13664f on accordproject:master.


Orchestrating Agents: Routines and Handoffs - Swarm

A cookbook walking through how you can use handoffs and routines to implement controllable orchestration. It also serves as the "launch" of the Swarm repo.

looks great, left two comments


Allow the theme to specify a default pdfwidth value

The theme should allow to specify a default pdfwidth value for images to be used if the pdfwidth attribute is not specified.
See https://github.com/asciidoctor/asciidoctor-pdf/issues/453

We have one condition to work out. If a default image width is specified in the theme, should that value take precedence over the width value in the image macro? (generally, the value of the width attribute is intended as metadata only, not for sizing).
We also need to decide on a name for the key. image_default_width? (It does have to start with image_).

If a default image width is specified in the theme, should that value take precedence over the width
value in the image macro?

The most detailed value should be the used one. If no value is specified in image: the default value should be used, otherwise the the specified value. In DocBook I used the default one to define the size for all "normal" images, expect the very few that needed a special setting.

image_default_width

Sounds good. If it is specific for the PDF output I would add also add pdf, e.g., image_default_pdfwidth

If it is specific for the PDF output I would add also add pdf, e.g., image_default_pdfwidth

It's in the PDF theme, so PDF is already implied here.

So to clarify, the default (specified in the theme) would not be used in this case:
image::file.png[Description,640,480]

but it would be used in this case:
image::file.png[Description]

correct?

correct?
Sounds perfect for me.

:+1:

I think the default width specified in the theme (image_width) should take precedence over the width attribute. I say this because the width attribute is rarely meaningful for PDF, so it should have the lowest priority.
I'm proposing the following precedence:

pdfwidth attribute
scaledwidth attribute
image_width theme key
width attribute

I'm proposing the following precedence:

pdfwidth attribute
scaledwidth attribute
image_width theme key
width attribute

+1 for the proposal


A way to prevent data load when using the <ma-data> component

If I recall correctly, <ma-data> loads data immediately. I was thinking of some use cases where it might be undesirable.
For example, suppose our data is private, and the user needs to log in to access it. So there is no need to fire load() after the component is mounted (or at some point after the page loads), only after the user logs in. But since we automatically load data after the user logs in, it perfectly suits this use case.
Another use case is if we need to use one backend as a source and another as storage. E.g., we want to copy data from one backend to another. So, it would be nice if we could prevent data loading from the storage backend.
If we decide to implement this feature, I wonder if it'll be a separate attribute or if we can follow the Vue API and have something like: <ma-data src.prevent="url"></ma-data>?
What do you think?

I don't think .prevent would be a good idea, as it's only ever used with event handlers.
Maybe a load attribute with values auto (default), manual, authenticated? That would also allow for future extensions to how data is loaded.


Build takes unusually long time...

I tried several times to build HPX following the build instructions. It does not progress beyond 86%.
[ 86%] Building CXX object src/components/component_storage/CMakeFiles/component_storage_component.dir/component_storage.cpp.o
The only argument I passed while running cmake is the install path.

The issue was on one particular machine....on a different machine, the build works fine...


Merge to live

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

File
Status
Preview URL
Details

Contributing.md
:white_check_mark:Succeeded

docs/docs-ref-autogen/excel/excelscript/excelscript.range.yml
:white_check_mark:Succeeded

docs/sample-scripts/async-excel-scripts.yaml
:white_check_mark:Succeeded

docs/sample-scripts/excel-scripts.yaml
:white_check_mark:Succeeded

generate-docs/json/excel/snippets.yaml
:white_check_mark:Succeeded

generate-docs/scripts/preprocessor.ts
:white_check_mark:Succeeded

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

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

File
Status
Preview URL
Details

Contributing.md
:white_check_mark:Succeeded

docs/docs-ref-autogen/excel/excelscript/excelscript.range.yml
:white_check_mark:Succeeded

docs/sample-scripts/async-excel-scripts.yaml
:white_check_mark:Succeeded

docs/sample-scripts/excel-scripts.yaml
:white_check_mark:Succeeded

generate-docs/json/excel/snippets.yaml
:white_check_mark:Succeeded

generate-docs/scripts/preprocessor.ts
:white_check_mark:Succeeded

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


Set Up Spinning Loader Component

Description
This PR adds the SpinningLoader component to the component library
Screencast
https://user-images.githubusercontent.com/12600902/177663364-217be100-e770-43f3-bb9d-837dbe628ce7.mov

is it possible to add a prop for the color? 🥸

is it possible to add a prop for the color? 🥸

Hey @pedroapfilho, when you say color do you mean the primary and secondary border colors of the loader element? Are you looking for props that will allow you to pass arbitrary values to change these colors? Or are you looking for more variety of variants in addition to the default (white on white) and minimal (blue on blue) variants?
Personally I would be more keen on designing and adding more variants. Opening up the interface to arbitrary colors feels like it might be a little risky in allowing for undesirable color combinations. It also might add complexity in terms of how to handle light/dark mode.
But if you expect a lot of variance in the color of the loader then arbitrary colors might be the way to go.

@noahub
the loaders for now should just be light and dark mode, both use blues.

--
Light Mode
Dark Mode

track
Base.Light
Darkmode.700

loader
Base.Blue
Base.Blue.Muted

@noahub the loaders for now should just be light and dark mode, both use blues.
--	Light Mode	Dark Mode
track	Base.Light	Darkmode.700
loader	Base.Blue	Base.Blue.Muted
I'm actually unsure how you're defining colors so i just put what we've named them in Figma.

Thanks for clarifying @ethan-bc. I grabbed the colors based on the button component loaders. Is there a variant needed for the loader seen here:


Return offset-aware datetimes

s3fs returns offset-naive datetimes, whereas https://github.com/fsspec/filesystem_spec/pull/1314 introduced datetimes at UTC in fsspec.
I often get errors because operations mixing offset-naive and offset-aware datetimes are not allowed.
Here is an example:
fsspec.filesystem("file").modified(...) - fsspec.filesystem("s3").modified(...)
# TypeError: can't subtract offset-naive and offset-aware datetimes

Would it be possible to introduce offset-aware datetimes in s3fs as well?

Actually, I think I would go the other way: local files don't actually have a timezone. We should decide one way or another, and make sure modified() behaves the same everywhere, which might take a little effort.

mmm, good point. Thinking more about it, I think it's OK if filesystem implementations can decide whether to return offset-aware or offset-naive datetimes.
However, I think they should return offset-aware datetimes when they can. I don't like what it's done here because we lose an important information.
As you said, local files don't actually have a timezone. I believe right now fsspec assumes that time infos use the system local timezone and converts to utc. Looks like a reasonable assumption to me, but if it's not a good assumption I agree that created and modified should return offset-naive datetimes.


Error: Building package sdl2:x86-windows failed with: BUILD_FAILED - VS2017 on Win7

c:\src\vcpkg>.\vcpkg install sdl2 curl
-- CURRENT_INSTALLED_DIR=C:/src/vcpkg/installed/x86-windows
-- DOWNLOADS=C:/src/vcpkg/downloads
-- CURRENT_PACKAGES_DIR=C:/src/vcpkg/packages/sdl2_x86-windows
-- CURRENT_BUILDTREES_DIR=C:/src/vcpkg/buildtrees/sdl2
-- CURRENT_PORT_DIR=c:/src/vcpkg/ports/sdl2/.
-- Using cached C:/src/vcpkg/downloads/SDL2-2.0.5.tar.gz
-- Testing integrity of cached file...
-- Testing integrity of cached file... OK
-- Extracting done
-- Applying patch C:/src/vcpkg/ports/sdl2/dont-ignore-default-libs.patch
-- Applying patch failed. This is expected if this patch was previously applied.
-- Applying patch C:/src/vcpkg/ports/sdl2/dont-ignore-default-libs.patch done
-- Configuring x86-windows-rel
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:14 (message):
Command failed: c:/src/vcpkg/downloads/cmake-3.8.0-rc1-win32-x86/bin/cmake.e
xe;C:/src/vcpkg/buildtrees/sdl2/src/SDL2-2.0.5;-DSDL_STATIC=OFF;-DSDL_SHARED=ON;
-DFORCE_STATIC_VCRT=OFF;-DLIBC=ON;-DBUILD_SHARED_LIBS=ON;-DCMAKE_CXX_FLAGS= /DWI
N32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP;-DCMAKE_C_FLAGS= /DWIN32 /D_WINDOWS /W3
/utf-8 /MP;-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON;-DCMAKE_FIND_PACKAGE_NO_PACKAGE
_REGISTRY=ON;-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON;-DBoost_COMPILER
=-vc140;-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE;-DCMAKE_VERBOSE_MAKEFILE=O
N;-DCMAKE_TOOLCHAIN_FILE=C:/src/vcpkg/triplets/x86-windows.cmake;-DCMAKE_CXX_FLA
GS_RELEASE=/MD /O2 /Oi /Gy /DNDEBUG /Zi;-DCMAKE_C_FLAGS_RELEASE=/MD /O2 /Oi /Gy
/DNDEBUG /Zi;-DCMAKE_SHARED_LINKER_FLAGS_RELEASE=/DEBUG /INCREMENTAL:NO /OPT:REF
/OPT:ICF;-DCMAKE_EXE_LINKER_FLAGS_RELEASE=/DEBUG /INCREMENTAL:NO /OPT:REF /OPT:
ICF;-G;Visual Studio 15 2017;-DCMAKE_BUILD_TYPE=Release;-DCMAKE_PREFIX_PATH=C:/s
rc/vcpkg/installed/x86-windows;-DCMAKE_INSTALL_PREFIX=C:/src/vcpkg/packages/sdl2
_x86-windows
Working Directory: C:/src/vcpkg/buildtrees/sdl2/x86-windows-rel
See logs for more information:
C:\src\vcpkg\buildtrees\sdl2\config-x86-windows-rel-out.log
C:\src\vcpkg\buildtrees\sdl2\config-x86-windows-rel-err.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_cmake.cmake:98 (vcpkg_execute_required_process)
ports/sdl2/portfile.cmake:50 (vcpkg_configure_cmake)
scripts/ports.cmake:73 (include)
Error: Building package sdl2:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: sdl2:x86-windows
Vcpkg version: 0.0.76-830c5eab4e49d5656d50cf6c613e9bbaf628f2f6
Additionally, attach any relevant sections from the log files above.
config-x86-windows-rel-out.log:
CMake Error at CMakeLists.txt:6 (project):
No CMAKE_C_COMPILER could be found.
config-x86-windows-rel-err.log:
-- The C compiler identification is unknown
-- Configuring incomplete, errors occurred!
See also "C:/src/vcpkg/buildtrees/sdl2/x86-windows-rel/CMakeFiles/CMakeOutput.log".
See also "C:/src/vcpkg/buildtrees/sdl2/x86-windows-rel/CMakeFiles/CMakeError.log".
CMakeOutput.log:
The system is: Windows - 6.1.7601 - x86
CMakeError.log:
Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
Compiler:
Build flags: ;/DWIN32;/D_WINDOWS;/W3;/utf-8;/MP
Id flags:
The output was:
1
Microsoft (R) Build Engine version 15.1.548.43366
Copyright (C) Microsoft Corporation. All rights reserved.
Build started 3/21/2017 4:19:34 PM.
Project "C:\src\vcpkg\buildtrees\sdl2\x86-windows-rel\CMakeFiles\3.8.0-rc1\CompilerIdC\CompilerIdC.vcxproj" on node 1 (default targets).
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Platforms\Win32\PlatformToolsets\v141\Toolset.targets(34,5): error MSB8036: The Windows SDK version 8.1 was not found. Install the required version of Windows SDK or change the SDK version in the project property pages or by right-clicking the solution and selecting "Retarget solution". [C:\src\vcpkg\buildtrees\sdl2\x86-windows-rel\CMakeFiles\3.8.0-rc1\CompilerIdC\CompilerIdC.vcxproj]
Done Building Project "C:\src\vcpkg\buildtrees\sdl2\x86-windows-rel\CMakeFiles\3.8.0-rc1\CompilerIdC\CompilerIdC.vcxproj" (default targets) -- FAILED.
Build FAILED.
"C:\src\vcpkg\buildtrees\sdl2\x86-windows-rel\CMakeFiles\3.8.0-rc1\CompilerIdC\CompilerIdC.vcxproj" (default target) (1) ->
(Desktop_PlatformPrepareForBuild target) ->
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Platforms\Win32\PlatformToolsets\v141\Toolset.targets(34,5): error MSB8036: The Windows SDK version 8.1 was not found. Install the required version of Windows SDK or change the SDK version in the project property pages or by right-clicking the solution and selecting "Retarget solution". [C:\src\vcpkg\buildtrees\sdl2\x86-windows-rel\CMakeFiles\3.8.0-rc1\CompilerIdC\CompilerIdC.vcxproj]
0 Warning(s)
1 Error(s)

Time Elapsed 00:00:00.95

Thanks for reporting this!
I've pushed 85169fa which should fix this issue by selecting a newer Windows SDK on Win7. Please let us know if this solves your issue!

Now I'm seeing different errors:
c:\src\vcpkg>.\vcpkg install sdl2 curl
Download cmake
No suitable version of cmake was found (requires 3.8.0 or higher). Download
portable version?
[Y] Yes  [N] No  [A] Always Allow Downloads  [?] Help (default is "Y"): y
Expected dependency downloaded path to be c:/src/vcpkg/downloads/cmake-3.8.0-rc1
-win32-x86/bin/cmake.exe, but was C:/src/vcpkg/downloads/cmake-3.8.0-rc1-win32-x
86/bin/cmake.exe
c:\src\vcpkg>.\vcpkg install sdl2 curl
-- CURRENT_INSTALLED_DIR=C:/src/vcpkg/installed/x86-windows
-- DOWNLOADS=C:/src/vcpkg/downloads
-- CURRENT_PACKAGES_DIR=C:/src/vcpkg/packages/sdl2_x86-windows
-- CURRENT_BUILDTREES_DIR=C:/src/vcpkg/buildtrees/sdl2
-- CURRENT_PORT_DIR=c:/src/vcpkg/ports/sdl2/.
-- Downloading http://libsdl.org/release/SDL2-2.0.5.tar.gz...
-- Downloading http://libsdl.org/release/SDL2-2.0.5.tar.gz... OK
-- Testing integrity of downloaded file...
-- Testing integrity of downloaded file... OK
-- Extracting source C:/src/vcpkg/downloads/SDL2-2.0.5.tar.gz
-- Extracting done
-- Applying patch C:/src/vcpkg/ports/sdl2/dont-ignore-default-libs.patch
-- Applying patch C:/src/vcpkg/ports/sdl2/dont-ignore-default-libs.patch done
-- Configuring x86-windows-rel
-- Configuring x86-windows-rel done
-- Configuring x86-windows-dbg
^C
c:\src\vcpkg>.\vcpkg install curl
-- CURRENT_INSTALLED_DIR=C:/src/vcpkg/installed/x86-windows
-- DOWNLOADS=C:/src/vcpkg/downloads
-- CURRENT_PACKAGES_DIR=C:/src/vcpkg/packages/zlib_x86-windows
-- CURRENT_BUILDTREES_DIR=C:/src/vcpkg/buildtrees/zlib
-- CURRENT_PORT_DIR=c:/src/vcpkg/ports/zlib/.
-- Downloading http://www.zlib.net/zlib-1.2.11.tar.gz...
-- Downloading http://www.zlib.net/zlib-1.2.11.tar.gz... OK
-- Testing integrity of downloaded file...
-- Testing integrity of downloaded file... OK
-- Extracting source C:/src/vcpkg/downloads/zlib1211.tar.gz
-- Extracting done
-- Configuring x86-windows-rel
-- Configuring x86-windows-rel done
-- Configuring x86-windows-dbg
^C
c:\src\vcpkg>.\vcpkg list
No packages are installed. Did you mean search?
c:\src\vcpkg>

-- Configuring x86-windows-rel done
-- Configuring x86-windows-dbg
^C

Did you experience a hang at that point and therefore killed the program? How long did you wait before killing it?
Could you look at the log files at buildtrees\sdl2\config-x86-windows-dbg-*.log and post the last dozen lines of them?

Yes, it hung at that point three times.  One of them sat for at least a half hour before I killed it.  Both of the -dbg-.logs are empty.

Hi @jwithers512 , thanks for reporting this issue!
Please open a new issue if this is still a problem for you.
Thx.


Typeblocking fails for some blocks

Describe the bug

From the forum: The any component blocks do not appear to work with typeblocking. The for each element in list block also does not appear.
Affects

[ ] Designer
[x] Blocks editor
[ ] Companion
[ ] Compiled apps
[ ] Buildserver
[ ] Debugging
[ ] Other... (please describe)

Expected behavior

All blocks should be instantiable via typeblocking.
Steps to reproduce

Attempt to create any component blocks using typeblocking. The string will not include any information about the target event name (see the post for details).

@ewpatton Typeblocking for block `for each number from is also not working properly.

@ewpatton, sure I would like to work on this can you please assign it to me?

Fixed by #2586


feat(ingestion/powerbi): Ingest datasets not used in PowerBI visualization(tiles/pages)

Merging because these changes aren't related to the kafka build


can BEGAN for imagenet dataset ? who have train this, i want to say, the results that i train is very bad!

who can tell me how to train BEGAN on ImageNet datasets? thanks a lot!

what image dimensions are you using?


Bug: see doubble Post while posting

check if only local or also on server

Looks like the bug is fixed.


Subgraph title characters are too restricted

Things I tried* with the subgraph title that didn't work:

subgraph new
line - prints subgraph new
line
subgraph some (text) - syntax error
subgraph "some (text)" - syntax error
subgraph some (text) - syntax error
subgraph "some (text)" - syntax error

* mermaid live editor 8.0.0-rc.8
I also couldn't find much documentation about subgraphs other than the few examples.

The examples with quotes work now (try
subgraph "some (text)"
subgraph "some #40;text#41;" (I removed the ampersands as they are not needed in mermaid's DSL and will be shown as characters in the label)
https://mermaidjs.github.io/mermaid-live-editor/#/edit/eyJjb2RlIjoiZ3JhcGggTFJcbnN1YmdyYXBoIFwic29tZSAjNDA7dGV4dCM0MTtcIlxuQS0tPkNcbmVuZCIsIm1lcm1haWQiOnsidGhlbWUiOiJkZWZhdWx0In19


Overrides field should not be capitalized in yaml serialization

This should be overrides when serialized, per: https://github.com/kubernetes/community/blob/master/contributors/devel/api-conventions.md#naming-conventions

@pmorie, does this issue still exist? otherwise can you close this.

This was fixed by https://github.com/kubernetes-sigs/federation-v2/commit/ada272855ee5155491e97a98eeef3baa54c202a3.


[nodedocs.css - personal changes]

I made some simple changes to nodedocs.css in my fork . Perhaps it is worth sharing a couple.
Basically I changed the header, toc > ul, breadcrumbs position to fixed and the header, breadcrumb, breadcrumbs opacity.
header {
opacity: 0.95; /* modfied /
color: #eee;
font-family: 'typewriter';
width: 100%;
position: fixed; / modfied */
top: 0px;
height: 50px;
background-color: #333;
box-shadow: -2px 0px 5px #444;
z-index: 3;
}
#toc > ul {
text-transform: capitalize;
background-color: #fff;
padding-top: 20px;
position: fixed; /* modfied */
left: 0px;
min-height: 1000px;
top: 50px;
width: 190px;
box-shadow: 3px -10px 5px #ccc;
webkit-box-shadow: 3px -10px 5px #ccc;
z-index: 2;
}
.breadcrumb {
padding-right: 20px;
font-weight: bold;
font-size: 14px;
background: transparent url('../img/crumbtrail.png') no-repeat scroll center right;
margin-right: 10px;
opacity: 0.2; /* modfied */
}
.breadcrumbs {
position: fixed; /* modfied /
right: -5px;
top: 60px;
padding: 6px;
background-color: #fff;
opacity:0.8; / modfied */
}
/* included */
.breadcrumbs a:hover {
color: black;
opacity: 1;
}

@massimiliano-giroldi do you have a commit I can pull in? That's easiest for me, and then you get the credit right?

The changes are in nodedocs.css file.
public (and so public/css/nodedocs.css) is in .gitignore .
I don't think I can just change the .gitignore (delete the 'public' entry).
Do you have a suggestion?

Actually: Have you looked at themes/css/nodedocs.css ? I don't know if that gets auto-copied or not, but that's where your changes should go.

You are absolutely right. I sent a (conservative) pull request for changes.

Awesome! We'll review it when time permits.


Fix console warnings

Fixes #713
Fixes #652

Deploy preview for govuk-react processing.
Building with commit 8dc5a6e49d4989f77e4e627581f3e3f4e6b671c9
https://app.netlify.com/sites/govuk-react/deploys/60a02e13fdf4a500089f757f

Codecov Report

Merging #782 (e597b79) into master (0180b0a) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #782   +/-   ##
=======================================
  Coverage   99.30%   99.30%
=======================================
  Files         121      121
  Lines         861      864    +3
  Branches      248      248
=======================================
+ Hits          855      858    +3
  Misses          6        6

Impacted Files
Coverage Δ

components/top-nav/src/index.js
89.47% <ø> (ø)

components/button/src/index.js
100.00% <100.00%> (ø)

components/link/src/index.js
100.00% <100.00%> (ø)

components/visually-hidden/src/index.js
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Fix fallout from https://github.com/opentracing/basictracer-go/pull/36

Apparently this needs a rebuild without cache, since circle has cached the old version of basictracer-go.

Thank you!
(Insert rant about the state of vendoring for small packages in Go)

Indeed.

Blargh... I'm in an airplane using my phone and GH won't allow mobile browser merges when the tests are failing.

If you can get into circle CI and trigger a rebuild without cache you might be able to work around.

Spoofed my browser :)
Thanks again.


issue with lighting off

Hey,
I've noticed some rendering issues with the lighting turned off when tilting the camera. Seems like it affects the example code aswell.
 I wasn't able to locate the origin of this in the code.
Any ideas? Thank you!
Tibor

Hi Tibor! Good bug, I almost forget that globe has no lighting pass)) I've got the problem. I'll try to fix it with next release.

Fixed with https://github.com/openglobus/openglobus/releases/tag/v0.4.3


Scope organization specific controllers under organization

We set the tenant in app/controllers/organizations/base_controller.rb using OrganizationScopable. The controllers scoped under controllers/organizations inherit from Organizations::BaseController. This means the logic in these controllers is executed in the tenant scope, e.g., calling Task.all will return all tasks for current organization only. This helps to keep data secure between organizations.
We have some routes/controllers that are used to create common Organization workflows, but they are not currently scoped under Organization. This is not ideal because it means that calling resources in these controllers could return all records from all organizations (e.g., Task.all will return all tasks from all orgs), presenting a risk of data bleeding. So, we need to move these routes, controllers under the organization scope.
Acceptance criteria:

move the list of controllers and associated routes (not crossed out) below into controllers/organizations and inherit from Organizations::BaseController instead of ApplicationController
Rename the classes appropriately for their new scope
Fix tests (renaming)

I'd like to work on this.

All yours @jmilljr24


Feature flags as VDU Variables

We have test/feature flags in the VDP, which are essentially 16-bit identifiers, with 16-bit values.
RISC OS systems had "VDU variables" which would be changed by various commands, and could be read back to find the current VDU state
Our flags are essentially a form of "VDU variable", but right now they are only used for an incredibly limited set of feature switching, and are effectively, from a user-software point of view, currently write-only.
If our flags become read-write (see #263 ) then they become more like a true variable, and so we should consider more closely aligning our use of feature flags with how Acorn did VDU Variables.  There are various other areas of VDP settings that could be useful to be able to expose, for instance #196.

Documentation on RISC OS VDU Variables can be found here: https://www.riscosopen.org/wiki/documentation/show/VDU Variables

RISC OS VDU Variables use an 8-bit identifier.  We could, potentially, copy their setup, setting the high-byte to a fixed value
Most of the values that RISC OS exposes have equivalents within the VDP, often in the current graphics context, with the exception of those that are more hardware-specific.
In RISC OS, values are 32-bit words.  None really need to be (except for variables that return an address, but those aren't relevant to us)


closing more info on trips window closes respective place in results (not the other way around)

have a presaved trip
load it on page load
search up a term that loads a place on that trip
open more info on that place in both windows
close more info in trip window

closes more info in result
open both again
close more info in result window
does not close more info in trip


Bug fix: particles sourced on cell boundaries

In the updated CSG functions a particle is lost error occurred if a particle was sourced exactly on a cell boundary. In standard Monte Carlo, this bug may never surface but samples in iQMC hit these boundaries quite often.
In short, replacing = with <= in region_check() returns the same cell ID  as was calculated before the updates.

Thanks @spasmann you rock!!!!!!!!


vSphere Parameter Update

vSphere provider for Terraform seems to use custom_configuration_parameters instead of configuration_parameters now. Reference is here. Also, I can't find any information about the connection arguments. Is this still valid?

That matches the docs! @chrislovecnm?

@siddharthist I just went through this with terraform.py too, it worked for me with vSphere6 and Terraform! Also love the Github handle. :+1:

@rossedman Thanks for your efforts! We just need someone with a little more vSphere knowledge to review and we'll merge ASAP :)

There are a few more tweaks as well with the changes. Traveling will comment next week.

Actually have a couple of minutes to comment.
We need a few more tweaks including:
provider "vsphere" {
  user           = "${var.vsphere_user}"
  password       = "${var.vsphere_password}"
  vcenter_server = "${var.vcenter_server}"
}

But we also may need to modify terraform.py.  See: https://github.com/chrislovecnm/microservices-infrastructure/commit/9e301f73e4198cd27adba7d04d8229e4529d0817#diff-6a5dab50836db01e702f478b8820b7c1
@rossedman I was planning a pull very earily next week.  Need to do some smoke testing.  Sorry for the delay.

@chrislovecnm Yeah, I made some commits to terraform.py yesterday that were tested and committed. I will look into this more and provide some additional commits to the PR. Any advice or anything else you want added just say the word and I'll do my best.

@rossedman appreciate the help! You can look at the tweaks that I made on my branch, but I don't think we need many modifications.  I have documentation already written, https://github.com/chrislovecnm/microservices-infrastructure/commit/dd483e268e66614f298c60fefc6608309195f086  which you can snag, or I can submit a PR with afterwards.
Again the help is appreciated greatly!

@chrislovecnm :+1: Awesome. Sounds good!

@chrislovecnm Should I go ahead and close this or do you need me to do some merges from what you have? Just realized this was still open.

@rossedman @chrislovecnm I'd like to get this merged. What do we need to do?

@stevendborrelli - I just added a couple of comments to @rossedman's work.  Otherwise it is pretty much ready to merge.  @rossedman questions?

@stevendborrelli @chrislovecnm Sorry I misunderstood original comments, but looking back not sure why. I guess I thought these would be merged into chris' branch for a full PR, but however you guys want to proceed I will follow your lead. I can make another commit with updates as well. Did the build fail only because of lack of tests or was something tripped?

@rossedman Don't worry about the CI build for now, the Jenkins builds almost always fail.

I'm going to merge this for now, and we'll wait on @chrislovecnm's PR for later.

@siddharthist Sorry for the delay! I've been getting crushed at work. Thanks for doing this.


Reduce compile time for single-device and multi-device recipes

Context
What is the purpose of this PR? Is it to

[ ] add a new feature
[ ] fix a bug
[ ] update tests and/or documentation
[x] other (improve compile time)

Improvements in compile time (on my A100 machine):
Llama3 8B QLoRA single-device: 83s -> 47s (-43%)
Llama3 8B full-finetune single-device: 29s -> 20s (-31%)
Llama3 70B QLoRA FSDP2: 104s -> 62s (-40%)
Changelog

No nested FSDP wrapping for LoRALinear, to reduce some recompiles.
mark_dynamic for each layer's input h, to avoid dynamic sequence length induced recompiles.
mark_dynamic for loss_fn inputs (logits and labels), to avoid dynamic sequence length induced recompiles.

Test plan
TODO (mentioned by Evan):

we have CI for our recipes to make sure loss values don't change, we could add something like this to the recipe test: https://fburl.com/pusfwz1n, since we don't have it for our FSDP2 recipe yet
How about just a stripped-down version of my test from https://github.com/pytorch/torchtune/pull/1419? Basically run for 1-2 models and show that memory and perf look good; I guess you already have compile time covered. Just paste in the memory and toks/sec into the PR desc.

Please make sure to do each of the following if applicable to your PR. (If you're not sure about any one of these just ask and we will happily help. We also have a contributing page for some guidance on contributing.)

[ ] run pre-commit hooks and linters (make sure you've first installed via pre-commit install)
[ ] add unit tests for any new functionality
[ ] update docstrings for any new or updated methods or classes
[ ] run unit tests via pytest tests
[ ] run recipe tests via pytest tests -m integration_test
[ ] manually run any new or modified recipes with sufficient proof of correctness
[ ] include relevant commands and any other artifacts in this summary (pastes of loss curves, eval results, etc.)

UX
If your function changed a public API, please add a dummy example of what the user experience will look like when calling it.
Example of docstring: https://github.com/pytorch/torchtune/blob/6a7951f1cdd0b56a9746ef5935106989415f50e3/torchtune/modules/vision_transformer.py#L285
Example in our docs: https://pytorch.org/torchtune/main/tutorials/qat_finetune.html#applying-qat-to-llama3-models

[ ] I did not change any public API;
[ ] I have added an example to docs or docstrings;

@yf225 , i have just landed the chunked CE. In that PR, i also changed the shift logic:
# Shift so that tokens < n predict n
logits = logits[..., :-1, :].contiguous()
labels = labels[..., 1:].contiguous()
logits = logits.transpose(1, 2)

and added chunking to the transformer + CE loss. I would be glad to help with testing the dynamic flags with you, if you need help.


Javascript Error on InteractiveImage

Hi,
I'm just starting to play around with datashader following one of your notebooks from the webinar and am getting the error below.  My dataframe has about 10 mil points, floating point, no nans.  This is run in a notebook as in the webinar.  I'm running 2.7, datashader-0.1.0, bokeh-0.11.1, MacOSX.  Many thanks!  Evan
p = figure(
x_range=(0, 1),
y_range=(0, 1),
tools='pan,wheel_zoom,box_zoom,reset',
plot_width=500,
plot_height=500,
)
pipeline = ds.Pipeline(df, ds.Point("s3", "modscag"))
InteractiveImage(p, pipeline)
TypeError: Cannot read property '$' of undefined
at Array.inline_js (eval at  (http://localhost:8889/static/notebook/js/main.min.js?v=40e10638fcf65fc1c057bff31d165e9d:89:4231), :54:14)
at run_inline_js (eval at  (http://localhost:8889/static/notebook/js/main.min.js?v=40e10638fcf65fc1c057bff31d165e9d:89:4231), :67:21)
at eval (eval at  (http://localhost:8889/static/notebook/js/main.min.js?v=40e10638fcf65fc1c057bff31d165e9d:89:4231), :77:9)
at eval (eval at  (http://localhost:8889/static/notebook/js/main.min.js?v=40e10638fcf65fc1c057bff31d165e9d:89:4231), :11:67)
at Array.forEach (native)
at run_callbacks (eval at  (http://localhost:8889/static/notebook/js/main.min.js?v=40e10638fcf65fc1c057bff31d165e9d:89:4231), :11:38)
at load_libs (eval at  (http://localhost:8889/static/notebook/js/main.min.js?v=40e10638fcf65fc1c057bff31d165e9d:89:4231), :23:9)
at eval (eval at  (http://localhost:8889/static/notebook/js/main.min.js?v=40e10638fcf65fc1c057bff31d165e9d:89:4231), :77:7)
at eval (eval at  (http://localhost:8889/static/notebook/js/main.min.js?v=40e10638fcf65fc1c057bff31d165e9d:89:4231), :82:4)
at eval (native)

What happens if you just call the pipeline object directly, as in
pipeline(x_range=None,y_range=None, width=300, height=300)?

Then the static image draws as I would expect.

Yet InteractiveImage works fine for you on the example notebooks, just not on your own data as here?

It does, but if I copy and paste the failing code into the example notebook it works, so seems something is wrong on my end.  Apologies!


Fix Rancher 2.0 support for the Stolon chart

What this PR does / why we need it:
This PR fixes functionality with Rancher and basically just mirrors what lwolf/stolon-chart which this chart is based upon has already done. It comments out replicationPassword and ``superuserPassword` to fix compatibility with Rancher's answers. Rancher does not seem to like it when a value is empty and for some reason refuses to replace it with the answers it's given in their UI.
Accommodating this it also generates a 40 character long alpha numeric if the passwords are not set, as lwolf does.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
There has been no issue submitted about this on this repository but this commit fixes Rancher compatibility with Rancher's answers functionality that fills in values. lwolf recently fixed this in his repository and I thought I'd apply it here as well.

/check-cla

/assign @mgoodness


Android crashes when dynamically setting tabBarBadge

Before submitting a new issue

[X] I tested using the latest version of the library, as the bug might be already fixed.
[X] I tested using a supported version of react native.
[X] I checked for possible duplicate issues, with possible answers.

Bug summary
I am experiencing an Android crash when setting a tabBarBadge dynamically.
I am using react-native-edge-to-edge and its Expo plugin to set the Material theme as per the instructions:
 ['react-native-edge-to-edge', { android: { parentTheme: 'Material3' } }]

Library version
0.7.3
Environment info
System:
  OS: macOS 14.6.1
  CPU: (12) arm64 Apple M3 Pro
  Memory: 268.52 MB / 36.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.11.0
    path: ~/.nvm/versions/node/v20.11.0/bin/node
  Yarn:
    version: 1.22.22
    path: ~/.nvm/versions/node/v20.11.0/bin/yarn
  npm:
    version: 10.2.4
    path: ~/.nvm/versions/node/v20.11.0/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /usr/local/bin/watchman
Managers:
  CocoaPods:
    version: 1.16.2
    path: /Users/raulgomezacuna/.rbenv/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.1
      - iOS 18.1
      - macOS 15.1
      - tvOS 18.1
      - visionOS 2.1
      - watchOS 11.1
  Android SDK:
    API Levels:
      - "23"
      - "26"
      - "27"
      - "28"
      - "29"
      - "30"
      - "31"
      - "33"
      - "34"
      - "35"
    Build Tools:
      - 28.0.3
      - 29.0.2
      - 29.0.3
      - 30.0.2
      - 30.0.3
      - 31.0.0
      - 33.0.0
      - 33.0.1
      - 33.0.2
      - 34.0.0
      - 35.0.0
    System Images:
      - android-29 | Google APIs Intel x86 Atom
      - android-29 | Google Play Intel x86 Atom
      - android-30 | Google APIs Intel x86 Atom
      - android-33 | Google APIs Intel x86_64 Atom
      - android-34 | ARM 64 v8a
      - android-34 | Google Play ARM 64 v8a
    Android NDK: Not Found
IDEs:
  Android Studio: 2024.1 AI-241.15989.150.2411.11948838
  Xcode:
    version: 16.1/16B40
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.5
    path: /usr/bin/javac
  Ruby:
    version: 3.1.4
    path: /Users/raulgomezacuna/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 15.1.2
    wanted: ^15.1.2
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.76.2
    wanted: ^0.76.2
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: true
  newArchEnabled: true

Steps to reproduce

Cold start the app
Wait x seconds (like with setTimeout for instance)
Crash happens when setting a badge and previously there wasn't any

Reproducible sample code
import { createNativeBottomTabNavigator } from '@bottom-tabs/react-navigation';
import {ExploreScreen, NotificationsScreen} from '@screens';
import { useTheme } from 'react-native-paper';

const Tab = createNativeBottomTabNavigator();

const TabNavigator = () => {
  const { colors } = useTheme();
  const [badge, setBadge] = useState<string | undefined>(undefined);

  useEffect(() => {
    setTimeout(() => {
      setBadge('3');
    } , 3000);
  }, []);

  return (
    <Tab.Navigator
      labeled
      barTintColor={colors.surface}
      tabBarActiveTintColor={colors.tertiary}
    >
      <Tab.Screen
        name="Explore"
        component={ExploreScreen}
        options={{
          title: 'Explore',
          tabBarActiveTintColor: colors.tertiary,
          tabBarIcon: ({ focused }) =>
            focused
              ? require('./assets/magnify-expand.png')
              : require('./assets/magnify.png'),
        }}
      />
      <Tab.Screen
        name="Notifications"
        component={NotificationsScreen}
        options={{
          title: 'Notifications',
          tabBarIcon: ({ focused }) =>
            focused
              ? require('./assets/bell.png')
              : require('./assets/bell-outline.png'),
          tabBarActiveTintColor: colors.tertiary,
          tabBarBadge: badge,
        }}
      />
    </Tab.Navigator>
  );
};

export default TabNavigator;

Thanks for reporting the issue, it looks like it's related to edge-to-edge theme.
Can you test if it happens with the built in config plugin?

No problem!
The crash still happens after uninstalling react-native-edge-to-edge and using the built-in config plugin.
I have also disabled the new arch. This time the error screen seems slightly different though:

Thanks for confirming it's not react-native-edge-to-edge, I will look into this

Hey!
Can you check what value is inside of your android/app/src/main/res/values/styles.xml?
It should look something like this: <style name="AppTheme" parent="Theme.Material3.DayNight.NoActionBar">
I couldn't reproduce the issue:
https://github.com/user-attachments/assets/9c3c76c7-3aae-4e80-b28d-efda3622abb9
If the issue persists please create a reproduction repository.

I ended up implementing my own Tabs to have more customisation options. I'll close the issue!


Expand Filesytem on 1st Boot of Image

This thread has some good info on a way to solve this:
Automatic Expand Filesystem after cloning a Rasbian image


fix crash in TdsSendTypeNVarchar for nvarchar(max)

Description
Previously, there was an issue in handling nvarchar(max) and varchar(max) in the code. Specifically, when dealing with atttypmod with a value of -8000 (representing TSQLMaxTypmod) in the PrepareRowDescription function for nvarchar and varchar, an incorrect value of atttypmod was being passed to the SetColMetadataForCharType function. This resulted in setting an incorrect maxSize for the column metadata entry.
For nvarchar(max), the atttypmod was -8000, causing the PrepareRowDescription function to pass -16008 to SetColMetadataForCharType. Internally, this negative value gets converted to 49528 as an unsigned int. Because of this if we assign a long string value to a nvarchar(max) variable with a length such that UTF16 output size is more than 49528 it will throw a FATAL log elog(FATAL, "UTF16 output of varchar/bpchar exceeds max length");
Issues Resolved
BABEL-4547
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Looks like this is a common issue for varbinarytypmodin, bpchartypmodin and varchartypmodin but you have fixed only n/varchar

We dont need tests to test these changes??

Added test cases


Remove PhysicalCPUs

This is the total number of physical CPUs (one physical CPU per socket) and is not the same as number of cores.

The official document is https://www.ogf.org/documents/GFD.147.pdf
There is also our unofficial html version http://glue20.web.cern.ch/glue20


Bug with UpdateDeviceShadow

Greetings :)!
I am building a project using this SDK and I have problem ... When I try to use the "UpdateDeviceShadow" method of the "Shadow" class the program responds with a "Segmentation fault" if you are not yet connected and subscribed to the device topics in the service.
I mean, if I first connect to the service and subscribe to the topics, I can use "UpdateDeviceShadow", however,  if I do not this in advance the library dies.
This is a problem because sometimes you would like to work offline, that is, if my device starts and tries to connect to the internet and can not, it could load the last known state of the device (which can be stored in a file) and work with it, and once it manages to connect to the internet then it updates its status with the most recent.
That is exactly what is happening to me, sometimes I do not have internet when I start the device, so the device load the last known state using a file and call "UpdateDeviceShadow" to work in a kind of "disconnected mode", but currently this is not possible.
Thanks a lot!

EDIT: I can fixed this moving the initialization of some classes prior to the connection.


update dependencies and add compat

add compat entries
update dependencies

Codecov Report

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

:exclamation: Current head 656a65e differs from pull request most recent head 1104030. Consider uploading reports for the commit 1104030 to get more accurate results

@@           Coverage Diff           @@
##             main      #47   +/-   ##
=======================================
  Coverage        ?   55.67%
=======================================
  Files           ?       21
  Lines           ?     2098
  Branches        ?        0
=======================================
  Hits            ?     1168
  Misses          ?      930
  Partials        ?        0

Continue to review full report at Codecov.

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


Add "repeat" option to "sigh test".

Have to emulate currently, with unnecessary overhead for each run and no built-in summary of pass/fail, via something like:
'for i in `seq 10`; do ./tools/sigh test --grep='demo'; done'
@mmandlis @dstockwell

I think we can mark this done.  You can run a large number of tests to determine flakiness and you get a summary of output.  Thanks so much @thebrianchen


IconButton ink splash should use the color of the button

IconButton's ink splash should use the color of the button for drawing the ink splash. See current behavior vs spec below.
Test case in: /examples/material_gallery/lib/demo/buttons_demo.dart

Spec:

Is this only for icon buttons or does this affect other sorts of material buttons?

I've only seen it for the icon buttons

that picture is toggle buttons, not icon buttons. we don't yet implement those. I actually haven't found spec text for icon buttons per se.

I am closing this on the basis that I cannot support the claim presented, as noted above.


registryfs.cpp: getActualUrl

/home/runner/work/overlaybd/overlaybd/src/overlaybd/registryfs/registryfs.cpp:241|getActualUrl:Failed to get actual url [url=http://<IP_ADDRESS>:19145/v2/library/redis/blobs/sha256:c62d96ea337990a7cd656edc1a4f4f0d2e0ca460bcda50358a8e40967e8e011f][ret=404]
l am using a simple registry which only handles  basic requests, such as manifests and blobs. So,  how to close this features?

@qi0523  ret=404 means the corresponding blob does not found. what registry did you use?

@liulanzheng i use p2p mode to download blobs. <IP_ADDRESS>:19145 is the upstream endpoint. The downstream failed due to performing getActualUrl first.

@HileQAQ  Please follow up this issue about p2p.

@qi0523 What is the result if you ping http://<IP_ADDRESS>:19145/v2/library/redis/blobs/sha256:c62d96ea337990a7cd656edc1a4f4f0d2e0ca460bcda50358a8e40967e8e011f?


react-native-fast-image Fails

Followed below steps:
npm i react-native-fast-image --save
npm link
and when I run app I get below error
" (0 , _react.forwardRef) is not a function "

same issue "react-native": "0.59.6" android

@pavankumarkl upgrade your react to v16.6.0

Same here, but with react.memo instead of react.forwardRef. @romreed 's solution worked for me.

after update react to 16.6.0, its work!
thanks to @romreed comment

RNFI only targets the latest version of React Native, which has an associated React version.
You will need to upgrade to a version of React later than 16.8.3.

thanks for your reply
@dylanvann
On Fri, 26 Apr, 2019, 8:02 AM Dylan Vann<EMAIL_ADDRESS>wrote:

RNFI only targets the latest version of React Native, which has an
associated React version.
You will need to upgrade to a version of React later than 16.8.3.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/DylanVann/react-native-fast-image/issues/448#issuecomment-486903691,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEMV7Q4LT64FHN3W2IDY3QLPSJSSBANCNFSM4HG3XZ6Q
.

@AlcuinGuest I am still getting this error.
"react": "^16.6.0",
"react-native-fast-image": "^5.2.0",
"redux": "^4.0.0",
"react-redux": "^5.0.7",
"react-native": "0.57.2",