BlocViewModel?

I really liked your implementation of Bloc in kotlin.
ViewModel is finely integrated with Activities (retention on activity recreate, etc) and other Android stuff in general.
Also ViewModel is responsible for holding the ui state, and reacting to ui actions (just like Bloc).
So, a BlocViewModel based on AndroidViewModel/ViewModel would be great and really useful.
BlocViewModel would be a AndroidViewModel/ViewModel with all capabilities of Bloc.
Your thoughts?

I think it should use viewmodel as you have suggested. For me the most important reason to use viewmodel is to use hilt.

I like this suggestion - I'll look into it!

I like this suggestion - I'll look into it!

Amazing. This will be really helpful as we will be able to use hilt, scopes and other cool stuff. Plus if google adds more features to viewmodel, we will be able to adopt them easily. Looking forward for an update.

I have looked into the library and the it can be achieved by exteneding BlocBase with ViewModel.
abstract class BlocBase<State>(initial: State)

But another serious issue arises here that KotlinBloc which is platform independent, becomes specific to android only. Maybe a separate library like com.github.ptrbrynt.KotlinBloc:viewmodel which would be specific to android. It's a suggestion. There might be other solutions to this as well.


Default CSS files

Is it our responsibility to provide "default CSS" files users can use? Arguably, the generated HTML with no styling is really ugly. Should we put our users to the burden of creating a CSS file just to try the application out? Or even to have their blog? Should we provide none, one or more styles? Should those styles belong in this repository, or elsewhere? Can we make it easier to get started with a style?
As a side note the current .css does not handle <img> tags so large images will render outside the intended page width, and has some other issues:

i also changed bg color bc very yellow
and the smallcaps was a bit dramatic, olde style for my taste
then i had to darken the code bg because it looked similar to bg
oh and i specify my sizes in rem or em, not px
apart from lines i guess
and some stuff i haven't switched to rem

(me: i find it easier on the eyes with less blue)

too yellow :(
i don't want old vibes personally

Shall I update the default CSS to the one I was referring too?

I'm not 100% percent sure I want to clutter the repository of the application itself with minor commits for style improvements. Maybe a separate repository with styles would be better?

That seems like overkill; as it is, the CSS serves as a form of documentation


IntentIQ and Datonics owned by AlmondNet

IntentIQ and Datonics appear to belong to the same group: AlmondNet. Should this be reflected in the "Owned by" field?
(I'm not affiliated with these companies)

Thanks for this, this checks out. Here are the sources:

"Our Parent Company – AlmondNet Group" https://www.intentiq.com/company
"Datonics (www.datonics.com), a subsidiary of AlmondNet..." https://www.datonics.com/about

I'll get this added to the next batch of database updates.


Transfer Utility  Code=2 "(null)" - iOS

Hi,
I'm trying to upload a picture to a S3 bucket on iOS, but on every first upload after app start the following error is returned in the completation handler. Then the next picture doesn't even start the upload (no info cames from progress callback)
"Error Domain=com.amazonaws.AWSS3TransferUtilityErrorDomain Code=2 "(null)" UserInfo={Server=AmazonS3, Transfer-Encoding=Identity, Connection=close, Content-Type=application/xml, Date=Tue, 08 Nov 2016 16:38:58 GMT, x-amz-request-id=A33BCEA53A29008B, x-amz-id-2=ew77OTuf2kBDt7ZKbZISzQLSex7oCU/ecKMgTFasY6+F2qtqjM4lKaZkEbQtXr36ncPU4IBdfKg=}"
Env: OSX El Capitan, XCode 8.1
Device: iPhone 6s Plus iOS 10

I'm facing the same issue aws 4.2.1

I was getting the same error output when device time was set into the future.

You could try logging out the calls made by the SDK using AWSLogger.default().logLevel = AWSLogLevel.verbose in AppDelegate.
When the image is being uploaded check if the region is being applied in the host
eg: .s3.<region_name>.amazonaws.com
I faced an issue where the region was not being applied.
So to resolve it has to set the AWSServiceConfigurations specific to region where the bucket is and then register it with the AWSS3TransferUtility and call it with the registered key.
From the AWS S3 SDK AWSS3TransferUtility:
/**
Creates a service client with the given service configuration and registers it for the key.
 For example, set the default service configuration in `- application:didFinishLaunchingWithOptions:`

 *Swift*

     func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {
         let credentialProvider = AWSCognitoCredentialsProvider(regionType: .USEast1, identityPoolId: "YourIdentityPoolId")
         let configuration = AWSServiceConfiguration(region: .USWest2, credentialsProvider: credentialProvider)
         AWSS3TransferUtility.register(with: configuration!, forKey: "USWest2S3TransferUtility")

         return true
     }

 *Objective-C*

     - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
         AWSCognitoCredentialsProvider *credentialsProvider = [[AWSCognitoCredentialsProvider alloc] initWithRegionType:AWSRegionUSEast1
                                                                                identityPoolId:@"YourIdentityPoolId"];
         AWSServiceConfiguration *configuration = [[AWSServiceConfiguration alloc] initWithRegion:AWSRegionUSWest2
                                                                              credentialsProvider:credentialsProvider];

         [AWSS3TransferUtility registerS3TransferUtilityWithConfiguration:configuration forKey:@"USWest2S3TransferUtility"];

         return YES;
     }

 Then call the following to get the service client:

 *Swift*

     let S3TransferUtility = AWSS3TransferUtility(forKey: "USWest2S3TransferUtility")

 *Objective-C*

     AWSS3TransferUtility *S3TransferUtility = [AWSS3TransferUtility S3TransferUtilityForKey:@"USWest2S3TransferUtility"];

 @warning After calling this method, do not modify the configuration object. It may cause unspecified behaviors.

 @param configuration A service configuration object.
 @param key           A string to identify the service client.
 */

@dccper-reuben For my case, registering the AWSS3TranserUtility solved the problem.
You saved my day!!!

@ondrejhanak Did you solved the 'time' issue? case We cannot ask users to set time accuraty.

@EdYao it was only on my testing device, where date was 1 whole day off from previous testing of different feature. So users were not involved in my case.


'use HTTPS' cannot be replaced by a translated file

'use HTTPS' cannot be replaced by a translated file

Fixed! Ty for letting me know


Update README.md

closes #2
Update README.md file with clearer project description, detailed instructions, and a table of contents to make it easier for users to understand and contribute to the project.

Calm down my friend😭 didn't even assign you to anything.

But thanks anyway

I am sorry, But thanks.

Ok! I really want to work on this. Can you assign me this task?

Ok! I really want to work on this. Can you assign me this task?

I will assign you officially, Hopefully you see the review notes above

Hello, @Dun-sin. Just want to remind you that I am not idle. I am working on it.

Hello, @Dun-sin. Just want to remind you that I am not idle. I am working on it.

well thanks for letting me know, i don't think it takes more than an hour tho, what's taking your time?

Hello @Dun-sin I have made the changes as you've guided. Should I make more changes?

Thank you so much for reviewing.

@mithindev it's much better, thanks for fixing them, just a little more change to Your PR, i gave the new review above

Thanks for this @mithindev

Sure.  I will do it.


[SPARK-49502][CORE] Avoid NPE in SparkEnv.get.shuffleManager.unregisterShuffle

What changes were proposed in this pull request?
This PR aims to avoid NPE in SparkEnv.get.shuffleManager.unregisterShuffle.
Why are the changes needed?
After SPARK-45762, the shuffle manager is initialized after the block manager, which means that when the driver cleans up the shuffle, the shuffle manager may not have been initialized yet, causing NPE.
24/09/03 20:09:51,668 [dispatcher-Executor] INFO BlockManager: Initialized BlockManager: BlockManagerId(168, x, 25467, None)
24/09/03 20:09:51,684 [block-manager-storage-async-thread-pool-2] ERROR BlockManagerStorageEndpoint: Error in removing shuffle 29
java.lang.NullPointerException
        at org.apache.spark.storage.BlockManagerStorageEndpoint$$anonfun$receiveAndReply$1.$anonfun$applyOrElse$3(BlockManagerStorageEndpoint.scala:61)
        at scala.runtime.java8.JFunction0$mcZ$sp.apply(JFunction0$mcZ$sp.java:23)
        at org.apache.spark.storage.BlockManagerStorageEndpoint.$anonfun$doAsync$1(BlockManagerStorageEndpoint.scala:89)
        at scala.concurrent.Future$.$anonfun$apply$1(Future.scala:659)
        at scala.util.Success.$anonfun$map$1(Try.scala:255)
        at scala.util.Success.map(Try.scala:213)
        at scala.concurrent.Future.$anonfun$map$1(Future.scala:292)
        at scala.concurrent.impl.Promise.liftedTree1$1(Promise.scala:33)
        at scala.concurrent.impl.Promise.$anonfun$transform$1(Promise.scala:33)
        at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:64)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

Does this PR introduce any user-facing change?
No
How was this patch tested?
GA
Was this patch authored or co-authored using generative AI tooling?
No

How is unregister shuffle getting called ? Shuffle registration requires SparkContext to have been initialized - which will include shuffle manager.

How is unregister shuffle getting called ?

The Executor is added in the case of dynamic allocation. It first initializes the BlockManager and registers it with the Driver, and then initializes the ShuffleManager.
https://github.com/apache/spark/blob/339d1c9d9d50bce63316ac788626bea998e71b06/core/src/main/scala/org/apache/spark/executor/Executor.scala#L162
https://github.com/apache/spark/blob/339d1c9d9d50bce63316ac788626bea998e71b06/core/src/main/scala/org/apache/spark/executor/Executor.scala#L355
The Driver will send removeShuffle RPC to all registered BlockManagers. At this time, there are some newly added Executors that have not yet initialized the ShuffleManager.
https://github.com/apache/spark/blob/339d1c9d9d50bce63316ac788626bea998e71b06/core/src/main/scala/org/apache/spark/storage/BlockManagerMasterEndpoint.scala#L469-L474
RemoveShuffle RPC has two code paths that will trigger.
https://github.com/apache/spark/blob/339d1c9d9d50bce63316ac788626bea998e71b06/core/src/main/scala/org/apache/spark/ContextCleaner.scala#L235-L241
https://github.com/apache/spark/blob/339d1c9d9d50bce63316ac788626bea998e71b06/sql/core/src/main/scala/org/apache/spark/sql/execution/SQLExecution.scala#L177-L183

Ah ! This is happening at the executor, not driver - thanks for clarifying.
Let me take a look at the detailed comment tomorrow (a bit late for me :-) )


Create Initial Tertiary Theme

This PR includes an update to introduce a third theme, tertiaryTheme, to Radiance for use on Admin + Pharmacy pages. tertiaryTheme includes new font and typography constants.

@iiimosley Reviewed the changes from your commit (77517052d394d8ea526704248b1881886702ad02) and they look good 👍


Refresh button added to Ui.

I have tried to reproduce a bug where if you try to invalidate the adapter while we are already loaded more than 2-page requests with ItemKeyedDataSource then there is a jump in the items.

I signed it!


[Bug] Ignoring components doesn't check allowModules?

Referencing https://github.com/marklawlor/tailwindcss-react-native/issues/16:
The ignoring components feature is great, and means we are now able to start fully using this library! But it's not quite there yet for our usage on web. I have made a little patch on our end that makes it usable so we will start to use it! 🎉
I may be missing something, but these are the issues we are having with it, and note this is on web:

isAllowedProgramPath appears to only check allowRelativeModules, and does not check allowModules or blockModules?
allowModules would need to override allowRelativeModules. We have separate paths in the tailwind config for the web/rn modules, so implicitly allowing the web modules defeats the purpose.
blockModules appears to be used in native-visitor but not in web?

Fixed in 0.0.27. Sorry about that must have overlooked it. I've updated the unit tests for web to include these cases

@marklawlor Perfect. Thank you!


events: address possible issues in pubsub

Motivation
There are several issues with pubsub, that could lead to goroutines leak and unnecessary memory allocations.
Found them while getting familiar with the code. If you prefer I can open bugs for each issue separately.
Changes

avoid allocation of the payload in the debug log
allow subscriber to exit if subscriber was closed and send is blocking
test that empty payload will not crash subscriber
add utilities to find the free port and wait until the subscriber is connected
with publisher

Test Plan
unit tests are sufficient
TODO
DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

@antonlerner cant add you as a reviewer for some reason, but please take a look

Q: Is the pubsub code currently used in the node anywhere? I thought we have phased it out in favor of the grpc api? Maybe it is used for some tests only?

@avive This is probably the case. Initially, I thought that this code is extensively used because it was imported everywhere. But it looks like that the subscriber is only initialized with SetupMultiNode, which is used only in a couple of tests and multi node simulation.

bors merge


Positive reward with 4 walls

looking at a wall with 4 eyes while walking into it resulted in a positive reward;

http://mlg.eng.cam.ac.uk/yarin/blog_3d801aa532c1ce.html
That's the > 0.75 threshold for forward reward. With a few eyes missing the walls, the overall proximity drops more it does in most cases, if the agent can get a little bonus for forward at that stage it will take it.
https://github.com/yaringal/DropoutUncertaintyDemos/blob/14fa4689bcf29e280bf3bb5c967f8bf10e530178/convnetjs/rldemo_comparison.js#L368
Generally I've found the threshold still works ok, takes tweaking but is kind of a "this is a doorway you'll accept" vs "that's a little too risky" in the end. Thinking the best bet would be to remove it and punish harder on walls some other way, so the forward bonus can't win out against walls when multiplied by those last few decimal points of the proximity being fed in.

This might work a little better, falling off quickly on the low end, instead of forward reward the instant walls are considered "clear".
if(this.actionix === 0 && proximity_reward > 0.2) forward_reward = 0.1 * Math.sqrt(proximity_reward-0.2);

I have a different task setup, with a goal and less eyes, extra nostril sensors for the goal direction. Random movement scores better than wall avoidance. Initially convergence is "move around the map to keep a decent average" with a mid-range score. Then final convergence is a high score and goal seeking behaviour, hopefully including getting out of traps, corridors and without spinning on the spot.
I'm seeing greedy doing okay learning walls independent of the goal reward, while thompson policy is falling into a local minima trying to cut it a little close with the forward reward, even with that exponent version. Also after halving proximity reward: forward_reward = 0.1 * Math.pow(proximity_reward/2, 2).

Removing the forward reward altogether results in thompson performing much better than greedy.

I'm finding generally that dropout (regardless of uncertainty implemented or not) will become obsessed with any conditional reward which jumps up/down out of nowhere.
For instance halving forward reward for forward turns:
if (this.actionix === 0 || this.actionix === 1 || this.actionix === 2) {
    forward_reward = whatever number;
    if (this.actionix === 1 || this.actionix === 2) {
        forward_reward = forward_reward / 2;
    }
}

Dropout will find itself hard up against a wall, looking along it, exploiting what it can from the half forward reward. Smoothly distributed rewards on the other hand it will be exploited without so much unexpected behavior.


merge from arlac77/template-arlac77-github,arlac77/template-esm-only

.travis.yml

chore(travis): (jobs.include)
chore(travis): add 14.3.0 remove 14.2.0 (jobs.include.node_js)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


MG + MIS Revision

[x] include traceability in terms of module numbers like M1, M2, etc.
[x] The specific technological choices are not really unlikely changes, as needs may change in the future
[x] Hardware hiding module should be more specific, specifically mentioning things like the camera which is very important in your design.
[x]  A few confusing sentence structures.
[x] Generally we use "name : Type", not "Type name" for definition variables and their types (e.g. environment variables). Use \text{} for multi-character variables (e.g. isPermissionGranted) to make them look less weird.
[ ] Some modules do not specify the type of module (e.g. Abstract Data Type, record module, etc).
[ ] You should break up some of these bigger modules by breaking out types like Item, UpdatedItem, etc. into their own modules.
[ ] Try to add code-specific stuff like tests before the end of the term. (For CI/CD; is this alluding to testing pipeline for CI/CD?; any correlation with design doc?)
[ ] I would have liked a bit more detail about problems you ran into. Time and money sure are problems for everyone, but try to be a bit more specific. (Reflection; need revisions for this section?)

SRS Assumptions performance


prefect-sqlalchemy

Description
What's cooking?
This PR adds a recipe for using Prefect with SQL alchemy.
Issue #149
Type of change

[x] New feature (non-breaking change which adds functionality)

New Recipe Checklist

[x] My PR is in the format of Add <project-name> recipe
[x] My recipe is reproducible and explains everything needed to run successfully. If my code has external dependencies, I make mention of them.
[x] My code is easily understandable and/or well-commented.

Hi @sidharth1805, welcome to prefect-recipes 🧑🍳 and congrats on your first contribution! We'll review this very soon 🙂

Thank you @serinamarie waiting to get added 😃

@zzstoatzz Have changed the requested

@ahuang11 Please check now 😃

@ahuang11 removed the os library can we run the workflows now 🙂

Thanks! It looks good to me. Was wondering if we should put this in beginner flows?

@ahuang11 Sure it would be great 🙂

Can I change then?

Yes

@ahuang11 Moved please check now

@sidharth1805 thanks for making these changes, looking good!
one last request from me, since you have log_prints=True on the flow, you don't need it on the tasks within that flow, since the tasks will inherit the log_prints=True setting - so can we take that out of the decorator for each task?

@zzstoatzz Done Please check

@sidharth1805 Thanks for creating this recipe! Please reach out to<EMAIL_ADDRESS>for your swag! 🧢


Feature: Documentation about Rust dependencies

Is your feature request related to a problem? Please describe.
Hello FastStream Team, first of all, thanks for your project and your work.
I am evaluating FastStream with PydanticV2 written in Rust for my project and wanted to confirm whether it includes any Rust extensions or dependencies.
I don't know Rust much {my project on Python - Django DRF}, but as far as I understand with Rust, you have a few options: 1) installing Rust on OS level {not the best option in a containerized environment} 2) Build "on the fly" while Docker container created {minimal build with only necessary parts for current container/app} 3) Just "classical" Rust installation inside of the container (similar as on OS level, but inside of the container}. 4) Python app can include some Rust part as a module/dependency, "built-in" / "embedded".
I want to use option 2, but if Rust in FastStream is already used as option 4, then I don't need to install anything.
TL;DR I am concerned about the necessity of having Rust installed when deploying FastStream in containerized environments.
Could you please provide insights into whether FastStream leverages Rust internally?
Thanks.
Describe the solution you'd like
Adding more information about Rust dependencies in the documentation and quick start.
Describe alternatives you've considered
If Rust is not included, it would be nice to have that option or (which will solve everything else) have a Docker container option.
Additional context
I use Django DRF + React on the frontend with the latest Python and the latest Ubuntu. I use Podman for containerization (it has "backward" combability with Docker and uses the same config files). I plan to use FastStream probably with RabbitMQ as a messaging broker for emailing micro-service (registration, product-related notifications, etc.). I use Prometheus if it's even relevant info (probably will use FastStream also for monitoring-related tasks and/or infrastructure tasks, but not sure right now).

Hello! The FastStream library does not use Rust at all, so no Rust installation is required to work with it.
As for Pydantic v2, while it is partially written in Rust, you generally do not need to install Rust to use it.
Why?
Precompiled binaries: Pydantic v2 is distributed as prebuilt wheels via pip, which include the Rust components already compiled. On most systems, you can install it easily: pip install pydantic
When is Rust needed?

If you’re on an unsupported platform without prebuilt binaries.
If you want to compile Pydantic from source.

For typical environments, neither FastStream nor Pydantic will require you to have Rust installed.

Hello @firstunicorn,
As @Rusich90 mentioned, FastStream library doesn't use Rust. It uses pydantic library.
In your docker container, simply install faststream using pip and it shoudl work without any problem.

Closing this issue.


[Branch 2.10] Fix some OWASP dependency problems.

Motivation
Fix some OWASP dependency problems, the details as below:

#16148
#15829
#15864
#14910

Modifications

Fix some OWASP dependency problems

Verifying this change

[x] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Documentation
Check the box below or label this PR directly.
Need to update docs?

[ ] doc-required
(Your PR needs to update docs and you will update later)

[x] doc-not-needed
(Please explain why)

[ ] doc
(Your PR contains doc changes)

[ ] doc-complete
(Docs have been already added)

I found we still have CVE in branch-2.10.  But don't find any related fix at master.
mariadb-java-client-2.7.5.jar
    <cve>CVE-2022-27444</cve>
    <cve>CVE-2022-27446</cve>
    <cve>CVE-2022-27449</cve>
    <cve>CVE-2022-27451</cve>
    <cve>CVE-2022-27452</cve>
    <cve>CVE-2022-27455</cve>
    <cve>CVE-2022-27457</cve>

These CVEs are about the server and they do not impact the client.

Another exception
Error:  pulsar-presto-distribution.tar.gz: pulsar-presto-distribution.tar: aether-connector-asynchttpclient-1.13.1.jar: CVE-2017-14063, CVE-2021-43138
Error:  pulsar-presto-distribution.tar.gz: pulsar-presto-distribution.tar: async-http-client-1.6.5.jar: CVE-2021-43138
Error:  pulsar-presto-distribution.tar.gz: pulsar-presto-distribution.tar: logback-core-1.2.3.jar: CVE-2021-42[55](https://github.com/apache/pulsar/runs/7089411725?check_suite_focus=true#step:8:56)0
Error:  pulsar-presto-distribution.tar.gz: pulsar-presto-distribution.tar: maven-compat-3.0.5.jar: CVE-2021-26291
Error:  pulsar-presto-distribution.tar.gz: pulsar-presto-distribution.tar: maven-core-3.0.5.jar: CVE-2021-26291
Error:  pulsar-presto-distribution.tar.gz: pulsar-presto-distribution.tar: maven-settings-3.0.5.jar: CVE-2021-26291
Error:  pulsar-presto-distribution.tar.gz: pulsar-presto-distribution.tar: netty-3.10.6.Final.jar: CVE-2019-16869, CVE-2021-37136, CVE-2021-37137, CVE-2019-20445, CVE-2019-20444
Error:  pulsar-presto-distribution.tar.gz: pulsar-presto-distribution.tar: okhttp-3.14.9.jar: CVE-2021-0341
Error:  pulsar-presto-distribution.tar.gz: pulsar-presto-distribution.tar: plexus-utils-2.0.6.jar: CVE-2017-1000487
Error:  pulsar-presto-distribution.tar.gz: pulsar-presto-distribution.tar: presto-cli-332.jar: CVE-2020-15087

Why doesn't the master branch report these problems?  : (


[Feature]: Redis / Elastic search plugin - DS schema not being displayed

Is there an existing issue for this?

[X] I have searched the existing issues

Description
The DB schema for Redis  and Elastic search dbs is not being displayed.
Steps To Reproduce

Connect to Redis / Elastic Search DS
Create a new query
Note that on the left entity explorer, on expanding the Redis DS, the DB schema is not displayed.

Public Sample App
No response
Environment
Release
Issue video log
No response
Version
Cloud

I can work on this. Please assign !


⚠ Bofrost.de has degraded performance

In c814adf, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 988 ms

Resolved: Bofrost.de performance has improved in 0556d90.


[JAVA-961] Standardize packages in spring security modules

Using another PR : https://github.com/eugenp/tutorials/pull/8921


Fix error handling in float unboxing

This is split from #5113.

@eric-wieser thank you for your patience on this. #5113 is now merged. Since this hasn't been reviewed yet, I think it could be rebase onto main and converted from draft.

Rebased, but I think this was failing in CI and I didn't have time to work out why. My hunch at the time was that there was a bug elsewhere.

I am picking this up again.

/azp run

Locally this fails for me with:
typ = float64, obj = <ir.LoadInstr '.63' of type 'i8*', opname 'load', operands [<ir.AllocaInstr '.49' of type 'i8**', opname 'alloca', operands ()>]>
c = _UnboxContext(context=<numba.core.cpu.CPUContext object at 0x169f9d1e0>, builder=<llvmlite.ir.builder.IRBuilder object at 0x169f9f550>, pyapi=<numba.core.pythonapi.PythonAPI object at 0x169f66620>)

    @unbox(types.Float)
    def unbox_float(typ, obj, c):
        is_error_ptr = cgutils.alloca_once_value(c.builder, cgutils.false_bit)
        float_ty = c.context.get_argument_type(typ)
        float_val = cgutils.alloca_once(c.builder, float_ty)
        with ExitStack() as stack:
            fobj = c.pyapi.number_float(obj)
>           with early_exit_if_null(c.builder, stack, fobj):
E           NameError: name 'early_exit_if_null' is not defined

numba/core/boxing.py:81: NameError

Following patch fixes:
diff --git i/numba/core/boxing.py w/numba/core/boxing.py
index 5ef82359ff..2abee35c38 100644
--- i/numba/core/boxing.py
+++ w/numba/core/boxing.py
@@ -78,14 +78,14 @@ def unbox_float(typ, obj, c):
     float_val = cgutils.alloca_once(c.builder, float_ty)
     with ExitStack() as stack:
         fobj = c.pyapi.number_float(obj)
-        with early_exit_if_null(c.builder, stack, fobj):
+        with cgutils.early_exit_if_null(c.builder, stack, fobj):
             # for debugging
             c.builder.store(c.context.get_constant(float_ty, float('nan')), float_val)
             c.builder.store(cgutils.true_bit, is_error_ptr)

         dbval = c.pyapi.float_as_double(fobj)
         c.pyapi.decref(fobj)
-        with early_exit_if(c.builder, stack, c.pyapi.c_api_error()):
+        with cgutil.early_exit_if(c.builder, stack, c.pyapi.c_api_error()):
             # for debugging
             c.builder.store(c.context.get_constant(float_ty, float('nan')), float_val)
             c.builder.store(cgutils.true_bit, is_error_ptr)

Locally this fails for me with:
typ = float64, obj = <ir.LoadInstr '.63' of type 'i8*', opname 'load', operands [<ir.AllocaInstr '.49' of type 'i8**', opname 'alloca', operands ()>]>
c = _UnboxContext(context=<numba.core.cpu.CPUContext object at 0x169f9d1e0>, builder=<llvmlite.ir.builder.IRBuilder object at 0x169f9f550>, pyapi=<numba.core.pythonapi.PythonAPI object at 0x169f66620>)

    @unbox(types.Float)
    def unbox_float(typ, obj, c):
        is_error_ptr = cgutils.alloca_once_value(c.builder, cgutils.false_bit)
        float_ty = c.context.get_argument_type(typ)
        float_val = cgutils.alloca_once(c.builder, float_ty)
        with ExitStack() as stack:
            fobj = c.pyapi.number_float(obj)
>           with early_exit_if_null(c.builder, stack, fobj):
E           NameError: name 'early_exit_if_null' is not defined

numba/core/boxing.py:81: NameError

This was an issue on CI too, I created a commit and pushed it to the branch for this PR.

It's now failing with:

  File "/home/vsts/work/1/s/numba/np/ufunc/dufunc.py", line 175, in add
    return self._compile_for_argtys(args, return_type)
  File "/home/vsts/work/1/s/numba/np/ufunc/dufunc.py", line 227, in _compile_for_argtys
    dtypenums, ptr, env = ufuncbuilder._build_element_wise_ufunc_wrapper(
  File "/home/vsts/work/1/s/numba/np/ufunc/ufuncbuilder.py", line 206, in _build_element_wise_ufunc_wrapper
    info = build_ufunc_wrapper(library, ctx, fname, signature,
  File "/home/vsts/work/1/s/numba/np/ufunc/wrappers.py", line 214, in build_ufunc_wrapper
    build_obj_loop_body(
  File "/home/vsts/work/1/s/numba/np/ufunc/wrappers.py", line 118, in build_obj_loop_body
    return _build_ufunc_loop_body_objmode(load, store, context, func, builder,
  File "/home/vsts/work/1/s/numba/np/ufunc/wrappers.py", line 64, in _build_ufunc_loop_body_objmode
    store(retval)
  File "/home/vsts/work/1/s/numba/np/ufunc/wrappers.py", line 111, in store
    native = pyapi.to_native_value(signature.return_type, retval)
  File "/home/vsts/work/1/s/numba/core/pythonapi.py", line 1431, in to_native_value
    return impl(typ, obj, c)
  File "/home/vsts/work/1/s/numba/core/boxing.py", line 83, in unbox_float
    c.builder.store(c.context.get_constant(float_ty, float('nan')), float_val)
  File "/home/vsts/work/1/s/numba/core/base.py", line 516, in get_constant
    return self.get_constant_generic(None, ty, val)
  File "/home/vsts/work/1/s/numba/core/base.py", line 505, in get_constant_generic
    impl = self._get_constants.find((ty,))
  File "/home/vsts/work/1/s/numba/core/base.py", line 45, in find
    out = self._find(sig)
  File "/home/vsts/work/1/s/numba/core/base.py", line 54, in _find
    raise errors.NumbaNotImplementedError(f'{self}, {sig}')
numba.core.errors.NumbaNotImplementedError: <numba.core.base.OverloadSelector object at 0x7f05e2830eb0>, (<<class 'llvmlite.ir.types.DoubleType'> double>,)

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

Note to self: this would cleanly rebase onto master..

E   - [1.0, 2.0, 0.0, 2.0, 0.0, 2.0]
E   + [1, 2, 0, 3, 0, 4]

This is the error I was originally seeing when I left this; I guess the other errors were caused by a bad rebase on my part.
My memory of this is that the test really is checking the right thing, and there is a bug here; but I never wrote down why...

What seems to be happening is that after the first error, the ufunc loop seems to skip doing any computation, and somehow just repeats the value it calculated before the first error. I think this is a numba issue not a numpy one.

E   - [1.0, 2.0, 0.0, 2.0, 0.0, 2.0]
E   + [1, 2, 0, 3, 0, 4]

This is the error I was originally seeing when I left this; I guess the other errors were caused by a bad rebase on my part.
My memory of this is that the test really is checking the right thing, and there is a bug here; but I never wrote down why...

It's strange to me, because out is of type float64:
(Pdb) out.dtype
dtype('float64')

What seems to be happening is that after the first error, the ufunc loop seems to skip doing any computation, and somehow just repeats the value it calculated before the first error. I think this is a numba issue not a numpy one.

right, I understand, the second and third 2.0 should be 3.0 and 4.0, the sqrt of 9 and 16.

So, the failure should look like:
numba/tests/npyufunc/test_errors.py:54: in check_ufunc_raise
    self.assertEqual(list(out), [1.0, 2.0, 0.0, 3.0, 0.0, 4.0])
E   AssertionError: Lists differ: [1.0, 2.0, 0.0, 2.0, 0.0, 2.0] != [1.0, 2.0, 0.0, 3.0, 0.0, 4.0]
E
E   First differing element 3:
E   2.0
E   3.0
E
E   - [1.0, 2.0, 0.0, 2.0, 0.0, 2.0]
E   ?                 ^         ^
E
E   + [1.0, 2.0, 0.0, 3.0, 0.0, 4.0]
E   ?

Note to self: this would cleanly rebase onto master..

but that doesn't fix any issues.

@eric-wieser is it possible that this had been broken before and is unrelated to the code in this PR? (The copying of the first value issue).

@eric-wieser is it possible that this had been broken before and is unrelated to the code in this PR? (The copying of the first value issue).

Probably not, as the test passes on main.

After an OOB conversation with @stuartarchibald -- I changed the type of the nan to be of a Numba type, not a NumPy type:
diff --git i/numba/core/boxing.py w/numba/core/boxing.py
index de2e0ade7a..4f0aaafe8a 100644
--- i/numba/core/boxing.py
+++ w/numba/core/boxing.py
@@ -80,14 +80,14 @@ def unbox_float(typ, obj, c):
         fobj = c.pyapi.number_float(obj)
         with cgutils.early_exit_if_null(c.builder, stack, fobj):
             # for debugging
-            #c.builder.store(c.context.get_constant(float_ty, float('nan')), float_val)
+            c.builder.store(c.context.get_constant(typ, float('nan')), float_val)
             c.builder.store(cgutils.true_bit, is_error_ptr)

         dbval = c.pyapi.float_as_double(fobj)
         c.pyapi.decref(fobj)
         with cgutils.early_exit_if(c.builder, stack, c.pyapi.c_api_error()):
             # for debugging
-            #c.builder.store(c.context.get_constant(float_ty, float('nan')), float_val)
+            c.builder.store(c.context.get_constant(typ, float('nan')), float_val)
             c.builder.store(cgutils.true_bit, is_error_ptr)

         if typ == types.float32:

This then does interesting things to the test:
numba/tests/npyufunc/test_errors.py:53: in check_ufunc_raise
    self.assertEqual(list(out), [1.0, 2.0, 0.0, 3.0, 0.0, 4.0])
E   AssertionError: Lists differ: [1.0, 2.0, 0.0, nan, 0.0, nan] != [1.0, 2.0, 0.0, 3.0, 0.0, 4.0]
E
E   First differing element 3:
E   nan
E   3.0
E
E   - [1.0, 2.0, 0.0, nan, 0.0, nan]
E   ?                 ^^^       ^^^
E
E   + [1.0, 2.0, 0.0, 3.0, 0.0, 4.0]
E   ?

I wrote the following test to look into this:
 💣 zsh» cat debug_8316.py                                                                                :(
import numpy as np
import pytest
from numba import vectorize

def sqrt(val):
    if val < 0.0:
        raise ValueError('Value must be positive')
    return val ** 0.5

def run(lis):
    arr = np.array(lis, dtype=np.float64)
    f = vectorize(['float64(float64)'], forceobj=True)(sqrt)
    out = np.zeros_like(arr)
    if any(arr < 0):
        try:
            f(arr, out)
        except ValueError as ve:
            assert 'Value must be positive' in str(ve)
    else:
        f(arr, out)
    return out

all_expected = (
    ([1], [1.0,]),                 # singleton positive
    ([-1], [0.0,]),                # singleton negative
    ([1, 1], [1.0, 1.0]),          # two positive
    ([1, -1], [1.0, 0.0,]),        # one positive, one negative
    ([-1, 1], [0.0, 1.0,]),        # one negative one positive
    ([-1, -1], [0.0, 0.0,]),       # two negative
    ([1, 1, 1], [1.0, 1.0, 1.0]),  # all positive
    ([1, 1, -1], [1.0, 1.0, 0.0]), # negative at end
    ([1, -1, 1], [1.0, 0.0, 1.0]), # negative in middle
    ([1, 4, -2, 9, -1, 16], [1.0, 2.0, 0.0, 3.0, 0.0, 4.0]), # original case
)

@pytest.mark.parametrize("test_input, expected_output", all_expected)
def test(test_input, expected_output):
    assert list(run(test_input)) == expected_output

And it prints:
========================================================================================================== FAILURES ===========================================================================================================
_____________________________________________________________________________________________ test[test_input4-expected_output4] ______________________________________________________________________________________________

test_input = [-1, 1], expected_output = [0.0, 1.0]

    @pytest.mark.parametrize("test_input, expected_output", all_expected)
    def test(test_input, expected_output):
>       assert list(run(test_input)) == expected_output
E       assert [0.0, nan] == [0.0, 1.0]
E         At index 1 diff: nan != 1.0
E         Use -v to get more diff

debug_8316.py:42: AssertionError
_____________________________________________________________________________________________ test[test_input8-expected_output8] ______________________________________________________________________________________________

test_input = [1, -1, 1], expected_output = [1.0, 0.0, 1.0]

    @pytest.mark.parametrize("test_input, expected_output", all_expected)
    def test(test_input, expected_output):
>       assert list(run(test_input)) == expected_output
E       assert [1.0, 0.0, nan] == [1.0, 0.0, 1.0]
E         At index 2 diff: nan != 1.0
E         Use -v to get more diff

debug_8316.py:42: AssertionError
_____________________________________________________________________________________________ test[test_input9-expected_output9] ______________________________________________________________________________________________

test_input = [1, 4, -2, 9, -1, 16], expected_output = [1.0, 2.0, 0.0, 3.0, 0.0, 4.0]

    @pytest.mark.parametrize("test_input, expected_output", all_expected)
    def test(test_input, expected_output):
>       assert list(run(test_input)) == expected_output
E       assert [1.0, 2.0, 0.0, nan, 0.0, nan] == [1.0, 2.0, 0.0, 3.0, 0.0, 4.0]
E         At index 3 diff: nan != 3.0
E         Use -v to get more diff

debug_8316.py:42: AssertionError
=================================================================================================== short test summary info ===================================================================================================
FAILED debug_8316.py::test[test_input4-expected_output4] - assert [0.0, nan] == [0.0, 1.0]
FAILED debug_8316.py::test[test_input8-expected_output8] - assert [1.0, 0.0, nan] == [1.0, 0.0, 1.0]
FAILED debug_8316.py::test[test_input9-expected_output9] - assert [1.0, 2.0, 0.0, nan, 0.0, nan] == [1.0, 2.0, 0.0, 3.0, 0.0, 4.0]

So, this seems to indicate, that if negative values are mixed with positive ones and if the negative value is not the last value, then somehow things "go wrong".


Reformat source code for consistent use of whitespace

At a minimum we'd have to agree on:
Use tab characters or spaces  (spaces)
Tab/indent size  (2 or 4)
Space before parens  (1)
Space around operators  (1)
Space before left brace  (1)
Space before keywords  (1)
Space in ternary operator  (1)
Space after comma in type arguments  (1)
Space after comma  (1)
Space after type cast  (1)
Else on new line  (Yes)
Right margin  (120 columns)
My preferences in parens.  I'd suggest doing this with a source code formatter all in one commit after the next release.

+1 on all except for right margin where my pref is 80.

Closing as WontFix


Report to pdf to client

It would be nice if there could be a way to sent out automatic reports (in .pdf) of the keywords position to an email address. For example per group or keyword. In that way i can send out statistics of the keyword position and competitor position to my peer or customer.

I am also desperate for this feature! +1

One way is to use MySQL database, understand the structure and generate your own reports.


[IQE] : Code folding shortcuts not working on Win 10 platform

Steps to Reproduce:
1 Open Brackets on Win 10
2 open any file eg index.html
3 Try "Collapse All" via shortcut "ALT+1"
Result :
the file is not collapsed
ENV: Brackets Release 1.3 build 1.3.0-16022
Platform : Win 10 Eng

@rawat11 Can you share the error if any on developer tools console (Go to Debug > Show Developer Tools)

@prafulVaishnav : It is an intermittent issue, There are no errors related to it in the  dev tools console.
Currently the shortcuts are working.
But the code folding icons are not getting visible for php code while it picks for html

@prafulVaishnav Yes, its working fine


correct 2 corrupted "t" via copy&paste, fixes #367

This is a good catch and I am pretty surprised that this was only observed on Windows.

Totally strange, never hit on such a bug before. There was a "ghost-char" between the "t" and the (" in the two avm_wait(
(as an off-topic note: i just evaluate EOS, and am very disappointed by its low usability. The missing return-values make working with EOS-style-CPP quite inconvenient. Be aware that AVM outperforms EOS in context of convenience. Yet, you need to work on usability of tools/docs, its very important).

Yeah, most tools hide it but vim does display it (even the GitHub diff doesn't show it).  Reminds me of the old days of BBEdit and its highly useful "zap gremlins" feature.
We had some fairly public AVM testing, this past weekend, and that is also what we found.  People were generally happy with the system but there are gaps in our docs and some rough edges on our tools.  So yes, we are aware that this is an area where we need more work.
Thanks for letting us know your sense of this.

"zap gremlins" feature

haha! fits with "ghost-char"!

So yes, we are aware that this is an area where we need more work.

And you need to be aware of another thing:
This work is something that needs to done by a person which is a natural (in simplifying systems/docs), and which does not know the (AION AVM) system very well (yet).


Don't create home for system accounts

Fixes users irc and systemd-resolve being changed after reboot,
as their home directory is in /run.
Won't create /home/{syslog,ntp} any longer (Ubuntu).

Thank you. :)


feature: allow special characters in label values and length > 63

getting this error when i try to save s3 path argument with slashes into a label:
a valid label must be an empty string or consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue',  or 'my_value',  or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])?') Invalid
or
"must be no more than 63 characters, metadata.labels: Invalid value:"

Not a bug.
https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set


modernizing the multiformat page

@pm-harshad-mane pointed out that this page was many years outdated. Put some lipstick on it...

@bretg Can we add link to the bidders listing page for PBS : https://docs.prebid.org/dev-docs/pbs-bidders.htm and PrebidJS: https://docs.prebid.org/dev-docs/bidders.html this will be helpful to someone trying to understand...

@bretg I have added links to Bidders documentation for both PBJS and PBS, please review once and push to production.


Spotbugs reports don't show violations

Description
When Spotbugs violations are found by the Maven plugin in the chunk workflow, the SpotBugs report that's published to GitHub still shows no violations.
Steps to reproduce

Introduce a violation to the code, eg. a known null-pointer dereference (see example workflow)
Push to GitHub
Wait for chunk workflow to run
Check SpotBugs report published to the first workflow run for that commit
See no violations in the report, but a failed chunk workflow run

Expected behaviour
The violations should show up in the SpotBugs report that's published to GitHub as a check.
Screenshots/Logs
See this example workflow run where this happened:
https://github.com/gchq/sleeper/actions/runs/5609467994/job/15197143883
https://github.com/gchq/sleeper/runs/15197294860
Background
The GitHub action we're using hasn't had a release in some time:
https://github.com/jwgmeligmeyling/spotbugs-github-action
The code that's in the main branch hasn't been released, but it hasn't had any changes since September 2021.

This works now as we converted the workflows to use Maven's reporting:

https://github.com/gchq/sleeper/issues/1061


Buffered versus direct drawing

At the lowest level, the Screen class enforces a refresh() before it will draw anything.  This is irritating for people who just want to do some simple drawing.  Consider providing 2 modes of operation for the class:

Buffered - bascially the current mode, but fully enforcing double buffering.
Direct - which will draw directly and so have no refresh required.

Some interesting decisions need to be made in both cases:

Whether to clear the screen or not at start up?  Possibly direct mode should leave that up to the user?

Also may be limited by what I can do to keep mouse support (through ncurses).  See http://stackoverflow.com/questions/4772061/how-do-i-use-getch-from-curses-without-clearing-the-screen

Whether to expose the current cursor position or not?  Makes less sense in buffered mode.
Whether to allow screen character look-ups?  Doesn't makemuch sense if the screen isn't reset to a known state (i.e. cleared) at start-up.

It feels like these may behighly related, but ultimately different class implentations...

Requires new API that is being proposed for v2.0

Might need current cursor position.  Looks like this uses u6-7.  See http://unix.stackexchange.com/questions/239271/parse-terminfo-u6-string

Windows cursor pos from https://msdn.microsoft.com/en-us/library/windows/desktop/ms683171(v=vs.85).aspx

Also need to think about relative movement inthis environment - e.g. start of line, up/down one line, etc.  That may be possible with a print method instead of print_at.  But if I do that, can I still support renderers using paint?  Maybe the correct API is to provide no print_at for direct mode and to make paint work from the current cursor pos?

It appears that I can only really use setupterm() in curses and so have to limit available function (e.g. no input at all).  That means an API like:

print_at
centre
palette
paint
highlight
dimensions (using "cols" and "lines" from terminfo)
is_visible

Plus some other methods that might now make sense if I can break out the classes neatly enough:

print (with relative positions [see cup, hpa and vpa] and colours?)
cursor movement (with relative motion? - see cub1, cuf1, cuu1, cud1)
Possibly print_renderer to simplify use of such things...
hide cursor (using "civis"/"cnorm")
fullscreen (using "smcup"/"rmcup")
clear (using "clear")
get_current_pos (using "u6"/"u7")


Translation submissions to the git repository are paused

I have one of my plugins listed in the translation tool and keep getting outdated translation updates because the tool uses an old code base as a reference. The settings page mentions that there are 3 errors (whatever that may mean) and translation submissions are paused. Yet I do get new translation submissions, it's just that they are no longer relevant.
What could be a reason for that?

Then there have been errors, or for example in the simple parser of the tool or in its use of git that created errors in the past. After 3 errors it stops trying. We can manually reset the tool. Not sure when I can do that. If it takes too long, please remember me.

Thanks for the reset.


Trunk Check functionality

Hi, I just wondered about the behaviour of the action when it runs. Trunk Check runs with a number of other actions in my repository. It's running fine, spotting issues where they arise and outputting the results. However, where it outputs the results is a little confusing. It appears to attach to another workflow as shown below.
I have the following trunk check workflow file:
name: Trunk Check
on: pull_request

jobs:
  main:
    name: Trunk Check
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v2
      - name: Cache Linters/Formatters
        uses: actions/cache@v2
        with:
          path: ~/.cache/trunk
          key: trunk-${{ runner.os }}
      - name: Trunk Check
        uses<EMAIL_ADDRESS>
And the workflow outputs can been seen from the "Check" tab in the pull request:

Clicking on "Trunk Check" takes me to Github Actions, where I can see the workflow logs.
"Trunk Check" Is also shown under my "semantic-release" check
Clicking on "Trunk Check" here, stays on the pull request checks tab and displays the trunk check output:

For clarify, here is my semanitc-release workflow file:
name: semantic-pull-request
on:
  pull_request_target:
    types:
      - opened
      - edited
      - synchronize

jobs:
  main:
    name: Validate PR title
    runs-on: ubuntu-latest
    steps:
      - uses: amannn/action-semantic-pull-request@v3
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

As you can see it doesn't mention running "Trunk Check" anywhere in this file, but for some reason the results of the Trunk Check workflow are added to this workflow.
So, nothing is "broken" as such, everything works. I'm just a bit confused by this behaviour and if it is expected?
Cheers
Chris

Hi Chris, unfortunately, this is a GitHub bug, there's basically a race when you run multiple workflows on the same branch/commit: https://github.community/t/github-actions-status-checks-created-on-incorrect-check-suite-id/16685
We can't do anything about it until they fix it ☹ - but as soon as they do, we will!


Sorting is not working?

Hi,
I'm trying to get the 10 latest launches. I'm sending the following request (here I've set the limit to 1 to demonstrate the issue).
POST https://api.spacexdata.com/v5/launches/query

{
  "options": {
    "limit": 1,
    "sort": "asc"
  }
}

Whether I send asc or desc in the sort parameter, I still get the same result.
{
  "docs": [
    {
      "fairings": {
        "reused": false,
        "recovery_attempt": false,
        "recovered": false,
        "ships": []
      },
      "links": {
        "patch": {
          "small": "https://images2.imgbox.com/3c/0e/T8iJcSN3_o.png",
          "large": "https://images2.imgbox.com/40/e3/GypSkayF_o.png"
        },
        "reddit": {
          "campaign": null,
          "launch": null,
          "media": null,
          "recovery": null
        },
        "flickr": {
          "small": [],
          "original": []
        },
        "presskit": null,
        "webcast": "https://www.youtube.com/watch?v=0a_00nJ_Y88",
        "youtube_id": "0a_00nJ_Y88",
        "article": "https://www.space.com/2196-spacex-inaugural-falcon-1-rocket-lost-launch.html",
        "wikipedia": "https://en.wikipedia.org/wiki/DemoSat"
      },
      "static_fire_date_utc": "2006-03-17T00:00:00.000Z",
      "static_fire_date_unix":<PHONE_NUMBER>,
      "net": false,
      "window": 0,
      "rocket": "5e9d0d95eda69955f709d1eb",
      "success": false,
      "failures": [
        {
          "time": 33,
          "altitude": null,
          "reason": "merlin engine failure"
        }
      ],
      "details": "Engine failure at 33 seconds and loss of vehicle",
      "crew": [],
      "ships": [],
      "capsules": [],
      "payloads": [
        "5eb0e4b5b6c3bb0006eeb1e1"
      ],
      "launchpad": "5e9e4502f5090995de566f86",
      "flight_number": 1,
      "name": "FalconSat",
      "date_utc": "2006-03-24T22:30:00.000Z",
      "date_unix":<PHONE_NUMBER>,
      "date_local": "2006-03-25T10:30:00+12:00",
      "date_precision": "hour",
      "upcoming": false,
      "cores": [
        {
          "core": "5e9e289df35918033d3b2623",
          "flight": 1,
          "gridfins": false,
          "legs": false,
          "reused": false,
          "landing_attempt": false,
          "landing_success": null,
          "landing_type": null,
          "landpad": null
        }
      ],
      "auto_update": true,
      "tbd": false,
      "launch_library_id": null,
      "id": "5eb87cd9ffd86e000604b32a"
    }
  ],
  "totalDocs": 148,
  "offset": 0,
  "limit": 1,
  "totalPages": 148,
  "page": 1,
  "pagingCounter": 1,
  "hasPrevPage": false,
  "hasNextPage": true,
  "prevPage": null,
  "nextPage": 2
}

Is there something wrong with sorting? Or am I doing something wrong?

When specifying the sort parameter, you need to pass the field(s) which you want the query result to be sorted by. The sort parameter accepts either an object or a string. Say we want to get the 10 latest launches. To do this, we can sort the data in descending order by one of several fields; I will choose the flight_number field for this example.
If I were to pass the sort value as an object, it would look like:
{
  "options": {
    "limit":10,
    "sort": {
      "flight_number":"desc"
    }
  }
}

If I were to pass the sort value as a string, it would look like (note the '-' preceding flight_number means to sort in descending order):
{
  "options": {
    "limit":10,
    "sort":"-flight_number"
  }
}

Hope this helps.

Thank you 🙏🏼


Configuration for rule "import/internal-regex" is invalid

An equivalent error also occurs for import/external-module-folders.

Error: .eslintrc:
Configuration for rule "import/internal-regex" is invalid:
Severity should be one of the following: 0 = off, 1 = warn, 2 = > error (you passed '"^my-namespace"').

In our .eslintrc we have the rule like:
  "import/internal-regex": "^my-namespace",

and if we try like this we just get a different issue:
  "import/internal-regex": [1, "^my-namespace"],

1:1   error    Definition for rule 'import/internal-regex' was not found
1:1   error    Definition for rule 'import/external-module-folders' was not found

Same issue if we use .eslintrc.js instead of .eslintrc.


B-Lazy doesn't fire sometimes when page has been visited

Not sure what it happening, but in Chrome (35.0.1916.114) on a Mac OSX (10.9.2), visiting my site that I've already visited, and possibly cached, none of the b-lazy elements change, nor do the success or error events fire.
If I press refresh, everything runs normally.  If I go up to the location bar and press enter it will load fine too.  Just sometimes when opening a new tab and typing in the url and hitting enter.
Wondering if anyone else is experiencing this, and/or it is a b-lazy issue, or something else.
FYI, here is my call to b-lazy:
var bLazy = new Blazy({
    selector: '.b-lazy',
    offset: 180, // Loads images 180px before they're visible
    success: function(ele){
        // Image has loaded
        // Do your business here
        console.log('img loaded');
    },
    error: function(ele, msg){
        console.log('b-lazy error:' + msg);
        console.log(ele);
        if(msg === 'missing'){
            // Data-src is missing

        }
        else if(msg === 'invalid'){
            // Data-src is invalid
        }
    }
});

Here is where I'm experiencing the issue: http://staging.aspirebeverages.com (even clicking on this link for me is a case when it sometimes does not fire)
Any ideas?  Thanks in advance!

Same problem here. I did a temporary fix by initializing it like this:
blazy = new Blazy();
setTimeout(blazy.revalidate, 100);

Please try the new version, 1.3.0. It should fix it.

Already done and yes seems to work :)
dinbror<EMAIL_ADDRESS>schrieb am Fr., 23. Jan. 2015 12:57:

Please try the new version, 1.3.0. It should fix it.
—
Reply to this email directly or view it on GitHub
https://github.com/dinbror/blazy/issues/24#issuecomment-71183834.

Experiencing this problem on the 1.3.1 version, using the revalidate temp fix for now

Hey Thomas.
Can you elaborate a bit? How do you reproduce it? Do you have a live example?

I will try to extract a example from the project I'm working on (still in development) and put this online next week.

I also still have the same issue on the 1.3.1 version. It happens on Chrome on PC when you refresh a page either with F5 or with the browser button for refresh. It won't replace the images that are in the viewport. All other images that are not in view work as expected.

In my case: the first couple of images in the dom load, but not all of the visible ones, as soon as I scroll they all load.

@landykos: do you have a live example?
I expect that you either initialize blazy before dom is ready or a lot of repainting is done

@dinbror currently only on local dev right now. I'll make sure and circle back once I have something up and running public facing.
Thanks!

In my case it had nothing to do with blazy but the combination with the packery layout plugin. I changed my code to trigger blazy after the layout algoritm is finished, that's moment to decide which images are within the viewport (and need to be loaded). This fixed my issue.

I had the same problem in Safari due to the load cache it uses when entering the URL or using the back button. Adding this jQuery on page load fixed it.
$(window).bind("pageshow", function(event) {
if (event.originalEvent.persisted) {
window.location.reload()
}
});
This was while using v1.4.0.

This issue still exists on v1.8.0. When I press back button in newest Chrome on Galaxy S6 lazy load doesn't work until I scroll a bit.

Yep,
I'm using version 1.8.2 and same problem is still there.
Only loads images for first time and doesn't work on cached pages.

hey @akashdeepkanojia.
Do you also see the issue on my examples page (http://dinbror.dk/blazy/examples/)?
What browser and device do you see the issue on?

I'm using OS X El Capitan
Chrome Version 56.0.2924.87 (64-bit)
Your example is working just fine.
This is my code:
var bLazy = new Blazy({      selector: '.container img',      success: function(element){ 	var parent = element.parentNode; 	parent.className = parent.className.replace(/\bloading\b/,'');     },     error: function(err){     	console.log('Error loading image.');     	console.log(err);     } });
If I add the following code at the end then my example works fine too:
setTimeout(bLazy.revalidate, 100);
What could be the issue?

Same issue here as @adkanojia. I'm on macOS Sierra, Safari 11.0.
Examples also working fine, but the "fix" setTimeout(bLazy.revalidate, 100); is not working.

I'm using this library in  combination with the Drupal integration (drupal.org/project/blazy) and can confirm this problem. Once I use minification of JS assets, this problem occurs. Without minification, it does not occur. I guess it's some sort of a timing problem.

I have the same issue with blazy, even sometimes setimeout for less than 500ms doesn't work, it turns out it's a body loading issue, so I added this line on the body element: <body onload="new Blazy();">, and it worked perfectly


python3

b12439f
Proposed change
Mothulity should be written in python3

The code refactoring should be as simple as:
[] running 2to3
[] adding print_function from future if really want to keep python2 support
[] changing the mothulity.yaml file content

Changing mothulity.yaml to more general list of dependencies raises little hell.
recent warning from the latest numpy (1.15) thrown just on import (calling help page)
_bootstrap.py:219: RuntimeWarning: numpy.dtype size changed, may indicate binary incompatibility. Expected 96, got 88

Specifing matplotlib below 2.0.0 solved it.


OSM SVGs

Tried out some SVGs that I exported from OpenStreetMaps (click share button and set the SVG format) and the Pathfinder server failed in some unknown way. Getting a highly complicated OSM SVG map to render smoothly would make a great demo.

I think there's a hard limit somewhere on SVG size, possibly just in the file uploading code.
I tried to run the demo on some of the test images from http://w3.impa.br/~diego/projects/GanEtAl14/, because that paper/site has images and timings for other vector graphics rendering methods to compare with, but it barfed on all but the smaller examples.

Yeah, there's a size limit. I should probably make the limit to something very large in local builds and only enforce the low limit on the public facing Web site.

I've hopefully made it easy to override the size limit now. One OSM I tried now panics in the stroking code, but I'd rather open specific followup issues about that.


core/cli: update vendored completion files

update the vendored completion files (click has since pushed
some updates that change the output of the completions)
update required click version to 8.1
so we dont regenerate the vendored completions
wrong in the future

ERROR: Could not install packages due to an OSError: [Errno 2] No such file or directory: '/home/runner/work/HPI/HPI/.tox/mypy-misc/lib/python3.8/site-packages/charset_normalizer-3.2.0.dist-info/top_level.txt'
Hm, may have been a race condition with the --parallel flag? Could retry before investigating further

Sorry, forgot to actually rerun the CI! Looks good now, seems like it's the --parallel flag indeed


Without this change, all belongsTo relationships are never persistet, because they are ignored (condition on line 63. the key in input is "belongsto_relationship", but $row->field is target column name, i.e. user_id.

I'm sorry, I don't understand what the issue is. Can you please elaborate?

You removed the condition check implemented here

Yes, I did, as it is not necessary anymore. The condition's purpose was to attemt to fix belongsTo relationships not working. But the fix didn't work for all use cases of belongsTo.
My proposed change fixes it for all belongsTo relationship by performing the $row->field mutation before checking if the parameter is present in request - the mutation was taking place too late for belongsTo relationship to work. Now it happens just in time.

The change to
if (!$request->hasFile($row->field) && !$request->has($row->field) && $row->type !== 'checkbox') {
    continue;
}

will break the user role issue again #2451, it is an exception to how the relation should behave.
It will also break resetting belongsToMany relationships, they need to be set to null further down in the loop, they can't continue.
Can I suggest leaving the user role exception there? Something like
if (!$request->hasFile($row->field) && !$request->has($row->field) && $row->type !== 'checkbox') {
    // if the field is a belongsToMany relationship, don't remove it
    // if no content is provided, that means the relationships need to be removed
    if (isset($options->type) && $options->type !== 'belongsToMany') {
        continue;
    }
    // if the field is related to user role, skip it
    if ($row->field === 'user_belongstomany_role_relationship' || $row->field === 'role_id') {
        continue;
    }
}

but keeping the other change you made.

@jpolive Are you sure that it will break user roles? In an application where this patch has been applied all relationships work. That includes changing user roles - I just checked that.
That exception there is necessary, to fix user roles when belongsTo relationships are broken. This fix fixes broken belongsTo relationships, so it fixes the user role issue.
Can you please elaborate on

It will also break resetting belongsToMany relationships, they need to be set to null further down in the loop, they can't continue.
?

How can moving a condition 2 statements up break something further down the loop?

@hojgr your right, but on a belongsToMany relationship with no content (ie. on a multi select field you remove all chosen options so the field becomes empty) we need the
$multi_select[] = ['model' => $options->model, 'content' => $content, 'table' => $options->pivot_table];
at the end of the current foreach loop to set the content to null if we continue we will never hit that line which will happen with the change to the if statement to always continue.
So we need to add a condition to not skip belongsToMany rows:
if (isset($options->type) && $options->type !== 'belongsToMany') {
    continue;
}

But adding the condition above will break the user role thing so you need to add the other condition as well:
if ($row->field === 'user_belongstomany_role_relationship' || $row->field === 'role_id') {
    continue;
}

I flipped the condition from $row->field !== 'user_belongsto_role_relationship because that also breaks absent belongsToMany relationships.
The moving a condition 2 statements up is correct and I believe we should keep that change.
What is breaking things is the change to the continue.

OK, I'm starting to understand what the issue is. I'll look into it soon and attempt to come up with a solution. I don't particularly like the fact that we are hardcoding user-role relationship to solve an issue. I think a solution that would be more broad would be a lot better - there is no reason a user-role relationship should be non-standard.

@hojgr  @emptynick  This is always true
$row->field !== 'user_belongsto_role_relationship'

That's why it's preventing role_id and user_belongstomany_role_relationship to be cleared while editing profile with the side effect of preventing any other belongstomany relationship to be reset.
Untill another fix is merged, I think we just need this:
-                if ((isset($options->type) && $options->type !== 'belongsToMany') || $row->field !== 'user_belongsto_role_relationship') {
+                if ((isset($options->type) && $options->type !== 'belongsToMany') || $row->field === 'role_id' || $row->field === 'user_belongstomany_role_relationship') {

As @jpolive pointed out

Closing because you deleted your branch.
https://github.com/the-control-group/voyager/pull/3016 will completely solve this problem.


⚠ Bofrost.fr has degraded performance

In 6e28cca, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 955 ms

Resolved: Bofrost.fr performance has improved in 8312753.


Minor improvements/optimizations

Just some low hanging fruit I optimized/improved while looking around the codebase, just simple surface-level changes.
I love what you guys are doing! I'm planning on reading more through the codebase and hopefully submitting more useful targeted PRs in the future, probably starting with improving type hinting coverage.

CI still fails. Can you fix the tests?

@cmyui If you make the tests pass we can merge this.

My apologies I've been away from my PC for a bit, time to get to work B)


Error: [libs\datamodel\connectors\dml\src\model.rs:231:53] called Option::unwrap() on a None value

Command: prisma introspect
Version: 2.17.0
Binary Version: 3c463ebd78b1d21d8fdacdd27899e280cf686223
Report: https://prisma-errors.netlify.app/report/13054
OS: x64 win32 10.0.19042
JS Stacktrace:
Error: [libs\datamodel\connectors\dml\src\model.rs:231:53] called `Option::unwrap()` on a `None` value
    at ChildProcess.<anonymous> (C:\Users\Miya\Project\REFACTOR\csmms\node_modules\prisma\build\index.js:39181:28)
    at ChildProcess.emit (node:events:378:20)
    at ChildProcess.EventEmitter.emit (node:domain:470:12)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)

Rust Stacktrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: <unknown>
  16: <unknown>
  17: <unknown>
  18: <unknown>
  19: <unknown>
  20: <unknown>
  21: <unknown>
  22: <unknown>
  23: <unknown>
  24: <unknown>
  25: <unknown>
  26: <unknown>
  27: <unknown>
  28: <unknown>
  29: BaseThreadInitThunk
  30: RtlUserThreadStart

Other report: https://prisma-errors.netlify.app/report/13053

And another: https://prisma-errors.netlify.app/report/13052


Replace obsoleted and unmaintaned transmissionrpc

Motivation for changes:
transmissionrpc is unmaintained. Swap to transmission-rpc as suggested in #2727.
Detailed changes:
Drop-in replacement of imports.
The newer transmission-rpc does not provide HTTPHandlerError. Instead it raises exceptions from requests.exceptions. Error handling on connecting to transmission has to be changed accordingly.
Addressed issues:

#2727  .

Possible improvements
Error handling could be more fine-grained, but requests.exceptions are very detailed as they are.

Excellent, looks good to me. Thanks!

From_transmission is not working. See error here.

The pip dependencies have not been updated to reflect this change. Users miss the transmission-rpc library and get an error:
CRITICAL transmission  xxx  transmission-rpc module version 0.11 or higher required.

The pip dependencies have not been updated to reflect this change. Users miss the transmission-rpc library and get an error:
CRITICAL transmission  xxx  transmission-rpc module version 0.11 or higher required.

transmission-rpc is an optional dependency like many others. Flexget warns it's required when you call a plugin that needs it, the rest is up to you

transmission-rpc is an optional dependency like many others. Flexget warns it's required when you call a plugin that needs it, the rest is up to you

True that the dependency is optional. So I was wrong to mention it as a pip-dependency.
But users get now when upgrading their Flexget no explicit notice that this dependency has changed. And when executing Flexget and receiving that critical error, I have doubts whether they notice the extra dash in transmission-rpc and understand that it is different from the package they have installed in the past.
Maybe an explicit error if transmissionrpc has been found but no transmission-rpc could help them.

True that the dependency is optional. So I was wrong to mention it as a pip-dependency.
But users get now when upgrading their Flexget no explicit notice that this dependency has changed. And when executing Flexget and receiving that critical error, I have doubts whether they notice the extra dash in transmission-rpc and understand that it is different from the package they have installed in the past.
Maybe an explicit error if transmissionrpc has been found but no transmission-rpc could help them.

I've added it to the Upgrade Actions page

I've added it to the Upgrade Actions page

@gazpachoking, could you please look into related issue https://github.com/Flexget/Flexget/issues/2794?

@gazpachoking, could you please look into related issue https://github.com/Flexget/Flexget/issues/2794?


csf_pattern district selection bug #2

There seems to be a misalignment between the chords and arcs in some instances.  For example:

select "Sunset" from the map or chart
select "Transit"
select "Richmond" from the map or chart.

Now the chords aren't aligned with the selected district's arc.

closed by #35


Optional route [[lang]] followed by (group) breaks router

Describe the bug
When I define a route like this
src/routes/
├ [[lang]]/
│ ├ (site)/
│ │ └ +page.svelte
│ │ ├ providers/
│ │ │ └ +page.svelte    // this does not work correctly
│ ├ (auth)/
│ │ └ // auth routes

When navigating to https://example.com/providers it loads [[lang]]/(site)/+page.svelte. When navigating to https://example.com/en/providers it now correctly loads [[lang]]/(site)/providers/+page.svelte
Navigating to  https://example.com/providers should load [[lang]]/(site)/providers/+page.svelte.
Reproduction
https://github.com/codeit-ninja/sveltekit-route-issue-repro
Logs
No response
System Info
System:
    OS: Linux 5.15 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)
    CPU: (16) x64 AMD Ryzen 7 5800X3D 8-Core Processor
    Memory: 7.53 GB / 15.58 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 18.20.4 - ~/.volta/tools/image/node/18.20.4/bin/node
    npm: 10.7.0 - ~/.volta/tools/image/node/18.20.4/bin/npm
    pnpm: 9.7.1 - ~/.volta/bin/pnpm
  npmPackages:
    @sveltejs/adapter-auto: ^3.0.0 => 3.3.1
    @sveltejs/kit: ^2.9.0 => 2.9.0
    @sveltejs/vite-plugin-svelte: ^5.0.0 => 5.0.1
    svelte: ^5.0.0 => 5.4.0
    vite: ^6.0.0 => 6.0.2

Severity
serious, but I can work around it
Additional Information
No response

possible workaround is to add a param matcher for "lang" that ensures "providers" can't match as a language
rename [[lang]] to [[lang=lang]]` and add /src/params/lang.ts with
export function match(value) {
	return value.length <4; // allows for 3 char language tags, you might want to limit this to languages supported by your app
}


Feature  request: Characters Tab + (maybe extra RAG) for  additional Context?

Just wanted to say your project is really great, I was wondering if you guys could  add a characters tab (similar to lorebook) For  writing, would be helpful! Also, if possible, some sort of extra RAG option  maybe? if not, that's  fine.

A characters tab feels too out of scope for this project at the present moment, but I guess RAG could be considered


Text emails not supported?

Actual behaviour
If I uncheck "send as HTML mail" in the backend the mail is still sent as an HTML mail.

Expected behaviour
I expect to get a plaintext mail.

Environment
Shopware 5.4.5

Steps to reproduce

Create mail templates in theme
Uncheck 'send as HTML mail', save, clear cache
Click on 'send test mail' OR trigger the sending of the mail in the frontend

Checklist

[X ] I have checked all issues and haven't found a similar report.
[ X] I am using the latest stable version of this plugin.

--
♥ ANY INCOMPLETE REPORT WILL BE CLOSED RIGHT AWAY ♥

Hmm
https://github.com/FriendsOfShopware/FroshTemplateMail/blob/master/Components/TemplateMailLoader.php#L74
setIsHtml is only triggered if a html template is also available. Is the file existing in your directory?

Is this Problem still there?


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/90844

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

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

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

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

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

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

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


Remove more bycolumn loops

This PR removes more bycolumn loops. These calls are inside the implicit tendency, which are still called with explicit solvers (except that the tendencies are added explicitly). This was found in this build.
This should fix some rather large performance issues for the gpu example (cc @bloops)
The benchmark is looking more promising:
Main branch:
[ Info: Ran step! 10 times in 17.764 s (45437150 allocations: 9.56 GiB), (1.780 s per step)
This PR:
[ Info: Ran step! 10 times in 127.031 ms (244420 allocations: 35.30 MiB), (15.710 ms per step)
I will say, one thing is very odd: why is the benchmark, which runs 20 steps, so much faster than the target job, which runs 60 steps? (at 15.710 ms per step, the difference should be < 1 second)

was this on the CPU or GPU?

was this on the CPU or GPU?

This was for the gpu example

It could just be compilation time? GPU kernels are much more expensive to compile.

I will say, one thing is very odd: why is the benchmark, which runs 20 steps, so much faster than the target job, which runs 60 steps? (at 15.710 ms per step, the difference should be < 1 second)

I saw that the first 10 steps (which includes compilation time) in the benchmark takes 40x more walltime than the next 10 steps (even without this PR). So perhaps the target job running 60 steps is also counting the compilation time?

Ah, my mistake. We modify h_elem in the buildkite performance job (I did it originally kind of as a demo). Let's just remove that argument. That should make it more similar.

@bloops, we're going to close this in favor of https://github.com/CliMA/ClimaCore.jl/pull/1341 and https://github.com/CliMA/ClimaCore.jl/pull/1332.


React Native Docs

There are a few React Native examples in the old docs that haven't made it into the new, as fas as I'm aware.  Where do we want them to go?
https://docs.feathersjs.com/clients/rest.html#react-native-usage
https://docs.feathersjs.com/clients/socket-io.html#react-native-usage
https://docs.feathersjs.com/clients/primus.html#react-native-usage

I have a bunch of client docs I'll push shortly here.

Related https://github.com/feathersjs/feathers-docs/pull/438

Most of these have been added in #438


Update interact.py

Faster Inference can be achieved by caching the paragraph hidden states and using the past argument in transformer.

Thank you so much for your observation and contribution! I had to fix a couple of things to get this to work on a GPU, and I've also cleaned up parts of the pull request. This change leads to a minor speedup in inference on a GPU (~5-10%, but it will likely be more for longer paragraphs), probably because GPT2 uses a transformer instead of an LSTM and self-attention steps happen in parallel (with respect to sequence length) on a GPU.
I've also verified that this change leads to an identical question generation compared to the baseline model.
A current low hanging fruit is batching the question generation decoding. This is likely to boost inference speed assuming the batch fits on the GPU.

I've moved this to #3 to include my commit and closing this for now. It would be great if you could review #3!

I have tried batching the question generation for a batch. It definitely improves the performance but generated questions are not as good as sequential Processing. It could be because of extra padding tokens we add while batching because of variable length answers .

One option (to avoid the padding issues) is to not have <answer-general> in the input, and instead keep it as a segment id at the correct part of the paragraph. This will also provide positional information about the answer.


Add files via upload

Hi  @Tkmiller85, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

I tried following the instructions but was not able to get all the cmd prompt instructions to work. I also had to try a few different things to get the file to upload and pull. I'm glad I was able to figure it out. It's a lot to take in for someone with no understanding of the way that GitHub works.

Oh, I'm sorry that it didn't work for you. Could you please elaborate on what happened?
I’d urge you to continue contributing to other open source projects.
We also have a slack team to help/mentor people trying to contribute to open source projects.
You can join the team by going to https://goo.gl/PM1Jdh


fix: benchmark client cannot connect to server

closes: 461
Please briefly answer these questions:
FYI: issue #461

what problem are you trying to solve? (or if there's no problem, what's the motivation for this change?)

what changes does this pull request make?

are there any non-obvious implications of these changes? (does it break compatibility with previous versions, etc)

closes: 461

I think is won't close the issue,


Rebuild include argument

This rebuild might solve the validation issues found with include argument. Still needs some work to sort out some issues found. But good enough to validate the schema side of things that it works as expected.

Coverage decreased (-0.6%) to 86.56% when pulling e0ce8848a762f63d243dd635e7f1c93aadd68f8c on feature/rebuild-include into 0755156d2420d0661f7ddbc940e16eae1c6f4041 on master.


Restrict available Protected Item types

Hi
Absolutely love this module and Comet Backup! Just had to put that out there. :)
Okay, so my idea is to add another configurable option in WHMCS whereby a client will need to select the backup type. (Files and Folders, SQL, HyperV, Windows Server, Exchange Server etc)
So if we could use something like:
Protected_Item_types|Select your backup type
and you then have the option to select which type you would like to use.
This will then either create or use a pre-setup policy which will restrict the Protected Items Types.
Reason for this: Backing up a home / personal computer might cost less then backing up a Server or SQL databases. It would be nice to have the option of having different pricing for the different backup types.

I believe you can already accomplish this by setting up different policies on your Comet server.  Then create a different product/service in WHMCS for your different user types.  In the "Module Settings" tab in WHMCS for each product, you can then select the appropriate policy that fits the particular case.

Thanks Burt! I actually realized this yesterday after posting. I think that should do the trick for now. :)


Correct line number in README for classes

Correct the linked line number in README for classes

Thanks @junjieqian!


Zeros truncated in AG data mapping file

The barcode prefix is truncated from the AG_full.txt map and the AG.txt file.

Same with the even1/10k files. Very weird. Good catch, will issue PR tomorrow

I know what happened... used excel...

Just so others are aware, AG sample IDs are prone to be interpreted as integers, not only by Excel but also by Pandas, so just be careful.

yes, but we have things like "BLANK123.foo.1231" included
On Mon, Mar 9, 2015 at 11:23 AM, Yoshiki Vázquez Baeza <
<EMAIL_ADDRESS>wrote:

Just so others are aware, AG sample IDs are prone to be interpreted as
integers, not only by Excel but also by Pandas, so just be careful.
—
Reply to this email directly or view it on GitHub
https://github.com/biocore/American-Gut/issues/130#issuecomment-77900154
.

Right, AFAIK pandas doesn't require all samples to have the same type,
it is kinda funny in that it infers the type as int even if there's a
few values that cannot be cast.
On (Mar-09-15|10:26), Daniel McDonald wrote:

yes, but we have things like "BLANK123.foo.1231" included
On Mon, Mar 9, 2015 at 11:23 AM, Yoshiki Vázquez Baeza <
<EMAIL_ADDRESS>wrote:

Just so others are aware, AG sample IDs are prone to be interpreted as
integers, not only by Excel but also by Pandas, so just be careful.
—
Reply to this email directly or view it on GitHub
https://github.com/biocore/American-Gut/issues/130#issuecomment-77900154
.

Reply to this email directly or view it on GitHub:
https://github.com/biocore/American-Gut/issues/130#issuecomment-77900635


How to add an entity for Tapo C120 camera to be able to add it to an automation setup in Home Assistant?

I've finally got sound on my Tapo C110 and C120 cams thanks to this fantastic project.
Now i wonder how i can setup an automation to capture video with sound and i am still missing an entity for the cams with sound.
Any help?

You can use https://frigate.video/ project. Or you can use go2rtc addon. In both cases, you will need to set up transcoding the audio to AAC format. It is the only one supported in the records. And it is not in your camera by default.
And none of this is related to this project.


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/30028

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

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


Switch dependency management to dep

@sttts @nikhita WDYT of switching to dep?  If you are ok with it I can open a PR.

I have found vgo (aka go) to be great.   Perhaps now is not the time to adopt dep?

@justinsb Looks like this is published from staging, and that may be why it hasn't been migrated yet.  FWIW the vgo doc says to use dep for production workloads.

Looks like this is published from staging, and that may be why it hasn't been migrated yet.

Yeah, I don't think we can move to dep unless k/k does. I'll close this in favour of https://github.com/kubernetes/kubernetes/issues/63607, which talks about using vgo for staging. Please reopen if needed.
/close


Add more warning to the doc for resetOffsetAutomatically

resetOffsetAutomatically is used only when it's allowed to ignore potential data loss or data duplicate. This PR adds more warning for this option. I additionally reformatted the table to look better in the markdown file. It should be same when it's rendered.

This is a doc change and I believe CI failures are not legit. Will merge this shortly.


Available space for indicating refresh request

Please provide more specific description for this issue: the title doesn't look like a issue?


High level consumer re-receives messages

We've got this problem for a really long time, no clue if it is found or fixed.
When we restart our consumer each time, it will re-receive some of previous received message again from server side.
And this only happened on high level consumer, simple consumer works fine here.

@ychen11 Before restarting the consumer are you closing the connection ?
try doing something like this
var callback = function(){};
consumer.close(true, callback);
the first parameter is for force and it will commit before closing the connection
https://github.com/SOHU-Co/kafka-node/blob/master/lib/highLevelConsumer.js#L583

Also worth noting here - kafka pretty much has an at least once consumer delivery guarantee so you should be able to handle the case gracefully.  That said… it shouldn't happen much - that should be a rare corner-case.

Looks like it is fixed in version 3.2, after we upgraded our client, it ain't happened again.
I will keep looking, close this for now


Create embeddable iframe for NDT HTML5 test

I'd like us to make it as easy as possible for third parties to drop in the HTML5 NDT test onto their own sites in the form of an iframe.
This involves fixing the following sub-issues:

Make the widget self-contained so that it has M-Lab's logo and a link back to M-Lab's site and brief text explaining that it's a bandwidth test. It shouldn't require surrounding context of the page to explain what the widget is.
Add a button to the widget that generates the HTML required for embedding
The client currently generates a JS warning: Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/. It's likely that mlab-ns isn't going to delay the page load much, but it'd be nice to avoid this. I think we can build more intelligence into the widget so that it the widget handles waiting for the mlab-ns response.

If any of these changes require patches to ndt-project/ndt, we can submit a PR to them.

I'm not able to close issues, so leaving a comment that I think PR #111 addressed this issue and I think it can be closed?


⚠ Bofrost.lu has degraded performance

In ae870d1, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2150 ms

Resolved: Bofrost.lu performance has improved in 2a7dbb8 after 21 minutes.


[$250] Expanding text expander snippets in the composer replace everything typed

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?: needs reproduction
Reproducible in production?: needs reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @twisterdotcom
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1711714936667039
Action Performed:

Open any report
Type some text and add emoji manually or delete some characters and add emoji

Expected Result:
Text typed before adding emoji should stay
Actual Result:
Replaces everything typed
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/38435837/e41bdc52-f9ef-4198-ac85-0c511b8f85d9
https://github.com/Expensify/App/assets/38435837/d302de8f-b3f2-4273-9a8e-48b094afc461

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01bb81fb54a19672c0
Upwork Job ID:<PHONE_NUMBER>632151552
Last Price Increase: 2024-04-04

Snaggin' this from ya as BZ @kevinksullivan .  I experience this all day so wanna help to try to get it fixed quickly.
@alitoshmatov can you see if you can find a way to reproduce without using TextExpander (TE) ?  Maybe you and contributors can download a free version from https://textexpander.com/    Or.. use another snippet/shortcut/expander app.   I don't think I've found a way to repro without TE.
@twisterdotcom , any new deets from your end since you reported this?

No new deets from me.  I tried disabling TextExpander and seeing if the same behaviour happened with Espanso, but it doesn't:
https://github.com/Expensify/App/assets/9133401/8c58c152-80d0-4ccc-b1fc-22080677a2ce
Although, as if by magic, I think we deployed something yesterday which fixed this because this is TextExpander now:
https://github.com/Expensify/App/assets/9133401/8448ef2c-232c-48cc-8d78-4ab22b674a46
@mallenexpensify if you confirm, let's close.

Oh snap, magic fixed here too!  Closing


Error transferring frame 0x00000000 @             0x00000000.

./util/fpga/cw310_loader.py --bitstream build/lowrisc_systems_chip_earlgrey_cw310_0.1/synth-vivado/lowrisc_systems_chip_earlgrey_cw310_0.1.bit --firmware build-bin/sw/device/examples/hello_world/hello_world_fpga_cw310.bin
CW310 Loader: Attemping to find CW310 FPGA Board:
Using bitstream :build/lowrisc_systems_chip_earlgrey_cw310_0.1/synth-vivado/lowrisc_systems_chip_earlgrey_cw310_0.1.bit
CW310 Board Found:
INFO: Programming firmware file: build-bin/sw/device/examples/hello_world/hello_world_fpga_cw310.bin
Programming OpenTitan with "build-bin/sw/device/examples/hello_world/hello_world_fpga_cw310.bin"...
Transferring frame 0x00000000 @             0x00000000.
Transferring frame 0x00000001 @             0x000007D8.
Error transferring frame 0x00000000 @             0x00000000.
Transferring frame 0x00000000 @             0x00000000.
Transferring frame 0x00000001 @             0x000007D8.
Error transferring frame 0x00000000 @             0x00000000.
Transferring frame 0x00000000 @             0x00000000.
Transferring frame 0x00000001 @             0x000007D8.
Error transferring frame 0x00000000 @             0x00000000.
Transferring frame 0x00000000 @             0x00000000.
Transferring frame 0x00000001 @             0x000007D8.
Error transferring frame 0x00000000 @             0x00000000.
Transferring frame 0x00000000 @             0x00000000.
Transferring frame 0x00000001 @             0x000007D8.
Error transferring frame 0x00000000 @             0x00000000.
Transferring frame 0x00000000 @             0x00000000.
Transferring frame 0x00000001 @             0x000007D8.
Error transferring frame 0x00000000 @             0x00000000.
Transferring frame 0x00000000 @             0x00000000.
Transferring frame 0x00000001 @             0x000007D8.
Error transferring frame 0x00000000 @             0x00000000.
Transferring frame 0x00000000 @             0x00000000.
Transferring frame 0x00000001 @             0x000007D8.
Error transferring frame 0x00000000 @             0x00000000.
Transferring frame 0x00000000 @             0x00000000.
Transferring frame 0x00000001 @             0x000007D8.
Error transferring frame 0x00000000 @             0x00000000.
Transferring frame 0x00000000 @             0x00000000.

I had similar issues. Try a different usb-port/adapter and make sure that the board is definitely powered up (6 green LEDs). Usb-power might not be enough.

I power it with the AC on the top left corner of this board.
And, after changed the USB port it seems successful in dmesg, however, the hello_world have the above problem still.

Correct it, I power it with the DC on the top left corner.

Can you double check the power settings (switches) as described in https://github.com/newaetech/ot-sca/blob/cwhusky-doc/doc/getting_started_bergen.md
Additionally, the usb-port can still be a problem.
In my case the device showed up in dmesg, and I even could flash the bitstream, but failed for the firmware. On one board the issue was the power supply, on the other the used USB-port/adapter.

i don't think this link is referenced in the opentitan getting started fpga
guide (even though there is a general description), i wonder if we should
just link it directly.
On Tue, Nov 23, 2021 at 3:15 AM Michael Tempelmeier <
@.***> wrote:

Can you double check the power settings (switches) as described in
https://github.com/newaetech/ot-sca/blob/cwhusky-doc/doc/getting_started_bergen.md
Additionally, the usb-port can still be a problem.
In my case the device showed up in dmesg, and I even could flash the
bitstream, but failed for the firmware. On one board the issue was the
power supply, on the other the used USB-port/adapter.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/issues/9200#issuecomment-976413975,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2RSVEPQVG3DVNX56E5Z3UNNZWVANCNFSM5H43MYJA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

i don't think this link is referenced in the opentitan getting started fpga guide (even though there is a general description), i wonder if we should just link it directly.

We should do that, but the link might change soon, as there is a pending PR https://github.com/lowRISC/ot-sca/pull/57
which corresponds to https://github.com/lowRISC/ot-sca/issues/50#issuecomment-957968228

Try pressing USB RST button, then reloading the bitstream, then try loading the firmware again? I was having the same error and that fixed it for me.

If you're following the FPGA user guide, it doesn't mention the needed argument to set up the PLL on the first run. Add --set-pll-defaults if you haven't, else there would be no clock.
I created a PR to fix that: https://github.com/lowRISC/opentitan/pull/8450

I am closing this issue as the corresponding fix has been merged a while ago already.

I'm facing the same problem now, but with a very specific FPGA build. When flashing a specific version of my custom built (different AES-SBOX) earlgrey version, I'm unable to flash any firmware.  With another FPGA build , I can flash every firmware.
I don't think this AES related, but that something during place and route went wrong and/or something is producing more noise. I will have a deeper look on that (probably) next week, but in the meantime: It might help to use a different FPGA build

I could debug this error further: The problem was that I somehow missed to rebuild the test_rom. Thus, I had an outdated/flawed boot_rom and consequently couldn't flash any firmware. Unfortunately, the error message doesn't help to much in this case. I know that it is clearly written in the getting started guide, but well... perhaps it helps other people when googling this error....


Thruster at an offset

Currently, the external assistive forces are applied at the center of mass, but for many shapes, it makes more sense to attach thrusters at the vertices/boundaries of the bodies instead. Supporting offsets would also allow multiple thrusters to be attached to the same body. I couldn't find anywhere if this is supported yet. If not, I'd be happy to make one and work towards a PR.

This seems like a very reasonable request.  After all, joints have offsets, too.  OK, if you open a PR we'll get this in.

Thrusters are no longer supported, please use MJX and xfrc_applied  :)