Segmentation fault with custom operator

Description
Hi all. I've just recently stumbled into a segmentation fault, which I can't really explain. Creating a new operator (even the softmax in the example) leads to it.
Environment info (Required)
----------Python Info----------
Version      : 3.5.2
Compiler     : GCC 5.4.0 20160609
Build        : ('default', 'Nov 17 2016 17:05:23')
Arch         : ('64bit', 'ELF')
------------Pip Info-----------
Version      : 9.0.3
Directory    : /home/exx/.local/lib/python3.5/site-packages/pip
----------MXNet Info-----------
Version      : 1.2.0
Directory    : /home/exx/.local/lib/python3.5/site-packages/mxnet
Commit Hash   : b2ccd34ad2801b6c87c957c28ad718562a4c5b6e
----------System Info----------
Platform     : Linux-4.4.0-92-generic-x86_64-with-Ubuntu-16.04-xenial
system       : Linux
node         : tensorflow
release      : 4.4.0-92-generic
version      : #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017
----------Hardware Info----------
machine      : x86_64
processor    : x86_64
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                32
On-line CPU(s) list:   0-31
Thread(s) per core:    2
Core(s) per socket:    8
Socket(s):             2
NUMA node(s):          2
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 79
Model name:            Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
Stepping:              1
CPU MHz:               1268.449
CPU max MHz:           3000.0000
CPU min MHz:           1200.0000
BogoMIPS:              4191.30
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              20480K
NUMA node0 CPU(s):     0-7,16-23
NUMA node1 CPU(s):     8-15,24-31
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm
 pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdseed adx smap xsaveopt cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts
----------Network Test----------
Setting timeout: 10
Timing for Conda: https://repo.continuum.io/pkgs/free/, DNS: 0.0764 sec, LOAD: 0.0217 sec.
Timing for PYPI: https://pypi.python.org/pypi/pip, DNS: 0.0028 sec, LOAD: 0.2659 sec.
Timing for FashionMNIST: https://apache-mxnet.s3-accelerate.dualstack.amazonaws.com/gluon/dataset/fashion-mnist/train-labels-idx1-ubyte.gz, DNS: 0.0201 sec, LOAD: 0.3272 sec.
Timing for Gluon Tutorial(cn): https://zh.gluon.ai, DNS: 0.1216 sec, LOAD: 0.3743 sec.
Timing for MXNet: https://github.com/apache/incubator-mxnet, DNS: 0.0022 sec, LOAD: 0.4305 sec.
Timing for Gluon Tutorial(en): http://gluon.mxnet.io, DNS: 0.2415 sec, LOAD: 0.3285 sec.

I'm using mxnet-cu80 for Python 3.5.
Build info (Required if built from source)
Downloaded via pip install --user mxnet-cu80==1.2.0b20180516. I was using mxnet-cu80-1.0.0, but ran into this same problem, and tried updating.
Error Message:
Segmentation fault: 11

Stack trace returned 10 entries:
[bt] (0) /home/exx/.local/lib/python3.5/site-packages/mxnet/libmxnet.so(+0x331d6a) [0x7f3b7618fd6a]
[bt] (1) /home/exx/.local/lib/python3.5/site-packages/mxnet/libmxnet.so(+0x2968b06) [0x7f3b787c6b06]
[bt] (2) /lib/x86_64-linux-gnu/libc.so.6(+0x354b0) [0x7f3be81064b0]
[bt] (3) /home/exx/.local/lib/python3.5/site-packages/mxnet/libmxnet.so(+0x4b7589) [0x7f3b76315589]
[bt] (4) /home/exx/.local/lib/python3.5/site-packages/mxnet/libmxnet.so(+0x4b8655) [0x7f3b76316655]
[bt] (5) /home/exx/.local/lib/python3.5/site-packages/mxnet/libmxnet.so(+0x684bf8a) [0x7f3b7c6a9f8a]
[bt] (6) /home/exx/.local/lib/python3.5/site-packages/mxnet/libmxnet.so(MXSymbolCreateAtomicSymbol+0x6e1) [0x7f3b782e66a1]
[bt] (7) /usr/lib/python3.5/lib-dynload/_ctypes.cpython-35m-x86_64-linux-gnu.so(ffi_call_unix64+0x4c) [0x7f3be6ef9e20]
[bt] (8) /usr/lib/python3.5/lib-dynload/_ctypes.cpython-35m-x86_64-linux-gnu.so(ffi_call+0x2eb) [0x7f3be6ef988b]
[bt] (9) /usr/lib/python3.5/lib-dynload/_ctypes.cpython-35m-x86_64-linux-gnu.so(_ctypes_callproc+0x49a) [0x7f3be6ef401a]

## Minimum reproducible example
I believe this is the core of what is leading me to the error:
```        user_embed = mx.symbol.Embedding(name="user_embed", data=user,
                                         input_dim=max_users, output_dim=embed_size)
        item_embed = mx.symbol.Embedding(name="item_embed", data=item,
                                         input_dim=max_items, output_dim=embed_size)
    user = mx.symbol.L2Normalization(user_embed)
    item = mx.symbol.L2Normalization(item_embed)
    dot = user * item
    dot = mx.symbol.sum_axis(dot, axis=1)
    cosine = mx.symbol.Flatten(dot)
    pred = mx.symbol.Custom(data=cosine, label=[score], name='sm', op_type='softmax')

The softmax operator is implemented as in the example (copy-paste).

Ok, I believe I'm mixing things. Closing this for now, until I've understood what's going on.


OpenStack is not respecting enable_config_drive: False

(Most probably not the right place to report this, writing it down so we can be aware)
$ grep -r config_drive *
config/provisioning-config.yaml:    enable_config_drive: False
config/mrackdb.json:        "config_drive": "True",

That is affecting Windows and Linux hosts. Changing mrack source code to force config_drive as True when provisioning hosts does not matter, same result.

This might be openstack provider configuration so it hardcodes the config drive option to true which we may not affect at all :) will close this issue for now.


chore: add binaries for 1.28.14, 1.29.9, 1.30.5

What type of PR is this?
/kind feature

What this PR does / why we need it:
add binaries cache for kubernetes patch versions 1.28.14, 1.29.9, 1.30.5
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 71.271%

Totals

Change from base Build<PHONE_NUMBER>8:
0.0%

Covered Lines:
2590

Relevant Lines:
3634

💛  - Coveralls


build: avoid using the legacy location for BlocksRuntime library

Update the library search path to use the CMake output directory.  This was
relying on the staging to make this work.  Additionally add the location for
BlocksRuntime as well.  This allows us to use the just built dynamic
BlocksRuntime and libdispatch.

@swift-ci please test

I have a change to SwiftPM to do something similar in the build.  Finally got around to cleaning up from the migration to CMake.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test


merge from template-kronos-app

package.json

chore(deps): add ^9.0.0 remove ^8.3.21 (devDependencies.npm-pkgbuild)

:tada: This PR is included in version 1.10.92 :tada:
The release is available on:

v1.10.92
GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Create framework for suggesting improvements o Linux For Health

I created this as a folder under the connect repo, but now thinking this might be best served by having its own repo under the organization as connect is just one of the components.

@jonathan-consensysHealth if you set up the build process that allows selection of the branch into the build as well as a ethereum smart contract to connect to a route into FHIR et al this would be fine.


[feature suggestion] Add a V4L source module

So that Radiance would be able to read from the webcam.

You can actually do this already using the MovieNode block. Just type in /dev/video0 into the prompt and you should get your webcam. There is also a super hacky way to pass arguments like resolution, but I forget how it works (not at a computer right now, sorry)

@yurivict does the MPV block work for you? It's under "Custom" in the library. MPV supports a pretty wide variety of URLs and parameters, you can see resources/qml/Instantiators/YoutubeInstantiator.qml as an example of an MPV-based node that builds an MPV-accepted URL from a youtube search query.


Homepage Testimonial Section Heading is missing

Describe the bug
The heading of the testimonial section of the website homepage is missing and too much spacing between rows.

Expected behavior
The section should have the heading Testimonials just like other sections have headings.

I would like to work on this issue

Added the heading , one more thing I noticed is the logo of red hat looks too small compared to the other sponsor logos. Shall we fix this too?

I would like to work on this issue

Added the heading , one more thing I noticed is the logo of red hat looks too small compared to the other sponsor logos. Shall we fix this too?

Awesome. What about the spaces (did you notice that as well). For the logo, noticed it too. @magicmatatjahu @mcturco can have a say on that.
You can send in a PR and wait for the review.

Yeah I saw that too. Working on it.

Cool. Alright then.👍

I tried and referred to docs too
using gap-y-0 but I see no changes in the website. I think I'm missing something

@starlightknown You will fix it from the testimonial.js file.
check line 11, where I underlined. That fixes it. Reduces the top and bottom padding from 16 to 4.


Inspection to warn you when using non-deterministic input types for file collection

In general, given consistent input, Gradle aims for consistent ordering for FileCollection. However, users can declare a set of dependencies using a HashSet, which might now enforce any ordering.
This is an ask to add an inspection (that can be enabled with an additional flag), that will report usages of types that do not have a deterministic iteration order when creating FileCollection. This issue can focus on FileCollection as that is the most common use-case.

This can cause unstable classpaths in third party plugins: https://github.com/asciidoctor/asciidoctor-gradle-plugin/issues/591
This might also be related to this issue: https://github.com/gradle/gradle/issues/15626

Sorry for the late reply.
This feature request is in the backlog of the relevant team and is prioritized by them.


docs: update etcd logging details

Since release 3.1.0-rc1, etcd can be forced to print logs to stdout
even if journals is available. This updates the workaround in our docs.
Reference https://github.com/coreos/etcd/pull/6799
Fixes https://github.com/coreos/rkt/issues/3394

LGTM


Support scenarios

https://github.com/beyond-all-reason/Beyond-All-Reason/blob/master/singleplayer/scenarios/scenario000.lua
https://github.com/beyond-all-reason/BYAR-Chobby/blob/b1fb5b4a60f91f5a214f43a64d07d4cdedb31a5b/LuaMenu/widgets/gui_scenario_window.lua#L677

Scenarios now implemented, but missing personal records because I don't believe there's any way for bar lobby to get this info currently

Supposedly there is a local socket interface for spring.exe that we might be able to utilise to send data between the lobby and game


trouble when login github for comments in my blog

my blog: https://perfectstranger.me/
when login github account I got a error 1101 from cloudflare

and I don't know how to fix it. I'm totally new for web development and wish your answer!

Utterances has been removed in the latest release. I decided to simplify things since it wasn't seeing much usage.

How can I configure Utterances?


JOSS #3

[ ] In the "Statement of Need" section, it would be beneficial to provide more detailed comments on the existing challenges in estimating survival parameters and performing full-body survival analysis within a deep learning framework. By addressing these challenges, the importance of developing an "interpretable and easy-to-use" survival analysis toolbox, like the one presented in this paper, becomes more evident.

[ ] In the "Statement of Need" section, It would be great to include the need for having computationally efficient tools in deep survival analysis, as this would highlight one of the advantages of this framework.

[x] Please fix the typo under example

neg_partial_log_likelihood(log_hz, event, time, reduction = 'sum') # **sum** of log likelihoods across patients
neg_partial_log_likelihood(log_hz, event, time, ties_method = "breslow")  # Dealing with ties **(Breslow)**

[x] In the API documentation, it would be great to mention that an error message will appear when event ties exist while the user does not specify the parameter "ties_method".

[x] Since most functions have been demonstrated with outputs using simulated toy datasets in the tutorial, could you add an example of the KM plot to showcase the visualization of your plot_km() function?

@tcoroller please review the update in the "Statement of Need section"

looks good, just checked. Is that all the to do list for this item?


[DPE-3634] Rework spark-history-server into new pattern

Refactoring of Spark History server according to new pattern
@marcoppenheimer @zmraul

Merging, given @theoctober19th and @welpaolo approvals, as this is really blocking the other PR #32 to be finalized. @juditnovak feel free to share thoughts (if any) anyway for future tuning and improvement. Thanks!

I was late to the party indeed :sweat_smile:
Joke aside: though not direct comments, but we looked at the PR together with @marcoppenheimer so his comments were representing my opinon as well.
Having said that, I'd like to +1 on his considerations regarding common read/write interface or not.
I also prefer his approach within the guidelines of "Simple is better than complex".
No matter what, most importantly I guess we all agree on the following: we all believe this is typically the level of detail we should leave as the freedom of the developer of the charm... (I.e. not part of any conventional standards or strongly recommended patterns.)


squid:S00122 - Statements should be on separate lines

This pull request is focused on resolving occurrences of Sonar rule
squid:S00122 - Statements should be on separate lines.
This pull request removes technical debt of 8 minutes.
You can find more information about the issue here:
https://dev.eclipse.org/sonar/rules/show/squid:S00122
Please let me know if you have any questions.
George Kankava

Automated message from Dropbox CLA bot
@georgekankava, it looks like you've already signed the Dropbox CLA. Thanks!

lgtm. this has been merged. thanks for the patch!


use std::unordered_map instead of std::map

lookup has constant complexity with std::unordered_map

Wow again, @schiller-manuel! :) Thanks for providing this PR - we really appreciate this! Will go through and test and report back.


Don't delete nodes that have used descendants

Fixes https://github.com/CesiumGS/gltf-pipeline/issues/532
Don't delete a node if it has a descendant that's used for skinning or animation. In the case of #532 a parent of a node in the skin's joints list was being removed. I confirmed the test passes in this branch but not in master.

:+1:


Only use/fetch cookies when necessary

Possibly fetching browser cookies adds additional download time when it is not necessary for most of the videos. Maybe a meta-tag (e.g. age-restricted=true) could be introduced so that cookies are only fetched for those age-restricted videos.

This can be used as a test case:
https://www.youtube.com/watch?v=pvy7BLaggt4
http://usdb.animux.de/index.php?link=detail&id=16397

Closing this as we now only fetch cookies when creating a session and this optimisation probably wouldn't be noticeable.


Some fields might not be present when assembling the signature

I think there could be a potential issue with the signature function which expects the following fields to always be present (see comments as to why they might not be)
TxAuthNo // Only present if Status is OK.
CAVV // Only present if the 3DSecureStatus field is OK or ATTEMPTONLY
AddressStatus // Paypal only
PayerStatus // Paypal only

In addition, the spec states that the vendor name must be lowercased prior to hashing.
Edit:
Futhermore, if the transaction status is ABORT - these fields aren't present either:
AVSCV2
AddressResult
PostCodeResult
CV2Result
3DSecureStatus
CardType
Last4Digits
TxAuthNo

These fields should all return an empty string "" if they are not present, so the hash ought still to work. In the V3.00 Server spec it says:

If a field is returned without a value this should not be included in the string [to be hashed].

So the empty strings can be concatenated together without any effect on the hash. It will be worth and end-to-end test though, and perhaps writing some tests, just to make sure all those values are empty strings and not nulls.
Also in the spec:

Please ensure the VendorName is lower case prior to hashing.

Good point. That can be fixed. I suspect all vendor names already are going to be lower-case, but best to be explicit (that warning is in the spec for a reason).

I suspected that the function would probably return an empty string hence why the hashing function continues to work, but I question it because the last four items that are expected to be optional have a second parameter of an empty string - I'm assuming as a default if the item is not present. As you say, it might be returning something falsey other than an empty string.

Hmm, I actually think maybe $this->httpRequest->request->get() will return null if the parameter is missing, but I'm having a hard time finding the function signature.
Not sure why that would still work, unless PHP is converting it to an empty string.

Possibly:
php > echo "hello" . null . "world";
helloworld
php > echo strlen("hello" . null . "world");
10
php > echo "hello" . false . "world";
helloworld
php > echo strlen("hello" . false . "world");
10

Seems like it should work, by a lucky fluke ;-)
Just to show a different type conversion:
php > echo "hello" . true . "world";
hello1world

Here is the spec for get():
http://api.symfony.com/2.0/Symfony/Component/HttpFoundation/Request.html#method_get
It will return a NULL by default, if the (POST) http value is not set. They should all be set to default to and empty string IMO, just to be a little more explicit on what is going on in that signature function.

I agree. Especially when IMO the SagePay spec doesn't do a good job of describing accurately which fields will be present when!

PR #54 puts in empty string defaults for unsent fields.


Rate limiting should be ignored when Redis client is unreachable

Description
If the Redis client throws an error, such as  ECONNREFUSED <IP_ADDRESS>:6379, RedisStore should act as a useless middleware instead of blocking the API where it's being used. Catching the Redis client error does not help since RedisStore will still throw an error about the Redis client.
Why
Rate limiting is not vital for an API like a database and it should not prevent it from working in case Redis is unreachable.
Alternatives
Catching Redis client errors, catching inside sendCommand.
signalLimiter = rateLimit({
            windowMs: 1 * 60 * 1000,
            max: global.gConfig.MAX_REQUESTS_PER_MINUTE,
            standardHeaders: true,
            legacyHeaders: false,
            store: new RedisStore({
                sendCommand: (...args) => {
                    try {
                        return redisClient.sendCommand(args);
                    }
                    catch (err) {
                        console.log("An error occurred while sending Redis command", err);
                        return true; // does not work
                    }
                }
            }),
        });

Desired behavior when Redis client error occurs:
signalLimiter ~= (req, res, next) => next();

Hi @dark-matter-matters,
Sorry for the late response :/
This is definitely a good idea - we could re-add the passIfNotConnected option to handle such connection errors.

The original reason I had removed that option in https://github.com/wyattjoh/rate-limit-redis/pull/43 was that it was now the developer who handled connection via a client of their own choice, so instead of returning true, they could simply return 0 to set the clients count to 0 and continue. That logic was invalidated when we switched from simple INCR commands to using EVALSHA, and it makes sense to add this option.

@wyattjoh what do you think?
@dark-matter-matters if @wyattjoh approves the idea, would you be interested in working on a PR for this? (or I could do it too :D)

@dark-matter-matters did this ever get implemented here?

I agree that an option for passIfNotConnected is useful, but may lead to situations where while booting, it may pass traffic through without limiting. Rate limiting from my perspective is a security feature, and this seems akin to saying "if the powers out, just unlock all the doors", which feels like a risk. The opt-in beheviour suggested bia the option seems like the best of both worlds, but I would rather see it only apply after the first connect, or perhaps accept a function that would get the number of attempts where it could adjust the internal state to allow or not.

It would be useful to be able to catch Redis errors and handle as needed.
For example when I need to update my Redis, it fails over to a replica using DNS, and the client is still connected to an old node for a while, which doesn't accept writes. In my application it'd be fine to disable rate limiting for the ~5min, instead of having the whole service unavailable.

seems akin to saying "if the powers out, just unlock all the doors", which feels like a risk

been in this situation multiple times. so happy that it is how it actually works in the buildings! i wouldn't care for getting locked in or out in this case

Ok, express-rate-limit v7.4.0 should be released shortly with a new passOnStoreError option that allows you to configure the limiter to "fail open" if your redis server goes down.

Ok, express-rate-limit v7.4.0 should be released shortly with a new passOnStoreError option that allows you to configure the limiter to "fail open" if your redis server goes down.

Hello,
We're facing strange async middleware issues with this flag passOnStoreError basically if redis store is not accessible (command timeout) - it should go to next middleware.
In our case it starts to execute next async middleware as expected but after promise is fired inside it - the next middleware starts without waiting until the last one finishes. On debugger basically code execution is jumping between two middlewares.

That doesn't sound good! Can you file a new issue, and also see if you can make a minimal project that reproduces the issue?


Issues with Retention Policy Module

Dear Team,
I was checking the Retention Policy Module and here are some issues which I found:

Instead of Table Caption in the header the Table Name is shown (which shows also the Prefix)

Expired Records field does not show correct values - even if records exist (before deleted with the manual run) the field always shows 0.

(Minor thing) Job Queue for Retention Policy does not have a description

Thank you for reaching out. Your request could be reporting a product bug not related to the AL extensibility. Please reach out to the relevant support channels as specified in Product Support
On premises - https://support.microsoft.com/en-us/supportforbusiness/productselection?sapId=93d37907-ad94-d591-22e9-593cfa09dd3f
On line – read more here https://docs.microsoft.com/en-ca/dynamics365/business-central/dev-itpro/administration/manage-technical-support or contact your partner
If you are a partner open a support incident through Partner Center - https://partner.microsoft.com/en-us/pcv/dashboard/overview


Coveralls file published with repo_token

The published npm package contains a .coveralls.yml which has a repo_token field. I don't know if this is security issue as I don't know what the token is for (and do not want to try testing it everywhere). It should probably be a npmignore line to keep it out of the package

Coveralls isn't in the repository anymore. Hasn't been for quite a while - that's safe to ignore.
Thanks for the ticket though :)


datasets of lion2tiger request

Hi, could you please release the datasets of the lion2tiger?
Many thanks!

+1


21/04/2023 - Reference to the article under publication added.

No further changes are required to the README.md file.


Fix Error when Authed, but deleted

In the case when a session was authenticated as a user, but the user was deleted BEFORE the session was logged out, every subsequent to the gallery would 500.
This fix makes it so if we get into this state, the user will be logged out, redirected to the home page, and shown a message indicating that their account was deleted.
Preview:

How was this tested?

Tested locally for both password auth and MSA auth accounts.

Does this PR fix https://github.com/NuGet/NuGetGallery/issues/7033?


Authentication failed with Salesforce CDP

Hi all !!
I'm getting an error when i try to connect with my Salesforce CDP environment. The error says "Authentication failure".
I think that is because salesforce CDP ask a verification code (multi factor authentication). I don't now if dbeaver supports this kind of authentication, but i'm not sure.
Thanks!

there has been no update for a long time.
If the issue is still actual, feel free to reopen it and add log files.


Implement Touchability

Implement a delegate method that reports when touches occur for the newest version.
Pass the location in the graph view where the touch occurred (in the ScrollableGraphView's space).
Pass the location of the point on the graph (in the ScrollableGraphView's space).
Pass the x and y values of that point.
This should allow users to respond to these touches and add do whatever they see fit (show other views with more information, etc).

Hey @philackm , super curious if you got any progress

Hi guys. Sorry for the lack of communication here. I'm currently working full-time and am in the last semester of my Master's course, so I have had very little time to dedicate to anything else. Hopefully once this semester is finished I will have some free-time to continue work on this.
Alternatively, I'm more than happy to assign a few people (if anyone is interested) as collaborators to maintain/check and merge pull requests.

Thanks for your reply and fully understandable. My personal thoughts is that the feature to select nodes and then do something with it (detail-screens etc..) is something requested a lot. And from what I've seen there are a few PR's ready offering this exact functionality.
But of course time is needed for it to be checked and merged, and until then Ill watch this repo closely!

Which repo did you find that has this functionality? @Julianvantveld


Wrong version number

When using the badge, it remove the last zero for version numbers.
For example, 1.19 is displayed as 1.19, but 1.20 will be displayed as 1.2. This is a bit confusing, because my minor numbers are simply incrementing, so 1.2 is an older version, and not the same as 1.20.

For example, 1.19 is displayed as 1.19, but 1.20 will be displayed as 1.2.

@kroese For debugging, please provide the real-world example you met.

https://ghcr-badge.deta.dev/qemu-tools/qemu-docker/tags?n=1&label=version&color=SteelBlue&ignore=1.93,1.92,1.91

This is a bit strange behaviour...

It might be a bug of anybadge. print(anybadge.Badge(label="test", value="1.20").badge_svg_text, file=open("a.svg", "w")) outputs:


Make cwd of elm-make a configurable option

This solves an esoteric edge case for me. I use Broccoli across different projects in a monorepo, and I often include one Brocfile within another in order to compose projects. However, this causes broccoli-elm to break because the cwd of the child_process.spawn call is always inherited from the current process, which is not always running within the Elm project directory.
For example:
monorepo/
  project1/
    Main.elm
    elm-package.json
    elm-stuff/...
    Brocfile.js
  project2/
    Brocfile.js

If the Brocfile in project1 compiles Main.elm and the Brocfile within project2 calls require on the Brocfile within project1, then broccoli-elm will run using project2 as cwd, not project1. This causes the compilation to fail because it can't find elm-package.json.
When cwd is not set, behaviour remains the same.

Thanks @ilikebits!

@ilikebits FYI: This is now updated on npm as well.


[Snyk] Upgrade rehype-parse from 8.0.4 to 8.0.5

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade rehype-parse from 8.0.4 to 8.0.5.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 22 days ago, on 2023-08-16.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report
Patch has no changes to coverable lines.
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
:loudspeaker: Thoughts on this report? Let us know!.


Possible typo in Jumps

From https://eldred.fr/gb-asm-tutorial-v2/part1/jumps.html#conditional-jumps:

ld bc, Tiles.end - Tiles sets bc to the length of the tile data: Tiles.end is the address of the first byte after the tile data, so subtracting Tiles to that yields the length.

Tiles.end should probably be TilesEnd. I couldn't find this source in this repository so I wasn't able to submit a PR.

Fixed locally, closing. Thanks!


Caching docker images for .Net 5

Description
Added the .Net 5 docker images to be pre-cached in windows-2019 and ubuntu-2004.
Ubuntu-2004:
mcr.microsoft.com/dotnet/sdk:5.0-buster-slim - Used to build .Net 5 applications
mcr.microsoft.com/dotnet/aspnet:5.0-buster-slim - Used to run ASP.Net 5 applications
mcr.microsoft.com/dotnet/runtime:5.0-buster-slim - Used to run .Net 5 applications
mcr.microsoft.com/dotnet/runtime-deps:5.0-buster-slim - Used to run self-contained .Net 5 applications
Windows-2019:
mcr.microsoft.com/dotnet/sdk:5.0-nanoserver-1809 - Used to build .Net 5 applications
mcr.microsoft.com/dotnet/aspnet:5.0-nanoserver-1809 - Used to run ASP.Net 5 applications
mcr.microsoft.com/dotnet/runtime:5.0-nanoserver-1809 - Used to run .Net 5 applications
Couple of notes:

I chose to list out each of the images, I could have just included the sdk image which will pull down the others as part of it.  But by listing each one it makes sure that the tests check for them all, and that the software report lists them all.
I chose to use the more specific tags instead of the "5.0" tag (which also would work), to make it more obvious in the software report what OS the container images are based off of (until I did this PR I didn't realize that when you pull down the exact same image+tag on a windows host vs a linux host you actually get different images - I think this makes it clearer for others like me)
There is no runtime-deps image for windows because the nanoserver base image includes all the runtime dependencies needed (unlike debian)
I only updated the windows-2019/ubuntu-2004 images because I'm assuming if you're developing against the latest and greatest .Net version, you're probably using the latest and greatest build server image too (happy to update and test the other images if desired)

Related issue:
#2784
Check list

[x] Related issue / work item is attached
[x] Tests are written (if applicable)
[x] Documentation is updated (if applicable)
[x] Changes are tested and related VM images are successfully generated

@dylan-smith could you please pull the latest main to your branch? Sorry for the delay

Hello @dylan-smith , Is this PR still actual for you? If yes - could you please pull the latest main so we will be able to rerun CI.

Hi @dylan-smith,
I am closing this PR due to no response. If this change is still needed for you, please, file an issue in our repo to add it. Thanks.


Measure crc source using u64

2^32 is too small to represent the files that are being transferred today, so this API can't practically be used in file integrity checks. Using a u64 is a requirement for any code handling 'real' data sets.
This gets tricky since the API is already stabilised. I think there are two options:

A Crc::amount_u64 method
Add a defaulted generic parameter to Crc

<N = u32> where Wrapping<N>: Add<Wrapping<N>>
fn Crc::amount(&self) -> N

The CRC implementation in this crate exists solely to support the formats that use it. (Also, we wouldn't want to decrease its performance at all, which increasing the internal state might lead to.)
This crate doesn't support the zip format, and I don't think that's likely to change; that should be in a separate crate. I'm hopeful that a 64-bit CRC could live in that crate as well, since none of the formats in flate2 would use it.


Call 'markNeedsLayout' in textAlign setter

This PR adds/calls the 'markNeedsLayout' in the textAlign setter of a Text widget.
fixes issue 140756
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

I think this is by design. The width of the paragraph, and the width of the longest line is determined before text alignment is applied.
See https://github.com/flutter/flutter/issues/140756#issuecomment-1919777559

(triage) I am going to close this per the previous comment and since there was no more follow-up.


Merge Two IDSA Glossaries

Which part of the repository is your change request related to?
There are two glossaries on IDS related terms, and it would be good to merge them accordingly, if it makes sense.
IDS-G Glossary
the glossary on IDSA main repository
Please describe which content you would expect here and tell us how to solve this request
The two can be merged under the glossary on IDS-G.
Can you already provide any alternative (or updated) content that can/should replace the existing content?
None
Additional notes
None

Done. All the existing content has been moved to https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Glossary and rest will follow.


If placeholder in multiselect is undefined, it should display the standard text

Now it is like this

We use this to have it say "all" when there is no items selected

We have added support for providing your own placeholder text (in our [WIP] Autocomplete component). By default the "x/y items selected" will be shown unless placeholder is defined. If you are setting your own placeholder text for multiple selections make sure its declarative of whats selected in the dropdown, this is especially important for people using screen-readers.


C_Cpp.enhancedColorization is not found

Does this issue occur when all extensions are disabled?: Yes/No No

VS Code Version: 1.75 Insiders
OS Version: Windows 11

Originally, C_Cpp.enhancedColorization was present in the settings of VSCode.
However, I messed up (because I installed waaaayyy too many extensions), so I had to uninstall it. Reinstalled and had some issues with some "cppbuild" not showing up (fixed that by installing Build ++ and then doing npm install cppbuild, which worked.) And, now....
I get this:

Why is this happening?! Please help me!

You probably haven't reinstalled the extension which defines this setting.

What extension?

I don't know. Maybe use Extensions view to search, then check the Contributes tab of ones that look familiar to you.

Installed the C++ Extension. It now shows up! 🥳

Good. Please close this issue.


Idf solution

When calculating tfidf for a term that is not in the corpus it returns 0, but calculating idf for the term is Infinity (division by zero).
This code caclucates idf according to the Lucene variation of idf.
https://lucene.apache.org/core/2_9_4/api/all/org/apache/lucene/search/Similarity.html
                                 numDocs
     idf   =       	1 + log (	________  )
                                 docFreq+1

Are we good to merge this? I just tested it locally and it seems okay!

Are we good to merge this? I just tested it locally and it seems okay!

Hey sorry for the delay, im going to merge this and bump the minor version i should be able to get it out today

hey sorry for the delay on this, can you double check your tfidf spec against the latest version? When i checkout your branch directly everything seems fine but when i merge it in it fails a few tests.
It looks like the tests its failing are the ones added here: https://github.com/NaturalNode/natural/commit/27aaf8c39c27b13b730840a80dec106d03886b21

ok all fixed up thanks!

Thanks for merging, but we need to bump the version and publish it to NPM as well. I actually still have the ability to merge this project, but I can't publish it, and I don't want to step on any toes. :)

sorry it totally slipped my mind, just bumped the version and published now. and dont worry at all about stepping on toes you're welcome to jump in if you want :)


Button

Description
Scroll up button fixed
Fixes #103
Type of Change:

Code
Quality Assurance
User Interface
Outreach
Documentation

How Has This Been Tested?
Tested locally

Checklist:

[x] My PR follows the style guidelines of this project
[x] I have performed a self-review of my own code or materials
[x] I have commented my code or provided relevant documentation, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

nice work.
just little bit of alignment problem of the arrow(inside the circle),make it in center.


[MINOR] fix pulsar-io maven build configuration in pom.xml to avoid WARNING log

there is always WARNING log in maven build log like following：
2021-02-20T15:39:58.6034609Z + echo -n 'Test Group : BROKER_GROUP_2'
2021-02-20T15:39:58.6035074Z + case $TEST_GROUP in
2021-02-20T15:39:58.6035488Z + broker_group_2
2021-02-20T15:39:58.6036948Z + build/retry.sh mvn -B -ntp test -pl pulsar-broker '-Dinclude=**/MessagePublishBufferThrottleTest.java' -DtestForkCount=1 -DtestReuseFork=true
2021-02-20T15:39:59.6481733Z Test Group : BROKER_GROUP_2[INFO] Scanning for projects...
2021-02-20T15:40:02.8370210Z [WARNING]
2021-02-20T15:40:02.8374144Z [WARNING] Some problems were encountered while building the effective model for org.apache.pulsar:pulsar-io-core:jar:2.8.0-SNAPSHOT
2021-02-20T15:40:02.8376090Z [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin com.github.spotbugs:spotbugs-maven-plugin @ line 57, column 15
2021-02-20T15:40:02.8377234Z [WARNING]
2021-02-20T15:40:02.8450898Z [WARNING] Some problems were encountered while building the effective model for org.apache.pulsar:pulsar-io-batch-discovery-triggerers:jar:2.8.0-SNAPSHOT
2021-02-20T15:40:02.8463439Z [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin com.github.spotbugs:spotbugs-maven-plugin @ line 71, column 15
2021-02-20T15:40:02.8464777Z [WARNING]
2021-02-20T15:40:02.8470179Z [WARNING] Some problems were encountered while building the effective model for org.apache.pulsar:pulsar-io-batch-data-generator:jar:2.8.0-SNAPSHOT
2021-02-20T15:40:02.8475823Z [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin com.github.spotbugs:spotbugs-maven-plugin @ line 88, column 21
2021-02-20T15:40:02.8476977Z [WARNING]
2021-02-20T15:40:02.8478130Z [WARNING] Some problems were encountered while building the effective model for org.apache.pulsar:pulsar-io-common:jar:2.8.0-SNAPSHOT
2021-02-20T15:40:02.8483317Z [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin com.github.spotbugs:spotbugs-maven-plugin @ line 69, column 21
2021-02-20T15:40:02.8487566Z [WARNING]
2021-02-20T15:40:02.8490101Z [WARNING] Some problems were encountered while building the effective model for org.apache.pulsar:pulsar-io-docs:jar:2.8.0-SNAPSHOT
2021-02-20T15:40:02.8492048Z [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin com.github.spotbugs:spotbugs-maven-plugin @ line 138, column 15
2021-02-20T15:40:02.8493180Z [WARNING]
2021-02-20T15:40:02.8494298Z [WARNING] Some problems were encountered while building the effective model for org.apache.pulsar:pulsar-io-aws:jar:2.8.0-SNAPSHOT
2021-02-20T15:40:02.8496227Z [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin com.github.spotbugs:spotbugs-maven-plugin @ line 76, column 15
2021-02-20T15:40:02.8523187Z [WARNING]
2021-02-20T15:40:02.8524658Z [WARNING] Some problems were encountered while building the effective model for org.apache.pulsar:pulsar-io-aerospike:jar:2.8.0-SNAPSHOT
2021-02-20T15:40:02.8526649Z [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin com.github.spotbugs:spotbugs-maven-plugin @ line 79, column 15
2021-02-20T15:40:02.8527775Z [WARNING]
2021-02-20T15:40:02.8528910Z [WARNING] Some problems were encountered while building the effective model for org.apache.pulsar:pulsar-io-netty:jar:2.8.0-SNAPSHOT
2021-02-20T15:40:02.8531178Z [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin com.github.spotbugs:spotbugs-maven-plugin @ line 101, column 21
2021-02-20T15:40:02.8532305Z [WARNING]
2021-02-20T15:40:02.8533005Z [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
2021-02-20T15:40:02.8533715Z [WARNING]
2021-02-20T15:40:02.8534410Z [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
2021-02-20T15:40:02.8535122Z [WARNING]
2021-02-20T15:40:02.8764319Z [INFO] ------------------------------------------------------------------------
2021-02-20T15:40:02.8766196Z [INFO] Detecting the operating system and CPU architecture
2021-02-20T15:40:02.8773375Z [INFO] ------------------------------------------------------------------------
2021-02-20T15:40:02.8774528Z [INFO] os.detected.name: linux
2021-02-20T15:40:02.8776403Z [INFO] os.detected.arch: x86_64
2021-02-20T15:40:02.8813515Z [INFO] os.detected.release: ubuntu
2021-02-20T15:40:02.8814927Z [INFO] os.detected.release.version: 16.04
2021-02-20T15:40:02.8815805Z [INFO] os.detected.release.like.ubuntu: true
2021-02-20T15:40:02.8816722Z [INFO] os.detected.release.like.debian: true
2021-02-20T15:40:02.8817899Z [INFO] os.detected.classifier: linux-x86_64
2021-02-20T15:40:02.8894526Z [INFO]
2021-02-20T15:40:02.8958527Z [INFO] ------------------< org.apache.pulsar:pulsar-broker >-------------------

/pulsarbot run-failure-checks


System Error when running Ganache 2.5.4 on win32

It happens when I executed eth_getLogs. Several times eth_getLogs passed but with no result, just freezing the script, but on 10th occasion it has crashed completely.
PLATFORM: win32
GANACHE VERSION: 2.5.4
EXCEPTION:
Error: Incompatible EIP155-based V 0 and chain id 1. See the second parameter of the Transaction constructor to set the chain id.
    at Transaction._validateV (C:\Program Files\WindowsApps\GanacheUI_<IP_ADDRESS>_x64__5dg5pnz03psnj\app\resources\static\node\node_modules\ganache-core\node_modules\ethereumjs-tx\src\transaction.ts:370:13)
    at Transaction.set [as v] (C:\Program Files\WindowsApps\GanacheUI_<IP_ADDRESS>_x64__5dg5pnz03psnj\app\resources\static\node\node_modules\ganache-core\node_modules\ethereumjs-tx\src\transaction.ts:387:16)
    at C:\Program Files\WindowsApps\GanacheUI_<IP_ADDRESS>_x64__5dg5pnz03psnj\app\resources\static\node\node_modules\ganache-core\lib\utils\transaction.js:116:23
    at Array.forEach (<anonymous>)
    at initData (C:\Program Files\WindowsApps\GanacheUI_<IP_ADDRESS>_x64__5dg5pnz03psnj\app\resources\static\node\node_modules\ganache-core\lib\utils\transaction.js:110:18)
    at new Transaction (C:\Program Files\WindowsApps\GanacheUI_<IP_ADDRESS>_x64__5dg5pnz03psnj\app\resources\static\node\node_modules\ganache-core\lib\utils\transaction.js:168:5)
    at Function.fromJSON (C:\Program Files\WindowsApps\GanacheUI_<IP_ADDRESS>_x64__5dg5pnz03psnj\app\resources\static\node\node_modules\ganache-core\lib\utils\transaction.js:228:16)
    at C:\Program Files\WindowsApps\GanacheUI_<IP_ADDRESS>_x64__5dg5pnz03psnj\app\resources\static\node\node_modules\ganache-core\lib\forking\forked_blockchain.js:384:21
    at Array.forEach (<anonymous>)
    at Object.callback (C:\Program Files\WindowsApps\GanacheUI_<IP_ADDRESS>_x64__5dg5pnz03psnj\app\resources\static\node\node_modules\ganache-core\lib\forking\forked_blockchain.js:382:31)
    at sendTxCallback (C:\Program Files\WindowsApps\GanacheUI_<IP_ADDRESS>_x64__5dg5pnz03psnj\app\resources\static\node\node_modules\ganache-core\node_modules\web3-core-method\src\index.js:664:29)
    at onJsonrpcResult (C:\Program Files\WindowsApps\GanacheUI_<IP_ADDRESS>_x64__5dg5pnz03psnj\app\resources\static\node\node_modules\ganache-core\node_modules\web3-core-requestmanager\src\index.js:179:9)
    at C:\Program Files\WindowsApps\GanacheUI_<IP_ADDRESS>_x64__5dg5pnz03psnj\app\resources\static\node\node_modules\ganache-core\lib\forking\forked_blockchain.js:136:11
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

It works after upgrade with Ganache UI (v2.7.0). Same error happens when I use ganache-cli.

That's great news - ganache-cli has been deprecated, and is now just ganache - try npm install -g ganache@latest, and just start Ganache with ganache going forward, and that should resolve the issue.
LMK if this doesn't help and we can look further.
Cheers!


Add a build step in the git CI workflow

WHY are these changes introduced?
We need to add a build step to the git CI workflow so that dependencies are accessible in the lint and test steps.
WHAT is this pull request doing?
Update the CI workflow to include a build step
Type of change

[ ] Patch: Bug (non-breaking change which fixes an issue)
[ ] Minor: New feature (non-breaking change which adds functionality)
[ ] Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[x] I have used yarn changeset to create a draft changelog entry (do NOT update the CHANGELOG.md file manually)
[ ] I have added/updated tests for this change
[ ] I have documented new APIs/updated the documentation for modified APIs (for public APIs)

Thank you!


Add Opulence IoC

Thank you very much! Unfortunately, I couln't work on it even though I promised it because improving the reliability of the test suite was more important.


13e9cfb1-a650-4270-8e10-3f06e2adaa0e

this is for automated testing

d00b37cf-3ba6-4f1c-b848-f77cca5a9449


Add FuelEfficientPilots from SpaceDock

This pull request was automatically generated by SpaceDock on behalf of theshepherd, to add FuelEfficientPilots to CKAN.
Mod details:
name = /mod/1466/FuelEfficientPilots
author = theshepherd
abstract = Give Pilots better fuel efficieny based on experience
license = public-domain
Homepage =
description = Pilots have the ability to get better fuel efficiency through experience, so now your five-star pilot can give you better bang for your buck!
Please direct questions about this pull request to theshepherd.

Needs to have MM added as a dependency

This was redone and a pull request was submitted (#5753)

Is there anything more I need to do?

@Space-Duck, you can remove this request.  Thanks


Fix for locale resource not setting LC_ALL

Description

Before we were using utilities like localectl set-locale locale-gen and update-locale, but now we are directly writing the contents in required files which affects system locale. This would be a generic change and will support almost all the OS and that too without relying on the presence of an external script to achieve the same functionality.
Ensured chef-style on the code changes made

Issues Resolved
Fixes #7904 MSYS-946: locale resource does not set LC_ALL
Signed-off-by: Kapil Chouhan<EMAIL_ADDRESS>Check List

[ ] New functionality includes tests
[x] All tests pass
[ ] RELEASE_NOTES.md has been updated if required (not required for bugfixes, required for API changes)
[x] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

In PR review discussion we're thinking we should remove the default values for both the properties. As written write now we would write LC_ALL even if the user only specified lang, and would write LANG even if the user only specified LC_ALL.
Functionally, I don't think that is a breaking change.

I lean pretty heavily to wanting to close out the issue as WONTFIX on this one.
I think if someone really wants to bypass the safety check here designed by the systemd developers to not allow setting LC_ALL that they should just use a file resource themselves, we should not support that.

I lean pretty heavily to wanting to close out the issue as WONTFIX on this one.
I think if someone really wants to bypass the safety check here designed by the systemd developers to not allow setting LC_ALL that they should just use a file resource themselves, we should not support that.

Yes, but as per the documentation, it seems that primary functionality of locale resource is only to set/unset the values of LANG and LC_ALL and not any other LC_ values. Using a utility (like localectl) would be significant if we have plans to set any LC_ values other than LC_ALL and we might want to update the document accordingly.
But consider if we follow the doc, then we have to provide an alternative to set these ENV values.
Additionally, as a part of sanity we may check that if the input locale is valid/available to be updated or not.
Please let us know your views.

okay, yes, the bigger issue here is that we need lc_collate and all the rest of them.    that should probably be an entirely separate issue and should get done first.

@lamont-granquist Are you recommending that we not use this to fix the locale resource's current claim that it can set LG_ALL in favor of a more comprehensive LC_* management resource?

A proposed "resolution."

We add support for the other LC_ environment variables (what is the definitive list?)
For Chef 15, we remove (or just deprecate?) the lc_all property. Either way, we end up with a warning or error that points to a deprecation page on the docs site. That error and page would say two things:

Setting LC_ALL is not recommended and can break Chef's parsing of command output in unexpected ways. Use one of the more specific lc_ properties as needed.
If you still want to set LC_ALL, use this file resource:

file "/etc/default/locale" do
  content "LC_ALL=blah"
end
``

(with better docs than that). should suggest the alternative files than just `/etc/default/locale`.

As discussed we fixed this through adding support for other LC variables and deprecating LC_ALL in #8324.


Add borderless table feature wrt #22638

Intended as a fix for #22638.
CC @mdo @Johann-S

This doesn't seem like the right solution in the code. I haven't tested this, but it could probably all be reduced to something like maybe?
.table-borderless {
  td, th {
    border: 0;
  }
}

All we need to do is override the default .table styles, so perhaps compare against that opening .table ruleset?

I guess it should work without the explicit tbodys. Thanks for the time @mdo, Updating my PR

Making myself a note that this needs docs for when we're ready for it.

@Varunram: can you add the new class in our docs?

Sure, let me rebase the PR on master and revert all redundant commits.

@mdo: LGTY?

@mdo @cvrebert Is this to be added in a future release?


Clarify the messaging around the failure notification options

I noticed issue #518 came up today. It has also been a point of confusion for me in the past. I think clarifying the wording and moving the repeated failure option out of advanced could help.
I think overall I'd prefer just having one "notify on every failure" option, but this would be a nice improvement too.

Lol I just commented on your PR saying there should be an on every failure.

Would you want a third option, or replace these two with a notify on every failure?
I think ideally I'd like to have something higher level I could configure - like 'everything but repeated success' or 'everything'

third one for now, can potentially remove the other two,
I think the third one could go in the main section and the other two in advanced
and see how that works for people
what i have at work in pipeline is: every failure and fixed

A minor quibble (especially as this is merged already), but having two options with "Only" in them as checkboxes -- suggesting that they're mutually exclusive, but allowing both to be selected -- seems confusing. I'd remove the word "Only" from both, and ideally reword these as "Notify for first failure" (or "Notify for initial failure") and "Notify for repeated failures". You could also use "upon" instead of "for".

@medianick see my comment in https://github.com/jenkinsci/slack-plugin/issues/520#issuecomment-466333001


Error loading the trained model.

Hi guys, how are you?
I'm trying to load my trained model but I'm getting the following error:File not found: filepath=modelo\model_74.keras. Please ensure the file is an accessible .keras zip file.
Keras Version: 3.0.5
Tensorflow Version: 2.16.1
Code I'm using to load the model
from tensorflow.keras.utils import CustomObjectScope
from tensorflow.keras.models import load_model

from keras import backend as K # Estrutura de manipulação de tensores simbólicos

""" IoU """
def iou(y_true, y_pred, smooth=1):
    intersection = K.sum(K.abs(y_true * y_pred), axis=[1,2,3])
    union = K.sum(y_true,[1,2,3])+K.sum(y_pred,[1,2,3])-intersection
    iou = K.mean((intersection + smooth) / (union + smooth), axis=0) # Média de um tensor, ao longo do eixo especificado
    return iou

""" Dice Coefficient """
def dice_coef(y_true, y_pred, smooth=1):
    intersection = K.sum(y_true * y_pred, axis=[1,2,3])
    union = K.sum(y_true, axis=[1,2,3]) + K.sum(y_pred, axis=[1,2,3])
    return K.mean( (2. * intersection + smooth) / (union + smooth), axis=0)

""" Dice Coefficient Loss """
def dice_coef_loss(y_true, y_pred):
    return 1 - dice_coef(y_true, y_pred)

scope = {'iou': iou, 'dice_coef': dice_coef, 'dice_coef_loss': dice_coef_loss}
path_model = 'modelo/model_74.keras'

with CustomObjectScope(scope):
    modelo = load_model(Path(path_model))

I tried other PATHS:
path_model = './modelo/model_74.keras'
or
path_model = 'modelo//model_74.keras'
or
path_model = './/modelo//model_74.keras'
or
path_model = '//modelo//model_74.keras'

@clebemachado,
Could you please confirm whether you are trying to execute the code with the keras3.0 or tf-keras. Also I tried to execute the mentioned code and it was executed with a different error. Kindly find the gist of it here. Thank you!

It was the keras version, I changed it to 3 and it worked.

Hi, I am having the same issue. I got a model saved to "myfile.keras" by the ModelCheckpoint callback using TF 2.16.1 and Keras 3.3.3 in Python 3.10.12. When trying to reload the model with
import keras
model=keras.saving.load_model("myfile.keras")

I also get the "File not found: ... Please ensure the file is an accessible .keras zip file." error message from the initial posting by clebemachado. The file is definitely there and looks integer as far as I can say. At the beginning it has a "keras_version" : "3.3.3" entry. Looking at the code around line 187 of saving_api.py (which is referenced in the error output), I could imagine that the problem is that the file is not in keras .zip format, but has a ".keras" file ending. However, assuming this is the case, how would I make ModelCheckpoint saving the model in .zip format then? And would there still be a way to access my already trained and saved model?
Note that the same code for saving and reloading the model worked absolutely fine on another machine with TF V2.15 and Keras V2.15 (yes, the reported versions are identical).
I am a bit desperate at the moment, as my already trained model seems lost and I also don´t know what to change for a re-run. Any help is very appreciated!
@clebemachado: Could you maybe explain what exactly you did here:

It was the keras version, I changed it to 3 and it worked.


(HELP) aimbot autostop movement / trigger the Auto shot only if accurate for sniper rifle

as the title say, because as the current aimbot code i will surely miss the sniper shot if i'm not actually standing still
tried inside if bestTarget
cmd->forwardmove = 0;
cmd->sidemove = 0;
cmd->upmove = 0;

but it just don't work accurately
please give me any hint thanks!

did u done:)?


go.dev: Refresh times?

Hello!
How long does it take until pushed changes to the Go doc of a repo show up on go.dev?
The old Godoc site had a handy REFRESH button.
Thanks for your hard work,
Horst

https://go.dev/about#adding-a-package

thx,
I was looking for a change introduced by a commit that's not been released.
My bad


Update to the latest version of ApiGen

Presently we are using 2.8.1 but the latest available is 4.1:
http://www.apigen.org/

It seems to be the latest tagged version is not all that stable, I am seeing the same error locally as described here: https://www.bountysource.com/issues/29262698-apigen-crashes-with-kdyby-events


Handling CInitial with CID that matches an existing connection

Currently we first match on the connection ID, and only then consider that a packet might want to start a new connection. We probably need to be smarter about this.

§7.2 Negotiating Connection IDs

When an Initial packet is sent by a client which has not previously received a Retry packet from the server, it populates the Destination Connection ID field with an unpredictable value. This MUST be at least 8 bytes in length.

Is this a realistic concern?


aptnesses, biophysics (logical-conflict)

This pull request was generated by the 'mq' tool

/trunk merge


DO NOT MERGE - Testing upstream fix

https://review.openstack.org/#/c/408643/

Per our discussion in #691 , we will open a PR to make sure HIL will install a good version of kombu


[BUG]Good Repository

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

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.
Desktop (please complete the following information):

OS: [e.g. iOS]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Not enough information has been provided in this issue for us to help. Please edit and provide more details or close the issue if the problem has been resolved.


Exact stratified sample

Merge request template: please remove the appropriate parts of this template.
Pre-merge request checklist (to be completed by the one making the request):

[x] I have performed a full review of this code myself.

For Python code in PySpark specific sections, all code should have been run in Jupyter notebooks.
For code in sections of the book containing both Python and R code, the page of the book should be constructed as described in the contributing guide and converted to a markdown file.

[x] I have formatted the outputs of code blocks correctly (to match other outputs in the book and in line with the style guide [coming soon])
[x] I have built the book as outlined in the contributing guide and confirmed that any additional/modified content is displaying as expected.

Details of this request (such as):

Extended the sampling page to include a method for returning an exact sample for stratified sampling
This contains both pyspark and sparklyr code
Page has been converted into the markdown file

Things to note about this request (such as):

One small change has been made to the reading of the csv for sparkly r, otherwise all older sections are unchanged.
Because it uses a random uniform dist for sampling, outs will have changed between the old and new versions of the page.

closes #102

Changes look good, I've built the book and verified that it's displaying correctly so will go ahead and merge.


Issues with "==" (rather than ">=") in dependency declarations

Hi!
Currently, tickeys has hardcoded dependencies like cython==0.20.2 (https://github.com/BillBillBillBill/Tickeys-linux/blob/master/setup.py#L5) on a single very specific version (at multiple places). That inflexibility is a big problem for distribution packing where other packages would need to be fixed to that very version just to keep tickeys working. If many applications did that, I could hardly use two applications depending on the same other package at the same time. I hope that illustrates the problem.
This is the patch I applied for 0.2.5 in Gentoo:
https://cgit.gentoo.org/proj/betagarden.git/tree/x11-misc/tickeys/files/tickeys-0.2.5-requirements.patch
Please remove any use of == upstream. Many thanks!
Best, Sebastian

Closing to keep https://github.com/issues clean for myself…


Compilation Issues

I used this a few days ago without any issue. Today when I try to verify the firmware code it fails. Below you'll find a copy/paste of the compilation attempt.
voodoo.cpp:37:0: warning: "DEBUG" redefined [enabled by default]
^
In file included from ../services/inc/debug.h:1:0,
from ../wiring/inc/spark_wiring.h:36,
from ./inc/application.h:36,
from voodoo.cpp:35:
../services/inc/service_debug.h:109:0: note: this is the location of the previous definition
#define DEBUG(fmt, ...)
^
voodoo.cpp: In function 'long unsigned int pingRead(int)':
voodoo.cpp:422:45: error: call of overloaded 'pulseIn(int&, PinState)' is ambiguous
                                         ^

voodoo.cpp:422:45: note: candidates are:
In file included from ./inc/application.h:36:0,
from voodoo.cpp:35:
../wiring/inc/spark_wiring.h:82:10: note: uint32_t pulseIn(pin_t, uint16_t)
uint32_t pulseIn(pin_t pin, uint16_t value);
^
voodoo.cpp:375:15: note: long unsigned int pulseIn(uint16_t, uint8_t)

Original pulseIn Function for the Spark Core - Version 0.1.1 (Beta)
^
voodoo.cpp: In function 'int ToServoIndex(int)':
voodoo.cpp:242:1: warning: control reaches end of non-void function [-Wreturn-type]
if (pin == 0 || pin == 1 || pin == 2 || pin == 3) return pin;
^
make[1]: *** [../build/target/user/platform-6voodoo.o] Error 1
make: *** [user] Error 2
Error: Could not compile. Please review your code.

Can cofirm that https://github.com/Gabriel-Lacatus/voodoospark/commit/cb019b3d79d4f0490ff127afa4abd5726204a6cc works as a fix for this particular issue.
Photon firmware 0.4.7


support 4 display

@feijiang1 & @YuanjunHuang
Please help take a review of this changes, thanks a lot!


Fixes pathValueMerge to merge and follow references.

Reviewed this and the change looks good. @michaelbpaulson waiting on signoff from you.

@trxcllnt @jhusain the path value merge was intentionally never suppose to follow references.  All path values should be reported without references.
Notice below, that no references should ever be encountered in a path.
var route = new Router({
    route: 'lolomo[{integer:indices}]',
    get: function(alias) {
        return alias.indices.reduce(function(acc, curr) {
            acc.push({
                path: ['lolomo', curr],
                value: $ref(toSomeList())
            });
            return acc;
        }, []);
    }
});

Even with higher precedence paths, the same holds true, the JSON-Graph/PathValue return never consider references, just flat merge.

This feature is solely justified by the need to support bulk data loading
of heterogenous collections.
Let's say I want to load all of the data in a list, but that list might
contain any number of different types (characters, videos, series). If
different fieldsets need to be loaded for different types, then using
refPaths is suboptimal. Using refPaths, you would have 2 (poor) options.

Overfetching by requesting the Union of the set of paths for all
possible types.

Underfetching by requesting only those paths common to all objects, and
then following up with a secondary network request once the types of all
objects have been ascertained.

As part of the roadmap we are exploring ways of adding better support to
Falcor for  heterogeneous lists. Call is a very heavy hammer for this type
of thing, and the downside of using it is that we don't get any cache
benefit. As a result, I hesitate to commit this change until we have
finished the roadmap process. This process is moving swiftly, so I should
expect to have better insight into our direction on this soon.
JH
On Sep 2, 2015, at 11:11 PM, Michael Paulson<EMAIL_ADDRESS>wrote:
@trxcllnt https://github.com/trxcllnt @jhusain
https://github.com/jhusain the path value merge was intentionally never
suppose to follow references. All path values should be reported without
references.
Notice below, that no references should ever be encountered in a path.
var route = new Router({
route: 'lolomo[{integer:indices}]',
get: function(alias) {
return alias.indices.reduce(function(acc, curr) {
acc.push({
path: ['lolomo', curr],
value: $ref(toSomeList())
});
return acc;
}, []);
}
});
Even with higher precedence paths, the same holds true, the
JSON-Graph/PathValue return never consider references, just flat merge.
—
Reply to this email directly or view it on GitHub
https://github.com/Netflix/falcor-router/pull/128#issuecomment-137346251.
--
You received this message because you are subscribed to the Google Groups
"Falcor" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit
https://groups.google.com/a/netflix.com/d/msgid/falcor/Netflix/falcor-router/pull/128/c137346251%40github.com
https://groups.google.com/a/netflix.com/d/msgid/falcor/Netflix/falcor-router/pull/128/c137346251%40github.com?utm_medium=email&utm_source=footer
.

@jhusain can we merge this commit for now, and decide what to do about it later?

As part of the roadmap we are exploring ways of adding better support to
Falcor for  heterogeneous lists.

I am very interested in this scenario. Was the roadmap already published?


Unit conversion for the ionisation kernel

Ionisation kernel requires T in eV, n in m^-3, dt in s.
Density values projected back onto rho_src need to be in L^-3 where L is the Nektar length unit

Resolved by #162 .


Add feature summarize and update metric report

Codecov Report

Merging #979 (cfce6d3) into main (764c86d) will decrease coverage by 0.26%.
The diff coverage is 23.07%.

@@            Coverage Diff             @@
##             main     #979      +/-   ##
==========================================
- Coverage   68.36%   68.09%   -0.27%
==========================================
  Files         203      205       +2
  Lines        9242     9338      +96
  Branches     1540     1548       +8
==========================================
+ Hits         6318     6359      +41
- Misses       2476     2530      +54
- Partials      448      449       +1

Impacted Files
Coverage Δ

towhee/functional/mixins/metric.py
27.71% <7.40%> (-1.41%)
:arrow_down:

towhee/functional/mixins/display.py
41.37% <24.35%> (-15.49%)
:arrow_down:

towhee/utils/ipython_utils.py
50.00% <50.00%> (ø)

towhee/utils/pandas_utils.py
50.00% <50.00%> (ø)

towhee/hub/repo_manager.py
81.08% <0.00%> (+0.90%)
:arrow_up:

towhee/dataframe/dataframe.py
74.15% <0.00%> (+1.04%)
:arrow_up:

towhee/engine/graph_context.py
92.30% <0.00%> (+1.53%)
:arrow_up:

towhee/engine/operator_runner/runner_base.py
93.97% <0.00%> (+1.80%)
:arrow_up:

towhee/engine/operator_context.py
86.95% <0.00%> (+2.17%)
:arrow_up:

towhee/engine/task_scheduler.py
74.07% <0.00%> (+2.46%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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

/lgtm
/approve


node-gyp fails on node 8.

See the following build history:
https://travis-ci.org/ProjectMirador/mirador/builds
This has been a common problem for our contributors who attempt to clone and run the project with npm install without explicitly setting the node version, and is also an extremely commonly googled error that never seems to have gone away. Most of the time upgrading above node 6 resolves the issue, but other times it requires deleting binaries. What is the root of this problem and what configuration can I implement that will stop this happening for our contributors (and Travis)?

The current set of failures look like they're due to node:latest now being Node 8.0.0
https://travis-ci.org/ProjectMirador/mirador/jobs/237638277
$ node --version
v8.0.0
$ npm --version
5.0.0

Gotcha. I can pin that for now. Thanks for the help. I notice this is a frequently posted issue to your tracker. Any idea of a root cause, or just that there are a lot of platforms in existence?

Changing the title to reflect node version.

For posterity: node versions are not ABI backwards compatible so the version of nan used is incompatible with<EMAIL_ADDRESS>

node versions are not ABI backwards compatible so the version of nan used is incompatible with<EMAIL_ADDRESS>
This has nothing to do with ABI compatibility; nan really doesn’t care about that.

I assumed...
In file included from ../src/Canvas.h:22:0,
                 from ../src/Canvas.cc:7:
../../nan/nan.h:45:3: error: #error This version of node/NAN/v8 requires a C++11 compiler
In file included from ../src/Canvas.h:11:0,
                 from ../src/Canvas.cc:7:
/home/travis/.node-gyp/8.0.0/include/node/v8.h:316:1: error: expected unqualified-id before ‘using’
/home/travis/.node-gyp/8.0.0/include/node/v8.h:808:1: error: expected unqualified-id before ‘using’
/home/travis/.node-gyp/8.0.0/include/node/v8.h:6356:35: error: ‘virtual v8::EmbedderHeapTracer::~EmbedderHeapTracer()’ declared virtual cannot be defaulted in the class body
In file included from ../../nan/nan.h:192:0,
                 from ../src/Canvas.h:22,
                 from ../src/Canvas.cc:7:
../../nan/nan_maybe_43_inl.h:13:1: error: expected unqualified-id before ‘using’

@refack The interesting bits are #error This version of node/NAN/v8 requires a C++11 compiler – ABI- and API-wise nan should be fine with Node 8.

So it's not ABI stability but<EMAIL_ADDRESS>requiring a C++11 compiler

@refack The interesting bits are #error This version of node/NAN/v8 requires a C++11 compiler – ABI- and API-wise nan should be fine with Node 8.

Close enough 😉 ABI stability / compiler requirements...

<EMAIL_ADDRESS>requiring a C++11 compiler

We’ve been requiring that for ages, though (since at least Node 4, I think?)

@aeschylus The "expected unqualified-id before ‘using’" error means your compiler is too old (probably gcc < 4.8.5).  Nan and node-gyp should work with node.js 8, I tested it days before the release.

@aeschylus created a PR for you https://github.com/ProjectMirador/mirador/pull/1432
You need a special config for travis to use GCC 4.8

<EMAIL_ADDRESS>requiring a C++11 compiler
We’ve been requiring that for ages, though (since at least Node 4, I think?)

@addaleax It seems like this specific travis job until today (v8) was just sliding under the wire with:
GCC version
gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

LLVM version
clang version 3.4 (tags/RELEASE_34/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix

@addaleax It seems like this specific travis job until today (v8) was just sliding under the wire with:

The Travis job wouldn't be building Node itself, it'd be building a native module. So it's probably to do with one of the dependencies (and maybe how it uses V8 APIs).
If you're not building native modules you don't need gcc at all.

 Pinning to the LTS version solved the issue for now.


Fix minification typo

The word "magnification" is used here, but looks like it should really be "minification".

thats funny!

That's a new feature. When you're code is too compact and you're getting paid by the line ... break out JS code magnification! :-)


Make spatial features valid geojson

Status
READY
Description
Should type of sc.spatial feature be SPATIAL or FEATURE (valid geojson)?

👍


How does one remove grunt in a pre-existing sails app?

We don't want to use the sails grunt build process, but already have generated a default project.
error:
------------------------------------------------------------------------
grunt-cli: The grunt command line interface. (v0.1.13)

Fatal error: Unable to find local grunt.

If you're seeing this message, either a Gruntfile wasn't found or grunt
hasn't been installed locally to your project. For more information about
installing and configuring grunt, please see the Getting Started guide:

http://gruntjs.com/getting-started

------------------------------------------------------------------------

error: Looks like a Grunt error occurred--
error: Please fix it, then **restart Sails** to continue running tasks (e.g. watching for changes in assets)
error: Or if you're stuck, check out the troubleshooting tips below.

error: Troubleshooting tips:
error:
error:  *-> Are "grunt" and related grunt task modules installed locally?  Run `npm install` if you're not sure.
error:
error:  *-> You might have a malformed LESS, SASS, CoffeeScript file, etc.
error:
error:  *-> Or maybe you don't have permissions to access the `.tmp` directory?
error:      e.g., `/sailing/.tmp` ?
error:
error:      If you think this might be the case, try running:
error:      sudo chown -R 501 /sailing/.tmp

http://sailsjs.org/#!/documentation/concepts/Assets/DisablingGrunt.html


generate token fails but step status is not failing

I have the following step in my workflow
   - name: Generate a token
        id: generate-token
        uses: actions/create-github-app-token@v1
        with:
          github-api-url: "https://custom.gitenterprise.com/api/v3"
          app-id: ${{ vars.APP_ID }}
          private-key: ${{ secrets.APP_PRIVATE_KEY }}
          owner: ${{ github.repository_owner }}

The action fails but the step result is not failure

Error from the step
repositories not set, creating token for all repositories for given owner ""
Failed to create token for "" (attempt 1): 'Expiration time' claim ('exp') is too far in the future -<EMAIL_ADDRESS>The issue seems to be random as relaunching the job with debug enabled now it show the step as failed

##[debug]Evaluating condition for step: 'Generate a token'
##[debug]Evaluating: success()
##[debug]Evaluating success:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: Generate a token
##[debug]Register post job cleanup for action: actions/create-github-app-token@v1
##[debug]Loading inputs
##[debug]Evaluating: vars.APP_ID
##[debug]Evaluating Index:
##[debug]..Evaluating vars:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'APP_ID'
##[debug]=> '35'
##[debug]Result: '35'
##[debug]Evaluating: secrets.APP_PRIVATE_KEY
##[debug]Evaluating Index:
##[debug]..Evaluating secrets:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'APP_PRIVATE_KEY'
##[debug]=> '***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]***
##[debug]'
RequestError [HttpError]: 'Expiration time' claim ('exp') is too far in the future -<EMAIL_ADDRESS>    at /scratch/ghe-runners/1/_work/_actions/actions/create-github-app-token/v1/dist/main.cjs:30470:21
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async hook (/scratch/ghe-runners/1/_work/_actions/actions/create-github-app-token/v1/dist/main.cjs:12119:22)
    at async getTokenFromOwner (/scratch/ghe-runners/1/_work/_actions/actions/create-github-app-token/v1/dist/main.cjs:29956:20)
    at async RetryOperation._fn (/scratch/ghe-runners/1/_work/_actions/actions/create-github-app-token/v1/dist/main.cjs:29856:24) {
  status: 401,
  request: {
    method: 'GET',
    url: 'https://custom.gitenterprise.com/api/v3/orgs/XAE/installation',
    headers: {
      accept: 'application/vnd.github.v3+json',
      'user-agent': 'actions/create-github-app-token',
      authorization: 'bearer [REDACTED]'
    },
    request: { hook: [Function: bound hook] AsyncFunction }
  },
  response: {
    url: 'https://custom.gitenterprise.com/api/v3/orgs/XAE/installation',
    status: 401,
    headers: {
      'access-control-allow-origin': '*',
      'access-control-expose-headers': 'ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset',
      'content-length': '143',
      'content-security-policy': "default-src 'none'",
      'content-type': 'application/json; charset=utf-8',
      date: 'Thu, 28 Mar 2024 14:36:18 GMT',
      'referrer-policy': 'origin-when-cross-origin, strict-origin-when-cross-origin',
      server: 'GitHub.com',
      'strict-transport-security': 'max-age=31536000; includeSubdomains',
      'x-content-type-options': 'nosniff',
      'x-frame-options': 'deny',
      'x-github-enterprise-version': '3.8.12',
      'x-github-media-type': 'github.v3; format=json',
      'x-github-request-id': '3f6bbd2b-182c-4923-8446-19f93fff227f',
      'x-runtime-rack': '0.018151',
      'x-xss-protection': '0'
    },
    data: {
      message: "'Expiration time' claim ('exp') is too far in the future",
      documentation_url<EMAIL_ADDRESS>    }
  },
  attemptNumber: 4,
  retriesLeft: 0
}
Error: 'Expiration time' claim ('exp') is too far in the future -<EMAIL_ADDRESS>##[debug]Node Action run completed with exit code 1
##[debug]Finishing: Generate a token

confirmed without debug the error is printed twice and the step succeed

We implemented retries:
https://github.com/actions/create-github-app-token/blob/78e5f2ddc08efcb88fbbee6cfa3fed770ba550c3/lib/main.js#L79-L81
The messages that are logged out are info logs, they occur multiple times due to the multiple retries. The messages include a the "attempt" not. In the end it worked out, hence the successful step.
But I agree we can make this less confusing by making clear that this error occurred but that we are retrying and also log out when it succeeded.

hi
the issue here is that even if the step fails in getting a token the jobs continues as the step is marked as successful (the job fail later because there's no token)

if i enable the debug run instead the step is correctly marked as failed

the job fail later because there's no token

Okay in that case something is definitely broken 🤔 Can you reliably reproduce it? Or do you see the problem intermittently?


[WIP] docs: evm-machine design doc

Pull Request type
In this design document, we dive into a refactor of the Kakarot's EVM-Machine implementation, compatible with Cairo's limitations raised in https://github.com/starkware-libs/cairo/issues/4032.
The accepted proposed design will need to:

Be easily refactorable
Have a low overhead cost compared to the one originally planned
Not introduce development complexity in other parts of the code

I believe that the proposed one performs well in all the points mentioned above. Please discuss it extensively!

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[x] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Resolves: #
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

What are the limitations of this approach?

It's a bit more expensive as we need to track each stack/memory's context-related segment length in a dict instead of as a simple variable.
Also, this imposes a limit on the maximum amount of memory space a context can allocate.

What are the limitations of this approach?

It's a bit more expensive as we need to track each stack/memory's context-related segment length in a dict instead of as a simple variable.
Also, this imposes a limit on the maximum amount of memory space a context can allocate.

Let's discuss it in our weekly
What is the limit on memory space per context?

the gas costs required to have a memory containing
125000 words is above the 30M gas limit. We will use this heuristic to bound the
maximum size of the memory to 125000 256-bits words. Therefore, we will bound
the maximum size of the memory to 125000 256-bits words.

@Eikix If you're okay with it I propose to merge the current design proposal, and to apply any modifications from SW's feedback in a new PR

@Eikix Reworked this:

Changes brought to the ExecutionContext docs
The Storage section has been entirely reworked

@Eikix Changes applied

mb just noticed this PR does not have mentions of "dirtyStorage"?
is dirtyStorage the equivalent of local_changes?
should we modify the other pr https://github.com/kkrt-labs/kakarot-ssj/pull/360

dirtyStorage is a name that is unique to Geth. For us, it's the combination of local_changes and global_changes.


[Proposal] Blob Storage as State Store

Describe the proposal
Blob storage is currently supported as output bindings (S3, Azure etc.) however I can see scenarios when blob storage would be extremely useful for state stores as well.
First, considering the availability of tools, it's much easier to view blob storage compared to say Dynamo DB.
Second, blob storage is extremely cheap for low traffic scenarios. I'm not quite sure whether blob storage is actually cheaper for high traffic as well.
Blob storage is a key-value storage too - key is blob name, value is blob content. One can attach key-value metadata for a blob as well. Optimistic concurrency is supported via ETags (for instance in Azure Blob Storage).

@aloneguid - are you interested in adding Azure Blob Storage as a state store?

I'm interested to do if it is free to take.

@msfussell I'm happy for @ksivamuthu to do it, I'm not too active for a next month or so. Looking forward to contribute to some other component soon.

@ksivamuthu Can you please create docs as well ?

@ksivamuthu please follow this doc style when you create the howto.


Added basic documentation for get_followers and get_following

This documentation is still missing details on pagination but I want to make changes to the method itself before doing that.

I added a simple example for pagination, should be sufficient for now.

I added a simple example for pagination, should be sufficient for now.


delayed_job worker not working on jruby <IP_ADDRESS>

We are trying to use DeplayedJob with jruby <IP_ADDRESS> and are having this issue: https://github.com/jruby/jruby/issues/3338
We think it is a jruby issue but we put it here for reference.

It would be ActiveRecord or jruby as we don't do anything to change this method


vnstat statistics do not persist through reboot.

Though I saw this resolved in a previous PR but current version does not appear to persist vnStat history through a reboot.

Statistics (rrd) replaces vnStat since 0.99.8. vnStat may be removed next release. May replace with an updated fork that doesn't randomly corrupt database.


Etap 1 - Checklist do oceny

[x] text is in C#
[x] build succeeded
[x] all UT are green
[x] Data layer is clearly stated using language terms only (no database, no file)
[x] Data API is clearly stated
[x] Data API is abstract
[x] Logic layer is clearly stated using language terms only
[x] Logic API is clearly stated
[x] Logic uses only the abstract Data layer API
[x] Presentation layer is clearly stated using language terms only
[x] Presentation uses only the abstract Logic layer API
[x] MVVM and XAMLare applied to implement GUI
[x] reactive and interactive user interaction for user (operator) communication
[x] reactive and interactive programming is used for the communication of layers
[x] Presentation - object model representing process data
[x] Fulfill functional requirements of the task
[x] Unit Test - layers are tested independently using abstract API
[x] Dependency injection (additional framework is not required)
[x] Mock is used for testing purposes (expected but not required)

Zaliczone ;)


please send me the code of the task of stand in line

Challenge Stand in Line has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 UBrowser/5.7.16817.1002 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

function nextInLine(arr, item) {
  // Your code here
 testArr.push(item);
  var removed=testArr.shift();
  return removed;  // Change this line
}

// Test Setup
var testArr = [5,6,7,8,9];

// Display Code
console.log("Before: " + JSON.stringify(testArr));
console.log(nextInLine(testArr, 5)); // Modify this line to test
console.log("After: " + JSON.stringify(testArr));

@ajitkumarsahu Your code is incorrect, you should be using the array passed in to your function as an argument - arr instead of testArr.
Please visit the Help Room or the HelpJS Room if you need help with the challenge. Happy Coding!

@ajitkumarsahu Sincere requests to not report issues seeking code assistance on the issue tracker. Please proceed to the chat rooms as suggested by @Manish-Giri !
Thanks and happy coding!


Some way to tag trials with info based on randomization in stimulus handler function (data.write() would be ideal, addProperty() isn't good enough)

If I could get the behavior of data.addProperties() without it overwriting the data on every single trial object before and after it, that would be ideal.
Consider the following variable I have for my experiment's testing phase.
    timeline: [
        {
            type: 'html-keyboard-response',
            stimulus: function() {
              //jsPsych.data.write({fixation_cross_trial : true});
              jsPsych.data.addProperties({fixation_cross_trial : true});
              return '
+
'
            },
            choices: jsPsych.NO_KEYS,
            trial_duration: 2000,
        },
        {
            type: 'html-keyboard-response',
            stimulus: function(){
               var myArray = [true, false];
              var rand = myArray[Math.floor(Math.random() * myArray.length)];
              // jsPsych.data.write({trial_stimuli_path:jsPsych.timelineVariable('image_path', true)});
              // jsPsych.data.write({fixation_cross_trial : false});
              jsPsych.data.addProperties({trial_stimuli_path:jsPsych.timelineVariable('image_path', true)});
              jsPsych.data.addProperties({fixation_cross_trial : false});
              if (rand == true) {
                // write's to this ccurrent trial object
                //jsPsych.data.write({treatment_display : "left"});
                jsPsych.data.addProperties({treatment_display : "left"});
                return "

" + "
No Treatment
"
              } else {
                //jsPsych.data.write({treatment_display : "right"});
                jsPsych.data.addProperties({treatment_display : "right"});
                return "
No Treatment
" + "

"
                 }
              },
            choices: [37, 39], //37 -- keycode for left arrow, 39 -- keycode for right arrow
        }
    ],
    timeline_variables: test_tl_stimuli // an array of image paths
}

In this experiment, there is a fixation cross trial that executes first. Then there is the actual test_stimuli trial, where an image is displayed side by side with a string that says "No Effect". These are the two main stimuli I have throughout the experiment for each trial. For each trial, the appearance of either stimuli on the right or left is supposed to be random - this is critical to the "reaction time" dimension of our experiment.
In the code, I tried initially using jsPsych.data.write(), I didn't read that one part of the documentation discouraging you from using it. The intention was to make it so that each trial could hold a new key object pair from every jsPsych.data.write() call. As you can see, I'm the things I'm trying to write into the trial are dynamic and based on things that happen in the handler function I've created for my stimulus.

 This holds the timelineVariable() that is loaded for that particular trial, or the image path that I'm trying to access on each specific trial.
I have a write call to give a key/value pair, fixation_cross, which holds a boolean for whether or not the current trial is a fixation cross trial. Ultimately, I don't need the fixation cross trials.
I have a write call that's supposed to give a key/value pair, treatment_display, which is supposed to indicate whether or not the randomization within my stimulus function chooses to put the timeline variable image on the left or right (or, indicates the opposite side from which the "No Treatment" string appears.

In my jspsych.init() function, I was finding that executing jspsych.data.displaydata('json') looks strange if you use jsPsych.data.write(). It appears that a new dictionary object/JSON object is created every time you use jsPsych.data.write(), and this object has almost entirely identical fields to other trial json objects (but it does include the field that you tried to write).
So here's the output for what should be two trials, a fixation cross trial and then a test_stimuli trial. But as you can see, it makes 6 json objects.
{
		"fixation_cross_trial": true,
		"trial_type": "html-keyboard-response",
		"trial_index": 6,
		"time_elapsed": 3826,
		"internal_node_id": "0.0-6.0-0.0",
		"user_id": "6DLz56Gl",
		"condition": "Mood",
		"total_trials": 2
	},
	{
		"rt": null,
		"stimulus": "
+
",
		"key_press": null,
		"trial_type": "html-keyboard-response",
		"trial_index": 6,
		"time_elapsed": 5827,
		"internal_node_id": "0.0-6.0-0.0",
		"user_id": "6DLz56Gl",
		"condition": "Mood",
		"total_trials": 2
	},
	{
		"trial_stimuli_path": "/static/images/stimulus_img1.png",
		"trial_type": "html-keyboard-response",
		"trial_index": 7,
		"time_elapsed": 5828,
		"internal_node_id": "0.0-6.0-1.0",
		"user_id": "6DLz56Gl",
		"condition": "Mood",
		"total_trials": 2
	},
	{
		"fixation_cross_trial": false,
		"trial_type": "html-keyboard-response",
		"trial_index": 7,
		"time_elapsed": 5828,
		"internal_node_id": "0.0-6.0-1.0",
		"user_id": "6DLz56Gl",
		"condition": "Mood",
		"total_trials": 2
	},
	{
		"treatment_display": "right",
		"trial_type": "html-keyboard-response",
		"trial_index": 7,
		"time_elapsed": 5828,
		"internal_node_id": "0.0-6.0-1.0",
		"user_id": "6DLz56Gl",
		"condition": "Mood",
		"total_trials": 2
	},
	{
		"rt": 1539.229999994859,
		"stimulus": "
No Treatment

",
		"key_press": 37,
		"trial_type": "html-keyboard-response",
		"trial_index": 7,
		"time_elapsed": 7368,
		"internal_node_id": "0.0-6.0-1.0",
		"user_id": "6DLz56Gl",
		"condition": "Mood",
		"total_trials": 2
	},

If I use data.addproperties() instead, then while I get one json object to represent each fixation trial and each test trial... Each call to data.addproperties overwrites the previous data.addproperties() calls all the way through the end of the experiment.
Is there a way to work around the limitations of addProperty() so that I can get something similar to data.write() that doesn't cause this strange behavior in the data? I can imagine myself making a python script to parse the JSON file correctly when I use data.write() (this experiment is on a flask application), but that's a lot of trouble just to get what I originally intended to be trial-by-trial tags.

Does the data property for trial objects do what you need, or is there some feature that is missing from that? You can use functions as values for the data property.
You can also modify the data object after each trial in the on finish event for that trial.


"Bărbulești" is listed in the drop-down menu

Description:
"Bărbulești" is listed in the drop-down menu alongside its corresponding county according to the law
Precondition:
The website is up an running.

Step 1
Type "Bărbulești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Bărbulești, IALOMIȚA".


Deep Dive into Default and Static Methods in Interfaces  - BAEL-1326

Closing in lieu of #3281, which does not have the diff issue with the pom.xml


Assume UNKNOWN if No Status

This matches the behavior we have in here

****************************************************************

libgrpc.so

     VM SIZE                                                         FILE SIZE
 ++++++++++++++ GROWING                                           ++++++++++++++

 -------------- SHRINKING                                         --------------
  [ = ]       0 [None]                                                -56  -0.0%
  -0.4%     -32 src/core/ext/filters/client_channel/subchannel.cc     -32  -0.4%
      -7.2%     -30 recv_trailing_metadata_ready                          -30  -7.2%
      -0.7%      -2 [Unmapped]                                             -2  -0.7%

  -0.0%     -32 TOTAL                                                 -88  -0.0%

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,965,218      Total (<)      1,965,242

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,909,023      Total (<)     10,909,025

 No significant differences in binary sizes

[microbenchmarks] No significant performance differences


Fix small journal issues

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2768/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2770/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2773/
Test PASSed.

@aaudiber PTAL

alluxio-bot, merge this please


Click-Up Internal Pilot

Hey team! Please add your planning poker estimate with ZenHub @brick-green-agile6 @sarahnw

Looks like we might get access to smartsheets after all.

Dreams DO come true! @anshulkumar-usds

we're using smartsheets, so closing this.


fix: refactor

:tada: This PR is included in version 1.17.13 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat: support TypeScript v5

There was a breaking change in the plugin interface. Code is refactored to support both v4 and v5. I've only tested v5.5.3 here, but the refactor is heavily borrowed from https://github.com/mrmckeb/typescript-plugin-css-modules
Closes #1

(different account but same person as @spetrac)
It was a bit tricky to test, because the dist folder will only be generated on build and rm was not working for me on windows, but I cloned the complete PR, replaced rm with rimraf and build it myself. All in all, it definitely works! If the package is published accordingly with the generated dist folder, this should fix #1. 👍
In addition with the yaml-loader webpack plugin, I got a working import for my current setup that generates the types dynamically and imports the files correctly in the final build.
Next step could be to combine both plugins, but for this the yaml dependency should be aligned to use the same package for both. Also features like imports or custom syntax as in js-yaml or multi-yaml-loader could be nice.

I was also gonna use it for INTL xD