Create db only if doesn't exist yet

This is a follow-up of https://github.com/influxdb/influxdb-python/pull/274

@slomek Have you taken a look at the tests failures?

Yep, I've had some issues with running them locally. I've changed the default behaviour to create dbs if they do not exist, but also added a flag if you want to fail anyway (and not to delete one of your tests). This breaks backward compatibility a little, but in my opinion it would be better this way.

@aviau Can you merge this or is there anything else I should fix first?

@slomek I am sorry for the long response time. Can you please switch the default around? Some people may rely on this throwing exceptions and I think its a saner default.
I will merge right after!

No problem, @aviau. Take a look on it now.

Thanks!!


differences in str(float) between Python 2 and 3

The fonttools xmlWriter also has the same problem with str(float) in python 2 and 3 as ufoLib, so I pinpoint the issue in here as well:
https://github.com/unified-font-object/ufoLib/issues/19
See for example:
https://github.com/behdad/fonttools/blob/master/Lib/fontTools/misc/xmlWriter.py#L146

I think we can close this now?


Error: more than one library with package name 'com.google.android.gms'

I have already made sure I have all the packages required installed via the SDK manager. When I try to build I get the follow error:
:processArmv7DebugResources FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':processArmv7DebugResources'.
> Error: more than one library with package name 'com.google.android.gms'
  You can temporarily disable this error with android.enforceUniquePackageName=false
  However, this is temporary and will be enforced in 1.0

Could you please list all the plugins, and check if any other plugin causing conflict?

I am also having this issue; plugin list:
com.flyingsoftgames.xapkreader 0.9.0 "Cordova Expansion File Reader"
com.google.playservices 21.0.0 "Google Play Services for Android"
cordova-plugin-admobpro 2.8.4 "AdMob Plugin Pro"
cordova-plugin-extension 1.1.4 "Cordova Plugin Extension"
cordova-plugin-shake 0.5.1 "Shake Gesture Detection"
cordova-plugin-whitelist 1.0.0 "Whitelist"
org.apache.cordova.device 0.3.0 "Device"
org.apache.cordova.device-motion 0.2.11 "Device Motion"

com.google.playservices 21.0.0 "Google Play Services for Android"
Please remove the plugin, as it's deprecated and not needed any more. It will cause conflict.
It's documented in the wiki page, please read for more details.

Which file to make the changes in?

cordova plugin remove com.google.playservices

This worked for me. Thank you very much.

getting same error on phonegap build. will u help me please?

Please check if you have the same reason. The google play framework is described as dependent in plugin.xml, it will be auto loaded. You should not install the library as another plugin, or else it will cause conflict.

i checked its conflicting with cordova admob plugin, but i want both working, what to do ? any help?

please list all the plugins you have in your project.

hey not able to post plugin:
plugin name="phonegap-plugin-push" source="npm">

<gap:plugin name="nl.x-services.plugins.socialsharing" /

plugin name="phonegap-plugin-push" source="npm">
param name="SENDER_ID" value="289031261344" />
/plugin>
plugin name="com.admob.google" spec="4.0.8" source="pgb" />
plugin name="cordova-plugin-media-capture" source="npm" spec="~1.2.0"/>
plugin name="cordova-plugin-console" source="npm" spec="~1.0.2"/>
plugin name="cordova-plugin-device" source="npm" spec="~1.1.1"/>
plugin name="cordova-plugin-device-motion" source="npm" spec="~1.2.0"/>
plugin name="cordova-plugin-device-orientation" source="npm" spec="~1.0.2"/>
plugin name="cordova-plugin-dialogs" source="npm" spec="~1.2.0"/>
plugin name="cordova-plugin-file" source="npm" spec="~4.1.1"/>
plugin name="cordova-plugin-file-transfer" source="npm" spec="~1.5.0"/>
plugin name="cordova-plugin-globalization" source="npm" spec="~1.0.3"/>
plugin name="cordova-plugin-inappbrowser" source="npm" spec="~1.3.0"/>
plugin name="cordova-plugin-media" source="npm" spec="~2.2.0"/>
plugin name="cordova-plugin-network-information" source="npm" spec="~1.2.0"/>
plugin name="cordova-plugin-splashscreen" source="npm" spec="~3.2.1"/>
plugin name="cordova-plugin-statusbar" source="npm" spec="~2.1.2"/>
plugin name="cordova-plugin-vibration" source="npm" spec="~2.1.0"/>
plugin name="cordova-plugin-whitelist" source="npm" spec="~1.2.1"/>
plugin name="io.litehelpers.cordova.sqlitestorage" spec="0.7.5" source="pgb" />
plugin name="org.tt.plugin.tts" spec="1" source="pgb" />
gap:plugin name="nl.x-services.plugins.socialsharing" />

You are using the wrong AdMob plugin, please remove the plugin com.admob.google, use cordova-plugin-admobpro.


ref tags are not identified and therefore the use of them may output incorrect warnings

I get:
[19:05:10] WARNING: cannot find 'ddDashboardListButtonRef' in type 'Index' Ln 19 Col 21 /src/dashboard/index.html
for the following html:
  <button click.delegate="onDashboardListDDClick(ddDashboardListButtonRef.attributes['aria-expanded'].value)" id="ddDashboardList"                         ref="ddDashboardListButtonRef" type="button" class="btn btn-sm btn-default dropdown-toggle" data-toggle="dropdown">                                                                                --------------------------------                             ${currentSelectedDashboard.entity.name}                         </button>
ddDashboardListButtonRef is mistakenly looked for in the ts file, but it shouldn't be there.
It's a valid html element.

published to 0.9.9


Speed Parameter of Polyphonic-tracks

Changing the 'speed' of polyphonic tracks upon the chromatic page only affects the currently selected track not the total of all poly-tracks

fixed.


It does not show other people nearby

Hello, i've compiled and installed the app in two iphone 5 with 8.1 installed , but when i run it and put the username in form, but don't show  the people nearby. How it's possibile ? it dosen't work anymore?
Another question, theoretically it is possible ti implement this in android ? or the bluetooth signal search only ios device?
Thanks
Alex

I also haven't been able to discover anyone nearby, testing with 3 different devices (iPhone 5, 6, and 6 Plus) and none of them can see each other.

Posted #25


Is server do not support patch operation?

I've got no route error when functions with patch operation like below was triggered.

container
    .item('some_id')
    .patch([{
        op: 'add',
        path: '/some_paths',
        value: 'some_value'
    }])

Patch operation is this
https://learn.microsoft.com/en-us/azure/cosmos-db/partial-document-update
Full response was like this
{
      code: 400,
      body: { message: 'no route' },
      headers: {
        'content-type': 'application/json',
        'content-location': 'https://localhost:8081/dbs/next-auth/colls/users/docs/15b91394-2982-409f-8f71-024f4594872c',
        connection: 'close',
        'x-ms-activity-id': '8e4f9947-c8bc-4ba4-a624-42a169fbdb14',
        'x-ms-request-charge': '1',
        date: 'Wed, 01 Feb 2023 18:03:57 GMT',
        'content-length': '22',
        'x-ms-throttle-retry-count': 0,
        'x-ms-throttle-retry-wait-time-ms': 0
      },
      activityId: '8e4f9947-c8bc-4ba4-a624-42a169fbdb14'
    }

And also, Offset-Limit clause is not implemented right?


Some famous algorithms not yet included [SWoC]

Found some famous algorithms that are not yet included in the library. Please go through it and mention those on which I can work
Dynammic Programming based :-

count all possible paths from top left to bottom right in a square matric
longest palindromic subsequence
number of unique (structurally different) BST with given number of nodes
rod cutting problem

Greedy based :-

fractional knapsnack
minimum spanning tree
activity selection

Tree based :-

symmetric tree
level order traversal
zigziag level order traversal
maximum depth of binary tree
invert binary tree

Hi @Abhijit2505 .
I also noticed that some of the major algorithms in string pattern matching and many others are not yet available here.
I would also want to work on these algorithms for SWOC if available!
Thanks.

Hi @Abhijit2505 .
I also noticed that some of the major algorithms in string pattern matching and many others are not yet available here.
I would also want to work on these algorithms for SWOC if available!
Thanks.

We know there are algorithms which are not included in the package.  Don't open an issue collectively, instead create issues of algorithms one by one.

We know there are algorithms which are not included in the package.  Don't open an issue collectively, instead create issues of algorithms one by one.


export: don't export branch node's key in snapshot

in IAVL, a branch node's key is always the smallest leaf key in it's right branch, the key can be infered during the import process, so no need to include it in the snapshot at all.
Migration process

Step 1, change the import logic to derive the branch node's key on the fly, ignore the one included in the snapshot, this is not a consensus breaking change.
Step 2, change the export logic to skip branch node's key, this should be considered as a breaking change and need a coordinated upgrade, so the snapshots created after the upgrade are updated consistently across the network.

Do we need to update the snapshot format version for this?
Consequences
Positives

Reduce snapshot size, say L is the number of leave nodes, previously we export 2 * L - 1 keys and L values, now we export L keys and L values, if key and value are the same length on average, it reduces 30% size of snapshot.
In the future, can apply delta encoding to the leaf keys to further reduce snapshot size, since the leaf keys are exported in order, apply delta encoding to it should produce very good compression rate.

fixed by #703


CTRL + C not working

ALL THAT IS NECESSARY:
Steps to reproduce

Run python script
Hit CTRL + C to stop

Expected behavior:
The python script stops
Actual behavior:
The python script doesn't stop
Reproduces how often:
85%
OS name and version:
Platformio-ide-terminal version:

Thank you for reaching out with this bug report.
You are getting this reply because the issue template was not filled in its entirety, overwritten,  or some portions were partially left out.
This issue template contains important information to be able to provide any kind of support, and will help us triage or reproduce the issue. Without reproduction no workaround or fix can normally be derived...
Copy and paste the template located at https://raw.githubusercontent.com/platformio/platformio-atom-ide-terminal/master/.github/ISSUE_TEMPLATE.md and fill in all fields. Logs / Errors / other information should be added at the bottom in the Notes portion of the issue template.
Tickets without this information may be closed and labeled invalid at our discretion.
Thank you for your understanding.

Turns out this is a git issue See https://github.com/git-for-windows/git/issues/1470

I closed this for 2 reasons,

Not enough info provided to duplicate despite @UGEYT insisting there no other requirements needed.
Since cant duplicate and after waiting nearly a month for a reply, its plain to see, its not possible to help those who cant/wont help other help them.

I usually lock threads once closed, but Ill leave this open in case @UGEYT provides step by step instructions The OS type, etc that was missing and provides an example script or anything hat will allow someone to replicate this.
Once that is done Ill reopen this. =)


Setting up proxy for deployment

Is your feature request related to a problem? Please describe.
As a contributor, I want the deployment front-end to communicate with the API server so that the application works on the production build.
Describe the solution you'd like
I've set up two servers for front-end and back-end and they need to be able to communicate with each other. Since the front-end uses relative URL's for API calls, these need to be redirected to the correct place.
This is done by adding a static.json file to the front-end folder that routes requests prefixed with /api/ to the API server. This affects only the production build.
Describe alternatives you've considered
Normally the back-end server also serves static front-end files so only a single server is running, but it's a pain to do due to the folder structure.
Additional context
N/A

If folder structure is a pain point, have we considered symlinking the frontend build directory to somewhere convenient in the backend side? (But that might cause problems for Windows git users who have turned of symlinking)
But this works - I approve.

Alternatively, might be worth investigating a build step that moves the the
built frontend (which will be in the build folder in the frontend after
running npm run build) into a suitable place in the backend?
On Mon, Mar 16, 2020 at 11:12 PM Ernest Wong<EMAIL_ADDRESS>wrote:

If folder structure is a pain point, have we considered symlinking the
frontend build directory to somewhere convenient in the backend side? (But
that might cause problems for Windows git users who have turned of
symlinking)
But this works - I approve.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/se701-group6/se701-assignment1/issues/60#issuecomment-599451344,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANUN6QDD4MHCSNNYJLPRC3RHX3QDANCNFSM4LL7BIJQ
.

Alternatively, might be worth investigating a build step that moves the the built frontend (which will be in the build folder in the frontend after running npm run build) into a suitable place in the backend?
…
On Mon, Mar 16, 2020 at 11:12 PM Ernest Wong @.***> wrote: If folder structure is a pain point, have we considered symlinking the frontend build directory to somewhere convenient in the backend side? (But that might cause problems for Windows git users who have turned of symlinking) But this works - I approve. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#60 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANUN6QDD4MHCSNNYJLPRC3RHX3QDANCNFSM4LL7BIJQ .

The entry point would need to be in the root directory, with a package.json that builds frontend and server. This way server.js can see the build folder but still needs to be configured to serve the build files. I think this can be revisited, but the current solution is (probably) easier?

I approve

I approve


EPERM error attempting to run example

Trying to run the following code:
var puppeteer = require("puppeteer");

puppeteer.launch().then(async browser => {
    let page = await browser.newPage();
    await page.goto('https://google.com');
    await page.screenshot({ path: 'screenshot.png' });
    browser.close();
});

I got an error:
Error: EPERM: operation not permitted, unlink 'C:\Users\tivac\Desktop\puppeteer-testing\node_modules\puppeteer\.dev_profile1\CrashpadMetrics-active.pma'
In the course of debugging this set DEBUG=* to try and understand where things were failing, but after doing that it then worked fine. 😕
Does the first-run experience not quite work right in non-DEBUG modes? I'm not sure, but that's what happened for me!

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Windows 10 Version 1607 (OS Build 14393.1593)

Speculating: you might've accidentally launched the script twice, and two parallel puppeteers tried to run chrome with the same profile folder - .dev_profile1.
We should generate profile folder names randomly so that parallel runs of puppeteer work fine.

It's possible! Seems unlikely though as I was launching node via the CLI and not doing anything different beyond originally setting headless : false since I wanted to see the browser. It repro'd every time until setting DEBUG, at which point everything began working perfectly.

+1

Hi,
I freshly used with only puppeteer, but still got the same error. I used the https://github.com/GoogleChrome/puppeteer/#usage first example script.

I've been running into this problem as well, though with an even simpler example script that just launches the browser and then immediately tries to close it:
const puppeteer = require('puppeteer');

(async () => {
  console.log("Launching browser.");

  const browser = await puppeteer.launch();

  console.log("Closing browser.");

  browser.close();
})();

I've tried manually deleting the node_modules/puppeteer/.dev_profile1 directory before running this script, and the error still occurs.
As a workaround, I've found that simply calling process.exit(0) when I'm finished works okay--puppeteer seems to be very nice about cleaning up after itself even in the case of unexpected process termination, so that's great!

I was seeing this the first couple times I ran the usage demo, but I didn't get it every time. About ten minutes later, I see far more successes than errors running the script. I'm not sure if that helps or not.

same problem, windows 10, node v7.10.0, puppeteer 1.0.0. setting DEBUG=* doesn't help, tried running as admin
D:\puppeteer>node index.js
fs.js:1081
  return binding.unlink(pathModule._makeLong(path));
                 ^

Error: EPERM: operation not permitted, unlink 'D:\puppeteer\node_modules\puppeteer\.dev_profile1\CrashpadMetrics-active.pma'
    at Object.fs.unlinkSync (fs.js:1081:18)
    at fixWinEPERMSync (D:\puppeteer\node_modules\rimraf\rimraf.js:210:13)
    at rimrafSync (D:\puppeteer\node_modules\rimraf\rimraf.js:310:28)
    at D:\puppeteer\node_modules\rimraf\rimraf.js:341:5
    at Array.forEach (native)
    at rmkidsSync (D:\puppeteer\node_modules\rimraf\rimraf.js:340:26)
    at rmdirSync (D:\puppeteer\node_modules\rimraf\rimraf.js:333:7)
    at fixWinEPERMSync (D:\puppeteer\node_modules\rimraf\rimraf.js:208:5)
    at rimrafSync (D:\puppeteer\node_modules\rimraf\rimraf.js:310:28)
    at ChildProcess.chromeProcess.on (D:\puppeteer\node_modules\puppeteer\lib\Launcher.js:87:7)

+1

same problem, windows 10, node v8.4.0, puppeteer 0.9.0

Everybody: could you please check if tip-of-tree puppeteer works for you? There have been some changes that might address this.

Windows 7 x64, Node .js 8.4.0.
With tip-of-tree puppeteer and example code from README.md, now I consistently get this error:
(node:1040) UnhandledPromiseRejectionWarning:
Unhandled promise rejection (rejection id: 1):
Error: EPERM: operation not permitted,
unlink 'c:\Windows\Temp\puppeteer_dev_profile-dgXrpD\CrashpadMetrics-active.pma'

(node:1040) [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.

Profile folders remain in the c:\Windows\Temp\.

Each folders contains 2 locked files:
DevToolsActivePort
CrashpadMetrics-active.pma

I didn't have any issues when I installed from latest. Caveat: I used a very different setup than what I had when I posted on this issue. At that time, I was integrating Puppeteer into an existing project, and after I got the error a couple of times, it just stopped erroring for some reason.
However, I wanted to give this update a test. I figured creating a new project was the easiest way to test this. I created a new project. I installed with yarn add puppeteer@latest. I ran an index.js file containing the readme example, and everything worked just fine every time I executed it. So... maybe it's fixed? Like I said, this was a different setup than what I had before, so it's not a terribly scientific experiment.

FWIW:
'use strict';

const puppeteer = require('puppeteer');

(async () => {
  const browser = await puppeteer.launch();
  const page = await browser.newPage();
  await page.goto('https://example.com');
  await page.screenshot({path: 'example.png'});

  try { await browser.close(); } catch (err) { console.log(err); }
})();

{ Error: EPERM: operation not permitted,
  unlink 'c:\Windows\Temp\puppeteer_dev_profile-l29R2q\CrashpadMetrics-active.pma'
    at Object.fs.unlinkSync (fs.js:1067:18)
    at fixWinEPERMSync (node_modules\rimraf\rimraf.js:210:13)
    at rimrafSync (node_modules\rimraf\rimraf.js:310:28)
    at node_modules\rimraf\rimraf.js:341:5
    at Array.forEach (<anonymous>)
    at rmkidsSync (node_modules\rimraf\rimraf.js:340:26)
    at rmdirSync (node_modules\rimraf\rimraf.js:333:7)
    at fixWinEPERMSync (node_modules\rimraf\rimraf.js:208:5)
    at rimrafSync (node_modules\rimraf\rimraf.js:310:28)
    at killChromeAndCleanup (node_modules\puppeteer\lib\Launcher.js:103:7)
  errno: -4048,
  code: 'EPERM',
  syscall: 'unlink',
  path: 'c:\\Windows\\Temp\\puppeteer_dev_profile-l29R2q\\CrashpadMetrics-active.pma' }

I am getting the same unlink error on CrashpadMetrics-active.pma.
Windows 7 Pro machine with fresh installs of Node 8.4.0 and puppeteer 0.9.0 from yesterday.

Seems to be fixed for me (Windows 7 x 64) after https://github.com/GoogleChrome/puppeteer/commit/ac109dba6ddaa62a32fe920e864238d41bf22251

Yes, should be fixed now.

I got same problem with default chromium instillation with puppeteer but I solved by using chrome instead of the chromium

I am using puppeteer to extract data and push it into a db since the data is more i subdivided the data and running multiple instances in different computers but then i am getting the same error. Please help @aslushnikov

+1

I have a solution, you have to close the page before closing the browser. Of course if you have more pages open, close all of them.
             await page.close();             await browser.close();

I have been closing the page, but this problem appears only in windows so i used ubuntu and everything went smoothly

Having the same issue ... can anyone help to take a look ? Thanks!

+1 headless true/false, and await closing browser made no difference. Windows 10 puppeteer v5.2.1

I just got the same issue once, it seems to be random on win 10, puppeteer 4.0.1, I think this bug should be reopened

Same problem for me! Windows 10, puppeteer v5.2.1.

Same problem, no issues when running headless.

Same , error happens on windows 10

Same over here

Same Problem here.
[Error: EPERM: operation not permitted, unlink 'C:\Users\xxxxxx\AppData\Local\Temp\1\puppeteer_dev_chrome_profile-sj0wiy\CrashpadMetrics-active.pma'] {
errno: -4048,
code: 'EPERM',
syscall: 'unlink',
path: 'C:\Users\xxxxxxx\AppData\Local\Temp\1\puppeteer_dev_chrome_profile-sj0wiy\CrashpadMetrics-active.pma'
}
Can some one open the issue with the dev team?

Any news regarding the issue?

We still get this with 5.2.1

Seeing this on 5.3.1 as well

I'm getting this on 5.3.1 as well.

Please, reopen this issue. Still happening.

I have a solution, you have to close the page before closing the browser. Of course if you have more pages open, close all of them.
 await page.close(); await browser.close();

Was having an issue with await browser.close() but thanks to @ivangergo3's answer adding a couple lines to close all the pages gets rid of the crash error! 😄
let pages = await browser.pages()
await Promise.all(pages.map(page =>page.close())
await browser.close()

let pages = await browser.pages()
await Promise.all(pages.map(page =>page.close())
await browser.close()

let pages = await browser.pages()
await Promise.all(pages.map(page =>page.close())) //one closing bracket is missing in the above code
await browser.close()

I am closing all the pages before closing browser, but still seeing this issue. Anyone else the same?

i have same problem with multiples open and close chromium, i think it's concurrence

I ended up fixing it in a somewhat ugly way by doing browser.process().kill('SIGKILL'); instead of await browser.close(); And the issue never happended again. Any drawbacks of this?

Yes the drawback is that it's not documented in the api and it's a
workaround not a solution. The puppeteer dev team should push a fix. Thanks
anyway for the notice :-)
On Fri, Dec 18, 2020, 06:03 caihongxu<EMAIL_ADDRESS>wrote:

I ended up fixing it in a somewhat ugly way by doing
browser.process().kill('SIGKILL'); instead of await browser.close(); And
the issue never happended again. Any drawbacks of this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/puppeteer/puppeteer/issues/298#issuecomment-747869465,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACLIE5B26YARSKBV22ZNKATSVLPBJANCNFSM4DXFG7VQ
.

Hello guys, just had this error in the latest version, in my case it was because I forgot an "await" before a "browser.close()". So you should close the browser like this :
await browser.close()

My await was already missing before, but It didn't show any error before I installed my project on another computer. So make sure not to forget your awaits just like me :P

Hello guys, just had this error in the latest version, in my case it was because I forgot an "await" before a "browser.close()". So you should close the browser like this :
await browser.close()

My await was already missing before, but It didn't show any error before I installed my project on another computer. So make sure not to forget your awaits just like me :P

Hello,
Neither closing all pages before closing browser or using browser.process().kill('SIGKILL'); is working for me. The issue occurs randomly.

Hello,
Neither closing all pages before closing browser or using browser.process().kill('SIGKILL'); is working for me. The issue occurs randomly.

~Hello guys, just had this error in the latest version, in my case it was because I forgot an "await" before a "browser.close()". So you should close the browser like this :~
await browser.close()

~My await was already missing before, but It didn't show any error before I installed my project on another computer. So make sure not to forget your awaits just like me :P~
EDIT : Nevermind, it happens randomly even after making sure the await is there. And The issue started appearing on other projects that were fine before.

+1

~Hello guys, just had this error in the latest version, in my case it was because I forgot an "await" before a "browser.close()". So you should close the browser like this :~
await browser.close()

~My await was already missing before, but It didn't show any error before I installed my project on another computer. So make sure not to forget your awaits just like me :P~
EDIT : Nevermind, it happens randomly even after making sure the await is there. And The issue started appearing on other projects that were fine before.

+1

您好，
在关闭浏览器之前关闭所有页面或使用browser.process().kill('SIGKILL');都对我不起作用。该问题是随机发生的。

+1

您好，
在关闭浏览器之前关闭所有页面或使用browser.process().kill('SIGKILL');都对我不起作用。该问题是随机发生的。

+1

Hello,
Neither closing all pages before closing browser or using browser.process().kill('SIGKILL'); is working for me. The issue occurs randomly.

+1

Hello,
Neither closing all pages before closing browser or using browser.process().kill('SIGKILL'); is working for me. The issue occurs randomly.

+1

Hello,
Neither closing all pages before closing browser or using browser.process().kill('SIGKILL'); is working for me. The issue occurs randomly.

Note that you use browser.process().kill() in place of await browser.close(). not after it.

Hello,
Neither closing all pages before closing browser or using browser.process().kill('SIGKILL'); is working for me. The issue occurs randomly.

Note that you use browser.process().kill() in place of await browser.close(). not after it.

I have the same issue and tried all above suggestion. The problem is that this error is only being logged, not thrown. This fucks with the application flow, as the error becomes undetected!

I have the same issue and tried all above suggestion. The problem is that this error is only being logged, not thrown. This fucks with the application flow, as the error becomes undetected!

browser.process().kill

Using browser.process().kill() had been working well for me so far (since the last time I posted). Note that in order for this to work you need to remove both browser.close() and page.close() code, otherwise you will still get stuck.

browser.process().kill

Using browser.process().kill() had been working well for me so far (since the last time I posted). Note that in order for this to work you need to remove both browser.close() and page.close() code, otherwise you will still get stuck.

Closing all browser pages before invoking close() worked for me (thanks @ CreativeBuilds)
const pages = await browser.pages();
await Promise.all(pages.map(page => page.close()));
await browser.close();

browser.process().kill

Using browser.process().kill() had been working well for me so far (since the last time I posted). Note that in order for this to work you need to remove both browser.close() and page.close() code, otherwise you will still get stuck.

Not working for me :(

I started getting this error on a Windows box but was after other changes I made trying to get puppeteer to run in a Debian VM. One of the things I had to do for Debian was to add  '--no-sandbox', '--disable-setuid-sandbox' arguments. Once I removed those, it started working on Windows again.
I forget the exact reason I had needed to add them to for Debian.

~Hello guys, just had this error in the latest version, in my case it was because I forgot an "await" before a "browser.close()". So you should close the browser like this :~
await browser.close()

~My await was already missing before, but It didn't show any error before I installed my project on another computer. So make sure not to forget your awaits just like me :P~
EDIT : Nevermind, it happens randomly even after making sure the await is there. And The issue started appearing on other projects that were fine before.

+1

+1

The workaround isn't working for me, I believe the reproduction of this bug is dependent on how fast the computer is.
This is my repro, gets the EPERM after 1-5 loops:
const puppeteer = require('puppeteer');
const sleep = ms => new Promise(resolve => setTimeout(resolve, ms));
(async () => {
	while (true) {
		console.log('launching');
		const browser = await puppeteer.launch({ headless: false, args: ['--no-sandbox'] });
		console.log('sleeping');
		await sleep(1000);
		console.log('closing pages');
		await Promise.all((await browser.pages()).map(async page => await page.close()));
		console.log('closing');
		await browser.close();
		console.log('sleeping');
		await sleep(1000);
	}
})();

I believe the headless: false, --no-sandbox, closing each page, and also the console.logs, all make the entire thing somehow slower in the right places, and cause the crashpad process to stay alive long enough so that rimrafs timeouts and throws the error (about 600ms).
A possible solution (which is bad but works) is to increase rimrafs maxBusyTries option so that it would retry a bit more, eventually it works. A better solution is to disable the crashpad process - #2778.

The workaround isn't working for me, I believe the reproduction of this bug is dependent on how fast the computer is.
This is my repro, gets the EPERM after 1-5 loops:
const puppeteer = require('puppeteer');
const sleep = ms => new Promise(resolve => setTimeout(resolve, ms));
(async () => {
	while (true) {
		console.log('launching');
		const browser = await puppeteer.launch({ headless: false, args: ['--no-sandbox'] });
		console.log('sleeping');
		await sleep(1000);
		console.log('closing pages');
		await Promise.all((await browser.pages()).map(async page => await page.close()));
		console.log('closing');
		await browser.close();
		console.log('sleeping');
		await sleep(1000);
	}
})();

I believe the headless: false, --no-sandbox, closing each page, and also the console.logs, all make the entire thing somehow slower in the right places, and cause the crashpad process to stay alive long enough so that rimrafs timeouts and throws the error (about 600ms).
A possible solution (which is bad but works) is to increase rimrafs maxBusyTries option so that it would retry a bit more, eventually it works. A better solution is to disable the crashpad process - #2778.

Disabling crashpad is actually not working, so not solving the initial issue

Removing "args: ["--no-sandbox"]" from my "jest-puppeteer.config.js" file, module.exports object makes this work on windows 10. My module.exports now looks like:
module.exports = {
launch: {
headless: false,
ignoreHTTPSErrors: true,
defaultViewport: { width: 1600, height: 900 },
// slowMo: 100,
// devtools: true,
},
};
my package.json looks like:
{
"name": "jest-cucumber-puppeteer-testing",
"version": "1.0.0",
"description": "jest cucumber puppeteer testing prototype",
"main": "index.js",
"scripts": {
"test": "env-cmd -f .env jest --runInBand",
"report": "node ./cucumber-report-config.js"
},
"runner": "jest-serial-runner",
"author": "",
"license": "",
"dependencies": {
"@types/expect-puppeteer": "^4.4.3",
"@types/jest-environment-puppeteer": "^4.3.2",
"@types/puppeteer": "^3.0.1",
"cucumber-html-reporter": "^5.2.0",
"dotenv": "^8.2.0",
"env-cmd": "^10.1.0",
"i": "^0.3.6",
"jasmine": "^3.7.0",
"jest-cucumber": "2.0.12",
"jest-puppeteer": "^4.4.0",
"jest-serial-runner": "^1.1.0",
"puppeteer": "^5.5.0",
"yarn": "^1.22.10"
},
"jest": {
"preset": "jest-puppeteer",
"setupFiles": [
"dotenv/config"
],
"testMatch": [
"**/*.steps.js"
],
"reporters": [
"default",
[
"./node_modules/jest-cucumber/dist/src/reporter",
{
"formatter": "json"
}
]
]
}
}

Closing all browser pages before invoking close() worked for me (thanks @ CreativeBuilds)
const pages = await browser.pages();
await Promise.all(pages.map(page => page.close()));
await browser.close();

Still not work for me, I've tried all approach above, but no one work for me :(

I started getting this error on a Windows box but it was after other changes I made trying to get puppeteer to run in a Debian VM. One of the things I had to do for Debian was to add '--no-sandbox', '--disable-setuid-sandbox' arguments. Once I removed those, it started working on Windows again.
I forget the exact reason I had needed to add them to for Debian.

I had the exact same situation and this seems to have worked for me

https://github.com/puppeteer/puppeteer/issues/6946 is the only real fix short of switching away from Windows.

I would like to report that, while this fix works (I prefer resolved vs rejected) and doesn't hang the browser, there is still a lot of instability caused by removing the temporary directory. Our production service on Windows crashes ever so often due to that. Right now the way we patched this is to schedule (setTimeout) deleting temp folder after a minute instead of immediately during close. Will report if this fully resolves the problem.

https://github.com/puppeteer/puppeteer/issues/6341#issuecomment-1002066697

@MahbbRah sadly doesn't work. This is not user profile but crashpad and metrics.

@MahbbRah sadly doesn't work. This is not a user profile but a crashpad and metrics.

For me as well it didn't work. the issue is it kept working suddenly got that bug again. But Yes I fixed it for my case it was this issue and this way I solved it.

Hello, I know it's not the prettiest thing, but I managed to solve this error using the home page that is created when using "puppeteer.launch()" instead of creating a new page,
I changed:
const page = wait browser.newPage();
for:
const pages = await browser.pages();
const firstPage = page[0]
By Cromium's rule, if all tabs/pages are closed it will also close so you don't need to use the command "await browser.close()"
at the end of it all.


Set up CI with Azure Pipelines

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Better readme detection

https://github.com/gogits/gogs/blob/master/modules/base/markdown.go#L66
I made a test case in a project called ReadmeTest.php which is getting displayed as a readme file instead of code. This should probably use a regex: ^readme(\.|$).

Thanks your report!
But it's duplicated to https://github.com/gogits/gogs/issues/877 , so I'm closing this and please follow on that one.


project

Hi,
I was wondering if it would be ok to make this the official TrinityCore account creator, forking it under https://github.com/TrinityCore and maybe improving it over time if users report issues and such (like adding support to master branch if it doesn't already). What do you think about it ?
Kind regards
jackpoz

Hi jackpoz,
Sure, no problem! I got another job after creating this so I haven't had time to work on it at all. It currently only supports the 3.3.5a branch (well, as of the last commit date), but it should be refactored to use SOAP instead so that it's branch-independent - just haven't had time.
Feel free to modify it and use it to your liking.
Thanks!

see https://github.com/TrinityCore/account-creator/pull/5 as required change for upcoming TC changes


Zeromq bitcoind subscriptions

PR for Listen to bitcoind with ZeroMQ #346.

@bodymindarts The way I am approaching it is that the wallet-clients are separate from the "loading of" or "total of" loaded wallets in the default (main) client. So, to use a wallet, you actually need a new wallet-client for this. Also the classes are done in a way that their methods don't overlap (at least for now).

@nicolasburtey @bodymindarts I think this is ready to get merged, at least from the perspective of testing. I am not sure where else changes need to be done for production compatibility (i.e. equivalent to the opening of the ports in docker-compose).

@bodymindarts bitcoindDefaultClient is now fully removed.


Create a Dataflow pipeline to resave EPP resources

This has two modes.
If isFast is false, then we will just load all EPP resources, project them to the current time, and save them.
If isFast is true, we will attempt to intelligently load and save only resources that we expect to have changes applied when we project them to the current time. This means resources with pending transfers that have expired, domains with expired grace periods, and non-deleted domains that have expired (we expect that they autorenewed).

This change is

OK I think this should be good to go


Add DynReplaceSlice op; make Dimension support negatives

Adds a DynReplaceSlice op, suitable (among other things) for backprop of DynSlice (though I haven't implemented generate_adjoints yet because we have broader issues with dyn shapes in autodiff that haven't been tackled yet). Adds the op, type prop tests, DynElimination, and execution tests.
Another major change in this PR is that Dimension (and therefore PartialShape) has been changed to include negative values. This felt necessary in order to support the overlap of dynamicness with right-indexiness in infer_slice_shape, and I think it will come up elsewhere in the future.
Since validation logic generally will not have safeguards against negative dimensions in the shape, I've put a check in set_tensor_type to throw when dimensions are negative; indirectly, this will trigger if validate_and_infer_types tries to set a negative shape, which means any issues should be detected. 🤞

Adding Changes API because we have to remove the ptrdiff_t conversion from Dimension. I don't think this should affect anything outside of the ngraph repo itself, but can't say for sure.

Back to WIP because I just realized that cough a lot of the test logic was #if 0'd out.


Steiner minimum tree not found for the graph with fixed weight on edges.

Did:
I have written a JUnit test that shows the problem of finding Steiner minimum tree.
Please see the attached:
TestFixedTwoHeuristicsSteinerTree.zip
To run the test:

Unpack the zip file in the main project directory preserving the directory structure. ( there is only one JAVA file)
Download and include in the project path "junit-platform-console-standalone" Jar, for example from the Maven repository.
Run the JUnit test src/sl/TestFixedTwoHeuristicsSteinerTree.java

Alternatively, remove the "junit-platform-console-standalone" dependency from the src/sl/TestFixedTwoHeuristicsSteinerTree.java file (import static org.junit.jupiter.api.Assertions.assertTrue;) and assert and run the program in debug mode to see that it doesn't have the path specified in the results.
Happened:
Got missing paths resulting in the Steiner tree being not complete.
The preview of one of the missing paths:

Moreover, the algorithm also doesn't find the paths between other terminals (Steiner vertices).
Expected:
To find the Steiner minimum tree in the test so that the test would end successfully.

Please help me with this issue. When I've omitted the last two commits in the git tree:
d21dd1ec9 made Mathematica output from examples more robust against errors
fe44a2761d fixed embarrassing bug
then test ends with the error:
java.lang.UnsupportedOperationException: no more advancement is possible
I don't have deep enough knowledge about the algorithm itself, but something is wrong in the algorithm implementation or I am doing something wrong in the test. Please guide me or try to fix the problem. Any feedback will be appreciated.

Okay, I'll look into it when next I have time.

I got your test running and worked up some drawing logic to help me understand it, but I need to spend more time to find the problem.  Sorry, I'm quite busy for the next couple of days!

I got your test running and worked up some drawing logic to help me understand it, but I need to spend more time to find the problem. Sorry, I'm quite busy for the next couple of days!

Ok, good to know it's working and reproducible also on another machine. I'll wait. I really appreciate any help you can provide.

Okay, I spent some time looking at it and I now partly understand my own code again.  :)  I think that one problem that's arising here is that the tree-marking algorithm does not gracefully handle edge weights of zero.  Zero-weight edges were never needed in my own uses of this code, so I probably never even considered testing them.  I apologize for that!  It's not a very strange thing to expect to work correctly, and I would prefer that it did work correctly.
Are zero-weight edges essential in your project?  If not, the easiest and fastest solution may be for you to replace the zero weights with very small weights.  I seem to find that replacing the 0.0 weights in your test case with Float.MIN_NORMAL causes the test to pass.  (Float.MIN_VALUE does not work, evidently because it's TOO small.  Float.MIN_VALUE * 2 works, though.  But it's probably safer not to go that small.)  Can you make the test pass on your machine by doing that?  And if so, are you satisfied with this solution?
My preference would be for weights of zero to work correctly, but it's tricky to find an elegant way to make that happen.  I have an idea of how it could be done, so if you really do require weights of zero, then maybe I can make it work.  But it'd be easier not to!

Okay, I spent some time looking at it and I now partly understand my own code again. :) I think that one problem that's arising here is that the tree-marking algorithm does not gracefully handle edge weights of zero. Zero-weight edges were never needed in my own uses of this code, so I probably never even considered testing them. I apologize for that! It's not a very strange thing to expect to work correctly, and I would prefer that it did work correctly.
Are zero-weight edges essential in your project? If not, the easiest and fastest solution may be for you to replace the zero weights with very small weights. I seem to find that replacing the 0.0 weights in your test case with Float.MIN_NORMAL causes the test to pass. (Float.MIN_VALUE does not work, evidently because it's TOO small. Float.MIN_VALUE * 2 works, though. But it's probably safer not to go that small.) Can you make the test pass on your machine by doing that? And if so, are you satisfied with this solution?

Great you have found it! Yes, the test passes on my machine too after replacing zero with Float.MIN_NORMAL. And yes, I'm satisfied. I think it will work for me for now. I got areas (islands) with zero-weight edges that I need to connect together with Steiner minimum tree. But I think I could live with the small, non-zero weight for now. It will probably have a very limited impact on where to leave the island because there probably will still be some edges with higher weights included in paths between those islands.

My preference would be for weights of zero to work correctly, but it's tricky to find an elegant way to make that happen. I have an idea of how it could be done, so if you really do require weights of zero, then maybe I can make it work. But it'd be easier not to!
Ok, but it would be nice to have the limitation at least in the project documentation, and maybe see the solution in the long run. I'll report the issue in the future if I'll find some corner case where it won't work for me.

Thank you for your support!


2.22.0 - Auto-response engine rewritten and actually functional

This verstion of Fred comes with a near-complete rewrite of the Crashes cog, making it faster, more reliable, and more useful.
Key features:

now processes all files in a message instead of one

processes all files in a zip separately, running regex on all of them
fixes #111

now properly uses asynchronous jobs for much faster processing
adds the username of who triggered a crash, either as a footer text or as embed author

closes #106

reacts to messages with files it will process with :eyes:

closes #109
other features in that issue are solved by textual notifications instead of reactions


Tox configuration for python source code.

Created the tox configuration.

Ran make format to format the python code using the defaults.

Introduce mypy and pylint

we can figure out the rules for these but should try to keep these errors down and 10/10.

Your code has been rated at 6.37/10

Found 4 errors in 3 files (checked 6 source files)

Follow ups:

add support format and lint checks for the rust code.

Hey @Mikcl 👋
Thanks for the PR 😄
I have one question and one suggestion. What does tox do? I have heard about it a lot but am not sure what it really does?
Also, I don't want to add pylint and mypy this early in the project. As Starfyre is still in very early stage and these tools slow down velocity IMO.
In the future, I was hoping to use the pre-commit.ci(https://pre-commit.ci/) + ruff(https://github.com/charliermarsh/ruff).
But I would like to ship a few versions before I add mypy to the repo. You know that types IMO types are 🤮

What does tox do?

Essentially a convenient venv wrapper.
Its useful for configuring tools to run against your repo (linters, tests, etc), often which require specific environment (env-vars, flags, isolation)
Would highly recommend for portability of ci (same commands on laptop and ci),
article for more detail on problem space

Also, I don't want to add pylint and mypy

Fair, happy to not include.

and these tools slow down velocity

Somewhat disagree.
Would it be possible to comprimise on including ruff?
From first use it is very fast and useful ( the --fix helps keeps things standard and is on 0 errors with all rules enabled except for line-too-long).

In the future, I was hoping to use the pre-commit.ci

Sounds good. Would recommend the pre-commit hook to call make format then make lint to maximise ci-portability.

Somewhat disagree.

</3

Would it be possible to comprimise on including ruff?
From first use it is very fast and useful ( the --fix helps keeps things standard and is on 0 errors with all rules enabled except for line-too-long).

Yep, we can do that. 😄

Sounds good. Would recommend the pre-commit hook to call make format then make lint to maximise ci-portability.

Sounds good. I will make an issue of this.


helm upgrade --dry-run fails with the following error : Error: UPGRADE FAILED: grpc: received message larger than max (36218786 vs. 20971520)

I am upgrading my services using helm upgrade command and i observe the same behavior for the below commands :

helm upgrade --dry-run <service_name>  --set image.tag=xxx -f values.yaml --namespace  --tiller-namespace  --debug

helm upgrade  <service_name>  --set image.tag=xxx -f values.yaml --namespace  --tiller-namespace

Output : Error: UPGRADE FAILED: grpc: received message larger than max (36218786 vs. 20971520)
helm version :
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Could anyone let me know what i might be doing wrong?

This may be a possible duplicate of one of the other tickets in the queue with a similar error? https://github.com/helm/helm/search?q=received+message+larger+than+max&type=Issues

I'm going to close this ticket due to inactivity, but please re-open if this still needs to be addressed. Thanks!


Improved heuristic for BrownianInterval's dependency tree.

Fixes #36.
What was meant to be a small speedup ended up being a Russian roulette between "small speedup" and "huge slowdown".

Could you explain a bit more what's changed?
Also, this doesn't seem like a complete fix to me. It is still possible to get very small step sizes, and the issue will likely bug the updated BTree and BPath in the future.

Sure.
So BInterval relies on a dependency structure between queried intervals as you know. If that's the only structure that is imposed, then a problem arises in that the backward pass ends up taking O(n^2) work in the length n, because you have to recompute your way forwards from the start to get to the queried interval, then step back a bit and repeat the whole procedure. (The cacheing offsets this somewhat but doesn't change the asymptotics.)
The resolution to this is to prespecify a tree-like dependency structure. This increases the cost of the forward pass from O(n) to O(nlogn), but decreases the cost of the backward pass to the same.
The problem now is that we have to pick a resolution to create this dependency structure down to.
The optimal resolution is a function of the average step size in the solver, and the size of the cache.
The bit that's been changed is the heuristic for figuring out the average step size in the solver. Previously, it was very crude: if any given step was less than 0.1 the smallest step so far recorded, then a dependency tree was created down to that resolution.
But because the terminal step in the new solver could be arbitrarily small, then this final step would trigger such a (completely unnecessary) dependency tree creation.
The fix is to actually calculate the average interval length that it's been queried width, and only trigger a dependency tree creation is that gets small enough. Just one tiny step isn't enough to trigger it.
This isn't an issue that should affect BTree or BPath - it's just an undesired interaction between the updated solver and an overly naive heuristic in BInterval.

Ok, thanks for explaining the average step size computation part. LGTM.
I think at some point, I want to revisit the weird behavior that dt is very small at the end. This actually does affect the new BPath I wrote, since it currently relies on Cholesky, and it's proving to not be very numerically stable. Though, alternatively, I could also use the H generation formulae in James' thesis and get the same thing.


Formatting with

Hello!
I'm using CodeMirror in combination with TinyMCE for creating Email signatures. One of the things I use a lot is '<br/>'. I'd like to make it so, that whenever there's a linebreak like that, Codemirror puts it on a new line. So far, as soon as I close and open the sourcecode window of TinyMCE, it all puts it on 1 line. I've had a scan through the files, but I can't find a setting anywhere. Any help?
Thanks in advance.

CodeMirror edits plain text. It does not format it. If TinyMCE feeds it a single line, it'll display a single line.


[Proposal]Support for supabase raw queries

Not sure if this feature is supported, I looked into the source code But I couldn't find a way to execute raw queries something like
final response = await _supabase.query('select * from $table1').execute();

Basically, I wanted to use joins, ~But I couldn't find that either~,
I found a way to use joins but looks like we don't need to specify a columnName on which the join is happening
  final response = await _supabase
        .from('$table1')
        .select('*, $table2!inner(*)')
        // .eq('$table2.$innerJoinColumn', '$table1.$innerJoinColumn')
        .execute();

So I was hoping raw query would help me run any kind of SQL query.

I believe raw query is not supported on the client libraries to avoid SQL injection. I don't think the js client library supports it either

@maheshmnj
Supporting raw query introduces security problem, so most likely will never be supported.
Currently, you can perform joins on tables that are associated via foreign keys, and when you have multiple foreign key relationships between two tables, an error message with instructions on how you can disambiguate will be thrown!


Accessibility Audit - Carbon Website: Help - Contact us

This epic is tied to a larger "release" that is meant to track the progress of the Accessibility Audit for the Carbon Website. We will audit all of the pages of the carbon website based on AVT 1, AVT 2, & AVT3 - which can be found here.

AVT 1: will audit the site against the IBM Accessibility Checker - browser extension

AVT 2: will audit the site against accessible keyboard interactions

AVT 3: will audit the site against screen readers

Legend:

🌶 fully audited - on all three AVT levels

:one: 🔍 AVT 1 audited
:two: 🔍 AVT 2 audited
:three: 🔍 AVT 3 audited

:boom: issues and documentation - on all three AVT levels are complete

:one: 🚨 AVT 1 issues submitted
:two: 🚨 AVT 2 issues submitted
:three: 🚨 AVT 3 issues submitted

:sparkles: tickets are triaged

Current status of this page:

Help -  Contact us - 2 issues - no new issues found

1⃣ 🔍 AVT 1 audited & 🚨 AVT 1 issues submitted

Closing due to inactivity. Will reopen if/when ready to be worked on again.


UIKit-applied dimming bug fixed by duplicating tintColor value

Updated so ScrollingNavigationController now maintains its own copy of the UINavigationBar's tintColor property - thus avoiding situations where UIKit-applied dimming is accidentally made permanent through a combination of UIAlert + device rotation for example.
More context at #391

Thank you @tifroz for the contribution. I'll release a new version right away.


fix: do not quote the divider in highlights

[!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

#138  👈
#137
main

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

Join @MartinBernstorff and the rest of your teammates on  Graphite

Merge activity

Apr 9, 2:18 PM GMT+2: @MartinBernstorff merged this pull request with Graphite.


read only after imaging to new card (homeassistant)

I am missing something here, but is it expected to be read-only after shrinking and copying the image to a new SD card? Is there a way to still edit the files?
For reference, I am cloning Home Assistant after removing sensors and devices. Home Assistant seems to be buggy using the shrunk image. I would also like to be able to edit my files in Windows before reuploading them to a new Raspberry Pi 4.

It should not be read only no. Did you cleanly shutdown before taking the image? I can't say Ive ran into this issue before.


[Feature proposal] changing textSizes to fontSizes

Hi, I would like to propose a change to the config, the property textSizes would be better named fontSizes to match the underlying css property it represents, as it's still in beta breaking changes shouldn't be much of an issue.
Another suggestion would be to add em units to text by default, right now 2xl represents 1.5rem, I was thinking something like 2x for 2em or so, this helps when building relative sizing from one element to another.

Agreed. It reminds me that there are inconsistencies in singular/plural form in the config properties.
Some are plural:

colors
screens
fonts
textSizes
fontWeights
textColors
backgroundColors
borderWidths
borderColors
shadows

And some are singular:

leading
tracking
backgroundSize
borderRadius
width
height
minWidth
minHeight
maxWidth
maxHeight
padding
margin
negativeMargin

I feel like they should all be plural.

Planning to make all of this consistent in the near future with backwards compatibility until 1.0.
I personally think standardizing on singular makes most sense; plural felt wrong after we added the "modules" section to the config. "Background size module" sounds more right to me than "background sizes module".
The default font scale will remain in rem though; you are free to change it to em in your own config of course but using em means you don't actually have a fixed type scale anymore. It's really easy to end up with fonts of every size imaginable if you're not careful since em will always multiply the font size of the parent.

@adamwathan I think em has a better advantage over rem because of the relativity.
If we design the components based on relativity rather than sizes it will be easier from design spec and implementation to meet the requirements.
This would be really handy if we want to use the same design in devises like TVs and so on where the proportion is really big, just increase the font-size and everything is relative to it container so.
Now, issues related to messing up the sizes we could always reset the font-size to be based on the font size base.
For example (any other good name is welcome)
.reset-font {  font-size: 1rem; }

@adamwathan Do you plan to use .font- instead of .text for font size classes?

This has been renamed in 1.0 👍

Actually I'd prefer to have anything text or font related to have the same prefix (I prefer text-). Font-style and text-transform always trips me up.


Wrb

🤷🏼♂

🤷🏼♂

No description provided.

I'm glad you asked! Many people come to GitHub because they want to contribute to open source 📖 projects, or they're invited by teammates or classmates who use it for their projects. Why do people use GitHub for these projects?

pphub://user?login=


fix: [Search v2.3] - Default name is not displayed correctly for multiline system message thread.

Details

Fixed Issues
$ https://github.com/Expensify/App/issues/49330
PROPOSAL: https://github.com/Expensify/App/issues/49330#issuecomment-2355413921
Tests

Go to DM.
Submit an expense with a multiline description.
Go to transaction thread.
Click Description.
Edit the description while maintaining the multiline format and save it.
Right click on the system message > Reply in thread.
Send a reply in thread.
Go to Search > Chats.
Click Filters > Select "In".
Select the thread in Step 8 > Save.
Click Save search.
Verify the title of the saved search is only shown in one line.

[x] Verify that no errors appear in the JS console

Offline tests

Go to DM.
Submit an expense with a multiline description.
Go to transaction thread.
Click Description.
Edit the description while maintaining the multiline format and save it.
Right click on the system message > Reply in thread.
Send a reply in thread.
Go to Search > Chats.
Click Filters > Select "In".
Select the thread in Step 8 > Save.
Click Save search.
Verify the title of the saved search is only shown in one line.

QA Steps

Go to DM.
Submit an expense with a multiline description.
Go to transaction thread.
Click Description.
Edit the description while maintaining the multiline format and save it.
Right click on the system message > Reply in thread.
Send a reply in thread.
Go to Search > Chats.
Click Filters > Select "In".
Select the thread in Step 8 > Save.
Click Save search.
Verify the title of the saved search is only shown in one line.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/a90ff933-4bd0-48c5-a81a-674b6b405ef4

Android: mWeb Chrome
https://github.com/user-attachments/assets/3077f38e-83a8-48d5-87d7-fbd201523149

iOS: Native
https://github.com/user-attachments/assets/091778e4-e138-400f-a73a-95859f94bb66

iOS: mWeb Safari
https://github.com/user-attachments/assets/e048dd33-8100-4c93-9730-0fa5e2549ca4

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/5ad2e2ba-a085-44e8-9b52-dc6cf939e8db

MacOS: Desktop
https://github.com/user-attachments/assets/5ee2d9cf-a646-4abb-a363-c93ba3784674

The iOS version is correct - this should only be 1 line.

@shawnborton is ooo, so I'm tagging @Expensify/design for another look. FWIW we're about to merge this PR that replaces the custom query header, so I wouldn't spend too much time fixing edge cases for it.

The search header should still be only 1 line or two as it's in prod?

I kinda think it should just be one—two lines isn't the worst thing in the universe, but one line just looks better and is much less distracting.
Otherwise I feel like this is looking pretty good.


Generated thumbnails are missing code text

Documentation URL
https://biomejs.dev/linter/rules/use-flat-map/
Description
The text in these quotes is missing on thumbnails:

Expectations
Text to appear on thumbnails.
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

The OG image generated does not have an issue rendering the text and matches what's inside the file. However, the text inside the file is already incorrect. It looks like the generation step fails to include the quoted text.


Awkward mappend strictness

Hrm.... mappend actually doesn't need to be (inherently) strict in either argument. The (b ~ (), c ~ ()) instance constraint gives us the type information we need. So we could just write
  mappend ulx uly = UL (mappend (getUL ulx) (getUL uly))

The trouble is that would be lazier than (<>), which is no good when they're expected to be utterly identical. So I guess we really have three decent options to consider:

Impose a (b ~ (), c ~ ()) constraint on the Semigroup instance, and make both (<>) and mappend exactly as lazy as for the underlying Semigroup/Monoid.
Leave things as they are right now.
Remove both instances and wait to see if there's a compelling need for them to be one way or the other.

The instances have been removed for now.


How to parse boolean switches

I would like to run a command that works like this:
command --foo true --bar true
but look like this:
command --foo --bar
Is this possible?

Can this be documented in the README somewhere?

If you'd like to take a stab at a pull request to add it to the readme that'd be great!


Show Release Notes in a notebook

In the Start Page link for the release notes. Show them on a notebook instead of opening a link.

WE will likely revisit the start page multiple times over the next few months.


 This may be related or a separate issue.

@enderland do you recall if that happened for Cyborg-Chronicles or Mythos mods, or both?

Will try to reproduce this in new Vue.js client, both AI Loser and AI Idiot, and both mods. @Zomis is this by design? Seems based on the server messages I see in the browser console that the server is doing this to the players.

Whoops, how has this been left untouched for two years? I know exactly why this happens, it's a bug in the server.


Guacamole instances randomly freezing

🐛 Bug Report
Guacamole instances running recently-built AMIs randomly freeze.  When this happens

All ssh sessions freeze
New ssh sessions cannot be established
Guacamole sessions freeze

To Reproduce
Steps to reproduce the behavior:

Instantiate an instance from a recently-built AMI generated from this repository
Wait long enough, and it will freeze

Expected behavior
Such instances should not freeze.

I tried tailing logs and looking at dmesg output while waiting for such an instance to freeze, but time and time again I saw nothing of interest.  Clearly the freeze was taking place before the logs could output anything.  Therefore the issue looks very much like a kernel panic.

Hoping that this issue was indeed caused by a kernel panic, I manually enabled kernel crash dumps in running Guacamole instances.  I basically used these instructions, although I found some of the steps listed there to be superfluous.  What is actually required is:

Modify the Guacamole server's security group and network ACLs to allow port 80 outbound.
sudo apt-get install kdump-tools $(uname -r)-dbg
Append nmi_watchdog=1 to the kernel command line in /etc/default/grub
sudo update-grub
Reboot the instance

There are some reports online of kernel panics appearing.  See, for instance, these links:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966846
https://forum.proxmox.com/threads/kernel-5-4-44-causes-system-freeze-on-hp-microserver-gen8.72050/page-2
https://lkml.org/lkml/2020/7/20/883

We caught a kernel panic on env0 in our staging environment.  I added the information to the original Debian bug report, since it looks like our problem is indeed a result of the recent kernel changes.
Links for investigating kernel crash dumps using crash:

https://www.linuxjournal.com/content/oops-debugging-kernel-panics-0
https://www.thegeekstuff.com/2014/05/kdump/

It took several failed attempts (partly because doing kernel foo in Docker is not a great way to test), but I modified the Guacamole AMI to boot into an older kernel that we used before and know to be good.  See these PRs:

cisagov/ansible-role-upgrade#11
cisagov/ansible-role-upgrade#12
cisagov/ansible-role-upgrade#13
cisagov/ansible-role-upgrade#14

Once the kernel bug has been resolved and is available in Debian, we can undo these changes.

It is worth noting that this issue is probably appearing in the Guacamole instance because we are running Docker there and the kernel bug involves cgroups.

Resolved in the pRs listed above, as well as #24.


Add failsafes in case Octokit api fails. Statically-stored most information in .json files. Change revalidation period for projects page. One issue with importing several variables and functions, where I had to manually import each from their respective file, instead of importing all from '../util'.

Add failsafes in case Octokit api fails. Statically-stored most information in .json files. Change revalidation period for projects page. One issue with importing several variables and functions, where I had to manually import each from their respective file, instead of importing all from '../util'.
Fixes uclaacm/opensource#114

More of a note for reproducibility: could we document how the fixtures were generated somewhere? I imagine when the APIs get updated, etc. we'll need to regenerate them, and that would be done by people who probably didn't work on this initial PR.

More of a note for reproducibility: could we document how the fixtures were generated somewhere? I imagine when the APIs get updated, etc. we'll need to regenerate them, and that would be done by people who probably didn't work on this initial PR.

Sure, this can definitely be done by adding it into a README as well as into our design doc for this project! Can you add that in as well to the README @JCamyre ?

Closed as with updates to Next.js 12, revalidation should work properly


Update

Upstreaming changes from the u-DALES project. This adds the ability for applications to handle their own halo allocations, rather than 2decomp creating halo arrays for them.


NFT Exchange: Mainnet Auction House

This update changes the ids and accounts from our devnet auction house contract to our mainnet auction house contract deployment. This contract shares the contract interface of commit of the metaplex repo: a93babf9079e14fcc2a2489a97616b1c6c0ff62c.

Task linked: CU-23n2gxc UI: Update Accounts and IDs with Mainnet Values

Task linked: CU-23ffnze Make NFT the default page

Task linked: CU-23ffnkk Reorder Navigation Tabs


New script $ZSH/tools/require_tool.sh to ensure version of tool

While writing the (future) emacs plugin, I had to ensure version of emacs installed was greater than 23. I remembered this script I had worked with during my studies. I have repacked and it here it is: require_tool.sh

$ ./require_tool.sh emacs 23 ; echo $?
0
$ ./require_tool.sh emacs 50 >/dev/null ; echo $?
emacs 50 or better is required: this is emacs 23.1.1
1

As this might be very helpful to other plugins, I believe `$ZSH/tools' directory is appropriate.
WDYT?
By the way, this zsh repo if a very very good idea. Thank you all!
Cheers
Tristan

Thanks for this!


Remove context div

When a scene creates a context, it creates an unnecessary div nested under the selector element.  By processing the size before setting the display to none, this div is not required.
This also addresses #361

I am worried that this change may cause unexpected results.
Because the DOMRenderer is now using the rootElement as its source in this change, it now contains the Canvas element for the WebGL context.  The DOMRenderer now has a child that has not been added by Famo.us and is not being tracked in the child array.

@redwoodfavorite In order to maintain true abstraction shouldn't the DOMRenderer only teach/tell the DOM?  What does the DOMRenderer learn from the DOM?
Even if the nested div is maintained, it would still be possible to add other DOM elements under the selector from outside the application.
I think your concerns are absolutely valid, but they should be addressed immediately because whether or not the nesting is removed, it could still become a problem.

I disagree with this change.  IMO we should be isolating ourselves from the containing div.

Also, this would force us to affect styling on the container to get our compositing results.

Closing.


Access Instance API values from mocha with enzyme?

I'd like to sanity check all the Field parser & normalizer functions working in a form.
I thought I might be able to use the Instance API via refs - but I can't seem to find my ref on wrapper.instance()
I was thinking of just creating a selector, and rendering the Form Instance API values to a div just for testing.
This is my progress so far:
  import { FormUnconnected } from 'form';

  it(`renders without invalidation errors`, () => {
    const Comp = reduxForm({
      form: FORM_NAME
    })(FormUnconnected);
    wrapper = mount(
      <Comp/>,
      options
    );
    const store = wrapper.instance().refs.wrapped.store;
    const registeredFields = wrapper.instance().refs.wrapped.store.getState().form[FORM_NAME].registeredFields
  });

Is there a proper way to do this?

I tried the following, and it just works™
const form = mount( <Form initialValues={{foo:"bar"}} />, this.wrapperOptions );
console.log( form.instance().values );

Can you create an example that reproduces your issue, please?

Closing due to inactivity.


Disable kotlin_experimental_app

kotlin_experimental_app seems broken
#26470
Risk Level: Low
Testing: N/A
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: N/A

/assign @snowp

I know what the root cause is. Will follow up shortly.

Experimental app should be fixed in https://github.com/envoyproxy/envoy/pull/26482

Closing as the root cause has been addressed in https://github.com/envoyproxy/envoy/pull/26482/files


feat: Filtering by status at Backoffice

Adding possibility to filter Projects, PDs and Investors by Status. I have again taken huge inspiration from Tota project ;) and moved full_text filter inside search_form_for formular so searching and filters are part of same form.
Styles are really simplified, for example for dropdown, I have used simple selectbox which should be fine from tech point of view and can be replaced later on by something more fancy...

Edit: Added also Category and Priority Landscape filters to Project page. ;)
Testing instructions
Open Backoffice and try to filter by Status Projects, PDs and Investors one by one.
Tracking
https://vizzuality.atlassian.net/browse/LET-505
https://vizzuality.atlassian.net/browse/LET-531
https://vizzuality.atlassian.net/browse/LET-532
https://vizzuality.atlassian.net/browse/LET-564
https://vizzuality.atlassian.net/browse/LET-534
https://vizzuality.atlassian.net/browse/LET-533

I see you added more filters @martintomas. Can you also add reset filter button? Just a link to entity index page, if any filter is applied.

Sure, I don't think it is at design, but don't see problem with adding it ;)

I have trouble with testing filtering by mosaic, because I messed up my db and need to reimport the locations table, I'll try to figure that out. In the meantime:

I found that filtering projects by status doesn't work for me, because the columns a text one in my db rather than int and  I'm not sure if this is sth I messed up locally (I do that a lot sadly) or there's a migration missing to convert it?
It appears to me as an inconsistency with the status filters that while on projects you have the ability to select a status, apply and then deselect it by choosing "Status", the same does not happen for project developers / investors (include_blank missing - you can ofc reset all filters).
Also not sure about the "Unverified" status in the projects status dropdown, shouldn't it read "Draft"? so that we don't confuse this status with the trusted / verified flag
I added a small suggestion regarding using subquery instead of pluck, unimportant if it creates additional problems

I have tried to address all your issues @agnessa

I have trouble with testing filtering by mosaic, because I messed up my db and need to reimport the locations table, I'll try to figure that out. In the meantime:

It is integer at my db, so I guess problem is with your database.

I found that filtering projects by status doesn't work for me, because the columns a text one in my db rather than int and  I'm not sure if this is sth I messed up locally (I do that a lot sadly) or there's a migration missing to convert it?

Status filter now uses trusted column for filtering and hopefully should work for you now.

It appears to me as an inconsistency with the status filters that while on projects you have the ability to select a status, apply and then deselect it by choosing "Status", the same does not happen for project developers / investors (include_blank missing - you can ofc reset all filters).

Added missing include_blank params so it should be consistent now.

Also not sure about the "Unverified" status in the projects status dropdown, shouldn't it read "Draft"? so that we don't confuse this status with the trusted / verified flag

Yup, switched to trusted column, text is now verified/unverified.

I added a small suggestion regarding using subquery instead of pluck, unimportant if it creates additional problems

Good point, I am using select and subquery now.


[Bug]: Getting NPE when accessing a field with a default value which is generated from rest binding with the optional field

Description
I am creating a record A using a rest binding with another record B. The record B and record A has the same record typed field, but in record B the field is optional and in record A that field has a default value. When accessing a member of this fiedl from record A, I am getting a NPE. But this works in in Ballerina SwanLake Update 8(2201.8.x).
Steps to Reproduce
Use the following code to reproduce the issue:
import ballerina/http;
import ballerina/io;

public type ConnectionConfig record {|
    http:BearerTokenConfig|http:OAuth2RefreshTokenGrantConfig auth;
    http:HttpVersion httpVersion = http:HTTP_2_0;
    http:ClientHttp1Settings http1Settings?;
    http:ClientHttp2Settings http2Settings?;
    decimal timeout = 60;
    string forwarded = "disable";
    http:PoolConfiguration poolConfig?;
    http:CacheConfig cache?;
    http:Compression compression = http:COMPRESSION_AUTO;
    http:CircuitBreakerConfig circuitBreaker?;
    http:RetryConfig retryConfig?;
    http:ResponseLimitConfigs responseLimits?;
    http:ClientSecureSocket secureSocket?;
    http:ProxyConfig proxy?;
    boolean validation = true;
|};

public function main() {
    ConnectionConfig connectionConfig = {
        auth: {
            refreshToken: "mockRefreshToken",
            clientId: "mockClientId",
            clientSecret: "mockClientSecret",
            refreshUrl: "mockRefreshUrl"
        }
    };
    http:ClientConfiguration config = {...connectionConfig};
    io:println(config.cache.enabled);
}

Run the file:
$ bal run test.bal

Compiling source
        test.bal

Running executable

[2024-09-04 12:38:39,740] SEVERE {b7a.log.crash} - Cannot invoke "io.ballerina.runtime.internal.values.MapValueImpl.getUnboxedBooleanValue(io.ballerina.runtime.api.values.BString)" because "<local37>" is null
java.lang.NullPointerException: Cannot invoke "io.ballerina.runtime.internal.values.MapValueImpl.getUnboxedBooleanValue(io.ballerina.runtime.api.values.BString)" because "<local37>" is null
        at test_service.main(test.bal:32)
        at $_init.$moduleExecute(.)
        at $_init.$lambda$$moduleExecute$(.)
        at io.ballerina.runtime.internal.scheduling.SchedulerItem.execute(SchedulerItem.java:54)
        at io.ballerina.runtime.internal.scheduling.Scheduler.run(Scheduler.java:320)
        at io.ballerina.runtime.internal.scheduling.Scheduler.runSafely(Scheduler.java:287)
        at java.base/java.lang.Thread.run(Thread.java:833)

Affected Version(s)
Ballerina SwanLake Update 9(2201.9.x) and Update 10(2201.10.x)
OS, DB, other environment details and versions
No response
Related area
-> Runtime
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

Simplified example
iimport ballerina/io;

type Inner record {|
    int foo;
|};

type Outer record {|
    Inner inner?;
|};

type OuterXBase record {
    Inner inner = {foo: 10};
};

type OuterX record {|
    *OuterXBase; // <- default value must come from the inclusion
|};

public function main() {
    Outer o = {};
    OuterX ox = {...o}; // <- without spread this works
    io:println(ox.inner.foo);
}

The fix will be released with the 10.1 patch versions as well.
https://github.com/ballerina-platform/ballerina-release/issues/2751

https://github.com/ballerina-platform/ballerina-release/issues/2750


are these private or public proxy links

title
private proxies are ones you can only get with the dispensers
public ones are in the discord channels every one can see

I’m very sure that most of them are public, I got the links from public sources, but I cannot guarantee that every single link is public (some private links may have been leaked or smth), and I never been banned from discord servers recently


fix: skip comment in field line when reserve comments

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


CLOUD-58088 add etl-edw default bp

@biharitomi @doktoric nearly final etl-edw bp

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/cloudbreak-pull-request/2699/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/mock-integration-test/190/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/cloudbreak-pull-request/2701/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/mock-integration-test/192/


Add Language server to https://github.com/Microsoft/language-server-protocol/wiki/Protocol-Implementations

Please send a PR to https://langserver.org/ as well.

PR added to langserver.org (https://github.com/langserver/langserver.github.io/pull/63), hence closing


the window has crashed (reason: 'crashed', code: '132')

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: June 2021 (version 1.58)
OS Version: Ubuntu16.04

Steps to Reproduce:

when use code to open the gui, it will display

Can you update to latest stable 1.62 and check if the crash happens ?

the problem has solved，it ’s due to two memory is not compatibility发自我的华为手机-------- 原始邮件 --------发件人： Robo @.>日期： 2021年11月5日周五 晚上7:28收件人： microsoft/vscode @.>抄送： cangfeng110 @.>, Author @.>主    题： Re: [microsoft/vscode] the window has crashed (reason: 'crashed', code: '132') (Issue #136479)
Can you update to latest stable 1.62 and check if the crash happens ?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.


Globed 1.2.3 crashes by trying to open 'My Lists' and 'Favorite Lists' on Proton 8.0 & 9.0 beta

I'm open to provide any additional details if required. Also, I was able to reproduce it multiple times and the logs look like they point to be always for the same reason. I don't know if it affects Windows.
Here is a few of the geode crashlogs:
2024-02-27_11-31-54.log
2024-02-27_11-23-47.log
2024-02-27_11-18-28.log

known, should be fixed now. try with v1.2.5

I confirm that 1.2.5 solves the problem. Closing the issue


punctuation_chars.h compilation errors on Windows (MSVC) + Clang

Hello,
I am setting up tree-sitter on a fresh installation today, and experiencing the following errors:
nvim-treesitter[rst]: Error during compilation
In file included from src/scanner.c:3:^M
In file included from src/tree_sitter_rst/scanner.c:6:^M
In file included from src/tree_sitter_rst/chars.c:2:^M
src/tree_sitter_rst/punctuation_chars.h:246:3: error: character too large for enclosing character literal type^M
  246 |   L'\U00010100',^M
      |   ^^M
... snip ...
src/tree_sitter_rst/punctuation_chars.h:308:5: error: character too large for enclosing character literal type^M
  308 |   { L'\U000110be', L'\U000110c1' },^M
      |     ^^M
fatal error: too many errors emitted, stopping now [-ferror-limit=]^M
20 errors generated.^M

I'm not too familiar with tree-sitter internals or C, but from some googling I think this L'\U00010100' is somehow not correct? Possibly this is related to the fix for #53.
Sorry I can't be of more help in diagnosing this - I'm happy to run any tests you might suggest.
I will try and see if the problem is reproducible on Linux + Clang.

Update: everything works fine on Linux + Clang

OK, after some digging I have found the following:

The L'...' syntax in C is a way of writing values of type wchar_t.
On Linux, sizeof(wchar_t) == 4, i.e. 32 bits, so literals greater than \U0000FFFF work fine.
On Windows, sizeof(wchar_t) == 2, i.e. 16 bits, so literals greater than \U0000FFFF cause compile errors.
In punctuation_chars.h, these character literals are assigned to int32_t, which ought to be big enough to hold the high-valued characters, but since they are written using the L'...' syntax, they must first go through wchar_t.

It seems to me that the best solution would be to write these characters as integer literals instead of wchar_t literals, if that makes sense?

Hi @jmacmahon thanks for debugging the problem!

It seems to me that the best solution would be to write these characters as integer literals instead of wchar_t literals, if that makes sense?

That makes sense, feel free to send a PR if you want!
/cc @SilverRainZ in case you have some opinions about this.

Hi,
I was working on a PR but got sidetracked trying to work out why the tests still passed on Windows despite the error - I assumed that there was no CI for Windows hence the error not being caught, but I see that in fact there is CI for Windows, but the tests nevertheless passed.
I was able to reproduce the unexpectedly-passing tests on my local Windows machine, but I couldn't work out why they were passing. In fact, I was able to completely delete the punctuation_chars.h file from my repo and run npm run test and have all the tests still pass.
So, I can do a PR with my suggested change, but actually I have no way of knowing if it would fix the problem since I can't get the tests to work right.

@jmacmahon you may be missing running npm run build before running the tests.

Unfortunately the tests still unexpectedly pass even if I do npm run build before npm run test.
(As an aside, I found that npm run build modified src/parser.c file with some number differences, but I think this is unrelated?)

Well, why the tests unexpectedly passed on Windows is beyond me, but I have submitted a PR anyway to fix the original problem.


Test PR

Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[ ] Ensure all commits include DCO sign-off.
[ ] Ensure that your contributions pass unit testing.
[ ] Ensure that your contributions contain documentation if applicable.

Description
Please describe your pull request.

Closing PR


Add logout support for OIDC in authn delegation

After a delegated authentication at an OIDC provider, if this OIDC provider sends a logout request to the CAS server, the CAS server does not perform a CAS logout. It works for SAML though.
This PR fixes the problem and adds a test to confirm the behavior.

I will investigate on failing tests.

I think the Publish documentation issue is not related to my change.

The delegation issue:
Execution failed for task ':support:cas-server-support-pac4j-webflow:testDelegation'.
> Failure closing session
  Standard error from JVM:
      OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended

does not seem to be related to my change either.

Re-running failing tests to confirm the outcome...

After re-running the failing tests, the SAML2 tests pass while the delegation tests still don't but I see the same issue on the master. Thus, I consider that this PR is not the culprit. Keep me posted if you need me to fix something in any case...

Thank you, sure. I'll take a look shortly.

This generally looks OK, thank you. I am in the process of moving OIDC/SAML2 functionality out of the main module for delegated authn, and when done, I'll also merge and include this changeset there in the final result. I am hoping to do this before the weekend.

Good! Thanks

This is merged into the master branch


Add changelog file to keep track of unreleased changes

Based on "Keep a CHANGELOG", this file should help us keep track of
what'll be in a new release, and also will make it easier to publish
release notes for new releases.

I wonder if we should start to pay more attention to our git history by squashing related commits in Pull Requests and making sure commit messages are descriptive. I collaborated to projects with strict rules about commit messages and merge policy and it makes much easier to know what changed, to generate changelog entries and to run git bisect when there's a regression.
Thoughts?

Looks good. I was fiddling the 0.9 tag so that this page lists the high-level things in that release: https://github.com/iovisor/bpftrace/milestone/1
I can squash more.
Also, I hope that 0.9 and 1.0 are the last "big" releases with a lot in the changelog. People may want to add niche stuff as they encounter it, but I hope we can defer as much of that to bcc as possible, leaving bpftrace simple and uncluttered.


"keep-alive" and "router-view" don't work properly when max="1"

Version
2.6.10
Reproduction link
https://codesandbox.io/s/vue-template-g669u
Steps to reproduce
<keep-alive max="1">
  <router-view v-if="$route.meta.largeCache"></router-view>
</keep-alive>
<keep-alive>
  <router-view v-if="!$route.meta.largeCache"></router-view>
</keep-alive>

Assuming we have some pages that require much memory and some pages that require only a little memory.
Let's say:
Home, PricyA, PricyB are memory intensive pages, while CheapA and CheapB are not.
The use case is to keep all cheap pages in the cache while only keep one pricy one.
However, for "keep-alive" tag, when the prop "max" is set to 1, the "beforedestroy" hook doesn't work, and therefore I cannot properly do a garbage collection.
What is expected?
beforedestroy called
What is actually happening?
beforedestroy is only called when max >=2

See https://github.com/vuejs/vue/issues/9972 regarding using max at 1. Also please, check keep-alive props documentation to control how to keep specific component alive but not others


Cannot get hot instance by hotRegisterer

Description
The handsontabl cannot show.  In the console, there are two errors.

ERROR TypeError: Cannot read property 'nativeElement' of undefined,  at handsontable-angular.js:148
This error occured when loading the  tag. As it happend after excuting ngOnInit() , but before ngAfterViewInit();
ERROR TypeError: Cannot read property 'updateSettings' of undefined
This error is due to get hot instance failed by hotRegisterer when executing

     getHotInstance(instance: string): Handsontable {
        return this.hotRegisterer.getInstance(instance);
     };

Detail please see demo. Thanks
Demo

https://stackblitz.com/edit/angular-handsontable-testing
Your environment

Angular version:  9.1.9
"@handsontable/angular": "^3.0.0",
"handsontable": "^6.2.2",
Wrapper version:
Browser Name and version: Chrome@81
Operating System: Windows10

Hi @lhf552004
First of all, you can use Angular 9 only with @handsontable/angular 5.1.1.
Nevertheless, even with the updated angular wrapper we still have some issue. You declare hot: Handsontable; but then you use hot as a string - this.getHotInstance('hot');. Besides this declaration isn't an instance declaration.
Here is a link to our docs about how to reference the Handsontable instance from the wrapper component - https://handsontable.com/docs/7.4.2/frameworks-wrapper-for-angular-hot-reference.html
As you can see, in .hml we set id - [hotId]="id", and next reference to it by id = 'hotInstance';. Then we use it this.hotRegisterer.getInstance(this.id) to get the instance of Handsontable.
Unfortunately, after these fixes we still have an error - Cannot read property 'nativeElement' of undefined. I think that you have to build hot-table first and only then reference to its. So AfterViewInit is too early to this type of operations.

OK @pnowak , thanks.


Copy & Paste between Projects

Problem
Copying and Pasting Elements or Pages from one Alva file or another does not have any effect.
Solution
Alva should allow you copy and paste between multiple windows.
Context
Depends on #642

Fixed with #657


fix: make it possible to use general stats

Till now it wasnt possible to get the general stats of the memcached server. If you try to call the method 'getStats()' or 'getExtendedStats()' without a special $type you will get this warning:

Warning: MemcachePool::getextendedstats(): Invalid stats type

Thank you very much. It seems like a valuable addition.


Fix the implementation of OnlyLiteralZero

This patch changes the implementation of OnlyLiteralZero to only fail if the second overload is chosen, instead of failing during overload resolution.
This patch cherry-picks 2de126cc5826a8d464270ead65a7a9a7b012b741.
Fixes #1419

Thank you❤🙏

❤🙏


How to set meeting_views_options

How to set meeting_views_options
like
opts.meeting_views_options = MeetingViewsOptions.NO_TEXT_PASSWORD+MeetingViewsOptions.NO_TEXT_MEETING_ID + MeetingViewsOptions.NO_BUTTON_PARTICIPANTS
Originally posted by @mirkarpude in https://github.com/driftboat/flutter_zoom/issues/9#issuecomment-922231550

@driftboat can you do enhance to include view options?

I have created a new branch "view_options" to implement this feature, It neet to  implement a Custom Meeting UI for this feature on iOS...

1.0.3+4(add meetingViewOptions to ZoomMeetingOptions(Android Only)) has been published.

1.0.3+5(add meetingViewOptions to ZoomMeetingOptions(Android&iOS)) has been published.


run all branches on travis

Changes Unknown when pulling ed9615a204098b4269dde9bd883cbb59c68f5c2a on all_branches into ** on master**.

Changes Unknown when pulling ed9615a204098b4269dde9bd883cbb59c68f5c2a on all_branches into ** on master**.

Changes Unknown when pulling ed9615a204098b4269dde9bd883cbb59c68f5c2a on all_branches into ** on master**.

Changes Unknown when pulling eebc8d650d6172f045e1497a8bed3e1da8865a9c on all_branches into ** on master**.

Changes Unknown when pulling bfff02ecc6374291da7c20270eb0608de05566fb on all_branches into ** on master**.

Changes Unknown when pulling fa7dec98f1018f10d72201ebb027b41265c69a6f on all_branches into ** on master**.

Changes Unknown when pulling e0776bbe9772e974994ecaecd1cefde15bccb861 on all_branches into ** on master**.

Changes Unknown when pulling 227819f0bf6ec629e89e5ef1011adb181c6ff9ed on all_branches into ** on master**.