RFC: Use UDFs as sources

Thanks @bakjos
I am wondering what specific HTTP service do you intend to connect through this source?
While looking into this requirement, I also came up with another idea:
If the requirement is to subscribe from poll-based API, such as Twitter streaming API, maybe we can introduce an external component for handling webhooks.
Here is a brief proposal:
RisingWave WebSync APIs

Instead of supporting arbitrary webhooks via SQL in RisingWave, this solution abstracts all integrations into a single, general WebSync API.
For example, to subscribe from Github events of a repo, RisingWave will first poll WebSync Server, which in turn polls from Github. The system operates in a stateless manner, eliminating needs for extra storage, such as Kafka.
This solution hides upstream details from RisingWave and allows users to customize their adapters.
Pros:

Highly extensible. One solution covers all scenarios.

Cons:

Deployment complexity increases.
One additional network hop caused by the WebSync Server.

I have 2 use cases that can be supported through UDFs, one is to pull data using a GraphQL query and update it using a long pooling (which is not supported through a webhook),  and the other is to support GraphQL subscriptions using SSE as the protocol.  Both using OAuth with service account client credentials.
Although both could be supported through custom sources, the time and effort required to develop these sources, the different authentication mechanisms, and the different protocols will make it harder to implement. The UDF will give more flexibility to use custom libraries already developed by the end users, connecting to other data sources not currently supported by RisingWave, and the ability to use a language they are already comfortable with (Java, Javascript, Python, Rust).
I agree we should always prefer a custom data source implemented for RW, but, there are many to be implemented, to name a few: GraphQL (Hasura, WebSockets subscriptions, SSE subscriptions, Multipart subscriptions),  HTTP long pooling, Webhooks, AMQP (RabbitMQ),  cube.js,  vector databases (Qdrant, pinecone)  and there are always nuances on how to connect to the existing ones which can limit what sources we can connect.

@bakjos sorry for my late response.
I generally align with your goal to provide enough flexibility for more sources. However, in terms of implementation, I believe that we should ensure the reusability of connector code. I am not 100% against embedding user code within the database, even though it could make the database difficult to maintain. But I think we should try to minimize the amount of user code unless absolutely necessary. For example, when it comes to Hasura Grafana SSE, I generally prefer offering a resuable, packaged connector instead letting users write everything from scratch.

Even we go toward this direction, I doubt if the UDF framework for stateless computation is suitable for ingestion as well.  🤔  Here are some points should be addressed in the framework:

Backfilling
State management (e.g, consumption progress)

BTW, I wonder why do you want to consume from Vector databases: Qdrant, pinecone?

Hi @neverchanje, would RW consider providing a plugin mechanism for custom Source/Sink? In this way, users who have a special requirement for a particular Source/Sink can implement this plugin, and RW can load this plugin at runtime.
As long as the user adheres to the rules of plugin implementation, such as for sources, whether it can replay from a specific offset? Does it support parallel reading? (like Kafka has multiple partitions and each partition is independent) etc. With these prerequisites, RW may have confidence in interacting with the outside world, and also enhance the flexibility of data integration.
Flink users can achieve this by implementing a SourceFunction or SinkFunction, and placing their jar to the location that Flink can find them at runtime. IMO, there are more than thousands of database systems in the world. RW may not be able to implement all of it, but can implement the most popular data sources such as Mongodb, Mysql and Postgres, so that users can use them out-of-the-box. For those less common data sources users may implement it by themselves.

@ly9chee thanks for this advice. I agree with your opinion that we can introduce a plugin system to enable users to integrate with more sources. I am actually exploring in this direction as well.
Nevertheless, I doubt if using Javacsript for pluggable sources is a good idea. Our current options include Java (we use JNI for several sinks and sources like Iceberg) and Rust. We'll probably not use other languages, at least in the short term.

@neverchanje thanks for your reply! IMO, it's all about the Source/Sink plugin interface that the RW will offer to the user, and the language used to implement the plugin is less critical (even rust is acceptable). For now, it is impossible to ingest data from or sink data to an external data source unsupported by RW, unless there is an intermediate component (such as Kafka) being used to transfer the data. This requires some extra efforts before RW can process the data, also involves thirdparty components, which increases the administrative work.

😄 Even Rust is acceptable. I exactly wrote the same thing in my design proposal.
But please note that CDC is more complex. Our current CDC framework involves both Java and Rust, as we utilize Debezium under the hood, and we also implement our own backfilling logic and shared-source.
I plan to initially prioritize the Source, particularly focusing on HTTP APIs like Github, Salesforce, Jira, etc.

@neverchanje UDFs are not restricted to javascript I am only using it as an example because it supports async and external calls through the fetch API, but the same behavior could be implemented in any of the other languages. Things like state or backfilling could be implemented by exposing some objects/interfaces to the UDF, in deno can be easily implemented.
The plugins are a bit harder to implement in Rust without using FFI, or WASM which the UDFs already support. one of the advantages of using UDFs is that can be easily done at runtime without having to compile/rebuild/redeploy  the entire project.
Vector databases are probably bad examples for sources, since will be more suitable for sinks, but any other database with a javascript/java/rust API could be used as a source through the UDFs.

Things like state or backfilling could be implemented by exposing some objects/interfaces to the UDF

Stateful UDF is not in our plan actually. cc @wangrunji0408 Because it can be trickly to limit the use of state stores while exposing the interface. We might consider opening the gate for UDF for sources, but not for UDF in stream processing.

The UDF itself should be stateless. But we can pass the state as a parameter to the function. Further, we can even expose host functions for UDF to call. This is feasible in both WASM and deno. So I think there's no problem in providing such flexibility while keeping the UDF stateless.

RisingWave WebSync APIs

Instead of supporting arbitrary webhooks via SQL within RisingWave, this solution abstracts all integrations into a single, unified WebSync API.
For example, to subscribe from Github events of a repo, RisingWave will first poll WebSync Server, which in turn polls from Github. The pipeline operates in a stateless manner, without the needs for extra storage like Kafka.
This solution hides upstream details from RisingWave and allows users to customize their adapters.
Pros:

Highly extensible. One solution covers all scenarios.
Easy to implement. It's safer to use 3rd-party libraries in externel component than in RisingWave.

Cons:

Deployment complexity increases.
One additional network hop caused by the WebSync Server.

Seems a valid design for https://github.com/risingwavelabs/risingwave/issues/16025

Note down some thoughts from off-line discussion.
There are generally 2 ways to allow users to ingest from customized sources

Webhook: RisingWave listens on a particular HTTP endpoint and data can be pushed into it.
User-defined source: RisingWave runs a UDF or something similar to pull data.

Both approaches have their fit cases, depending on whether the external system prefers to push or pull data. For example, GitHub naturally publish changes via Webhook, while a 3rd-party database or messaging system would most likely provide a pull-based client.
I just took a look on MZ's webhook support. The authorization is a big challenge. I would rather offload this to a cloud-based stateless service to convert an HTTP request to an INSERT into RisingWave.
Regarding of user-defined source/sink, I agree with this RFC that reusing UDFs seem to be a good idea. Hopefully this can achieve the goal with minimal work and complexity.


Prefer std::atomic over MemoryBarrier when available

Also submitted upstream as https://github.com/google/leveldb/pull/449.
In port/atomic_pointer.h, the preference is to use MemoryBarrier if available, and only fall back to std::atomic if it isn't available.
I believe it would be preferable to use std::atomic, as it may allow better performance, and integrates without changes into ThreadSanitizer.
This PR changes the preference to std::atomic if available.

Can be closed as duplicate of https://github.com/bitcoin-core/leveldb/pull/2


#12 add error handling

Fixes #12
@crhdev would you be able to achieve your desired functionality with this behavior?
You basically have the ability to either stop scheduler execution on error or let it go on depending on the event and exception thrown

Good look for me!


How can we have replication of Redis from one DC to another, but control the nodes Redissson connects to

DC's . in LN and US
Want primaries + slaves in US, just replicas in LN
Want Sentinel HA
Want to hit the primaries+slaves in US when runnng service on US, LN would only be used with reconfigure/failover.

But it looks like the connection pool will try to spread over all slaves?

You can use org.redisson.connection.balancer.WeightedRoundRobinBalancer or implement your own using org.redisson.connection.balancer.LoadBalancer interface


[BUG] One to one relation breaks cache entities relations

I have an entity like :
/**
 * User
 *
 * @ORM\Table(name="user")
 * @ORM\Entity()
 * @ORM\Cache(usage="NONSTRICT_READ_WRITE", region="region_user")
 */
class Language
{

    /**
     * @ORM\Cache(usage="NONSTRICT_READ_WRITE")
     * @ORM\OneToOne(targetEntity="UserInfos", mappedBy="user", cascade={"remove"})
     */
    private $infos = null;

    /**
     * @ORM\ManyToOne(targetEntity="Language")
     * @ORM\JoinColumn(name="actual_lang_id", referencedColumnName="id")
      * @ORM\Cache(usage="NONSTRICT_READ_WRITE")
     */
    private $actualLanguage;

}

I tried to investigate why the cache returns users with actualLanguage = null ( because every user hav an actual Language )
I found that in Doctrine\ORM\Cache\DefaultQueryCache, the function get doesn't seems to resolve my Users linked entities right.
As my users have a One to One relation, I found in $rsm->relationMap, I have the User to Infos relation.
So, my user $hasRelation is true so it doesn't resolveAssociationEntries.
My user doesn't have any $entry['associations'] neither so it don't resolveAssociationEntries after.
I don't know whats wrong here.
I don't know if I don't have any associations because I didn't requested any entities in EAGER mode and if it's normal.
Maybe the enities needs to resolveAssociationEntries each time.
Why don't you resolve them if you have oneToOne associations ?
The only thing I know is that my entities aren't complete when I get them back from cache.
Thanks in advance

I have exactly the same issue

Is this still valid for 2.6.0?
On 26 Dec 2017 11:22, "Phoenix Gao"<EMAIL_ADDRESS>wrote:

I have exactly the same issue
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/doctrine/doctrine2/issues/6051#issuecomment-353951654,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJakB4AaaAVhxVOPfl45HAyiepv3Q8Cks5tEMjwgaJpZM4KFJ1p
.

@Ocramius Currently I'm using doctrine/orm 2.5.13, will try 2.6


DOC: fixed spelling of show_variabless

Coverage increased (+0.4%) to 99.489% when pulling 4a039a94b5bd59ed28f31e85a1069d22d546a9b1 on gdmcbain:patch-2 into 3031d3b3d1a5e212975480021474886abd2ca7c1 on benbovy:master.

Thanks @gdmcbain !


feat: add hook to transform h's arguments

Context
In Vue Test Utils (VTU) we provide two core features: “Shallow Mount” and “Stubs”.
Both shallowMount and stubs enable the user to short circuit rendering a component tree. You can opt into this feature on any mount command (using stubs) or shallowMount command (stubs everything).
This PR adds the necessary functions to enable Vue Test Utils to implement shallowMount and stubs for Vue 3.
Implementation Details
Existing shallowMount functionality in VTU w/ Vue 2
shallowMount is implemented by overwriting $createElement in a beforeCreate hook and conditionally choosing to apply the real $createElement. In VTU we are able to support shallowMounting parent components that use the h function directly.
Implementing shallowMount in Vue 3
Identical implementation using beforeCreate hook is not possible because h is not modifiable for a parent component instance like it was in Vue 2.
Proposed API
Conditionally overload h’s functionality when its parent context wants to stub the component. Do this by using a transformer function to mutate the arguments passed into h.

This function is called transformHArgs and it returns an array of arguments to be applied to all h functions.
Add the ability to reset transformHArgs with a reset function.

Example Usage
Statically override all calls to h to return an h1 tag (this isn't useful, but it demonstrates the API)
import { transformHArgs, h } from '@vue/runtime-core/src/h'
transformHArgs(() => ['h1', 'Hello World'])
h('div', 'Hello') // renders a vnode equivalent to
Hello World

Conditionally modify what is rendered
import { transformHArgs, h } from '@vue/runtime-core/src/h'
transformHArgs((hArgs, instance) => {
    // if the component is in the "stubs" list for Vue Test Utils
    //     return [`stub-${instance.type.name}`]
    // return hArgs // Passthrough to the real h function
})

h({ name: 'my-component' , template: '' }) // renders <stub-my-component/> if it is found in the "stubbed list"

Questions

Should this API be exported from @vue/runtime-core?
Thoughts on how to avoid querying document.body in the test for the ComponentInternalInstance? Do we have an element reference available on the vm still?

Great progress! I think we will need to update src/index.ts to export this:
export {
  h,
  + resetTransformHArgs,
  + transformHArgs
} from './h'

Also no luck using this so far. Minimal repro if what I did:

cd into packages/runtime-core
updated index.ts to export the transform functions like suggested above
yarn build runtime-core
set up a simple babel-node env to be able to confuse esm-bundler.js (also tried with raw node, same result as below)
do this

import { transformHArgs, h } from './dist/runtime-core.esm-bundler.js'

transformHArgs(() => ['div'])

console.log(
  h('span')
)

Final console.log returns a bunch a vnode like so:
{
  _isVNode: true,
  type: 'div',
  props: null,
  // ...
}

Once this is working, it should be type: span.
No luck overriding the arguments so far... Hmm. Seems like once you do import { h }, even if you transform args, the original h is still "cached" or something, and the override does nothing. I didn't even know you could redefine ES modules dynamically like this (maybe you can't?)
I'll keep playing around.


ipc: icmsg: increase stack size of RX work queue thread

Increases default size of stack used by work queue RX thread from 1024 to 2048 1280 to avoid memory issues.
After adding the buffer with the default size of 128 that is allocated on the thread's stack (see #77552), there is too little stack left during heavy stress.
I observed the issues on nRF54H. I was stressing the device (doing different 802.15.4 operations in a loop).
I was consistently seeing weird parameter addresses (ending in z_arm_usage_fault) in icmsg_stack ().
Changing the stack size to >1280 solves the issue. I believe that this should be set as default as this scenario applies to a wide range of users who are stressing the device enough.
Edit: The increase to 2048 is problematic due to memory constraints. Let's increase to 1280, which is just enough.

@e-rk @ankuns

Hi @arnopo, could you review? It is a small change


Regent: potential bug in parallelizer or reduction operator

Compiling the following script
import "regent"

local C = regentlib.c

local Np = 10
local Nx = 2
local Ny = 2
local Nz = 2

fspace Fields {
   xx : double,
   y : double
}
__demand(__cuda, __leaf, __parallel)
task InitMesh( Mesh : region(ispace(int3d),Fields) )
where
   writes(Mesh.{xx,y})
do
   __demand(__openmp)
   for c in Mesh do
      Mesh[c].xx = double(c.x)/(Np-1)
      Mesh[c].y = 1.0/(Np*Np)
   end
end

__demand(__cuda, __leaf)
task InitStats( Mesh : region(ispace(int1d),Fields) )
where
   writes(Mesh.{xx,y})
do
   __demand(__openmp)
   for c in Mesh do
      Mesh[c].xx = double(c)/(Np-1)
      Mesh[c].y = 0.0
   end
end

__demand(__cuda, __leaf)
task AddStats(Mesh : region(ispace(int3d),Fields),
              Stat : region(ispace(int1d),Fields))
where
   reads(Mesh.y),
   reduces+(Stat.y)
do
   __demand(__openmp)
   for c in Mesh do
      Stat[c.x].y += Mesh[c].y
   end
end

task main()
   var r = region(ispace(int3d,{Np,Np,Np}),Fields)
   var s = region(ispace(int1d,Np),Fields)

   var cs = ispace(int1d,Nx)
   var ps = partition(equal, s, cs)

   var cr = ispace(int3d,{Nx,Ny,Nz})
   var pr = partition(equal, r, cr)

   InitMesh(r)
   InitStats(s)

   -- This parallel does not work
   __demand(__parallel)
   for c in cr do
      AddStats(pr[c], ps[c.x])
   end

end

--regentlib.start(main)
regentlib.saveobj(main, "Example.o", "object")

produces the error:
loop optimization failed: argument 2 is not provably projectable or invariant
         AddStats(pr[c], ps[c.x])

If the '' __demand(__parallel)'' in the main task is commented, the script is successfully compiled and correct results are produced.
Am I doing something wrong with the reduction privileges?

The problem is the use of c.x in the index expression of ps[c.x]. It should be possible to allow this, just will take a little time since everyone is crunching on SC papers at the moment.

Ok, thanks for replying.
Knowing that I am not doing anything massively wrong is already something.
Let me know when you will be able to implement this feature.

SC deadline is April 10, if you don't see a reply by a couple days after that, please ping this issue again.

Should be fixed in 2f18640cf081305939e833178a1ad25a92e590a5.

Yes, It works. Thanks


CIP and CIAO

readme needs updating to articulate the acronyms of CIP and CIAO

found it on the nhs-ciao repository


Add support for API keys

https://github.com/pypa/warehouse/issues/994
This lets users provision an API key, and then use that API key with
forklift.legacy.file_upload. It uses macaroons so advanced users can
further restrict usage of their API key.
This work was originally started at https://github.com/lukesneeringer/warehouse/tree/tokens at the 2018 US PyCon.
It adds a section on /manage/accounts where you can create a new token:

Then a splash shows up with your new API key (note that this key is just on my local dev instance, not a real production key):

And the key is listed on /manage/accounts:

You can then use the key with something like:
curl -X POST "http://<IP_ADDRESS>/legacy/?:action=file_upload&version=0.1&name=<package name>&account_token=<key from splash>

Macaroons allow you to further reduce the scope of the API key. For example:
>>> from pymacaroons import Macaroon
>>> macaroon = Macaroon.deserialize('MDAxNmxvY2F0aW9uIHB5cGkub3JnCjAwMjdpZGVudGlmaWVyICJhIHB1YmxpYyB0b2tlbiBhcGkgaWQiCjAwMzFjaWQgaWQ6IGE2YmQ3N2NiLWIzY2QtNDcwNS05N2JkLWEwMzZlMWZjYTkyMQowMDJmc2lnbmF0dXJlIIqV_7ozeE7EXj_xdacB_zUkUJTOT3l9wgjNfSWMuDurCg')
>>> macaroon.add_first_party_caveat("package: exampleproject")
<pymacaroons.macaroon.Macaroon object at 0x103f24630>
>>> macaroon.serialize()
'MDAxNmxvY2F0aW9uIHB5cGkub3JnCjAwMjdpZGVudGlmaWVyICJhIHB1YmxpYyB0b2tlbiBhcGkgaWQiCjAwMzFjaWQgaWQ6IGE2YmQ3N2NiLWIzY2QtNDcwNS05N2JkLWEwMzZlMWZjYTkyMQowMDIwY2lkIHBhY2thZ2U6IGV4YW1wbGVwcm9qZWN0CjAwMmZzaWduYXR1cmUgksBAiGLCnUJxORDKDc-XV0ZkrKGG3yglj0WYR8OazVEK'

... and then the key is scoped to uploading just that package.
There's many places this pull could go from here. There should probably be additional testing, particularly off the happy path. We could add a first party caveat to support the key expiring after a certain date. Make instead of package it should be packages so you can support restricting it to a set of packages? You wouldn't want to support multiple package caveats on a Macaroon - otherwise someone who gets your Macaroon could just add another package, defeating your earlier restriction!
Feedback welcome!

Thanks! I finally figured out how to run the linter locally. I'll look at the coverage issues in the meantime.

I accidentally hosed this branch when trying to update it / resolve merge conflicts last night. See instead #4949.


Refactor getMetadata to use await/async

This reduces the nesting, and makes the logic flow easier to understand (for me, at least).

PTAL; I included the individual commits along the way as maybe they're easier to review. (Maybe not?)


e100_base-relase: 0.0.0-0 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository e100_base-relase to 0.0.0-0:

upstream repository: https://github.com/gaitech-robotics/e100_base.git
release repository: https://github.com/gaitech-robotics/e100_base-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.7.2
previous version for package: null

Holding for sync .


Support Python 3.7

Update support status in README.md
Update .travis.yml (see also: https://github.com/travis-ci/travis-ci/issues/9815)

Coverage remained the same at 86.641% when pulling 09e0e508cfe2a6c88ff2057651704af0267c67db on tats-u:support_py37 into 68d4005284b72a891d0c0f81afabea087fc45960 on k2kobayashi:master.

@tats-u Thanks!


Simplifying observation/photo/sound licenses

When someone joins iNaturalist, they get separate CC-BY-NC licenses added to their observations, photos and sounds unless they un-check the 'Yes license my...' box.
Not surprisingly, the vast majority of iNat users (78%) go with these settings (the NC-NC pink block in the lower left of the graphs). There's another cohort of around 5% who uncheck the box (the ARR-ARR pink block towards the center of the graphs).
The interesting cohort, is the cohort that modifies these default bundled settings. I thought the remaining pink blocks on this graph represented large cohorts that actively changed their settings, but unfortunately I think these are mostly artifacts for how we've rolled things out over the years (e.g. switching from CC-BY to CC-BY-NC, rolling out licenses first, and then sound) and how people opted in or out of these features as they were introduced, so I'm not sure there's a lot to learn from the data without very rigorously retracing exactly how we rolled things out... oh well.

But it does seem that most users aren't doing much other than leaving the settings checked, unchecking them, or perhaps actively altering things in a way that makes photos and/or sounds AllRightsReserved but not Observations (if these aren't artifacts). But its clear that people are NOT opting out of Observations licensing independently of the 'bundled opt out' which is almost certainly driven by concern over media (not observations).
With that in mind, here's a proposal to:
(a) make it so that observations must be licensed for new users
(b) combine photo and sound licenses for new users
in order to greatly simplify what it means for an observation to be 'licensed'. With these changes, 'licensed observations' will have CC licenses applied to their media (photos/sound). 'unlicensed observations' will have media that is AllRightsReserved.
In the iNat terms of service we can make it clear that the non-media portion of observations created on iNat are considered licensed content without explicitly displaying licenses for this non-media portion of an observation.

For what it's worth, one can't really copyright 'an observation', in the sense of copyrighting the fact that you observed or reported observing something, only copyrightable element (other than media) is the creative content in the writing of a description and/or comments if any.

@tnywlls, that's correct in US copyright law, but when we originally introduced licensing we thought it was already confusing enough, and trying to convey the fact that only an observation with a description or tags could even be considered copyrightable in the US was too complex. Also, we are an international website, and IP laws concerning databases vary quite a bit across national jurisdictions, so your statement is not necessarily correct elsewhere (the US is actually kind of progressive in this regard). http://opendefinition.org/guide/data/ provides a good overview. To be really solid about licensing, we should probably consider a different, more data-oriented license for the observation
Scott, are you proposing that we remove the ability to declare a license for your observations, or just remove that option from the signup process?

Thanks for the link, a good summary.  My point is that I wonder what someone expects when they copyright an observation on iNat.  Do they really care whether you copy their text, or are they thinking they are protecting the information that they saw xyz at abc on nnnn:nn:nn.   Or do they think they are invoking a database copyright for all their observations?
I think the cleanest, and most useful approach is to just make it a condition of use of the site that any observation data is openly licensed for all to use, but they may restrict usage of media.

I feel like I've noticed more people recently who have "all rights
reserved" on their observations (and media) and they seem to:

be using a mobile app.
often have numbers in their username.
have their full name on their profile.

Here are a couple of examples from today:
http://www.inaturalist.org/observations/2346107
http://www.inaturalist.org/observations/2346706
http://www.inaturalist.org/observations/2346315
This leads me to suspect that the default setting for creating a new
account from a mobile app via Facebook (or google) is ARR rather than CC
BY-NC. Can someone confirm? Does creating an account via FB or G+ apply ARR
settings by default? Happy to start a new thread for this if appropriate.
Couldn't test this myself as my Facebook account is already linked to my
iNat account.
On Thu, Oct 15, 2015 at 6:54 AM, tnywlls<EMAIL_ADDRESS>wrote:

Thanks for the link, a good summary. My point is that I wonder what
someone expects when they copyright an observation on iNat. Do they really
care whether you copy their text, or are they thinking they are protecting
the information that they saw xyz at abc on nnnn:nn:nn. Or do they think
they are invoking a database copyright for all their observations?
I think the cleanest, and most useful approach is to just make it a
condition of use of the site that any observation data is openly licensed
for all to use, but they may restrict usage of media.
—
Reply to this email directly or view it on GitHub
https://github.com/inaturalist/inaturalist/issues/637#issuecomment-148350457
.

--
Carrie E. Seltzer, Ph.D.
National Geographic's Great Nature Project
www.greatnatureproject.org

Good sleuthing Carrie, I made an issue https://github.com/inaturalist/design/issues/49

Once we implement this, I propose we get rid of the bottom right section of Obs/show now dedicated to observation licensing and flagging inappropriate obs by doing the following:

move licensing edit link to the photo license section below the photo (black arrow)
add 'flag' link to Appropriate section in Data Quality Assessment (red arrow)
add language about what inappropriate means to modal for flagging
(green arrow)

Also, looks like some weird formatting in the Appropriate section currently when obs are flagged:

Scott, are you proposing that we remove the ability to declare a license for your observations, or just remove that option from the signup process?

@kueda sorry just saw this, I'm proposing we remove the ability to declare a license for observations. Specifically:
Step 1:
Wire up Signup so that:
Checking the 'license my content' box sets photo: CC-BY-NC, sound: CC-BY-NC, observation: CC-BY
Unchecking the box means photo: nil, sound: nil, observation: CC-BY
Step 2:
Alter Account UI so that:

For new users, instead of 3 choosers there's just a single 'Default Media License' chooser, e.g. like this but labeled differently:

For old users add the following transition tool above the existing Licensing UI:

We've simplified how licenses work and now only support a single media license for photos AND sound rather then separate licenses for observations, sound and photos. For new users, all observations are automatically given a CC-BY license that can't be altered and a single Media license applies to both photos and sounds. As an existing user, nothing has changed for you, but we encourage you to adopt this simpler system. This will:
1) apply a CC-BY license to all of your past observations and set this as your license moving forward
2) apply your current photo license to all of your past sounds as a single media license
3) simplify this interface so that there is just a single media license chooser
(Yes please) (No thanks)

Where 'Yes Please' changes the user's content and switches to the new user License UI
Step 3:
Stop displaying observation licenses on observation/show for all observations:


There is no role found in ansible from host machine while vagrant provision

Hi, I haven't run this in a while (since it wasn't created). I had a quick look this afternoon and the galaxy stuff is redundant so I've removed it. I've reduced the number worked and managers so it's more manageable. It builds docker and the swarm but blew up installing consul.
I'll try and have a look tomorrow and see what's going on.

is there any update on this

I'm not going to able to look at it till next week tbh.
What are you trying to achieve? It was just a proof of concept for running a cluster locally. Something that I knocked up and haven't touched since. It did work when I did it.
I'll try and find some time later but im away for the weekend so wont get any time to help out till next week

i want to spin up this instances
On Fri, Apr 21, 2017 at 4:57 PM, James Morgan<EMAIL_ADDRESS>wrote:

I'm not going to able to look at it till next week tbh.
What are you trying to achieve? It was just a proof of concept for running
a cluster locally. Something that I knocked up and haven't touched since.
It did work when I did it.
I'll try and find some time later but im away for the weekend so wont get
any time to help out till next week
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jamesdmorgan/nomad-cluster/issues/2#issuecomment-296166676,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOnTbbdkuronfAat72dWQ4kU0qeJMSigks5ryJKtgaJpZM4NDFXR
.

--
[image: --]
kunalsing thakur
[image: https://]about.me/kunalsingthakur
https://about.me/kunalsingthakur?promo=email_sig&utm_source=email_sig&utm_medium=email_sig&utm_campaign=external_links

I have made a couple of slightly hacky changes to correct docker / docker-py and change ansible docker -> docker_container and it now spins up and I can see the UI on http://<IP_ADDRESS>:8000/


core validation: possible image state false positive

Hi,
we just changed some stuff in our renderer to take advantage of not needing to transfer images to their use state if the operation would replace the complete content of that image anyways. But the layer complains about the wrong layout. In our specific case, we copy our backbuffer color image into the swapchain image. The swapchain image is kept as is after it was acquired. After the copy operation the needed barrier from transfer dst to wsi src is done, as the content of the image should be preserved for presentation (so get from wsi -> copy (and forced state to transfer dst by the copy op) -> barrier (transfer dst -> wsi src) -> submit to wsi).
So this is also a question if this is a bug by us or a bug of the layer?
As i read the spec, there is no requirement to transfer the state away from wsi src.

I believe this is your bug.
Even if you don't care about preserving contents, a subresource must be transitioned to the layout you use it under. If you don't need to preserve the contents, it's always valid to specify VK_IMAGE_LAYOUT_UNDEFINED as the previous layout, which should make the actual cost of the transition very small, but you must still do it:

VU for vkCmdCopyImage:
dstImageLayout must specify the layout of the image subresources of dstImage specified in pRegions at the time this command is executed on a VkDevice

If you disagree, point me at the spec language that supports your theory of not needing a layout transition if you replace the entire content.

I think you are correct.


Cross repo tests for core PR #19652

Cross repo tests for https://github.com/ManageIQ/manageiq/pull/19652 (MiqAction)

Merged, closing.


⚠ DesiTorrents has degraded performance

In 0fd1b8e, DesiTorrents ($DST) experienced degraded performance:

HTTP code: 200
Response time: 4727 ms

Resolved: DesiTorrents performance has improved in cbf3e24.


add time attribute into the testsuite element

Add time attribute into the <testsuite> element of the Xunit output file.

Tests are needed. See atest/README.rst for details about creating them and the existing xUnit related tests for examples. You ought to be able to add a new test to the existing test suite.

Hello, @pekkaklarck
Can not run tests as follow:

Is there anything else to be done to run the tests?

Closed in favor of #2986. Notice @kanchi240 that you could also just keep working in the same branch and the PR would be updated automatically.


support django 2.0

Do you plan support django 2.0 ?

sure, but I have to wait until django-filter and django-cms support Django-2.0, before I can start with the migration process.


A few minor issues

DW20 pack v1.1.1, Not sure if it is included by FTB I may have added it.
3 Minor problems.
1 The Experience crafter CAN be over filled, I think it is by giving it a smaller amount of Experience then trying to fill it to max, the bar will display something like 1490/1395. And it takes 1395 from the player if they have it.
2 Particles, I think absorption is the one I am having difficulty with, it is very in-your-face, it is fine if I turn Particles to minimal in the video settings ....... but that is universal and affects particles like Botania which is only showing when looking at Botania operations ..... not at all times in FoV
3 I managed most of the mod without looking at Google, Youtube or your Wiki but it took the Youtube tutorial link on the Wiki to show me why trinkets have both a 5x5 recipe and a 3x3 recipe (within a 5x5 layout), worst is that I had actually watched the tutorial back around release and had forgotten.
Solutions suggestions
1 Limit the amount taken to "1395-current stored" and or provide an option to remove essence.
2 lower the particle level or maybe include a cheap item to craft with the trinket to lower particle effects. Maybe each craft lowers particles by 10/100, so using it 10 times removes completely or 9 times is equal to Minimal
3 Add a tooltip "this recipe removes effects"
I am enjoying the mod, I like creative flight without needing to travel to the End but it might be a little cheap ... then again I am swamped with Ghast essence using 1 captured Ghast and Ars nouveau Drygmy's.

I'll check it out. Thanks for the report. About particles, that's a vanilla thing. Not much I can do about that. I believe there are other mods that can turn those off though

BTW, the 3x3 recipe for trinkets is not for removing effects. It's for reforging the trinket to give it better effects

vanilla has an option to hide particles itself, check the function with additional parameters on adding effects

Correct.... it also hides ALL particles, not just those that persist in the players FoV, thing like Botania mana and other particles that are needed to see a mod is working .... not that it is available ATM but it would also turn off the marker for Astral Sorcery shards and the particle that show where to best place altars. I am sure that other mods currently available would also be hard to use with particles hidden. So Yes you can..... but it is not an ideal solution.


Deploy fails due to log groups not being torn down

If you run a system test with buildDeployTest.sh, tear it down, then buildDeployTest.sh again, it fails to deploy due to log groups not being deleted during the tear down.

This one has got me too several times...really annoying.

One approach is to use a different instance ID each time, in case it's valuable to keep the log groups around. We should probably at least automate deleting the log groups as an optional part of the tear down scripts.

We'd probably want to be able to delete an instance of Sleeper, then deploy a new one with the same instance ID. That seems like something that should work.
We could add some random or date/time-based identifier to the log group name, but that would make it harder to read.

There doesn't seem to be a good solution for now.

The tear down scripts already delete things that were configured to be retained. If that's what they do they could do that for log groups as well.

It doesn't look like there's a good way to find all the log groups that need to be torn down. They don't seem to be listed as resources in the CloudFormation stack, and tags set on the stack aren't propagated to the log groups.
We might be able to examine each Lambda to find the log group associated with it, and something similar for ECS. That would be a pretty complicated work-around though.
There's also this issue where when you flag an S3 bucket to auto-delete its objects when it's torn down, the Lambda function that does that gets a log group with a retention policy of never expire:
https://github.com/aws/aws-cdk/issues/24815
There's also an option of automatically deleting all log groups that aren't associated with a resource deployed via CloudFormation, as seen in this tool:
https://gist.github.com/seeebiii/c91815200915a17131c9d908c525c357
That will only work in cases where all your Lambdas are deployed via CloudFormation, so we can't build it into Sleeper.


Add a prototype of the model compilation configs for SD

Looks like there's a lint failure. Please run
black --line-length=79 .


HowTo return an error condition to Alexa ?

Imported issue from https://bitbucket.org/xoseperez/fauxmoesp/issues/97
Walter Steinchen created an issue 2019-07-03
If for whatever reason my physical device has an error/or is not reachable .. how can I return that back, so that Alexa says
f.e. “pink lamp is not reachable”.
Many Thanks!

When I try this, after a couple seconds I get a response from Alexa like "Pink lamp is not responding" (simply tested by powering down my ESP and telling Alexa to turn on the device)


The netty-all.jar is missing the native-image.properties files from sub-modules

The GraalVM Native Image configuration files under META-INF are automatically included in the generated jar of the corresponding module, e.g., native-image.properties is included in the netty-codec-http.jar, but not in nety-all.jar. I looked around the Netty build system but couldn't figure it out. It looks like the sub-module jars include the files in the corresponding META-INF directories automatically.
cc: @pmlopes

I don't know the inner details of the netty-all build process. I guess it would be nice to have but I am at the same level as you here...

I will have a look.

Fixed by https://github.com/netty/netty/pull/9518... PTAL


Server does not start with empty mounted directories (/var/lib/go-server /var/log/ ...etc)

ubuntu@ubuntu-xenial:~/dev-env-setup$ docker logs -f linux_gocd-server_1
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 7
Starting Go Server ...
[Thu Jun 16 09:41:55 UTC 2016] using default settings from /etc/default/go-server
/usr/share/go-server/server.sh: line 180: /var/log/go-server/go-server.out.log: Permission denied
/usr/share/go-server/server.sh: line 181: /var/log/go-server/go-server.out.log: Permission denied
Jun 16 09:41:55 82e1892ae7d1 syslog-ng[15]: syslog-ng starting up; version='3.5.3'
Error trying to validate file agent-bootstrapper.jar: java.io.FileNotFoundException: /var/lib/go-server/agent-bootstrapper.jar (Permission denied)
Error trying to validate file agent.jar: java.io.FileNotFoundException: /var/lib/go-server/agent.jar (Permission denied)
Error trying to validate file agent-launcher.jar: java.io.FileNotFoundException: /var/lib/go-server/agent-launcher.jar (Permission denied)
Error trying to validate file cruise.war: java.io.FileNotFoundException: /var/lib/go-server/cruise.war (Permission denied)
Error trying to validate file historical_jars/h2-1.2.127.jar: java.io.FileNotFoundException: /var/lib/go-server/historical_jars/h2-1.2.127.jar (No such file or directory)
Error trying to validate file cruise-config.xml: java.io.FileNotFoundException: /etc/go/cruise-config.xml (Permission denied)
Error trying to validate file config.properties: java.io.FileNotFoundException: /etc/go/config.properties (Permission denied)
Error trying to validate file cruise-config.xsd: java.io.FileNotFoundException: /etc/go/cruise-config.xsd (Permission denied)
Error trying to validate file jetty.xml: java.io.FileNotFoundException: /etc/go/jetty.xml (Permission denied)
Error trying to validate file go_update_server.pub: java.io.FileNotFoundException: /etc/go/go_update_server.pub (Permission denied)
/var/lib/go-server/db/h2deltas/2_create_indexes.sql (No such file or directory)
/var/lib/go-server/db/h2db/cruise.h2.db (No such file or directory)
Error trying to validate file log4j.properties: java.io.FileNotFoundException: /etc/go/log4j.properties (Permission denied)
== Thu Jun 16 09:42:26 UTC 2016: Waiting for Go Server dashboard to be accessible ...

Is there no way to do this without copying the files from inside the container?

I had to create the go user and group and chown the volumes. Is there any other way?

Hi! I solved it by using a named volume in docker compose.
`
version: "2"
volumes:
gocd-server-volume: {}
services:
gocd-server:
image: gocd/gocd-server
ports:
- "8153:8153"
volumes:
- gocd-server-volume:/etc/go
- gocd-server-volume:/var/lib/go-server
- gocd-server-volume:/var/log/go-server
`

Marking closed. Do you think there's scope to update the README with better instructions?

Yes. Instead of telling users to use data-only container the README should say that they should use named volumes because that is the easiest way to do it and you don't have to create a container.
docker run -d -i -t -p 8155:8153 -v gocd-server-volume:/var/lib/go-server -v gocd-server-volume:/var/log/go-server -v gocd-server -volume:/etc/go gocd/gocd-server
The reason is that when you use docker-compose volumes mapped directly to host the owner of the folder mounted folders is the same as the one in the host. When you use named volumes (as I did in the previous comment) this problem is solved because the folders are still owned by the right user.
I had this problem also because I'm new to docker and I didn't know how named volumes worked.


How to use this library in an Angular 2 spa

I'm wondering if there are any examples or guidance available on how to use this library in an angular 2 app?
I'm not hugely experienced in javascript development but I've had a go at using oidc-client in a simple app.  However as soon as I add a reference (to the compiled version) in my index.html, the angular system seems to stop working.  Triggering a click event starts it up again and data is rendered to the view as normal .  Sign-in, get user, sign-out etc all seem to work well.  However the ui does not get updated (unless I trigger a click afterward).
Is there something I'm missing that will get this playing nicely with Angular 2?

I don't know Angular2, but I suspect they use a module system. This means you should be loading oidc-client from the "lib" folder (not the "dist" folder).

Ah now it's working better, thank you.  If I import the library like this:
import * as Oidc from 'oidc-client/lib/oidc-client.js';
it seems to be working good at runtime.  I'm using typescript and the compiler is not happy but I guess I just need a definitions file or something.

Yes, I have an open issue for TS file. Feel free to contribute one if you get the time.

does this seem right for the tsd? oidc-client.d.ts.... I haven't tested it yet. if someone has the time let me know.

@jmurphzyo i'll take a look when i can. also... i don't know TS... so i'll just assume all the syntax is legit.

@brockallen The only part that might be off is the JoseUtil because of the outside dependency. I made a custom .d.ts file I will post it as well. jsrsasign.d.ts it is missing several modules but those were the ones I saw odic depended on

I think the only things we really need to document are the public APIs, right?

yes, I actually just rewrote the library in typescript and those were all the definition files..

Also using this for Angular 2.
@jmurphzyo are you going to share the typescript version?
@brockallen if either @jmurphzyo did a pull request, or I rewrote this in typescript and did a pull request would you be happy to move to typescript?
I could set it up as a UMD module so it will still work as a vanilla lib if you are interested.

I'm really struggling with exactly how to get the UserManager working with an Angular2 spa. I want to automatically redirect to the login page when my spa page loads, but I seem to be having issues with how that flow should work.  Can you guys please provide an example for this scenario?

Call getUser() at startup and if the returned value is null, then call signinRedirect(). Does that not work for you?

@brockallen Thanks for the quick response. That's what I'm doing in my init:
let userPromise = this._userManager.getUser().then(function (user) {             if (!user) {                 console.log("No user returned. Calling SigninRedirect!");                 self._userManager.signinRedirect({ data: 'some data' }).then(function () {                     console.log("signinRedirect done");                 }).catch(function (err) {                     console.log(err);                 });             }         });
And this seems to get stuck in an infinite loop.

You should use a dedicated callback page for handling the response from the token service -- this way the sensitive handoff has fewer points of attack. Once it's done processing the callback then redirect back to your main app URL.

I'll give that a shot. Thanks again for the quick response and the guidance. I love the work you guys have done with IdentityServer and this library. Making my job much easier!!

I love the work you guys have done with IdentityServer and this library. Making my job much easier!!

Thanks. Feel free to encourage your company to hire us for an architecture review, code review, or something else like that :)

@brockallen The separate callback page did the trick. Thanks again!  I'll see what I can do to get you guys in sometime :)

@tstone84 having some troubles of our own. This might help you or anyone else using a # in their URL.
As you can see below our SPA already has a # in the URL
redirect_uri: 'http://localhost:3000/#/main/login?', // this address and tenant

SigninResponse.js calls parse URL with a hard coded #
var values = UrlUtility.parseUrlFragment(url, "#");

We were getting an error that the id_token was not found as the response was being parsed from /main/etc.... Our parameters were being returned all as query parameters after the ?
To solve this we did a string replace
userManager.signinRedirectCallback(href.replace('#', '').replace('?', '#'))
     .then((result) => {
           console.log('result', result)
     })

@brockallen  would be nice to have an optional param
var splitFrom = '#' || param.splitFrom;
var values = UrlUtility.parseUrlFragment(url, splitFrom);

Not sure the best place to set this option?

@vespertilian there's already support for this. you would just call this instead:
mgr.signinRedirectCallback(thePartOfTheHashYouNeedToHaveValidated).then(...)

IOW, if you're doing routing or something else in angular, then you parse the url using whatever framework you're using and pass the rest of the hash fragment to the *Callback APIs.

@brockallen Makes sense. Thank you for your work on this and your quick response.
Our current solution feels a little inelegant.
In angular we can also pull these param's off the URL. Do you think passing them in directly would be better? Does the library support this? Happy to help out if you like.
Also think about my offer to Typescriptify the project for you. Will still work as a vanilla JS library.  One cool benefit of Typescript is you can use TypeDoc.
We have been using http://typedoc.io/ to document some of our internal modules in Typescript.  You get lots of docs for free.

In angular we can also pull these param's off the URL.

Well, again, any given app can form that URL in any way. The only thing you need to do is pass the non-app part to the API.

@vespertilian did you see the pr this guy issued? #63

I have everything working well at this point, except for renewing access tokens. I have an Angular2 SPA and I'm capturing the AccessTokenExpiring event and allowing the user to decide to continue working or logout.  The logout was easy. However, i'm struggling with which userManager method to call to refresh my data access token. It seems if I use signInSilent(), I will need to provide a silent redirect uri, which I assume the Idsvr will redirect to, which I'd rather not have, as it would redirect from where the user is currently working.  Is there a solid example of what I should be doing??
Thanks!!

@brockallen If you want I will create a sample angular 2 project for you to put in the samples but the documentation would be fairly poor because I am limited on time but it's the least I can contribute!

@jmurphzyo sure, that'd be great. and we're all short on time :)

here's a quick example project of using this lib with angular 2. I threw it together relative quick and did a fast write up of how to get it working.
https://github.com/jmurphzyo/Angular2OidcClient

@jmurphzyo thanks. i added it as a link to the wiki for samples.

tstone84, I am entering an infinite loop as well. Can you share how you called this callback.html/ callback.component.ts page? A few lines of code on how this is being done?
This clientside code has me a bit confused. .NET was easier. Thanks

@DoubleExposure We ended up using a separate static callback.html page as Brock recommended. It's just a blank .html page with a script.  Obviously, you will want to redirect or add additional logic to redirect where you would like the user to be redirected to. Here's the code in that page:
<script>            new Oidc.UserManager().signinRedirectCallback().then(function(user) {                console.log("signin response success", user);                window.location.href = 'index.html';             }).catch(function(err) {                 console.log(err);             });  	</script>

@tstone84 I have trying static callback.html on new angular 4.0.0 but i can't, have you try it?

@kodelapan Yes, we are using a callback.html with Angular 4.  The js in the html page looks something like this:
<script>            new Oidc.UserManager().signinRedirectCallback().then(function(user) {                console.log("signin response success", user);                window.location.href = 'index.html';             }).catch(function(err) {                 console.log(err);             });  </script>

Thanks, successfully after update angular to 4.0.2 and node 6


VC 2.0 add validUntil and validBefore

Features:

changes the DateRegexp to an XML schema DateTime and expands tests on it
move expirationDate into the VC 1.0 validators and only checks date when mode is verify
adds validUntil and associated tests
adds validBefore and associated tests
make some minor corrections with test data for better consistency

Codecov Report

Merging #168 (bf5c4b2) into update-vc-2.0 (fdc98f6) will increase coverage by 0.91%.
The diff coverage is 97.93%.

:exclamation: Current head bf5c4b2 differs from pull request most recent head 352f41a. Consider uploading reports for the commit 352f41a to get more accurate results

Additional details and impacted files
@@                Coverage Diff                @@
##           update-vc-2.0     #168      +/-   ##
=================================================
+ Coverage          89.43%   90.35%   +0.91%
=================================================
  Files                  5        5
  Lines                994     1057      +63
=================================================
+ Hits                 889      955      +66
+ Misses               105      102       -3

Files
Coverage Δ

lib/index.js
90.56% <100.00%> (+0.84%)
:arrow_up:

lib/helpers.js
92.39% <95.65%> (+2.39%)
:arrow_up:

Continue to review full report in Codecov by Sentry.

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

@aljones15 it looks like this PR has moved (or is moving) well beyond validUntil and validBefore. Is that correct? If so, we should relabel the PR at least.
I'm also a bit concerned about us ending up with one massive PR to review. Can we do more, smaller PRs against a non-main branch (as this one is against update-vc-2.0)? That would make reviews much faster, safer, and more sane. 😃

I will refrain from merging any further PRs into this PR, but as this PR and the other PR: https://github.com/digitalbazaar/vc/pull/170 had both been approved it seemed safe to merge the two.

I will refrain from merging any further PRs into this PR, but as this PR and the other PR: #170 had both been approved it seemed safe to merge the two.
As for this PR moving beyond validUntil & validBefore that was not intentional, but the feature making credentialStatus.id optional branched from the validUntil branch so it couldn't be aimed at the core VC 2.0 branch/PR.

Mostly, my aim is to keep topics clear...and now it's pretty muddied what's going on.
Also, as @JSAssassin mentioned earlier, the fields are validFrom and validUntil--and we should change this PR to match.
Thanks!

@BigBlueHat @davidlehn please double check this as this is your last chance before merge into update-vc-2.0.


fix pdb-dev endpoints

@sureshhewabi - i think when you manually copied over the changes to add accession to pdb-dev end point mistake was made. This PR fixes.

Sorry about that


[Request] A6000: Allow camera operation while charging.

Currently if you plug in a charger on an external battery pack, you cannot use the camera or even access the menu.
I tested an RX100 and noticed that you can use the camera while it is charging.
I don't know if it's possible, but I would like to use my a6000 while it is connected to a battery pack.

+1

OMG YES +1
this has been a killer on the a6000, battery life sucks

+1

if its not possible over software, i suggest you getting a battery dummy for NP-FW50 (around 15-20$)
and a 7.4v li-ion battery pack (commonly used in bike flashlights. must be a 2S / 2Cell li-ion/lipo.

+10086

Like to have this feature!

+1

THISSSSSSS <3

+1

+1

+1


Sign bridged windows binaries

This separates the provider build/packaging steps so we can add signatures before uploading.
Signing is done using Jsign, which has the advantage of being able run on Ubuntu.
Confirmed the signature is OK on a Windows VM:

Refs https://github.com/pulumi/home/issues/3766

Validated here https://github.com/pulumi/pulumi-xyz/actions/runs/12242813485/job/34151349361

@blampe @danielrbradley this now breaks the third party providers I rolled out ci-mgmt to:
https://github.com/pulumiverse/pulumi-acme/actions/runs/12248873082/job/34169377386
https://github.com/pulumiverse/pulumi-scaleway/actions/runs/12248856577/job/34169268696
https://github.com/pulumiverse/pulumi-cockroach/actions/runs/12248837708/job/34169220478


decapitalise user in remove user button

Context
Content change to change Remove User -> Remove user as per conversation with James.
Link to Trello card
https://trello.com/c/8iOeOIVi/4322-change-invite-and-delete-user-terms-in-service-to-add-user-and-remove-user
Things to check

[x] This code does not rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] Required environment variables have been updated added to the Azure KeyVault

This should also be updated -> https://github.com/DFE-Digital/apply-for-teacher-training/blob/main/spec/system/provider_interface/remove_provider_user_spec.rb#L76


(@Banded Body Press) gen9alphabetsoup: Annihilape,Timburr,Snow Warning+Cloak ban

@Banded Body Press: "Annihilape,Timburr,Snow Warning+Cloak ban"
Created via Iolanthe on Sun, 05 Nov 2023 15:38:33 GMT.

Superseded by https://github.com/OperationTourCode/OTC/pull/383/files


Transfer Thumbs Up (Pandora) to Love (Last.fm)

I'd like (love?) to see the option to sync thumbed up tracks in Pandora as loved tracks on Last.fm, and maybe the ability to removed thumbed down tracks from Last.fm library.  Maybe the same with services such as Grooveshark and Youtube as well?

Requesting this issue be closed!

You can close it yourself, you know

Was I tired enough to not notice that?
Thanks ;)


Zip file upload to data stream endpoint fails

When uploading a zip file to the data stream endpoint, it fails with a
[log] [CAMS DEBUG] RESPONSE: 500
      {"statusCode":500,"exception":"java.lang.NullPointerException","message":"Cannot invoke \"org.springframework.web.multipart.MultipartFile.getBytes()\" because \"zipFile\" is null","path":"POST /api/data-stream-service-zip"}

complaining that there is no zip file.
But - as you can see from my debug window, there is a file in the POST request:

In general, there is no documentation (as I can see) on exactly how the HTTP request should look like (headers, content types, etc).

As discussed, the compressed data does not require to be a separate file. We will use ByteArray, Gzip compressed Json.
A endpoint for testing purposes is available
POST /api/data/zip
This endpoint is tested using binary data achieved from
function createGzipFile(filename, jsonData) {
    const jsonString = JSON.stringify(jsonData);
    const buffer = Buffer.from(jsonString, 'utf-8');
    zlib.gzip(buffer, (err, compressedBuffer) => {
        if (err) {
            console.error(err);
            return;
            }
        // File created only for testing purposes
        fs.writeFileSync(filename, compressedBuffer);
    });
}

However, if we decided to used this method, the ByteArray should be handled by a HttpMessageConverter in the backend, before the request reach controller

Just tested with a small payload and it seems to work.

Just tested uploading 10 unique measurements - and got them back again. All good.

Testing endpoint is removed, we keep old endpoint: /api/data-stream-service-zip


edit tmp files instead of actual so the script can be rerun multiple times

https://github.ibm.com/IBMPrivateCloud/roadmap/issues/63828
Ability to deploy the peripheral resources required for BR of cs db, mongodb, zen 4 & 5, and keycloak. Also deploys the utility resources used in SF.

ready for review now


Remove note that session setting affects new sessions

Missed this while reviewing https://github.com/crate/crate/pull/17032

Let's port it?

Let's port it?

Port where? The other PR that incorrectly added it wasn't backported


How to use existing dashboards as scenes objects

Is that possoible to use existing panels in scenes app ?

no, but the options & fieldconfigs are the same


Export Starfield Mesh Tool does not show up after installation

I installed the addon (Install...>ZIP file) and enabled it. For some reason, the tool does not show up on the tools sidebar widget. There is a tool called "Export Material" that asks for a texconv.exe file path, which I provided, but I cannot figure out how to select the Starfield weapon mesh that I want to work on.

It is looking like I may be referring to an old tutorial. When I did File > Export NIF, that worked. I also noted that MESH files were now deprecated in 1.2, so I am assuming that I can use these NIF files without doing anything else. Feel free to correct me otherwise.

Resolved with updated version of package. Getting assistance on Discord


Bugfix/#1164 coop replay broken

This fix allow to correctly play coop replays.
I don't know if it's the right solution thought .
For some reason for the coop replays the map file name is empty in the metadata.
Maybe we should fix the replay files instead ?

Please try to always put one issue into one commit via amend option. And if you format the comitt the following way
[title]
[newline]
[description]
Fixes #[issue number]
Then github closes the issue on merge and also puts the title as title and the description as description in the PR by itself

Ok noted.
I found another cleaner way to fix the problem.
I'll close this pull request and open another cleaner one with the correct commit naming convention and one commit per issue.


feat: Rename Konnect "runtimes" on the docs homepage

Description
What did you change and why?

Since Konnect is renaming "runtimes", we needed to update the homepage to change "runtimes".
I know the homepage on main is now the refreshed one and this is the old one, but I wanted to make sure everything was updated. Was there anything I missed?

Include any supporting resources, e.g. link to a Jira ticket, GH issue, FTI, Slack, Aha, etc.
DOCU-3380
Testing instructions
Netlify link:
Checklist

[x] Review label added
[x] PR pointed to correct branch (main for immediate publishing, or a release branch: e.g. release/gateway-3.2, release/deck-1.17)

@cloudjumpercat , I see text, images, etc from the old homepage layout in this update, we're missing details from https://github.com/Kong/docs.konghq.com/pull/5933/ . @fabianrbz can you please take a look at why we're out of sync? Thanks.

Fixed merge conflicts and issues with the rebase, so this can be merged after a review now


fix: Revamped the frontend

fixes issue #58

Thanks for taking time out to contribute to MIND @vulpes231 . Greatly appreciated! Could you please provide screenshots of the revamped front end? It would help us evaluate the visual improvements you've made. Thank you!


UE5 Addition

Changes
Fixed an ( Issue ) Related to Char* , from illegal move to a string value instead
This ensures and avoids the issue of rebuilding it through the batch file
Additionally fixes the Problem for manual build through Project - > Plugins
( Note: Building is only nessecary if the files such as " Binaries / Intermediate " are missing from the plugin files )
Updated the CLI version, which is now directly downloading the latest available on WakaTime website and supports the " waka_ " prefix before the apiKey for reference
(waka_apiKey)
(Note: CLI and Prefix use is in reference to the CLI version being used, both with or without a prefix should work based on testing, unless the Wakatime APIKey does not get changed, on that note Restart the Engine And it should work as intended sending a heartbeat to the servers).
Removed user specific code from the files
.Vscode
(Not nessecary to be included because these are built by and for each developer and commonly cannot be used by others, its directly for the one that made it)
Build Info
To Download the Source, building can only be done through:

Batch file of Unreal Engine.
Add the Plugin to the Project -> Plugins ( Building it from Engine -> plugins wont work ).

(Note if there are issues Building it, please references to the following https://www.youtube.com/watch?v=2HHJ6AYnwFw&list=WL&index=428 ) And References that in  https://github.com/TheAshenWolf/WakaTimeForUE/issues ), Any issues with the code will be written in the CMD files, that can be fixed ( It sections them out in detail! )
To Download the Working version, Pre-Built for Unreal Engine 5 use or see https://github.com/VerzatileDev/WakaTimeForUE/releases/tag/v.1.2.5
Future
Updates to accomidate the Plugin version within code will be done in a different Update instead as the following is specifically used to build and Update the version of the plugin to accomidate UE5 and new Updates to CLI versions of Wakatime.
This includes rest of the code changes, as the following update it aimed towards fixing current problems to make it work within UE5

Possibly be able to change the Version that is shown on the Plugin as referenced here https://github.com/TheAshenWolf/WakaTimeForUE/issues/38 Would be a good addition so that Unreal 4 and 5 are seperated.

Downloaded source, built it (after struggles with missing SDKs), got few heartbeats.
Seems to be working properly, great job!

Yeah I think as far as SDK's goes that is not something we have to touch nessecarily, as if they are already developing with unreal they should be familiar with it I would say at least.

Oh, the SDKs were unrelated to the plugin :D I was reinstalling Unreal from scratch, so some stuff was missing.


[User privacy] Select the model utilized in the backend.

Hi,
Gorilla-CLI fuses the capabilities of various Language Learning Models (LLMs) like Gorilla LLM, OpenAI's GPT-4, Claude v1, and others to present a user-friendly command-line interface.
Does it mean user queries are submitted to GPT4(OpenAI) or Claudev1(Anthropic) ?
Can I select or opt for Gorilla only inference ?
Can user be provided option with setting up Gorilla model on local setup ? Is there plan to release Gorilla model checkpoints ?

Thanks for trying out Gorilla-cli @ravindra-ut . This is a great suggestion. I was wondering perhaps user can pass an argument --model and include that in the RESTful call? Do you want to maybe raise a PR for this - if you are interested  - would love to have you join this project as a contributor! I can modify the back end to respect the model choice.

Yup always! The models are evolving rapidly rite now. So, we will release the model checkpoints once it stabilizes to a certain extent.

@ShishirPatil An issue that may arise when passing the --model argument is that some users may find it cumbersome to specify it with every command they run. I think it would be great to have a config.json file that saves user settings, and we can potentially remove USER_ID_FILE and UPDATE_CHECK_FILE as well. All the information could then be stored within the config.json file. The file will also be useful and make the code cleaner as the system grows and has more complex features that require individual user information to be saved.
With this approach, we would check the config.json if models are specified, and if so, pass it into the RESTFUL call.

Hey @Noppapon thanks for taking this on! Yeah, that is a good suggestion - we can have a config.json that can have all this information in one place. Maybe we can still allow the users to over-ride the config with the --model or -m flag, in those cases where they want to use a model one-off? Thoughts!
Otherwise, this sounds good - let me know when you raise the PR and I can review it. Thanks man!

Thank you, @ShishirPatil ! I've made several additions in the same PR to clean up the code related to argument passing and the UI, using the Click framework. Along with that, users can now execute essential commands like --help, --version., and some more, which I think would be useful. The PR is now ready for review.


A11y_AzureDataStudioStayHealthy_Notebook_Toolbar_AI4D: Control type set wrong for add cell and toggle option

“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHubTags:#A11y_AzureDataStudioStayHealthy;#A11ySev2;#A11yTCS;#A11yMAS;#Benchmark;#DesktopApp;#WCAG4.1.2;#WCAG1.3.1;#SQL Azure Data Studio;#FTP;#AI4D;#Win32;
Environment Details:
Application Name: Azure Data Studio
Version: 1.20.0-insider (system setup)
Commit: fd29e35
Date: 2020-07-02T05:40:02.292Z
VS Code: 1.46.0
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363
Additional Details:
MAS References:WCAG4.1.2, WCAG1.3.1
Tool: Accessibility insights for desktop
Repro Steps:

Launch Azure Data Studio Insiders application.
Connect to server.
Right-click connection and click New Notebook
Click on cell and select code cell.
Launch accessibility insights for desktop and hover over the tool bar .

Actual:
On hovering over the controls in the toolbar "add cell" and "toggle option" has been set as "menu item" and "list item" respectively.
Expected:
The control should be set as button and announced as button itself.
User Impact:
Screen reader users will get wrong control information.
Attachment link for Reference:

@fsteffi We already set the aria role to button for these :

And they're announced correctly in NVDA :
tool bar
Run cell (F5)  button
tool bar
tool bar
Toggle More  button
Delete  button
Move cell up  button
Move cell down  button
Add cell  menu button  subMenu

So I don't see any issues there. Can you confirm if there's some other issue with our implementation?
@MaddyDev It does look like we're not correctly announcing the menu status for the "Toggle More" button though. Could you looking into fixing that?

the above issue is not repro in latest env so closing the bug.

Github Tag:#Closed;


css: Use SCSS nesting in subscriptions.scss for .stream-row.

Is this ready for review?

I wanted to ask you if we need to do more. There are so many styles that are set for multiple selectors (separated by comma). Do we want them to segregate and combine with common parents and nest accordingly?

OK; in that situation, you should make that clear in the PR description or comments; otherwise it's unclear what you want reviewers to do with it.
I'll also mention that a PR that consists only of commits that are mergable should probably not be tagged as a "draft" in any case; you can always do another PR for part 2 if there's more things you might add later.

I merged the first 3 commits and commented on the 4th.  I don't think we need to aim to reorganize everything in this giant file.  A few good ones to target next include:

.subscriber-list
.subscriptions-container
#subscription_overlay (possibly with a block of the form #stream_privacy_modal ul.grey-box #subscription_overlay ul.grey-box?)
.stream-creation-body and other things with creation in their name.

@timabbott fixed the PR, this can be merged now.

Merged as the commits ending with 239278ed900ce74764fb2760c41a13d6debaefef, after shortening the commit titles.  You may want to reuse the patterns I used there for future SCSS PRs.

Yes I'm using the same commit message patterns. I'll omit the file name in the future if the line gets too long.


[BUG] Crypto lib on MacOS is unsupported

MacOS (Darwin) python versions doesn't support Crypto lib.
Substitute with standard cryptography.

complied


bmp termination message

bmp termination message should not have per peer header
bmpcodec should either clear the whole context (if context is limited to a bmp session) when receiving termination or clear all peers from the session originating the termination message (if context is for a whole collector)

Fixed in PR#50


viewport zoom needs to be addressed

I think this is causing major headaches with safari browsers. browser is not readjusting size but instead just zooming in on the content. This throws off touch targets:
Here is an article by mozilla developers on this topic from a few weeks ago:
"Sites can set their viewport to a specific size. For example, the definition "width=320, initial-scale=1" can be used to fit precisely onto a small phone display in portrait mode. This can cause problems when the browser doesn't render a page at a larger size. To fix this, browsers will expand the viewport width if necessary to fill the screen at the requested scale. This is especially useful on large-screen devices like the iPad. (Allen Pike's Choosing a viewport for iPad sites has a good explanation for web developers.)
For pages that set an initial or maximum scale, this means the width property actually translates into a minimum viewport width. For example, if your layout needs at least 500 pixels of width then you can use the following markup. When the screen is more than 500 pixels wide, the browser will expand the viewport (rather than zoom in) to fit the screen:
<meta name="viewport" content="width=500, initial-scale=1">
Other attributes that are available are minimum-scale, maximum-scale, and user-scalable. These properties affect the initial scale and width, as well as limiting changes in zoom level.
Not all mobile browsers handle orientation changes in the same way. For example, Mobile Safari often just zooms the page when changing from portrait to landscape, instead of laying out the page as it would if originally loaded in landscape. If web developers want their scale settings to remain consistent when switching orientations on the iPhone, they must add a maximum-scale value to prevent this zooming, which has the sometimes-unwanted side effect of preventing users from zooming in:
<meta name="viewport" content="initial-scale=1, maximum-scale=1">
More info here

more potential relevant reading:
part 1

part 2


forever list shows no jobs while they exist

Hello,
when I do
user1@localhost:~$ forever start node_app/app.js

the process is launched as expected but when I want to list the current jobs, nothing is found. Here is the output:
user1@localhost:~/node_app$ ps aux | grep node
user1      22803  0.0  3.6 642588  9040 ?        Ss   13:58   0:00 node /home/user1/.nvm/v0.6.4/bin/forever start node_app/app.js
user1      22804  0.1  5.0<PHONE_NUMBER>6 ?        Sl   13:58   0:00 node /home/user1/node_app/app.js
user1      22951  0.0  0.2   6076   572 pts/1    S+   14:03   0:00 grep node
user1@localhost:~/node_app$ forever list
The "sys" module is now called "util". It should have a similar interface.
info:   No forever processes running

I am using Debian 6 with Node.js 0.6.3/0.6.4 and the last version of Forever installed with NPM.

#175 #163


feat(cf): update setup docs to match Halyard additions

spinnaker/spinnaker#3961

@jkschneider can you take a look? Thanks.


fix: always try without perms, if fail, sudo

Fixes #959.
Tested on a clean install macOS Mojave VM.
License: MIT
Signed-off-by: Henrique Dias<EMAIL_ADDRESS>

Please ignore Travis failure.


[SPARK-8199][SQL] follow up; revert change in test

@rxin / @davies
Sorry for that unnecessary change. And thanks again for all your support!

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@tarekauel If Calendar is created inside for-loop (i), we should use i, otherwise use 1, is it correct?

there are four more places (below that) need to be fixed.

After this rush, you should have more rest, also me. :)

Now it's right, isn't it?

LGTM.

Test build #1113 has started for   PR 7505 at commit d09321c.

Test build #1113 has finished for   PR 7505 at commit d09321c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Thanks - I've merged this.


Installation via Plugin Directory Fails?!

My KANBOARD Configuration

Application version: 1.2.20
PHP version: 7.4.30
PHP SAPI: fpm-fcgi
HTTP Client: cURL
OS version: Linux 4.15.0-188-generic
Database driver: mysql
Database version: 5.7.37-nmm1-log
Installed at: all-inkl.com
Installed Plugins:

AddMermaid
Auto Email Extended Actions (Not yet tested)
AutomaticActionUX  (Not yet tested)
Broadcast
Chat
EmailTaskHistory   (currently does not work?)
MarkdownPlus
Self-Registration
Wiki

Browser: SeaMonkey 2.53.14 Beta pre, Build-Identifikator:<PHONE_NUMBER>0005  (Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0)

STR

Close existing Task
» Will be transferred to Closed Area
» Expected: I get Email info because I was creator
Actual: No email   😥

Additional Info:
a) I see the plugin in the KANBOARD file system (using ftp)
b) In Plugins Dir the plugin still shows "Install"
c) so all as per forum posting
BTW: I haven't a clue where to modify plugin settings (email recipients, ...). Manual tells nothing.

Hello, this is an Automatic Action.... did you select and configure from the action list after you have installed the plugin?

I updated the readme with usage instructions

I will do a test with the new plugin version, soon


Swift 4.0 support

Hi!
I converted project to swift-4.0.

someone please merge to support swift4

I also need it for Swift 4 ! @pskow can you provide your branch link that suports swift 4 ?
Or may some one could merge it to suport swift 4 !
Thanks !

@Alexookah is it possible to merge it ? thanks!

sorry i am not able to merge any settings in this repo. i just checked the code and marked these changes to be merged maybe from the repository owner or so.

@kevin-hirsch is it possible to merge it for suport swift 4.0 ?

Thanks a lot for this PR! 💯
It's merged ✅


really bad IO

System has really high IO-wait during network- and/or filesystem-operations. At the same time cpu-usage is low by arround 6%
Example (during emerge -av vim):
# vmstat 10 10
------cpu-----
us sy id wa st
 0  3 70 23  0
 0  6 39 54  0
[..]

I am now crosscompiling @system, because I suspect the official experimental stage3 build.


Remove unnecessary cast

Found by the latest version of closure-compiler (v20150729)

Looks good @fredj.  Please merge.


Exceptions used to create ErrorHeader needs to be accessible

MslControl converts exceptions (via MessageBuilder.createErrorResponse) into a ErrorHeader and passes that to MessageDebugContext. Those exceptions have very valuable information for logging and diagnostics purposes. I would like the exception to be passed class that outside implementations control, like how MessageDebugContext is provided to MSL and can log headers. It could even be a new call on MessageDebugContext (which could be added a Java 8 default method on the interface), e.g. MessageDebugContext.exceptionFound(Exception). Or  as a second parameter to sendHeader, but that's awkward if there is header is a MessageHeader. Maybe MessageDebugContext, should be refactored to have a sentMessageHeader(MessageHeader) and a sentErrorHeader(ErrorHeader, Throwable). This would make it easier for implementors too, since we wouldn't have to do an instance of on the Header and do the delegation ourself.

I don't really understand what you're asking for. All MslExceptions are thrown back out to the caller already. You get them. You don't need a new function to access them and you don't need to parse ErrorHeaders to figure out what went wrong.

Are you thinking that we should look at MslControl.request's Future for exceptions? I believe it will throw an ExecutionException. So the contract with caller is to look at the cause of the ExecutionException and look for a MslException? If so, the docs could be improved, since they it says the Future will throw a MslException direction.

Yes, look at the cause of the thrown ExecutionException. The documentation doesn't explicitly say this right now since by definition a Future can only throw an ExecutionException or an InterruptedException, but it can be made clearer like you said so I've opened issue #89.

Closing since the exceptions can already be accessed.

I agree that exceptions can be handled by the caller, but I'm asking for a hook so that I can provide general solution to my implementations. Specifically I asked for the exception to be passed to MessageDebugContext which is a class that I already provide to my implementations, it is meant for debugging a message. MessageDebugContext receives the ErrorHeader but that that isn't adequate to debug a message's error.
If I can't hook into MSL to log exceptions, each system has to look for the exceptions coming out of the Future and call my logging function. They should be looking at the exceptions already, but that's to react to the exception, I don't want to conflate the behavior of reacting to an exception and the simple act of logging. Currently my only option to ask that each call my logging function ("please, pretty please") or put some abstract over MSL to be centrally log these exceptions. I don't think an abstraction over MslControl should be needed to centrally log exceptions.
The framework should make it possible to log exceptions via a MSL provided hook/callback.

Are you planning to implement an abstraction over MessageContext, and then require applications to use your MessageContext implementation, in order to centrally log exceptions? Versus requiring applications to use your MslControl abstraction in order to centrally log exceptions?
netflix-msl-library was originally envisioned as an abstraction over the MSL stack that would be used by all Netflix applications, instead of using the MSL stack directly, and this also matches the design for the MSL Auth service.
Also, an application that gets a MslException inside an ExecutionException from the Future will not be reacting in any way other than potentially to log the exception. The response will already have been sent. But unless you also require all applications to also make sure the response gets sent out from the OutputStream you will also want an abstraction over MslControl in order to provide that functionality by default.

If you want to see every MslException thrown, looking at only the error responses that go out will not show you all of them because there are situations where an exception is handled or bypassed.
If you want to see every MslException thrown that results in an error response being sent, looking only at the MslException inside the ExecutionException that is thrown to the calling application will not show you all of them because MSL is self-healing and establishing communication may require multiple messages and round trips.
If you want to see every MslException thrown that would result in an error response being sent, looking at only the error responses being sent will not show you all of them because an error response will not be sent if the max message count has been hit.

The three top-level locations that can provide insight are the MessageDebugContext, MessageRegistry, and ExecutionExceptions thrown from MslControl APIs. The better place to log things is inside individual classes provided by the application's MSL configuration because that is the only place where the exception is guaranteed to exist and will not get swallowed up by MSL core logic.


Large files raise 504 timeout errors when trying to upload them to staging but do not show a helpful error

Overview
A clear description of the bug.
Expected Behavior
If there is a 504 timeout, the error message shown says that it took to long to upload the file.
Actual Behavior
When there is a 504 timeout the error message only says "An error prevented uploading that file"
Steps to Reproduce

Log into staging
Attempt to upload
large-test-file-4316.csv.txt

Additional context
Ultimately we want to change or optimize the upload process in some way so that we are not susceptible to these timeouts. For the time being, we need a message that explains more clearly the type of failure we encountered.

On staging there were several copies of the large file queued up to be processed, which indicates that the Django code may have kept running and completed the insert and job scheduling after the timeout. This makes things trick to deal with.
I did some testing and found that the problematic file took 3 seconds to import in development with the develop branch, and 1 second after I used bulk_create rather than individual model saves. We should be using bulk create in this situation, but I think the full solution is temporarily dropping the file somewhere and having a Batch job slice it up without any time pressure.


Automated cherry pick of #4072: fix: 导出用户标签不加user:前缀

Cherry pick of #4072 on release/2.11.
#4072: fix: 导出用户标签不加user:前缀

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@8aa376a). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             release/2.11   #4075   +/-   ##
==============================================
  Coverage                ?   7.13%
==============================================
  Files                   ?     480
  Lines                   ?   78065
  Branches                ?       0
==============================================
  Hits                    ?    5567
  Misses                  ?   72031
  Partials                ?     467

Flag
Coverage Δ

#aFlag
7.13% <ø> (?)

Impacted Files
Coverage Δ

pkg/compute/models/guests.go
0.63% <ø> (ø)

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 8aa376a...c63a471. Read the comment docs.

/approve
/lgtm


Using jenv to set Java version on Jenkins Mac agent node

Description
Using jenv instead of Jenkins tool to set Java version on Mac agent nodes
Issues Resolved
part of https://github.com/opensearch-project/opensearch-build/issues/4272
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

tesing a jenkins file with using input_manifest as 3.0.0/opensearch-3.0.0.yml on staging CI
[Pipeline] {
+ jenv local openjdk-21
[Pipeline] withEnv
[Pipeline] {
[Pipeline] withEnv
[Pipeline] {
[Pipeline] withDockerRegistry
[Pipeline] withDockerRegistry
[Pipeline] echo
get java_version
[Pipeline] sh
 > git rev-parse origin/main^{commit} # timeout=10
 > git config core.sparsecheckout # timeout=10
 > git checkout -f f603314c1481e6b72603313f523e2de20a830c90 # timeout=10
[Pipeline] {
[Pipeline] {
[Pipeline] isUnix
[Pipeline] withEnv
+ java -version
openjdk version "21.0.1" 2023-10-17 LTS
OpenJDK Runtime Environment Temurin-21.0.1+12 (build 21.0.1+12-LTS)
OpenJDK 64-Bit Server VM Temurin-21.0.1+12 (build 21.0.1+12-LTS, mixed mode)
[Pipeline] {


Libby Downloader hangs: continuation of May 13 issue

FireFox 91.11.0esr (64-bit)
Debian 5.10.0-13-amd64
Version 0.4.0

That is indeed a different issue, thanks for reopening. Is there any way you could test on a more recent version of Firefox? I know it’s an ESR build, but the 91 release was 2 years ago (we’re up to 114 now). I’ll see about reproducing locally with that build in the meantime.

Confirmed this extension is incompatible with that version of Firefox. Confirmed working on 102 ESR build that ships with Debian Bullseye. Assuming you're running Buster still, my recommendation would be to upgrade to Bullseye to get a more current build (it's EOL in 2 months anyway).


Dynamic replication networks

It should be possible to dynamically add/remove replication connections to/from replication endpoints. A prerequisite for this feature is already implemented with #116.

This ticket also includes the functionality to dynamically turn replication per connection on and off, so that uni-directional replication during application upgrade (#107) can be supported.

Covered by #314. Might become a ticket later but closing for now until decomposition of #314 into work packages becomes more stable.

@krasserm is there any plan to release this feature ?

@coding4m most likely with 0.9, beginning of 2017


Significant Lag upon hitting enter on prompt

Description
I just finished moving over my install/configuration of zsh/prezto over to my OpenBSD 6.3 box and there is a significant lag when displaying the prompt. So for example at the prompt I type nothing and when I hit enter there is a significant lag (~1-1.5s)on showing the next prompt. This slows down executing commands on the machine a lot as you can imagine having to wait to enter the next.
I have these configs running on OS X and FreeBSD and don't have this issue. Is there a way to troubleshoot where the problem lies?
Expected behavior
That the prompt displays in milliseconds not seconds.
Actual behavior
That the prompt displays in ~1-1.5 seconds.
Steps to Reproduce
Install ZSH and Prezto on openbsd and use the sorin prompt.
Versions

Prezto commit: e149367445d2b
ZSH version: 5.4.2
OS information:

Is it on the whole prompt or just the git portion? Do you see any performance differences if you're in a git repo vs outside one?

It behaves the same where its on a git repo or not. Its the entire prompt that has the lag to display.
--
Adonis

On Jul 20, 2018, at 5:50 AM, Kaleb Elwert<EMAIL_ADDRESS>wrote:
Is it on the whole prompt or just the git portion? Do you see any performance differences if you're in a git repo vs outside one?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Which other modules do you have enabled?

I've narrowed it down to the autosuggestions plugin. Having it enabled causes the issue. I will update with some more info to see what exactly in autosuggestions may be causing it. Any ideas from your end?

I don't use autosuggestions, but I seem to recall other people mentioning issues with a large history value and autosuggestions.

In my case the history is pretty fresh. I need to retest with OpenBSD 6.4.
Sent with GitHawk


macOS Ventura issues

Bug Report
Current Behavior
I can't see no content of my mail in Mail app and MS Outlook.
I can't write mail messages anymore.
When I disable the colorfulSidebarX plugin,  normal behaviour comes back.in both mail app's.
I tried to put the two APP's in blacklist , but that doesn't make any difference !
Environment
MacbookPro 15" 2018

MacForge version(s): v 1.1.0
OS version: macOS Version 13.0 (22A380)
Plugins: colorfulSidebarX

I was also having this issue and took forever to realize it was macforge... the only plugin I use is afloatX, but it appears that 'disabling injection' from the menu bar allows it to still work (at least, the invert color function that I use) but the mail previews come back in outlook.


Layered navigation for price is not working, when click on bar it shifts to rightmost end.Getting this issue in case of configurable product only.

Framework Version: 0.1.6

Framework Version: 0.1.6

Fixed


A11y_PowershellEditorServices_Installation_Screenreader:Narrator does not read the "Expand/Collapse" state of the buttons(Disable,Settings,Command,Language,Debugger,Color themes)

Environment Details:
VSCode Version : 1.25.1
OS Version : Win10
Additional Details:
Screenreader ,MAS1.3.1
Repro Steps:
1.Launch Visual Studio code desktop application.
2.Navigate to "Extension" button of "ActivityBar"->Enter "PowerShell" in "Search Extension" text field and click on "Install" button.
3.Start narrator & navigate using "Tab" key to  "Disable" button , and observe if narrator reads collapsed/Expanded for disable button.
4.Navigate to Settings, Commands, Languages, Debugger, Color themes under the Contributors Tab item , and observed that whether narrator reads the state of the buttons as collapsed/Expanded.
Actual:
Narrator does not read the Collapsed/Expanded state of the buttons(Disable, Settings, Commands, Language, Debugger, Color themes)
Expected:
Narrator should read the Collapsed/Expanded state of the button(Disable, Settings, Commands, Language, Debugger, Color themes)
Recommendations:
Refer below link which is repository of bug fixes code snippets:
https://microsoft.sharepoint.com/teams/msenable/mas/pages/browse-fixes.aspx
User Impact:
User will not able to know the state of the buttons as Collapsed/Expanded.
MAS Reference:
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}
Does this issue occur when all extensions are disabled?: Yes
A11y_PowershellEditorServices_Installation_Screenreader.pptx

Narratpr os mpt si[[prted


Extend storage functionality (encrypt/decrypt, ...)

Description
Extend storage functionality with encryption as we currently have in the dev branch, might require some bigger changes to the storage module, because the current version is reduced to the basic functionality.
Transaction ids and output ids can't be used as keys in the db directly, otherwise any encryption is useless since the corresponding things can be found in the public
Motivation
Privacy
Requirements

Add options to set an encryption key
Encrypt/decrypt storage with it
Be able to change the encryption key
Function do "logout", which clears the encryption key and data in memory
Function to delete the storage

Open questions (optional)
Might make sense to wait for https://github.com/iotaledger/wallet.rs/issues/806 before doing it or doing both at once
Are you planning to do it yourself in a pull request?
No.

Having gained some experience now with it, I'ld say I can take this in an upcoming sprint.


About Image Entropy

In models/stage1_dynamic/dqvae_dual_entropy.py . I think  bins=torch.linspace(0, 1, 32) should be changed to bins=torch.linspace(-1, 1, 32) , or do not use transforms.Normalize([0.5, 0.5, 0.5], [0.5, 0.5, 0.5] to preprocess images.
In Entropy.entropy(),
values = values.unsqueeze(2)
residuals = values - bins.unsqueeze(0).unsqueeze(0)
kernel_values = torch.exp(-0.5 * (residuals / sigma).pow(2))

pdf = torch.mean(kernel_values, dim=1)
normalization = torch.sum(pdf, dim=1).unsqueeze(1) + epsilon
pdf = pdf / normalization + epsilon

When values which shape is [batch_size * patch_num, patch_pixel_nums] in range [-1, 1] and bin in range [0, 1], if all pixel values in patch is <0, then the residuals will be <0 too. As a result, kernel_values approaches 0 at an extremely fast rate when residuals decreasing and pdf will have several large value with other values close to 0, so the entropy value will be very low.
This can lead to an issue where the entropy will be low regardless of the content if the brightness of the image is low. I think this is not the expected behavior.

Thanks for your interest and valuable advice! You are right and we find that this is benefical to change the bins to [-1,1]. We will update the corresponding code. We also update it in the readme.


[LIVY-466][RSC] Fix RSCDriver exception during RPC shutdown

What changes were proposed in this pull request?
During RSCDriver's shutdown, it will first shutdown RPC server, and then all the RPC clients. When RPC client is closed, it will register a timeout to avoid orphaned RSCDriver, but this is not necessary during RSCDriver's shutdown, so here fixing this issue. The details can be seen in JIRA.
How was this patch tested?
Local verification.

Retest.

Merging to master and branch-0.5.


Keyboard shortcut support

We could add a way to control playback with the keyboard.

Sadly (or fortunately), due to how the keyboard shortcut registration API works, this cannot be implemented in a universal way by a Letterbox view. Since the view itself is not a first responder implementing it on the view does not work (shortcuts are never retrieved). And we cannot provide a Letterbox view method returning default shortcuts for direct use by a parent context, as the methods would then be defined on the view, not on the parent context, which means they wouldn't participate to the shortcut list either.
Fortunately this API is very simple to use and apps can implement shortcuts in a snap. This also avoids conflicts and is overall better IMHO. I thus updated the demo and documentation for more information about how such a feature can be implemented.
This is available on the feature/keyboard-shortcuts branch. I also exposed the standard Letterbox skip intervals so that applications can decide to use the same values when implementing shortcuts.

From a WWDC 2020, https://developer.apple.com/wwdc20/10109:

Following the model-view-controller pattern, the ideal place to define this behavior is in your custom view controller subclass.

Thanks for the iteration.

I assigned this issue to milestone 6.2.0, as keyboard controls are available in the demo (and documentation has been updated accordingly).


Minimap is broken (Terrain glitch in certain areas - some areas are fine)

https://i.imgur.com/e0HVZpE.jpg

I see this issue too. restarting gwtoolbox fixes it when it happens but at the risk of crashing the game

temporary workaround: click Load Now on your settings to load the correct map

Fixed in 09b59acbb8a0f9c6763857fab2302ce6613d6034


feat: allow for Authorization header override with raw parameter

This PR creates a Raw Authorization type which allows the user to set the full Authorization header in a websocket request if the server they are connecting to does not conform to Bearer or Basic auth.

Motivation

Solution

PR Checklist

[trivial change ] Added Tests
[x ] Added Documentation
[ no] Breaking changes

I have an issue where I cannot get this enum variant to work as intended. My WSS endpoint expects a custom header and an api key, and if I provide it using Authroization::raw, I just get a HTTP 403. The reason this is strange is because on an equivalent js app using web3-providers-ws, we are able to instantiate the ws connection correctly using our custom headers :
const customWsProvider = new WebSocketProvider(WS_URL, {
  headers: {
    'KEY' : val
  },
})

in my experience the equivalent ethers-rs code is not totally equivalent:
let api_key = // .. ;
let auth = Authorization::raw(format!("KEY {api_key}"));
let provider = Provider::<Ws>::connect_with_auth(url, auth).await?

Any help would be appreciated.