feat: Update README.md, add beelzebub honeypot project

Hey, thanks for this awesome list :)
Beelzebub is an advanced honeypot framework designed to provide a highly secure environment for detecting and analyzing cyber attacks. It offers a low code approach for easy implementation and utilizes virtualization techniques powered by GPT-3.

Thank you for your contribute. Beelzebub is a really fantastic tool, so I have added it into the awesome gpt list before. You can find it here.
https://github.com/cckuailong/awesome-gpt-security#investigation
I'll be great if you want to add some introduction about the creative tool.


odb/lefout: fix segfault on no layer for insertObstruction()

fixes #3649
it is tricky to run deltaDebug.py on segfaults, so I wasn't able to provide an example.
Shot in the dark to fix the segfault... I can run make generate_abstract on the testcase I couldn't share.

It will fix the crash but I'm uncertain if you are losing an obstruction that should be in the abstract.  If you look at the rect with no layer, can you see where it is coming from?

Replaced by #3657


Overline, linethrough and superscript text

I would like to underline, overline, linethrough and superscript text.
I there any possibility to do this?
Thank you.

Underline is already supported.
Strike (and maybe overline) is something you can achieve using custom annotations, have a look to the wiki on that.
I have never dealt with sub- or superscript yet. How would you do that manually?

Ok, I will try to implement Strike and overline soon with custom annotations. I let you know as soon as I have tried.
superscript, I know a software where I can set a boolean to true(button) and the paragraph is after a superscript. But I really not sure how we can implement this. But it will be nice to have something similar.

Fixed in 1.0.0. See https://github.com/ralfstuckert/pdfbox-layout/wiki/Markup


refactor generator

gen: move assertion sorter to a function so it could be reused
bool_compare: use variables in generator
bool_compare: use predicting order for tests
bool_compare: refactor tests
compares: use variables in generator
compares: use a predictive order for tests

These commits were part of #107 and #111 that were suggested changes were discarded, but the refactoring made in each PR could be kept as discussed here

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
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 93.611%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2110

Relevant Lines:
2254

💛  - Coveralls

This PR uses commits available in:

#116 created for #106
#111 created for #110

@Antonboom do you think we could merge this one, it would help me to refactor for

#94

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
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 93.611%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2110

Relevant Lines:
2254

💛  - Coveralls

I pushed too fast sorry.
I will fix other too

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
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 93.611%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2110

Relevant Lines:
2254

💛  - Coveralls

I resolved all your comments @Antonboom please check and review.
The number of changes is then very limited

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
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 93.611%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2110

Relevant Lines:
2254

💛  - Coveralls


MCO Monitoring run's indefinitely

on some case's, the MCO is restarted before the loop find's that the API is down
need to improve this check by checking if the update is already completed and give it a timeout.
# shared-utils/wait_for_sno_mco.sh

while [ ${retry} != 0 ]; do
    oc --kubeconfig=${KUBECONFIG} get nodes &>/dev/null
    if [[ $? == 0 ]]; then
        echo "$(tput setab 7)$(tput setaf 4)[ZTPFW - Monitoring MCO - SNO]$(tput sgr 0) >>>> API is up...waiting until mco will restart the node"
        sleep 10
        retry=$((retry + 1))
    else
        echo "$(tput setab 7)$(tput setaf 4)[ZTPFW - Monitoring MCO - SNO]$(tput sgr 0) >>>> API is down...The Cluster is restarting"
        retry=0
    fi
done

The script works fine...
The problem will appears only if you re-run the pipeline (due to a failure in the pipe steps) without stop the script for any reason...
in this case, the script should be stopped and re-launched again.
With the happy path is working fine...
Is it worth fixing in this case?

after talking with @eifrach we will add a previous timeout just to ensure at the end of the first loop api is not from another re-run


HAWQ-759. Fix query cannot be terminated by pg_cancel_backend or pg_t…

Please review, Thanks!

LGTM. +1.

+1

+1


Fix README.md text

Description
Update README.md text fixing a mismatched operator name.
slurmctld operator should be slurmd operator on https://github.com/omnivector-solutions/slurmd-operator#features
How was the code tested?
No test is needed.
Checklist

[x] I am the author of these changes, or I have the rights to submit them.
[x] I have added the relevant changes to the README and/or documentation.
[x] I have self reviewed my own code.
[ ] All requested changes and/or review comments have been resolved.

Good catch! Thank you for correcting this.


Latest Version of Nifi

Is it possible to get this upgraded to the latest version of Nifi? 1.25 is the stable version at the moment.

Can you please update to the latest version of nifi. As there are many changes in 2.0 so, we can use Python to customize any processor.
Thanks in advance!


Condition variables

Zephyr kernel APIs that cover:
pthread_cond_wait
pthread_cond_timedwait
pthread_cond_signal
pthread_cond_broadcast

Draft API for condition variables...
/**
 * @brief Initialize a condition variable
 *
 * @param condvar pointer to a @p k_condvar structure
 * @retval 0 Condition variable created successfully
 */
__syscall int k_condvar_init(struct k_condvar *condvar);

/**
 * @brief Signals one thread that is pending on the condition variable
 *
 *
 * @param condvar pointer to a @p k_condvar structure
 * @retval 0 On success
 */
__syscall int k_condvar_signal(struct k_condvar *condvar);

/**
 * @brief Broadcast to all threads that are pending on the condition variable
 *
 * @param condvar pointer to a @p k_condvar structure
 * @retval 0 On success
 */
__syscall int k_condvar_broadcast(struct k_condvar *condvar);

/**
 * @brief Waits on the condition variable releasing the mutex lock
 *
 * Automically releases the currently owned mutex, blocks the current thread
 * waiting on the condition variable specified by @a condvar,
 * and finally acquires the mutex again.
 *
 * The waiting thread unblocks only after another thread calls k_condvar_signal, or
 * k_condvar_broadcast with the same condition variable.
 *
 * @param condvar pointer to a @p k_condvar structure
 * @param mutex Address of the mutex.
 * @param timeout Waiting period for the condition variable in ms
 *                or one of the special values K_NO_WAIT and K_FOREVER.
 * @return
 */
__syscall int k_condvar_wait(struct k_condvar *condvar, struct k_mutex *mutex,
			     k_timeout_t timeout);

/**
 * @brief Statically define and initialize a condition variable.
 *
 * The condition variable can be accessed outside the module where it is defined using:
 *
 * @code extern struct k_condvar <name>; @endcode
 *
 * @param name Name of the condition variable.
 */
#define K_CONDVAR_DEFINE(name)                                                 \
	Z_STRUCT_SECTION_ITERABLE(k_condvar, name) =                           \
		Z_CONDVAR_INITIALIZER(name);


Get Thingiverse application approved

Needed to scale OAuth2 flow beyond 10 users.

Application details filled out and submitted, waiting for approval.

Have you gotten any sort of response from Thingiverse yet?

Nope. I've tried their official support form, Twitter and even Reddit to get into contact, but nothing. Their whole service is crappy. Also there appears to be another breaking change in the API again that I'll investigate later this week. Maybe we should drop support for them completely?

Honestly it's looking like that may be the way to go. I am probably going to migrate my own things from there to MyMiniFactory too. Even their android app has been broken for too long...

Unlikely that this will ever happen. A PR is made to remove Thingiverse from the new sign-in flow and keep the old legacy flow working for it (until we completely remove Thingiverse support in the future maybe). Closing for now so we can prep the next release (hopefully together with the next Cura beta).


copy a TStyledToolButton from a TStyledToolbar on a Tpanel

When i copy a TStyledToolButton from a TStyledToolbar on a Tpanel does not copy the Stylefamily, style class, etc. I have to set them manually after copy.

You can copy and place a StyledToolButton directly on a Form or Panel, but it's a bug... It's a miracle that a StyledToolButton works outside a StyledToolbar. Use a StyledButton instead if you need a button outside a Toolbar.


Disable left scrolling

I'm trying to disable left direction scroll. I couldn't find any solution with UIPageViewController. any suggestions?

Not sure what your use-case is but you could probably open the ImageViewer on the first item then when the user swipes to the second item remove the first item in the landedPageAtIndexCompletion block. Would that work for you?

Closing due to inactivity.


Update dev-runtime to export a patched stylex

Today, the the @stylexjs/dev-runtime package exports a single inject function that monkey-patches the @stylexjs/stylex package to be able to work at runtime.
Update the package so that it can be used instead of the @stylexjs/stylex package.
It should be possible to import the entire StyleX API from @stylexjs/dev-runtime.
One Open Question
It is possible to change some configuration settings for StyleX. What is the best way to handle this configuration in the dev runtime? There are two possible options here:
Export an extra function called configure that lets you define the settings and then it can be developer's responsibility to make sure that configure is called before any other StyleX API is used.
OR...
We could make configure return the entire StyleX API, and the developer is then expected to define a single file with a configuration and then use the API from that file in the rest of the codebase.
If we can enable the first path, that would be preferable as it would be easy to find-replace the package name once the build steps are set up.

Could the babel plugin be configured to set what the runtime is by rewriting the import? Then there's no need for another config?

The babel plugin can already be configured to inject function calls that inject styles at runtime. It automatically insert an import for the function that injects styles at runtime that is otherwise not part of the @stylexjs/stylex runtime.
So if you're using Babel, you don't need to use dev-runtime.

The only value of the dev-runtime is the ability to use StyleX without setting up any build steps or code transformations. It happens to re-use most of the code from the shared package or it wouldn't be worth maintaining at all.

@nmn Can you assign this to me? I want to take have a look at this.

Fixed in #746


Script annotations output

Pull Request Checklist

[x] Fixes #740
[x] Tests added
[x] Documentation/examples added
[x] Good commit messages and/or PR title

This PR implements the output annotation behaviour described in #740. The case with output params in the function signature as Path is not tested and this can be done with #652.
def func(..., output_param: Annotated[Path, Parameter(output=True, global_name="...", name="")]) -> Annotated[arbitrary_pydantic_type, OutputItem]:
    output_param.write_text("...")
    return output

@dejamiko you don't need to call _get_class_defaults, the hera mixin automatically handles it. See https://github.com/argoproj-labs/hera/blob/49140d07990cca8f2a22b72f1cf08aea8c225ca5/src/hera/shared/_global_config.py#L157


Changing file_size value in Django admin interface is not working.

Hello,
Changing the file_size value in the Django admin interface is not working when the value is 0 or less. While the page says that the value has been updated, going back into the objects page shows the original value instead of the updated one.
I checked the value in the database to make sure it's not just a graphical bug, but the value is unchanged there too.
It seems to only be a problem when the value is 0 or lower (it gets changed back to the original value).
Changing the value to something else higher than 0 works well, but putting 0 or less will change it back to the original value instead of the previous positive value.

What is the goal of manually changing the file_size using Django admin interface?
Shouldn't the file size always reflect the size of the file? I may be missing something here.

The goal is limited, I found this problem after trying to apply the Simple Test of #1465
This is definitely not an important problem to fix, but I thought it would be interesting to at least have it documented, in case we might need to change the file_size manually in the future for some other reason.

Maybe we can close this issue.
I found that I can set values < 0

But for some reason when you set value to 0, it goes back to these values

I close this issue. @ObadaS feel free to re-open it if you think it is relevant.


Add adaptive wait_sleep support

This change is

Coverage decreased (-0.5%) to 58.97% when pulling 19ef4956a1b4f9ebbf49225abdca5eb659cbb9ff on VDigitall:use_requests into 33fcda55f4e199d8eeac3143a457ca06b289350e on openprocurement:use_requests.


Enable jest-matchers in browser context by splitting utils

Summary
Jest testing is limited to execution in a node JS context currently. Since it's javascript, it's useful to run it in a real browser context at times, or at east run portions of it.
My use case is for running tests in react storybook with the specs addon. My setup mocks storybook-addon-specifications with jest's describe and it implementations when running via the cli, but currently has to use an entirely separate expect package for the actual assertions. This is problematic because the other expect implementation varies slightly from jest's and because it adds functionally duplicate dependencies to the project.
This PR adds a small amount of jest's functionality to the browser by decoupling jest-matcher from node. No new code was added, I just split out the messages and regex utilities from the jest-utils package.
Test plan
Tested using yarn link locally. (+yarn test)
Code change (from a working storybook/spec setup):
diff --git a/stories/components/buttons.spec.js b/stories/components/buttons.spec.js
index ad180f7..613fb5e 100644
--- a/stories/components/buttons.spec.js
+++ b/stories/components/buttons.spec.js
@@ -1,7 +1,7 @@
 import React from 'react';
 import { withKnobs } from '@kadira/storybook-addon-knobs';
 import { mount } from 'enzyme';
-import expect from 'expect';
+import expect from 'jest-matchers';

 import {
     storiesOf,
@@ -36,6 +36,9 @@ storiesOf('Button', module)
     const story = <PrimaryButton onClick={onClick}>Primary Button</PrimaryButton>;

     specs(() => describe('Primary Button', () => {
+        it('fails', () => {
+            expect(true).toBe(false);
+        });
         it('has a label', () => {
             const output = mount(story);
             expect(output.text()).toBe('Primary Button');

Browser console output:

Storybook UI:

Open questions
It's arguable that this should be part of a major release, since external packages dependent on jest-utils could break.

I like this!

I don't currently have enough time to review this PR specifically but this is definitely something I want and we should make it happen before publishing Jest 19.

cc @mjackson @vjeux when we ship Jest 19, we should be able to rename jest-matchers to expect now!

Thanks for the heads up, @cpojer. I probably won't be able to take a look until next week. Is that OK?

I agree this would be very useful. It's painful to use a slightly compatible "expect" implementation.


[Testing, Tooling] feat: implement in-memory networks

Summary
Human Summary
Adds implementations for the InMemoryCosmosNetwork interface from #289:

BaseInMemoryCosmosNetwork
"Abstract" implementation intended to be embedded in "concrete" implementations. It implements the following interface members:

#GetClientCtx()
#GetNetworkConfig()
#GetNetwork()

Additionally, it includes the following convenience methods:

#InitializeDefaults()
#GetLastAccountSequenceNumber()
#NextAccountSequenceNumber()

inMemoryNetworkWithSessions()
Implementation where #Start() creates InMemoryNetworkConfig#NumSuppliers number of genesis suppliers and #NumSuppliers * #AppToSupplierRatio number  of applications where #AppToSupplierRatio number of applications will match one service with each supplier (in distinct pairings). It also creates corresponding on-chain accounts (auth module) for each genesis actor. It exposes #CreateClaims() and #CreateProofs() methods for each session * InMemoryNetworkConfig#NumSession number of session.

inMemoryNetworkWithGateways()
Implementation where #Start() creates InMemoryNetworkConfig#NumApplications and #NumGateways number of genesis applications and gateways, respectively. It also creates corresponding on-chain accounts (auth module) for each genesis actor.

Issue

#141
#263
#264
#265
#289
:point_right: THIS PR :point_left:
#285
#266
#250

Type of change
Select one or more:

[ ] New feature, functionality or library
[ ] Bug fix
[ ] Code health or cleanup
[ ] Documentation
[ ] Other (specify)

Testing

[ ] Run all unit tests: make go_develop_and_test
[ ] Run E2E tests locally: make test_e2e
[ ] Run E2E tests on DevNet: Add the devnet-test-e2e label to the PR. This is VERY expensive, only do it after all the reviews are complete.

Sanity Checklist

[ ] I have tested my changes using the available tooling
[x] I have performed a self-review of my own code
[ ] I have commented my code, updated documentation and left TODOs throughout the codebase

@bryanchriswhite Didn't let me leave a comment: looks good nice cleanup of different pieces. Only question that stands out to me is there something you've found related to subscribing to events on these in-memory networks? I couldn't find much when doing the delegation client integration test but you have a lot of context rn it seems

@h5law Just posting here for posterity, but let's leave this until after the v0.50 migration.
We may be leverage some of the newer patterns (example) as we integrate it with our specific business logic.
Also spoke about it with @bryanchriswhite as well

@h5law Just posting here for posterity, but let's leave this until after the v0.50 migration.
We may be leverage some of the newer patterns (example) as we integrate it with our specific business logic.
Also spoke about it with @bryanchriswhite as well

@Olshansk I would definitely hold off on #307 but I think we can push this through as reviewers are able to allocate bandwidth to it.

Discussed offline with @bryanchriswhite. Holding off on this until after the migration

Closing, superseded by #412 & #417.


Snyk high vulnerability

Prototype Pollution [High Severity] in<EMAIL_ADDRESS><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>

Should be fixed


Keep only non-dev packages in repo

It makes releases much smaller.

This is an interesting piece of change in the lock file.
I've simply issued composer update --no-dev (Composer v2)

This is an interesting piece of change in the lock file.
I've simply issued composer update --no-dev (Composer v2)

Just a quick note: The composer post install script has not been executed in this pull request, which leads to a couple of namespaces not being properly prefixed in vendor/symfony/var-dumper/Cloner/AbstractCloner.php.

Just a quick note: The composer post install script has not been executed in this pull request, which leads to a couple of namespaces not being properly prefixed in vendor/symfony/var-dumper/Cloner/AbstractCloner.php.

Thank you.
rm -rf vendor/ && composer install gives me
Generated optimized autoload files containing 1466 classes
> sed -i '' 's/'\''Symfony/'\''Spatie\\WordPressRay\\Symfony/g' ./vendor/symfony/var-dumper/Cloner/AbstractCloner.php
sed: can't read s/'Symfony/'Spatie\\WordPressRay\\Symfony/g: No such file or directory
Script sed -i '' 's/'\''Symfony/'\''Spatie\\WordPressRay\\Symfony/g' ./vendor/symfony/var-dumper/Cloner/AbstractCloner.php handling the post-install-cmd event returned with error code 2

Thank you.
rm -rf vendor/ && composer install gives me
Generated optimized autoload files containing 1466 classes
> sed -i '' 's/'\''Symfony/'\''Spatie\\WordPressRay\\Symfony/g' ./vendor/symfony/var-dumper/Cloner/AbstractCloner.php
sed: can't read s/'Symfony/'Spatie\\WordPressRay\\Symfony/g: No such file or directory
Script sed -i '' 's/'\''Symfony/'\''Spatie\\WordPressRay\\Symfony/g' ./vendor/symfony/var-dumper/Cloner/AbstractCloner.php handling the post-install-cmd event returned with error code 2

I'll merge this in, and run composer again for to get the lowest version of dips

I'll merge this in, and run composer again for to get the lowest version of dips

@szepeviktor @jeffreyvr I've prepared v1.2.1 on the master branch. It has not been released yet.
Could you both check if the current master is ok?
If followed these steps to prepare it: https://github.com/spatie/wordpress-ray#release-instructions-for-maintainers

@szepeviktor @jeffreyvr I've prepared v1.2.1 on the master branch. It has not been released yet.
Could you both check if the current master is ok?
If followed these steps to prepare it: https://github.com/spatie/wordpress-ray#release-instructions-for-maintainers

Did a quick test, everything seems to be working.

Did a quick test, everything seems to be working.


Issue/7498 documentation menu collapses

Description
Fix bug where clicking a sub-element from the Inmanta Lifecycle Service Manager menu would collapse the whole menu.
Fix similar behavior for the iso-only pages of the Administrator Documentation section (Operational Procedures With LSM and Support Procedure)
Bug was caused because we were using the .. only:: ... directive to control structure (which sections to include) whereas it should only be used for including/excluding content within a fixed structure.
Use the exclude_patterns functionality of the conf.py file instead.
Behavior on iso:

check that clicking items no longer collapses the menu
check that previous page / next page links work as intended. i.e. from the Platform Developers Guide page, the next page should be Inmanta Lifecycle Service Manager

Screencast from 30-05-2024 10:46:12.webm
Behavior on oss:

check that the Inmanta Lifecycle Service Manager page is not present in the menu
and that it is not accessible either via next page links. i.e. from the Platform Developers Guide page, the next page should be Administrator documentation
also check it is not accessible via entering url directly e.g. by navigating to http://<IP_ADDRESS>:8000/lsm

Screencast from 30-05-2024 10:43:29.webm
The current approach generates the following warnings when building oss:
WARNING: toctree contains reference to excluded document 'administrators/operational_procedures_with_lsm'
WARNING: toctree contains reference to excluded document 'administrators/support'
WARNING: toctree contains reference to nonexisting document 'lsm/index'

I'm not sure what to do with these warnings, either accept them or suppress them via conf.py e.g.:
EDIT: After discussion I think it's fine to leave these warnings as they are.

if tags.has("oss"):
    # Suppress warnings when building oss docs because some toc trees
    # reference files that we explicitely exclude (e.g. administrators/support.rst)
    suppress_warnings = ["toc.excluded", "toc.not_readable"]

closes https://github.com/inmanta/inmanta-core/issues/7498
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
- [ ] Type annotations are present
- [ ] Code is clear and sufficiently documented
- [ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
- [ ] Correct, in line with design
- [ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
- [ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Failed to merge changes into iso6 due to merge conflict. Please open a pull request for these branches separately by cherry-picking the commit that was made on the branch master (git cherry-pick f164a1ab8177e99f5ee5492da0a6a0382e85752a).

Merged into branches master in f164a1ab8177e99f5ee5492da0a6a0382e85752a

Not closing this pull request due to previously commented issues for some of the destination branches. Please open a separate pull request for those branches by cherry-picking the relevant commit. You can safely close this pull request and delete the source branch.

This branch was not deleted as it seems to still be in use.

Processing #7698.


Prevent TracingDriver registration when not in use

Pull request #70 caused issues since the driver will be registered and never de-register itself when not in use due to static references from JdbcTracingUtils

Pull Request Test Coverage Report for Build 343

8 of 10 (80.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.003%) to 50.686%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/io/opentracing/contrib/jdbc/JdbcTracing.java
4
5
80.0%

src/main/java/io/opentracing/contrib/jdbc/TracingDriver.java
1
2
50.0%

Totals

Change from base Build 342:
-0.003%

Covered Lines:
517

Relevant Lines:
1020

💛  - Coveralls

@asvanberg you moved static boolean traceEnabled from TracingDriver class to JdbcTracing class;
could you clarify how moving static variable solved the issue?

When any of the tracing wrappers (TracingConnection, TracingPreparedStatement, and so on) create a span they call JdbcTracingUtils#call which has a static reference to TracingDriver to check if tracing is enabled or not. This will cause the class to be loaded by the JVM and the static initializer to be run (TracingDriver:49) which will register itself with the DriverManager. If the tracing driver is not in use due to using TracingDataSource and another driver it will not be deregistered.
For example when undeploying an application in Tomcat the following warning is generated
WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ROOT] registered the JDBC driver [io.opentracing.contrib.jdbc.TracingDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
PS. I'm also wondering why this check is even there since you have to explicitly enable tracing, why should there be a flag to turn it back off again?


Raycasting world mouse position on a ground plane in orthographic (isometric) mode

Hey again.
I have been having fun experimenting with Pixi3D.
I succeeded in getting the world mouse position of a 3d ground plane with this code:
		var normal = new PIXI3D.Vec3.fromValues(0, 1, 0)
		var plane = new PIXI3D.Plane(normal, 0.01)
		var ray = PIXI3D.Camera.main.screenToRay(MouseX, MouseY)
		var raycast = plane.rayCast(ray);
		var point = ray.getPoint(raycast)

But it doesn't seem to work in orthographic mode. Only in perspective.
Is there anything I have to change for it to work in orthographic mode?
Please let me know if you need a working example or more code.
Thanks!

I have to check and see why this wouldn't work with orthographic camera.

Thank you jnsmalm! I made a playground example in case it helps:
https://www.pixiplayground.com/#/edit/j0rijRVXRBPItApj_DyqI
I did some research and it seems like this might be a common problem raycasting an orthographic camera.
https://stackoverflow.com/questions/18553209/orthographic-camera-and-selecting-objects-with-raycast
Any idea how I might adapt that solution to my code?

Think I found a solution for it, seems like has to be done just a tiny bit different for orthographic camera. Use this function instead, I will also fix this in the lib.
function screenToRay(x, y) {
  let screen = PIXI3D.Camera.main.screenToWorld(x, y, 1);
  if (screen) {
    return new PIXI3D.Ray(screen.array, PIXI3D.Camera.main.worldTransform.forward);
  }
}

Brilliant. Thank you again jnsmalm! It works very nicely now.
var ray = PIXI3D.Camera.main.orthographic ? screenToRay(MouseX, MouseY) : PIXI3D.Camera.main.screenToRay(MouseX, Mouse)
Using this hack for the moment :)


Send pet to a friend who also has the extension installed

Awesome app!
I was wondering if it's possible to add this feature in the future - connect with friends who also use the extension and send them your pet or they send theirs temporarily. Like when you are bored and want to check on them or when you need their help with something.

Hmm. I like this idea. It would work well for pair programming, if your pets would hang out together 🤔

Does this sound okay? I have thought of a import and export pet command.

The export pet command exports a text file with the Type of Pet, The Colour and The Name of The Pet.
The import pet command reads the file, which you can send to a friend for pair programming, and then loads the pet into the pet panel.

This means you can share files to show your pet setup, which is essentially pair programming.


[docs] Add missing words in translations

[x] I have followed (at least) the PR section of the contributing guide.

@mersad998 the docs translation is not maintained for now. It evolves too fast for the community to maintain it, so we removed it, hoping to find a way to avoid having 50% Portuguese and 50% English mixed in a page.
Did you see some Portuguese translation in the docs?

Note that the values changed here would get lost in the next sync with translate.mui.com.


[BugFix] Fix replay TransactionState log error (#27383) (backport #27390)

[FE PR Coverage Check]
:disappointed: fail : 2 / 6 (33.33%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/transaction/OlapTableTxnLogApplier.java
2
6
33.33%
[149, 150, 151, 152]


gperftools cpu profiler coroutine process cause segmentation fault

gperftools cpu profiler coroutine process cause segmentation fault, does cpu profiler conflict with  coroutine implemented with  assembly instruction?

Not sure about "conflict". Thing is in order to profile we capture stack traces from signal handler. We have 2 ways:
a) using frame pointer register
b) using libunwind (which uses dwarf-like CFI data that was originally introduced to handle exceptions).
In (b) case your asm needs to have correct CFI annotation so that stack trace capturing works. Easiest way to test is single-step your asm in gdb and try 'bt' on each step and ensure you still have good one.
Coroutine-wise I actually have code with right CFI stuff here: https://github.com/alk/swapcontext_light/blob/master/swapcontext_light.S
In (a) case your asm needs to ensure that frame pointer register (i.e. rbp on x86-64) is correct at any instruction.
Alternative is blocking SIGPROF during switch. So that profiler will not try to "unwind" when cpu is inside your code.
Closing the "ticket" for now. Feel free to reopen if you think there is anything to fix in gperftools.


[Bug] Instrument system event for loading (PNG) images  (can be different to files)

Already working due to RandomAccessFile.open(String, int)


steppers form sent empty payload

Bug, feature request, or proposal:
hello i was following this guide... steppers using-a-different-form-for-each-step and when i try to send a post request... i got empty payloads
What is the expected behavior?
i would want to be able to have data posted.
What is the current behavior?
i got empty payloads

What are the steps to reproduce?
enrollment.component.ts
 ..... some import code ....
@Component({
  selector: 'app-enrollment',
  templateUrl: './enrollment.component.html',
  styleUrls: ['./enrollment.component.scss'],
  animations : fuseAnimations
})

export class EnrollmentComponent implements OnInit
{
    enrollment = new Enrollment();
    displayData=false;

    // Horizontal Stepper
    horizontalStepperStep1: FormGroup;
    horizontalStepperStep2: FormGroup;
    horizontalStepperStep3: FormGroup;
    horizontalStepperStep1Errors: any;
    horizontalStepperStep2Errors: any;
    horizontalStepperStep3Errors: any;

    constructor(
        private fuseConfig: FuseConfigService,
        private enrservice: EnrollmentService,
        private formBuilder: FormBuilder,
        public snackBar: MatSnackBar,
    )
    {
        this.fuseConfig.setSettings({
            layout: {
                navigation: 'none',
                toolbar   : 'none',
                footer    : 'none'
            }
        });

        // Horizontal Stepper form error
        this.horizontalStepperStep1Errors = {
          firstName: {},
          lastName : {}
        };

        this.horizontalStepperStep2Errors = {
            address: {}
        };

        this.horizontalStepperStep3Errors = {
            city      : {},
            state     : {},
            postalCode: {}
        };
    }

    ngOnInit()
    {
        // Horizontal Stepper form steps
        this.horizontalStepperStep1 = this.formBuilder.group({
          firstName: ['', Validators.required],
          lastName : ['', Validators.required]
        });

        this.horizontalStepperStep2 = this.formBuilder.group({
            address: ['', Validators.required]
        });

        this.horizontalStepperStep3 = this.formBuilder.group({
            city      : ['', Validators.required],
            state     : ['', Validators.required],
            postalCode: ['', [Validators.required, Validators.maxLength(5)]]
        });

        this.horizontalStepperStep1.valueChanges.subscribe(() => {
            this.onFormValuesChanged();
        });

        this.horizontalStepperStep2.valueChanges.subscribe(() => {
            this.onFormValuesChanged();
        });

        this.horizontalStepperStep3.valueChanges.subscribe(() => {
            this.onFormValuesChanged();
        });
    }

    onFormValuesChanged()
    {
       ...
    }

    get diagnostic() { return JSON.stringify(this.enrollment) }

    finishHorizontalStepper()
    {
         console.log('Values = ', this.horizontalStepperStep1.value, this.horizontalStepperStep2.value, this.horizontalStepperStep3.value);
        this.enrservice.finishHorizontalStepper(this.enrollment)
            .subscribe((enrollment: Enrollment) => {
                    // Show the success message
                    this.snackBar.open('Enrollment success', 'OK', {
                        verticalPosition: 'top',
                        duration        : 6000
                    });

                    // Change the location with new one
                    /* this.router.navigateByUrl('enrollment/'); */
                });
    }
}

enrollment.service.ts
 .... some import code ....

const API_URL = environment.apiServer;
const httpOption = {
    headers: new HttpHeaders({ 'Content-Type': 'application/json; charset=utf-8' })
};

@Injectable()
export class EnrollmentService
{
    enrollment: any;

    constructor(private http: HttpClient)
    {
    }

    /**
     * Create New Chat
     * @param contactId
     * @returns {Promise<any>}
     */
    finishHorizontalStepper(enrollment: Enrollment): Observable<Enrollment>
    {
        return this.http.post<Enrollment>(API_URL, JSON.stringify(enrollment))
    }

}

Which versions of Angular, Material, OS, TypeScript, browsers are affected?
"@angular/cdk": "5.2.2",
"@angular/common": "5.2.6",
"@angular/compiler": "5.2.6",
"@angular/core": "5.2.6",
"@angular/flex-layout": "2.0.0-beta.12",
"@angular/forms": "5.2.6",
"@angular/http": "5.2.6",
"@angular/material": "5.2.2",
"@angular/material-moment-adapter": "5.2.2",
Is there anything else we should know?

Please keep GitHub issues for bug reports / feature requests. Better avenues for troubleshooting / questions are stack overflow, gitter, mailing list, etc.


the function name "isStatefulSetReady" is confusing

https://github.com/Orange-OpenSource/cassandra-k8s-operator/blob/b29202cb98191a7af01f703273a90a5e089b8b07/pkg/controller/cassandracluster/statefulset.go#L256
This function name “ isStatefulSetReady” is confusing.
According to my understanding, he should be "isStatefulSetUnReady".

Hi @mackwong you're right :) thanks!


Expand default project area and project area shapefile size limits in Tasking Manager

What's your idea for a cool feature that would help you use OHM better.
We should expand the default size limits for Tasking Manager for project area (5000 km^2) and project area shapefile (1MB) to 15000 km^2 and 3MB respectively.
Current workarounds
Breaking an area down into multiple projects, which is tougher to manage.
Additional Info
From Slack, @willemarcel pointed out these env variables are configurable here:
(https://github.com/OpenHistoricalMap/tasking-manager/blob/staging/example.env#L179-L182)
& that this can be set by passing an ENV VAR.
see: https://greeninfo.slack.com/archives/CACTQ7MU4/p1663789148763929

I have created the PR for osm-seed https://github.com/developmentseed/osm-seed/pull/270 that will incluude the new env vars

@jeffreyameyer , I've just updated the ENV VAR  for TM, Could you try uploading the file. ?

@Rub21 - I tried, but it doesn't appear to be working... YET! :)

@willemarcel , I have increased 3 times the default values, https://github.com/OpenHistoricalMap/ohm-deploy/blob/main/values.production.template.yaml#L481, but seend that not working.

@jeffreyameyer @Rub21 could you make my user (wille) an admin or organization manager? So I can check it.

@willemarcel I just promoted your username to Manager

@Rub21 I know what is the problem. The ohm-deploy takes care only of the TM backend and those settings are needed by the frontend. I believe you need to modify it in this file: https://github.com/OpenHistoricalMap/tasking-manager/blob/staging/.github/workflows/production.yml

@willemarcel  , I have update the ENV VAR for the front-end , it is ready to merge to master, https://github.com/OpenHistoricalMap/tasking-manager/pull/20, there is some changes that is pending, could you check it ?


Procedural Texturing

Since we already have a RNG I think we can exploit it in order to generate some fancy Pigments.
I'd like to explore the world of Procedural Texturing and create:

[x] MarblePigment
[x] WoodPigment
[ ] CloudPigment

I'm using this as a reference

I've not found a sufficiently satisfying reference for the clouds...maybe in the future I'll add them.
In addition I've also introduced the LavaPigment, which was not in my original intention.
I try to merge


feat: v14 migration

Description
Hotfix: Resetes the pending nonces for testnet only. This would fix the issue caused by running the wrong migration script in v13 .
The new migration script still sets ZetaACccounting for mainnet , but does not reset the nonces .
Closes:
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Include instructions and any relevant details so others can reproduce.

[ ] Tested CCTX in localnet
[ ] Tested in development environment
[ ] Go unit tests
[ ] Go integration tests
[ ] Tested via GitHub Actions

Checklist:

[ ] I have added unit tests that prove my fix feature works

Added some logs for testing

x/crosschain/migrations/v5/migrate.go

Closing as released


STENCIL-2493 - Do not display "none" option for required pick lists

Correctly hiding the “none” option for required pick lists (without
photo)
I've also verified that this works with and without a default selection on the option.
Proof:

@bc-miko-ademagic updated.

I think we should test this before merging

Tested on integration store 💚


[Docs] Add help for DLL load failed error

Looks like as of tensorflow 2.1, on Windows you need "Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019" (see here). This should be added to the docs here and probably also here.

Added to docs here


Messer not displaying incoming messenges.

Description

Messer is not displaying incoming messages. They are present when checking the thread history however. This is on Windows 10 64, using the latest updates as of 12/17/19.

I have tested it on the command prompt, and ps core 6 inside of windows 10's new terminal.
Steps to Reproduce

Install messer following the guide.
Login.
Have friend send you message.

Expected behavior: [What you expect to happen]
Incoming message should display.
Actual behavior: [What actually happens]
Incoming message does not display.
Versions
Run and copy-paste the results of the following:
npm: 6.13.1
node: v13.3.0
messer: 0.7.1
Windows 10, 64 bit.

Thanks for reporting this @wgehalo, it looks like it could be related to this issue report on the api we use, but I'll check it out.

this bug seems to be critical, the same problem has inpact on fb-messenger-cli issued here
https://github.com/Alex-Rose/fb-messenger-cli/issues/220

I have still same issue
npm: 6.13.1
node: v13.3.0
messer: 0.7.1
macOS Catalina 10.15.4

Same issue. It looks like it's because of the API changes Facebook made recently to move messenger to using MQTT (a type of messaging protocol like WebSockets).
I had a look at the issues in the facebook-chat-api repo as @tomquirk linked and found the library was depreciating its api.listen method in favour of api.listenMqtt (see issue #786 in facebook-chat-api). The change looks to be a drop-in replacement, so it looks like all we'll need to do is change the line in Messer where this API is being used.
I did some testing locally to try this. The api.listen method is used in the messen library on line 139. After changing this line to api.listenMqtt, it looked like incoming messages were being displayed properly.


Setting up for 86box or VM

How to set up browservice for usage in 86box or VM in VMware Workstation? I can set it up on my Windows PC or Ubuntu 20.04 server

Wait... didn't you read the README?


Adds Move language

Reasons for making this change:
I am a core contributor to the Aptos blockchain https://github.com/aptos-labs/aptos-core, and I've written enough Move contracts to be inconvenienced / copy the same .gitignore between each.  Trying to make it as simple as possible for onboarding.
Move language is used for MoveVM based blockchains as the language native to them.  The compiler provides a folder build/ that holds the build artifacts.
The .aptos/ folder is ignored so people do not upload their private keys to a git repository.
Links to documentation supporting these rule changes:
Here's the Move book, though, it looks like it doesn't explicitly say that this comes from the compiler.
Example:
$ ls
Move.toml sources
$ aptos move compile --dev
Compiling, may take a little while to download git dependencies...
UPDATING GIT DEPENDENCY https://github.com/aptos-labs/aptos-core.git
INCLUDING DEPENDENCY AptosFramework
INCLUDING DEPENDENCY AptosStdlib
INCLUDING DEPENDENCY MoveStdlib
BUILDING Coin
{
  "Result": [
    "0000000000000000000000000000000000000000000000000000000000111111::coin"
  ]
}
$ ls
Move.toml build     sources

This applies to all blockchains that use the Move compiler.
Additionally, for Aptos specifically the Aptos CLI adds an account it'll create a file structure like below where the config.yaml has credentials in it:
$ ls -a
.          ..         .aptos     .gitignore Move.toml  build      sources
$ ls .aptos
config.yaml

It's best that all Move blockchains add anything here that may add unwanted credentials associated with their blockchains.
If this is a new template:

Link to application or project’s homepage: Aptos Foundation

@martinwoodward, what do we have to do to get these merged?

@wirecat any chance you could look at this one?

@dooleydevin mind taking a look at this?
The main important thing here is that, by providing this, users are less likely to share their credentials accidentally in repositories.

@gregnazario the gitignore file makes sense to me 😄 since move is a pretty specialized language, would you mind moving this under the community directory?

@gregnazario the gitignore file makes sense to me 😄 since move is a pretty specialized language, would you mind moving this under the community directory?

Sure, that works for me. Will it show up under the general github .gitignore search?

It will not, but it will be available for copying as you need and it allows other Move developers to collaborate on the file 👍

@gregnazario the gitignore file makes sense to me 😄 since move is a pretty specialized language, would you mind moving this under the community directory?

Sure, that works for me. Will it show up under the general github .gitignore search?

It will not, but it will be available for copying as you need and it allows other Move developers to collaborate on the file 👍

Hmm... I guess that's okay for now, but I think the focus on getting it into the main .gitignore list was to prevent people from uploading their credentials accidentally.

@dooleydevin mind giving it a look again :). Thanks!


merge from konsum-frontend-svelte

package.json

chore(deps): add ^3.0.8 remove ^3.0.7 (devDependencies.vite)

.github/workflows/browser_ci.yml

chore: add ${{ matrix.os }} (jobs.test.runs-on)
chore(deps): add 18.7.0 (jobs.test.strategy.matrix.node)

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

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

Your semantic-release bot :package::rocket:


Router searchParameter gets reset to default value (of zod schema) after navigations (and using retainSearchParams)

Which project does this relate to?
Router
Describe the bug
Using retained searchParams, if we change the retained param x form a to b on some route (lets say route-a) and we navigate to route-b, which doesn't change param x, param x will revert back to its default value.
This is a regression because it works on using older versions.
Same code older versions:
stackblitz
Same code latest versions:
stackblitz
Your Example Website or App
-see desc
Steps to Reproduce the Bug or Issue

click on Home route (see Auth defaults to true)
click on Settings route (see Auth remains true)
click on About route (see now Auth is false)
click on Home route:
4.a older version: Auth remains as false (which is expected)
4.b newer version: Auth changes back to true (which is unexpected)

Expected behavior
after chaning the retained searchParams, it should stay unchanged after navigations, and only change if explicitly said so.

some other weird thing here is that even without using this middle params stay on URL, kinda making retainSearchParams useless, unless im not grasping the use of it correctly.

Screenshots or Videos
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

which version exactly introduced the regression?

hi @schiller-manuel, its specefially this PR: 2747

same here, seems like 1.81.5 introduced this bug


Manual curation for 2022.02 release

Submission window should open around mid-January.
Checklist:

[ ] Step 1 — Process
[ ] Step 2 — Curate

[ ] Curation
[ ] Review 1
[ ] Review 2

[ ] Step 3 — Export
[ ] Step 4 — EFO feedback

Spreadsheet is ready for @BaronKoy

Ready for review, currently:

269 DONE
26 IMPORT
26 SKIP
10 UNSURE

I've done a quick review and change couple of the UNSURE to DONE.
I've also reviewed a few DONE as well that seemed to be wrong. I changed them to UNSURE/IMPORT and left comments

I have reviewed the manual curation spreadsheet. In detail the ones of status done and import without previous or exact mappings and all with status of unsure.

Of them, I changed 4 imports to unsure due to different reasons, all explained in the "comments" column with a reference for @BaronKoy to check, if possible.
Also made a few comments on the unsure.

@tcezard @M-casado Thank you for term reviews.
I have reviewed all comments and some labels have now been set to NEW or IMPORT, which will be included in the EFO import list. Majority of these were labels which were mapped to obsolete terms.
I still cannot find any external sources to create "irinotecan response - toxicity/adr" as a new term however, so I am suggesting this label is skipped this iteration.
@apriltuesday Ready for export and EFO import cross referencing.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/43880

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/44161

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/54051

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/57035

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/63769


Implement Highscores

It would be good to see your local highscores and if we could get a server running, sync this with global highscores so we can see how good people are at this game. The function we could use for fetching highscore online would be http_get. Highscore background and frame would need to be implemented and a font would have to be chosen. I think that your 3 best scores and 3 best global high scores would be a good enhancement.

If we don't want people to send fake requests, we can use this hashing library - https://marketplace.yoyogames.com/assets/250/string-hashing-script, and append a hash of the highscore plus a secret key on the end of each request, though I doubt anyone's going to do this


Some Equipment Stats options do not work?

"Show Atk/Def style icons", "Overlap Atk/Def stats on icons", "Show all 3 strength stats", "Write spellbook name", "Show Prayer and Weight", and "Show accurate weight" all seems to be defaulted to on with no ability to toggle them. Not sure if I'm missing something, but if so it is not clear what they change then.

Equipment Stats > Use all equipment stat options > uncheck


No delete project option

Well there is a create project option which is very helpful. People will try create a project for every domain i guess. But if there are a lot of domains it'll be difficult to manage those. A delete project option will be alot helpful.

Great suggestion, I don't think that would be too difficult to implement. I'll add it to my next round of features to look at.

Had some time today to review this. The commit above doesn't purge the data, but effectively archives the project so you can't interact with it anymore. If you find that you need to actually purge the data, let me know, but this should be up on the Chrome and Firefox stores pretty soon.


TestClient Read method should be ReadAsync

https://github.com/aspnet/SignalR/blob/dev/test/Microsoft.AspNetCore.SignalR.Tests/TestClient.cs#L134
Read -> ReadAsync

Resolved: https://github.com/aspnet/SignalR/pull/702


Bug fix/gal/39 fix api

https://github.com/ofir-zeitoun/expenses-client/assets/11245756/596c13f5-ea72-41ad-828b-e77056e5595c


Reset homeguild on guild leave

Store a list/dict in bbGuild objects of users who have this guild set as their homeGuild.
When a player leaves a guild check if it was their homeguild and handle. probably don't change their cooldown to prevent abuse
when the BOT leaves a guild, check if any players have this has their homeguild, and reset homeguild on those users. probably don't change their cooldown to prevent abuse

going to do this the long way of not storing users against guilds, just brute force checking through users DB for users with that homeguild as and when. It'd take up far too much memory to store ANOTHER reference to every user.

Marking this as won't do.
If a user leaves a guild and then rejoins, they won't like being on transfer cooldown. Same for kicking and re-adding the bot.


Feature request: DotNet configure version

I noticed I got some vulnerability reports on NuGet packages that were reported for netcore2.1 and lower however, my application is on netcore3.1.
Because of that, I'd like to have a flag where I can set the dotnet version to eliminate the need of suppressing every vulnerability that is not applicable.

Sounds like you have some false positives. I'd rather see which dependencies are causing the misidentification and fix the engine. Some of them may already be flagged as issues with the FP Report label.

I have no intention of building a feature to specify the .net version and hide related vulnerabilities. Instead, we need to tune the engine.


Export / import for team chats

It'd be ideal if there was a way to import existing data from Slack/Mattermost into team chats, maintaining the old usernames and timestamps on messages.
Now obviously there's no way for Keybase to verify the integrity of these messages (because they're coming from an old unsecured system), so maybe the import could just be signed by one of the team owners, and then if anyone is looking at those old messages, they can see via some visual indicator that they're the result of an import, and not actually signed or made by the person with that username.
We'd also like to be able to regularly export our team conversations. If Keybase servers go down tomorrow (after all, there's no revenue generation for Keybase at the moment!), we don't want to suddenly be locked out of all of our data and message history (Git is a little less concerning because there's distributed copies on other machines).

is there a way to export all chat data from Slack?????.......... TIL... lol

Yeah. Importing channels, messages, and files from a Slack export would be great... (might take a while though...)

Any progress on this?


[SR-1672][Parser] Improve diagnostics for trailing closures in stmt-condition

What's in this pull request?
CC: @jrose-apple , @lattner
Instead of enclosing whole expression:
  if let _ = retInt { 1 } {
                   ~^
                   (     )
  if fooObj.meth2(1) { 0 } {
                   ~~^
                   ,      )

Caveat:

That might lead to a second-round fix-it to add an argument label, but it's closer to standard Swift style for this case.

Resolved bug number: (SR-1672)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Test case suggestion please!

What's stopping us from adding the correct argument label?

(and, nice work and thank you :-) )

What's stopping us from adding the correct argument label?

Because this code is in Parse, I think we don't know the actual argument label yet. 😢

Oh, that's pretty unfortunate. Maybe instead of issuing the diagnostic in Parse we can move it to Sema? We should be building the TupleExpr correctly at this point, right?

This parser patch looks great. Don't sell yourself short. :-D Feel free to ask us things (here or on swift-dev).

@jrose-apple
Moved diagnostic logic to Sema.
I will revise the test cases, but if you have time, could you give me early feed back?
One behavior change: we now also recover trailing closure before where clause. e.g:
if let x = someOptional { ... } where someCondtion(x) {
   // ...
}

Some questions:

Sema/MiscDiagnostics.cpp#performStmtDiagnostics is the right place to diagnose?
Where the test cases should be in? I feel test/Parse/recover.swift is not relevant anymore.
I feel the logic to find the trailing closure is too complicated. Is there more simple way?

Updated test cases.
@swift-ci Please test

Updated the test cases.
Squashed.
@swift-ci Please test

@swift-ci Please test

@swift-ci Please test OS X platform

Sorry to leave you hanging! This looks pretty good, given the constraints. I agree that the use of an ASTWalker seems like overkill, but it does seem like the current best way to look through arbitrary expressions synthesized during type-checking.
There's already a test/expr/closure/trailing.swift, so maybe it makes sense to put the tests there.

@jrose-apple Thank you!
Moved test cases to test/expr/closure/trailing.swift

@swift-ci Please test


Cassandra requires Java 8 while all others are using Java 7

Reverted to Cassandra 2.2.4 from Apache repo instead of the Datastax repository. Java 7 works with Cassandra 2.2.4


Erroneous ArgumentNullExecption when Compressor is given an empty string

My personal reason for the request has been fixed downstream, closing.


fix: players are not deleted even using destroy op

well, the players actually deleted, but when the gatewayClosed event emitted, it creates a new one because of this@SocketContext.getPlayer(guildId) on the event

Thanks for the fix. For a explanation of this bug:
This was introduced on https://github.com/Frederikam/Lavalink/commit/7ef3f3890951655ad143d1739b2c29122b486b2b
When the player emits the gatewayClosed event (which will happen after the player is deleted), https://github.com/Frederikam/Lavalink/commit/7ef3f3890951655ad143d1739b2c29122b486b2b#diff-69d704c1fea4e5422f61cba6d43b943a69202a8ff81995fb3ebcc74d94f7511eR196 will just create a new Player instance, effectively making the "deletion" of the first player object not happen in practice (even though it just adds a completely new one, so the memory overhead should be lower for the leaky object)


Map to index action of controllers when no action is specified.

I figured other people would want the ability to route to index action of controller by default when none is provided.

Sorry meant to add a description.  I figured other people would want the ability to route to index action of controller by default when none is provided.

@carc1n0gen Will it show 404 or 500 if index method does not exist?

It displays 500 with the message "Template post/index.html not found."

I don't think either of these are a good idea:
GET     /:controller/                           :controller.index
*       /:controller/:action                    :controller.:action

The potential security downside is pretty high.

I tend to agree with @pushrax on this issue. I don't much like catch all routes like this. I would remove the current catch all instead of adding another.

@carc1n0gen thanks for taking the time to share this with the community. I'm closing since it's an easy change for a dev to make themselves.


aws.lambda.CallbackFunction: Support lambdas greater than 69905067 bytes via intermediate S3 bucket

From @chrsmith on November 15, 2017 19:29
Running pulumi preview doesn't detect if a lambda to be deployed is too large for AWS, which leads to a catastrophic failure when you try to deploy your program. Perhaps we could issue a warning/error if we detect this during preview?
error PU2003: Plan apply failed: rpc error: code = Unknown desc = Error creating Lambda
function: RequestEntityTooLargeException: Request must be smaller than 69905067 bytes
for the CreateFunction operation

status code: 413, request id: 8ae171d3-ca34-11e7-b1aa-01928c26ca07

Copied from original issue: pulumi/pulumi#573

This has not come again in nearly 2 years - and users can of course move to using S3 directly if they want - closing for now.

Hello. I'm currently getting similar error when trying to deploy my stack
error: 1 error occurred:
	* updating urn:pulumi:dev::aok-multi-pulumi::aws:lambda/function:Function::dev-v1-internal-reportProblem: 1 error occurred:
	* error modifying Lambda Function (dev-v1-internal-reportProblem-98cdf56) Code: RequestEntityTooLargeException:
	status code: 413, request id: c5d75820-7a09-4859-a18a-991ac87c88b5

The weird thing about this error that it goes away if I run pulumi up again in few minutes. But then it would appear again when we try to deploy some other changes to that stack.
Lambda package size (after the latest deployment) is 33.0 MB.
Also, @lukehoban  I have a question regarding

and users can of course move to using S3 directly if they want
Do you mean there is a setting in pulumi that enables uploading lambdas to s3? I that a documented feature?

Thanks in advance

UPDATE:

The weird thing about this error that it goes away if I run pulumi up again in few minutes. But then it would appear again when we try to deploy some other changes to that stack.

Actually the lambda is not updated on the AWS, despite pulumi up not returning any errors.

This has not come again in nearly 2 years - and users can of course move to using S3 directly if they want - closing for now.
@lukehoban I ran into this issue using APIGateway which uses the lambda function serialization aws.lambda.CallbackFunction can I use s3 in this instance?

I ran into this issue using APIGateway which uses the lambda function serialization aws.lambda.CallbackFunction can I use s3 in this instance?

Good point - it is not currently possible to use an S3 bucket with aws.lambda.CallbackFunction. I'll reopen this issue to track adding that support.

When trying to use an s3Bucket parameter with aws.lambda.CallbackFunction I'm met with this error
error: aws:lambda/function:Function resource 'callback-function-lambda' has a problem: Conflicting configuration arguments: "filename": conflicts with s3_bucket. Examine values at 'Function.Filename'.

If anyone runs across this issue and is trying to find a solution. A current workaround is to invoke an intermediate aws.lambda.Function inside your aws.lambda.CallbackFunction
const json = JSON.stringify({
    bucketId: bucket.get()
});
const lambdaResponse = await lambda.invoke({
    FunctionName: containerLambdaFunction.get(),
    Payload: json
}).promise();

I pass in ID's of resources that I want to use in the container so that I have access to them through the aws-sdk. You can create a container image the same way shown here. This way you can move all the heavy dependencies or large amounts of code to the container while still keeping the functionality of the aws.lambda.CallbackFunction.

I took a look at this, and the following patch provides an almost solution - but it is blocked by the inability to compute a SAH256 hash of the archive to pass as sourceCodeHash to aws.lambda.Function.  Without this, the function cannot be updated - changing the source code will replace the contents of the S3 Bucket Object, but will not cause the Lambda to be redeployed from the new contents. I've opened https://github.com/pulumi/pulumi/issues/11738 to provide a way in the Pulumi SDK to enable this.
diff --git a/sdk/nodejs/lambda/lambdaMixins.ts b/sdk/nodejs/lambda/lambdaMixins.ts
index 7253e8817b..250a7f4fb1 100644
--- a/sdk/nodejs/lambda/lambdaMixins.ts
+++ b/sdk/nodejs/lambda/lambdaMixins.ts
@@ -16,6 +16,7 @@ import * as pulumi from "@pulumi/pulumi";

 import * as arn from "../arn";
 import * as iam from "../iam";
+import * as s3 from "../s3";
 import * as utils from "../utils";

 import { Function as LambdaFunction, FunctionArgs } from "./function";
@@ -167,6 +168,13 @@ export type BaseCallbackFunctionArgs = utils.Overwrite<FunctionArgs, {
      */
     handler?: never;

+    /**
+     * Not allowed when creating an aws.serverless.Function.  The [code] will be generated from the
+     * passed in JavaScript callback, and can be placed into a Bucket Object, but not a specific object
+     * version.
+     */
+    s3ObjectVersion?: never;
+
     /**
      * A pre-created role to use for the Function. If not provided, [policies] will be used.
      */
@@ -344,7 +352,7 @@ export class CallbackFunction<E, R> extends LambdaFunction {
         // lambda options without us having to know about it.
         // The default version for Lambda functions now is NodeJS16. As of April 30 2022, Node12
         // is EOL/ nodeJS 14 is only in maintenance mode so it's best to upgrade to Node16
-        const functionArgs = {
+        const functionArgs: FunctionArgs = {
             ...args,
             code: code,
             handler: serializedFileNameNoExtension + "." + handlerName,
@@ -353,6 +361,25 @@ export class CallbackFunction<E, R> extends LambdaFunction {
             timeout: args.timeout === undefined ? 180 : args.timeout,
         };

+        if (args.s3Bucket || args.s3Key) {
+            if (args.s3Bucket === undefined || args.s3Key === undefined) {
+                throw new Error("Both `s3Bucket` and `s3Key` must be provided if either is provided.");
+            }
+
+            const obj = new s3.BucketObject(name, {
+                bucket: args.s3Bucket,
+                key: args.s3Key,
+                source: code,
+            }, opts);
+
+            // Remove code from the functionArgs so we use the S3 bucket args instead of the code.
+            functionArgs.code = undefined;
+
+            // TODO: Set sourceCodeHash to ensure that the function is recreated when the
+            // archive changes.
+            // functionArgs.sourceCodeHash = ...
+        }
+
         // If there is no custom Runtime argument being passed to the user
         // then we should add "runtime" to the ignoreChanges of the CustomResourceOptions
         // This is because as of 12/16/19, we upgraded the default NodeJS version from 8.x to 12.x as 12.x is latest LTS

@flostadler FYI


The main branch is not protected

Protect the main branch and only allow me to accept PR to main.

Fixed. Push to master requires review by owner.


Set up Tailwind Css Crashing

I've been using the extension for a while and it was working really well until I tried cloning my repo to a fresh local folder. Now when I try to setup tailwind through the context menu it produces the following:
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Bcl.AsyncInterfaces, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. O sistema não pode encontrar o arquivo especificado.
File name: 'Microsoft.Bcl.AsyncInterfaces, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'
at System.Text.Json.Serialization.Metadata.DefaultJsonTypeInfoResolver.GetDefaultSimpleConverters()
at System.Text.Json.Serialization.Metadata.DefaultJsonTypeInfoResolver..ctor(Boolean mutable)
at System.Text.Json.Serialization.Metadata.DefaultJsonTypeInfoResolver.RootDefaultInstance()
at System.Text.Json.JsonSerializerOptions.GetOrCreateDefaultOptionsInstance()
at System.Text.Json.JsonSerializerOptions.get_Default()
at System.Text.Json.JsonSerializer.GetTypeInfo(JsonSerializerOptions options, Type inputType)
at System.Text.Json.JsonSerializer.SerializeAsync[TValue](Stream utf8Json, TValue value, JsonSerializerOptions options, CancellationToken cancellationToken)
at TailwindCSSIntellisense.Settings.SettingsProvider.d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at TailwindCSSIntellisense.SetUpTailwind.d__14.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Community.VisualStudio.Toolkit.BaseCommand.<>c__DisplayClass8_0.<b__0>d.MoveNext()
Can you help me get it working again? I have tried uninstalling the extension and installling it again but no luck.

Sorry about that! It looks like I forgot to update one of the related NuGet packages; it should now be working in the latest extension update.

No problem! It does look like I still referenced an incorrect version of System.Text.Json in the current version (VS ships with Microsoft.Bcl.AsyncInterfaces 6.0.0 and 7.0.0 is not shipped in the extension) which is why you still got the error. I have downgraded System.Text.Json to 6.0.9 so there shouldn't be anymore errors regarding missing dependencies.
If you run into any issues, please let me know!
Sorry for the inconvenience, and thanks for letting me know!

Just reinstalled and it worked! Thanks for your quick response! This extension is awesome.


Fix global meter handling, configuring metric deltas instead of cumulative

Fixes accessing global meter provider instance.
Uses "delta" temporality instead of "cumulative" for meters, based on recommendations here: https://docs.datadoghq.com/opentelemetry/guide/otlp_delta_temporality/?code-lang=go

My apologies for this one! While testing I incorrectly read the data in Middleware. Currently Middleware does not appear to support the "delta" temporality of data, it is simply ignored, so this PR will not fix anything until MW has a solution in place.


Move cindercompatibleapi module to Sushi project

What this PR does / why we need it:
Considering cindercompatibleapi is a plugin for integrating openstack, we need to move this module into sushi project.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

Hi @xing-yang , could you take a review?


SFProcessTurn causing CREATE_FAILURE and stack rollback

When using the pca-main.yaml template to create the CloudFormation stack, the PCAServer will CREATE_FAIL because of the nested PCA stack entering a CREATE_FAILED state. This happens because the Lambda function SFProcessTurn fails with the error:
SFProcessTurn: CREATE_FAILED - Resources handler returned message: "Layers consume more than the available size of 262144000 bytes"

Reproduced.. thanks for reporting @flick1533. These lambda layers are dynamically created during install so perhaps the underlying packages have exanded in size and hitting this limit. We'll investigate. Thanks again.

Confirmed issue is in ffmpeg lamba layer, caused by pulling latest ffmpeg release from https://johnvansickle.com/ffmpeg/releases/ffmpeg-release-amd64-static.tar.xz - which, as of Spet 10th, is v5.1.1, a larger distribution that pushes the aggregate lambda layer size over the limit.
You can resolve immediately by setting CF stack parameter: ffmpegDownloadUrl to previous (smaller) ffmpeg build:  https://www.johnvansickle.com/ffmpeg/old-releases/ffmpeg-4.4-amd64-static.tar.xz
I'll also make a patch release of PCA to pin the ffmpeg version to 4.4 by using it as the new default value for download.


[CSApply] Handle OptionalForce component when is initial component on key path expr

Fixing crash when ForceOptional kind is the first component on CSApply.

Resolves SR-13442.

@swift-ci Please smoke test

@swift-ci  Please smoke test

Something wrong with the build? It still not triggered 🤔
Should we try again or just wait a bit more?

Looks like it didn't get triggered
@swift-ci please smoke test

@swift-ci please smoke test

Thanks @hamishknight @xedin :)


Cleaned up Runner and Abstract by shortening some expressions.

All tests still pass. (now that #118 is merged ;-))

and that's all for today ;-)

This seems fine. However I do note that many unit tests are failing in Ruby 1.9.3. Another reason to drop support for everything below 2.0? :)
They are failing because of __dir__ in twine_test_case.rb. __dir__ was added in Ruby 2.0.

@sebastianludwig Fixed the < 2.0 unit tests in b2b4bdcc8aaffe0384bd08b0b569e9f0b784a690

Yeah, totally my fault. I should have been testing with the lowest supported version. I'll mention that in the ruby 2.0 issue and will fix it if the support level remains on 1.8.7.


pana/google_maps/3.3.2: dartfmt failed

I'm seeing this recurring error in the analyzer logs:
pana/google_maps/3.3.2: `dartfmt` failed.
Exception: dartfmt on lib/ failed with exit code -15
Exceeded timeout of 0:02:00.000000

Error:
    Exception: dartfmt on lib/ failed with exit code -15
    Exceeded timeout of 0:02:00.000000

Seems this package is too big to format or it ran into some bad performance in dartfmt? Unclear how we should handle cases like this. It seems to be the only one.

Running dartfmt on that project takes about 1m 30s to complete on my Macbook with SSD, it is possible that it can exceed the 2-minutes timeout even on a slightly less powerful CPU or lower IOPS disk. I don't see a reason why we couldn't increase the timeout to eg. 5 minutes.

google_maps is now successful in the analysis, the dartfmt process was completed in 2 minutes 5 seconds.


refactor: N-10 Naming Suggestions

[ ] rename validate -> TBD
[ ] rename update_proposal -> decided against, as update_proposal can also update the metadata_uri, and I feel like it would be too verbose
[x] rename target when appropriate https://github.com/snapshot-labs/sx-starknet/pull/590/commits/b9c2755d655820e2f86926400a54da7b2179908f
[x] rename l1_account_address a571f1b728d8ac92369c11c7cb9996f0ccb1e1f5
[x] rename reinitialize 5bb2b0100c0905ab4e72479c3a1e7c14fbf31a3f
[x] rename EthBalanceOfVotingStrategy 4aa949e68cb02f2b38454e705285ce70db3ea80f

Closes #572

should we rename eth_tx to l1_tx? Might be worth being consistent to remove all mentions of 'eth' unless it specifically refers to the token itself

I don't know about that, if I say out loud "you can authenticate via an eth signature" or "you can authenticate via an l1 signature" I feel like the former is clearer ?

should we rename eth_tx to l1_tx? Might be worth being consistent to remove all mentions of 'eth' unless it specifically refers to the token itself

I don't know about that, if I say out loud "you can authenticate via an eth signature" or "you can authenticate via an l1 signature" I feel like the former is clearer ?

yeah true


Add loop bound state registry

The registry allows to store information bound to a specific loop. This can be useful to store state of globals like a DNS resolver.
Rationale for a global DNS resolver
Nobody wants to inject a resolver into everything that does some sort of I/O. Using IP addresses everywhere instead of hostnames also doesn't make sense.
Therefore there should be a global default DNS resolver. But this resolver needs a read watcher for the response. If the loop gets swapped and a DNS request is made, the resolver would never get the read event, since the stream is only watched in the old loop. The resolver also doesn't get any info about the loop swap, so it can't use a new watcher.
With a loop bound registry, it can just store the connection in the loop and will use a new connection when the loop is swapped, because the state doesn't exist any longer. Once the loop is put back, it can use the old connection again.
This API should only be used by real global objects. Most packages won't need to use this API, but it's required for the mentioned use cases.

Looks good to me; I'd like to have someone else merge it though.

I don't think we have consensus here yet.

Not sure whether storeState / putState / setState. I don't like setState, it makes me think it's an event loop state, not something not actually related to the loop driver but just data.

@kelunik yeah, I'm not sure on consensus, that's why I'd like to have someone else merging it when it's clear that there's consensus … as I'm biased as it was my idea ;-)

@kelunik either we have get/set or store/fetch. Both variations are fine with me (but not set/fetch).

What about putting the registry stuff into a trait, or a subclass? Subclass may be slower than desired. Is anything else likely to need this registry stuff?

Having a trait to do that wouldn't be a bad idea, I totally agree. (You mean additionally to the interface methods, right?)

@bwoebi yeah, in addition.

What's the benefit of moving it out when just the Loop uses it?

It's additional responsibility, that could be tested and documented on its own.

The registry has to be swapped with the loop, how does that work with a trait?

Traits are literally compiler-assisted copy and paste. It would work in exactly the same way as if the code was inside the loop.

In that case the trait would rely on a variable being present in the loop class. I don't see the benefit here. Just a disadvantage that we rely on a static variable being present in the trait.
Separation of concerns is fine, but not for the sake of it if you have to use a trait for it. Because that doesn't separate anything, it just moves it out, so it can be used in multiple places.

If the property is on the trait then the class would rely on the variable being present. That's an ok relationship since the class already knows it's using the trait. Alternatively, there are abstract method signatures to ensure traits have access to the data from the classes that use them.
They're separate responsibilities. I won't bore you with the benefits of SRP (there are good books which do a much better job of explaining it than I do), but essentially one trades speed for isolated testing, documentation, maintenance and limited side effects to modifying behaviour.

Yes, but this is a utility class that just has static methods and only execute changes state at all, so the number of site effects is quite limited.

If the property is on the trait then the class would rely on the variable being present.

Traits can't define static members in PHP.

@kelunik Why should traits not be able to define static members? Works in 5.5 all the way up to current master.
@assertchris Thinking about it, I don't think traits are a very good way to enforce SRP. Please leave it in. I'd like to have one class with all the public methods viewable at once. A trait only hides these.
In general, it is fine with SRP. The responsibility is managing the loop, and part of it is managing the attached state too.
The PR is LGTM to me and shall be merged.

@bwoebi Seems like the German translation is just plain wrong then.

Innerhalb von Traits kann auf statische Variablen zugegriffen werden, aber diese können nicht in Traits definiert werden.  Fixed in doc commit 339170.

@assertchris I think it's fine as trait then. Refactored it and added tests.

Can we merge this?

@bwoebi @trowski @AndrewCarterUK Can you merge this? I don't want to merge my own PR.


Override commit flag for pre-releases only

Current behaviour:
If the commit flag in config.json is set to true it is still overriden to false when doing changeset version for all releases
Fix:
commit flag will be overriden only for pre-releases

This got superseded by https://github.com/atlassian/changesets/pull/437


diagonal lines, inserting up and down arrow and other possible extensions

example why this is cool
Only providing diagonal lines and have a way to insert up and down arrow should be sufficient for most cases.
However having the optional + in several cases could also simplify drawing.
The ultra interface would be of course a curve plotting from a selection via commands and interpolation of results, but thats quite some complexity.

That's cool indeed. There are some impressive ascii art in there.
One difference with them is that venn.nvim is using the special box-drawing characters instead of standard ASCII. I guess if you prefer this style DrawIt or one of its fork could be an option.
I see now that they are also diagonal characters ╱, ╲, ╳. We could integrate them in venn.nvim somehow. I'm currently not sure how the drawing process would look like.
Plots would be cool indeed. I think it would have to be a separate plugin though.

It would also be nice to be able to use a dashed ascii line instead of just a solid one.

I see now that they are also diagonal characters ╱, ╲, ╳. We could integrate them in venn.nvim somehow. I'm currently not sure how the drawing process would look like.

There are typically 2 modes for lines in inkscape: 1. accurate and 2. interpolated
As I understand it, the main implementation problem for both approaches is to get useful information for the console/terminal font to decide, if the non-accurate line interpolates
1.
   x
 /
x
2.
x
|
x
3.
x
 \
  x

One needs to figure out the prescaling factor of the terminal font to know the diagonal offset (in this case / and \ need 2 character's right- and leftwards, but this might become arbitrary complex with utf8 symbol width.

It would also be nice to be able to use a dashed ascii line instead of just a solid one.

This is a good idea and might be a recurring request. I have added two functions set_line and set_arrow to customize the style of lines and arrow for each direction. We might have a style parameter in the future.
For example to get the standard ascii style, you would set:
require"venn".set_line({ "s", "s" , " ", " " }, '|')
require"venn".set_line({ " ", "s" , "s", " " }, '+')
require"venn".set_line({ " ", " " , "s", "s" }, '+')
require"venn".set_line({ " ", "s" , "s", "s" }, '+')
require"venn".set_line({ "s", " " , "s", "s" }, '+')
require"venn".set_line({ "s", "s" , " ", "s" }, '+')
require"venn".set_line({ "s", "s" , "s", " " }, '+')
require"venn".set_line({ " ", " " , "s", "s" }, '-')
require"venn".set_arrow("up", '^')
require"venn".set_arrow("down", 'v')
require"venn".set_arrow("left", '<')
require"venn".set_arrow("right", '>')

Not sure, if the character width can be queried in a simple way from utf8.
The box-drawing characters are actually already multi-byte character so I needed to compute the width. There is one function in neovim, I don't recall the name anymore to get the displayed width of any string.

The main issue was more about how to keep a logical user interface for vim while allowing the drawing of diagonal characters. Draw a rectangle in Visual + VBox, to draw a rectangle. Draw a rectangle of width/height 1 to draw an arrow.
I'm not sure where to fit diagonal lines.

It would also be nice to be able to use a dashed ascii line instead of just a solid one.

This is a good idea and might be a recurring request. I have added two functions set_line and set_arrow to customize the style of lines and arrow for each direction. We might have a style parameter in the future.
For example to get the standard ascii style, you would set:
require"venn".set_line({ "s", "s" , " ", " " }, '|')
require"venn".set_line({ " ", "s" , " ", "s" }, '+')
require"venn".set_line({ "s", " " , " ", "s" }, '+')
require"venn".set_line({ " ", "s" , "s", " " }, '+')
require"venn".set_line({ "s", " " , "s", " " }, '+')
require"venn".set_line({ " ", "s" , "s", "s" }, '+')
require"venn".set_line({ "s", " " , "s", "s" }, '+')
require"venn".set_line({ "s", "s" , " ", "s" }, '+')
require"venn".set_line({ "s", "s" , "s", " " }, '+')
require"venn".set_line({ " ", " " , "s", "s" }, '-')
require"venn".set_arrow("up", '^')
require"venn".set_arrow("down", 'v')
require"venn".set_arrow("left", '<')
require"venn".set_arrow("right", '>')

Not sure, if the character width can be queried in a simple way from utf8.

The box-drawing characters are actually already multi-byte character so I needed to compute the width. There is one function in neovim, I don't recall the name anymore to get the displayed width of any string.
The main issue was more about how to keep a logical user interface for vim while allowing the drawing of diagonal characters. Draw a rectangle in Visual + VBox, to draw a rectangle. Draw a rectangle of width/height 1 to draw an arrow. I'm not sure where to fit diagonal lines.

Thanks,
It seems it works for the future lines drawn, it doesn't seem to change the existing lines .. is this expected? Any way to forcefully  change all lines?

Thanks,
It seems it works for the future lines drawn, it doesn't seem to change the existing lines .. is this expected? Any way to forcefully change all lines?

Yes this is expected. It should be viewed as a configuration that is put in the init.lua/init.vim for any future drawings. If you want to replace existing drawings, that's a completely different topic.


make django notifiy errors via email to<EMAIL_ADDRESS>

set up ADMIN_EMAILS in django settings and proper configuration of logging

Sending email is blocked on finding a way to do this. As a work around, do the following:

Configure Django logging to log 500 tracebacks, etc.
Configure stackdriver to email these log messages to us.


Launch issue (Folder Processor)

Hi there. I've downloaded the CCA tool suite for BitCurator and everything works fine except for the Folder Processor, which will not open at all - no activity when the icon is double clicked or right-click+open. I'm not overly experienced with working in Linux, but as far as I can tell the install went perfectly, including the PyQt5 install. Is there any reason you can think of in which the Disk Image Processor and the SIP Creator open and work fine, but the Folder Processor doesn't open at all?
I'm using the latest CCA tool release on BitCurator 2.2.8.
Apologies if this is the wrong forum for this question (new to GitHub), but any help that can be offered would be much appreciated.
Thank you,
Jarad

Hi @WhenSkiesAbove, thanks for filing this issue! And my apologies for the very long response.
If you're still interesting in resolving this, could you tell me what output you get entering the following into a terminal? Does the GUI launch?
python3 /usr/share/ccatools/folderprocessor/main.py

Another thing to check: Sometimes the installation process doesn't quite get the executable permissions right for the launchers in /home/bcadmin/Desktop/CCA Tools. Try right-clicking on the Folder Processor icon, selecting "Properties", and then making sure "Allow executing file as a program" is checked under the Permissions tab. The first time you launch the program it may also open a dialog asking you to trust and launch the program - if so, select yes.

Hi Tessa,
Thanks for the reply. I think I figured out what the issue was, or at least something that made it work for my particular instance. When I ran the command you suggested above, it returned an import error line 26, in <module> import Objects | ModuleNotFoundError: No module named 'Objects'.
I ended up changing the sys.path.append line in main.py as the location of my objects.py file didn't match what was in main.py ('/usr/share/dfxml/python' in original VS '/usr/share/dfxml/python/dfxml' in my setup). Not sure if that's universal or not, but that's where it is for me. Also made objects lowercase to match my objects.py file, if that's relevant. I don't super know what I'm doing - very new at this - so hopefully doing this didn't screw anything else up I didn't foresee.
Thanks! For this and all your work making this software!

Hi @WhenSkiesAbove, I'm glad you figured it out! It looks like you hit the same issue as #4. Each of the repositories has since been patched to use a pinned and included version of the DFXML Python bindings rather than relying on the ones in BitCurator, so if you re-install it should be fixed now. I'm closing this as resolved for now but feel free to re-open if you continue to have any issues!


Remove upper bound version constraints

Missing functionality
ydata-profiling is difficult to incorporate into an existing stack due to a number of dependency conflicts because of the upper bound version constraints: https://github.com/ydataai/ydata-profiling/blob/master/requirements.txt
Are these upper bound constraints necessary or would you be willing to remove them going forward? https://iscinumpy.dev/post/bound-version-constraints/
Proposed feature
Upper bound version constraints are removed from requirements.txt.
Alternatives considered
No response
Additional context
No response

Hi @ndawe,
We had some internal debates about removing the upper bound!
The consensus we reached is to remove it for large libraries with an active release cycle (e.g. pandas, numpy, scipy) and keep the version fully pinned for smaller ones, with less activity. In case we observe problems in the future (as we did in the past!), we will have to pin them back.
This is on the the roadmap for the next version.

Hi @ndawe ,
as per what @aquemy mentioned we have removed some of the upper bound limitations. For pandas v2.0 we are actively working to make it available.

Hi @ndawe
pandas 2 is now enabled in ydata-profiling 4.3.0! Give it a go :)


Training data / time

Few questions:

How much data was the demo model trained on?
How many epochs?
How long did training take and what system?

actually there is misinformation in this repository but when I searched for information about the approach and resources they relied on for the model I found this official article, it may help you understand how things work here a little better

It seems that the number of training steps is 870000 and the number of trained samples is 192478464. This second number seems to be the total combinations audio+noise+rir trained, so front ground audios could be repeated. You can check this information creating a script loading and printing pretrained models. Training time depends on hardware architecture, so it's dificult to estimate.


Added a new resource

Hello, I have added a new useful link for the HTML tags, that contains all the basic HTML tags that can be used for the markdown table. I hope this small contribution will help other learners as well.

Hello @florinpop17, I would like to inform you that this may be spam. The user creates hundreds of PRs that looks similar to advertise the page "scaler.com".


Write a C program to convert string to sentencecase

Description
Write a C program to convert string to sentencecase
Sentencecase is a style of writing in which the first letter of the first word is capitalized.
Input  : "hello world"
Output : "Hello world"

How to contribute

Save the solution in ConvertStringToSentencecase.c file
Add ConvertStringToSentencecase.c file in program/convert-string-to-sentencecase folder

!assign


Uncaught TypeError: Cannot read property 'getPath' of undefined

[Enter steps to reproduce below:]

...
...

Atom Version: 1.7.3
System: Unknown Windows Version
Thrown From: preview-plus package, v1.2.6
Stack Trace
Uncaught TypeError: Cannot read property 'getPath' of undefined
At /C:/Users/Zodiac/.atom/packages/preview-plus/lib/status-view.coffee:138

TypeError: Cannot read property 'getPath' of undefined
    at BrowserView.open (file:///C:/Users/Zodiac/.atom/packages/preview-plus/lib/status-view.coffee:68:19)
    at BrowserView.openChrome (file:///C:/Users/Zodiac/.atom/packages/preview-plus/lib/status-view.coffee:46:6)
    at HTMLSpanElement.<anonymous> (C:\Users\Zodiac\AppData\Local\atom\app-1.7.3\resources\app.asar\node_modules\atom-space-pen-views\node_modules\space-pen\lib\space-pen.js:220:36)
    at HTMLSpanElement.jQuery.event.dispatch (C:\Users\Zodiac\AppData\Local\atom\app-1.7.3\resources\app.asar\node_modules\jquery\dist\jquery.js:4435:9)
    at HTMLSpanElement.elemData.handle (C:\Users\Zodiac\AppData\Local\atom\app-1.7.3\resources\app.asar\node_modules\jquery\dist\jquery.js:4121:28)

Commands
     -1:27.4.0 markdown-preview:toggle (atom-text-editor.editor.is-focused)
  2x -0:36 core:delete (atom-text-editor.editor.is-focused)
     -0:29.7.0 markdown-preview:toggle (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "disabledPackages": [
      "navigate",
      "browser-plus"
    ]
  }
}

Installed Packages
# User
emmet, v2.4.3
preview-plus, v1.2.6

# Dev
No dev packages

preview-plus - is deprecated..Please try pp(https://atom.io/packages/pp)


[Feature] Redis embedding store spring boot starter

Hi, I add langchian4j-redis-spring-boot-starter implementation. Test run correct in my local environment.
btw, I'll add spring boot starters to the other vector stores in a few days. Waiting for your code reviews!

@langchain4j Hi! I've been done it with adding default dimension by EmbeddingModel.dimension().

Note: Thit PR should be merged after #29


[DOCFIX] Fix typo in LockResource comment

What changes are proposed in this pull request?
Fix the typo: from if to is
Why are the changes needed?
Fixed typo
Does this PR introduce any user facing changes?
Not at all

alluxio-bot, merge this please

alluxio-bot, merge this please


The ability to provide a custom StateListDrawable for action buttons

[To be specified]

This isn't very specific

With the code that hasn't been published as a release, you can already use a state list for the color of the action buttons. Not sure where you would need state list drawables.

I mean, provide to the Builder a StateListDrawable programmatically, not from res.
Like:
StateListDrawable states = new StateListDrawable();
states.addState(new int[] {android.R.attr.stateNotNeeded}, R.drawable.btn_off);
states.addState(new int[] {android.R.attr.state_pressed, android.R.attr.state_enabled},R.drawable.btn_off);
states.addState(new int[] {android.R.attr.state_focused, android.R.attr.state_enabled},R.drawable.btn_on);
states.addState(new int[] {android.R.attr.state_enabled}, R.drawable.btn_on);

Then:
MaterialDialog D = new MaterialDialog.Builder(A)
[...]
.btnSelector(states, DialogAction.POSITIVE)
[...].build();
Add a btnSelector(StateListDrawable state, DialogAction which) method.

Updated your comment to format the code and provide syntax highlighting correctly.

The library used to allow Drawable instances to be passed there, but there are weird issues that come out of it. You can try it if you want (using a fork of the library).


Unable to load DLL 'Microsoft.CognitiveServices.Speech.core.dll

Please provide us with the following information:

This issue is for a: (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

After I followed the steps in the doc, and run the VoiceAssistantClient.exe, I got an error.
And I can not find the Microsoft.CognitiveServices.Speech.core.dll in the bin\x64\Debug folder

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 10

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Hi there,
Thanks for reporting this issue. We are able to reproduce it and should have a fix checked in soon. The fix we have is to update the nuget package for Microsoft.CognitiveServices.Speech to the 1.10 release. Could you try that and see if it works for you?

Update to Speech SDK 1.10 does not fix the issue. We are working on another fix.

Copying the dll from the package folder works, thanks!


Add psmisc

Add psmisc, using the new overlay format (https://github.com/bazelbuild/bazel-central-registry/issues/1566)

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (psmisc) have been updated in this PR. Please review the changes.

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (psmisc) have been updated in this PR. Please review the changes.


all vesions except 'latest' disappeared

Details

Project URL: http://scrapy.readthedocs.io/ (we're using custom domain: https://doc.scrapy.org/)

Expected Result
There used to be documentation version selector.
Actual Result
Now the version selector is gone (the UI element is still present, but there are no versions available). Also, docs other than 'latest' are not available at all, links to these docs are broken.
Versions still have checkboxes checked near them in readthedocs project options; I don't think we changed anything recently.

Scape is set to a single_version project, which removes the other versions that are associated with it.

Thanks for the quick answer! It fixed it. Maybe someone checked this checkbox occasionally. Sorry for noise!


Support Decoding Message Data from MessageOut Receipt

We should consider adding a feature to the SDK to decode the Message data property, as this functionality could be beneficial for certain users.
It may also be possible to decode this on the fly when parsing the MessageOut receipt.

More context on the following discussion.

Unassigning myself from this after a conversation with @nedsalk this will be apart of the broader ABI refactor in https://github.com/FuelLabs/fuels-ts/pull/3085

Users need to be able to define their own coders for this to work completely.

Coders for functions/configurables, etc. will use a Sway spec version of encoding. However, messages may require custom coders to be passed in which don't match the spec, because their encoding is left for the user to define. (relates to https://github.com/FuelLabs/sway/issues/5514)


[FR] Pull due time of tasks

First of all, great job with this plugin.
I currently use it to backup my calendar events and to-dos (which are simple tasks from Todoist), and than delete my projects or calendars from Todoist safely.
If there was an possibility to pull the time that the task was due would be really good for me to understand better past to-dos and events.
An option to prepend this time would also be a good option to get good integration with Day Planner plugin.
Thank you very much for your attention.
Example:
%% COMPLETED_TODOIST_TASKS_START %%

To-dos

07:00 Task X
23:50 Task Y

Calendar 1

09:00 Event A
16:00 Event B

Calendar 2

12:15 Event C
22:30 Event D

%% COMPLETED_TODOIST_TASKS_END %%

Hi @guihasparyk ,
Thanks for the proposal, I'll have a look into if API provides this data