tests: Mass SMP disablement on non-SMP-safe tests (part 1 of 3)

**_This is a workaround to the CI performance trouble #13688
It's impossible to change so many tests at once and have a CI run that completes in the 2 hour limit, so I'm splitting the modified tests out into three separate patches and submitting them to be merged before the main pull request.  With master as it stands right now, these changes (to set CONFIG_SMP=n) are noops as no platforms have that set by default._**
(Chunk 1 of 3 - this patch was split across pull requests to address
CI build time limitations)
Zephyr has always been a uniprocessor system, and its kernel tests are
rife with assumptions and outright dependence on single-CPU operation
(for example: "low priority threads will never run until this high
priority thread blocks" -- not true if there's another processor to
run it!)
About 1/3 of our tests fail right now on x86_64 when dual processor
operation is made default.  Most of those can probably be recovered on
a case-by-case basis with simple changes (and a few of them might
represent real bugs in SMP!), but for now let's make sure the full
test suite passes by turning the second CPU off.  There's still plenty
of SMP coverage in the remaining cases.
Signed-off-by: Andy Ross<EMAIL_ADDRESS>

Codecov Report

Merging #13704 into master will increase coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #13704      +/-   ##
==========================================
+ Coverage   52.24%    52.3%   +0.05%
==========================================
  Files         307      307
  Lines       45413    45418       +5
  Branches    10508    10513       +5
==========================================
+ Hits        23726    23755      +29
+ Misses      16898    16873      -25
- Partials     4789     4790       +1

Impacted Files
Coverage Δ

drivers/clock_control/nrf_power_clock.c
50% <0%> (-2.11%)
:arrow_down:

arch/posix/core/posix_core.c
90.9% <0%> (-1.02%)
:arrow_down:

boards/posix/nrf52_bsim/time_machine.c
52.45% <0%> (+4.91%)
:arrow_up:

boards/posix/nrf52_bsim/irq_handler.c
78.3% <0%> (+13.2%)
:arrow_up:

boards/posix/nrf52_bsim/argparse.c
46.98% <0%> (+15.66%)
:arrow_up:

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 29dac22...a708755. Read the comment docs.

Took at look at that seemingly reproducible m2gl025_miv failure.  That's a RISC-V board that uses the "renode" simulator, not qemu.  It's installed in CI, but not part of the SDK and I haven't had time to figure out how to build it yet.  The failure on this particular test seems to be pre-existing in our tree, it's nothing to do with this patch.
Filed in #13960.  Please merge anyway, basically :)


Change name of "Phi" actor

Hi @thooton,
I'm just quickly skimming over this project. I noticed that you call your actors Phi and Epsilon and they are told to have an argument where they take a strong position on one side (an idea which I quite like and also planned on implementing after reading "The Socratic Method").
Isn't the naming a little dangerous, considering that a prompt for one of the Phi models might be "You are Phi, an AI model that ...".
I would assume the model trained on this data would have a strong bias to produce the opinion that your Phi actor had.

You raise a valid concern. I prefer using neutral identifiers to avoid unintentional bias.

This is a good point, I hadn't thought of this. I've changed the names to "Aspen" and "River" in #8 in order to avoid this.
I would use neutral names like "Debater 1" and "Debater 2", but I fear that it would be too easy for the LLM to confuse them and forget which position each is supporting. Concrete names can be easily referenced.


moved the calls back

I moved the calls for lidHookOutside();   buildLightTubes(); buildButtons(); lidHookInside(); back to the original locations.  This fixed the button issue.
But it does break (well maybe not break but change) the inspectx/y functionality. But I do see that you had separate inspect options for the light tubes and buttons so having them as part of the inspect function wasn't there before.  If I get a chance I may look at how to get the inspectx/y working for everything but as you have the other options it's probably not necessary.
The inside/outside functions do not work still.  If I have a chance to look at that more later I will.
Will probably look at adding fillets to the button recess also.

@rosenhauer,
I restored a working v2.0.5 version of YAPPgenerator_v20.scad so the test and example programs work with that version (basically removed fillets from that version).
Also added test programs for v2.1
Now investigating how to add a v2.1 tag to this new version... -done that before but no idea how :-(
Hope this does not interfere with your (future) work.
Regards

First off thanks for creating this project.
I'm not wanting to take it over as it's your baby, but as I have my first
3D printer on order and already have 4 different project boxes to make I'm
running into limitations that I can help eliminate.
I've been going through the code more closely and found some
inconsistencies and things that I think would improve the code.
Unless you have an objection I'm working on the following:

Update the debug inspect code.
a. I've moved it in my test copy to the very end (after everything is
rendered) so one config will cut everything.
b. I changed it to be from the true origin and configurable front/back
left/right so you can even cut it outside the main body and through the
buttons.

I already added an option for cutting the cutouts to only the thickness
of the face it's on (unfortunately I don't think I had that all working in
the copy I uploaded last time). This is helpful if you have connectors/pcb
supports to avoid below.
[image: image.png]
a. I was thinking of changing these to have a depth parameter with 0
defaulting to the face thickness.
b. Deeper cuts can be used to create vents that wrap around the edges of
the box.
[image: image.png]
c. I also noticed that how you were calculating the cutouts is different
for different sides (like the right/left differ by more than just the shift
to the different plane so I was going to rewrite that into a single module
that you can specify the plane in.
d. I also noticed that you have the cutouts for the screw holes in
the cutoutsInXY so they are actually cut out multiple times (not a problem
in the final result but takes more time). I will separate those out also.

Some more options to have preview and render quality options so you can
get fast onscreen and higher quality final renderings.

Making a "master" config embedded in the generator that you can enable
with a keyword to make sure that every combination of options can be tested.
a. It will be a rather large box with an example of each feature:
Cutouts on each face
Base Mounts
Snap connectors
Light Tubes
Buttons
Connectors
b. Every option for each of the above. for example:
Shape (square, round, user defined)
each coordinate system
with and without rotation

I see that there are a few different coordinate options:
//-- pcb_standoffs  -- origin is pcb[0,0,0]
//-- base plane    -- origin is pcb[0,0,0]
//-- Lid plane    -- origin is pcb[0,0,0]
//-- cutoutsGrill    -- origin is pcb[0,0,0]
//-- front plane  -- origin is pcb[0,0,0]
//-- back plane  -- origin is pcb[0,0,0]
//-- left plane   -- origin is pcb[0,0,0]
//-- right plane   -- origin is pcb[0,0,0]
//-- connectors
//-- normal         : origen = box[0,0,0]
//-- yappConnWithPCB: origen = pcb[0,0,0]
//-- base mounts -- origen = box[x0,y0]
//-- snap Joins -- origen = box[x0,y0]
//-- origin of labels is box [0,0,0]
//-- lightTubes  -- origin is pcb[0,0,0]
//-- pushButtons  -- origin is pcb[0,0,0]
//-- origin of labels is box [0,0,0]

Several of my projects have multiple circuit boards so for many of the
options like cutouts I would prefer to use box coordinates.  So I was
thinking of adding an optional coordinate system to the ones that it makes
sense to.

You also have yappCenter options for most (but not all objects - for
example circular cutouts don't have yappCenter code/options) and it looks
like yappCenter isn't consistent in how it's implemented.  In some cases
it's done by adjusting the parameters for example in makeCutoutsInXZ and
other places it uses the "center = true" option for example in
cutoutsInXY.  The latter adjusts all three axis and the former is just
adjusting the axis that the position specifies. If I combine all of the
cutouts into a single method it will make them all implemented the same.

Unless you are opposed to any of these changes I'll work on them over the
next little bit.  My printer should be here at the end of the week. So I'm
trying to get my designs done before then so I have something useful
to test out the printer with.
Regards
Dave
On Tue, Nov 14, 2023 at 4:55 AM mrWheel @.***> wrote:

@rosenhauer https://github.com/rosenhauer,
I restored a working v2.0.5 version of YAPPgenerator_v20.scad so the test
and example programs work with that version (basically removed fillets from
that version).
Also added test programs for v2.1
Now investigating how to add a v2.1 tag to this new version... -done that
before but no idea how :-(
Hope this does not interfere with your (future) work.
Regards
—
Reply to this email directly, view it on GitHub
https://github.com/mrWheel/YAPP_Box/pull/25#issuecomment-1809982434, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AIBTUKBVA2OE6NYTOQQD3UTYENE33AVCNFSM6AAAAAA7JKBL4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBZHE4DENBTGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Dave

@rosenhauer,
Yes, it ís my “baby” but as I wrote before: I’m an incremental developer and after a view iterations of the code I’m losing sight of what I have coded already and sometimes I reinvent modules I already have.
So your findings after the code review are correct. There is some inconsistency in the API’s for the deferent array’s.
If you have the time please make the code better and more consistent!
The YAPPgenerator is used by a lot of people and they will all benefit from your work.
What printer have you bought?
Regards,
Willem

Sounds like a plan.  Making it better for everyone was my goal.  I'm a
full-time developer but enjoy helping out on projects like this on the
side.
I got a refurbished Ender 3 S1.  I think it will be good for my first one.
On Wed, Nov 15, 2023, 1:18 AM mrWheel @.***> wrote:

@rosenhauer https://github.com/rosenhauer,
Yes, it ís my “baby” but as I wrote before: I’m an incremental developer
and after a view iterations of the code I’m losing sight of what I have
coded already and sometimes I reinvent modules I already have.
So your findings after the code review are correct. There is some
inconsistency in the API’s for the deferent array’s.
If you have the time please make the code better and more consistent!
The YAPPgenerator is used by a lot of people and they will all benefit
from your work.
What printer have you bought?
Regards,
Willem
—
Reply to this email directly, view it on GitHub
https://github.com/mrWheel/YAPP_Box/pull/25#issuecomment-1811927514, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AIBTUKDGEDUUEKH3YBLCK6TYERUERAVCNFSM6AAAAAA7JKBL4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJRHEZDONJRGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


ssl support for LANCommander.Lancher.

Basically if we put lancommander behind a SSL proxy nginx reverse proxy with a certificate. can we have the client able to communicate with the server? or is it only supported directly using ports 1337 using http only?
would be good to have that extra option to run SSL if we could. also would be good to have the server able to run on a SSL port if we choose to do so as well. I know this may add some complexity to the project, but hopefully not too much our of reach.

this is what we see from the client app logs
2024-09-16 22:07:37.681 +10:00 [ERR] The SSL connection could not be established, see inner exception. System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.  ---> System.Security.Authentication.AuthenticationException: Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion'.  ---> System.ComponentModel.Win32Exception (0x80090326): The message received was unexpected or badly formatted.    --- End of inner exception stack trace ---    at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](Boolean receiveFirst, Byte[] reAuthenticationData, CancellationToken cancellationToken)    at System.Net.Http.ConnectHelper.EstablishSslConnectionAsync(SslClientAuthenticationOptions sslOptions, HttpRequestMessage request, Boolean async, Stream stream, CancellationToken cancellationToken)    --- End of inner exception stack trace ---    at RestSharp.ResponseThrowExtension.ThrowIfError(RestResponse response)    at RestSharp.RestClient.ExecuteAsync(RestRequest request, CancellationToken cancellationToken)    at RestSharp.RestClientExtensions.ExecuteAsync[T](IRestClient client, RestRequest request, CancellationToken cancellationToken)    at LANCommander.SDK.Client.AuthenticateAsync(String username, String password, Boolean ignoreVersion)    at LANCommander.Launcher.Services.ProfileService.Login(String serverAddress, String username, String password)    at LANCommander.Launcher.UI.Authenticate.Login.OnFinish(EditContext editContext) 2024-09-16 22:09:24.224 +10:00 [ERR] The SSL connection could not be established, see inner exception. System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.  ---> System.Security.Authentication.AuthenticationException: Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion'.  ---> System.ComponentModel.Win32Exception (0x80090326): The message received was unexpected or badly formatted.    --- End of inner exception stack trace ---    at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](Boolean receiveFirst, Byte[] reAuthenticationData, CancellationToken cancellationToken)    at System.Net.Http.ConnectHelper.EstablishSslConnectionAsync(SslClientAuthenticationOptions sslOptions, HttpRequestMessage request, Boolean async, Stream stream, CancellationToken cancellationToken)    --- End of inner exception stack trace ---    at RestSharp.ResponseThrowExtension.ThrowIfError(RestResponse response)    at RestSharp.RestClient.ExecuteAsync(RestRequest request, CancellationToken cancellationToken)    at RestSharp.RestClientExtensions.ExecuteAsync[T](IRestClient client, RestRequest request, CancellationToken cancellationToken)    at LANCommander.SDK.Client.AuthenticateAsync(String username, String password, Boolean ignoreVersion)    at LANCommander.Launcher.Services.ProfileService.Login(String serverAddress, String username, String password)    at LANCommander.Launcher.UI.Authenticate.Login.OnFinish(EditContext editContext)

could we be hitting this from a windows 10 computer as the launcher host
https://stackoverflow.com/questions/28286086/default-securityprotocol-in-net-4-5/28333370#28333370

SSL works fine, make sure your nginx proxy is configured to use TLS 1.3 and TLS 1.2:
https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/linux-nginx?view=aspnetcore-8.0&tabs=linux-ubuntu
To get the web UI to work as well the reverse proxy must support websockets.


OperatorHub image is using Docker v1 Schema

Hi Team,
The ArgoCD image on OperatorHub (quay.io/redhat-cop/argocd-operator@sha256:d661aba8a5bc7c8a69cd7d5da8193585118b93f3e7ef14a213e1fa9c2684b47c) is of manifest type v1 schema and not v2.
V1 is legacy and has been deprecated by Docker and this project should really be used v2.
https://docs.docker.com/registry/spec/deprecated-schema-v1/
This is also limiting the ability to perform disconnected installs of this Operator using the OpenShift provided manuals as the schemas are changes by Skopeo / Docker resulting in a SHA digest change and the image not being able to be located by the OLM.
See below for the manifest-inspect.
./manifest-tool inspect quay.io/redhat-cop/argocd-operator@sha256:d661aba8a5bc7c8a69cd7d5da8193585118b93f3e7ef14a213e1fa9c2684b47c
ERRO[0001] application/vnd.docker.distribution.manifest.v1+prettyjws not supported
ERRO[0001] Unknown descriptor type:

Ack. This is problematic. @jmckind could you re-build and re-push the specific image ?


feat: implement value only serialization and deserialization

Depending on the context the serialization of a Meta-Model-Element may change. IdShorts for instance won't be serialized in a SubmodelElementList but must be in a SubmodelElementCollection. The test-resources (json) never hold the idShort themselves. That is kinda confusing but not necessarily a problem. There are however errors in the test-json files that don't comply with the spec (p.163ff).

I have splitted the ValueOnlyMapper into a JsonValueOnlySerialiser and a JsonValueOnlyDeserialiser class.

Will be taken care of with https://github.com/eclipse-aas4j/aas4j/pull/160


feat: add issue-body default

closes https://github.com/stefanbuck/github-issue-parser/issues/46
🎉

Does this mean issue-body isn't required in the action setup anymore? If so, I think the README should be updated too.

Amazing! It's really awesome to see you all to care enough about this little project to spend your time improving it. Thank you  ❤

For some odd reason the release pipeline was using an older commit as a baseline and this resulted in another 3.0.0 release ergo the pipeline failed with tag 'v3.0.0' already exists. I created the release manual for now, but the same happended earlier before as well see https://github.com/stefanbuck/github-issue-parser/pull/43#issuecomment-1283287852 @gr2m do you have any idea what is causing this?

Given this is happening since https://github.com/stefanbuck/github-issue-parser/pull/39 it must be related to this change. Is there another way to address https://github.com/stefanbuck/github-issue-parser/issues/23?

I had a quick glance but don't know what the reason might be. I gotta go for today, but could you file an issue and assign it to me please? I'll have a look tomorrow

I had a quick glance but don't know what the reason might be. I gotta go for today, but could you file an issue and assign it to me please? I'll have a look tomorrow

I had this browser tab still open for some reason, so I created the issue 👌 ☝


Fix the issue that EndTime in FragmentInstanceContext is not set

Description

When the FragmentInstance is not complete, its endTime is not set. It will lead to NPE when parse it to long when fetching FragmentInstance status.
Fix an issue that the coordinator cannot cleanup QueryExecution if the QueryExecution throws exception when constructing, which will lead to client stuck.

Coverage decreased (-0.008%) to 54.182% when pulling 6db6e964133edacd34d30ff666b88d4302666da5 on xingtanzjr/fix_coordinator_cleanup into 6952eed0e6dd2a884ee6df43a46fca0982ebcea0 on master.

There is executionEndTime.compareAndSet(null, now); in updateStatsIfDone of FragmentInstanceContext, you can change it to executionEndTime.compareAndSet(-1, now);

fixed


wrong current_path under certain circumstances

Not sure why it sometimes happens and now always, but in a mounted directory i get something that looks like the variable name instead of the actualy pwd content.
No shortening option is enabled.

~current_path

actually it should look like this:

/mnt/usb0/tmp

It has to do with powerlevel9k.zsh-theme via https://github.com/bhilburn/powerlevel9k/blob/master/powerlevel9k.zsh-theme#L812
If i remove the -P everything seems to work as expected

@anthraxx - Thanks for filing this bug! And great debugging! Very interesting that removing the -P fixes it. Looking at the ZSH docs for print, that flag does:
-p

    Print the arguments to the input of the coprocess.

To be honest, I don't really see how that flag is relevant to what we are doing because there isn't really a coprocess, here.
@dritter - Can you think of any harm in removing that flag?

very gentle bump :smile_cat:

@anthraxx - Sorry, and thanks for the bump! I think we're good to proceed with just removing the flag. Are you up for submitting a PR for it? =)

pull request opened: #776

Closing this issue to continue the discussion in the PR itself, #776, which is bitrotting at the moment.


review client code

The code in mquictt_client/src/lib.rs is severely out of date compared to the assumptions made by the server side. This requires a thorough review of the client side code. This will also solve #7.

@abhikjain360 did you remove the broadcast branch? 😅


Method for enabling specific preview rules

My ruff configuration is structured as a deny list where I've enabled all rules and then disable the rules that I don't want.
In 0.0.289, this looked something like:
preview = true  # added in 0.0.289
select = [
    "ALL",
    # other specific preview codes
]
ignore = [
    "PREVIEW",  # added in 0.0.289
    # other selectors I don't want
]

With the removal of the "PREVIEW" selector in 0.0.290, it doesn't look like there's an easy way to disable all the preview checks that I don't want without either:

changing my config to be an allow list rather than a deny list, or
explicitly ignoring every preview check that I'm not selecting with it's fully qualified code.

I would love to have some mechanism to select specific preview rules without doing either of these.

Thanks for this -- we actually discussed this internally last week and have something proposed in https://github.com/astral-sh/ruff/pull/7390 that would enable this kind of workflow (although we haven't yet decided to merge it). I'll \cc @zanieb who is owning preview behavior and thinking about these kinds of configuration issues.
(Zanie is out next week so might be a few days before a reply.)

Ah we thought the PREVIEW selector was generally useless for ignores because if it's precedence but it was usable with ALL.
I'm happy with the approach in #7390 but wanted to wait for some user feedback regarding the current experience to ensure it resolves your needs. Please let us know if it'd work for you!

The approach in #7390 looks good to me.


xcode 8.3 - warnings

Compiling on Xcode 8.3 gives tons of warnings. Especially for the SQLCipher project. Is there a way to silence these warnings and put it into the SQLite.swift.podspec?

If you only want to silence these warnings you can add the option inhibit_warnings to your podfile.
pod 'SQLite.swift/standalone', :inhibit_warnings => true

But that's definitely not the solution, there is a reason for this warnings. So +1 for fixing them.

Many of the warnings seem to be just from "warning: '+=' is deprecated"

I see 3 issued from the SQLite.swift and 95 issues in the accompanied SQLCipher.
pod 'SQLite.swift/SQLCipher', '~> 0.11.2'

I'll have a look later. A new release is due anyway...

Fixed warnings and released as 0.11.3.


Doesn't work with Redis on Memorystore GCP

When trying to run on gcp:
rma -s <IP_ADDRESS>
Match *:   0%|                                                                                | 0/34 [00:00<?, ?it/s]
Traceback (most recent call last):
File "/usr/local/bin/rma", line 9, in
load_entry_point('rma==0.1.16', 'console_scripts', 'rma')()
File "/usr/local/lib/python3.5/dist-packages/rma-0.1.16-py3.5.egg/rma/cli/rma_cli.py", line 97, in main
File "/usr/local/lib/python3.5/dist-packages/rma-0.1.16-py3.5.egg/rma/application.py", line 127, in run
File "/usr/local/lib/python3.5/dist-packages/rma-0.1.16-py3.5.egg/rma/scanner.py", line 85, in scan
File "/usr/local/lib/python3.5/dist-packages/rma-0.1.16-py3.5.egg/rma/scanner.py", line 53, in batch_scan
File "/usr/local/lib/python3.5/dist-packages/rma-0.1.16-py3.5.egg/rma/scanner.py", line 61, in resolve_types
File "/usr/local/lib/python3.5/dist-packages/rma-0.1.16-py3.5.egg/rma/scanner.py", line 58, in resolve_types
File "/usr/local/lib/python3.5/dist-packages/redis/client.py", line 3498, in call
return client.evalsha(self.sha, len(keys), *args)
File "/usr/local/lib/python3.5/dist-packages/redis/client.py", line 2704, in evalsha
return self.execute_command('EVALSHA', sha, numkeys, *keys_and_args)
File "/usr/local/lib/python3.5/dist-packages/redis/client.py", line 755, in execute_command
return self.parse_response(connection, command_name, **options)
File "/usr/local/lib/python3.5/dist-packages/redis/client.py", line 768, in parse_response
response = connection.read_response()
File "/usr/local/lib/python3.5/dist-packages/redis/connection.py", line 638, in read_response
raise response
redis.exceptions.ResponseError: Error running script (call to f_b89215e5d8808de13e1c715aaedbb744ce4536e7): @user_script:5: @user_script: 5: Unknown Redis command called from Lua script
Any ideas ?

Same problem here.


Missing Local Chapters

Hi,
The following are marked as type=osm but should be type=osm-lc to mark them as Local Chapters

[x] Argentina
[x] Czechia
[x] Democratic Republic of Congo
[x] Japan
[x] Kosovo
[x] Oceania
[x] Poland
[x] Slovakia

Complete list of Local Chapters is here: https://wiki.osmfoundation.org/wiki/Local_Chapters

I had some time today, so I updated these and added the missing ones 👍

Ah thanks! 💖💖


fix: SSR hydration mismatch in Image component

Whoops, Thanks! Somehow I didn't run into this SSR hydration during testing.


Flutter Web gives Error: UnimplementedError with File f = new File('example.txt');

Bug report
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

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

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System information

OS: [e.g. macOS, Windows]
Browser (if applies) [e.g. chrome, safari]
Version of supabase-js: [e.g. 6.0.2]
Version of Node.js: [e.g. 10.10.0]

Additional context
Add any other context about the problem here.

Hi @ExzaSolutions, dart:io doesn't support flutter web. You need to use https://pub.dev/packages/universal_io instead.


Feature Request: Add 'tag' or 'comment' parameter.

Because these processes run for a prolonged period of time -- it would be nice to be able to include some sort of 'tag' or 'comment' parameter, so that the purpose of the heliocron process could be identified more easily via 'ps'.  The parameter/value doesn't need to actually do anything - but including one currently causes an error for an invalid parameter.

Sounds like a good idea - I'll look into it this weekend


feat(GroupTheory/Perm/Centralizer): compute the centralizer of a permutation

Let α : Type with Fintype α (and DecidableEq α).
The main goal of this file is to compute the cardinality of
conjugacy classes in Equiv.Perm α.
Every g : Equiv.Perm α has a cycleType α : Multiset ℕ.
By Equiv.Perm.isConj_iff_cycleType_eq,
two permutations are conjugate in Equiv.Perm α iff
their cycle types are equal.
To compute the cardinality of the conjugacy classes, we could use
a purely combinatorial approach and compute the number of permutations
with given cycle type but we resorted to a more algebraic approach.
A subsequent PR #17047 treats the case of the alternating group.

[ ] depends on: #9359

And please split this up

I have removed the main new part to another PR (#17522). The present PR consists of basic useful lemmas.

I don't understand what the large-import tag means, because it doesn't seem I have modified imports.

bors r+


Android: disable in-app purchases #48

Changes :

[android] disabled in-app purchases #48

Replaced by #159


Update to flow 0.2.0?

Flow got updated with some bug fixes: https://www.npmjs.com/package/flow-bin
Would be awesome to get tryflow.org reflecting those updates. We're using it a lot at Facebook and having it up to date would be great :)
Thanks!

Good to know that this service is useful.
Redeployed. Also, the cache was flushed (TODO: add cache invalidation depends on flow version).
Feel free to create any type of issues about how this service could be improved.


Migrate misc atests to new test framework

Codecov Report
Base: 97.08% // Head: 95.51% // Decreases project coverage by -1.57% :warning:

Coverage data is based on head (7fb3534) compared to base (3ebf782).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #718      +/-   ##
==========================================
- Coverage   97.08%   95.51%   -1.58%
==========================================
  Files          24       24
  Lines        3057     3057
==========================================
- Hits         2968     2920      -48
- Misses         89      137      +48

Impacted Files
Coverage Δ

robocop/exceptions.py
89.47% <0.00%> (-8.78%)
:arrow_down:

robocop/checkers/misc.py
93.93% <0.00%> (-5.20%)
:arrow_down:

robocop/checkers/errors.py
92.44% <0.00%> (-4.07%)
:arrow_down:

robocop/utils/misc.py
94.27% <0.00%> (-3.97%)
:arrow_down:

robocop/checkers/comments.py
96.62% <0.00%> (-3.38%)
:arrow_down:

robocop/checkers/documentation.py
93.54% <0.00%> (-3.23%)
:arrow_down:

robocop/checkers/__init__.py
96.38% <0.00%> (-2.41%)
:arrow_down:

robocop/checkers/lengths.py
96.33% <0.00%> (-2.10%)
:arrow_down:

robocop/utils/run_keywords.py
91.89% <0.00%> (-1.36%)
:arrow_down:

robocop/checkers/naming.py
96.42% <0.00%> (-0.90%)
:arrow_down:

... and 2 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


DO NOT MERGE - KAFKA-1194 PARTIAL bug fix

This is a partial fix to the retention mechanism on Windows.
It makes sure to close a segment file handles prior to deletion trial.
Why is it partial? As it cannot work together will the log compaction policy.
Should work with a similar to the following configuration:
log.segment.bytes=1048576
log.retention.bytes= 5485760
log.retention.minutes = 1
log.retention.check.interval.minutes = 1
log.cleanup.policy = delete
log.cleaner.enable = false
log.roll.ms = 10000 <= Can be specified but will not cause any failure without the above two lines of configuration (log.cleanup.policy, log.cleaner.enable)
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Tested and not working for delete topics.
zookeeper-server-start ...
kafka-server-start
kafka-topics --zookeeper localhost:2181 --topic test --create --partitions 2 --replication-factor 1
kafka-console-producer --broker-list localhost:9092 --topic test
> foo
> bar
kafka-topics  --zookeeper localhost:2181 --topic test --delete

Fails with
[2018-11-20 09:18:43,525] ERROR Error while renaming dir for test-2 in log dir C:\tmp\kafka-logs (kafka.server.LogDirFailureChannel)
java.nio.file.AccessDeniedException: C:\tmp\kafka-logs\test-2 -> C:\tmp\kafka-logs\test-2.f221682bcfbf429db2f6cafe7256ef9a-delete
        at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
        at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
        at sun.nio.fs.WindowsFileCopy.move(Unknown Source)
        at sun.nio.fs.WindowsFileSystemProvider.move(Unknown Source)
        at java.nio.file.Files.move(Unknown Source)
        at org.apache.kafka.common.utils.Utils.atomicMoveWithFallback(Utils.java:802)
        at kafka.log.Log.$anonfun$renameDir$2(Log.scala:730)
        at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:12)
        at kafka.log.Log.maybeHandleIOException(Log.scala:1944)
        at kafka.log.Log.renameDir(Log.scala:728)
        at kafka.log.LogManager.asyncDelete(LogManager.scala:857)
        at kafka.cluster.Partition.$anonfun$delete$1(Partition.scala:354)
        at kafka.utils.CoreUtils$.inLock(CoreUtils.scala:251)
        at kafka.utils.CoreUtils$.inWriteLock(CoreUtils.scala:259)
        at kafka.cluster.Partition.delete(Partition.scala:348)
        at kafka.server.ReplicaManager.stopReplica(ReplicaManager.scala:351)
        at kafka.server.ReplicaManager.$anonfun$stopReplicas$2(ReplicaManager.scala:381)
        at scala.collection.Iterator.foreach(Iterator.scala:937)
        at scala.collection.Iterator.foreach$(Iterator.scala:937)
        at scala.collection.AbstractIterator.foreach(Iterator.scala:1425)
        at scala.collection.IterableLike.foreach(IterableLike.scala:70)
        at scala.collection.IterableLike.foreach$(IterableLike.scala:69)
        at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
        at kafka.server.ReplicaManager.stopReplicas(ReplicaManager.scala:379)
        at kafka.server.KafkaApis.handleStopReplicaRequest(KafkaApis.scala:200)
        at kafka.server.KafkaApis.handle(KafkaApis.scala:111)
        at kafka.server.KafkaRequestHandler.run(KafkaRequestHandler.scala:69)
        at java.lang.Thread.run(Unknown Source)
        Suppressed: java.nio.file.AccessDeniedException: C:\tmp\kafka-logs\test-2 -> C:\tmp\kafka-logs\test-2.f221682bcfbf429db2f6cafe7256ef9a-delete
                at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
                at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
                at sun.nio.fs.WindowsFileCopy.move(Unknown Source)
                at sun.nio.fs.WindowsFileSystemProvider.move(Unknown Source)
                at java.nio.file.Files.move(Unknown Source)
                at org.apache.kafka.common.utils.Utils.atomicMoveWithFallback(Utils.java:799)
                ... 22 more

Please test on your end for this test case too, and I think this PR should address this error

Hi Stephane,
Thank you for testing.
I do think that topic deletion should work on windows as well, but do we really want to bind it with the log retention feature?
What I am trying to do here, is "attack" the lacking windows support in a "step by step" manner, according to features which are most requested by the community.
That been said, I will take a look at the directory renaming error as well (hopefully on Sunday), as I am traveling abroad shortly.

To me, anything that has to do with log files being moved, renamed and deleted should be addressed as part of this PR.

Thanks Stephane,
By binding the entire file handling (renaming, moving, deleting) as a single issue, we are preventing the community from having a better version.
I do agree that the topics you've mentioned should be addressed, but to be practical - I cannot estimate when I will have the time to solve all these issues.
Personally, I can only take it step by step.
I would advise looking at this PR as a file retention enabler.
It's the minimal non obtrusive change (I was able to come up with) required in order to make the mechanism work.
It seems (to me) that as these issues are being handled by people, based on free time and good will, it is worth considering the approach I've proposed.
But that's just me :-)


Inefficient code generation leads to very misleading results

Apologies for the horribly generic synopsis. Please adjust as the root cause becomes clear.
Whilst timing some getpid() calls I noticed some odd behaviour. Take the following script:
#  cat getpid-slow.bt
tracepoint:syscalls:sys_enter_getpid
{
        @[tid] = nsecs;
}

t:syscalls:sys_exit_getpid
/@[tid]/
{
        @average["getpid"] = avg(nsecs - @[tid]);
        @[tid] = 0;
}

interval:s:10
{
        print(@average);
        clear(@average);
}

On my system this produces:
@average[getpid]: 2695

@average[getpid]: 2716

@average[getpid]: 2763

@average[getpid]: 2334

@average[getpid]: 2656

However, if I manually hoist the time calculation out of the avg() into a local variable with:
# diff getpid-slow.bt getpid-fast.bt
--- getpid-slow.bt      2019-08-01 08:59:35.412161939 -0700
+++ getpid-fast.bt      2019-08-01 08:59:47.041174182 -0700
@@ -6,7 +6,8 @@
 t:syscalls:sys_exit_getpid
 /@[tid]/
 {
-        @average["getpid"] = avg(nsecs - @[tid]);
+        $time = nsecs - @[tid];
+        @average["getpid"] = avg($time);
         @[tid] = 0;
 }

then the runs look like this:
#  /tmp/bpftrace ./getpid-fast.bt
Attaching 3 probes...
@average[getpid]: 1858

@average[getpid]: 1825

@average[getpid]: 1580

@average[getpid]: 1487

@average[getpid]: 1559

It looks like this change means we execute in the BPF interpreter for a lot less time! If you dump out the byte code with -vv then we seem to generate a very odd and wasteful looking sequence of byte code that is executed before the call to bpf_ktime_get_ns() in the slow version and after it in the hoisted version. In the slow version bpf_ktime_get_ns() is at instruction 187 in its block but at instruction 14 in the hoisted version.

The code sequence I'm referring to above looks like this:
15: (73) *(u8 *)(r10 -9) = r7
16: (73) *(u8 *)(r10 -10) = r7
17: (73) *(u8 *)(r10 -11) = r7
18: (73) *(u8 *)(r10 -12) = r7
19: (73) *(u8 *)(r10 -13) = r7
20: (73) *(u8 *)(r10 -14) = r7
21: (73) *(u8 *)(r10 -15) = r7
22: (73) *(u8 *)(r10 -16) = r7
23: (73) *(u8 *)(r10 -17) = r7
24: (73) *(u8 *)(r10 -18) = r7
25: (73) *(u8 *)(r10 -19) = r7
26: (73) *(u8 *)(r10 -20) = r7
27: (73) *(u8 *)(r10 -21) = r7
28: (73) *(u8 *)(r10 -22) = r7
29: (73) *(u8 *)(r10 -23) = r7
30: (73) *(u8 *)(r10 -24) = r7
31: (73) *(u8 *)(r10 -25) = r7
32: (73) *(u8 *)(r10 -26) = r7
33: (73) *(u8 *)(r10 -27) = r7
34: (73) *(u8 *)(r10 -28) = r7
35: (73) *(u8 *)(r10 -29) = r7
36: (73) *(u8 *)(r10 -30) = r7
37: (73) *(u8 *)(r10 -31) = r7
38: (73) *(u8 *)(r10 -32) = r7
39: (73) *(u8 *)(r10 -33) = r7
40: (73) *(u8 *)(r10 -34) = r7
41: (73) *(u8 *)(r10 -35) = r7
42: (73) *(u8 *)(r10 -36) = r7
43: (73) *(u8 *)(r10 -37) = r7
44: (73) *(u8 *)(r10 -38) = r7
45: (73) *(u8 *)(r10 -39) = r7

That's a sample - there's about 80 or so instructions in that sequence.

This is due to:
diff --git a/src/ast/semantic_analyser.cpp b/src/ast/semantic_analyser.cpp
index bbb9816..f38bf66 100644
--- a/src/ast/semantic_analyser.cpp
+++ b/src/ast/semantic_analyser.cpp
@@ -62,7 +62,7 @@ void SemanticAnalyser::visit(String &string)
     err_ << "String is too long (over " << STRING_SIZE << " bytes): "
          << string.str << std::endl;
   }
  string.type = SizedType(Type::string, STRING_SIZE);
 }

$ sudo bpftrace -e 'BEGIN { @["abc"]=1 }'
551: hash  flags 0x0
	key 64B  value 8B

This is done to ensure all map keys have the same size so that @["abc"] and @["xxxxxxxxx"]` works, but as a side effect it will have to memset 64 bytes.
I think it should be doable to keep track of the required string size (the size of the longest string) and use that instead of a fixed 64 bytes. This should reduce the amount of instructions for the average program by quite a bit, e.g. comm which is used often is 16 bytes max.
Changing  the memset to work with 8 bytes instead of 1  might be possible to but might be a lot of work as all array types are [x * i8] atm.

This problem should be now mitigated by #2044.
Running on my machine, the above two variants produce roughly the same numbers.


NIFI-12269 Resolve Maven Build Warnings for Plugins

Summary
NIFI-12269 Resolves Maven build warnings for several plugin versions by setting the plugin version in the plugin management section of the root Maven configuration.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[X] Apache NiFi Jira issue created

Pull Request Tracking

[X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[X] Pull Request based on current revision of the main branch
[X] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[X] Build completed using mvn clean install -P contrib-check

[X] JDK 21

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Thanks @exceptionfactory I've been meaning to get to this! +1 will merge


Installing

If possible, can you please tell me what needs to be installed and in what order to set up everything necessary before running the software?

Just follow the installation of psdr-cuda: https://psdr-cuda.readthedocs.io/en/latest/core_compile.html


Residence support

Hi mcmonkey or Fortifier42  !
It's is possible to hook with https://www.spigotmc.org/resources/residence-1-7-10-up-to-1-10.11480/ plugin please ?
It's an amazing plugin (always in dev) to protect area like a worldguard.
I use it since 2 years and hope depenizen can add:

[x] on residence player enter residence
[x] location.is_residence
[x] residence.owner

Thanks you !
(PS: the developer is stilling available on spigot discussion page, not irl, not github)

Is in dev?

It... doesn't look like @Fortifier42 ever added this, yet 2 boxes have been checked?.. I guess I'll add them now

Think this was in my latest PR...


Fix for K3s hardened profile test failures.

Related: https://github.com/rancher/cis-operator/issues/169
This PR fixes  4.2.1, 4.2.2 and 4.2.3 test failures for k3s-cis-1.6-hardened, k3s-cis-1.20-hardened and k3s-cis-1.23-hardened profiles.

Can someone in K3s team also review this @cwayne18

Merging the PR

FYI post approving it.


ARROW-11723: [Rust][DataFusion] Change SQL parser to use PostgreSQL dialect

As suggested by @andygrove we should use the PostgreSQL dialect now (by default), now that we decided o be PostgreSQL-compatible.
Currently this makes the VarProvider fail (introduced here: https://github.com/apache/arrow/pull/8135), which depends on identifiers starting with @, and which is not supported in PostgreSQL. I am wondering if we should remove this feature or make it work in another way?

The Apache Arrow Rust community is moving the Rust implementation into its own dedicated github repositories arrow-rs and arrow-datafusion. It is likely we will not merge this PR into this repository
Please see the mailing-list thread for more details
We expect the process to take a few days and will follow up with a migration plan for the in-flight PRs.

https://github.com/apache/arrow/pull/10096 has removed the arrow implementation from this repository (it now resides in https://github.com/apache/arrow-rs and https://github.com/apache/arrow-datafusion) in the hopes of streamlining the development process
Please re-target this PR (let us know if you need help doing so) to one/both of the new repositories.
Thank you for understanding and helping to make arrow-rs and datafusion better


network: move socket apis from address to socket

Move all network stack/socket layer interactions from addresses to
sockets. First step towards consolidating all socket layer calls in one place.
Risk Level: High
Testing: unit tests
Docs Changes: n/a
Release Notes: n.a

@mattklein123 thanks for the quick review and really glad you found the patch useful!
I'll change back the names of the SocketInterface functions to the original ones. Is it okay then if we postpone the TODOs and the other optimizations (not abusing the fd and syscalls) to the next PRs?
In fact, once we're done with this, if it makes sense to you, I'd like to push another PR that hides all of the remaining socket syscalls behind Socket functions, e.g., set/getsockopts.

@florincoras yes I'm fine with any order of PRs you want to do. My general ask is to make them small if possible and if there is pure code movement involved please do that as a discrete PR. Thank you!

Split into multiple PRs


cs fixed

Coverage remained the same at 100.0% when pulling a8047ba4f33e94a52b25d067ec6b22042e660eff on digitronac:feature/fix-cs into 042fd38e50c74a54119922b9df902c8751299e0e on tasmaniski:master.


It would be useful it forecastlr could also take dynamic (type number) y_val argument

Currently we use it on percentage based data. So it is simple to specify (100%) or some other hard coded value.
However there are situations where current values and limits are both pieces of data provided in the time series (HAProxy session limits, File descriptor limits, etc). If they y_val argument could be of type Number and not just Scalar we could create this sort of instantiated dynamic forecasting without having to go back and send the data itself as a percentage when creating the alert.

This has been fixed


Remove output metadata options that do not apply

Checklist

[x] I'm reporting a feature request
[x] I've verified that I'm running youtube-dl version 2020.02.16
[x] I've searched the bugtracker for similar feature requests including closed ones

Description

This is the output argument I am using:
-o "Downloads\Videos\%(extractor)s - %(uploader)s-%(upload_date)s-%(playlist)s #%(playlist_index)s - %(title)s [%(id)s].%(ext)s"
I would like for youtube-dl to, instead of always using this and then later requiring me to remove all the NA-NA-NA from files without the tags, know if the downloaded video actually has the tags and do a if check.
For example: https://v.redd.it/ps7wzmoq02j41 outputs Reddit - Artem10397-20200225-NA #NA - Russian cyberpunk. [ps7wzmoq02j41].mp4.
My feature proposal would make youtube-dl automatically rename it to Reddit - Artem10397-20200225- Russian cyberpunk. [ps7wzmoq02j41].mp4

That's technically impossible to implement what you request in your example. The max that can be is inserting empty strings instead of NA.

That's technically impossible to implement what you request in your example. The max that can be is inserting empty strings instead of NA.

Are you saying that it's now possible to change to an empty string?
I agree with the @HASJ 's intention. It would be nice to change the NA statement with conditional or OR operation.


rds - should not return "DBClusterIdentifier" if the instance is not in a cluster

Creating an issue here in case you can't see the comment on the PR.
When describe_db_instances(), the API implementation should not return "DBClusterIdentifier" property in the JSON if the instance is not in a cluster.
Please see comments on https://github.com/spulec/moto/pull/5101

Thanks for raising this @kentnsw!


Exception handling syntax is not Ruby compliant

The Crystal rescue syntax is not Ruby compliant. With exception handling, Crystal failed to run Ruby code, and vice versa.
In Crystal, it looks like :
rescue e : TypeOfException

But in Ruby, we can see :
rescue TypeOfExcepion => e

I think it is weird to choose not to follow the Ruby syntax on this kind of detail. Would someone kindly put me in the picture ?
Seriously, this is not about the best syntax, I just complain about this unexpected incompatibility.

Crystal is not a Ruby implementation, there are many syntax differences
=> is used in Ruby for hash literal. In crystal we use : for type restrictions, so we think : is more consistent. We think => in exception syntax in Ruby is inconsistent.

I understand the compiled program problematics. Crystal cannot handle the dynamical properties of a Ruby VM. Moreover, Crystal typing syntax is needed and Ruby interpreters yell on parsing. However, it is thinkable to have compatible parsers in both world. Rubies could update their parser to ignore typing syntax (Python 3.5 seems to behave like this).
We don't have the option to write Ruby-Crystal friendly code today (this is the case for exceptions handling). I just notice that some maybe justified but avoidable things don't follow the way to make it possible.

I'll close this because it's starting to look like a duplicate of https://github.com/manastech/crystal/issues/593
We have no plans of changing Crystal's syntax to make it Ruby compatible.


Unwanted params

I have an 'id' path param, which is dot defined anywhere and I'd like it gone.
Also, all my requests have a 'token' header. I would like to remove it, since I am using a specific Authorization header.
Here is my route definition:
'DELETE /api/v1/projects/:project_id' : {
    controller: 'ProjectController',
    action: 'destroy',
    swagger: {
      summary: 'Delete',
      description: 'Delete a project and all its dependents',
      parameters: [
        {
          in: 'header',
          name: 'Authorization',
          required: true,
          type: 'string',
          description: 'Bearer {{token}}'
        },
        {
          in: 'path',
          name: 'project_id',
          required: true,
          type: 'integer',
          description: 'ID of the project to delete'
        }
      ],
    }
  }

The Swagger UI output:

see https://github.com/theoomoregbee/sails-hook-swagger-generator#configurations for ways to update generated specification before it outputs the .json


Fluentd is restarting when handling big file through fluent-bit forward input

FluentD 0.12
FluentBit 0.11
CentOS
FluentD Configuration
<source>
  @type  http
  @id    input1
  @label @mainstream
  format /^(?<customer>\w*);(?<year>(\d{4}))-(?<month>(\d{2}))-(?<day>(\d{2})) (?<hours>(\d{2})):(?<minutes>(\d{2})):(?<sec>(\d{2})),(?<nano>(\d{3}));(?<professional>.*);(?<citizen>\w*);(?<action>\w*);(?<activity>[\w ]*);(?<activity_id>[\w ]*);"(?<activity_desc>.*)";?(?<channel>\w*)$/
  port  24224
  @log_level trace
</source>

<source>
  type forward
  bind <IP_ADDRESS>
  port 12225
  @label @mainstream
</source>

<label @mainstream>

        <filter **>
          @type parser
          format /^(?<customer>\w*);(?<year>(\d{4}))-(?<month>(\d{2}))-(?<day>(\d{2})) (?<hours>(\d{2})):(?<minutes>(\d{2})):(?<sec>(\d{2})),(?<nano>(\d{3}));(?<professional>.*);(?<citizen>\w*);(?<action>\w*);(?<activity>[\w ]*);(?<activity_id>[\w ]*);"(?<activity_desc>.*)";?(?<channel>\w*)$/
          key_name log
          reserve_data true
          suppress_parse_error_log false
        </filter>

		<filter **>
          @type record_transformer
          <record>
            customer_key ${record["customer"]}-${record["year"]}-${record["month"]}
			@timestamp ${record["year"]}-${record["month"]}-${record["day"]}T${record["hours"]}:${record["minutes"]}:${record["sec"]}
          </record>
        </filter>
	<match **>
	  @type elasticsearch
	  logstash_format true

	  host "my host"
	  time_key @timestamp
	  time_key_exclude_timestamp false
	  port 9200
	  user something
	  password something_else
	  target_index_key customer_key
	  index_name fluentd
	  type_name fluentd

	  buffer_type file
	  buffer_path /opt/fluentd/buffer/fluentd.*.buffer

	</match>
</label>

Fluent-bit  configuration
[SERVICE]
    Flush     1
    Daemon    On
    Log_Level debug
    Log_File  /data/preprod/test/logviewer2/log-recovery.log
    HTTP_Monitor on
    HTTP_Port 2020

[INPUT]
    Name tail
    Path /data/preprod/test/logviewer2/failtest.txt

[OUTPUT]
    Name forward
    Host host/with/fluentD
    Port 12225

logs generated using java method
@Test
	public void testCostam() throws IOException {

		BufferedWriter bw = null;
		FileWriter fw = null;

		try {

			fw = new FileWriter("c:/klucze/failtest.txt");
			bw = new BufferedWriter(fw);
			for(int i = 0 ; i < 1000000; i++){
				String msg = "trinity;2017-04-15 00:00:00,180;AVS;;BULKREAD;Message;;\"\";fail_test"+i + "\n";
				bw.write(msg);
			}

			System.out.println("Done");

		} catch (IOException e) {

			e.printStackTrace();

		} finally {

			try {

				if (bw != null)
					bw.close();

				if (fw != null)
					fw.close();

			} catch (IOException ex) {

				ex.printStackTrace();

			}

		}
	}

I am trying to find out if log forwarding is reliable, as I have requirement that i can't loose any log while i send it from fluent-bit to fluentd which is storing them in elasticsearch. Everything works pretty well but, when i try to use in_tail plugin with fluentbit to transfer logs from single file (70mb, file generated by above function) i get errors, fluentD restarts itself few times, and in the process i am loosing around 50% of logs.
some logs frome fluent bit
[2017/05/04 10:17:36] [debug] [out_forward] request 2052648 bytes to flush [2017/05/04 10:17:36] [debug] [out_fw] 23868 entries tag='tail.0' tag_len=6 [2017/05/04 10:17:36] [error] [out_fw] error writing content body [2017/05/04 10:17:36] [error] [out_fw] error writing content body [2017/05/04 10:17:36] [debug] [retry] re-using retry for task_id=18 attemps=2 [2017/05/04 10:17:36] [debug] [sched] retry=0x1a87650 18 in 16 seconds [2017/05/04 10:17:36] [debug] [retry] re-using retry for task_id=26 attemps=2 [2017/05/04 10:17:36] [debug] [sched] retry=0x1aaefa0 26 in 19 seconds [2017/05/04 10:17:36] [error] [out_fw] error writing content body [2017/05/04 10:17:36] [debug] [retry] re-using retry for task_id=29 attemps=2 [2017/05/04 10:17:36] [debug] [sched] retry=0x1aaeef0 29 in 7 seconds [2017/05/04 10:17:36] [error] [out_fw] error writing content body [2017/05/04 10:17:36] [debug] [task] task_id=6 reached retry-attemps limit 2/1 [2017/05/04 10:17:36] [ warn] [engine] Task cannot be retried: task_id=6 thread_id=2 output=forward.0 [2017/05/04 10:17:36] [debug] [task] destroy task=0x1a97bc0 (task_id=6) [2017/05/04 10:17:36] [debug] [dyntag tail.0] 0x1a96600 destroy (tag=tail.0) [2017/05/04 10:17:36] [error] [out_fw] error writing content body [2017/05/04 10:17:36] [debug] [retry] re-using retry for task_id=8 attemps=2 [2017/05/04 10:17:36] [debug] [sched] retry=0x1a87ab0 8 in 3 seconds
and some logs from fluentD
2017-05-04 08:18:19 +0000 [info]: process finished code=9 2017-05-04 08:18:19 +0000 [error]: fluentd main process died unexpectedly. restarting. 2017-05-04 08:18:19 +0000 [info]: starting fluentd-0.12.35

Are you using Fluent Bit v0.11.4?

Yes, i am using FluentBit v0.11.4 ,  was trying with similar setup on fluentBit v.010, but fluentd had reset more frequently

Just to isolate the problem, what about if you add this option to your input section:
[INPUT]
    Name and
    Mem_Buf_Limit 10MB

Please try mem_buf_limit and let me know if that helps

Setting Mem_Buf_Limit at 10MB at fluent-bit didn't help. FluentD is still restarting and fluent-bit.
I also tried removing record transformers from fluentD config file, but it didn't help.

@edsiper Do you reproduce this problem on your side?

@repeatedly cannot reproduce here.
@TomekLacina would you please provide a sample of your /data/preprod/test/logviewer2/failtest.txt file that helps to reproduce the problem ?

this is sample line from test data, more can be easily produced by java snipped I have posted before.
test;2017-04-15 00:01:00,131;AVS;;BULKREAD;Message;;"";failTest0
I have tried tweaking  configuration a bit, and it started to working. I have realised that, when I set
buffer_chunk_limit higher than 8m, fluentD is restarting, I have also switched to td-agent and fluentd provided there, and it seems to work for now.


Adding Flask-Stormpath to the extension registry.

I'd love to get Flask-Stormpath listed on the Flask extension registry. I've followed all the inclusion rules (to the best of my knowledge). Would love to have someone review it and get it added (if possible!).

You added the project to the unlisted section.  Force push a commit with it in the correct section and I'll merge.

70f9c13d5119d5b983fe022077665c721fc8fac6

Thanks for adding it in! Any chance you're going to push the updates live sometime soon? ^^ <33


Add beta mode

Add beta mode, add related SWF files, and update README.

Thank you for your contribution! Please apply the same patches to main, and re-open the pull request, since I don't want to waste an hour trying to merge this into main. Thanks!


Fixes for the build problems introduced by the earlier gen-report merge.

Quick commit in-between work and lack of old GHC's to test with lead to the previously merged gen-report breaking the Travis tests. This should fix all those issues. See #142

Thanks!


Adding new content to message.

Hello,
When Baresip initialized I want to add a content to registration message to become like this
        REGISTER sip:sip.cloud.com SIP/2.0
        Via: SIP/2.0/UDP <IP_ADDRESS>:5060;branch=z9hG4bK-10503-1-0
        From: <sip:xxxxx@sip.cloud.com>;tag=1
        To<EMAIL_ADDRESS>        Call-ID<EMAIL_ADDRESS>        CSeq: 1 REGISTER
        Max-Forwards: 70
        Contact: xxxxx@<IP_ADDRESS>:5060
        EXTRAAAA : 5
        Content-Type: application/sdp
        Content-Length: 0

The extra info I want to add is  EXTRAAAA : 5
Thanks,

have a look in reg.c:
https://github.com/alfredh/baresip/blob/master/src/reg.c#L196
you can modify the call to sipreg_register to something like this:
			      params[0] ? &params[1] : NULL,
			      "Extra: 5\r\n"
			      "Allow: %s\r\n", uag_allowed_methods());


Annotation API

This PR uses an experimental annotation API (Nextflow PR coming soon) to define processes.
Notable changes:

processes are defined as regular functions with a @ProcessFn annotation that defines additional process configuration.
the function parameters define the process inputs, while the inputs section in the annotation only defines how to stage files / environment vars / stdin based on the parameters
similarly, the outputs section separates the staging out of files / envs / stdout from the outputs definition with emit
the annotation uses the same builder DSL to define directives, inputs, and outputs
the script=true denotes that the process generates script tasks, in which case the function should return the task script
processes are invoked exactly as before, each input channel is mapped to a function argument
since the process inputs can be statically typed, the sample tuple is replaced with a Sample class for better type checking

What is the goal of this experimentation? I understand that static typing is a bonus and I like having a well defined value object for input/output. A huge downside that I see is that this is even further away from a pure DSL and closer to just writing pure Groovy and thus you are limiting the audience of who can read/write workflows in this way. I would say that the nextflow DSL already exposes a lot of Groovy to pipeline authors, which increases the complexity and limits accessibility.

I agree that the DSL already exposes a lot of Groovy code, and I would love for it to become more declarative. I think most people want to either use a purely declarative syntax or use a programming language that they're already familiar with, but the DSL sits in a weird middle ground that satisfies no one.
The goal of this annotation API then is to provide the pure Groovy approach, while at the same time we could work to make the DSL more declarative. This way, users can use one approach or the other based on what they are more comfortable with, and they can even be mixed within the same pipeline (i.e. you might write your pipeline with the DSL but use modules written in pure Groovy).
In other words, the programmatic approach "frees" the DSL to become more declarative without the burden of having to support every possible use case. If the DSL doesn't support some particular edge case, you can always fall back to the programmatic approach.
As for static types, I have a few ideas for how to add also them to the DSL, but there are a few design trade-offs to consider. The annotations here support static types by basically being more verbose, so I think in the DSL we would want something more concise.

All good points Mahesh. While I don't like the added verbosity of the inputs / outputs either, it was done in order to enable arbitrary types.
For inputs, you declare the inputs and their types (the function arguments) and in the inputs section you define what you want to stage into the task in terms of the arguments. So you could have a Sample class with various Path members, like reads and then you declare with Paths you want to stage e.g. path { sample.reads } and so on.
For outputs, you declare which envs/files/stdout you want to stage out of the task, and then you declare the outputs, one channel for each emit. The key point is that you can emit anything -- a simple value, tuple, map, custom type -- and you can reference what you staged out by matching key.
This rnaseq-nf isn't complicated enough to illustrate this point, so let me try an example here:
@ProcessFn(
inputs={
    path('file1.txt') { sample[1] } // if sample were a tuple [ id, left, right ]
    path('file1.txt') { sample['left'] } // if sample were a map
    path('file1.txt') { sample.left } // if sample were a record
},
outputs={
    path('$file1', 'file1.txt')
    path('$file2', 'file2.txt')
    emit { [ sample.id, path('$file1'), path('$file2') ] } // tuple
    emit { [ id: sample.id, left: path('$file1'), right: path('$file2') ] } // map
    emit { new SamplePair( sample.id, path('$file1'), path('$file2') ) } // record
})
def PROC(sample) {
  // ...
}

Also there's still the two object types path and Path which can add to the confusion.

path has a different meaning here, it is really a directive rather than a type. We could just as easily have directives like pathIn and pathOut but that felt weird. Whereas Path is the standard Java type that you're already using when you invoke file() or Channel.fromPath(). You just never have to say Path explicitly but we start doing static types then you will.

Any suggestions how this might go with reusable modules (i.e. nf-core modules)? Say one workflow defines the Read class with just name and path, but another workflow defines it with name, cohort, path, strand. Is there a way to pass on input field values of a class to output field values of a class using a predefined process definition. How much would need to change when included into two different workflows where the classes are defined differently. I guess one should interfaces here for the type. That would make it easier if the user wants to define the class with a different name.

This is an exploration activity. I don't think it will ever be used for real pipelines.

@mahesh-panchal this is a good question regardless of the annotation API, since we want to have static types for the DSL. That is, how can users share and re-use types without clobbering each other's definitions.
I think in nf-core you would want to follow a similar approach for types as you do with modules. For example the nf-core/modules repo could have a lib directory with a groovy script for each type definition, and modules can reference those types. Currently this is the only way to re-use custom types beyond a single module, but we could make them include-able components like processes if it makes sense.
Beyond that, I would say that the community will just have to find alignment around common types. You can always start out by having a custom type for every module and then combining types where it makes sense. Types can extend a common base type or interface where there is shared structure/behavior, but that is a game that should be played with caution.

The goals of this exploration were to (1) improve error messages for syntax errors (2) support static types and (3) explore the trade-offs of writing pipelines in pure Groovy. The annotation API isn't a specific thing that we want to do so much as a vehicle for those goals, it satisfied all of them.
I think if we add a programmatic interface it should be in Python, so a pure Groovy approach is probably just another weird middle ground.
Thinking about the DSL, I think we can minimize the amount of Groovy code by (1) isolating as much Groovy code as possible to the lib directory while enforcing a simpler syntax for Nextflow scripts (basically processes + workflows + basic Groovy syntax) and (2) studying the nf-core pipelines for gaps in the DSL where Groovy is heavily used and plug them (see the current work on channel topics, cmd output type, module config). A linter would be much easier to write if we don't have to support the entire Groovy language 😉

I think the idea makes some sense. I think the goal of the Nextflow DSL is more to make it easy to define a workflow without needing to know Groovy. However a quick glance at NF-core reveals that many workflows use both meaning Nextflow developers now need to know by NF and Groovy. Most of the DSLs that I have seen and used augment an existing programming language to make it easier to perform certain tasks so it is not too surprising that Groovy can leak into Nextflow (it would be hard to prevent it).
To truly prevent the need to learn two languages I think you would have to either define Nextflow as a language (not a DSL). This could certainly be done. The other path would be to do what is suggested here and write only Groovy and use annotations or some other metaprogramming to define the parts that will be distributed processes/ dependencies in the DAG etc.

Closing since this exploration has concluded. Follow https://github.com/nextflow-io/nextflow/pull/4553 for updates on adding static types to process inputs/outputs.

Folks, I have developed a prototype for typed process inputs/outputs which reuses some ideas from this exploration but in the context of the existing DSL. Feel free to check it out and offer any feedback there: #26


docs: Use new lexicon and remove dashes

- What I did

s/@platform/atPlatform
removed dashes (as they didn't look tidy)
shortened description of at_commons

- Description for the changelog
docs: Use new lexicon and remove dashes

Turned to draft as I just spotted some post at_mono stuff that needs fixing.

Good to go now


Some improvements regarding odbc-api usage

Hello @genusistimelord ,
thanks for providing an r2d2 adapater for odbc-api. I assumed some of the code has been copy pasted for r2d2-odbc and I want to propose some changes more idiomatic to odbc-api.
Cheers, Markus

Hello @genusistimelord ,
thanks for providing an r2d2 adapater for odbc-api. I assumed some of the code has been copy pasted for r2d2-odbc and I want to propose some changes more idiomatic to odbc-api.
Cheers, Markus

yes it was based on the original r2d2-odbc .
Thank you for your help.


Update log4j version

Environment Details

Helidon Version: 3.x and 4.x

see https://github.com/helidon-io/helidon/blob/566cfc4fc1cf43792b37af1dd7484fe22815ccb4/dependencies/pom.xml#L95
see https://mvnrepository.com/artifact/org.apache.logging.log4j/log4j-api
We need to update log4j to a more recent version.  Requested by a user.

Reopening to also address slf4j and logback versions


How to get selected value?

How to get selected option from the dropdown?

This can be done via the onSubmitEditing prop. You can check the example project to see how this works. Hopefully this will help you.


[edn/dv] Assert that local escalate causes FSM error

Description
EDN specific issue of: https://github.com/lowRISC/opentitan/issues/16269
Effort range 2-4

estimate 4

@vogelpi for visibility on this one. Believe that this should be done in the first sprint. Please lower priority and backlog if risk is low.

@moidx and I discussed this today and think this is low risk and can hence be postponed to the production tapeout.
We'll move it to M2.5 backlog for now.

Closing as this is a duplicate of #16269 .


[Chores] Use new version of inyono/changelog

in the new changelog.ts there is no need to set name, but just tagName.

FYI: name is just an optional "prettier" name (e.g. in our case to get rid of the v prefix).

Thanks for your feedback.
I didn't know that. In version 0.4 the changelog package works good. With that is this issue resolved.
But just to note: after upgrading it to 0.5.2 I get the error
/home/hugo/ws/serlo/serlo.org-database-layer/node_modules/ts-node/dist/index.js:842
            return old(m, filename);
                   ^
Error [ERR_REQUIRE_ESM]: require() of ES Module<EMAIL_ADDRESS>from /home/hugo/ws/serlo/serlo.org-database-layer/scripts/changelog.ts not supported.
Instead change the require of index.js in /home/hugo/ws/serlo/serlo.org-database-layer/scripts/changelog.ts to a dynamic import() which is available in all CommonJS modules.
    at Object.require.extensions.<computed> [as .js] (/home/hugo/ws/serlo/serlo.org-database-layer/node_modules/ts-node/dist/index.js:842:20)
    at Object.<anonymous> (/home/hugo/ws/serlo/serlo.org-database-layer/scripts/changelog.ts:26:21)
    at Module.m._compile (/home/hugo/ws/serlo/serlo.org-database-layer/node_modules/ts-node/dist/index.js:848:29)
    at Object.require.extensions.<computed> [as .ts] (/home/hugo/ws/serlo/serlo.org-database-layer/node_modules/ts-node/dist/index.js:850:16)
    at phase4 (/home/hugo/ws/serlo/serlo.org-database-layer/node_modules/ts-node/dist/bin.js:414:16)
    at bootstrap (/home/hugo/ws/serlo/serlo.org-database-layer/node_modules/ts-node/dist/bin.js:49:12)
    at main (/home/hugo/ws/serlo/serlo.org-database-layer/node_modules/ts-node/dist/bin.js:32:12)
    at Object.<anonymous> (/home/hugo/ws/serlo/serlo.org-database-layer/node_modules/ts-node/dist/bin.js:526:5) {
  code: 'ERR_REQUIRE_ESM'
}


Add function to export spatialdata to legacy anndata format

As discussed in https://github.com/scverse/spatialdata-io/issues/47 and https://github.com/nf-core/spatialtranscriptomics/issues/39#issuecomment-1908014245

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

Comparison is base (1f97ea7) 41.25% compared to head (bde0314) 37.01%.
 Consider uploading reports for the commit 560fe96 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #102      +/-   ##
==========================================
- Coverage   41.25%   37.01%   -4.25%
==========================================
  Files          16       16
  Lines         875     1086     +211
==========================================
+ Hits          361      402      +41
- Misses        514      684     +170

Files
Coverage Δ

src/spatialdata_io/__init__.py
100.00% <100.00%> (ø)

src/spatialdata_io/converters/legacy_anndata.py
50.00% <50.00%> (ø)

... and 8 files with indirect coverage changes

Thank you @grst for the PR. I am adding a from_legacy_anndata() function so that I can setup some tests of bidirectional conversion on artificial data.
One note on your implementation. I see that the code assumes that adata.uns is populated with dataset information. This is generally not the case. I would change the signature from
def to_legacy_anndata(sdata: SpatialData) -> AnnData:
	pass

to
def to_legacy_anndata(sdata: SpatialData, coordinate_system: str | None = None) -> AnnData:
	pass

With the following behavior:

if coordinate_system is not specified and their is only one coordinate_system in the SpatialData object, then coordinate_system will assume that value. Otherwise an error is raised.
the function identifies all the images that belong to a particular coordinate system, and for each of them creates a dataset_id value, which is placed in adata.uns['spatial'].
for each of these images, the transformation to the coordinate system is applied and the image is downscaled 2 times, once to create a ~2000x2000 image and once to create a ~600x600 image. These images are placed inside adata.uns['spatial'], together with their scalefactors
if no table is present, an empty AnnData object is created (with only things in uns), otherwise the table information is copied to the AnnData object to be returned
if the table annotates labels or shapes, the centroids and average radii are computed, and this info is placed in sdata.uns and sdata.obsm.

What do you think about this? If you agree on the above I will continue your PR and proceed with the implementation.

Sounds good, I'm just wondering how generalizable this function needs to be. Has the "legacy AnnData" format been used for anything but visium?

Yes it has been for many techs, for instance in the legacy squidpy datasets and with SODB. Anyway I'll try to not overgeneralize: I want to lay down some foundations for eventual converters for other libraries but I'll still keep it focused on the legacy anndata.

I think I fixed the problem with the docs. Now all the errors (docs and tests) are due to the lack of a release in spatialdata.


TriggeringSignal.COMBAT_ACTION Should be Splitted to Better Simulate Game Mechanics

Tests were performed showing cards like Absorbing Prism cannot trigger status effects that are described as "After Your Character uses a Skill".

Scheduled.

fixed in 538af2e


prepare-yum-repositories: cooperate with make CUSTOM_REPO=...

@caringi , @pkubatrh, that's what I talked about yesterday...  It detects
whether CUSTOM_REPO=/an/repo/file.repo or CUSTOM_REPO=/dir/repo/
was passed during 'make build'.
It's not nice, but it is neither the first hack in that file.  Comments welcome!

Looks good, thanks.

Looks good, I do not think we need the line below with this change:
[ -f /etc/yum.repos.d/redhat.repo ] || SKIP_REPOS_ENABLE=true

We should also document that the user has to provide a specific name for his repository if he wants to use the feature (outside CUSTOM_REPO which does it for him). Do we even have the documentation for yum-prepare-repositories somewhere?

On Monday, April 30, 2018 8:49:00 AM CEST Petr Kubat wrote:

Looks good, I do not think we need the line below with this change:
[ -f /etc/yum.repos.d/redhat.repo ] || SKIP_REPOS_ENABLE=true

So I dropped it.  Thanks.

We should also document that the user has to provide a specific name for his
repository if he wants to use the feature (outside CUSTOM_REPO which does it
for him).

Documented.

Do we even have the documentation for yum-prepare-repositories somewhere?

I don't think so, except for the self-documentation in the file itself.
That would be separate issue, though.

I don't think so, except for the self-documentation in the file itself. That would be separate issue, though.

Definitely. I was just wondering where would be the best place to make the change but if we do not have anything yet it should suffice to have it in-code.

Fedora CI fails when trying to pull s2i-core - seems like it is not available in the registry (but should be). Not related to this PR so ignoring.

Works good with both CUSTOM_REPO use cases so lgtm, merging.


how to import without type checking

I have a bunch of modules which are auto generated.
For these modules, obviously there is no separate typescript declaration file. So when i try to import them in my typescript file, the compiler give an error msg.
Sample directory structure:
src
- main.ts
- templates
- - test.html.js

Sample code:
import React = require('react');
import test = require('../templates/test.html');

Here line 2 will give an error cause there is no typescript definition for '../templates/test.html' module.
How do i use the module inside typescript?
The modules are in common-js format and I am generation ES5. Using typescript 1.6

You can use
declare var require: Function;
var test: any = require("react");

Did you even read the question?
First off, the issue is not with require("react");, its with  require('../templates/test.html');.
Also the issue is not with the type of 'test', its with typescript not finding a declaration for  '../templates/test.html'.

Even after modifying with your code:
import React = require('react');
declare var require: Function;
import test = require('../templates/test.html');

I still get the error
Cannot find module '../templates/test.html'

These sorts of general questions are probably better on StackOverflow...  Especially since you are trying to combine React and TypeScript, you need a broader audience of people to help you.
I suspect you will need to declare an ambient module for your project.  So somewhere as part of your project, you should have a .d.ts that would contain something like this:
declare module '../templates/test.html' {
    export var index: any;
}

Or some sort of type that is meaningful in your code.

import test = require('../templates/test.html');

It looks like you didn't read my answer. I used a var, not an import.

`'../templates/test.html'

I suspect that if you're trying to get the textual content of a file, then you want to use readFile. If there's something about require that I'm not aware of, then others might be able to help better.

Did you even read the question?

Please watch your tone in the future.
And as @kitsonk mentioned, these sorts of questions are more well-suited for StackOverflow.


fix typos

Fix typos.

@marcguzmanalbiol What should I do now? I think my handle needs to be added to that list...
https://github.com/0xPolygonHermez/clabot-config/blob/master/.clabot


Cannot export .ipynb file to .py file.

Environment data

Jupyter Extension version (available under the Extensions sidebar): v2020.11.392013122
Python Extension version (available under the Extensions sidebar): 3.9
OS (Windows | Mac | Linux distro) and version: XXX
Python and/or Anaconda version: XXX
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): XXX
Jupyter server running: Local | Remote | N/A

Expected behaviour
I expected it to export to a .py file.
Actual behaviour
I got an error.
Steps to reproduce:
Output for Jupyter in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Jupyter)

<EMAIL_ADDRESS>~/.vscode/extensions/ms-toolsai.jupyter-2020.11.392013122/pythonFiles/pyvsc-run-isolated.py jupyter nbconvert --version
<EMAIL_ADDRESS>~/.vscode/extensions/ms-toolsai.jupyter-2020.11.392013122/pythonFiles/pyvsc-run-isolated.py jupyter nbconvert --version
Error 2020-12-01 16:05:31: Export failed [r [Error]: Traceback (most recent call last):
File "/Users/JacobEkegren/.vscode/extensions/ms-toolsai.jupyter-2020.11.392013122/pythonFiles/pyvsc-run-isolated.py", line 26, in
runpy.run_module(module, run_name="main", alter_sys=True)
File<EMAIL_ADDRESS>line 210, in run_module
return _run_module_code(code, init_globals, run_name, mod_spec)
File<EMAIL_ADDRESS>line 97, in _run_module_code
_run_code(code, mod_globals, init_globals,
File<EMAIL_ADDRESS>line 87, in _run_code
exec(code, run_globals)
File "/Users/JacobEkegren/Library/Python/3.9/lib/python/site-packages/jupyter.py", line 4, in
main()
File "/Users/JacobEkegren/Library/Python/3.9/lib/python/site-packages/jupyter_core/command.py", line 285, in main
command = _jupyter_abspath(subcommand)
File "/Users/JacobEkegren/Library/Python/3.9/lib/python/site-packages/jupyter_core/command.py", line 124, in _jupyter_abspath
raise Exception(
Exception: Jupyter command jupyter-nbconvert not found.

at ChildProcess.<anonymous> (/Users/JacobEkegren/.vscode/extensions/ms-toolsai.jupyter-2020.11.392013122/out/client/extension.js:9:101413)
at Object.onceWrapper (events.js:313:26)
at ChildProcess.emit (events.js:223:5)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)]

Thanks for the bug. It looks like you don't have nbconvert installed correctly into your interpreter.
You can try fixing this by:

Creating a new environment from scratch. We should prompt you to install ipykernel which will download nbconvert.
Try installing nbconvert yourself into your 3.9 environment.

@jekegren01, please reopen if Rich's suggestion doesn't fix it for you.


issue in Batch syntax coloring, but upstream ericzou/ebundles is unmaintained

Per blob/master/grammars.yml (line 244), source.dosbatch is associated to "vendor/grammars/ebundles/Bundles/MSDOS batch file.tmbundle", which points to:
https://github.com/ericzou/ebundles "TextMate bundles ported to e-texteditor"
However,

ericzou/ebundles has had no commits in the last 7 years
http://e-texteditor.com/ (which ericzou/ebundles mentions as homepage) currently appears to have been overtaken by someone else
ericzou's GitHub homepage reports no contributions later than last year's October
http://www.ericzou.com (which is mentioned in https://github.com/ericzou/ ) is empty and provides no contact information

Last Oct 23, I reported an issue on ericzou/ebundles, about wrong unclosed string handling (an unterminated string is rendered on github.com as if it were multi-line and including the subsequent lines, breaking the syntax coloring). In a month, this issue has not received any attention.

@astroxe if you're comfortable making the change then please fork the upstream repository and make the fix. We can then switch out the grammar repository for Batch to your fork.
If you decide to go this route then please be sure to provide links to Lightshow demonstrating the fix: https://github-lightshow.herokuapp.com/

I'm not sure why this issue is closed. It seems to me that this is not resolved. There is another issue with batch files that comments do not function as they should either. I have been communicating with Jess Hosman at github support about this possibly related issue.
@echo off
rem this text should be green
echo hello world


Added common components

Added table, title and tag common components
Added view for ancestries
Adjusted views and routes

Preview of changes views:


Modifiers cannot be deleted/removed from certain Item types

[v1.3] Item types affected:

Specialization (via cog in top-right position)
Force Power (via cog in top-right beside Basic Power)
Signature Ability (via cog in top-right beside Base Ability)

Example reproduction:

Create a new Specialization item.
Click the cog in the top right to open modifier list.
Add a modifier.
Attempt to delete it by clicking the little trashcan icon.

Expected result:

Modifier dies horribly and vanishes without a trace.

Actual result:

Immortal modifier refuses to die.

After doing some research, this broke as part of the Foundry Core update 0.7.9.  I've taken a cursory look at it and updates to the item data are not propagating to the render function, but are making their way into the database but because of the workflow with the forms, it adds/removes the modifier and then removes/adds it back to the previous state.

After doing some research, this broke as part of the Foundry Core update 0.7.9.  I've taken a cursory look at it and updates to the item data are not propagating to the render function, but are making their way into the database but because of the workflow with the forms, it adds/removes the modifier and then removes/adds it back to the previous state.

Fixed in dev branch.

Fixed in dev branch.


blank screen with thunderbolt connected monitor

Regression?
Yes
System Info and Version
 System/Version info
<Paste the output of the command here>

Description
External monitor connected via thunderbolt (from my laptop directly to the monitor) does not consistently display and spawn a workspace when it is hotplugged. Works when Hyprland is started with the monitor plugged in. Regression from 41 when this worked reliably and regression from 42 (non -git release) when it worked inconsistently.  Peripherals and charging correctly work.
Symptoms matched  #7321 but issue was not fixed when others were.
How to reproduce
Observe display on boot, unplug Dell XPS 9310 from an HP monitor via thunderbolt, plug back in, observe no display.
Crash reports, logs, images, videos
Logs forthcoming based on hyprwm/aquamarine#76

dmesg.log

hyprland.log

can you please add your hyprland.conf

hmm.. does it work on sway?
btw this seems unrelated to AQ_NO_MODIFIERS since there is no DDB stuff in dmesg.log

@romanstingler  Sorry for the delay, this setup is at my workplace.
env.txt
Most of my dotfiles are from Illogical Impulse (though I've since moved on to an amalgamation of a few setups so there's some customization)
hyprland.conf.txt
env.conf.txt
execs.conf.txt
general.conf.txt
rules.conf.txt
colors.conf.txt
keybinds.conf.txt

Update - When I boot the machine up unplugged and then plug it in, the display works fine. It seems as though if the display has been seen already since first Hyprland launch it fails to get readded.

Update - When I boot the machine up unplugged and then plug it in, the display works fine. It seems as though if the display has been seen already since first Hyprland launch it fails to get readded.

uuuh... can you give hyprland.log where you boot, and replug so it works

Any updates? I'm still having this exact same problem.

I am using workaround for this where I just restart the monitor and then image appears.

I have the same issue. What is working for me is :
hyprctl dispatch dpms off DP-x
hyprctl dispatch dpms on DP-x

Or two dpms toggle...

I have the same issue. What is working for me is :
hyprctl dispatch dpms off DP-x
hyprctl dispatch dpms on DP-x

Or two dpms toggle...

I ended up with the same hack myself.

@christophe-vescovi @erahhal
can you guys give a full hyprlandd.log of you guys using the dpms trick
I think the problem is that the enable commit fails because a pageflip is happening or something

I've attached the log.
hyprland.log

Not sure if related but on occasion the DPMS trick doesn't work, and when this happens wdisplays and wlr-randr show the same external display twice.

Update - When I boot the machine up unplugged and then plug it in, the display works fine. It seems as though if the display has been seen already since first Hyprland launch it fails to get readded.

uuuh... can you give hyprland.log where you boot, and replug so it works

Hi! Sorry for the delay, I've been in super crunch mode since September. Here's a log file of me launching hyprland, Plugging in my monitor successfully, unplugging, plugging in my monitor unsuccessfully, unplugging, then closing hyprland.
hyprland.log

@croots can you try this patch.txt for hyprland
@erahhal your issue seems unrelated based on logs (its some weird output manager stuff like you said)
you should make an issue and try to find a minimum repo with a config as close to the default one as possible

@croots can you try this patch.txt for hyprland

This patch worked with 93b4478e70af6ffb08a4a66a6d0364c3296db296! Thanks for your help.


doc backport: clean up and move doc of OPENSSL_TRACE from man1/openssl.pod to man7/openssl-env.pod

This backports #25540 to 3.0 and 3.1:
The general text required some cleanup,
and the details on OPENSSL_TRACE fit much better in openssl-env.pod.
Checklist

[x] documentation is added or updated
[ ] tests are added or updated

Merged to 3.0 and 3.1 - thanks for the swift reviews


Broken OpenType slanted fractions

Description
When using text with #set text(fractions:true), but not rendering fractions, the output doesn't behave too well
#set text(fractions: true)
1 20 333333 1/4 1/5/5 6/ /7

renders as

whereas it should look like (or something similar)

Reproduction URL
No response
Operating system
Web app, Linux
Typst version

[X] I am using the latest version of Typst

Can't change anything about how the OpenType feature works, but I added a note to the docs that advises against enabling this property globally.


CivitAI Link Not Connecting??

For the last few days my A1111 has not been able to connect to the CivitAI website and yesterday my connections that are usually shown on the CivitAI website are gone. I've been trying to create a new key but its just hanging on "generating key"
Is this due to the host change? Looking on Discord seems like I'm not the only having the issue but I haven't seen anyone address any of the posts. Here is my debugging text below.
If it is because of the host change it's totally understandable, just a heads up would be great!
#######################################################################################################
Initializing Civitai Link
If submitting an issue on github, please provide the below text for debugging purposes:
Python revision: 3.10.6 (tags/v3.10.6:9c7b4bd, Aug  1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)]
Civitai Link revision: 2dfc03c17304278ca0b456366cc7871a2af8377b
SD-WebUI revision: baf6946e06249c5af9851c60171692c44ef633e0
Checking Civitai Link requirements...
[!] python-socketio[client] version 5.7.2 NOT installed.
#######################################################################################################

#86


docker: fix data race on err

Fix data race on err variable in the goroutine

Could you please sign off your commits (try git commit -s) in order to pass CI checks?
https://github.com/containerd/project/blob/master/CONTRIBUTING.md#sign-your-work

@mxpv sign-off added. Thanks.


how to use the Slimux in tmux?

hi,guys.I see the video from @dvbuntu and decide to use the Slimux.
I install it by Vundle,not the pathogen.
Then i set the configure.

After that ,i want to test it .
But i don't how to use it in the tmux.

i use the C-c,C-c in the vim and C-b o change to another window, Then i don't know how to do .
Does everyone give me am example. Thanks.

I got it by checking the slime. Thanks.


PrimaryDataService.scala is unused and could possibly be removed

Looks like edu.ie3.simona.agent.participant.data.primary.PrimaryDataService is not used anywhere.

I remember some discussions I had with @ckittl some time ago - maybe he can explain why this class is needed/exists?!

It was meant to serve as a meta-information container for services. Back then, when there hasn't been a primary source at all, I envisioned it to be one service among the others. Thus, it was meant to be treated as any other service, e.g. like in
https://github.com/ie3-institute/simona/blob/eb986c5691c9f7d5bcd79f4ca0bda2111ed22b75/src/main/scala/edu/ie3/simona/agent/participant/ServiceRegistration.scala#L46-L56
However, with the current implementation, the primary source is distinguished from the secondary services. This means, that we can fully revise the structure of DataService trait and it's children.


Add start date in a rule in admin widget

Hi,
i want to set event recurrences in the admin widget with a start date but i dont find how to do this, start date of my rules automatically take a datetime.now()
from datetime import datetime
import recurrence

myrule = recurrence.Rule(
    recurrence.DAILY
)

pattern = recurrence.Recurrence(
    dtstart=datetime(2015, 10, 2, 0, 0, 0),
    dtend=datetime(2015, 10, 9, 0, 0, 0),
    rrules=[myrule, ]
)

It thats i want, i got an event started a 2october with daily recurences to 9 october, i check to python dateutil and its easy to do this directly with it too. In your app i really enjoy the admin widget, my users can easy enter complex recursive events with it, but if they can't set a start date will difficult.
in recurrence.fields we can see this : " Field that stores a recurrence.base.Recurrence object to the
database."
Ok i go in base.Recurrence i see this :
`dtstart` : datetime.datetime
        Optionally specify the first occurrence. This defaults to
        `datetime.datetime.now()` when the occurrence set is
        generated.

Im in this case, it generate me an automatic start date.
In recurrences.forms.RecurrenceField :
`accept_dtstart` : bool
            Whether to accept a dtstart value passed in the input.

Im really confuse, how to set a dtstart in the input?
Thanks for your help

You can't do this with the JavaScript widget - if you need to do this, add a DateField to your model, and then use that for generating recurrences.

You mean i have to do something like this ?
class Event(models.Model):
    title = models.CharField(_('title'), max_length=100,unique=True)
    slug = models.SlugField(_('slug'), unique=True,null = True, blank = True)
    start = models.DateField(_('start'))
    end = models.DateField(_('end'))
    recurrences = RecurrenceField()

    def save(self, *args, **kwargs):

        myrule = recurrence.Rule(
        recurrence.DAILY
        )

        pattern = recurrence.Recurrence(
        dtstart=self;start,
        dtend=self.end,
        rrules=[myrule, ]
    )
    self.recurrences = pattern

    super(Event, self).save(*args, **kwargs)

But like this how can i deal with complex recurrences? In this case i dont find the utility of the JavaScript widget if i have to create my own api if i want a start date for my recurrences...
Thanks

No, you can just modify the way you get recurrences back to specify a start date, not the actual recurrence that is saved.

an automatic dtstart is set to datetime.now() when i save my models, there is no way to override this by my start date?

Sure there is - with something like this on your Event model:
def occurrences_between(self, start_date, end_date):
    return self.recurrences.between(start_date, end_date,
                                    dtstart=start_date - timedelta(days=1),
                                    dtend=end_date)

If you don't want an end date, then you can use after. There's some documentation for this which you might find helpful.

Sry i dont understand, if i have this (no end date) :
class Event(models.Model):
    title = models.CharField(_('title'), max_length=100,unique=True)
    slug = models.SlugField(_('slug'), unique=True,null = True, blank = True)
    start = models.DateField(_('start'))
    recurrences = RecurrenceField()

i put my start date to 2015-10-02 , i create a daily recurrence rule with the javascript widget with until at 2015-10-09, when i save models thats create me a daily occurence with a start date at 2015-09-21 to 2015-10-09, i can't override the automatic dtstart set to 2015-09-21 with my own start date?

When you save your model, you create a recurrence rule. You can (and should) override dtstart, per the documentation I linked above, in whatever code you're using to get yourself back a list of dates from a recurrence rule (I presume that's what you're doing - there's not much point storing recurrence information unless you're trying to get some dates out of the rule).
So, in your case, if you want to get a generator of occurrences beginning at the start attribute of your model, you'd do something like this:
def occurrences(self):
    return self.recurrences.after(self.start, dtstart=self.start, inc=True)

Hi,
Thanks,i find a way with the between method, in my case i have a date from a datepicker and want list events with an occurrences for this date so :
models
class Event(models.Model):
    title = models.CharField(_('title'), max_length=100,unique=True)
    date_start = models.DateTimeField(_('start'))
    recurrences = RecurrenceField(null = True, blank = True)

    def occurrences_between(self, start_date, end_date):
            return self.recurrences.between(start_date, end_date,
                                dtstart=self.date_start + timedelta(days=1),inc=True )

views
def get_date1(request,date="2015-10-06"):

    eventDate = datetime.strptime(date,'%Y-%m-%d')
    eventDate = pytz.utc.localize(eventDate)

    event_array = []
    getEvents = Event.objects.all()

    for event in getEvents:

         if event.recurrences and event.occurrences_between(eventDate,eventDate + timedelta(days=1)):

            if not event in event_array:
                event_array.append(event)

return render(request, 'agenda/date1.html', locals())

But i have a little problem, i dont find a way for include the until date in occurrences, if i set same start_date and until date i got the event at the date, but if my start_date is a 2015-10-02 and until at 2015-10-09, my event stop at 2015-10-08.
Thanks

I'm not quite sure what you're asking here. If your pattern doesn't match 9th October, you won't get 9th October. If you want to manually add the date 9th October, you can always add the date onto your array manually. Or am I misunderstanding what you're trying to do?

I assume that when i enter a daily recurrences for example from 2015-10-02 to 2015-10-09 my event finish at 2015-10-09 not at 2015-10-08 so why the until date is exclude?

I have find why i have to add timedelta (days=1) when i call occurrences_between, if my own date_start is at 2015-10-02  00:00 and if i do raise ValueError(self.date_start) during occurences_between, thats return me this : 2015-10-01 22:00:00+00:00 , but if i show my date_start in the templates that return me 2015-10-02, i think i have a timezone problem or something like that...

Problem solve, timezone problem, i set default timezone to utc and just will convert output if needed. Sry for these incomprehensible questions i was so confused with dates and time :p
Last question, set a datetime.now() as default dtstart create so much usless occurrences in my case and i think many others, It would not be better to give us the possibility to set our own dtstart, and if the user want datetime.now he just set himself?
Thanks

Glad you worked it out.
As to changing dtstart, that'd be backwards incompatible, and I'm not convinced it's worth the effort, personally. If someone can come up with a good way to make the change without making upgrading django-recurrence hard, I'd be happy to take a look, but let's handle that elsewhere.


Fix onnx-mlir.py docker wrapper

Requiring input files to have known suffix (.onnx, .json, or .mlir) greatly simplifies the onnx-mlir.py docker wrapper.
Signed-off-by: Gong Su<EMAIL_ADDRESS>

Requiring input files to have known suffix (.onnx, .json, or .mlir) greatly simplifies the onnx-mlir.py docker wrapper.

Just confirming that this new requirement is only for the onnx-mlir.py script, or do you intend to also enforce it for onnx-mlir and onnx-mlir-opt to keep things consistent?

# Release/bin/onnx-mlir foo
Invalid input file 'foo': Either an ONNX model (.onnx or .json or '-'), or an MLIR file (.mlir) needs to be provided.

onnx-mlir already does it. Don't know about onnx-mlir-opt.

Jenkins Linux ppc64le Build #6950 [push] Fix onnx-mlir.py docker ... started at 23:33

Jenkins Linux amd64 Build #7886 [push] Fix onnx-mlir.py docker ... started at 22:31

Jenkins Linux s390x Build #7903 [push] Fix onnx-mlir.py docker ... started at 23:31

Jenkins Linux amd64 Build #7886 [push] Fix onnx-mlir.py docker ... passed after 1 hr 1 min

Jenkins Linux s390x Build #7903 [push] Fix onnx-mlir.py docker ... passed after 1 hr 26 min

Jenkins Linux ppc64le Build #6950 [push] Fix onnx-mlir.py docker ... passed after 1 hr 31 min


Fireball splash rotation based on player rotation, not spell rotation

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Launch a fireball
Rotate before it lands
Watch

Expected behavior
A fireball should be rotated the way it flies

This bug will be resolved in the next release (v0.4)


Fix missing transaction ID in success URL & fix coding standard

You need to send transaction ID to success page.

I can't test success page because I don't know how to enter those URLs, you need to give instructions for those fields.

I tried it but not sure why it still has an error "Transaction ID not provided" from getSuccess function.
Also, this below returns $payment as null.
$payment = $paymentRepository->getFirstBy([
'charge_id' => $tran_id,
]);
Log::info('Payment data from Repository', ['payment' => $payment]);

For Reconcile (Check Transaction) and Transaction List API, please see this: https://github.com/alnovate-digital/aba-payway-botble/blob/main/README.md