TranscriptLoggerMiddleware should update activity.Id on the cloned activity

Version
All versions
Describe the bug
https://github.com/microsoft/botbuilder-dotnet/blob/master/libraries/Microsoft.Bot.Builder/TranscriptLoggerMiddleware.cs#L69
            // hook up onSend pipeline
            turnContext.OnSendActivities(async (ctx, activities, nextSend) =>
            {
                // run full pipeline
                var responses = await nextSend().ConfigureAwait(false);

                foreach (var activity in activities)
                {
                    LogActivity(transcript, CloneActivity(activity));
                }

                return responses;
            });

The cloned activity in the code above should include the ResourceResponse.id retrieved from sending the activity to the server. Currently, all outgoing activities logged will NOT have this id
Expected behavior
Activities logged should contain the actual id of the activity (which is determined by the server, when sending the message).
[bug]

This seems to be solved already, a different way, in dotnet:
https://github.com/microsoft/botbuilder-dotnet/blob/fb65b0063c0e8df711c92247ba156d1e088012c4/libraries/Microsoft.Bot.Builder/TurnContext.cs#L274
Sorry for the noise.


DOCUMENTATION AND OTHER ISSUES

Please can you show me an example on how to use queries or a documentation  quite confusing
,,,
user_info
followers
following
posts
post_info
likes
comments
feed
explore
,,,
and for some reason action.likes dont work for me .
login(username='xxxxxxx', password='xxxxxxx') for liker in likes('BhT6gpHFwMj'):             like(liker)

thanks

Hello. Sorry about the documentation. I can't work on it right now, maybe soon. For now, I would suggest you to play a bit with onegram using ipython. All responses are python dicts.
About action.likes: on instagram you can't like a person, but you can follow instead. The only thing you can like is a post.
You can try to change your code a bit:
from onegram import likes, like, posts

for liker in likes('BhT6gpHFwMj'):
    # Like last post of the liker - if it has any
    last_post = next(posts(liker), None)
    if last_post:
        like(last_post)

Don't forget to keep it updated: pip install -U onegram.

I'm closing this issue, but feel free to keep in touch. Later I'll open docs-related issues.
If you prefer, there's a also chat room where you can place any question.


Updates Docs adds more hints for server setup

Updates Docs adds more hints for server setup in htaccess file

Hi if you want new Coding Style (CS) you may check this commit which is not in this pull request:
https://github.com/flobee/jquery-file-upload/commit/be620e9f4333f2225bcf4318af2ca6db89fdf0cf

Thanks for your pull request @flobee.
Unfortunately I don't see the benefit of those contributions.
Maybe this would be better suited in a fork?
If there's an exact topic that this set of changes is about, I'll gladly add it to the Wiki.

Hi, the pull request shows changes for this:
https://github.com/blueimp/jQuery-File-Upload/pull/3472/commits/8d8b42bb8084982b2070a0d5a6fd657b6bca08ff
If this is not a benifit people maybe get lost :-/
All other listed here are not included. I'm not often send pull request, so maybe misunderstanding.
I forked already your project but will leave it as good as i can as is :-) Except coding style. This was a must have for me.

You can keep the coding style or any other aspect in your fork whichever way you want. :)
I've added a note about the Apache Headers module to .htaccess file here: https://github.com/blueimp/jQuery-File-Upload/commit/fa04f7b0f8e04a15e397a6797c14a491c5d07fa4
As a recommendation, if you want maintainers to include your pull requests it's better to keep them atomic, with one set of focused changes.


proc_dlatch: discard \init on bits that get transformed into direct connections

Fixes #1443

Actually, I'm not sure this works. This change discards \init signals on direct connections:
module top(input i, output reg o);
initial o = 1'b0;
always @* o = i;
endmodule

but what about situations like:
module top(input clk, i, output reg o, p);
initial p = 1'b0;
always @(posedge clk) o <= i;
always @* p = o;
endmodule

where the \init of p would otherwise be used to initialise the FF on o?
And what about situations like:
module top(input clk, i, output reg o, p);
initial o = 1'b0;
initial p = 1'b0;
always @(posedge clk) o <= i;
always @* p = i;
endmodule

where the \init values are consistent?


Update create-a-phone-system-auto-attendant.md

@MikePlumleyMSFT
Let me know if you have any questions.

Thanks, @carolynblanding.


New Counter APP

An APP made with HTML, CSS , JS so could I add that?

Sir I have already generated PR regarding this issue please go through from that.

I have to cancel that because someone committed that app when open this issue , so what should I do now.


Add an arg parser to simpletest.py

This change adds an argument parser so that you can call simpletest.py
directly from the command line.  You can invoke it with:
$ python simpletest.py --sensor  --pin <pin #>
Sensor can be one of 'dht11', 'dht22', or 'am2302', however defaults to
the dht22 sensor.  Pin can either be a string or an integer and
corresponds to the GPIO pin that is attached to the sensor.

Hi @pdevine - thanks for your work here.  I'm closing this, but I want to make clear that it's because:

we've currently got a house style for simpletest code, and it doesn't (generally) include argument parsing or efforts at a full-featured CLI - we mostly focus on the simplest thing that will work, and try to avoid complications that might derail a user who hasn't worked with Python before.

we're deprecating this library in favor of Adafruit_CircuitPython_DHT, and trying to focus our maintenance energies there.


MNT make init atomic

Fixes #42
Need to merge https://github.com/skops-dev/skops/pull/45 first so that this can properly be tested.

Super clean 🧼

I see why the added test does not cover the Exception part: It fails outside of the try, namely here:
https://github.com/adrinjalali/skops/blob/593f605e3d364a77867b799f46b816e488b4e45d/skops/hub_utils/_hf_hub.py#L277-L279
So for the test to actually cover the line, the error would have to occur inside of _create_config. Perhaps the most robust way to achieve that would be to patch the function and make it raise?

It's all green now @BenjaminBossan

Could you please resolve the merge conflict?

Done, and CI is green!


Typo in the .NET Implementations article

Type of issue
Typo
Description
Before going into detail about the .NET implementations, there is a list of implementations that will be elaborated on in the following text. However, the first item

Does not match the corresponding title

Page URL
https://learn.microsoft.com/en-us/dotnet/fundamentals/implementations#net-5-and-later-versions
Content source URL
https://github.com/dotnet/docs/blob/main/docs/fundamentals/implementations.md
Document Version Independent Id
0b9ceffa-ccd9-d338-9dbe-752ac93bb2ad
Article author
@dotnet-bot
Metadata

ID: edc3ae50-d51a-ae5d-6c95-b32852c973a9
Service: dotnet-fundamentals

Related Issues

Is any one work on this issue??

@Legend4it I created this PR as soon as I reported the issue


Having certain configs enabled breaks the resource pack.

After enabling the extra configs of War, Stars, and Bending: Some of the default wands only appeared as sticks and no longer had their custom models. Blasters from the Stars config had no model as well. Also, as in prior builds of Magic, unless this changed, lightsaber models showed always open and never closed to just the hilt. Unsure if it's just a confliction or somehow the resource pack that my server gives is bugged.

Sorry for responding so late- there is a special RP that gets used when you include the war configs, but it should still be working. This is how my dev server is setup.
If you're still having issues and want support, please show me the configs you've got to add in the examples.

Main thing is that apparently some tiers of wands have certain models. One of my players stated that after I enabled the other configs aside from default that the wands just became sticks. I reset the config to default but the wands are still broken. When I had Stars enabled, the sabers didn't work quite right and blasters were sticks. When war was enabled as well, its items looked right.

Wanda being sticks is pretty odd since the item they use is the wooden hoe.
Can you share the configs you’re using via hastebin, please?

Ok, here is a pastebin of my config https://pastebin.com/W8tX2Yzi

Sorry for never getting back to this. Please re-open if you're still having problems. The config you pasted had a pretty general Yaml issue, a space in front of add_examples.


Could it support custom decompression ?

The custom compress option is a very good idea.
I came up with an idea to take advantage of this.
The way I would use a compression library like lz-string to literally "compress" the file.
const compressShader = (shader: string) => {
  const s = shader.replace(...);
  return LZString.compressToUTF16(s);
}

This method worked well.
By decoding before compileShader() on the read side, it worked as expected.
import vs from '../glsl/shader.vert';
const vsd = LZString.decompressFromUTF16(vs);

But if possible, a decompress callback option would be a smarter implementation.
I would be glad if you could support this.

Hi @uctakeoff and thanks for using this plugin!
I'm not 100% sure I'm understanding your request though. Currently a custom compress callback can be used at build time (it makes more sense in production environments, but it's totally valid in development as well) to save some space and it will output a compressed shader when importing it in a .js file.
It is possible to add a custom decompress callback, but I need your help to figure out a use case for this: I guess it won't make sense decompressing it before passing to JS 'cause it will mean - compress a shader and immediately after decompress it so it will have the original shape when importing into .js file..?
Or the logic behind that is to allow using already compressed shaders before even parsing them via vite-plugin-glsl so you can import them decompressed into JavaScript..?
Both options are possible, I just cannot quite understand the purpose of having such functionality.
If on the other hand, you want to call a custom decompress function (originally passed as an option to this plugin) right from a .js file, even though this also might be possible if I save it in some "static" method in order to expose it later, you will need to import this plugin at least twice: once in your vite.config file and then again in a .js file that will call this decompress callback.
Honestly sounds weird to me 'cause I thought vite plugins should be used only in a  vite.config file.

Perhaps I have misunderstood the usage.
I thought glsl's compression feature was to reduce the package size after build. (This is what is called "minify".)
The smaller the package size, the better.
If this is the case, I thought that the compressed code does not necessarily have to be readable. You can use gzip if it is effective in compression.
Also, for some products, it makes sense to make the source code less readable.
It has the effect of making it difficult for others to reverse engineer the code. (Of course, it is not perfect.)
For such applications, I thought it would make sense to use a compression algorithm or encryption process in the glsl plugin's compression function.
When I thought of such a device, I thought it would be nice to have a decompression function.
Am I misinterpreting something?

Yeah, I think we've misunderstood each other. 😅

I thought glsl's compression feature was to reduce the package size after build.

vite-plugin-glsl's compression is actually a minifier which might use a default algorithm (with compress: true) or a custom callback passed to the same compress option. What it's aimed to do at the and of the day, is to strip away whitespaces from your shaders in order to reduce bundle size and load them a bit faster.

For such applications, I thought it would make sense to use a compression algorithm or encryption process in the glsl plugin's compression function.

Yeah, I agree, but I think at that point it would make more sense apply the same compression algorithm to the whole bundle and not only to your shaders.
I've found these compression plugins that might do just what you need, but I'm not sure about decompression. Maybe that could be something to develop from scratch...

https://github.com/vbenjs/vite-plugin-compression
https://github.com/alloc/vite-plugin-compress
https://github.com/nonzzz/vite-plugin-compression

Hope this helps, cheers!

Unfortunately, the plug-ins you mentioned do not seem to have any obfuscation effect.
The general compress/minify algorithm does not allow modification of the string content without permission.
In short, I was hoping for the effect that the string would not look glsl at first glance.
It would have been nice to have decompress: boolean|((s: string) => string) as well as the compress option.
Thank you for your consideration.

In short, I was hoping for the effect that the string would not look glsl at first glance.

Got it. Yeah, unfortunately that's out of scope of this plugin too.
No problem, thanks for using it. Please consider smashing a star button if you've found it any useful, thanks!


Run Danger from GHA

Move Danger job from Travis to GitHub Actions.
#no-changelog

What's different about the danger that is directly integrated to GitHub versus the danger run that is integrated into GHA (and was travis)?

@paulb777 TBH I was not aware of a GitHub danger version. Would you share a link please?

See the two danger runs in this PR - @morganchen12, do you know how danger is integrated?

See the two danger runs in this PR - @morganchen12, do you know how danger is integrated?

Discussed with Morgan: the check is added by the Danger run from CI - it is not a separate run.

Do you know why the check and danger runs are now both doubled on the PR?

Danger reports a separate check because it was initially designed to run from a travis before_script, which is unable to separate danger failures and main job script failures. It still does this in GHA, even though the GHA job is granular enough to report its own success/failure.


Automounts service account token for buildx testing postsubmit

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


[MOO-786]: Gallery widget text filter

Checklist

Contains unit tests ✅
Contains breaking changes ❌
Contains Atlas changes ✅
Compatible with: MX 9⃣
Did you update version and changelog? ✅
PR title properly formatted ([XX-000]: description)? ✅

Native specific

Works in Android ✅
Works in iOS ✅
Works in Tablet ✅

Feature specific

Comply with designs ✅
Comply with PM's requirements ✅

Please remove unnecessary emojis and sections and this comment before proceeding
This PR contains

[ ] Bug fix
[X] Feature
[ ] Refactor
[ ] Documentation
[ ] Other (describe)

What is the purpose of this PR?
Add a new filtering widget to gallery widget

@UrazAkgultan  please rebase and remember to use yarn :)

@UrazAkgultan there are few conflicts, it requires a rebase

@UrazAkgultan there are few conflicts, it requires a rebase.. it its also not targeting main

@diego-antonelli  Yes, I'm aware. The gallery widget's PR was separate in the old repo. First, we planned to release the gallery widget without the filtering feature, so the Gallery widget was reviewed and tested, but then we decided to release it with text filtering. It is the reason why targeting was the gallery widget's branch. I've updated it to the main branch.


ES6 is current now, so use "fill" instead of "filter" to get Function constructor

fill is supported only on chrome and firefox (on desktop browsers at least).
Not supported on explorer and mobile browsers
:-1:

I would also keep the filter method, as it is working for older browsers.

But many thanks for the suggestion! I love to see, that you are still trying to improve my mess.

We could change it in the future... After people stop using old IE, and the browsers will support ES6

As I see here only IE (are Microsoft going to release any new versions?), some old androids, Safari and old Node.js do not support this. I think we can enable this feature soon

I reopened this now, cause ES6 is now all around.


[SPARK-31426][SQL] Fix regressions of toJavaTimestamp/fromJavaTimestamp

What changes were proposed in this pull request?
Reuse the rebaseGregorianToJulianMicros() and rebaseJulianToGregorianMicros() functions introduced by the PR #28119 in DateTimeUtils.toJavaTimestamp() and fromJavaTimestamp(). Actually, new implementation is derived from Spark 2.4 + rebasing via pre-calculated rebasing maps.
Why are the changes needed?
The changes speed up conversions to/from java.sql.Timestamp, and as a consequence the PR improve performance of ORC datasource in loading/saving timestamps:

Saving ~ x2.8 faster in master, and -11% against Spark 2.4.6
Loading - x3.2-4.5 faster in master, -5% against Spark 2.4.6

Before:
Save timestamps to ORC:                   Best Time(ms)   Avg Time(ms)   Stdev(ms)    Rate(M/s)   Per Row(ns)   Relative
------------------------------------------------------------------------------------------------------------------------
after 1582                                        59877          59877           0          1.7         598.8       0.0X
before 1582                                       61361          61361           0          1.6         613.6       0.0X

Load timestamps from ORC:                 Best Time(ms)   Avg Time(ms)   Stdev(ms)    Rate(M/s)   Per Row(ns)   Relative
------------------------------------------------------------------------------------------------------------------------
after 1582, vec off                               48197          48288         118          2.1         482.0       1.0X
after 1582, vec on                                38247          38351         128          2.6         382.5       1.3X
before 1582, vec off                              53179          53359         249          1.9         531.8       0.9X
before 1582, vec on                               44076          44268         269          2.3         440.8       1.1X

After:
Save timestamps to ORC:                   Best Time(ms)   Avg Time(ms)   Stdev(ms)    Rate(M/s)   Per Row(ns)   Relative
------------------------------------------------------------------------------------------------------------------------
after 1582                                        21250          21250           0          4.7         212.5       0.1X
before 1582                                       22105          22105           0          4.5         221.0       0.1X

Load timestamps from ORC:                 Best Time(ms)   Avg Time(ms)   Stdev(ms)    Rate(M/s)   Per Row(ns)   Relative
------------------------------------------------------------------------------------------------------------------------
after 1582, vec off                               14903          14933          40          6.7         149.0       1.0X
after 1582, vec on                                 8342           8426          73         12.0          83.4       1.8X
before 1582, vec off                              15528          15575          76          6.4         155.3       1.0X
before 1582, vec on                                9025           9075          61         11.1          90.2       1.7X

Spark 2.4.6-SNAPSHOT:
Save timestamps to ORC:                   Best Time(ms)   Avg Time(ms)   Stdev(ms)    Rate(M/s)   Per Row(ns)   Relative
------------------------------------------------------------------------------------------------------------------------
after 1582                                        18858          18858           0          5.3         188.6       1.0X
before 1582                                       18508          18508           0          5.4         185.1       1.0X

Load timestamps from ORC:                 Best Time(ms)   Avg Time(ms)   Stdev(ms)    Rate(M/s)   Per Row(ns)   Relative
------------------------------------------------------------------------------------------------------------------------
after 1582, vec off                               14063          14177         143          7.1         140.6       1.0X
after 1582, vec on                                 5955           6029         100         16.8          59.5       2.4X
before 1582, vec off                              14119          14126           7          7.1         141.2       1.0X
before 1582, vec on                                5991           6007          25         16.7          59.9       2.3X

Does this PR introduce any user-facing change?
Yes, the to_utc_timestamp function returns the later local timestamp in the case of overlapping local timestamps at daylight saving time. it's changed back to the 2.4 behavior.
How was this patch tested?

By existing test suite DateTimeUtilsSuite, RebaseDateTimeSuite, DateFunctionsSuite, DateExpressionsSuites, ParquetIOSuite, OrcHadoopFsRelationSuite.
Re-generating results of the benchmarks DateTimeBenchmark and DateTimeRebaseBenchmark in the environment:

Item
Description

Region
us-west-2 (Oregon)

Instance
r3.xlarge

AMI
ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20190722.1 (ami-06f2f779464715dc5)

Java
OpenJDK 64-Bit Server VM 1.8.0_242 and OpenJDK 64-Bit Server VM 11.0.6+10

Test build #121130 has started for PR 28189 at commit 794cc5e.

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

Test build #121132 has started for PR 28189 at commit 94dc31e.

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

Test build #121130 has finished for PR 28189 at commit 794cc5e.

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

Test build #121132 has finished for PR 28189 at commit 94dc31e.

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

@cloud-fan @HyukjinKwon @dongjoon-hyun  Please, have a look at the PR.

Test build #121192 has started for PR 28189 at commit a28f2a1.

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

Test build #121192 has finished for PR 28189 at commit a28f2a1.

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

Merged build finished. Test FAILed.

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

retest this please

Test build #121209 has started for PR 28189 at commit a28f2a1.

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

Test build #121209 has finished for PR 28189 at commit a28f2a1.

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

Merged build finished. Test FAILed.

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

jenkins, retest this, please

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

Test build #121218 has started for PR 28189 at commit a28f2a1.

Test build #121218 has finished for PR 28189 at commit a28f2a1.

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

thanks, merging to master/3.0!

Hi, @cloud-fan .
This seems to break branch-3.0. Could you take a look at that once more?
[ERROR] [Error] /home/runner/work/spark/spark/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/DateTimeUtils.scala:181: not found: value millisToMicros
700
[ERROR] one error found

Sorry I didn't run tests when backporting as it only has a very small conflict. I've fixed it in branch-3.0 after local tests pass.

WDYT of merging https://github.com/apache/spark/pull/27618 to branch-3.0? Missing the changes in branch-3.0 causes problems already twice, see https://github.com/apache/spark/pull/27964#issuecomment-602153140

Thank you so much, @cloud-fan .


IA -> AI

It would be better to let only the name AI and no more IA

I completly agree that it's not coherent to call AI IA and IA AI.

this has been dealt with


fix: xfail some parquet tests due to item -> element change in pyarrow 13

following our solving of #346 we can xfail failing tests based on version combinations

Codecov Report

Merging #352 (bf4a663) into main (e30ad13) will increase coverage by 0.01%.
Report is 5 commits behind head on main.
The diff coverage is 100.00%.

:exclamation: Current head bf4a663 differs from pull request most recent head ee426a6. Consider uploading reports for the commit ee426a6 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main     #352      +/-   ##
==========================================
+ Coverage   94.80%   94.81%   +0.01%
==========================================
  Files          20       20
  Lines        2481     2487       +6
==========================================
+ Hits         2352     2358       +6
  Misses        129      129

Files Changed
Coverage Δ

src/dask_awkward/lib/io/parquet.py
92.07% <100.00%> (ø)

src/dask_awkward/lib/testutils.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[SMALL] Migrations: mention assembly when no contexts found

This is usually going to be because you have the wrong project selected
in Package Manager Console (or because you are in the wrong directory
for CLI). Writing out the info helps folks work out they have the wrong
assembly.
Fixes #5276

@natemcmaster could you take a quick look at this one

:shipit: assuming no tests need updating. I didn't find any tests that execute this code path :-(

Correct, that string is only used in the one place in our code base. I'll run a full build.cmd before pushing though.

Merged https://github.com/aspnet/EntityFramework/commit/5532d079847ebb60a29b3adfcc69c7f7833843ae


[bugfix] toISOString function also return null

toISOString(keep Offset?: boolean) function return string or null.
So, please rewrite moment.d.ts .

Merged in 651dff4d0c8914c9a9f73503bcb1a52e78de8a36

Sorry, I had to revert this. TS code breaks after the change: https://github.com/moment/moment/issues/6194

Sorry, I had to revert this. TS code breaks after the change: #6194

But this would be correct, right?
The Date.toISOString() spec says it either returns a string or throws a RangeError: https://tc39.es/ecma262/multipage/numbers-and-dates.html#sec-date.prototype.toisostring
Should Moment.js do the same?


Wont Run in Production only in Development

Hi guys I hope I can get some help. I have added the sidekiq-scheduler gem it was working fine in production until I changed the schedule from 1 day to 2 days. Now it seems to be stuck. It does not run anymore. Im not sure what is happening. I added the enable true which was missing before but the docs say that its set to true by default. I have restarted the workers and I can see that they are started and that they are scheduled but nothing happens. You can see my settings below. Thanks
2017-12-14T04:22:16.729284+00:00 heroku[worker.1]: Starting process with command bundle exec sidekiq -e production -C config/sidekiq.yml 2017-12-14T04:22:17.458493+00:00 heroku[worker.1]: State changed from starting to up 2017-12-14T04:22:25.469203+00:00 app[worker.1]: 4 TID-ou1q16mms INFO: See LICENSE and the LGPL-3.0 for licensing details. 2017-12-14T04:22:25.469204+00:00 app[worker.1]: 4 TID-ou1q16mms INFO: Upgrade to Sidekiq Pro for more features and support: http://sidekiq.org 2017-12-14T04:22:25.469997+00:00 app[worker.1]: 4 TID-ou1q16mms INFO: Booting Sidekiq 5.0.0 with redis options {:url=>"redis://redistogo:REDACTED@koi.redistogo.com:11606/"} 2017-12-14T04:22:25.500596+00:00 app[worker.1]: 4 TID-ou1q16mms INFO: Loading Schedule 2017-12-14T04:22:25.500603+00:00 app[worker.1]: 4 TID-ou1q16mms INFO: Scheduling reminder_queue {"every"=>["2d"], "class"=>"ReminderQueueWorker", "queue"=>"default"} 2017-12-14T04:22:25.503927+00:00 app[worker.1]: 4 TID-ou1q16mms INFO: Schedules Loaded 2017-12-14T04:22:25.503974+00:00 app[worker.1]: 4 TID-ou1q16mms INFO: Starting processing, hit Ctrl-C to stop
`
sidekiq.yml
development:
:concurrency: 5
production:
:concurrency: 6
:queues:

default
:enabled: true
:schedule:
reminder_queue:
every: ['2d']
class: ReminderQueueWorker

sidekiq.rb
require 'sidekiq'
if Rails.env.production?
Sidekiq.configure_client do |config|
config.redis = { url: ENV['REDIS_URL'], size: 3 }
end
end
procfile
web: bundle exec puma -C config/puma.rb
worker: bundle exec sidekiq -e production -C config/sidekiq.yml
release: rake db:migrate
`

Forgot to mention that it works when I force it by click the enqueue now button.

Just tested with a similar configuration, with every: '2d', manually advanced the system's calendar 2 days, and worked as expected.
Please note that if the sidekiq process started at 2017-12-14T04:22:25...+00:00, the every job will be enqueued at 2017-12-16T04:22:25...+00:00
Btw, could you format the config/sidekiq.yml file a bit?

Ya its weird cause it works fine on my staging and local but doesn't work on my production server. Its been stuck like that for a while. I changed the schedule multiple times. You can see when it ran last time here.

I have it formatted just copied and pasted the code came out like that lol.

It wasnt working but to test it out some more. I added the first_in: '120s' to force it to go faster. I will let you know if it works in 2 days from now so you can close this thanks!

Did the job run 120s after sidekiq started?
Did you explicitly set the job's queue? Smth like:
class SampleJob < ApplicationJob
  queue_as :milestones
  # ...

Hi thanks for getting back to me! The jobs did run after I added first_in: '120s', The jobs continued to run over the weekend. So it appears to be working now. I guess you have to tell them when they should start and not just how often. Although when I first implemented this gem I added when the jobs should start and it was working, BUT when I changed when the jobs should run from everyday to every 3 days thats when it stopped working. Even when I had it configured to start the first one after 12hrs. Thats why you can see that the last job ran a month ago in the picture I posted. By this time I had already deleted the option of when the job should start. So its working but something did go wrong at some point. Adding when the job should run made something happen I guess.  Not too sure what other feed back I can give you. Thanks again for the awesome gem :)


Ideas about DOCumenntation ..🙂

I feel we should have 'TROUBLEshooting' pages with all the common errors encountered while building apps using our platform. Also, we can recoMMEnD some solutions for these errors/warnings/problems, WHATever!
How ABOUT that?:) @mcollina
COMMON ERRORS, and their SOLUTIONS...🙂

cc @lucamaraschi... we need a proper writer for this.🙂

It's on our list! Thanks!


Deploy your Docker image to Kubernetes

As a developer
I need to deploy my Docker image to Kubernetes
So that I can manage and scale the microservice efficiently
Details and Assumptions
* Kubernetes cluster is set up and accessible.
* The Docker image for the microservice is available in a Docker registry.

Acceptance Criteria
gherkin
Given that I have access to the Kubernetes cluster
When I deploy the Docker image to Kubernetes using Kubernetes manifest files
Then the microservice should be deployed and running in the Kubernetes cluster
And I should be able to access the microservice via its Kubernetes service endpoint


[7923] Performance profile sign off completed page

Context
Performance profile sign off completed page
Changes proposed in this pull request
Added performance profile sign off completed page
Guidance to review

Important business

[ ] Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?
[ ] Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?
[ ] Do we need to send any updates to DQT as part of the work in this PR?
[ ] Does this PR need an ADR?

NB: Please notify the #twd_data_insights team and ask for a review if new fields are being added to analytics.yml

 Performance profile sign off completed page

Looks good @defong :shipit:


support webAssembly

What is the problem you're trying to solve
now docker already support   webAssembly
refer:https://docs.docker.com/desktop/wasm/

Describe the solution you'd like
support webAssembly like docker
Additional context
No response

What change is needed?

Hi, nerdctl team. I'm newer to nerdctl. But let me share my knowledge.
runc and youki already support running wasm.
https://containers.github.io/youki/user/webassembly.html
I wonder if it would be feasible to change the oci runtime via nerdctl and annotate the config.json? If we can do that, we can support them. As the youki team, please let us know if there is anything we can do to help.

nerdctl run --label is propagated to OCI runtime annotations, so it should just work?

I guess containerd-shim-wasmtime-v1 should also work?
https://github.com/deislabs/runwasi
Is there any change needed on the nerdctl side?

nerdctl run --label is propagated to OCI runtime annotations, so it should just work?

Awesome. Maybe this will work if it propagates to the OCI Runtime side that supports it.

I guess containerd-shim-wasmtime-v1 should also work?
https://github.com/deislabs/runwasi

I guess yes :+1:

Is there any change needed on the nerdctl side?

Perhaps from the user's side, if they pass the flag(e.g. nerdctl run --wasm ...), they can run it in wasm, or they want a frendly document for wasm?

extract from docker

--platform=wasi/wasm32. This specifies the architecture of the image you want to use. By leveraging a Wasm architecture, you don’t need to build separate images for the different machine architectures. The Wasm runtime does the final step of converting the Wasm binary to machine instructions.

So we should also support the platform wasi/wasm32 not sure that we support this on the nerdctl side

ctr do not require the to set the platform https://github.com/deislabs/runwasi#containerd-shim-wasmtime-v1

When I using the runwasi, the ctr can run successfully:
root@kay201:~# sudo ctr run --rm --runtime=io.containerd.wasmedge.v1 ghcr.io/containerd/runwasi/wasi-demo-app:latest testwasm2 /wasi-demo-app.wasm echo 'hello'
exiting
hello

But it can not used by the nerdctl:
nerdctl -n default run --rm --runtime=io.containerd.wasmedge.v1 ghcr.io/containerd/runwasi/wasi-demo-app:latest echo 'hello'

Output:
WARN[0000] cannot set cgroup manager to "systemd" for runtime "io.containerd.wasmedge.v1"
FATA[0000] failed to create shim task: Others("hook command exited with non-zero exit code: 1"): unknown

I think there may be some issue with the hooks :-)

I think there may be some issue with the hooks :-)

Could you open an issue in the runwasi repo?

When I using the runwasi, the ctr can run successfully:
root@kay201:~# sudo ctr run --rm --runtime=io.containerd.wasmedge.v1 ghcr.io/containerd/runwasi/wasi-demo-app:latest testwasm2 /wasi-demo-app.wasm echo 'hello'
exiting
hello

But it can not used by the nerdctl:
nerdctl -n default run --rm --runtime=io.containerd.wasmedge.v1 ghcr.io/containerd/runwasi/wasi-demo-app:latest echo 'hello'

Output:
WARN[0000] cannot set cgroup manager to "systemd" for runtime "io.containerd.wasmedge.v1"
FATA[0000] failed to create shim task: Others("hook command exited with non-zero exit code: 1"): unknown

I think there may be some issue with the hooks :-)

I met the question toooo.
Things were going well when I used ctr:
root@node-154:~/projects# ctr run --runtime io.containerd.wasmedge.v1 --platform=wasi/wasm docker.io/wasmedge/example-wasi:latest  example-wasm
Random number: -1232506751
Random bytes: [200, 18, 114, 41, 83, 31, 9, 234, 134, 63, 159, 196, 193, 237, 51, 255, 34, 117, 227, 155, 24, 195, 139, 77, 169, 0, 215, 32, 134, 82, 51, 107, 123, 71, 211, 188, 86, 176, 5, 8, 100, 35, 86, 209, 52, 135, 104, 236, 231, 95, 103, 130, 157, 252, 182, 98, 180, 189, 211, 33, 79, 71, 54, 60, 184, 72, 91, 85, 44, 23, 96, 210, 217, 226, 167, 99, 155, 231, 197, 89, 23, 224, 144, 229, 229, 240, 244, 37, 55, 200, 254, 192, 188, 4, 233, 146, 39, 179, 73, 75, 166, 205, 115, 183, 17, 101, 99, 205, 135, 113, 173, 111, 77, 89, 99, 195, 164, 186, 6, 147, 238, 27, 75, 211, 121, 144, 121, 167]
Printed from wasi: This is from a main function
This is from a main function
The env vars are as follows.
PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
The args are as follows.
/wasi_example_main.wasm
File content is This is in a file

But when I used nerdctl，it went wrong:
root@node-154:~/projects# nerdctl run --runtime io.containerd.wasmedge.v1 --platform=wasi/wasm docker.io/wasmedge/example-wasi:latest  example-wasm
WARN[0000] Platform "wasi/wasm" seems incompatible with the host platform "linux/amd64". If you see "exec format error", see https://github.com/containerd/nerdctl/blob/main/docs/multi-platform.md  error="unknown OCI architecture string: \"wasm\""
WARN[0000] cannot set cgroup manager to "systemd" for runtime "io.containerd.wasmedge.v1"
FATA[0002] failed to create shim task: Others("hook command exited with non-zero exit code: 1"): unknown

any update?


"Cannot read property 'type' of undefined" in CloseButton

:tada: This issue has been resolved in version 0.7.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


BadgeApp: Tailor text asking for justification for each question

"Please explain" is too generic - give more details specific to the question.  In some cases, perhaps an explanation shouldn't be there.

In many cases they may just be URLs, or have a URL in part.

Perhaps if you click "Met", don't show the justification (but then can't explain why), and only show when unmet.
In some cases, we may always want an explanation.  In others, the explanation may be optional for met.  In still others, may not want an explanation if it's met (don't show it).  In some cases, the answer may be a single URL.  E.G., for a ChangeLog, tell them just use the developer version of the ChangeLog.
The key issue is that on the one hand, we want to avoid shopping cart abandonment.  On the other hand, we want later readers outside the project to be able to confirm that a project really has met the criteria (since we're not doing third party vetting).
Perhaps put an asterisk by every box that needs to be filled out, i.e., make it clear in the UI what's required if some are required and some are not.  E-commerce uses "asterisk is required" - people are used to that.

Make it clear when you NEED to add an explanation, vs. when it's optional.
Debate: What should be done with "Met" and explanations?  We want to avoid shopping cart abandonment, vs. provide information for people who want to later verify.  Perhaps suggest "URL".

I recommend that several of the Met's should have an add optional explanation button that you have to click to see the text box.

The problem with "add optional explanation" is that it requires them to take an extra step, just to do an extra step.
There are several different issues here:

We need to make it clear what's optional, and what is not.  I think we need to make the display much clearer. To meet that, I've changed it so that if you say "Met" the placeholder text clearly says "(Optional)" at the beginning.  In contrast, if you say "Unmet" on SHOULD and SUGGESTED, it's now shown in yellow (it goes into the "required-data" class).  We can do many other visual cues; the key is to provide a visual queue when they HAVE to enter text vs. it being optional.
We need to simplify the display when there's clearly nothing that could be said.  I've added new met_suppress and unmet_suppress parameters so that when there's no useful text that could be supplied, the justification field never shows up.  E.G., "met_suppress" is set for oss-license-osi; if this is met (because your license IS approved by OSI) there's really no need to justify that, anyone can look at up at the OSI site.
We should tailor the questions, in at least some cases.  The form generator now supports "unmet_placeholder" and "met_placeholder" so that specific questions can be asked in specific cases, and I've made changes for oss-license-osi.  I will say, though, that simply making the default placeholder text different for the "met" and "unmet" situations makes a real difference... we might not need to make as many specific questions now.

The other recurring case is URLs.
--
Dan Kohn<EMAIL_ADDRESS>tel:+1-415-233-1000
On Thu, Oct 15, 2015 at 12:11 PM, David A. Wheeler<EMAIL_ADDRESS>
wrote:

The problem with "add optional explanation" is that it requires them to
take an extra step, just to do an extra step.
There are several different issues here:

We need to make it clear what's optional, and what is not. I think
we need to make the display much clearer. To meet that, I've changed it so
that if you say "Met" the placeholder text clearly says "(Optional)" at the
beginning. In contrast, if you say "Unmet" on SHOULD and SUGGESTED, it's
now shown in yellow (it goes into the "required-data" class). We can do
many other visual cues; the key is to provide a visual queue when they HAVE
to enter text vs. it being optional.
We need to simplify the display when there's clearly nothing that
could be said. I've added new met_suppress and unmet_suppress parameters so
that when there's no useful text that could be supplied, the justification
field never shows up. E.G., "met_suppress" is set for oss-license-osi; if
this is met (because your license IS approved by OSI) there's really no
need to justify that, anyone can look at up at the OSI site.
We should tailor the questions, in at least some cases. The form
generator now supports "unmet_placeholder" and "met_placeholder" so that
specific questions can be asked in specific cases, and I've made changes
for oss-license-osi. I will say, though, that simply making the default
placeholder text different for the "met" and "unmet" situations makes a
real difference... we might not need to make as many specific questions now.

—
Reply to this email directly or view it on GitHub
https://github.com/linuxfoundation/cii-best-practices-badge/issues/59#issuecomment-148491599
.

We probably need to merge the repo-url question into repo-track, and eliminate repo-url as a separate question.  We already ask for the project repo earlier; having this separate (and much later) is just confusing.  That would make it all simpler.

Oh, a quick note: Only a small amount of placeholder text is shown, so we don't want to make them long.  The  older IEs don't support placeholder; we could polyfill or make it a tooltip if that matters.

We've made it far more flexible and given the form MUCH better defaults.  I'm leaving this issue open until I walk through every criteria to try to craft more-specific placeholder text (or detail text).

I think addressing #259, plus the work done, resolves this.


Adding Azure Environment

Adding the ability to specify the Azure Environment so the module will work in clouds outside of the public one as well.
https://www.terraform.io/docs/language/settings/backends/azurerm.html#environment

Thank you for extending this! :)

This has been released as v0.1.28


Mapper

There are two methods in the Mapper trait that are unsafe. What would it take to make them safe ? Could we, e.g., error or panic if the frame is actually not unused ?

The map_to and identity_map are unsafe because the passed PhysFrame must be unused. There is no way to efficiently check whether a frame is used because we would need to traverse the whole page table hierarchie. While there are ways to make this lookup effective (e.g. an inverted page table), this isn't really something that the library can provide because it's too opinionated.
We could of course add an UnusedPhysFrame wrapper type that is unsafe to construct. Using this type, we could create safe variants of the map_to and identity_map methods. However, this would only shift the unsafety to a different place, so I'm not sure if that is what you want.

Could we cache whether the frame is used/unused within the frame itself ?

There might not be any memory available for this information in the frame. For example, imagine that we want to map a frame as stack memory: The CPU will potentially use every byte in that frame.

I meant in the PhysFrame type, as a field.

The problem is that PhysFrame has safe constructor methods, so nothing is preventing the programmer from constructing two PhysFrame instances that represent the same frame.
I think the UnusedPhysFrame type could make sense since the FrameAllocator already uses a similar approach (unsafe to implement, returned frames must be unused). By making the FrameAllocator return UnusedPhysFrames, most of the time no unsafe is needed for calling map_to etc.

Sounds good!

I opened #89 with these changes.


Fix uneven trailing whitespace in strings

Found as part of https://github.com/JuliaLang/julia/pull/46372 - the reference parser treats lines of uneven whitespace in a weird inconsistent way so there's some differences in whitespace in the final deindented string. This change removes those differences.

Thanks Claire and happy to see you again! 💜

Thanks! :heart:


BottomSheetController - random crashes

Hello @thomsmed, Thanks for your repository, very helpful!
I can see one crash reported from Crashlytics with this code.
    func start(moving presentedView: UIView, interactiveDismissal: Bool) {
        self.interactiveDismissal = interactiveDismissal

        heightAnimator?.stopAnimation(false)
        heightAnimator?.finishAnimation(at: .start)
        offsetAnimator?.stopAnimation(false)
        offsetAnimator?.finishAnimation(at: .start)

        heightAnimator = createHeightAnimator(
            animating: presentedView, from: presentedView.frame.height
        )

        if !interactiveDismissal {
            offsetAnimator = createOffsetAnimator(
                animating: presentedView, to: stretchOffset
            )
        }
    }

It crashes on this line:
        heightAnimator = createHeightAnimator(
            animating: presentedView, from: presentedView.frame.height
        )

This is not really frequent, but sometimes it happens with this fatal error:
Fatal Exception: NSGenericException
*** Collection <__NSArrayM: 0x28073bed0> was mutated while being enumerated.

Here is the stacktrace from Crashlytics:

Any idea how to fix this crash? Thank you so much!!

Any idea @thomsmed? 🙏🤞

Hi! And sorry for my super duper late reply 😅 I had a quick look at it, and I can't see any immediate reason for this to happen (also tried to provoke a crash, but no success). But I suspect there are some edge cases where the two UIViewPropertyAnimators "steps on each others toes" (maybe if the user fiddles too much with the bottom sheet?)
Anyway. I've wanted for a long time to improve this example code, as it has some issues... And are currently working on some updates inspired from the latest example project added to this repo (Interactive animations with UIViewPropertyAnimator).
Hopefully I'll have an updated BottomSheetController example ready soon! And I hope that will also address weird issues like the one you are experiencing.
It makes me really happy that people are actually finding these example project useful, so keep the feedback coming! 😄 And I'll try to reply faster in the future 😅

Thank you so much, cannot wait for that!! 🙏

Alright! I have now updated the example code for BottomSheetController. I think the changes bring great improvements to both code and behaviour of the bottom sheet.
Merged with #37
Go and check it out! 😄 It depends a little bit on how you've utilised this example code in your own app, but everything should work as before 🙏
Hopefully these changes will also address the issues you were seeing.
Closing this GitHub issue.


TOMEE-2612 - updated  javaee-api to 8.0-1

We need to resolve MR conflics, I guess :)

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

We are on the way to 8.0-2 so this PR needs an update :)

As 8.0-2 is ready now, we should update this PR and the JIRA to reflect latest changes :)

@cesarhernandezgt Is this PR still needed?

@cesarhernandezgt Is this PR still needed?

We can close this PR. But I'll update TomEE since it seems now apart from the version we also need to fix the maven version format: https://github.com/apache/tomee/blob/master/examples/access-timeout-meta/pom.xml#L57


Setup Sidekiq to Process Battery Data

https://github.com/mperham/sidekiq

Add HourEnergy to store it afterwards


Fix RMC FixTime parsing that can lose sub-second precision with doubles

When calling AddSeconds on the DateTimeOffset, in .NET 6 it rounds the double to the closest millisecond value. However, this changed in .NET 7. https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/7.0/datetime-add-precision
Regardless of whether or not this package adds .NET 7 support, this change will ensure that we don't lose any subsecond precision from the NMEA message.
For NMEA messages that have less than 3 digits of precision, this will not change any behavior
"$GPRMC,141825.2,A,4249.92297,N,08548.52186,W,000.01,227.1,040322,005.5,W*54"
But for NMEA messages with more than 3 digits of precision, this will preserve that precision.
"$GPRMC,141825.1999,A,4249.92297,N,08548.52186,W,000.01,227.1,040322,005.5,W*54"

#116

@dotMorten we would appreciate this getting in soon so we can make the switch to .NET 8. Thanks!


[Bug][Pipeline] The pipeline gets stuck if the tool has not space let in the disk

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
When we have too many pipelines running at the same time, the git extractor gets full, and the disk gets full. The pipeline gets stuck and does not even respond to the stop command.

What do you expect to happen
I believe the cancel pipeline command would stop the pipeline and clean the /tmp folder to be able to reschedule the pipelines to different times.
How to reproduce
Run pipelines in parallel that collets a number of git repos that are bigger than the disk space collects.
Anything else
Thanks for reading my post.
Version
v1.0.1-beta9@e061ef2
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

Hi @dosu, Thanks for the points. They are useful, but I believe I should have them embedded in the tool as a user. If I click to stop the pipeline, it needs to stop and clean the disk by itself.
It will help the user to keep going without needing technical intervention, as now it just makes the pipelines stucked.


User is not showing up in my req

I run this code and I login with Google, but no user is stored in req, so when it redirects back to the index page, it still shows "Login" and NOT "account". Why/How can this be?
I put a breakpoint in my "function (request, accessToken, refreshToken, profile, done) {" and it shows profile is filled with data and so I "return done(null, profile)", but I can't access profile or user anywhere else

I have the same problem, did you manage to solve it? @SethKitchen

Same issue here

You mean in the example I suppose? This is presumably because the example doesn't actually set up any proper session storage (it just assumes there's a redis instance running somewhere, which doesn't really make sense.) The example really should be reworked to use an in-process memory storage solution to avoid having this external dependency.


frida.attach does not work for Linux->iOS

...got xpcspy working on iOS 14.2 on an iPhone 8 with a Linux host but I had to change this line :) Awesome project!
I also noticed that Jetsam might kill processes with too many XPC messages when attaching to them, at least without filter. I already increased the Jetsam limits for the target process. In my experience, processing as few data as possible with JavaScript/Frida can solve such issues.

Awesome, thanks! Also could you give an example of a process to produce the problem on iOS?


Http requests doesn't work in background

It seems that the plugins success to find position even on background and even when screen is locked (Android device - Samsung Galaxy S7). But HTTP requests using Axios are not getting sent after 4-5 minutes.
Is there any fix for this?

I had the same issue, i used Fetch (native javascript) to do the http post. And found some advice to use this cordova-plugin-advanced-http. And it works, i have been testing it, but so far okay.

I have the same problem for my Huawei Mate 20 Pro with power management set to manual. I'm doing my own POST method instead of the built in one. @ekohadim, how has your mentioned change gone? Has it worked past the 5mins? The funny this is after the phone wakes up, it then starts POSTing the data again, as per my question here and so catches up on the geolocation. It takes an app that is real time in to a delayed realtime, so it sort of doesn't work as it should.
https://forum.ionicframework.com/t/httpclient-infinity-timeout/183413/2


SDS + Gridding

Hi Ethan,
Thank you so much for the interesting work. I am currently working on a project utilizing SDS for NeRF optimization. In your implementation, Grid Prior seems like a promising trial for me. I saw you commented in your code that Gridding is not working for SDS right now (here). Could you please elaborate more on this? Much appreciate!

Hey! So that comment is misleading and SDS should work too! I just didn't implement it since I prefer using dataset updates instead of SDS.
In summary, I only experimented with SDS vs. dataset updates (in an apples-to-apples comparison) for full images. This is not to say that SDS with grid prior cannot be used, though! Feel free to implement it for SDS if you'd like. :)
However! One issue you'll find with SDS is that it will be challenging to use > 4 images for joint inpainting. This requires averaging over multiple grid permutations while denoising images, and I don't see a straightforward way to do this with SDS. Hopefully this helps! Thanks for your patience on my reply.


Add update node auth

Description of change
Add update node auth
Links to any relevant issues
Fixes #1690
Type of change

Enhancement (a non-breaking change which adds functionality)

How the change has been tested
Added test and nodejs example
        await manager.updateNodeAuth("https://api.testnet.shimmer.network", {basicAuthNamePwd: ["name", "password"]});
        await manager.updateNodeAuth("https://api.testnet.shimmer.network");

logs
2023-02-21 16:06:35 (UTC) reqwest::connect                           DEBUG starting new connection: https://api.testnet.shimmer.network/
2023-02-21 16:06:35 (UTC) iota_client::node_manager::http_client     DEBUG GET: 202 ms for 200 OK https://api.testnet.shimmer.network/api/core/v2/info
2023-02-21 16:06:36 (UTC) iota_wallet::account::update               DEBUG [UPDATE ACCOUNT WITH NEW CLIENT] new bech32_hrp: rms
2023-02-21 16:06:36 (UTC) iota_wallet::account::update               DEBUG [SYNC] storing account Alice after updating it with new client options
2023-02-21 16:06:36 (UTC) iota_wallet::account::handle               DEBUG [save] saving account to database
2023-02-21 16:06:36 (UTC) iota_wallet::account::update               DEBUG [UPDATE ACCOUNT WITH NEW CLIENT] new bech32_hrp: rms
2023-02-21 16:06:36 (UTC) iota_wallet::account::update               DEBUG [SYNC] storing account Bob after updating it with new client options
2023-02-21 16:06:36 (UTC) iota_wallet::account::handle               DEBUG [save] saving account to database
2023-02-21 16:06:36 (UTC) iota_wallet::message_interface::message_handler DEBUG Message: UpdateNodeAuth{ url: https://api.testnet.shimmer.network/, auth: <omitted> }
2023-02-21 16:06:36 (UTC) iota_wallet::account_manager::operations::client DEBUG [update_node_auth]
2023-02-21 16:06:36 (UTC) iota_wallet::storage::manager              DEBUG save_account_manager_data
2023-02-21 16:06:36 (UTC) iota_client::node_manager::syncing         DEBUG sync_nodes
2023-02-21 16:06:36 (UTC) reqwest::connect                           DEBUG starting new connection: https://api.testnet.shimmer.network/
2023-02-21 16:06:36 (UTC) iota_client::node_manager::http_client     DEBUG GET: 395 ms for 200 OK<EMAIL_ADDRESS>2023-02-21 16:06:36 (UTC) iota_wallet::account::update               DEBUG [UPDATE ACCOUNT WITH NEW CLIENT] new bech32_hrp: rms
2023-02-21 16:06:36 (UTC) iota_wallet::account::update               DEBUG [SYNC] storing account Alice after updating it with new client options
2023-02-21 16:06:36 (UTC) iota_wallet::account::handle               DEBUG [save] saving account to database
2023-02-21 16:06:37 (UTC) iota_wallet::account::update               DEBUG [UPDATE ACCOUNT WITH NEW CLIENT] new bech32_hrp: rms
2023-02-21 16:06:37 (UTC) iota_wallet::account::update               DEBUG [SYNC] storing account Bob after updating it with new client options
2023-02-21 16:06:37 (UTC) iota_wallet::account::handle               DEBUG [save] saving account to database
2023-02-21 16:06:37 (UTC) iota_wallet::message_interface::message_handler DEBUG Response: Ok(())
2023-02-21 16:06:37 (UTC) iota_wallet::message_interface::message_handler DEBUG Message: UpdateNodeAuth{ url: https://api.testnet.shimmer.network/, auth: <omitted> }
2023-02-21 16:06:37 (UTC) iota_wallet::account_manager::operations::client DEBUG [update_node_auth]
2023-02-21 16:06:37 (UTC) iota_wallet::storage::manager              DEBUG save_account_manager_data
2023-02-21 16:06:37 (UTC) iota_client::node_manager::syncing         DEBUG sync_nodes
2023-02-21 16:06:37 (UTC) reqwest::connect                           DEBUG starting new connection: https://api.testnet.shimmer.network/
2023-02-21 16:06:37 (UTC) iota_client::node_manager::http_client     DEBUG GET: 344 ms for 200 OK https://api.testnet.shimmer.network/api/core/v2/info

Change checklist

[ ] I have followed the contribution guidelines for this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that new and existing unit tests pass locally with my changes

Conflicts :(


Add optional string extension for checking if nil or empty

Swift 3.1 opens a new world of extensions by allowing to target concrete types. This is an optional string extension for checking for isNilOrEmpty stolen from C#. Unit test included.
Instead of this:
if optionalStr == nil || optionalStr?.isEmpty == true {
    blah.. blah.. show warning.. etc..
}

Do this:
if optionalStr.isNilOrEmpty {
    blah.. blah.. show warning.. etc..
}

@basememara Thank you for your contributions 🎉
If you could please fix this breaking build due to specializing a generic parameter I would appreciate it.
This may be better suited as a String extension rather than on Optional.
I don't think there is a good protocol to constrain Wrapped to.
It doesn't make sense to use something like ExpressibleByStringLiteral.
If you decide to keep it in Optional then please move it to the Optional file.

I think the build is failing because the .travis is targeting Xcode 8.2. I have another PR for updating the .travis config.

I just saw your comments in the other PR, makes sense. We might have to hold off on this extension if this is something we want to add. Thanks for the feedback 👍

@basememara thank you! I'm hoping we can update to Xcode 8.3 and remove this limitation.


Change tests to use updated XCTestCaseProvider protocol

Updated swift-corelibs-foundation tests based on changes made in https://github.com/apple/swift-corelibs-xctest/commit/e5c0cb36bc445d0522f7ec28a8342b2681f68666.

Thanks!


fix When col stats is Unknow, not expression should return the stats with selectivity of 1

Proposed changes
When col stats is Unknow, not expression should return the stats with selectivity of 1

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 46.73 seconds
stream load tsv:          551 seconds loaded<PHONE_NUMBER>9 Bytes, about 129 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.1 seconds inserted 10000000 Rows, about 343K ops/s
storage size:<PHONE_NUMBER>3 Bytes

run builldall

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 47.3 seconds
stream load tsv:          558 seconds loaded<PHONE_NUMBER>9 Bytes, about 127 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.2 seconds inserted 10000000 Rows, about 342K ops/s
storage size:<PHONE_NUMBER>5 Bytes

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 46.37 seconds
stream load tsv:          544 seconds loaded<PHONE_NUMBER>9 Bytes, about 131 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          28.8 seconds inserted 10000000 Rows, about 347K ops/s
storage size:<PHONE_NUMBER>6 Bytes


Shortcuts Ctrl + r, Ctrl + s, Ctrl + t of Explore & SQL Lab

There's no Ctrl + r hot key & Ctrl + s invokes default Chrome save page in Explore.
Ctrl + t invokes default Chrome new tab in SQL Lab.
There's one Chromium issue about Ctrl + t

Issue 33056: Ctrl keys: Ctrl-N, Ctrl-T and Ctrl-W no longer available to client side JavaScript in Chrome4

In Chrome 4 it works similary to Firefox, except some keyboard combination:

Ctrl + N
Ctrl + Shift + N
Ctrl + T
Ctrl + Shift + T
Ctrl + W
Ctrl + Shift + W

These combinations cannot get captured by Javascript.

Expected results
All shortcuts work.
Actual results
Explore hot key Ctrl + r does not exist.
Explore hot key Ctrl + s invokes default Chrome save page.
SQL Lab hot key Ctrl + t invokes default Chrome new tab.
Screenshots
Explore hot keys

SQL LAb hot keys

How to reproduce the bug 1

Go to a chart
Press Ctrl + r & Ctrl + s
Hot key Ctrl + r does not exist
Hot key Ctrl + s invokes default Chrome save page

How to reproduce the bug 2

Go to SQL Lab
Press Ctrl + t
Hot key Ctrl + t invokes default Chrome new tab

Thanks for the bug report! We'll look into it.

The UI has changed slightly, so I have created a new ticket to reflect the new UI: https://github.com/apache/superset/issues/12429
Can we close this ticket?

The UI has changed slightly, so I have created a new ticket to reflect the new UI: https://github.com/apache/superset/issues/12429
Can we close this ticket?

The UI has changed slightly, so I have created a new ticket to reflect the new UI: #12429
Can we close this ticket @junlincc?

yes! thank you so much @eschutho

The UI has changed slightly, so I have created a new ticket to reflect the new UI: #12429
Can we close this ticket @junlincc?

yes! thank you so much @eschutho


Inject head tag in a different position

Hi there, regarding styled component head tag:

Is there a way to configure in which position inside the HEAD the highlighted tag will be injected ?

relevant to this topic, I also have an issue with styled-components version 5.0.1! Since we have this post here, I did not create a new issue thread!
it's fully described in a stackoverflow post... would be good to have a follow up on it

relevant to this topic, I also have an issue with styled-components version 5.0.1! Since we have this post here, I did not create a new issue thread!
it's fully described in a stackoverflow post... would be good to have a follow up on it

It looks like we have roughly the same issue, using both sass and styled components. How can I give priority to those sass styles gathered with minicssplugin rather than styled components stuff?

Bump on this issue if possible.
It would be good to get a direction on this.
We have an issue whereby we manage a react component library. We want to move to styled-components but in doing so styled-components styles will override our customer's styles due to the position in the head.
So you need to increase specificity from a customer style's point of view. Which could be a breaking change and work for them.
I found an issue: https://github.com/styled-components/styled-components/issues/1707
which said to add a placeholder into the head.
This seems to work ie: <style data-styled="active" data-styled-version="5.1.1"></style>.
Meaning other app styles appear after the styled-components styles.
But I am not sure if this is a recommended direction on this issue.

Have similar issue #3181


investigate excessive memory usage while zooming

Memory usage can spike occasionally while zooming. Sometimes it's severe enough for iOS to terminate the app.
I can reproduce this on the example app by zooming in/out in an area such as Los Angeles or San Francisco where there is a lot of detail on the map.

here's what I've found so far:
Vector tiles, when decoded from protobuf, consume a lot of memory, easily exceeding 1GB.
There are three GC root paths that retain these decoded tiles:

the vector tile cache
tiles being displayed on the map (corresponding to map widgets)
tiles that are being processed (e.g. in an isolate)

During zooming the problem is exacerbated, because there are more tiles on the map, and if you zoom quickly enough you can have processing on isolates that is no longer needed due to tiles having been requested but not completed processing. The queue of work can easily get over 50.
My plan to address it:

eliminate the vector tile cache completely, and in its place add a byte cache. Each tile will consume roughly 40kb, meaning that we can have ~250 tiles cached in a 10MB memory space
add cancellation to processing so that obsolete jobs can be discarded quickly, freeing up related memory and eliminating unnecessary processing
introduce LIFO to the execution queue, increasing the chance of having obsolete processing tasks and improving task completion latency when multiple jobs are queued
consider reacting to memory pressure more aggressively by releasing vector tile data for map tiles that are visually displayed

Experiment on flutter-vector-map-tiles/tree/memory-investigation
learning so far:

RSS usage seems to be the issue, since overall app memory usage is small, but RSS can grow to 0.8GB and higher
enabling background rendering can contribute to greater RSS usage
rarely I'll see a huge (>600MB) jump in Raster Picture memory
tap-to-zoom to a high zoom can reproduce the crash
the changes on the above branch appear to reduce likelihood of crashes

Further experimentation has lead me to observe that Raster Picture memory usage remains nominal as long as the map zoom is not far beyond the tile zoom.
In my example, map tile data is limited to a maximum zoom of 14, whereas I have the maximum zoom of the map set to 20. The map layer will allow zooming beyond the maximum zoom of the tile data by rendering tile size 14 at the map zoom size (in this case, up to 20).
When I have the map zoomed to level 14, I don't see any Raster Picture memory usage on the memory timeline. Following is a zoom level to observed RasterPicture memory usage:

Zoom
Maximum Observed Raster Picture Memory Usage

14
0

15
130MB

16
280MB

17
1.1GB

Memory usage varies depending on the tile being rendered, with some tiles needing much less than observed.
My current theory is that Canvas must allocate memory to render details outside of the visual area, and that the amount of memory used corresponds both to the size of the canvas and to the level of detail in the tile.
Increasing the difference between the tile zoom and the map zoom causes increased memory usage, so should be limited to devices that can supply the necessary memory.
A viable workaround is to limit the maximum zoom of the map to the same as the maximum available tile size, or within one level higher.
Recommendation: For maps that display on mobile devices, with a map tile with maximum zoom of 14, limit the map maximum zoom to 15.

My current theory is that Canvas must allocate memory to render details outside of the visual area, and that the amount of
memory used corresponds both to the size of the canvas and to the level of detail in the tile.

Can the canvas be restricted somehow to not allocate memory outside the drawing area?
At a first glance, it sounds strange, that rendering at high zoom levels consumes so much memory - because the details are usually much less then in a low zoom level.
I also saw the the renderMode setting was removed, especially "raster". A bit above raster cache is mentioned. Is this still an issue? (currently I am experimenting with maximumZoomDifference: 4)

Can the canvas be restricted somehow to not allocate memory outside the drawing area?

Not that I'm aware of. Feel free to open a ticket with the flutter team, perhaps this is something that they could fix.
The raster cache has been removed completely so it should no longer be an issue.
In my testing having a zoom difference greater than the default caused issues, but I left it configurable since I didn't want to presume the use-case (e.g. device memory, tile source)

Thanks, unfortunately I don't have the background knowledge to open a ticket with the flutter team.
Thanks for the impressive work on this module.

You’re welcome!
Out of curiosity why do you want such a large zoom offset?
On Sun, Jun 19, 2022 at 10:32 AM Alexander Menk @.***>
wrote:

Thanks, unfortunately I don't have the background knowledge to open a
ticket with the flutter team.
Thanks for the impressive work on this module.
—
Reply to this email directly, view it on GitHub
https://github.com/greensopinion/flutter-vector-map-tiles/issues/24#issuecomment-1159781302,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEKDQ7VFSXLDU43BR7ZYH2DVP5KUNANCNFSM5MBF4JHQ
.
You are receiving this because you modified the open/close state.Message
ID: @.***
com>

@greensopinion I believe the standard openmaptiles only support zoom level 14 and in our app we want to be able select positions with a higher accuracy (zoom 18)
I am wondering if this canvas problem also effects performance in other regards.
We were trying also the mapbox GL flutter package and it feel much faster (also with OSM Liberty). But maybe that's something for another thread.

I believe the standard openmaptiles only support zoom level 14 and in our app we want to be able select positions with a higher accuracy (zoom 18)

I'm using zoom 14 tiles at zoom 16 without issue. To go higher, I recommend looking at another source of tiles. For example, Mapbox goes to zoom level 22.
Performance of native and web-based map libraries is much better. This library has a long ways to go to get rid of jank fully. Performance is much better without memory pressure, so avoiding over-zooming will help.


[Feature Request] Multisite Support with Global Tables

Hi, it would be nice if multisite could be supported to facilitate easier deployment and management across networks.
It could work like this:

The plugin checks if it's network enabled. If yes, then store the settings network-wide. or
Add support for constants that can be declared in wp-config.php (should help with automated deployments as well) or
both

Thank you for considering.

Thanks for your message.
Will look into this WordPress "Multisite" feature to see what we could do.

Hi @julienloizelet
There is any support for wordpress constants to configure many websites at same time ?

There is any support for wordpress constants to configure many websites at same time ?

Hi @bilyboy785, not for now.
Thanks

Hi @taropaa ,
I just released a 2.5.0 version of the plugin that supports Multisite installation:

Plugin has to be network activated
we store and use settings in the wp_sitemeta table (instead of the wp_options table for a single WordPress installation).

Thanks


New role "rmt"

@krtek4, @sephii do you think that it will make sens to create a RMT role? Maybe it could help to spread RMT usage for RVF users...

This means we'd absolutely need to have the git config copied in the box so that the commits are done with the correct author. Also I don't feel it's something that's of the box concern but more of the project concern (apart from adding RMT to the project we would install anything else, except perhaps PHP, right?).

Yes, this means the ability to be able to commit from the box. But this is already what are doing many RVF users.
And then yes, it related to the project developper tools. But same as for Fabric, but it's more easy to have all the developers tools in the box.

Is RMT installable "globally" like composer is ?
If it is the case, it makes sense to have a role, if he has to live in the project directory, I am a lot less sure.

Yes, it's possible: https://github.com/liip/RMT#option-2-composer-global-installation

How would you define if it's fits for a role or not?

the PR was merged !


Input/output image resolution

Is it possible to train and run a model with 1028x1028 pixels images?

Here they discus 512x512 and 1024x1024
https://github.com/affinelayer/pix2pix-tensorflow/issues/22

Thanks Sam


[3434][Perf]: Partial fragment support

We are currently migrating to the new Apollo codegen.
However, the new codegen runs for over 30 minutes and uses a lot of memory to generate the latest Swift types, and our CI is constantly failing to complete.
I'm opening this PR to suggest collecting feedback from the repo authors before committing further. I suspect this is related to https://github.com/apollographql/apollo-ios/issues/3434.
What is going on?
Whenever the RootFieldBuilder
https://github.com/apollographql/apollo-ios-codegen/blob/6db35551c7bc0879b61539c08338253a7b4a146b/Sources/IR/IR%2BRootFieldBuilder.swift#L6
tries to build named fragments via buildNamedFragmentSpread https://github.com/apollographql/apollo-ios-codegen/blob/6db35551c7bc0879b61539c08338253a7b4a146b/Sources/IR/IR%2BRootFieldBuilder.swift#L401
It will eventually try to reuse a previously built fragment in BuiltFragmentStorage. Some fragments can contain large numbers of entities which might not be relevant to the original intent.
With this PR, I suggest adding the ability to use partial fragments, which would reduce the number of data to be merged into the EntitySelectionTree.
For this example, I'm reducing the filtering out of entities with FieldPaths larger than 3 in depth.
With this change, the same swift output is generated against our schema, but the duration is reduced from 30 to 3 minutes, and the memory usage is reduced to 400 MB.

@igor-florescu-ck: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

🛠 Docs Preview Building...

Configuration
{
  "repoOverrides": {
    "apollographql/apollo-ios-dev@main": {
      "remote": {
        "owner": "igor-florescu-ck",
        "repo": "apollo-ios-dev",
        "branch": "feature/3434/codegen-perf"
      }
    }
  }
}

2c49f9c2847ba566df94a09ad2aa63a304e6320d


LICENSE file missing

Thank you for making this interesting plugin.
I can't find if the source is released under a license. Is there a license?

Hi @crshrprt! I have added the basic MIT license to the project. Feel free to use and modifiy the code to your liking. Thank you and have a good day!


Gossip trust values at an ordinal.

Gossip trust values at an ordinal.

This PR is superseded by PR https://github.com/Constellation-Labs/tessellation/pull/684.


Discussion: Parsing of documents/Link scraping.

As part of making signup as easy as possible, we are thinking if there would be any benefit of adding an uploaded document parsing and the ability to add a link to be sourced and imported.
We are not sure, what do you think?

@DevvKris @nocategory I have moved this issue to feedback repo, as it would require changes on API side.
We can keep discussing it here. :)

Let me post here small update with more information. :slightly_smiling_face:
After few internal discussions we cleared out that not only this is possible to do without modifying the API, but also that we would probably prefer to do it in this way.
The current API already exposes mutations to change profile data (like skills and such), so document parsing/profile import can be done either completely in browser (if it's practical) or as separate small service which we can host.
Big benefit of both approaches is that both can be done as opensource projects.
So, if anyone is willing to help with this, please let us know what way would you prefer.
Links to any resources for doing it on the browser side are also welcome, as well as any thoughts on security and performance side of it. I think we would like to avoid going with a solution that compromises security of community members or makes browser to slow your device to a halt. :slightly_smiling_face:

That’s great news!

I am more of a back-end person, so I am a bit biased on this matter. I am more inclined in favor of a separate microservice, but I'm not sure about the security aspect of this decision.
The reason I favor this approach at this point is that it separates concerns of components inside the system: candidate-web provides the service of representation, the back-end API provides the service of the core business logic.
I have, however, coded up a small example for front-end file upload in vanilla JS (har-har) to prove the concept. It expects text files, but I know for certain this can be extended to images. It can probably be extended to PDF files as well:
https://codepen.io/lilsweetcaligula/pen/WmRKVy
P.S. Do I understand correctly we can use this on frontend with something like webpack?
https://www.npmjs.com/package/pdf-parse

I am more of a back-end person, so I am a bit biased on this matter. I am more inclined in favor of a separate microservice

That's our point of view right now as well, yet it really depends on community I think.
Also, given links that you provide, I have the feeling that it will be easier and faster to try out implementing it in browser first.
If it will not work out, we can fallback to backend implementation.

but I'm not sure about the security aspect of this decision.

If we'll roll with implementation in browser, my guess would be that the big question would be "can malicious PDF hurt user in any way?". But, on the other hand, Firefox uses similar approach and is considering that to be secure, and we do not expect users to try to parse random PDFs from malicious actors. (Should we? :slightly_smiling_face: )
If we roll with implementation on the backend, then it's mostly about trust that backend does what expected with PDF and nothing more. If the service will be opensource, everyone can see what is it doing with provided data. Then it's mostly the trust that we haven't made any malicious adjustments while deploying it.
I am not aware of any interest on our part to hoard PDFs, and given the whole direction EU takes with protection of personal data (see GDPR for example), my guess would be that it is in our best interest to not store them.

https://codepen.io/lilsweetcaligula/pen/WmRKVy

Yep, FileReader can be used to read file that user provides.
But instead of fileReader.readAsText(file) we can do fileReader.readAsBinaryString(file) or fileReader.readAsArrayBuffer(file), depends on what will work best to get data to pass to pdf-parse.

P.S. Do I understand correctly we can use this on frontend with something like webpack?
https://www.npmjs.com/package/pdf-parse

To me right now it look like we can. It uses pdf-js which should work in browsers (Firefox uses it).
If anyone would try it out and provide some kind of proof-of-concept of extracting text from PDF uploaded via FileReader, we would be grateful. :slightly_smiling_face:

@ivan-kolmychek-devv I tried to get a proof of concept and sort of succeeded. I successfully set up the upload form, selected a .pdf file and had its output logged to the console.
However, there's one problem that I may need help with. The pdf.js package which is the basis for all of the PDF libraries, requires a worker, to which it sends GET requests, e.g.:
express:router dispatching GET /static/pdf.worker.js
express:router dispatching GET /0.js

Two issues:

the worker is served as text/html with the Vue's app scaffold. The pdf.js package complains because it expects application/javascript. Surprisingly it still parses the pdf file and logs output.
the 0.js script is apparently generated by the pdf.js package. I have not figured out what 0.js does exactly, or how to customize its generation path. Nothing is spawned in the root directory. While seemingly not causing issues, I'd rather know what it is.

I coded the logic dependent directly on the pdf.js interface because packages like pdf-parse and pdf2json caused issues with setting them up. It should not be a problem, however.
I have not submitted a PR because of the outlined issues.

Interesting.
I am not sure I have answers to these issues right now, as I don't have any experience with these libs. I hope someone else will pop up in thread that does, but until then let's try to sort it out. :slightly_smiling_face:

I have not submitted a PR because of the outlined issues.

Not all the contributions have to be in form of PRs. You have spent your time researching the issue and wrote here about results that you wrote. To me this sounds like a sizable contribution already. :slightly_smiling_face:

I coded the logic dependent directly on the pdf.js interface because packages like pdf-parse and pdf2json caused issues with setting them up. It should not be a problem to resolve the issues with the packages, however.

Can you share which issues did you stumbled upon? This way either someone can share the way to resolve them, or at least everyone else who wants to take a shot at an issue will be warned about them. :slightly_smiling_face:

However, there's one problem that I may need help with. The pdf.js package which is the basis for all of the PDF libraries, requires a worker, to which it sends GET requests ...

Just to clarify - worker as in separate process running on users machine? Or ServiceWorkers? Or WebWorkers?

the worker is served as text/html with the Vue's app scaffold. The pdf.js package complains because it expects application/javascript. Surprisingly it still parses the pdf file and logs output.

Do I understand correctly that there is an issue with how the webpack-dev-server serves the files from pdf.js? Or are we talking about any other (separate) server that you have to run?
Please let me know if I misunderstand something, I am pretty sure your knowledge and experience on this right now are bigger than mine. :slightly_smiling_face:

M'eh, the culprit was a typo in the worker's path.
HTML was rendered because when no path was found, the app would reply with a basic HTML scaffold (not the 404 page). I solved (?) the problem by requiring pdfjs-dist/webpack to have the worker configured automatically.
If needed, you can actually copy the worker over to the static folder and point the library to it, I explained how in the comment in the source code inside the CvUpload component.
By the way, the mysterious GET request to 0.js disappeared once I fixed the typo. Whether a worker is auto-configured or not.
P. S.: I found the Express router debug output to be quite useful. Just add DEBUG=express:router to the candidates script in package.json. Additionally, you can define a separate script for convenience:
"scripts": {
  "candidates-debug": "cross-env APP_NAME=candidates DEBUG=express:router webpack-dev-server --inline --progress --config build/webpack.dev.conf.js",
}

Parsing from https://github.com/DevvJobs/candidates-web/pull/34 (thanks @lilsweetcaligula) is now enabled in development version. Right now it extracts all the text from PDF.
We have briefly discussed internally how we should proceed - we think it's best to do so with skills and that we should have an extra step before submitting results, so it's easy to see what exactly skills will be created, delete what you don't want to be sent, fill in any missing information, fix anything that's wrong and so on.
Our suggestion would be to do it in these steps:

A. Add extraction of skills from the PDF text, they can be put into state. Display them on page just as static text, for debug purposes and so other community members can jump in, test it out and help.
B. Add code that will try to find those skills by making API queries, result can be put to state. Display found skills as well, for debug purposes.
C. Add ability to fill in missing data for each skill - for example, while it is possible to detect years of experience in particular skill, we think it's better to leave it for later, so for now we can ask to fill them out manually.
D. Add code to send the result - found skills with all the required data - to server.
E. Improve from there

Feedback and suggestions are welcome.

Created https://github.com/DevvJobs/candidates-web/issues/37 for step A of the plan.


Support of other DocTypes and namespaces

Hello everyone,
In the framework of the MDoc implementation in wwWallet and the alignment with the EUDI ARF we noticed that in the library the org.iso.18013.5.1.mDL doc type is the only available option. Unfortunately this seems to be incompatible with the EUDI and ARF requirements which mandates a namespace and an attestation type of “eu.europa.ec.eudi.pid.<#increment>” for PIDs.
The library currently supports only the 'org.iso.18013.5.1.mDL' DocType, limiting its usability for developers who wish to implement solutions with custom DocTypes.
Adopting a more flexible approach to accommodate any DocType would be more than useful for anyone who is using this library as a core layer to implement solutions using the mDL specification ISO.18013-5.

Hi @kkmanos
Could you please provide us with some examples and links about this?
Thank you in advance.

This might be as simple as removing the DocType restriction and instead allow any string to be specified as a DocType. Currently it is restricted to the specific mDL string:
export type DocType = 'org.iso.18013.5.1.mDL';

So maybe it could become this?
export type DocType = 'org.iso.18013.5.1.mDL' | string;

It appears the addIssuerNameSpace function already allows for arbitrary custom namespaces so that probably wouldn't have to change:
addIssuerNameSpace(namespace: 'org.iso.18013.5.1' | string, values: Record<string, any>): Document;

Yeah, that's correct.
My original question was out of curiosity, as the ISO standard currently only accepts org.iso.18013.5.1.mDL:
From section 7.1 - mDL document type and namespace:

The document type for an mDL document shall be “org.iso.18013.5.1.mDL”.

I guess it comes down to whether you want this library to support only mDLs, or any arbitrary mdoc produced following the underlying standard.
Here's a link to the introduction of the PID for EUDI ARF. Then there's this second document with sections on the doc type and namespace proposed and notes specific to the mdoc encoding of it.

Thank you!

Hi everyone,
Thanks to the latest improvements in the library, we were able to successfully introduce the mDoc format in https://funke.wwwallet.org/ as part of the SPRIN-D Funke competition!
It will soon also be part of the core wwWallet software.

Nice!
Just FYI, this library was implemented in accordance with ISO 18013-7 (draft date: 2023-08-02).
However, there is a more recent draft dated 2024-02-13 that we need to review to ensure the library is updated accordingly (for example, the structure of the session transcript was changed).


[Bug] App Crashes while tracking latest Chapter on both MAL And Anilist

Device information

Tachiyomi version: 1.4.1(r325)
Android version: 10
Device: RMX1851

Steps to reproduce

Open tracking Function
Refresh the tracking page

Expected behavior
It supposed to do tracking with latest chapter that we read.
Actual behavior
But while doing tracking the app eventually crashed.
Other details
Error Name : Cancelled due to java.lang.NullPointerException

Try relogin MAL

Sounds like the Mal issue, you just need to relog


Update AllJoyn Link

AllJoyn has changed and the website was integrated with OCF
Fixes #37

Seems good to me, thank you Ahmed ! 👍


Command for Text above XP Bar

So I believe in 1.8 they added the ability for text over the XP Bar. I think it would be useful to add a command similar to the title command that allowed text to be displayed there.
Here's an example of how Jobs uses it:

You say that like we don't already have one :P
`- adjust  "action_bar:<&e>You gained a <&b>potato<&e>!"

Ok :P Thank you mcmonkey, asked in chat and couldn't find anything on it.

What chat? Denizen has an official chatroom -> http://mcmonkey.org/ircchat_denizen


Vary long start

Image tomcat:8.0.22-jre8
Vary long start.
log:
25-May-2015 16:06:20.304 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory /usr/loc
al/tomcat/webapps/ROOT
25-May-2015 16:18:46.687 INFO [localhost-startStop-1] org.apache.catalina.util.SessionIdGeneratorBase.createSecureRandom Creation of SecureRandom instanc
e for session ID generation using [SHA1PRNG] took [746,031] milliseconds.
25-May-2015 16:18:46.721 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory /usr
/local/tomcat/webapps/ROOT has finished in 746,418 ms
...

25-May-2015 16:18:47.307 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 747077 ms

It looks like you're running on a machine with low entropy.

It is a virtual machine. How can I increase entropy?

I've run into this problem before with boot2docker/VirtualBox and didn't
find a great solution.
I think I ended up sshing into the VM and running something like “du -x /"
repeatedly until the available entropy got high enough. I looked for a way
for the VM to share the host's entropy pool, but didn't find anything.

Here's a related issue in the VirtualBox issue tracker that has a couple other suggestions on how to get more entropy into the VM: https://www.virtualbox.org/ticket/11297

Thank you for the answers.
As I understand, low entropy is a problem for all VMs.

What about changing catalina.sh to use /dev/urandom via a java property.  -Djava.security.egd=file:/dev/./urandom

@dpwspoon That's a reasonable workaround for development purposes.

What about for production?  I'm not a cryptology expert but the following posts seem to make it seem like urandom is secure.  post1 and post2

I'm bumping into this tonight — startups that take 5-10 minutes. Has anyone ever figured out a real solution to this for production systems?

I would infer from the linked post and article that switching to /dev/urandom would be fine.

That is correct

FYI, for a while Docker has had a trivial way to make this switch that doesn't involve any changes to Tomcat or a system property — docker run --device /dev/urandom:/dev/random ...

Sounds like this is pretty well understood and solved now. :+1:
(Might be worth adding something to the image documentation, if it's still a recurring problem. :smile:)


add changelog for v0.4.0

Summary

add changelog for v0.4.0

Ticket Link
n/a
Release Note
NONE

Can we get #527 in first since this changes the grpc api?

yes sir! 😃

Looks like #527 landed.
can we update the changelog with the #527 enhancement?
thanks

Looks like #527 landed. can we update the changelog with the #527 enhancement?
thanks

added! :)

@k4leung4 @haydentherapper @dlorenc PTAL

@dlorenc ping to merge this, i dont have permissions to merge


build: enable arm64 build for linux and darwin

Pull request
What this PR does / why we need it
Add arm build to output publish binaries
Which issue(s) this PR fixes
Fixes #195
Describe testing done for PR
Tested on Raspberry Pi 4b, tanzu framework built in the RBP4 and the plugin built in a CI and installed in the RBP4

Additional information or special notes for your reviewer
Pending testing  ARM MacOS

arm64 is not officially supported by tanzu framework and darwin-arm64 does not build correctly, then this issue will be resolved when it is officially supported


awa-lwt rekey issue

Same issue as in #58.

this is not an issue, since in awa-lwt, Lwt.pick is used (and the timeout is cancelled when some other promise is fulfilled).

This is just a minor comment to explain why Lwt.nchoose_split is used (and not Lwt.pick) in awa-mirage: I had some issues when the timeout is triggered and there is still something to handle on the network side (which is overridden by the timeout) (e.g. https://github.com/mirage/awa-ssh/pull/35#issuecomment-956005503).


Fails to run app published to Microsoft Store

Describe the bug
Cannot open the app which is developed on WindowsAppSDK and published to Microsoft Store. Looks like the application never launches but the application crashes with the error below in the event log.

CoreCLR Version: <IP_ADDRESS>06
.NET Version: 6.0.2
Description: The process was terminated due to an unhandled exception.
Exception Info: System.DllNotFoundException: Unable to load DLL 'Microsoft.ui.xaml.dll' or one of its dependencies: The specified module could not be found. (0x8007007E)
...

But the app can run correctly on the PC with WindowsAppSDK dev environment. So sounds the Publish wizard does not include all necessary references/assemblies nor Windows does not install them automatically.
Steps to reproduce the bug

Create a project by "Blank App, Packaged (WinUI in Desktop)" template and code something. Ensure it can build and run correctly under Package mode.
Generate the .msix files by Visual Studio.
Generate the .msixbundle file by MakeAppx bundle and publish to Microsoft Store.
Install the app from Microsoft Store in another non-dev PC.
Fails to launch sadly. It says, "unable to load DLL 'Microsoft.ui.xaml.dll' or one of its dependencies" in event viewer.

The following is copied from my project file.
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>WinExe</OutputType>
    <TargetFramework>net6.0-windows10.0.22000.0</TargetFramework>
    <TargetPlatformMinVersion>10.0.22000.0</TargetPlatformMinVersion>
    <ApplicationManifest>app.manifest</ApplicationManifest>
    <Platforms>x86;x64;arm64</Platforms>
    <RuntimeIdentifiers>win10-x86;win10-x64;win10-arm64</RuntimeIdentifiers>
    <PublishProfile>win10-$(Platform).pubxml</PublishProfile>
    <UseWinUI>true</UseWinUI>
    <EnablePreviewMsixTooling>true</EnablePreviewMsixTooling>
    <PublishRepositoryUrl>true</PublishRepositoryUrl>
    <AppxAutoIncrementPackageRevision>False</AppxAutoIncrementPackageRevision>
    <GenerateTemporaryStoreCertificate>True</GenerateTemporaryStoreCertificate>
    <GenerateAppInstallerFile>False</GenerateAppInstallerFile>
    <AppxPackageSigningTimestampDigestAlgorithm>SHA256</AppxPackageSigningTimestampDigestAlgorithm>
    <AppxSymbolPackageEnabled>True</AppxSymbolPackageEnabled>
    <GenerateTestArtifacts>True</GenerateTestArtifacts>
    <AppxBundle>Always</AppxBundle>
    <AppxBundlePlatforms>x86|x64|arm64</AppxBundlePlatforms>
    <AppxPackageSigningEnabled>True</AppxPackageSigningEnabled>
    <!-- Other nodes -->
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.WindowsAppSDK" Version="1.0.0" />
    <PackageReference Include="Microsoft.Windows.SDK.BuildTools" Version="10.0.22000.197" />
    <Manifest Include="$(ApplicationManifest)" />
  </ItemGroup>
  <!-- Other nodes -->
</Project>

Expected behavior
The app launches well just like what I am debugging.
Screenshots
Following is from event viewer.

CoreCLR Version: <IP_ADDRESS>06
.NET Version: 6.0.2
Description: The process was terminated due to an unhandled exception.
Exception Info: System.DllNotFoundException: Unable to load DLL 'Microsoft.ui.xaml.dll' or one of its dependencies: The specified module could not be found. (0x8007007E)
...

NuGet package version
1.0.0
Packaging type
Packaged (MSIX)
Windows version
Windows 11 version 21H2 (22000)
IDE
Visual Studio 2022
Additional context
This is not about DEV environment but about the app has been published to Microsoft Store and installed in other PC without the DEV environment of WindowsAppSDK.

https://github.com/microsoft/WindowsAppSDK/issues/1762