Is it possible to use it in a Handlebars file ?

Hi !
I'm using your bundle, and it is exactly what I need !
Working perfectly with Twig
My problem is that I now use handlebarsjs template file for a specific functionality in my symfony app.
Is there a equivalent of {{ someInteger|rating }} for handlebars ??
Thanks

@odecharette Currently StarRatingBundle only supports twig.  It shouldn't be too hard to add a handlebar helper though.  If you look in Extensions/StarRatingExtension.php you'll notice that the rating extension is basically just passing off the variables to a template to render.  If you decide to do this feel free to submit it as a pull request as i'd love to include handlebar support if possible.


Upgrade Envoy to v1.23.0 and misc changes

Upgrade Envoy to envoyproxy/envoy:v1.23.0.
In places where Validate() was called use ValidateAll() instead as Validate() only returns the first error message whilst it would be useful to return all the error messages.
Remove resources (limits) from development/testing/manifests/2_envoyfleet.yaml.
Expose admin port in config/samples/gateway_v1_envoyfleet.yaml.
Signed-off-by: Mohamed Bana<EMAIL_ADDRESS>
This PR...
Changes

Fixes

Checklist

[ ] tested locally
[ ] added new dependencies
[ ] updated the docs
[ ] added a test

😍

I stand corrected it looks like that CI doesn't agree with me

I see that CI passes but what I would like to see is that we split this PR into two smaller PRs. One to handle container image update and the other one to include changes like Validate -> ValidateAll and similar.
Just to keep them separate in case we need to revert one of these changes.
What do you think?
@kylehodgetts what do you think?

I'll make those changes.


Command line reference page incomplete; also has apparently inconsistent h2/h3

At https://gleam.run/writing-gleam/command-line-reference/, e.g. publish is h3, deps-list is h2.
The reference is also missing (maybe not all are relevant):

check
clean
help
update

Oops, thank you.

Hi @lpil, I would like to work on the documentation for this project. Can you please assign this issue to me?

Thank you @HatGuy68 !


support dockerd and docker daemon in unit files

Using docker daemon has been deprecated since docker v1.13.  This means that if you are using a recent version of docker, the unit files for upstart and systemd call the deprecated binary that is not installed.  However, for people running older versions of docker, using docker daemon is correct.  In this pull request I am adding support for people using dockerd.  Here is a related issue https://github.com/garethr/garethr-docker/issues/701.

Works well on docker >= v1.12.1

I'm no mantainer but, couldn't this be more easily done just assigning proper default values in params.pp to docker::service::docker_command and docker::service::daemon_subcommand ?


BUG: Sign in sign up missing

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I want to add a sign it button in signup form and signup button in sign in form
Add ScreenShots

What browser are you seeing the problem on?
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'23 contributor
[X] I want to work on this issue

@TechSpiritSS please assign this to me


[WIP]Pango text provider integration

The pr provides pango integration for Kivy text provider.It is renders devanagri ,arabic text easily as tested by this script .Other text providers failed to load the text and just showed boxes instead.
This pr is inspired by
https://github.com/kived/kivy/tree/text-pango
https://github.com/kived/kivy/tree/text-pango2
I have worked around many tutorials and problems posted on issues thread in a repository.These script will provide the working knowledge of pango.
I found the following link also helpful link
This pr is work in progress and welcome suggestions from reviewers.While working on it i realised cairo is capable of doing many more things like lateral inversion of text,animation of text.These feature are crucial for heads up display devices(HUD).
I will weed out pep8 errors in upcoming commits.
Edit:-

text rendering without pango image
text rendering with pango image

I have added a brief detail about text layout engine in this pdf.I have briefly discussed also the details of Pango and Harfbuzz. Limitations of Harfbuzz are also discussed in it.

closing in favour of #5073


CNOT pulse gate Bug

Environment

Qiskit Terra version: 0.24.1
Python version: 3.9.15
Operating system: Windows

What is happening?
Sorry to my English. I hope you understand.
If I use Pulse with my own calibration set at Fakebackend, and when I run the circuit including CNOT(The job type is schedule), then  Its result is really weird thing. I write my code below.
How can we reproduce the issue?
from qiskit import QuantumCircuit
from qiskit import transpile, schedule
from qiskit.tools.visualization import plot_histogram
import matplotlib.pyplot as plt
from qiskit import pulse, Aer
from qiskit.pulse.library import Gaussian, GaussianSquare, Drag
from qiskit.providers.fake_provider import FakeManila
from qiskit.visualization import plot_histogram
from qiskit.circuit import Gate, Parameter
import numpy as np
Working case :
backend = FakeManila()
circ=QuantumCircuit(2)
circ.rz(-np.pi/2,0)
circ.sx(0)
circ.rz(np.pi/2,0)
circ.barrier()
circ.sx(0)
circ.barrier()
circ.sx(0)
circ.barrier()
(#circ.cx(0,1))
circ.measure_all()
with pulse.build(backend, name='X') as x_q0:
pulse.play(Drag(duration=160, beta=-1.5858585858585856, amp=0.08388888888888889, sigma=40), pulse.drive_channel(0))
circ.add_calibration('sx',[0], x_q0)
circ_transpile = transpile(circ, backend,initial_layout=[0,1])
circ_sched=schedule(circ_transpile, backend)
job = backend.run(circ_sched, shots=20000)
counts_scaled = job.result().get_counts()
counts_scaled
then the result is pretty understandable. Because this code is just have one hadamard gate
But Non-Working case:
backend = FakeManila()
circ=QuantumCircuit(2)
circ.rz(-np.pi/2,0)
circ.sx(0)
circ.rz(np.pi/2,0)
circ.barrier()
circ.sx(0)
circ.barrier()
circ.sx(0)
circ.barrier()
circ.cx(0,1)
circ.measure_all()
with pulse.build(backend, name='X') as x_q0:
pulse.play(Drag(duration=160, beta=-1.5858585858585856, amp=0.08388888888888889, sigma=40), pulse.drive_channel(0))
circ.add_calibration('sx',[0], x_q0)
circ_transpile = transpile(circ, backend,initial_layout=[0,1])
circ_sched=schedule(circ_transpile, backend)
job = backend.run(circ_sched, shots=20000)
counts_scaled = job.result().get_counts()
counts_scaled
this circuit is bell state circuit but result is like {'00': 3395, '01': 16605}.
What should happen?
Just output is measure of bell state result with little noise.
Any suggestions?
NOne

Thanks for sharing @BeomGyuChoii
I think there is a bug here, but I don't think it's related to the pulse gate, but rather to the measurement handling for the schedule. You can recreate the bug without the pulse gate:
backend = FakeManila()
circ=QuantumCircuit(2)
circ.sx(0)
circ.cx(0,1)
circ.measure_all()

circ_transpile = transpile(circ, backend,initial_layout=[0,1])
job = backend.run(circ_transpile, shots=20000)
counts_scaled = job.result().get_counts() # Seems correct

circ_sched=schedule(circ_transpile, backend)
job = backend.run(circ_sched, shots=20000)
counts_scaled = job.result().get_counts() # Definitely wrong

The circuit run seems to be ok, but the schedule run is wrong, and doesn't measure qubit 1 at all. (It should be noted that running schedules on IBM backends is headed for deprecation [and actually won't work even now on some of them]).
@to24toro, what do you think? Is it related to the fixes you've been working on?
(@nkanazawa1989 FYI)

There could be some bug since Aer pulse simulator is not maintained recently (this is replaced with Qiskit Dynamics now, but fake backends don't support dynamics path).
Anyways just scheduling the circuit with fake backend calibration doesn't work in many case. This is because you need to know exact Hamiltonian of your device at the time the calibration data is generated, but we don't update the Hamiltonian parameter in regular basis. Basically you need to recalibrate all of your pulses on a simulator instance, with the hard-coded Hamiltonian.

Here is an even simpler example which reproduces the bug:
backend = FakeManila()
circ=QuantumCircuit(2)

circ.sx(0)
circ.sx(1)
circ.measure_all()

circ_transpile = transpile(circ, backend,initial_layout=[0,1])
circ_sched=schedule(circ_transpile, backend)

job = backend.run(circ_transpile, shots=20000)
counts_scaled = job.result().get_counts()
# {'10': 5835, '00': 5916, '11': 3996, '01': 4253} - seems ok
job = backend.run(circ_sched, shots=20000)
counts_scaled = job.result().get_counts()
# {'00': 2887, '01': 17113} - definitely wrong

Thanks @TsafrirA for further investigation. I agree this is a simulator bug about measurement instruction handling. We recently did some refactoring for measurement scheduling, but no test was broken with this refactoring. Can you also put the repr of circ_sched ?

Just what I was looking at.
Schedule((0, Play(Drag(duration=160, sigma=40, beta=-0.803458359149747, amp=0.09951569310073495, angle=0.0069670825682855535, name='X90p_d0'), DriveChannel(0), name='X90p_d0')), (0, Play(Drag(duration=160, sigma=40, beta=-0.6480781322121083, amp=0.09633544983165646, angle=0.020048140208258274, name='X90p_d1'), DriveChannel(1), name='X90p_d1')), (160, Acquire(22400, AcquireChannel(0), MemorySlot(0))), (160, Acquire(22400, AcquireChannel(1), MemorySlot(1))), (160, Play(GaussianSquare(duration=22400, sigma=64, width=22144, amp=0.27999999999999997, angle=-2.592031183709648, name='M_m0'), MeasureChannel(0), name='M_m0')), (160, Play(GaussianSquare(duration=22400, sigma=64, width=22144, amp=0.27, angle=2.652928848157663, name='M_m1'), MeasureChannel(1), name='M_m1')), (22560, Delay(1680, MeasureChannel(0))), (22560, Delay(1680, MeasureChannel(1))), name="circuit-120")
It seems like the schedule is OK. Should I move this issue to Aer?

Yes,
(160, Acquire(22400, AcquireChannel(0), MemorySlot(0))), (160, Acquire(22400, AcquireChannel(1), MemorySlot(1)))

looks like acquires are schedule properly. I think this is not related to Terra.

@BeomGyuChoii
A new issue was opened in Qiskit-Aer (1858) just to be on the safe side, but it should be mentioned that Qiskit Aer's pulse simulator is deprecated and headed for removal (1809). Pulse level simulations should be done using Qiskit Dynamics.

DynamicsBackend tutorial is good to start with. The dynamics backend can take circuit and simulate it at Hamiltonian level.
https://qiskit.org/ecosystem/dynamics/tutorials/dynamics_backend.html
We'll close this issue. Feel free to reopen it.

Thanks for taking care of this problem


Incremental --build, then delete generated js file, then another incremental --build does not recreate js file

TypeScript Version:  3.4.0-dev.20190326

Search Terms:
incremental
Code
tsconfig.json:
{
  "compilerOptions": {
    "incremental": true
  }
}

x.ts:
console.log("hello");

Expected behavior:

$ tsc --build
x.js has been generated
$ rm x.js
$ tsc --build

Expected: x.js has been regenerated
Actual behavior:
x.js still does not exist
Related Issues:
Did not find any.

Hmm the root cause of this is that in general our incremental build (BuilderProgram) isn't equipped to deal with missing output file as indication to build but changed file as more like it. Need to think about what we can do here. Till then the workaround is to run --clean and then build or add comment or something into the file whose output needs to be generated.
Note that this didn't originate with just --incremental, this would be same behavior when you followed same pattern but were running tsc --build --watch from first step (even without --incremental in compiler options)

A separate, but possibly related issue: deleting source .ts files does not remove the related .js files. Right now, to address this, I clean the output directory before every compilation - but this makes it impossible for me to use the --incremental flag.

@irakliy81 that's totally out of scope and does not work even without --incremental. Build cannot delete any output file unless you specify clean (which will also delete output files of config specified at that moment)

👍 also experienced this bug: we have a piece of code which imported a recently deleted file, and since we use caching of buildinfo in CI, parallel branch builds started to experience this missing file too. However, the error was different than just 'module not found', it was another type error from patient-0 branch. Thus, I wonder, if buildinfo remembers build errors too?

@sheetalkamat - yes, I wouldn't expect it to work without --incremental flag since in that case there is no info stored about the previous build. But with the --incremental flag, it should be possible to remove output files if the source files have been removed.
A separate question: how do you specify clean? It doesn't seem to be a valid compiler option.

@irakliy81 --clean

@milesj - thanks! But it doesn't seem to be listed here: https://www.typescriptlang.org/docs/handbook/compiler-options.html and if I try to set it in VS Code I get "unknown compiler option" error. Am I missing something?

It's part of project references. Not sure if it's available outside of that. https://www.typescriptlang.org/docs/handbook/project-references.html

any plans on fixing this? cc @sheetalkamat

For clarity: What/who is deleting the output files and why?

There are multiple workarounds for this issue.

Run tsc --b --clean
Delete .tsbuildinfo file as well

Its not clear why only .js file is deleted

@RyanCavanaugh

For clarity: What/who is deleting the output files and why?

I’ve had this happen when an unrelated clean script deleted output directories including, but not necessarily limited to, Typescript output. I mean, normally I assume that if I delete output and re-run a build tool, the output will be recreated; that’s true of all build tools I’m used to, for web development or otherwise, except, in this case, Typescript.

Your expectations are fine, we're just trying to figure out if the scenario is common enough that e.g. people who have 1,200 build outputs should be paying the cost on every single operation for TS to check if all those outputs still exist. Can the "unrelated clean script" just delete the .tsbuildinfo as well?

well yes, then we have to check files existence on our side in CI. Which is fine, but as already mentioned, against expectations

I've noticed also tsc -b --clean only cleans the output files without rebuilding them, is this the desired behavior? Since the command is tsc -b --clean I assumed it will build also.

tsbuildinfo also does not get invalidated when tsconfig.json changes. Thus code generated e.g with target: es2017 does not get rebuilt when the target gets changed.

@matthiasg See #31118.

@glen-84 thanks.

Your expectations are fine, we're just trying to figure out if the scenario is common enough that e.g. people who have 1,200 build outputs should be paying the cost on every single operation for TS to check if all those outputs still exist. Can the "unrelated clean script" just delete the .tsbuildinfo as well?

This is reasonable, but I think the 90% case is worth covering here: something like if outDir doesn't exist at all (or maybe the first output file?) does not exist when starting a new tsc --incremental, assume it's been externally deleted and ignore .tsbuildinfo?
Another workaround / fix for people who need these external tools is to simply place the .tsbuildinfo in the outDir so it gets cleaned too.

@simonbuchan

so it gets cleaned too.

killing the whole purpose here

The --incremental feature is really new and I haven't found a lot of information on how it works internally.
Is it fair to assume that the TS compiler will/could generate the output faster when it has a .tsbuildinfo file even if there isn't any output files?
If the build time is going to be the same as a fully clean one with no .tsbuildinfo, then storing them in git does not make any sense.
On the other side, if the build time should be indeed faster then I think the scenario is compelling enough to investigate how much of cost it will have and if it is worth fixing this. Any project that runs CI or a developer doing a fresh checkout will benefit from this and save precious time.

Here is an usecase when incremental build breaks developer experience:
We have a file that reads all A/B experiment configuration files (.ts) from folder using glob.
These files are compiled using tsc (experiments/.ts in ts-config).
When developer deletes experiment file.ts they expect compiled file to be removed too, otherwise A/B test stays active. Only manually checking and deleting build info helps.
Hope it’s clear.

Two completely different things are being discussed here and it'd be good to keep things separate. The OP refers to the first issue and it's what we're tracking with this item.
Should --incremental assume that some files may have been deleted from disk?
There's a real perf cost to doing this and it's unclear how you would often get in this state in a way where you couldn't automate yourself back into a good state (e.g., if a script is deleting some random subset of JS files, that script should also delete .tsbuildinfo and force a rebuild).
Should a subsequent build delete files that were generated by a prior build but no longer have a source?
This was discussed offline for a bit and we think the answer is a hard no. As far as we know this behavior isn't precendented by other incremental compiler tools (open to corrections on this point), and the stakes of deleting arbitrary files on disk are simply higher than we'd like to engage with. Scenarios where the enumerated set of files substantially matters are somewhat rare (IOW most of the time the import graph is what matters), as is deleting a source file in the first place. Incurring the cost of a clean or manual delete doesn't seem like a very high burden compared to the amount of work and risk on our side to figure out what a "correct" delete is. We could maybe think about some very clearly-named flag like deleteJavaScriptFilesInOutputFolderThatLackCorrespondingInputs but it's just not something we're keen to do.

Thanks for the clarification, @RyanCavanaugh. Here's my thoughts:

Should --incremental assume that some files may have been deleted from disk?

In the general case, I'm fine with this, even if it breaks the cache transparency, I think. But it's pretty common to delete the entire output directory, and it's an unnecessary small cut to have to remember to delete the build cache too compared to other tools. Perhaps checking for just the output dir leads to false confidence?

Should a subsequent build delete files that were generated by a prior build but no longer have a source?

Scenarios where the enumerated set of files substantially matters

Substantially, perhaps, but the standard use case is the pack up everything in the out directory. For someone that's not paying attention, this means they are bloating their package size.

as is deleting a source file in the first place.

Eh, depends on your style. moving source files is fairly common. The repo I'm in at the moment has 43 renames or deletes in the last 100 commits.

Incurring the cost of a clean or manual delete doesn't seem like a very high burden compared to the amount of work and risk on our side to figure out what a "correct" delete is.

Not sure why there are scare quotes here: what's wrong with lastBuildOutput.filter(f => !newBuildOutput.includes(f))?

Any news on a fix?

I so much agree with @simonbuchan

and it's an unnecessary small cut to have to remember to delete the build cache too compared to other tools

I just lost 1 hour with that.
Adopted new "project" strategy (for a src + test simple project); built; cleaned the whole dist; wondered half an hour why subsequent tsc -b didn't produce any output at all; tried to digg and remove incremental tag (which I hate in general, stateless in mind); got "incremental option may not be disabled for composite projects"; got stuck.

I would have assumed that --incremental stores and checks the signatures of both the definitions and the generated sources.
In the current state there's basically a secret contract saying that nobody but tsc can touch the build output. It's not what I would assume from something simply advertised as an incremental build. And apart from subtle phrasing in the 3.4 release notes I don't think it's clear from the docs either that only types definitions are checked.
I too would be for making --incremental check the generated sources too by default ; if this comes to an unreasonable cost to certain projects, having an additional, clearly labelled setting (eg. --incrementalTypeChecking) to restore current behavior would probably be enough to make everyone happy.

I enabled composite to use references, and I lost an hour tracking down this heisenbug.

This is a bit confusing.

If we don't run with --build, then the tsc program completes very fast, with no clues as to why, as if everything is fine.

Running just tsc should give a helpful message. Or, even better, it should run the project in --build mode.
Perhaps we need an option in tsconfig.json that can make the --build option not required.

If we run tsc --clean, it fails, without a helpful message. There's no obvious way to know that it should be tsc --build --clean

It's just not intuitive. I think many people spend many hours (if not days) fiddling around with this stuff. It is too time consuming.

This is a bit confusing.

If we don't run with --build, then the tsc program completes very fast, with no clues as to why, as if everything is fine.

Running just tsc should give a helpful message. Or, even better, it should run the project in --build mode.
Perhaps we need an option in tsconfig.json that can make the --build option not required.

If we run tsc --clean, it fails, without a helpful message. There's no obvious way to know that it should be tsc --build --clean

It's just not intuitive. I think many people spend many hours (if not days) fiddling around with this stuff. It is too time consuming.

Should --incremental assume that some files may have been deleted from disk?

There's a real perf cost to doing this and it's unclear how you would often get in this state in a way where you couldn't automate yourself back into a good state (e.g., if a script is deleting some random subset of JS files, that script should also delete .tsbuildinfo and force a rebuild).

Experience report:
We are running into this in the context of converting one project in a monorepo from JS to TS. So we used to have an index.js in one of our libraries. I converted it to index.ts and added a build script in the package.json. All contributors install all dependencies and run all build scripts anyway as part of the monorepo tooling, so I assumed that they would not see any difference. But when contributors switch back and forth between a branch that has my changes and a branch that does not have my changes, git ends up deleting the index.js but not the tsconfig.tsbuildinfo. I think because the other branch has index.js tracked by git but not tsconfig.tsbuildinfo. So the end result of switching branches back and forth is that the build is broken and can only be repaired by cleaning.
I saw a couple of colleagues complaining in Slack and was affected myself, so I guess that more colleagues were affected but didn't complain. I estimate we lost about 10 person hours because of this, plus some confidence in typescript. (Personally I'm still confident in typescript, but some colleagues had a first bad interaction).

We are having problems similar to @Toxaris
Sometimes, tsc stop recompiling some files, assuming that they are unchanged. The only way to recover is to force a change in the affected file or delete the .tsbuildinfo file.
In our case too, it seems to happen when switching branches or rebasing.
I have also tried looking into the .tsbuildinfo contents, but I don't know how to interpret them.
Is there a strategy we can use to pin down the problem?

For "should a subsequent built delete files that were generated by a prior build but no longer have a source?", https://github.com/microsoft/TypeScript/issues/16057 is closely related (with several links to libs that patch in this behavior).

Running an incremental build should produce the same result as removing the output folder and running a normal build

I strongly agree with this statement!
At the moment, incremental builds provide maximum performance but with the possibility of "incorrect" or unexpected output (i.e., it does not build a file we expected it to build).
I'd rather the incremental build always be 100% correct. Ideally it should be faster than a full clean and build, since it can skip the compilation of some modules.
Maybe we need a different flag that guarantees correctness, but with a slight performance penalty?
"compilerOptions": {
    ....
    "incrementalSafe": true
}

Safety should be opt-out, not opt-in.

Safety should be opt-out, not opt-in.

I agree, but since this issue has been open 2 years, I was hoping to suggest something that might be accepted, so those of us who care can use the safer option.
Ideally, the "incremental" : true should guarantee correct output, and we can have more advanced options to adjust the build speed / safety if desired, like:
"compilerOptions": {
    ....
    "incremental": {
        "checkMissingOutputFiles": true,  // if an output *.js file disappears or was modified, we rebuild it on the next pass. default: true.
        "checkMissingSourceFiles": true,  // if a source *.ts file disappears, we delete the associated output file on the next pass. default: false.
    }
}

The default values for checkMissingOutputFiles and checkMissingSourceFiles were chosen because they are safest.

I just got hit by an issue from a renamed source file, where the old output JS file ended up getting executed instead, and had a runtime error.
I think my case was specifically the Should a subsequent build delete files that were generated by a prior build but no longer have a source? issue. But it sounds like the general issue at hand is from trying to keep the source and output files in sync (kind of similar to cache invalidation?)
I'm a fan of having configuration options for correctness / speed tradeoffs if possible.
In my opinion, it should guarantee correctness by default, but configuration options to toggle would be awesome.
It sounds like there's multiple ways for the compiled output directory to get out of sync with the source, where incremental builds won't re-sync. This makes incremental builds less valuable for me, by not being able to trust whether the output directory is in the expected state or requires some manual inspection / fixing.
My understanding of some current workaround options are:
1. Manually delete the outDir & .tsbuildinfo when I run into an error (my current approach, but might be non-obvious if an error is related or not)
2. Write my own custom logic to identify if the outDir has gotten out of sync (seems fairly complicated to me)
3. Always delete the outDir & .tsbuildinfo before incremental compilation (removes most of the benefit of incremental)
I'm curious if there's any other good workarounds!
Regarding precedents for deletion, I'm familiar with some related config flags in a couple other tools.
But they're specifically for source to target directory sync, rather than incremental compilation:

rsync --delete: delete extraneous files from dest dirs

https://linux.die.net/man/1/rsync

aws s3 sync --delete: Files that exist in the destination but not in the source are deleted during sync.

https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html

Hi,
I just found the same problem on my NestJS project.
Here is the process with a very simple typescript project to reproduce it easily :

Create a "test" folder, go inside on a shell, and type the command : npm i typescript --save-dev (very simple "package.json" and "package-lock.json" files are created, defining this only dev dependency)".
Type the command: npx tsc --init (a "tsconfig.json" is created).
Modify the "tsconfig.json" contents with this:
{ "compilerOptions": {  "module": "commonjs",  "baseUrl": "./src",  "rootDir": "./src",  "outDir": "./dist",  "target": "es2017",  "incremental": true  } }
Create a "src" subfolder in your "test" folder, owning a simple "test.ts" file defining a simple class:
(export class MyClass {})
Build the project by typing in the "test" folder the command: npx tsc -p tsconfig.json
The "test/dist" folder is created owning only one file "myfile.js" defining the MyClass class. But a "tsconfig.tsbuildinfo" file has also been created NOT into the "dist" folder like the documentation explains, but in the "test" folder at the same level than the "tsconfig.json" file.
Delete the "dist" folder and build the project again with the same command than the step 5 above.
The "dist" folder is NOT generated this time, and the tsc command returns no error (code returned is 0).

AND MOST IMPORTANT: NestJS set this "incremental" property to "true" by default in every new NestJS project. This is how I've found the problem. For several days I got no problem: the "tsconfig.tsbuildinfo" file was generated inside the "dist" folder. But at a certain moment, I should have set a bad config because I did several configuration tests, and the "tsconfig.tsbuildinfo" has been generated in the main folder of the project as in the above example, causing the problem.
The only bypass I see:

Delete the "tsconfig.tsbuildinfo" file if it is not generated inside the "dist" folder but in the main project folder.
Or simply unset the "incremental" option, or set it to false.

Regards.

Should --incremental assume that some files may have been deleted from disk?

My use case for having the --incremental flag check the existence of "outputted" files on disk is that I have multiple tools building into the same folder and I would like to delete the build folder between builds.
e.g.
{
  "scripts": {
    "clean": "rm -rf dist",
    "build": "npm run clean && npm run build:js && npm run build:types && npm run build:files",
    "build:js": "swc src --outdir dist",
    "build:types": "tsc --declaration --emitDeclarationOnly",
    "build:files": "cpx src dist --ignore *.ts"
  }
}

The reason I would like to clean between builds is because files might have been deleted since the last build and not removing them increases the size of the build artifact, is confusing to debug and can result in unexpected consequences during execution - e.g. move foo.ts to foo/index.ts and nodejs will still require the old generated artifact.
I was hoping that --incremental would save the compiler from a notable amount of work, even if it did mean writing the output files again.
Similar to other posters it took me a while to understand what was happening and finally end up here 😄

I'm seeing similar behavior when running a build doesn't output a new build (I use incremental as well). Deleting the tsbuildinfo does fix this. However I found that the issue I had was using "emitDecoratorMetadata" in the tsconfig for our decorators. This for some reason prevents the builds from re-generating the build output.


GUI interaction with Pointer Function is off.

So I am trying to build a GUI using the pointer function. I was using the demo and everything was working as expected. However I desperately need to use the mono version however because of https://github.com/godotengine/godot/issues/70050, the demo crashes. So I figured out I can still use the blocks from the plugin for the GUI however the tracking is somehow off when using the pointer. As shown in the video below, almost complete viewport surface is recognized as the button in the middle and two other buttons I placed (checkbox and check button) are completely ignored, making my GUI completely useless. I guess it should be related to my initialization since it works just fine in the demo. Any help would be appreciated.
https://user-images.githubusercontent.com/81292621/224969034-4a9ba781-3e9e-43f3-9cf0-82c7b4bca1d4.mp4

I just found the real cause of the problem. Neither the viewport node nor it's parents are are allowed to be scaled. If scaled, FunctionPointer doesn't take the new position in consideration.


Investigate how to approach error handling improvements

[x] Task list for improving error handling
[x] Unique definition list/guide line of error responses like error codes, stacktrace and logging

The tasks list is included in #219


Faint static noise on Linux

I'm facing this issue where the speakers emits a very faint static/white noise.
Usually I have to get really close to hear, but it's very noticeable at night since everything is quiet and I can hear from normal distance.
I've done the audio fixes described on the README and on some the issues here and I have my volume controls + headphones working (mic doesn't work but I don't really care).
For the noise I've tried:

lowering volumes/muting on alsamixer;
the modprobe model fix (and turing off power save);
fiddling with the conf files on .config/wirepumber;
reinstalling Arch and Fedora 40 (both on Pipewire and GNOME if that matters).

This happens on a clean install so it's not like any of the fixes are causing it.
Wondering if there's anything else that could be done about that?

If the noise happens even with speaker muted etc it's not the speakers. I'm pretty sure that's just coil while from other internal components which will pretty much always happen with the device powered on.


Fix TypeError when missing metadata

Fix issue when having meetings created with missing metadata fields, for example created by the following ILIAS Plugin https://sourceforge.net/projects/bigbluebuttonil/.

Thanks!


Free allocated memory in all return paths

avoid memory leak in c_read, c_http_server_read and c_http_client_read from memory allocated by go_str function
fix 93acf4d
[ ] Required #913

Great finds, now included in #913. Closing.


fixRecord return row count in audit log for internal query. (#39616)

backport: https://github.com/apache/doris/pull/39616

run buildall


[BUG] unable to use THORChain swap route

Describe the bug
It is impossible to use THORChain swap route due to a transaction hash error
To Reproduce
Steps to reproduce the behavior:

Select a Thorchain swap route
sign the swap
See error

Expected behavior
Able to swap over Thorchain
Screenshots

Desktop (please complete the following information):

Version 1.0.8

Hi there,
We use GitHub issues as a place to track bugs and other development-related issues.
Please see the link below to our dedicated support line: Help Center : Click Here
Ticket ID: FN1506
Note: Click on the live chat icon at the bottom corner of the page to start a conversation


Make JSON streaming API more flexible

First of all, the high level goal is to reduce memory when serving large amounts of data that comes from a database and gets serialized to JSON. There may be a better way to achieve this than what I suggest here.
My proposal is to change the JsonMapper interface such that an implementation can have more control of all the resources necessary to pull off a reduced-memory mapping for any situation. Specifically, if the OutputStream for the HTTP request were exposed by the API, then I could write my own variant of JavalinJackson() to stream according to our setup (or perhaps that code could be generalized enough to be added to JavalinJackson directly.) In addition to having access to the OutputStream, the API would also need to signal to Javalin who is responsible for writing the output.
A proposal is made at the end of all the background info that follows. It would add a function to JsonMapper.

Example working code, but as an extension function
I will show my workaround code, which should illustrate what we might want to see in the JsonMapper API. In my example we're using JDBI for the database, and Jackson for JSON serialization.
From our database, JDBI lets us reduce memory by returning a Stream<T> of objects. And Jackson allows us to use a SequenceWriter to iteratively consume a Stream<T> and map the JSON objects to an OutputStream.
Here's a Context extension function that does this and works correctly:
fun Context.streamToJson(stream: Stream<*>) = this.apply {
    contentType(ContentType.APPLICATION_JSON)
    val mapper = defaultObjectMapper // our ObjectMapper, same one that I passed to Javalin as a JavalinJackson() config
    mapper.writer().writeValues(outputStream()).use { sequenceWriter ->
        sequenceWriter.init(true) // wrapInArray=true, a Stream<T> of data implies an array in the JSON output
        stream.forEach { sequenceWriter.write(it) }
    }
}

This function is utilized inside a lambda such that the database and stream resources are kept alive until the lambda completes. The controller code looks like this:
fun getElephants(ctx: Context) {
    daoBigStuff.getAllElephants { stream ->
        ctx.streamToJson(stream)
    }
}

And the database call looks like:
typealias JsonStreamer<T> = (stream: Stream<T>) -> Unit

fun getAllElephants(streamer: JsonStreamer<Elephant>) {
    db.jdbi.open().use { handle ->
        handle.createQuery("select * from elephant")
            .mapTo(Elephant::class.java)
            .stream()
            .use {
                streamer.invoke(it)
            }
    }
}

Abstraction of the JSON provider
All of the above works, but it seems that the correct place for the Jackson specific code should be inside JavalinJackson(), or my own implementation of JsonMapper if need be.
The existing function ctx.jsonStream()
Here's why the existing function doesn't work. A call to ctx.jsonStream() ends up calling JavalinJackson.toJsonStream(), which creates an intermediate OutputStream to hand to Jackson. Then it starts up a separate thread to drive Jackson's output into an InputStream for the JsonMapper interface to consume.
That extra thread is a problem because the original thread's call to toJsonStream() will return right away, and that causes the JDBI try-with-resources to close the stream before Jackson can do anything with it in the new thread.
Why the thread?
I suspect it is to keep everything oriented in one direction (in this case "consume") to make the request lifecycle code straight forward. All of the "outbound" functions in the JsonMapper interface (toJsonString() and toJsonStream() have a "consuming" orientation -- you are expected to produce a String or an InputStream. In the JavalinJackson implementation, the Jackson output stream gets piped to an input stream by that thread.
Who is responsible for putting the JSON on the output stream?
The "consume" orientation of the JsonMapper interface also implies that Javalin is responsible for delivering the output.
If we change the API such that an implementation of JsonMapper can write the output directly, then Javalin will need to know that it is no longer responsible to write anything.
Proposed function
Perhaps adding this single function can communicate who is responsible for the output, and provide the output stream to the JsonMapper implementer:
interface JsonMapper {
      :
      :

    fun handleOutputStream(outputStream: OutputStream, obj: Any, type: Type): Boolean = false

      :
      :
}

The code behind ctx.jsonStream() would call handleOutputStream() first, and if it returns false, then continue the way it always does. But if it gets back true, then the implementation of JsonMapper has taken responsibility of sending out the results. Of course the JsonMapper implementation can check obj to be type Stream or Iterator or whatever it may expect to handle, or decide to pass.

Here's what that code change would look like: https://github.com/bseib/javalin/pull/1
No tests yet... I am having trouble getting my machine setup to do maven's test suite against master, so I'll have to come back to that.

Here is a related issue which led to the implementation of the current method: https://github.com/javalin/javalin/issues/1285

For direct and blocking write operations like this, where the method itself is writing, we have used writeSeekableStream, I guess we could call this writeJsonStream.
The SeekableWriter also wraps the operation in ctx.async{} in order to prevent blocking the thread, which may or may not be desirable here.
Have you thought about compression? (GZIP/Brotli)

The phrase "JSON Streaming"
Interesting stuff WRT x-json-stream, the phrase "JSON Streaming", and all the variations on concatenating chunks of JSON in a single response. If I were in that situation, I'd wrap those separate chunks (whether homogenous or heterogeneous data) inside a single uber-JSON structure such that the whole thing is still a valid application/json content type.
If anything, I should be careful here with what I call "JSON Streaming" when the rest of the world might have a slightly different idea of what that phrase means.
To be clear, I meant my "JSON Streaming" phrase be a conventional HTTP request that returns an application/json content-type, BUT not store the entire data (twice) in memory. (Twice because the entire SQL response would be stored in memory first, then the entire JSON structure could be built in memory before sending.)
writeSeekableStream
Are you suggesting an addition function named writeJsonStream that would live next to writeSeekableStream in Context.kt?
I'm thinking that the correct place for this code would be inside JavalinJackson, and from there we have access to our objectMapper, and we're implementing JsonMapper to communicate back to Javalin. But we don't currently have access to ctx.writeSeekableStream() (or  ctx.writeJsonStream()) in there.
With respect to being seekable and range related headers, a reduced-memory construction of JSON like this is NOT really seekable, so we don't want an Accept-Ranges header at all. The async behavior in this fn doesn't help either -- see next.
ctx.async{} or anything threaded
Anything with a separate thread would kill my proposed code, which uses a simple lambda to solve the try-with-resources ownership problem. I could explore if there are other ways of keeping my database's try-with-resources alive in one thread until another thread is done consuming it to convert to JSON. But my "keep it simple" instincts don't like that idea. 😅
Compression

Have you thought about compression? (GZIP/Brotli)

In my draft code for Context.kt, I used outputStream() instead of req().outputStream(), so that it uses the compressed instead of the raw output stream. It's subtle, so it probably deserves a comment in the code.

This will be mostly unrelated to writeSeekableStream, it's just that the name should indicate that this method writes directly.

Agreed that a function name like writeJsonStream() conveys who's responsible to do the writing and is aligned in that manner with writeSeekableStream.

Fair enough, I am guessing you're not doing this because requests are very slow, only to decrease memory usage. The user could always call async manually, if they wish.

Yeah, for our situation it was a memory issue that ultimately made its docker container die, and kubernetes having to spin up a new one. The user's experience was a dropped connection when the container died. Now memory consumption is basically a constant for each request regardless of how many rows of data are coming back from the db. In fact, I think this is good memory hygiene in general, and I've converted a significant number our data calls to take this approach.

Nice, sounds like we have a plan then, feel free to submit a PR 😊

Nice, sounds like we have a plan then, feel free to submit a PR 😊

Okay, good. I have the bits and pieces on a branch, but I'm not sure what's up with my windows box not cooperating with running maven tests. I may just move to another machine to try it there...

t I'm not sure what's up with my windows box not cooperating with running maven tests. I may just move to another machine to try it there...

I do 50/50 on Windows and macOS, and I haven't run into any issues. Are you using the Maven Wrapper? Or just Maven? Or IntelliJ?

I just checked out latest master branch at fc7e7deb14, and I ran ./mvnw test (from a gitbash terminal) and got the following error. I haven't spent any time to investigate. 😦
$ ./mvnw test
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Javalin (parent)                                                   [pom]
[INFO] javalin                                                            [jar]
[INFO] javalin-testtools                                                  [jar]
[INFO] javalin-micrometer                                                 [jar]
[INFO] javalin-bundle                                                     [jar]
[INFO]
[INFO] ---------------------< io.javalin:javalin-parent >----------------------
[INFO] Building Javalin (parent) 5.3.3-SNAPSHOT                           [1/5]
[INFO] --------------------------------[ pom ]---------------------------------
[INFO]
[INFO] --- maven-enforcer-plugin:3.1.0:enforce (enforce-maven) @ javalin-parent ---
[INFO]
[INFO] --- maven-resources-plugin:3.2.0:copy-resources (copy-license) @ javalin-parent ---
[INFO] Skipping the execution.
[INFO]
[INFO] --- maven-resources-plugin:3.2.0:copy-resources (copy-pom-properties) @ javalin-parent ---
[INFO] Skipping the execution.
[INFO]
[INFO] --- kotlin-maven-plugin:1.7.10:compile (compile) @ javalin-parent ---
[WARNING] No sources found skipping Kotlin compile
[INFO]
[INFO] --- maven-compiler-plugin:3.10.1:compile (java-compile) @ javalin-parent ---
[INFO] No sources to compile
[INFO]
[INFO] --- kotlin-maven-plugin:1.7.10:test-compile (test-compile) @ javalin-parent ---
[WARNING] No sources found skipping Kotlin compile
[INFO]
[INFO] --- maven-compiler-plugin:3.10.1:testCompile (java-test-compile) @ javalin-parent ---
[INFO] No sources to compile
[INFO]
[INFO] -------------------------< io.javalin:javalin >-------------------------
[INFO] Building javalin 5.3.3-SNAPSHOT                                    [2/5]
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-enforcer-plugin:3.1.0:enforce (enforce-maven) @ javalin ---
[INFO]
[INFO] --- maven-resources-plugin:3.2.0:copy-resources (copy-license) @ javalin ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-resources-plugin:3.2.0:copy-resources (copy-pom-properties) @ javalin ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @ javalin ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] Copying 1 resource
[INFO]
[INFO] --- kotlin-maven-plugin:1.7.10:compile (compile) @ javalin ---
[WARNING] Source root doesn't exist: C:\git\javalin\javalin\src\main\kotlin
[WARNING] Using experimental Kotlin incremental compilation
[INFO] Compiled 0 Kotlin files using incremental compiler
[INFO]
[INFO] --- maven-compiler-plugin:3.10.1:compile (java-compile) @ javalin ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources) @ javalin ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] Copying 38 resources
[INFO]
[INFO] --- kotlin-maven-plugin:1.7.10:test-compile (test-compile) @ javalin ---
[WARNING] Using experimental Kotlin incremental compilation
[INFO] Compiled 0 Kotlin files using incremental compiler
[INFO]
[INFO] --- maven-compiler-plugin:3.10.1:testCompile (java-test-compile) @ javalin ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 33 source files to C:\git\javalin\javalin\target\test-classes
[INFO] /C:/git/javalin/javalin/src/test/java/io/javalin/examples/HelloWorldStaticFiles_linked.java: C:\git\javalin\javalin\src\test\
java\io\javalin\examples\HelloWorldStaticFiles_linked.java uses or overrides a deprecated API.
[INFO] /C:/git/javalin/javalin/src/test/java/io/javalin/examples/HelloWorldStaticFiles_linked.java: Recompile with -Xlint:deprecatio
n for details.
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M7:test (default-test) @ javalin ---
[INFO] Using auto detected provider org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
[INFO]
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[ERROR] TestEngine with ID 'junit-jupiter' failed to discover tests
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Javalin (parent) 5.3.3-SNAPSHOT:
[INFO]
[INFO] Javalin (parent) ................................... SUCCESS [  2.290 s]
[INFO] javalin ............................................ FAILURE [ 12.199 s]
[INFO] javalin-testtools .................................. SKIPPED
[INFO] javalin-micrometer ................................. SKIPPED
[INFO] javalin-bundle ..................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  14.717 s
[INFO] Finished at: 2023-01-30T13:34:44-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M7:test (default-test) on project javalin:
[ERROR]
[ERROR] Please refer to C:\git\javalin\javalin\target\surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] There was an error in the forked process
[ERROR] TestEngine with ID 'junit-jupiter' failed to discover tests
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: There was an error in the forked process
[ERROR] TestEngine with ID 'junit-jupiter' failed to discover tests
[ERROR]         at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:701)
[ERROR]         at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:311)
[ERROR]         at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:268)
[ERROR]         at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1334)
[ERROR]         at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:
1167)
[ERROR]         at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:931)
[ERROR]         at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
[ERROR]         at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2(MojoExecutor.java:370)
[ERROR]         at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute(MojoExecutor.java:351)
[ERROR]         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:215)
[ERROR]         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:171)
[ERROR]         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:163)
[ERROR]         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
[ERROR]         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
[ERROR]         at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java
:56)
[ERROR]         at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
[ERROR]         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:294)
[ERROR]         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
[ERROR]         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
[ERROR]         at org.apache.maven.cli.MavenCli.execute(MavenCli.java:960)
[ERROR]         at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:293)
[ERROR]         at org.apache.maven.cli.MavenCli.main(MavenCli.java:196)
[ERROR]         at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR]         at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR]         at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR]         at java.base/java.lang.reflect.Method.invoke(Method.java:566)
[ERROR]         at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
[ERROR]         at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
[ERROR]         at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
[ERROR]         at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
[ERROR]         at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR]         at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR]         at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR]         at java.base/java.lang.reflect.Method.invoke(Method.java:566)
[ERROR]         at org.apache.maven.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:53)
[ERROR]         at org.apache.maven.wrapper.WrapperExecutor.execute(WrapperExecutor.java:152)
[ERROR]         at org.apache.maven.wrapper.MavenWrapperMain.main(MavenWrapperMain.java:76)
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :javalin

I do use IntelliJ for me IDE too...

Are you able to run the tests from IntelliJ?

I get the same error:

Here is how I invoked the tests, in case I did something wrong. (I'm from gradle world and less familiar with maven, esp in the IDE...)

This weekend I'll be on a Mac I can try it on.

Try running the tests inside the javalin module, not the project parent.

 Sorry for the noise. I hope to work on a PR this weekend.

Not your fault, Maven is pretty primitive tool and it doesn't work that well with Kotlin & IntelliJ, so you may experience random issues - clean just wipes it out and rebuilds everything from scratch, I know from my experience :P

@tipsy and @dzikoysk I'm looking for some feedback before I start writing unit tests. See my comment here: https://github.com/bseib/javalin/pull/1/files#r1096578337

Also, is it okay if I were to push a work in progress PR to this repo (rather than my own) to get feedback? Or do you want more "complete" PRs only? Or don't care... ? 🤷♂

Question for you @tipsy -- I notice when I push to my PR, the automated tests spin up. On an average month, do you cross the billing threshold for using github actions and get billed?

Also, is it okay if I were to push a work in progress PR to this repo (rather than my own) to get feedback? Or do you want more "complete" PRs only? Or don't care... ? 🤷♂

It's very okay, I prefer that all PRs make it to this repo as soon as possible, so people can see what's up 😊

Question for you @tipsy -- I notice when I push to my PR, the automated tests spin up. On an average month, do you cross the billing threshold for using github actions and get billed?

What now? I don't think so, but where can I check this? 😅

It's very okay, I prefer that all PRs make it to this repo as soon as possible, so people can see what's up 😊

Okay good, I just opened my work in progress at https://github.com/javalin/javalin/pull/1813

Question for you @tipsy -- I notice when I push to my PR, the automated tests spin up. On an average month, do you cross the billing threshold for using github actions and get billed?

What now? I don't think so, but where can I check this? 😅

Here's how I saw this:

I forked javalin/javain --> bseib/javalin
I pushed some code and opened a PR on my own repo
The PR spins up the "Test all JDKs on all OSes" when it is opened, and again whenever I push to that branch of the open PR.

The bottom section of my PR looks like:

Or I can see the details of all this under the "Checks" tab in my PR:

When I just opened my PR #1813 on this repo, it spins up these checks too:

That part I get, but I didn't know there was a billing threshold.

Oh my mistake, you're right about actions being free for public repos:

GitHub Actions usage is free for standard GitHub-hosted runners in public repositories


Not loading commands from app_root folder

Commands from /app/commands aren't being loaded. The "app_root" property of runaway-config.json is not being taken into consideration for loading up command files.

So I'm curious how your project is setup? What runway does is it scans all these directories to try and find where your commands are. Let me know which one you are expecting it to be in and maybe I can help from there.

@n0nag0n I think the issue is that in those paths, it doesn't consider app_root from $config, it just checks DIR etc. Could we have it use that value?
I would also consider the wording to take on "command" and "commands" as some project use singular phrasing :)

So app root is actually specified in each of the commands that you want to run. For example in the ControllerCommand in the core repo, you can see that it's used here. I didn't include it in the base because some commands don't need the app root.
https://github.com/flightphp/core/blob/master/flight/commands/ControllerCommand.php#L32-L41

And with the comment about command vs commands, the other directories in the skeleton are all plural for scaling reasons. Yes you may only have one command in there, but as projects grow, you'll likely add some additional commands and as soon as you do, you'll now have the command/ folder with multiple commands in there. If you want to refactor it, and depending on how you setup your namespaces and such, you could unintentionally introduce a bug into your project. I would just leave it plural and wait for your project to become so awesome that you plan on making another command in the future!

So, it is misleading as "app root" sounds like where all the controllers, commands, services, etc, are located.
I think the problem here is:
There is no way to specify the commands directory.
The solution could be:

Use app_root (like my PR)
Add another option to the configuration

I guess it would help me to understand a) where you are running php runway (like your project root or from a random place in your server/vm/environment) and b) where your app root is and what it's defined as. The code I shared earlier, specifically https://github.com/flightphp/runway/blob/master/runway#L30 would hit your commands folder just fine if your commands are in projectroot/app/commands/. The only variable is the current working directory changes depending on where you run the runway command.
app_root is specifically for actions like creating new controllers, active record models, etc.
I suppose I could see the error if you are trying to run php vendor/bin/runway and you're trying to hit your app directory. I think that might need to be changed in the paths to search.
Btw, I saw your PR, and it could be added, but I would need to make some changes because as of right now it would throw notices if $config['app_root'] happened to not be defined in a project.

I had some time tonight, what do you think of this pull? Should include everything that you were talking about https://github.com/flightphp/runway/pull/5

I haven't had a chance to test it out but from a read over it looks good to me!

Hey guys, sorry for the late reply.
What I did basically was to create a new project using composer
create-project flightphp/skeleton cool-project-name . You'll notice the
"commands" folder is created inside the "app" subdirectory. Then I started
to create my commands inside that folder and noticed they didn't work as
expected, even though .runway-config.json had the right app_root attribute.
In my case, I did the following modification to the runway.php (mostly
because my commands have different namespace then flight\commands:
$addedCommands = [];
foreach($paths as $path) {
foreach(glob($path) as $commandPath) {
if(basename($commandPath) === 'AbstractBaseCommand.php') {
continue;
}
if (preg_match('/Command.php$/', $commandPath) === 0) {
continue;
}
// $command = str_replace('.php', '', basename($commandPath));
// $command = 'flight\commands\'.$command;
$namespace = preg_match('/namespace (.*);/', file_get_contents($commandPath),
$matches)
? $matches[1]
: 'flight\commands';
$command = $namespace.'\'.str_replace('.php', '', basename($commandPath));
if(in_array($command, $addedCommands, true) === true) {
continue;
}
$addedCommands[] = $command;
require_once $commandPath;
$consoleApp->add(new $command($config));
}
}
I also added $cwd.'/app/commands/.php' into $paths array (as I was in a
hurry), but the folder coming from "app_root" attribute from
runway-config.json should also be considered.
On Fri, 27 Sept 2024 at 03:51, Mark Hughes @.**> wrote:

I haven't had a chance to test it out but from a read over it looks good
to me!
—
Reply to this email directly, view it on GitHub
https://github.com/flightphp/runway/issues/3#issuecomment-2378248283,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRHMAVUEMPFAIPVYPQLEJDZYS2ZBAVCNFSM6AAAAABOHQ47YCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZYGI2DQMRYGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

ahh the OG speaks! This is helpful. So with the changes I've done this should also help out. But you do bring up a point that other namespaces need to be considered as well.
I added the ability for it to dynamically find the namespaces and added a while bunch of config options you can just add in via the config file now.
https://github.com/flightphp/runway/releases/tag/v1.1.0
Let me know if this fixes your issues.


Add suport for codec in socket output

Allows defining own message delimiter for the socket output.
The default is \n so this shouldn't break anything for existing users.
Also added new tests to check for the correct behavior

Hey @DeeJayBro, I'm trying to migrate stream outputs to use codecs instead, could you copy the way that the file output works: https://github.com/Jeffail/benthos/blob/master/lib/output/file.go, ignore the delim field there as it's just for backwards compatibility.

@Jeffail Should I just ignore the append/truncate specific fields?

Migrated to Codec System

Looks good, thanks @DeeJayBro!


added and patched more metadata to the js file

all variable metadata from cmip6 (from json files)

@antarcticrainforest , I also added cmor_table metadata and added that to the index so it shows it at the web.


⚠ AVS (kty) has degraded performance

In e797cc8, AVS (kty) (https://avus.com.br) experienced degraded performance:

HTTP code: 200
Response time: 8048 ms

Resolved: AVS (kty) performance has improved in 97b69c5.


Encountered error while running ManifestTool generation workflow.

ENV: Ubuntu-20.04
Encountered error while running ManifestTool generation workflow. Error: Unable to load shared library 'MonoPosixHelper' or one of its dependencies. In order to help diagnose loading problems, consider setting the LD_DEBUG environment variable: libMonoPosixHelper: cannot open shared object file: No such file or directory
The same environment, when I used sbom-tool v0.1.13 to scan source code, it can generate sbom file correctly. But, it encountered the error above when I use sbom-tool v0.2.0. How to fix it?  The command is as follows:
salus Generate -b ./test -bc ./test -di test:latest -pn Test -pv 0.0.1 -nsb https://test.com/ -V Verbose -m .

sorry, the command is below:
salus Generate -b ./test -bc ./test -pn Test -pv 0.0.1 -nsb https://test.com/ -V Verbose -m .

Get this package installed to your Linux distribution
https://www.mono-project.com/download/stable/#download-lin

Hi @newertp - I just checked and looks like the newer version has some issues and I have rolled back the change. Please continue to use v0.1.13 for now, as we put out a fix to the new version, thanks.


Non symmetric dist

Going over the tests now. @mariamasotti1 what was the reasoning for adding the varargs (...) to various calls? This seems to be the cause of at least some of the failing tests


Added the URL input type.

Updated the forms (and navbar) to support the URL input type.

Thank you!


Add IO operations "from/load" to the LazyFrame implementation

This is related to #227
In the first PR for that issue, #202, we discussed a possible lazy: true option to control which backend to use. I end up using both :backend and :lazy to make it easier for clients to choose the backend. This adds the possibility for a backend to be implemented both using an eager (the default) and lazy version. WDYT?
I also choose to "delegate" the load of binaries to the eager implementation, and then converting it to lazy. This is mostly for convenience, because there is not such loaders in the Polars backend.

I love the direction. Definitely like having both :backend and :lazy opts. Yeah I think that also makes sense regarding loading binaries. It's in memory already anyway so you don't lose much compared to loading from file. Definitely should document that clearly though.

Definitely should document that clearly though.

@cigrainger You mean about the :lazy option or the usage of the eager by the load_ functions?
Anyway, I'm going to add documentation in a future PR.


DM-35580: Pin photutils to <1.5.

photutils 1.5.0 enforces an odd-sized filter, causing failures in the
Spectractor tests.  Pin it back for now until the code can be fixed.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender


How to change the default anim to something less cartoonish

The default animation is very cartoonish. Was this ever critiqued at by a designer? The docs don't mention how to change it. If it's not possible to modify the animation to make it less cartoonish, then this severely limits the usefulness of the library.

I believe this "cartoonish" animation was definitely "critiqued" by the designers and then well documented on the Google Material Design website. As you can see in the index.css file, almost all sizing and animation properties have references to where these settings were taken from:
  /*
    * Exits and closing:
    * A navigation drawer opens over 250ms but closes over 200ms.
    * @see https://material.io/design/motion/speed.html#duration
    *
    * Accelerated easing:
    * Elements exiting a screen use accelerated easing, a transition in which
    * the element starts at rest and ends at peak velocity.
    * @see https://material.io/design/motion/speed.html#easing
    *
    * Decelerated easing:
    * Incoming elements are animated using decelerated easing, in which
    * transitions begin at peak velocity (the fastest point in an element's
    * movement) and end at rest.
    * @see https://material.io/design/motion/speed.html#easing
    *
    * Scrim color opacity: 32% (1 - 0.32 = 0.68)
    * @see https://material.io/components/navigation-drawer#theming
    */

Answering to your question how to change the default animation, use plain css with the same class names and css selectors, just like you would change other third party components in your application. In this particular case, you need to override the following property:
.HamburgerDrawer .HamburgerDrawer-panel {
  transition: transform 200ms cubic-bezier(0.4, 0, 1, 1), visibility 1s linear;
}

Hope this helps.


Sphinx Python Documentation

Add support for the generation of Sphinx documentation for MaterialX Python, using the approach described here:
https://pybind11.readthedocs.io/en/stable/advanced/misc.html#generating-documentation-using-sphinx

I'd like to take a stab at this for the ASWF Dev Days 2023.
If I’m understanding this right, the work here roughly consists of two parts:

Integrating a Sphinx build of the MaterialX Python API documentation into the MaterialX CMake build
Adding/extending docstrings for MaterialX Python bindings using pybind11

While it may not be possible/feasible to add/curate docstrings for all MaterialX Python bindings during Dev Days, it should be possible to lay the foundation for building API documentation using Sphinx on the day.
Proposed approach/outcome:

An optional extra build target similar to the existing cmake --build . --target MaterialXDocs (which uses doxygen to generate C++ API documentation), possibly named MaterialXDocsPython.
Documentation in HTML format that is generated in a sibling folder next to the existing C++ API documentation (as opposed to living in the same html folder).

Proposed artifacts:

A new CMake module at cmake/modules/FindSphinx.cmake to be able to find the sphinx-build executable (Windows: sphinx-build.exe) from documents/CMakeLists.txt using find_package(Sphinx).

cf. https://eb2.co/blog/2012/03/sphinx-and-cmake-beautiful-documentation-for-c-projects/
cf. https://www.vortech.nl/en/integrating-sphinx-in-cmake/

Modifications to documents/CMakeLists.txt to create a new build target named MaterialXDocsPython, which would run sphinx-build to generate Python API developer documentation, in a directory that is separate to the existing doxygen-generated html documentation, e.g. named html-sphinx.

https://www.sphinx-doc.org/en/master/tutorial/getting-started.html

A Sphinx configuration template file (e.g. documents/sphinx-conf.py.in) that would be filled with values of configuration variables like MATERIALX_LIBRARY_VERSION as part of the build, in order to generate the conf.py file that sphinx-build uses.

This would be similar to the existing developer/Doxyfile.in from which documents/CMakeLists.txt generates Doxyfile for configuring the doxygen run.
https://www.sphinx-doc.org/en/master/usage/configuration.html

Integration of existing developer guide contents in Markdown format from documents/DeveloperGuide/ into the Sphinx-generated Python API documentation, e.g. using the myst_parser extension:

https://www.sphinx-doc.org/en/master/usage/markdown.html
GraphEditor.md
MainPage.md
ShaderGeneration.md
Viewer.md

A new paragraph in the Building API Documentation section in documents/DeveloperGuide/MainPage.md to describe how to build the Python API documentation using Sphinx.
Integration of docstrings from MaterialX Python bindings that are defined in source/PyMaterialX/ from compiled Python C extensions, e.g. from lib/PyMaterialXCore.cpython-312-darwin.so etc.

PyMaterialXCore/
PyMaterialXFormat/
PyMaterialXGenGlsl/
PyMaterialXGenMdl/
PyMaterialXGenMsl/
PyMaterialXGenOsl/
PyMaterialXGenShader/
PyMaterialXRender/
PyMaterialXRenderGlsl/
PyMaterialXRenderMsl/
PyMaterialXRenderOsl/

I'd like to continue our work on this from last year’s ASWF Dev Days next week:
https://github.com/AcademySoftwareFoundation/MaterialX/pull/1567


Delete selected row using DELETE key (instead of del button on each line) ?

    ShortcutListener OnDeleteKeyPressed =
    new ShortcutListener("", KeyCode.DELETE, new int[10])
    {
        @Override
        public void handleAction(Object sender, Object target)
        {
            if(getKeyCode()==KeyCode.DELETE)
            {

                Set<SomeBean> selection = [enclosing grid lass].this.getSelectedItems();
                if( selection!=null && !selection.isEmpty() )
                    Notification.show("DELETE:\n" + selection);
            }
        }
    };
    // Route the DEL key
    addShortcutListener(OnDeleteKeyPressed);

If the field in the first column is TextField, ComboBox or DateField, the Delete Key will open the Editor and clear the field.
Is your idea, that there would be a method in the extension where you can define the Delete key behavior. I.e. 1. the the current behavior or 2. delete the row?


Add logs when tracing information is not propagated

Pull Request Test Coverage Report for Build 197

7 of 9 (77.78%)  changed or added relevant lines in 3 files are covered.
16 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.02%) to 73.327%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/client.go
0
1
0.0%

internal/internal_worker.go
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

internal/internal_task_pollers.go
2
72.68%

internal/internal_activity.go
3
72.0%

internal/internal_utils.go
11
89.44%

Totals

Change from base Build 193:
-0.02%

Covered Lines:
8187

Relevant Lines:
11165

💛  - Coveralls


Survey Form using HTML

Assign me with this task under hacktoberfest

Please add description and images of the changes.

Can you pls assign me this issue?

This survey form will contain a survey of the page. In this we basically take a survey of the user of how frndly this site is for them.
A survey option will be displayed on the site which would be helpful for us to make the site more user frndly. I am attaching the image in the following comment.

Pls assign me this task under hacktoberfest

@prajaviS please create a PR. I'm assigning you the issue.


Make graph filters a popup

Currently the filters are an embedded button above the graph on mobile.
We should move the toggle to become a sticky button on the bottom of the viewport so that it's visually present and moves the graph up above the fold.
When clicked the filters can become a modal that completely takes over the viewport

Love this idea.


Feature: Add Groups of worlds or "world sets"

Hello,
I'd like to request that you add groups of worlds.
When I am trying to have a permission apply on a specific set of worlds (Not globally) I have to duplicate the permission node in the editor 4 times for each world.
Can you add it so you can (in config.yml) set multiple "sets" of worlds. You would be able to have a permission's world as the name of a "world set" you have configured and the set would refer to multiple other worlds it would then take only one permission node to apply to multiple worlds.
Thanks.

Just create a group and apply the permissions to it.
Then you can add or set the group to the user in a specific world using /lp user <user> parent add/set <group> world=<world>

Please read what I wrote, that isn't what I'm talking about.
On Sun, Jun 17, 2018, 3:20 AM Andre_601<EMAIL_ADDRESS>wrote:

Just create a group and apply the permissions to it.
Then you can add or set the group to the user in a specific world using /lp
user  parent add/set  world=
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lucko/LuckPerms/issues/1055#issuecomment-397862774,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKvJUlTveFyxIkuefErp1mBHbOi4U3g8ks5t9hExgaJpZM4UqtqP
.

You can use the world rewrite settings to achieve a similar outcome
https://github.com/lucko/LuckPerms/blob/957a918bd6aa315b5cda8a9df7f7124aa3124aee/bukkit/src/main/resources/config.yml#L425-L431


Web implementation does not handle dark mode gracefully

I think this can be addressed with dark mode CSS properties here:
https://github.com/PolyMeilex/rfd/blob/master/src/backend/wasm/style.css

Not today, but I can take a look into making these changes in the near future if nobody gets to it first

Or this could be fixed by https://github.com/PolyMeilex/rfd/pull/129

Does this do the trick: https://github.com/PolyMeilex/rfd/pull/170 ?


feat(sheets-data-validation): support dropdown filter & fix paste error on data-validation cell

close https://github.com/dream-num/univer/issues/2974
close https://github.com/dream-num/univer/issues/2986

Pull Request Checklist

[ ] Related tickets or issues have been linked in the PR description (or missing issue).
[ ] Naming convention is followed (do please check it especially when you created new plugins, commands and resources).
[ ] Unit tests have been added for the changes (if applicable).
[ ] Breaking changes have been documented (or no breaking changes introduced in this PR).

https://github.com/dream-num/univer/issues/29
问题1：
模糊搜索需要区分大小写
问题2：
输入非首位字符时，无法搜索到选项


RAC-5946:   add NPM  Publish.groovy

It will become a template for docker/ova/vagrant publish codes'  template.
it's unit-tested.
@PengTian0  to review.
Explanation:
I put all groovy variable on the top of SH script, because it's easier for migration in the future . so that we can just replace the groovy variable on the top to other inputs.

👍


Predictkube

Signed-off-by: Jorge Turrado<EMAIL_ADDRESS>Provide a description of what has been changed
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO)

Related to https://github.com/kedacore/keda/issues/2800
Related to https://github.com/kedacore/keda/pull/3429

Would you mind rebasing and providing a more clear PR title / description to clarify the intent please?

lol, What have I done? 🤦
Sure, let me put it well...

There was another branch (created by me, surely by error) in this repo named exactly equal to my branch in my fork, that has produced a wrong behaviour opening the PR. I have created another PR with the correct changes.
Good catch


\mathbf and \imath, \jmath

MathJax does not math-bold \imath or \jmath.

That is correct, because that is also what LaTeX does.  You need to use \boldsymbol{\imath} for a bold version of \imath.  If you want a roman (rather than italic) dotless i, even in LaTeX that takes some work.  In MathJax, you could use \mmlToken{mi}[mathvariant="bold"]{ı}, but only if you are using the STIX fonts (as the required character isn't in the MathJax TeX fonts).

Wow! It seems that if you use STIX fonts, it is automatically roman
(even with $\mathbf{imath}$)
I never guessed that STIX fonts would render that differently.

It seems that if you use STIX fonts, it is automatically roman (even with \mathbf{math})

That should not be the case, and I can't reproduce it.  Here is what I get for
\imath\mathbf{\imath}\boldsymbol{\imath}\\
\mmlToken{mi}[mathvariant="normal"]{ı}\mmlToken{mi}[mathvariant="bold"]{ı}

using the STIX fonts:

Ok. This somewhat weird: With the attached files, I seem to be getting different behavior.
If you can confirm your behavior with my file, then I must simply have out-of-date software.
imath.pdf

Sorry, it's miscommunication.  When I said use the STIX fonts, I was talking about in MathJax, not LaTeX, and my example above with the image is for MathJax as well.  It looks like the stix package in LaTeX alters things so that \mathbf does affect \imath.  That isn't the case in MathJax.


Replace the old GIF in the README

Describe the feature
In our README, there is a GIF of the project's website. We would like to replace this GIF with a better-quality one. Also, the website has been updated with minor changes and we would like to show it off as well.
What should happen while recording the GIF

Change the title to Demo Website
Choose a nice dark theme from the drop-down menu
Add one or two badges (it's the little + below the Line 1 )
Click on the Generate button and wait until the preview changes. Make sure you wait 0.5-1 second after the card has generated itself so we can see the result.

Of course, you can include more actions to show off the site's features.
Checklist

[ ] In the README, the old GIF is replaced with the new one and is exactly in the same position.
[ ] The GIF is uploaded to the docs/ folder and referenced from there in the README.
[ ] The GIF is cropped so that only the main content of the page is visible.
[ ] The GIF is high quality and everything is clearly readable.

Additional context

We are open to any ideas. Feel free to make suggestions in the comments section or by opening a new topic.
If you want to start working on this task, please write a comment so I can assign you this issue.

Thank you! Made the update and created PR


Add first version of iOS build script

Adds first version of iOS build script that includes only csrc files with no third party dependencies.
Sample run command:
LIBTORCH_HEADER_ROOT="/path/LibTorch-Lite/install/include" IOS_ARCH="x86_64" ./build_ios.sh

HI @hwangjeff  . Looks good. May I ask, please put in the description the list of artifacts that will be generated by this script and a small note how do we plan on distributing these binaries ?


Allow setting no_ping and if sending a ping send it of the right type

the kind:ping causes slack to constantly respond with an invalid message type now.   Also allow disabling the ping in case the user wants to handle it on their own.

Plus one, I updated SlackBots and suddenly started getting error messages all over.
I've rolled my own ping a long time ago, so being able to disable the built-in ping would be really nice.


Two issues: Error while installing datamule[all] and importing datamule after installing the basic package

Two issues:

Unable to install datamule[all]
`python -m pip install datamule[all]

zsh: no matches found: datamule[all]`

After successfully installing the basic version (pip install datamule), getting the following error when trying to import datamule:
`>>> import datamule as dm

Traceback (most recent call last):
File "", line 1, in
import datamule as dm
File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/datamule/init.py", line 21, in
from .sec_downloader import Downloader
File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/datamule/sec_downloader.py", line 14, in
from pkg_resources import resource_filename
ModuleNotFoundError: No module named 'pkg_resources'`

Gotcha. Just pushed a patch that should fix your error. What IDE are you using? (e.g. vscode, colab,..)
For 1. I think the command for shell is  python -m pip install "datamule[all]" . (I use command prompt)

I think the issue was that setuptools was not declared as a requirement in the datamule setup.py, which works for most environments but not yours.

Hello John,
Thank you for your quick reply, guidance, and contribution to the community.
I am using command prompt on a Mac as well. The quotes "datamule[all]" did the trick.
I guess that the [all] option also installs setuptools (?), as when I tried installing setuptools, I got a prompt that the 'requirements were already satisfied'.
I look forward to using datamule!
P.S. Now off to figure out how to rename the files to reflect ticker/cik + Year and then extract the required information :)

Something that may be useful for you to know is that accension number is cik - year - number of filings. So<PHONE_NUMBER>15118890 is cik<PHONE_NUMBER> year 2015. Using packages company tickers data with accession number cik should work for your case.
Btw, what data are you trying to extract?

Thanks you, John. I sent you a Linkedin request. May be we could chat there?

Sure.


[SPARK-33477][SQL] Hive Metastore support filter by date type

What changes were proposed in this pull request?
Hive Metastore supports strings and integral types in filters. It could also support dates. Please see HIVE-5679 for more details.
This pr add support it.
Why are the changes needed?
Improve query performance.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit test.

Test build #131274 has started for PR 30408 at commit ba2f553.

Test build #131274 has finished for PR 30408 at commit ba2f553.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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/SparkPullRequestBuilder/131274/
Test PASSed.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35878/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35878/

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/SparkPullRequestBuilder-K8s/35878/
Test PASSed.

@wangyum can you resolve the conflicts? thanks!

Test build #131357 has started for PR 30408 at commit ce5f0d1.

last question about correctness: Does hive execute the partition predicate as date comparison or string comparison? The later can be problematic.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35961/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35961/

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/SparkPullRequestBuilder-K8s/35961/
Test PASSed.

Test build #131357 has finished for PR 30408 at commit ce5f0d1.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class ExecutorSource(
 implicit class MetadataColumnsHelper(metadata: Array[MetadataColumn])

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/SparkPullRequestBuilder/131357/
Test PASSed.

It's date comparison: https://github.com/apache/hive/blob/rel/release-2.3.7/metastore/src/java/org/apache/hadoop/hive/metastore/MetaStoreDirectSql.java#L1141-L1148

Test build #131624 has started for PR 30408 at commit 752eb8d.

Test build #131624 has finished for PR 30408 at commit 752eb8d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Build finished.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/131624/

retest this please

Test build #131631 has started for PR 30408 at commit 752eb8d.

Test build #131631 has finished for PR 30408 at commit 752eb8d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/131631/

Build finished.

@shaneknapp Did you set :export LANG=en_US.UTF-8?
org.apache.spark.sql.AnalysisException: org.apache.hadoop.hive.ql.metadata.HiveException: MetaException(message:java.nio.file.InvalidPathException: Malformed input or input contains unmappable characters: /home/jenkins/workspace/SparkPullRequestBuilder@3/sql/hive/target/tmp/hive_execution_test_group/warehouse-1355e680-268f-4224-b549-eaddcadcf136/DaTaBaSe_I.db/tab_ı);

This issue should be fixed if we set export LANG=en_US.UTF-8, more details:https://issues.apache.org/jira/browse/SPARK-27177

@wangyum How about asking it in the spark-dev thread so that Shane could notice it quickly?http://apache-spark-developers-list.1001551.n3.nabble.com/jenkins-downtime-tomorrow-evening-weekend-tt30405.html

Build finished.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/36225/

Build finished.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/36229/

retest this please

Test build #131689 has started for PR 30408 at commit 752eb8d.

Test build #131689 has finished for PR 30408 at commit 752eb8d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Build finished.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/131689/

Build finished.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/36288/

Test build #131740 has started for PR 30408 at commit 29c489a.

Test build #131740 has finished for PR 30408 at commit 29c489a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Build finished.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/131740/

retest this please.

Test build #131751 has started for PR 30408 at commit 29c489a.

Merged to master.

Test build #131751 has finished for PR 30408 at commit 29c489a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Build finished.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/131751/

Build finished.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/36338/

Build finished.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/36349/

@wangyum Could you add more test cases to check the NULL handling cases? For example,

Include NULL values in the data set
Include NULL values in the predicates
Include null-safe equals

Please check https://spark.apache.org/docs/3.0.1/sql-ref-null-semantics.html#comp-operators

@wangyum Could you add more test cases to check the NULL handling cases? For example,

Include NULL values in the data set
Include NULL values in the predicates
Include null-safe equals

Please check https://spark.apache.org/docs/3.0.1/sql-ref-null-semantics.html#comp-operators

@wangyum Could you add more test cases to check the NULL handling cases? For example,

Include NULL values in the data set
Include NULL values in the predicates
Include null-safe equals

Please check https://spark.apache.org/docs/3.0.1/sql-ref-null-semantics.html#comp-operators

OK

@wangyum Could you add more test cases to check the NULL handling cases? For example,

Include NULL values in the data set
Include NULL values in the predicates
Include null-safe equals

Please check https://spark.apache.org/docs/3.0.1/sql-ref-null-semantics.html#comp-operators

OK


Any chance of a branch that will work for Unity (C# 4)?

This doesn't seem to be supported for Unity :/ hahah.... I know, I know, C# 4 bleh. But hey -- 183 forks, figured one of these guys may have one.

You may want to try DiscordUnity. Last I heard, there are long-term plans for Unity to use .NET Standard, but until then...


Nevergrad error in robyn_run()

Project Robyn
Describe issue
Robyn tells me Nevergrad is not installed, even though it should be as I've run the code before without issues (see screenshot).

I see that Robyn runs reticulate's py_module_available() under the hood to produce this error, which is basically reticulate's import() function with an error handler, so I ran this code manually which produced the following error:

Is it possible that this error is then caused by the use of a deprecated NumPy feature?
Environment & Robyn version
Robyn version: 3.11.0
R version: 4.4.0

I got the same issue as well, but 2 weeks back it was working fine for me as well. Any luck solving it ?

This error needs an update from the Nevergrad's side. I'll ping them and keep you updated.
cc @igorskokan

Seeing the same error.  Tried to install an older version of nevergrad, still no luck.

Until the Nevergrad fix, see a workaround here
https://github.com/facebookexperimental/Robyn/issues/998

Nevergrad landed the fix yesterday
The Nevergrad code should work with both numpy1 (at least reasonably
recent) and numpy2.0.
Check it out and let us know.
On Fri, 21 Jun 2024 at 12:20, gufengzhou @.***> wrote:

Until the Nevergrad fix, see a workaround here
#998 https://github.com/facebookexperimental/Robyn/issues/998
—
Reply to this email directly, view it on GitHub
https://github.com/facebookexperimental/Robyn/issues/1004#issuecomment-2182557533,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARF52KDJUXNNZ2N7Q43NBW3ZIQEAZAVCNFSM6AAAAABJUQWT4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBSGU2TONJTGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@gufengzhou I'm no longer getting the same error, but a new one:

Will this require an update on Robyn's end?

Have you updated /reinstalled nevergrad? If yes please also restart R and try.
After the above, If this still occurs, an user here has solved it by updating the R version. See https://github.com/facebookexperimental/Robyn/issues/1006

Thanks Gufeng, that worked!

Would you please let me know if you needed to update R or not?
If yes, which R versions did you have before/after?

I did need to update, yes. I updated from 4.4.0 to 4.4.1


Create a shoop button doesn't work

Description
On initial setup, after creating the super user and network settings, the "Create a shop" button doesn't seem to work.  Or do anything.
Button in question:

This is the only thing that shows when visiting the backend URL.  While I don't think this is release blocking since we have initial stores already, it is blocking my local testing for other work.
Repro steps

Destroy local SQLite DB and run migrations
Run backend
Go to http://localhost:9000 and follow the prompts

Not sure why the button says 'shoop' - searching the codebase for 'shoop' returns nothing. Is it somehow running old code?

Looks like this is preventing display of the Nav & modal:
if (!localStorage.isAdmin || !admin) {
  return null
}

Ha, the shoop change was actually so I could identify the correct button because there's two Create a shop buttons in the FE code.  That was a local-only change.  The button in question is in StoreSelector.

So, localStorage.isAdmin is undefined for me, which would make useAuth not run at all.
useAuth({ only: () => localStorage.isAdmin })

And that never gets set because of this:
https://github.com/OriginProtocol/dshop/blob/7863f4e682baa893386eaa3bc8f23bf83d777a81/shop/src/utils/useAuth.js#L34-L36
And the backend returns sucess: false because of this:
https://github.com/OriginProtocol/dshop/blob/7863f4e682baa893386eaa3bc8f23bf83d777a81/backend/routes/auth.js#L149-L159
There's a lot of subtle interactions going on here.  Wondering if we should make this dummy-obvious.  success: false for any reason other than a request failure seems risky.


fix: Support for multibyte character strings.

Make the GenerativeModel#generateContentStream method compatible with multibyte character strings.

https://github.com/googleapis/nodejs-vertexai/issues/78

Closing this since https://github.com/googleapis/nodejs-vertexai/issues/78 was fixed by https://github.com/googleapis/nodejs-vertexai/pull/86.