sails-redis performance issue

Hello guys !
I'm currently doing some benchmark on my application and found some performance issues regarding to Redis.
I have a simple API endpoint (Notification.find().limit(20)) and around 1200 notification rows in both dbs (Redis + Postgresql)
When I run a GET request on that endpoint (GET /notification), Redis is 10x slower than Postgresql.
Postgresql: 26ms to return 20 notification objects (from 1200 rows total)
Redis: 430ms
Redis settings (in config/connections.js)
redis: {
    adapter: 'sails-redis',
    host: process.env.REDIS_HOST || 'localhost',
    port: process.env.REDIS_PORT || 6379,
    db: process.env.REDIS_DB || '',
    pass: process.env.REDIS_PASS || null,

    options: {
        // low-level configuration
        // (redis driver options)
        parser: 'hiredis',
        auth_pass: process.env.REDIS_PASS || null,
        no_ready_check: true,
        socket_nodelay: true,
        enable_offline_queue: true,
        return_buffers: false,
        detect_buffers: false
    }

}

UPDATE: Redis takes the same amount of time to load 1 or 1000 items so I think Redis is not the issue for this slow performance, might be caused by sails-redis adapter itself when establishing the connection with Redis db.
Does anyone know why Redis is so slow in fetching data?
Best,

@billyshena I think its because sails-redis has to go find how many keys you actually have in a specific model, so..
Keys are like "waterline:notification:1" or something like that for your model, I think the problem is that
we have to figure out how many notification models there are, and do a single get for each one we thing is there, then run it through processing and then limit that then spit out then values... whereas if you just do it with redis you don't do any processing of it, and you don't do a get for each Key in the db, whereas I'm guessing your doing something like "waterline:notification:*" since the * which will get all the models correctly.
Hope this helps.

Hi @Ryanc1256 , thanks for your quick answer !
I do have my keys that look like this: "waterline:notification:id:717"
I'm currently using Waterline to fetch the data in my Redis database (simple Model.find().limit(1) would take 200 ms, same if I set .limit(1000)).
Would you suggest to use a native query to fetch my data from Redis?
Best,

@billyshena it really depends on what you want to do... if you want to have a lot of "joins" and doing the ".populate("ModelName")" thing, i would say stay with waterline as that is pretty intense to do by your self, but if your just doing something simple by just doing the .find( name ) then it might be easier to do native, but then again like i said you lose a lot of flexibility.
Personally, in one of my projects i use the native instead of ORM but i only use it due to the this module doesn't support ttl which im hoping someone will add soon (dreaming)...
but going "native" means you have to do so much manual stuff, like processing for example...
doing something like this in waterline...
id = 1
Model.find({ id: id }).limit( 1 )
would turn into something like
Native.get("waterline:model:" + id, function( err, response ){
if ( err ){
doSomething(err);
} else {
var result = JSON.parse( response );
//do extra stuff...
}
});
So that is like the easiest thing i can think of, for a native query, and the more infomation you use, the harder it gets to maintain...
I love using ORMs as it just makes everything super super easy...
if you love making things, you could always make an simple ORM for redis only, or something, that would streamline a "Native" thing, but then you have to make a ORM loader and all that, it just makes the project a bit longer to build and then you have to figure out how to make queries fast and such... which is pretty hard

Well I use Redis for simple Model.find() but I find that strange that a simple query like Model.find().limit(1) would take Redis around 200 ms to return the data (Postgresql = 20 ms)
I think I'll try in native just to compare the performance.

@billyshena yeah, well if its simple queries like that by all means go a head, it may be simpler until we get a better select method...
Since this has come up a couple times, and you mentioning it.... I think its time to look at how we do it and my mind is ticking away on ways to get it on par with postgressql and all that, well it should be way faster as it does far less and redis is the fastest DB atm ( i think?? )
You have to know also that Postgresql does cache queries whereas redis doesn't do anything like that, so if it simple select queries postgresql probably will comparable speeds  due to caching, if you turn that off you might see that Redis will blow Postgresql out of the water, well from my experience anyway.

@Ryanc1256 I've tried using .native (KEYS *) as you mentioned and it is like 5-10 times faster than using Waterline .find() method to query my Redis keys.
I think Waterline is doing something wrong with the .find() method.

Model.native(function(err, collection) -> collection.keys('*') -> takes around 50 ms (1200 keys)
Model.find().exec() -> takes around 500 ms (1200 keys)

Hope a maintainer of the repo can take a look at the sails-redis adapter.
Best,

@billyshena woop's totally forgot to reply...
Anywho, hes my reply.
So waterline/redis isn't doing anything wrong but its doing it the like sql does it which I think is the wrong way of doing it...
But lets say you have 1200 keys
what this adapter does, keep a list off all the keys in the database so you would have something like
"waterline:model:_indexes" which has a list... of all the indexes in it...
so it would map to
waterline:model:1
waterline:model:2
waterline:model:3
waterline:model:4
... etc up to
waterline:model:1200
So every time you do a ".find" it has to do another query to get that list and do the original query...
Model.find()
that's why it takes like 100 times as slow...
But if your finding with a non-key so you have your database model like
Model
id: key
name: text
... etc...
So when you do a query like ".find({name: "bob"})"
this is where it gets a lot slower...
So it has to grab every key then process it, to see if name is equal to "bob"
And P.S I'm pretty much the only maintainer of this repo :p
But don't worry, I'm planning to make this far far far better... but I'm just thinking of everything and making sure everything is way way way faster... so it's almost as fast as a native find...
Without breaking thing's for people that already use this module.-

+1 I also came across this issue and would love to help on a solution, thanks!

@acolin I think its a re-write of the query system to be smarter at what it does to go find the keys, which is a big undertaking I think and since its a big change we also need make sure it doesn't break anything from the previous versions....
I also want to add ttl as well which is redis key expiration too... but for later...
I just need to find some time to big all this together...
Thinking of doing it here...
https://github.com/Ryanc1256/sails-redis
Was thinking about a full re-write but I have no time for that... so this will do for now.

Okay I have more of an idea down so lets put it down on paper...
So first step is move the connection.get to an better way, so we can get some debug information in that so we know what queries are running without putting console.log or sails.log everywhere...
Now the 4 crud methods are going to change too... ( later )

this will make all the methods more streamline and more away from how mysql does it and move it to an newer redis crud system and faster...
primarily the find method.

@Ryanc1256 That would be awesome, do you plan to release a new version of this adapter?
Best,

Well yeah it will be a new major release... I think i got to talk it over with the other guys, but if your keen to look at that url above :P

@Ryanc1256 cool, will take a look at your repo

@acolin cool, i think ill try to put that debug info in this weekend, when i have a bit of free time and then i can start moving on to the other more intensive moves after i know whats fully going on... p.s. probably could do with some help with that, since its probably a big thing, so any help is appreciated :P

@Ryanc1256 sure, let me know once you have a big picture for the next release, I'll be glad to help.

@Ryanc1256 @mikermcneil Hi guys, are any of these performance issues still relevant?

@acolin @Ryanc1256 @billyshena Hey everyone, thanks for the all the input on this issue so far!  We're moving all the redis cases to the main Sails repo (balderdashy/sails/issues) to keep a closer eye on things and boost exposure to the entire community.


Spruce up README and add CONTRIBUTING

All righty y'all https://github.com/webpack/webpack/issues/908
See how the readme looks on my fork: https://github.com/JonDum/webpack
I had the idea of adding some of the loaders to the readme because it gives a good idea about the types of things webpack can do, but I think there might be too many now haha.
There's still also the issue of organizing and tagging Issues as they come in.

nitpick: I'd move jsx-loader out of templating.... into dialects maybe?

I think README could also mention Hot Module Reloading as a feature.

@andreypopp Could you take a stab at writing a section for HMR for me? I honestly haven't used that myself yet.

Added a revision. Loving the feedback. I'm going to wait for some others to chime in before doing more now.

@JonDum Still reading... Could you replace Webpack with webpack? Lowercase is the correct spelling.

Thanks...


obj-c: RPCs to link-local IPv6 addresses report "Connection lost." errors but actually succeed

When using an ipv6 link-local address as the target for RPCs, the call completes immediately, reporting an error, because SCNetworkReachability reports the host as not reachable. If the host is reachable, the call actually does execute, and the server will observe it, but the caller will never get the response because the call finishWithError'd. If you remove the explicit "preflight reachability" error handling, RPCs work as expected and the result is correctly reported instead of a connection issue.
diff --git a/.../GRPCClient/GRPCCall.m b/.../GRPCClient/GRPCCall.m
index b6309aad2..16f89f7cf 100644
--- a/Pods/gRPC/src/objective-c/GRPCClient/GRPCCall.m
+++ b/Pods/gRPC/src/objective-c/GRPCClient/GRPCCall.m
@@ -446,9 +446,11 @@ - (void)startCallWithWriteable:(id<GRXWriteable>)writeable {
   __weak typeof(self) weakSelf = self;
   void (^handler)(void) = ^{
     typeof(self) strongSelf = weakSelf;
-    [strongSelf finishWithError:[NSError errorWithDomain:kGRPCErrorDomain
-                                                    code:GRPCErrorCodeUnavailable
-                                                userInfo:@{ NSLocalizedDescriptionKey : @"Connectivity lost." }]];
+// SCNetworkReachability does not appear to work for link-local addresses on iOS even though it
+// works fine in a swift playground (both macOS and iOS).
+//    [strongSelf finishWithError:[NSError errorWithDomain:kGRPCErrorDomain
+//                                                    code:GRPCErrorCodeUnavailable
+//                                                userInfo:@{ NSLocalizedDescriptionKey : @"Connectivity lost." }]];
   };
   [_connectivityMonitor handleLossWithHandler:handler
                       wifiStatusChangeHandler:nil];

Interestingly, SCNetworkReachability works fine with link-local addresses in a swift playground (targeting both macOS and iOS, iOS shown below). But the same code written in objective-c and run in the simulator fails to report link-local as reachable.

Apple's guidance (and arguably general wisdom) suggests not preforming "reachability preflight". There are a few reasons for this, but mainly it's impossible to know if a host will be reachable in the future, so the only way to know for certain is to try and establish the connection and execute the request. Apple's guidance suggests only using SCNetworkReachability in the event that prior connections have failed and you would like to ascertain diagnostic information about network configuration.
The objective-c layer does make use of SCNetworkReachability in order to flush channels on connectivity change events, which does seem like an arguably appropriate use. But I also wonder if there's a less destructive way to gracefully handle interface transition events such as simply creating a new channel if the current one becomes closed (e.g. the user disabled wifi or cell radios). This also allows the system to gracefully transition connections across interfaces since connection tuples generally don't carry interface information (and if they do in the case of ipv6 link-locals, flushing the channel won't do anything anyway since the target host would not be reachable via the new interface). In any event, connectivity errors should probably only be reported if RPCs actually fail due to loss of connectivity.

Note: you cannot generally use the objective-c code with link local addresses yet. Use the patch in the referenced PR on https://github.com/grpc/grpc/issues/14369.

Thanks for pointing this out. For this particular issue I'll try it out. For reachability, we are not doing any preflight (or I do not think that is preflight). We only care about network transition. The reason why we proactively destroy channels are because the BSD sockets that Apple provides does not error out during some cases of the network transition activities. Destroying channels is a mitigation of this problem to initiate channel destroy from the top in these cases. Once we integrates CFStream it is likely we can get rid of this part of code.

1.11.0-pre2 is published if you want to try that :)

@muxi your changes to connectivity monitor resolve this!


After switching to SwiftUI App, the dynamic link does not work when the app is in the background

Description
I recently raised the minimum deployments to 14. Therefore, we migrated our app to comply with the App protocol.
I wrote it like the code below Running a Firebase dynamic link when the app is in the background does not perform any logic.
Has anyone solved this problem?
App.swift
@main
struct MyApp: App {
@UIApplicationDelegateAdaptor(AppDelegate.self)
var appDelegate
@Environment(.scenePhase) var scenePhase
var body: some Scene {
    WindowGroup {
        SplashView()
            .onOpenURL { url in
                print("onOpenURL")
            }.onContinueUserActivity("name") { activity in
                print("name \(activity.description)")
            }
    }
}

}
SceneDelegate.swift
class SceneDelegate: NSObject, UIWindowSceneDelegate, ObservableObject {
func scene(_ scene: UIScene, openURLContexts URLContexts: Set<UIOpenURLContext>) {
    ~~
}

func scene(
    _ scene: UIScene,
    willConnectTo session: UISceneSession,
    options connectionOptions: UIScene.ConnectionOptions
) {
    ~~
}

func scene(_ scene: UIScene, continue userActivity: NSUserActivity) {
    ~~
}

}
AppDelegate.swift
func application(_ application: UIApplication, continue userActivity: NSUserActivity,
restorationHandler: @escaping ([UIUserActivityRestoring]?) -> Void) -> Bool {
~~
}
func application(_ app: UIApplication, open url: URL, options: [UIApplication.OpenURLOptionsKey: Any] = [:]) -> Bool {
~~
}
func application(_ application: UIApplication, open url: URL, sourceApplication: String?,annotation: Any) -> Bool {
~~
}
I recently raised the minimum deployments to 14. Therefore, we migrated our app to comply with the App protocol.
I wrote it like the code below Running a Firebase dynamic link when the app is in the background does not perform any logic.
Has anyone solved this problem?
App.swift
@main
struct MyApp: App {
@UIApplicationDelegateAdaptor(AppDelegate.self)
var appDelegate
@Environment(.scenePhase) var scenePhase
var body: some Scene {
    WindowGroup {
        SplashView()
            .onOpenURL { url in
                print("onOpenURL")
            }.onContinueUserActivity("name") { activity in
                print("name \(activity.description)")
            }
    }
}

}
SceneDelegate.swift
class SceneDelegate: NSObject, UIWindowSceneDelegate, ObservableObject {
func scene(_ scene: UIScene, openURLContexts URLContexts: Set<UIOpenURLContext>) {
    ~~
}

func scene(
    _ scene: UIScene,
    willConnectTo session: UISceneSession,
    options connectionOptions: UIScene.ConnectionOptions
) {
    ~~
}

func scene(_ scene: UIScene, continue userActivity: NSUserActivity) {
    ~~
}

}
AppDelegate.swift
func application(_ application: UIApplication, continue userActivity: NSUserActivity,
restorationHandler: @escaping ([UIUserActivityRestoring]?) -> Void) -> Bool {
~~
}
func application(_ app: UIApplication, open url: URL, options: [UIApplication.OpenURLOptionsKey: Any] = [:]) -> Bool {
~~
}
func application(_ application: UIApplication, open url: URL, sourceApplication: String?,annotation: Any) -> Bool {
~~
}
Reproducing the issue
No response
Firebase SDK Version
10.15
Xcode Version
14.3.1
Installation Method
Swift Package Manager
Firebase Product(s)
DynamicLinks
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

Please note that the Firebase Dynamic Links service will be shutdown on August 25, 2025. In the meantime, only critical or security issues will be fixed in the SDK.
More at https://firebase.google.com/support/dynamic-links-faq


ci(release): extract fragment of release notes for github release

Proposed changes
Split the changelog using a regex matching all h1 and h2 and extract the changeset on top.
Then, use the same process as before for publishing.
Testing
Tested on my machine by altering the changelog.md and running the script (logging instead of publishing, ofc). I also checked what the RegExp was doing here: https://regex101.com/r/UitWby/1.

CDX-185

Blocked by #193 prolly


Integrate datastore in to Codex

Once SQLite is fully integrated in to nim-datastore.

Is it the same as #138 ?

Yes, good point, closing.

let's delete this issue entirely!


Global plugin state

some suggestions...  General pattern here is that anything that knows about the plugin manager should update the plugin manager directly using it's API.  and anything that needs to show something about the plugin manager should be listening only to the plugin manager for events.  (we can extend this pattern back to call order in a future PR if needed).
I haven't had time to look yet, but I also found myself wondering what the new signals on the preferences dialog were for?
this will currently break the call order preservation of a disabled plugin.  but I will explain that to everyone.  We need to accommodate that on the plugin manager model first

I haven't had time to look yet, but I also found myself wondering what the new signals on the preferences dialog were for?

This was to accommodate for resetting the plugin state back to default values (everything enabled).  At the time, I was trying not to change this within the preferences dialog, but I can't remember why right now.


Refactor ActionInstructionReceiverImpl to improve clarity

Motivation and Context
This commit intends to make it easier to understand the code.
This commit makes not changes to the functionality of the system.
What has changed
This PR only contains refactorings, no functionality has changed.

Extract Method to improve readability
Replace Nested Conditional with Guard Clauses
Replace Method with Object

How to test?
Run the acceptance tests.
Links
Done as part of https://trello.com/c/lZYrIXw7/118-create-an-auto-verifying-notify-endpoint-service

Is Coday misconfigured? I was expecting to see Cyclomatic complexity, Npath, coupling metrics, method size, class size alerts, but they seem to be missing?

 Create an auto-verifying notify endpoint service


The resolveActivity doesn't work for Android 11 like this

The lint says It needs @SuppressLint("QueryPermissionsNeeded"). Also, it doesn't open the activity.
Code lab page number: https://developer.android.com/codelabs/android-workmanager#8
override fun onCreate(savedInstanceState: Bundle?) {
   // Setup view output image file button
   binding.seeFileButton.setOnClickListener {
       viewModel.outputUri?.let { currentUri ->
           val actionView = Intent(Intent.ACTION_VIEW, currentUri)
           actionView.resolveActivity(packageManager)?.run {
               startActivity(actionView)
           }
       }
   }
}

Thanks! This was exactly my issue on my Android 12 Device. I added @AlveZs's  <queries> code in the AndroidManifest.xml right under the  <uses-permission> section and it worked.

+1 @AlveZs solution works.

Since we're running the default handler, a simple startActivity(Intent(Intent.ACTION_VIEW, currentUri)) call would work without a need for resolution and hence, a need for the queries permission.


Ensure restore doesn't write broken files

Required for all non-trivial PRs

[x] Rebased/mergable
[x] Tests pass

Restore would try to open the shard if there was an error.  If there
was an error, the files written are very likely to be partially written
and they can cause the server to panic.
To prevent a shard from trying to open broken files, we now write to
a temp file and rename it to the actual name only after fully writing
and fsyncing the file.

:+1:


fix: Assign max_instances=1 according to the comments in a markdown…

… section
Assign max_instances=1 to match the comment in the markdown section: 'Currently, your compute cluster aml-cluster can only scale do a maximum of one node.'
Module: 04
Lab/Demo: 04
Fixes # 1
Changes proposed in this pull request:
Assign max_instances=1 (currently max_instances=2) to match the comment in the markdown section: 'Currently, your compute cluster aml-cluster can only scale do a maximum of one node.'

Thanks for pointing it out. Already fixed in another PR.


Move specific generator, enrichers to separate repositories

Enricher and Generators which a specific to a tech-stack like spring-boot, vert.x, thorntail should be grouped together.
When moving to fabric8-build, these enrichers will be ables to support more than Maven but also Graddle and other environments which can provide a proper context.
So the suggestion is to move those parts out into separate repositories or as part of fabric-build in separate modules.

@rhuss any idea how enrichers/generators will be configured? I've faced several issues with the current approach and had to find a convoluted way to go back to the roots (Maven XML...).
Another aspect is how the extension mechanism would work? Plugin dependency? Project dependency? My question is somewhat oriented as I would love to see the possibility to add the Vert.x enricher/generator into the Vert.x Maven Plugin and just using this plugin would magically enable the support.

For adding new enricher etc. we are using plugin dependencies. The configuration of the enrichers / generators can be done by XML already (its a generic map) or via properties, too.
See e.g. https://github.com/fabric8io/fabric8-maven-plugin/blob/master/samples/spring-boot-with-yaml/pom.xml#L79-L89

The issue I faced with configuration was the lack of structural support. It was supporting key-value pairs, but the value was not a composite construct (like another key-value set). Maybe I missed something.

Any possibility to register an enricher/generator using a programmatic way or Maven Component (@Component)?


The default export condition must come last

When package.json is generated, the conditional exports are in the wrong order: "default" must be the last one.
I reported the issue upstream in https://github.com/atomicojs/exports/issues/7.

Hi @DamienCassou Thank you for noticing this. Version 3.50.4 fixes this bug. I'll be attentive to anything you need. Greetings!


Jitsi related Pods should have liveness/readiness checks

We currently don't have liveness/readiness checks for the prosody and web pods.
I suggest to use the return value of prosodyctl status to gain confidence in the prosody readiness.
For the web pod I suggest to just use the HTTP port and check for a successful query.

ReadinessProbes for prosody and web deployment are established. Your recommendations have been used. In fact prosodyctl status returns a 0 code if and only if prosody is running correctly, see https://github.com/bjc/prosody/blob/master/prosodyctl. The use of liveness checks should be discussed further.


chg: Bump max python version to 3.11, bump deps, poetry.lock

This one look like a lot, but isn't really.

Mark the lib as compatible with python 3.11. Not sure why it wouldn't, but it forces all the packages depending on this lib to block python 3.11
Bump all the dependencies
Bump the poetry.lock file to poetry 1.3+ format

Thank you @Rafiot, merged!

Released https://github.com/3c7/bazaar/releases/tag/v0.2.1


[FLINK-19269] Make the PushingAsyncDataInput.DataOutput aware of endOfInput

What is the purpose of the change
In this PR PushingAsyncDataInput.DataOutput is notified
about the end of input. It also moves the propagation to the bounded
operators of that signal from OperatorChain to the DataOutputs.
Verifying this change
This change is already covered by existing tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot run azure

Hi @pnowojski could you take a look at the changes, as it touches some of the streaming runtime parts? Or maybe you could ask somebody else that works on the streaming runtime part?

Ad. 2 Very good point. I totally missed that. Will add it.
Ad. 1 Will add tests.

In the end we decided to put the sorting logic into the DataInput instead of DataOutput. Therefore this Pr is not valid anymore.


Update operation + signature validation

Update operation
Signature validation
Add tests
Order of operation is like sidetree's resolver

Codecov Report

Merging #112 into master will increase coverage by 0.57%.
The diff coverage is 95.31%.

@@            Coverage Diff             @@
##           master     #112      +/-   ##
==========================================
+ Coverage   36.84%   37.41%   +0.57%
==========================================
  Files         250      250
  Lines        3412     3448      +36
  Branches      247      253       +6
==========================================
+ Hits         1257     1290      +33
- Misses       2036     2039       +3
  Partials      119      119

Impacted Files
Coverage Δ

packages/element-lib/src/sidetree-v2/op.js
100% <ø> (ø)
:arrow_up:

packages/element-lib/src/sidetree-v2/func.js
89.7% <100%> (ø)
:arrow_up:

...es/element-lib/src/sidetree-v2/protocol/resolve.js
93.75% <95.23%> (-1.25%)
:arrow_down:

Continue to review full report at Codecov.

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


insertText is not coming in refs in react-quill

Please look into the issue

I need insertText in refs too. Please help. @zenoamaro @alexkrolick

@avneet2112 you can getEditor first, then pass the editor and Delta to setEditorContents(editor, Delta) to insert your text.

I need insertText too. Please help. :(

It looks like v2.0 has been updated, but the Docs and demos have not been updated.

It seems a bit strange but you can access insertText() like this:
  const rq = quillRef.current.makeUnprivilegedEditor(
    quillRef.current.getEditor()
  );
  const ed = quillRef.current.getEditor();
  ed.editor.insertText(rq.getSelection().index, "★");


do you plan on releasing training code?

Yes, training code will be released by this week. Thanks.


Activation annotations

Coverage decreased (-5.05%) to 73.629% when pulling b55c5a11f47e36af1e3dd46e01628cc776b1885e on activation-annotations into a23344ed0012b8d9f444e9ba14e8baf9a16951be on master.

Coverage decreased (-5.06%) to 73.613% when pulling 4a4a81f1e24f8e3d27ead8f3eb8c910e01031eb3 on activation-annotations into a23344ed0012b8d9f444e9ba14e8baf9a16951be on master.

Coverage increased (+0.7%) to 79.384% when pulling 0efdb087c7ea7107d21d6bde06fb25ea5c86ad54 on activation-annotations into a23344ed0012b8d9f444e9ba14e8baf9a16951be on master.

Coverage increased (+0.7%) to 79.384% when pulling 0efdb087c7ea7107d21d6bde06fb25ea5c86ad54 on activation-annotations into a23344ed0012b8d9f444e9ba14e8baf9a16951be on master.


feat: Add support for guardrails ai plugin

Description
This PR adds support for the Guardrails AI plugin to the Portkey Gateway. The Guardrails AI plugin provides several validators for enhancing content safety and quality control in AI applications.

Hey @kaushikb11 - Are you planning to finish this PR? Or else I will create an issue for this and close the PR for now so that others can pick it up.


Sergen from Postgres with non-default schema

When using sergen to generate code for a table in PostgreSQL that is outside of the default schema, it throws an exception at the end: Npgsql.PostgresException: 42P01: relation "TABLENAME" does not exist
Tables in the default 'public' schema do not have this issue, and when working with SQLite the schema is not a problem at all.
After tracing it back to PostgresSchemaProvider.cs, I believe this can be fixed by including the schema with the table name as follows:
"WHERE pg_class.oid = '" + schema + ".\"" + table + "\"'::regclass " +

@JesseGlidewell ,
thanks for tracing and sharing this with us :-). As Volkan currently seems to be very busy implementing many of the things he has shown in the roadmap proposition, it would make it easier for him if you could implement this within a git pull request so that he can just approve and merge it.
(This would also get more attention than here in the issue forum).
Just my 5 cents...
With kind regards,
John

Thanks for the suggestion John. I'll probably take a crack at it next month, since this isn't the only issue with Postgres we've had to work around, it's just the only one I currently have a real solution for. If possible I'd like to include fixes for those other bugs as well, or failing that document the workarounds for them.

I don't have Postgress installed at the moment, if you can change it and test and ensure that this is correct for all Postgress versions, i may apply the change.

Hello,
I have same problem\error "Npgsql.PostgresException: 42P01: relation "TABLENAME" does not exist" in configuration Asp .Net Core project + Serenity.CodeGenerator 3.13.4 + PostgreSQL 12 for tables that are outside of the default schema. Does it will be fixed by JesseGlidewell recommendation?

@vsudik I have workarounds for this and a few other Postgres issues, so there wasn't much incentive to test the above change across all database versions before submitting a pull request. So if you have the time, please feel free to pick up the task. But if you need a quicker fix you can use this SQL command to modify the database so sergen can work with other schemas:
ALTER DATABASE "databaseName_v1" SET search_path TO otherSchema, public

@JesseGlidewell Thank You, I will use your trick, but I have to rename some tables with same names in different schemas before it.


Fix envoy build

Signed-off-by: Lizan Zhou<EMAIL_ADDRESS>

cc @mdouaihy

Looks like the CI failed because the OS X build timed out -- maybe try running again, it might not be an actual issue with the PR

I restarted the build


Javadoc analysis fails on Windows

JavaDoc analysis doesn't work on Windows due to a bug in the handling of paths: On Windows path components regularly contain colons like in C:\some\path. This clashes with the unconditional use of ":" as a path separator in the JavaDoc invocation since the resulting argument for -classpath is something like this: C:\some\path:C:\some\other\path
All places where a fixed path separator of ":" is assumed have to be replaced by File.pathSeparator for Windows compatibilty.

Oh yes, you're right -- I always tend forget those Windows guys as Unix fanboy :-)
thanks!


Clear existing command when command is run

Fixes https://github.com/microsoft/vscode/issues/144279

This seems to break shell integration on windows, probably due to the change in handleCommandStart. Needs more work.


Fix CI Pipeline

These adjustments should fix the CI pipeline.
Had a successful run at https://github.com/brhahlen/OTGW-firmware/actions/runs/4935274530/jobs/8821372551

I can confirm this fixes it.


⚠ Spryr has degraded performance

In c0a46de, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 7423 ms

Resolved: Spryr performance has improved in a82e59d after 7 minutes.


Returning multiple outputs

Many of the interfaces return multiple outputs. Should these be returned as a tuple, a list, a dictionary (a bunch)?
tuple and list would be the simplest option, but make it harder for the user to know which output is which
a dictionary would solve that problem with keys (a bunch is similiar to a dictionary, not sure if it is advantageous in our case, it's used from nilearn datasets: https://github.com/dsc/bunch)

I like the idea of the dictionary/bunch a lot. I had been using set numbers of variables to return but this is not very useful unless you know exactly what should be returned by the function. The bunch code appears to be mature.

I think dictionary is a good choice, unless anyone has a strong opinion on using bunch (which would introduce an additional dependency). Example in the MGDM interface:
https://github.com/juhuntenburg/cbstools-python/blob/master/cbstoolspython/brain/mgdm_segmentation.py#L132-L140
https://github.com/juhuntenburg/cbstools-python/blob/master/cbstoolspython/brain/mgdm_segmentation.py#L302-L303

Perfect.


Updated install instructions

using go install rather than go get

Lol, wait, I already did this (https://github.com/fogleman/primitive/pull/102)... dejavu!


Docker Hub image outdated

Just pulled sudoforge/murmur:latest and it has an outdated docker-entrypoint.sh:
/etc/murmur # curl -skL https://raw.githubusercontent.com/sudoforge/docker-images/master/murmur/docker-entrypoint.sh > docker-entrypoint.sh
/etc/murmur # diff /usr/local/bin/docker-entrypoint.sh docker-entrypoint.sh
50,53c50,53
<     SSL_CERTFILE=/data/cert.pem
<     SSL_KEYFILE=/data/key.pem
<     SSL_CAFILE=/data/intermediate.pem
<     SSL_DHFILE=/data/dh.pem
---
>     SSL_CERTFILE=${MUMBLE_CERTFILE:-/data/cert.pem}
>     SSL_KEYFILE=${MUMBLE_KEYFILE:-/data/key.pem}
>     SSL_CAFILE=${MUMBLE_CAFILE:-/data/intermediate.pem}
>     SSL_DHFILE=${MUMBLE_DHFILE:-/data/dh.pem}
76d75
<     setVal welcometext '"'
78c77
<     echo -n "${parsedContent}\"" >> "${CONFIGFILE}"
---
>     setVal welcometext "\"$parsedContent\""
94c93,101
<     /opt/murmur/murmur.x86 -ini "${CONFIGFILE}" -supw $SUPERUSER_PASSWORD
---
>
>     # Using -supw currently throws a fatal error and exits the program. It has
>     # been fixed in the upstream project by commit d8203ba94 [1], after the
>     # current version (1.3.0). To bypass the issue and allow the entrypoint
>     # script to proceed, we are ignoring the erroneous exit code by executing
>     # `true` if the first invocation fails.
>     #
>     # [1]: https://github.com/mumble-voip/mumble/commit/d8203ba94d528b092e0ff5a52a51af28f8f592f1
>     /opt/murmur/murmur.x86 -ini "${CONFIGFILE}" -supw $SUPERUSER_PASSWORD || true

Do you have a mechanism that auto-updates images upon commit?

Hey! Thanks for spotting this and opening an issue. That is really, really strange. I re-built the image locally and notice a difference (although not on the entrypoint):
➜ container-diff diff remote://sudoforge/murmurd:1.3.0-3 daemon://sudoforge/murmurd:latest --type=history --type=file

-----File-----

These entries have been added to sudoforge/murmurd:1.3.0-3: None

These entries have been deleted from sudoforge/murmurd:1.3.0-3: None

These entries have been changed between sudoforge/murmurd:1.3.0-3 and sudoforge/murmurd:latest:
FILE               SIZE1        SIZE2
/etc/shadow        469B         469B

-----History-----

Docker history lines found only in sudoforge/murmurd:1.3.0-3: None

Docker history lines found only in sudoforge/murmurd:latest: None

Running a container and copying it to my local filesystem didn't show a difference between the entrypoint:
gh::sudoforge/docker-images [ master ]
➜ docker cp 6d861f3621a6:/usr/local/bin/docker-entrypoint.sh murmur/docker-entrypoint.sh

gh::sudoforge/docker-images [ master ]
➜ git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean

I've manually built a new release, :1.3.0-4, and updated the :latest tag. Can you confirm that the issue is no longer present for you?

Do you have a mechanism that auto-updates images upon commit?

Internally, yes. I was waiting for GitHub Actions to set this up, but due to the low churn here, never got around to doing that even after my account gained access. Thanks for the push -- I'll move this to Github Actions today.

The difference between the two /etc/shadow images is just the UID for the murmur user:
➜ diff -ur shadow-3 shadow-4
--- shadow-3    2020-03-20 00:11:25.000000000 -0700
+++ shadow-4    2020-04-04 06:57:05.000000000 -0700
@@ -26,4 +26,4 @@
 smmsp:!::0:::::
 guest:!::0:::::
 nobody:!::0:::::
-murmur:!:18341:0:99999:7:::
+murmur:!:18356:0:99999:7:::

Hey! Thanks for spotting this and opening an issue. That is really, really strange. I re-built the image locally and notice a difference (although not on the entrypoint):
➜ container-diff diff remote://sudoforge/murmurd:1.3.0-3 daemon://sudoforge/murmurd:latest --type=history --type=file

-----File-----

These entries have been added to sudoforge/murmurd:1.3.0-3: None

These entries have been deleted from sudoforge/murmurd:1.3.0-3: None

These entries have been changed between sudoforge/murmurd:1.3.0-3 and sudoforge/murmurd:latest:
FILE               SIZE1        SIZE2
/etc/shadow        469B         469B

-----History-----

Docker history lines found only in sudoforge/murmurd:1.3.0-3: None

Docker history lines found only in sudoforge/murmurd:latest: None

This is simply the UID of the murmur user, and is expected:
➜ diff -ur shadow-from-remote-latest shadow-from-local-latest
--- shadow-3    2020-03-20 00:11:25.000000000 -0700
+++ shadow-4    2020-04-04 06:57:05.000000000 -0700
@@ -26,4 +26,4 @@
 smmsp:!::0:::::
 guest:!::0:::::
 nobody:!::0:::::
-murmur:!:18341:0:99999:7:::
+murmur:!:18356:0:99999:7:::

Running a container and copying it to my local filesystem didn't show a difference between the entrypoint:
gh::sudoforge/docker-images [ master ]
➜ docker cp 6d861f3621a6:/usr/local/bin/docker-entrypoint.sh murmur/docker-entrypoint.sh

gh::sudoforge/docker-images [ master ]
➜ git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean

I imagine that you might have an outdated :latest. Can you run docker inspect sudoforge/murmurd:latest --format='{{ .Id }}' and provide the output here?

Do you have a mechanism that auto-updates images upon commit?

Internally, yes. I was waiting for GitHub Actions to set this up, but due to the low churn here, never got around to doing that even after my account gained access. Thanks for the push -- I'll move this to Github Actions today.

@KetchupBomb Is this still an issue for you?

Haha, I see the problem. You have two images, sudoforge/murmur and sudoforge/murmurd.
I've been using the former (which was last updated 5 months ago), while the later (which was updated 2 days ago) has the changes I've been after.
Your readme has sudoforge/murmur in header text, but the body of the document uses the proper sudoforge/murmurd, I just didn't notice.
I leave it up to you to do what you wish. Marking as closed.

Ah, you're totally right
I can't recall why the image name was changed -- I don't have an issue describing the change; [just one referencing the new name from last year][0]... Shoot. I'm sorry for the confusion; I almost never sign into my account on the public registry, and didn't remember that there were two images.

_< I can't believe I glossed over that in your initial comment.

@KetchupBomb Just an FYI, I've closed out #96, which talked about the decision regarding the names. The associated commit has an updated README which discusses the plan regarding deprecation of the sudoforge/murmur and sudoforge/murmurd image names.


Safe to use?

Checking to see if this is still safe to use since it seems there had been many tools causing bans.

They have changed the way the map seed is encoded in memory so this will no longer find the map seed so then the map generation logic does not work.
It should still be able to read the monsters and items near by from memory.
I would not recommend running it on battle net as similar tools have resulted in bans.


Wire Frame

Figma Wire Frame
Create a wire frame that shows the basic page layout and design intentions.

FIRST


Embeddable URLs from the "driveItem: preview" endpoint fail to load ~20% of the time.

Category

[ ] Question
[ ] Documentation issue
[ x] Bug

Expected or Desired Behavior
Embeddable URL that should display the contents of the sharepoint office file in the web browser (as ready only).
Observed Behavior
Fails about 20% of the time with JS errors on the viewer (through the link returned). When this occurs, the viewer does not load, and the page needs to be refreshed.
Steps to Reproduce
Call the "driveItem: preview" endpoint, receive an embeddable link to display within an iframe. Fails to load ~20% of the time.
Thank you.

Does this issue affect OneDrive for Business, OneDrive Personal, or both services?  Also do you know which viewer(s) or file type(s) are affected by this issue?

I'm using it Microsoft Graph 1.0 which is using SharePoint, but I'm assuming it's the same and uses One Drive for business. It's affecting all Document, Excel, and PowerPoint viewers. This is the endpoint I'm using: https://docs.microsoft.com/en-us/graph/api/driveitem-preview?view=graph-rest-1.0
The same link works if refreshed. There are some request issues for cross domain requests. I think it could be due to the way the older anonymous web viewer was set up. It could be a combination of these JavaScript errors that stop it from loading.

As part of a repository clean up effort we are closing older issues. If this issue remains, please: open a new issue, reference this issue, and provide any additional details that may help in resolution. Thank you for your understanding as we work to improve our responsiveness.


Update MEMBERS.csv

Can't add the logo to the website yet until I get the LF contract amended, but can get official on the list

Closing in favour of #92.


add retry logic on response stream failure

Motivation
The instagram API, over HTTP 1.1, occasionally exhibits these
issues:

socket reset of TCP connection
partial JSON response stream leading to JSON parse errors

This addresses the errors by retrying the request when either a
socket exception or JSON parse error occurs.
It is worth noting that the instagram API over HTTP2 does not
seem to have these issues. It would be much more work to allow
HTTP 2, at this point, because Java does not support in their
native APIs.
Solution
Provide a configurable setting to retry the request on stream
failure.
Only one retry is attempted. If the response failed again the
errors will be propagated.
Missing
A test should be provided to check the retry logic.
retry on invalid json response
single retry; must be enabled in InstagramConfig
fix retry logic

Addresses #184.

Hey @marcbr8 and @tdeekens, take a look.

Coverage decreased (-10.7%) to 56.069% when pulling 125843b7ce0c52856beec2dbf9b8fc2e4bb7864a on abargnesi:retry-on-invalid-json-response-body into 9c89b9f651471cab8b138c45acf99de2d13d009d on sachin-handiekar:master.

The code coverage reduction is due to missing tests. I will try to address this soon.

Thanks a lot @abargnesi! We could also try looking into adding the tests and swing up a PR against this one...

Sounds great, thanks!
On Thu, Nov 24, 2016, 3:09 PM suǝʞǝǝpʇ<EMAIL_ADDRESS>wrote:

Thanks a lot @abargnesi https://github.com/abargnesi! We could also try
looking into adding the tests and swing up a PR against this one...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sachin-handiekar/jInstagram/pull/186#issuecomment-262839238,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJHxXp6Wy7L5ZeEKtLx_LJueNtBUHyOks5rBe7jgaJpZM4K73n9
.

Cool thanks @abargnesi I'll have a look into the tests and help out as I can

This PR should also include retrying on 500 status code. I am seeing occasional 500 Internal Server Error fetching comments user media.
I'll add support for this shortly within this PR.

Cool. I tried to add tests but it's really difficult to set up (there are actually no tests for InstagramBase at all...)

Coverage decreased (-10.8%) to 56.002% when pulling 32c61beadeff1a4ff00899b7a0792de3e32c4d2f on abargnesi:retry-on-invalid-json-response-body into 9c89b9f651471cab8b138c45acf99de2d13d009d on sachin-handiekar:master.

Yeah it does seem a bit tricky to create test fixtures. You would want to mock the first invocation of InstagramBase.getApiResponse and return Response objects that exhibit the error behavior (e.g. throwing a socketexception, response with malformed json, 500 response).
You could then assert that subsequent invocations return a successful response in order to prove the retry logic occurred.
Or you could count invocations of testResponseBody (might need protected scope here).

It would be possible. But I noticed that most of the logic has not being tested at all. Most of the test coverage is so high because getters, setters and constants are being tested.

Some tests that should help increase the coverage
https://github.com/abargnesi/jInstagram/pull/1

Oh yay.

Does anyone know why this is still included neither in 1.1.9 nor in 1.2.0-SNAPSHOT despite of being merged more than two month ago?


KBV-623 X-Ray Tracing of Experian calls

Proposed changes
X-Ray Tracing of lambdas and specific methods.
What changed

Add tracing to the powertools dependency configuration
turn off powertools during unit tests
use tracing in lambda handlers
use tracing to surround experian api calls
use tracing for VC JWT signing

Why did it change
Trace latency in calls to external APIs, and JWT signing.

Issue tracking

KBV-623

Simple enough


bump version of num_cpus to 1.0

In the process of updating the dependencies of another far upstream package that eventually includes hyper, I noticed that num_cpus had finally stabilized and made a 1.0 release. There were no code changes in the 1.0 release from 0.2.13 (https://github.com/seanmonstar/num_cpus/commit/7aab1fbc30b9bf39e74b0624dc037af694ce4da3)
The tests for hyper pass on my machine.

Is there any way to see GitCop without signing up?

failures:
server_empty_response_chunked
server_empty_response_chunked_without_calling_write
server_get_chunked_response
server_get_fixed_response
test result: FAILED. 5 passed; 4 failed; 0 ignored; 0 measured

It looks like failing tests on windows were present on master already. Should I be targeting 0.9.x branch instead?

Yes, master does not even use the num_cpus crate anymore.

@seanmonstar  It's a dev-dependency on master right? That is why I thought it would be a really low impact change because it would not even touch the release code.

Is there even any point in updating the num_cpus version? @seanmonstar  You do know best after all...

Oh you're right, it's used in the examples/hello.rs file. I had completely forgotten. Updating it doesn't hurt, in this case. The failing tests have been known, thanks to the published version of mio, as seen in #816 .


Login & Sign-Up Buttons

For some odd reason, neither of the login or sign up buttons actually take you to their individual screens. I will try to fix this, and have tried to, but I do not know when it'll actually be fixed.

I tried to fix it with a function since that would make the readability easier but it still for some reason doesn't work.


mise updates

move all mise tasks to folder hierarchy, and some cleanups along the way

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#282  👈
#244 : 1 other dependent PR (#256 )
#243 : 1 other dependent PR (#251 )
#238
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @chrisaddy and the rest of your teammates on  Graphite


Application Stopped from Listening Database

Application runs as expected, as long as it does not pass more than 30 or 35 minutes from application starting. If then, the console application that make the inserts continue on recording in database but net core application does not get noticed of the change in table anymore. Could you please take a look and see why this behaviour? Could we enable an everytime listen channel in netcore?
Thanks in advance
Juan

pgsql connection is using the same thread from the pool as the host, it's not a good thing. ms SqlDependency use a separate appDomain for the process which is more robust. https://github.com/microsoft/referencesource/blob/master/System.Data/System/Data/SqlClient/SqlDependency.cs

may implement IHostedService for this https://docs.microsoft.com/en-us/dotnet/architecture/microservices/multi-container-microservice-net-applications/background-tasks-with-ihostedservice


Convert to associated constants

Two problems with this:

breaking API change
requires nightly

I suppose this will need to wait until associated constants are stable.

Yeah for now this crate builds on stable, so we'll have to wait for associated constants to be stable to merge this unfortunately.

@tamird It seems like the associated_const feature will remain unstable for the near future. So it might make sense to pre-release this on crates.io as a separate crate (e.g. bitflags_associated_consts). This would allow nightly users to take advantage of the nicer API.

This needs a rebase to pick up various changes made on master; I'll try to get to it this week.

Rebased; probably won't pass until 1.20 is stable.

Rebased again. Beyond the use of associated constants, this also uses compiletest, which requires nightly. Do we want to just remove the compile-fail test?

The stable/beta builds seem to still be failing due to experimental features?

Yes, I believe that's because this PR adds a dependency on compiletest, which requires nightly (see my last comment). Should I just remove the compile-fail tests?

Removed compiletest; lmk if you'd like me to squash the commits, but this should be green now.

r? @alexcrichton

👍
Thanks @tamird!


Discuss onAccessibleClick and alternatives like exposing PressListener.a11yClickingProperty

This lengthy title stems from #831, and whether or not onAccessilbeClick is the best api for what we are trying to accomplish. Having a fully separate function that is only fired when a press occurs with a11y is nice, but I could also foresee wanting to have branching logic inside the same function that holds other input related code.
For example, something like:

    var pressListener = pushButtonModel.createListener( {
      press: function() {
        if ( pressListener.a11yClickingProperty ) {
          // do a11y specific stuff
        }
        this.fire(); // always fire for both a11y and mouse
      },

This is just a bad example with pseudo code, but I think it conveys my point.

@jessegreenberg do you have any concerns about this? I like the idea of simplifying the number of callbacks to pass into the PressListener constructor. We may find that we will still need options like this for the sun/ButtonModel hierarchy because we will only have access to the PressListener from ButtonModel.createListener. This seems like the most robust and straightforward way to proceed.

No concerns at all, I definitely think this should be explored as a general improvement.

Worked on this with @jessegreenberg today. We removed accessibleClick listener and moved an a11yClicking check into the same listener as is fired with the mouse.
@jonathanolson would you please review this as part of you work with PressListener?

This issue is incredibly old. @jonathanolson and I have worked multiple times on PressListener since then. I'm going to close. Please reopen if you feel differently.

Oops, didn't close, but did just do another review of this code! Closing


How to pass the authorization token as header information

Hi,
I have my grpc service behind an API gateway. The gateway protects the service using an API key. I am able to use the above using grpcurl as follows:
grpcurl \
-H 'Authorization:<api_key>\
-d '{}' \
<endpoint>.cloudapp.azure.com:8080 \
<namespace>.HelloService/SayHello

I want to load test the same thing using ghz and I am facing issues in calling using the metadata
ghz \
-m '{"Authorization" : "<api_key>"}' \
--call <namespace>..HelloService/SayHello \
-d '{}' \
<endpoint>.cloudapp.azure.com:8080

I keep getting the error
rpc error: code = Unauthenticated desc = unexpected HTTP status code received from server: 401 (Unauthorized); transport: received unexpected content-type "application/json"

Also having this issue

We are also running into the same issue. Requests work fine with grpcurl but not with ghz
Our Header format is Authorization: Bearer <token>.

Try ghz --metadata="{\"authorization\": \"Bearer $TOKEN\"}"
It works fine for me.

I have already tried many different ways to do that, and it still doesn't work with Ghz, but it perfectly works with grpcurl.

also seeing this what works grpcurl works with -H "Authorization: Bearer $TOKEN" but ghz does not with  --metadata="{\"authorization\": \"Bearer $TOKEN\"}"

If it helps move things along here is what grpcurl does to tranform headers into metadata

I dug a little bit and found the issue is ghz only passes the metadata you provide with the requests you define. There is an explicit request it makes on your behalf if you do not provide an explicit proto or protoset to reflect over your service to get the info it needs to structure its requests called grpc.reflection.v1alpha.ServerReflection/ServerReflectionInfo.
ghz does not send the metadata you provide with the grpc.reflection.v1alpha.ServerReflection/ServerReflectionInfo request. In my case, this is what causes the cli to error out because authorization is needed for both that as well as the request I'm asking it to make.

there is however a work around which is to pass the same data passed with metadata with an additional reflect-metadata arg
ghz \
 --metadata="{\"authorization\": \"Bearer $TOKEN\"}"  \
 --reflect-metadata="{\"authorization\": \"Bearer $TOKEN\"}" \
 ...

I understand the value in having the flexibility but this is a bit of leaky abstraction for me and a detail callers shouldn't have to think about. I think the default should be to pass metadata in --metadata otherwise I assume this will just cause others the same confusion


Parse register table error but not abort

If we use following config ('C' is used instead of 'c'):
OSDTRRX_EL1			S2_0_C0_C0_2
The rdasr will not abort, and then reading error register!

Fixed


Worked on issue 243; replaced input with self.wait_for_user_input; other changes

Worked on issue #243 that was assigned to me.
This includes the following:

Replaced input with self.wait_for_user_input in the following Python scripts:

TC_OpstateCommon.py
TC_RVCCLEANM_2_1.py
TC_RVCCLEANM_2_2.py
TC_RVCOPSTATE_2_1.py
TC_RVCOPSTATE_2_3.py
TC_RVCOPSTATE_2_4.py
TC_RVCRUNM_2_1.py
TC_RVCRUNM_2_2.py
matter_testing_support.py

Removed input_msg argument from wait_for_user_input
Accordingly, passed test steps into prompt_msg, and appended "Press Enter when ready".
Adjusted the return value accordingly, taking into account that it needs to end with an \n for the text to print properly in the test framework.

@austina-csa this seems to need more CLA signing


Exchanges text is not Visible/ Microsoft Edge Browser

@mryoso1994 also tested on Windows 10 Edge Version 101.0.1210.53 (Official build) (64-bit). Are there any other SVGs which aren't displaying?

@mryoso1994 also tested on Windows 10 Edge Version 101.0.1210.53 (Official build) (64-bit). Are there any other SVGs which aren't displaying?

Microsoft Edge
Version 101.0.1210.53 (Official build) (64-bit) thats the only part that are not displaying

i also tried InPrivate Incognito/ Same issu

e

I highlighted to check if it was going to show but it still doesn't.

@mryoso1994 strange ... could you check if the image (svg) url is working in edge? e.g: https://websitexf.xcash.rocks/assets/images/partners/5f72164dfa34506ed9ddb079_stex_orange.svg
Thank you!

yes its working

.

todo's:

[test in incognito mode]
[ask google]

i can't reconstruct the bug, in any setting the svg's get displayed ...
I guess I need to boot windows ;-P

@mryoso1994  are you running with any extensions/ plugins?

@mryoso1994 are you running with any extensions?

@mryoso1994 are you running with any extensions?

im not running any extensions.


Add new Couchbase usecase for 0.5

What this PR does / why we need it: New usecase for 0.5
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #896

@mahebbar -- The changes related to Couchbase are updated as part of the PR https://github.com/openebs/openebs/pull/906.
Closing this PR.


Adds an account behavior to disable folders

Some sync services (Feed Wrangler) don't support folders. This behavior removes the account from the UI when adding new folders.
#2049

Looks like this issue can be closed

Looks like this issue can be closed


Conditional menu build fix for window

@Stanzilla You can test it.

Fixes it!

Nice @chabou  @ppot 💯 '


How to build it with gtk4-layer-shell feature?

Hi, thanks for the interesting project!
I have issue building it on my Arch, here is what I tried:
git clone --depth 1 <repo>
cd mixxc

cargo build --release --features=Sass,Wayland

output:
   Compiling gdk4-sys v0.7.2
   Compiling gsk4-sys v0.7.3
   Compiling gtk4-sys v0.7.3
   Compiling gtk4-layer-shell-sys v0.1.2
The following warnings were emitted during compilation:

warning: `PKG_CONFIG_ALLOW_SYSTEM_CFLAGS="1" "pkg-config" "--libs" "--cflags" "gtk4-layer-shell-0" "gtk4-layer-shell-0 >= 1"` did not exit successfully: exit status: 1

error: failed to run custom build command for `gtk4-layer-shell-sys v0.1.2`

Caused by:
  process didn't exit successfully: `/tmp/cargo-installBvtVwJ/release/build/gtk4-layer-shell-sys-3911a91337e99d03/build-script-build` (exit status: 1)
  --- stdout
  cargo:rerun-if-env-changed=GTK4_LAYER_SHELL_0_NO_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
  cargo:warning=`PKG_CONFIG_ALLOW_SYSTEM_CFLAGS="1" "pkg-config" "--libs" "--cflags" "gtk4-layer-shell-0" "gtk4-layer-shell-0 >= 1"` did not exit successfully: exit status: 1
  error: could not find system library 'gtk4-layer-shell-0' required by the 'gtk4-layer-shell-sys' crate

  --- stderr
  Package gtk4-layer-shell-0 was not found in the pkg-config search path.
  Perhaps you should add the directory containing `gtk4-layer-shell-0.pc'
  to the PKG_CONFIG_PATH environment variable
  Package 'gtk4-layer-shell-0', required by 'virtual:world', not found
  Package 'gtk4-layer-shell-0', required by 'virtual:world', not found

warning: build failed, waiting for other jobs to finish...
error: failed to compile `mixxc v0.1.5`, intermediate artifacts can be found at `/tmp/cargo-installBvtVwJ`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

While submitting the issue, I've realized I'm missing gtk4-layer-shell shared, I've installed it via such PKGBUILD:
# Maintainer: Shengyu Zhang<EMAIL_ADDRESS># Contributor: Brett Cornwall<EMAIL_ADDRESS># Contributor: Adrian Perez de Castro<EMAIL_ADDRESS>
pkgdesc='A library to create panels and other desktop components for Wayland using the Layer Shell protocol and GTK4'
pkgname=gtk4-layer-shell
pkgver=1.0.1
pkgrel=1
arch=(x86_64 aarch64)
license=(MIT)
url="https://github.com/wmww/gtk4-layer-shell"
depends=(
    "gtk4"
    "wayland"
)
makedepends=(
    "gtk-doc"
    "gobject-introspection"
    "meson"
    "ninja"
    "valabind"
    "python"
)
source=("$pkgname-$pkgver.tar.gz::$url/archive/v$pkgver.tar.gz")
sha256sums=('f7b8d352065a540d4cb7b0cbfdeb2c2efea55b57cfb717de5c880fde41e65cb1')

build() {
    meson setup \
          --prefix=/usr \
          --wrap-mode=nofallback \
          --buildtype=plain \
          -Dtests=true \
          -Ddocs=true \
          -Dintrospection=true \
          -Dvapi=true \
          -Dexamples=true \
          "$pkgname-$pkgver" \
          build
    ninja -C build
}

# See: https://github.com/wmww/gtk4-layer-shell/issues/12
# check() {
# ninja -C build test
# }

package() {
    DESTDIR="$pkgdir" ninja -C build install
    install -D -m 644 "$pkgname-$pkgver/LICENSE" "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"
}

Then mixxc can be successfully built \o/

Sorry for the noise. Hopefully this issue helps someone.
Cheers!

No problems, gtk4-layer-shell unlike it's gtk3 predecessor is not yet packaged for all Linux distributions.
(I had to make a template for Void Linux myself)
If you have any other questions, or if some things confuse you, feel free to open an issue, this might help me to improve README for everyone else.


 If you need help, you may report this error at:
typings ERR!   https://github.com/typings/typings/issues
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\Giovanni\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "run" "typings" "--" "install" "dt" "~" "core-js" "--save" "-global"
npm ERR! node v6.9.1
npm ERR! npm  v3.10.9
npm ERR! code ELIFECYCLE
npm ERR! @ typings: typings "install" "dt" "~" "core-js" "--save" "-global"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ typings script 'typings "install" "dt" "~" "core-js" "--save" "-global"'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the  package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     typings "install" "dt" "~" "core-js" "--save" "-global"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     c:\Users\Giovanni\Documents\angular2\todo\npm-debug.log

No space in between. dt~core-js

Thanks

Da: Homa Wong<EMAIL_ADDRESS>Inviato: giovedì 8 giugno 2017 05:09
A: typings/typings
Cc: bonannogiovanni; Author
Oggetto: Re: [typings/typings] typings install (#803)
No space in between. dt~core-js
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/typings/typings/issues/803#issuecomment-306985891, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Ab6OUweOffrPnM_0YMYqdJAc_-7QfIdmks5sB2X2gaJpZM4Nza6e.


2.1.0 ctrtransfer image wont fit

Due to the large file size (794.6 MB) it is impossible for me to fit this file in my /files9 folder.  I have a 4 GB SD Card.
First, is the file suppose to be this large?  If so, is it mandatory that I have an 8 GB SD Card?  I feel even if I deleted all extraneous files from my card I still would not have room.
EDIT: After grabbing a backup and trying again there was plenty of room to spare.  Odd, because I had just made the backup and it should have been the exact same size.  Problem solved I suppose..

If you've solved your problem, feel free to close the issue.


\big(, \Big etc. doesn't work

\big(, \Bigl( etc. produce normal size ( instead of bigger size brackets.

Fixed by e64bb4b.


seq2ffv1  - catch errors that ffmpeg is too old

16-bit RGB is only available in the most recent git heads. Find a way to catch the ffmpeg error and tell user to update!

Closing this as users will most likely have a newer ffmpeg at this point.


Class Methods Namespace Not Renaming WIth Parents Classes

Hi, the bug is related to namespaces and this call functions, the bug consist that when Auto Generated Class is renamed, all the Function/Methods that has that namespace ( Class/Struct )

will get out of scope and wont de-compile,

the function will look for the old ( Namespace/Class ) Name, should not be automatically followed those changes by the main class rename?
To Reproduce this, just find anywhere where you can auto create an struct/class
After that, find a function which has the thiscall convention, receiving the previous auto-created Struct object as this pointer
Then open the function renamer, and change namespace to this Auto-created Struct, after that, just rename the struct, and function should go out of scope, because still is in the old name of the struct.
The Expected behaviour should be that the this method automaticlly Follow the namespace changes becouse parent Class name also changed
some screenshot after rename

all comming back to normal after renaming back to old class namespace of the method

Environment (please complete the following information):

OS: Windows 10
Java Version: java 19.0.1
Ghidra Version: Lastest ( 10.2.2 )

Ghidra Origin: official GitHub distro

Related to #4745, _, and whatever others I've missed.
Blatantly obvious problem with an obvious solution, that hasn't been fixed because?

Blatantly obvious problem with an obvious solution, that hasn't been fixed because?

While I will be the first to admit this is severely flawed, a good solution with referential-integrity is not obvious.
Underlying issues we are currently faced with include:

No mechanism for strict 1-to-1 referencing between a Ghidra Class Namespace and its associated Class Structure and related datatypes.
No formal/rigid namespace organization for datatypes which utilize adhoc category folders.
A fuzzy search is done for the match-up/relationship between a Ghidra Class Namespace and a Structure.  It is possible for multiple Classes to get mapped to the same stucture (many-to-one).  This is a bad.  The search does attempt to use category paths to give preference to a match.
Inconsistent category naming conventions for Class Structure containment.  Should its category folder have the same path as the Class or the path of the parent Namespace.  Both conventions are used.
Within symbol namespaces, Ghidra currently assumes every namespace path is unique and has no clear way to deal with duplicate definitions which may exist within a single binary.

Use cases to consider:

Rename of a single Structure.  Multiple classes may be fuzzy-matched-up with single structure being renamed - should they all be renamed if structure is renamed?  What about category that contains the structure?  Should give user ability to either propogate rename or not.  API vs GUI cases to consider.
Rename of a single Ghidra Class.  Other classes may be fuzzy-matched-up with the same structure being renamed - should they all be renamed or lose their fuzzy structure association?  What about the containing category name?  Could consider renaming it too if its name currently matched the structure, although not guarenteed to be correct.  Should give user ability to either propogate rename or not.  API vs GUI cases to consider.
How should rename of a datatype category be handled which could contain many class structures somewhere within its hierarchy?  How should such a rename impact the namespace paths of Ghidra Classes which may be associated with structures whose path is changing?  Very easy for a category path change to impact one or more fuzzy associations.
How should rename of a Namespace be handled which could contain many Ghidra Classes somewhere within its hierarchy?  How should such a rename impact the category paths of structures which may currently have a fuzzy-association to affected Ghidra Classes?

@astrelsky I would be curious to hear your recommendations.

I've been using using the UniversalID to pair a class to the DataType (struct, class or union). This can be painlessly stored in the GhidraClasss' as it's just a long. The documentation for getUniversalID states "This value is intended to be a unique identifier across all programs and archives. The same ID indicates that two datatypes were originally the same one. Keep in mind names, categories, and component makeup may differ and have changed since there origin." If for some reason the DataType with the stored id no longer exists, just create a new one.
I think the UniversalID was the obvious solution I was referring to. I will admit that I was just following someone else's example "... yell loud enough and someone will eventually come over to see what all the fuss is about... doesn't mean they'll do anything about it...".
Is it GhidraClasses, GhidraClass's or GhidraClass' I have no idea. ¯_(ツ)_/¯

@astrelsky Where do you store this value and how do you get Ghidra to respect the relationship?  Assuming Ghidra would respect this relationship, I assume the category and structure name now become meaningless to the association.  It would still have the same organizational challenges and how to cope with namespace/category renaming.

@astrelsky Where do you store this value and how do you get Ghidra to respect the relationship? Assuming Ghidra would respect this relationship, I assume the category and structure name now become meaningless to the association. It would still have the same organizational challenges and how to cope with namespace/category renaming.

I store it in a database table my plugin uses. I can't actually get Ghidra to respect the relationship without modifying Ghidra itself. All I can do is check when VariableUtilities.findExistingClassStruct et al. return a DataType other then the expected one and log the error.
As far as storing the value in Ghidra it could go right in SymbolDB's DBRecord used in GhidraClassDB. Obtaining the DataType from the UniversalID is trivial (See DataTypeManager.findDataTypeForID(UniversalID datatypeID)`).

As indicated in my initial post, the biggest challenge is overcoming the fuzzy-association and ensuring that it does not break as names are changed.  The only good solution requires the use of a fuzzy-association to be eliminated and somehow a 1-to-1 two-way association created and maintained.   We would also have to contend with the organization of related datatypes associated with a namespace/class.  Establishing a formal organization approach for a namespace/class and its associated datatypes within the datatype manager is where things get very complicated.

As indicated in my initial post, the biggest challenge is overcoming the fuzzy-association and ensuring that it does not break as names are changed.  The only good solution requires the use of a fuzzy-association to be eliminated and somehow a 1-to-1 two-way association created and maintained.   We would also have to contend with the organization of related datatypes associated with a namespace/class.  Establishing a formal organization approach for a namespace/class and its associated datatypes within the datatype manager is where things get very complicated.

You overcome the fuzzy-association by removing it as that is the entire problem. Trying to locate a datatype (which has a unique identifier that does not change) by a property the user can freely change at will is foolhardy.
The means of a one to one association already exists. The UniversalID is a unique id for a datatype that does not change when any of the datatypes other properties change.


velge and reactjs

Is is possible to use velge within a react component/container? Do you have any suggestions how to accomplish this?
Thanks

Velge can definitely be used within a React component. The main thing you need is a ref to the underlying DOM node (more about refs).
For example:
import Velge from "velge"
const VelgeComponent = React.createClass({
  render() {
    return React.DOM.div({ className: "velge-container", ref: (ref) => this.container = ref })
  },

  componentDidMount() {
    this.velge = new Velge(this.container)
  },
})

this.container will be a DOM node -- the same as what you would get from document.querySelector or document.getElementById.
Let us know if you have any follow-up questions.

Thanks @TaylorBriggs  for suggesting this code. I am trying to make a freestanding component with Velge that I can then import into a form inside another component. My adaptation of your code (es6-ified) doesn't work:
import React, { Component } from 'react';
import Velge from "velge";

class VelgeComponent extends Component {
  componentDidMount() {
    this.velge = new Velge(this.container)
  }
  render() {
    return (

 this.container = ref })>
 )
  }
})

export default VelgeComponent

Any obvious mistakes stand out?
Thanks again

Looks like a couple of errant parens. Give this a shot:
import React, { Component } from 'react'
import Velge from 'velge'

class VelgeComponent extends Component {
  componentDidMount() {
    new Velge(this.container)
  }

  render() {
    return (

 this.container = ref } />
    )
  }
}

export default VelgeComponent

You would only need to keep a reference to the instance (this.velge) if you planned on calling its methods in the component or attaching event handlers to it. If you do attach event handlers to the velge instace, you'll want to unbind them in componentWillUnmount. You can also pass options into the Velge constructor as the second argument.

Sorry to be taking up so much of your time trying to solve this. I'm very grateful for your help.
When I tried the ew ncode with the fixed parens, it didn't cause errors but wasn't visible in the browser when rendered inside the component I imported it into. Upon inspected element, I noticed that it's height was 0px. So I added some inline style as shown below. Then it was visible as a red box but wasn't a functioning component. I also tried re-adding the "this.velge = " which I originally had but I think you inadvertently omitted when you retyped my repaired code. Anyway, with the code below, all I  get is a non-functioning red box in the browser. None of the chosen are displayed.
import React, { Component } from 'react'
import Velge from 'velge'

class VelgeComponent extends Component {
  componentDidMount() {
    this.velge = new Velge(this.container, {
      choices: [
        { name: 'macintosh' },
        { name: 'cortland' }
      ],
      chosen: [
        { name: 'jonagold' },
        { name: 'snow sweet' }
        ]
      }
    );
  }

  render() {
    return (

 this.container = ref } />
    )
  }
}

export default VelgeComponent

Which version of react are you using? You might need to use a string ref instead of the callback, e.g., ref="container" on the element attribute and this.refs.container when instatiating Velge. Right now, it appears that the ref callback is not happening, so the Velge instance is not being created.
On Thu, Feb 18, 2016 at 10:32 PM, David Handel<EMAIL_ADDRESS>wrote:

Sorry to be taking up so much of your time trying to solve this. I'm very grateful for your help.
When I tried the ew ncode with the fixed parens, it didn't cause errors but wasn't visible in the browser when rendered inside the component I imported it into. Upon inspected element, I noticed that it's height was 0px. So I added some inline style as shown below. Then it was visible as a red box but wasn't a functioning component. I also tried re-adding the "this.velge = " which I originally had but I think you inadvertently omitted when you retyped my repaired code. Anyway, with the code below, all I  get is a non-functioning red box in the browser. None of the chosen are displayed.
import React, { Component } from 'react'
import Velge from 'velge'
class VelgeComponent extends Component {
  componentDidMount() {
    this.velge = new Velge(this.container, {
      choices: [
        { name: 'macintosh' },
        { name: 'cortland' }
      ],
      chosen: [
        { name: 'jonagold' },
        { name: 'snow sweet' }
        ]
      }
    );
  }
  render() {
    return (

 this.container = ref } />
    )
  }
}
export default VelgeComponent

---
Reply to this email directly or view it on GitHub:
https://github.com/dscout/velge/issues/13#issuecomment-186045758

react version 0.14.7
I tried your suggestion with above without success. When I log out this.velge inside componentDidMount after it is instantiated I get it in the console: Velge {options: Object, store: Store, ui: UI, addCallbacks: Array[0], remCallbacks: Array[0]} so is was created.

Sorry you're having so much trouble with this. One thing I notice is your chosen values are not included in choices. Your options should look like:
this.velge = new Velge(this.container, {
  choices: [
    { name: 'macintosh' },
    { name: 'cortland' },
    { name: 'jonagold' },
    { name: 'snow sweet' }
  ],
  chosen: [
    { name: 'jonagold' },
    { name: 'snow sweet' }
  ]
})

I also put together a sample app that you should be able to run as-is. I'm not sure what your build step is, but I'm using webpack (and the webpack-dev-server) in this example.
react-velge.zip

Thanks @TaylorBriggs. Got it! This is another good working example to have for others.

@dbhandel glad it's working now :)
I've opened a PR with examples for the popular frameworks so other folks hopefully have an easier time integrating Velge with their projects.


npm update -g "broke" http-server

http-server previously installed globally.  Accidentally issued an npm update to all of global (tacked on -g out of  habit..was typing too fast) and when http-server updated to 0.7.1, it will not start
attempting to run [http-server]
Error: listen EACCES
at errnoExeption (net.js:904:11)
at Server._listen2 (net.js:1023:19)
at listen (net.js:1064:10)
at net.js:1146:9
at dns.js:72:18
at process._tickCallback (node.js:419:13)
at Function.Module.runMain (module.js:499:11)
at startup (node.js:119:16)
at node.js:906:3

Thanks. Closing this then :smile:

wait. You didn't do anything to address this issue

Nothing changed. I thought the comment from @bleggett solved this issue.
... can you open an issue on node-portfinder? thanks!


Indexing notes in "search manuscript"

From an email from Debra:
"What I had wanted to check was that you have the search within the "indexing notes" field per source, as here:
https://cantusdatabase.org/searchms/123612
On the left side underneath Office/Mass and Genre, you can search for words that are entered in the indexing notes. I think maybe you have this already (I think I have checked with you before). The option I am using today is searching for a length greater than zero, so that I can pull up any/all notes in one particular source."
on OldCantus this looks like this, for reference

and searching for " " (space) gives 180 results on this particular manuscript.

addendum:

this probably wasn't initially included because it is comparatively new to OldCantus
This should only be on "search manuscript". Per Debra "Also, Jan put it in only one place: the "search this manuscript" page that you get to in the RH menu. This is the spot for it, I think, since you would likely only want to search within a source for the notes (for now, anyways - and the notes aren't tidy, so we don’t want to advertise them too much on the main search page)."

I'm working on this.
In starting to do so, I realized that the main Chant Search view and the Chant Search MS view, which share a template, have a bunch of copy-pasted and slightly tweaked code, so I'm going to spend some time writing additional tests, and then refactoring these views to make things simpler. (I was starting to work on this for the Search MS view, and in trying to make the clicking-on-column-headers thing work, I realized that with so much duplicated code, I'm really likely to introduce bugs if we don't clean these views up).

the refactoring work I mentioned in July has been partially implemented, but work remains on this. I'll try to get back to this once we sort out #1098.


Bump deprecation warnings from 7.0 to 8.0

The updated places are:

tests where the warnings act as test data.
Deprecation of 'force' was extended
Deprecation of 'SourceDirectorySetFactory' was extended (#15844)

@bot-gradle test QFL

OK, I've already triggered QuickFeedbackLinux build for you.

@bot-gradle test QFL

OK, I've already triggered QuickFeedbackLinux build for you.


sync fail after node restart

Codecov Report

Merging #13 into master will decrease coverage by 0.47%.
The diff coverage is 68.65%.

@@            Coverage Diff             @@
##           master      #13      +/-   ##
==========================================
- Coverage   77.05%   76.57%   -0.48%
==========================================
  Files         204      204
  Lines        4637     4675      +38
  Branches      204      223      +19
==========================================
+ Hits         3573     3580       +7
- Misses       1064     1095      +31


Input stream

This is not meant to be merged into master, as the code quality isn't up to par. I just thought I would open a pull request so that if I am doing something fundamentally wrong, it can be caught now instead of when the big refactor commit comes through.

u have to rename model to viewmodel too


[1pt]  Fix acquire for ras2fim use

ras2fim product had a need to run the acquire 3dep script to pull down some HUC8 DEMs. The old script was geared to HUC6 but could handle HUC8's but needed a few enhancements. ras2fim also did not need polys made from the DEMs, so  switch was added for that.
Also, the earlier version on the "retry" feature would check the file size and if it was smaller than a particular size, it would attempt to reload it.  The size test has now been removed. If a file fails to download, the user will need to look at the log out, then remove the file before attempting again. Why? So the user can see why it failed and decide action from there.
Note: later, as needed, we might upgrade it to handle more than just 10m (which it is hardcoded against).
Changes

data

usgs

acquire_and_preprocess_3dep_dems.py:  As described above.

fim_pipeline.sh:  a minor styling fix (added a couple of lines for readability)
fim_pre_processing.sh: a user message was incorrect.

Testing
A full HUC8 conus domain run was done to download all of the HUC8 DEMs from USGS.
Issuer Checklist (For developer use)
You may update this checklist before and/or after creating the PR. If you're unsure about any of them, please ask, we're here to help! These items are what we are going to look for before merging your code.

[x] Informative and human-readable title, using the format: [_pt] PR: <description>
[ ]  n/a Links are provided if this PR resolves an issue, or depends on another other PR
[x] If submitting a PR to the dev branch (the default branch), you have a descriptive Feature Branch name using the format: dev-<description-of-change> (e.g. dev-revise-levee-masking)
[x] Changes are limited to a single goal (no scope creep)
[x] The feature branch you're submitting as a PR is up to date (merged) with the latest dev branch
[x] Changes adhere to PEP-8 Style Guidelines
[x] Any change in functionality is tested
[ ] n/a  Passes all unit tests locally (inside interactive Docker container, at /foss_fim/, run: pytest unit_tests/)
[x] New functions are documented (with a description, list of inputs, and expected output)
[x] Placeholder code is flagged / future todos are captured in comments
[x] CHANGELOG updated with template version number, e.g. 4.x.x.x
[x] Reviewers requested
[x] Add yourself as an assignee in the PR  as well as the FIM Technical Lead

Merge Checklist (For Technical Lead use only)

[ ] Update CHANGELOG with latest version number
[ ] Update the Citation.cff file to reflect the latest version number in the CHANGELOG
[ ] If applicable, update README with major alterations

There is no rush at all to get this merged.


Using Oauth as apikey

Hi Drewn,
It would be great if the $apikey is little bit flexible for the Oauth too.
Kind Regards,
John

Hi Drewn,
I've done some changes to the and it work, can you have a look.
I'm not satisfied with my code.
Kind Regards,
John

Could you point me to the part of the MailChimp API you're looking to implement?


tour: Missing page: Spanish

In:
https://tour.golang.org/welcome/2
If you click on Spanish, the page is 404 (Not Found).

The link was fixed, so we can close here.


Support for Apollo 2.x.x + Redux

Hi! I am having some trouble getting set up with Redux and Apollo.
The existing with-redux-and-apollo example is only compatible with Apollo 1. Apollo 2 severs out-of-the-box support for redux in favor of Apollo's client side state management, but luckily https://github.com/rportugal/apollo-cache-redux gives you a way to still use redux with Apollo 2. That being said, I'm brand new to Nextjs and setting up the dev environment with Apollo 2 and Redux has been challenging, if anyone has ideas about how to accomplish this please let me know! An updated example would be greatly appreciated :)

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Your Environment

Tech
Version

next
beta

node
9.0.0

browser
chrome

I will have time tonight to get a PR up for review.

This definitely needs an overview. Open to any and all changes. 😁

@zdenham
The more I delved into this, the more I found myself wanting to keep Apollo in charge of its store and Redux in charge of its. (Though this could be a personal preference on my end, of course.)
I've kept the initial PR with-apollo-and-redux as is, though I do not know if it will get a pass, as I did not notice that apollo-cache-redux is/was in alpha.
To that end, we could use apollo-cache-inmemory instead. But wanted to see what your hope or intention for using Redux and Apollo together was.
I created another example with-apollo-and-redux-saga that has Apollo and Redux Saga completely separated. Though it may be too specific of an example for a PR.

I am working on a personal project with complex local state where redux makes a lot of sense.

The project I'm working on uses redux to manage complex local state (not as a caching mechanism for apollo). I am only adding in Apollo right now because I wanted to try out graphql. For my use case, I think separate stores makes a lot more sense and will be easier to integrate. Thanks for the example, I think the with-apollo-and-redux-saga will do the trick. I'll try it out tomorrow and let you know how it goes!

Oh very cool! Thank you for sharing. I may change the with-apollo-and-redux example to use apollo-cache-inmemory then. That way it's a stable example, and a good starting off point for people who want to break things out on their own.
Please let me know if with-apollo-and-redux-saga is helpful, and any feedback. That way we can see if another example and PR is in order.
Thanks @zdenham !

@JeromeFitz this example is perfect for my use case! And I think its a good idea to update the with-apollo-and-redux to use apollo-cache-inmemory as a lot of people trying to mix apollo 2.0 and redux are probably looking for separate stores for their data layer and local state. At least from my (limited) experience with the libraries that's what I was looking to do! Thx again for the example

Awesome, that is great to hear!
I think I'll do a PR for with-apollo-and-redux-saga as well then, and see what @timneutkens and @ads1018 may have to say about improvements.

May be relevant to anyone's interests currently working with Apollo & Redux at the moment.
Managing your local data in Apollo Client with apollo-link-state:

https://dev-blog.apollodata.com/the-future-of-state-management-dd410864cae2
https://github.com/apollographql/apollo-link-state

Awesome stuff thanks @JeromeFitz. I'll take peek this weekend. And yeah...thanks for sharing those links. I'm looking forward to replacing redux with apollo client. Looks like a great way to manage local state.

I believe this was solved a while back.


2251-67 still no support?

Hi guys,  for a forensic project I need to access secure hidden partition from a flash with this controller. Did you have a solution for it now? Can you help to try to patch it or create a custom firmware?  Do you think I can send the special unlock command thru usb or I will need the password as well,  therefore only patching will work?
Thanks for your answer.

thanks for such greate answer..............

Hi I am work in goldiran lg company
We also make flash
Working with phison,SMI,alcor
I have some firmware
Example fw67v6.10.53
Fw67v6.11.10
If some one need email me

In warranty we first clean flash memory erase with uptool
And use mpall+new firmware
I also share files and how to extract firmware
In flash boot

http://flashboot.ru/flash_recovery/2015/05/03/extract-2251-03-firmware.html

I see some body say after firmware sail killed flash. I say no before insert to PC hold nand chip 29+30 with one piece as wire hold for 3second and let it
In hardware boot mode you must hold 2 pin io

davodamirajam Are you able to dump the firmware ?

let me to example something
for example we have a 2251-07 98 de 98 92
if i dump firmware and write to another flash disk
if second flash have a hardware bad block ???
so firmware is crashed
before the dump and write must be re mark bad block
On Mon, Feb 1, 2016 at 5:22 PM, dummys<EMAIL_ADDRESS>wrote:

davodamirajam Are you able to dump the firmware ?
—
Reply to this email directly or view it on GitHub
https://github.com/adamcaudill/Psychson/issues/121#issuecomment-177979204
.


Page > Client Details

[x] Cards has wrong bottom margin, it shoudl be 8px

All tasks has been fixed correctly. I'm closing this issue.


Second presence is "blinking" on the multiplayer text editor with Tiptap and Yjs

I'm building a multiplayer text editor with Liveblocks, Tiptap and Yjs
Everything seems to be working fine, except that the cursor/caret from the other presence is "blinking" when the text is focused by the primary user

This starts happening when I click on the text (focus on it)

Hey @stevenfabre could you please give me some help here?
I have no idea of what might be causing this problem
I commented out everything that is not directly related to the core functionality of the feature (like in this example) but I still get this issue

Hey @henriquedevelops, sorry we missed your issue! This is an unfixed Tiptap bug. Luckily it only happens when React's strict mode is enabled, which is only in development mode. In production, the issue doesn't occur.
I'm closing this because we have the same issue here:

https://github.com/liveblocks/liveblocks/issues/1161


[bug] entities not respawning after the 1.4.1

Entities can not automatically respawning after I updated the mod to 1.4.1

Your respawn groups might be frozen. Try running /respawn unfreeze all

I tried unfreeze but it didn't work

Are you open to sharing the world file so I could take a look at the nbt data?

I will just try the newest 1.5.0 to make sure it’s still not working of not, thanks a lot

Server crashed when first player entry with 1.5.0 version of the mod, but the 1.4.3 runs fine

Could you post the crash log.


Build failure: rocm-llvm-libc-6.0.2

Steps To Reproduce
Steps to reproduce the behavior:

build rocm-llvm-libc-6.0.2

Build log

Build Log
https://gist.github.com/khaneliman/ebdafe3b92413ea91fad1f3734e9148c

Additional context

Metadata

Notify maintainers

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

Duplicate of https://github.com/NixOS/nixpkgs/issues/368672