Types of build model elements contributed by init scripts conflict with types from project build scripts

Applying a plugin A both from an init script and from a project build script can cause class cast exceptions when the build logic loaded in the project script classloader tries to reference any object created by plugin A in a statically typed manner using a type defined by plugin A or one of its dependencies.
For example, applying the build scan plugin in both init.d and Kotlin build script fails with the following unhelpful error message:

com.gradle.scan.plugin.internal.api.f_Decorated cannot be cast to com.gradle.scan.plugin.internal.api.f

This happens because when applying the build scan plugin in an init script, the registered buildScan extension is defined in the init scripts classloader scope. Then, when configuring the buildScan extension in a project script, the type of the extension comes from another classloader, hence the ClassCastException.
The same scenario works in Groovy scripts as long as the offending types are not referenced, that is relying on dynamic dispatch. It would however fail with a @CompileStatic Groovy or Java binary plugin.
Expected Behavior
One can interact with objects created by plugins applied in init scripts from project build scripts.
A warning or a reasonable error message might be enough.
Context
See https://github.com/gradle/kotlin-dsl/issues/489
Workarounds
Either:

use groovy scripts/plugins
use kotlin scripts and withGroovyBuilder {}
use plugins written in kotlin or any statically compiled language and reflection :(

I had the same issue.
Scan applied on the ~/.gradle/init.d/init.gradle, I haven't had any issue while my projects had the root build.gradle in groovy, but when I added the scan to a project with a root build.gradle.kts I had to remove my init.gradle file to make it work.

I ran into this same issue when trying to apply a plugin to my root project from an init script. My plugin consumes an extension that's added by a plugin applied in to root build file. I understand the theory about each script having its own individual class loader, but I'm unclear about the rules for how class loaders and selected, and how to contribute to their classpaths.
For example, this hack in my init script allows me to apply load the plugin in the right class loader:
rootProject {
    afterEvaluate {
        extensions.findByName("errorReporter")?.javaClass?.classLoader?.withGroovyBuilder {
            val clazz = TwitterErrorReporterPlugin::class.java
            val pathToClass = clazz.name.replace('.', '/') + ".class"
            val resource = URL(clazz.classLoader.getResource(pathToClass)!!.file.replace("(?<=\\.jar)!.*".toRegex(), ""))
            "addURL"(resource)
            apply(plugin = "com.twitter.twitter-error-reporter")
        }
    }
}

What's interesting here is that apply(plugin = "com.twitter.twitter-error-reporter") looks up the plugin in the right class loader (that of the root build file, where the errorReporter extension is registered), even if it runs in the context of the init script. I expected a buildscript block within rootProject to allow me to contribute to that classpath, but it seems to be ignored entirely – is that a bug?
Contributing the plugin jar file directly to the classloader using the hack in the example above does the trick but, of course, that's less than ideal :)

That's a tricky hack :)

What's interesting here is that apply(plugin = "com.twitter.twitter-error-reporter") looks up the plugin in the right class loader (that of the root build file, where the errorReporter extension is registered), even if it runs in the context of the init script.

That's the way plugin application works. Look up happens from the plugin target context into which your hack injects the classpath of your plugin.

I expected a buildscript block within rootProject to allow me to contribute to that classpath, but it seems to be ignored entirely – is that a bug?

rootProject { buildscript {} } in an init script does contribute to the root project script classpath. You can then access types from the root project script. But it doesn't contribute to the init script classpath and the rootProject {}  callback is invoked in the context of the init script otherwise there would be more surprising behaviour like types available in the init script but unavailable in that block. Moreover, the classpath contributed by the rootProject { buildscript {} } block isn't immediately available to the code following in rootProject {}. That's because the callback is directly evaluated and not parsed in two stages as build scripts are. This is a discrepancy that could be seen as a bug yes.
With that in mind here's an attempt to achieve the same without reflection:
rootProject {
    buildscript {
        repositories {
            maven(url = "https://example.org/repo") // made up repo url
        }
        dependencies {
            classpath("com.twitter:twitter-error-reporter:x.y.z") // made up coordinates
        }
    }
    // defer in order for plugin lookup to see the contributed classpath
    afterEvaluate {
        apply(plugin = "com.twitter.twitter-error-reporter")
    }
}

Ahhh that works like a charm, thank you so much! I wasn't aware that buildscript blocks would evaluate synchronously at all. That's certainly a more sensible way to achieve the same thing :). The Groovy builder is still needed in the context, but I understand now how all the pieces fit together. Thanks for the explanation!


moved how to write an itwin connecter documentation from sample to imodeljs docs

 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.

restarted from a clean branch


Mixing multiple classes with nested selectors can lead to undesired output

Mixing multiple classes in an element with the cx function oftentimes seems to lead to classes being merged into one big class with all the styled mixed together.
An example can be seen in the screenshot below where the top element had two classes applied to it, title and bigTitle, now merged together into a single class. The bottom element had only the title class applied to it.

This behaviour can ruin the expected output when, for instance, nested & selectors are applied, such as
&+& {
  color: red
}

In this scenario, & is expected to be title and it is expected to be applied to the bottom element. Given the above mentioned behaviour, it won't work because there are no longer 2 contiguous elements with class title.
I've cooked a simple reproduction example here: https://codesandbox.io/s/suspicious-sara-ou8303?file=/src/App.js
Thank you so much for you work, I've been using this library a lot lately!

Hi @andrezzoid,
Thanks for reaching out and puting together a clear reproduction repo.
Best I can do from where I stand is offer you to use TSS's nested selector featur.
See it implemented on your sandbox: https://codesandbox.io/s/romantic-gates-l1jc89?file=/src/App.tsx
Beyond that, tss-react, and it's it's main seling point, is meerly a wrapper arout @emotion/react. If you want we can ping Adarist, see what's he's insignt on the issue if the nested selector approach dosen't work for you.
Best,


Improve text spelling/grammar/formatting

Various spelling/grammar/formatting improvements.
This PR consolidates https://github.com/iterative/cml.dev/pull/289 https://github.com/iterative/cml.dev/pull/290 https://github.com/iterative/cml.dev/pull/291 https://github.com/iterative/cml.dev/pull/292 https://github.com/iterative/cml.dev/pull/293 https://github.com/iterative/cml.dev/pull/294 https://github.com/iterative/cml.dev/pull/295 https://github.com/iterative/cml.dev/pull/296 as requested in https://github.com/iterative/cml.dev/pull/289#issuecomment-1206529160, plus one more spelling fix (BitBucket -> Bitbucket).

closes #289, closes #290, closes #291, closes #292, closes #293, closes #294, closes #295, closes #296


Add links to Contributor Guidelines

Follow up to https://github.com/kubernetes-sigs/network-policy-api/pull/47#pullrequestreview-1165322550
We should update our README to have pointers back to the K8s contributor guidelines and maybe even add our own?

/good-first-issue

/assign

/kind documentation

Done with #53 Thanks @cailynse!


No type checking results in styled variable references blowing up

import { colors } from '@compiled/website-ui';

export const LinkItem = styled.a`
  display: block;
  font-weight: 500;
  padding: 0.5rem 0;

  :hover {
    background-color: ${colors.codeBackground};
  }
`;

Known problem. Work around is to do:
background-color: ${() => colors.codeBackground};

Which will turn it into a CSS var

Fixed in 095018d


Add deseq2_vsn parameter

Many thanks to contributing to nf-core/chipseq!
Please fill in the appropriate checklist below (delete whatever is not relevant). These are the most common things requested on pull requests (PRs).
PR checklist

[x] This comment contains a description of changes (with reason)
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If necessary, also make a PR on the nf-core/chipseq branch on the nf-core/test-datasets repo
[x] Ensure the test suite passes (nextflow run . -profile test,docker).
[x] Make sure your code lints (nf-core lint .).
[x] Documentation in docs is updated
[x] CHANGELOG.md is updated
[ ] README.md is updated

Learn more about contributing: https://github.com/nf-core/chipseq/tree/master/.github/CONTRIBUTING.md

Add .Rprofile and .Renviron empty files to container and refer to them in nextflow.config to avoid local clashes
--deseq2_vst allows users to pick the much faster vsn transform over rlog for differential analysis

My test run finally finished and it seems to have worked. But it threw a different error that DESeq2 had some dependency issues. I am currently running more tests to get to the bottom of it.


Question: Select multiple days ( not range )

Hi, thank you for your effort for giving us this extension, very helpful.
I couldn't find a way to load multiple days and/or select multiple days.
Can you help me or there's no such feature?
Thank you.

if you look at the examples, you see that selecting and storing dates is something you need to implement yourself. In your quite simple case you'd look at the "select range" example but instead of the range logic you just store all pressed dates in a list.


WIP: Carthage support

This adds support for using Moya with Carthage, using the technique described in CocoaPods/pod-template#106. It merely makes it possible to build with Carthage, though, to be useful without requiring the user to have CP installed as well, the Pods/ directory would need to be added to the repo. I didn't want to pollute the PR with that, though.
It is WIP, because it currently needs master of both CocoaPods and Carthage. I'll update the PR once those things are released, for now it is just for the adventurous.
The only duplicated effort this requires is declaring the dependencies in the Cartfile as well as the Podfile.

Cool, thanks Boris!

@ashfurrow since both CP as well as Carthage have shipped now with the required changes, this should be good to merge.
Keep this in mind, though:

the Pods/ directory would need to be added to the repo

OK cool. I've got a PR open for checking in the Pods directory. Once that is :green_apple: , I'll merge and you can rebase from master? Or should it be safe to merge directly in?
/cc @MichaelMcGuire

Ha, meeerrrrge conflict.

@neonichu Wanna rebase so I can merge?

@ashfurrow should be good to merge now, sir!

:red: can you pod install or update or whatever needs to pass?

@ashfurrow this should be :ok_hand: now


Added backers and sponsors from OpenCollective

now sponsors & backers will show up in your readme and others can back you from here as well.

:)

Was this removed for a reason? I don't see a commit that does this (did you force push?)

I force pushed, yes. Reason would be that I don't think its needed.

Why not? Just wondering.

Hello am not a robot willing to Skype appreciate my robot assume position to be sorted and fixed as soon as
Cheers
Eilatan

Well, it makes me uneasy to take donations from private persons (this was never the intention), and I don't want to actively chase companies for sponsorship. If any company likes what I do here they should hire me instead. I started this project (and was paid for doing so) at my last workplace/employer. They needed scalable WebSockets and didn't care if I made this open source or not, so I did. Now, this company has gone "poof" and I'm currently not employed (as of the beginning of May).
I'm currently being interviewed by various companies and will be joining any of these any time soon (well, that is my plan at least). So I don't really have a real issue with funding right now and I would much rather have some company hire me to work with various stuff where WebSockets could be one of these things, instead of taking donations. I keep doing this because I find it amusing and any donations on top of this wouldn't change anything.


Update log-analytics-api-alerts.md

Changed WorkspaceId to WorkspaceName in the Example script
Also changed 'OI-Default-East-US' to {Resource Group Name} at three places. But it should be ideally changed at all other places too.

@ansingha,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@ansingha : Thanks for your contribution to the Azure documentation! The author, @bwren, has been notified to review your proposed change.

@ansingha,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Warning if no index exists

The file has no index, both versions just spin.
https://s3.amazonaws.com/iobio/samples/test_files/no_index.bam

@AlistairNWard is this file public? I can't access it.

Fixed in #97


Fix "KeyError: u'max'" On Length Validator

I'm using flask-babelex for translations. When I try to raise a Length ValidationError, I get a KeyError because the message isn't using the default "%(num)d" or a dict. This pull changes "%(min)d" and "%(max)d" to "%(num)d".
Here's the whole gist if you're interested: https://gist.github.com/anonymous/a6210e203faa1a6c8ebc

Just realized I had to update translations to fix this. Updated the pull request.

@crast can you take a look at this? The change is much smaller than it looks, mainly just changing "min" to "num" here so it jives with ngettext defaults: https://github.com/wtforms/wtforms/pull/231/files#diff-f98d8f668897e84e001195c93ac781a7R97

I'll have to


[Feature Request] how can I add my component in the package?

Existing Component
No
Component Name
tree-rtl
Description
I made a copy of the tree.js component then edited it for myself (converted from LTR to RTL). I need to LTR and RTL together.
how can I add the tree-rtl.js component to the package?

anyone can help me?

I add my js file to indx.js:
import TreeRtl from '../packages/tree/index.js';
and I found that the lib folder had to be rebuilt. But I don't know how?
please help me.


LANG-1600 restore handling of collections for non-json ToStringStyle

Restore non-json-style handling of appendDetail() for Collection

addresses issue introduced in LANG-1542 with commit 1dddec8
add test cases for non-empty collections, maps, and arrays
break out those test cases into separate methods for legibility

CLA: n/a, covered by clause 5 of the Apache License

Coverage increased (+0.0007%) to 94.705% when pulling 8d027c87741acfafad2ba07428fd94646b5ca53a on amphied:LANG-1600_fix_collections_for_non-json_tostringstyle into 31dc5c700e1a08f4af33d94301ff06790533099b on apache:master.


Error while running Node.Js

Hey,
i tried to follow your video & steps. when i try "node index.js" i get this error
dyld: lazy symbol binding failed: Symbol not found: ____chkstk_darwin
can you tell me how to Fix this ??
i use a iMac (Late 2012) , with macOS High Sierra (10.13.6)
the other video (Generative Art) i was able to do it and works perfectly. This one gives the darwin error. Pls let me know how to fix it

dyld: lazy symbol binding failed: Symbol not found: ____chkstk_darwin
Referenced from: /Users/iMac/Desktop/Minter/generative-art-opensource/node_modules/canvas/build/Release/libpixman-<IP_ADDRESS>.dylib (which was built for Mac OS X 10.15)
Expected in: /usr/lib/libSystem.B.dylib
dyld: Symbol not found: ____chkstk_darwin
Referenced from: /Users/iMac/Desktop/Minter/generative-art-opensource/node_modules/canvas/build/Release/libpixman-<IP_ADDRESS>.dylib (which was built for Mac OS X 10.15)
Expected in: /usr/lib/libSystem.B.dylib
Abort trap: 6

I get the same error. Were you able to fix it?


[Brackets auto-update Windows] No message is given to user if user clicks on Cancel in Save As dialogue.

Description
No message is given to user if user clicks on Cancel in Save As dialogue.
Steps to Reproduce

Launch brackets 1.13.
Create a new file and type some text. Do not save this file.
Go to help > Check for updates.
Update dialogue appears. Click on Get it now.
Click on Update Now.
Save Changes dialogue will appear.
Click on Save button. Save As dialogue appears.
Click on cancel. No message is given to user.

Expected behavior: A message "Brackets could not be updated" should be given to user if user clicks on Cancel in Save As dialogue.
Actual behavior: No message is given to user if user clicks on Cancel in Save As dialogue.
Versions
Windows 10 64 Bit
Release 1.13 build 1.13.0-17624

This issue has been fixed in the latest builds. Please validate. @ayushrathi15

Verified on build 1.13.0-17666.


[storage][backend] NVMfPath: add list/get/stats rpcs

Signed-off-by: Boris Glimcher<EMAIL_ADDRESS>

depends on https://github.com/opiproject/opi-api/pull/300


Readme updates

Need link to jupyterlab plugin tutorial, link to labextension documentation, talk about commonjs and the default export for ES6.

Link to overview talk: https://youtu.be/WVDCMIQ3KOk


Inventory part 1, part 2, and CD with Argo

some fixes to Inventory Micro App - Part 1

Second commit takes out links to the MOOC, link to the Welcome page instead.

Third commit starts moving stuff between Inventory part 2 and CD with Argo pages to help remove overlap.


Documentation needed: Contributor's Guide

Description
We need to put together a Contributor's Guide for the developers and collaborators of Raijin. However, it needs to be done in a way to complement each other with Uxarray's (which is not put together yet either)
Links to other examples, if applicable
GeoCAT's Contributor's Guide

Close as not needed, as we're going to link directly to UXarray's Guide (https://github.com/NCAR/projectraijin.github.io/pull/11)


Tag control does not implement propertyChanging for bindable properties

When you're binding to properties of the tag control i.e. the BackgroundColor it binds correctly however does not reflect any later changes in the binding context.
For example consider the following code:
<controls:Tag
                            Text="{Binding Text}"
                            BackgroundColor="{Binding Color}" />

This binds correctly when it renders first, however if the underlying "Color" property later changes at runtime it does not get reflected on the control.

Thanks for the PR!


[MM-22558] Fix 3rd party login detection

Summary
The recent update to fix support for MM subpaths missed updating the section of code that determines if a 3rd party login process has begun or is ending. This PR updates that section of code to now allow proper 3rd party authentication to work with subpaths.
Issue link
https://mattermost.atlassian.net/browse/MM-22558

@deanwhillier
Error trying doing the automated Cherry picking. Please do this manually


Use FlatLaf JTabbedPane Close Buttons When Using FlatLaf

Turns out FLatLaf can display a close button for tabs on a JTabbedPane (I really love that library). ModernDocking will still need to implement one for system look and feels, but we can leave it up to FlatLaf for all the other themes.

Swapped to using the FlatLaf close button. Still need to set our own tab components to get a draggable component. This is done by adding a JLabel with the dockable tab text.


[Bug]: Camera disappeared after moving to Homebase 3

What happened?
After I set up the plug in, I added a Homebase 3 to my system.  I moved the garage camera to the base and then went to the app and shared the base with my guest account.  I tried to add it in the plugin, but it does not find it.  I refreshed the Eufy login, and it was not discovered. I restarted the plugin, refreshed Eufy and still cannot find it.  Now, in addition to not finding the Homebase, it will not find my garage camera since it's in the homebase.
Device Type
Station (Supported)
Plugin Version
v2.0.x (Supported)
HomeBridge Version
v1.6.x (Supported)
NodeJS Version
v18 (Supported)
Operating System
Raspbian 10+ (Supported)
Relevant log output
[22/01/2024, 15:07:36] Got SIGTERM, shutting down child bridge process...
[01/22/2024, 15:07:37]	[EufySecurity]	INFO	Finished shutdown!
[22/01/2024, 15:07:49] [homebridge-eufy-security] Cannot start child bridge, it is still running or was not manually stopped
[22/01/2024, 15:07:49] [homebridge-eufy-security] Child bridge process ended
[22/01/2024, 15:08:13] [homebridge-eufy-security] Starting child bridge...
[22/01/2024, 15:08:17] [homebridge-eufy-security] Launched child bridge with PID 556489
[22/01/2024, 15:08:21] Registering platform 'homebridge-eufy-security.EufySecurity'
[22/01/2024, 15:08:22] [homebridge-eufy-security] Loaded homebridge-eufy-security v2.2.21 child bridge successfully
[22/01/2024, 15:08:22] Loaded 8 cached accessories from cachedAccessories.0E92D47EB7E3.
[01/22/2024, 15:08:23]	[EufySecurity]	WARN	warning: planned changes, see https://github.com/homebridge-eufy-security/plugin/issues/1
[01/22/2024, 15:08:23]	[EufySecurity]	INFO	Country set: US
[01/22/2024, 15:08:23]	[EufySecurity]	INFO	Finished initializing!
[22/01/2024, 15:08:25] Homebridge v1.7.0 (HAP v0.11.1) (homebridge-eufy-security) is running on port 55890.

config
{
    "username": "**",
    "password": "**",
    "country": "US",
    "deviceName": "",
    "platform": "EufySecurity",
    "_bridge": {
        "username": "0E:92:D4:7E:B7:E3",
        "port": 55890
    },
    "ignoreStations": [],
    "ignoreDevices": [],
    "cleanCache": true
}

Bonjour, j’ai le même probleme depuis la mise à jour de ma indoor cam C210 et l’association automatique à homebase 3. Elle n’est plus reconnue comme camera


perl 5.8.8 is supported?

I try use with perl 5.8.8, but get mistake only.. Can you help me?
use strict;
use WWW::Telegram::BotAPI;
my $api = WWW::Telegram::BotAPI->new (
        token => '128914425:my_token-my_token-my_token-my_token-my_token-my_token',
        force_lwp => 1,
        async => 0
    );
    $api->api_request ('getMe');
    # Uploading files is easier than ever.
    $api->sendPhoto ({
        chat_id => 123456,
        photo   => {
            file => "/path/to/png/1441213424_178_Download.png"
        },
        caption => "Look at my cool photo!"
    });

try ./bot.pl and get
ERROR: 400 Bad Request at /usr/lib/perl5/site_perl/5.8.8/WWW/Telegram/BotAPI.pm line 139.
(in cleanup) ERROR: 404 Not Found at /usr/lib/perl5/site_perl/5.8.8/WWW/Telegram/BotAPI.pm line 139.
what i can do wrong?

Hello,
thanks for your report! I tried the module with Perl v5.8.8 (which is almost 10 years old!) and there was indeed a problem.
Basically, Perl was calling my AUTOLOAD subroutine when destroying the module object. This happened because I didn't implement a DESTROY subroutine for cleanup.
I just released a new version (v0.02) which fixes this issue. It should be available on CPAN shortly.
About your specific problem (the HTTP 400 Bad Request), it looks like you are doing something wrong. Please check the following:

Ensure that the token you are using is valid and updated. (to test, make a request with your browser to https://api.telegram.org/botYOUR_TOKEN_GOES_HERE/getMe and see if it works)
Ensure that the parameters you are passing to the requested method are valid. You can check for this in the official Bots API documentation. If you are using the example you pasted, then it obviously won't work because chat_id is not set to a real chat ID (123456)! Methods to retrieve the correct chat ID to use are described in the documentation linked before.

By the way, there's no need to use force_lwp and async in this case.

Hi!
I install 0.2 version. All fine.
use strict;
use warnings;
use utf8;
use WWW::Telegram::BotAPI;
use Data::Dumper;

my $api = WWW::Telegram::BotAPI->new (
        token => 'my-token-here-my-token-here-my-token-here-my-token-here-my-token-here',
        force_lwp => 1,
        async => 0
    );
    print $api->getMe->{result}{username} , '-' , $api->getMe->{result}{chat_id} ;

return bot username and chat_id  without any errors!

Here it is.
I'm closing the issue since the original problem has bene resolved.


KwikIO tests fail

======================================================================
ERROR: test_assert_readed_neo_object_is_compliant (neo.test.iotest.test_kwikio.TestKwikIO)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/andrew/dev/neo/neo/test/iotest/common_io_test.py", line 499, in test_assert_readed_neo_object_is_compliant
    return_path=True):
  File "/Users/andrew/dev/neo/neo/test/iotest/tools.py", line 419, in iter_read_objects
    readall=readall):
  File "/Users/andrew/dev/neo/neo/test/iotest/tools.py", line 311, in iter_generic_readers
    clean=clean):
  File "/Users/andrew/dev/neo/neo/test/iotest/tools.py", line 231, in iter_generic_io_objects
    clean=clean)
  File "/Users/andrew/dev/neo/neo/test/iotest/tools.py", line 196, in create_generic_io_object
    ioobj = ioclass(filename=filename)
  File "/Users/andrew/dev/neo/neo/io/kwikio.py", line 90, in __init__
    model = kwik.KwikModel(self.filename) # TODO this group is loaded twice
  File "/Users/andrew/anaconda/envs/neo_py3/lib/python3.6/site-packages/klusta/kwik/model.py", line 593, in __init__
    clustering=clustering)
  File "/Users/andrew/anaconda/envs/neo_py3/lib/python3.6/site-packages/klusta/kwik/model.py", line 1039, in open
    self._create_waveform_loader()
  File "/Users/andrew/anaconda/envs/neo_py3/lib/python3.6/site-packages/klusta/kwik/model.py", line 662, in _create_waveform_loader
    rate = self._metadata['sample_rate']
KeyError: 'sample_rate'
-------------------- >> begin captured stdout << ---------------------
/var/folders/mv/kgprbvgd62sbty3tvwnw0lvh0000gq/T/files_for_testing_neo/kwik/experiment1.kwik

--------------------- >> end captured stdout << ----------------------

conda list
...
klusta                    3.0.16                    <pip>
...
tqdm                      4.17.1                    <pip>
...

@lepmik any ideas? Is it a new version of klusta, perhaps?

It's the kwik test file that's wrong. It's an output from OpenEphys, remnant from the first version of the IO. If you exchange the test files with hybrid_test_120sec.* from http://phy.cortexlab.net/data/ it should work.

Hi @lepmik thanks for the quick response. The test files you pointed to are > 200 MB, which is really too big since they would be downloaded to the machine of anyone who wants to run the test (they are cached for future runs, but even for a one-time download this is too big).
Would it be possible to generate a shortened version, with, e.g. 2 seconds of activity?

Absolutely, where should I put it/send it?

On any file sharing service, then send me the link privately, and I will upload them to the G-node repository where we keep Neo test files.

Sent them to you now. Sorry for being so late.
2017-09-27 12:17 GMT-07:00 Andrew Davison<EMAIL_ADDRESS>
On any file sharing service, then send me the link privately, and I will
upload them to the G-node repository where we keep Neo test files.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NeuralEnsemble/python-neo/issues/395#issuecomment-332627120,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADQn8M4QeVutywokfWUl7kl0qYmS3kwPks5smp9QgaJpZM4PkaQt
.

--
Mikkel Elle Lepperød http://cinpla.org/people/
Centre for Integrative Neuroplasticity (CINPLA http://cinpla.org)
University of Oslo (UiO http://uio.no)
Kristine Bonnevies hus, room 2513


Proxy Tipe sock4

I have a problem
if i use proxytype socks4 it always crashes after 5 minutes.
I want to use 2 types of proxies to increase views. http/s and sock4

Can you post your config.json here?

I'm sorry, this problem is solved, it's my fault.


Run git clean with two -f

in order to properly clean subdirectories that are git repos
see https://stackoverflow.com/questions/9314365/git-clean-is-not-removing-a-submodule-added-to-a-branch-when-switching-branches
pr-link: Alluxio/alluxio#12091
change-id: cid-8398680f527f28fc588b29769925aeaf1d8e5b45

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/11214/
Test PASSed.


Added a method to create a version snapshot to the FedoraResource interf...

...ace.
https://jira.duraspace.org/browse/FCREPO-1402

Resolved with: https://github.com/fcrepo4-labs/fcrepo4-client/commit/cb8bc9e69dcafac727c421caaddd5ae8c6ef0a9a


use built-in base64_encode if available

In https://github.com/ojroques/vim-oscyank/blob/4b068e5b553f907c5f6d00b0ab9e1e3b98cf71bf/plugin/oscyank.vim#L41 it might make sense to check for https://github.com/vim/vim/commit/810785c6890ef0a1cd2428410c8488cacfbac77b

By the way, seems that Konsole will get OSC support with 24.12


[CP] Fix dart run resolution on dev-releases

Commit(s) to merge
258598eeb6612df137f6ae445e5a2d8af418da54
Target
2.19 beta and forward
Prepared changelist for beta/stable
https://dart-review.googlesource.com/c/sdk/+/273743
Issue Description
dart run will do a full resolution every time if your current sdk is a dev-release.
Causing unnecessary churn.
See eg. https://github.com/dart-lang/sdk/issues/50617
What is the fix
Removing the logic that would consider a resolution stale if it is a dev-release.
Why cherry-pick
All users of dart run on beta releases.
Risk
low
Issue link(s)
See eg. https://github.com/dart-lang/sdk/issues/50617
Extra Info
This bug affects only sdk's that are themselves dev-releases.
But as any beta-release is also a dev-release we should better fix it.
Only the https://dart.googlesource.com/pub.git/+/04f7bce8 commit is needed for this, but the other commits are either minor or themselves reverted, and seem low-risk.

LGTM

Here is the diff of pub that this includes:
https://dart.googlesource.com/pub.git/+/4fd2051bb8060ea2f2e02b13dfeb2f793d197994..21aa23f148a428ae4dd97a27ecc70b08c1328089/

lgtm

Merged into 2.19.0-444.2.beta


Sketch of doing http.status log lines

Was weighing between this approach and just manually doing log.SCountOne for each of the three methods (pub / sub / mkstream)

Looks good to me except for a couple very minor details.

Closing in favor of #23


Custom versioning strategy - is it supposed to set app bundle?

Hey! I'm using this action and it's awesome.
I'm trying an action for handling versions and changelogs, so I want to use custom versioning strategy in the Unity Builder.
Here's part of my setup:
        # Generate changelog with conventional commits
        - name: Conventional Changelog Action
          id: changelog
          uses: TriPSs/conventional-changelog-action@v3
          with:
            github-token: ${{ secrets.github_token }}
            skip-commit: "true"
            output-file: "false"

        # Build APK
        - name: Build APK with Unity
          uses<EMAIL_ADDRESS>          with:
            versioning: Custom
            version: ${{ steps.changelog.outputs.tag }}
            projectPath: ${{ matrix.projectPath }}
            unityVersion: ${{ matrix.unityVersion }}
            targetPlatform: ${{ matrix.targetPlatform }}
            buildsPath: build
            buildName: androidbuild

My questions are:

Am I using the correct inputs? Docs mention the version field but there's no example.
What is that value used for? I created APKs and the app bundle is still 0.1, which is the default value in the Unity project settings. Should this value be overriden by Unity Builder versioning? I don't understand what this is used for. I'm uploading the builds to AppCenter and later will go to the stores and I'd like them to get the version number from Unity Builder.

Hi @gpiffaretti, and thank you for your report.
First off; you're using a pretty old version of unity-builder, lots has been improved since then and some of the things you read in the docs may not even be available in v0.10 yet.

Am I using the correct inputs?

Yes I think so, but if you use the custom strategy it's up to you to provide the correct version number.
What does your tag looks like?

Docs mention the version field but there's no example.

Note that version is by default configured, so you don't have to do anything with this input unless you want to override the default behaviour.
Could you be very specific about what you would like to see for the example? I think it may be worth adding this to the docs.

What is that value used for? I created APKs and the app bundle is still 0.1, which is the default value in the Unity project settings. Should this value be overriden by Unity Builder versioning?

Yes, but I suspect this didn't happen because you're inputting some string that is not compatible with the version field. Maybe you could try omitting the v part from v0.0.0.

I'm uploading the builds to AppCenter and later will go to the stores and I'd like them to get the version number from Unity Builder.

Have you considered using builders default versioning? Might be worth considering as people have adapted it  to update the correct versions throughout.

Hope that answers your question. Feel free to reopen if not.


Exceptions handling (null handling)

There were no null checks on some of the fields, due to which we are seeing high number of exceptions. Following are the issues found during profiling -

SetUidGppService.toInt() - NumberFormatException
PubmaticBidder.parsedKADFloor() - NumberFormatException
Ccpa.isEnforced() - PrebidException

Attaching PR to fix handle these exceptions -
https://github.com/prebid/prebid-server-java/pull/3035

@Net-burst any update on this?

@amanpatniajmer hi. Sorry for the delay. This is still on our plate. We should be able to get to the issue pretty soon.

@Net-burst got merged.

Yeah, thanks for your contribution @amanpatniajmer ! Closing this issue.


Build of benchmark test fails with gcc 14.2.0

I try to run the benchmarks test on macOS using gcc 14.2.0, I get:
$ tests bench -r -c M1
INFO  > Benchmark          Compile     (native, no_opt) make CROSS_PREFIX= bench CYCLES=M1 AUTO=1 OPT=0
test/hal/hal.c: In function ‘init_rdtsc’:
test/hal/hal.c:250:10: error: ISO C forbids conversion of object pointer to function pointer type [-Werror=pedantic]
  250 |   name = (name##proc *)(dlsym(kperf, #name)); \
      |          ^
test/hal/hal.c:159:3: note: in expansion of macro ‘F’
  159 |   F(int, kpc_get_counting, void)               \
      |   ^
test/hal/hal.c:256:3: note: in expansion of macro ‘KPERF_LIST’
  256 |   KPERF_LIST
      |   ^~~~~~~~~~

Same thing using Apple's default /usr/bin/gcc (which is actually clang 16.0.0) works fine.

Thanks @rod-chapman , what exact steps did you do?

This is a known issue https://pubs.opengroup.org/onlinepubs/009695399/functions/dlsym.html

That proposed change doesn't work, since the conversion to (void *) in the printf() call is then illegal for the same reason. I will try the pragma.

This appears to work and it compiles OK with both clang 16 and gcc 14.2.0 on my Mac:
/* Temporarily disable -Wpedantic here to allow conversion
 * from (void *) to function-pointer.
 */
#pragma GCC diagnostic push
#pragma GCC diagnostic ignored "-Wpedantic"

#define F(ret, name, ...)                     \
  name = (name##proc *)(dlsym(kperf, #name)); \
  if (!name)                                  \
  {                                           \
    printf("%s = %p\n", #name, (void *)name); \
    return;                                   \
  }
  KPERF_LIST
#undef F


Pixiv - Show the image's upload URL

I don't have much to explain here. I like to source content, so if I'm about to share an upload with more than one page, I believe being able to copy the upload's URL right inside Grabber would be quite useful. I was thinking it could be shown in the "More details" tab when you inspect the upload, but it could also be a right click option that's specific to Pixiv. Better yet, it could be a global option for images that have listed sources. It'd take less clicks that way.

Do you want the source url or the page url? I'd also appreciate a key binding to copy an image's page url or open it in a browser, but it sounds like a quite specific use case to me.

Page URL. If adding a key/right-click option for it is too specific, then I'd suggest sticking to my first alternative. Pixiv page URLs should exist within the program, at the very least.

No one's looked at this, judging by the lack of interaction. The Page URL in the "Details" tab for images from the Pixiv source still takes you to an error page because it's an API URL and not the actual page URL, so the option to open Pixiv images in a browser is useless unless you meticulously edit the URL to take you to the actual page.
Has there been any progress on that? It seems weird that this is still an issue after two years. I'm not demanding people look into this, but having the page URL take you to an error page is odd.


Traffic light doc string updates

Update traffic_lights_states and light_recurrent_states doc strings in initialize and drive request and response.

Built html docs page locally, can see userguide.md is updated,  model_config and model_fields are excluded from pythonapi docs. Doc strings in request and response fields needs to be merged to the documentation branch before it can take effect in the docs


to close #138 detect if map move depends on gestures

Added hasGesture property on MapPosition. OnPositionChanged user can check if map is moved by controller or by user gestures.

+1

new usage:
 onPositionChanged: (MapPosition mapPosition, bool hasGesture) {
                    if(hasGesture == true) {
                     ...
                    }
                  },

Looks good, thanks for your patience!

This seems to be broken on version 0.5.0


DeskPad output always looks blurry even when HiDPI resolution is selected

Nice catch! When HiDPI options were added in https://github.com/Stengo/DeskPad/pull/10, the stream resolution was not adjusted accordingly, so it ended up looking the same as the low DPI variant. This should be fixed by https://github.com/Stengo/DeskPad/commit/268581f8be7a0aaea86c6990e116ea7138c3521c and is now available in Release v1.3


Multiple choice selection

As I understand it the bot framework doesn't allow for multiple choices to be selected at once from a choice prompt in Node.  Is this on the roadmap somewhere?  Are you able to speak to the timing of implementation?

At this time there is not a roadmap or ETA to share.

@mwbrown66 you could express your interest in this feature here, maybe this will give some more attention about its implementation.

Thanks - will do.
On Wed, Sep 13, 2017 at 1:14 PM, Damian<EMAIL_ADDRESS>wrote:

@mwbrown66 https://github.com/mwbrown66 you could express your interest
in this feature here https://github.com/Microsoft/BotBuilder/issues/2091,
maybe this will give some more attention about its implementation.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/BotBuilder/issues/3431#issuecomment-329252248,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AX7MfbbAU6khbbmXhDyJwhHYa255lP1Fks5siBuXgaJpZM4POl1J
.

--
Matt Brown
Technology
Xuba, LLC


Strand and read placement biases

Hi!
FreeBayes reports 4 INFO fields that are used to assess strand and read placement bias.

##INFO=<ID=SAF,Number=A,Type=Integer,Description="Number of alternate observations on the forward strand">
##INFO=<ID=SAR,Number=A,Type=Integer,Description="Number of alternate observations on the reverse strand">
##INFO=<ID=RPL,Number=A,Type=Float,Description="Reads Placed Left: number of reads supporting the alternate balanced to the left (5') of the alternate allele">
##INFO=<ID=RPR,Number=A,Type=Float,Description="Reads Placed Right: number of reads supporting the alternate balanced to the right (3') of the alternate allele">

Graphical illustration:

adapted from freebayes in depth: model, filtering, and walkthrough, page 9, Erik Garrison 2015*
Can you include these metrics in MapCaller?
Thank you!

Thanks for the suggestion. I agree these bias information is also important for downstream analysis. I'll design data structures to keep track of these information. The strand bias means an allele only occurs at specific strand, while cycle bias means an allele occurs at the beginning sequencing cycle. However, I don't understand what the placement bias means. Could you please explain it for me? Thank you very much. Moreover, Erik Garrison also mentioned allele imbalance. What does it mean? It seems like we can only observe an allele in a small portion of read alignments covering the locus. Is it correct?

Thanks for considering bias info!
Read placement bias info is used to filter for sites with reads balanced to each side (left and right), as explained in freebayes in depth: model, filtering, and walkthrough, pages 16-17, Erik Garrison 2015.
I am not familiar with allele imbalance, but it seems to be related with this:
from Galaxy Training!, Calling variants in non-diploid systems, Anton Nekrutenko 2018
it reflects significant deviation from the diploid (50/50) expectation (see https://galaxyproject.github.io/training-material/topics/variant-analysis/images/freebayes.pdf for more details)

Moreover, Erik Garrison also mentioned allele imbalance. What does it mean? It seems like we can only observe an allele in a small portion of read alignments covering the locus. Is it correct?

@ekg - can you confirm the definition?

At a heterozygous genotype the fraction of observations for the pair of
alleles is unlikely under an unbiased binomial sampling model.
On Tue, Oct 8, 2019, 08:51 Torsten Seemann<EMAIL_ADDRESS>wrote:

Moreover, Erik Garrison also mentioned allele imbalance. What does it
mean? It seems like we can only observe an allele in a small portion of
read alignments covering the locus. Is it correct?
@ekg https://github.com/ekg - can you confirm the definition?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hsinnan75/MapCaller/issues/25?email_source=notifications&email_token=AABDQEMF2PHGS3D2HCAXU73QNQUYTA5CNFSM4I52KXU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEATBSZA#issuecomment-539367780,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABDQEPFAYRHG7QPLMDH5TTQNQUYTANCNFSM4I52KXUQ
.


CLI[Test]: Improve test coverage for core/helm module

:tada: This issue has been resolved in version 0.14.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Async functions become unreponsive if Lambda global timeout occurs

When invoking an async promise if Lambda kills the function prior to the async promise being realized on subsequent calls the function is hung and doesn't enter the handler until either a new Lambda zip is uploaded or the Lambda function times out on AWS's infrastructure internally.
Using https://github.com/Type-Zero/promise-timeout-hang you can create two functions promise-hang and promise-timeout. When promise-timeout is invoked, the function will print Starting function and then throw a timeout error. Subsequent invocations behave the same.
Invoking promise-hang will print Staring function and then timeout via the Lambda timeout. Subsequent executions will not run the handler and you will not see Starting function. Basically at this point the function is useless.
I'm making this issue here because this is the top level where we encountered it but reading around the internet like http://theburningmonk.com/2016/05/aws-lambda-constant-timeout-when-using-bluebird-promise/ it appears that the problem lies in how bluebird is handling async promises.
Any insight is welcome. I'm not quite up to debugging this all the way down.

@joekiller Thanks for reporting this - I haven't run into it, as the functions I have in production are all using the legacy core.async behaviour.  The obvious naive, miserable, expedient hack would be doing something like this in user code:
;; i haven't executed this
(defn racing-timeout [outer-promise ctx]
  (let [remaining (-> ctx cljs-lambda.context/time-remaining (* MAGIC-FACTOR)
         timeout  (-> (ex-info "Timeout" {::type :timeout})
                      p/rejected (p/timeout remaining)]
    (p/any [outer-promise timeout]))

;; You'd then have e.g.
(deflambda xyz [_ ctx]
 (racing-timeout (the-real-guy) ctx))

Obviously that sucks, and given that the stakes are so high, you'd want to have a really conservative MAGIC-FACTOR, like .8 or something.  Also, putting it in cljs-lambda would be no fun, b/c as per the link you gave, it will alter the user-facing behaviour of timeouts.
I'm with you that trying to get to the bottom of this some other way seems like the right approach, and I'm motivated to have Bluebird promises work w/ cljs-lambda.
The difficulty in debugging it (locally, ideally) is that I'm not 100% clear on how the Lambda harness terminates an invocation - which is something I'll look into.  Given that, it'd probably be trivial to reproduce in a short Javascript file, to take Lambda out of the equation.  I'll post any updates here.

N.B. from looking through /var/runtime/node_modules/awslambda/index.js (via docker run -t -i --entrypoint sh lambci/lambda), it looks like a native library, liblambdaruntime.so (linked w/ libpthread FWIW) is used to manage the details of invocations, so it's likely they're doing something cute on the edges of the Node process.  That's going to make it a little harder to reproduce, but there's only so many different things they could be doing, I guess.

I haven't tried myself but https://github.com/lambci/docker-lambda has a
very similar execution environment.
-Joe
Sent via mobile.
On Feb 13, 2017 6:06 PM, "Moe Aboulkheir"<EMAIL_ADDRESS>wrote:

N.B. from looking through /var/runtime/node_modules/awslambda/index.js
(via docker run -t -i --entrypoint sh lambci/lambda), it looks like a
native library, liblambdaruntime.so (linked w/ libpthread FWIW) is used
to manage the details of invocations, so it's likely they're doing
something cute on the edges of the Node process. That's going to make it a
little harder to reproduce, but there's only so many different things they
could be doing, I guess.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nervous-systems/cljs-lambda/issues/62#issuecomment-279553061,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA-bxwh1TMSq7sAD8XUAFYFOR4u22eN4ks5rcOHWgaJpZM4L_zrt
.

Doh, obviously from you second remark you are using docker-lamda

Annoyingly, I can't reproduce this in Javascript, using the code from that blog post.  I tried old versions of bluebird, incl. the one used by promesa, as well as invoking via API Gateway, and reducing the memory allocation to the minimum - it logs hello every time.

After some headache, I can get it to happen in JS if I set the function timeout to 1 second and include a module-level statement to generate a million random bytes and encode them to hex.  Without that statement (or, presumably, something taking an equivalent amount of time, like, say, loading some compiled Clojurescript) I can't trigger it.
Doing it with Clojurescript, I can get it to fail with this:
(def ^:export promise-hang
  (js* "function(input, ctx) { console.log('Starting'); require('bluebird').delay(5000).then(function() {ctx.succeed(nil, \"Hello\") }); }"))

(that's w/ :optimizations :none, with no dependencies except for clojure & clojurescript, w/ bluebird in the npm deps - i.e. it's not an interaction w/ the cljs-lambda runtime library, or promesa, it seems be be a combination of bluebird and the amount of time it takes to load the handler module).

Interesting.
I'm attempting to make a pure JS version like in the article as well. Depending on where this goes we might raise an issue with AWS for assistance but ideally we can solve this without their involvement.

In case this is helpful:
handler.js
const P = require('bluebird');

for (var i = 0; i < 100; i++) {
  require('crypto').randomBytes(10000).toString('hex');
}

module.exports.hello = function(event, context, cb) {
  console.log('hello');
  P.delay(3000).then(() => context.succeed()).catch(err => context.fail(err));
}

serverless.yml
service: hello

provider:
  name: aws
  runtime: nodejs4.3

package:
  include:
     - node_modules/**
functions:
  hello:
    handler: handler.hello
    timeout: 1
    memory: 128
    events:
      - http:
          path: ok
          method: get

package.json
{
  "dependencies": {
    "bluebird": "^3.4.7"
  }
}

(The above exhibits the behaviour w/ serverless invoke -f hello -l - doesn't need to be used via API Gateway.
In terms of fixing it, I've tried a few things:

Promise.setScheduler(f => setTimeout(f, 0))
const Promise = require('bluebird').getNewLibraryCopy() (at module level, as well as at the start of the handler)
process.on('unhandledRejection', function() {})

This is totally an AWS issue, but yeah, they would take forever.

Here is an AWS forum search with others having this problem: https://forums.aws.amazon.com/search.jspa?mbtc=17f935f4bea316e32a9c36a30b3949eeab4b30887c2b473ff38f848b540f764d&threadID=&q=bluebird&objID=f186&userID=&dateRange=all&numResults=15&rankBy=10001

Thanks.  Note that in the example I gave above, it should be memorySize, I think, not memory - it will always work w/ Serverless' default memory size of 1024.

I'm out of time for today, a couple of notes:
I don't think this is related to Bluebird - I think that, bizarrely, toplevel code just takes longer to run the second time around - so given an example with either a very small timeout or significant module-level work, the invocation is terminated before the function is called.
Take this guy, with no promises:
const init = Date.now();

for (var i = 0; i < 200; i++) {
  require('crypto').randomBytes(10000).toString('hex');
}

module.exports.hello = function(event, context, cb) {
  console.log(Date.now() - init);
  setTimeout(
    function() {
      context.succeed('Done');
    }, 3000);
}

deploying and then running 3 times, I get, 61, 959, and then nothing/timeout.
If I move the first two chunks inside the handler, I get values from 500-timeout, with no definite jump in the magnitude between the first invocation and the rest.  In both cases, it doesn't wedge until you redeploy - if the duration of the work is very close to the timeout value, it'll work sometimes if you repeatedly invoke.
I'm not sure why the elapsed time is 15x smaller for the first invocation only when the work is happening at the toplevel.

In terms of why promise-hang behaves differently from promise-timeout - I don't yet have an answer, but so far all of the minimal examples I've tried have had errors reducible to the issue I described above.

The init = Date.now() is outside the handler context, so that is resolved at the initial container start up and the context carries over on subsequent executions (http://blog.rowanudell.com/database-connections-in-lambda/) so that is why the numbers get bigger when it runs again.
I'm still digging into why a subsequent execution doesn't work but it seems like it has something to do with container re-use and thawing.
I side note, I think the library needs to be updated to use the new callback function for lambda conclusion. This may actually fix lingering promises problem. Because using context method calls freezes the execution immediately while using the callback function the docs indicate that other methods are allowed to complete. (Punchline in bold):

When the context methods are called, AWS Lambda freezes the Node process immediately, without waiting for the event loop associated with the process to empty. The process state and any events in the event loop are frozen. When the function is invoked again, if AWS Lambda re-uses the frozen process, the function execution continues with its same global state (for example, events that remained in the event loop will begin to get processed). However, when you use callback, AWS Lambda continues the Lambda function execution until the event loop is empty. After all events in the event loop are processed, AWS Lambda then freezes the Node process, including any state variables in the Lambda function.

I found this after reading up on container reuse in Lambda. I wanted to look more into how our context callbacks were working. I googled lambda context.fail and one of the first hits I found was Using the Earlier Node.js Runtime v0.10.42 - AWS Lambda which mentions in the transitioning to new nodejs runtime that the latest lambda wants us to use the newer callback method instead of using context object calls.

@joekiller I'd have noticed if that was what was happening - in none of my invocations did init have the same value as a previous call:
const init = Date.now()
...
module.exports.handler = function(...) {
console.log([init, Date.now() - init]);
...
}

2017-02-14 18:43:03.583 (+00:00)        6ac274d6-f2e5-11e6-908c-25be2e820445    [1487097783535, 48]
2017-02-14 18:43:06.964 (+00:00)        6c7f4000-f2e5-11e6-a731-ab7d1ae05307    [1487097786362, 602]
2017-02-14 18:43:09.502 (+00:00)        6e12fee6-f2e5-11e6-b6f9-69ccac0aab6d    [1487097788983, 519]
2017-02-14 18:43:11.782 (+00:00)        6f730478-f2e5-11e6-a9bf-11057c99bb17    [1487097791283, 499]
2017-02-14 18:43:14.220 (+00:00)        70d2bb45-f2e5-11e6-8ea9-c1393fa9b2b8    [1487097793584, 636]

If you want to check whether using the callback affects your function, something like
(defn ^:export promise-hang [x y cb]
  (prn "Starting function")
  (-> (p/delay 5000)
       (p/then (fn [] (cb nil "Finished function")))))

I'm not sure that it would - in your example none of the context methods are called, because the function is terminated.

I think you are correct that the example will not use the callback either. The delay will never return if the timeout always kills the process first.
I made the example the way I did because it appeared to make the same behavior each time. In our real code though we expect nearly all code to run faster than the timeout but believe that the legacy way of calling context methods causes lingering promises to go unresolved which makes the code unsreponsive after the initial execution.

I can publish a snapshot tomorrow which uses the callbacks, if you want to test with that, but regarding the above, a pure Javascript example which captures the issue you're talking about would be helpful to me.

@joekiller another example, in the context of your project:
(defn ^:export promise-hang [input ctx cb]
  (prn "Starting function")
  (-> (js/Promise.
       (fn [resolve]
         (js/setTimeout #(resolve) 3000)))
      (.then (fn [] (cb nil "OK")))))

That's not using bluebird, but rather the native node promise, and none of the cljs-lambda wrappers are in play - this function will be directly invoked by Lambda, with the only other work being the loading of Clojurescript & libraries - and it still hangs with nothing printed.

How about a snapshot that leaves all context or callback executions to the client instead. I think the root problem is having the context calls always happening when the lamda handler finishes. Dropping out of the function without a signal is valid. It does trigger a error on Amazon's side but that is expected.

If the context.[success, done, error] is called then code execution is frozen but outstanding promises may be realized on subsequent executions on the same container. Further because of the single state machine underneath if multiple promises or callbacks stack up their variables to call with are overridden by the last executions context.
Even if the code was changed to resolve the promises prior to exit, ie using the callback, with the default !stop invoking callback or context methods, the interface is taking away that 4th exit option of dropping out of the function with no calls.
Forgive me if I'm misunderstanding the code.

PS the following is the repo I was testing for JavaScript. I think the linked commit best matches what we are trying to test. Also note that it appears that const init = Date.Now() can actually change as it appears that const gets compiled into a mutable reference resolved in the handler. I wrote a file to disk to test this. Also sometimes the const does resolve in the global content sometimes when I tested. I can't really explain it other than some strange state side effect.
https://github.com/Type-Zero/promise-timeout-hang-js/blob/ff27a2305b3bf4c474e4ee9ccd4f72fc3e1a43cf/index.js

@joekiller You can do that already, per my most recent example above - you just define a regular clojurescript function w/ :export metadata, and have an entry for it in the cljs-lambda -> functions section of your project file.  You get the arguments directly from Lambda, which treats it as a bare Javascript function.  If you want the arguments in exactly the same shape as you get them from cljs-lambda, then you can do:
;; this won't pass you the cb argument, but it's also not doing anything complex at all
(def ^:export handler
  (cljs-lambda.util/wrap-lambda-fn (fn [ctx event] ...)))

Neither of those approaches touches the context object for you - deflambda and async-lambda-fn, the thing it uses, are specifically for the case where context management is being delegated to the library.

Okay, so currently we have something like:
(defn handle-this [{:keys [event context] :as request}]...)

(def app
  (-> handle-this
      wrap-that))

(def ^:export myfunction
  (make-lambda app))

Are you saying to instead do the following to prevent touching of the context object?
(def ^:export myfunction
  ((cljs-lambda.util/wrap-lambda-fn app))

If that is true, then that'll probably work for us and I'd be in favor of updating those context calls to callbacks.

@joekiller, yeah, basically:
;; wrap-lambda-fn takes a function, returns a function, so you don't need to invoke its
;; return value, only to bind it to a name:
(def ^:export myfunction (cljs-lambda.util/wrap-lambda-fn some-fn-of-two-args))

On the other thing,  looking at the AWS code, there is a difference in how the context/callback is handled:

function invoke(handler, event, baseContext, finish) {
    let waitToFinish = true;
    let consumed = false;
    const callback = (err, data) => {
        if (consumed) {
            return;
        }
        consumed = true;
        finish(err, data, waitToFinish);
    };

    const context = Object.assign({
        set callbackWaitsForEmptyEventLoop(value) {
            waitToFinish = value;
        },
        get callbackWaitsForEmptyEventLoop() {
            return waitToFinish;
        },
        done : function(err, data) {
            waitToFinish = false;
            callback(err, data);
        },
        succeed : function(data) {
            checkExpectedArgRange('succeed', arguments, 0, 1);
            context.done(null, data);
        },
        fail : function(err) {
            checkExpectedArgRange('fail', arguments, 0, 1);
            context.done(isUndefinedOrNull(err) ? '__emptyFailParamBackCompat' : err, null);
        }
    }, baseContext);

    handler(event, context, callback);
}

i.e. if you happen to have work in the event loop, by default, the callback will wait for it to complete, calling context.done etc. will not - that is the only difference, but it may be germane to what you're trying to do.
My offer about changing cljs-lambda to implicitly use the callback parameter still stands (and giving it as a third parameter to wrap-lambda-fn inputs which support that arity)- that's about all I can do.

I forgot the actual code that made the lambda.on my.mobile so please excuse the crude screenshot

I'll try this tomorrow.

Cool. Try updating the code as I think it'll fix the black hole anyway but I think we'll invoke as you suggested after testing.

@joekiller If by black hole, you mean any of the (apparently) sticky timeouts demonstrated in the examples posted here or in the linked blog post, I personally don't think so - and I'm easily able to recreate them using the snapshot, or just using Javascript code which invokes the callback.  It may fix some other issue you're seeing which isn't captured in the examples, though.
io.nervous/cljs-lambda 0.6.5-SNAPSHOT (i.e. runtime library)
If you are managing completion yourself (by exporting the result of wrap-lambda-fn), there's a :handler-callback key in the context record:
((:handler-callback ctx) (js/Error. "Oops"))
((:handler-callback ctx) nil {:x 1 :y 2}))

If using deflambda or async-lambda-fn, the callback will be used to signal completion.  ctx/done! etc. will obviously continue to do the same thing as their js counterparts, if invoked explicitly.

Okay we tested using the callback, the lightweight wrapper and eventually pulled out cljs-lambda all together and it still happened. Eventually we pulled bluebird out and everything seemed to work again. So we have filled https://github.com/petkaantonov/bluebird/issues/1341

OK - I hope you get some resolution.  Note that while I can reproduce the issue when that example function's deployed with a memory size of 128mb and timeout of 1 second, I can also reproduce it if I change the first line to:
const ignore  = require("bluebird").noConflict();

So that the handler body is using the native promise.  If you pull out bluebird, but you don't replace its import with something which takes a similar amount of time to load, then all variables are not being controlled for.

Hi @moea, so after much head scratching, everything works fine after bumping the ram on the lambda function. We are going to dig into it a little more and ask AWS why resumption of a previously frozen function that executed would then cease to work.

Hi i'm closing this. I can finally reproduce the problem in pure JS. Check it out here: https://github.com/Type-Zero/promise-timeout-hang-js
The short is it seems if your code outside of the handler consumes more than ~16% of your memory, if NodeJS suffers a timeout, the function is hosed.
The crypto code outside the handler proved with some tweaking to consistently kill the function.

Oh my god. Just in case anyone else lands here and makes my mistake: make sure you haven't accidentally deployed AWS.config.update(...) using a localhost endpoint instead of an actual AWS region-specific endpoint. That can present with similar symptoms as above (say, if the only async function you're using is accessing a DynamoDB document client) but for utterly different reasons.
@joekiller Despite my stupidity, I've managed to learn a lot from this discussion. Thanks for posting it.

FYI AWS finally fixed the memory problem.


Feat polling app

Please describe the changes this PR makes and why it should be merged:
Added a RealTimePolling app built using million.js and React. It allows users to vote and see the progress through numbers and simple progress bar.
Status
Closes #615

[ x] Code changes have been tested against prettier, or there are no code changes
[x ] I know how to update typings and have done so, or typings don't need updating

Semantic versioning classification:

[ ] This PR changes the codebase

[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
[ ] This PR changes the internal workings with no modifications to the external API (bug fixes, performance improvements)

[ ] This PR only includes non-code changes, like changes to documentation, README, etc.

 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.Uzair Noman seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@UzairNoman, this is nice.  But there is no button to clear/reset the form or delete an option.  I had to refresh the page before I could create a new poll.
Can you add them? Then we can merge this PR.

Hi @Timonwa, there is a blocker to making your suggested changes, please have a look at the issue I created #680. Since this is the issue with block() wrapper. Can I implement this without wrapping the function in block()?
Let me know what you think.
Thanks

Hey there @UzairNoman, could you please share a screen recording of the problem and maybe share a link to your code? Thanks

Hey there @UzairNoman, could you please share a screen recording of the problem and maybe share a link to your code? Thanks

Hi @tobySolutions, I have mentioned the blocker in screen sharing in issue https://github.com/aidenybai/million/issues/680. But I think you have closed the polling app feature, this feature is almost completed, just need a reset button as @Timonwa suggested. I will implement it soon we find some solution to #680.

Oh. @UzairNoman, sorry about that. Unfortunately, accepted projects have to be using Millionjs. You can try again when the issue has been resolved.


Add type predicate to Boolean (BooleanConstructor)

Suggestion
Add an overload to Boolean defintion
 interface BooleanConstructor {
     new(value?: any): Boolean;
-    <T>(value?: T): boolean;
+    <T>(value?: T): value is Exclude<T, false | null | undefined | 0 | ''>
     readonly prototype: Boolean;
 }

playground
Use Cases

Array.filter
declare const actions: Array<(() => void) | null | undefined>
actions.filter(Boolean).forEach(act => act())

Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

Duplicate of #31164, #24063, #16655. Was implemented by #29955, and broken by #31515.


macro-dial-tryagaintwo is not setting up dial command properly

probably some kind of variable scope snafu
dial cmd is getting an empty number
this is after the first attempt was properly formatted, we got here because of temporarily unavailable response from provider
[Jun 17 21:31:04] VERBOSE[12993][C-00000287] pbx.c:     -- Executing [s@macro-dial-tryagaintwo:5] Dial("SIP/twilio-termination-000003dd", "SIP/@twili
o-termination,,g") in new stack
[Jun 17 21:31:04] VERBOSE[12993][C-00000287] netsock2.c:   == Using SIP RTP CoS mark 5
[Jun 17 21:31:04] VERBOSE[12993][C-00000287] app_dial.c:     -- Called SIP/@twilio-termination
[Jun 17 21:31:04] VERBOSE[1468][C-00000287] chan_sip.c:     -- Got SIP response 400 "Invalid phone number" back from <IP_ADDRESS>:5060

this was an outgoing-dialstatus-CONGESTION
only one for that day
outgoing-dialstatus-CHANUNAVAIL attempts from that day did not have the problem
does this happen for all CONGESTION?


EXC_CRASH (SIGKILL (Code Signature Invalid)) When launching app signed on MacOS

Describe the bug
Desktop App crash at launch for macOS.
Log when launching task packagePkg
....
/Users/XXXX/Documents/Projects/XXXX/build/compose/tmp/sign/libskiko-macos-x64.dylib: signed  []
/Users/XXXX/Documents/Projects/XXXX/build/compose/tmp/sign/libskiko-macos-x64.dylib: signed Mach-O thin (x86_64) [XXX.XXXXX.libskiko-macos-x64]
Warning: Using unsigned app-image to build signed pkg.
....

EDIT: After setting my certificate Application & Installer to "Always trust" like I saw in the logs. I unable to build a distributable. And I get:
Related problem saw in https://slack-chats.kotlinlang.org/t/8263564/hey-guys-i-am-trying-to-publish-my-jetpack-compose-app-to-th
/Users/XXXX/Documents/Projects/XXXX/build/compose/tmp/sign/libskiko-macos-x64.dylib: signed  []
Warning: unable to build chain to self-signed root for signer "3rd Party Mac Developer Application: XXXX (XXXX)"
/Users/XXXX/Documents/Projects/XXXX/build/compose/tmp/sign/libskiko-macos-x64.dylib: errSecInternalComponent

Error:
Exception Type:  EXC_CRASH (SIGKILL (Code Signature Invalid))
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: CODESIGNING 1 Taskgated Invalid Signature

Gradle:
nativeDistributions {
            targetFormats(TargetFormat.Pkg)
            packageName = "XXXXXX"
            packageVersion = "1.0.6"

            macOS {
                bundleID = "XXXX.XXXXXX.XXXXX"

                provisioningProfile.set(project.file("embedded.provisionprofile"))
                runtimeProvisioningProfile.set(project.file(("runtime.provisionprofile")))
                entitlementsFile.set(project.file("entitlements.plist"))
                runtimeEntitlementsFile.set(project.file("runtime-entitlements.plist"))

                appStore = true

                signing {
                    sign.set(true)
                    identity.set("3rd Party Mac Developer Application: XXXX (XXXX)")
                    keychain.set("/Users/XXXX/Library/Keychains/login.keychain-db")
                }
            }
        }

Affected platforms

Desktop

Versions

Kotlin version*: 1.9.20
Compose Multiplatform version*: 1.5.11
OS version(s)* (required for Desktop and iOS issues): MacOS 14.0 (23A344)
OS architecture (x86 or arm64): arm64
JDK (for desktop issues): jdk-<IP_ADDRESS>+1

To Reproduce

Launch task packagePkg

Expected behavior
App launch successfully
Additional context
App needs to be available on TestFlight

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


DIY hardware tutorial for the Locha Mesh

Goal of this anex.
According the open natura of the proyect we need to publish a DIY - Do It Yourself -  alternative for all who want to build it.

This Draft is open for reviews and/or corrections or improvements of the reviewers, feel free to comment.

@luisan00 this PR has been reviewed and edited. You can approve it to be merged when you've finished adding images or anything you may have left to add.


Incorrect placement of Anything V3 pt file

I have noticed that you recently added the .vae.pt file to the colab file.
Sadly, the placement is wrong as it is a hypernetwork which means it needs to be located in models/hypernetworks that folder doesn't exist by default and also needs to be created first via mkdir -p models/hypernetworks while being inside the folder.
example that I used and gave to someone else before the edit:
!pip install -q https://github.com/camenduru/stable-diffusion-webui-colab/releases/download/0.0.14/xformers-0.0.14.dev0-cp37-cp37m-linux_x86_64.whl

!git clone https://github.com/camenduru/stable-diffusion-webui
%cd stable-diffusion-webui
!mkdir -p models/hypernetworks

!sed -i -e 's/numpy==1.23.3/numpy==1.21.6/g' requirements_versions.txt
!sed -i -e 's/fairscale==0.4.9/fairscale==0.4.6/g' requirements_versions.txt

!wget https://huggingface.co/Linaqruf/anything-v3.0/resolve/main/Anything-V3.0-pruned.ckpt -O /content/stable-diffusion-webui/models/Stable-diffusion/Anything-V3.0-pruned.ckpt
!wget https://huggingface.co/Linaqruf/anything-v3.0/resolve/main/Anything-V3.0.vae.pt -O /content/stable-diffusion-webui/models/hypernetworks/Anything-V3.0.vae.pt

!python launch.py --share --force-enable-xformers

@Mar0xy please check vae.pt and hypernetworks again 🙄

Just checked again and noticed that I got very confused about terms again during the night :sweat_smile:


Future request - progress bar

cpz and rmz are very fast, but adding some eye candy like progress bar would be possible?

That'll require a bunch of extra CPU time which goes against the goals of the project, so not going to happen. Thanks for the suggestion though.

Would it be possible instead to add a flag like --progress or --verbose to get some insight into what has been deleted/copied so far? Particularly with a huge directory, would be helpful to get a sense for how long it might take + parallelization factor.

I'm open to having something behind a flag. I still don't think a progress bar is a good idea since that implies reading the entire source directory to get accurate percentages, but I think having a simple Number of files copied: N line that's continuously updated is reasonable. Won't have time to work on it myself though.

Ooooh, now this would be neat: https://github.com/emersonford/tracing-indicatif. I had planned on adding tracing at some point anyway. Just needs the right cfgs.

This would be nice - either method you've highlighted. After moving 50GB tree of various sized files from local to SAN storage tonight I'm a convert - fast - last time I did this was with tar. The lack of progress did make me a little concerned as to how long it was going to take. It would certainly leave me concerned if I were to be moving terabytes of data (potentially taking days or weeks) and not really knowing if things had locked up. Even the old spinning /-|/- cursor every couple hundred files or MB could be enough to ease the nerves.  :)

Totally forgot about this, but I had added tracing support for other reasons! Anyway, I added an off-by-default progress feature that when compiled in logs every directory's copy progress. It's pretty noisy IMO (see https://github.com/emersonford/tracing-indicatif/issues/6 if you want to work on that) and was ~2x slower by wall-clock than without progress (and can be orders of magnitude worse if your terminal can't keep up with the output stream, but again that can be fixed by https://github.com/emersonford/tracing-indicatif/issues/6).
To use the feature you need to install with cargo install --features progress.

@SUPERCILEX Do all commits from the previous release add only a progress bar or something else (speed/stability)? If something more, would it be possible to make a new release and add it to cargo.io (a new release without the progress bar by default, sounds reasonable)?

I'm happy to throw up a release. 2.1.0 is out. :)


Error while charging ninebot es4 from 4a charger on shfw 133-3.7.2

When I updated from 133-3.7.1 to 133-3.7.2 my scooter stopped charging on the 4a charger, a red wrench appears briefly and charging restarts.This is not observed on firmware 255-3.7.2, but it does not display the external battery in scootbatt on 255 firmware. Please fix this:(

When I updated from 133-3.7.1 to 133-3.7.2 my scooter stopped charging on the 4a charger, a red wrench appears briefly and charging restarts.This is not observed on firmware 255-3.7.2, but it does not display the external battery in scootbatt on 255 firmware. Please fix this:(

Bug reports go there, thanks.
https://github.com/scooterhacking/scooterhacking-issues-public/issues/


Trigger: Ctrl + Left click

Greetings,
I am trying to trigger a "Ctrl + Left click" at an element, which normally will open a popup window.
At this point, I am using the following method (from phantomjs):
casper.page.sendEvent('click', 100, 100, 'left', 0x04000000);
// and then
casper.echo(casper.popups.length);
// which returns 0
Can anybody confirm that clicking with a modifier is possible?

I don't know but, I think it can not work with bookmarks - right?

Sorry, but I can't follow your comment.
After some further testing, I actually managed to open a popup.
So, I can confirm that the above is possible.


Add multi vhost would be a great add

I do love docker and use it on my local for some projects.
It would be great if we can make it to multi-host, so we can have multiple projects inside it.
I can make a PR for this, if you want.

@ivankristianto This is an awesome idea.
Not having a single docker environment for multiple WordPress sites is the only reason I haven't ditched WAMP yet:
+ wp-docker
+ project-1
+ project-2

Could you just map the sites-available directory to a directory with nginx configs for any projects you have?

In docker-compose.override.yml you could try adding another nginx / volumes / conf file mapping (see docker-compose.yml) for default.conf instead of what it is, then you can add a few different hosts/servers there.

This project is intended to be one project per environment.


Redirecting only stdout to os.devnull with subprocess causes error in stderr

The problem is demonstrated below. It doesn't occur if stderr is redirected to DEVNULL (or perhaps the exception is just swallowed in that case). With CPython there are no problems.
IronPython 2.7.9 (<IP_ADDRESS>) on .NET 4.0.30319.42000 (64-bit)
Type "help", "copyright", "credits" or "license" for more information.
>>> from subprocess import Popen, PIPE
>>> import os
>>> DEVNULL = open(os.devnull, 'w')
>>> p = Popen(['python', '-c', 'print("hi")'], stdout=DEVNULL, stderr=PIPE)
>>> print p.stdout
>>> print p.stderr.read()
close failed in file object destructor:
sys.excepthook is missing
lost sys.stderr

@pekkaklarck I'm not able to reproduce the issue over here. I get the following output:
IronPython 2.7.9 (<IP_ADDRESS>) on .NET 4.0.30319.42000 (64-bit)
Type "help", "copyright", "credits" or "license" for more information.
>>> from subprocess import Popen, PIPE
>>> import os
>>> DEVNULL = open(os.devnull, 'w')
>>> p = Popen(['python', '-c', 'print("hi")'], stdout=DEVNULL, stderr=PIPE)
>>> print p.stdout
None
>>> print p.stderr.read()

>>>

Are you sure the exception message is it not coming from python?

The error probably comes from the executed python. I don't get it when I run the same code with CPython or Jython, so I thought it has something to do with IronPython. Since you don't get it, it may be due to something else. I can try to debug it further.

Closing since I'm not able to reproduce the issue, feel free to re-open if you have any more info.


Bad Error Handling

Errors should be passed up to the top-level user-interface method, rather than being panic!s. Errors should include their original cause and be encapsulated in Results. Errors should be displayed to the user, and should prompt the user to press Enter before quitting.

This is done for roblox_steam_launcher_master, but not for roblox_steam_launcher_substitute.


consider non-factioned roguelikes

[ ] egyptian/fossils
[ ] frost ice / yetis
[ ] illagers in non-factions biomes
[ ] bugs - think sillithus mixed with ice and fire
[ ] nether - flesh, blood, and bones, and vampires
[ ] nether - fire, fire, fire, and lava
[ ] end - endstone, obsidian, stygian fluids, pink
[ ] stank - garbage, mud, poison, stank

FLESH FROM BONE!

STOP SAYING THAT!

https://www.youtube.com/watch?v=4xuQv8IPJ18


Expose content negotiation DSL for HTML responses

---------- Forwarded message ----------
From: Arto Bendiken
Date: Wed, May 26, 2010 at 3:18 PM
Subject: Re: Rack::LinkedData
To: Nicholas J Humfrey
On Wed, May 26, 2010 at 2:04 PM, Nicholas J Humfrey wrote:

Finally, have you had any thoughts about mixing RDF serialisations
with
ERB/HTML responses? It would be go to set this per route, rather than
creating a new 'fake' RDF writer. How about something like this?

get '/njh' do
@rdf = RDF::Graph.new { ..... }
negotiate 'text/html', 'application/xhtml+xml' do
erb :page
end
@rdf
end
I really need this for dbpedia lite.

The assumption in Rack::LinkedData is currently that the Rack app will
handle any HTML requests. That is, if you e.g. output an ERB page as
the Rack app's response, then Rack::LinkedData won't do anything to
that response, propagating it upwards to the web server without any
changes.

I saw that, however the issue is trying to making it part of the content
negotiations. I want to to able to give the request header: "Accept:
application/rdf+xml;q=0.5,text/html" and to get some HTML back by
preference.

That ("application/rdf+xml;q=0.5,text/html") should work, actually -
your application always has first shot at what kind of a response it
wants to generate.
But I suppose the problem with the present setup is not so much
knowing when to generate an HTML response, but knowing when to
generate an RDF one without having to parse the Accept header oneself.
So yeah, we need something more for this.

So, as far as I can tell, the example you gave should more or less
work, if you wrap an if/then/else block around the negotiate versus
returning the @rdf object. (I'm assuming negotiate is a Sinatra
construct.)

No 'negotiate' is something I just made up. I thought it might be
something that could be added to Rack::LinkedData to add a content type to
the negotiations.

Right, that makes sense. I'll see what I can do; I'll probably create
something similar to the content negotiation DSL in Rails (good ol'
responds_to), which should look and work quite similar to what you
want.

Use https://github.com/kamui/accept_headers.


Populate New Issue with template

https://github.com/blog/2111-issue-and-pull-request-templates
We'd need to first do a lookup for any file called ISSUE_TEMPLATE.md in either root or .github then apply that markdown to the body of the new issue.

Wo! I hadn't even thought of this. Love it!

Omg yes!

So I started doing this and then realised I approached it completely wrong 😅 Turns out GitHub don't care about file extensions or the case it's written in so using GET /repos/:owner/:repo/contents/:path searching for the file name wouldn't work
Instead need to load both directories (root and .github) and do some sort of regex to find the files
Gonna hold off a little until more files stuff has been done (being worked on at the moment) but writing this to remind myself/who ever picks it up

https://help.github.com/articles/about-issue-and-pull-request-templates/
Just seen this on Fastlane, looks super cool! Would be ace if we could work it out

If only there was an API

GitHub offers a simple way to add an issue template but it is restricted to people with write access to the repo.
It would be awesome if someone with write access could implement this. After implementing this and #2126, we would be a step away from complying with community standards.

I think this is was about implementing it in the app, not necessarily the repository itself. That said, we could also benefit from this. Will work with a pull request as well, so free to open one @rodrigobdz!
Sent with GitHawk

I would love to but unfortunately I don't have enough access right to create the templates as suggested in the guide.

You should be able to, GitHub just offers some UI/help to create them for project owners. Starting with a issue_template.md should be fine if you’re up for it 👍
And otherwise we can sort it out after!
Sent with GitHawk

I'll import the templates from elsewhere and submit a PR today.


Digitally Sign Build

When trying to install Pear AI windows defender blocks the installation

Describe the solution you'd like
Digitally Sign the application similar to the way Cursor AI does

Example Certificate from Cursor AI

Will do! Waiting on our Windows certificate. This shall be done very soon. Thanks


CamelQuarkusQuartzConnectionProvider should implement PoolingConnectionProvider

I'm not entirely sure how Quartz treats differently ConnectionProvider & PoolingConnectionProvider. But since Agoral is backing CamelQuarkusQuartzConnectionProvider, then it should probably implement PoolingConnectionProvider if possible.

@jamesnetherton There is a problem with PoolingConnectionProvider.
In case of PoolinConectioProviderQuartz calls different method (with comparison to ConnectionProvider) - code.  This method propagates all configuration attributes to the datasource. Problem is, that before getting the datasource I need to know the DS name, to inject appropriate agroal ds. With ConnectionProvider this was not a problem, because datasourceName could be propagated right into the camel-quarkus class - code.
I see several options, how to handle this:

Enforce limitation to use only 1 ds -> therefore name is not needed
I can implement a "workaround", which allows configuration of ds name in the same way as with ConnectionProvider. There is only 1 limitation - no other properties could be set in that way.
Better sollution then 1. I can configure through quarkus properties, which one DS should be used for the quartz. Which allow users to define more DSs and select one of them for the quartz. Limitation is, that only 1 DS could be used for the quartz.

My PoV:
Solution 3 is better then 1 -> it limits users to use only 1 DS for quartz cluster (which might cover majority of the use cases)
Solution 2 allows to define several quartz clusters with different DS. (users can not use other properties for connectionPoolProvider as is stated here)
It should be possible to combination solutions 2 and 3 together (choose 1 DS and configure properties for it or to use more DSs without properties). Do we want to make this configuration too complex?

Do we want to make this configuration too complex?

It's already quite complex so I guess we should avoid complicating it any further.
Let me think on what to do a bit more. It's probably not super critical that we move to PoolingConnectionProvider but it'd be nice if we can find a clean way of doing it.

Another fact I wasn't considering before. This functionality (clustering via quartz properties) should probably work with the back compatibility - moving any part of the configuration to quarkus's properties is probably not desired.
I can prepare a "relatively" clean solution, which will allow most of the functionality as is now. We can then discuss over it, whether it is suitable.

Requirement is now superfluous since https://github.com/apache/camel-quarkus/commit/858727e46d6930aefafe302d35d339e7f73e6de6.


Send email after queue processing is complete

Processing the drafts needs to send email notification after the job is complete ~ either successful or error


Bot bob

@alanmarkoTrilitech it looks like this PR has re-introduced a bug that we solved near the beginning of this process:


Remove inlineBlameColor

As I wanted to change the color for the inline blame text, I was trying to use the supplied setting inlineBlameColor in the README, but after digging into the PR, I found out that it was removed to use a more standardized way which is the editorCodeLens.foreground setting inside the workbench.colorCustomizations object.
So, I opened this PR to remove the misleading setting from the README.

Hey RAZINJ! Thank you for the PR.
I'm sorry that the documentation was incorrect. I am very grateful you took the initiative to fix it.

A new version is being pushed.

Awesome, glad to help!


Write release script for Linux

We write a manual release script so that we can package for Linux on releases. We do not automate to allow for easier debugging at the moment.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 0.531%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4

Relevant Lines:
753

💛  - Coveralls


Remove the Suspense boundary for individual items

As mentioned in https://github.com/vercel/next-rsc-demo/issues/13#issuecomment-988319153, we think removing the spinners for individual items will reduce layout shift and improve the overall experience of this app.

When I tried this locally I got weird hydration errors. Is that specific to me?

Not specific to you, that's something we are looking into — reverting to a previous Next.js release should fix it (#14).

📝 Changed routes:

/rsc.server

(view full size)

Commit ffa69f6f7c3e804d7e4448f66825796413e715a5 (https://next-rsc-demo-80bg8t89h.vercel.sh).

Should we also fix up the parent suspense boundary to be more natural than a spinner? For example by giving body min height and then making the fallback empty, or something.

Good call, min div height with some skeletons inside (that matches the item height) will be better.

Updated now, with animating skeletons: https://next-rsc-demo-git-shu-0653.vercel.sh/rsc. Should be good for now I think.

Can we make is to that the height of the skeleton is the same as the height of the content? Do we not know the number of the rows or the size of each?

❤

Sometimes when I refresh I get this:

But not every time.

When it's broken, I can see the scripts on the right are missing from the HTML:


⚠ Hartman Foundation has degraded performance

In 3460202, Hartman Foundation (https://gordonhartman.com/) experienced degraded performance:

HTTP code: 200
Response time: 2346 ms

Resolved: Hartman Foundation performance has improved in cf06f5c.


Tables without primary_key

Hi Guys,
I'm trying to use with a table without primary key but I can't.
Can I do this? I have a table without primary key and the table need be without.
Thanks.

Same requirement. The table is not inside my system, it is external DB with external system filling this DB, and I can't change it's DDL.


dx-box item template [shrink] does not work

To help us process the issue more efficiently, please provide the following information:

Specify the version of the devextreme-angular and devextreme packages you are using.
devexteme version: 17.2.4
devextreme-angular version: 17.2.4

Specify the type of the issue (check one with "x"):
[x ] bug Report
[ ] feature request
[ ] support inquiry

It's not clear to me how I can reproduce the issue on my side. Please provide me with a sample project that reproduces the issue.


Add pdnsim

This adds an analyze_power_grid facility to OpenROAD. External dependency on a voltage source location file and a default resistance configuration file for via resistance and per-unit R.

I noticed that the pdn sim references a standalone mode in the readme versus the integrated usage. I think it would be good to highlight the integrated usage. What others have done is to eliminate the standalone mode and in the readme point to the integrated version to reduce maintenance.

I just noticed the failure on bp_fe_top. this morning.
Error: field droute_viols fails rule 213.0 <= 193.0. I will look into it and update the documentation.

droute_viols is the field that @maliberty added to ensure that changes do not cause drastic regressions to the number of DRVs (as detected by TritonRoute).
Does PDNSim actually impact the QoR, or is it just an analysis engine? If it's the latter, that indicates that some other change on the branch is responsible.

why is this using a side file to read resistances when they are in the database?
that is not only a pain to maintain but anytime you copy data you are asking for inconsistencies


bower install does not work

Bower registry is under a new domain.
bower install does not work, at least for me till I added .bowerrc and set the registry to https://registry.bower.io

For Neuro, I ended up migrating over to yarn.  Bower was having an avalanche of issues for me. The whole story escapes me at the moment, but I feel like it was no longer going to be supported moving forward.

My issue was that my bower version was out of date and the registry URL needed changing. There was no need for this PR tbh. Make sure Bower is up to date and should work. At least it did for me


darwin.stdenv: remove openssl

Motivation for this change
Together with #21078 this will get rid of openssl and lzo in the darwin stdenv.
I'm testing a branch WIP with #21078, #21099 and #21101.
Things done

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

[ ] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

+bootstrap-python-2.7.12.drv
+bzip2-<IP_ADDRESS>.1.drv
-bzip2-<IP_ADDRESS>.1.drv
-clang-5.3.patch
+cmake-3.6.2.drv
-cmake-3.6.2.drv
-curl-7.51.0.drv
-curl-7.51.0.tar.bz2.drv
-db-5.3.28.drv
-db-5.3.28.tar.gz.drv
-e0ec3471cb09.drv
-gdbm-1.12.drv
-gdbm-1.12.drv
-gdbm-1.12.tar.gz.drv
-hook.drv
+libarchive-3.2.2.drv
-libarchive-3.2.2.drv
-libssh2-1.7.0.drv
-libssh2-1.7.0.tar.gz.drv
-libxml2-2.9.4.drv
-link-against-ncurses.patch
+lzo-2.09.drv
-lzo-2.09.drv
-no-arch_only-6.3.patch
-openssl-1.0.2j.drv
-openssl-1.0.2j.drv
-openssl-1.0.2j.tar.gz.drv
+pkg-config-0.29.drv
-pkg-config-0.29.drv
-properly-detect-curses.patch
-python-2.7-distutils-C++.patch
-python-2.7.12.drv
-python-2.7.12.drv
-readline-6.3.tar.gz.drv
-readline-6.3p08.drv
-readline-6.3p08.drv
-readline63-001.drv
-readline63-002.drv
-readline63-003.drv
-readline63-004.drv
-readline63-005.drv
-readline63-006.drv
-readline63-007.drv
-readline63-008.drv
-setup-hook.sh
-sqlite-3.15.0.drv
-sqlite-autoconf-3150000.tar.gz.drv
-use-etc-ssl-certs.patch

Can you elaborate on what your goal here? Is it to reduce closure size? If so, how much does it improve that situation?

The main thing I would like is to make diff with the linux stdenv smaller, the main things that I would like to get rid of are curl and openssl.

Ah okay!
On Mon, Dec 12, 2016 at 14:52 Daiderd Jordan<EMAIL_ADDRESS>wrote:

The main thing I would like is to make diff with the linux stdenv smaller,
the main things that I would like to get rid of are curl and openssl.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/21101#issuecomment-266533949, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAKP4tZDBBq954xLqStGhy-AoVeR5Ufks5rHaYCgaJpZM4LKpZr
.

I think the main thing that brings in a lot of stuff is cmake, I'm not sure why it uses --system-libs.

Probably because it's nice for us to not have a bunch of different versions
of things floating around. If we need to apply a patch or fix to OpenSSL,
people might be surprised that CMake isn't using them because it bundles
its own
On Mon, Dec 12, 2016 at 14:58 Daiderd Jordan<EMAIL_ADDRESS>wrote:

I think the main thing that brings in a lot of stuff is cmake, I'm not
sure why it uses --system-libs.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/21101#issuecomment-266535504, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAKP-k2NZU__n9BhCoPFyN3BqHanwAAks5rHadSgaJpZM4LKpZr
.

It doesn't pull in openssl directly, it's stuff like curl and libarchive.

Closing in favor of #21596


Yabai not fully working macOS Ventura 13.2.1

Since updating from macOS Monterey 12.6.3 to Ventura 13.2.1 Yabai doesn't seem to be fully working. I have tried a fresh install, re-disabling System Integrity Protection and re-enabled non-Apple-signed arm64e binaries, however the issue persists. Certain/basic functionality remains such as the bsp layout. However other settings such as window_shadow being off doesn't work.
I created an similar issue for skhd https://github.com/koekeishiya/skhd/issues/251#issue-1625310601

I posted my steps for fixing the issue here, still not entirely sure what fixed the issue: https://github.com/koekeishiya/skhd/issues/251#issuecomment-1471844866


Panic in go client when submission request fails / times out

Observing a panic in the go client when it errors out during file submission.
When using the v1.0.0 go client function SubmitSampleFile to submit a file, the following error is returned to the caller:
triage: Post "https://private.tria.ge/api/v0/samples": dial tcp <IP_ADDRESS>:443: i/o timeout

Then a panic occurs in sample.go:
Failed to submit file
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x666965]
goroutine 60344 [running]:
github.com/hatching/triage/go.(*Client).SubmitSampleFile.func1()
/go/pkg/mod/github.com/hatching/triage@v1.0.0/go/sample.go:108 +0xe5
created by github.com/hatching/triage/go.(*Client).SubmitSampleFile
/go/pkg/mod/github.com/hatching/triage@v1.0.0/go/sample.go:101 +0x3f2

The trace seems a bit confusing that it would fail on those lines (vs say in the defer or somewhere else).  So probably needs a bit more digging to see whats going on and how to recover cleanly.

Seeing another spate of these.  Based on the trace, I suspect its due to unchecked errors in the multipart calls, but I don't have a good way to consistently reproduce:
// samples.go
		jsonField, _ := mw.CreateFormField("_json")
		jsonField.Write(request) // jsonField can be nil

		fileField, _ := mw.CreateFormFile("file", filename)
		io.Copy(fileField, file) // fileField can be nil


docs: redis type annotations

The pr is just showing one commit:

But the branch has 2 commits:

I created a new pr https://github.com/jina-ai/jina-hub/pull/3537


Slow thumbnail generation on large documents

Hi,
Large documents (500+ pages) exhibit a significant delay if opened which is apparently caused by the thumb bar.
Any ideas how to improve this?

Hmm, interesting I don't think many of us have tested this on that large of a PDF! A good solution would be to lazy load the thumbnail images in the background instead of having to wait to load all of them to display the PDF. Thanks for the catch!

Same issue here. Loading a regular size magazine, (~120 pages) takes almost 7seconds.

@romanvolkov-io @Niphery Performance should be dramatically better in 2.1.6, please let me know if this fixes it!

@ranunez It's way better yes thank you for the reactivity 👍
However the thumbnail preview take some times to load the first time I open the PDF.
Not really an issue at the moment but I though i would let you know.

Yeah, I've already implemented something like that in a customer project recently. I also store generated thumbnails for caching purposes and regenerate them on demand.