text:
delay doesn't allow to use void in target

The effect in the target expects void, a conditional number arrives from doneData - a mismatch in delay types
example:
delay({
    source: someFirstFx.doneData,
    timeout: 1000,
    target: someSecondFx,
});

Could you add a reproduce in https://www.typescriptlang.org/play ?

@sergeysova check this

the second effect takes data from the store via attach

maybe in delay we need to be able to choose between source/clock?

Okay, I transformed your example into minimal reproduce:
import { delay } from 'patronum';
import { createEvent } from 'effector';

const input = createEvent<string>()
const output = createEvent<void>();

delay({
    source: input,
    timeout: 1000,
    target: output,
});

Try it

more complete example

You could solve it in userland. Something like this will work.
delay({
  source: sample({
    clock: input,
    fn: () => {},
  }),
  timeout: 1000,
  target: output,
});

authors: k0lyan mindyourlifeguide sergeysova

repo: effector/patronum


text:
Warning: React.findDOMNode is deprecated. Please use ReactDOM.findDOMNode from require('react-dom') instead.

Hi, I'm getting this warning here:
  updateSuggestionsPosition: function updateSuggestionsPosition() {
    if (!this.refs.caret || !this.refs.suggestions) return;

    var containerEl = this.refs.container;
    var caretEl = this.refs.caret;
    var suggestionsEl = React.findDOMNode(this.refs.suggestions); // <<<<<< Warning here.
    var highligherEl = this.refs.highlighter;
    if (!suggestionsEl) return;

    var leftPos = caretEl.offsetLeft - highligherEl.scrollLeft;
    // guard for mentions suggestions list clipped by right edge of window
    if (leftPos + suggestionsEl.offsetWidth > containerEl.offsetWidth) {
      suggestionsEl.style.right = "0px";
    } else {
      suggestionsEl.style.left = leftPos + "px";
    }
    suggestionsEl.style.top = caretEl.offsetTop - highligherEl.scrollTop + "px";
  },

Can potentially be fixed by using:
    var suggestionsEl = ReactDOM.findDOMNode(this.refs.suggestions);

Ack, this is probably my fault with https://github.com/effektif/react-mentions/pull/56 Should probably just list react-dom as a dependency instead of my PR.

My guess would be that we can find a way to update the style without figuring out the DOM node first. I would really like to leave react-dom out as a dependency because it ads a whopping 500kb to the build.

So ignore the warning for now, we leave this issue open and try to find a solution in the meantime.

@frontendphil any update on this issue? Does it make sense to add React-DOM as a dependency until a different solution is found?

As we need to support NPM 3 at some time, we probably need to depend on react and react-dom explicitly anyways. So probably we need to add those as a dependency. Only problem I see is with the combined build. There I really don't want to include the react and react-dom sources. I'm open for solutions on how to exclude them there.

I would vote for adding NPM 3 support, dropping Bower support, and no longer providing a combined build with version 0.3.

Hi @frontendphil, if you are using the combined build (that is my case btw) is probably safe to assume that you are including those dependencies on your own (and leaking them into the global scope like window.ReactDOM or global.ReactDOM).
Maybe you could just check for those globals.

@pzavolinsky is most likely correct, otherwise I'd agree with @jfschwarz and drop Bower support as NPM 3 is probably a more adequate solution moving forward anyway.

Any updates on this issue being resolved?

@pzavolinsky leaking into global/window space doesnt seem kosher
+1 @evankline question

@fremn :) true, although a combined build is all about leaking stuff into global/window.
In any case, I'm not suggesting leaking stuff but rather taking advantage of the fact that:

the only sensible usage of react-mentions's combined build is after react-dom's combined build.
the combined build for react-dom already leaks the missing dependency.

That is:
<script src="https://fb.me/react-dom-0.14.6.js"></script>
<script>
  // ReactDOM was leaked into window:
  ReactDOM.findDOMNode !== undefined
</script>
<script src="react-mentions-combined-build.js"></script>

The full-blown hack could be more or less:
var reactDOM = typeof global !== "undefined" && global.ReactDOM
  || typeof window !== "undefined" && window.ReactDOM
  || require('react-dom');

That being said, I do agree that this type of solution is somewhat post-apocalyptic and an alternative that removes the need for ReactDOM.findDOMNode would make the world a better place.

Running into this too.

var suggestionsEl = React.findDOMNode(this.refs.suggestions);

doenst this.refs.suggestions nowadays (react 0.14+) returns the dom element on it's own? According to the docs: https://facebook.github.io/react/docs/top-level-api.html#reactdom.finddomnode

In most cases, you can attach a ref to the DOM node and avoid using findDOMNode at all.

So can't we simply use var suggestionsEl = this.refs.suggestions;?

Any solution for this?

Fixed in v0.3.0

source: gharchive/issue

authors: coryvirok evankline fremn frontendphil jfschwarz johannesnagl pzavolinsky sisardor styks1987

repo: effektif/react-mentions

license_type: permissive

license_source: bigquery


text:
Docs

@Col-E wants us to have docs. I think, that's a good idea. We have three ways of doing it:

Just docs in code
Javadoc on github pages (we need to sync it with auto builds on CI)
Extra markdown docs

I like the second way. The only thing is, that this will make our code pasta-looking. As the "Clean Code" book tells, javadoc is not always good.
Any thoughts?

Doing them with java doc, they are hosted here.

repo: egordorichev/LastTry

license: mit


text:
Tools.jar Missing

LastTry-dev>gradlew clean build dist --stacktrace
Configuration on demand is an incubating feature.
:core:clean
:desktop:clean UP-TO-DATE
:core:compileJava FAILED
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':core:compileJava'.

Could not find tools.jar

Try:
Run with --info or --debug option to get more log output.

Exception is:

org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':core:compileJava'.
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:69)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:46)
        at org.gradle.api.internal.tasks.execution.PostExecutionAnalysisTaskExecuter.execute(PostExecutionAnalysisTaskExecuter.java:35)
        at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:64)
        at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)
        at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:52)
        at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)
        at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:53)
        at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
        at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:203)
        at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:185)
        at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.processTask(AbstractTaskPlanExecutor.java:66)
        at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.run(AbstractTaskPlanExecutor.java:50)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor.process(DefaultTaskPlanExecutor.java:25)
        at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter.execute(DefaultTaskGraphExecuter.java:110)
        at org.gradle.execution.SelectedTaskExecutionAction.execute(SelectedTaskExecutionAction.java:37)
        at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:37)
        at org.gradle.execution.DefaultBuildExecuter.access$000(DefaultBuildExecuter.java:23)
        at org.gradle.execution.DefaultBuildExecuter$1.proceed(DefaultBuildExecuter.java:43)
        at org.gradle.execution.DryRunBuildExecutionAction.execute(DryRunBuildExecutionAction.java:32)
        at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:37)
        at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:30)
        at org.gradle.initialization.DefaultGradleLauncher$4.run(DefaultGradleLauncher.java:154)
        at org.gradle.internal.Factories$1.create(Factories.java:22)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:52)
        at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:151)
        at org.gradle.initialization.DefaultGradleLauncher.access$200(DefaultGradleLauncher.java:32)
        at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:99)
        at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:93)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:62)
        at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:93)
        at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:82)
        at org.gradle.launcher.exec.InProcessBuildActionExecuter$DefaultBuildController.run(InProcessBuildActionExecuter.java:94)
        at org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28)
        at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
        at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:43)
        at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:28)
        at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:78)
        at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:48)
        at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:52)
        at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
        at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:37)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
        at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:26)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
        at org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute(RequestStopIfSingleUsedDaemon.java:34)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
        at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:74)
        at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:72)
        at org.gradle.util.Swapper.swap(Swapper.java:38)
        at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:72)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
        at org.gradle.launcher.daemon.server.health.DaemonHealthTracker.execute(DaemonHealthTracker.java:47)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
        at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:66)
        at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
        at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:72)
        at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
        at org.gradle.launcher.daemon.server.health.HintGCAfterBuild.execute(HintGCAfterBuild.java:41)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
        at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:50)
        at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:246)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
        at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
Caused by: java.lang.IllegalStateException: Could not find tools.jar
        at org.gradle.internal.jvm.JdkTools.<init>(JdkTools.java:57)
        at org.gradle.internal.jvm.JdkTools.current(JdkTools.java:44)
        at org.gradle.api.internal.tasks.compile.JavaHomeBasedJavaCompilerFactory$SystemJavaCompilerFactory.create(JavaHomeBasedJavaCompilerFactory.java:77)
        at org.gradle.api.internal.tasks.compile.JavaHomeBasedJavaCompilerFactory$SystemJavaCompilerFactory.create(JavaHomeBasedJavaCompilerFactory.java:75)
        at org.gradle.api.internal.tasks.compile.JavaHomeBasedJavaCompilerFactory.findCompiler(JavaHomeBasedJavaCompilerFactory.java:57)
        at org.gradle.api.internal.tasks.compile.JavaHomeBasedJavaCompilerFactory.create(JavaHomeBasedJavaCompilerFactory.java:44)
        at org.gradle.api.internal.tasks.compile.JavaHomeBasedJavaCompilerFactory.create(JavaHomeBasedJavaCompilerFactory.java:28)
        at org.gradle.api.internal.tasks.compile.JdkJavaCompiler.createCompileTask(JdkJavaCompiler.java:55)
        at org.gradle.api.internal.tasks.compile.JdkJavaCompiler.execute(JdkJavaCompiler.java:44)
        at org.gradle.api.internal.tasks.compile.JdkJavaCompiler.execute(JdkJavaCompiler.java:33)
        at org.gradle.api.internal.tasks.compile.NormalizingJavaCompiler.delegateAndHandleErrors(NormalizingJavaCompiler.java:101)
        at org.gradle.api.internal.tasks.compile.NormalizingJavaCompiler.execute(NormalizingJavaCompiler.java:50)
        at org.gradle.api.internal.tasks.compile.NormalizingJavaCompiler.execute(NormalizingJavaCompiler.java:36)
        at org.gradle.api.internal.tasks.compile.CleaningJavaCompilerSupport.execute(CleaningJavaCompilerSupport.java:34)
        at org.gradle.api.internal.tasks.compile.CleaningJavaCompilerSupport.execute(CleaningJavaCompilerSupport.java:25)
        at org.gradle.api.tasks.compile.JavaCompile.performCompilation(JavaCompile.java:157)
        at org.gradle.api.tasks.compile.JavaCompile.compile(JavaCompile.java:139)
        at org.gradle.api.tasks.compile.JavaCompile.compile(JavaCompile.java:93)
        at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:75)
        at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$IncrementalTaskAction.doExecute(AnnotationProcessingTaskFactory.java:244)
        at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:220)
        at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$IncrementalTaskAction.execute(AnnotationProcessingTaskFactory.java:231)
        at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:209)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61)
        ... 68 more

BUILD FAILED
Total time: 1.08 secs

Hm, thanks for bug report! Something is wrong with gradle. Can you post more info, please? (uname -a and gradle info, also, java version would be useful).
Thanks!

Updated your post so the exception is more legible.

Updated JDK worked.

Glad, that it worked. So here is a few options, you can play around:

Launch app with -nl arg, to disable light and load game faster
Launch app with -d arg, witch enables debug mode. In it you can press / and open dev console.

Give your self some items, using console. You just simply type in console: /give lt:dirt 100. lt:dirt is dirt block id and 100 is count. Full list of items can be found here: https://github.com/egordorichev/LastTry/blob/dev/core/assets/data/items.json

Thanks! I'll have some fun then after work.
Minor thing: It seems to crash without notice after about 30 seconds of gameplay.

Hm, could you please, paste the log here? It goes into console. We just found some issues with Windows saves/home dirs. Will be fixed today.

authors: Col-E egordorichev kenten132


text:
QR code in vaccination certificate for 1st dose was scanned in QR scanner and it displayed the details. But it is not the case for certificate for 2nd dose. I tried to scan the QR code of 2nd dose certificate; but in vain.  Both the certificates are downloaded from COWIN app. Pl rectify the defect.

Describe the bug
Please do not enter any personal information, for COWIN / registration / certificate related issues login to https://www.cowin.gov.in/home and report issue
A clear and concise description of what the bug is (only DIVOC api / module).
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

@ansvprasad we tested the certificate once more and its able to verify both 1st and 2nd dose certificates. Can you share your pre-enrollment code here, that will help for debugging. (tejash.jl1020@gmail.com)

authors: ansvprasad tejash-jl

repo: egovernments/DIVOC

license: MIT

license_source: github-api


text:
Closes #1346: assertion on paths made generic to work on windows

Some unit test path issues fixed for windows.

test this please

source: gharchive/pull-request


text:
Improve support for Java 9+

This is a PoC for Java 9+ (up to current Java 18) support. We don't have to use the ByteBuddy agent implementation verbatim, but it proves that things can be made to work.

Can we reopen https://github.com/ehcache/sizeof/pull/65 and merge it for 0.4.1 release? It's much simpler than this PR so I think can be merged easier than this.

@chrisdennis do you see a chance, to get this merged and to solve the java-9+ problems? questioning, if ehcache is still using this library and - if not - what else?

authors: barclay-reg chrisdennis stiga-huang

repo: ehcache/sizeof


text:
No module named dateutil (pip 0.1.14, Server 2019)

pip install 0.1.14, server 2019, unable to run tesla_dashcam without this error:

Had to install python-dateutil to resolve:
pip install python-dateutil

Thank you. Missed adding that package to setup file.
Just released 0.1.15 with fix.


text:
unable to run the code

Can you please share the setup instructions getting below error
"pytesseract.pytesseract.TesseractError: (1, 'Error opening data file C:\Users\Ankur.Biswal\AppData\Local\Tesseract-OCR\tessdata/tessdata/eng.traineddata Please make sure the TESSDATA_PREFIX environment variable is set to the parent directory of your "tessdata" directory. Failed loading language 'eng' Tesseract couldn't load any languages! Could not initialize tesseract.')"

This looks like an error that is specific to your environment and related to Tesseract, not this image-table-ocr library. I can't really provide any more help than the error message. Does that eng.traineddata file exist? Is TESSDATA_PREFIX set to the parent directory? If you have confirmed both of those facts, it could be an issue with file permissions.

authors: AnkurAlankarBiswal eihli

repo: eihli/image-table-ocr


text:
🛑 API is down

In b052ca6, API (https://api.either.digital/status) was down:

HTTP code: 523
Response time: 15703 ms

Resolved: API is back up in 5f67a3f.

repo: eitherdigital/status-page


text:
Create Posts “apples”

Automatically generated by Netlify CMS

👷 Deploy Preview for eloquent-chandrasekhar-302983 processing.
🔨 Explore the source changes: 809c92efc4df74f4fc1e2bebdaadfa075a468cf4
🔍 Inspect the deploy log: https://app.netlify.com/sites/eloquent-chandrasekhar-302983/deploys/61ad4d32d2a9e20008e24211


text:
Indicate issue status (open/closed) with icon color

The /notifications list on GH colors the issue and PR icons according to their status, which I find really useful for deciding which issues to jump to / read first.

Hi @anandthakker! Unfortunately the payload from the GitHub API does not give any information regarding the state of PRs and Issues. It would be really useful to have but our hands are tight.
I would be more than happy to implement such functionality if the API gets updated at some point.

Ah -- totally understandable.  Thanks for the super handy tool!
On Mon, Jun 1, 2015 at 2:13 PM Emmanouil Konstantinidis <
notifications@github.com> wrote:

Closed #45 https://github.com/ekonstantinidis/gitify/issues/45.
—
Reply to this email directly or view it on GitHub
https://github.com/ekonstantinidis/gitify/issues/45#event-319220247.

authors: anandthakker ekonstantinidis

repo: ekonstantinidis/gitify


text:
[feat] blueprint config generation

see https://github.com/rebuy-de/aws-nuke/pull/507

that would be really nice 👍

authors: ekristen mgnisia

repo: ekristen/aws-nuke


text:
Restructure application

Restructure using this methodology. https://medium.com/node-js-javascript/working-without-frameworks-part-1-b948f281f782

https://github.com/ekristen/docker-index/tree/restructure

repo: ekristen/docker-index


text:
refactor to typescript

Are there any plans to migrate to TS?  Would help boost the DX for initial use.

Hi @jamesholcomb,
No plans, but PRs are welcome! 👍

@jamesholcomb you can use this library which from version 2.0.0 is in typescript.
https://gitlab.com/kenble/fcm-http2

Hi @fctaddia,
Thanks for your work converting my project to TypeScript!
Would be nice to receive some credit in your repository's README...

Hi, sorry but the library is new and I hadn't finished writing the README yet. However I mentioned it in the "Contributions" section of my README. If you want to participate in library improvements in typescript you are welcome. Thanks and sorry again if I didn't mention you before

I have implemented similar functionalities using TypeScript. If you're interested, you can check out how I approached it in my project. For more details, you can refer to the NPM package I used. It's been quite effective for managing Firebase Cloud Messaging in my TypeScript applications.

Hi @jeevan-blaze,
Thanks for your work converting my project to TypeScript!
Would be nice to receive some credit in your repository's README, though!

authors: eladnava fctaddia jamesholcomb jeevan-blaze


text:
fix: ignore unstash coverage errors

What does this pull request do?

It adds a couple of catchError steps to avoid failure when the stash does not exist
Related issues
closes https://github.com/elastic/apm-agent-python/issues/913

:green_heart: Build Succeeded

Expand to view the summary

Build stats

Build Cause: [Pull request #914 opened]

Start Time: 2020-09-02T11:13:03.976+0000

Duration: 28 min 2 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
10927

Skipped
8506

Total
19433

Steps errors
Expand to view the steps failures

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-2.7 django-1.11

Duration: 4 min 46 sec

Start Time: 2020-09-02T11:19:00.617+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-2 none

Duration: 3 min 2 sec

Start Time: 2020-09-02T11:19:14.679+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-3 none

Duration: 3 min 12 sec

Start Time: 2020-09-02T11:19:05.667+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-3 mysqlclient-newest

Duration: 1 min 11 sec

Start Time: 2020-09-02T11:31:07.021+0000

log

authors: apmmachine kuisathaverat

repo: elastic/apm-agent-python


text:
if nodeIp has '/' and the form /, just return .

If I run the mr job which reads data from ES and writes parquet files on HDFS, I got the following errors:
...
java.lang.IllegalArgumentException: Network location name contains /: my-host01/10.xxx.xxx.xxx
at org.apache.hadoop.net.NodeBase.set(NodeBase.java:87)
at org.apache.hadoop.net.NodeBase.(NodeBase.java:65)
at org.apache.hadoop.yarn.util.RackResolver.coreResolve(RackResolver.java:111)
at org.apache.hadoop.yarn.util.RackResolver.resolve(RackResolver.java:95)
...
I noticed that nodeIp from PartitionDefinition has such form like /.
After removing slash and ip part of nodeIp, and just returning hostname, my mr job works fine.
I am not sure if it happened to my case.

This has been fixed in master through 98ab1527f05930fbe99d691d3ecd33d0d7225087. Further more in case of a host/ip, using the IP is preferred.
Thanks for raising the PR!

authors: costin mykidong

repo: elastic/elasticsearch-hadoop


text:
no point to get FD usage if we are not root which will trigger and fl…

No point to get FD usage if we are not "root" , this will trigger audit if DISA_STIG has been applied
DISA_STIG V-72127 - All users of the openat command must be audited
On busy systems this will flood audit daemon specially if its continuously running (e.g. metricbeat) without root permission which on safety critical system applications will run with non-root privileges
E.g. audit rules:
-a always,exit -F arch=b32 -S creat -S open -S openat -S truncate -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
-a always,exit -F arch=b32 -S creat -S open -S openat -S truncate -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access
-a always,exit -F arch=b64 -S creat -S open -S openat -S truncate -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access
-a always,exit -F arch=b64 -S creat -S open -S openat -S truncate -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access

:grey_exclamation: Build Aborted

The PR is not allowed to run in the CI yet

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Reason: The PR is not allowed to run in the CI yet

Start Time: 2021-11-13T10:23:37.842+0000

Duration: 3 min 46 sec

Commit: d8cbb7c0ad18e51ec6a3876c7e1cb487b3c7de3a

authors: elasticmachine navid-yaghoobi

repo: elastic/gosigar


text:
.golangci.yml - Removed deprecated linters and unused depguard

Remove deprecated linters:
WARN [runner] The linter 'ifshort' is deprecated (since v1.48.0) due to: The repository of the linter has been deprecated by the owner.
WARN [runner] The linter 'deadcode' is deprecated (since v1.49.0) due to: The owner seems to have abandoned the linter. Replaced by unused.
WARN [runner] The linter 'structcheck' is deprecated (since v1.49.0) due to: The owner seems to have abandoned the linter. Replaced by unused.
WARN [runner] The linter 'varcheck' is deprecated (since v1.49.0) due to: The owner seems to have abandoned the linter. Replaced by unused.

Remove depguard. The linter was not configured with any rules so it blocks all imports.

:green_heart: Build Succeeded

Buildkite Build
Commit: c558b9b249d760ceaee4c3d688fa6c7551b9cfc2

authors: andrewkroh elasticmachine

repo: elastic/stream


text:
why copyHeaders remove dst header key-values first?

func copyHeaders(dst, src http.Header) {
	for k, _ := range dst {
		dst.Del(k)
	}
	for k, vs := range src {
		for _, v := range vs {
			dst.Add(k, v)
		}
	}
}

I write cookie to response in middleware, but goproxy will remove response headers. What should I do?.

because one header could have multiple values.
Just calling Add would keep the previous value, and add another value to
the header.
On Tue, Nov 21, 2017 at 6:23 AM, luwei notifications@github.com wrote:

func copyHeaders(dst, src http.Header) {
for k, _ := range dst {
dst.Del(k)
}
for k, vs := range src {
for _, v := range vs {
dst.Add(k, v)
}
}
}
I write cookie to response in middleware, but goproxy will remove response
harders
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/elazarl/goproxy/issues/259, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAP4os6f1BtEKRFJcTttR4A-XhLchLsqks5s4lAogaJpZM4QlQ8y
.

authors: elazarl luweimy

repo: elazarl/goproxy


text:
Apple Rejection

Our app got rejected by Apple "Guideline 4 - Design". 🤦

We'll probably go change the width using style: AuthButtonStyle(...but perhaps it would make sense to have static size for all buttons.
Thanks for the library!

considering that I'm in the preparation stages for my first Flutter app, I couldn't resist digging into this one a little bit..
the Apple HIG was last updated on 11th January 2022, however this package's 2.0.3 release (current latest) is from 16th December 2021.
there are a number of changes that I suspect may be causing trouble here, but I think the first point listed might be the most notable difference:

Text now uses SF Pro instead of SF Pro Text and SF Pro Display

meanwhile, this package is currently set to use Source Sans Pro for AppleAuthButton.
I just created a new Flutter project to test, and the "Sign in with Apple" buttons do have a very different font face and icon margin size. I haven't gone pixel bashing for differences (yet...?) though, so there may be more to it.

Thanks @ZaLiTHkA. I hope it's just the width. I'm going to submit this and see what happens.:

Will report back. But I guess it's up to the reviewer...

Hi there, I think probably that the issue is related to the width, if so I'll give all buttons the same width.

@hermuxo
Hhmmm I don't know if only me see that Google button is a little smaller than the others.

@hermuxo Hhmmm I don't know if only me see that Google button is a little smaller than the others.

Thanks updated. Also good to remember textScaleFactor

Got accepted by Apple. Closing.

authors: ZaLiTHkA elbeicktalat hermuxo


text:
Getting and setting Cookies

Hey, I just started using C# and I was looking into this PCL. I got it working after looking at examples and everything. I was wondering if it was possible to get the Cookies from the connection and using storing and sending those Cookies when a new connection is made.
If that can be done, could you please post an example? Thanks for this lib. anyways :)

By default, HttpClient disposes it's handler after the first use, even if you make multiple requests. You can make use of the InnerHandler property of the ClearanceHandler, set this to be an HttpClientHandler which you can define to store cookies, and then set up the HttpClient to not dispose the handler. Something like this should work:
var cookieContainer = new CookieContainer();
using (var cfHandler = new ClearanceHandler()) {
    cfHandler.InnerHandler = new HttpClientHandler() {
        UseCookies = true,
        CookieContainer = cookieContainer
    };
    using (var client = new HttpClient(cfHandler, false)) {
        // do stuff here..
    }
}

Sorry, but I didn't get the code. Care to explain a little?
I wanted to connect to a site and grab all the cookies that the website makes for this particular connection and then pass these cookies to another instance of the client to use those cookies and connect to that website. How should I approach this in c#?
I've been writing in Python and it being Python, it was pretty easy. This is still confusing for me.

Here is another example:
// Shared CookieContainer, that will contain all cookies
var cookies = new CookieContainer();

// First client instance
var client1 = new HttpClient(new ClearanceHandler(new HttpClientHandler
{
    UseCookies = true,
    CookieContainer = cookies // setting the shared CookieContainer
}));

client1.GetStringAsync("http://target.site");

// Second client instance
var client2 = new HttpClient(new ClearanceHandler(new HttpClientHandler
{
    UseCookies = true,
    CookieContainer = cookies // setting the shared CookieContainer
}));

client2.GetStringAsync("http://target.site");

Thanks :+1:

authors: Xonshiz elcattivo kade-robertson

repo: elcattivo/CloudFlareUtilities


text:
chore (sync service): remove redundant spans

Part of https://github.com/electric-sql/electric/issues/2032.
I removed 2 spans that seem redundant:

shape_write.log_collector.handle_txn: this span wraps the handle_transaction function. However, there is already a span pg_txn.replication_client.transaction_received that in fact calls into handle_transaction.
shape_write.log_collector.handle_relation: this span wraps the handling of relation messages. Similarly to transactions, there is a pg_txn.replication_client.relation_received span that ends up calling into the handle_relation function.

Here are the relevant code snippets:
Electric.Postgres.ReplicationClient:
{m, f, args} = state.transaction_received

OpenTelemetry.with_span(
  "pg_txn.replication_client.transaction_received",
  [num_changes: length(txn.changes), num_relations: MapSet.size(txn.affected_relations)],
  fn -> apply(m, f, [txn | args]) end
)

The call to apply is a chain of calls that eventually ends up calling handle_transaction (and does nothing more):
Electric.StackSupervisor:
transaction_received: {Electric.Replication.ShapeLogCollector, :store_transaction, [shape_log_collector]}

Electric.Replication.ShapeLogCollector.ex:
def store_transaction(%Transaction{} = txn, server) do
  ot_span_ctx = OpenTelemetry.get_current_context()
  GenStage.call(server, {:new_txn, txn, ot_span_ctx}, :infinity)
end

def handle_call({:new_txn, %Transaction{xid: xid, lsn: lsn} = txn, ot_span_ctx}, from, state) do
  OpenTelemetry.set_current_context(ot_span_ctx)
  Logger.info("Received transaction #{xid} from Postgres at #{lsn}")
  Logger.debug(fn -> "Txn received in ShapeLogCollector: #{inspect(txn)}" end)

  OpenTelemetry.with_span("shape_write.log_collector.handle_txn", [], fn ->
    handle_transaction(txn, from, state)
  end)
end

Question
I removed the spans from Electric.Replication.ShapeLogCollector, another option would be to remove the spans from Electric.Postgres.ReplicationClient, any preference here?

I wouldn't call those spans redundant because they cover code executed in different processes.
My original idea with these was to have a way to tell if there's any significant delay between receiving a transaction in the replication client process and storing it in shape log collectors. Given our architecture of running a separate log collector for each shape, a single transaction may be stored N times and the time profile of that could like like N parallel child spans or a waterfall of N spans. What I mean is that looking at a trace could lend us insights into potential inefficiencies in the transaction processing architecture.
I haven't spent much time testing this, though. If removing those spans still maintains a hierarchical relation between the root pg_txn.replication_client.transaction_received span and the leaf shape_write.consumer.handle_txns spans started in each shape consumer, then it's fine to remove this intermediate shape_write.log_collector.handle_txn span.

Nevermind my above comment. I've double-checked that the shape_write.consumer.handle_txns span doesn't have a hierarchical relation with the pg_txn.replication_client.transaction_received span. So removing the two intermediate spans here doesn't make anything worse in terms of observability for us.

My original idea with these was to have a way to tell if there's any significant delay between receiving a transaction in the replication client process and storing it in shape log collectors.

I think it's important to not lose visibility about scheduling delays, but would we be able to track the time without adding the span?

Could we update metrics of p.50, .p99 latency on the parent span? e.g. update the attributes latency attributes in transaction_received when the child process starts

For context, it's almost half of the spans if we handle the top two.

My original idea with these was to have a way to tell if there's any significant delay between receiving a transaction in the replication client process and storing it in shape log collectors.

I think it's important to not lose visibility about scheduling delays, but would we be able to track the time without adding the span? For example, could we update metrics of p.50, .p99 latency on the parent span? i.e. update the latency attributes in transaction_received when the child process starts.
For context, it's almost half of the spans if we handle the top two.

@balegas
This PR removes redundant spans. Don't think we have to bubble up anything here.
I guess your comment was meant for https://github.com/electric-sql/electric/pull/2054 ?

This PR removes redundant spans. Don't think we have to bubble up anything here.
I guess your comment was meant for https://github.com/electric-sql/electric/pull/2054

I don't think #2054 does what I'm asking, but you can clear it out to me. In #2054 you're defining a sampling strategy for root spans, which will apply for descendant spans. Which means that if we sample process_x_log_data we also sample decode_message, which is still double of the spans we need.
I think decode_message time should always coalesced into parents span

This PR removes redundant spans. Don't think we have to bubble up anything here.
I guess your comment was meant for #2054

I don't think #2054 does what I'm asking, but you can clear it out to me. In #2054 you're defining a sampling strategy for root spans, which will apply for descendant spans. Which means that if we sample process_x_log_data we also sample decode_message, which is still double of the spans we need.
I think decode_message time should always coalesced into parents span

Sure, we can do that in a separate PR

authors: alco balegas kevin-dp

repo: electric-sql/electric


text:
macOS Store Crash: Entitlements as Binary Plist instead of Plist

MAS-signed App crashes which results in the apps rejection by Apple.
After a few hours of investigation I figured out that there is an issue with the entitlements of the App. In the Console Application the following message is thrown.
failed to parse entitlements for MyApp[84767]: OSUnserializeXML: syntax error near line 1
I then enabled DEBUG=electron-osx-sign* which allowed me to see that the entitlements of the app were in binary plist format, not in plist format. The entitlements are provided as a valide plist, but codesign somehow "converts" it to the binary format.
In fact the current version available in the AppStore has the entitlements provided as plist, not as binary plist.
Any input on this odd behaviour?

I also opened an TSI at Apple. My guess is, that there was a change in Apples codesign tool.

Apple hasn't responded to the TSI yet:/

Am I the only one that experience this issue?

I had this problem too: Resigning the app with codesign introduced a binary diff in the first XML line of the entitlements. I could reproduce this in every run of codesign, even when resigning with the exact same entitlements.
The problem finally disappeared after rebooting (!) the OS-X machine. Believe it or not. This is not a real solution for sure. Nevertheless, anyone struggling with this problem might want to try this.

I found this because I am also experiencing a similar error related to entitlements parsing:
  ⨯ Command failed: codesign --sign XXXX --force --timestamp --entitlements build/entitlements.mas.inherit.plist /path/to/project/dist/mas/MyAppName.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libEGL.dylib
Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 6

I was able to find a solution. In case anyone comes across this, I will share what worked for me.
I ran the following scripts on my plist files:
plutil -convert xml1 build/entitlements.mas.plist
plutil -convert xml1 build/entitlements.mas.loginhelper.plist
plutil -convert xml1 build/entitlements.mas.inherit.plist

This modified each of my plist files to change whitespace characters. It looks like spaces have been converted to tabs, so perhaps some kind of auto-formatting ran in my editor to reformat the Plist files incorrectly. Running putil -convert xml1 on them seems to fix it. Code signing is now passing for me.
Example diff:
diff --git a/build/entitlements.mas.inherit.plist b/build/entitlements.mas.inherit.plist
index 57d0b41..4759d0a 100644
--- a/build/entitlements.mas.inherit.plist
+++ b/build/entitlements.mas.inherit.plist
@@ -1,14 +1,14 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
 <plist version="1.0">
-  <dict>
-    <key>com.apple.security.app-sandbox</key>
-    <true />
-    <key>com.apple.security.inherit</key>
-    <true />
-    <key>com.apple.security.cs.allow-jit</key>
-    <true />
-    <key>com.apple.security.cs.allow-unsigned-executable-memory</key>
-    <true />
-  </dict>
+<dict>
+       <key>com.apple.security.app-sandbox</key>
+       <true/>
+       <key>com.apple.security.cs.allow-jit</key>
+       <true/>
+       <key>com.apple.security.cs.allow-unsigned-executable-memory</key>
+       <true/>
+       <key>com.apple.security.inherit</key>
+       <true/>
+</dict>
 </plist>

Strugled with this issue today. IMO should be in docs.

Sounds like this is malformed user plist files, not sure how they become malformed but it's not an issue with osx-sign specifically

I've identified that when I open the file entitlements.mac.inherit.plist with vscode, and save it (tested on mac), the bug appears.
Solution  ?
Maybe there is an option in vscode about formatting the file... I don't know.
Submit an issue to vscode ?

authors: MarshallOfSound copperschnack idoodler rachonzedev t-mish tinacious

repo: electron/electron-osx-sign


text:
Inferring author for win32 targets does not give a good error when it's not found

Preflight Checklist

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Issue Details

Electron Packager Version: 14.1.1 and above
Electron Version: 8.2.2
Operating System: Windows 10 (Version 1909)
Last Known Working Electron Packager version:: 14.1.0

Expected Behavior
# npm run build
Packaging app for platform win32 x64 using electron v8.2.2
Packaging app for platform linux x64 using electron v8.2.2
Packaging app for platform darwin x64 using electron v8.2.2
Wrote new apps to:
..\build\atomic-tweetdeck-win32-x64
..\build\atomic-tweetdeck-linux-x64
..\build\atomic-tweetdeck-darwin-x64

Actual Behavior
# npm run build
  electron-packager Electron Packager 14.1.1
  electron-packager Node v12.16.2
  electron-packager Host Operating system: win32 10.0.18363 (x64) +0ms
  electron-packager Packager Options: {"_":[".","atomic-tweetdeck"],"platform":"win32,linux,darwin","arch":"x64","electron-version":"8.2.2","electronVersion":"8.2.2","tmpdir":false,"out":"../build","app-version":"0.13.0","appVersion":"0.13.0","version-string":{"FileDescription":"Atomic TweetDeck","ProductName":"Atomic TweetDeck"},"versionString":{"fileDescription":"Atomic TweetDeck","productName":"Atomic TweetDeck"},"icon":"favicon.ico","overwrite":true,"deref-symlinks":true,"derefSymlinks":true,"download":{"rejectUnauthorized":true,"reject-unauthorized":true},"junk":true,"prune":true,"dir":".","name":"atomic-tweetdeck","protocols":[]} +2ms
  electron-packager Target Platforms: win32, linux, darwin +6ms
  electron-packager Target Architectures: x64 +2ms
  electron-packager Unable to find all properties in parent package.json files. Missing props: "author" +0ms
Could not locate a package.json file in "d:\Projects\Public\atomic-tweetdeck\master" or its parent directories for an Electron app.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! atomic-tweetdeck@0.13.0 build: `build.bat build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the atomic-tweetdeck@0.13.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\dogan\AppData\Roaming\npm-cache\_logs\2020-04-24T03_24_11_127Z-debug.log

To Reproduce
Clone atomic-tweetdeck, remove author from package.json (currently there is none) and run npm run build or the following raw command (no NPM required):
electron-packager ./ atomic-tweetdeck --platform=win32,linux,darwin --arch=x64 --electron-version=8.2.2 --no-tmpdir --out=../build --app-version="0.13.0" --version-string.FileDescription="Atomic TweetDeck" --version-string.ProductName="Atomic TweetDeck" --icon=favicon.ico --overwrite

Additional Information
It tells you it can't find package.json and doesn't tell you why unless you set DEBUG=electron-packager. The reason it fails is because my package.json doesn't have an author. Build doesn't fail if I add an author.
If author is required, it should tell you without having to use DEBUG. Author should be optional.

Is it possible to make author optional? @malept

If it's not specified, the author stays "GitHub, Inc." which is inaccurate.

authors: dogancelik malept

repo: electron/electron-packager


text:
Error: Failed to staple your application with code: 66. Cannot download ticket. CDHash must be set.

I'm facing the error below when building and signing the application.
$ electron-forge make
✔ Checking your system
✔ Loading configuration
✔ Resolving make targets
  › Making for the following targets: zip, dmg, pkg
❯ Running package command
  ✔ Preparing to package application
✔ Loading configuration
✔ Resolving make targets
  › Making for the following targets: zip, dmg, pkg
❯ Running package command
  ✔ Preparing to package application
  ✔ Running packaging hooks
    ✔ Running generateAssets hook
    ✔ Running prePackage hook
      ✔ [plugin-webpack] Preparing native dependencies
      ✔ [plugin-webpack] Building webpack bundles
  ❯ Packaging application
    ❯ Packaging for x64 on darwin
      ✔ Copying files
      ✔ Preparing native dependencies [0.3s]
      ✖ Finalizing package
        › Failed to staple your application with code: 66
          Processing: /private/var/folders/64/73k0p2zd5nl8_mybklz01k640000gp/T/electron-packager/darwin-x64/Project/Project.app
          Properties are {
          NSURLIsDirectoryKey = 1;
          NSURLIsPackageKey = 1;
          NSURLIsSymbolicLinkKey = 0;
          NSURLLocalizedTypeDescriptionKey = Application;
          NSURLTypeIdentifierKey = "com.apple.application-bundle";
          "_NSURLIsApplicationKey" = 1;
          }
          Props are {
          }
          Cannot download ticket. CDHash must be set.
  ◼ Running postPackage hook
◼ Running preMake hook
◼ Making distributables
◼ Running postMake hook

An unhandled rejection has occurred inside Forge:
Error: Failed to staple your application with code: 66

Processing: /private/var/folders/64/73k0p2zd5nl8_mybklz01k640000gp/T/electron-packager/darwin-x64/Project/Project.app
Properties are {
    NSURLIsDirectoryKey = 1;
    NSURLIsPackageKey = 1;
    NSURLIsSymbolicLinkKey = 0;
    NSURLLocalizedTypeDescriptionKey = Application;
    NSURLTypeIdentifierKey = "com.apple.application-bundle";
    "_NSURLIsApplicationKey" = 1;
}
Props are {
}
Cannot download ticket. CDHash must be set.
at Object.<anonymous> (/project_path/node_modules/@electron/notarize/lib/staple.js:22:19)
    at Generator.next (<anonymous>)
    at fulfilled (/project_path/node_modules/@electron/notarize/lib/staple.js:4:58)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

My packagerConfig value in forge.config.js looks like this.
packagerConfig: {
  ...,
  osxSign: {
      "identity": "Developer ID Application: Name Name (code)"
    },
    osxNotarize: {
      tool: 'notarytool',
      appleId: process.env.APPLE_ID,
      appleIdPassword: process.env.APPLE_PASSWORD,
      teamId: process.env.APPLE_TEAM_ID,
    },
  ...
}

It looks like there's nothing missing from the configuration, my guess is that it could be related to certification/provisioning profile.

I ran in to this issue as well and it turned out that I wasn't correctly specifying my certificate. You may want to try running
security find-identity -p codesigning -v
to see which certificates you have installed on your development machine, and if there's more than one, be sure you're providing the details for the correct identity.
If that's all looking fine, you may want to check to see if you've specified your entitlements. That would looks something like this:
     osxSign: {
      identity: "Developer ID Application: xxx (xxx)",
      hardenedRuntime : true,
      gatekeeperAssess: false,
      entitlements: "build/entitlements.mac.plist",
      entitlementsInherit: "build/entitlements.mac.plist",
    },

and your entitlements.mac.plist file at minimum will probably contain something like this:

com.apple.security.cs.allow-unsigned-executable-memory

com.apple.security.cs.allow-jit

Some additional helpful resources:
https://til.simonwillison.net/electron/sign-notarize-electron-macos
https://kilianvalkhof.com/2019/electron/notarizing-your-electron-application/

@bihellzin hi, I ran the security find-identity -p codesigning -v command, my certificate does not appear in the list, but when opening Keychain Access it is in Login/Certificate. In My Certificate it is not there, is the reason here?

The issue was really related to the certificates, not the notarize itself. I'm closing the issue.

Hi, I'm facing the same issue. Have you found the solution? Thanks!

authors: bihellzin hysasuke tinhnvc-gadget wdzierson

repo: electron/notarize


text:
0.4.1

@phated

Thanks!

authors: YanagiEiichi phated

repo: eleme/thrift-parser


text:
Jan2023 PR

PR description
Fixed Issue(s)

Documentation

[ ] I thought about documentation and added the doc-change-required label to this PR if
updates are required.

Changelog

[ ] I thought about the changelog and included a changelog update if required.

Okay

repo: elenduuche/besu


text:
ROS 2 Support

Are there any timelines for ROS 2 support?

We have plans to support ROS 2 , however, we don't have timeline yet, please wait ..


text:
🛑 MCU - Owncloud is down

In 8acec8d, MCU - Owncloud (https://cloud.cdeluruguay.gob.ar/login?redirect_url=/apps/dashboard/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MCU - Owncloud is back up in 730e75a after 5 minutes.

repo: elfoche/monitoreo


text:
Tv shows with single quote

Hi!
I would like to thank you for this amazing addon.
However, I realized that tv shows titles with single quotes return with the error "No links were found".
Some examples: The handmaid's tale and all the marvel's shows.
I have tested the last version (0.0.49) and the error persists.
Since Quasar works fine with those titles, I wonder if there's a chance to fix this.
Thanks in advance.

Searching with payload (episode): {u'episode': 6, u'title': u'\u0440\u0430\u0441\u0441\u043a\u0430\u0437 \u0441\u043b\u0443\u0436\u0430\u043d\u043a\u0438', u'season': 1, u'tvdb_id': 321239, u'imdb_id': u'tt5834204', u'titles': {u'ru': u'\u0440\u0430\u0441\u0441\u043a\u0430\u0437 \u0441\u043b\u0443\u0436\u0430\u043d\u043a\u0438', u'en': u"the handmaid's tale", u'ua': u'\u0456\u0441\u0442\u043e\u0440\u0456\u044f \u0441\u043b\u0443\u0436\u043d\u0438\u0446\u0456', u'original': u"the handmaid's tale", u'source': u"The Handmaid's Tale"}, u'absolute_number': 0, u'year': 2017}

This is all about the searcher. Some trackers find results with quotes, some do not. Quasar was removing quotes, it was helping for some trackers/requests, but some were failing.
Maybe it will be fixed in burst.


text:
MSID: 87555 Version: 2 DOI: 2023.03.22.533803

[PLACE MANUSCRIPT AND EDITOR DETAILS HERE WHEN AVAILABLE] See step 3
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v1/by-publisher/elife/get-by-manuscript-id?manuscript_id=87555)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/87555/v2)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews and QC
Who can help: Production team

[ ] QC passed or QC not needed

Who can help: Editorial team

[x] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2023.03.22.533803)
[ ] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/87555/v2/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2022.10.28.514241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2022.10.28.514241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/87555)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/87555

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/87555

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/87555/v2/87555-v2.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/87555)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

Reviews pending.

authors: JGilbert-eLife nlisgo

repo: elifesciences/enhanced-preprints-import


text:
IIIF server deployment is broken

Description
When enabling the new IIIF integration on the main deployment, the image file location logic isn't replacing the paths, thus the output is failing to load a local image file.

Changes in https://github.com/elifesciences/enhanced-preprints/pull/268 increases logging for the path replacement. Once they are deployed, it should help illuminate what the string replacement is looking for, and can be compared with the log file output of the converted html/json.

Looks like the encoda paths are using the original directory path, whereas when we run the filePath later through realpath, it traverses the symlink and returns a different path. PR #282 Should fix this by running the file path through realpath before handing it to encoda

repo: elifesciences/enhanced-preprints


text:
🛑 Jellyfin is down

In 60fb976, Jellyfin (https://jellyfin.elightcap.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Jellyfin is back up in 2055927.

repo: elightcap/statuspage


text:
feat: remove saved gradients

Created an option to remove just one saved gradient and at the top corner an option to remove them all.
Also I placed a condition to show the saved card only if the user have some saved gradient.
Thanks!

Thanks for your contribution!
@all-contributors add @amimaro for code

authors: amimaro eliutgon

repo: eliutgon/tailwind-gradient-generator


text:
unsafe_fragment signature change

Issue https://github.com/elixir-ecto/ecto/issues/2265

This explores a unsafe_fragment(binary(), list()) implementation where ? characters in the first argument are interpolated with the values from the second argument. Hoping to get some quick feedback as there is a couple different ways this could be done.
I was also thinking it may be nice to have similar function signatures for fragment and unsafe_fragment. Any thoughts on changing fragment(...) to fragment(binary(), list()) as well? Would that be a bit too frivolous for a breaking change?

Any thoughts on changing fragment(...) to fragment(binary(), list()) as well? Would that be a bit too frivolous for a breaking change?

With fragment we need the list at compile time because that's when we build the query, allowing a list could be confusing because you would think that the following is possible:
params = [post.title]
select(query, [post], fragment("?", params))

@ericmj the problem is that the two APIs are now inconsistent. One uses varargs, the other one does not and uses a list. Maybe we should call this something else rather than unsafe_fragment? I understand though that they are inconsistent exactly because they have different requirements, but I think the differences in API will be confusing.

Hi @dallincrane! After talking to @ericmj we have realized that the old API supported query expressions in interpolation:
unsafe_fragment("? = ?", p.foo, 1)

But this one does not (or if it does, it is a bit inconsistent as it requires a compile time literal). For this reason, we have decided to keep unsafe_fragment as is.
Maybe we could introduce this PR as a dynamic_fragment but I think we should wait until we have more use cases. Thoughts?

@josevalim, sounds good to me! I would think #{} interpolation of the first arg and general string concatenation should work for most cases.

I've noticed a couple of differences in the APIs betweenfragment(...) and unsafe_fragment(...) that might be good to clear up and I could use this PR to submit some changes if needed!
In the example you gave above I would expect that to work, but the first argument always requires ^
from p in "posts", where: unsafe_fragment(^"? = ?", p.foo, 1)
To summarize
fragment("hello") # GOOD
fragment(^"hello") # BAD

unsafe_fragment("hello") # BAD
unsafe_fragment(^"hello") # GOOD

I still definitely have a lot to learn here, but it seems like ^ should only be required when the value isn't a compile-time literal. I know that the implementation is a little different when it comes to compile-time vs runtime for fragments. However, as a user, I would still expect the interface to feel similar across the board.
With all 4 examples above being compile-time literals I'm thinking that they should all work?

@dallincrane the thing is that if you are using unsafe_fragment and you have a literal string, then you have no reason to use an unsafe_fragment. :)

authors: dallincrane ericmj josevalim

repo: elixir-ecto/ecto


text:
Add {:nilify, columns} to on_delete reference option.

Postgres 15 allows the user to specify which columns should be set to null if the referenced record is deleted.
A side note: I noticed that one of the common on delete options from postgres/mysql is not present: ON DELETE SET DEFAULT. I was wondering if this was on purpose or I can submit a PR to add it? I wasn't sure if it was left out on purpose to avoid having to do the same thing for associations.

A side note: I noticed that one of the common on delete options from postgres/mysql is not present: ON DELETE SET DEFAULT.

Sounds good to support it. At the same time nobody asked for it, so we are probably fine. :) Especially as nilifying likely covers the exact same cases.

Sounds good to support it. At the same time nobody asked for it, so we are probably fine. :) Especially as nilifying likely covers the exact same cases.

Sorry I should have put it in description, this person here asked for ON DELETE SET NULL columns and ON DELETE SET DEFAULT columns:
https://groups.google.com/g/elixir-ecto/c/IIbzAgZYgXw

authors: greg-rychlewski josevalim


text:
BIT(1) type cannot load <<1>> as type :boolean #1366

This is on branch v1.1 for MySQL type BIT(1) being translated to a boolean. A similar change may be required on the master branch (ecto v2.0).
diff --git a/lib/ecto/adapters/mysql.ex b/lib/ecto/adapters/mysql.ex
index 73cd825..0c03e62 100644
--- a/lib/ecto/adapters/mysql.ex
+++ b/lib/ecto/adapters/mysql.ex
@@ -93,6 +93,8 @@ defmodule Ecto.Adapters.MySQL do
do: super(type, json_library.decode!(binary))
def load(:map, binary) when is_binary(binary),
do: super(:map, json_library.decode!(binary))

def load(:boolean, <<0>>), do: {:ok, false}
def load(:boolean, <<1>>), do: {:ok, true}
def load(:boolean, 0), do: {:ok, false}
def load(:boolean, 1), do: {:ok, true}
def load(type, value), do: super(type, value)

@paulgithub, you have sent a PR from the v1.1 branch to the master branch. Please send your changes to the master branch and I can "port" them to v1.1 if necessary, thank you! :heart:

Sorry about that the issue is that the code has been updated and I am unable to verify whether the change I make on master will work correctly.
I believe https://github.com/liveforeverx thought he had updated this to echo 2.0 but could not find the changes there.
diff --git a/lib/ecto/adapters/mysql.ex b/lib/ecto/adapters/mysql.ex
index 5a14e5c..be6132d 100644
--- a/lib/ecto/adapters/mysql.ex
+++ b/lib/ecto/adapters/mysql.ex
@@ -106,6 +106,8 @@ defmodule Ecto.Adapters.MySQL do
do: [&json_decode/1, &Ecto.Adapters.SQL.load_embed(type, &1)]
def loaders(_primitive, type), do: [type]

defp bool_decode(<<0>>), do: {:ok, false}
defp bool_decode(<<1>>), do: {:ok, true}
defp bool_decode(0), do: {:ok, false}
defp bool_decode(1), do: {:ok, true}
defp bool_decode(x), do: {:ok, x}

I am therefore nervous of making this pull request without testing.

On 12 Apr 2016, at 16:09, José Valim notifications@github.com wrote:
@paulgithub https://github.com/paulgithub, you have sent a PR from the v1.1 branch to the master branch. Please send your changes to the master branch and I can "port" them to v1.1 if necessary, thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub https://github.com/elixir-lang/ecto/pull/1367#issuecomment-208954332

authors: josevalim paulgithub

repo: elixir-lang/ecto


text:
OTel - Add context propagation

An implementation example for https://github.com/elixir-tesla/tesla/issues/567
Adds a new middleware in order to make explicit that OTel will be used when plugged.
closes #567

Hey @carrascoacd 👋
Thank you both for this 💜💜💜

authors: carrascoacd teamon

repo: elixir-tesla/tesla


text:
fix url for icq profile icon

Signed-off-by: inter pmrtorrents@gmail.com

To consider backport to 1.0.x line

repo: elkarte/Elkarte


text:
Hi

What article on docs.github.com is affected?

What part(s) of the article would you like to see updated?

Additional information

What article on docs.github.com is affected?

What part(s) of the article would you like to see updated?

Additional information


text:
Lachie's notes

These notes expand on @mgold's original annotations, commenting on the latest 0.18 version of the compiler.
All of the changes are in the README.md, although I have also added a haskell-resources.md for persons coming to these compiler docs who are new to Haskell, or would like a refresher.
I've also listed a way to run the Elm compiler and its associated tooling from source through Elm-env, a Dockerized environment that installs the codebase from source.
Probably more to come! These are just some initial notes.

Looks great, keep it coming!

authors: breezykermo mgold

repo: elm-community/elm-compiler-docs


text:
no error on duplicate names in @docs lists

The file Exports.elm has this code.
module Exports exposing (..)

{-| Module docs.

@docs foo, foo
-}

{-| doc comment -}
foo : Int
foo = 2

Documentation is successfully generated (must expose Exports in elm-package.json):
[
  {
    "name": "Exports",
    "comment": " Module docs.\n\n@docs foo, foo\n",
    "aliases": [],
    "types": [],
    "values": [
      {
        "name": "foo",
        "comment": " doc comment ",
        "type": "Int"
      }
    ],
    "generated-with-elm-version": "0.16.0"
  }
]

And rendered (thanks doc preview!) as:

Values (functions, types, etc) with duplicate @doc references should be detected and trigger an error similar to missing documentation.

Yes. For example, this occurs "in the wild" on http://package.elm-lang.org/packages/circuithub/elm-list-extra/3.10.0/List-Extra, which has two entries for find, one in section Basics and another in section Searching.

Tracking in #1374. Thanks!

I have used this bug/feature on purpose in here: https://github.com/gampleman/elm-visualization/blob/master/src/Visualization/Scale.elm. The idea there is that the module exposes several data-structures and operations on them. The operations are polymorphic, but not all structures support all operations. So I use headings for the structures and list all operations that are supported for that structure underneath it - the repetition allows this.
(Of course it could be worked out from the type signatures what supports what, but the type signatures in that module are very long and gnarly).

The new parser fixes a ton of issues, so I'm no longer tracking things in the meta issue. This is also not really a parsing problem. A new check would need to be added.

In my development build, I am seeing:
-- DUPLICATE DOCS -------------------------------------------------- src/Url.elm

There can only be one `custom` in your module documentation, but it is listed
twice:

22| @docs absolute, relative, crossOrigin, custom, custom, Root
                                           ^^^^^^  ^^^^^^
Remove one of them!

Thanks for the report!

authors: evancz gampleman jvoigtlaender mgold

repo: elm-lang/elm-compiler


text:
Images with webp extension aren’t served

I have blank images when trying to use webp, when I replace them with jpg versions all is working fine.

How widely supported is webp right now? Which browsers? Are there conditions under which the mime type work or not?

Not so widely, really, blink based browsers, android devices and opera mini, but it’s 67% of browsers market share. As for other browsers, Edge is not currently planning to support it, Firefox has a bug, but the status of it is unclear.
Wikipedia says that mime type is image/webp and it is unofficial (can’t find reasons for why it’s so, though).

authors: evancz kibin

repo: elm-lang/elm-reactor


text:
Leave passwords alone

Secure passwords often contain characters that would be modified by
parse_input_value(), e.g. quotes. Let's just leave the password values
as specified by the user.
Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de

This seems like a valid request. I just looked at the roundcube source and they also use get_input_value() but with some parameters (see https://github.com/roundcube/roundcubemail/blob/681ba6fc3c296cd6cd11050531b8f4e785141786/index.php#L101-L102). So we have to find out why they do this and if it's important.

Ah, right, they still use get_input_value() but with $allow_html == TRUE. Fixed.

Commited. Thank you.

authors: dscho elm

repo: elm/Roundcube-SMTP-per-Identity-Plugin


text:
Add a page that lists packages published by a single author

We currently have /packages/author/package and /packages/author/package/version. It'd be nice to have /packages/author as well.

Hi, you can use this thing in a meantime:
https://elm.pravdomil.com/packages/
And search for "rl-king/".

authors: pravdomil rl-king


text:
non ascii char

hi, ran this on debian oldstable, python3, but it failed with:
File "squish_velocity.py", line 34
SyntaxError: Non-ASCII character '\xc2' in file squish_velocity.py on line 34, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details
I removed the degree symbol's from the .py and it worked great.

Thanks, updated the .py!

authors: TerraRoot elmerilaakkonen

repo: elmerilaakkonen/squish-velocity


text:
Enable phpstan 0.12

Not sure if there are any BC breaks. Just wanna see what CI says. Maybe we'll have to drop the 0.11 support.

I'm working on support over in #12. There are some complex issues unfortunately. I'll need help from the PHPStan guys to solve them.

Quick update on the status of PHPStan 0.12 support. This repo is probably ready to go, and you can try it out with a ^0.7-dev constraint (you'll also need PHPStan at ^0.12-dev for now).
Unfortunately you'll still get a bunch of PHPStan warnings about Phony itself that look like ... no value type specified in iterable type .... I think this needs to be fixed by improving the PHPDoc in Phony itself, but I'm still trying to figure out the best way to do that.

See https://medium.com/@ondrejmirtes/generics-in-php-using-phpdocs-14e7301953 in case you didn't yet.

As of today you should find new versions of Phony with better PHPStan 0.12 compatibility . Still waiting on this fix to land in a tagged version of PHPStan, but aside from that, there shouldn't be any more major issues.

authors: enumag ezzatron

repo: eloquent/phpstan-phony


text:
[FEAT] Support Variables as Direct Activity Inputs Without Scripting

Currently, retrieving data from a variable for use in an input field requires additional scripting. It would be beneficial to implement a more streamlined approach, similar to how we directly assign output to a variable.
This change would enhance both readability and usability.
Let me know if more information is required!

Hello ,
It should be already available .
You can take a look at #274 for ui side and https://github.com/elsa-workflows/elsa-core/pull/5918 for server side implementation
These PR allow you to choose the variable component in the dropdown list (instead of script) and then choose the variable in a new dropdown.

Oh my apologies I totally overlooked these PR's. Thank you for the addition.

authors: jdevillard sNakiex

repo: elsa-workflows/elsa-studio


text:
Can't install versions higher than 0.1.1

Thanks a bunch for writing this package, it's been quite useful for me for finding siphons in chemical reaction networks. It seems like I can't install versions higher than 0.1.1 though, trying to do so gives the error
(@v1.11) pkg> add Satisfiability@0.1.2
   Resolving package versions...
ERROR: Unsatisfiable requirements detected for package Satisfiability [160ab843]:
 Satisfiability [160ab843] log:
 ├─possible versions are: 0.1.0 - 0.1.1 or uninstalled
 └─restricted to versions 0.1.2 by an explicit requirement — no versions left

I think it's fixed (I can update to 0.2.0 using Pkg). To prevent this issue in the future, I should write a deployment checklist for releasing new versions. When you have time @vyudu can you check it?

Thanks so much! I'm probably not the best person to ask though, I haven't actually had any experience with registering packages and stuff (maybe @isaacsas could take a look? He maintains the package I work on).

I can confirm that I can now get v0.2.0 via the general registry. So it seems to have been released ok.

However, it somehow looks like you deleted the tag here?
Usually my process is to use the @JuliaRegistrator register() command to register a new release (with the Project.toml updated to the new version number). With Tagbot setup it then handles automatically tagging a new branch.

Error while trying to register: Register Failed
@isaacsas, it looks like you don't have collaborator status on this repository.

@isaacsas I made a v0.2.0 tag several months ago, but forgot to call the registrator bot. Then I couldn't call it because the tag already existed. The Internet said to delete the tag and call the bot, which I did yesterday, but then I couldn't create the tag again, mostly because I couldn't figure out where to do it. I figured it out this morning, so now it looks like there is a tag and a registered release. Does it look OK to you? Thanks for checking.

authors: JuliaRegistrator elsoroka isaacsas vyudu


text:
Way to get response in onAfterHandle to perform response transform

Hi, I'm currently seeking way to transform response from a handler and/or on the global ElysiaApp.
{
  code: number,
  data: T, // <= T is the returned data from main handler
  status: boolean,
  message: "OK" | "ERROR"
}

I want all of my API's response shape to be uniform like above. But I don't necessarily want to return { code: xx, data: xx, ....... } on every handler.
Naturally I tried using onAfterHandle, but looks like it doesn't support getting response from the main handler. Sure there's a set object but it only allows setting headers.
This would also allow something like "Prety JSON Middleware" in Hono.js (https://hono.dev/middleware/builtin/pretty-json), which transforms the output into pretty JSON.
Is there a way to achieve this? Thank you.

Hi 👋
you could do something like this:
import { Elysia } from 'elysia';

type MyResponse<T = unknown> = {
  code: number;
  data: T;
  status: boolean;
  message: 'OK' | 'ERROR';
};

new Elysia()
  .onError((ctx) => {
    return {
      code: ctx.set.status ?? 500,
      data: ctx.error.message,
      status: false,
      message: 'ERROR'
    } satisfies MyResponse;
  })
  .onAfterHandle((ctx, response) => {
    return Response.json(
      {
        code: ctx.set.status ?? 200,
        data: response,
        status: true,
        message: 'OK'
      } satisfies MyResponse,
      ctx.set
    );
  })
  .get('/', () => {
    return {
      my: 'json'
    };
  })
  .get('/throw', () => {
    throw new Error('something went wrong!');
  })
  .listen(3000);

You have to wrap the response in Response.json until https://github.com/elysiajs/elysia/pull/167 is merged.

http://localhost:3000{
    "code": 200,
    "data": {
        "my": "json"
    },
    "status": true,
    "message": "OK"
}

http://localhost:3000/throw{
    "code": 500,
    "data": "something went wrong!",
    "status": false,
    "message": "ERROR"
}

Hi, thank you! Awesome. I didn't realize there's a second argument you can use in Handler 😅
I've read the docs a dozen times and looks like the response argument is not documented enough... I appreciate the amazing works of the maintainers though
However when I ran this code, I got an error because the schema I defined in response.200 doesn't match the type returned by onAfterHandle's transform.
new Elysia()
  .onAfterHandle((ctx, response) => {
    return Response.json(
      {
        code: ctx.set.status ?? 200,
        data: response,
        status: true,
        message: 'OK'
      } satisfies MyResponse,
      ctx.set
    );
  })
  .get('/', () => {
    return {
      name: 'json'
    };
  }, {
    response: {
      200: nameSchema
    }
  })
  .listen(3000);

Invalid response, 'name': Expected string

Expected: {
  "name": ""
}

Found: {}

when I remove the response property in the hook, I got the wanted result:
{"code":200,"data":{"name":"json"},"status":true,"message":"OK"}

If I read the docs correctly, Validation on Response must've happened right before After Handle, not after it. Is there something I'm missing or is this a bug?

I've written blog on this you can check this out !
https://www.adarsha.dev/blog/elysia-uniform-response

Hi, thank you! Awesome. I didn't realize there's a second argument you can use in Handler 😅
I've read the docs a dozen times and looks like the response argument is not documented enough... I appreciate the amazing works of the maintainers though
However when I ran this code, I got an error because the schema I defined in response.200 doesn't match the type returned by onAfterHandle's transform.
new Elysia()
  .onAfterHandle((ctx, response) => {
    return Response.json(
      {
        code: ctx.set.status ?? 200,
        data: response,
        status: true,
        message: 'OK'
      } satisfies MyResponse,
      ctx.set
    );
  })
  .get('/', () => {
    return {
      name: 'json'
    };
  }, {
    response: {
      200: nameSchema
    }
  })
  .listen(3000);

Invalid response, 'name': Expected string

Expected: {
  "name": ""
}

Found: {}

when I remove the response property in the hook, I got the wanted result:
{"code":200,"data":{"name":"json"},"status":true,"message":"OK"}

If I read the docs correctly, Validation on Response must've happened right before After Handle, not after it. Is there something I'm missing or is this a bug?

did you found any solution for this, facing same issue

@adarshaacharya Nah. I ended up wrapping every endpoint's response manually with a helper function.
So return ok(data) becomes { code: 200, data: data, ... }
I don't know if this issue still applies to the new Elysia versions though, as I haven't worked with the code again.

@masnormen i think that means we have to wrap every response schema with helper function as well.
I'm trying with latest version and facing same issue, guess we have to wrap every response + response schema with the utility functions :)

authors: adarshaacharya bogeychan masnormen

repo: elysiajs/elysia


text:
nrf: Add some fixes for issues pointed out by clippy

Cleans up ~30 issues pointed out by clippy, though there are still some left which would either require annotations or involve touching some code I wouldn't touch for now..

bender run

authors: Dirbaio plaes

repo: embassy-rs/embassy


text:
Add async Mutex.

What it says on the tin :)
It allows sharing data between tasks when you want to .await stuff while holding it locked.

bors r+


text:
Google Palm2 support

🚀 The feature
Excellent framework :) looking forward for google palm2 support 😎
Motivation, pitch
https://twitter.com/21_inception/status/1682231293168459776

Alternatives
No response
Additional context
No response

Hi @taranjeet  I think the custom app supports vertex ai PaLM2

@taranjeet I think embedchain already support PaLM2 via custom app https://cloud.google.com/vertex-ai/docs/generative-ai/start/quickstarts/api-quickstart

addressed here: https://github.com/embedchain/embedchain/pull/403

authors: aaishikdutta ishaan-jaff taranjeet

repo: embedchain/embedchain


text:
Adding Turkish STSBenchmark

This is the first dataset for Turkish afaik and I have not added my points. Lastly, I will be adding as many Turkish datasets as possible.

[x] I have tested that the dataset runs with the mteb package.
[x] I have run the following models on the task (adding the results to the pr). These can be run using the mteb -m {model_name} -t {task_name} command.

[x] sentence-transformers/paraphrase-multilingual-MiniLM-L12-v2
[x] intfloat/multilingual-e5-small

[x] I have checked that the performance is neither trivial (both models gain close to perfect scores) nor random (both models gain close to random scores).
[x] I have considered the size of the dataset and reduced it if it is too big (2048 examples is typically large enough for most tasks)
[x] Run tests locally to make sure nothing is broken using make test.
[x] Run the formatter to format the code using make lint.

Thanks for the response, I am not also big fan of translation datasets however I thought it was a verified translation since it was released via a publication. I will be adding mukayese and other non-translated Turkish datasets soon.

Thanks for the response, I am not also big fan of translation datasets however I thought it was a verified translation since it was released via a publication. I will be adding mukayese and other non-translated Turkish datasets soon.

If you find some evidence of validation (e.g. quote from article). Then we can move on with the dataset. Otherwise, we can focus on the other datasets.

decent and possible errors will not cause major errors.

A right, but nothing has been done to remedy the errors?
I think, given that there seems to be good alternative datasets, that I would focus on non-translated datasets.

authors: KennethEnevoldsen asparius

repo: embeddings-benchmark/mteb


text:
v4.0.0 just hangs

😦 https://travis-ci.org/ming-codes/ember-ui-kit/builds/239776698
Even in local runs too. It looks like the browser never connects.

Did you include a call to the new start function? https://github.com/ember-cli/ember-cli-qunit#upgrading

😅 just saw there's a bunch of closed issues of the same problem.

authors: ming-codes trentmwillis

repo: ember-cli/ember-cli-qunit


text:
[WIP] Use ember-qunit as an NPM dependency.

This removes ember-qunit as a bower dependency (in favor of using NPM
directly).
Currently, this adds ember-qunit, ember-test-helpers, and klassy
(required by ember-test-helpers) to vendor.js. That is slightly
unfortunate, as ideally these would be added to test-support.js
instead, however there is no mechanism other than app.import in
ember-cli today (1.13.x timeframe) to handle this.
IMO, we should add a addon-test-support tree, that appends to
test-support.js by default. This would allow addons to provide test
helpers much simpler than we can today.

:+1: This would give us more reason to solve the addon test support issue :P

Ya, agree. I'm looking into that in ember-cli (possibly for 2.x).

Updated to utilize treeForAddonTestSupport which is being proposed upstream in https://github.com/ember-cli/ember-cli/pull/5205.
Ultimately, this will either require a backwards compat shim (for older versions of Ember CLI) or it will depend upon the newer Ember CLI version after that new hook is added (and require a major version bump).

https://github.com/ember-cli/ember-cli/pull/5205 is merged upstream but will not be available to consumers until ember-cli@2.2.0-beta.1 ships.
I have updated this PR to enable backwards compat with older Ember CLI versions so that this is not a breaking change.  We can remove the backwards compat shim layer, when we bump major versions.

authors: mmun rwjblue


text:
Fix README Documentation

It appears the main example in the README is incorrect.
See stackoverflow question/answer http://stackoverflow.com/questions/29921395/how-do-you-use-ember-js-addons/29927126

Issue #227 and pull request #230 both relate to this problem. There is discussion around the collection helper and additional changes in #230 - I was going to close this PR but I'll leave it open for someone with access to close if they see fit..
This PR solves the main issue on README and doesn't really cover anything else like #230 does. Merging this PR might solve the larger problem quicker leaving #230 open for all the other things? Or get rid of this and leave it all as #230..

repo: emberjs/list-view


text:
problem: potential thread-race when accessing a Ledger seed

solution: use Mutex to access Ledger connection

Pull Request Test Coverage Report for Build 4662762385

13 of 30 (43.33%)  changed or added relevant lines in 9 files are covered.
19 unchanged lines in 15 files lost coverage.
Overall coverage increased (+0.2%) to 54.374%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/migration/source/common.rs
0
1
0.0%

src/structs/seed.rs
1
2
50.0%

src/sign/bitcoin.rs
1
3
33.33%

src/storage/vault_ethereum.rs
0
2
0.0%

src/sign/key_source.rs
0
3
0.0%

src/sign/ethereum.rs
1
5
20.0%

src/structs/wallet.rs
7
11
63.64%

Files with Coverage Reduction
New Missed Lines
%

src/blockchain/addresses.rs
1
51.85%

src/blockchain/ethereum/address.rs
1
75.0%

src/blockchain/ethereum/signature.rs
1
75.0%

src/convert/proto/address.rs
1
80.0%

src/convert/proto/book.rs
1
78.26%

src/convert/proto/seed.rs
1
79.07%

src/crypto/encrypted.rs
1
87.78%

src/crypto/kdf.rs
1
88.46%

src/crypto/pk.rs
1
66.67%

src/proto/wallet.rs
1
48.99%

Totals

Change from base Build 4633698946:
0.2%

Covered Lines:
2132

Relevant Lines:
3921

💛  - Coveralls

authors: coveralls splix

repo: emeraldpay/emerald-vault


text:
The "dismissible" prop has no effect

Describe the feature / bug 📝:
Using a variety of functions, such as toast() or toast.custom(), whether passing a jsx component or otherwise, adding the dismissible prop has no effect.
Steps to reproduce the bug 🔁:

In terminal: npx create-react-app sonner && cd sonner
npm i sonner
In greenfield project (App.js):

import logo from './logo.svg';
import './App.css';
import { toast } from 'sonner';
import { Toaster } from 'sonner';

function App() {
  return (

      <Toaster />

          Edit src/App.js and save to reload.

          Learn React

        <button onClick={() => toast(
A custom toast with default styling
, { dismissible: false })}>Trigger toast</button>

  );
}

export default App;

Click button.
Toast is dismissed after default duration.

I have the same issue at `v1.4.41. I would prefer to not have to set duration as something very long just to have it stay until being dismissed. (I know the toast is opinionated and maybe this preference is not compatible). I checked the docs to make sure.

authors: axelhj siiiiilvio

repo: emilkowalski/sonner


text:
Long recipe IDs push tooltip offscreen

When show recipe IDs is enabled, any long ID will cause to tooltip to become very large, and no longer able to fit inside the screen, as shown in the screenshot. I can't propose a specific solution to this problem because I have no idea what would be a good solution haha.
Example:

the world if tooltip auto-wrapping was in vanilla
for now, see if Tooltip Fix helps

Fixed in 1.0.0

authors: LemmaEOF Nataly171 emilyploszaj

repo: emilyploszaj/emi