text:
Fix interpolation and systems schedule

Interpolation not works properly due the problem described in #464.
We removed TimestepMode from crate, because we do not see reason for why this should even exists. Idea of FixedUpdate loop which Bevy engine implements look fine, and another game engines also use this for physics steps. Description about current master implementation:

TimestepMode::Fixed  - looks nice, but do not interpolate results, who wants to use that? This can be easy misleading for new users of crate.
TimestepMode::Variable - it make physics heavily addicted by Update's delta time and is really far of deterministic, also change speed of physics depending on render time which makes difficult to catch up render by physics what occurs slow simulation on e.g. weaker computers.
TimestepMode::Interpolation - before does not work correctly, user system execution was skipped and lerp was poorly implemented.

Now, after our changes, every user defined system which impact physics like movement etc. should execute in engine's schedule FixedUpdate and before crate's system set PhysicsSet::SyncBackend. Also for things like slow motion effects change engine's fixed delta time by Bevy API.
Resolves #464, resolves #379, closes #463
And probably #465, #475

The current implementation does not allow for a lot of flexibility of schedule design anymore. My game uses a custom schedule to have more control over the physics loop which is not possible here anymore. Maybe we could define a self.physics_schedule and self.write_back_schedule to differentiate between both use cases. This can not be easily fixed by putting my systems before or after the rapier system set since it does not allow for not executing or executing irregularly.

@phisn about custom schedules we need to have the expected behavior from #464 to have working interpolation. Bevy's FixedUpdate schedule was created for this purpose, and suits for this ideal. I do not know, why you want to replace this from API, because way how it works after my changes are so common in another game engines, and games just exists with that solution. But maybe you want to have possibility for execute next physics step by hand? Then user-defined systems should also be executed what I do not remember if it possible in Bevy to make (I guess yes), and this is a things what we can make (if we can).
About transform changes, and preverting interpolation. This exists originally in code, and this is a feature what have sense, because make teleporting instant instead of flying all over the map. Real world physics do not have things like teleport, everything works with impulses and forces, not by teleporting, and teleporting is not a things what can be interpolated, because physics engine do not know what changed in what way. You can create impulse or force, what will be rotate your object with having interpolation, or also add rotation similar to position to character controller what Rapier do not implement yet.

authors: Vixenka phisn


text:
Doesn't compile under 4.06.0+trunk due to safe-string default

Using opam 1.2.2 and 4.06.0+trunk (safe-string enabled by default):
#=== ERROR while installing zed.1.5 ===========================================#
# opam-version 1.2.2
# os           linux
# command      jbuilder build -p zed -j 4
# path         /home/hcarty/.opam/4.06.0+trunk/build/zed.1.5
# compiler     4.06.0+trunk
# exit-code    1
# env-file     /home/hcarty/.opam/4.06.0+trunk/build/zed.1.5/zed-16785-0edee0.env
# stdout-file  /home/hcarty/.opam/4.06.0+trunk/build/zed.1.5/zed-16785-0edee0.out
# stderr-file  /home/hcarty/.opam/4.06.0+trunk/build/zed.1.5/zed-16785-0edee0.err
### stderr ###
# Error: This expression has type bytes but an expression was expected of type
# [...]
# (cd _build/default && /home/hcarty/.opam/4.06.0+trunk/bin/ocamlopt.opt -w -40 -g -I /home/hcarty/.opam/4.06.0+trunk/lib/bytes -I /home/hcarty/.opam/4.06.0+trunk/lib/camomile -I /home/hcarty/.opam/4.06.0+trunk/lib/ocaml -I /home/hcarty/.opam/4.06.0+trunk/lib/react -no-alias-deps -I src -o src/zed_utf8.cmx -c -impl src/zed_utf8.ml)
# File "src/zed_utf8.ml", line 303, characters 26-29:
# Error: This expression has type bytes but an expression was expected of type
#          string
#       ocamlc src/zed_rope.{cmo,cmt} (exit 2)
# (cd _build/default && /home/hcarty/.opam/4.06.0+trunk/bin/ocamlc.opt -w -40 -g -bin-annot -I /home/hcarty/.opam/4.06.0+trunk/lib/bytes -I /home/hcarty/.opam/4.06.0+trunk/lib/camomile -I /home/hcarty/.opam/4.06.0+trunk/lib/ocaml -I /home/hcarty/.opam/4.06.0+trunk/lib/react -no-alias-deps -I src -o src/zed_rope.cmo -c -impl src/zed_rope.ml)
# File "src/zed_rope.ml", line 541, characters 13-91:
# Error: This expression has type bytes but an expression was expected of type
#          Zed_utf8.t = string

In particular, this blocks installation of utop.

Same pb with:
opam  2.0.0~beta4 | linux/x86_64 | ocaml 4.06.0+flambda

https://github.com/diml/zed/pull/8

I just hit this. The fact that it blocks the install of utop is kind of bad, it means I can't really upgrade to 4.06. :(

@pmetzger everything that "needs to be done" is finished. We just need for the releases to hit opam-repository.

@cfcs I didn't notice that the "#8" was a link. :)
Apologies!

Is this problem still active or can we close it? @diml?

This is OK now!  Thank you for the nudge @pmetzger.  Closing.

source: gharchive/issue

authors: Fourchaux cfcs hcarty pmetzger rgrinberg

repo: diml/zed

license_type: permissive

license_source: bigquery


text:
Internal Request Dingo\Api\Exception\InternalHttpException when api returns a json

ErrorException in InternalHttpException.php line 22:
Argument 1 passed to Dingo\Api\Exception\InternalHttpException::__construct() must be an instance of Illuminate\Http\Response, instance of Illuminate\Http\JsonResponse given, called in C:\xampp\htdocs\test\vendor\dingo\api\src\Dispatcher.php on line 525 and defined

Example route:
Route::get('/home', 'HomeController@index');
$api->version('v1', function ($api) {
	 $api->get('test', function(){
        return response()->json(['message' => 'Bad request, please verify your request route', 'status_code' => 400],400);
    });
});

Example HomeController:
      public function index()
    {
        $dispatcher = app('Dingo\Api\Dispatcher');
        return $dispatcher->get('test');
    }

When visit api.localhost.com/home i receive InternalHttpException. why?? is not possible return the original json?
when i use a route in dispatcher that returns a class works ok, but in my api, a lot of end points returns a json.
anybody can explain how works dispatcher??
a lot of thanks
Laravel 5.2

@j1yaktech I don't think you can put a response in route closure any more.
You need to dispatch to the correct route. Try this:
return $dispatcher->get('api/test');

// or double check your route using this command
php artisan api:routes

The dispatcher will throw InternalHttpException if the response status code is not successful (>= 200 && < 300). I think this is kinda wrong and it make it hard to work with REST API.

catch (Dingo\Api\Exception\InternalHttpException $e) dont work

I think the only to do it ATM is replace the dispatcher with or own.

@jenky Could you specify how to do it?

@ivankurn Create your own dispatcher that extends to original class and overwrite the dispatch method. Then overwrite the dispatcher in the container by registering it on your provider, make sure your provider has been loaded after dingo/api's provider.

You do not need to return response()->json. I know that's what Laravel says, but the API handles the formatting of the response and it causes some trouble. I could allow it, but it's just easier to not use the response()->json method when returning your responses.
Just return whatever it is, how it is. If it's an error, try throwing a HttpException instead of building a response. If you need custom headers, simply return a new Response instance and adjust the status code/headers how you wish. Avoid using Response::json.

Oh and the InternalHttpException is for when an error response is returned for an internal request. It's so everything is normalized and is meant to make things easier. You can catch this exception in your controller (or route closure) and then act on it.
try {
    app('api.dispatcher')->post('users', ['name' => 'foo', 'password' => 'bar']);
} catch (Dingo\Api\Exception\InternalHttpException $e) {
    $response = $e->getResponse();

    // you can now do whatever you want with the response, check it's content, status code, etc.
}

authors: ivankurn j1yaktech jasonlewis jenky jlien-calwater

repo: dingo/api


text:
"Sites you've probably visited" Returns Inaccurate Results

I landed on the site using Chrome 46.0.2490.80 and it did not load a single site that I've actually visited with the exception of a few like Reddit and Quizlet which I feel it would be incorrect to assume are accurate results simply because of the scale/traffic those sites get.
I'm running Chrome with the following extensions:

Application Launcher for Drive (by Google) 3.2
Devtools Terminal 0.4.0
Evernote Web Clipper 6.7
Ghostery 5.4.8.1
Google Art Project 1.0.37
HTTPS Everywhere 2015.8.13
LastPass: Free Password Manager 3.2.41
Mailvelope 1.2.2
Pushbullet 278
Stylish 1.4.0
Tampermonkey 3.11
uBlock Origin 1.2.0

Having also tried loading the site with an exception from HTTPS Everywhere, the result was the same.

an exception from HTTPS Everywhere

Have you tried disabling HTTPS Everywhere completely?

Disabled HTTPS Everywhere, the returned list was 12 sites that I've never visited.

I suspect this is due to interference with your addons (which is noted as a limitation in the README, fwiw); try opening an incognito window and seeing whether the results change. Addons are disabled by default in incognito but you can check by going to chrome://extensions.

Disabled HTTPS Everywhere <-- LOOL if this fix the issue i won't disable it.

It doesn't fix the issue in general, though it might prevent it for some cases.

Then is a protection agains your crappy test.

How is this a "crappy test"? It's a privacy issue that can be taken advantage of by users that don't have their browsers properly configured.

authors: Qix- bet0x cooperpellaton diracdeltas jomo

repo: diracdeltas/sniffly

license: mit


text:
chore(main): release 0.3.0

:robot: I have created a release beep boop
0.3.0 (2024-09-22)
Features

providers: flatten multi-providers when using useExisting (#10) (48df581)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.3.0
:sunflower:

source: gharchive/pull-request

repo: dirkluijk/needle-di

license: MIT

license_source: github-api


text:
Error on startup after bot prepares slash commands

Hey there, after I start the bot I see this warning in the terminal, and it appears that the slash commands are not appearing in my guild. Thanks in advance!
[28/7/2021 4:11:37 a. m.] INFO > [READY] Bot is online and ready in 2 guild(s)!
[28/7/2021 4:11:37 a. m.] INFO > Preparing Slash Commands...
Error: [403] The Authorization token you passed did not have permission to the resource.
    at Object.processQueue (https://deno.land/x/discordeno@11.2.0/src/rest/process_queue.ts:101:40)
    at async Object.processRequest (https://deno.land/x/discordeno@11.2.0/src/rest/process_request.ts:31:5)
[28/7/2021 4:11:37 a. m.] WARN > Error: Location:
    at Object.runMethod (https://deno.land/x/discordeno@11.2.0/src/rest/run_method.ts:36:9)
    at upsertSlashCommands (https://deno.land/x/discordeno@11.2.0/src/helpers/interactions/commands/upsert_slash_commands.ts:16:21)
    at file:///C:/Users/gm_10/OneDrive/Documents/discordbot/src/events/ready.ts#7:63:13
    at Map.map (https://deno.land/x/discordeno@11.2.0/src/util/collection.ts:95:20)
    at Object.bot.eventHandlers.ready (file:///C:/Users/gm_10/OneDrive/Documents/discordbot/src/events/ready.ts#7:62:18)
[28/7/2021 4:11:37 a. m.] INFO > Updated Guild 😤🙏 (859883782470238268) Slash Commands...
Error: [403] The Authorization token you passed did not have permission to the resource.
    at Object.processQueue (https://deno.land/x/discordeno@11.2.0/src/rest/process_queue.ts:101:40)
    at async Object.processRequest (https://deno.land/x/discordeno@11.2.0/src/rest/process_request.ts:31:5)
[28/7/2021 4:11:37 a. m.] WARN > Error: Location:
    at Object.runMethod (https://deno.land/x/discordeno@11.2.0/src/rest/run_method.ts:36:9)
    at upsertSlashCommands (https://deno.land/x/discordeno@11.2.0/src/helpers/interactions/commands/upsert_slash_commands.ts:16:21)
    at file:///C:/Users/gm_10/OneDrive/Documents/discordbot/src/events/ready.ts#7:63:13
    at Map.map (https://deno.land/x/discordeno@11.2.0/src/util/collection.ts:95:20)
    at Object.bot.eventHandlers.ready (file:///C:/Users/gm_10/OneDrive/Documents/discordbot/src/events/ready.ts#7:62:18)
[28/7/2021 4:11:37 a. m.] INFO > Updated Guild test (814768016298213387) Slash Commands...
[28/7/2021 4:11:37 a. m.] INFO > [READY] Slash Commands loaded successfully!

The bot needs to be invited with the right scopes in order to be able to create slash commands. (application.commands)

This one

Ah, I missed that when creating the invite link. Thank you!

authors: Yaikava wildflowericecoffee

repo: discordeno/template


text:
Submittion Whaffle

What is your username and discriminator?
whaffle#8765
Why did you join Discord Linux?
I'm rather new to linux, specifically swapping from Windows 10 to Lubuntu 18.10, I often run into a few errors when doing some things and was looking for a reliable source of help.
Where did you hear about Discord Linux?
Tech-savvy people
What is the passphrase that was assigned to you by the bot?
7xf321y8b1jx1.md
ID: 404142934909386755
Created: 2018/01/20 05:19:44

From Ethan Weegee#9302 :
This form is only for people who do not have a phone to verify with Discord. Please read the message that mentions you in the welcome channel.

authors: DiscordLinuxBot akrispynugget

repo: discordlinux/rules


text:
Support update article urls of a given site id

Tested with script below:
$ python3 fb-site.py 20 --update --headful
$ python3 fb-site.py 20 --update
$ python3 fb-site.py 90
$ python3 fb-post.py 2400

我想這樣做不太好 https://github.com/disinfoRG/FbScraper/pull/35 因為1. 這樣看起來 site update 如果要 update N 篇文章，browser 就會開啟關閉 N 次
2. 看 fb_site.py 的程式的人，會看不懂 fb_post.main 這個 function 在做什麼，為什麼要這樣傳參數給它

repo: disinfoRG/FbScraper


text:
ci: fix GHA CI build matrix

It would appear that requesting Go 1.21 in the build matrix has no effect whatsoever on what go toolchain is actually used to build the project. See https://brandur.org/fragments/go-version-matrix.
Specifying 1.22.0 in the go.mod go directive forces the 1.22 toolchain to be used for building Go source files, ignoring whatever Go version we set in the GHA CI matrix.
You can see the "wrong" toolchain to be used in the screenshot below:

Luckily we can enforce the right setting by setting GOTOOLCHAIN=local which forces Go to use the locally available toolchain instead of downloading the one requested by go.mod.
If we want to be one minor version back compatible we need to drop the go.mod go directive to 1.21.0, too.
As for the image builds, the Docker image we use sets the GOTOOLCHAIN=local by default:
$ docker run -it golang:1.22.5 /bin/bash
root@f0dde6c33f17:/go# go env GOTOOLCHAIN
local

Ah, yes, these are the fun ones. I think this is caused by https://github.com/distribution/distribution/pull/4347, which switched to the SemVer format, which forces it to download the version. I've tried to avoid using that format, but not sure how much longer Go allows the old format to be used.
Honestly, I think that the go-setup-action should also either set GOTOOLCHAIN=local or produce a big fat error when trying to specify a version without it being set.

What's with the new certs in the vendor folder? Is that really an artifact of the go toolchain change?

What's with the new certs in the vendor folder? Is that really an artifact of the go toolchain change?

I am not entirely sure. The certs were added as part of running go mod vendor. I remember looking into that at the time
I had a look at the dependency repo (github.com/google/s2a-go) and saw that the certs (used for testing only) were added in https://github.com/google/s2a-go/pull/103  which was included in https://github.com/google/s2a-go/releases/tag/v0.1.1
Our deps are pinned to v0.1.4 https://github.com/distribution/distribution/blob/0e850894d651bbd4e47e612c387baae82c7d1e9f/go.mod#L63
So it's a bit strange. My theory at the time was there is a difference in how different toolchain versions handle dependency vendoring (i.e. go mod vendor command) 🤷♂
Now, I'm thinking we should bump the Go version in the go.mod to 1.22 anyway, now that 1.23.X has been out for a bit, which will nuke these certs from the vendor

My theory at the time was there is a difference in how different toolchain versions handle dependency vendoring (i.e. go mod vendor command) 🤷♂

Yes, I think newer versions more aggressively pruning files from vendor. It already excluded testdata directories elsewhere, and for these ones already removed the .pem files.  Perhaps the only reason it kept the directory was because it detected the .der files as binary files and kept them before;
https://github.com/google/s2a-go/tree/v0.1.4/internal/v2/remotesigner/testdata

I think we should bump it back to 1.22 🤷♂ WDYT @Jamstah

We can specify the Go version in the go.mod file and split the matrix into two jobs: one that uses the version defined in go.mod and another that uses the local version.
Like: https://github.com/prometheus/prometheus/commit/1e01e97151c9db59178dfbabd5e60f4b3916cb83#diff-b803fcb7f17ed9235f1e5cb1fcd2f5d3b2838429d4368ae4c57ce4436577f03fR44

We can specify the Go version in the go.mod file and split the matrix into two jobs: one that uses the version defined in go.mod and another that uses the local version.
Like: prometheus/prometheus@1e01e97#diff-b803fcb7f17ed9235f1e5cb1fcd2f5d3b2838429d4368ae4c57ce4436577f03fR44

Isnt that what this PR is actually doing? Am I missing something?

I've decided to bump the Go version in go.mod and Dockerfiles

We can specify the Go version in the go.mod file and split the matrix into two jobs: one that uses the version defined in go.mod and another that uses the local version.
Like: prometheus/prometheus@1e01e97#diff-b803fcb7f17ed9235f1e5cb1fcd2f5d3b2838429d4368ae4c57ce4436577f03fR44

Isnt that what this PR is actually doing? Am I missing something?

I mean, we don't use the matrix, and break them into two jobs.

I mean, we don't use the matrix, and break them into two jobs.

I think the matrix works well. No need for unnecessary redundancy IMHO 🤷♂

authors: Jamstah milosgajdos thaJeztah wy65701436

repo: distribution/distribution


text:
Pickle-able Distributions

Make distributions pickle-able.

not exactly a solution, but close: dill can serialize distributions.

repo: dit/dit


text:
Generating single html - root-chunk-override is not equivalent to setting chunk attribute on map root element

Expected Behavior
I set the "root-chunk-override" property as "to-content", in the html5.init target, to make the output one html containing all topics in the dita source.
Actual Behavior
However, it still generates separated topic html files at the same time while it will only generate one single html when I set the chunk attribute to "to-content" in the ditamap source.
Possible Solution
No possible solution currently.
Steps to Reproduce

Go to org.dita.html5 plugin folder
Find build_dita2html5.xml file
Locate the html5.init target
Add the line: <property name="root-chunk-override" value="to-content"/>
Publish with html5 transtype

Environment

DITA-OT version: 3.7.0
Operating system and version: Windows
How did you run DITA-OT?
dita command
Transformation type:
HTML5

I can reproduce the problem, possibly if someone were to investigate this further, in the "ChunkModule" Java class there is a "removeChunkSources(..)" method which should probably remove the source files which are chunked together. And this does not happen although the init(...) method in the same class seems to propagate the chunk override value to the map root.

Attaching a zip containing a small map and two topics for tests:
flowers.zip
Coming back to this, there are now two ChunkModule classes, the new one for DITA 2.0 is located in "org.dita.dost.chunk.ChunkModule" and the older one in "org.dita.dost.module.ChunkModule".
The problem can be reproduced with a DITA 1.3 map, so the old "org.dita.dost.module.ChunkModule" implementation is used. And the problem is in the method "org.dita.dost.reader.ChunkMapReader.process(Document)" which should set the root chunk override on the root element before calling "readLinks(doc);".
if I were out of curiosity to change the DOCTYPE declaration of the DITA Map to make it 2.0:
 <!DOCTYPE map PUBLIC "-//OASIS//DTD DITA 2.x Map//EN" "map.dtd">

and then publish to HTML5 using the "root-chunk-override" param set to "combine", I get a NullPointerException instead:
 java.lang.NullPointerException: Cannot invoke "java.net.URI.resolve(java.net.URI)" because "chunk.src" is null
at org.dita.dost.chunk.ChunkModule.rewriteLinks(ChunkModule.java:230)
at org.dita.dost.chunk.ChunkModule.lambda$9(ChunkModule.java:193)
at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1625)
at java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:762)
at org.dita.dost.chunk.ChunkModule.generateChunks(ChunkModule.java:188)
at org.dita.dost.chunk.ChunkModule.processCombine(ChunkModule.java:85)
at org.dita.dost.chunk.ChunkModule.execute(ChunkModule.java:52)

So there seem to be bugs in both implementations.
@jelovirt what's your opinion on this?

Attaching a zip containing a small map and two topics for tests: flowers.zip
Coming back to this, there are now two ChunkModule classes, the new one for DITA 2.0 is located in "org.dita.dost.chunk.ChunkModule" and the older one in "org.dita.dost.module.ChunkModule".
The problem can be reproduced with a DITA 1.3 map, so the old "org.dita.dost.module.ChunkModule" implementation is used. And the problem is in the method "org.dita.dost.reader.ChunkMapReader.process(Document)" which should set the root chunk override on the root element before calling "readLinks(doc);".
if I were out of curiosity to change the DOCTYPE declaration of the DITA Map to make it 2.0:
 <!DOCTYPE map PUBLIC "-//OASIS//DTD DITA 2.x Map//EN" "map.dtd">

and then publish to HTML5 using the "root-chunk-override" param set to "combine", I get a NullPointerException instead:
 java.lang.NullPointerException: Cannot invoke "java.net.URI.resolve(java.net.URI)" because "chunk.src" is null
at org.dita.dost.chunk.ChunkModule.rewriteLinks(ChunkModule.java:230)
at org.dita.dost.chunk.ChunkModule.lambda$9(ChunkModule.java:193)
at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1625)
at java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:762)
at org.dita.dost.chunk.ChunkModule.generateChunks(ChunkModule.java:188)
at org.dita.dost.chunk.ChunkModule.processCombine(ChunkModule.java:85)
at org.dita.dost.chunk.ChunkModule.execute(ChunkModule.java:52)

This NPE comes probably from "org.dita.dost.chunk.ChunkModule.collectChunkOperations(URI, Element, List)" which has a commented out ** //.src(href)** when chunk is combine.
So there seem to be bugs in both implementations.
@jelovirt what's your opinion on this?

So, do you mean that we need to rewrite the java module?

I added the issue #4036 to look into the NPE obtained when using DITA 2.0 maps with "root-chunk-override" set to "combine".

Sorry, I have no knowledge about Java.
---- Replied Message ----
| From | Radu @.> |
| Date | 11/03/2022 22:34 |
| To | @.> |
| Cc | @.@.> |
| Subject | Re: [dita-ot/dita-ot] Generating single html - root-chunk-override is not equivalent to setting chunk attribute on map root element (Issue #4019) |
@Billy-102 yes, the fix needs to be done in the Java org.dita.dost.reader.ChunkMapReader class this code:
final Element root = doc.getDocumentElement();
if (rootChunkOverride != null) {
    final String c = join(rootChunkOverride, " ");
    logger.debug("Use override root chunk \"" + c + "\"");
    root.setAttribute(ATTRIBUTE_NAME_CHUNK, c);
}

should be moved 3 lines up before the call to "readLinks(doc);".
Do you have Java knowledge to check out the project, make the changes on your side and then re-build it?
I will try to find some time to create a pull request and a testcase for it but I'm not sure in what DITA OT version the fix will be included.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Thank you. Waiting for your pull request. And then I might test it in the version 3.7.x
---- Replied Message ----
| From | Radu @.> |
| Date | 11/03/2022 22:34 |
| To | @.> |
| Cc | @.@.> |
| Subject | Re: [dita-ot/dita-ot] Generating single html - root-chunk-override is not equivalent to setting chunk attribute on map root element (Issue #4019) |
@Billy-102 yes, the fix needs to be done in the Java org.dita.dost.reader.ChunkMapReader class this code:
final Element root = doc.getDocumentElement();
if (rootChunkOverride != null) {
    final String c = join(rootChunkOverride, " ");
    logger.debug("Use override root chunk \"" + c + "\"");
    root.setAttribute(ATTRIBUTE_NAME_CHUNK, c);
}

should be moved 3 lines up before the call to "readLinks(doc);".
Do you have Java knowledge to check out the project, make the changes on your side and then re-build it?
I will try to find some time to create a pull request and a testcase for it but I'm not sure in what DITA OT version the fix will be included.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@raducoravu  Thank you. I can see the commits in this site, but how can I apply this modification to my installed DITA-OT? I have never practiced such approach before.

@Billy-102 I suspect my changes will be part of DITA OT 4.0 which should be released sometime next week.

Ok, thank you.
在 2022-11-07 16:17:07，"Radu Coravu" @.***> 写道：
@Billy-102 I suspect my changes will be part of DITA OT 4.0 which should be released sometime next week.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

repo: dita-ot/dita-ot


text:
Replace hashlib with crypto

Removed the requirement for hashlib because it no longer works well on node 0.6.

Or another idea is to depend on hashlib2: https://github.com/karlseguin/hashlib/

repo: ditesh/node-poplib


text:
[DF-446] fix resend integration tracking

The resend integration's endpoint for tracking is giving 400's in production. Create a resend application, and use ngrok or the equivalent to test locally.
From SyncLinear.com | DF-446

going to assign to @neo773 if he's available, because he worked on the original ticket.

/bounty $20

/attempt #658

authors: maxgurewitz tobihans

repo: dittofeed/dittofeed


text:
Automate app packaging

@Chunosov
Please describe steps of manual packaging from original sources
Then we will try to automate and add to CI (travis)

Added redist script in #10

Redists scripts are there. Making the app buildable properly via CK is a big story which will be covered by other, more specific tasks (the first one of them is #25). So, closing this ticket.

authors: Chunosov DVEfremov dsavenko