memoryDriver not working

I tried the localforage-memoryStorageDriver on it's own using the example in the README.md as a base and it doesnt seem to work at all. If I swap it for the inbuilt drivers localforage.INDEXEDDB for example it works fine or do not specify the driver it uses the default drivers.
Can someone provide a fix or a working example?

Hi @abarke
I'll try to take a look at what the problem is using the localforage-memoryStorageDriver. Did you see any particular error or was it just failing silently?
Cheers

Thanks @RasCarlito it was failing silently.

Thanks for the info!
Can you tell me what version of localforage and localforage-memoryStorageDriver you are using?

axios-cache-adapter 2.1.1
localforage 1.7.2
localforage-memoryStorageDriver 0.9.2

Hey @abarke ! I added a unit test to make sure it is continually tested.
I was able to make it work like this:
import axios from 'axios'
import { setup } from 'axios-cache-adapter'

import localforage from 'localforage'
import memoryDriver from 'localforage-memoryStorageDriver'

async function exec () {
  // Define the memory driver in localforage
  await localforage.defineDriver(memoryDriver)

  // Create a localforage instance forcing the memory driver
  const store = localforage.createInstance({
    driver: memoryDriver._driver
  })

  // Create an axios instance with the cache adapter passing the created store
  const api = setup({
    cache: { store }
  })

  // Then just use the axios instance as you normally would
  const response = await api({
    method: 'get',
    url: 'https://httpbin.org/get'
  })

  console.log(response.status) // > 200

  // Get stored data from localforage directly
  const { data } = await store.getItem('https://httpbin.org/get')

  console.log(data.status) // > 200
}

Tell me if this works for you 😃

Yes it was missing. I think the way the memory driver integrates with localforage changed at some point 😅

Hi @abarke, just checking in with you if the localforage memory driver integration worked alright with you so that I can close this issue.
Thank you in advance for getting back to me 😄

Sorry I didn’t manage to test it. I will have a look tonight. Thanks.
From: Carl Ogren<EMAIL_ADDRESS>Sent: Mittwoch, 19. Dezember 2018 11:09
To: RasCarlito/axios-cache-adapter<EMAIL_ADDRESS>Cc: Alex Barker<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [RasCarlito/axios-cache-adapter] memoryDriver not working (#39)
Hi @abarkehttps://github.com/abarke, just checking in with you if the localforage memory driver integration worked alright with you so that I can close this issue.
Thank you in advance for getting back to me 😄
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/RasCarlito/axios-cache-adapter/issues/39#issuecomment-448540185, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AhG3lZd0AnRBYD77EE-07E3gKPx8LgwEks5u6hA-gaJpZM4XKPns.


Added ability use the dependency as a framework so it works with Carthage.

This does not impact Cocoapods at all, but adds support for Carthage by adding a framework target that has its scheme shared. @nairteashop can you merge this sometime soon so I, and others, can point to you main repo rather than a fork?

Thanks, @antonino-u. Merged.


conflict with your requirements or minimum-stability.

Hi,
The issue is when i am running this command  "php composer.phar install" after installing composer.
Terminal is throwing error:
Problem 1
- The requested package toorop/ovh-sdk-php 0.1.0 is satisfiable by toorop/ovh-sdk-php[0.1.0] but these conflict with your requirements or minimum-stability.I am doing this on ubuntu terminal.
So cannot be able to find the issue. If anybody could help me.
Thanks

I have resolved the same using this:
ADD this:
minimum-stability: dev, prefer-stable: true
and comment out
"toorop/ovh-sdk-php": "dev-master",
This thing worked for me. You guys can try as well.
Regards


Update balance UI

Updates the balance text a bit to more closely resemble the screens in Figma and the Bitcoin Design guidelines on units and symbols and on protecting a wallet.
Basically, I turned on some font features according to the Figma designs and added a better symbol for when the balance is hidden.
It's not perfect yet, I also want to add:

The possibility to cycle through states (BTC, sats, hidden) by clicking on a balance. For that we need some global state and I didn't want to touch that quite yet.
Formatting based on the user’s locale. Currently I hardcoded the BTC symbol to be prefixed to the number (as it is done in the U.S. with USD amounts. However, I didn't know what to do with the sats symbol as it looked strange when prefixed to a number so I kept it as a postfix. Open for suggestions on this one!

For a first version it should be fine though. Let me know what you think!
Not sure how we want to organize custom CSS going forward. I used a CSS Module but am open to do it differently or just add everything to index.css for now.
📸

See also https://github.com/joinmarket-webui/joinmarket-webui/issues/19.

Wonderful!
Regarding the sat symbol: so far most interfaces still use "sat" or "sats," i.e. no symbol at all. Thunderhub—which looks quite neat in general I have to say—uses the sat symbol, and simply puts it at the end using a slightly dimmer font color:

Most other interfaces, including bitcoin and lightning wallets, simply use "sat" or "sats" either before or after the number (usually after).
1ML:

LightningNetwork.plus:

Updated to use the sat symbol (resolves #19).
The bitcoin design guidelines don't really use a specific sat symbol so maybe we should let the user pick if they want a symbol or just "sat(s)" in the upcoming settings page. Maybe @GBKS has some input on that? For now, I'd say let's keep it simple and just go with the symbol.
I also added digit groups using Intl.NumberFormat as suggested by the design guides. For now I hardcoded the formatting to the en-US locale but we could do more location specific things in the future.
Regarding browser compatibility of Intl.NumberFormat: It should be available on all somewhat modern browsers. Does someone have any experience with that? And a more broad question: What browser compatibility are we targeting in general?

Great! Let's keep it as is for now. We can do some polishing for v4 later on, I'm sure we can improve things here and there. Different font color for the symbol would also be easier on the eyes, for example.


OADP-2770:  Mongodb e2e datamover with block mode

E2E test case for the block mode.
The concept is to use PVC which is a type of volumeMode: Block. This PVC is used by the mongodb container to be used in:

initContainers
That container is responsible of using the PV as a block volumeDevice. It first creates filesystem on that device and then checks if it can be mounted. For debug information it also creates a flat file with EPOCH timestamp inside.
We use init container mongo, which has the mkfs.ext4 CLI in it. UBI image is missing that CLI. We use mongo image so we don't download to the cluster multiple different images to create deployment.

containers
That container has also the volumeDevice available, so first thing it do is to use previously formatted block device and mounts it to a given path. That path is then used by docker-entrypoint.sh to initialize mongo database and use it as persistent volume.

Above method allows to create an application with block device and use it for backup and restore. Once the application is restored it will contain files from the filesystem on the block device.
Such patter can be used across other test cases.
To deploy sample application:
 $ oc create ns mongo-persistent
 $ oc apply -f pvc/default_sc-block-mode.yaml
 $ oc apply -f mongo-persistent-block.yaml

/retest

/retest

/retest

/retest

/retest

/test 4.13-operator-e2e-aws

[x] deployed the block mongo app standalone on my cluster
[x] confirmed the volumeMode is block
[x] reviewing CI logs https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_oadp-operator/1193/pull-ci-openshift-oadp-operator-master-4.13-operator-e2e-aws/1717841677239980032/artifacts/operator-e2e-aws/e2e/build-log.txt
[x] :/ velero logs are cut off but ok.. https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_oadp-operator/1193/pull-ci-openshift-oadp-operator-master-4.13-operator-e2e-aws/1717841677239980032/artifacts/operator-e2e-aws/e2e/artifacts/mongo-datamover-e2e/must-gather/quay-io-konveyor-oadp-must-gather-sha256-17c270de0bed794ec43a7108b646e70e199c08b37e49a663e4f1e43cde587c55/must-gather/clusters/3e44be7b/namespaces/openshift-adp/logs/velero-66c5dfd4f4-8hrk5/current.log
[x] executed a manual b/r of mongo-persistent    w/ data validation ++

VERY WELL DONE!!  nice easy way to just add the block mode test in :)   During the manual test I saw the db pod take a while to start, but it's to be expected.


[All] Resing the window flush the inputs and result

Describe the bug
When resizing the window, all values (inputs and result) are cleared, even the selected Unit for converters.
Steps To Reproduce
Steps to reproduce the behavior:

Goto any converter
Hit 1
Resize the window

Expected behavior
Not cleared

This issue is no longer occurred on latest WASM build.
Version: 0.1.0-uno.1+486


Multiple HOCs using React.ElementConfig breaks type checking of prop types

A simple HOC works once, but if the HOC is used again, type checking is breaks.
Try Flow
import * as React from "react";

class MyComponent extends React.Component<{foo: number}> {};

declare var make: <T>(T) => React.ComponentType<React.ElementConfig<T>>;

var One = make(MyComponent);
var Two = make(One);

<One foo="should_error" />;

// Does not error
<Two foo="should_error" />;

Now both error


No Matches break the ITS and rbcl ID Engine atm

Wrong number of columns passed to the id engine code for ITS and rbcl, will fix soon

Fixed with boldigger2.


maybe this?

The export_plink docs say that it accepts a Locus, or any Struct that implements a contig + position. This change (untested) takes the MT, creates a new version of locus without the chr prefix, uses that as a key, then export_plink is called.
Not sure if a similar trick is possible with a VCF export - I doubt it, that would mean a VCF is written where the 'contigs' in the variant rows don't match anything in the headers

@MattWellie is it ok to close this PR?


Add DVV-checks for Talpa rights of purchase

Description
Compare permit address with DVV primary and other addresses and only allow continuing when addresses match.
Compare attributes street_name, street_number, apartment, city and postal_code.
Update Talpa rights of purchase tests and add new tests for address comparison.
Context
PV-845
How Has This Been Tested?
Through updated unit tests.
Manual Testing Instructions for Reviewers
This is better to test with Talpa explicitly also.

LGTM!


tooltip is not working for img tag

Doing like that you will not see tooltip on mouse hover.

It works only for link tags like that

But documentation says you can use it on any tag

Hi! I was with the same error, and I tried to encapsulate the element that you want to show a tooltip with a div element with the properties that need like that:
React component:
import React from 'react';

export function Tooltip({ position, label, children, ...props }) {
  return (

      {children}

  );
}

Thanks!


perf(core): use JSON.stringify for comparing object in expressionProperties.

What kind of change does this PR introduce? feature

This change is

Codecov Report

Merging #725 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #725      +/-   ##
==========================================
+ Coverage    94.2%   94.22%   +0.01%
==========================================
  Files          17       17
  Lines         777      779       +2
  Branches      224      226       +2
==========================================
+ Hits          732      734       +2
  Misses         45       45

Impacted Files
Coverage Δ

src/core/src/services/formly.form.expression.ts
95.29% <100%> (+0.11%)
: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 fc3f935...2211ee8. Read the comment docs.


PUT a file with rustls seems broken

I have a https server using actix-web and rustls on the receiving side where I can upload files using a PUT request. That is tested using multiple clients like curl and others. It seems to work just fine. The URL is a regular https://host:port/ url, so there is nothing special there. I have double checked that it is using "https://" (and this is further validated by the fact that it works with native-tls).
I then have a client application using reqwest to upload a file to the said server, and I initially just used the default features and everything worked fine. I then disabled the default features and enabled rustls.
reqwest = { version = "0.11.13", features = ["rustls-tls", "stream"], default-features=false }
And suddenly things fail, getting TLS errors on the receiving side like
2023-03-16T12:57:59.710+01:00 ERROR actix-rt|system:0|arbiter:0/140378614589184 [rustls::conn+1327] TLS alert received: AlertMessagePayload {               ┤
    level: Fatal,                                                                                ┤
    description: BadCertificate,                                                                                ┤
}

The client side error is send failed because receiver is gone, so the server just kills the connection due to the error above.
If I just revert Cargo.toml back to
reqwest = { version = "0.11.13", features = ["stream"] }
things work again.
The code in question is
                let client = reqwest::Client::new();
                let body = Body::wrap_stream(rx);
                let mut request = client.put(dest_url).body(body);
                if let Some(user) = username {
                    request = request.basic_auth(user, password);
                }
                let res = request.send().await?;

My issue is resolved by reverting back to native tls (even though I would prefer rustls), but I thought this might be something you would like to look at.

Looks like it's a certificate issue. You could look at the other feature, rustls-tls-native-roots, which will look for the certificates on your machine like native-tls does.

But I'm not using any client certificate.

Sorry, I meant it will load certificate chains. It uses those to determine what Certificate Authorities to trust, which signed the certificate your server uses.

Are you configuring the server to use a self-signed certificate? That might explain what's going on.

I realize I had forgotten about this issue. Thanks for the feedback, I will have another go and investigate the certificate chains.

Not able to reproduce exactly, but it looks like it was the native roots that got me. Closing


Ranges support

Please provide way to use ip addresses with ranges.
ip1 = IPAddress('<IP_ADDRESS>')
ip2 = IPAddress('<IP_ADDRESS>')

ip = IPAddress('<IP_ADDRESS>')

(ip1..ip2).include? ip

It looks like IPAddress::IPv4 just needs succ defined (self + 1 will work), but for this use case Range#cover? would be a lot faster and already works on 0.8.0.
ip1 = IPAddress('<IP_ADDRESS>')
ip2 = IPAddress('<IP_ADDRESS>')

ip = IPAddress('<IP_ADDRESS>')
outside = IPAddress('<IP_ADDRESS>')

(ip1..ip2).cover?(ip) # => true
(ip1..ip2).cover?(outside) # => false

@bjmllr see PR#27. Adding #succ is worst way possible, since IP-addresses are actually 32-bit/128-bit integers, and Ruby can work in appropriate way with range of integers, you just need to add #to_int methods.


Use Trusted task terminology

Reference: EC-390

Make note of the second commit:
Mass renaming of *acceptable to *trusted
Attention: this also changes rule short codes, which I think for these
rules should be okay.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (0128fcc) to head (0ae90b8).
Report is 17 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #945   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          101       101
  Lines         4812      4812
=========================================
  Hits          4812      4812

Files
Coverage Δ

policy/pipeline/required_tasks.rego
100.00% <100.00%> (ø)

policy/pipeline/task_bundle.rego
100.00% <ø> (ø)

policy/pipeline/task_bundle_test.rego
100.00% <100.00%> (ø)

policy/release/attestation_task_bundle.rego
100.00% <ø> (ø)

policy/release/attestation_task_bundle_test.rego
100.00% <100.00%> (ø)

policy/release/base_image_registries.rego
100.00% <ø> (ø)

policy/release/base_image_registries_test.rego
100.00% <100.00%> (ø)

policy/release/lib/attestations_test.rego
100.00% <100.00%> (ø)

policy/release/tasks.rego
100.00% <ø> (ø)

policy/release/tasks_test.rego
100.00% <100.00%> (ø)

Tracking rollout, there was an issue in the pipeline, just making sure the change has been deployed

Validated in audit logs the new policy was applied.


Add support VPC Constellation Alpha Prime right

This repo is closing in favour of a successor repo https://github.com/brammmers/edrefcard2
If this is still an issue, please re-open it there.
Thank you!


Include s from Helmet in SSR output.

This seems to have been an oversight, unless there is something I'm missing.

Thanks @klarstrup. I'm making improvements in the next release per #101, including more idiomatic <head> tags (i.e. using components instead of an object definition), and adding missing html/body attributes, link, style, script and noscript, so I'll go ahead and close this.


Move Build onto the injection-gen based controller infrastructure.

I've broken this into finer grained commits as a sort guide for migration.  I can try to take a crack at doing something along these lines for tekton as well, but the goal of the broader refactoring was to effectively eliminate boilerplate outside of pkg/reconciler/foo for writing controllers, and keep our various controllers from drifting apart as we add features (e.g. this gives Build various metrics integrations including stackdriver that I believe it lacked previously).
This also enables us to pretty trivially consolidate controllers, or split them apart by simply changing what goes into the main binary.
/hold
cc @bobcatfish @vdemeester @n3wscott

@mattmoor nice ! I'll look into that for tekton :angel:

@vdemeester let me of @n3wscott know if you run into any trouble :)

/hold cancel


inconsistent document between README.md and docs.microsoft.com

The example of Specifying a user assigned managed identity with the DefaultAzureCredential should mention that the id can also be specified as env var of AZURE_CLIENT_ID.
See document on the code repo:
https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/identity/Azure.Identity/README.md#specifying-a-user-assigned-managed-identity-with-the-defaultazurecredential

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4f73df56-2312-5851-7b59-3dfb766e5f66
Version Independent ID: 31be349e-063e-6696-bc5f-752c413fa079
Content: Azure Identity client library for .NET - Azure for .NET Developers
Content Source: api/overview/azure/identity-readme.md
Service: identity
Product: azure
Technology: azure
GitHub Login: @maggiepint
Microsoft Alias: magpint

Thank you for your feedback.  Tagging and routing to the team members best able to assist.

Hi @herohua Thanks for the feedback. Could you clarify which section of the document is missing the statement about AZURE_CLIENT_ID? It appears that the one in your example has the text at the bottom.


When to release codes?

Wonderful job!!!I'd like to ask when you release codes and models?Thanks a lot.

Thank you so much for your interest and support. I am currently busy with other submissions. I will release the code as soon as possible. Again, thank you for your patience and understanding!

Thanks for your reply.And how about your synthetic face dataset.

Thanks for your reply.And how about your synthetic face dataset.

Certainly, the synthetic facial expression dataset will be released. Just a few days.

@wang-zidu Hey, any updates on this?

Thank you for your interest and patience. The initial release version is scheduled to be open-sourced no later than May 26th, and I'm working towards this goal.

练代码的实现。您有计划分享训练代码吗？

您有计划分享训练代码吗？

您有计划分享训练代码吗？

建议不要等，大概率不会开源的，而且自己复现其实也不难

您有计划分享训练代码吗？

建议不要等，大概率不会开源，而且自己复现其实也不难

我看你之前也想复现，  你复现成功了吗老哥

且自己复现其实也不难

有偿指导一下


Creating a new folder in open dialog needs a manual refresh (like F5) to show up

VSCode Version: 1.9.1
OS Version: Windows 10 (Version 1511, Build 10586.545)

Steps to Reproduce:

Open VS Code.
From File menu, select "Open File" (or "Open Folder", or "Save As").
Try to create a new folder by clicking "New Folder".
The new folder does not show up.
Press F5 to refresh.
The new folder shows up.
Now, try to rename the folder.
When you hit enter after renaming the folder, it still shows as "New Folder".
Hit F5.
Now, it shows as the renamed folder.

It may be a bug in the common library being used for development for Microsoft products. I verified using Firefox and Notepad. In Firefox, the behavior is alright. I can create new folder and rename it without having to refresh. But, in Notepad, the above mentioned issue is present.
Probably, the developers/maintainers of this project know best where to forward this issue in case it needs to be fixed by some other team at Microsoft.
Thanks.

The issue is not related to VS Code since you can reproduce it in notepad.
However I am not sure where to best file Windows 10 bugs - I would try to us the windows feedback application.


 I suspect bad usage of  aemInstall instead of aemEmbed + exportPackage directive.

Please report only issues if you are sure that the problem is with plugin itself. If you will be totally blocked please report an issue but with much more details. To be honest I am not able to help everybody starting using the plugin. I am trying to iteratively updating the docs but I cannot help everybody with each specific scenario. I have no profits from that and this is just my good will to help... But I have limited time and power 😉


Use reselect to create selectors

We should use reselect for creating selectors in the redux-store package. redux-toolkit exposes an createSelector method that is re-exported from reselect. The main benefit is memoization

Yes!


Add health check endpoint (laravel#190)

New /health_check endpoint will be available when Reverb server is running, that will response with {"health":"OK"} to support k8s HTTP health checks required by some cloud provider Load Balancers (i.e. GCP)

Is there a reason not to make it /up like a normal Laravel health check endpoint?

Is there a reason not to make it /up like a normal Laravel health check endpoint?

Updated route to /up

It was released yesterday: https://github.com/laravel/reverb/compare/v1.0.0-beta10...v1.0.0-beta11


Improvement for k8s.io/docs/concepts/scheduling-eviction/assign-pod-node/

It may be useful to make in bold the fact that pod affinity is namespaced, and maybe also include namespace in the examples

Hi , i would like to work on this issue

/assign @himanshu007-creator

/triage accepted
/language en
/kind feature

Can you pinpoint the lines that needs changes?
Thanks


Make contents of __init__.py equal across projects

Changes
See https://github.com/databricks/databricks-sdk-py/issues/343#issuecomment-1866029118.
Corresponding PR for the Python SDK: https://github.com/databricks/databricks-sdk-py/pull/488.
Tests
Unit test to confirm the SHA1 of the file contents.

Thanks! Then this is ready to merge. Could you click the merge button? (I don't have write access)


Equipmentbox astrometry-data - text goes outside the box

After solving the css problems with Jetpack / Photen the equipmentbox looks a little bit strange on certain browser sizes: it is too small.  This will vanish, when using a big screen or the browser will be very small (responsive design).

Cheers
Axel

Suggestion:

generally switch to 2 column design
make the skyplot bigger
size of the font within the astrometry-data can be reduced by custom css

Suggestion:

generally switch to 2 column design
make the skyplot bigger
size of the font within the astrometry-data can be reduced by custom css

I will look at it (dealing with themes is so tiresome)

I will look at it (dealing with themes is so tiresome)

Hi Matt, you don't have to: I am doing this, because this is my task using T.Joy. Thanks for your time.
I am posting my solution here.

Hi Matt, you don't have to: I am doing this, because this is my task using T.Joy. Thanks for your time.
I am posting my solution here.

I am now totally satisfied with the solution I found. I also added some changes to the css for

problem of thread solved

bigger skyplot

2 columns layout with smaller font

problem found in astrometry.editor.css

No relative values min-height/width:

nano astrometry.css
.skyplot div {
  min-height: 100%;
  min-width: 100%;
}

/* bigger skyplot image */
.skyplot img {
  width: 100%!important;
}

/* relation between skyplot and data - optional */
.astrometry-image-data {
  grid-template-columns: 1.5fr 2fr;
}

/* Two column layout with less grid gab and smaller font- optional */
.astrometry-data {
   grid-template-columns: 1fr 2fr 0fr 0fr;
  grid-gap: 0.5rem;
  font-size: 1.4rem;
}

.astrometry-data > .col3 {
  grid-column: 1;
}
.astrometry-data > .col4 {
  grid-column: 2;
  white-space: nowrap;
}

Other things:

Black background in the editor for astrometry data. Add at the end:

nano astrometry.editor.css
.astrometry-image-data {
    background: rgb(220,220,220)!important;
}

Thanks Matt

I am now totally satisfied with the solution I found. I also added some changes to the css for

problem of thread solved

bigger skyplot

2 columns layout with smaller font

problem found in astrometry.editor.css

No relative values min-height/width:

nano astrometry.css
.skyplot div {
  min-height: 100%;
  min-width: 100%;
}

/* bigger skyplot image */
.skyplot img {
  width: 100%!important;
}

/* relation between skyplot and data - optional */
.astrometry-image-data {
  grid-template-columns: 1.5fr 2fr;
}

/* Two column layout with less grid gab and smaller font- optional */
.astrometry-data {
   grid-template-columns: 1fr 2fr 0fr 0fr;
  grid-gap: 0.5rem;
  font-size: 1.4rem;
}

.astrometry-data > .col3 {
  grid-column: 1;
}
.astrometry-data > .col4 {
  grid-column: 2;
  white-space: nowrap;
}

Other things:

Black background in the editor for astrometry data. Add at the end:

nano astrometry.editor.css
.astrometry-image-data {
    background: rgb(220,220,220)!important;
}

Thanks Matt

Remember adding your CSS to the theme customizer, since it is a theme dependant change and to not overwrite it, if you update the plugin.

Remember adding your CSS to the theme customizer, since it is a theme dependant change and to not overwrite it, if you update the plugin.

Thanks Matt - perfect match.
P.S. just for completness and our theme specific changes (T.Joy).
Unfortunately it was not possible - at least for my theme T.Joy to add custom CSS for the bock editor. For now, I therefore had to make to following changes to get the same results according to the theme layout in the Gutenberg-Editor.
Like Matt said: this should be in a custom theme css and NOT alter the plugin css file.
nano astrometry.editor.css

.astrometry-image-data .equipment {
     background: rgb(255,255,255);
}

.astrometry-image-data {
    background: rgb(220,220,220)!important;
}

/* bigger skyplot image */
.skyplot img {
  width: 50%!important;
}

.skyplot div {
  min-height: 25%!important;
  min-width: 25%!important;
}

/* bigger skyplot image */
.skyplot img {
  width: 25%!important;
}

/* relation between skyplot and data - optional */
.astrometry-image-data {
  grid-template-columns: 0.25fr 1.5fr!important;
}

/* Two column layout with less grid gab and smaller font- optional */
.astrometry-data {
  grid-template-columns: 0.25fr 1.5fr 0fr 0fr!important;
  grid-gap: 0.5rem;
  font-size: 1.4rem;
}

.astrometry-data > .col3 {
  grid-column: 1!important;
}
.astrometry-data > .col4 {
  grid-column: 2!important;
  white-space: nowrap!important;
}

Thanks Matt - perfect match.
P.S. just for completness and our theme specific changes (T.Joy).
Unfortunately it was not possible - at least for my theme T.Joy to add custom CSS for the bock editor. For now, I therefore had to make to following changes to get the same results according to the theme layout in the Gutenberg-Editor.
Like Matt said: this should be in a custom theme css and NOT alter the plugin css file.
nano astrometry.editor.css

.astrometry-image-data .equipment {
     background: rgb(255,255,255);
}

.astrometry-image-data {
    background: rgb(220,220,220)!important;
}

/* bigger skyplot image */
.skyplot img {
  width: 50%!important;
}

.skyplot div {
  min-height: 25%!important;
  min-width: 25%!important;
}

/* bigger skyplot image */
.skyplot img {
  width: 25%!important;
}

/* relation between skyplot and data - optional */
.astrometry-image-data {
  grid-template-columns: 0.25fr 1.5fr!important;
}

/* Two column layout with less grid gab and smaller font- optional */
.astrometry-data {
  grid-template-columns: 0.25fr 1.5fr 0fr 0fr!important;
  grid-gap: 0.5rem;
  font-size: 1.4rem;
}

.astrometry-data > .col3 {
  grid-column: 1!important;
}
.astrometry-data > .col4 {
  grid-column: 2!important;
  white-space: nowrap!important;
}


Propose simplification to gallery codes

@h-mayorquin What would you think about removing the last bit of the conversion galleries that involves printing out the is_file() result on the path?
I've always thought it looks a bit awkward, and it occurred to me now that it's also not a great indicator of success. In fact, there are many points that can occur during any given run_conversion call that will result in a file being created, but the contents are corrupted and the NWB file is unreadable. The is_file() check would still be true, but not a good indicator that nothing went wrong.
Likewise, if anything does go wrong, it will show up as a traceback (however complicated and hdmf or h5py-nested it might be) from the interface.run_converssion(...) call, so it's more like we're asserting that there is no unexpected stderr from that line above

Yes, I don't think checking for file existence is doing a great check at verifying that the conversion ran successfully. Ultimately, we need a better way (any suggestions?). If you feel that the advantages of this weak test are not as large as the cost of the extra line I am fine with removing them, I don't have a strong feeling for this one
Can you describe some situations when the test would throw a false success?

Ultimately, we need a better way (any suggestions?)

The test would fail if such an error occurred during the run_conversion call wouldn't it? So the doctest being treated as an actual test unto itself would fail correspondingly and even have the traceback stack for it. I'd be fine with just relying on that as the assurance of pass/fail.
If you really do still want to keep a more unit-test like vibe to it, though, where there's some kind of structural assertion at the end, the most reliable thing would be a roundtrip access, i.e.,
with NWBHDF5IO(path=nwbfile_path, mode="r") as io:
    nwbfile = io.read()

which might be nice as well so then the user can look at the file contents/structure right away (if they're using a notebook, for instance, in the next cell they could just immediately print that variable to see a rough outline of content).

Can you describe some situations when the test would throw a false success?

Basically anything that would cause an error after a write-io is established. Basically, all run_conversion operations using nwbfile_path can be generalized to a structure of
with NWBHDF5IO(...) as io:
    # do a bunch of stuff to some in-memory nwbfile object
    io.write(nwbfile)

So if there's an error that occurs after the context creates the file, you'll still be left with a file and anything that had been partially written to it prior to the error.
Some of the worst types of this though are errors that can occur during the io.write() step, such as when you setup an iterative write for a dataset that doesn't raise any problem when you first make the neurodata type, but then encounters an unexpected read-access or shaping error after the iteration starts.

Thanks for explaining. Yes, this is fine to me. For the moment we can rely on the doctest just throwing any assertion as a failure. In the future, we can add a function that does a round-trip which we can use for code reduction in the gin-tests and doctests and users can use to check their conversions.

I like that these galleries are tested, but I don't want to sacrifice readability to improve tests here. If we want to do thorough tests, we should do that in the testing suite

Yes, this makes sense to me. I committed the remaining changes.


not giving result

i have run the tool with some multiple domain and a single domain but after taking to much time it can't give any result

Can you gave me more context like the format of domains you provided

Closing the issue. You were blocked from the Wayback API URL. If you disagree, feel free to reopen it

You Can Use VPN or Some Proxies to get rid of it and Use Waytime and Other tool like waybackurls .


[BUG] required packages docs are incomplete

Describe the bug
install docs at https://longhorn.io/docs/1.2.2/deploy/install/ are not complete
installing on fedora 35 server minimal with listed packages the longhorn-driver-deployer never passes the init step and longhorn-ui gets stuck in a crash/restart loop due to dns issues
ui pod needs to have dns related errors so might be k3s related, but this bug is to ensure docs are complete for longhorn for verifications before installing. environment check script from github doesnt report issue with minimal installation but it has errors
To Reproduce
Steps to reproduce the behavior:

install fedora 35 minimal from netinst iso
install listed packages from https://longhorn.io/docs/1.2.2/deploy/install/ and k3s/helm
install longhorn with helm chart
k3s kubectl get pods -n longhorn-system
observe crashing/non-running pods

Expected behavior
all pods start and run normally after installation
Log or Support bundle
If applicable, add the Longhorn managers' log or support bundle when the issue happens.
You can generate a Support Bundle using the link at the footer of the Longhorn UI.
Environment

Longhorn version: 1.2.2
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): helm
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: fedora 35 server minimal

Number of management node in the cluster: 1
Number of worker node in the cluster: 2

Node config

OS type and version:
CPU per node:
Memory per node:
Disk type(e.g. SSD/NVMe):
Network bandwidth between the nodes:

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
Number of Longhorn volumes in the cluster:

Additional context
using fedora 35 server standard install works which likely means a package needs installed when using minimal version.

@tuesdaycodes
I created a k8s cluster and longhorn according to your os/configuration successfully.
Not sure what errors did you encountered.  You can provide the error log for further investigation.
For k3s DNS issue, you may refer to
https://longhorn.io/kb/troubleshooting-dns-resolution-failed/

@derekbit where is the env file referenced for k3s in your docs? does it mean the normal config file for k3s? i dont use the same config on standard and dns worked out of the box (except longhorn not actual persisting data).

@tuesdaycodes
You can check k3s official document https://rancher.com/docs/k3s/latest/en/installation/install-options/server-config/ .

Probably we could enhance the environment check script to check the longhorn-backend:9500 is available.

Probably we could enhance the environment check script to check the longhorn-backend:9500 is available.

Let's use #3355 to enhance it. Close this one.


RT-1.30: BGP nested import/export policy attachment changes incorporated

Updated metadata.textproto
vender check included for NOKIA
Added deviations.
Updated nested_policies_test.go
Added deviation for prefixset_Mode.
Added deviation to skip rp match set options.
"This code is a Contribution to the OpenConfig Feature Profiles project ("Work") made under the Google Software Grant and Corporate Contributor License Agreement ("CLA") and governed by the Apache License 2.0. No other rights or licenses in or to any of Nokia's intellectual property are granted for any other purpose. This code is provided on an "as is" basis without any warranties of any kind."

Pull Request Functional Test Report for #3532 / 32ab1b2671e50be361aa8f73d6aae928da822157
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

RT-1.30: BGP nested import/export policy attachment

Cisco 8000E

RT-1.30: BGP nested import/export policy attachment

Cisco XRd

RT-1.30: BGP nested import/export policy attachment

Juniper ncPTX

RT-1.30: BGP nested import/export policy attachment

Nokia SR Linux

RT-1.30: BGP nested import/export policy attachment

Openconfig Lemming

RT-1.30: BGP nested import/export policy attachment

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

RT-1.30: BGP nested import/export policy attachment

Cisco 8808

RT-1.30: BGP nested import/export policy attachment

Juniper PTX10008

RT-1.30: BGP nested import/export policy attachment

Nokia 7250 IXR-10e

RT-1.30: BGP nested import/export policy attachment

Help

/fptest virtual

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.268%

Totals

Change from base Build<PHONE_NUMBER>0:
0.0%

Covered Lines:
1983

Relevant Lines:
3588

💛  - Coveralls

/fptest virtual

HW log with these changes are available at - b/380856696

/fptest virtual


Request CMOS chip behaviour

The undocumented out (c),0 instruction is the original NMOS Z80 behaviour. On newer CMOS Z80 chips it writes 0xff instead. I have an emulator option to control the behaviour, so I can see the effects on software that uses that instruction. I've only just realised that since switching CPU core the option no longer has any effect.
In my local copy I've implemented a handler called on_is_cmos_z80, which returns true if it's CMOS, false if it's NMOS (the default). The core uses the return value to pick either 0xff or 0 for the instruction implementation and the disassembler output.
If you think that's how you'd implement it I can put up a small pull request with the changes. If you think there's a better way to do it could I please request it be supported in a future release?

This a bit overlaps with #15, it probably should be implemented via introducing of CPU variants. I'm going play with the code a little to figure out a natural way to do this...


Storage: Refactor DMFileReader

What problem does this PR solve?
Issue Number: ref #6233
Problem Summary:
What is changed and how it works?
Refactor DMFileReader to make life easier~
Separate the packs can do clean read.
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-integration-test

/run-build-release

Maintaining must_seek makes the code seem cumbersome and odd.
According to the code, the cost of seek is negligible if we don't really need to seek. Maybe we can remove must_seek and just seek every time before reading from disk.
https://github.com/pingcap/tiflash/blob/master/dbms/src/IO/Compression/CompressedReadBufferFromFile.cpp#L54-L83

Totally agree, I will remove it.

/hold

/run-all-tests

/run-unit-test

/unhold

/run-all-tests

/run-unit-test


Update values-ru/strings.xml

Typos, punctuation and style fixes.
I noticed that translations come from translatewiki too late. So if PRs like this are fine -- great, if not -- I could probably redo it on the wiki.

Thanks a lot for improving the Russian interface!
As you have found out, localization is done at translatewiki.
Would you mind applying your modifications there?
Then close this pull request.
Thanks a lot, and sorry for the trouble! :-)


TODO: fix Travis when releasing

Needs API_KEY in Travis also

https://github.com/spacchetti/spago/releases/tag/<IP_ADDRESS>


Inconsistency in parameters in README

In the following section from the README, HASH_MODE and HASH_TYPE are inconsistent. Not sure which one is valid but may confuse someone trying to use in the future.

HASH_FILE=hashcat-3.6.0/examples0.hash POT_FILE=hashcat.pot HASH_MODE=0 ./naive-hashcat.sh

....

HASH_TYPE is the hash-type code. It describes the type of hash to be cracked ...

PS: Came from Hacker News, not personally a user and know this is small but hope it helps someone in the future. Cool project!

Just fixed with 7dc2e3bfd128a4e72dc6e0503d5944c5ab250e45. Thank you for bringing this to my attention! I appreciate it :smile_cat:


⚠ Bofrost.es has degraded performance

In 455dfa5, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1844 ms

Resolved: Bofrost.es performance has improved in 482e864 after 15 minutes.


Prepare the 0.15.0-alpha.2 release

@callemall/material-ui Guys take a look

Yeah, that's some good changes that we have inside this new upcoming alpha release :tada:.

Geez, another big alpha! Looks good to me though :+1:

@callemall/material-ui It's ready


Improve signing methods docs

Improve documentation around signing methods, integrating in improvements made recently in the legacy docs.
Reference information (e.g., parameters) for eth_signTypedData should be documented separately in the api-spec (see https://github.com/MetaMask/api-specs/issues/94).
Fixes #11

@metamaskbot publish-preview


Merge master with updated openblas

Merging in changes made in #31

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Added contribution section to the docs

I added a contribution section to the documentation. The section is quite a lot inspired by the one of EnergyModelsBase, but I think i removed all references to EMX packages after the copy-paste.
In its core, it is inspired by the one of JuMP.

I added all changes. From my end, it is good to merge. I leave it to you @trulsf  to merge it once @hellemo has approved as well (if you consider it required).
A side note:
We moved to EMX to test x64 LTS and latest now on both Windows and Linux while we removed nightly and x86 (it does not really makes sense as the first x86-64 CPUs came out in 2003). We could consider including ARM tests, if supported. This requires adjustments to the Julia Action versions as can be seen in this PR of EMRP.


fix: pinot select query logic

SUMMARY
Update Pinot selection query logic.

Direct return the field if it time grain is None.
No need to remove groupby fields from selection list anymore.

Codecov Report

Merging #9954 into master will decrease coverage by 11.93%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #9954       +/-   ##
===========================================
- Coverage   71.33%   59.40%   -11.94%
===========================================
  Files         585      401      -184
  Lines       30889    12740    -18149
  Branches     3237     3237
===========================================
- Hits        22036     7568    -14468
+ Misses       8744     4993     -3751
- Partials      109      179       +70

Flag
Coverage Δ

#cypress
?

#javascript
59.40% <ø> (ø)

#python
?

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

No need to remove groupby fields from selection list anymore.
Is this because it's been addressed in a newer version of Pinot? Do we not case about people on older versions? [Genuine questions] idk how the Pinot community distribution across versions is...

No need to remove groupby fields from selection list anymore.

Is this because it's been addressed in a newer version of Pinot? Do we not case about people on older versions? [Genuine questions] idk how the Pinot community distribution across versions is...

Thanks for bring this up!
In general, it won't change the behavior for old users as old pinot just ignores those fields, no matter the presence and always assume they are there. That's the reason we removed them to make query looks more like Pinot Style.
This code change is for pinotdb-pypi >=0.3.1, which leverages new Pinot SQL Endpoint(available on Pinot 0.3.0+)

I've also tested this code with both pinotdb 0.2.5 and 0.3.1, both works.


refactor(zk-explorer): Reorganize project structure

Summary of changes
Provide a detailed description of proposed changes.

Mostly refactoring and re-organization changes: No new functionality or existing one has been added/removed.
The reason why this project structure was chosen is because it reduces nesting, which makes things harder to find, and keeps things simple, while still maintaining organization and separation of concerns.
This re-organization is needed because there were two semi-separate project structures, so this PR consolidates them into one.
Some useMemos that were being used on constant-time operations were removed.
Removed unused components/files.
Prefer default exports for most things.
Avoid using index.ts files to just re-export things: Sure they make importing things look cleaner, but they come at an arguably larger cost: Need for continuous maintenance. Regardless, we as developers don't touch/work with import statements as much as actual code.

Improved project structure

components: Houses reusable UI components that do not handle fetching or managing data ("dumb" components). These are typically presentational and receive data via props.
constants: Stores various constants that can be used throughout the app, like API endpoints, default values, or configuration settings.
containers: Includes "smart" components that are responsible for data fetching and state management, often using server-side rendering provided by Next.js.
context: Holds React context definitions and providers.
hooks: Contains custom React hooks.
server: Dedicated to server-side logic like API route definitions, data fetching functions, and utilities that interact with databases, authentication, etc. Grouped by functionality (e.g., auth, user data).
utils: A collection of utility functions.

Proposed area of change
Put an x in the boxes that apply.

[ ] apps/bridge-dapp
[ ] apps/hubble-stats
[ ] apps/stats-dapp
[ ] apps/tangle-dapp
[ ] apps/testnet-leaderboard
[ ] apps/faucet
[x] apps/zk-explorer
[ ] libs/webb-ui-components

Reference issue to close (if applicable)
Specify any issues that can be closed from these changes (e.g. Closes #233).
Not applicable
Screen Recording
If possible provide a screen recording of proposed change.

Code Checklist
Please be sure to add .stories documentation if any additions are made to libs/webb-ui-components.

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

@yurixander, kindly address the merge conflict in this PR


add pango_attr_font_desc_new

I'm not sure why this wasn't already added.  Maybe there's something that I'm missing.

Thanks!


Adding windowsProfile and maxAgentPools property in the new 2019-04-01 api version

MaxAgentPools is a read only field. It's purpose is to show whether the current managed cluster is able to support the new multi-agentpool APIs. Old clusters will have the value 1 because they can't add new agent pools. But new clusters will have the value  8 because new agent pools can be added.
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[x] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[x] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[x] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-go

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-node

Automation for azure-sdk-for-ruby

Can one of the admins verify this patch?

@sarangan12, do you have any idea why the SDK generation failed? Is it because I can't remove a required property?

Automation for azure-sdk-for-java

@sarangan12, please take a look. This is needed for Windows Agent pool preview starting soon.

@AutorestCI regenerate azure-sdk-for-go

@jhendrixMSFT , could you take a look? Seems like sarangan12 is not available right now.

Can you please clarify what you mean by "Windows Agent pool preview", does it mean that these new APIs are preview?  The swagger is under a stable directory which would indicate otherwise.

@xizhamsft Please respond to @jhendrixMSFT question before merging. ALso, I want to confirm if you are aware this is a breaking change?

@jhendrixMSFT Yes. I can confirm that it is not a mistake to include agent pool API into a "stable" API version. Our PMs and ARM agreed on this. The preview text is added mainly to give customer an idea that it is something new.
@sarangan12 Yes. This is is a breaking change. That is why we decided to to it in this new 2019-04-01 API version.


custom testing API client implementation

Hi :wave:
First of all big thanks for developing this great package!
I have been using drf-openapi-tester in a few Django-based projects and it works like a charm, however, usually, I'm adding the same code to every project - rest_framework.client.APIClient subclass that simply validates response against OpenAPI description using SchemaTester.
What do you think about adding such a client to drf-openapi-tester package?

Hi!
That sounds interesting. How would it look?

Something like this works for me nicely:
from typing import Optional

from django.conf import settings

from openapi_tester.schema_tester import SchemaTester
from rest_framework.response import Response
from rest_framework.test import APIClient

class OpenAPIClient(APIClient):
    """``APIClient`` validating responses against OpenAPI description."""

    def __init__(
        self,
        *args,
        openapi_description_tester: Optional[SchemaTester] = None,
        **kwargs,
    ) -> None:
        """Initialize ``OpenAPIClient`` instance."""
        super().__init__(*args, **kwargs)
        self.openapi_description_tester = (
            openapi_description_tester
            or self._default_openapi_description_tester_factory()
        )

    def request(self, **kwargs) -> Response:  # type: ignore[override]
        """Validate fetched response against given OpenAPI description."""
        response = super().request(**kwargs)
        self.openapi_description_tester.validate_response(response)
        return response

    def _default_openapi_description_tester_factory(self) -> SchemaTester:
        """Initialize default ``SchemaTester`` instance."""
        return SchemaTester(
            schema_file_path=settings.OPENAPI_DESCRIPTION_FILEPATH,
        )

Of course, we can make it more generic by requiring passing openapi_description_tester when initializing this client.

Just so I completely understand then, using this in tests would look something like this?
schema_tester = SchemaTester()
client = OpenAPIClient(tester=schema_tester)
response = client.request('GET', '/api/v1/test')

instead of
schema_tester = SchemaTester()
response = client.get('/api/v1/test')  # 'client' if included as a fixture in pytest tests, 'self.client' in TestCase
schema_tester.validate_response(response=response)

This seems equally verbose. Are there specific cases where you would save lines of code, or make things less complex by (re-)using the client instead of the schema tester instance directly? 🙂

Yes, however, you can still use client.get(...) etc, because these methods use request under the hood. Additionally, you can enforce all developers working on the project to use OpenAPIClient by simply overriding the client fixture (or defining and using a new, custom fixture e.g. openapi_client), then you will be sure all newly implemented views will be validated against the OpenAPI description. So then it will look like a regular view test:
response = client.get('api/v1/test')

or when using openapi_client fixture instead of overriding client:
response = openapi_client.get('api/v1/test')

great, so I will prepare PR in the following days!
Sure I will use "schema" instead of "description".
BTW I'm using "description" mostly because of this glossary


feat(donasi): Donasi Warga page + widget

Closes #329
Description

the donasi.tsx page added
donation-card reusable component added .
donasi_page collection on config.yml added
informasi_donasi.json contents added

Current Tasks

[x] create a donasi page
[x] create a donasi widget on the homepage
[x] add donasi warga collections on config.yml
[x] add donasi warga page contents
[x] write the integration test for donasi page and donasi widget

donasi widget added.

@mazipan Yes. We need to add that to ~/lib/layout/navigation-data.tsx. But I think we can do that on a separate PR as per usual.

Then, it's your call @resir014
All good from me.
Already check the preview page, looks good to me.

Sorry for nitpicking, but I don't think we need a folder here. 😅
Please make the changes accordingly. Thanks, @syauqy! 🙏

😄  sure mas @zainfathoni, thank you for the suggestion


Can't update docker image

Which trigger/binding are you using?
HTPP
Which language are you using?
Typescript /NodeJS
Provide resource details

archivette
e40d0a43-943e-458b-9967-40dac7f289c0

Expected behavior
Upgrading should work without any deny assignment  in ACA and CLI / not crash happen when upgrading with Portal on the function app directly (configuration → upgrading the number)
Actual behavior

On portail, with function app → Configuration, got:

{"error":{"code":"ResourceNotProvisioned","message":"The ContainerApp 'archivette' has not been provisioned successfully. ProvisioningState: 'Failed'."}}

I can't even stop or restart the app.
2. When tried using ACA by ACA > container > edit and deploy I got the deny assignment error.
3. When tried using az containerapp update --name <functionAppName> -g <group> --image "<name>/<image>:<tag>" i get the same deny assignment :
(DenyAssignmentAuthorizationFailed) The client '@client' with object id 'd74c0f8c-3730-4fcd-a30c-de3b7ea2ef2e' has permission to perform action 'Microsoft.App/containerApps/write' on scope '/subscriptions/e40d0a43-943e-458b-9967-40dac7f289c0/resourceGroups/managedEnvironment-Archivette-9cdd_FunctionApps_46c02ae9-3f8f-419a-8cf3-962483c84148/providers/Microsoft.App/containerApps/archivette'; however, the access is denied because of the deny assignment with name '46c02ae9-3f8f-419a-8cf3-962483c84148' and Id '46c02ae93f8f419a8cf3962483c84148' at scope '/subscriptions/e40d0a43-943e-458b-9967-40dac7f289c0/resourceGroups/managedEnvironment-Archivette-9cdd_FunctionApps_46c02ae9-3f8f-419a-8cf3-962483c84148'.

To Reproduce
For context, by error, the old docker image was deleted before changing it in ACA.
But we could at last create a new revision and change using the managed environnement without any deny assignment.
Screenshots

Logs
/
Additional context
/

Hi @Mara-Li  , recommend you not to change/update from Azure container app resource portal pages. Can you please try update of images from Azure Functions resource portal pages, configuration tab and try  start/stop from Azure functions resource itself

If above does not work , can you redeploy the image and check?


catalina.out logrotate error

On Debian Wheezy, when I set up a Tomcat instance like so:
class { "::tomcat":
version => '7'
}
tomcat::instance { 'foo':
ensure      => 'present',
server_port => $tomcat_server_port,
http_port   => $tomcat_http_port,
ajp_port    => $tomcat_ajp_port
}
The module creates /etc/logrotate.d/catalina-foo containing:
/srv/tomcat/foo/logs/catalina.out {
copytruncate
size 500M
dateext
rotate 53
compress
delaycompress
missingok
create 644 tomcat tomcat-admin
}
This generates an error from logrotate:
/etc/cron.daily/logrotate:
error: catalina-foo:10 unknown group 'tomcat-admin'
error: found error in /srv/tomcat/foo/logs/catalina.out , skipping
error: skipping "/srv/tomcat/foo/logs/catalina.out" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
When I create the tomcat-admin group manually and add the following to the instance declaration in the manifest:
group => 'tomcat-admin',

The group ownership of the instance directories updates but when I run logrotate the same permissions error occurs:
error: skipping "/srv/tomcat/foo/logs/catalina.out" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
I can resolve this by specifying the logs_mode in the instance declaration:
logs_mode => '2750',

A quick fix would be to remove the group-write from the default mode of the file resource that creates the log/ directory.
More comprehensively, it would be good to update the 'create' line the logrotate.catalina.erb template to include the group parameter:
  create 644 tomcat <%= @group =>

But I imagine you must have some reason for marking the logrotate file explicitly as 'unmanaged'?

@dmcnicks could you provide a PR for that?


User friendly unsupported feature notification

What this PR does: enable sai for DSE-NEXT persistence
Which issue(s) this PR fixes:
related to jsonapi issue
Checklist

[x] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[x] CLA Signed: DataStax CLA

@Yuqi-Du for future reference, it would be good to use descriptive title for PR: although this PR is needed for "user-friendly unsupported feature notification", change here is not for that, but to fix dse-next persistence backend to indicate it does have SAI support.
(I'll change the title)


Pass the requestBody as it is to user supplied matching function

fix #344

Strange, I see different git log in this PR compared with my command line.

commit bce1155ed851d5f2e6c09f0c603f0edd61dad946 (HEAD -> master, roschaefer/master)
Author: Robert Schaefer<EMAIL_ADDRESS>Date:   Thu May 31 00:03:39 2018 +0200
    Update README
commit 33a74cc353780d0c4b8888114a2833764ba7c5d8
Author: Robert Schaefer<EMAIL_ADDRESS>Date:   Wed May 30 23:57:19 2018 +0200
    Provide a fix for #344 and let tests pass
commit d52f6f89f35bb51f9708a7fe40da8248603b69f8
Author: Robert Schaefer<EMAIL_ADDRESS>Date:   Thu May 31 00:58:13 2018 +0200
    Expose #344 in a unit test
commit de85ff658fde949c74049c9439c612e4f0c885b6
Author: Robert Schaefer<EMAIL_ADDRESS>Date:   Wed May 30 23:46:49 2018 +0200
    Expose #344

@danielspaniel Do you want me to remove de85ff658fde949c74049c9439c612e4f0c885b6?

No .. I don't mind the redundancy in this case Robert. Thanks for the PR and the fixing :)
will get this merged when I wake up


[Task] Add more verbose logging around database operations

I believe my original intent with this task was to add some logs to each query to describe the purpose of that query when logging to the server. This was likely in a time when we were not planning to log the entire query to the server. Since we are now logging the query, this is less important.
Closing, since we can always bring this back up if it is important.


node v4 compat #6

Resolves #6: Node v4 support by refactoring destructured assignment and rest params. These were additional refactors needed beyond just adding 'use strict';. Added the necessary tests.

Merged and released as 2.1.1. Sorry it took so long.


Device not waking up when receiving a notification

pushy_flutter: ^1.0.12

When the device is locked and we send a notification - the device screen does not come on nor does it show a notification bar?
Do you have any ideas how we can awake the device and show a notification that can be clicked?
Thanks

Hi @calvinmuller,
Thanks for reaching out. We'd be glad to assist with your issue.
Please consult this article for a solution:
How can I send notifications to Android devices in Doze / power saving mode?

Please let me know if there's anything else I can help with.


Cannot dynamically switch between builds with dynamic URLs in unityConfig

Please avoid duplicates

[X] I checked all open issues and discussions and none of them matched my problem.

Language and Compiler
Babel and WebPack JavaScript
What environment are you using?
Server Side Renderering
When does your problem occur?
When the Unity App is running
What does your problem relate to?
I don't know
React-Unity-WebGL Version
9.4.0
React Version
18.2.0
Unity Version
2022.2.9f1
What happened?
Hello!
We are trying to add build versions (debug, release) of our player to our NextJS app. Essentially, we want to be able to toggle between builds on a staging or even production environment for debugging purposes, but without reloading the page if possible.
We have put our versions in the public folder like stated and both versions are able to load when the URLs are hardcoded in the useUnityContext params.
Though, it seems that we are unable to dynamically change the values after the player has loaded.
Here's a simplified example of what we're trying to achieve (just a proof of concept for now)
  const [isDebugMode, setIsDebugMode] = useState(false);

  const playerVersion = isDebugMode ? 'debug' : 'release';
  const playerCompression = isDebugMode ? '' : '.br';

  const {
    unityProvider,
  } = useUnityContext({
    loaderUrl: `/player/${playerVersion}/Build/${playerVersion}.loader.js`,
    dataUrl: `/player/${playerVersion}/Build/${playerVersion}.data${playerCompression}`,
    frameworkUrl: `/player/${playerVersion}/Build/${playerVersion}.framework.js${playerCompression}`,
    codeUrl: `/player/${playerVersion}/Build/${playerVersion}.wasm${playerCompression}`,
    streamingAssetsUrl: `/player/${playerVersion}/StreamingAssets`,
  });

// ...

return (

      <button onClick={() => setIsDebugMode(!isDebugMode)}>TOGGLE</button>

        <Unity
          unityProvider={unityProvider}
        />
        <UnityLoading
          isLoading={!isReadyToStart}
          value={loadingPercentage}
        />

  );

We can see that the values changes, but nothing in the unityProvider.unityConfig prop changes
Is this expected? Is there a way to toggle between players without reloading the page?
Thanks!
Reproducible test case
No response
Would you be interested in contributing a fix?

[ ] yes, I would like to contribute a fix

same issue @jeffreylanters

@kroussea  i fixed that;
try this:
  const _unityProvider = useDeepCompareMemo(() => {     return {       ...unityProvider,       unityConfig: {         loaderUrl:/player/${playerVersion}/Build/${playerVersion}.loader.js,         dataUrl: /player/${playerVersion}/Build/${playerVersion}.data${playerCompression},         frameworkUrl: /player/${playerVersion}/Build/${playerVersion}.framework.js${playerCompression},         codeUrl: /player/${playerVersion}/Build/${playerVersion}.wasm${playerCompression},         streamingAssetsUrl: /player/${playerVersion}/StreamingAssets`,
},
};
}, [unityProvider, playerVersion,playerCompression]);
return (
<Unity
  ...
    unityProvider={_unityProvider}
  />`

@kroussea

Here's what I have with your suggestion (quick and dirty for now). I don't have useDeepCompareMemo, but I figure a simple useMemo would suffice just to try it out.
...
const [isDebugMode, setIsDebugMode] = useState(false);
const context = useMemo(() => ({
    loaderUrl: `${playerHost}/vSpacePlayer/${playerVersion}/Build/${playerVersion}.loader.js`,
    dataUrl: `${playerHost}/vSpacePlayer/${playerVersion}/Build/${playerVersion}.data${playerCompression}`,
    frameworkUrl: `${playerHost}/vSpacePlayer/${playerVersion}/Build/${playerVersion}.framework.js${playerCompression}`,
    codeUrl: `${playerHost}/vSpacePlayer/${playerVersion}/Build/${playerVersion}.wasm${playerCompression}`,
    streamingAssetsUrl: `${playerHost}/vSpacePlayer/${playerVersion}/StreamingAssets`,
  }), [playerHost, playerVersion, playerCompression]);

  const {
    unityProvider,
    loadingProgression,
    addEventListener,
    removeEventListener,
    sendMessage,
    UNSAFE__detachAndUnloadImmediate,
    UNSAFE__unityInstance,
  } = useUnityContext(context);

  const _unityProvider = useMemo(() => {
    return {
      ...unityProvider,
      unityConfig: {
        loaderUrl: `${playerHost}/vSpacePlayer/${playerVersion}/Build/${playerVersion}.loader.js`,
        dataUrl: `${playerHost}/vSpacePlayer/${playerVersion}/Build/${playerVersion}.data${playerCompression}`,
        frameworkUrl: `${playerHost}/vSpacePlayer/${playerVersion}/Build/${playerVersion}.framework.js${playerCompression}`,
        codeUrl: `${playerHost}/vSpacePlayer/${playerVersion}/Build/${playerVersion}.wasm${playerCompression}`,
        streamingAssetsUrl: `${playerHost}/vSpacePlayer/${playerVersion}/StreamingAssets`,
      },
    };
  }, [unityProvider, playerVersion, playerCompression, playerHost]);
...

return (

      <button onClick={() => setIsDebugMode(!isDebugMode)}>TOGGLE</button>

        <Unity
          unityProvider={_unityProvider}
        />
        <UnityLoading
          isLoading={!isReadyToStart}
          value={loadingPercentage}
        />

  );

When I toggle the debug state, it seems to reload the player, though at some point the canvas goes all black and it gives me this error:

I'm using react-unity-webgl v9.4.0, and not sure I could upgrade since I'm using UNSAFE__detachAndUnloadImmediate which I see has been removed in the latest version...


urxvtd service: init

Motivation for this change
Lower resource usage! See the ArchWiki for details.
I'm not 100% sure how to document this best. Any suggestions? Should I add some XML tags in the description?
Things done

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

[x] NixOS
[ ] OS X
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Okay, I think the current solution to the environment variables will be fine. It pollutes every user's env just a little, but I can't imagine anything harmful will come of it. I've tested it and it's working. Once we figure out the whole target business, this will be ready to go.

Another option could be writing a desktop manager service (like for xterm) which starts urxvtd and maybe open a first terminal window with urxvt.

@rnhmjoj I don't think this is the common use case of urxvt, most people want to use their existing window manager/desktop environment.

@Mic92 Thanks!


Added functionality for parent-only links in cd-menu

Needed for CoderDojo/cp-zen-platform#1066

Requires Requires CoderDojo/cp-users-service#232


Client.dll/Engine.dll Missing half the time

engine.dll missing or client.dll missing no matter what i do.

been an issue for while and it happens on and off

#1059

Didn't work still missing it


Require SUT files relative to test file directory

This way you are not forced to run each test within test file directory, even
if you still can.
Useful to be able to run each test from the parent directory, which
makes workflow easier mainly if you are running everything inside, for
example, a docker container.

Plus one on this feature. I see a good use case for it in future.
I keep all my exercises in a single folder, ~/exercism/elixir. Given the feature this PR proposes, I will now be possible to easily run tests for all exercises.
This may be useful when tests for exercises get updated (unfortunately this process is not automated by exercism cli yet): one may want to check that new/updated tests still pass given the solution codes. Similarly, if a new version of elixir comes out with some methods removed/deprecated – one can run all tests and see if something fails.
This would allow a sort of a home grown CI for exercises.

Nice improvement. Thanks! 🎉


AI Journaling Insights

Is your feature request related to a problem? Please describe.
I would love make this even more personalized by receiving insights on my journaling.
Describe the solution you'd like
I think you could add your OpenAI key and then use Semantic Search to surface relevant previous passages you journaled about. Also automatically classifying journal entries or extracting different tags would be super cool.
Describe alternatives you've considered
Exporting all data to ChatGPT

Also, I'd love to work on this feature myself, just let me know if you think it's cool and I'll get to work.

@th8m0z Let's have a chat on Starbook Discord


Feature - Handle Renovate bot package.json

Is your feature request related to a problem? Please describe.
https://github.com/ossf/scorecard/pull/322 , does not handle package.json (within a "renovate" section) https://docs.renovatebot.com/configuration-options/

Closing partially due to age, and Renovate deprecated this config 2 years ago:

Storing the Renovate configuration in a package.json file is deprecated and support may be removed in the future


This SCIM2 testcase validates for existing users when provisioning

Purpose
This test case validates for already created users
Tested environments
1.Ubuntu18.04
2.Java: 1.8.0_161
3.Identity Server fresh pack with embedded ldap

closing this PR as a new PR https://github.com/wso2/product-is/pull/4154 is created


[v1.1] Bot Revamp

everything

Code looks runnable, some useless lines of code?

just abit man thanks for checking out


Fails to detect installed dependencies

Installed versions of nauty 2.7.2, RingDecomposerLib 1.1.3 and nlohmann_json 3.10.5 are currently ignored by the build system and instead the dependencies are fetched again. Is there a way to avoid the redundant builds and make sure molassembler is build against the proper dependencies.
Issue #3 might be related to multiple versions of nauty being available on the system.

This should be possible for nauty and RingDecomposerLib, as Molassembler executes a standard find_package call in these cases. If the packages can't be found because they're installed in a non-default location, you can help CMake to find them by setting the environment variable CMAKE_PREFIX_PATH accordingly. (Alternatively, you can also use package-specific variables like RingDecomposerLib_DIR).
For nlohmann/json, Molassembler doesn't provide a way to use it as a preinstalled dependency. Since this dependency consists only of two files which have to be downloaded and don't add a lot of compilation overhead, I think it's not worth the hassle to externalize this dependency.

For nlohmann/json, Molassembler doesn't provide a way to use it as a preinstalled dependency

This is a problem, even with a single header file the project should be able to find it as preinstalled dependency. Especially for a popular package like nlohmann/json which is available in most package managers this should be the preferred approach.

After checking the nauty import I noticed that I cannot provide my own installation since you require a CMake based build at:
https://github.com/qcscine/molassembler/blob/8be2afcf42aa9d8bf13bd54d406eccff352f0970/cmake/ImportNauty.cmake#L10-L12
However nauty is an autoconf package and does not work with find_package out of the box unless you provide a custom finder, which seems to not be available in this repository. I had to add the following rudimentary finder:
# cmake/Findnauty.cmake
if(NOT TARGET nauty)
  find_library(NAUTY_LIBRARY "nauty")
  find_path(NAUTY_INCLUDE_DIR "include/nauty")

  add_library("nauty" INTERFACE IMPORTED)
  target_include_directories(
    "nauty"
    INTERFACE
    "${NAUTY_INCLUDE_DIR}"
  )
  target_link_libraries(
    "nauty"
    INTERFACE
    "${NAUTY_LIBRARY}"
  )
endif()

Similar finder works for RingDecomposerLib which doesn't export CMake package files in version 1.1.3
if(NOT TARGET "RingDecomposerLib")
  find_package("RingDecomposerLib" CONFIG)
endif()

if(NOT TARGET "RingDecomposerLib")
  find_library(RingDecomposerLib_LIBRARY "RingDecomposerLib")
  find_path(RingDecomposerLib_HEADER "include/RingDecomposerLib.h")
  get_filename_component(RingDecomposerLib_INCLUDE_DIR "${RingDecomposerLib_HEADER}" DIRECTORY)

  add_library("RingDecomposerLib" INTERFACE IMPORTED)
  target_include_directories(
    "RingDecomposerLib"
    INTERFACE
    "${RingDecomposerLib_INCLUDE_DIR}"
  )
  target_link_libraries(
    "RingDecomposerLib"
    INTERFACE
    "${RingDecomposerLib_LIBRARY}"
  )
endif()


Question: Encoding parameters for http://jsonapi.org structure

Just wondering if anyone had any tips or ideas about the way to setup parameters for http://jsonapi.org structure.
For example the json structure for our Login is:
{
  "data": {
    "attributes": {
      "email"<EMAIL_ADDRESS>      "password": "password",
      "client-uuid": "e43ccaf0-b66f-49f8-95f1-ee9e14a88962"
    }
  }
}

And the structure for refreshing a token is:
{
  "data": {
    "type": "user-authentications",
    "id": "58fc7178-e135-462e-b328-ec8802023579",
    "attributes": {
      "long-jwt": "eyJ0eX...TIE"
    }
  }
}

My question is around defining a way to shuffle values into the data.attributes, vs data.id etc.
The obviously terrible, poor man's way to do it:
extension AwesomeAPI: RxMoya.TargetType {
  ...
  var parameters: [String: AnyObject]? {
    switch self {
    case .Login(let email, let password, let clientID):
      return ["data": ["type": "user-authentications", "attributes": ["email": email, "password": password, "client-uuid": clientID]]]
    case .RefreshToken(let longToken, let clientID):
      return ["data": ["type": "user-authentications", "id": clientID, "attributes": ["long-jwt": longToken]]]
   }
}

Would this be the responsibility of the conformer to TargetType, or should someone else create these structures?
Any thoughts would be super appreciated :) This is probably more of a Slack question than a question on issues.

What you've got is actually how things are done, except broken into several lines. Here's an example of using it.

I'm going to create a mapper for it, a public pod, if you want to participate

Cool! Please consider submitting a PR to the readme to add it :+1:


Implementation for processing leader

@cruhland @larioj PR is ready for review.

FYI, I rebased and squashed on top of the latest master.

@jsancio back to you! Had some comments about the tests...they should be extrapolated to all test cases/fixtures.

@cruhland @larioj Ready for review. Thanks!

Thanks for the review @cruhland and @larioj


Could you make a compilation video of the "I swear to god" and "Retard alert" tags?

What is your question?
Make a video showing all the dumb***es and @ShadowMario absolute roasting of them. Add it to the README or maybe as an Easter Egg to the engine? Or just YT...

We won't do it.


NIP-22: Event created_at Limits

https://nostr-nips.com/nip-22

Name
Description

limits.event.createdAt.maxPositiveDelta
Maximum number of seconds an event's created_at can be in the future. Defaults to 900 (15 minutes). Disabled when set to zero.

limits.event.createdAt.minNegativeDelta
Maximum number of seconds an event's created_at can be in the past.  Defaults to zero. Disabled when set to zero.

Cannot apply this to regular events, for example 1059 (PDM) have a random created_at, possibly created in the past.... so for now I keep this only for non-regular event kinds


Tweak ecosystem_versions schema to be consistent

We want to know three things for every ecosystem component:

The raw version string and the name of the manifest file that it was pulled from. This provides great fidelity, especially if there are multiple sources of versions (looking at you Python with .python-version + setup.py etc in the same repo)
"rounded" / summarized versions of the above that are easy to write comparison queries against. Ie, max/min supported versions that are rounded to decimals rather than semver so that in a SQL-like query language we can easily write comparison queries.

So this starts the process of transforming our existing metrics to this format.

I'm no longer on the :dependabot: team and this PR changes metrics, which requires accompanying changes on the Dependabot internal back-end, so not something I can move forward with on my own.
I'll leave it up to the current team to decide whether to proceed with this or close it out.


AuthLord Phase 1

Setup completed: Laravel, PHP, Composer, MySQL configured and verified. Ready for development.

Application
Version
Description

Laravel Framework
11.34.2
PHP framework for developing web applications with the MVC architecture.

PHP
8.3.6
A programming language widely used for web development.

Zend Engine
4.3.6
Engine that interprets and executes PHP code, with Zend OPcache for optimization.

Composer
2.8.3
Tool for managing PHP packages and libraries.

MySQL
8.0.40
Relational database system widely used in web applications.

Apache
2.4.58
Web server that processes and serves web pages and APIs.

Ubuntu Linux
24.04.1 LTS (Noble)
Open-source Linux distribution widely used in development environments.

AuthLord core structure is functional and deployed with migrations and templates.


⚠ Samsung has degraded performance

In 7a117c9, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2543 ms

Resolved: Samsung performance has improved in 6f5a4aa.


AP-58 Enable Mobile bancontact payments

Summary

Bancontact mobile payment option added, as per documentation, to the available payments.
Tested scenarios
For the api v52 payment method:  bcmc_mobile_QR and bcmc_mobile_app are provided and passed to the Adyen checkout web component.
The code has also been verified to be able to work with api v64.
One issue arose: for bcmc_mobile_QR,
On the test account for payment returned the response: Could not find an acquirerAccount.
Fixed issue: #58

@acampos1916 The CI runner uses an image with a Composer 2 version.
Two possibilities:

install / downgrade composer on the runner
update packages to use composer 2 (but this could have other restrictions as PHP version is current set at ^7.0

@acampos1916 The CI runner uses an image with a Composer 2 version.
Two possibilities:

install / downgrade composer on the runner
update packages to use composer 2 (but this could have other restrictions as PHP version is current set at ^7.0

Thanks @bortefi, I opened a PR to downgrade composer in main.yml https://github.com/Adyen/adyen-shopware5/pull/76 @msilvagarcia @cyattilakiss what do you think?

@acampos1916 The CI runner uses an image with a Composer 2 version.
Two possibilities:

install / downgrade composer on the runner
update packages to use composer 2 (but this could have other restrictions as PHP version is current set at ^7.0

Thanks @bortefi, I opened a PR to downgrade composer in main.yml #76 @msilvagarcia @cyattilakiss what do you think?

Since you only change it in the CI I think it's all right 👍


💡 [FEATURE] - Text alignment properly

Idea Contribution

[X] I have read all the feature request issues.
[X] I'm interested in working on this issue
[X] I'm part of GSSOC organization

Explain feature request

Explain your solution
I want to align the text properly
Any alternative approaches/features
No response
Additional Context
I want to work on this issue.
Please assign me this issue.

Hello, I'm interested in working on this issue. Please assign it to me.

What do you man asslign? you mean the text overflow?

Dis is duplicate issue


added missing endpoints

added all missing music, extension, music, teams, users and videos endpoints to the update-endpoints branch
I have also added the newer endpoints (block user, unblock user, whisper, chat announcement, get/update chat color etc.)

Wow that's huge, thanks! I'll review the changes tomorrow

@romanzipp all changes merged

nice, Thanks!


Cannot evaluate simple predicate without SMT solver

kevm-bug.tar.gz
This file comes from a simple proof on https://github.com/kframework/evm-semantics/pull/912/commits/06c9c8b514b544057e27a81e568acd89eda58654.
The proof is from tests/specs/functional/lemmas-no-smt-spec.k, and looks like this:
    claim <k> runLemma ( 1 ==Int bool2Word( B:Bool ) )   => doneLemma ( B ==K true ) ... </k>

The error produced looks like this:
kore-exec: [2886042] Error (ErrorDecidePredicateUnknown):
    Failed to decide predicate:
        /* Sfa */
        \not{R}(
            /* Spa */
            \equals{SortBool{}, R}(
                /* Fl Fn D Sfa */ VarB:SortBool{},
                /* Fl Fn D Sfa Cl */ /* builtin: */ \dv{SortBool{}}("false")
            )
        )
    with side condition:
        /* D Sfa */ \top{_PREDICATE{}}()

@ehildenb Can you confirm that the evm-semantics build system still runs this spec without the SMT solver?

@ttuegel yes the build system passes --haskell-backend-command 'kore-exec --smt=none', and if you look at kore-exec.sh, you can see the --smt none option. Anything else you'd like me to verify about that?

This was probably triggered by #2170 and would be fixed by #2174. I need to investigate that, but that's where I'll start.

What I've found so far is that during the application of this equation, we send the condition to the solver when we check the requires, here, and this is what triggers the error because we're running this test without the solver.

I'm can't really explain how this ever worked. The cited rule requires the SMT solver to be applied. My hope for fixing this right now is that, as part of #1986, the backend will apply simplification rules before and after function definitions, so we can avoid that rule with the appropriate lemma.


Load exception

Dispatch load exception so that others can react without capturing the corresponding error. Will be used in conjunction with https://github.com/dart-lang/test/pull/682

I think you have to send this through gerrit now? not sure

Talk to @jmesserly and @vsmenon ...

Looks fine, but yeah, you'll need to use the new gerrit workflow.  Github is now read-only for the sdk.
Note - this file (dart_library.js) is only used internally.  You'll need to do something different for external tests.

Also – tests?


Linux mint docker <IP_ADDRESS> build fails

Creating a container on linux mint fails with DNS errors.
I am following the quickstart / tutorial from Docker - build your own image
Might be related to issue docker/docker#20026
Output of docker version:
Client:
 Version:      1.10.2
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   c3959b1
 Built:        Mon Feb 22 21:37:01 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.10.2
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   c3959b1
 Built:        Mon Feb 22 21:37:01 2016
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 9
 Running: 0
 Paused: 0
 Stopped: 9
Images: 2
Server Version: 1.10.2
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 30
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 3.19.0-32-generic
Operating System: Ubuntu 14.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.773 GiB
Name: robin-K73E
ID: Q7FL:6LJ7:BUUU:5UVX:T7VP:V5UR:4ZRF:PUBR:KXP6:6HOK:DUIT:G54W
WARNING: No swap limit support

Provide additional environment details (AWS, VirtualBox, physical, etc.):
Using Virtualbox on a crappy laptop
List the steps to reproduce the issue:
1. I am running the following Dockerfile
FROM docker/whalesay:latest
RUN apt-get -y update && apt-get install -y fortunes
CMD /usr/games/fortune -a | cowsay

2. Command i use is:
docker -D build -t docker-whale .

Describe the results you received:
Sending build context to Docker daemon 64.51 kB
Step 1 : FROM docker/whalesay:latest
 ---> 6b362a9f73eb
Step 2 : RUN apt-get -y update && apt-get install -y fortunes
 ---> Running in 33ab092e1119
Err http://archive.ubuntu.com trusty InRelease

Err http://archive.ubuntu.com trusty-updates InRelease

Err http://archive.ubuntu.com trusty-security InRelease

Err http://archive.ubuntu.com trusty Release.gpg
  Could not resolve 'archive.ubuntu.com'
Err http://archive.ubuntu.com trusty-updates Release.gpg
  Could not resolve 'archive.ubuntu.com'
Err http://archive.ubuntu.com trusty-security Release.gpg
  Could not resolve 'archive.ubuntu.com'
Reading package lists...
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/InRelease

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-updates/InRelease

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-security/InRelease

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/Release.gpg  Could not resolve 'archive.ubuntu.com'

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-updates/Release.gpg  Could not resolve 'archive.ubuntu.com'

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-security/Release.gpg  Could not resolve 'archive.ubuntu.com'

W: Some index files failed to download. They have been ignored, or old ones used instead.

Describe the results you expected:
Doing a wget on any of the urls works just fine.
Obviously a container that could connect to to urls as well.
Provide additional info you think is important:
What i tried so far
After some issue tracking i found 2 ways to help with dns
doing:
 docker -dns <IP_ADDRESS> build -t docker-whale .

and
adding DOCKER_OPTS="--dns <IP_ADDRESS> --dns <IP_ADDRESS>"
to the /etc/default/docker file.

Both ways still fail.
Then i found ticket docker/docker#20026
But sadly Linux Mint is not using firewalld. It is using ufw.
I disabled ufw, restarted the docker daemon but sadly still no luck when running the docker file.
Any clue if this is related to the 20026 issue or might this be something different?
Some os info
➜  cat lsb-release
DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=17.3
DISTRIB_CODENAME=rosa
DISTRIB_DESCRIPTION="Linux Mint 17.3 Rosa"
➜  cat os-release
NAME="Ubuntu"
VERSION="14.04.4 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.4 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
➜  uname -a
Linux robin-K73E 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Hmm this looks like a corporate network issue. Looks like dns request to not-corporate dns servers is blocked. So i had to disable dnsmasq so it got the corporate dns server details in my container. So using the default public dns servers is not really the best option imho.

@pollyrobin did it work correctly after changing to the corporate DNS servers?

Luckily it did so it does not really look like an issue. Except if something can be done at Dockers side not to automatically use public DNS servers but try to find the locally used ones first(but i think i my case this was a dnsmasq issue)

The default dns configured is <IP_ADDRESS>, to prevent issues in cases where (e.g.) <IP_ADDRESS> is used as DNS, which won't work inside the container (where <IP_ADDRESS> points to the container itself).
I'll close this issue


chore(deps): update dependency glob to v11.0.0

chore(deps): update dependency glob to v11.0.0
chore: migration for glob v9

resolved in #162


Bump react-konva from 17.0.1-3 to 17.0.2-0

Description

Bump react-konva from 17.0.1-3 to 17.0.2-0
Type of change

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

How to test

Checklist

[x] I have tested this code
[ ] I have updated the documentation

Pull Request Test Coverage Report for Build 738597429

3 of 4 (75.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 30.391%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/commons/sagas/WorkspaceSaga.ts
0
1
0.0%

Totals

Change from base Build 737949506:
0.02%

Covered Lines:
2564

Relevant Lines:
7743

💛  - Coveralls


[BUG] Note title with special characters result in wrong filename

Please confirm

[x] I am running the latest version of this plugin

Describe the bug
Creating a note that contains - (and also other special characters like +) while prefixing the title with the UUID results in an incorrect note name:

a-b -> a-202211081846-a-b.md
a+b -> a+b202211081846-a+b.md

To Reproduce
Steps to reproduce the behavior:

Start nvim
:Telekasten new_note
Insert e.g. a-b
Filename is incorrect

Expected behavior
The filename to start with the UUID instead of (parts of) the title.
Operating system (please complete the following information):

OS: Linux (Arco Linux)

Additional context

Neovim version 0.8.0.
Parts of my config:

require('telekasten').setup({
    -- ...
    prefix_title_by_uuid = true,
    new_note_filename = "uuid-title",
    uuid_type = "%Y%m%d%H%M",
    uuid_sep = "-",
})

This line is the culprit. It looks like we must first sanitize the filename, otherwise it will return the original title as the subdir.
I will come with a fix this evening or tomorrow.

Closed with https://github.com/renerocksai/telekasten.nvim/commit/de4502bd558e05ce617df177acff2c1e86f39155

Works like expected, thank you.


Feat: working version tying permissions to teamproject role

Jira Ticket: VADC-809
New Features

uses the new permissions framework introduced in https://github.com/OHDSI/WebAPI/pull/2301 to assign specific cohortdefinition permissions to a "team project" role when a new cohort is made by a "team project" user in Atlas

Example:
Creating a cohort (with id 8) while logged in as a team member of "team project" def, results in the following records:
"def"	"cohortdefinition:8:check:post"
"def"	"cohortdefinition:8:put"
"def"	"cohortdefinition:8:delete"
"def"	"cohortdefinition:8:version:*:get"
"def"	"cohortdefinition:8:info:get"
"def"	"cohortdefinition:8:get"
"def"	"cohortdefinition:8:version:get"

Query used for list above:
select
    sec_role.name, sec_permission.value
  from
    webapi.sec_role
    inner join webapi.sec_role_permission on sec_role.id = sec_role_permission.role_id
    inner join webapi.sec_permission on sec_role_permission.permission_id = sec_permission.id
 where
   sec_role.name = 'def'

Motivation
Motivation for this PR is twofold:

This change ensures that when another user logs in with the same "team project" (def in this case), this user will get the role def assigned and thus inherit access to cohorts accessible to this role (8 in this case).

By linking the cohorts to a "team project" role instead of linking them directly to a user, it becomes possible to get the complete list of all cohorts for a given "team project" (which is useful in other scenarios / for some of the other non-atlas tooling integrating with this DB)

Merge order
Should be merged after https://github.com/vinci-ohdsi/WebAPI/pull/5

PR #107 replaces this one.


Improve parallelism of repartition operator

Which issue does this PR close?
Close https://github.com/apache/arrow-datafusion/issues/6290
Rationale for this change
I was testing query performance for https://github.com/apache/arrow-datafusion/issues/6278 and noticed that only. a single core was being used on a query entirely in memory. When I spent some time looking into it, the plan looked correct with repartitioning but for some reason it wasn't properly repartitoning
What changes are included in this PR?
Don't yield on every batch -- yield only after we have made some decent progress (in this case at least partition_count batches)
Are these changes tested?
I manually tested this -- I will add a benchmark for it shortly
My manual test results are:
On main (Keeps only 1 core busy for most of the time)
4 rows in set. Query took 10.631 seconds.

With this PR (keeps the cores much busier)
4 rows in set. Query took 3.705 seconds.

Are there any user-facing changes?

cc @crepererum

FYI @metesynnada I don't know if you have any thoughts on this approach (or the yield in general, as you reported https://github.com/apache/arrow-datafusion/issues/5278 initially)

Hi @alamb, @metesynnada is unavailable for this month, he will be back at the end of the month. I checked this PR out and it  looks better than the status quo to me.

I plan to leave this open for another day or two for comments and then will merge in

I merged up from main -- and once CI passes I plan to merge this PR

Side note: when I've added the yield statement I was wondering if this would be too much overhead, but my assumption was the the batches would hopefully be big enough so that wouldn't matter. Seems that I was wrong 😅

Side note: when I've added the yield statement I was wondering if this would be too much overhead, but my assumption was the the batches would hopefully be big enough so that wouldn't matter. Seems that I was wrong 😅

I think the fact that the source in this case is a MemoryExec (where all the data is already in memory and can be provided almost instantaneously hurts us)


k8s: fix incorrect EndpointSlice API version [1.12]

This is a backport of https://github.com/cilium/cilium/pull/27277 to 1.12 branch.
This commit fixes a bug that k8s watcher incorrectly chooses the discovery/v1beta1 EndpointSlice in environments where discovery/v1 EndpointSlice is available.
The agent doesn't wait for the discovery/v1 EndpointSlice to be received and ends up removing live services because of this bug.
The issue happens in the following scenario:

The agent initializes and runs the informers for Service and EndpointSlice.
The reflectors list the resources from kube-apiserver and replace DeltaFIFO.
The informers pop items from the DeltaFIFO and call the onAdd handler one by one.
If the Service handler is called first, ServiceCache.UpdateService doesn't emit the UpdateService event, because the service is not ready. (No backend)
The EndpointSlice handler is called next, ServiceCache.updateEndpoints emits UpdateService event.
The agent doesn't wait until the event triggered at step 5 is processed, and calls SyncWithK8sFinished.
The agent removes live services because it hasn't heard about it. (It is supposed to hear about those services in the event process triggered at step 5)

fixes: #27215

/test-backport-1.12


When my controller is connected my wifi is gone

Hello when I connect my ds4 on bluetooth my wifi isn't working idk why... please help me or if a ds4windows dev see this please do a patch. (I have bad english)

I also have the same problem when I connect it by BT.


[bugfix] Fix remote auto-detection crash

If you try to auto-detect a remote partition, ReFrame will crash as follows:
Traceback (most recent call last):
  File "./bin/reframe", line 22, in <module>
    cli.main()
  File "/users/karakasv/Devel/reframe/reframe/frontend/cli.py", line 617, in main
    autodetect.detect_topology()
  File "/users/karakasv/Devel/reframe/reframe/frontend/autodetect.py", line 229, in detect_topology
    with runtime.temp_environment(modules=temp_modules,
NameError: name 'temp_modules' is not defined

This PR fixes this and introduces a unit test that tests that.

@jenkins-cscs retry daint

Codecov Report

Merging #2189 (73c3aa7) into master (0e294f2) will decrease coverage by 0.06%.
The diff coverage is 23.07%.

@@            Coverage Diff             @@
##           master    #2189      +/-   ##
==========================================
- Coverage   86.31%   86.25%   -0.07%
==========================================
  Files          53       53
  Lines        9557     9566       +9
==========================================
+ Hits         8249     8251       +2
- Misses       1308     1315       +7

Impacted Files
Coverage Δ

reframe/frontend/autodetect.py
60.00% <23.07%> (-2.42%)
:arrow_down:

Continue to review full report at Codecov.

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