OpenFL 4.x rendering problem on iPhone 6s plus when allow-high-dpi is true

Recently, I am updating my openfl project to 4.x. But rendered graphic is smaller than before on iPhone 6 Plus and stays in the lower-left corner of the screen. I tried the PiratePig from the openfl-samples and got the same result.
But there is no problem when the games were running on iOS simulators.

Update: When <window allow-high-dpi="false"/> is set, there is no problem except for poor graphics quality.

Update: This issue is still unresolved in OpenFL 4.4.1 / Lime 3.4.1.
This issue make the iOS target almost useless. :sad:

I have not been able to reproduce this. Could you remove the app from your device, then try and install again? What version of Xcode are you using?

I have tried to completely remove and reinstall the app and also tried different iOS devices.
The testing results are listed below.
Building Environment:

Xcode: 8.1
IPHONE_VER in .hxcpp_config.xml: 10.1
OpenFL: 4.4.1
Lime: 3.4.1
Command Line: openfl update -clean ios

Results:

iPhone 6s Plus: not ok
iPhone 5s: ok
iPad Pro: ok
iPhone 6s Plus simulator: ok
iPhone 6s simulator: ok
iPad Air simulator: ok

Maybe it is related to screen rendering scale factors. The scale factor for iPhone 6s Plus is 3 (https://www.paintcodeapp.com/news/iphone-6-screens-demystified).
What iOS device are you using? @jgranick

@jgranick I'm happy to dig the problem deeper. Would you like to give me some suggestions on where to start with? I have developed in C++ for over 10 years and made a mobile game (iOS/Android) with OpenFL 3.x legacy.

The first question (I think) is if we are getting the correct events from SDL.
You could listen to stage.addEventListener (Event.RESIZE, function (event) { trace (stage.stageWidth, stage.stageHeight)); from OpenFL, or stage.window.onResize.add (function (width, height) trace (width, height)); for the Lime event.
I think that maybe this is not coming through, since we handle resize events in the "PiratePig" sample.
This is where SDL events come in:
https://github.com/openfl/lime/blob/develop/project/src/backend/sdl/SDLApplication.cpp#L109
I wonder if the issue is that the GL context is resized, but that we are not receiving the event, or if the size is reported incorrectly, or perhaps there is a chance that SDL is doing the right thing, but we handling it wrong somehow.
A little more investigation should help. My wife's iPhone 6 just stopped working, so I don't have anything to test with here (currently)

Thanks for your suggestions. I'll investigate the problem this weekend.

I have found the problem in Lime.
https://github.com/openfl/lime/blob/develop/project/src/backend/sdl/SDLRenderer.cpp#L142
double scale = outputWidth / width;
should be
double scale = double(outputWidth) / width;
The correct scale for iPhone 6(s) Plus is 2.608696. Without type casting, the division operation was be an integer division, the result was 2.

I have created a pull request in openfl/lime. @jgranick

Awesome, thank you 😁


Put https://makecode.microbit.org/pkg/LaboratoryForPlayfulComputation/pxt-blockytalkybluetooth/ as web site of repo

GitHub as a feature to associate a web site,
https://makecode.microbit.org/pkg/LaboratoryForPlayfulComputation/pxt-blockytalkybluetooth/
is the rendering of the README file.

@pelikhan I made the website reference our descriptive website here: http://www.playfulcomputation.group/blockytalkyble.html
Any objections?

Sounds good.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Ben Shapiro<EMAIL_ADDRESS>Sent: Friday, November 10, 2017 7:35:05 AM
To: LaboratoryForPlayfulComputation/pxt-blockytalkybluetooth
Cc: Peli de Halleux; Mention
Subject: Re: [LaboratoryForPlayfulComputation/pxt-blockytalkybluetooth] Put https://makecode.microbit.org/pkg/LaboratoryForPlayfulComputation/pxt-blockytalkybluetooth/ as web site of repo (#5)
@pelikhanhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpelikhan&data=02|01|jhalleux%40microsoft.com|d2ee7b925ab84294144b08d528509e59|72f988bf86f141af91ab2d7cd011db47|1|0|636459249081979336&sdata=D4aWV%2BbqhXu6%2FoEgqNBV3OIqqVvnMAZm0%2FqHia0t7eI%3D&reserved=0 I made the website reference our descriptive website here: http://www.playfulcomputation.group/blockytalkyble.htmlhttps://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.playfulcomputation.group%2Fblockytalkyble.html&data=02|01|jhalleux%40microsoft.com|d2ee7b925ab84294144b08d528509e59|72f988bf86f141af91ab2d7cd011db47|1|0|636459249081979336&sdata=vUMYERRYIP1TZXXnYA7z978gXHZrkoct8kV4dULWv1s%3D&reserved=0
Any objections?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FLaboratoryForPlayfulComputation%2Fpxt-blockytalkybluetooth%2Fissues%2F5%23issuecomment-343505101&data=02|01|jhalleux%40microsoft.com|d2ee7b925ab84294144b08d528509e59|72f988bf86f141af91ab2d7cd011db47|1|0|636459249081979336&sdata=IE%2FRH5wD5VPrXBKwbInoCSOfxsi8Ad5MRfeUbVKYu3E%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAD-4KQ90LNLwJtHfQjjTPt2vpF9cpV8Jks5s1G0pgaJpZM4QZrFA&data=02|01|jhalleux%40microsoft.com|d2ee7b925ab84294144b08d528509e59|72f988bf86f141af91ab2d7cd011db47|1|0|636459249081979336&sdata=K1GzFjoEdEp5KSBpiWks9%2BEM%2BtRfJ%2B0%2BtiZsU5GuuGQ%3D&reserved=0.


[Bug Report] RescaleAction wrapper does not change the action_space accordingly

Describe the bug
The RescaleAction wrapper in (gymnasium.wrappers.rescale_action) does not change the action_space accordingly.
In contrast, the RescaleAction wrapper in gym.wrappers.rescale_action does!
When I compare both implementations, the following lines are missing in the gymnasium variant compared to the gym variant.
self.action_space = spaces.Box(
    low=min_action,
    high=max_action,
    shape=env.action_space.shape,
    dtype=env.action_space.dtype,
)

This looks like a bug to me.
Code example
import gymnasium as gym
#import gym

env = gym.make("Pendulum-v1")
env = gym.wrappers.rescale_action.RescaleAction(env, min_action=-1, max_action=1)

print(env.action_space)
# gymnasium-->Box(-2.0, 2.0, (1,), float32)
# gym --> Box([-1.], [1.], (1,), float32)

System info
gymnasium: 0.28.1 (pip)
gym: 0.21.0 (pip)
python: 3.7
Ubuntu 20.04
Additional context
No response
Checklist

[X] I have checked that there is no similar issue in the repo

Thanks, this is also fixed in the experimental version of the wrapper, experimental.wrappers.RescaleActionV0


fix: upgrade to version 3.1.24

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign rajdavies
You can assign the PR to them by writing /assign @rajdavies in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
7c7d3db599f89f81cb30bbcd942f5afa36fc4cbf
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
7c7d3db599f89f81cb30bbcd942f5afa36fc4cbf
link
/test vault

gsm
7c7d3db599f89f81cb30bbcd942f5afa36fc4cbf
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
7c7d3db599f89f81cb30bbcd942f5afa36fc4cbf
link
/test vault

gsm
7c7d3db599f89f81cb30bbcd942f5afa36fc4cbf
link
/test gsm

tls
7c7d3db599f89f81cb30bbcd942f5afa36fc4cbf
link
/test tls

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


CB-13870 change default from UAP to 10.0

What does this PR do?
... which means the same but works for check_reqs as well.
This is an "update" to https://github.com/apache/cordova-windows/pull/241
What testing has been done on this change?
Manual installation as platform and ran cordova requirements successfully:
C:\Projects
λ cd "Cordova Projects\

C:\Projects\Cordova Projects
λ cordova create windowsMaster2
Creating a new cordova project.

C:\Projects\Cordova Projects
λ cd windowsMaster2

C:\Projects\Cordova Projects\windowsMaster2<EMAIL_ADDRESS>λ cordova platform add https://github.com/apache/cordova-windows#master
Using cordova-fetch for https://github.com/apache/cordova-windows#master
Warning: using prerelease platform<EMAIL_ADDRESS>Use 'cordova platform add windows@latest' to add the latest published version instead.
Adding windows project...
Creating Cordova Windows Project:
        Path: platforms\windows
        Namespace: io.cordova.hellocordova
        Name: HelloCordova
Windows project created with<EMAIL_ADDRESS>Discovered plugin "cordova-plugin-whitelist" in config.xml. Adding it to the project
Installing "cordova-plugin-whitelist" for windows
Adding cordova-plugin-whitelist to package.json
Saved plugin info for "cordova-plugin-whitelist" to config.xml
--save flag or autosave detected
Saving windows@https://github.com/apache/cordova-windows#master into config.xml file ...

C:\Projects\Cordova Projects\windowsMaster2<EMAIL_ADDRESS>λ cordova requirements

Requirements check results for windows:
Windows OS: not installed
Error: Cannot read property 'os' of undefined
(node:11008) UnhandledPromiseRejectionWarning: CordovaError: Some of requirements check failed
    at C:\nvm\v9.4.0\node_modules\cordova\src\cli.js:414:27
    at _fulfilled (C:\nvm\v9.4.0\node_modules\cordova\node_modules\cordova-lib\node_modules\q\q.js:787:54)
    at self.promiseDispatch.done (C:\nvm\v9.4.0\node_modules\cordova\node_modules\cordova-lib\node_modules\q\q.js:816:30)
    at Promise.promise.promiseDispatch (C:\nvm\v9.4.0\node_modules\cordova\node_modules\cordova-lib\node_modules\q\q.js:749:13)
    at C:\nvm\v9.4.0\node_modules\cordova\node_modules\cordova-lib\node_modules\q\q.js:557:44
    at flush (C:\nvm\v9.4.0\node_modules\cordova\node_modules\cordova-lib\node_modules\q\q.js:108:17)
    at process._tickCallback (internal/process/next_tick.js:150:11)
(node:11008) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:11008) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

C:\Projects\Cordova Projects\windowsMaster2<EMAIL_ADDRESS>λ cordova platform rm windows
Removing platform windows from config.xml file...
Removing windows from cordova.platforms array in package.json

C:\Projects\Cordova Projects\windowsMaster2<EMAIL_ADDRESS>λ cordova platform add https://github.com/apache/cordova-windows#janpio-CB-13870_2
Using cordova-fetch for https://github.com/apache/cordova-windows#janpio-CB-13870_2
Warning: using prerelease platform<EMAIL_ADDRESS>Use 'cordova platform add windows@latest' to add the latest published version instead.
Adding windows project...
Creating Cordova Windows Project:
        Path: platforms\windows
        Namespace: io.cordova.hellocordova
        Name: HelloCordova
Windows project created with<EMAIL_ADDRESS>Installing "cordova-plugin-whitelist" for windows
--save flag or autosave detected
Saving windows@https://github.com/apache/cordova-windows#janpio-CB-13870_2 into config.xml file ...

C:\Projects\Cordova Projects\windowsMaster2<EMAIL_ADDRESS>λ cordova requirements

Requirements check results for windows:
Windows OS: installed Windows 10
MSBuild Tools: installed 15.5
Visual Studio: installed (user-specified)
Windows SDK: installed 10.0
Windows Phone SDK: installed 10.0

(current master first, show the problem, then this branch, show that it works)
Checklist

[x] Reported an issue in the JIRA database
[x] Commit message follows the format: "CB-3232: (android) Fix bug with resolving file paths", where CB-xxxx is the JIRA ID & "android" is the platform affected.
[ ] Added automated test coverage as appropriate for this change.

Yes, this is actually required for cordova requirements not to explode (which happened after the change to UAP).


Got "Visitor error" when I canceled the importer

maybe nice to have Error: instead of Visitor error:  ?

I found a place when this is happening
-            .map_err(|err| ScannerError::Normal {
-                err: err.into(),
+            .map_err(|_err| ScannerError::Normal {
+                err: anyhow!("aaa"),

I'm trying to understand how to make the change in proper way


Add support for logs to the infra attributes processor.

What does this PR do?
Implements logs processor for infraattributesprocessor. Gets entities from resource attributes and applies entity tags and global tags as resource attributes.

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Website Docker image

At the moment it's a bit of a hassle for people to test out PRs on the website. You need to set up a LAMP / MAMP / WAMP server locally which can put newcomers off.
Even though we won't use it in production, it could be nice to have a simple Docker container to run a server for people to test PRs. Thinking about it, it will have to mount a checked-out version of the code for this, so we can presumably use an existing Docker container and just write an example command in the docs / Readme about how to do this.
Any suggestions / previous experience?

Speaking from trying to set it up locally myself: the biggest issue was getting all the credentials right and comment parts out, where I didn't have them, all related to the different sources for stats, tweets etc. So if we could maybe could put dummy json files and dev tags around other parts it should work.

Honestly, I've tried setting up a LAMP server, which I haven't done in years.
And even if it got way easier that it was, I failed miserably to render the nf-co.re website.
I would definitively like something to help render the website more easilly.

To better replicate the server: which version of php and apache is running on it, @ewels?

Awesome! 🚀


feat(footer): introduce cookie preference placeholder

Related Ticket(s)
Refs #3583.
Description
This change adds <dds-legal-nav-cookie-perferences-placeholder>, a placeholder for cookie preference link.
Changelog
New

<dds-legal-nav-cookie-perferences-placeholder>, a placeholder for cookie preference link.

I tried and the link doesn't seem to be getting loaded in. Going to see what's going on there.

Superseded by: #3656


Add TrustedTypes support to lit-next

When running in a browser that supports TrustedTypes this will create a lit-html policy and use it for blessing the content of tagged template literals before we hand it off to HTMLTemplateElement#innerHTML for parsing.

Can you add a changelog entry before merging?

This change is giving me compilation issues in Typescript. See https://github.com/lit/lit/issues/1780


Add libfmt dependency to README

libfmt is required to build this project. This should be added to the README.

It's better now!

Yes! Closing :)


Add App icon

Add icon for app, loading screen, etc.

Looks like the icons have to be changed in the android directory, which is excluded from commits.
I may want to create a script that automatically updates the icons locally--as well as instructions for generating the icon--so I don't have to commit that directory (or the iOS one, if/when I decide to run my app there).

Commits:

d2240658c87d6283b219f74282e78fac1c6a2c4b
777852920f96bfb015d30e86acb8e69d9af8ec50
926d136965f95998a7a6cfa915c385b57d266430

A new task was created to update the splash screen.

The android image assets were being ignore by .gitignore: https://github.com/johneastman/todo/commit/1197290e2437c28037d27959b4b5d9f4fb6bf1fe


ssr: Fix missing scoreboard and wrong timin in config reads

Two bugs in the RTL prevented the use of the scfgr/scfgri instructions

A missing scoreboard connection to keep track of the destination register value
Timing in the stream_to_mem converter. The SSR respond with the read value in the same cycle as the request is made. Previously, the id and valid signals were delayed a cycle but not the data. This change removes the delay such that the response comes in the same cycle as the request

This now allows SSR barriers such as
  asm volatile(
    "1: \n"
    "scfgri t0, 0\n"        // reat status word
    "srli   t0, t0, 31\n"   // extract done bit 31
    "beqz   t0, 1b\n"       // repeat if done bit not set
    ::: "t0");

Is the timing ok like this or should we insert a cut on the response?

Two bugs in the RTL prevented the use of the scfgr/scfgri instructions

A missing scoreboard connection to keep track of the destination register value

Perfect.

Timing in the stream_to_mem converter. The SSR respond with the read value in the same cycle as the request is made. Previously, the id and valid signals were delayed a cycle but not the data. This change removes the delay such that the response comes in the same cycle as the request

Interesting that this works, I would have thought that the stream_to_mem requires one cycle latency. Another fix would be to also delay data, right? I think I'd me more comfortable in getting such a fix in - not so much regarding the timing, but at least in the upstream reqrsp protocol a cycle delay between a request and a response is necessary. Does that make sense?

Sure, this has now 1 cycle latency


Correction for raw affiliation UMR 6226 CNRS -University of Rennes; University of Tlemcen T. Roisnel

Correction needed for raw affiliation UMR 6226 CNRS -University of Rennes; University of Tlemcen T. Roisnel
raw_affiliation_name: UMR 6226 CNRS -University of Rennes; University of Tlemcen T. Roisnel
new_rors: 043vm9914;015m7wh34;00adwkx90
previous_rors: 043vm9914;015m7wh34
works_examples: W4387665734
contact: 29f2d11953e77506ab64c81290f43ac1:ec5163a66c0072b0759a6f4b0b43ef42 @ univ-rennes.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


HMR Infinite request loop after restarting webpack serve

Bug report

What is the current behavior?
I've been working on a webpack 5 migration and have run into a bug where HMR gets stuck in an infinite loop after restarting the dev server. Sorry I'm not sure if this is an issue specific to webpack dev server or not, it seems to be originating from this repo.
If the current behavior is a bug, please provide the steps to reproduce.

Start webpack dev server webpack serve
Modify a source file.
Now you observe the first hot-update.json request like http://localhost/static/customer-dashboard.263d2b2c0d78de6116e2.hot-update.js
Stop WDS.
Console:

[WDS] Disconnected!
GET http://localhost:9111/sockjs-node/info?t=1627083911242 net::ERR_CONNECTION_REFUSED

Start WDS.
Crash loop starts: GET http://localhost/static/customer-dashboard.c3beb7f29395129d613f.hot-update.json 404 (Not Found)

I have to manually refresh the page to resolve it, but the browser is freezing up at this point from the thousands of requests.

Call stack
(anonymous) (jsonp chunk loading:538)
Promise.then (async)
__webpack_require__.hmrM (jsonp chunk loading:537)
Promise.then (async)
hotCheck (hot module replacement:234)
check (dev-server.js:15)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)
Promise.then (async)
check (dev-server.js:16)
(anonymous) (dev-server.js:29)

The jsonp chunk loading error:
TypeError: Cannot read property 'requestContent' of undefined
We write the output to disk using devServer.writeToDisk and serve it from a separate server but I've also tested it without writing to disk and making requests direct to WDS, same results. That means I also have output.clean = true, but I get the same results when disabling this.
I'm using persisted cache but get the same results when disabling the cache.
EDIT: Confirmed not broken in 5.45.1. I'm guessing it was introduced in #13576, what do you think @rockwalrus ? What I was seeing was that updateModules was [] and maybe should have been undefined since the window was never reloading.
https://github.com/webpack/webpack/blob/a32b0fd041260f3303b9329c9a65cc4afe102390/hot/dev-server.js#L15-L16
What is the expected behavior?

Other relevant information:
webpack version:  5.46.0
Node.js version: tested on node 10 and 14
Operating System: macos 10.14.6
Additional tools:
Chrome
webpack-dev-server 3.11.2

Can you provide repo?

@alexander-akait here you go https://github.com/stefan-toubia/webpack-5-hmr-bug
I was able to repro the issue on this repo.

Fixed https://github.com/webpack/webpack/pull/13877


Proposal: introduce isWritable() method for ChannelHandlerContext

Very often I have to use next code pattern:
ctx.channel().isWritable()
It would be very convenient to introduce the same method for the ChannelHandlerContext:
ctx.isWritable()
WDYT?

I think I would only do it if there is any notion of have different writability states per ChannelHandlerContext otherwise you could basically say this for most Channel methods.


Zero confidence intervals

Hi,
I am trying to generate confidence intervals for the below sample data. I am using RandomForestRegressor with bootstrapping enabled.
X_train shape (270, 7)
[[ 12.  20.   1. ... 300.   1.   0.]
[ 12.  20.   1. ... 300.   1.   0.]
[ 12.  20.   1. ... 300.   1.   0.]
...
[ 12.  30.  10. ... 300.   1.   0.]
[ 12.  30.  10. ... 300.   1.   0.]
[ 12.  30.  10. ... 300.   1.   0.]]
Test data shape (36,7)
[[ 12.  10.   1.   1. 300.   1.   0.]
[ 12.  10.   5.   1. 300.   1.   0.]
[ 12.  10.  10.   1. 300.   1.   0.]
...
[ 12.  10.   1.   4. 300.   1.   0.]
[ 12.  20.   1.   4. 300.   1.   0.]
[ 12.  30.   1.   4. 300.   1.   0.]]
I generate ci data as
ci_data = fci.random_forest_error(model, x_train, x_test,  calibrate=True)

However, ci_data contains all zeroes
[1.89472718e-34 1.89472718e-34 1.89472718e-34 1.89472718e-34
1.89472718e-34 1.89472718e-34 1.89472718e-34 1.89472718e-34
1.89472718e-34 1.89472718e-34 1.89472718e-34 1.89472718e-34
1.89472718e-34 1.89472718e-34 1.89472718e-34 1.89472718e-34
1.89472718e-34 1.89472718e-34 1.89472718e-34 1.89472718e-34
1.89472718e-34 1.89472718e-34 1.89472718e-34 1.89472718e-34
1.89472718e-34 1.89472718e-34 1.89472718e-34 1.89472718e-34
1.89472718e-34 1.89472718e-34 1.89472718e-34 1.89472718e-34
1.89472718e-34 1.89472718e-34 1.89472718e-34 1.89472718e-34]
Do you have any pointers as to what could be going wrong here? Thanks.

I'm not sure. Might be related to the feature that has the same value for
every observation?
On Wed, Feb 28, 2018 at 5:45 PM, Swarnendu Biswas<EMAIL_ADDRESS>wrote:

Hi,
I am trying to generate confidence intervals for the below sample data. I
am using RandomForestRegressor with bootstrapping enabled.
X_train shape (270, 7)
[[ 12. 20. 1. ... 300. 1. 0.]
[ 12. 20. 1. ... 300. 1. 0.]
[ 12. 20. 1. ... 300. 1. 0.]
...
[ 12. 30. 10. ... 300. 1. 0.]
[ 12. 30. 10. ... 300. 1. 0.]
[ 12. 30. 10. ... 300. 1. 0.]]
Test data shape (36,7)
[[ 12. 10. 1. 1. 300. 1. 0.]
[ 12. 10. 5. 1. 300. 1. 0.]
[ 12. 10. 10. 1. 300. 1. 0.]
...
[ 12. 10. 1. 4. 300. 1. 0.]
[ 12. 20. 1. 4. 300. 1. 0.]
[ 12. 30. 1. 4. 300. 1. 0.]]
I generate ci data as
ci_data = fci.random_forest_error(model, x_train, x_test,  calibrate=True)
However, ci_data contains all zeroes
[1.89472718e-34 1.89472718e-34 1.89472718e-34 1.89472718e-34
1.89472718e-34 1.89472718e-34 1.89472718e-34 1.89472718e-34
1.89472718e-34 1.89472718e-34 1.89472718e-34 1.89472718e-34
1.89472718e-34 1.89472718e-34 1.89472718e-34 1.89472718e-34
1.89472718e-34 1.89472718e-34 1.89472718e-34 1.89472718e-34
1.89472718e-34 1.89472718e-34 1.89472718e-34 1.89472718e-34
1.89472718e-34 1.89472718e-34 1.89472718e-34 1.89472718e-34
1.89472718e-34 1.89472718e-34 1.89472718e-34 1.89472718e-34
1.89472718e-34 1.89472718e-34 1.89472718e-34 1.89472718e-34]
Do you have any pointers as to what could be going wrong here? Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/scikit-learn-contrib/forest-confidence-interval/issues/72,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHPNuEqqPpo7unzy3ag1M-mIRXa-gJtks5tZ1KrgaJpZM4SXodE
.

Thanks for the tip. I had tried it, but it does not help. I trimmed my data set to now contain only features that change and the label. But I still get the zero CIs. Without normalization (which is possibly not a must for random forests), I get the following error:
/usr/local/lib/python3.6/dist-packages/forestci/calibration.py:102: RuntimeWarning: invalid value encountered in true_divide
  g_eta_main = g_eta_raw / sum(g_eta_raw)

This happens because all entries in mask are zero:
    def neg_loglik(eta):
        mask = np.ones_like(xvals)
        mask[np.where(xvals <= 0)[0]] = 0

data.zip

Could you also send along the code you ran?

I have got it to work if I use a StandardScaler() or MinMaxScaler(). Otherwise, I get the following error:
/lib/python3.6/site-packages/forestci/calibration.py:86: RuntimeWarning: overflow encountered in exp
  g_eta_raw = np.exp(np.dot(XX, eta)) * mask
/lib/python3.6/site-packages/forestci/calibration.py:102: RuntimeWarning: invalid value encountered in true_divide
  g_eta_main = g_eta_raw / sum(g_eta_raw)
[nan nan nan nan nan nan nan nan nan nan nan nan nan nan nan nan nan nan
 nan nan nan nan nan nan nan nan nan]

data.csv.zip
This is the code and I have attached the data file:
import csv
import sys
import numpy as np
from matplotlib import pyplot as plt
from sklearn.ensemble import RandomForestRegressor
from sklearn.preprocessing import StandardScaler, MinMaxScaler
import sklearn.model_selection as xval
import forestci as fci

# Read data from csv file
file = open("./data.csv", "r")
mpg_X = []
mpg_Y = []
reader = csv.reader(file)
for line in reader:
    line = [float(x) for x in line]
    mpg_X.append(line[1:4])
    mpg_Y.append(line[-1])

mpg_X = np.array(mpg_X)
mpg_Y = np.array(mpg_Y)

# xscaler = MinMaxScaler()
# yscaler = MinMaxScaler()

# n_mpg_x = xscaler.fit_transform(mpg_X)
# n_mpg_y = yscaler.fit_transform(mpg_Y.reshape(-1, 1))
n_mpg_x = mpg_X
n_mpg_y = mpg_Y

# split mpg data into training and test set
mpg_X_train, mpg_X_test, mpg_y_train, mpg_y_test = xval.train_test_split(n_mpg_x, n_mpg_y, test_size=0.1,
                                                                         random_state=42)

mpg_forest = RandomForestRegressor(n_estimators=200, random_state=42)
mpg_forest.fit(mpg_X_train, mpg_y_train.ravel())
mpg_y_hat = mpg_forest.predict(mpg_X_test)

# Calculate the variance:
# inbag = fci.calc_inbag(mpg_X_train.shape[0], mpg_forest)
mpg_V_IJ_unbiased = fci.random_forest_error(mpg_forest, mpg_X_train, mpg_X_test,   # inbag=inbag,
                                            calibrate=True)
print(mpg_V_IJ_unbiased)

plt.scatter(mpg_y_test, mpg_y_hat)
min_x = min(min(mpg_y_test), min(mpg_y_hat))
max_x = max(max(mpg_y_test), max(mpg_y_hat))

plt.plot([min_x, max_x], [min_x, max_x], 'k--')
plt.xlabel('Reported label')
plt.ylabel('Predicted label')
plt.show()

plt.errorbar(mpg_y_test, mpg_y_hat, yerr=np.sqrt(mpg_V_IJ_unbiased), fmt='o')
plt.plot([min_x, max_x], [min_x, max_x], 'k--')
plt.xlabel('Reported label')
plt.ylabel('Predicted label')
plt.show()

@arokem Did you have a chance to try out the code? Were you able to reproduce the error I faced?

Thanks for posting this. I was also getting nans, and was able to work backwards by starting with your example and filling in my own data.

@stl-christywilloughby Welcome. Have you been able to fix the NaNs? If yes, were you able to identify any patterns in the data or usage that causes this?

I also get the same error:
/lib/python3.6/site-packages/forestci/calibration.py:102: RuntimeWarning: invalid value encountered in true_divide   g_eta_main = g_eta_raw / sum(g_eta_raw)
I've been running this code on my own dataset and this error appears both when I use StandardScaler and if I don't use StandardScaler. Is there any update on the potential cause for this?

I am having the same error using my own dataset. It appears that not all of the features in my dataset produce this error (i.e., when I subsample my dataset, the code works, depending upon the exact subsample chosen):
/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/forestci/calibration.py:86: RuntimeWarning: overflow encountered in exp   g_eta_raw = np.exp(np.dot(XX, eta)) * mask
/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/forestci/calibration.py:101: RuntimeWarning: overflow encountered in exp   g_eta_raw = np.exp(np.dot(XX, eta_hat)) * mask
/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/forestci/calibration.py:102: RuntimeWarning: invalid value encountered in true_divide   g_eta_main = g_eta_raw / sum(g_eta_raw)

@swarnendubiswas
I encountered the same issue. After I tried out your codes with MinMaxScaler(), this probrem is solved with confidence intervals in the scale of the MinMaxScaler. How could we restore these confidence intervals as the initial units?
Thanks.

@smile4lee Sorry I do not get your question.

@smile4lee Sorry I do not get your question.

@swarnendubiswas Sorry for the confusion. I mean the similar issues mentioned in #83. We need the variance in same order as the orginal data (without scaler), how could we transform the variances corrersponding to the orginal data?

According to the documentation the forestci.random_forest_error performs calibration. Set the calibration to False and you will not receive the NaNs. As for the calibration method you will have to go in detail over the code.
I personally do the calibration after I obtained the standard deviation with forestci.random_forest_error
Hope this helps.

Are there some update regarding this issue?
Avoid calibration doesn't seem to be a solution, since variance can be negative.

This thread helped me realize that the issue was with caliberation, so I turned it off. But as @Niccolo-Ajroldi said, this is not a solution but a work around. I will do the calibration differently for now


Bump v16x branch to 1.6.7

tests failures appear to be kokoro infrastructure failures related to this branch
portability tests failed with: ssh_exchange_identification: Connection closed by remote host
all failures outside of the mac tests failed with a com.google.devtools.kokoro.config.ConfigException
mac tests failed with Homebrew must be run under Ruby 2.3!


added open graph

Pull Request Template

Please provide all of the details below. Pull requests missing any of the information below will be closed!

Sumarise what this PR fixes: < enter details >
Added open graph HTML and image
Fixes #: < Enter Issue ID/URL >
Checklist:
(Add an x between the brackets to check the items)

[X] I have sumarised what this PR fixes above
[ ] I have provided the issue ID/URL above
[X] This PR fixes only the issue mentioned above (create seperate PRs for seperate issues)
[ ] I was the first one to claim the issue or I created the issue

@TTumyr we are trying to associate pr's with current issues. The changes look good, but there was no issue present. I'll pull this in as it is a positive change, but please check for issues first next time..


Halo for roads without name tag

I would like to suggest a feature within the Background Settings tab.  The default would not to be active but for users applying road names it is difficult to see which road segments do and don't have name tag applied.  The use of this feature may help create more comprehensive road name data.
This feature would display a red halo around roads that do not have a name tag.  I have attached an example from the GoMap!! app showing how it is done there.  We have found this feature to be very useful in the app and would love to see an option in iD that functions in a similar method.

I'd prefer to keep validation specific styling out of iD and instead push users who are interested in validation towards dedicated QA tools like Osmose or Keepright or similar.
I'm also ok with having people build integrations between QA tools and iD.  This could work similar to our existing Mapillary integration:  checkboxes under the Map Data panel can toggle a data overlay showing users where issues are, and a floating div somewhere with action buttons like "mark as resolved" or "not an issue".

I would like to push back on this a little.  This feature could be very useful to users of iD to help identify where better mapping needs to occur in a city.  Also the QA tools typically don’t update in realtime making it awkward to use and less efficient.  Using tools like JOSM is more ‘powerful’ but I’d like to see this possible to average/new OSM users.
If the integration pane similar to Mapillary is a possibility, can you provide where that develop occurs and who integrates that into this repo?  A basic QA toolset in the “Map Data” area would really help improve data overall on a general level.

On May 16, 2016, at 12:57 PM, Bryan Housel<EMAIL_ADDRESS>wrote:
I'd prefer to keep validation specific styling out of iD and instead push users who are interested in validation towards dedicated QA tools like Osmose or Keepright or similar.
I'm also ok with having people build integrations between QA tools and iD. This could work similar to our existing Mapillary integration: checkboxes under the Map Data panel can toggle a data overlay showing users where issues are, and a floating div somewhere with action buttons like "mark as resolved" or "not an issue".
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub https://github.com/openstreetmap/iD/issues/3113#issuecomment-219513826

If the integration pane similar to Mapillary is a possibility, can you provide where that develop occurs and who integrates that into this repo?

Sure that's a fair question.. Like the Mapillary development, the work will probably be done by a third party that has some useful permissively licensed data that they they want to show up in iD.  I know that somebody is working on a QA integration with iD now and I'd love to get a PR from them and help them integrate it.


Having problem working with packages.nuget.org/api/v2

(Bug created from support request query)
I'm developing a .NET service which checks nuget packages through the nuget api: packages.nuget.org/api/v2.
The service sometimes crush with the error:
System.InvalidOperationException: An error occurred while loading packages from 'https://packages.nuget.org/api/v2': The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. (see in Event_Viewer_Error.png attachment).
I've read about the problem and most of the pages points to a certificate problem.
I tried to enter the https://packages.nuget.org/api/v2 address with the browser several times. The weird thing is that sometimes the pages loads and sometimes I get a privacy error. (see in Browser_Error.png attachment).

please reopen if this is still an issue.


Increase ticker max length to 6

Justification for this PR: This is in preparation for registering the SUNDAE token metadata;
There's not a great abbreviation for SUNDAE, and we have already built up expectations around the token being named SUNDAE; changing it at the 11th hour would create significant confusion and create fertile soil for scammers.

Some evidence for distribution of token tickers in the wild on other chains:
https://ethereum.stackexchange.com/questions/25619/is-there-length-limits-on-token-symbols

Thanks! Can we also make corresponding update in README.
Additional test in here would be handy too. :sweat_smile:
I don't know if this is enough or is there a need to do a change also elsewhere in this repo, but maybe not... :thinking:
@rvl @sevanspowell.
I think we need the same change in cardano-wallet as there seems to be the same constraint there :man_shrugging:

Perhaps we should increase the max length to 9 so that the MILKSHAKE ticker is also possible?

@piotr-iohk Would you like me to bump the max length to 9, as suggested by rvl?

Would you like me to bump the max length to 9, as suggested by rvl?

I don't have strong opinion. I'm fine with 9.

@piotr-iohk feedback addressed :) I wasn't 100% able to confirm the test locally, as I couldn't get it to run the newly built version of the code, it kept falling back to the version at 5 characters, but it seemed straightforward enough.

@Quantumplation Would you also be able to raise a PR on CIP-26. There was no particular reason for choosing max length 5 - only that there should be some limit, and the ticker is meant to be a short identifier which abbreviates the token name. For example, the max ticker length on NASDAQ is 5, and MSFT is the ticker for Microsoft. If token creators choose long tickers, they may get truncated in GUIs.

Will do :)

Took me a little while @rvl, but here you go: https://github.com/cardano-foundation/CIPs/pull/207


Fix resource leak in ServerArgument

Hi,

Travis CI on osx-oraclejdk8 failed, maybe you need to merge with master first (we have fixed it);
Any suggestions about  metrics/*?  PR https://github.com/apache/iotdb/pull/1303 wants to remove it.

Hi, @jixuan1989 . Thanks for your comments, the master branch has been merged. I think it will take a long time to remove the entire metrics/*, so it is necessary to solve this memory leak problem. What do you think?


Please add license

Hello, I'm interested in using your code in another project. It would be nice if you could add a license. Preferably MIT.
Thanks!

Thanks a lot!


example usb2

Hello! I tried to enter the sample code usb, but git forbids me:  Invalid username or password
andrea@tec-martin:~/Documenti/Git/picostdlib> git push --set-upstream origin Martinix75
remote: Invalid username or password.
fatal: Autenticazione non riuscita per 'https://github.com/beef331/picostdlib.git/'
andrea@tec-martin:~/Documenti/Git/picostdlib>
I'm learning these days to use git, so chances are I'm still doing something wrong! :(

I believe your origin is my repo, fork it then do git remote add-url devel $yourGitUrlToFork, the git push --set-upstream devel $YourGitBranch

maybe I succeeded !!! let me know if the hello_ub file has arrived :))

You did it! And also showed me that there needs to be sugar for the gpio as such i made https://github.com/beef331/picostdlib/blob/master/src/picostdlib/gpio.nim#L66
which is used like setupGpio(led1, 25, Out)


Implement Gunicorn Serverhooks

User Story - Business Need
Gunicorn provides event hooks to provide insight into how workers are being used.
We need insight into the lifetime of workers so that we can properly forecast how many workers we actually need to handle X amt of requests.
To be clear, CPU/Memory usage are going to be the overriding factors for scaling, but having a better of idea of what the GUnicorn workers are being utilized will help us making the proper decisions.
To implement this ticket, update the gunicorn_config.py file with the following methods:
def post_fork(server, worker):
    server.log.info("Gunicorn Worker spawned (pid: %s)", worker.pid)

def pre_fork(server, worker):
    server.log.info("Gunicorn Worker exiting (pid: %s)", worker.pid)

def when_ready(server):
    server.log.info("Gunicorn Server is ready. Spawning workers")

def pre_request(worker, req):
    worker.log.info(f"Gunicorn Worker is about to process request: {worker.pid}")

def post_request(worker, req, environ, resp):
    worker.log.info(f"Gunicorn Worker finished processing request: {worker.pid}")

Check with @k-macmillan to determine if any of the above methods are overkill.

[x] discuss with QA

User Story(ies)
As a Notify Developer
I want check the cloudwatch logs for when Gunicorn is starting/killing processes
So that I know how Gunicorn is handling load
Additional Info and Resources
Engineering Checklist

[x] Add post_fork to gunicorn_config.py
[x] Add pre_fork to gunicorn_config.py
[x] Add when_ready to gunicorn_config.py
[x] Add pre_request to gunicorn_config.py
[x] Add post_request to gunicorn_config.py

Acceptance Criteria

[x] Verify that post_fork messages are in Cloudwatch
[x] Verify that pre_fork messages are in Cloudwatch
[x] Verify that when_ready  messages are in Cloudwatch
[x] Verify that pre_request messages are in Cloudwatch
[x] Verify that post_request messages are in Cloudwatch

QA Considerations

[ ] regression passes
[ ] the AC is verified in Perf

Potential Dependencies
Out of Scope

Hey team! Please add your planning poker estimate with Zenhub @cris-oddball @EvanParish @justaskdavidb2 @k-macmillan @kalbfled @ldraney

You can log from just the post_requst method.  That has the original request and the response as parameters.  There is likely a time associated with both of those:
def post_request(worker, req, environ, resp):
    pass


Expose eip 712 hash public for tests

This is needed for https://github.com/omisego/elixir-omg/pull/656

I think it's a bad idea, to discover an internal function for test

I think it's a bad idea, to discover an internal function for test

Idea here is to keep functions internal in production code. I expose then in a separate test contract to test dependency conformance.

It looks weird to me as well though....why we would need to expose function for "end-to-end" test?
By "end-to-end" usually it should be pretty blackbox testing, isn't it?

By "end-to-end" usually it should be pretty blackbox testing, isn't it?

Strictly said it's dependency conformance test we have eip-712 hashing dependency in elixir and in solidity, we need to make sure they both do the same. Do I address you concern @boolafish :question:

Okay, got your point.
However, I feel this is a bit overkill and would be better to just write unit tests in both implementations (BTW, it seems like in elixir, those functions are just test fixture, do we really care?). I am saying unit test because,  If I have the right understanding, the function here is pretty much pure computation and we should ideally have enough confident it is correct by just unit test.
I guess what we want is both to be "correct" and naturally be the same. Also, take a bit extreme example, if we are writing a add(x, y) function, would you test dependency this way?

my cents:
Generally we definitely avoid exposing any "test-only" interfaces, guts and all that, I'm trying to be super careful that this never happens and treat "testing via public API" even dogmatically I'd say.
That being said I think this context here is special:
Errors that arise from things like incorrect signatures/merkle proofs/hashing/encoding in Solidity contracts are notoriously hard to debug, at least with the current tooling we use (I'm not aware of anything that would revolutionize here, yet). This prompted me to suggest we build such suite of compliance test, tests of signature being the first.
We do have end-to-end, public-API based tests that test whether the contract behaves as expected when prodded with inputs coming from our Elixir code - those are the :integration tests. And this is the black-box testing you're speaking to here, and this is the, let's say "main test" we're looking at, when figuring out whether we can talk to the contract.
Those :integration tests however take ages to execute, so we keep only a minimum amount of those, testing selected "happy paths" only.
Suppose we didn't have those compliance tests like this one, and one of those high level :integration tests failed - it would take considerable effort to rule out problems with the signing mechanism.
Other example (and my current plan for these compliance tests to evolve) is the merkle hashing/proving code - I'd love to be able to always reliably tell that this is executed identically on both Solidity and Elixir end, but doing so extensively via our public APIs would be tedious.

just write unit tests in both implementations

I think such unit tests would never tell you whether both implementations work the same - they could both do the job as specified but still produce different signatures. Simplest example would be when one of the EIP-712 implementations would miss one round of keccak256-ing or abiEncodePacked-ing somewhere.
On the other hand, in a way, this is a unit test.  We're asserting that two disparate implementations of an algo give bit by bit identical results, under multiple varying inputs.

Also, take a bit extreme example, if we were writing a add(x, y) function, would you test dependency this way

I don't agree with the analogy implied - add is way more natural, debuggable than a stack of keccaks,encodings etc where all data looks like /dev/random and your test feedback is basically just transaction ok | transaction failed

Errors that arise from things like incorrect signatures/merkle proofs/hashing/encoding in Solidity contracts are notoriously hard to debug

I agree, that is also why I am pushing so hard to have unit test in contract. Currently we don't really have unit test hitting the Eip712StructHash.sol. To do so, it means we would need some mock/test contract that exposes the function, but I think the trad-off is good and also this practice is heavily used by openzepplin.

Simplest example would be when one of the EIP-712 implementations would miss one round of keccak256-ing or abiEncodePacked-ing somewhere.

Doesn't this means your test is basically written wrong? If what your test is expecting/asserting is something we are confident to be the "true" value, and both implementation has the test suite that makes us confident they are both correct, how would this happen?

I think I do see your pain point for hard to pinpoint the failing part. My 2 cent would be let's try to improve our unit tests on contracts first. Ideally this should even block integration test from running.
However, if this still obviously does not help the situation, or it's just really too hard to write good quality solidity test codes then we go that path of "testing both implements are same".


Dynamic DataRow2 Height setting

Hi there,
I have run into this issue several times. I cannot figure out how to set the height of each data row to fully wrap the text contained within it.
It often just cuts off some of the text that is displayed in the row when it is too long to fit on a single line.
Am I missing a param for this? Or is it not supported at the moment?

Hi. All rows are fixed width and there's no logic in the Widgets that can help to size their rows, columns and cells to fit contents. The only advice I can give is choosing widths (columns adapt to parent width OR minWitdh) and heights that work for most of the anticipated cases.


create-db-schema

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#99  👈
#98
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @richardhuaaa and the rest of your teammates on  Graphite


Refs #32074 -- Removed usage of deprecated Thread.setDaemon().

threading.Thread.setDaemon has been deprecated since Python 3.10.
Setting the daemon attribute directly is recommended.

@tirkarthi Thanks :+1:, it was deprecated < 1 day ago, so let's wait for 3.10.0b1 before merging this.

@tirkarthi Thanks :+1: Welcome aboard :boat:

Test failure is not related with this patch.

Thanks @felixxm :)


New client version shown as -1 bytes

Happens both on German and English translations.

System info
OS: Windows
Client: 1.1.7-RC1
Wanna have the bug fixed quickly?
Visit Issue hunt...

@Brutus5000 already looked into it I think....

Our content server throws 403 if you request it with HEAD. We need to check why, might be related to the docker changes on the content-server.

Oh wait I tested this on our servers but current file is on Github. And Github gives 403

Brutus suggests to kill the display of size and replace by an estimate

Is this still a thing?

Is this still a thing?

The problem with Github still exists, but since I'm currently uploading files to my mirror for faster download speed, it's not a problem.

The problem with Github still exists, but since I'm currently uploading files to my mirror for faster download speed, it's not a problem.


Use select for due dates

Current dependencies on/for this PR:

main

PR #438   👈

This comment was auto-generated by Graphite.


can I get leaf index while predict

Infact, I cann't  find "pred_leaf : bool, optional (default=False),  Whether to predict leaf index." while using lightgbm on spark (scala 2.11.12 / spark2.4), although I can find it in "from lightgbm.sklearn import LGBMClassifier" and use it like "lgbm.predict(val_df,pred_leaf=True)".
How can I get the predict leaf index? plz help me. Thanks！

https://github.com/microsoft/SynapseML/pull/768


Top Node.js Monitoring Tools

this fixes #1065
Article Checklist
Preliminary Checks - Formatting and Structure

[x] Does your article follow any of the suggested structure formats? - see example formats
[x] Is your article properly formatted in Markdown? - see Github Markdown guide
[x] Have you used the correct folder and file structure? - see Contribution Guidelines
[x] Is your article over 750 words? - Tool: Wordcounter.net
[x] Have you used our preferred heading structure? - H3 (###) and up
[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.
[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.
[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images
[x] In your PR - add a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.

NOTE: (1st time contributors - submit ONLY one article to get familiar with the process and style-once published, you can then submit any number of articles.)
Grammar Checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid -  Grammarly
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical Checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide

Contribution Guidelines
For first-time contributors and for more details, see Contributing Guidelines

@LinusMuema, I have updated this article.

@LinusMuema, I have updated this article.

Hi @hectorkambow
You could give this article a plag check and final review.

plagiarism check done

Please be sure to go over some of minor edits I made for flow @EKahuha
cc @LinusMuema  🚀


Implement equality = and inequality <> support for BinaryView

Is your feature request related to a problem or challenge?
Part of https://github.com/apache/datafusion/issues/10918, [StringViewArray](https://docs.rs/arrow/latest/arrow/array/type.StringViewArray.html) support in DataFusion
@Weijun-H  added support for <> and != forStringView in  https://github.com/apache/datafusion/pull/10985. We also need similar support for BinaryView
Describe the solution you'd like
In order to improve performance of these queries we will need the ability to actually compare StringViewArrays  to constant values (and likely to each other)
Thus I would like to be able to run
BinaryView = scalar
BianryView = StringViewColumn
I basically want to to run the following queries (where table foo has BinaryView columns)
> create table foo as values ('Andrew', 'X'), ('Xiangpeng', 'Xiangpeng'), ('Raphael', 'R');
0 row(s) fetched.
Elapsed 0.002 seconds.

> select * from foo where column1 = 'Andrew';
+---------+---------+
| column1 | column2 |
+---------+---------+
| Andrew  | X       |
+---------+---------+
1 row(s) fetched.
Elapsed 0.003 seconds.

> select * from foo where column1 <> 'Andrew';
+-----------+-----------+
| column1   | column2   |
+-----------+-----------+
| Xiangpeng | Xiangpeng |
| Raphael   | R         |
+-----------+-----------+
2 row(s) fetched.
Elapsed 0.001 seconds.

> select * from foo where column1 = column2;
+-----------+-----------+
| column1   | column2   |
+-----------+-----------+
| Xiangpeng | Xiangpeng |
+-----------+-----------+
1 row(s) fetched.
Elapsed 0.002 seconds.

> select * from foo where column1 <> column2;
+---------+---------+
| column1 | column2 |
+---------+---------+
| Andrew  | X       |
| Raphael | R       |
+---------+---------+
2 row(s) fetched.
Elapsed 0.001 seconds.

Describe alternatives you've considered
I suspect we will need to update the coercion logic and maybe also the arrow equality kernels like https://docs.rs/arrow/latest/arrow/compute/kernels/cmp/fn.eq.html
Additional context
No response

I want to try it.

Thanks @PsiACE !
I think you can mostly follow the model / examples of StringView.
Please remember to create a PR that targets the string-view branch (not main)

Closed in https://github.com/apache/datafusion/pull/11004


feat: Bring back the coloured menu bar

Adds the the background colour and blur back to the menu bar.
Looks like:

As per @EM4Volts request

sad, @Alystrasz i really liked the feature, it gives the ui a better overall look, makes the menu buttons stand out instead of being just there.


the logout-dialog layer remains visible on the second screen after wlogout does what it needs to

This is what hyprlock leaves behind after calling hyprlock.

It disappears after a while / after random inputs / idk
I am on Hyprland, in case that's relevant, and my configuration can be found here
This is what my config looks like, for reference

This affects 1.2 and 1.2.1

@alba4k Can you build from the latest commit and see if that fixes your issue?

fixed, thanks!


New version: Dolang v3.0.2

Registering package: Dolang
Repository: https://github.com/EconForge/Dolang.jl
Created by: @albop
Version: v3.0.2
Commit: 77914b3ee3ad1b7060089be508d8aeeba36ec7b0
Reviewed by: @albop
Reference: https://github.com/EconForge/Dolang.jl/commit/77914b3ee3ad1b7060089be508d8aeeba36ec7b0#commitcomment-34747279

Needs a [compat] section in Project.toml with at least an entry for julia itself, e.g.:
[compat]
julia = "1"

would mean that the package is compatible with Julia versions [1.0.0, 2.0.0).


Remove unused variables

Find the other issues found here - https://deepsource.io/gh/pnijhara/alpha_vantage/issues/?category=recommended
This PR also adds .deepsource.toml configuration file to run DeepSource analysis on the repo with. Upon enabling DeepSource, the analysis will run on every PR and commit to detect 560+ types of issues in the changes — including bug risks, anti-patterns, security vulnerabilities, etc.
To enable DeepSource analysis after merging this PR, please follow these steps:

Signup on DeepSource with your GitHub account and grant access to this repo.
Activate analysis on this repo here.

You can also look at the docs for more details. Do let me know if I can be of any help!

Thanks for this PR! What advantage would this deepsource have over pep8 or just updated github actions? Is this a new technology? This is the first I've seen of it. Would love to try it out if it's reliable. Looks like it has caught a few good bugs in here.

DeepSource is a static analysis tool natively integrated with GitHub/GitLab code review workflows. The Python analyzer catches not only the style issues ( code violating PEP8 guidelines ) but detects issues which can compromise security and performance, anti-patterns, type-check issues, potential bug-risks, test-coverage issues etc.
The service is completely free to use for open-source and is reliable. Behind the scenes, the analyzer catches these issues by looking for patterns in the AST of the code. You should give it a try.


Update the Dockerfile Notebook Version to 0.1.7

Updates the Kaskada client to version 0.1.7 in the dockerfile notebook.
Q: Do we need to push a new image somehow to ghcr?

I don't think we are using this dockerfile anymore externally.  Maybe it is better to just delete it?

I definitely don't want to be constantly updating hard-coded library versions. Can the be folded into the jupyter environment Eric has on a branch and all the hard-coded versions removed?

Sure. There are currently at least 6 dockerfiles in the root of the repository and maybe more if we are building docker images from other branches. I'll file another issue and close out this PR.


bug(tenantresources): using actual resourceversion during createorupdate

Closes #687.

Thanks for the review, @aslafy-z, going to merge it.


problems with main.css during npm run build since 1.0.12

Is this a bug report?
Yes
Have you read the Contributing Guidelines on issues?
yes
Environment
(Docusaurus version via npm outdated docusaurus or yarn outdated docusaurus, OS, Node, npm, yarn)
Package     Current  Wanted  Latest  Location
docusaurus   1.0.12  1.0.12  1.0.14
OS : Mac High Sierra
Node : v8.4.0
npm : 5.6.0
yarn : 1.5.1
Steps to Reproduce

Update to version 1.0.12 or beyond
Run npm install followed by npm run build to generate the build
Since this PR - https://github.com/facebook/Docusaurus/pull/569 - When I build and deploy my site I have css issues.
When I deploy my site it does not display correctly, css is broken. In Chrome devtools console I see ```Resource interpreted as Stylesheet but transferred with MIME type test/plain: "https://www.www.www/doc-site/css/main.css"

Expected Behavior
After update to 1.0.12 and later css would work correctly.
Actual Behavior
When I deploy my site it does not display correctly, css is broken. In Chrome devtools console I see ```Resource interpreted as Stylesheet but transferred with MIME type test/plain: "https://www.www.www/doc-site/css/main.css"
Reproducible Demo
To demo this..

init and build the demo site. Have a look at the generated css file.
Deploy the build directory. You will see that css us broken.

@dgracehmh It could be something to do with your web server's settings. Docusaurus has been using the latest version and there aren't issues with it.
It would help if you could answer the following questions:

What web server are you using for serving the CSS? Docusaurus uses GitHub pages hosting
Try to run the website locally on localhost:3000. Does the warning still show and does the CSS work fine? Inspect the network tab and see the content-type of the HTTP request on your web server vs local server.
Is your website or code online for us to reproduce?

I have a suspicion it is not due to the cssnano change but due to the addition of <!DOCTEXT html> in #566, which makes the browser warn about non-standard practices.
My recommendation would be to check your web server configuration that it is serving the CSS files correctly. I had to make this change to the local web server to get it to work - https://github.com/facebook/Docusaurus/pull/566/files#diff-fe37ce87a7b7b83106303bf9233b49fbR508

@yangshun

I am using nginx to serve the site on an internal cloud via docker container.
Running locally is fine.
Sorry, my docs are not online. I've been deploying using exact same config (nginx + docker + Docusaurus) but when I update to 1.0.12 or beyond on the exact same config the css is broken.

I'm trying to dig in to figure out what changed since 1.0.11 to break my setup.

The change was that we added doctype to the top of each html file, and that
makes browsers less forgiving about non-standard practices. Please check
the content type of the CSS file being served. It shouldn't be anything to
do with cssnano
On Thu, Apr 26, 2018, 9:13 AM Darragh Grace<EMAIL_ADDRESS>wrote:

@yangshun https://github.com/yangshun

I am using nginx to serve the site on an internal cloud via docker
container.
Running locally is fine.
Sorry, my docs are not online. I've been deploying using exact same
config (nginx + docker + Docusaurus) but when I update to 1.0.12 or beyond
on the exact same config the css is broken.

I'm trying to dig in to figure out what changed since 1.0.11 to break my
setup.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/Docusaurus/issues/602#issuecomment-384700200,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQRHcCZ31q1KLhho7wB_D6m4uqQz-Dzks5tsfI0gaJpZM4Ti_1q
.

@darren128 Please check that your webserver is serving the CSS files using the correct HTTP content-type header - text/css and not text/plain.
Closing for now. Please reopen if you find that it is indeed a bug.

@yangshun Wrong person :)

Oops. Sorry 😄
@dgracehmh ^^

Thanks for the pointers @yangshun  : I changed my nginx configuration (content-type header - text/css) and got it working again. I guess it's handy to have a record of it here in case someone else comes up against the something similar.

@dgracehmh  Or if you think there is a place in the docs we should add something, a doc update PR might be a good thing too.

Done @JoelMarcey , hopefully it's ok - https://github.com/facebook/Docusaurus/pull/611

so fwiw S3 doesn't seem to set these mime types by default either. can't the link tag be adjusted?


fix: add override to packages of pnpm sharp and vite-imagetools

This snippet solve problem of #23.
Tested in production on:

Docker
Windows
Arch Linux
Debian 12
Ubuntu server 24.04 LTS

Thank you for your contribution!


The state type is required to implement Default even if client code never calls new or new_from_iter

The README claims the following: https://github.com/osa1/lexgen/blob/6be10c9ab5c56a5421a72891ba1069acec8e9b15/README.md?plain=1#L302-L308
However, as the library currently stands, the state type is required to implement Default even if the new and new_from_iter functions are never used. The reason is that the new and new_from_iter do not list $StateType: Default as a constraint, yet assume an implementation of Default in their bodies, and therefore if $StateType does not implement Default, the compilation of the entire program fails, even if the client never uses those functions.
A partial solution, which I implemented in the process of making https://github.com/osa1/lexgen/pull/53, is to add $StateType: Default as an explicit constraint. However, this only bypasses the problem if$StateType contains generic parameters. So, if $StateType does not implement Default, $StateType = Foo<'input> and $StateType = Foo<'a> are fine, but $StateType = Foo<'static> and $StateType = Foo are not. The fact that Rust rejects Foo<'static>: Default means that I had to do 'input: static and Foo<'input>, which solves the issue but creates warnings that the generic parameter 'input should be replaced with 'static. This is also only a partial solution because it does not allow a state type that does not implement Default if the state has no generic parameters.
(In my opinion, the rejection of a function with constraint Foo: Default, where Foo does not implement Default, is an illogical design choice on the part of Rust. If the constraint Foo: Trait is not satisfied, that is no different in principle than if Foo<T>: Trait is not satisfied for some choice of T. If Foo<T>: Trait is not satisfied for some choice of T, that simply means that the function is not usable for such T. If Foo: Trait is not satisfied where Foo has no generic parameters, this should simply mean that the function is not usable under any circumstances, not that the compiler should reject the function definition. This illogical design choice unfortunately makes my PR messy.)

To be honest, I think the simplest solution would be to make a breaking change and remove the new and new_from_iter functions. It would be slightly inconvenient for people whose types implement Default, who would have to explicitly pass default() to the *_with_state functions. However, the current situation is much more inconvenient for the people whose types do not implement Default (e.g. because all their constructors take parameters). If the state type is required to implement Default, that restricts what programs may be written. On the other hand, removing the two convenience functions would mean that users whose types do implement Default would have to type slightly more than they otherwise would, but would not fundamentally change what programs are possible.

Thanks for reporting this.
As can be seen from my wording in the README ("Used when the lexer has user state that does not implement Default"), my intention was to support user states that do not implement Default, but apparently I didn't do it right.
IIRC, originally we only supported state that implements Default. The constructors ..._with_state were added later.
Just to be concrete, here's the relevant parts of the generated code for a lexer Lexer(LexerState) -> ():
struct Lexer<'input, I: Iterator<Item = char> + Clone>(
    ::lexgen_util::Lexer<'input, I, (), LexerState, ::std::convert::Infallible, Lexer<'input, I>>,
);

impl<'input> Lexer<'input, ::std::str::Chars<'input>> {
    fn new(input: &'input str) -> Self {
        Lexer(::lexgen_util::Lexer::new(input)) // error: `LexerState: Default` is not satisfied
    }

    fn new_with_state(input: &'input str, user_state: LexerState) -> Self {
        Lexer(::lexgen_util::Lexer::new_with_state(input, user_state))
    }
}

impl<I: Iterator<Item = char> + Clone> Lexer<'static, I> {
    fn new_from_iter(iter: I) -> Self {
        Lexer(::lexgen_util::Lexer::new_from_iter(iter)) // error: `LexerState: Default` is not satisfied
    }

    fn new_from_iter_with_state(iter: I, user_state: LexerState) -> Self {
        Lexer(::lexgen_util::Lexer::new_from_iter_with_state(
            iter, user_state,
        ))
    }
}

lexgen_util::Lexer::new_from_iter and lexgen_util::Lexer::new require the state to implement Default.
I'm not sure if we can fix this without making the generated lexer structs (struct Lexer above) parametric on user state type, which would allow us to do something like:
struct Lexer<'input, I: Iterator<Item = char> + Clone, S>(
    ::lexgen_util::Lexer<'input, I, (), S, ::std::convert::Infallible, Lexer<'input, I>>,
);

impl<'input, S: Default> Lexer<'input, ::std::str::Chars<'input>, S> {
    fn new(input: &'input str) -> Self {
        Lexer(::lexgen_util::Lexer::new(input))
    }
}

Now Lexer::new would only type check if S: Default is satisfied.
To avoid typing the more complicated type MyLexer<MyLexerState> instead of MyLexer, we could generate a new type and a type synonym:
struct Lexer_<'input, I: Iterator<Item = char> + Clone, S>(
    ::lexgen_util::Lexer<'input, I, (), S, ::std::convert::Infallible, Lexer_<'input, I, S>>,
);

type Lexer<'input, I> = Lexer_<'input, I, LexerState>;

impl<'input, S: Default> Lexer_<'input, ::std::str::Chars<'input>, S> {
    fn new(input: &'input str) -> Self {
        Lexer(::lexgen_util::Lexer::new(input))
    }
}

impl<'input, S> Lexer_<'input, ::std::str::Chars<'input>, S> {
    fn new_with_state(input: &'input str, user_state: S) -> Self {
        Lexer(::lexgen_util::Lexer::new_with_state(input, user_state))
    }
}

Now the code should be backwards compatible and it should no longer require UserState: Default unless new or new_with_input are used.
I wanted to demonstrate the problem in detail but on the way came up with a solution..
WDYT about this solution @alan-j-hu? Would using a type synonym (instead of a struct) for the generated lexer type be a problem?
That said, I think it should be OK to just make new and new_from_iter take a state argument, just to keep the implementation simpler. I'm not sure if it would worth generating an extra type and making the code generator more complicated just so that some users won't have to pass Default::default() to lexer constructor in some cases. Passing Default::default() to constructors doesn't sound too bad.

I don't see any issues with creating a type alias. I'm fine with either the type alias or removing the new and new_from_iter functions, whichever you think is better design for your library.

I wasn't sure how much complexity the solution described above would add to the code generator so wanted to give it a try. It turns  out it's not too bad, so I just implemented it.


New version: Freeplane.Freeplane version 1.9.9

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.0 schema?

Microsoft Reviewers: Open in CodeFlow

/azp run


Xcmsend Application

Project Abstract

XCMSend aims to be the seamless way to interface with chains via XCM, designed to provide an unbiased platform, and user-friendly cross-chain message transfers within the Polkadot ecosystem. Think of a no-code layer to compose transactions.

Grant level

[ ] Level 1:  Up to $10,000, 2 approvals
[x] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (bank details via email or BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) address in the application).
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

I have read and hereby sign the Contributor License Agreement.

@Noc2 ty for the fast response, the application has now been updated to use USDT on polkadot, after the guidelines found here:
https://github.com/w3f/Grants-Program#pencil-process

Thanks @semuelle, we will add Talisman as well as Subconnect in M1.
@Noc2 Hi David, it's true (we agree) xcm should be abstracted away for consumers, perhaps we can be better in our communication of the vision.
We are not trying to build a wallet, instead we are aiming toward building a low-code drag and drop canvass UI that gives non-technical designers, as well as technical developers, a birds-eye-view interface to design workflows that xcm enables, i.e. teleport, swap and all the novel features from chains, such as: governance, time/price scheduling, DAOs, and all the pallets and primitives connections with workflows that are yet to be realised. "Like a Zapier for Substrate".
Users can design transaction flows and use them in their own DApps.
Eventually the name might change but for simplicity, we are naming it with what it will do in the short term, because we don't want to spend any time right now on naming.
Here is a near term vision mockup for how the drag and drop UI will look.

It's a nodal canvass so the user can build diagrams, putting together workflow scenarios made up of pallets from different chains. Anything that is connected by hrmp/xcmp. Users can come up with useful permutations that might be harder to see without this kind of interface.

And when you pair that with real-time updates all in one place, the user will enjoy testing transactions, and become more effective at building the next generation of DApps. And this vision is aligned to the concept  of Cores, an application layer on top of Relay/Parachains, where apps will be leveraging parts of different chains.
so just to clarify we aren't trying to push XCM onto consumers.

Thanks for the comments!
I have updated the application to explain our vision better, which is to be a easy to use gateway for XCM transactions.
@semuelle I agree with you, the average let's say defi users is probably most likely using subwallet, talisman or even metamask for evm compatible chains. We have changed M1 to support the most used browser wallets in the dotsama ecosystem, including Talisman and Subwallet.
@Noc2 Their are several wallets/parachain projects that provide a basic xcm cross chain transfer functionality, but only in a limited way. With XCMSend we want to auto index and support all open channels, letting the network decide what routes are open for the end user. Instead of Cherry-picking 1-6 chains and supporting that. A focus on the Non-bias XCM transactions. As mentioned in the updated application, we want to provide a easy to use gateway into XCM for everyone, web2 companies and client libraries, dapp developers, parachain teams that want to test that their XCM send token functionality is working on Rococo. The vision is to allow a broad usergroup to interact with the dotsama ecosystem using XCM in a hassle-free way.
If I can answer any more questions, don't hesitate to poke me.  Also, we have a presentation of XCMSend, if anyone is interested I can send over the link to it, lmk.
Thanks!

@Noc2 certainly,
The reason behind launching on Rococo is to:
1: Provide a sandbox/playground enviroment where connected connected parachains and users can test XCM functionality.
2: Our goal and roadmap is currently to first launch on Rococo, make sure XCMSend is stable, later launch on Kusama and then finally go to Polkadot. Allowing us to gain feedback from the community during each step of the way, so we can shape XCMSend to as useful as possible. Taking in user feedback on the way.


is there a way to replace handle with custom layout

is there a way to replace handle with custom layout

There's thumbImage on iOS. I don't think it's currently possible in android.

It looks like you wanted to ask a question rather than request the functionality. If you're interested in having thumbImage on Android, please consider sending a PR :)

i want to add some kind of dynamic layout to handler. as example i need to add lable which shows current value and changing color with disabled status. and some alignment issues having with thumbImage solution.


Can't use readableStream's on "data" ?

hello,
I'm trying to get a file content from ftp, without having to write it on disk.
I'm doing the following, but it seems the "data" event is never triggered...
I'm using latest version (v1.3.5).
Code to reproduce:

const Ftp = require('promise-ftp')
const client = new Ftp();
client.connect()
    .then(() => client.get('path-to-file'))
    .then((stream) => {
        return new Promise( (resolve, reject) => {
            let buffer = '';
            stream.once('close', () => resolve(buffer));
            stream.once('error', reject);
            stream.on('data', function (chunk) {
                console.log(chunk.toString());
                buffer += chunk;
            });
        });
    })
    .then(() => client.end());

Am I missing something ?

I ran in the same problem. The 'data'-Event is never fired, because the stream is never written.
You need to add a Writeable.
Try this:
const Ftp = require('promise-ftp')
const client = new Ftp();
client.connect()
    .then(() => client.get('path-to-file'))
    .then((stream) => {
        return new Promise( (resolve, reject) => {

            stream.pipe(new Writable({
                write(chunk, encoding, callback: (error?) => void) {
                    callback();
                }
            }));

            let buffer = '';
            stream.once('close', () => resolve(buffer));
            stream.once('error', reject);
            stream.on('data', function (chunk) {
                console.log(chunk.toString());
                buffer += chunk;
            });
        });
    })
    .then(() => client.end());


Suggestion: One Audio Track at a time

Stax currently encodes all the audio tracks two at a time and then when done starts the video encoding.
I would suggest flipping the order:
Always start the video encoding and then up to one audio track at a time as well.
The audio tracks do not take much processing but can often thrash the hard drives for a long time, this is exasperated when two audio tracks are thrashing the disk at the same time and storage speeds slow to a crawl.
I have had encodes spend an hour on the audio tracks before starting on the video encode.

If Audio encoding is bringing your PC to a crawl then there some other underlining issues with your PC. a single Harddrive (7200rpm) can write at 80MBs+. SSD can write even faster. Which is plenty of some simple audio.
You can alter the Parallel process in the Settings. The Default is set to 2.

The uncompressed raw WAV files that the encoder makes as intermediary states which are all over 5GB each that's the slow down.
I am not running sub standard equipment.

Whatever the case may be, Stax76 is retired and my forked version I don't plan on changing how the audio is processed.

Crap, I thought I was in the Forked Version <IP_ADDRESS>. This is where the crash dialog took me. Very sorry.
Also I can't find the Forked Version page.

It takes awhile to update everything inside the software. Updating the URL had a low priority during the first release. New URL will be included with the next release.
Fork: https://github.com/Revan654/staxrip


Update README.md

Thank you for adding us.I changed loadium url and added selenium support.

Thank you for update.


Add a checkbox for choosing a host.

Hi @anryko ,
For the easy selection of the hosts, would it be possible you to add a checkbox to select the hosts?
For example:

I do not know if this is possible because it must surely add a submit button to activate choices.
Thank you for your reflection on this subject.
Cordially.

Hi @smeapng,
After filtering the required hosts, if count is <=4 you can just press "Enter" to open those.
I'll investigate the possibility to add checkboxes later.
Thanks for the idea.

Hi @anryko ,
Thank you for your answer.
Yes it is true that there is that possibility, but if the names of the machine differs it is not possible to do it with the enter key.
Thank you for the work done on the getDash script, it's great.
Cordially.

Hello @anryko ,
To solve this problem of checkbox, I finally create a generic dashboard that gathers the metrics that are common to all my hosts with a variable to choose the name of the hosts and create in this dashboard a link that calls the script getdash See all metrics).
As this I can select several hosts easily and run them in the getdash script.
Here is a screenshot ("Show All Metric" link call the getdash script): :

Thanks to you for this script.
You can close this request if you wish.
Cordially.

Hey @smeapng
Look good.
Thank you.


Loop in the dfs_search execute only once

I'm running you ToT test. In hotpot/tot.py, the loop in the dfs_search function executes only once: "while stack and it < 1:"
May you fix it?
Thank you!

fixed


Add info to Readme for running MIFC locally and making a PR

To help get people involved I should update the readme to have the necessary info for them to make a PR.

closed with #29

Reopening issue to fix formatting

Closed again with #30


[DOCS] for sample: auth-blocking-functions | Cannot extract event_type

auth-blocking-functions
Given the Google Documentations here to Getting user and context information, some fields are not available on the AuthBlockingEvent dataclass.
For example I can extract the following:
from firebase_admin import initialize_app
from firebase_functions import https_fn, identity_fn, options

initialize_app()

@identity_fn.before_user_signed_in()
def handle_user(
    event: identity_fn.AuthBlockingEvent,
) -> identity_fn.BeforeSignInResponse | None:
    email = event.data.email
    uid = event.data.uid
    event_id = event.event_id
    event_type = event.credential

However, the following does on exist on the even signature.
from firebase_admin import initialize_app
from firebase_functions import https_fn, identity_fn, options

initialize_app()

@identity_fn.before_user_signed_in()
def handle_user(
    event: identity_fn.AuthBlockingEvent,
) -> identity_fn.BeforeSignInResponse | None:
    event_type = event.event_type
    auth_type = event.auth_type
    resource = event.resource
    # etc

Close and moved here https://github.com/firebase/firebase-functions-python/issues/180


⚠ Bofrost.es has degraded performance

In 7f858eb, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1574 ms

Resolved: Bofrost.es performance has improved in 4b208fa after 25 minutes.


Fix indenting that breaks nodes > 1

Depends-On: https://github.com/openstack-k8s-operators/dataplane-operator/pull/429

/test install-yamls-deploy

recheck

@rabi: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name 	Commit 	Details 	Required 	Rerun command
ci/prow/install-yamls-deploy 	eb4fc14 link 	false 	/test install-yamls-deploy
Full PR test history. Your PR dashboard.

I know this is not related to this PR, but this is why install-yamls-deploy failed.  The control plane could not successfully deploy because the Ceilometer deployment hit this:
Warning  Failed          24m (x3 over 25m)    kubelet            Failed to pull image "quay.io/infrawatch/sg-core@sha256:f277dbed6ec445a3b4707b8d3dd71d871feebb8e92ec9995d49e003c6069931d": rpc error: code = Unknown desc = reading manifest sha256:f277dbed6ec445a3b4707b8d3dd71d871feebb8e92ec9995d49e003c6069931d in quay.io/infrawatch/sg-core: manifest unknown: manifest unknown

I checked quay, and indeed that sha256 does not exist for infrawatch/sg-core.

/test install-yamls-deploy

recheck

recheck
jobs fixed

Now the baremetal job is broken with https://github.com/openstack-k8s-operators/edpm-ansible/pull/358.  Testing with https://github.com/openstack-k8s-operators/dataplane-operator/pull/429

recheck


 I received code and returned it, so what did that prove? and how is that linked to "prevents a malicious user from flooding your endpoint with events" ??
for (B) it explains nothing as well. It says to http get some url over some port, then? how the response look like? is it providing a  code and I should match this code with the code that came with the handshake, and if they match if so return the code with 200 and if not return something else? supposing so, again, how is that related to anything about "prevents a malicious user from flooding your endpoint with events"

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

ID: fd2804d1-be50-6dd0-c9ec-a28cdac20137
Version Independent ID: ac404907-c826-32e7-f383-807489a99e35
Content: WebHook event delivery - Azure Event Grid
Content Source: articles/event-grid/webhook-event-delivery.md
Service: event-grid
GitHub Login: @spelluru
Microsoft Alias: spelluru

Thank you for your feedback! We have assigned this issue to the author to review further and take the next course of action.

@jfggdl @robece @Kishp01 - could you please review and respond when you get a chance? Thanks

@MhAllan, thank you very much for your feedback. I will update the documentation according to your concerns. However, I want to make sure that I address your questions.
Regarding (A), the fact that your application is prepared to handle and return the validation code indicates that you were expecting to receive that event and hence you are the one who created the event subscription that sends events to your application. Imagine the scenario that there is no handshake validation supported and a hacker gets to know your application URL. He can create a topic and an event subscription with your application's URL and start conducting a DoS attack to your application by sending a lot of events. The handshake validation prevents that to happen. If someone else get to know your application URL, they can still create an event subscription but because you are not aware of those malicious events coming to your application, you did not implement that validation. That is scenario A.1. Now A.2: imagine that you already have in your app the validation implemented because you created your own event subscriptions. Even if a hacker creates an event subscription with your app URL, your (correct) implementation of the validation request/event will check for the aeg-subscription-name header in the request to ascertain that is an event subscription that you recognize. We will additional documentation to provide this level of clarity. Now scenario A.3: even after that correct handshake implementation, a hacker can flood your app (hey, it already validated the event subscription). To prevent that, you must secure your webhook with AAD authentication: https://docs.microsoft.com/en-us/azure/event-grid/secure-webhook-delivery. That is another clarification that we will add to the documentation.
on (B), if in your validation of the validation event (excuse me for the redundancy), you identify that it is not an event subscription for which you are expecting events, then you would not return a 200 response or event would not even return a response. Hence, the validation will fail.
I hope this clarifies things. Please tag me (@jfggdl) if you have more questions.

I created a work item to update documentation for this.
#please-close

Thank you so much @jfggdl for detailed answer


Styled-theming prevents usage of custom themes

Since styled-theming doesn't allow opening issues I'll open one here.
So, I'm building an UI library with React and Styled Components. We first had pretty extensive theming using the default ThemeProvider setup.
Since this was getting out of hand we decided the implement styled-theming. We now have a bunch of declarations like these:
const borderRadius = theme('layout', {
    [themeLayouts.basic]: '8px',
    [themeLayouts.compact]: '6px',
});

const chipColor = theme('mode', {
    [themeModes.basic]: grey100,
    [themeModes.dark]: white,
    [themeModes.light]: black,
});

export const StyledChip = styled.button`
    border-radius: ${borderRadius};
    color: ${chipColor};
`;

However, now we want to add support for the consumer of the library to add their own layout/mode. While using the default way of theming this was really use to achieve. However, because of the usage of styled-theming I don't see any way on how this is possible since the layouts/modes are hardcoded inside of the UI library.
So my question is: is it correct that styled-theming prevents the consumer of the UI library to add their own custom theming? If so, I'll remove it.

That library isn’t maintained here

@probablyup but it's in the Styled Components repo and the package itself doesn't have the option to open issues?

I believe it was contributed to our org by the original author but is community maintained.
@mxstbr can we get issues turned on for it?

Just for future reference if everyone ever ends up here, this is how I've solved it now:

Changed the import theme from 'styled-theming' to styledTheming from 'styled-theming'.
This was how I had the primary color in my UI kit defined:

const colorPrimary = styledTheming('mode', {
    [themeModes.basic]: purple100,
    [themeModes.dark]: white,
    [themeModes.light]: black,
});

I changed that to this:
const colorPrimary = styledTheming('mode', {
    [themeModes.basic]: ({ theme }) => theme.colorPrimary || purple100,
    [themeModes.dark]: white,
    [themeModes.light]: black,
});

I did this for all of my variables used by styled-theming. In this way the user of my UI kit can overwrite the basic theme by passing properties to the ThemeProvider.


Refactor and fix issues in Editor Dock Manager

Fixes https://github.com/godotengine/godot/issues/88000
Fixes https://github.com/godotengine/godot/issues/87234
Fixes https://github.com/godotengine/godot/issues/74215
Fixes crash when disabling the Filesystem in Editor Features when it is at the bottom. (related: #84125)
Fixes both // FIXME: Find it, in a horribly inefficient way. in EditorDockManager::load_docks_from_config()
Fixes // FIXME: Close all floating docks to avoid crash. in EditorNode::_feature_profile_changed() from #84122

removed close_all_floating_docks()

Fixes dock select popup drawing issues with scaling, sizes, and rtl.
Fixes dock names being untranslated when moving to floating window or to bottom panel.
Fixes clicking on the signals or group button in the Scene Tree Dock while the Node dock is floating shows errors.
related https://github.com/godotengine/godot/pull/84193

Implementation Details
EditorDockManager

Added DockInfo struct and a HashMap<Control *, DockInfo> of all docks to be able to easily access information on docks.

This replaces the bottom_docks Vector.

Replaced _edit_current() with _update_layout() to handle all updating that needs to happen after any dock moves. Previously some actions like floating a dock wouldn't save the layout, so it wouldn't restore if a crash occurs.
Docks disabled with Editor features are moved out of the dock and hidden, instead of using hidden tabs. They use set_dock_enabled() which sets a flag and closes or opens the dock.
close_dock() will hide the dock and move it out of the tab container, so it doesn't affect anything and isn't seen in the dock menu. open_dock() will restore the dock to its previous location. These will also be useful for https://github.com/godotengine/godot-proposals/issues/8206
Saving a closed disabled dock will still add it to a slot so we know where to restore it to after loading, just like floating windows.
Saving bottom docks was changed to do the same so it is more like closed and floating docks. This means that previous layouts with a bottom dock will need to be resaved.
Simplified and made private _update_dock_slots_visibility() because hidden tabs no longer need to be checked.
Added _move_dock() to handle moving the dock, to make sure it is always properly handled when removed from the bottom panel or a floating window, and making sure the title is set when moving to a TabContainer.
focus_dock() handles focusing on a dock no matter where it is.

Extracts the dock popup into its own class DockContextPopup. (https://github.com/godotengine/godot/pull/84193#discussion_r1452675069)

It now operates on a dock Control, rather than indexes for the dock and bottom panel item.
Added tooltips for the L/R move tab buttons.
The docks are drawn now at the appropriate position when in rtl.
Editor scale is now used for tab drawing.

Before (150%):

After (150%):

Size issues when buttons were added/removed are fixed.

Before:

After:

Docks at the bottom panel can now float directly (https://github.com/godotengine/godot/pull/86765#issuecomment-1904962229).
Tabs can be right clicked to open the popup.

Changes:

Removed the layout_changed signal and instead use save_editor_layout_delayed(). This prevents unnecessarily saving multiple times in a row. This saving is only really in case of a crash, and it doesn't need to happen immediately.
_dock_container_update_visibility() replaces _update_dock_slots_visibility(), and it just updates the one tab container's visibility when it is needed, when a child is added or removed.
set_docks_visible() handle updating the dock slots visibility itself.
Connected dock slots to active_tab_rearranged to make sure layout is updated when dragging a tab within itself.
Made sure _update_layout() only happens once after docks have been moved.
Changed DockInfo name to title to be more accurate and better distinguish from when the Control's name is used instead.
Fix Bottom Dock context menu position when not in fullscreen.
Rebased.

Does EditorNode::edit_current() need to be called whenever the layout changes?
I have it there because it was being called when the layout changed in some cases, but I don't know if it is actually needed.

Rebased to fix merge conflicts.
Shortcut is now saved in dock info instead of in the meta.
Also fixed to show translated dock title in floating window.

Thanks!


Closes: #1

Updated validations.py python script
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

Updated the file as per the instruction give by the instructor


Feature Support bitmap for materialized index.

Proposed changes
Not ready to review...
Problem summary
todo...
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.69 seconds
load time: 429 seconds
storage size:<PHONE_NUMBER>5 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221206143158_clickbench_pr_58822.html


Emmet BEM filter doesn't work as expected

I'm trying to use bem filter with emmet. But I get modifiers instead of elements and other way around.

VSCode Version:  1.21.0
OS Version: OSX: High Sierra

Steps to Reproduce:

Type article.post>p.__title+.date.__date|bem and press TAB to expand. From this I would expect following output:

  <date class="post__date"></date>

But instead I get:

  <date class="post post--date"></date>

So it's clear that filter interprets __ as a modifier and other way around. .

Does this issue occur when all extensions are disabled?: Yes
Thanks for checking this out :)

@OlegIvaniv Can you share your the values you set for the emmet.preferences setting?

@ramya-rao-a I don't haven any emmet.preferences setting.

@OlegIvaniv You need to use article.post>p.-title+date.-date|bem to get

  <date class="post__date"></date>

bem.elementSeparator and bem.modifierSeparator control what the class name should be in the expanded abbreviation. I believe you thought they referred to the operator/symbols used in the abbreviation
See https://docs.emmet.io/filters/bem/