Older buffers are not being deleted

Probably:

border buffers
fps buffers (finder, previewer, sorter)
termopen things may not be getting completely destroyed.

Until I can confirm otherwise, I think it's done. Will open with specific ones later.


Victorhu/korebuild

First attempt to see if the new build works on travis/appveryor.
The scripts still point to my branch.
cc @dougbu @BrennanConroy @pranavkm @natemcmaster

@victorhurdugaci Is this PR stale? I see you already merged in d0709e4a12382d94de39988a5876d134163c07ab


Error in Parameter Handling

Hi there,
when experimenting with compiling a parameterized quantum circuit partly with Qiskit and partly with TKET using the following example:
from pytket.extensions.qiskit import qiskit_to_tk, tk_to_qiskit
from pytket.passes import CliffordSimp
from qiskit.circuit.library import TwoLocal
from qiskit import transpile

qc = TwoLocal(1, "ry", "cz", reps=1, entanglement="linear")
qc_transpiled = transpile(qc, basis_gates=["sx", "rz", "cx", "x"], optimization_level=3)

tket_qc = qiskit_to_tk(qc_transpiled)
CliffordSimp().apply(tket_qc)
transformed_qc = tk_to_qiskit(tket_qc)

qc_transpiled_again = transpile(transformed_qc, basis_gates=["sx", "rz", "cx", "x"])

qc_transpiled_again = qc_transpiled_again.assign_parameters({qc_transpiled_again.parameters[i]: 0 for i in range(len(qc_transpiled_again.parameters))})

I face a TypeError: could not cast expression to complex error.
Apparently, there is some error in the parameter handling in combination with sympy. When executing
expr = qc_transpiled_again.data._circuit._data[2].operation.definition.data._circuit.global_phase
assigned_expr = expr.assign(qc_transpiled_again.parameters[0],1).assign(qc_transpiled_again.parameters[1],1)
print(assigned_expr)
print(assigned_expr._symbol_expr)
print(assigned_expr.is_real())

the expression is apparently not real, although the symbolic representation can be reduced to a real number. Even a assigned_expr._symbol_expr.evalf() does not reduce the assigned_expr and returns -0.5*(3.14159265358979 - 2*atan2(-0.841470984807895, 0.540302305868143)). Maybe the atan2 causes the problem?
I used Qiskit v0.45.3, pytket_qiskit v0.48.0 using python 3.11 under Mac OS v14.2.1.

Hi there,
unfortunately, the error still persists in pytket-qiskit v0.50.0 with qiskit v1.0.2. However, the error message is now a bit different: TypeError: EvalfMixin.evalf() got an unexpected keyword argument 'real'
It would be highly appreciated if you could have a look into this issue, since it currently prevents a smooth combination of compilation passes from both qiskit and tket within our MQT Predictor framework.

Interestingly, when I try to convert the quantum circuit after the tket CliffordSimp() via dumping and then loading via the qasm format using

from qiskit import QuantumCircuit
from pytket.qasm import circuit_to_qasm_str

transformed_qc = QuantumCircuit.from_qasm_str(circuit_to_qasm_str(tket_qc))

I get a different error: QASM2ParseError: "'atan2' is not a parameter or custom instruction defined in this scope"

Thank you for reporting this, I will take a look and try to understand what is going on

Thank you for reporting this, I will take a look and try to understand what is going on

Thanks a lot for that. I was wondering whether you already had the time to have a look?

Hi @nquetschlich
Thank you for being so patient, the issues was a bit tricky.
I have been able to reduce this to a problem in qiskit interacting with sympy and I have submitted a bug report.
I will keep an eye on this and try to update as soon as this is fixed.
More details can be found at: https://github.com/Qiskit/qiskit/issues/12144

The issue in qiskit was caused by an updated and what we were trying in the conversion is not expected to work any more.
I have updated that now and put out a release candidate.
Can you please check if this solved all the issues you have?
You can install it with pip install pytket-qiskit==0.51.1rc0

The issue in qiskit was caused by an updated and what we were trying in the conversion is not expected to work any more.
I have updated that now and put out a release candidate.
Can you please check if this solved all the issues you have?
You can install it with pip install pytket-qiskit==0.51.1rc0

Thanks a lot for fixing this issue. I tried it out and it works.


fetchurl: better support multiple hash types

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

[ ] NixOS
[ ] OS X
[x] Linux

[ ] 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.

Instead of requiring that Nix be new enough to handle the sha512 hash
type if it is passed to fetchurl with an assert, instead fallback to
other hash types if Nix is not new enough. This enables passing
multiple hash types (e.g. sha256 and sha512) to fetchurl in a way that
can be evaluated on both new and old Nixes that do/do not support the
newer hash (sha512).
See conversation at https://github.com/NixOS/nixpkgs/pull/15048.
This did not cause any rebuilds for me (with Nix version 1.11.2); I did not test with an older Nix but I will try to do that soon. If this change is accepted, I would like to have future changes require both sha256 and sha512 hashes so they can evaluate on both old and new Nix versions.
cc @vcunat

I added a commit that gives util-linux both sha512 and sha256 hashes, and it seems to evaluate with both Nix 1.10 and Nix 1.11.2. Further testing would be appreciated to make sure this works properly with both old and new Nix versions.

+1 for reverting to sha256 in util-linux (your 2nd commit).
I'm less sure about the 1st commit. As long as nix will rebuild when changing hash type (that's unfortunate!), I think there is little value in allowing sha512 for newer nix, because old nix users cannot use the binaries produced by the new nix (they have to build it themself, as @vcunat pointed out in https://github.com/NixOS/nixpkgs/pull/15048#issuecomment-219149502).
Due to it being a mass-rebuild (!), I'd like to defer to others to decide whether to merge (the util-linux commit) to staging or master.

What's our story for upgrading to newer hashes? Being stuck on sha256 forever is not something that I'm OK with; we need to have cryptographic agility to be able to update to newer, stronger hashes over time. Maybe this will require some changes to Nix itself, or maybe we should have a policy about how long to wait for a newer Nix version to disseminate (1 major nixpkgs version?) before bumping the minimum required version, but IMO it's important that we find a story for this that preserves backwards compatibility.
Personally, I use a number of tweaks that mean I have to recompile everything anyways, so I don't mind. Another point is that I'm assuming Hydra has a new Nix and will use sha512 for the binary cache, so only users with old Nix versions will need to recompile; this may be a good incentive to have them upgrade sooner rather than later.
Also note that the second commit has both sha512 and sha256, so without the first commit fetchurl will always try to use sha512, but will throw an assert if Nix is too old.

Also, I don't see why this is a mass-rebuild; this just causes fetchurl to skip looking at sha512 if Nix is too old, and the only package that this would affect is util-linux with the second commit, which can now be evaluate on old Nix instead of simply throwing an assert.

Oh, right, it isn't mass-rebuild (I thought it did s/sha512/sha256/, but it really adds sha256).
But how important is it to have sha512 now, as opposed to waiting one more release cycle (6 months)? I'm asking seriously, I don't know what kind of risk it poses.
Another possibility, IMHO, would be to backport sha512 support to Nix 1.10, the version used on NixOS 15.09.
Anyway, I'm not against this patch. I just said I was unsure about the 1st commit, as I explained above.

I didn't follow this discussion and staged 26e8e3e654d439 meanwhile, with the glibc security rebuild. I think the main incentive for sha512 was changes in Mozilla's releases https://github.com/NixOS/nix/issues/679 that made getting other hashes from them more difficult.

@bjornfor @vcunat How do you feel about this PR now? It's one release cycle later (16.09 is almost here), more packages are using sha512 (see #16391 for example), and makes it easier to move from sha256 -> sha512 by supporting multiple hashes in fetchurl allowing users with older Nix to continue evaluating packages.

Hm, I'd like to back out of this discussion. I'll leave the decision whether this is the right approach to more skillful / knowledgeable Nix'ers.

@grahamc security, enhancement

Another release cycle is up soon, so this workaround shouldn't be needed (everyone should be running a recent enough Nix soon). Plus, the fact that evaluating the same packages on different Nix version sounds highly undesirable. Closing.


Implement $everything operation roadmap

User story
As a user, I want to retrieve all resources related to a Patient
Acceptance criteria

When I call https://{fhirserver}/Patient/{resourceId}/$everything
I receive a bundle with all resources that have the patient id as subject reference

Fhir documentation:
https://www.hl7.org/fhir/operationdefinition.html
https://www.hl7.org/fhir/patient-operation-everything.html
Working example:
https://try.smilecdr.com/baseR4/Patient/1565/$everything?_count=100&_format=json
I would like to know when this functionality will be released.
Thank you.

@holpit we don't have an ETA on when we expect to support this but will update this issue as we make timing decisions. In the meantime, you can make two API calls to get all the details. First you can grab the patient record using /Patient/ and then a second call to retrieve all the patient data using /PAtient//*

Some more context from implementers was discussed here: https://chat.fhir.org/#narrow/stream/179166-implementers/topic/.24everything.20with.20_type

We have this implemented now: https://docs.microsoft.com/en-us/azure/healthcare-apis/fhir/patient-everything


Setting t_Co

For most terminals I've tried this with under Linux (xfce4-terminal, urxvt), the dracula theme does not work.
To fix this, just add:
set t_Co=256 before the let g:colors_name = 'dracula'  on line 21.
I figure it would be just as easy for you to add this directly than for me to issue a pull request.
Thx.
JS

This is an umbrella repository for all themes. I see you left a comment on https://github.com/dracula/vim/issues/29#issuecomment-300545098 so I'm going to close this for now.


On default GPS is now turned off.

To turn GPS on we to add "gps": true in the local_config

Changed on all but Smartparcs 1.3


in /login Redirect to /dashboard if user logged in

if user logged in and request /login, then redirect her to /dashboard

@pharzam , complate this issue

@4s9h4r There are two bugs, that I quick fix them
Any way please review commit  # 812e438 & # 3692551
Thank you


Rake task to reslug a Person

This rake task can be used to reslug a Person instance:
$ bundle exec rake reslug:person["old-slug","new-slug"]

It will do the following:

Update the slug of the instance in the database
Re-index the person with the new slug
Republish the person to the Publishing API with the new slug
Publish a "redirect" content_item to redirect the old slug to the new
Re-index all dependent documents (published news articles and speeches)

Trello: https://trello.com/c/HG019ljy/215-5-create-rake-task-to-reslug-people

:+1:


added postman model for java and a directory for other implmentations…

I believe this is ready to go

My only suggestion would be to add a line to either/both the home readme and the model directory readme suggesting that people could contribute their own model implementations. But otherwise, this looks good to me.


BrowserStack service support

Also includes small refactoring that allows to link the NPM module.

Hi,
Thanks for this... but Moonraker already supports Browserstack / Saucelabs etc via the normal remote webdriver connection, you just need to include your user / key in the browser capabilities (along with the browser configurations they support) in the config:
Browserstack:
"seleniumServer": "http://hub.browserstack.com/wd/hub",

  "browser": {
    "browserstack.user": "USERNAME",
    "browserstack.key": "KEY",
    "browserName": "Safari",
    "browser_version": "8.0",
    "os": "OS X",
    "os_version": "Yosemite",
    "resolution": "1920x1080"
  }

Saucelabs:
"seleniumServer": "http://ondemand.saucelabs.com:80/wd/hub",

  "browser": {
    "username": "USERNAME",
    "accessKey": "KEY",
    "browserName": "safari",
    "version": "8.0",
    "platform": "OS X 10.10"
  }

I'm not sure what benefits the dependency browserstack-webdriver brings, but its not had any activity since May 2014 and seems to be using an older version of selenium-webdriver (2.40.0)..

@dannyjhall I haven't realise that, that's awesome!
Could be this useful documentation added to README.md?

@vectart Absolutely! I'll make sure its updated with these examples.

@dannyjhall Wonderful, thank you very much!


Generate scripts do not work in Cygwin on Windows 10

Arrow keys do not respond and Ctrl-C will not properly stop the process.

Duplicate #1975


2024.08.0 array slicing does not preserve masks

Describe the issue:
Since dask 2024.8.0, slicing a masked array does not preserve the mask.
Minimal Complete Verifiable Example:
import numpy as np
import dask.array as da

arr = np.ma.array(range(8), mask=[0, 0, 1, 0, 0, 1, 0, 1])
darr = da.from_array(arr, chunks=(4, 4))

print(arr[[2, 6]])
print(darr[[2, 6]].compute())

Output with 2024.8.0:
[-- 6]
[2 6]

This works as expected  with 2024.7.0:
[-- 6]
[-- 6]

Anything else we need to know?:
I suspect this line may be at least part of the problem
https://github.com/dask/dask/blob/1ba9c5bf9d0b005b89a04804f29c16e5f0f2dadf/dask/array/_shuffle.py#L190
np.concatenate does not preserve masks, although there is an open PR to change that: https://github.com/numpy/numpy/pull/22913.  For masked arrays there is np.ma.concatenate.
I have not been able to test any further because my internet connection is currently flakey and my attempt to make a dev environment failed.
Environment:

Dask version: 2024.8.0
Python version: 3.12.5
Operating System: Ubuntu
Install method (conda, pip, source): conda

Thanks for your report. I put up a pr to fix. Generally, we don't have much if any test coverage for masked arrays, so that can be a bumpy ride


What magic is applied to Binding.Path property so it is default?

I'm trying to create a custom extension (localization from a server-side database).
The goal:
<AppBarButton Label="{l:Text TextId=About}" Click="{x:Bind About_Click}"/>

I tried:
    /// <summary>
    /// Provides a localized string for UI.
    /// </summary>
    [MarkupExtensionReturnType(ReturnType = typeof(string))]
    public class TextExtension : MarkupExtension
    {
        #region Properties

        /// <summary>
        /// Text ID to show.
        /// </summary>
        public string TextId { get; set; }

        #endregion

        #region Init and clean-up

        public TextExtension()
        {
            // Do nothing
        }

        public TextExtension(string textId)
        {
            TextId = textId;
        }

        #endregion

        #region Main functionality

        protected override object ProvideValue()
        {
            return TextId;
        }

        #endregion
    }

But having the parameterized constructor does not seem to help, I get an error:
XamlCompiler error WMC0610: The XAML Binary Format (XBF) generator reported syntax error '0x09d7'

So I assume there is a class or property attribute. But I can't find the source code for Binding markup extension. Can you help me out here?

@MikeHillberg Can you weigh in here?

Bonus question - how do I force the app to redraw when the user changes the language?

Correct, support for parameterized constructors isn't currently on the radar. @mc0re is the motivation syntactic cleanliness, or is there some kind of desired functionality that requires initialization of the markup extension's state to happen in the constructor and which can't be equivalently done via properties that are set by the markup and then read in the extension's ProvideValue() implementation?

@alwu-msft, It's the desire to have a shorter code :-)  So in short, one shouldn't expect that feature any time soon.


Tani's Submission

IM OPTING INN

opting in for the prizwe

forgot to opt in my bad. made a new one


Avoid CVE-2021-30130.

See: https://github.com/advisories/GHSA-vf4w-fg7r-5v94

@singpolyma  is there something I can do to help merging this PR ?

Maybe I don't understand how composer constraints work, but does this actually fix anything? Won't composer get the latest version anyway unless you tell it to do otherwise?

it's more a "this way you can't , even by mistake,  install openpgp-php with a insecure dependencies"
i.e
day 1:
I install a lib that brings  as a deps  phpseclib  with "*" as a requirement and I get it as  the insecure version (as it was the latest of that time)
day 200:
I'm the "don't fix it if it's ain't broken kind of guy"  and so i prefer to add new library with the minimum of upgrade needed
-> without this , you will still stay with an insecure version
-> with this the user will have this lib upgraded

Won't composer get the latest version anyway unless you tell it to do otherwise?
Yes, if just your lib has this dependency.

Other lib: 2.0.0
Your lib: ^2.0 !=2.0.8
=> composer loads 2.0.0
Other lib: 2.0.0
Your lib: ^2.0.31
=> composer shows error and does not load insecure 2.0.0

Alright. I don't love putting wrong metadata on but I guess if it fixes bad practise probably no one is using such an old version anyway, and if they need to continue for some reason they can change it back themselves easily.


[SPARK-11042] [SQL] [BRANCH-1.5 TEST-ONLY] Add a mechanism to ban creating multiple root SQLContexts/HiveContexts in a JVM

https://issues.apache.org/jira/browse/SPARK-11042

This is a test-only PR. We will not merge it.

Merged build triggered.

Merged build started.

Merged build triggered.

Merged build started.

Test build #43576 has started for   PR 9077 at commit a888f42.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43574/
Test FAILed.

test this please

Merged build triggered.

Merged build started.

Test build #43577 has started for   PR 9077 at commit a888f42.

Test build #43576 has finished for   PR 9077 at commit a888f42.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43576/
Test FAILed.

Merged build finished. Test FAILed.

Test build #43577 has finished for   PR 9077 at commit a888f42.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43577/
Test FAILed.

test this please

Merged build triggered.

Merged build started.

Test build #43581 has started for   PR 9077 at commit a888f42.

test this please

Merged build triggered.

Merged build started.

Test build #43581 has finished for   PR 9077 at commit a888f42.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43581/
Test FAILed.

Merged build finished. Test FAILed.

Test build #43595 has started for   PR 9077 at commit a888f42.

Test build #43595 has finished for   PR 9077 at commit a888f42.

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

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43595/
Test PASSed.

Merged build finished. Test PASSed.


Fix(plugins): Support zeroes in interface numbers for range_expand

Change Summary
Support zeroes in interface numbers for range_expand

Related Issue(s)
Fixes issue where zeroes in interfaces got ignored. Gi1/0/1-2 resolved to [Gi1/1, Gi1/2].
Component(s) name
arista.avd.range_expand
Proposed changes

Check that values are not None instead of boolean checks.

How to test

Added test case to pytest (failed until fix was applied)
Refactored tests to be better.

Checklist
User Checklist

N/A

Repository Checklist

[x] My code has been rebased from devel before I start
[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation and documentation have been updated accordingly.
[x] I have updated molecule CI testing accordingly. (check the box if not applicable)

LGTM from my point of view


REVEALER_preprocess command line example doesn't run without modifications/REVEALER_preprocess.py doesn't pass col_sample/col_class/col_genename to produce_mutation_file

Although --col_sample, --col_class, and --col_genename are being parsed as arguments, these values aren't being passed to produce_mutation_file().
I added lines like:
if args[ 'col_sample' ] != None:
col_sample = args[ 'col_sample' ]
else:
col_sample = 'Tumor_Sample_Barcode'
to the argument parsing, where the default values matched the default arguments defined in produce_mutation_file().
I then added lines like
...
col_sample = col_sample,
....
to the produce_mutation_file() call sites.
With these changes, REVEALER_preprocess.py seems happy with the input described in the example.
The previous error message when these values weren't passed was a rather unhelpful message from the pandas package:
KeyError: "Passing list-likes to .loc or [] with any missing labels is no longer supported. The following labels were missing: Index(['Hugo_Symbol', ....], dtype='object').
I might suggest that a nice user-friendly error (e.g. 'Hugo_Symbol' is not a column in the input_file.) would be helpful here in the case that users mistype a column name.

Hi @cdputnam,
Thank you so much for suggestions!
I will work on improvement for user interaction and debugging once I finish all finals.
Best,
Yoshii

Hi @cdputnam
Sorry for the late update. It was happening because the incorrect file was updated. Now the whole thing is updated with the proper test function. README is also updated for better instruction now!
Would you like to give it a try again?
Best,
Yoshii


Db2 Operator

Signed-off-by: Prabhat Dubey<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

New Submissions

[ ] Does your operator have nested directory structure?
[ ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Is your submission signed?

Updates to existing Operators

[ ] Is your new CSV pointing to the previous version with the replaces property?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Submit operators to both upstream-community-operators and community-operators at once
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

@prabhatdubey1, I see that you created pull request for different changes and probably deleted previous branches. Please submit only one pull request for kubernetes-operator and openshift-operator and stay with one pull request until it is merged. Will you be so kind and delete all useless pull requests? Thanks you very much


NFTs on my profile dont load automatically

What happened?
When i revisit my profile the collections etc don’t load
Please reproduce in steps
/
Expected Behavior
/
What browsers are you seeing the problem on?
Firefox
Are you logged in?
Yes
At which address did you encounter bug?
kodadot.xyz
Screenshots
Paste from your clipboard or upload screenshots/video
https://user-images.githubusercontent.com/92786519/174310852-7b416bf9-bc71-4bfb-b07b-78f80ebf4213.mov
Relevant log output
Uncaught (in promise) Error: Network error: NetworkError when attempting to fetch resource.
    NuxtJS 124
da68234.modern.js:1:2600410
2022-06-17 15:43:44          API-WS: disconnected from wss://kusama.api.onfinality.io/public-ws: 1001:: Going Away da68234.modern.js:1:1877867
[API] disconnected 1538a12.modern.js:1:778475
Loading failed for the <script> with source “https://static.cloudflareinsights.com/beacon.min.js”.  (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 504.

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 504.
7
Uncaught (in promise) Error: Network error: NetworkError when attempting to fetch resource.
    NuxtJS 124
da68234.modern.js:1:2600410
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 504.
2
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).
4
Error Network error: NetworkError when attempting to fetch resource. 2 da68234.modern.js:1:2692397
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).

Uncaught (in promise) Error: Network error: NetworkError when attempting to fetch resource.
    NuxtJS 124
da68234.modern.js:1:2600410
Uncaught (in promise) Error: Network error: NetworkError when attempting to fetch resource.
    NuxtJS 124
da68234.modern.js:1:2600410
Uncaught (in promise) Error: Network error: NetworkError when attempting to fetch resource.
    NuxtJS 124
da68234.modern.js:1:2600410
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).

Uncaught (in promise) Error: Network error: NetworkError when attempting to fetch resource.
    NuxtJS 92
da68234.modern.js:1:2600410
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).

Uncaught (in promise) Error: Network error: NetworkError when attempting to fetch resource.
    NuxtJS 124
da68234.modern.js:1:2600410
Uncaught (in promise) Error: Network error: NetworkError when attempting to fetch resource.
    NuxtJS 124
da68234.modern.js:1:2600410
Uncaught (in promise) Error: Network error: NetworkError when attempting to fetch resource.
    NuxtJS 87
da68234.modern.js:1:2600410
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 504.

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).

Uncaught (in promise) Error: Network error: NetworkError when attempting to fetch resource.
    NuxtJS 124

Payment link for reward
https://kodadot.xyz/transfer/?target=<My_Kusama_Address_check_https://github.com/kodadot/nft-gallery/blob/main/CONTRIBUTING.md#creating-your-ksm-address>
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Seems like CORS issue on SubSquid?
What's your URL to debug?
Can you still replicate it? Want to know if the error still occurs.
Is it happening on https://beta.kodadot.xyz as well?
WFM https://kodadot.xyz/rmrk/u/CuHWHNcBt3ASMVSJmcJyiBWGxxiWLyjYoYbGjfhL4ovoeSd

Apparently it works now on both beta and kodadot.xyz
Interesting 🗡
Anyway, when i posted this, it was after replication, so not one time thing tho. Let’s see if it comes back

Hello darkness my old friend

log
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 504.
15
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).
Error: Network error: NetworkError when attempting to fetch resource.
NuxtJS 6
81b5587.modern.js:1:70664
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).
error Error: Network error: NetworkError when attempting to fetch resource.
NuxtJS 6
da68234.modern.js:1:942157
error Error: Network error: NetworkError when attempting to fetch resource.
NuxtJS 6
da68234.modern.js:1:942157
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).
5
error Error: Network error: NetworkError when attempting to fetch resource.
NuxtJS 6
da68234.modern.js:1:942157
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).
4
Error Network error: NetworkError when attempting to fetch resource. da68234.modern.js:1:2692397
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).
4
Uncaught (in promise) Error: Network error: NetworkError when attempting to fetch resource.
NuxtJS 6
9 da68234.modern.js:1:2600410

Backend (graphql) endpoint crash

This is coming up now, same issue
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 502.
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 502.
2
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 502.
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 502.
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 502.
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 502.
2
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 502.
2
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 502.
2
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 502.
2
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 502.
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).
Error: Network error: NetworkError when attempting to fetch resource.
NuxtJS 6
81b5587.modern.js:1:70664
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).
error Error: Network error: NetworkError when attempting to fetch resource.
NuxtJS 6
da68234.modern.js:1:942157
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).
error Error: Network error: NetworkError when attempting to fetch resource.
NuxtJS 6
da68234.modern.js:1:942157
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).
error Error: Network error: NetworkError when attempting to fetch resource.
NuxtJS 6
da68234.modern.js:1:942157
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).
2
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).
3
Uncaught (in promise) Error: Network error: NetworkError when attempting to fetch resource.
NuxtJS 6
3 da68234.modern.js:1:2600410
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).
Uncaught (in promise) Error: Network error: NetworkError when attempting to fetch resource.
NuxtJS 6
4 da68234.modern.js:1:2600410
Error Network error: NetworkError when attempting to fetch resource. da68234.modern.js:1:2692397
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://app.gc.subsquid.io/beta/rubick/006/graphql. (Reason: CORS request did not succeed). Status code: (null).
2
Uncaught (in promise) Error: Network error: NetworkError when attempting to fetch resource.
NuxtJS 6

this seems to be a recuring problem, not directly connected to the profile, but in general, subsquid / indexer keeps having crashes. I've added the research label, if anybody feels like digging around and finding out why does this keep happening, it would be great

We've cut limits to 450 recently, observing if it would happen again.

#3287

okay, just noticed this cors error is for rubick while I'm on bsx so perhaps this is more related to

https://github.com/kodadot/nft-gallery/issues/3364

Meanwhile solved by removing queries.
Queries needs to have refactor

#3426


The breaker is not destroy leaves

the breaker is not destroy leaves
1.21.1-NeoForge_21.1.22
breakerplacer-1.0.1+1.21
Sinytra Connector-2.0.0-beta.2+1.21.1
Forgified Fabric API-0.102.0+2.0.12+1.21.1

This bug happens because the block is only destroyed when the Breaker is able to get items from the block's loot table. As leaves have a randomized chance of giving items normally, they are not destroyed unless that randomized chance is triggered.
This will be fixed in the next version of the mod. Thank you for reporting it.

Bug has hopefully been fixed in version 1.0.2+1.21. The mod now checks the tool's capabilities against the target block's hardness and takes that into account as well when deciding whether the block can be broken.
Please let me know if you find any other strange behaviour. Thank you!
https://github.com/user-attachments/assets/b115b3ec-d5f4-403a-a4c0-b23f6775c19f
  /**
   * miningSpeed > 0.95F ensures all hand-breakable items are breakable
   * miningSpeed >= blockHardness ensures the correct tools are used for harder-than-hand-breakable blocks
   **/
  public boolean canBreakBlock(ItemStack stack, CachedBlockPosition cachedPos) {
    // Get target block's information from cached position
    BlockState blockState = cachedPos.getBlockState();
    BlockPos blockPos = cachedPos.getBlockPos();
    WorldView world = cachedPos.getWorld();

    // Check if the item is a tool and get its mining speed
    float miningSpeed = stack.getMiningSpeedMultiplier(blockState);

    // Check the block's hardness
    float blockHardness = blockState.getHardness(world, blockPos);

    // Determine if the tool can break the block
    boolean canBreak = miningSpeed > 0.95F && miningSpeed >= blockHardness;

    // Additional check for specific tool materials if needed
    boolean isCorrectTool = stack.isSuitableFor(blockState);

    return canBreak || isCorrectTool;
  }

A by-product of this method is that blocks such as wooden logs can now only be broken with a wooden axe or greater, as their hardness is 2.0. I think this is an acceptable drawback, but if any outlandish examples are found please let me know.


Render the products in "Shop By Category" section dynamically

Is your feature request related to a problem? Please describe.
Currently the products are rendered like this:

Describe the solution you'd like
I would like to render the products dynamically .
Describe alternatives you've considered
No response
Additional context
No response

Can I work on this one?

Hey @Adithya-Sr  Thanks for opening the issue. Go ahead!


How to get line information and file path of source code after processing?

Hello, author
After I use command joern-parse /src/directory and joern-export --repr cpg14 --out outdir to dump all cpgs of source codes in /src/directory to outdir. For each .dot file, it's text is like
digraph "main" {
"3074457345618258674" [label = "(METHOD,main)" ]
"3074457345618258700" [label = "(METHOD_RETURN,int)" ]
"3074457345618258675" [label = "(PARAM,int argc)" ]
"3074457345618258676" [label = "(PARAM,char *argv[])" ]
"3074457345618258696" [label = "(printf,printf(\"What is the meaning of life?\n\"))" ]
"3074457345618258698" [label = "(exit,exit(0))" ]
"3074457345618258679" [label = "(<operator>.logicalAnd,argc > 1 && strcmp(argv[1], \"42\") == 0)" ]
"3074457345618258691" [label = "(fprintf,fprintf(stderr, \"It depends!\n\"))" ]
"3074457345618258694" [label = "(exit,exit(42))" ]
"3074457345618258680" [label = "(<operator>.greaterThan,argc > 1)" ]
"3074457345618258683" [label = "(<operator>.equals,strcmp(argv[1], \"42\") == 0)" ]
"3074457345618258684" [label = "(strcmp,strcmp(argv[1], \"42\"))" ]
"3074457345618258685" [label = "(<operator>.indirectIndexAccess,argv[1])" ]
  "3074457345618258675" -> "3074457345618258700"  [ label = "DDG: argc"]
  "3074457345618258676" -> "3074457345618258700"  [ label = "DDG: argv"]
  "3074457345618258680" -> "3074457345618258700"  [ label = "DDG: argc"]
  "3074457345618258679" -> "3074457345618258700"  [ label = "DDG: argc > 1"]
  "3074457345618258684" -> "3074457345618258700"  [ label = "DDG: argv[1]"]
  "3074457345618258683" -> "3074457345618258700"  [ label = "DDG: strcmp(argv[1], \"42\")"]
  "3074457345618258679" -> "3074457345618258700"  [ label = "DDG: strcmp(argv[1], \"42\") == 0"]
  "3074457345618258679" -> "3074457345618258700"  [ label = "DDG: argc > 1 && strcmp(argv[1], \"42\") == 0"]
  "3074457345618258691" -> "3074457345618258700"  [ label = "DDG: fprintf(stderr, \"It depends!\n\")"]
  "3074457345618258694" -> "3074457345618258700"  [ label = "DDG: exit(42)"]
  "3074457345618258696" -> "3074457345618258700"  [ label = "DDG: printf(\"What is the meaning of life?\n\")"]
  "3074457345618258698" -> "3074457345618258700"  [ label = "DDG: exit(0)"]
  "3074457345618258691" -> "3074457345618258700"  [ label = "DDG: stderr"]
  "3074457345618258674" -> "3074457345618258675"  [ label = "DDG: "]
  "3074457345618258674" -> "3074457345618258676"  [ label = "DDG: "]
  "3074457345618258674" -> "3074457345618258696"  [ label = "DDG: "]
  "3074457345618258674" -> "3074457345618258698"  [ label = "DDG: "]
  "3074457345618258680" -> "3074457345618258679"  [ label = "DDG: 1"]
  "3074457345618258680" -> "3074457345618258679"  [ label = "DDG: argc"]
  "3074457345618258683" -> "3074457345618258679"  [ label = "DDG: 0"]
  "3074457345618258683" -> "3074457345618258679"  [ label = "DDG: strcmp(argv[1], \"42\")"]
  "3074457345618258675" -> "3074457345618258680"  [ label = "DDG: argc"]
  "3074457345618258674" -> "3074457345618258680"  [ label = "DDG: "]
  "3074457345618258676" -> "3074457345618258683"  [ label = "DDG: argv"]
  "3074457345618258674" -> "3074457345618258683"  [ label = "DDG: "]
  "3074457345618258674" -> "3074457345618258691"  [ label = "DDG: "]
  "3074457345618258674" -> "3074457345618258694"  [ label = "DDG: "]
  "3074457345618258676" -> "3074457345618258684"  [ label = "DDG: argv"]
  "3074457345618258674" -> "3074457345618258684"  [ label = "DDG: "]
  "3074457345618258679" -> "3074457345618258694"  [ label = "CDG: "]
  "3074457345618258679" -> "3074457345618258691"  [ label = "CDG: "]
  "3074457345618258680" -> "3074457345618258685"  [ label = "CDG: "]
  "3074457345618258680" -> "3074457345618258683"  [ label = "CDG: "]
  "3074457345618258680" -> "3074457345618258684"  [ label = "CDG: "]
}

So I wonder given a .dot file. Could I get the source code file path corresponding to the dot file, and line number corresponding to each node in the CPG?  Because the line number infomation and file path are quite important to my task.

This is currently not directly supported (as an API call or something similar).
The actual implementation for the String representation of nodes for printing to .dot is here:
https://github.com/ShiftLeftSecurity/codepropertygraph/blob/master/semanticcpg/src/main/scala/io/shiftleft/semanticcpg/dotgenerator/DotSerializer.scala#L41
The file name of the current method (method.file.name) you want to print the .dot file for could be retrieved here:
https://github.com/ShiftLeftSecurity/codepropertygraph/blob/master/semanticcpg/src/main/scala/io/shiftleft/semanticcpg/dotgenerator/DotSerializer.scala#L33
So you could adapt this particular lines of code there, build codepropertygraph locally (sbt publishLocal) and use that version to build joern locally as well.

The dot generation was rewritten a few times, the issue could be outdated. I am closing it for now, please re-open it, if you still have questions.


feat: add 'remove' method to useSessionStorage

Description

Adds missing remove feature on session storage hook.
Feature was already available for local storage hook.
Adds tests to session storage hook.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as before)

Checklist

[X] Read the Contributing Guide
[X] Perform a code self-review
[] Comment the code, particularly in hard-to-understand areas
[X] Add documentation
[X] Add hook's story at Storybook
[X] Cover changes with tests
[X] Ensure the test suite passes (yarn test)
[X] Provide 100% tests coverage
[X] Make sure code lints (yarn lint). Fix it with yarn lint:fix in case of failure.
[X]Make sure types are fine (yarn lint:types).

Please release ;)


:robot: triggering CI on branch 'release-next' after synching from upstream/main

OCF Webhook is merging this PR

OCF Webhook is merging this PR

OCF Webhook is merging this PR

OCF Webhook is merging this PR

OCF Webhook is merging this PR


fix escaping

Description
The escaping is incorrect for the Windows task recipe when constructing the command for the windows_task resource.

There are superfluous escape backslash (\) characters before the ", just one escape suffices.
The > and & characters are special characters that also need to be escaped with ^.  See http://www.robvanderwoude.com/escapechars.php

Issues Resolved
This PR resolves #417
@KirkMartinez had already resolved the issue manually, this PR just incorporates his fix.
       Recipe: chef-client::task
         * directory[C:/chef/run] action create (up to date)
         * directory[C:/chef/cache] action create (up to date)
         * directory[C:/chef/backup] action create (up to date)
         * directory[C:/chef/log] action create (up to date)
         * directory[C:/chef] action create (up to date)
         * log[debug client_cmd] action write

         * windows_task[chef-client] action create

       Recipe: chef-client::config
         * file[C:/chef/log/client.log] action create[2016-09-13T11:35:04-07:00] WARN: Mode 640 includes bits for the owner, but owner is not specified
       [2016-09-13T11:35:04-07:00] WARN: Mode 640 includes bits for the group, but group is not specified
        (up to date)
         * template[C:/chef/client.rb] action create (up to date)
         * directory[C:/chef/client.d] action create (up to date)
         * ruby_block[reload_client_config] action nothing (skipped due to action :nothing)
         * ruby_block[reload_client_config] action create
           - execute the ruby block reload_client_config

       Running handlers:
       Running handlers complete

This has been tested with TK on Windows 2012R2.
Check List

[ ] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[x] New functionality includes testing.
[x] New functionality has been documented in the README if applicable
[x] The CLA has been signed. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

I think there is still a problem.  I found that the command I used created a task, but it was not correct.  It was not set to run as SYSTEM; the /RU and /RL switches were included in the command to run.  I  ended up using single-quotes around the command passed to cmd, and confirmed that actually works:
schtasks /CREATE /TN "chef-client" /F /SC "minute" /MO "30" /ST "21:25" /TR "cmd /c 'C:/opscode/chef/bin/chef-client -L C:/chef/client.log -c C:/chef/client.rb -s 300 > NUL 2>&1'" /RU "SYSTEM" /RL "HIGHEST"

@KirkMartinez @tas50 Yes, this PR takes that into account and everything in the Task is set up correctly.  Take a look at a fresh TK Windows 2012R2 instance with the changes from this branch.

Thanks @jeremymv2


correctly stop the driver in the event of an error that happens before a connection is established

when disconnected, the old implementation of abort() didn't do the following:

properly forward a Error() message to the framework (the cause)
close driver.stopCh

/cc @spacejam

Please add to the commit msg why this "stop" call is correct and the old one isn't.

added details to commit message and force-pushed. not sure why travis-ci hasn't bothered to build this yet.

AFAICT lgtm

lgtm

reactivated the travis-ci hooks for this project, and closed/re-opened this PR to trigger a build

looks like failing tests are unrelated flakes. :ship:

@jdef travis ci tells the master build (https://travis-ci.org/mesos/mesos-go/builds/89106214) is broken since this PR, PTAL

Pretty sure these are test flakes
On Fri, Nov 6, 2015 at 11:01 AM, Sergiusz Urbaniak<EMAIL_ADDRESS>
wrote:

@jdef https://github.com/jdef travis ci tells the master build (
https://travis-ci.org/mesos/mesos-go/builds/89106214) is broken since
this PR, PTAL
—
Reply to this email directly or view it on GitHub
https://github.com/mesos/mesos-go/pull/200#issuecomment-154448340.


Add missing docker build for cosmovisor-wrapped osmosis binary image

What is the purpose of the change
This PR adds the strategy to build docker images with cosmovisor inside wrapping osmosis binary.
Testing and Verifying
This image has been released to a development docker registry and has been tested in our node deployments.

LGTM


How to display Blog Content?

Thank you for putting this together!
My understanding of Nuxt is not great but growing as I tinker with it.

How would I display individual blog posts located at content/blog/post-1.md?
A question about image paths. This works in development ![vectorme](../public/assets/images/vectorme.png) but is broken when uploaded to Netlify.

Please forgive my newb questions.

That would be mapped to /blog/post-1, you can read more here.
In Nuxt, public directory is mapped to /, so you need to change ![vectorme](../public/assets/images/vectorme.png) into ![vectorme](/assets/images/vectorme.png).


Import PC/SC-Lite 1.9.3

This commit also drops the patch that's not needed anymore,
as it went into the upstream release.

The only files I modified manually were:

third_party/pcsc-lite/README.google


filter.nostr.wine doesn't work for global

Describe the bug
Page is stuck in a loading state when selecting filter.nostr.wine as the relay for global.

Global feed works fine with filter.nostr.wine on Damus, so I think the bug is in Snort.
To Reproduce
View global feed and select filter.nostr.wine as the relay. If you don't have filter.nostr.wine setup as one of your relays, you can go here for instructions on how to set that up.

Seems like someone fixed this. It's working now.


New Crowdin updates

Not sure what happened with the Crowdin translations here. I asked over at https://community.crowdin.com/t/skip-untranslated-strings-not-working-anymore/2544


Fix for Invalid Date throwing error 500

Overview

Resolves #111
Adds a check to ensure a valid date and valid time is entered when creating a new ElectionSession

Unit Tests Created

Adds a corresponding unit test that checks cases for this for start and end dates and start and end times.

Steps to QA

Try creating a new ElectionSession with invalid start date/end date/start time/end time.
You should get invalid messages for Enter a valid date. for the dates, Enter a valid time. for the times. As well, at the top you should get an overall message of The ElectionSession must have a valid start and end time.
If the dates and times actually exist then the ElectionSession should create successfully.
Play around, see if I overlooked anything.

This is really minor and I don't think it's related to the ticket, but do you mind changing the helper text to:
When does your Election Session finish? (YYYY-MM-DD and HH:MM:SS) or some other message that includes the format for date and time. Ditto for Election start time


Check for require when binding commonjs

Previously, the binder didn't check for a declared function named 'require' when binding require in JS. It unconditionally treated 'require' as the commonjs function, even when a local function named 'require' existed and even in ES modules. Now, the binder checks for a local function named require and avoids binding in that case.
Both before and after, actually importing the module causes the checker to issue an error saying that top-level functions named 'require' are illegal. But this error doesn't show up until you've imported from the module, so you won't notice it in the editor, where JS errors are most useful.
Within-binder checks for declared functions are dependent on binding order, but function binding simulates hoisting by binding all function declarations first, so it should be pretty reliable.
Fixes #48726

Note: The "'require' is reserved by the compiler" error has to do with emit, so it shouldn't be issued on any .js file. That's a separate issue though.

Will this end up breaking code that relied on the fact that we treat a function named "require" specially? I know that yarn plugins are passed a require function as an argument (so you can require things lazily / get the same dep as the executing yarn version), and having require recognized as the require function is helpful there.

Similar question to Jake’s: does this check affect ambient declarations? Both @types/node and @types/webpack-env declare require.

@andrewbranch No: lookupForSymbolName doesn't look in the global scope, so it won't affect files that reference those types. However, a declare function require() in the same file would block require use there, even though that's not legal JS syntax.
@jakebailey Yes: based on the test noCrashOnParameterNamedRequire. While technically correct, the assumption that require behaves like commonjs require is really useful for understanding code most of the time.
ES modules would be less likely to have a require passed to them, I think. Do you think this change makes sense if restricted to ES modules? I went ahead and did that, but if you can access require in an ES module (and if people commonly do), then even that probably doesn't make sense.
I looked at a couple of yarn plugins but they were written in TS, and I didn't see any require passed around.
Two more things:

This is a common pattern in bundled code too, but the references are to other regions in the same bundled file, so we've never been able to resolve them unless the bundle is in the same directory as the source.
I can't figure out how to trigger the "please don't name your function require error in the editor." Improving the usability of that seems to be a better alternative fix at this point.

I looked at a couple of yarn plugins but they were written in TS, and I didn't see any require passed around.

My example is in a private repo so I can't link it here, but here is the example from the yarn docs: https://yarnpkg.com/advanced/plugin-tutorial/#writing-our-first-plugin

Closing this after various discussions. I think a warning against writing a function named require is better.


🩹 OSIDB-2562 Hide source column

Checklist:

[x] Linting passed
[x] Type checks passed
[x] Tests suite passed
[x] Commits consolidated
[x] Changelog updated
[x] Test cases added/updated
[X] Jira ticket updated

Summary:
Temporary hiding the Source column on Flaw queues and renaming Source field labels to CVE Source:

The current value of the source field is where the flaw was reported. This information is not very valuable on this page. Instead, we need to track what system the flaw was created in (SNOW, Assembler, etc; ). Today, we only get flaws from assembler or a direct users. So we should hide the source column on Index page for now. When we do an integration with SNOW, we could then expose the field with more meaningful data.

Additionally, we should rename the source field on the CVE page to 'CVE Source' so that it is more clear what the field represents.

Changes:

Hidden Source column from IssueQueue and IssueQueueItem
Renamed Source field label to CVE Source at FlawForm
Renamed Source field to CVE Source at AdavancedSearch
Updated FlawForm tests with new CVE Source label

Considerations:

CVE Source remains editable on FlawForm
CVE Source is still a valid search field for AdvancedSearch
After SNOW integration review possible new values and field behavior (may be static and auto-generated)

Looks good, only weak request I have is: if commenting the code instead of deleting, say why, because it might not be clear when the right time to delete the comments is

Looks good, only weak request I have is: if commenting the code instead of deleting, say why, because it might not be clear when the right time to delete the comments is

I like this process--keeps my 'delete 'em all (let the gc sort em out)' tendencies in check


fix if route not found for partial

Aims to fix the #1920.

@marvinhagemeister, I think this is done by #2072.


Verify why double unwrapping and pointers are used

https://github.com/farcaller/zinc/commit/8900158be89ecc10059effca1583d30b5d968e84 introduces some strange syntax.

Usage of pointers was fixed as a side-effect of 2f15d444
I've gone through and grok'd the double-unwrapping. It's because we have a Vec full of Option<Some>, so when you call vec.get(), you get &Option<Option<Some>> We unwrap only the first option, asserting that maybe_pin_index will be within the bounds of the Vec.

Since we're already panicking on the failure of the index dereference, we might as well just use the Index trait directly. I'll submit a PR that will make it a little more clear.


Questions about the test set 1000 images from CelebA-HQ dataset

I have tried to reproduce the results and observe that the given test images from the subset of the CelebA-HQ dataset are 100 images in total. However, according to the paper, it should include 1000 images. Could you upload the full 1000 image subset? Thank you.

Thanks for your interest！
We have renewed the demo test dataset (100 pics to 1000) for a broader evaluation, check it out! ^ ^

Thank you!


[IOS] [ENHANCEMENT] [NativeAnimated] Allow shadowOpacity and shadowRadius in NativeAnimated

Motivation
I want to animate shadowOpacity style property with Native Animated (useNativeDriver: true). This is useful for example in an ios-like navigation transition where the shadow fades in with the view that is sliding in from the side. Code comment for STYLES_WHITELIST says:
In general native animated implementation should support any numeric property that doesn't need to be updated through the shadow view hierarchy (all non-layout properties).
so I just added shadowOpacity (and shadowRadius too because why not?).
Test Plan
Before this change, setting shadowOpacity (or shadowRadius) to an AnimatedValue (with useNativeDriver: true) would throw the error: Style property 'shadowOpacity' is not supported by the native animated module.
After adding shadowOpacity (and shadowRadius), there is no error. The animation looks correct so it seems to be working. I also tried setting a ridiculously large shadowRadius and could see that working too.
Please advice on any further testing I should do.
Release Notes
[IOS] [ENHANCEMENT] [NativeAnimated] - Allow shadowRadius and shadowOpacity as NativeAnimated style properties.

Nice that it works without any changes! Do you know if shadowOffset also works? I guess not since it's an object, it might need some tweaks in native animated to support it.

@facebook-github-bot shipit

Yes it almost seemed too simple... Support for shadowOffset was addressed some time ago I think

@janicduplessis circle-ci has failed in test-android with something that I don't understand at all, doesn't seem related to this change. Am I expected to do something about this?


ARM OSX Migrator

continue PR https://github.com/conda-forge/r-maps-feedstock/pull/14

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.

@conda-forge-admin please rerender

As stated in PR https://github.com/conda-forge/r-maps-feedstock/pull/14 the issue seems to be related to the CPU type with R
If I understand everything correctly, the CI runs on an x86 machine and tries to cross-compile to OSX ARM. The maps package tries to build some lib called shlib using an R_HOME environment variable (see here) and this R_HOME seems to try to use some OSX ARM R version that of course does not run on x86

closes https://github.com/conda-forge/r-maps-feedstock/pull/14


[staging] boost: 1.81 -> 1.86

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Bisect says that 3aeb9755e933c27809782891cfbed1660894123e boost: 1.81 -> 1.86 broke pkgsi686Linux.boost build on staging as:
$ nix build --no-link -f. -L pkgsi686Linux.boost
...
gcc.compile.c++ bin.v2/libs/stacktrace/build/gcc-14/release/x86_32/threading-multi/visibility-hidden/from_exception.o
libs/stacktrace/build/../src/from_exception.cpp:170:2: error: #error On this platform memory leaks are possible if capturing stacktrace from exceptions is enabled and exceptions are thrown concurrently and libc++ runtime is used. Define `BOOST_STACKTRACE_LIBCXX_RUNTIME_MAY_CAUSE_MEMORY_LEAK` to suppress this error if the library would not be used with libc++ runtime (for example, it would be only used with GCC runtime). Otherwise, disable the boost_stacktrace_from_exception library build (for example by `./b2 boost.stacktrace.from_exception=off` option).
  170 | #error On this platform memory leaks are possible if capturing stacktrace from \
      |  ^~~~~

    "g++"   -fvisibility-inlines-hidden -fPIC -m32 -pthread -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden -march=i686  -DBOOST_ALL_NO_LIB=1 -DBOOST_COBALT_USE_STD_PMR=1 -DNDEBUG   -I"."  -c -o "bin.v2/libs/stacktrace/build/gcc-14/release/x86_32/threading-multi/visibility-hidden/from_exception.o" "libs/stacktrace/build/../src/from_exception.cpp"

...failed gcc.compile.c++ bin.v2/libs/stacktrace/build/gcc-14/release/x86_32/threading-multi/visibility-hidden/from_exception.o...

I looked into this a bit and I expect this to show up for other platforms as well. If you take a look at the code that produces the error: https://github.com/boostorg/stacktrace/blob/boost-1.86.0/src/from_exception.cpp#L162-L185
You will find that none of this should be evaluated if BOOST_STACKTRACE_ALWAYS_STORE_IN_PADDING is set to 0. That value of that is set at https://github.com/boostorg/stacktrace/blob/boost-1.86.0/src/exception_headers.h#L9-L13.
Does stdenv.hostPlatform.useLLVM imply that libcxx is used?
If yes we can set boost.stacktrace.from_exception=off in that case and define=BOOST_STACKTRACE_LIBCXX_RUNTIME_MAY_CAUSE_MEMORY_LEAK otherwise.
If not then I don't know.

Yes, at least by default (though stdenv.cc.libcxx != null might be a bit more robust):
# on x86_64-linux:
nix-repl> stdenv.cc.libcxx
null

nix-repl> pkgsLLVM.stdenv.cc.libcxx
«derivation /nix/store/v2n8l6z08s5pj1k2h72b5kv9gdws34y3-libcxx-x86_64-unknown-linux-gnu-18.1.8.drv»

At least building pkgsLLVM.re2c results in libcxx:
$ nix build -f. pkgsLLVM.re2c
$ lddtree result/bin/re2c | fgrep c++
    libc++.so.1 => /nix/store/vv1ml03vyvzk50y9sa53ip0dbg60mvsc-libcxx-x86_64-unknown-linux-gnu-18.1.8/lib/libc++.so.1
    libc++abi.so.1 => /nix/store/vv1ml03vyvzk50y9sa53ip0dbg60mvsc-libcxx-x86_64-unknown-linux-gnu-18.1.8/lib/libc++abi.so.1

innoextract build regressed in master. Proposed the fix as:

https://github.com/NixOS/nixpkgs/pull/367699

wesnoth build regressed in master. Proposed the fix to pin it to older version until there is an upstream support:

https://github.com/NixOS/nixpkgs/pull/367957


mutex

What version of Go are you using (go version)?

$ go version
go version go1.14.6 darwin/amd64

Does this issue reproduce with the latest release?
no
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/puzhengsong/Library/Caches/go-build"
GOENV="/Users/puzhengsong/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GONOPROXY="*.xiaoduoai.com,*.xiaoduotech.com"
GONOSUMDB="*.xiaoduoai.com,*.xiaoduotech.com"
GOOS="darwin"
GOPATH="/Users/puzhengsong/go"
GOPRIVATE="*.xiaoduoai.com,*.xiaoduotech.com"
GOPROXY="https://goproxy.cn,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/2y/drl9zw754xz3cjww8t4_jb7c0000gn/T/go-build741237267=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

in mutex.go
https://github.com/golang/go/blob/97b3ce430bb64fb6c8dfb244d400468932f2e984/src/sync/mutex.go#L207
if old>>mutexWaiterShift == 0 || old&(mutexLocked|mutexWoken|mutexStarving) != 0 { 				return 			}
can old&(mutexLocked|mutexWoken|mutexStarving) != 0 ==> old&mutexWoken != 0?
because the mutexLocked and mutexStarving is always 0 bit
What did you expect to see?
What did you see instead?

The state of old can change in further iterations of the loop
Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
For questions please refer to https://github.com/golang/go/wiki/Questions


Connect problem

Hi! Dear author,Ihave try to connect 2 devices as same settings. I only connect one device at a time.One of  them successful. It works very well.But the other one does not.Can you help me to fix it?Thanks a lot. The Android system version is 7.0. Sshd and Android tools are installed and running on this devices.

Can you provide me the full logs by click top-right "..." menu item "Show Scrcpy Logs"?

Can you provide me the full logs by click top-right "..." menu item "Show Scrcpy Logs"?

Thanks for your help.I try it but there is no button.I need install other version?Now is v2.2

Thanks for your help.I try it but there is no button.I need install other version?Now is v2.2.

Can you provide me the full logs by click top-right "..." menu item "Show Scrcpy Logs"?

Hello scrcpy v1.21
ACTION> Dismiss
Data: (null)
Error: Error Domain=NSPOSIXErrorDomain Code=60 "Operation timed out"
Time Remaining: 1.797693134862316e+308
Time Remaining: 1.797693134862316e+308
Time Remaining: 1.797693134862316e+308
Hello scrcpy v1.21
ACTION> Show Scrcpy Logs
Data: (null)
Error: Error Domain=NSPOSIXErrorDomain Code=60 "Operation timed out"
Time Remaining: 1.797693134862316e+308
Hello scrcpy v1.21
Time Remaining: 1.797693134862316e+308
Data: {length = 1, bytes = 0x53}
Error: (null)
CMD> adb get-serialno
DEBUG: Screensaver enabled
RET> [adb get-serialno] (1)
DEBUG: Device serial: emulator-5554
DEBUG: Using server: $TMPDIR/share/scrcpy/scrcpy-server
RET> Upload [/private/var/containers/Bundle/Application/853132A3-1075-42C1-94D0-869B34CC0CCC/App.app/scrcpy-server] => [$TMPDIR/share/scrcpy/scrcpy-server] (YES)
CMD> adb -s emulator-5554 push $TMPDIR/share/scrcpy/scrcpy-server /data/local/tmp/scrcpy-server.jar
RET> [adb -s emulator-5554 push $TMPDIR/share/scrcpy/scrcpy-server /data/local/tmp/scrcpy-server.jar] (1)
CMD> adb -s emulator-5554 reverse localabstract:scrcpy tcp:27183
RET> [adb -s emulator-5554 reverse localabstract:scrcpy tcp:27183] (0)
CMD> adb -s emulator-5554 shell CLASSPATH=/data/local/tmp/scrcpy-server.jar app_process / com.genymobile.scrcpy.Server 1.21 log_level=debug bit_rate=3000000 max_fps=60
RET> [adb -s emulator-5554 shell CLASSPATH=/data/local/tmp/scrcpy-server.jar app_process / com.genymobile.scrcpy.Server 1.21 log_level=debug bit_rate=3000000 max_fps=60] (1)
DEBUG: Interrupting socket
DEBUG: Server disconnected
DEBUG: Server terminated
ACTION> Show Scrcpy Logs
Can you give me some help?

Are you connecting two or more devices at the same time via the same ssh server?

Are you connecting two or more devices at the same time via the same ssh server?

No.Just one devices every time.The ssh server run in each Android devices.It work well on a vivo devices without PC.The ssh server and adb server run on the phone.I think the settings are correct.But it doesn’t work on a Samsung devices with same steps an settings.

Samsung devices work well on windows.

Are you connecting two or more devices at the same time via the same ssh server?

No.Just one devices every time.The ssh server run in each Android devices.It work well on a vivo devices without PC.The ssh server and adb server run on the phone.I think the settings are correct.But it doesn’t work on a Samsung devices with same steps and settings.

Can you execute adb devices on your Termux which installed on your Samsung phone?

Are you connecting two or more devices at the same time via the same ssh server?

No.Just one devices every time.The ssh server run in each Android devices.It work well on a vivo devices without PC.The ssh server and adb server run on the phone.I think the settings are correct.But it doesn’t work on a Samsung devices with same steps and settings.

Can you execute adb devices on your Termux which installed on your Samsung phone?

Then, try to execute adb -s emulator-5554 reverse localabstract:scrcpy tcp:27183 to see what happens.

adb -s emulator-5554 reverse localabstract:scrcpy tcp:27183

~ $ adb devices
List of devices attached
emulator-5554   device
~ $ adb -s emulator-5554 reverse localabstract:scrcpy tcp:27183
adb: error: more than one device/emulator
~ $
I think it’s Samsung device’s problem.It display more than one device.Actually it just one device.Your app work well.

It seems there are some known issues on adb reverse over tcpip. scrcpy's workaround is try to switch to adb forward https://github.com/Genymobile/scrcpy/issues/5
But, scrcpy iOS app have not adaptived with adb forward now. I'm planning to adaptive this.
As you said befor Samsung devices work well on windows, have you tried to connect your Samsung via tcpip but not usb and use scrcpy on windows?

It seems there are some known issues on adb reverse over tcpip. scrcpy's workaround is try to switch to adb forward Genymobile/scrcpy#5
But, scrcpy iOS app have not adaptived with adb forward now. I'm planning to adaptive this.
As you said befor Samsung devices work well on windows, have you tried to connect your Samsung via tcpip but not usb and use scrcpy on windows?

Yes,it work well on windows via tcpip not usb.Here are some logs.
scrcpy 1.21 https://github.com/Genymobile/scrcpy D:\scrcpy-win64-v1.21\scrcpy-server: 1 file pushed, 0 skipped. 9.3 MB/s (40067 bytes in 0.004s) adb.exe: error: more than one device/emulator ERROR: "adb reverse" returned with value 1 WARN: 'adb reverse' failed, fallback to 'adb forward' [server] INFO: Device: samsung SM-N935F (Android 8.0.0) INFO: Renderer: direct3d INFO: Initial texture: 1440x2560

Got it, it looks like it can be fixed by adb forward, I will try.

It seems there are some known issues on adb reverse over tcpip. scrcpy's workaround is try to switch to adb forward Genymobile/scrcpy#5
But, scrcpy iOS app have not adaptived with adb forward now. I'm planning to adaptive this.
As you said befor Samsung devices work well on windows, have you tried to connect your Samsung via tcpip but not usb and use scrcpy on windows?

Yes,it work well on windows via tcpip not usb.Here are some logs.
scrcpy 1.21 https://github.com/Genymobile/scrcpy D:\scrcpy-win64-v1.21\scrcpy-server: 1 file pushed, 0 skipped. 9.3 MB/s (40067 bytes in 0.004s) adb.exe: error: more than one device/emulator ERROR: "adb reverse" returned with value 1 WARN: 'adb reverse' failed, fallback to 'adb forward' [server] INFO: Device: samsung SM-N935F (Android 8.0.0) INFO: Renderer: direct3d INFO: Initial texture: 1440x2560

Got it, it looks like it can be fixed by adb forward, I will try.

Thanks for you help. Looking forward to good news.

Scrcpy.ipa.zip
Hi, can you try to use this version to connect your Samsung Android? And give me a feedback, thanks.

Probably Termux's ADB problem ,I have same problem.
I connect phone by wifiadb ip and specify device serial  wifiadb ip.
It is work fine.

Scrcpy.ipa.zip
Hi, can you try to use this version to connect your Samsung Android? And give me a feedback, thanks.

It work well with Force Adb Forward.It’s perfect!Thank you for your help.

You can try open wifiadb and specify device serial option emulator-5554 or wifiadb’s ip

I have try this ,it doesn’t work.Now the author fix it,it work well now.

Scrcpy.ipa.zip
Hi, can you try to use this version to connect your Samsung Android? And give me a feedback, thanks.

It work well with Force Adb Forward.It’s perfect!Thank you for your help.

Can you try to disable Force ADB Forward and connect again? I would like to know if the automatic fallback to adb forward is working.

It doesn’t work.I remember the tips as same as before version 2.3.Just like the pic on the top.I will try again next week.

Here is a screenshot,just like before.

Hi, @Sun930391 can you try this version with "Force ADB Forward" disabled? I want to check if I've fixed the issue that fallback to adb forward when adb reverse failed.

Hi, @Sun930391 can you try this version with "Force ADB Forward" disabled? I want to check if I've fixed the issue that fallback to adb forward when adb reverse failed.
Scrcpy.ipa.zip

It work well with "Force ADB Forward" disabled.I think you fixed it.Good job!👍

That's good, thanks for your feedback.

That's good, thanks for your feedback.

You’re welcome. Thank you for your hard work .I’m happy to do something for you.I have a new idea.The server option maybe pull down button.The history servers maybe saved.I can connect multiple devices faster.Now I need type the server address every time.

Add a button just like “Add Server” for multiple address .And I can choose a saved server address faster.This is my suggestion,maybe you have a better idea.

That's good, thanks for your feedback.

You’re welcome. Thank you for your hard work .I’m happy to do something for you.I have a new idea.The server option maybe pull down button.The history servers maybe saved.I can connect multiple devices faster.Now I need type the server address every time.

According to your needs, I strongly recommend that you copy the connect information into a URL scheme and add it to the home screen, so that you can switch between different mobile phone connections very quickly. You just need to fill in the information and click on the top-right menu ... then click Copy URL Scheme, and use the system app Shortcuts to add to home screen.

That's good, thanks for your feedback.

You’re welcome. Thank you for your hard work .I’m happy to do something for you.I have a new idea.The server option maybe pull down button.The history servers maybe saved.I can connect multiple devices faster.Now I need type the server address every time.

According to your requirement, I strongly recommend that you copy the connect information into a URL scheme and add it to the home screen, so that you can switch between different mobile phone connections very quickly. You just need to fill in the information and click on the top-right menu ... then click Copy URL Scheme, and use the system app Shortcuts to add to home screen.

I have try it.It’s really cool.I didn’t notice before.Thanks again.


Unexpected char

Hi, console says there are issues after copying all files into my Unity project.
Assets/Entitas/Documentation/dynsection.js(3,13); BCE0044: unexpected char: '&'.
Any idea?
Thanks.
I have an idea / suggestion / found a bug / have question / want to contribute.

Hi, remove documentation folder or move outside Assets folder

Correct. Only import the Entitas folder into Unity. Don't import other folders like Documentation or CodeGenerator


edx sandbox playbook failed

Hi, my deployment at Azure via oxa-tools occurs errors, but I can't sure how to resolve it.
TASK [notifier : Check if incommon ca is installed] ****************************
fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["test", "-e", "/usr/share/ca-certificates/incommon/InCommonServerCA.crt"], "delta": "0:00:00.002138", "end": "2019-06-16 20:42:49.302412", "failed": true, "rc": 1, "start": "2019-06-16 20:42:49.300274", "stderr": "", "stdout": "", "stdout_lines": [], "warnings": []}
...ignoring

TASK [notifier : Retrieve incommon server CA] **********************************
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "Failed to validate the SSL certificate for www.incommon.org:443. Make sure your managed systems have a valid CA certificate installed. You can use validate_certs=False if you do not need to confirm the servers identity but this is unsafe and not recommended. Paths checked for this platform: /etc/ssl/certs, /etc/pki/ca-trust/extracted/pem, /etc/pki/tls/certs, /usr/share/ca-certificates/cacert.org, /etc/ansible"}
	to retry, use: --limit @/oxa/configuration/playbooks/edx_sandbox.retry

How can I resolve it?
Thank you.
PS: I use master.fic

I found fixed information from edx:
https://github.com/edx/configuration/pull/5200
When it will be merged in this code base?
Thank you.

Hi @regionbbs,
Can you tell me which openedx version your are trying to install

I use v2.7 (from github's release record).
I found some errors from bootstrap.log...

@regionbbs
Have you managed to resolve this issue? This edX driving me crazy 😠. I finally deployed last week in test environment, and files and scripts are not useful today.
I getting the same error regarding InCommonServerCA.crt.
Thanks,

No, I am still waiting for team to resolve them...

I have tried to run onebox.sh, and got error:

But when I use bootstrap.sh -r mysql -e bvt to run, it can be done.
And I tried to run bootstrap.sh -r mongo -e bvt, and got error:

I can't find edx_mongo.yml at installation source.

I have used another vendor's solution to deploy openedx on azure.

I have tried both devstack and fullstack installation and it was successful without any errors except the certificate one. I have forwarded the certificate issue to the concerned team and will be fixed soon
Other than this there we no issues I got during installation. I am still trying to figure out what exactly caused this.

Can you share how do you test it? maybe I can help to reproduce or find root cause.
I run my deployment at Central US location.

I did the stamp deployment based on the documentation and not extra changes (without SSL, SSH cert and domain name). Powershell version above 3 and AzureCliVersion 2

My PowerShell version is also above 3 and AzureCliVersion 2.
Which location do you use?

Hi, my deployment at Azure via oxa-tools occurs errors, but I can't sure how to resolve it.
TASK [notifier : Check if incommon ca is installed] ****************************
fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["test", "-e", "/usr/share/ca-certificates/incommon/InCommonServerCA.crt"], "delta": "0:00:00.002138", "end": "2019-06-16 20:42:49.302412", "failed": true, "rc": 1, "start": "2019-06-16 20:42:49.300274", "stderr": "", "stdout": "", "stdout_lines": [], "warnings": []}
...ignoring

TASK [notifier : Retrieve incommon server CA] **********************************
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "Failed to validate the SSL certificate for www.incommon.org:443. Make sure your managed systems have a valid CA certificate installed. You can use validate_certs=False if you do not need to confirm the servers identity but this is unsafe and not recommended. Paths checked for this platform: /etc/ssl/certs, /etc/pki/ca-trust/extracted/pem, /etc/pki/tls/certs, /usr/share/ca-certificates/cacert.org, /etc/ansible"}
	to retry, use: --limit @/oxa/configuration/playbooks/edx_sandbox.retry

How can I resolve it?
Thank you.
PS: I use master.fic

Hi
About this issue
You can check this link to solve this issue.
https://github.com/edx/configuration/pull/5203/commits/cf991cb046532ab1ec7f96b4a9577d8ac0938130
Thanks

Yeah it is already under development, will update you soon

I made a successfully deployment after I made a bundle cert (include CA root cert, intermediate cert and server cert) and redeployed with original configuration.
You may make some notes about this at deployment instructions.
Thank you.

Just to update you guys, issue is resolved. We have merged the changes into master
For reference:
https://github.com/microsoft/edx-configuration/pull/514
thanks


Request: Sidebars

Would be great to have sidebars to use for admin dashboards.

@S4qib do you have a nice example to show what you have in mind?


Missing declaration file for module 'xstate'

I installed the latest version 1.2.1 to try xstate in a new project written in typescript and I'm getting an issue when importing something from the module.
I use this import statement as indicated in the README
import { Machine } from 'xstate';
But in the TS compiler output, I get "ERROR in src/app/app.machine.ts(1,25): error TS7016: Could not find a declaration file for module 'xstate'. '/home/stephane/Libertrip/ModelV2/node_modules/xstate/dist/xstate.js' implicitly has an 'any' type."
It seems the built library lacks a declaration file to allow imports of all members using the module name.
One possible workaround is to specify the path to the file declaring the member
import xstate from 'xstate/lib/index';
Then I gain access to xstate.Machine which is correctly typed.
For convenience, would it be possible to fix this?

This should work on the beta 2.0 version (releasing soon, in December): just npm install xstate@beta 😄


Deep link to live app from bcc media

done for app in v5.1.5. which is in pipeline.

guess the rest here is tvos

its done in tvOS


When this trigger triggers the pipeline?

I am not sure I understand tumbling trigger
When I create a pipeline afresh and create a trigger and publish, it works well
But, when I edit something in a pipeline and publish it, it does not work. Also, sometimes when i recreate/modify the trigger, this also doesn't trigger the pipeline

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

ID: 301444c9-ee60-645b-a5d9-9c8897704b54
Version Independent ID: b0c9414a-ee16-1cf5-8d04-89f64d001e94
Content: Create tumbling window triggers in Azure Data Factory
Content Source: articles/data-factory/how-to-create-tumbling-window-trigger.md
Service: data-factory
GitHub Login: @sharonlo101
Microsoft Alias: shlo

@Karishma-Tiwari-MSFT @MicahMcKittrick-MSFT
I am facing issue with Tumbling window trigger as it is not triggering my pipelines. I created a basic trigger with 15 mins of recurrence.
I can see schedule trigger working but nor tumbling one.
Is this because Azure devops is enabled for my data factory.
I tried same exercise with my local Azure account (Not git enabled) and it was working there.


✨ Add GROOV_STATIC_ASSERT for better compile time error messages

The formatted diagnostics don't work before clang 15/GCC 13.2, so need to turn off those fail tests for earlier compilers the same as https://github.com/intel/cpp-std-extensions/blob/main/test/fail/CMakeLists.txt


Making sure boost::filesystem::exists() does not throw

This fixes #1502: boost::filesystem::exists throws unexpected exception

LGTM


How to enable GPU for rviz

I need to render a large number of point cloud and marker array in rviz, now the rviz fps is very low(< 1fps),  I tried to open a terminal with GPU(mine is Nvidia1050Ti) and then run rviz in that terminal, but it doesn't help. I found the the GPU memory usage by rviz is very low(4 Mb) which is abnormal. So I want to know is there any way to enable GPU for rviz?
Your environment

OS Version:  Ubuntu 20.04
ROS Distro: [Noetic]
RViz

$ rviz
[ INFO] [1674207641.917945501]: rviz version 1.14.19
[ INFO] [1674207641.918000845]: compiled against Qt version 5.12.8
[ INFO] [1674207641.918017279]: compiled against OGRE version 1.9.0 (Ghadamon)
[ INFO] [1674207641.929910597]: Forcing OpenGl version 0.
[ INFO] [1674207642.369170630]: Stereo is NOT SUPPORTED
[ INFO] [1674207642.369286811]: OpenGL device: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
[ INFO] [1674207642.369384268]: OpenGl version: 4.6 (GLSL 4.6).
QFileSystemWatcher::removePaths: list is empty
QFileSystemWatcher::removePaths: list is empty

The output OpenGL device: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 already indicates that the GPU is used for rendering.
Maybe you GPU is already overloaded with (pre)processing of the point-cloud data, i.e. receiving and preparing data for display? This is done in a separate thread for each PC display.

The output OpenGL device: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 already indicates that the GPU is used for rendering. Maybe you GPU is already overloaded with (pre)processing of the point-cloud data, i.e. receiving and preparing data for display? This is done in a separate thread for each PC display.

Thank you for your reply, maybe I need to decrease to point number.

Yes.


Provide a way to programmatically remove formatters

Currently there's #add_formatter for registering a new formatter. But there's no counterpart to remove one. This would be useful in skroutz/rspecq#6 or other custom runners maybe. The rationale is that we want to run a dry-run with a JSON formatter to grab the example IDs, and right after (in the same process) issue the regular run.
I'd like to do something like this:
def files_to_example_ids(files)
  formatter = RSpec::Core::Formatters::JsonFormatter.new(StringIO.new)
  RSpec.configuration.add_formatter(formatter)
  RSpec.configuration.dry_run = true

  opts = RSpec::Core::ConfigurationOptions.new(files)
  RSpec::Core::Runner.new(opts).run($stderr, $stdout)

  # collect individual examples
  JSON.parse(out.string)["examples"].map { |e| e["id"] }
ensure
  RSpec.configuration.dry_run = false

  # NOTE: this doesn't exist
  RSpec.configuration.remove_formatter(formatter)
end

Does that sound reasonable? Or perhaps there's already a way to do this that slipped my eyes? Thanks in advance!

Ah, a bit too hasty. It seems that #clear_examples does the trick.

What do you collect from this dry run exactly? Just the example ids?
RSpec.world has a all_examples method. It's marked as private, but I guess for such a closely integrated tool as rspecq, it's quite ok to rely in the internals that deeply.

@pirj Yep, I want to obtain the example ids of a subset of the files. https://github.com/skroutz/rspecq/pull/36 is what I came up with. Do you think it's better to do this via Rspec.world.all_examples?

The RSpec globals are intended for use by RSpec itself in a single pass, but you can create your own versions of configuration, world etc and use those when you need something more complex. In theory you should be able to duplicate a config and add the formatter / dry run for this purpose.

@agis If all_examples is providing the information you need, that you can feed to RSpec later on, sure.
Just a word of precaution specifically about splitting by examples. Examples may have stateful setup. The simplest example is:
before(:all) { @admin = create(:admin) }
before(:each) { sign_in @admin }

Sometimes, this setup is so heavy that it takes the majority of the spec run time.
If you split the examples that need this setup across workers, those workers will each have to run this setup.
let_it_be/let_once are used in the wild, I've seen several major projects using them, primarily to speed tests up.
The same applies to splitting by example groups, as they similarly can have shared setup.
So in a generic case, I'd stick to splitting by spec files.

Thanks for the heads up @pirj. In the generic case, we do schedule whole spec files. We only split very slow files to individual examples (see documentation).


Autogrpup tabs by domain

I'd love to have new tab autoassigned to a group based on group rule (lie acid tab extension) so to have a single or multiple domain, or a series of wors that match into url, get automatically assigned to a group

Good idea, I planned the feature already.
Stay tuned.

Supported in v1.0.0


ci: merge upgrade test into integration script

Fixes #
Description

Checklist

[ ] PR is rebased to/aimed at branch develop
[ ] PR follows Contributing Guide
[ ] Added tests (if necessary)
[ ] Extended README/Documentation (if necessary)
[ ] Adjusted versions of image and Helm chart in values.yaml and Chart.yaml (if necessary)

Codecov Report
Patch and project coverage have no change.

Comparison is base (a14573f) 97.13% compared to head (25aa1e0) 97.13%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #927   +/-   ##
========================================
  Coverage    97.13%   97.13%
========================================
  Files           23       23
  Lines         1290     1290
========================================
  Hits          1253     1253
  Misses          37       37

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add Glide and make repeatable builds with latest rackhd bindings

This introduces a Glide file so that we create repeatable builds of the binary.
In order to make things compile, I needed to fix the way some of the type assertions were done, and deal  with the fact that gorackhd and gorackhd-redfish are built using different versions of swagger (and those different versions have an incompatible change for importing libraries like strfmt and httpkit.

Awesome. nice work @codenrhoden


reserved identifier violation

I would like to point out that identifiers like “__CONFIG_SERVER_H_” and “__PROPERTY_HASHMAP_H_” do eventually not fit to the expected naming convention of the C++ language standard.
Would you like to adjust your selection for unique names?

thank you for point out this problem .we will fixed it as soon as possbile

How do you think about to avoid that this software depends on undefined behaviour?


Update countryDAO & regionDAO

Added "authenticate": false for both countryDAO & regionDAO
And removed AuthenticatedDAO in countryDAO

You should keep the AuthenticatedDAO, we don't want random people updating our list of countries/regions.
AuthenticatedDAO has an option to allow anonyous reads, which is what we want in this case I believe.  Authenticate writes, but allow anonymous read.
Alternatively decorate with a ReadOnlyDAO so no clients can change the contents, authenticated or not.

ReadOnlyDAO would be fine on the client as new countries and regions always need some code support they are associated with bank accounts, corridors, ... locale.

The AuthenticatedDAO's still need to be there otherwise anyone can just connect and update those DAO's. They were already configured property to authenticate writes but not reads. Just remove authentication of the service level, which you did.

@jlhughes They need setup for nanopay, but this is generic FOAM/NANOS code, where they don't generally need any extra processing. Just putting back the AuthenticatedDAO that only authenticates writes works for both NP and non-NP users.

Put AuthenticatedDAO back based on Kgr's review. Thank you for reviewing and helping me.


chore(deps): update dependency eslint-plugin-jest to v28

This PR contains the following updates:

Package
Type
Update
Change

eslint-plugin-jest
devDependencies
major
27.9.0 -> 28.5.0

Release Notes

jest-community/eslint-plugin-jest (eslint-plugin-jest)
v28.5.0
Compare Source
Features

allow @typescript-eslint/utils v7 as a direct dependency (#1567) (1476f10)

v28.4.0
Compare Source
Features

valid-expect: supporting automatically fixing missing await in some cases (#1574) (a407098)

v28.3.0
Compare Source
Features

prefer importing jest globals for specific types (#1568) (c464ae3)

v28.2.0
Compare Source
Features

support providing aliases for @jest/globals package (#1543) (744d4f6)

28.1.1 (2024-04-06)
Bug Fixes

max-expects: properly reset counter when exiting a test case (#1550) (b4b7cbc)

v28.1.1
Compare Source
Bug Fixes

max-expects: properly reset counter when exiting a test case (#1550) (b4b7cbc)

v28.1.0
Compare Source
Features

add prefer-importing-jest-globals rule (#1490) (37478d8), closes #1101

v28.0.0
Compare Source
Bug Fixes

allow ESLint 9 as peer dependency (#1547) (3c5e167)
drop support for Node 19 (#1548) (c87e388)
no-large-snapshots: avoid instanceof RegExp check for ESLint v9 compatibility (#1542) (af4a9c9)

Features

drop support for @typescript-eslint/eslint-plugin v5 (#1530) (150e355)
drop support for Node v14 (#1527) (df5e580)
remove no-if rule (#1528) (f976fc8)
remove snapshot processor and flat/snapshot config (#1532) (98087f9)
upgrade @typescript-eslint/utils to v6 (#1508) (dc6e8cd)

BREAKING CHANGES

Node v19 is no longer supported
removed unneeded snapshot processor and flat/snapshot config
dropped support for @typescript-eslint/eslint-plugin v5
dropped support for Node v14
removed no-if in favor of no-conditional-in-test

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional<EMAIL_ADDRESS>|| ^7.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/eslint-plugin-jest
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR!   peerOptional<EMAIL_ADDRESS>|| ^7.0.0" from<EMAIL_ADDRESS>npm ERR!   node_modules/eslint-plugin-jest
npm ERR!     dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR!