Updated free-courses-en.md

Updated the Node.js section with a link to a free course on Udemy
What does this PR do?
Add resource(s)
For resources
Description
Updated the Node.js section with a link to a free course on Udemy
Why is this valuable (or not)?
This course will help you get started with Node.js development in under 2 hours
How do we know it's really free?
Labeled as free by Udemy
For book lists, is it a book? For course lists, is it a course? etc.
Course
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

@eshellman This PR was merged successfully however Hacktoberfest has now excluded this repository from participation as it did  not follow the rules of the event, Can you clarify?

Read #8671


[UI] Default Value for User's not Assigned to any Teams on User's Listing Page

Affected module
Does it impact the UI, backend or Ingestion Framework?
UI
Describe the bug
Let's add a default value when user is not assigned to any Team. Ex. None.

Version:

OpenMetadata version: 0.9.0

cc - @darth-coder00, @harshach

@ShaileshParmar11 can you look into this with add user thing?

Yes, Sure ill look in to it.

Can you assign this to me?


Contributor instructions per component

Minimum statement, but need more content

Notes for QA

Links to /components/UNIT-TESTS.md and /components/README.md wont work until this is merged into main.
This is largely an engineering tasks but we could use content review for the Contributor/developer documentation sections of the component readmes.

Good to go!


An instructional gap in generate-keys: Option 1

https://medalla.launchpad.ethereum.org/generate-keys
Option 1: Use binary executable file
This step directs a user to download a zip/tarball file from a github release page but does not instruct the user to extract the binary from the zip. Failure to extract the binary causes the next step to fail. Option 1 should include instructions for extracting the zip/tarball. This issue appears consistent across the directions for all three platforms.

@superphiz, while i haven't included specific instructions, I've tried to address that here.


Fix my mistake

refs #679
Do not have to run brew install mecab and brew install mecab-ipadic.

Great 👍


Deploying bicep files with warnings fails the deployment

Using the task with a bicep file as the template parameter when bicep has warning outputs results in the message:

Deployment process failed as some lines were written to stderr

This is correct, bicep is writing lines to stderr, but they are warnings only, not errors.
The result is that the bicep deploy doesn't occur. If I use az deployment sub create locally, the bicep deployment completes successfully.
Is there a way to continue deployment even though these warnings are written to stderr?
I've tried setting continue-on-error: true but it seems the error occurs after bicep to arm compilation and before the arm deployment so the result of this setting doesn't effect the ARM stage of the deployment
I've opened an issue at https://github.com/Azure/bicep/issues/2905 for the underlying issue as the warnings are incorrect compared to the ARM spec.

Hi @damienpontifex , at the moment if stderr is not empty we throw an error. Considering stderr should only be used for errors, changing the behaviour will require a lot of approvals and changes.
Let's wait for the bicep team to come up with a fix then we can see if such a feature is needed or not.

Thanks for the insight. I know they're also introducing listing and others, so warnings are probably a standard thing the bicep tool will continue to produce.
I'll raise it on the bicep repo as well with this info about warnings and stderr and it's relation to tasks such as this deployment and see where the discussion goes to get a good outcome

Agree that this is a bicep issue and they should not put warnings in stderr.
We could introduce an input called failOnStdErr which can be set to false in such cases.

Per this stackoverflow post, my understanding is the correct convention is to emit warnings to stderr:
https://stackoverflow.com/questions/1430956/should-i-output-warnings-to-stderr-or-stdout
Can the task instead read the error code of the command? If it is anything other than 0, the task should fail. cc @anthony-c-martin.

Hi @damienpontifex/ @alex-frankel , there certainly seems to differing opinions in the community!
But yes, irrespective how different people think, it certainly seems over aggressive to fail the action if just a warning is written to stderr. Problem is that we do not know what is warning and what is an error. And we have seen customer complaints where a tool failed and just outputted to stderr without setting a non zero exit code.
What we can do is to introduce an input called fail on standard error which if set to false will ignore any data in stderr. the default value, though, will remain true to ensure backward compatible behavior.
Does this sound okay to you?

And we have seen customer complaints where a tool failed and just outputted to stderr without setting a non zero exit code.

I'd argue this is a bug in the tool, which should have emitted a non-zero exit code. My understanding is this the exact purpose of an exit code, so I'd strongly recommend we rely standard exit code patterns as the default behavior, with an option to opt-in to fail a task if there is any output on stderr like you are describing.

What we can do is to introduce an input called fail on standard error which if set to false will ignore any data in stderr.

How will this task work with error codes in this case? Let's say I've opted in to this new property such that the task will not fail if there is output on stderr, will the task now respect error codes?

the default value, though, will remain true to ensure backward compatible behavior.

Instead of keeping the current default behavior, which I think leads to unexpected results, can we instead introduce a new default behavior in a new version of the task? i.e. azure/arm-deploy@2 It would be good to take advantage of semantic versioning for these types of things.
Thoughts?

How will this task work with error codes in this case? Let's say I've opted in to this new property such that the task will not fail if there is output on stderr, will the task now respect error codes?

Yes, it should always respect exit code.

Instead of keeping the current default behavior, which I think leads to unexpected results, can we instead introduce a new default behavior in a new version of the task? i.e. azure/arm-deploy@2 It would be good to take advantage of semantic versioning for these types of things.

Yes, this is a good candidate for v2. We will add this to backlog for v2.

@damienpontifex We are working on the fix for this issue here.

Thanks @t-dedah I've been following that PR as well and keen to try out the fix once merged.
Thanks for the open discussion on this and jumping straight in to figure something out

I have tried my deployment again using azure/arm-deploy@releases/v1 with the setting failOnStdErr: false and everything worked as expected.
Thank you for the open discussion and quick turnaround 🎉. I'd be happy to close (maybe you'll want to wait until v1 tag is updated to include this change)

@damienpontifex We have released the fix in v1, now you can test that too.

I switched it back to azure/arm-deploy@v1 and got the original error "deployment process failed as some lines were written to stderr"
Maybe caching of the task or something. I'll give it a day and queue it again to try again because I can see https://github.com/Azure/arm-deploy/tree/v1 has the commit merged in already.

@damienpontifex , let me check.

@damienpontifex Please try again, there was issue with build process but its resolved now.

@t-dedah tried again and it worked with @v1 🍾

@damienpontifex I am closing this issue now, feel free to reopen if you have any more queries.


posFromIndex and indexFromPos assume length of line separator is 1

However, if e.g. lineSeparator is set to "\r\n", which has length 2 in javascript, things don't fit anymore.
See https://github.com/codemirror/CodeMirror/blob/master/lib/codemirror.js#L7651

Good point. Attached patch should fix this.

Thanks! :)


Guard against nil *http.Response

Fixes #659

This change should not be merged as is. See my comment https://github.com/google/go-github/issues/659#issuecomment-311488297.
I don't think the issue exists on master.
However, we can make an improvement to newResponse documentation as follows:
 // newResponse creates a new Response for the provided http.Response.
+// r must not be nil.
 func newResponse(r *http.Response) *Response {

Then it's just a matter of making sure we never call newResponse(nil). Which, as far as I can tell, we do not in latest master.

SGTM.  Thank you, @shurcooL!

It seems to me that the nil check is a better solution than a code comment, as it protects against future mistakes.

The nil check and code comment serve different purposes. The nil check changes the behavior of the newResponse function. The code comments simply helps better describe the current behavior of the newResponse function.
I don't think we want to change the behavior of newResponse. Currently, it expects a non-nil *http.Response, and always returns a non-nil *github.Response. That's how it's designed, and that's how it's being used. If we change its behavior to return nil values sometimes, then we need to update other code, otherwise it would panic (e.g., this line would panic if newResponse returns nil). That means adding more if resp == nil { /* handle nil case */ } elsewhere. That's not helpful.
It's a private function for use within go-github. It's used only in 3 places in all of go-github, so it's very easy to ensure we don't make a mistake and give it a nil value.
Thanks for wanting to contribute. I made the suggestion of improving documentation of newResponse. If you want to update this PR to do that, we can accept it. If you don't want to do that, it's not a problem. Let us know how you want to proceed. Thanks.


How do I make a custom build on MacOS?

When I make a custom build on MacOS it makes a libllama.so file. However it seems Llamasharp is expecting a .dll file? I also see a libllama.dylib, and the runtimes folder has other dlls. How do we determine which runtime it uses?
The reason I'm trying to do this is the latest llama.cpp project has support for Metal and it runs much faster on my hardware. I'm trying to build an API around it, which I can do with the files from /runtime out of the box, but I'm not familiar enough with building C++ to include my custom build in there.

LLamaSharp uses P/Invoke to interop with native library. It's the dotnet runtime's responsibility to decide which file to use since the call is only something like DllImport("libllama").
Because I don't have a MAC device, it's the community effort that makes the MAC library file, which is libllama.dylib. Is it possible to generate it on your MAC book?

LLamaSharp uses P/Invoke to interop with native library. It's the dotnet runtime's responsibility to decide which file to use since the call is only something like DllImport("libllama").
Because I don't have a MAC device, it's the community effort that makes the MAC library file, which is libllama.dylib. Is it possible to generate it on your MAC book?

Yes, this is essentially what I came here to ask, is how do I do that? I don't see a way to build the .dylib file. When I build the project with libraries what I get is a .so file
So is all that is needed is just putting that .so file in there? Or do I also need to generate the .dylib file? If so, how do I build the dylib file?

When I make a custom build on MacOS it makes a libllama.so file. However it seems Llamasharp is expecting a .dll file? I also see a libllama.dylib, and the runtimes folder has other dlls. How do we determine which runtime it uses?
The reason I'm trying to do this is the latest llama.cpp project has support for Metal and it runs much faster on my hardware. I'm trying to build an API around it, which I can do with the files from /runtime out of the box, but I'm not familiar enough with building C++ to include my custom build in there.

I make a PR to the repository with metal support. You already have that version on my fork if you want to test it

When I make a custom build on MacOS it makes a libllama.so file. However it seems Llamasharp is expecting a .dll file? I also see a libllama.dylib, and the runtimes folder has other dlls. How do we determine which runtime it uses?
The reason I'm trying to do this is the latest llama.cpp project has support for Metal and it runs much faster on my hardware. I'm trying to build an API around it, which I can do with the files from /runtime out of the box, but I'm not familiar enough with building C++ to include my custom build in there.

I make a PR to the repository with metal support. You already have that version on my fork if you want to test it

That's super cool, I'll check it out. Thank you!
As someone not good with C++, how did you generate that .metal and .dylib file from the llama.cpp project? I'd like to understand how that process works in case I want to make custom builds

And LLAMA_METAL=Off if you want a only CPU version

.so is a static framework, you need to compile llama with -DBUILD_SHARED_LIBS=ON to build a dynamic version, which this binding expects.


Write the project report

This PR closes #34.
Hi @sacha-escudier and @int-ptr-ptr. Let's make this branch our drafting place for the report. I have already written the introduction and will add my sections soon. Let's all push our writings to this branch, and then we can merge the pull request and close #34 with it.

[x] Abstract
[x] Introduction
[x] Mesher
[x] Elements and Fields
[x] Plotter
[x] Software Quality and Maintenance
[ ] Conclusion and Outlook
[ ] General Revision

I think we should only use \texttt{} for FastFEM and codes only. It puts an emphasis on FastFEM. We don't need it for PyVista, etc.


Bug: dynamic thresholding changes secondary sampler name

Brief description: When saving an image in SD.Next, the dynamic thresholding extension is changing the name of the latent sampler in the image's recorded metadata by appending "_dynthresXXX" characters to the end. This is transposed back to latent sampler name field when feeding the image metadata to the Text2Image tab causing it to name a sampler that doesn't exist.
In looking at the code, it appears that when issue #58 was implemented, somehow the thresholding name for the latent sampler is being restored as the latent sampler's original name.
Linking to the bug explanation as originally posted on the SD.Next issues page:
https://github.com/vladmandic/automatic/issues/2124

I don't have a fix for this, but I ran a few tests on the code, specifically in dynamic_thresholding.py, lines 163 and 180.
Lines 179-181 correctly restore the names of each sampler, however by that point it appears that the metadata has already been recorded (or copied for later recording) with the altered latent sampler name? It's not clear to me why this same bug doesn't also affect the primary sampler name.


Add support for jit-grunt

Just In Time plugin loader for Grunt - https://www.npmjs.com/package/jit-grunt
Improves build time of Grunt tasks by loading plugins as and when they are needed rather than loading them all upfront before executing

@pra85 You must be on some PR-marathon, are you? :)

@chinchang  You can say that :grin:

@pra85 would be great if you could mention the time we are cutting off here in the PR description. It looks like premature optimization to me.

I measured the execution time for the tasks using time-grunt plugin. The findings are as follows -
For the grunt deploy task, the gain of using jit-grunt is minimal (around 5-10% faster)
Screenshot of running grunt deploy without jit-grunt

Screenshot of running grunt deploy with jit-grunt

Higher gains (In range of 30% faster build time) are within reach when running grunt default task with jit-grunt
Screenshot of running grunt default without jit-grunt

Screenshot of running grunt default with jit-grunt

The reason for this improvement is because jit-grunt loads in only thegrunt-contrib-sass plugin rather than following the default behavior of grunt, which loads in all the plugins mentioned in grunt.loadNpmTasks (aka grunt-contrib-cssmin and grunt-contrib-concat as well) even though they aren't required for completing the task.
The important thing to note being, introducing jit-grunt affects the build time in a positive manner (some tasks more than others, but always positive). I am aware that the profiling depends on the machine being used and the gains might be minimal when using a powerful machine (faster processor and SSD maybe)
Another plausible reason to use jit-grunt would be the reduced clutter in the Gruntfile in form of multiple grunt.loadNpmTasks statements being replaced by a single line. This might not be much (as hint.css only uses 4 grunt plugins currently) but none the less its a change to reduce redundancy.


Support optionally making the root serving directory writable.

Fixes #4.

I have updated the PR. What is your opinion?

FTP_CHOWN_ROOT has been added to the latest update. Closing this PR.


Installed but not really able to do anything

Hello,
sorry for being a complete beginner to programming. But I'm not able to really do anything. just tried the example provided:
"import fastf1 as ff1
from fastf1 import plotting
from matplotlib import pyplot as plt
plotting.setup_mpl()
ff1.Cache.enable_cache('path/to/folder/for/cache')  # optional but recommended
race = ff1.get_session(2020, 'Turkish Grand Prix', 'R')
laps = race.load_laps()
lec = laps.pick_driver('LEC')
ham = laps.pick_driver('HAM')"
So I'm getting an error code of:
"File "C:****\F1\F1FastTest.py", line 12, in  plotting.setup_mpl()
AttributeError: module 'fastf1.plotting' has no attribute 'setup_mpl'"
and if I comment it out it gets stuck at:
"File "C:**\anaconda3\envs\spyder\lib\site-packages\requests_cache\backends\storage\dbdict.py", line 74, in connection
con = sqlite.connect(self.filename)
OperationalError: unable to open database file"
I tried several Python versions but didn't seem to fix the issue. Is it because ther eis a live session going on?
Did you install using pip install fastf1? If yes, did you have  a previous version installed? Try to do a clean installation of the fastf1 package.
Also, the string 'path/to/folder/for/cache' needs to be replaced with a valid path to an existing folder. But that should raise a different error.

Thanks, sorry for late answer but that solved my issues!


_exists function

Shouldn't this be tokenId <= _minted instead of just tokenId < _minted ?
If I mint only 1 token, the function will return false for _exists(1).
Also breaks if I pass in tokenId of 0.

The tokenId starts with zero. It's why it is less.
What do you mean by "Also breaks if I pass in tokenId of 0."?
-------- Original Message --------
On Jun 30, 2022, 5:56 PM, pale-aura wrote:

image
Shouldn't this be tokenId <= _minted instead of just tokenId < _minted ?
If I mint only 1 token, the function will return false for _exists(1).
Also breaks if I pass in tokenId of 0.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Oh ok I see now. Thanks for clarifying.
What was the reason for starting token id at 0? I think that could be a deal breaker for a lot of projects because it creates a weird user experience.

It's a more natural indexing option in coding, and the original ERC721A also uses that.
I am thinking of adding support for changing starting index, but I haven't get a chance to do that. Let me know if you are interested in sending a PR.
-------- Original Message --------
On Jul 2, 2022, 2:13 PM, pale-aura wrote:

Oh ok I see now. Thanks for clarifying.
What was the reason for starting token id at 0? I think that could be a deal breaker for a lot of projects because it creates a weird user experience.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>


fix: set tags programatically

DD support has been rather unhelpful in mitigating our infrastructure->tags->datadog problem.
Just to move us forwards adding this "hack"
Overview
Adding tags to metrics depending on which application is running
Changes

Get the application mode
Store it in process dictionary
retrieve it, send it to DD

Testing

Coverage remained the same at ?% when pulling a9dbf457d9a60c97cbd13bbd2e76aba653b374ad on dd_tags into 962de5ee9b32cc827682934461d32231115d4aa3 on master.

This will allow us to filter by vmstats.* metrics and the application name. But it kinda forces us into using distinct cluster environments for each deployment.

@jbunce do you want a change?

Let's roll with this for the time being


add animated gif

Codecov Report

Merging #141 (21658d6) into main (3286f9d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #141   +/-   ##
=======================================
  Coverage   57.78%   57.78%
=======================================
  Files          51       51
  Lines        2916     2916
=======================================
  Hits         1685     1685
  Misses       1117     1117
  Partials      114      114

Flag
Coverage Δ

unittests
57.78% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3286f9d...21658d6. Read the comment docs.


Tests for CASSANDRA-8523

I keep getting lost while trying to read _test_insert_data_during_replace. I'm not sure what the issue is for me, but it may be helped by changing the names of the nodes to indicate their function, like replaced_node and new_node. I'll mess with it and push a commit for you to cherry-pick if I think it helps readability.

I'll mess with it and push a commit for you to cherry-pick if I think it helps readability.

Here's my branch with renamed node variables: https://github.com/riptano/cassandra-dtest/compare/master...mambocab:pull-1155_rename-nodes
I think it helps track the uses of nodes through the test, and I've had Russ give it a once-over, so I'm pretty confident it helps readability. If you agree, could you cherry-pick it onto this PR?

Looks great, mostly style nits from me. Let me know if you want me to take on any particular changes and I'll provide a commit to cherry-pick. Thanks for the tests!

Addressed comments as well as did a refactoring to improve reuse and efficiency of replace_address_test. The most relevant changes are:

Extracted common methods between tests: _setup, _do_replace, _stop_node_to_replace, _insert_data, _fetch_initial_data, _verify_replacement, _verify_data, _wait_for_replacement, _verify_tokens_migrated_successfully
Extracted cluster nodes to class variables: self.query_node, self.replaced_node and self.replaced_node
Made suite faster and more deterministic with:
Reduce number of keys inserted/queried with stress
Use byteman to interrupt streaming
Reduce cassandra.ring_delay_ms from default of 30s to 10s and cassandra.broadcast_interval_ms from default of 60s to 10s.
Removed Try to restart node 3 (should fail) check since it's not meaningful, and filled CASSANDRA-12485 for a proper check

I removed the @attr('resource-intensive') annotations so test are not ignore on CI:

2.1
2.2
3.0
trunk

@mambocab friendly ping in case you missed the notification, since both the ticket and this are quite large so rebases can get painful. I will try to be faster in the next follow-up. :)

Thanks for the ping! Reviewing now.

What are your thoughts on this failure? http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-trunk-8523-dtest/12/testReport/junit/replace_address_test/TestReplaceAddress/unsafe_replace_test/

The other builds look clean though. Let me know what you think of that error. Most of my other comments are nits.
Once you address my ignore_log_errors comment, could you kick off another set of runs on cassci?

Thanks for the follow-up. The unsafe_replace_test failure was due to waiting other's node notice in the refactor, which was not present in the original test, so I fixed this.
I updated branch with suggested nits and resubmitted tests:

2.1unpatched
2.2
3.0
trunk

@mambocab this is +1 after travis nit, yes?

Yep, +1. Thanks, Paulo!

Patch committed.

Paulo, can you rebase and merge? Thanks

Rebased, now merging. Thanks all!


Feat/delete implementation

This PR brings addresses #307 by implementing the (missing) DeleteData message in the Cognitarium smart contract, which provides the functionality to delete triples from the contract's state.

size-limit report 📦

Path
Size

target/wasm32-unknown-unknown/release/okp4_objectarium.wasm
427.77 KB (0%)

target/wasm32-unknown-unknown/release/okp4_law_stone.wasm
634.53 KB (0%)

target/wasm32-unknown-unknown/release/okp4_cognitarium.wasm
776.12 KB (+2.6% 🔺)

Status: implementation done. Missing tests.

Rebased to include #311 and #322 (among others).


Training blocking rule produces error

What happens?
When I train the blocking rule on the 'name' column, it gives the error: Column 'nan' does not exist
The blocking rules work for the other columns is there a reason why this is occurring, can't seem to find any documentation that would lead to this error?

To Reproduce
training_blocking_rule = "l.name = r.name"
training_session_fname_sname = spark_linker.estimate_parameters_using_expectation_maximisation(training_blocking_rule)
OS:
Windows
Splink version:
3.0.1
Have you tried this on the latest master branch?

[X] I agree

Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?

[X] I agree

To help, we'd need to see your full settings object please

Sure i've included my code as well as the last training block which leads to the error as shown above. Thanks for the help.
cc_spark_lower = company_spark.select('unique_id',
    *[lower(col(col_name)).name(col_name) for col_name in ['name','description','head_office_location','website_1',
                                                           'ownership']]
)

company_settings = {
    "link_type": "dedupe_only",
    "comparisons": [
        cl.jaro_winkler_at_thresholds("name", 0.7),
        cl.levenshtein_at_thresholds("description"),
        cl.exact_match("head_office_location", term_frequency_adjustments=True),
        cl.levenshtein_at_thresholds("website_1"),
        cl.exact_match("ownership")
    ],
    "retain_matching_columns": True,
    "retain_intermediate_calculation_columns": True,
}

spark_linker = SparkLinker(
    cc_spark_lower,
    company_settings
)

spark_linker.estimate_u_using_random_sampling(target_rows=1e6)

training_blocking_rule = "l.name = r.name"
training_session_name = spark_linker.estimate_parameters_using_expectation_maximisation(training_blocking_rule)

Does the traceback provide more detail?  Sometimes it shows the SQL statement.  The placement of the nan would help us debug.
I think it's fairly likely it's due to

You could try setting target_rows to a much higher value e.g. target_rows=1e8

Haven't looked at this in detail, but this can happen if your training_blocking_rule produces no matches - see #852. Looking at the output from the u-training step suggests that it may well be the case here.

In my case it would be more likely that the other columns excluding name would produce no matches, would this be the reason? Also i realised that the warning for name was exact match but i was using jaro-winkler. Have provided the traceback below for more details as well.

Thanks for the update


Improve usage of StringNames in GraphEdit

I noticed that GraphEdit emits signals with StringName argument, using a variable of String type. What's more, StringNames are being assigned to that variable, resulting in String <-> StringName conversions all over the place.
I changed connecting_from and connecting_target_to to StringName and fixed their usage to avoid String conversions. I also improved and simplified some code (loops etc.).

Thanks!


Less allocations

whats the point of https://github.com/chkr1011/MQTTnet/blob/develop/Source/MQTTnet/Client/Receiving/MqttApplicationMessageReceivedHandlerDelegate.cs
why not use events like before? if the intention was to not block the server if the eventhander is expensive / blocking we still need to add task.run otherwise it still blocks.
I would like to use events to distribute the packets to sessions as it seems the foreach over the concurrentdictionary allocates lists and arrays.
this bit:
https://github.com/chkr1011/MQTTnet/blob/420b35e37d9eea2cd0126ab74b7f5e7d36055c73/Source/MQTTnet/Server/MqttClientSessionsManager.cs#L207-L213
before:

Method
Mean
Error
StdDev
Gen 0
Gen 1
Gen 2
Allocated

Send_10000_Messages
12.19 ms
0.3646 ms
1.0225 ms
1718.7500
546.8750
31.2500
1.45 MB

after:

Method
Mean
Error
StdDev
Gen 0
Gen 1
Gen 2
Allocated

Send_10000_Messages
11.81 ms
0.3674 ms
1.083 ms
1500.0000
375.0000
31.2500
1.22 MB

Please don't just delete newly added classes like "MqttClientPublishResult". This class is still missing some properties like the reason string and the user properties from the original ACK packet. Removing that allows no access to the results from the ACK packet.
I was wondering if it is possible to reuse the "ReceivedMqttPacket" maybe because this is generated for every received message but in the end it is used only for deserialization. After that it can be maybe reused. But I am not sure. That are just thoughts.

Please don't just delete newly added classes like "MqttClientPublishResult"

oki il revert that. I just didnt know the intention of the class....

This approach tries to cover multiple things.

Allow using async methods and wait for the task to keep message ordering
Still choose between sync and async if required (wrapped in every delegate class)
Allow implementing some interfaces and set same class as handler for different things. Just a style thing than using += and -= etc.
This should not be used in server internals. Why do you think so?

The problem with events is proper attach and detach. Also the Enqueue... method was async for some time. NOW I agree that it may can be changed to an event.

with valuetask:

Method
Mean
Error
StdDev
Gen 0
Gen 1
Gen 2
Allocated

Send_10000_Messages
10.40 ms
0.2157 ms
0.6361 ms
765.6250
265.6250
-
547.9 KB

Looks promising but is ValueTask also supported in 4.5.2 and UWP?

yup just requires a reference to System.Threading.Tasks.Extensions

How long do you want to work on this? I want to release 3.0.0 soon so I would prefer 1) no critical and fundamental changes but 2) still all required API changes (if required) to avoid changed APIs next release. But I don't know how long you will need and whats on your list (if there is any list).

I put back MqttClientPublishResult so this is ready for review. I am just tinkering and the gain isnt great enough that this kind of changes block the release of 3.0.0

Grad to see your guys using  ValueTask
I will write a blog post about this library at about the time you release new version!

Is there any progress on this? I would like to close it. We can fur sure reopen it if there is any progress but I always think there is a "new" merge request but there is not 😄

ill close it for now


how can I create a task ?

Hi,
I check the example folder but i can't find any example related to a simple task creation.
I need to create a task with a description, title and reminder date
thank you very much

Sorry to disturb but if you're using Office365, maybe you can try out the CreateItem sample script from the Task samples.
Starting guide is explained here.
In any case, feel free to get back to me for any issue or needed help.

@mikaelcom Sorry but I forgot to mention that i need to create tasks on exchange 2013, is this possible without using another library? I already wrote some code for other function using phpEws and if is possible I want use only one library for Exchange

The examples are not meant to be all inclusive, they are a meant to provide a simple starting point. Have you tried creating a task? Between the examples, code documentation and the resources linked in the README, there should be plenty of information to point you in the right direction
I'm closing this as it doesn't conform to the issue template. If you are still having trouble, please open a new issue and complete the template in full, including what you've tried so far.

// Build the request,
$request = new CreateItemType();
$request->Items = new NonEmptyArrayOfAllItemsType();
$abc = array();
$abc['Subject'] = $caldata['subject'];
$abc['StartDate'] = $start->format('c');
$abc['DueDate'] = $end->format('c');
$abc['Body'] = $caldata['description'];
$request->Items->Task[] =$abc;
$response = $client->CreateItem($request);
The above thing i have implemented in application.Working Perfectly. Hope this will help you.

This worked for me:
    $client = new Client(self::EXCHANGE_SERVER, $email, $password, self::EXCHANGE_VERSION);

    $request = new CreateItemType();
    $request->Items = new NonEmptyArrayOfAllItemsType();
    $task            = new TaskType();
    $task->Subject   = $task_data['subject'];
    $task->StartDate = $task_data['start_at']->format('c');
    $task->DueDate   = $task_data['due_at']->format('c');

    $task->Body              = new BodyType();
    $task->Body->_           = $task_data['description'];
    $task->Body->BodyType    = new BodyTypeType();
    $task->Body->BodyType->_ = BodyTypeType::TEXT;
    $task->Importance        = ImportanceChoicesType::NORMAL;
    $task->Status            = TaskStatusType::IN_PROGRESS;
    $task->PercentComplete   = 50.;

    $request->Items->Task[]  = $task;

    $response = $client->CreateItem($request);


Document tagged templates

Support of tagged templates was added by rescript-lang/rescript-compiler#6250.
This PR is meant to document this new feature that will land with v11.1.

You still need to change the used version in test-examples. Unfortunately, testing uses only thebmost current version for now still.

thanks guys for the review, the tests pass now!


Is there a 3D version of this library?

I love the arrows!
I need to do this in 3D though.
Thanks.

Unfortunately, there is no direct support for 3d in Kivy. And this library is specifically for Kivy


nflows is no longer an optional dependency

See https://github.com/noegroup/bgflow/blob/ae1dc6a9b3bcd7f0382c98614a572b2ae1b3a540/bgflow/nn/flow/transformer/spline.py#L2
This should be imported in the class.
Tests need to be changed accordingly as well.

You are right, this is a bug.
It should be an optional dependency though.
I will fix it


support for catchcn ensemble run

Add CatchCN-specific export variables to EnsGridComp.
Required to support ensemble simulations with CatchCN in GEOSldas needed by @gmao-jkolassa.
Dependencies:

Depends on GCM GC PR https://github.com/GEOS-ESM/GEOSgcm_GridComp/pull/645, which in turn depends on MAPL PR https://github.com/GEOS-ESM/MAPL/pull/1683

Prior to merging, change components.yaml accordingly.

@gmao-jkolassa , if you want to test ensemble run, please use this fresh checkout of the branch .

This is just to confirm that an ensemble experiment using the current version of this branch works without any issues for both CatchCNCLM40 and CatchCNCLM45. Note that I only tested that it runs. Please let me know if you would like a full science-validation of this.

We have to change MAPL if we don't add 2 to the ens_id_with.  I think the id should include "_exxxx" even we drop of the backward compatibility.  @gmao-rreichle

@gmao-rreichle @gmao-jkolassa It should work now. But the nightly test would fail because we have hard coded HISTORY.rc for global assume and globules assume

We have to change MAPL if we don't add 2 to the ens_id_with. I think the id should include "_exxxx" even we drop of the backward compatibility. @gmao-rreichle

@weiyuan-jiang, I don't understand how MAPL comes into this.  I agree that we don't want to change MAPL, but maybe there's another way to distinguish between the number of digits and the total string length (ens_id_width) in LDAS.

These two assert should ease your concern if the users still use 4 for the width. Actually, the 6 is used in the lads_setup which should not have problem.
](https://github.com/GEOS-ESM/GEOSldas/blob/a045efd37511be89e3763a97cd3c07b7b3443473/src/Components/GEOSldas_GridComp/GEOS_LdasGridComp.F90#L179-L180)

The way we extract the template has to change in MAPL if we change is the width.
https://github.com/GEOS-ESM/MAPL/blob/160a8d720f5357d07d419818db7f53d51d471f2b/generic/MAPL_Generic.F90#L1508-L1509

I ran two shorts tests with the latest version of this branch. It builds successfully and runs successfully for both CatchCN40 and CatchCN45.

When this branch is merged, the two files for nightly test should be changed too:
/discover/nobackup/mathomp4/LDAS_Restarts/NGHTLY_TST_TV4000/HISTORY_L4_SM.rc
/discover/nobackup/mathomp4/LDAS_Restarts/NGHTLY_TST_CS/assim/ldas179b8_C180/run/HISTORY.rc
replace VEGDYN0000 with VEGDYN_e0000
@mathomp4 , We will let you know when we merge

@weiyuan-jiang, @gmao-jkolassa, I applied a hopefully final set of minimal edits https://github.com/GEOS-ESM/GEOSldas/pull/584/commits/f1bd407041126d84aadd2ccffc29069aeffc2a86
I don't think we need to retest the new functionality.
@weiyuan-jiang, did you run the LDAS Nightly tests with the above-mentioned edits to HISTORY.rc? If we are sure the GEOSldas PR is 0-diff for GEOSldas, we can ask @biljanaorescanin to test the matching GCM GC PR https://github.com/GEOS-ESM/GEOSgcm_GridComp/pull/645
and then ask Scott to merge the matching GCM GC PR as soon as he can.


[AST 6.0] Div to CDDT

Chain strat but without the RNG on the RNG job

I want to say this is done in DivinationDowntime already?
I'm unsure if there is a difference
if so, lemme know and I'll update it

I consolidated this one with of cooldowns


Filter connector credentials

The connection parameters of a database connector may include credentials to access the external resource.
This credentials could potentially leak into some logs:

[x] 1.1 INSERT statements in the Rails log (from main app)
[x] 1.2 request parameters in the Rails log (from main app)
[x] 2.1 FDW SQL statements in the Rails log (from resque workers)
[x] 2.2 Explicit logging to Rails log (from resque workers)
[x] 2.3 UPDATE statements in the Rails log (from resque workers)
[x] 3. PostgreSQL logs
[x] 4. Notification emails

Note that 3. is avoided by the logging configuration in PostgreSQL.

 Whay do you think?

Thanks @juanignaciosl !
I think adding a test to detect when the monkey-patching becomes ineffective is important. I'll give it a try; having some unit-test for that shouldn't be as tricky as the acceptance for this is.

I added something worth checking before going any further with monkey patching.
Cheers!

@rafatower @juanignaciosl I've removed the monkey-patching and set the log-level to :info instead. Can you review this latter changes (last 3 commits)

@rafatower I think this is now ready for acceptance


Transform REST Endpoint to an Azure Function

The more i look into the project, the more i ask myself as the main feature is receiving a Post payload :

should it be transformed in an Azure Function ?

It's a good suggestion but I don't have any plans to convert it in the near future. But I will keep this as an open suggestion.

Related to the azure function question, can this currently be run in a full on-premise situation (Azure DevOps server with on prem webservice)?

if you can run a Docker container, or even better, have a Kubernetes with KEDA installed, then you will be able to run it.

The Azure Function approach has already been done by https://github.com/tfsaggregator/aggregator-cli

+1 for the recommendation on converting this into an Azure function.

Here is a project that does use Azure functions to achieve the same results. https://github.com/CodeRunRepeat/AdoAutoStateTransitions

Here is a project that does use Azure functions to achieve the same results. https://github.com/CodeRunRepeat/AdoAutoStateTransitions

I ended up combining the efforts from this repo by @danhellem and couple of another github users and here is my first attempt at making this solution working with Server less Azure Functions.
azure-boards-automate-state-transition-serverless


Page type usage table shows a bulk actions checkbox in the header

Issue Summary
The page type usage table incorrectly shows a bulk actions checkbox in the header, making the table body incorrectly aligned with the header:

Steps to Reproduce

Spin up bakerydemo
Click on "Add child page" while browsing the "Welcome to the Wagtail Bakery" page
Click on the "Pages using ... page" link on the right hand side of the page type name (this is a bit hidden, I think we could improve the UI somehow)

See result

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?
The bulk actions checkbox shouldn't be present, so that the table body correctly aligns with the header.

Fixed in #10004


Parameter reference page not updating

https://pixhawk.org/firmware/parameters

Should this be moved to the dev guide? Auto generated and pushed to the gitbook repo, or is sync still problematic?

That would be preferable so everything is in one place. Either by automatic sync or by including (iframe) external content. I think @hamishwillee intended to look into that.

In my opinion yes it should be moved to the devguide. How is this built now? What are the existing sync issues?

There's a script (python ./Tools/px_process_params.py -s src --wiki) that generates docuwiki output in the form:
====== Parameter Reference ======
<note>**This list is auto-generated from the source code** and contains the most recent parameter documentation.</note>

==== Attitude EKF estimator ====

|< 100% 25% 45% 10% 10% 10% >|
^ Name ^ Description ^  Min ^  Max ^  Default ^
^ :::  ^ Comment ^^^^
| **EKF_ATT_V3_Q0** | Body angular rate process noise |   |   |  1e-4 |
| ::: |

 ||||
| **EKF_ATT_V3_Q1** | Body angular acceleration process noise |   |   |  0.08 |
| ::: |

 ||||
| **EKF_ATT_V3_Q2** | Acceleration process noise |   |   |  0.009 |
| ::: |

 ||||
| **EKF_ATT_V3_Q3** | Magnet field vector process noise |   |   |  0.005 |
| ::: |

 ||||
| **EKF_ATT_V4_R0** | Gyro measurement noise |   |   |  0.0008 |
| ::: |

 ||||
| **EKF_ATT_V4_R1** | Accel measurement noise |   |   |  10000.0 |
| ::: |

 ||||
| **EKF_ATT_V4_R2** | Mag measurement noise |   |   |  100.0 |
| ::: |

 ||||
| **ATT_J11** | Moment of inertia matrix diagonal entry (1, 1) |   |   |  0.0018 |
| ::: |

 ||||
| **ATT_J22** | Moment of inertia matrix diagonal entry (2, 2) |   |   |  0.0018 |
| ::: |

 ||||
| **ATT_J33** | Moment of inertia matrix diagonal entry (3, 3) |   |   |  0.0037 |
| ::: |

 ||||
| **ATT_J_EN** | Moment of inertia enabled in estimator |   |   |  0 |
| ::: |
If set to != 0 the moment of inertia will be used in the estimator
 ||||

In the recent past we had issues with syncing between the github dev-guide repo and the gitbook internal repo. We have completely reset the gitbook repo, and it seems to work now, we will have to see how stable it is.

Thanks!
@dagar @bkueng I've created an output format for markdown #6975 , which you can preview here (for a little while). The output format is actually HTML since markdown is quite limited in its table handling. I also moved comments inside the "name" row, because the old format was a bit ugly.

Note that my gitbook has a floating right in-page table of contents that allows easy navigation of the list of parameters (and any other headings). Any reason not to add the same plugin to devguide?
I also made each of the parameters an id="parameter_code", so you will be able to link to any parameter - e.g. https://hamishwillee.gitbooks.io/px4-user-guide/content/en/orphans/parameters.html#ATT_W_GYRO_BIAS

Is this OK? Any thoughts on improving?
To get this included in a build I'd make my build machine automatically run the  parameter extraction tools when triggered, update the devguide git tree and copy in the new file, merge the new file. Let gitbook handle the rebuild their end. That requires some playing with scripts on the build machine.
@dagar Any better way to handle this, and if not, can you sort that part out, since I don't have access ....

p.s. @bkueng  - where would be the best place in devguide TOC for the parameters to live? Perhaps near https://dev.px4.io/advanced-configurations.html

Nice! The table of contents on the old page was helpful, but we can live without it if it's not easy.
The param metadata has expanded quite a bit since the old wiki. In particular the values are now quite important, and the reason why many params no longer have a min/max. https://github.com/PX4/Firmware/blob/master/src/modules/mavlink/mavlink_params.c#L108
On a somewhat related note I believe @LorenzMeier also started doing something similar with airframe metadata. We should look into displaying that as well. https://github.com/PX4/Firmware/blob/master/ROMFS/px4fmu_common/init.d/13013_deltaquad#L6

The TOC on the page is easy and desirable (IMO). I've added request for its addition: https://github.com/PX4/Devguide/pull/109

The param metadata has expanded quite a bit since the old wiki. In particular the values are now quite important, and the reason why many params no longer have a min/max. https://github.com/PX4/Firmware/blob/master/src/modules/mavlink/mavlink_params.c#L108

Great. Is that just for my information, or is there something I need to "do"?

On a somewhat related note I believe @LorenzMeier also started doing something similar with airframe metadata. We should look into displaying that as well.

Lets wait on Lorenz for information on how far he got/intentions/what needs to happen.
Have you any thoughts regarding the last part - automating the build process?

Values are another nice to have if it looks easy to incorporate, but we can live without.
Do you have any access to the automated build for the hosted gitbook? One option is we could generate the output in the PX4 Firmware build and upload it to S3. Every time the gitbook updates it could download a copy. Another option is using jenkins (http://sitl01.dronetest.io/) to generate a commit.

Values are another nice to have if it looks easy to incorporate, but we can live without.

Not "super" easy. The big problem here is that within a group there are parameters that have values, parameters that have min/max, and parameters that are boolean (others)? We need to work out how to best present that and collect it in a way that we can sensibly render (we could just have columns for values as well, but that would be pretty messy).
This is definitely worth doing though! What are all the files in which parameters are defined?

Do you have any access to the automated build for the hosted gitbook? One option is we could generate the output in the PX4 Firmware build and upload it to S3. Every time the gitbook updates it could download a copy. Another option is using jenkins (http://sitl01.dronetest.io/) to generate a commit.

I thought this was just auto-generated by gitbook(.com) using a webhook from submissions to the github repo? Can't really comment without knowing how it is hosted and generated. That said, I'd be tempted to use jenkins to generate a commit in Devguide of the parameters when needed.

Thanks! One more thing we can do is display the unit of each parameter (if it has any). And if we find a good way, the parameter values & booleans (I don't think we have more types).

What are all the files in which parameters are defined?

They are pretty much distributed within the source tree.

Perhaps near https://dev.px4.io/advanced-configurations.html

Yes, makes sense.
For the airframes, there's already an xml generated and pushed to S3 based on latest master: http://px4-travis.s3.amazonaws.com/Firmware/master/airframes.xml
There's a script in Tools/px_process_airframes.py. Should be quite easy to turn this into HTML. The fancy version would be to have schematic pictures of the type and outputs (maybe overlay the text to generic pictures or generate the images with ImageMagick, ...). I talked to @LorenzMeier and it's what he has in mind as well.

That said, I'd be tempted to use jenkins to generate a commit in Devguide of the parameters when needed.

I agree, it should be completely automated. Using jenkins sounds like a good way to do it.

Hi Beat,

So is it correct that the Gitbook is just build from our Devguide github repo (triggered via a webhook?)

What are all the files in which parameters are defined?
They are pretty much distributed within the source tree.

I guess what I actually meant is "How can I find all the files that we need to process". Looking a bit deeper I think that we already scan for all the required information  in srcparser.py) so it is just a matter of reformatting/presenting.
Is that correct/your understanding?

For the airframes, there's already an xml generated and pushed to S3 based on latest master: http://px4-travis.s3.amazonaws.com/Firmware/master/airframes.xml
There's a script in Tools/px_process_airframes.py. Should be quite easy to turn this into HTML. The fancy version would be to have schematic pictures of the type and outputs (maybe overlay the text to generic pictures or generate the images with ImageMagick, ...). I talked to @LorenzMeier and it's what he has in mind as well.

OK, let us know.

That said, I'd be tempted to use jenkins to generate a commit in Devguide of the parameters when needed. I agree, it should be completely automated. Using jenkins sounds like a good way to do it.

@dagar Can you do the work needed?

So is it correct that the Gitbook is just build from our Devguide github repo (triggered via a webhook?)

No, gitbook has a separate git repo copy, and the webooks cause a sync of the repos - which then causes a rebuild & publication.

Is that correct/your understanding?

Ah ok. Yes, exactly. You can look at the generated xml (http://px4-travis.s3.amazonaws.com/Firmware/master/parameters.xml), which contains all the extracted information.

@dagar @bkueng After reviewing all the parameters I've come up with this new version. This adds

"type" information below the code
2 new columns for increment and units
Enum/values, decimal, bitmasks, reboot required. are displayed in description with "mini heading" IFF they exist.
Scope is displayed at the TOP of the table if it is the same for all parameters in the table. Otherwise it is displayed in the description in the same way as bitmasks etc.
Board is NOT displayed - there were no parameters that set this.

Questions:

What is decimal? Is it important/should it be displayed.
Is this OK/better, suggestions for improvement?

If you are OK with this then I will submit a PR with the changes. This is used by calling
python ./Tools/px_process_params.py -s src --markdown
@dagar - Is there anything you need to make the automatic build into gitbook happen, and can you ETA?

Hi - on airframe meta data: The goal is to generate a picture for every autopilot which marks the outputs you should be connecting - e.g. MAIN1 - left aileron, MAIN2 - right aileron, etc. We have that meta data already in for a number of airframes and it would allow to generate automatic wiring diagrams. These should also include airspeed and GPS, so that a user gets a complete picture.

@LorenzMeier That sounds awesome! Is anyone tasked with this tooling (generating the diagrams) and if not, what sort of generation tools were they planning on using?

Beat was looking into it but no, we do not have a person on this right now full-time.

OK, I've submitted #6990  which includes fixes as discussed above and with Beat.

@hamishwillee it looks like you can include external markdown?
If we do it that way we can avoid creating a new jenkins users with appropriate permissions and the potential gitbook sync issues we've been hitting.
WIP parameters.md generate and upload - https://github.com/PX4/Firmware/pull/6992

Hi @dagar
There is nothing to indicate gitbook can import from arbitrary locations (only locally or from github), though it might be able to. Another complication is that importing files from github (and presumably elsewhere is VERY slow). Doesn't matter much on the server, but it will slow a local build quite a lot ... which is painful for editors.
The best way from my perspective is that every time a new md file is built it gets submitted into the Devguide on github.
Thoughts?
H

Alright, let's give it a try.
@LorenzMeier can we use PX4BuiltBot for this purpose? If so we just need to get his credentials on jenkins and I can do the rest.

@hamishwillee do you want to manually commit the parameters.md from s3 (https://s3.amazonaws.com/px4-travis/Firmware/param_markdown/parameters.md) initially? I can work on getting jenkins (or something else) push access to the repository as a separate task.

@dagar How often do they change? ie If I submit manually do I need to put a note stating that these could be out of date? ETA on pushing from repo?

The version here on the old site (https://pixhawk.org/firmware/parameters) was late updated June 2016, and I still use it multiple times per week. Adding the date generated or based on PX4 version certainly wouldn't hurt.
The auto update needs a few things that are out of my control (github, gitbook, jenkins user with permissions, etc).

OK, then I will submit an update later today. Thank you!

Done - you can see it here: https://dev.px4.io/parameter_reference.html
Note the filename. Keep me posted on progress for auto-update please. Once that is done (and possibly before) we'll want to redirect from https://pixhawk.org/firmware/parameters

@dagar we've now got both DevGuide and User guide "places" for the parameter reference:
DevGuide: https://dev.px4.io/parameter_reference.html
User Guide: https://docs.px4.io/en/advanced_config/parameter_reference.html
So feel free to auto-update these spots whenever you like! The repos are both under PX4 org.

Moving the auto-update to next release since we already have the baseline functionality needed.

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 30 days. Feel free to reopen this issue if you deem it appropriate.
(This is an automated comment from GitMate.io.)


Switch from faux-ESM to real ESM exports

Reporting an issue
Thank you for taking an interest in rrule! Please include the following in
your report:

[x] Verify that you've looked through existing issues for duplicates before
creating a new one
[x] Code sample reproducing the issue. Be sure to include all input values you
are using such as the exact RRule string and dates.
[x] Expected output
[x] Actual output
[x] The version of rrule you are using 2.7.0
[x] Your operating system macOS Monterey 12.4
[ ] Your local timezone (run $ date from the command line
of the machine showing the bug)

The "module" field in package.json is non-official, and not a real ESM specification of npm: https://stackoverflow.com/a/42817320/1268612
Switching away from "module" to use the "exports" and "type": "module" fields in the package.json would allow for better compatibility with ESM, everywhere it is used.
You may even consider making it a pure ESM package, as mentioned here: https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c
Expected output (see "type" and "exports" fields):
$ cat node_modules/rrule/package.json
{
  "name": "rrule",
  "version": "2.7.0",
  ...
  "main": "dist/es5/rrule.js",
  "type": "module",
  "exports": "./dist/esm/src/index.js",
  "types": "dist/esm/src/index.d.ts",
  ...
}

Actual output (see the outdated faux-ESM "module" field):
$ cat node_modules/rrule/package.json
{
  "name": "rrule",
  "version": "2.7.0",
  ...
  "main": "dist/es5/rrule.js",
  "module": "dist/esm/src/index.js",
  "types": "dist/esm/src/index.d.ts",
  ...
}

Thanks for the suggestion. I don't think we're ready to abandon cjs users at this point, especially considering how new ESM is to Node itself, but I would like to improve the ESM support. What do you think about a solution like the one outlined here: https://redfin.engineering/node-modules-at-war-why-commonjs-and-es-modules-cant-get-along-9617135eeca1

Maybe it would work, I've heard some (rare) accounts of projects providing both ESM and CJS successfully. Any kind of improvement would be great! 👍

Please take a look at the latest (2.7.1) and let me know how it's working for you now

@davidgoli thanks for the new version!
rrule is still not published as ESM.
Importing and using rrule in the following file (import copied from the readme) leads to an error.
index.mjs
import { RRule } from 'rrule';

console.log(RRule);

The error is this below:
node index.mjs
file:///Users/k/p/ical-move-events/index.mjs:1
import { RRule } from 'rrule';
         ^^^^^
SyntaxError: Named export 'RRule' not found. The requested module 'rrule' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'rrule';
const { RRule } = pkg;

    at ModuleJob._instantiate (node:internal/modules/esm/module_job:124:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:179:5)
    at async Loader.import (node:internal/modules/esm/loader:178:24)
    at async Object.loadESM (node:internal/process/esm_loader:68:5)
    at async handleMainPromise (node:internal/modules/run_main:63:12)

Luckily there is a workaround and it is printed out in the error message, but a lot of users will probably not notice it or not understand:
import pkg from 'rrule';
const { RRule } = pkg;

console.log(RRule);

So probably this issue should be reopened, for seamless real ESM support.

@davidgoli do you think you could reopen this issue? I think it is not resolved yet.

@davidgoli I'll open a new issue for this and link to it here instead.

Same Issue here,
import pkg from 'rrule';
const { RRule } = pkg;
This workaround resolves the module error, but gives me a RRule is not a constructor error when trying to create a new RRule object.
Anyone ever found a solution ?

@JuicyZest this issue is closed, can you copy your comment above to the current issue over here?

#548


initialSlide being ignored on rerender.

I have a use where there are buttons in the slides that effect the state and triggers a rerender. I'm keeping track of the current slide and adding this to to the state and then using it for the initialSlide property, but it seems it always goes to the second slide every time. In the react debugger in chrome I can see the prop updates as it should, but it's not affecting the carousel. Any help would be appreciated!

Yes, I was just trying to figure out why my slide position didn't update. Exactly this case. It seems to be completely ignored.

InitialSlide is meant only for initial render. To change slide after 1st render, you have to use slickGoTo method
Check this example
https://github.com/akiran/react-slick/blob/master/examples/SlickGoTo.js

This doesn't make any sense in a redux context. Please don't close before the discussion is over. Feels kinda rude.

We are following the API of original slick
http://kenwheeler.github.io/slick/
Currently we have slickGoTo prop which can be used to change slide.
But because of some issue we had to deprecate it in favor of slickGoTo method.

Ok, so what you have to do is something like this:
componentDidUpdate (prevProps) {
	if (this.refs.slider) {
		this.refs.slider.slickGoTo(this.props.someIndex);
	}
}

Yes, you can do that if you are getting someIndex from redux store.
You also have to prevent re-render of Slider when someIndex change by implementing shouldComponentUpdate.  Otherwise you will lose animation effect during slide change

The thing is, I have a carousel where there are a set of options a user goes through. I start with slide one select something, then swipe to slide 2. When I click in slide two, it will render as slide 1, since my props have changed. Then if I use slickGoTo, it will animate from slide 1 to slide 2. The user will be confused as it switches from slide 2 to slide 1 without animation, then slides to slide 2 in an animated way? That would be very odd behavior. Is there some way to do slickGoTo without the animation?

So it looks like the slick library accepts a second argument of a boolean to animate or not..
    Slick.prototype.goTo = Slick.prototype.slickGoTo = function(slide, dontAnimate) {

        var _ = this;

        _.changeSlide({
            data: {
                message: 'index',
                index: parseInt(slide)
            }
        }, dontAnimate);

    };

But it doesn't seem to be accepted in react-slick...
slickGoTo: function slickGoTo(slide) {
    this.innerSlider.slickGoTo(slide);
},

@shendrick Nice catch.
Can you open a new issue with that feature request

set variableWidth=false, the state may be work. if you set variableWidth=true & initialSlide=someIndex, the slider don't know the width, so do not work. hope to help.


Macro: Monomers are stacked and difficult to read after importing a file

Steps to Reproduce

Switch to Macro mode
Open file peptide_Bzl.zip

Actual behavior
Monomers are stacked and difficult to read after opening file
Expected behavior
Monomers should be spaced out and easy to read after opening file
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser Chrome
Version 112.0.5615.138 (Official Build) (64-bit)

Ketcher version
Version 2.17.0-rc.1

Autotests added.

Tested. Fixed.


Latest version

According to RELEASE.MD, it seems latest version is 5.3.1.
According to NPM, it seems latest version is 3.5.3.
I was so far using version 4.1.5 and was thinking about migrating to the latest version, which I guess should be in the 5.x.y
Can you tell me what version to use and why versions seems to have been decremented at some point... or is that just a typo in package.json, where 3.5.3 should be 5.3.3?

Good morning Brice,
My most sincere apologies; I had a dyslexic moment when performing some releases over the weekend.
Should be all consistent at v5.3.4 now.
Again, sorry; but good to hear from you :-)
Kind regards,
David.

On 8 Jun 2015, at 08:07, Brice Morin<EMAIL_ADDRESS>wrote:
According to RELEASE.MD, it seems latest version is 5.3.1.
According to NPM, it seems latest version is 3.5.3.
I was so far using version 4.1.5 and was thinking about migrating to the latest version, which I guess should be in the 5.x.y
Can you tell me what version to use and why versions seems to have been decremented at some point... or is that just a typo in package.json, where 3.5.3 should be 5.3.3?
—
Reply to this email directly or view it on GitHub https://github.com/steelbreeze/state.js/issues/11.

No problem, every one can make mistakes ;-) Good to see you always fix my issues quickly :-)

5.3.x works perfectly, our ThingML compiler is now migrated to that version and all our tests passes. Keep up the good work!

That's great to hear - thanks for the update.


Make home page banner centered and favicon addition

The banner would look better if it covered the entire visible viewport on opening the home page. Also the banner would look better if centered. And favicon is missing. I would like to work on these issues.

@developer-diganta Assigning this issue to you. Happy Coding !


Display for Utterance Search has been modified in a way that is not great

The display for utterance search was much better before.
Currently, aside from any other aesthetic issues, the hierarchical relationships are obscured/misleading.

For example, "Grammatical Construction" appears to have the same relationship to negative, wh-question, and yes-no question that "rhetorical question" has to rhq.  But that's not correct.  Grammatical construction should be at a higher level.  Is it possible to add a bit of indentation to made these hierarchical relationships clear?  E.g.

Grammatical Construction
negative
wh question
yes-no question
+  rhetorical question
rhq

etc.
Also, the wrapping is happening in a way that wastes space.
There's plenty of room for, e.g.
   + topic/focus
         * sentence-initial adverb       *  focus      * topic
    + conditional/when
         * conditional    * when

Also "role shift" and "relative clause" appear to be grouped under "conditional/when", but
they are on the same level, i.e.
    + conditional/when
         * conditional    * when
    * role shift
    * relative clause

The same issues are relevant for the non-manual markings section, as well.

OK - I see what was causing the problem.  I had the screen zoomed out.  Seems the formatting is not preserved.  So this is much less serious than I thought!    It is fine when zoomed to actual size :-)

Fixed - Not an issue, at least when display size has not been modified in the browser.


Revert @Deprecated

Removed @Deprecated from constructor. Closes #852.

@georgeanderson Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@georgeanderson Thank you for signing the Contributor License Agreement!

Merged within 19d0b8188ad3b43af20156aeed86a8d526a66919.


Settings screen

Codecov Report
Attention: Patch coverage is 0% with 6 lines in your changes are missing coverage. Please review.

Project coverage is 0.00%. Comparing base (de3fcc5) to head (e0bcdbc).

Files
Patch %
Lines

...ys/showcase/presentation/CreateNavigationRoutes.kt
0.00%
4 Missing :warning:

.../jamiecruwys/showcase/presentation/MainActivity.kt
0.00%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@          Coverage Diff          @@
##            main    #124   +/-   ##
=====================================
  Coverage   0.00%   0.00%
=====================================
  Files          6       6
  Lines         72      72
  Branches      13      13
=====================================
  Misses        72      72

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Doc] Update README.md to address upb issue

Fixes https://github.com/grpc/grpc/issues/34405

Forcefully merged as this is github-only


test: Always select nodes by label

The node name for nodes in e.g. GKE is not fixed as in Packet nodes. So selecting nodes based on their name, as done in GetCiliumPodOnNode doesn't work there. This commit renames GetCiliumPodOnNode to GetCiliumPodOnNodeWithLabels and ensures we always select nodes by label in tests.

test-me-please

This pull request is not touching any SIG-specific code, but only ci-structure's. So I think we're ready to merge without the last few team reviews.


Can you document how to customize colorschemes in puget.

There's not a ton to document here, but I've added a link in the README to the puget.color.ansi namespace, which shows all of the available color codes you can apply.

Thanks
On Thu, Sep 29, 2016, 10:12 AM Greg Look<EMAIL_ADDRESS>wrote:

There's not a ton to document here, but I've added a link in the README to
the puget.color.ansi namespace, which shows all of the available color
codes you can apply.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/greglook/puget/issues/34#issuecomment-250531000, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACTW1m_epWogZJViWpgEW1kqMZqtpCHQks5qu_GPgaJpZM4J_va7
.


is there has a short key support in the openrefine?

@zhouyao1994 Please ask your questions on the mailing list, Stack Exchange or Twitter. Do you mean keyboard shortcuts? It would help if your question was a bit more explicit.

@wetneb  oh thank you very much to remind me . i just find that there is no support for the keyboard shortcuts support~


USB-to-Ethernet Adapter Information

Overview
Advanced Settings is updated

Implementation details

Display USB-to-Ethernet Adapter information

Description
Manufacturer
Driver Version

Display a message if there is a firmware update for the adapter

Design
https://www.figma.com/file/bVtCogdwiXj3ndpk4AWXCx/Milestone-1%3A-Read-and-Execute?node-id=1297%3A88764

Acceptance criteria

[ ] Add a new section to Advanced Settings
[ ] Get information for U2E
[ ] Add a toast
[ ] Writing test


This is a bug bounty test.. dont panic. Please do not approve. npjlsp

This is a bug bounty test.. dont panic. Please do not approve. npjlsp

If you are the same person who's spammed us with two similar PRs recently PLEASE STOP. This repository is not a playground.
I am closing this, locking it, and reporting you to GitHub.


POST Support

Gobuster is the best directory bruteforcer around, IMHO. However, there are two features I would love to see. One is a dream, the other is something that I believe should be implemented.

POST Support
It would be really helpful for us to be able to supply a verb for the request. This would allow us to find lots of additional content only listed in POST requests. It would also be great to say "do both GET and POST"
Recursive option
I realize this goes against what gobuster stands for, but I think it would be a great feature for people with different needs.

I'd like to put a bounty of a $5 on the POST request feature (since someone already has a POST request) and a bounty of $15 on the recursive feature. Bounty will be paid when code is pushed to main branch
Thanks again for such a great product!
Justin

Hi Justin,
Thanks for the message. The specification of other verbs is something that's in the works to be honest. There's a more general case that we're keen to catch as well, so expect that to happen.
Recursion isn't as easy as it sounds for a number of reasons, and I am yet to put a post together about it to explain why. I might get on that today! From there at least we can all have a discussion about it.
As far as bounties go, I do appreciate the gesture, however we don't accept donations. If you're interested in supporting the project in any way, you can make use of our OpenCollective  project where we accept donations from the community and pass the funds on to charity.
Cheers again mate, I love the constructive discussion that people invest in this project. It's humbling and flattering to have good people invest their time. Watch this space, we do have a lot more coming!
OJ

Hi !
I'm wondering if this issue is still considered and if the possibility of choosing the VERB can be implemented ?
I definitely think this options should be interesting (not only POST but also arbitrary methods).
Thank you for this great tool !
Tiyeuse

@tiyeuse yeah I'm keen to get this support in too. It's definitely on the cards!

@tiyeuse if you use the v3.1-cleaned branch you can use already custom verbs and POST requests


Remove unneeded check

Codecov Report
Attention: 260 lines in your changes are missing coverage. Please review.

Comparison is base (e977081) 93.48% compared to head (f86cc89) 95.54%.
Report is 91 commits behind head on main.

Files
Patch %
Lines

integration/test_collection_openai.py
41.25%
84 Missing :warning:

weaviate/collections/batch/base.py
83.85%
46 Missing :warning:

integration/test_collection_rerank.py
32.69%
35 Missing :warning:

integration/test_batch_v4.py
95.08%
14 Missing :warning:

integration_v3/test_backup_v4.py
92.76%
11 Missing :warning:

mock_tests/test_collection.py
85.71%
10 Missing :warning:

weaviate/collections/aggregations/base.py
94.57%
9 Missing :warning:

weaviate/collections/batch/batch_wrapper.py
86.20%
8 Missing :warning:

integration/conftest.py
88.52%
7 Missing :warning:

integration/test_collection_aggregate.py
97.41%
7 Missing :warning:

... and 10 more

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #857      +/-   ##
==========================================
+ Coverage   93.48%   95.54%   +2.05%
==========================================
  Files          70      167      +97
  Lines        8625    17138    +8513
==========================================
+ Hits         8063    16374    +8311
- Misses        562      764     +202

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


JEI and SpongeForge cause Vanilla recipes and recipes for other mods using the vanilla crafting table to disappear.

Affected Product(s)
SpongeForge
Version
1.16.5-36.2.5-8.2.0
Operating System
Windows
Java Version
openj9 <IP_ADDRESS>5
Plugins/Mods
jei-1.16.5-<IP_ADDRESS>9.jar (mod)
spongeforge-1.16.5-36.2.5-8.2.0-universal.jar (mod)
serverlistplus-3.5.1 (plugin)

Describe the bug
When loading JEI and spongeforge in the minecraft version of 1.16.5, there is an error when checking the datapack list. Because of this error, when a client logons on to the server, they cannot see any crafting recipes in the crafting table or JEI gui. This is from the server point of view pack.mcmeta, unable to get pack info for it. Crafting is still possible; however, the recipe is invisible
Link to logs
https://paste.gg/p/anonymous/27db6a4d9a244780a82ae7d80d27f974

Also, an additional note is that in the mods folder, the spongeforge mod is written as: aaa_spongeforge-1.16.5-36.2.5-8.2.0-universal.jar as stated to do on spongeforge website for known mod incompatibilties.

Also, an additional note, I run a significantly larger modpack then the one posted here; however, I was having the disappearing recipes in the crafting table, I decided to test and took out all the others mods while testing datapacks and claim to this conclusion.

Hello,
I tested on my side but the recipes are visibles as shown in the screenshots.
I didn't find serverlistplus version 3.5.1, only 3.5.0.
I tested with the original spongeforge plugin name and with the added aaa_.
Also, it's not errors but warnings.
Did I do something wrong ?

Hello, so right off the bat, I noticed there quite a few difference, one being that you have sponge api and sponge installed as plugin and the fact you have a different version of serverlistplus which I just found on ore the sponge platform. Another thing is are you using the jvm arguments I am using to start the server and are you forcing it to use a certain version of java like I am so it  does not just pick a general version. I will try adding sponge api and sponge to see if that helps the problem.

These are the arguments used: java -Xms11G -Xmx11G  -XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:ParallelGCThreads=4 -XX:+UnlockExperimentalVMOptions -XX:+DisableExplicitGC -XX:G1NewSizePercent=30 -XX:G1MaxNewSizePercent=40 -XX:G1HeapRegionSize=8M -XX:G1ReservePercent=20 -XX:G1HeapWastePercent=5 -XX:G1MixedGCCountTarget=4 -XX:InitiatingHeapOccupancyPercent=15 -XX:G1MixedGCLiveThresholdPercent=90 -XX:G1RSetUpdatingPauseTimePercent=5 -XX:SurvivorRatio=32 -XX:+PerfDisableSharedMem -XX:MaxTenuringThreshold=1 -XX:MaxGCPauseMillis=50 -XX:+AlwaysPreTouch -XX:+UseStringDeduplication -Dfml.ignorePatchDiscrepancies=true -Dfml.ignoreInvalidMinecraftCertificates=true -XX:-OmitStackTraceInFastThrow -XX:+OptimizeStringConcat -XX:NewRatio=3 -jar forge-1.16.5-36.2.39.jar nogui
PAUSE

After more testing I found out that jei starting to work again with just spongeforge and jei, now i will start implenting all the other mods again to see if it is still problematic.

Alright, after a little more testing I found out that the mod that was breaking minecraft recipes with jei and spongeforge is the mod: tomes2.0.1 for minecraft version 1.16.5. It seems as the tomes mod is incompatible,


Stab at README.md for documenting search.

I got to thinking about the need to document, understand options for adopting campuses that came up at sprint review yesterday.
Would a README about search features help?

Changes Unknown when pulling 280b7a7f4a3334768951417a14a991d1b05a4bdc on apetro:search_docs into ** on UW-Madison-DoIT:master**.

Changes Unknown when pulling 843473d58966375f58e215ba25fa75d0f4086206 on apetro:search_docs into ** on UW-Madison-DoIT:master**.

:+1:


How to select a local JVM for the runClient task?

I'm trying to use a specific JDK on my PC to run the runClient task. The problem is that Gradle always selects the AZUL JDK, and even if I comment out the vendor.set(JvmVendorSpec.AZUL), the task still uses another JDK 8 from the Gradle cache. Even if I try to specify this through gradle.properties or run the task via terminal by passing the JVM location as an argument, the task keeps using the same JDK 8. It only changes when I modify vendor.set.

Does modifying property org.gradle.java.installations.paths to tell gradle where to look for toolchains work for you? Run gradle -q javaToolchains to check.

Run command above to see if your JDK available within Window Registry.
If not, check the path and create new key and make sure path it correctly.
This also happen to me cause Gradle doesn't respect IDEA java setting.

gradle -q javaToolchains

My mistake, I use JVMs with DCEVM in old projects, and these VMs are all inside folders named "dcevm." For some reason, the DCEVM 8 directory contained the Java 11 binary, so Gradle couldn't find the Java 8 that it actually needed inside that directory.


Add LICENSE

Adds MIT LICENSE to the project

Thanks, @m-abdelwahab!
Since we started working on this last year, should it be Copyright (c) 2022 – 2023 Neon Inc.?
And do we need to acknowledge node-postgres/Brian Carlson? The node-postgres LICENSE file makes me think we do, but I'm not 100% sure where we put the acknowledgement.

should it be Copyright (c) 2022 – 2023 Neon Inc.
Sure

do we need to acknowledge node-postgres
Not sure if this should be in the license.It's probably good enough to be in the README


Create LCM_0f_2_number.cpp

Star the repo this is mandatory and you can also follow me.

Done Sir. Please accept my PR.


Add support for GCC/MinGW compilers

Fixes compilation under GCC.
Fixes AVX2 detection for Clang

Tested under

Ubuntu 19.04 AMD64

GCC 8.3
Clang 8.0

Windows 10 AMD64

MSVC 16.3 Preview 1
MinGW 9.1

Test suite is OK for all cases: 476/476 (https://github.com/Mixaill/directxmathtest/tree/gcc-fixes)

Thanks for the reminder to update all the auxiliary stuff in the repo. You should merge the latest changes to your fork:
XDSP

@walbourn rebased and cleaned up

Sorry, wasn't quite done...
SHMath
One more coming shortly for the 'Extensions'

@walbourn rebased and cleaned up. For #ifdef __GNUC__ read previous comment.

Sorry, took longer than I expected. Extensions updated in this commit.

@walbourn rebased

@walbourn cleaned up and retested with:

MSVC 16.3, MinGW 9.1 and Clang 8.0 on Windows 10
GCC 9.1 and Clang 8.0 on Ubuntu 19.10

Hi, just found this PR. I'm trying to use DirectXMath on Linux / Mac, I'd be happy to test on Mac.

Same any progress on this?

Well, looks like currently we have several unsolved issues:

untested on MacOs
"sal.h" on non-Windows platforms.

Rebased and retested:

Ubuntu 20.04 amd64

GCC 9.2.1-30ubuntu2: 476/476
Clang 9.0.1-8ubuntu1: 476/476

I've add 90% of your changes including fixes to the ARM-NEON path to build with clang / GCC in this pull request.

@walbourn I think it would be useful to add a little instruction to README.me where to download the sal.h file.

Agreed. I mentioned it in the wiki, but I can add it to the readme as well.

Updated readme in this commit


VGNC parser update

Description
Update to the VGNC parser during the first stage of the xref sprint. See ENSCORESW-2886.
Updates were as agreed... no $_ variable handling, croak on error, linting in general...
Parser now using Text::CSV.
Use case
Describe the problem. Please provide an example representing the motivation behind the need for having these changes in place.
Benefits
If applicable, describe the advantages the changes will have.
Possible Drawbacks
If applicable, describe any possible undesirable consequence of the changes.
Testing
no unit tests.

Coverage remained the same at 81.127% when pulling 3f8a47ba8702ae9a126ed5373b925c914cf14330 on xref_VGNC into fb849f5a081df4e1d1eb5d5fbbba8de0eeb416e8 on feature/xref_sprint.

I think those 4 xrefs were simply added to VGNC between your two runs
They parse correctly using the unchanged parser but they are not in the file I downloaded just two days ago

thanks @magaliruffier, I can confirm that is correct.
Rerun both version, and results are consistent at 16124 xrefs, so an extra 19 from yesterday.
Good to know the sources are updated regularly!

I've updated based on the reviews, let me know if more changes are required.

Are you happy with the current state of this parser, @nerdstrike ?


further information in timeline

Tasks
It would be interesting to show information about:

watering layer
fertilization layer

in the timeline. To not overload the user with too much information, this should only be shown when the watering or fertilization layer is active whereas the plant information is not shown on those two layers.
On all the other layers only the plant information is shown.
@danielsteinkogler can you please give the information how to do that here, so that @hatchla can work on that later?
Use case
timeline

That means the timeline api needs some query parameter or we have different timeline APIs.

Thx for your input! Sounds like a standard job to introduce a query parameter or are there special complications?

@markus2330 the description is updated now.


[question] how to install containerd independently without dockerd ?

Hi, All,
When I do some work with containerd, I found that it is hard to install containerd independently. There is no detailed doc about containerd's independent installation.
Can anyone help to attach me some reference about this?
Thanks in advance.

Installation is as simple as make && make install.

Thanks a lot for your quick reply. @wenjianhn
Actually when I use branch master to make,  it works fine for me.
While I found that checkout the commit 2a5e70cbf65457815ee76b7e5dd2a01292d9eca8 which is used by docker-1.12.6. In the root directory of containerd, I execute make, it fails to show:
containerd ((HEAD detached at 2a5e70cb)) $ make
cd ctr && go build -ldflags "-X github.com/docker/containerd.GitCommit=2a5e70cbf65457815ee76b7e5dd2a01292d9eca8 " -o ../bin/ctr
container.go:21:2: no buildable Go source files in /Users/allensun/go/src/github.com/docker/containerd/specs
make: *** [client] Error 1

I know there is some code still located on github.com/docker/containerd not github.com/containerd/containerd. So I cloned the repo docker/containerd and checkout the commit id 2a5e70cbf65457815ee76b7e5dd2a01292d9eca8 as well.
While the error message confused me a lot. Could you give me guidance about how to build the older branch of containerd?
Thanks a lot.

@allencloud I guess you tried to build containerd on macOS?
You need to use Linux.

Yeah, you are exactly correct. OK, I will try Linux.
BTW, what is the problem with macOS? 😄 🍻

Simply because it is for Linux.
GOOS=linux cross-compilation may work on macOS, but does not seem officially supported.

@allencloud
You can build containerd 2a5e70c in docker/containerd.
~/code/go/src/github.com/docker/containerd$ make
cd ctr && go build -ldflags "-X github.com/docker/containerd.GitCommit=2a5e70cbf65457815ee76b7e5dd2a01292d9eca8 " -o ../bin/ctr
cd containerd && go build -ldflags "-X github.com/docker/containerd.GitCommit=2a5e70cbf65457815ee76b7e5dd2a01292d9eca8 "  -tags "" -o ../bin/containerd
cd containerd-shim && go build -tags "" -ldflags "-w -X github.com/docker/containerd.GitCommit=2a5e70cbf65457815ee76b7e5dd2a01292d9eca8 " -o ../bin/containerd-shim

Thanks a lot for the help, my friends.
Closing this.


setting sdk_resource as customized for runAqaTest

Fixes https://github.com/adoptium/aqa-tests/issues/2097
cc @llxia @sophia-guo @smlambert

Yes we are in a code freeze right now so this will not get merged for a bit.  @julian55455 you can still mark it as a Outreachy contribution despite the delay to merge it.

This PR is dependent PR of https://github.com/adoptium/aqa-tests/issues/2097, which will not fix https://github.com/adoptium/aqa-tests/issues/2097. Might be better to update the description to related instead of fix https://github.com/adoptium/aqa-tests/issues/2097

@julian55455 could you please update the description as suggested in https://github.com/ibmruntimes/ci-jenkins-pipelines/pull/108#issuecomment-1284285148? Thanks

Is there a reason why we aren't delivering this upstream to the main Adopt repo?

Adopt uses upstream as they use staged SDK on Jenkins. Semeru pipeline uses customized (SDK URL from artifactory). This is a special case for Semeru.

Got it, thanks.

@AdamBrousseau could you please review this PR? Thanks


Resolve conflicts from master branch.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.5 out of 6 committers have signed the CLA.:white_check_mark: tharindu-bandara:white_check_mark: madurangasiriwardena:white_check_mark: dewniMW:white_check_mark: vihanga-liyanage:white_check_mark: thanujalk:x: wso2-jenkins-botYou have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.3 out of 7 committers have signed the CLA.:white_check_mark: wso2-jenkins-bot:white_check_mark: dewniMW:white_check_mark: madurangasiriwardena:x: Tharindu Bandara:x: tharindu-b-hewage:x: vihanga-liyanage:x: thanujalkTharindu Bandara seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


通过Store获取后，无法卸载“干净”

i get ScreenToGif from Windows Store, then i remove it, but in Settings, there is some mistake??? why?

That's possibly an issue with Windows itself, not ScreenToGif.
That settings page displays all programs that once used the notification drawer (system tray).
I'm not sure if it ever cleans any missing apps from it.

That's possibly an issue with Windows itself, not ScreenToGif.
That settings page displays all programs that once used the notification drawer (system tray).
I'm not sure if it ever cleans any missing apps from it.

@NickeManarin
i have resolve this problem, as your said, that is not ScreenToGif's fault, but Win.
Howto:

open regedit
delete key IconStreams and PastIconsStream from HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\CurrentVersion\TrayNotify
restart explorer.exe from Taskmgr.exe

@NickeManarin
i have resolve this problem, as your said, that is not ScreenToGif's fault, but Win.
Howto:

open regedit
delete key IconStreams and PastIconsStream from HKEY_CLASSES_ROOT\Local Settings\Software\Microsoft\Windows\CurrentVersion\TrayNotify
restart explorer.exe from Taskmgr.exe


Created an Arch Linux PKGBUILD

Hi, I created a PKGBUILD for shazamio, you can find it on the Arch User Repository here: https://aur.archlinux.org/packages/python-shazamio

Hello, the package is failing to install;
-> No AUR package found for python-keyring<24.0  -> No AUR package found for python-cachecontrol=0.12.9  -> could not find all required packages: python-cachecontrol =0.12.9 could not find all required packages: python-keyring <24.0
The packagebuild/srcinfo needs to be updated...

@amotzwohgj updated, thanks, now it builds correctly again.


Operator page UI updates

Let's update the operator page according to Figma views.

Also, I think we should hide the text "Click undelegate below..." if all tokens have been already undelegated.


mkl needs preloading when using python interface

for some reason MKL shared libraries are not loaded with libshogun (even if they are linked) when using the shogun interface....

ldd output for libshogun.so
https://pastebin.com/v6MHVQxN
and the python interface _shogun.so
https://pastebin.com/QhZF5qh4
The error is "Intel MKL FATAL ERROR: Cannot load libmkl_avx2.so or libmkl_def.so."
The current workaround is something in the lines of
export LD_PRELOAD=/opt/conda/lib/libmkl_core.so:/opt/conda/lib/libmkl_sequential.so

this problem is actually due to a badly setup environment in that docker image.... but we cannot do anything about this, just advise users to fix their environments or play around with env variables

reopening this because:
https://mail.scipy.org/pipermail/numpy-discussion/2009-October/046020.html
but we can have couple of workarounds for this from shogun side... so lets be nice with our users

we are trying to use this if possible https://software.intel.com/en-us/articles/a-new-linking-model-single-dynamic-library-mkl_rt-since-intel-mkl-103


feat: upgrade DataFusion, Arrow, PyO3, ObjectStore

BREAKING CHANGE:

Removed access to MultipartId, cleanup_partial_writes. Uploads are now automatically cleaned up.

FragmentWriteProgress no longer has any multipart_id argument.

CommitHandler and ManifestWriter APIs now take a Lance ObjectStore rather than object_store::ObjectStore.

New features:

For S3 and Azure (these features were already implemented for GCS):

Max object size is now 2.5 GB, up from 50GB.
Retries are now performed for Connection reset network errors.
Reduced number of IOPS for writing small objects (<5MB)

Codecov Report
Attention: Patch coverage is 64.00000% with 153 lines in your changes missing coverage. Please review.

Project coverage is 80.24%. Comparing base (0195ed7) to head (8d7b61d).

Files
Patch %
Lines

rust/lance-io/src/object_writer.rs
67.93%
71 Missing and 13 partials :warning:

rust/lance/src/io/exec/planner.rs
20.83%
18 Missing and 1 partial :warning:

rust/lance-index/src/scalar/btree.rs
0.00%
10 Missing :warning:

rust/lance-index/src/scalar/expression.rs
0.00%
6 Missing :warning:

rust/lance-io/src/object_store.rs
72.22%
3 Missing and 2 partials :warning:

rust/lance-io/src/object_store/tracing.rs
81.81%
3 Missing and 1 partial :warning:

rust/lance-table/src/io/commit.rs
66.66%
0 Missing and 4 partials :warning:

rust/lance-core/src/utils/testing.rs
0.00%
2 Missing :warning:

rust/lance-index/src/scalar.rs
0.00%
2 Missing :warning:

rust/lance/src/dataset/fragment/write.rs
0.00%
0 Missing and 2 partials :warning:

... and 10 more

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2594      +/-   ##
==========================================
+ Coverage   79.93%   80.24%   +0.30%
==========================================
  Files         212      211       -1
  Lines       61643    61433     -210
  Branches    61643    61433     -210
==========================================
+ Hits        49276    49296      +20
+ Misses       9438     9185     -253
- Partials     2929     2952      +23

Flag
Coverage Δ

unittests
80.24% <64.00%> (+0.30%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update set-value

"dependencies": {
  "set-value": ">=4.0.1"
}

Security issue is caused by gulp 4.0.2 and can't be fixed until gulp is updated.

<EMAIL_ADDRESS>is using cache-based and union-value and they are using set-value:
<EMAIL_ADDRESS>requires<EMAIL_ADDRESS>via a transitive dependency on<EMAIL_ADDRESS><EMAIL_ADDRESS>requires<EMAIL_ADDRESS>via a transitive dependency on<EMAIL_ADDRESS>
Both projects already have issues and pull request addressing and fixing the security  vulnerability:

https://github.com/jonschlinkert/union-value/pull/12
https://github.com/jonschlinkert/cache-base/pull/25

Currently no issue in https://github.com/gulpjs/gulp/issues related to this vulnerability.

Small updates:

cache-base is fixed with PR https://github.com/jonschlinkert/cache-base/pull/23
union-value is still not fixed. PR is open, but no reply from author: https://github.com/jonschlinkert/union-value/pull/12


Flixpatrol Doc Changes

Description
Add in_the_last and in_the_last_<<key>> back to flixpatrol docs and remove not used flixpatrol builder options
Issues Fixed or Closed

Fixes #(issue)

Type of Change

[x ] Documentation change (non-code changes affecting only the wiki)

Checklist

[x ] My code was submitted to the nightly branch of the repository.

Closed as it pushed to master


Update scala3-library to 3.5.2

About this PR
📦 Updates org.scala-lang:scala3-library from 3.4.3 to 3.5.2
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (3.4.3).
You might want to review and update them manually.
build.sbt
project/build.sh
project/deploy.sh

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala3-library" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-lang", artifactId = "scala3-library" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:semver-spec, old-version-remains, commit-count:1

Superseded by #529.


kv cache breaks generation

If I turn the kv cache on, autoregressive generation produces junk.
Here's a diagnostic: replace autoregressive_wrapper.py with this one: autoregressive_wrapper.txt (rename to .py)
This is the diff:
Running this on a testcase, such as your enwiki8 example, the output is that the logits are indeed scrambled between kv cache on vs off.
When testing generation on a small dataset, like Karpathy's Tiny Shakespeare, we see that KV cache breaks the generation:
KV cache on:
BIANCA:
Pardon, like an unwioul.

one nobistasele me, for me.

Were'e tondove ture ture.see tove t, gureforec tat ittheeft,
Tatt, deeeFooond
't!'tcitcit!
We tufn ture-p ton tovit thon tathon tap,
A'e
't!
'e
'e tctc,
'eSattc, tc,
'e
'eeatvaS:
'e t!s tcap tLeee t,
'ee t,
De t!

CORIOLANUS:
Why, having I can say 'tis the people?

First Servant:
Ha! what comes he ha'?

MENENIUS:
Now, I'll not budge thee with abard; not too much.
I have a ta'en for these sequesters must as
contrary'd to Rome, not Marcius, Lord Romenture;
My backetked Pravent; and, but at noblemant
More than any shall fine be a rought ,
Give up the to take and victor's bone
Have grace meet by my brother's life.

AUTOLYCUS:
Wear willow have we'll stout the coronatorsy.

First Gentleman:
Whom, how

If you want, you can fix it, or you can also just wait and I'll figure out the cause and submit a PR in a week.
As an aside, I'm running some changes to the enwik8 example: LR schedule, removing gradient accumulation, increasing batch size, and turning on flash attention. This significantly improves the performance and is codesize-neutral. Would you welcome these changes?

@ad8e hey Kevin
thanks for reporting
i quickly checked on a test script and it seems to be fine
import torch

from x_transformers import (
    TransformerWrapper,
    Decoder,
    AutoregressiveWrapper
)

model = TransformerWrapper(
    num_tokens = 20000,
    max_seq_len = 1024,
    attn_layers = Decoder(
        dim = 8,
        depth = 1,
        heads = 4
    )
)

model = AutoregressiveWrapper(model)

prompts = torch.zeros((1, 1))

generated = model.generate(
    prompts,
    seq_len = 100,
    temperature = 0.,
    cache_kv = False
)

kv_cache_generated = model.generate(
    prompts,
    seq_len = 100,
    temperature = 0.,
    cache_kv = True
)

assert torch.allclose(generated, kv_generated)

could you modify the script so that it breaks?

@ad8e as for your following offer, it is ok, as the library is model architecture specific. what you mention is all training related

@ad8e yea, it generates just fine for me, unable to reproduce what you are seeing. can you possibly provide more details? reproducible script, hyperparameters, etc

@ad8e ah, got to the bottom of it Kevin
so it turns out the default (absolute positional embedding) is not kv cache friendly once you exceed the maximum sequence length (context window). however, it should still work when decoding from 1st token to max_seq_len
i added an assert to prevent this, but also defaulted it to rotary pos emb, which is the preferred positional embeddings these days, and kv cache friendly.
ok, back to the holidays; have a great new years Kevin

Thanks, this fixes the issue and is better than what I would have PR'd. Sorry that I dumped two bad testcases and then went to sleep.

@ad8e as for your following offer, it is ok

To clarify, do you mean it is ok to do it, or "it is ok" as in it is not necessary?

have a great new years Kevin

You too!

Thanks, this fixes the issue and is better than what I would have PR'd. Sorry that I dumped two bad testcases and then went to sleep.

@ad8e as for your following offer, it is ok

To clarify, do you mean it is ok to do it, or "it is ok" as in it is not necessary?

have a great new years Kevin

You too!

it isn't necessary


remove side bar and trending section

Is your feature request related to a problem? Please describe.
currently, the template for creating a post is rendering on base.html we want it to be separate.
Because trending and side bar is present in base.html use #101 header and footer

I want to work on this issue.. @harsh-9in

I want to work on it

@ManishShah120 Actually @Akshi149  discussed me already about this issue. Infact, It was her proposal.
So, @Akshi149 would work on this issure.
@ManishShah120 I am creating few issues soon.

@harsh-9in have a look

looks cool :+1:

Should I change the header and footer in base.html?
Currently this is separate post page

No no need to change there.
Is it working fine I mean all the features are working properly?

Yeah