New saving sessions don't register

Describe the bug
I got an email about an hour ago that new saving sessions are back in order and that one is starting today (2024-12-11) between 6-7pm, along with an opt-in button. I went to check if my automation had fired and noticed that the binary_sensor.octopus_energy_a_<account>_octoplus_saving_sessions sensor hadn't changed, and hence the automation didn't run.
I did see that, octopus_energy_all_octoplus_saving_sessions shows a bunch of activity, but I'm not sure how to see details for those events.
Could it be that something about the APIs has changed for the 2024 saving sessions? Any other information I can provide?
Reproduction steps
Be invited to a saving session
Expected behaviour
Saving session is detected, automation is triggered to join it.
Tariff Code
20L3168997
Integration Version
13.2.1
Home Assistant Version
2024.12.1
Fresh Install?
Not specified
Home Assistant Logs
I had not enabled debug logging at the time
Confirmation

[X] I confirm that I cannot find my solution within the documentation
[X] I confirm that I cannot find my solution within the FAQ

Pretty sure this (at the moment) is because the sign up appears to be via email and is not yet on the website / API so there isn't a way for the integration to see the session. Once octopus integrate it into their website this may well work again.

Yea ... I created a calendar and updated my automations to trigger from that (as well as the API)

Yeah for some reason they haven't updated the API to include the upcoming event. I hope they're not building yet another set of APIs...

@BottlecapDave I think it needs changing as they're now region specific so probably changing things on the backend for that. Its possible that the APIs will change for that.

I did wonder if they've gone manual to avoid us automating ....

From what I could gather from their messaging, the regioning seemed like it was superficial leaderboards, but re-reading it, you might be right. Hopefully they can build the free electricity API while they're at it 📟

From what I could gather from their messaging, the regioning seemed like it was superficial leaderboards, but re-reading it, you might be right. Hopefully they can build the free electricity API while they're at it :p

Yeah its not just superficial boards this time. Last year it kinda was for stats.

There is also a team name.  I chose "Home Assistant" ... maybe if its near the top Octopus will take more notice :-)

From what I could gather from their messaging, the regioning seemed like it was superficial leaderboards, but re-reading it, you might be right. Hopefully they can build the free electricity API while they're at it :p

Yeah its not just superficial boards this time. Last year it kinda was for stats. Appears the region is involved in the NESO requirements too.

NESO are now dispatching the DFS as similarly as they can other balancing services. So I’m guessing that the price and utilisation will be better if the aggregator(Octopus for us) can guarantee the region of demand reduction.

Interestingly, ESO published documentation last year that discussed automation and people 'rigging the system' re the 2022/2023 saving session season. Their comment was that 1. there was no evidence or it wasn't a meaningful proportion and 2. it was not harmful to the purpose of shifting loads. This seemed surprisingly honest and weighted.
I think automation would actually contribute towards the goal. So realistically I wouldn't see why NESO or octopus would actively discourage automating and optimising output of saving sessions. If NESO are paying people it's because they benefit (more) from it. I haven't looked for similar documentation re: last year's activity.
Big thanks to all the devs!

For previous Saving Sessions I used a Node Red automation to react to the 'Octopus Saving Session Baseline Electricity (acct no)' entity to switch my Tesla Powerwall2s to Off Grid ensuring that I was not consuming any power during the session. Last night I had to do this manually as the entity is no longer present (ie. unknown). As Saving Sessions are now back on it would be useful if the entity could be reinstated if still in the API.

Same here, I have an automation (as I imagine many of us do) for load shedding during saving sessions which will turn off non-critical items, such as heating in the workshop. In my opinion this kind of automation is exactly what savings sessions are supposed to encourage and automating it is exactly in line with goals. Let's keep our fingers crossed that lack of API support is just an omission due to time constraints.

Yea ... I created a calendar and updated my automations to trigger from that (as well as the API)

Have you got code for this that you can post?

I created some date helper entities (date, start time, end time) and an amount so I could inject those into Predbat as a manual export rate override.
Not fancy but it worked with Predbat deciding whether to discharge my battery or not

Many thanks!

I wasn't expecting the autojoin or baselines to work at the moment because OE don't seem to be fully back to using the API.
I had expected to see the latest event in the saving session events entity though.  It only seems to show all the events up until March.   I see this using graphql.  How is the integration fetching SS events? Why can't it see this one?
            {
               "id" : 1324,
               "code" : "EVENT_16_111224",
               "startAt" : "2024-12-11T18:00:00+00:00",
               "endAt" : "2024-12-11T19:00:00+00:00",
               "totalParticipants" : 403847,
               "rewardPerKwhInOctoPoints" : 480,
               "devEvent" : false,
               "targetGsp" : [ ],
               "status" : "DONE"
            }

I'm seeing the saving session in the attributes of octoplus_saving_session_events. The saving sessions are only refetched every 30 minutes and just reports whatever the API reports. I'm hoping the new API isn't too different so that the transition can be quick.

I'm seeing the saving session in the attributes of octoplus_saving_session_events. The saving sessions are only refetched every 30 minutes and just reports whatever the API reports. I'm hoping the new API isn't too different so that the transition can be quick.

I'm seeing the event that was on 11th December now in the joined_events part of the events.  I am pretty sure it wasn't in the list earlier, and it definitely wasn't in the available_events before the session - I could see it wasn't in the event list, and if it was, Predbat would have tried to auto-join it.
Maybe populating the API has only just started?
🤞for the next session

I'm seeing the saving session in the attributes of octoplus_saving_session_events. The saving sessions are only refetched every 30 minutes and just reports whatever the API reports. I'm hoping the new API isn't too different so that the transition can be quick.

I am still not seeing the event from December in my list.  This is 13.2.1

Oh, this is just showing joined events? I thought it was the complete list of previous events as returned by
query savingsessions($accountNumber: String!){
  savingSessions(accountNumber:  $accountNumber) {
    account(accountNumber: $accountNumber) {
    events
...

I didn't join the event on 11th.

Oh, this is just showing joined events? I thought it was the complete list of previous events

its titled 'joined events' in my event sensor:

and the session (which I did join) is showing in the list:

Am sure it wasn't earlier.
I exported about 3kWh in the session, so £2 profit or so and the agile rates afterwards were not too bad

The lists have been reset and only show this season's events now.
so for mein the API, joined_events = [] and events list only shows the 1 event from 11th.
The integration is now just empty so there is no history to show and obviously no future events on the horizon.


Update pubsub.md

Typo "subscribed"

Codecov Report

Merging #161 (bafb6c9) into master (b2a7ac7) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #161   +/-   ##
=======================================
  Coverage   91.82%   91.82%
=======================================
  Files          47       47
  Lines        2384     2384
=======================================
  Hits         2189     2189
  Misses        195      195

Impacted Files
Coverage Δ

src/CoreApi/BlockApi.cs
96.59% <0.00%> (-2.05%)
:arrow_down:

src/BlockExchange/Bitswap1.cs
95.31% <0.00%> (+4.68%)
:arrow_up:

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 b2a7ac7...bafb6c9. Read the comment docs.


KAFKA-12198: Migrate connect:json module to JUnit 5

More detailed description of your change

Use junit5 methods to replace junit4 ones
change assertEquals(true) to assertTrue
optimize import order

Summary of testing strategy (including rationale)
QA
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@dengziming Could you fix the conflicting files? thanks!

@dengziming Could you fix the conflicting files? thanks!

@dengziming Could you fix the conflicting files? thanks!

Sorry for the late reply, done!

@dengziming Could you fix the conflicting files? thanks!

Sorry for the late reply, done!


ci: Merge proto_format/format checks

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

this will conflict with #26125 - preferably that one should go first as its more invasive and rather get it out of the way

@kyessenov apologies i havent made progress on this - ive been thinking about how best to do it - and as you rightly pushed back its quite a dev-invasive change that needs some testing
im thinking about a totally different approach:

use git ls-files and git hash-object to create a comparable hash tree
move the proto_format comparison code to envoy.code.check

i think using bazel to create a hash-tree will be much faster than passing around and un/tarring fileystems - envoy.code.check can then create a hash-tree very quickly using git as from the current filesystem. I need to test this out but i think this will reduce the cost of running this when there is no change to very little, and will optimize the change situation also

still working on this altho it will end up looking pretty different


Is this only for PC or can this work for PS4

Or if possible, is there a way to add custom songs to a PS4?

PS4 doesn't have mod support for Beat Saber. It's PC only and this is the only way for song loading.


BIO_read() in tls_extract_pem() incorrect

In function tls_extract_pem() line ~1275 while calling function BIO_read():
Code should be
		status = BIO_read(bio, &pemCert[offset], length - offset);

Instead of
		status = BIO_read(bio, &pemCert[offset], length);

Since the latter would be a buffer overflow; the length of remaining buffer is length - offset.

@thecrazyonestherebels Thank you for the hint.


Refactor LISAv2

Can you please move all the logic in powershell modules so that we can write unit tests in pester for all the core framework?
Basically, Run-Lisav2 should become a shim layer that call the main function from a module.

I am not sure if I can do code-review 186 files change. Can you also do document update in the same PR? It looks many changes.

@ader1990 could you describe more specifically which logic to move?

all of it, run-lisav2.ps1 should import one PS module and call the init main function like this Start-LisaV2 &param

This way, we can use pester to test all the framework methods and leave almost nothing in the core framework to be tested as a full run.


[transformer-remark] Update dependency html-to-text

Description
Created a new project and got the following audit message:
┌──────────────────────────────────────────────────────────────────────────────┐
│                                Manual Review                                 │
│            Some vulnerabilities require your attention to resolve            │
│                                                                              │
│         Visit https://go.npm.me/audit-guide for additional guidance          │
└──────────────────────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Low           │ Prototype Pollution                                          │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ minimist                                                     │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in    │ >=0.2.1 <1.0.0 || >=1.2.3                                    │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ @gridsome/transformer-remark                                 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ @gridsome/transformer-remark > html-to-text > optimist >     │
│               │ minimist                                                     │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://npmjs.com/advisories/1179                            │
└───────────────┴──────────────────────────────────────────────────────────────┘

Steps to reproduce

Run gridsome create new-project-name
Run npm i -s @gridsome/source-filesystem @gridsome/transformer-remark

Expected result
No audit issues are shown
Actual result
Got an audit message
Environment
Paste the information here as shown by gridsome info
  System:
    OS: macOS 10.15.4
    CPU: (4) x64 Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz
  Binaries:
    Node: 12.6.0 - /usr/local/bin/node
    Yarn: 1.17.3 - /usr/local/bin/yarn
    npm: 6.14.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 80.0.3987.163
    Safari: 13.1
  npmPackages:
    @gridsome/source-filesystem: ^0.6.2 => 0.6.2
    @gridsome/transformer-remark: ^0.5.0 => 0.5.0
    gridsome: ^0.7.13 => 0.7.13
    gridsome-plugin-tailwindcss: ^2.2.43 => 2.2.43
  npmGlobalPackages:
    @gridsome/cli: 0.3.1

Additional Information
I have already analyzed the audit issue and it seems that html-to-text isn't maintained anymore.
Here the related comment from the package author: https://github.com/werk85/node-html-to-text/issues/198#issuecomment-606622234
Alternative packages

https://github.com/priotas/html-to-text/tree/next

Currently not available at npm

https://github.com/KillyMXI/node-html-to-text

Available at npm: https://www.npmjs.com/package/@mxiii/html-to-text

Sounds like the author may be handing it off to someone for maintenance. If it happens soon enough, Gridsome may not need to migrate to a fork just yet.

html-to-text isn't the issue here, its that transformer-remark is using an old version of html-to-text, which has an out of date dependency (optimise - no longer maintained and no longer listed as a dependency of html-to-text in recent versions)
Solution would be for [transformer-remark] to replace "html-to-text": "^4.0.0", with "html-to-text": "^5.0.0" as a dependency I think.

@grace-snow  the answer is "yes and no"
No:
The problem is that the used minimist version is set to 1.2.0 in their package-lock.json.
There is a DependBot PR to use 1.2.3 as version --> https://github.com/werk85/node-html-to-text/pull/199
Yes:
After the PR is merged, we can solve it by upgrading the html-to-text version to ^5.0.0.
But please correct me, if I'm wrong.
Thanks!

Any news?

@ahsath werk85/node-html-to-text#200

@noxify That PR has been merged now. Looks like their version of minimist in package.json is updated:
https://github.com/werk85/node-html-to-text/blob/00adb127abf1a34d858e117c69b1b2cc223baf6f/package.json#L31

@missmatsuko thanks for the hint - I will check it

@missmatsuko tested it with a fresh installation, but I got the same audit message.
It seems that they have to release the changes

This can be closed, it seems.

Hey @KillyMXI
thanks for the update - i will give it a try and will close the issue if everything is working as expected.

Tested it with
    "@gridsome/transformer-remark": "^0.6.3",
    "gridsome": "^0.7.21",

and the alert isn't shown anymore.


Increase the speed of getting replica back to healthy state

Case

some replica go temporary offline
Distributed table connection pool error_count for that replica get high
replica gets back online again, but Distributed doesn't use it for a long time, as the speed of error_count decreasing is very slow currently (halved every 10 minutes).

We need to make some better heuristic for that.
We can just decrease the value for
DBMS_CONNECTION_POOL_WITH_FAILOVER_DEFAULT_DECREASE_ERROR_PERIOD
but in that case flapping replica errors will be 'forgotten' too fast ( see https://github.com/yandex/ClickHouse/commit/192bbc02859ba140cb46878750318dbbc13f5837 ).
Maybe we should introduce some upper limit for error_count and never increase it above that number to give a chance to return back alive fast enough?

decreasing is very slow currently (halved every 10 minutes)

For whatever reason, I remember that my first intention was to halve every 60 seconds. It means that 1000 errors will vanish after 10 minutes. Let's change it accordingly...

Maybe we should introduce some upper limit for error_count and never increase it above that number to give a chance to return back alive fast enough?

Reasonable. Let it be 1000 by default. It means that 10 minutes is always enough for recovery.
PS. We can also think about totally different algorithms. Some kind of weighted sampling according to bayesian bandits. Reason: if the number of errors differs insignificantly, start to infrequently try use replicas with slightly more errors.

So the proposal is:

Decrease DBMS_CONNECTION_POOL_WITH_FAILOVER_DEFAULT_DECREASE_ERROR_PERIOD to 60 seconds.
Add DBMS_CONNECTION_POOL_WITH_FAILOVER_MAX_ERROR_COUNT = 1000
Add 'replica_error_decrease_period' and 'replica_error_max_count' to make those settings configurable.
Add current error count to system.replicas ?


Webhook notifications

We need quite soon an asynchronous way to notify (remote) third-party code that "events" are happening (pull, push start, push end? pretty much).
One use case is to notify the docker hub and index of events from the registry. Other use cases are enumerated in docker/docker-registry#689, which is superseded by this issue.
Proposal
To implement this feature, we will notify listeners via http messages when a given event happens. Reliable, at-least-once delivery will be attempted until a 2xx response is received.
Notification listeners will be configured in the registry configuration file. Authenticity for a listener can be controlled by TLS certificates if an https endpoint is defined. The configuration may support other sinks besides http/https.
A summary of events in the initial version are the following:

Manifest Pushed
Manifest Pulled
Manifest Deleted
Blob Pushed
Blob Pulled
Blob Deleted

The following sections cover some of the proposed events and an example of what that data might look like. The protocol is subject to change and we are unlikely to lock it down for the beta release.
Actor and Source
The event notifications should include a source and actor, created from the request and authorization context of the request. The actor should indicate which authorized user initiated the event action and any request context (request id, etc.). The source should identify the registry system and node from which the event originated.
Registry Notification Types
Manifests
Manifest Pushed

Name
Tag
Manifest Hash
Current Time
Account (If Known)

Example
{
	"name": "library/ubuntu",
	"tag": "14.04",
	"manifestHash": "sha256:2c39bdf1854ced6871b52452cbe8833edda34c7f299583567b400cecf2998837",
	"currentTime": "2015-01-13T00:15:28.469328",
	"url": "https://registry.docker.com/v2/library/ubuntu/manifests/14.04",
	"account": "tianon"
}

Manifest Pulled

Name
Tag
Manifest Hash
Current Time
Account (If Known)

Example
{
	"name": "jlhawn/crawler-webserver",
	"tag": "v3.1.4-a159",
	"manifestHash": "sha256:941e74dc593fc8976122c316647048399fa0b490b858769739924eea5ea14334",
	"currentTime": "2015-01-13T00:18:05.236706",
	"url": "https://registry.docker.com/v2/jlhawn/crawler-webserver/manifests/v3.1.4-a159",
	"account": "samalba"
}

Manifest Deleted

Name
Tag
Manifest Hash
Current Time
Account (If Known)

Example
{
	"name": "dmcgowan/fresh-baked-cookies",
	"tag": "chocolate-chip",
	"manifestHash": "sha256:4f98543ac6f792c1352e8c5a0555601ab3fd3497810581606c36c7416c5ffe37",
	"currentTime": "2015-01-13T00:18:54.781669",
	"url": "https://registry.docker.com/v2/dmcgowan/fresh-baked-cookies/manifests/chocolate-chip",
	"account": "dmcgowan"
}

Blobs
Blob Pushed (Upon conclusion)

Name
Blob Hash
Current Time
Account (If Known)

Example
{
	"name": "dmp42/portrait-landscape",
	"blobHash": "sha256:bb40a9ef6deed88cb1de6a50b6e2df6d301f52374805b98ca77b819b0f3ed3fa",
	"currentTime": "2015-01-13T00:21:58.110908",
	"url": "https://registry.docker.com/v2/dmp42/portrait-landscape/blobs/sha256%3Abb40a9ef6deed88cb1de6a50b6e2df6d301f52374805b98ca77b819b0f3ed3fa",
	"account": "goforgopher"
}

Blob Pulled (Upon conclusion)

Name
Blob Hash
Current Time
Account (If Known)

Example
{
	"name": "stevvooe/fresh-powder",
	"blobHash": "sha256:d712d5f15eda3abf569f3423714ad10d065d43421ad9efeeb9f6a1f6113ce0a8",
	"currentTime": "2015-01-13T00:23:15.083209",
	"url": "https://registry.docker.com/v2/stevvooe/fresh-powder/blobs/sha256%3Ad712d5f15eda3abf569f3423714ad10d065d43421ad9efeeb9f6a1f6113ce0a8",
	"account": "mikelipz"
}

Originally proposed by @jlhawn from https://gist.github.com/jlhawn/1c177252d343ae042e09.

First real event coming through after a push:
POST /_test HTTP/1.1
Host: localhost:8082
Accept-Encoding: gzip
Content-Type: application/vnd.docker.distribution.events.v1+json
User-Agent: Go 1.1 package http

{
   "events": [
      {
         "uuid": "60605ee7-e34e-4868-a2f3-34b039fa95ee",
         "timestamp": "2015-01-27T16:43:01.403566331-08:00",
         "action": "push",
         "target": {
            "type": "manifest",
            "name": "library/redis",
            "digest": "sha256:ca18155814ea932217da10270a95ed3f0eaeeeb2ffaa4aa08a0ec985367b83f7",
            "tag": "2",
            "url": "http://localhost:5000/v2/library/redis/manifests/2"
         },
         "actor": {
            "name": "--todo--",
            "addr": "<IP_ADDRESS>:58014"
         },
         "source": {
            "addr": "Stephens-MacBook-Pro.local:5000",
            "host": "example.com"
         }
      }
   ]
}

There are some problems to work out, but starting to get somewhere.
cc @jlhawn


Failed to get region

When trying to execute kubescape with EKS cluster I get the following error
➜ kubescape scan --format pdf  --use-artifacts-from /tmp/scape  --exclude-namespaces kube-system,kube-public  -l debug
[debug] Armo URLs. api: api.armo.cloud; auth: auth.armo.cloud; report: report.armo.cloud; UI: portal.armo.cloud
[info] ARMO security scanner starting
[warning] Kubernetes cluster nodes scanning is disabled. This is required to collect valuable data for certain controls. You can enable it using  the --enable-host-scan flag
[info] Downloading/Loading policy definitions
[success] Downloaded/Loaded policy
[info] Accessing Kubernetes objects
◓[debug] Collecting images vulnerabilities
[debug] Collecting rbac resources
[debug] Collecting cloud data
◑[warning] failed to collect cloud data. error: failed to get region
[success] Accessed to Kubernetes objects
[info] Scanning. cluster: arn:aws:eks:eu-central-1:REDACTED:cluster-test
[success] Done scanning. cluster: arn:aws:eks:eu-central-1:REDACTED:cluster-test
[success] Scan results saved. filename: report.pdf

Overall risk-score (0- Excellent, 100- All failed): 31

➜ kubescape -v
kubescape version v2.0.150

@Daniel-GrunbergerCA  Any updates regarding this issue?

Hi @ampc
Thank you for pointing out this issue.
Kubescape tries to get your cluster region from the cluster name. I have updated this functionality. Can you please update to the current latest version (v2.0.151)  and confirm whether it works for you?
We also support reading cloud configuration from environment variables. On this case, you can set the KS_CLOUD_REGION environment variable to "eu-central-1". We will soon release documentation regarding that.

@Daniel-GrunbergerCA
Tested with the latest version and it's working. Thank you.


JedisPool does not really block threads when pool is exhausted

Hi,
I'm using Jedis from a multi threaded environment and I'm constantly getting the
redis.clients.jedis.exceptions.JedisConnectionException: Could not get a resource from the pool     at redis.clients.util.Pool.getResource(Pool.java:22)
Here is my jedisPool config
JedisPoolConfig poolConfig = new JedisPoolConfig();
        poolConfig.setMaxActive(WorkingThreads * 4);
        poolConfig.setMaxIdle(WorkingThreads * 4);
        poolConfig.setMinIdle(5);

    poolConfig.setWhenExhaustedAction(GenericObjectPool.WHEN_EXHAUSTED_BLOCK);
        poolConfig.setMaxWait(- 1);
        poolConfig.setTestOnBorrow(true);

In the above example WorkingThreads = 6 because there are 6 threads running in the same time.
Here is the usage pattern of using Jedis connections:
class Worker
{
    private static JedisPool pool;

// on a thread of execution
   void DoSmth()
{
    Jedis cn =null;
    try
    {
         cn = pool.getResource()
        // do something
    }
    catch { pool.returnBrokenResource(cn); cn=null; }
    finally { if (cn!=null) pool.returnResource(cn);}

}

}

Now the problem is that I never see threads that wait for an available resource and I always get Could not get a resource from the pool error message.
All threads execute the DoSmth method about 100 times a second. I get an error message about 1 per 100K executions. After getting this exception, the thread tries again to obtain a Jedis connection in <5ms and most of the times gets one. If the threadpool is exhausted why doesn't it blocks until a new connection gets available? Also, if all other threads own a connection for an instance of the time, there are still plenty of connections available in the pool. The Redis server is set to close a connection after 30s of inactivity.
Everything got better when using poolConfig.lifo = false; but still i get plenty of errors. Is JedisPool really threadsafe ?
I'm using Redis 2.4 and Jedis 2.1.

Do we need to return resource after getting it from pool ?

@mjmanav4 Yes, but not right after getting it. You should return a resource after completing works with it. Also it is important to note that in current days you don't need to call returnResource anymore. A call to close() of the resource (Jedis) is what you need.


mod multi requires forge 39 or above

was trying to figure out, and couldn't successfully find a way to resolve this issue and still play on forge 38.0.17 on 1.18 minecraft.

Update the mod.


permission denied to access property apply when rendering a component inside Modal component

Hello,
I try to render a custom component (empty for now, just a 'p'  tag for testing) inside the Modal flowbite component like this :
 <Modal v-if="open" @close="closeModal">
            <template #header>

Header test

            </template>
            <template #body>

                   <custom-component"></custom-component>

            </template>
            <template #footer>

The footer test

            </template>
  </Modal>

But I can't and I get this error :
Uncaught Error: Permission denied to access property "apply"
I tried to put my custom component inside 'Suspense' but that's doesn't work...
Any Idea ?
Thanks a lot

Couldn't reproduce the problem, if the error happens again, create a new issue


"Issue" on -h command.

The DM help string still sending the old prefix in the message bellow:
Type -h for help.
That's in BotConfig table and I think that should be changed to automatic detection since we have the .prefix now.
Also, this message is not in ResponseStrings.json, would not this be a problem because the translations?

that's your own setting. DmHelpString. you have to modify it yourself in bot config.


When starting up Kestrel throws EADDRNOTAVAIL error

When starting up the ASP.NET app in IIS, Kestrel throws the following exception:
Microsoft.AspNet.Server.Kestrel.Networking.UvException: Error -4090 EADDRNOTAVAIL address not available
   at Microsoft.AspNet.Server.Kestrel.Networking.Libuv.Check(Int32 statusCode)
   at Microsoft.AspNet.Server.Kestrel.Networking.UvTcpHandle.Bind(ServerAddress address)
   at Microsoft.AspNet.Server.Kestrel.Http.TcpListener.CreateListenSocket()
   at Microsoft.AspNet.Server.Kestrel.Http.Listener.<>c__DisplayClass5_0.<StartAsync>b__0(Object _)

I first thought it might have something to do with having two ASP.NET apps, both listening to port 80 in IIS (different subdomain bindings though). This proved wrong when booting up a fresh VM in Azure, routing subdomain to that one and getting the same error, indicating it might be something else. The only thing I can currently think of that is significantly different from the two ASP.NET apps is that one runs on dnx-clr-win-x<IP_ADDRESS>-rc1-update1 (the failing one) and the other one still on dnx-clr-win-x<IP_ADDRESS>-rc1-final (the working one).
For reference, a StackOverflow I started before trying it on a fresh VM:
http://stackoverflow.com/questions/34228559/how-do-i-get-httpplatformhandler-and-kestrel-to-play-nicely-with-multiple-websit

Update: I confirmed that going back to dnx-clr-win-x<IP_ADDRESS>-rc1-final fixed the issue for me, so it must be some kind of bug introduced in update-1.

@janpieterz There's no known reason for apps on with different subdomains on port 80 to have any problem. What is your web command in project.json?

My apologies about the earlier 'fix'. This only fixed it on my own PC running in IIS, not on the server.
@GuardRex I think you're onto something. I added a server.urls there to allow remote listening while in development, but my File Publish has not removed this so it probably tries to attach itself to an IP it can't reach.
I saw your massive explanation post, also detailing your publish changes. Do you know of any way to have a local server.urls that is different than the deployed one?

@GuardRex Just confirmed it working when I removed my server.urls specific for local usage. Would still appreciate your insight in how to have development urls there while allowing these to be different when deployed.
If you'd like to submit your insights as an answer on StackOverflow I'll accept it as an answer, plus I'll close this issue. Thanks a lot!

@janpieterz I think so ..... sort of ... you can specify the command to run through modifications to the web.config file. Something like this (maybe ... just spitballing here) ...
<httpPlatform
    processPath="%DNX_PATH%"
    arguments="--project F:\MyApp\approot\packages\MyApp\1.0.0\root web"
    stdoutLogEnabled="true"
    stdoutLogFile="..\logs\httpplatform"
    startupTimeLimit="3600"></httpPlatform>

... where you see "web" there ... you could put a different command from project.json, say "web2" ... a command that on the server would have a different server.urls specified. Then, the only issue would be how to substitute the web.config file with the "server version" on the server and the "local version" of web.config still has "web" command with server.urls for the local environment. It should only come down at that point to getting a local web.config and a server web.config.
We would need @Tratcher to come in here with his vast knowledge and tell us if this is the right way to go.

Actually, it might be even simpler than that with the command. This might work ...
```xml
<httpPlatform
    processPath="%DNX_PATH%"
    arguments="--project .. web"
    stdoutLogEnabled="true"
    stdoutLogFile="..\logs\httpplatform"
    startupTimeLimit="3600"></httpPlatform>

@janpieterz I just filed an issue related to this for doc coverage that deals with configuration of the httpPlatform element in scenarios just like this: https://github.com/aspnet/Docs/issues/786. Please do ping back if this turns out to be a good approach.

That  would certainly work for me, although I'd more expect the core of my issue (the binding to a non-existing IP, no way to 'overwrite' whatever is in project.json when publishing (should this be a publish setting?)) to be solved differently.

@janpieterz Not so far as I know ... I mean when you say override or overwrite what's in project.json, you'd have to do something like this with PowerShell ... https://github.com/GuardRex/net5-autoupdate-version ... but its horrible and might not even work.
I have a gut feeling that having two commands in project.json and then triggering one command locally and triggering the other command on the server probably fits the design best. It only comes down to triggering one command or the other with a local web.config and a server web.config. I'm trying to think what I've seen about that scenario of having a different web.config on the server, but I don't remember it coming up.
The only reason that IIS Basic Settings path to the application is pointed to wwwroot is to read the web.config file AFAIK. I wonder if you would simply point the app in IIS to read from a folder where there is a server web.config file sitting there that isn't published with the app ... that web.config is the one with this other command that has the server.urls that the server should be using. That file would sit in a stable location outside of your deployment.
Really though ... when things get this wild, you need @Tratcher to jump in and give us a hand.


rdkafka: Add zstd support

Motivation for this change
Needed zstd support in kafkacat
Things done
Tested consuming from a kafka topic with zstd compression enabled via kafkacat.

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 129520 at 0e2591aa run on aarch64-linux 1

3 packages marked as broken and skipped:

clickhouse
python38Packages.streamz
python39Packages.streamz

7 packages skipped due to time constraints:

bareos
ceph (ceph-dev)
ceph-client
ceph-csi
libceph
qemu_full
vector

13 packages built successfully:

collectd
collectd-data
haskellPackages.haskakafka
haskellPackages.hw-kafka-client
haskellPackages.hw-kafka-conduit
haskellPackages.mu-kafka
haskellPackages.pipes-kafka
kafkacat
libserdes
python38Packages.confluent-kafka
python39Packages.confluent-kafka
rdkafka
rsyslog

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 129520 run on x86_64-linux 1

1 package marked as broken and skipped:

bareos

1 package failed to build and already failed to build on hydra master:

python38Packages.streamz: log was empty

1 package failed to build and are new build failure:

ceph-client: log was empty

23 packages built:

ceph (ceph-dev)
ceph-csi
clickhouse
collectd
collectd-data
haskellPackages.haskakafka
haskellPackages.hw-kafka-client
haskellPackages.hw-kafka-conduit
haskellPackages.mu-kafka
haskellPackages.pipes-kafka
kafkacat
libceph
libserdes
php74Extensions.rdkafka
php80Extensions.rdkafka
python38Packages.confluent-kafka
python39Packages.confluent-kafka
python39Packages.streamz
qemu_full
rdkafka
rsyslog
sambaFull (samba4Full)
vector


Automate release

Should include:

Tagging
PR for new version on CDNs
Add release notes.
Push to CDNs

We believe this is fixed in 2.0.0.  Please retest against 2.0.0 release and open a new issue following Issue Reporting guidelines in 2.0.0 if you believe this is still an issue.


Specify python version and decode filenames from utf8

I am not very familiar with python, so this PR mostly points to 2 problems:

script looks not compatible with python3, so I need to specify python2 in 1st line
script cannot handle unicode filenames despite UTF-8 locale
After these 2 commits it started working on my system.

The intention is to support both versions. I plan to fix this issue next
week.
On Fri, Jul 8, 2016, 10:14 googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project. Before we can look at your
pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll
verify. Thanks.

If you've already signed a CLA, it's possible we don't have your
GitHub username or you're using a different email address. Check your
existing CLA data https://cla.developers.google.com/clas and verify
that your email is set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
If you signed the CLA as a corporation, please let us know the
company's name.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/adb-sync/pull/5#issuecomment-231370440, or mute
the thread
https://github.com/notifications/unsubscribe/AAPWsCJYbhO2PyEJyrQIXHobB_QLx0J9ks5qTls2gaJpZM4JIEeV
.

Just committed hopefully all required UnicodeError fixes. There were a few more. Can you retest both in Python 2 and 3?

Thank you, looks working for me.

I assume this is obsolete now, as the real fix was changing
     if line.startswith('total '):

to
     if line.startswith(b'total '):

I'm gonna migrate the code to have some type checking in order to better detect such issues.


Submit fellowship application

Description

This is for the maintainers as part of the fund launching work.
Specifics

[x] write answers draft
[x] write video script draft
[x] record video
[x] submit application

@chrisaddy 🎉


Coins added to portfolio are not saved across restarts

Is there a setting to make this save?

Added to latest commit: https://github.com/KomodoPlatform/BarterDEX/commit/b41700044e2c91aa10434174c8307b142dc80f24

This is the best day :D


UI and REST API need a shared ground truth for application logic

@pkdash @dtarb @mauriel133 @horsburgh
Issue #1618 demonstrates a design issue that is going to come up repeatedly as we try to complete the REST API. Much of the application logic of HydroShare -- including what can be done to each kind of resource -- is only implemented at the UI level. Though there is a spreadsheet defining some what this logic is, it covers only file/folder issues and is not comprehensive. A systematic approach needs to be developed that serves as "ground truth" for both the UI and the REST API as to how to implement this application logic.

A common approach -- though I am not yet recommending this -- is to make the REST API definitive and have the UI refer to it as to what is allowed. Thus, the application logic is implemented as a set of external and internal REST endpoints. The reason people do this is that REST helps one code this easily.

The other way to approach this is to create application middleware that both the UI and REST interface refer to in determining application logic. This is what the access control system is, but it is only a subsystem of application logic and does not document the limits of what can be done in editing each kind of resource. We would need a different logic engine to determine what one "can" do to each kind of resource, separate from the UI. This would not be an authorization logic like access control, but rather, a validation logic for edits that determines what kinds of edits can be performed without violating resource type limitations.  Our existing validators are not comprehensive enough to serve this function -- yet.

@alvacouch I think having a validation app/module for various actions on resource that both the REST and internal view functions can use would be better.

@aphelionz I would like you to think about this issue.

@alvacouch @pkdash
I think you're both right. We need to start steering towards the idea that the UI and the REST API are separate, that the REST API is the one and only source of truth in the application, AND that middleware modules are going to save us from ourselves.
We need to stop putting application logic in the views starting now and only use them to render templates, and then only access the REST API via AJAX calls in the UI layer. That will be a huge step in the right direction.

@alvacouch @pkdash @aphelionz Totally agree REST API and UI need to share the ground truth for application logic. I believe we have been trying to achieve this by putting application logic into utility functions/methods that are called by both views for UI and REST API end points. We definitely want UI and REST API to behave similarly that utilize the same ground truth application logic so we only need to maintain application logic in one place without duplication.

@hyi @alvacouch @pkdash
I want to be careful in how we talk about this so we're clear about what our objectives are.
When we say the UI and REST API behave similarly, my concern is that there are two code paths that the application execution can take - one through the UI layer from a user clicking through the site, and another through the API layer from applications and AJAX calls.
My proposal is that they should be one and the same, and all logic should live within and ONLY within the REST API. This can be achieved with short term and long term implementations.

Stop putting application logic in the views, only use views to render HTML scaffolding and require the templates to fire AJAX requests to the REST API moving forward. We can start doing this today.
Incrementally refactor out (over the following weeks/months) application logic that exists within the views to middleware that the REST API can consume to fulfill any requests made to it.

An easy win would just be to pick a single page or section of the application to do this with. I can't suggest one right now because I'm part way through auditing the code, but I will make a proposal when I'm done. In the meantime I'm open to suggestions! Is there a module or section of the app that's compartmentalized enough to do easily as a proof of concept?

@aphelionz This may be a naive question, but by require the templates to fire AJAX requests to the REST API moving forward, how are views are used then? Currently, templates fire all requests to internal APIs which are mapped to view functions. These view functions pretty much retrieve parameters from requests and then call common utility functions (which can be put into a middleware layer) that are called by corresponding REST API end points as well, then return a HTML scaffolding page. Yeah, it'd be good if you can pick a single page to do this to illustrate your proposal so I can understand it better. I suggest the My Resource page as a candidate to start with since it only involves one view function create_resource() once the Create new button is clicked, so thought that might be a good place to start as a proof of concept.

@hyi
Not a naive question at all! My proposal is very opinionated and dogmatic, but I think it's necessary in order to keep our code and architecture clean. Maybe a better way to say what I said would be "For application logic, we need to incrementally start replacing django.Views with django_rest_framework.Views"
This is a utopian vision, so bear with me: In the end, I'd like to see one single django view that renders HTML to the browser: url('^$', 'views.index') or something like it. From that index we would build out a Polymer/React/ Much like what Mezzanine does. Then, before that in urls.py we consolidate all application logic. Thus our Django app becomes a large-scale REST API that also happens to render an index.html file, which contains the front-end app.
Now that I've said that and probably horrified everybody reading it, do know that my proposal is much less a one-time overhaul of everything and much more steering the ship slowly toward a new bearing. I'm very sensitive to the concerns of user-facing functionality, the horrors of refactoring, and the risk of losing funding if things go wrong.

Also @hyi great suggestion in regards to the My Resource page. That's perfect - essentially one AJAX call to retrieve the list of resources, and another AJAX call to create new.

@alvacouch @pkdash @hyi
SEO Concerns about having a primarily AJAX driven front end can be mitigated with three approaches

Google and other crawlers are showing an increasing aptitude in crawling JS-rendered data
We can explicitly submit a sitemap.xml telling Google/Bing/etc exactly where every single resource is located
We can use the history.pushState api, or a routing library to generate proper urls and not have to rely on "hash" urls like /#/my-resources anymore

@aphelionz Thanks for the elaboration on your proposal. Now I understand what you are proposing here and I'd be looking forward to seeing your proof-of-concept.

@hyi I will aim to not disappoint :)

@aphelionz I like this architecture you are proposing which seems to be a standard way of doing things in modern web applications. Though I have little background in UI frameworks and UI programming, I think we are not using any of the available JavaScript reactive frameworks to our advantage. I feel like we have lot of logic built into template code. Some of the templates are huge too.

Inviting in @dtarb @mseul @danames @horsburgh with a little high-level background on this issue. This issue came about when I was assigned to take over the REST API. My goals in this are to:

Make it possible to do more or less anything in a Tethys app that one can do in the UI. Thus
The Tethys apps can "extend" the UI in ways that help users, more easily than we can extend the core UI.

The main vehicle for this is the REST API.
However, I quickly discovered that this involves an "arms race" between the REST API and the UI:
3. Anything that one does in one, one has to duplicate in the other.
4. Both embody complex application logic.
5. This logic is difficult to keep in sync.
This makes keeping the REST API and the UI in sync an ongoing management nightmare.
The most complex piece of this determining "What is one allowed to do to a resource of a specific type?" This is currently hard-coded into the views of the various kinds of resources. Clearly, this logic needs to be in one place, rather than two. But more importantly, the Tethys apps should also be able to utilize this logic. The only place that one can put the logic that makes total sense, therefore, is the REST API: it is the glue between Tethys and the UI.
So, this is not a proposal for changing the UI. It is instead a proposal for adopting a different set of practices for constructing the UI. There are many ways we could build the UI. All of them result in more or less the same look and feel to a user. The technique we pick depends upon other requirements. The technique we picked initially was from the Django tutorials. This is fine for simple sites, but we have an extra requirement: a facile interface to apps.hydroshare.org. That changes the picture substantively, as well as the appropriate practices.
The new set of practices is just as expressive as the way we've been making the UI so far, but it has the added advantage of eventually enabling one to do more or less anything with a Tethys app that one can do with the UI, with a guaranteed consistent response regardless of which way one interacts with the system. It also allows independent programmatic control by programs that are not Tethys apps, at the same level of expression.
The Tethys apps are the future of the UI, and I want to enable them to the extent possible. But this also -- automagically -- enables automatic population of resources from external means.

Copy that, @alvacouch. Thanks for the context My proposal stands.


Export Text Customization

Description
Ability to customize more export settings, specifically:

Ability to disable hierarchy view or adornment text in output -- just display raw API calls in order
Ability to turn off EID and/or action number text in output
Cleanup of HTML tags in export text (only the params are marked up currently, so they're hard to read in a text editor... meanwhile, the other text isn't marked up at all so you can't view it in a browser)
Optional HTML / plain text
(stretch) Collapsible groups for hierarchy in HTML output

The first two would greatly help when using diff tools; currently, the first difference breaks the chain because all subsequent EID / action numbers are different.
The others would also help when showing others and for general readability.
Environment
RenderDoc 1.15 (https://github.com/baldurk/renderdoc/commit/a490606012b4ba1785cec109180acb21990f7594)
Windows 10
OpenGL
Thanks!! RenderDoc is awesome!

From what you're describing I assume you're talking about the export from the event browser, though I'm not sure what you mean about markup for parameters.
I don't think this is a valuable enough feature to add though. If you wanted more customisable/sophisticated export options you could write a UI extension to add whichever features you want, but I don't think this merits adding extra complexity.

Yes, the event browser export is what I meant.
I've attached an example of the html markup - it's hard to read in a normal text editor (notepad++), but impossible to read in a web browser, because it's not all marked up with html tags.
As for the other things (removing EIDs / action numbers)... if I add code to strip those (and the tree characters) and insert check boxes in the options dialog to control that, would you accept a pull request for the changes?
parameters_in_html.txt

OK that is definitely a bug, those are not meant to be there. That's purely for styling in the UI. I'll fix the code to strip those tags properly.
I would not want a pull request for those changes, if I thought the feature was beneficial to add I would leave the issue open to implement eventually - I don't expect/require user contributions or close on those grounds. As I say if you want it on the main builds you could write a UI extension, or else if you'd prefer to make the changes you could build a modified version of RenderDoc locally.


Add new version 2.0.1 to issue bug template

@kezhenxu94  You are right. BTW, does it have some way auto-update github issue version base on git tag or release version? I search and could not found it

@kezhenxu94 You are right. BTW, does it have some way auto-update github issue version base on git tag or release version? I search and could not found it

We can do that via GitHub Action , will do some investigation

I thinks we could delete and do no accept issue in below version, WDYT @lenboo @CalvinKirs @caishunfeng @kezhenxu94 @dailidong
- 2.0.0-alpha
- 1.3.4
- 1.3.4
- 1.3.3
- 1.3.2
- 1.3.1
- 1.2.1
- 1.2.0
- 1.1.0(Not Apache Release)

In other word , we only accept bug report in version
- dev
- 2.0.1
- 2.0.0
- 1.3.9
- 1.3.8
- 1.3.6

Codecov Report

Merging #7458 (85cb510) into dev (1f1edb2) will decrease coverage by 0.06%.
The diff coverage is 32.20%.

:exclamation: Current head 85cb510 differs from pull request most recent head 9eb0c12. Consider uploading reports for the commit 9eb0c12 to get more accurate results

@@             Coverage Diff              @@
##                dev    #7458      +/-   ##
============================================
- Coverage     41.29%   41.22%   -0.07%
+ Complexity     3664     3657       -7
============================================
  Files           634      635       +1
  Lines         26397    26426      +29
  Branches       2957     2959       +2
============================================
- Hits          10900    10895       -5
- Misses        14470    14505      +35
+ Partials       1027     1026       -1

Impacted Files
Coverage Δ

...cheduler/api/controller/AccessTokenController.java
88.23% <ø> (ø)

...r/api/service/impl/WorkFlowLineageServiceImpl.java
35.35% <0.00%> (ø)

.../org/apache/dolphinscheduler/common/Constants.java
80.00% <ø> (ø)

.../org/apache/dolphinscheduler/dao/MonitorDBDao.java
11.76% <0.00%> (ø)

...e/dolphinscheduler/dao/utils/MySQLPerformance.java
0.00% <0.00%> (ø)

...phinscheduler/dao/utils/PostgreSQLPerformance.java
0.00% <0.00%> (ø)

.../datasource/api/client/CommonDataSourceClient.java
0.00% <0.00%> (ø)

...asource/api/datasource/BaseDataSourceParamDTO.java
78.57% <ø> (ø)

...asource/clickhouse/ClickHouseDataSourceClient.java
0.00% <ø> (ø)

...r/plugin/datasource/hive/HiveDataSourceClient.java
1.51% <0.00%> (-0.03%)
:arrow_down:

... and 68 more

Continue to review full report at Codecov.

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

I thinks we could delete and do no accept issue in below version, WDYT @lenboo @CalvinKirs @caishunfeng @kezhenxu94 @dailidong
- 2.0.0-alpha
- 1.3.4
- 1.3.4
- 1.3.3
- 1.3.2
- 1.3.1
- 1.2.1
- 1.2.0
- 1.1.0(Not Apache Release)

In other word , we only accept bug report in version
- dev
- 2.0.1
- 2.0.0
- 1.3.9
- 1.3.8
- 1.3.6

If we agree and do that, we should upgrade our doc, and point out to user which version is our LTS project

I thinks we could delete and do no accept issue in below version, WDYT @lenboo @CalvinKirs @caishunfeng @kezhenxu94 @dailidong
- 2.0.0-alpha
- 1.3.4
- 1.3.4
- 1.3.3
- 1.3.2
- 1.3.1
- 1.2.1
- 1.2.0
- 1.1.0(Not Apache Release)

In other word , we only accept bug report in version
- dev
- 2.0.1
- 2.0.0
- 1.3.9
- 1.3.8
- 1.3.6

+1

manifest for apache/dolphinscheduler:2.0.1 not found:

manifest for apache/dolphinscheduler:2.0.1 not found:

We need some time to push the Docker images, and next time please don't mix the issue, your questions I nothing to do with this pull request

sorry

@a5833488 Docker images for 2.0.1 are pushed


Move dev deps into devDependencies

Scope & Purpose
This moves undocumented JS dependencies we only use during ArangoDB development (e.g. testing, build) into the devDependencies section of our package.json file to allow easier filtering of these during releases.
This has no effect on its own but allows us to adjust the release process to not rely on hardcoded lists and instead look at the actual JSON.

[x] :hammer: Refactoring/simplification

Checklist
N/A
Related Information

[x] Jira ticket: APM-277

What about mocha?

Replaced by #16542, which includes these changes.


Local session management

Track the current user session in a unique LocalStorage entry and offer the list of previous sessions on page load if the user wants to resume.

Display a non-intrusive, self-dismissing prompt to let the user know there are existing sessions to resume. The modal should only appear if the user wants to continue. Do not prevent the user from working on a fresh page by having to dismiss a modal.
Allow users to delete or clear all the previous sessions. Otherwise, it will keep building up in the browser cache.
User sessions should now have created and last updated timestamps.
Give the user an option to name the session for easier resume

The sessions are now persisted across refreshes as part of https://github.com/labeleven-dev/bettercallsol/pull/89 in sessionStorage. This solves a few of our problems.
This issue probably needs to be reworked into a save/load feature


QA-1607: Enhance TestRunner to include test types based on the test suite configuration.

This PR enhances TestRunner to include the test configuration file name from TestSuite as a new property (resourceFileName property) in TestRunSummary and TestConfiguration classes.
The resourceFileName property is of the format

perf/**.json
integration/**.json
resiliency/**.json

etc.
This enhancement facilitates grouping of test runner results on the dashboard.
For a screen shot of the BigQuery table with the new resourceFileName property, see the Acceptance Criteria section of the Jira ticket QA-1607..
For a trial WSM test run using this new version (0.0.9-SNAPSHOT), please refer to workflow https://github.com/DataBiosphere/terra-workspace-manager/runs/3956951516?check_suite_focus=true.

@marikomedlock  One more note on the output files generated by TestRunner. Of the following files only SUMMARY_testRun.json contains a unique id.
RAWDATA_userJourneyResults.json RENDERED_testConfiguration.json SUMMARY_testRun.json
I think we should enhance TestRunner with two wrapper classes for test config and user journey results with the additional id property matching the SUMMARY_testRun.
We could do it in a separate PR.

I like the idea of combining the other JSON files into SUMMARY_testRun.json. The Cloud Function doesn't care about the layout of the JSON, it simply bulk uploads the JSON fields matching the BigQuery table schema in the backend.

That sounds good to me. If you'd prefer to get this change in so your dashboard work can continue, and then make a future ticket to combine the files and eliminate the duplication here, I'm good with that too. Let me know.

I created a new Jira ticket QA-1612 to merge the output files. I am all good for this ticket to move forward.


[Meru] [New pricing] Implement middleware to check that the user has a valid subscription for pages of the app.

All pages of the app (but a few, like the subscribe and settings pages) needs to be gated by a valid subscription,  we need to add a new flag to the requireSubscription to withDefaultUserAuthRequirements in front/lib/iam/session.ts and mark all to be gated pages with that flag set to true.

Will use plan.limits.canUseProduct once #4290 lands


correct bad path config-sample file

Just saw this flaw while installing :)

Nice catch! Thanks for the fix :+1:


_ebpf_program_program_information_provider_changed must ensure program type descriptor and helper prototypes remain unchanged upon provider load.

ebpf_program must save the program type descriptor and helper prototypes once a program-info provider attaches. After that it must use the saved value to compare when provider reloads to make sure those havent changed. The only allowed change are the helper function addresses.

Maybe save a hash


ENH/FIX: use scipy / avoid creating figure for computing PSDs

mpl.psd does not play nicely with memory / forking / joblib. Use matplotlib.mlab.csd directly to avoid opening figures or use scipy.signal.welch instead.
example:

def _pwelch(epoch, nperseg, noverlap, nfft, fs):
    return [welch(channel, nperseg=nperseg, noverlap=noverlap,
                  nfft=nfft, fs=fs)[1]
            for channel in epoch]

def compute_psds(epochs, fmin=0, fmax=np.inf,
                 segment_size=128, n_overlap=100, n_fft=4096, n_jobs=1,
                 keep_mean=False, verbose=None):
    X = epochs.get_data()
    if keep_mean is not True:
        X = X.copy()
        X -= np.nanmean(X, axis=-1)[..., np.newaxis]

    sfreq = epochs.info['sfreq']
    parallel, my_pwelch, _ = parallel_func(
        _pwelch, n_jobs=n_jobs, verbose=verbose)

    psds = np.empty(epochs.get_data().shape[:-1] + (n_fft // 2 + 1,))
    freqs = np.arange(psds.shape[-1]) * (sfreq / n_fft)
    for i_epoch, fepoch in enumerate(parallel(
        my_pwelch(epoch, nperseg=segment_size, noverlap=n_overlap, nfft=n_fft,
                  fs=epochs.info['sfreq']) for epoch in X)):
        for i_channel, fchannel in enumerate(fepoch):
            psds[i_epoch, i_channel, :] = fchannel

    freq_mask = np.where(np.logical_and((freqs > fmin), (freqs < fmax)))[0]
    freqs = freqs[freq_mask]
    psds = psds[..., freq_mask]
    return psds, freqs

@yousrabk wan't to give it a try?

see #1748


Bug: incorrect formatter output with explicit MIN_FRACTION_DIGITS

'numberFormatterOptions'=>[
                NumberFormatter::MIN_FRACTION_DIGITS => 0,
                NumberFormatter::MAX_FRACTION_DIGITS => 0,
 ]

\Yii::$app->formatter->asCurrency($model->price, 'EUR');

//output 129 517,00 €

Here is why this happens: http://php.net/manual/en/numberformatter.formatcurrency.php#114376

@cebe this happens while
main.php //global configuration
'numberFormatterOptions'=>[
                NumberFormatter::MIN_FRACTION_DIGITS => 0,
                NumberFormatter::MAX_FRACTION_DIGITS => 0,
 ]

Fixed, thanks for reporting! Also congrats to the nice issue number :)

Have same problem in 2.0.12(intl is 1.1). asCurrency() ignores numberFormatterOptions.
Code after https://github.com/yiisoft/yii2/blob/2.0.12/framework/i18n/Formatter.php#L1373 breaks formatting. If I delete it or place before "// set attributes" comment or delete options in Formatter config (such as decimalSeparator, thousandSeparator) all works fine.

@ptz-nerf please open a new issue and provide the code that produces the problem.

Hi! I have a same problem in 2.0.16, ICU version is 60.2, PHP version is 7.2.15, OS Ubuntu 18,04.
echo Yii::$app->formatter->asCurrency(2000, 'USD'); // "2 000,00 $", but except "2 000 $"


'SVGElement.offsetHeight' is deprecated

Chrome Canary reports "'SVGElement.offsetHeight' is deprecated and will be removed in M50, around April 2016. See https://www.chromestatus.com/features/5724912467574784 for more details". Obviously not too pressing yet but I thought I'd mention it.

On closer inspection this actually me running jQuery 1.11.3 with some other code alongside. My apologies, please ignore.


Memory settings

Not going to go through ghacks-user.js line by line for now, is there any memory settings changed there? I notice FF uses more memory than before, and getting heavy after sometimes. Could it be add-ons memory leak, I've no idea for now

no "memory settings" per se but cache is disabled by default. Can't think of anything else from the top of my head that could cause increased memory usage.

I think it could be something prevent FF to use swap page, instead its continue filling up ram
I remember that happened that time when I used Tor browser hardened version, even later its developers commented about that thing, I hope ghacks-user.js got nothing to do with that, also the FF private window is heavier than I used to feel before ghacks-user.js.. any way I'll investigate the root of that thing, would post again later..

There's really nothing in the user.js that should affect core performance except

the e10s section which is inactive and there as a FYI
disk cache which IMO should have no affect if you have plenty of RAM and don't have 100's of tabs open
GPU / hardware acceleration << if you disable and reset the two prefs under 2508. I would also go to the settings "Options>Advanced>General>Use hardware acceleration when available" and toggle this off and back on to make sure that anything OS specific gets picked up

What's the propose of e10 section?

It's under 1100 section.

A lot of graphics related settings are disabled , webgl 2d 3d etc.. I doubt if FF still that usable, I'm facing difficulties  with cookies and lastpass, feeling like to go back to use vanilla FF with some slight tweaks..

Cookies are disabled by default, thus logins are problematic.
You have to either edit the user.js or install a cookie manager.

Cookies are disabled by default, thus logins are problematic You have to either edit the user.js or install a cookie manager.

I know that, I turned everything off, I exit FF, launched it again my cookies in the exception list keeps get deleted...

@bonbonboi
Try a brand new profile and add the user.js. Excluding video performance (gpu/hardware acceleration will make a difference), there really is NOTHING that will cripple/ruin FF's performance. Your problems are more likely to be with extensions - you have already (I think) mentioned decentraleyes being slow (or maybe that was someone else). I'm not having any of these problems - default user.js and I have decentraleyes. Going to close this ticket.

As for your cookies problem, try removing all the entries: about:preferences#privacy

Exceptions

remove the entries for allowed or whatever you have in there - make a list first for later

Show Cookies

Remove them all

Now go to each site you wanted the exception and click on the info icon in the urlbar>right arrow>more information>Permissions tab> Set Cookies - uncheck use default and tick "Allow" or "Allow for Session".
I have the same issue with Cookie Controller. Items added via CC work fine, items added manually are not respected by CC. CC of course has an extra setting (Allow first party only).
I do not know why your cookies seem to be messed up, but if you're like me - I have about 20 entries for cookies since everything is blocked by default, so it should be easy to make a quick list, clear it, wipe cookies, re-add exceptions.


New Rector to read entity property type from the Attribute

The TypedPropertyFromColumnTypeRector exists, but as it seams it works only on Annotations not on Attributes.

That would be great addition. Could you send a PR?

Closing as accepted to avoid keep issue tracker focus on unclear issues that needs our attention.
Feel free to send PR with it :+1:


Added the X icon in social links.

PR Description 📜
Fixes #88

Mark the task you have completed ✅

In the GameSphere-Multiplayer, the X icon(formerly Twitter) is added.
This would increase the number of players since X is a large social community.

Point down the features

[X] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[X] I have performed a self-review of my own code or work.
[X] My changes generates no new warnings.
[X] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[X] I have added screenshot for review.

## Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Raised PR. Kindly check it @Durgesh4993

OK @Durgesh4993 I will change it

I've removed the last icon kindly check it @Durgesh4993

Changes made as suggested kindly merge the pr @Durgesh4993

Kindly merge the pr @Durgesh4993.

Made necessary changes..kindly merge it @Durgesh4993

I have made the changes as suggested why is it not merged ? Kindly clarify @Durgesh4993


Code coverage Monitoring Integration

Add Jest Coverage Reporting
Description
Enable test coverage reporting for the frontend using Jest to track code coverage and identify untested parts of the codebase.
Tasks

Update Jest configuration to enable coverage collection.
Ensure the coverage report is generated in the coverage/ directory.
Use the following coverage reporters:

text: Displays coverage in the terminal.
lcov: Generates an lcov.info file.
html: Generates an interactive HTML report.

/assign


Upstream Spec Changes

So it looks like currently this extension has drifted a bit from the upstream spec that's being ratified. Most notably the prefix has changed from KHR to MSFT, and some other minor property names have changed as well.
Would you be open to a PR to change these names in the exporter to reflect the upstream?

The KHR version is actually the most recent version and has had additional feedback applied which are not in the MSFT version. The PR in the Khronos repo hasn't been updated just to avoid noise while we finish the last few pieces, but you can see the history in https://github.com/eoineoineoin/glTF
An earlier version of this plugin does use the MSFT prefix (but I suspect that's not what you want!):
https://github.com/eoineoineoin/glTF_Physics_Blender_Exporter/tree/hk_users


[BUG] service CA and hostpath are getting the incorrect ip address

What happened:
[vagrant@fedora ~]$ kubectl get po -o wide -n openshift-service-ca            service-ca-7bffb6f6bf-46276
NAME                          READY   STATUS    RESTARTS   AGE    IP          NODE     NOMINATED NODE   READINESS GATES
service-ca-7bffb6f6bf-46276   1/1     Running   2          4m6s   <IP_ADDRESS>   fedora   <none>           <none>
[vagrant@fedora ~]$ kubectl delete po -n openshift-service-ca            service-ca-7bffb6f6bf-46276
pod "service-ca-7bffb6f6bf-46276" deleted
 [vagrant@fedora ~]$ kubectl get po -o wide -n kubevirt-hostpath-provisioner kubevirt-hostpath-provisioner-59t4b
NAME                                  READY   STATUS    RESTARTS   AGE     IP          NODE     NOMINATED NODE   READINESS GATES
kubevirt-hostpath-provisioner-59t4b   1/1     Running   0          5m57s   <IP_ADDRESS>   fedora   <none>           <none>

What you expected to happen:
[vagrant@fedora ~]$ kubectget po -o widepo -n openshift-service-ca    service-ca-7bffb6f6bf-hxhrk
NAME                          READY   STATUS    RESTARTS   AGE   IP          NODE     NOMINATED NODE   READINESS GATES
service-ca-7bffb6f6bf-hxhrk   1/1     Running   0          18s   <IP_ADDRESS>   fedora   <none>           <none>
[vagrant@fedora ~]$ kubectl get po -n kubevirt-hostpath-provisioner   kubevirt-hostpath-provisioner-lkdwm -o wide
NAME                                  READY   STATUS    RESTARTS   AGE   IP          NODE     NOMINATED NODE   READINESS GATES
kubevirt-hostpath-provisioner-lkdwm   1/1     Running   0          52s   <IP_ADDRESS>   fedora   <none>           <none>

How to reproduce it (as minimally and precisely as possible):

Deploy steps from microshift.io
kubectl get po -o wide -n service-ca -n openshift-service-ca
kubectl get po -o wide -n kubevirt-hostpath-provisioner

Anything else we need to know?:

RPM
^C[root@fedora ~]# kubectl get po -wA
NAMESPACE              NAME                              READY   STATUS              RESTARTS   AGE
kube-system            kube-flannel-ds-b9vdq             0/1     Init:0/2            0          9s
openshift-dns          dns-default-nj4w2                 0/2     ContainerCreating   0          9s
openshift-dns          node-resolver-dwg8k               0/1     ContainerCreating   0          9s
openshift-ingress      router-default-6c96f6bc66-n5jvm   0/1     Pending             0          13s
openshift-service-ca   service-ca-7bffb6f6bf-67hcg       0/1     Pending             0          14s
kube-system            kube-flannel-ds-b9vdq             0/1     Init:1/2            0          14s
kube-system            kube-flannel-ds-b9vdq             0/1     PodInitializing     0          38s
kube-system            kube-flannel-ds-b9vdq             1/1     Running             0          39s
kubevirt-hostpath-provisioner   kubevirt-hostpath-provisioner-x9p5d   0/1     Pending             0          0s
kubevirt-hostpath-provisioner   kubevirt-hostpath-provisioner-x9p5d   0/1     Pending             0          0s
kubevirt-hostpath-provisioner   kubevirt-hostpath-provisioner-x9p5d   0/1     ContainerCreating   0          0s
openshift-ingress               router-default-6c96f6bc66-n5jvm       0/1     Pending             0          54s
openshift-service-ca            service-ca-7bffb6f6bf-67hcg           0/1     Pending             0          55s
openshift-ingress               router-default-6c96f6bc66-n5jvm       0/1     ContainerCreating   0          54s
openshift-service-ca            service-ca-7bffb6f6bf-67hcg           0/1     ContainerCreating   0          55s
openshift-dns                   node-resolver-dwg8k                   1/1     Running             0          117s
kubevirt-hostpath-provisioner   kubevirt-hostpath-provisioner-x9p5d   1/1     Running             0          77s
openshift-service-ca            service-ca-7bffb6f6bf-67hcg           1/1     Running             0          2m7s
openshift-dns                   dns-default-nj4w2                     1/2     Running             0          4m5s
openshift-dns                   dns-default-nj4w2                     2/2     Running             0          4m5s
openshift-ingress               router-default-6c96f6bc66-n5jvm       0/1     Running             0          4m10s
openshift-ingress               router-default-6c96f6bc66-n5jvm       0/1     Running             0          4m11s
openshift-ingress               router-default-6c96f6bc66-n5jvm       1/1     Running             0          4m24s

Containerized
NAMESPACE              NAME                          READY   STATUS    RESTARTS   AGE
openshift-service-ca   service-ca-7bffb6f6bf-n9rnj   0/1     Pending   0          0s
openshift-service-ca   service-ca-7bffb6f6bf-n9rnj   0/1     Pending   0          0s
openshift-ingress      router-default-6c96f6bc66-7rnm5   0/1     Pending   0          0s
openshift-ingress      router-default-6c96f6bc66-7rnm5   0/1     Pending   0          0s
openshift-service-ca   service-ca-7bffb6f6bf-n9rnj       0/1     Pending   0          5s
openshift-dns          dns-default-j2vnx                 0/2     Pending   0          0s
openshift-dns          node-resolver-wr7w2               0/1     Pending   0          0s
openshift-ingress      router-default-6c96f6bc66-7rnm5   0/1     Pending   0          5s
openshift-dns          dns-default-j2vnx                 0/2     Pending   0          0s
openshift-dns          node-resolver-wr7w2               0/1     Pending   0          0s
kube-system            kube-flannel-ds-4dnf9             0/1     Pending   0          0s
kube-system            kube-flannel-ds-4dnf9             0/1     Pending   0          0s
kube-system            kube-flannel-ds-4dnf9             0/1     Init:0/2   0          1s
openshift-dns          node-resolver-wr7w2               0/1     ContainerCreating   0          1s
openshift-dns          dns-default-j2vnx                 0/2     ContainerCreating   0          1s
kubevirt-hostpath-provisioner   kubevirt-hostpath-provisioner-2qmtb   0/1     Pending             0          0s
kube-system                     kube-flannel-ds-4dnf9                 0/1     Init:1/2            0          10s
kubevirt-hostpath-provisioner   kubevirt-hostpath-provisioner-2qmtb   0/1     Pending             0          0s
kubevirt-hostpath-provisioner   kubevirt-hostpath-provisioner-2qmtb   0/1     ContainerCreating   0          0s
openshift-service-ca            service-ca-7bffb6f6bf-n9rnj           0/1     Pending             0          18s
openshift-ingress               router-default-6c96f6bc66-7rnm5       0/1     Pending             0          18s
openshift-service-ca            service-ca-7bffb6f6bf-n9rnj           0/1     ContainerCreating   0          18s
openshift-ingress               router-default-6c96f6bc66-7rnm5       0/1     ContainerCreating   0          18s
kube-system                     kube-flannel-ds-4dnf9                 0/1     PodInitializing     0          57s
kube-system                     kube-flannel-ds-4dnf9                 1/1     Running             0          58s
kubevirt-hostpath-provisioner   kubevirt-hostpath-provisioner-2qmtb   1/1     Running             0          90s
openshift-dns                   node-resolver-wr7w2                   1/1     Running             0          2m1s
openshift-service-ca            service-ca-7bffb6f6bf-n9rnj           1/1     Running             0          2m6s

The takeaway from the above is when you look at the startup of the pods. RPM is waiting until flannel is fully in a Running state whereas with the container the service-ca and hostpath go into ContainerCreating before the flannel container is Running. Which is causing us to get the improper IP

On a large rhel 8 system with more resources and patched this doesn't seem to be an issue. I'm going to keep open for tracking purposes but we may not need to do anything

I've just hit this issue on the Jetson board. Good catch @cooktheryan

@mangelajo @oglok it seems like on slower systems the pods enter ContainerCreating once flannel goes into init. I can't seem to locate the check in the code to ensure flannel was running. I wonder if we try to validate readyReplicas is 1?

@cooktheryan I believe this was due to RPMs not being properly re-created and we had a bug for cri-o and rhel8. Can we check if this is still failing on rhel8?

@mangelajo going to close this. I'm thinking we are good


Join example

Do we really want to be encouraging people to do joins this way (massively-wasteful cross), rather than re-indexing files by authorId and bookId? I thought our learning from your recent attempts at doing this for the SQL workload (and as identified in the readme) was that this becomes untenably slow incredibly quickly?


Add methods & code for quantifying degree of change in environment

If the environment is relatively stable we might not expect richness to change much, but if it's shifting a lot then we might expect meaningful shifts. This is a related problem to #253, but is a multivariate change instead of a univariate one. Since we are interested in the environment as it drives richness we should also consider whether we want to weight all environmental factors equally or give more weight to those shown to correlate with richness.

[ ] Decide on quantification approach
[ ] Code it up
[ ] Add to runs

One possibility is to use something like a Mantel test to determine if the environment is generally getting more different from the last year of data.
We should just stick to weighting all environmental variables equally, normalize them all, and use a Euclidean Distance (or some other distance if there's a clearly superior one) to quantify the change.


Add PR Template

Issue Description:
Add a PR template to the repository to make the PR opening process easier for contributors.
Additional Information:
I want to contribute as part of GSSoC'23.
Labels:
[Add appropriate labels to categorize the issue, such as bug, enhancement, documentation, etc.]
documentation

HI could you assign me this issue as i am really good at writing

HI could you assign me this issue


Document Apps #359: Ability to force refresh bindings for app after call

Summary
This PR documents Apps #359: ability to force bindings refresh after a call. It replaces #1179.
The Calls and Bindings pages were updated with new content.

@neflyte sorry if I created coonfusion, but I am assuming this supersedes https://github.com/mattermost/mattermost-developer-documentation/pull/1179? If so, please close the other one. cc @asatkinson we need to streamline the process :)

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!

@asatkinson - This PR has a "do not merge/awaiting release" label. What release is this PR waiting on? Is it possible to merge this PR in now?

Confirmed with @azigler that this PR is waiting for apps framework 1.2 to be merged and deployed into the Marketplace repo https://github.com/mattermost/mattermost-marketplace/pull/331


[AutoPR datafactory/resource-manager] Add exposure control APIs according to the compliance request.

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4958

(message created by the CI based on PR content)


Update live-unit-testing-faq.md

Changed required min version from 1.1.17 to 1.1.11

@morrisjoe,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


helmet added for managing meta tags

Only problem is that I had to remove react strict mode but can't really do anything about that due to helmet not implementing newer safe features.


Development: Move lectures' create, read, update and delete features into the lecture micro service

Checklist
General

[x] I tested all changes and their related features with all corresponding user types on a test server (artemistest6).
[x] I chose a title conforming to the naming conventions for pull requests.

Server

[x] I followed the coding and design guidelines.
[x] I added multiple integration tests (Spring) related to the features (with a high test coverage).
[x] I implemented the changes with a good performance and prevented too many database calls.
[x] I documented the Java code using JavaDoc style.

Client

[x] I followed the coding and design guidelines.

Motivation and Context

This PR is the last that moved features from Artemis to the lecture microservice. It moves features related to CRUD actions on lectures.
Description

Note for code review: LectureService, LectureResource and LectureIntegrationTest are copied from Artemis. They are not implemented by me and I think that their review can be skipped, but if you wish you can review them as well. Excluding those files reduced the changes with ~750 lines.
The client changes are related to the changed app name coming from the Lecture microservice. Since its name is lectureApp, messages starting with artemisApp.lecture.* had to be changed to lectureApp.lecture.*.
Steps for Testing

Prerequisites:

Test server 6: https://artemistest6.ase.in.tum.de/ - it is already deployed there
1 Instructor (artemis_test_user_12 or you can create another instructor account using the server administration)
1 Student (artemis_test_user_1 or you can create another student account using the server administration)

Log in to Artemis
Navigate to Course Management
Open/Create a course (the course should be deleted in the last steps) and create a lecture => lecture should be successfully created
Edit the lecture => the lecture should be successfully updated
Add attachments and 1-2 lecture units to the lecture (1 of them should be an exercise) => should work fine
Navigate to course overview and the lecture you created => the lecture should be there including the units and the attachments you added
Navigate to Course Management and delete the exercise that was linked to the lecture
Open the lecture and check that the exercise is removed from the lecture units list
Delete a lecture => the lecture should be successfully deleted

Review Progress

Code Review

[ ] Review 1
[ ] Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Test Coverage

Screenshots

Thanks @b-fein for the review. I tried to apply all your comments. Would be great if you can re-review


Port int16 support to Mean kernel

@advaitjain this PR ports int16 support to the Mean kernel.
BUG=Fixes #239

@advaitjain ready for review

apologies for the delay. I will review and respond tomorrow.

@advaitjain The old tests cover the first two code paths
if (params->keep_dims && special_case_4d_axes_1_and_2) {

and
} else if (op_data->input_zp == op_data->output_zp &&
                 op_data->input_scale == op_data->output_scale) {

I added an additional test to cover the else clause.


Add environment variables to helm chart deployment object

User Story
As an operator I would like to add proxy settings to the controller to access github in order to download the components.yaml file.
Detailed Description
When we bring up the controller, it tries to download files from Github which has to go through proxy. User should be able to set http_proxy as an environment variable in the values.yaml files when installing via helm.
It should be as easy as adding the following after this line https://github.com/kubernetes-sigs/cluster-api-operator/blob/main/hack/charts/cluster-api-operator/templates/deployment.yaml#L93
          env:
            {{- if .Values.env }}
            {{- toYaml .Values.env | nindent 12 }}
            {{- end }}

Then update the values.yaml user can include
env:
  - name: http_proxy
    value: http://myproxy.com:1234

Anything else you would like to add:
/kind feature

/triage accepted


Bug in argument check (metrics)

Hi guys,
thanks for the awesome work.
While using it, the line below throws an error, when metrics is specified.
https://github.com/automl/jahs_bench_201/blob/e9a93ade6cd80028b45d46e15de2cd96574a9662/jahs_bench/api.py#L108
I think it should be
unknown = metrics - set(self.__known_metrics)

instead.
Cheers, Philipp

You're right :) I erroneously made this change before but the merged PR should fix it :)


The new match finding algorithm is slow

The new match finding algorithm dominates all the time of entire process for some types of passwords.

Fixed in commit: 3b81c157744f62840515bd1216026202a5c6f6d4


Inline custom afl_maybe_log() on x86_64

Similar to #11 but inlining the implementation in every block. (Probably not a good idea, but worth trying.)

I gave this a shot and unfortunately it performs slower than #11 in all cases :sweat_smile:. Going to close this so I can focus on the other implementation as well as prefetching.

I gave this a shot and unfortunately it performs slower than #11 in all cases :sweat_smile:. Going to close this so I can focus on the other implementation as well as prefetching.

Yay, was hoping this one would be the slowest, as it's also the most memory-hungry approach 😄

Yay, was hoping this one would be the slowest, as it's also the most memory-hungry approach 😄


Typo in comment in add_noise function for PointModel class?

Should noise_to_signal_ratio defined as "X_rms/S_rms" be squared in the comment in line 193 in point_model.py such that
"noise_to_signal_ratio: float, defined as (X_rms/S_rms)**2 where X is noise and S is signal." ?
At the moment, the documentation says that the input parameter noise_to_signal_ratio = sqrt(epsilon) if I understand it correctly.

From @gregordecristoforo in 7b808086.


Create LICENSE

This project does not have any explicit license specified. I have added the Apache License 2.0 as an example, since that is the license ActiveMQ itself uses.
Adding an explicit open-source license would be beneficial for the users of the project.

@n0ha Thanks for your Pull Request! I like the MIT license more in general, or is there something that would speak against it? As this is only a Dockerfile, there is no need to copy the ActiveMQ license.

@n0ha Thanks! Merging this now.


Implement missing write your epilogue move

Hi,
this implements a missing move: Write your epilogue. Tested and works fine

Looks good.


New command: flow run cancel

Usage
flow run cancel
Description
Cancels a specific flow run for the specified Microsoft Flow
Options

Option
Description

-n, --name<name>
The name of the run to cancel

-f, --flow<flow>
The name of the Microsoft Flow to cancel

-e, --environment<environment>
The name of the environment where the Flow is located

--confirm
Don't prompt for confirmation

Additional Information
Use Fidler or Postman and disable a flow in the UI to see the exact post request. Will be a Post request tot the following url:
https://emea.api.flow.microsoft.com/providers/Microsoft.ProcessSimple/environments/{{environement}}/flows/{{flowid}}/runs/{{runid}}/cancel?api-version=2016-11-01.

If I look at the REST API call, it refers to run ID rather than run name. Should we rename -n, --name to -i, --runId?

Good point; I tried to be consistent with the flow run get: https://pnp.github.io/cli-microsoft365/cmd/flow/run/run-get/.

Gotcha! In that case, let's stay with the current spec 👍

Let me take a shot a this.

Awesome! Thanks for your help @Abderahman88 its all yours 👍🏻
You can find our contribution guides in the wiki
Don't hesitate to reach out if you need any assistance.

No problem @garrytrinder. Happy to help.
After this one, I will do #1871

Does the runId has some kind of pattern to check if it's valid?

Something that I found that seems to me pretty odd.

Run ID exists and it's correct --> I get response 200 (what is expected - last part of Run ID = 4637979CU165)

Run ID is completely wrong --> I get response 404 (what is expected - last part of Run ID = 4638009ZZ999)
The error says that the resource is not found.

Run ID is partially wrong --> I get response 200 (is odd - last part of Run ID = 4637979ZZ999)
I find this very strange, because the run does not exist in my environment.

It seems like the 5 last characters of the RUN ID are not taken into account to check if the run exists or not.
Any explanation for this?

I don't know how exactly the run ID is composed, so for now, I'd suggest we skip any validation of it.

Great investigation on the status codes @Abderahman88 from experience with working with this endpoint in the past, there are some status codes returned that you certainly would not expect. See https://github.com/pnp/cli-microsoft365/issues/1063#issuecomment-535977685 as an example.
We could query this with the Azure support and see what they suggest?


Support server <> server replication

See draft spec: https://github.com/verida/VIPs/blob/develop/VIPs/vip-6.md#research-next-steps
First step is to research the technical details and confirm assumptions are correct: https://github.com/verida/VIPs/blob/develop/VIPs/vip-6.md#research-next-steps

Research next steps
Confirm the role based data access assumptions are correct
Open Fauxton on database A (dev1):

[x] Create a user with the role test-replicater (password123)
[x] Create a test database test-replication-database
[x] Create security entry in the test database granting test-replicater role access as a member
[x] Create a validate_doc_update() entry that allows test-replicater role to write

{
  "_id": "_design/only_permit_write_users",
  "validate_doc_update": "\n    function(newDoc, oldDoc, userCtx, secObj) {\n        if ([\"v6c116e6212a63f80eedc231d6b9e2473f7e07e15ee2959b0ce6f22ee76742c41\"].indexOf(userCtx.name) == -1 && userCtx.roles.indexOf('test-replicater') == -1) throw({ unauthorized: 'User is not permitted to write to database' });\n}"
}

Note: The addition to the normal code is  && userCtx.roles.indexOf('test-replicater') == -1

[x] Login to Fauxton with user test-replicater and confirm it can read and write the test-replication-database.
[ ] Create a JWT auth token for user test-replicater and confirm it can read and write the test-replication-database.

Confirm push replication works as expected
Open Fauxton on database B (dev2):

[x] Create a user with the role test-replicater
[x] Create a JWT auth token for the user that never expires

Open Fauxton on database A (dev1):

[ ] Create a replication entry in database A that replicates to database B and configure it to authenticate with the JWT auth token

{
    "_id": "serverA-replication-",
    "source": "http://myserver.com/foo",
    "target": {
        "url": "http://localhost:5984/bar",
        "auth": {
            "basic": {
                "username": "user",
                "password": "pass"
            }
        }
    },
    "create_target":  true,
    "continuous": true
}

[ ] Create a new record on database A

Open Fauxton on database B (dev2):

Verify the new record was created
Verify the validate_doc_update() entry has been replicated
Verify the _security entry has been replicated and includes the role test-replicater as a member

Test pad
curl -H "Host: acacia-dev1.tn.verida.tech:5984"
-H "accept: application/json, text/plain, /"
-H "authorization: Bearer "
"https://acacia-dev2.tn.verida.tech/_session"
curl -H "Host: acacia-dev1.tn.verida.tech:5984"
-H "accept: application/json, text/plain, /"
-H "authorization: Bearer "
"https://acacia-dev1.tn.verida.tech/test-replication-database/_all_docs?include_docs=true"

Testing has proven that Auth JWT's can not be used for authentication between storage nodes. The spec has been updated to reflect this (use username/password instead).

Implementation tasks:
The following high level changes need to be made to the Storage Node and Client SDK.
Storage node
Endpoints:

[ ] /auth/replicationCreds - Generate credentials for replicating storage nodes
[ ] /user/checkReplication - Confirm replication is configured correctly for; all databases OR a single database

Other changes:

[ ] components/dbManager/configurePermissions write function needs to check userCtx.roles includes the role ${contextHash}-replicator
[ ] components/dbManager/configurePermissions security doc needs to add the role ${contextHash}-replicator in the members list
[ ] Refactor the storage of databases in a context to have their own database so they can be syncronized via CouchDB replication

Client SDK

[ ] Call checkReplication() when opening a context to ensure the replication is working as expected.
[ ] Don't start using a new node until it is fully syncronized? (need to check /status)
[ ] Open a connection to a random (active) endpoint, rather than all the endpoints


further chunk the repartition writing; switch to .compute()

This helps enable running the repartitioning command on large datasets by allowing for chunking by filter and tract.  Also improves overall performance significantly on large datasets by computing the active dataset rather than keeping it on disk with dask.

@timothydmorton it looks like you merged @brendancol pr #172 into this? Is that correct.

OK, this is now cleaned up and rebased on the black-formatting PR, and includes #172.

Will be superseded.


os exit codes

Thank you for this tool!
I am running it as a Kubernetes job and noticed that medusa export ... always returns an exit code of 0.
I wanted to know if you're open for a pull request to make sure all errors are returned back to main.go and change main.go to:
	err := cmd.Execute()
	if err != nil {
		fmt.Println(err)
		os.Exit(1)
	}

Or use log.Fatal/log.Fatalf where appropriate ?
let me know which approach makes sense and I'll open a PR.

Sure, that would be great if you can help implementing this.
Thank you for your feedback and contribution!

Thank you so much for your contribution. I have merged the your pull request. Improving the error handling was much needed.
Please do not hesitate to create issues if you experience any errors while using Medusa.


fix extraneous colon in test jamfile causing a build warning

jking@ubuntu:~/boost/libs/algorithm/test$ ../../../b2 -q
Jamfile.v2:19: Unescaped special character in argument algorithm:

Why the quoting?  (I don't have any problem with removing the colons)

There is no standard for this, just using what I've seen in libraries I have been in the most.  Examples with and without quotes are abundant.

Changed it to what you were looking for.


Don't depend on a specific NUnit version

@Jetski5822 says you can add something to the csproj file

meh


feat(linter): handle cjs module.exports.foo = bar and exports.foo = bar

Current dependencies on/for this PR:

#2492  👈
main

This stack of pull requests is managed by Graphite.

Merge activity

Feb 24, 10:54 AM EST: @Boshen merged this pull request with Graphite.


added range macros

I added some macros for generating sequences of numbers at compile-time.
One of them is an extended mfor (see #125) and useful to generate loops over fixed-size types.
If macros can dispatch on arrays  (#104), this way a generic macro for iterating over arrays can be written (which makes it easier to iterate over fixed-size types in general, since they mostly use array as data)
Examples of usage of in-range can be found in my linear-algebra lib (#146)

Thanks for this.  It's being merged for range and range-fn: in-range will be removed, and a new mfor added that uses eval-macro-call on its list argument.


List of genres (categories) on iTunes/the App Store

We need a list of all the possible categories (Apple internally calls them "genres") on the App Store.

This one's easy: https://itunes.apple.com/WebObjects/MZStoreServices.woa/ws/genres has a full list.
We are interested in first-level category 36 (App Store). The grab a list of all second-level subcategories (there are also third-level categories but only for "Games", "Magazines & Newspapers", "Stickers") :
const genreJson = await fetch('https://itunes.apple.com/WebObjects/MZStoreServices.woa/ws/genres').then((r) =>
    r.json()
);

const appsGenres = genreJson[36];
if (appsGenres.name !== 'App Store') throw new Error('Unexpected API response.');

const subgenres = Object.values(appsGenres.subgenres).reduce((acc, cur) => ({ ...acc, [cur.name]: +cur.id }), {});
subgenres.all = 36;
console.log(subgenres);

That yields:
{
  "Business": 6000,
  "Weather": 6001,
  "Utilities": 6002,
  "Travel": 6003,
  "Sports": 6004,
  "Social Networking": 6005,
  "Reference": 6006,
  "Productivity": 6007,
  "Photo & Video": 6008,
  "News": 6009,
  "Navigation": 6010,
  "Music": 6011,
  "Lifestyle": 6012,
  "Health & Fitness": 6013,
  "Games": 6014,
  "Finance": 6015,
  "Entertainment": 6016,
  "Education": 6017,
  "Books": 6018,
  "Medical": 6020,
  "Magazines & Newspapers": 6021,
  "Catalogs": 6022,
  "Food & Drink": 6023,
  "Shopping": 6024,
  "Stickers": 6025,
  "Developer Tools": 6026,
  "Graphics & Design": 6027,
  "all": 36
}


Is it possible to get full GPS information at "high" frequency from the build in GPS of the modem?

From our discussion of today; would be possibly useful for generating test data for designing / testing custom 6dof + GPS Kalman filters:

is it possible to get lat, lon, timestamp, velocity, heading, quality indications from the GPS (are there even more quantities we may be interesed in?)
at as high frequency as possible; what kind of frequency is possible with the GPS on the modem? 1hz, 2.5hz, 5hz, 10hz, 25hz, 50hz are common values

Velocity and sensitivity is available

yippi :) .

We should try to get the GPS datasheet (exact GPS chip?) to be able to check specs.
May want to use for "true real value" a GPS RTK "in addition" if possible, if close to the coast, and RTK signal is available, accuracy is around 1cm.

(with RTK 1cm is absolute accuracy, wonder if relative accuracy may be even higher (since normal gps has typically 2.5-5m absolute accuracy, but relative accuracy may already there be much better).

Another way to test against ground truth is to use a wheel like Jim et co, but dataset of field data would still be useful anyways:)