In WIN10 anaconda error

e:\Anaconda3\envs\env_Sid\lib\site-packages\torch\utils\cpp_extension.py:322: UserWarning: Error checking compiler version for cl: [WinError 2] Не удается найти указанный файл
warnings.warn(f'Error checking compiler version for {compiler}: {error}')
ИНФОРМАЦИЯ: не удается найти файлы по заданным шаблонам.
Traceback (most recent call last):
File "main.py", line 13, in
from models.Embedding import Embedding
File "C:\Users\user\Barbershop\models\Embedding.py", line 3, in
from models.Net import Net
File "C:\Users\user\Barbershop\models\Net.py", line 3, in
from models.stylegan2.model import Generator
File "C:\Users\user\Barbershop\models\stylegan2\model.py", line 11, in
from models.stylegan2.op import FusedLeakyReLU, fused_leaky_relu, upfirdn2d
File "C:\Users\user\Barbershop\models\stylegan2\op_init_.py", line 1, in
from .fused_act import FusedLeakyReLU, fused_leaky_relu
File "C:\Users\user\Barbershop\models\stylegan2\op\fused_act.py", line 14, in
os.path.join(module_path, "fused_bias_act_kernel.cu"),
File "e:\Anaconda3\envs\env_Sid\lib\site-packages\torch\utils\cpp_extension.py", line 1156, in load
keep_intermediates=keep_intermediates)
File "e:\Anaconda3\envs\env_Sid\lib\site-packages\torch\utils\cpp_extension.py", line 1367, in _jit_compile
is_standalone=is_standalone)
File "e:\Anaconda3\envs\env_Sid\lib\site-packages\torch\utils\cpp_extension.py", line 1465, in _write_ninja_file_and_build_library
is_standalone=is_standalone)
File "e:\Anaconda3\envs\env_Sid\lib\site-packages\torch\utils\cpp_extension.py", line 1908, in _write_ninja_file_to_build_library
with_cuda=with_cuda)
File "e:\Anaconda3\envs\env_Sid\lib\site-packages\torch\utils\cpp_extension.py", line 2024, in _write_ninja_file
'cl']).decode(*SUBPROCESS_DECODE_ARGS).split('\r\n')
File "e:\Anaconda3\envs\env_Sid\lib\subprocess.py", line 411, in check_output
**kwargs).stdout
File "e:\Anaconda3\envs\env_Sid\lib\subprocess.py", line 512, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['where', 'cl']' returned non-zero exit status 1.

same issue here

Hi, installing C++ compiler worked for me. I installed Visual Studio first and then compiler according to https://code.visualstudio.com/docs/cpp/config-msvc. After installation I also added folder with cl.exe (C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.32.31326\bin\Hostx64\x64) to the System Variable Path. You can check the succesful installation by the command cl or cl.exe - it is described in the link above. After installation of cl.exe restart the prompt window and Anaconda.

Hi, I found out the issue is that you don't have cl.exe installed on your computer. Therefore, installing C++ compiler worked for me. I installed Visual Studio first and then compiler according to https://code.visualstudio.com/docs/cpp/config-msvc. After installation I also added folder with cl.exe (C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.32.31326\bin\Hostx64\x64) to the System Variable Path. You can check the succesful installation by the command cl or cl.exe - it is described in the link above. After installation of cl.exe restart the prompt window and Anaconda.

Can you deploy it on Windows 10? Why do I have a lot of dependencies that don't install? Can you teach me?


[Project] G-ratio vs diameter

Human data present two clusters of g-ratio VS diameter:

Why??
large g-ratio

smallg

to perform this kind of study. Use https://www.mathworks.com/matlabcentral/fileexchange/13857-graphical-data-selection-tool

this issue is not specific to ADS


Adds press grid to homepage

PressLogoGrid doesn't seem to be laying out great when I put Chrome in mobile mode.  :-/

Ahh, while typical zoom levels don't result in this happening, below 340px or with zoom on this will break. Fix incoming!

https://github.com/covid-projections/covid-projections/pull/769


Only ignore get-kubeconfig error when !all

If you are writing a script to launch k3s clusters checking the exit
code of get-kubeconfig is an easy way to tell if the kubeconfig is
available for use.

True, we shouldn't drop the exit code her ein that case.
Additionally, there's also the --wait flag that lets you wait for the kubelet to start before continuing.
Thanks for the PR :+1:


ember support!

Description

Motivation

How Has This Been Tested?

Types of changes

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

Checklist:

[ ] I have read the Contributing guide.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.

Thanks for the contribution, but closing in favor of Knockout.

See, I came here thinking this might actually be a thing, but now I'm confused. Is this officially closed, or is Ember being harped on here? I don't get it.

This was an inside joke issue to test a workflow. It shouldn't be treated as a possible roadmap ;)
Nothing against Ember; while it's mature it's not as popular as the other frameworks we already support.

Hahah, okay. Still, might take that good first issue tag on as a challenge.
:P
On Wed, Jan 2, 2019, 3:00 PM Kam Figy<EMAIL_ADDRESS>wrote:

This was an inside joke issue to test a workflow. It shouldn't be treated
as a possible roadmap ;)
Nothing against Ember; while it's mature it's not as popular as the other
frameworks we already support.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Sitecore/jss/pull/101#issuecomment-450968509, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AF9e5o2RoxvxlJ59GwLpecHD32vWXDm-ks5u_Q_NgaJpZM4ZQwof
.


Enums without possible values have an empty values property

Before this PR, an Enum leaf without values (used in a schema like Enum()) would have values and values_s properties that were a list/set containing a single value, None. This didn’t make sense to me, and it complicated producing clean documentation output.
Instead, for the “any values are accepted” case, we’ll keep those two Enum properties as an empty list & set, and check for this specific case when validating a document against a schema.
Finally, this PR cleans up the code that produces documentation for Enum leaves.

Removing duplicates makes total sense! Thanks for noting that!
Even when an integer isn't assigned, I suspect that many enums have an
inherent order. For example, there are a lot of fields that have a success
status and then a large number of error cases (e.g. DNS status code). In
the current code, we shuffle all the values and the success value will show
up in a random location among the errors.
It seems reasonable that developers could control this order, for example
choose to order these by alphabetical order, to group similar values, or
group them by cipher strength, or by popularity. I think that as a user,
I'd find it frustrating that the documentation I look at is both random and
(seemingly randomly) shuffled on me instead of following a coherent,
predictable order.
I don't think we necessarily need to fix that today though!
On Tue, Apr 17, 2018 at 1:53 PM Chris Dzombak<EMAIL_ADDRESS>wrote:

@cdzombak commented on this pull request.
In zschema/leaves.py
https://github.com/zmap/zschema/pull/31#discussion_r182229946:

         m = "%s: the value %s is not a valid enum option" % (name, value)

         raise DataValidationException(m)

def _docs_common(self, parent_category):

   retv = super(Enum, self)._docs_common(parent_category)

   if len(self.values_s):

       retv["values"] = list(self.values_s)

I don't think I understand why you convert to a list here given that L250
sets the list locally.
The list is available locally, but it would be confusing to present to a
documentation user a list of possible values which might contain
duplicates. Using a set as canon for documentation of the enum's possible
values avoids that confusion.
This seems particularly worrisome because enums are inherently ordered.
Enumerated types in general are not inherently ordered; they're a set of
identifiers. In some languages which allow (or require) an enum to be
backed by (or convertible to) an integral type, the order in which the
identifiers are listed does matter.
ZSchema is not a language where this ordering matters; we use the
schema-provided list of identifiers to document and validate which values
are allowed in an Enum leaf. These are both use cases which are
well-served by a set; we don't actually use the order anywhere.
(The fact that the schema declares possible Enum values in a list is an
artifact of API convenience.)
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/zmap/zschema/pull/31#discussion_r182229946, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAMSUMTAG635Lw9inuSI6KcqNfjRhn1jks5tplY9gaJpZM4TXT43
.

I absolutely agree that if we return integers we should just mark them as
integers! To clarify, I wasn't referring to those but rather the string
status codes that are output. :) In the case of the DNS example, there is
an enum of status strings here:
https://github.com/zmap/zdns/blob/master/conf.go#L8
https://github.com/zmap/zdns/blob/master/conf.go#L81 that are returned.
This pattern exists in bunch of other places in both zmap and ZGrab as
well. I do think those are reasonable to mark as an enum In the schema,
given that they're defined as an enum in the code.
Apologies for the vague example in the last comment.
On Wed, Apr 18, 2018 at 9:21 AM Chris Dzombak<EMAIL_ADDRESS>wrote:

Even when an integer isn't assigned, I suspect that many enums have an
inherent order. For example, there are a lot of fields that have a success
status and then a large number of error cases (e.g. DNS status code). In
the current code, we shuffle all the values and the success value will show
up in a random location among the errors.
This is true, but for this example (and similar ones, like HTTP status
codes) I don't believe an Enum is the correct approach to model that
field in ZSchema.
There are a number of unassigned and reserved and "private use" DNS rcodes
https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-6
going up to 2^16, and so an Enum that models the full range of possible
rcodes is just an unsigned 16 bit integer, for which we already have a
type https://github.com/zmap/zschema/blob/master/zschema/leaves.py#L352.
Any more constrained enum would not completely capture the possible range
of return values, and it would be nonsenscial to reject scan results that
happen to contain an uncommon DNS rcode.
A similar problem applies with HTTP status codes
https://en.wikipedia.org/wiki/List_of_HTTP_status_codes. It's common
for third parties like Cloudflare to use custom error codes, so any Enum
that captures the full set of possible values would need to spell out every
integer from 100 through 599. In this case, a plain old integer type makes
more sense.
It seems reasonable that developers could control this order, for example
choose to order these by alphabetical order, to group similar values, or
group them by cipher strength, or by popularity.
Fair enough. We're not using this in our schema today, but it is a
possible use case.
I think that as a user,
I'd find it frustrating that the documentation I look at is both random and
(seemingly randomly) shuffled on me instead of following a coherent,
predictable order.
Sorting the items in the set with sorted might be sufficient to produce a
consistent and predictable order in docs, but if you want to document enums
in a particular order, that wouldn't work.
I don't think we necessarily need to fix that today though!
¯_(ツ)_/¯ the fix is easy enough whenever we want to make it.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/zmap/zschema/pull/31#issuecomment-382445284, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAMSUCzyNumTanG35gEStPS_xBM3ki3Vks5tp2fsgaJpZM4TXT43
.


[Testing] TextScene

Description
This adds compose tests to the text scene.
Review checklist

[x] PR is split into meaningful commits for the ease of reviewing
[x] Tests have been written
[ ] Screenshots added (where applicable)
[x] Appropriate labels have been applied

Codecov Report

Merging #38 (561c2ee) into main (d5abd2c) will increase coverage by 3.7%.
The diff coverage is 100.0%.

@@           Coverage Diff           @@
##            main     #38     +/-   ##
=======================================
+ Coverage   64.7%   68.5%   +3.7%
=======================================
  Files         23      23
  Lines        434     435      +1
  Branches     106     106
=======================================
+ Hits         281     298     +17
+ Misses       104      76     -28
- Partials      49      61     +12


[question][help wanted] there is esno, and why use jiti another node ts runtime ?

https://github.com/antfu/esno esbuild ts node runtime
https://github.com/unjs/jiti Runtime typescript and ESM support for Node.js (CommonJS)
Why do I need to use jiti if I already have esno? I am confused about using these two libraries at the same time.

Sorry does it related to this project?

yes, I'm ask about the tech choice about why use jiti when there is already esno.

esno is for developing only, and jiti is used in vite-plugin-windicss to load configure files in the runtime.


[FEATURE] Add docvalue_fields to msearch request

Is your feature request related to a problem?
docvalue_fields does not exist for msearch requests in this version of the SDK which currently makes it impossible for us to switch.
What solution would you like?
Add docvalue_fields to the msearch request.
Is there a particular reason this is missing? If not, I will make a contribution.
E: I just realized that quite a few fields are missing, including, but maybe not limited to:
docvalueFields
profile
rescore
version
collapse
indicesBoost
explain
storedFields
timeout
stats

Is there a particular reason this is missing? If not, I will make a contribution.

No, no reason other than it wasn't done.
In general we're trying to add things to https://github.com/opensearch-project/opensearch-api-specification and generate code in clients, see https://github.com/opensearch-project/opensearch-java/issues/284 if you are interested in helping!

+1, we are blocked by docvalue_fields too. Requesting to kindly prioritize this feature.


[kiali] update to Kiali v1.9

This moves the istio/installer charts to use Kiali v1.9.
Note that this uses quay.io repo just like our older helm chart did as you see here.
Note also that, just as the older helm chart did as you see here, this pulls in the major.minor version (v1.9) leaving the ability for this to pull in z-stream patch versions as they become available. Kiali distributes patches/bug fixes and moves its vX.Y quay label to the latest z-stream release ensuring istio users are pulling in the latest patched release in the X.Y line.
cc @jwendell

I will take this out of "draft" state once we finish our QE testing on this environment.

LGTM, only minor thing is you are using 1.9.0 certain places and 1.9 certain places.  Can we be consistent @jmazzitelli ?

you are using 1.9.0 certain places

the only place I see where 1.9.0 is used is the Chart yaml - I was unaware we are allowed to use just "1.9" there. I thought X.Y.Z was required in Chart.yaml. Is that not true? Or is 1.9.0 used somewhere else?

Ah i missed that, that SG, looks good to me.
I did some quick testing with kiali 1.9, looks decent.

Testing here is good. Moving out of draft - this should be ready to merge.
@jwendell we can cherry pick this over to 1.4, also. correct?

/cherrypick release-1.4

@howardjohn: once the present PR merges, I will cherry-pick it on top of release-1.4 in a new PR and assign it to you.

In response to this:

/cherrypick release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@howardjohn: #503 failed to apply on top of branch "release-1.4":
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	istio-telemetry/kiali/Chart.yaml
M	istio-telemetry/kiali/templates/configmap.yaml
M	istio-telemetry/kiali/values.yaml
A	test/demo/kiali.gen.yaml
Falling back to patching base and 3-way merge...
Auto-merging test/demo/gen-kiali.yaml
CONFLICT (content): Merge conflict in test/demo/gen-kiali.yaml
Auto-merging istio-telemetry/kiali/values.yaml
Auto-merging istio-telemetry/kiali/templates/configmap.yaml
CONFLICT (content): Merge conflict in istio-telemetry/kiali/templates/configmap.yaml
Auto-merging istio-telemetry/kiali/Chart.yaml
CONFLICT (content): Merge conflict in istio-telemetry/kiali/Chart.yaml
Patch failed at 0001 update to Kiali v1.9

In response to this:

/cherrypick release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

hmmm... should I create a manual PR for the cherry pick?

hmmm... should I create a manual PR for the cherry pick?

Yes, please.

cherry pick PR: https://github.com/istio/installer/pull/504

cc @jwendell @howardjohn
auto-cherry-pick failed - see 1.4 cherry pick PR here: https://github.com/istio/installer/pull/504


using theme value on Box is not working using Sx Prop

Hey Guys,
There seems to be a bug when using theme values using sx props as a styling mechanism on Box Component.
To replicate try to change the background color of a box using sx={{bgcolor: "primary.main"}}, and this won't work. However the same line works correctly on other component like Paper.
I even forked the codesandbox demo for sx - props here. It won't even work there. I really don't think this is intentional from MUI team :)

Try wrapping your app/parent component in a ThemeProvider: https://codesandbox.io/s/example-material-demo-forked-4exgp?file=/demo.tsx
`const theme = createTheme({});
export default function Example() {
return (

<Box
sx={{
bgcolor: "primary.main",
boxShadow: 1,
borderRadius: 1,
p: 2,
minWidth: 300
}}
>
<Box sx={{ color: "text.secondary" }}>Sessions
<Box sx={{ color: "text.primary", fontSize: 34, fontWeight: "medium" }}>
98.3 K

<TrendingUpIcon
sx={{ color: "success.dark", fontSize: 16, verticalAlign: "sub" }}
/>
<Box
sx={{
color: "success.dark",
display: "inline",
fontWeight: "medium",
mx: 0.5
}}
>
18.77%

<Box sx={{ color: "text.secondary", display: "inline", fontSize: 12 }}>
vs. last week

);
}`

I too have this issue.
Updating the import to import {Box} from '@mui/material fixes the issue of Box accessing the theme generally, but it seems Box only has access to the default material theme colors and not the custom theme provided by <ThemeProvider theme={theme}>...</ThemeProvider>. Both <Box bgcolor="primary.main">...</Box> and <Box sx={{ bgcolor: "primary.main" }}>...</Box> display the default material primary blue.

I too have this issue.
Updating the import to import {Box} from '@mui/material fixes the issue of Box accessing the theme generally, but it seems Box only has access to the default material theme colors and not the custom theme provided by <ThemeProvider theme={theme}>...</ThemeProvider>. Both <Box bgcolor="primary.main">...</Box> and <Box sx={{ bgcolor: "primary.main" }}>...</Box> display the default material primary blue.

Please provide a reproduction via CodeSandbox (https://material-ui.com/r/issue-template-latest).

Please provide a reproduction via CodeSandbox (https://material-ui.com/r/issue-template-latest).

Never mind, I had ThemeProvider importing from @emotion/react and not @mui/material... face-palm.

I would suggest adding this to the docs somewhere as a "things to look out for" if it's not already there. I've already been burned by this a couple times when using VS Code's auto import. Seems like this is something that can easily trip up newcomers to MUI 5

Please provide a reproduction via CodeSandbox (https://material-ui.com/r/issue-template-latest).

Never mind, I had ThemeProvider importing from @emotion/react and not @mui/material... face-palm.

Please provide a reproduction via CodeSandbox (https://material-ui.com/r/issue-template-latest).

Never mind, I had ThemeProvider importing from @emotion/react and not @mui/material... face-palm.

ahaha I did exactly the same mistake!!! This auto-completion man... I also did the same mistake with createTheme() importing it from @mui/system instead of @mui/material/styles
As @kachi1227 said, it would be a great idea to include these import mistakes in the docs, in order to prevent people from doing these silly mistakes. I almost quit MUI because of this...


Replace debug = 1 with debug = true

When I attempted to build for Debian stretch, I hit the following issue:
~/a/alacritty (master)
$ cargo deb --install

cargo-deb: unable to parse Cargo.toml
  because: invalid type: integer `1`, expected a boolean for key `profile.release.debug`

Replacing the 1 with true seems to have fixed the issue!

Thanks for opening a PR, but please see https://github.com/jwilm/alacritty/issues/1438 for further information about this.

Ah, cool. I'm pretty new to this stuff and probably searched prior work poorly. 👍

No problem, thanks for trying to help out. It's always appreciated! :)


Add provisional DataCite ontology with dummy types

This is a draft of the DataCite ontology converted from https://schema.datacite.org/meta/kernel-4.6/include/datacite-funderIdentifierType-v4.xsd. The conversion was done https://github.com/srdc/ontmalizer.
Please note that several types were missing in the specification and replaced with xs:string for the time being.

nice, thanks! would it makes sense to have the json-ld serialisation in addition to this?

nice, thanks! would it makes sense to have the json-ld serialisation in addition to this?

It's reasonable to include that artifact. I haven't yet found a way to write JSON-LD directly from ontmalizer and the tool for TTL -> JSON-LD (https://github.com/stain/owl2jsonld) has problems with the URIs included.  I'll keep it in the back of my mind.
There is already an issue for the missing types: https://github.com/datacite/datacite/issues/1748

ok, cool, thanks. I will approve and merge for now, and add the issue for later. Thanks for the change!


Strategy gets called more than once for the same type for some cases

Description
When two registration exist for a type, strategies get called for both registrations. A valid use case for more than one registration is for singletons registered for more than one interface (as explained in the documentation: https://github.com/unitycontainer/unity/wiki/Upgrading-to-Release-v5.2.1).
This is inconsistent - for all other cases strategies get executed only once per single concrete type.
To Reproduce
First, enhance TestDoubles.SpyStrategy to count the number of times it's called for different build keys:
internal class SpyStrategy : BuilderStrategy
{
    public override void PreBuildUp(IBuilderContext context)
    {
        this.BuildUpWasCalled = true;
        this.Context = context;
        this.BuildKey = context.BuildKey;
        this.Existing = context.Existing;

        this.UpdateBuildUpCallCount();                       // change
        this.UpdateSpyPolicy(context);
    }

    public override void PostBuildUp(IBuilderContext context)
    {
        this.Existing = context.Existing;
    }

    public IBuilderContext Context { get; private set; }

    public INamedType BuildKey { get; private set; }

    public object Existing { get; private set; }

    public bool BuildUpWasCalled { get; private set; }

    public Dictionary<INamedType, int> BuildUpCallCount { get; private set; }
        = new Dictionary<INamedType, int>();              // change

    private void UpdateBuildUpCallCount()                 // change
    {
        if (!this.BuildUpCallCount.ContainsKey(this.BuildKey))
        {
            this.BuildUpCallCount[this.BuildKey] = 1;
            return;
        }

        this.BuildUpCallCount[this.BuildKey]++;
    }

    private void UpdateSpyPolicy(IBuilderContext context)
    {
        var policy = (SpyPolicy)context
            .Policies
            .GetOrDefault(typeof(SpyPolicy), context.BuildKey, out _);

        if (policy != null)
        {
            policy.WasSpiedOn = true;
        }
    }
}

And then the following unit test will fail:
[TestMethod]
public void unitycontainer_container_125()
{
    var ioc = new UnityContainer();
    var spyStrategy = new TestDoubles.SpyStrategy();
    ioc.AddExtension(new TestDoubles.SpyExtension(spyStrategy, UnityBuildStage.PreCreation));

    ioc.RegisterSingleton<MockLogger>();
    ioc.RegisterType<ILogger, MockLogger>();
    ioc.RegisterType<ObjectWithLotsOfDependencies>();

    var result = ioc.Resolve<ObjectWithLotsOfDependencies>();

    var strategyCallCountForMockLogger
        = spyStrategy.BuildUpCallCount[new NamedTypeBuildKey<MockLogger>()];

    Assert.AreEqual(1, strategyCallCountForMockLogger);
}

Additional context
When resolving ILogger, within the BuilderContext.NewBuildUp method we travel through the strategy chain  which contains SpyStrategy. But first, we reach BuildKeyMappingStrategy which:

changes the build key to the mapped-to type (i.e. MockLogger)
creates a DynamicMethodBuildPlan for the same build key

In the next step we reach BuildPlanStrategy, which executes the build plan from "2" above. This in turn executes a second build up, BuilderContext.BuildUp for the same type - MockLogger with the same strategy chain. This correctly constructs MockLogger and executes SpyStrategy for MockLogger.
However, after this we are back in the "parent" loop in NewBuildUp, which reaches SpyStrategy again and executes it for MockLogger again.

Note that when MockLogger is not a singleton, or we resolve MockLogger directly, not indirectly by some other type the strategy is called only once, as expected.


Analyze PII with PHI domain throws 500 Internal server error

Test disable for now while service investigates:

Azure.RequestFailedException : Internal server error
Status: 500 (Internal Server Error)
ErrorCode: InternalServerError

https://msazure.visualstudio.com/Cognitive Services/_workitems/edit/9956158

This has been fixed


move column to the end of grid causes the grid header to offset from body..

We've encountered an issue where if I drag the column header to the far right, the header becomes decoupled from the body and offset by about the width of the vertical scrollbar.
This doesn't seem to happen on the demo page, and so am wondering if someone has encountered this before and could get some advice on how to fix this.
Note: I'm using angular 1.3 in my project.

First I'd try upgrading to unstable (or to the new rc19 that might go out today), that's the most obvious difference with the tutorial pages.

No response for 2 weeks, assuming issue is resolved by upgrade.

Thanks! Yes, the bug was fixed, but ui-grid's vertical and horizontal scrollbars must be enabled for the table for the fixes to be applied.  Otherwise, the default browser scrollbars creates the misalignment between the header viewport and the grid-body viewport depending on the OS and the timing of the native scrollbars rendering by the browser.
The fix seems to work by making ui-grid's scrollbar override the native scrollbars and recalculate the spaces properly.


fix(versions): update Activiti/activiti-keycloak versions into master

UpdateBot pushed helm dependency: common to: 1.1.15

UpdateBot commands:
updatebot push-version --kind helm common 1.1.15

UpdateBot commands:
updatebot push-version --kind helm common 1.1.16

UpdateBot commands:
updatebot push-version --kind helm common 1.1.17


Fix spurious test failure with "creates new identifiers" [OSF-6970]

Purpose
Debug and fix a spurious test case failure with 37ae2bbc27de10bdc9cb3331aae408f719fbb881 under TEST_BUILD="varnish", where nodeControl > ViewModels > ProjectViewModel > create new identifiers dies with a TypeError inside contribAdder:
TypeError: Fake XHR onreadystatechange handler threw exception:
'undefined' is not an object (evaluating 'response.data.map')
(/home/travis/build/CenterForOpenScience/osf.io/website/static/js/tests/tests.webpack.js:131102:0
<- webpack:///website/static/js/contribAdder.js:257:0)

Changes
n/a
Side effects
n/a
Ticket
https://openscience.atlassian.net/browse/OSF-6970

From @brianjgeiger in Jira:

I briefly looked at skipping the failing test in OSF-7002, but it looks to be a race condition related to the sinon fake xhr functionality. In practice, if you were to skip the one failing test, then two other completely unrelated tests will fail. As mentioned in the comment on 7002, I'm good with skipping all the viewmodel tests since we'll be moving over to Ember which will have proper testing. There will be at least a few tests left over that will just test js functions and not knockout viewmodels.

I find http://stackoverflow.com/questions/38525336/typeerror-fake-xhr-onreadystatechange-undefined-is-not-a-constructor and note that this is a fake XHR onreadystatechange handler. Is response undefined or is it response.data?

OSF-7002 was closed by turning relevant tests off in #6463. Here's @brianjgeiger's notes from 7002:

The test nodeContro=>ViewModels=>ProjectViewModel=>it('creates new identifiers') fails frequently with the failure described below. The problem seems to be some kind of timing issue, because skipping this test will cause others to fail in similar ways. Things that are definitely worth looking into:

Old versions of all of our JS test running software
Occasionally tests report that they force a full page reload
The test 'should not crash initials function when name contains two spaces' does not call done() and so times out
Several of the new logTextParser tests fail in Chrome

 nodeControl
   ViewModels
     ProjectViewModel
       ✓ has no identifiers when identifiers are null
       ✓ has identifiers when identifiers are not null
       ✓ can have identifiers when public, registered, and admin
       ✓ cannot have identifiers when private, not registered, or not admin
       ✓ builds the correct absolute urls
       ✗ creates new identifiers
	TypeError: Fake XHR onreadystatechange handler threw exception: 'undefined' is not an object (evaluating 'response.data.map') (/home/travis/build/CenterForOpenScience/osf.io/website/static/js/tests/tests.webpack.js:131102:0 <- webpack:///website/static/js/contribAdder.js:257:0)

After having done a brief glance at the tests, either this task will need to be "Fix race condition with sinon fake xhr on viewmodel tests" or it will be "Remove viewmodel tests from JS tests to leave only pure unit tests". I'm good with either solution. As we convert over to Ember, we'll have proper testing done within the Ember framework.

Or can be replaced by OSF-6970, but the comment above still stands.

First step here is to revert #6463 so we can see the spurious test failures again: done in 351a38749fa86aebeb71776f825b18fe32bccd8d. Next I'm going to whittle down to just those test cases, to see if we can still see the spurious failures without churning CPUs for half an hour ... ;-)

I don't understand why this shows up under the Varnish tests. What does Varnish have to do with this?

The call appears to be:
/home/travis/build/CenterForOpenScience/osf.io/node_modules/karma/bin/karma start --single-run --browsers PhantomJS

But why?

That's an old test run, from three months ago. But the first test run on this PR just completed, and it still runs karma under TEST_BUILD="varnish". Is that a mistake?

test_travis_varnish definitely includes test_js. The docstring makes it seem like not an accident, and test_js isn't run under either of the other two Travis test chunkings. Okay! So TEST_BUILD="varnish" is a bit misleading, but for our purposes here we're on the right track.

Constrained build succeeded in under five minutes. Probably even quicker now that the Travis cache is primed.

Bah. But I can't restart Travis builds without closing and reopening the PR. :-/

Hmm ... did they close that loophole? 😞

Build restarted. 👍

The full run does fail still, under "create new identifiers" as well as three others. 👍

The test suite creates a stub server using sinon. When calling createIdentifiers ... I guess somewhere under there we land in getContributors, where $.ajax hits the sinon mock?

I moved the JS tests to the varnish branch because that was the fastest to run. If it had to be restarted, I wanted it to be a five minute wait, not a 35 minute wait.

Yeah, I figured. It was just confusing since the test suite was still called just "varnish". PR to clean that up a bit in #6656.

Alright, so what's this about a sinon race condition?

The Sinon docs state that autoRespond is not suitable for tests as it will execute asynchronously. This defaults to 10ms later, which is just enough to bump to the next frame of execution, potentially causing some race conditions with the tests. I discovered this because I had similar failing test cases related to AJAX.
I ended up implementing a respondImmediately property on the fakeServer that will synchronously respond to any request. This just got merged into the project a few weeks ago (v1.14.0), but if you update to the newest version you should be able to get it. Check out the docs here.

http://stackoverflow.com/questions/11304225/sinon-js-fake-server-autorespond-usage

Looking at those docs, both autoRespond and respondImmediately appear to default to true. Is that true? If so, which wins? What's our configuration? Are we using a version of Sinon to which these docs apply?

We specify "karma-sinon": "^1.0.5", but not sinon.
$ npm ls karma-sinon
<EMAIL_ADDRESS>/Users/whit537/workbench/cos/osf.io
└──<EMAIL_ADDRESS>
$ npm ls sinon
<EMAIL_ADDRESS>/Users/whit537/workbench/cos/osf.io
└──<EMAIL_ADDRESS>extraneous

npm ERR! extraneous<EMAIL_ADDRESS>/Users/whit537/workbench/cos/osf.io/node_modules/sinon
$

Extraneous packages are packages that are not listed on the parent package's dependencies list.

https://docs.npmjs.com/cli/prune

Alright, so our version is greater than the version where respondImmediately was added. Are we using it?

I'm working on getting the tests running locally. Hitting a PhantomJS issue.
WARN [launcher]: PhantomJS have not captured in 60000 ms, killing.
INFO [launcher]: Trying to start PhantomJS again (1/2).
WARN [launcher]: PhantomJS have not captured in 60000 ms, killing.
INFO [launcher]: Trying to start PhantomJS again (2/2).
WARN [launcher]: PhantomJS have not captured in 60000 ms, killing.
ERROR [launcher]: PhantomJS failed 2 times (timeout). Giving up.

Upgraded PhantomJS, still no luck. Looks like https://github.com/karma-runner/karma-phantomjs-launcher/issues/84.

Honestly, I'm surprised, that so many people still using PhantomJS. It so slower than using regular Chrome/Safari and debuggability is so much worse.

https://github.com/karma-runner/karma/issues/783#issuecomment-28617233
Hmm ...

👍
osf.io| $ inv karma --single --browsers Chrome

[...]

  nodeControl
    ViewModels
      ProjectViewModel
        ✓ creates new identifiers

Chrome 54.0.2840 (Mac OS X 10.10.5): Executed 1 of 1 SUCCESS (0.077 secs / 0.031 secs)

osf.io| $

http://cosdev.readthedocs.io/en/latest/osf/testing.html#debugging-tests

So far it looks like  is never called(?).
LOG LOG: 'wat?'
LOG LOG: 'creating identifiers'
        ✓ creates new identifiers

Chrome 54.0.2840 (Mac OS X 10.1

diff --git a/website/static/js/contribAdder.js b/website/static/js/contribAdder.js
index 0c8fbad..eb6b9f0 100644
--- a/website/static/js/contribAdder.js
+++ b/website/static/js/contribAdder.js
@@ -245,6 +245,8 @@ AddContributorViewModel = oop.extend(Paginator, {
         self.notification(false);
         var url = $osf.apiV2Url('nodes/' + window.contextVars.node.id + '/contributors/');

+        console.log('contrib adding');
+        debugger;
         return $.ajax({
             url: url,
             type: 'GET',
diff --git a/website/static/js/nodeControl.js b/website/static/js/nodeControl.js
index 9acfac4..369dc6f 100644
--- a/website/static/js/nodeControl.js
+++ b/website/static/js/nodeControl.js
@@ -253,6 +253,7 @@ var ProjectViewModel = function(data, options) {

     self.createIdentifiers = function() {
         // Only show loading indicator for slow responses
+        console.log('creating identifiers');
         var timeout = setTimeout(function() {
             self.idCreationInProgress(true); // show loading indicator
         }, 500);
diff --git a/website/static/js/tests/nodeControl.test.js b/website/static/js/tests/nodeControl.test.js
index 5c0076d..30a41f4 100644
--- a/website/static/js/tests/nodeControl.test.js
+++ b/website/static/js/tests/nodeControl.test.js
@@ -76,7 +76,8 @@ describe('nodeControl', () => {
                 assert.equal(vm.doiUrl(), 'http://ezid.cdlib.org/id/doi:24601');
                 assert.equal(vm.arkUrl(), 'http://ezid.cdlib.org/id/ark:/24601');
             });
-            it('creates new identifiers', (done) => {
+            it.only('creates new identifiers', (done) => {
+                console.log('wat?');
                 vm.createIdentifiers().always(() => {
                     assert.equal(vm.doi(), '24601');
                     assert.equal(vm.ark(), '24601');

I only find two places where getContributors is called:

ContribAdder.prototype.init
contributors.test.js

Alright, so it's curious that the "create new identifiers" test fails inside of getContributors. Is there some parallelization going on?

Here's an open ticket about adding that to Karma: https://github.com/karma-runner/karma/issues/439 ... so ... no? probably not?

It'd sure be nice if we logged test failures to Sentry (or whatever we're using), to help with debugging this sort of thing.

I'm running the full karma suite locally to see what I can see. I'm seeing 4 failures and now 8 failures. Trying to get a consistent result ...

Unicode checkmarks and Xs are clever and readable, but hard to search for in log output. :-/

Here are the 4 failures I'm getting:
        works for internal absolute URLs with different protocol
          ✗ URLs that does not contain search or hash
        AssertionError: expected 'protocol://osf.io/mst3k/files/' to equal '/mst3k/files/'
            at Context.<anonymous> (base/website/static/js/tests/tests.webpack.js?afedfef4ca112e0699905ff5f999

          ✗ URLs that contain search, not hash
        AssertionError: expected 'protocol://osf.io/mst3k/files/?q=random' to equal '/mst3k/files/?q=random'
            at Context.<anonymous> (base/website/static/js/tests/tests.webpack.js?afedfef4ca112e0699905ff5f999

          ✗ URLs that contain hash, not search
        AssertionError: expected 'protocol://osf.io/mst3k/files/#hashhash' to equal '/mst3k/files/#hashhash'
            at Context.<anonymous> (base/website/static/js/tests/tests.webpack.js?afedfef4ca112e0699905ff5f999

          ✗ URLs that contain both search and hash
        AssertionError: expected 'protocol://osf.io/mst3k/files/?q=random#hashhash' to equal '/mst3k/files/?q=
            at Context.<anonymous> (base/website/static/js/tests/tests.webpack.js?afedfef4ca112e0699905ff5f999

Unrelated, in other words.

But at least I can get that result consistently now. :)

So at this point I'm thinking of trying to build in some call stack logging, and then rerunning the build a few times here to see if we can trigger the bug again and get some debugging output.

https://github.com/stacktracejs/stacktrace.js

Now on the first run of the morning I've got five failures ... oh! The new one is from my naive attempt at a stacktrace comprehension. :-)
         ✗ creates new identifiers
        TypeError: 'caller', 'callee', and 'arguments' properties may not be accessed on strict mode functions
            at Context.<anonymous> (base/website/static/js/tests/tests.webpack.js?9fdf003aafbd7ef4ffb9e9795190

Hmm ... I need to understand Bower better, it seems ...

ReferenceError: StackTrace is not defined

Blech. I tried dropping back from bower and just using the CDN, but I get the same result. Hmm ... :thinking:

Harumph. The script does define a StackTrace object.

I have StackTrace TTW.

diff --git a/website/static/js/tests/nodeControl.test.js b/website/static/js/tests/nodeControl.test.js
index 003c3e1..7d73dc9 100644
--- a/website/static/js/tests/nodeControl.test.js
+++ b/website/static/js/tests/nodeControl.test.js
@@ -76,7 +76,8 @@ describe('nodeControl', () => {
                 assert.equal(vm.doiUrl(), 'http://ezid.cdlib.org/id/doi:24601');
                 assert.equal(vm.arkUrl(), 'http://ezid.cdlib.org/id/ark:/24601');
             });
-            it('creates new identifiers', (done) => {
+            it.only('creates new identifiers', (done) => {
+                console.log(StackTrace.get());
                 console.log('wat?');
                 vm.createIdentifiers().always(() => {
                     assert.equal(vm.doi(), '24601');
diff --git a/website/templates/base.mako b/website/templates/base.mako
index 2a2a4d4..58f74c6 100644
--- a/website/templates/base.mako
+++ b/website/templates/base.mako
@@ -304,6 +304,7 @@
     <link rel="stylesheet" href="/static/vendor/bower_components/osf-style/css/base.css">
     <link rel="stylesheet" href="/static/css/style.css">

+    <script src="https://cdnjs.cloudflare.com/ajax/libs/stacktrace.js/1.3.1/stacktrace-with-promises-and-json-polyfills.min.js"></script>
     % if settings.USE_CDN_FOR_CLIENT_LIBS:
         <script src="//ajax.googleapis.com/ajax/libs/jquery/1.11.2/jquery.min.js"></script>
         <script>window.jQuery || document.write('<script src="/static/vendor/bower_components/jquery/dist/jquery.min.js">\x3C/script>')</script>

Yeah, but still not in test context. Hmm ... :thinking:

I guess I need to install with bower after all, and then require in the test file—where does require pull from? What's the right path to use there?

With Webpack, things included via bower should be accessible with require via the name defined in the bower.json file. I don't think it will need a path as such.

Got it!

diff --git a/bower.json b/bower.json
index e3effec..619e453 100644
--- a/bower.json
+++ b/bower.json
@@ -21,6 +21,7 @@
     "zeroclipboard": "2.1.6",
     "osf-style": "https://github.com/CenterForOpenScience/osf-style.git#5dcf5997ad2808ffc7c8564f94cde102bf7a4a96",
     "At.js": "jquery.atwho#e18af47fdcb327605533a9da259225176e3013c8",
-    "academicons": "1.7.0"
+    "academicons": "1.7.0",
+    "stacktrace-js": "1.3.x"
   }
 }
diff --git a/webpack.common.config.js b/webpack.common.config.js
index be513e9..02350f5 100644
--- a/webpack.common.config.js
+++ b/webpack.common.config.js
@@ -79,6 +79,7 @@ var entry = {
         'lodash.get',
         'js-cookie',
         'URIjs',
+        'stacktrace-js',
         // Common internal modules
         'js/fangorn',
         'js/citations',
diff --git a/website/static/js/tests/nodeControl.test.js b/website/static/js/tests/nodeControl.test.js
index 003c3e1..31cc084 100644
--- a/website/static/js/tests/nodeControl.test.js
+++ b/website/static/js/tests/nodeControl.test.js
@@ -5,6 +5,7 @@ var $ = require('jquery');

 var utils = require('./utils');
 var nodeControl = require('js/nodeControl');
+var StackTrace = require('stacktrace-js');

 var nodeData = {
     node: {
@@ -76,7 +77,8 @@ describe('nodeControl', () => {
                 assert.equal(vm.doiUrl(), 'http://ezid.cdlib.org/id/doi:24601');
                 assert.equal(vm.arkUrl(), 'http://ezid.cdlib.org/id/ark:/24601');
             });
-            it('creates new identifiers', (done) => {
+            it.only('creates new identifiers', (done) => {
+                console.log(StackTrace.get());
                 console.log('wat?');
                 vm.createIdentifiers().always(() => {
                     assert.equal(vm.doi(), '24601');

Hmm ... might need to figure out source maps, since line numbers in tests.webpack.js aren't very helpful.

LOG LOG: 'wat?'
LOG LOG: 'creating identifiers'

  nodeControl
    ViewModels
      ProjectViewModel
        ✓ creates new identifiers
LOG LOG: '/website/static/js/tests/tests.webpack.js', 's'
LOG LOG: '/website/static/js/tests/tests.webpack.js', 'Object.get'
LOG LOG: '/website/static/js/tests/tests.webpack.js', 'Context.<anonymous>'
LOG LOG: '/node_modules/mocha/mocha.js', 'callFnAsync'
LOG LOG: '/node_modules/mocha/mocha.js', 'Test.Runnable.run'
LOG LOG: '/node_modules/mocha/mocha.js', 'Runner.runTest'
LOG LOG: '/node_modules/mocha/mocha.js', undefined
LOG LOG: '/node_modules/mocha/mocha.js', 'next'
LOG LOG: '/node_modules/mocha/mocha.js', undefined
LOG LOG: '/node_modules/mocha/mocha.js', 'next'

diff --git a/bower.json b/bower.json
index e3effec..619e453 100644
--- a/bower.json
+++ b/bower.json
@@ -21,6 +21,7 @@
     "zeroclipboard": "2.1.6",
     "osf-style": "https://github.com/CenterForOpenScience/osf-style.git#5dcf5997ad2808ffc7c8564f94cde102bf7a4a96",
     "At.js": "jquery.atwho#e18af47fdcb327605533a9da259225176e3013c8",
-    "academicons": "1.7.0"
+    "academicons": "1.7.0",
+    "stacktrace-js": "1.3.x"
   }
 }
diff --git a/webpack.common.config.js b/webpack.common.config.js
index be513e9..02350f5 100644
--- a/webpack.common.config.js
+++ b/webpack.common.config.js
@@ -79,6 +79,7 @@ var entry = {
         'lodash.get',
         'js-cookie',
         'URIjs',
+        'stacktrace-js',
         // Common internal modules
         'js/fangorn',
         'js/citations',
diff --git a/website/static/js/tests/nodeControl.test.js b/website/static/js/tests/nodeControl.test.js
index 003c3e1..9d10f9d 100644
--- a/website/static/js/tests/nodeControl.test.js
+++ b/website/static/js/tests/nodeControl.test.js
@@ -5,6 +5,7 @@ var $ = require('jquery');

 var utils = require('./utils');
 var nodeControl = require('js/nodeControl');
+var StackTrace = require('stacktrace-js');

 var nodeData = {
     node: {
@@ -76,7 +77,15 @@ describe('nodeControl', () => {
                 assert.equal(vm.doiUrl(), 'http://ezid.cdlib.org/id/doi:24601');
                 assert.equal(vm.arkUrl(), 'http://ezid.cdlib.org/id/ark:/24601');
             });
-            it('creates new identifiers', (done) => {
+            it.only('creates new identifiers', (done) => {
+                StackTrace.get().then(function(frames) {
+                    for (var f, i=0; f=frames[i]; i++) {
+                        console.log( f.fileName.replace(/http:\/\/localhost:9876\/base/, '')
+                                               .replace(/\.js\?[0-9a-f]+/, '.js')
+                                   , f.functionName
+                                    );
+                    }
+                });
                 console.log('wat?');
                 vm.createIdentifiers().always(() => {
                     assert.equal(vm.doi(), '24601');

Alright, first pass at stacktrace logging in c5259de9e08a4ff245a2f54064633b525546fb78.

Red! Ohpleaseohpleaseohplease

Sigh.
jshint /home/travis/build/CenterForOpenScience/osf.io/website/static/js
/home/travis/build/CenterForOpenScience/osf.io/website/static/js/contribAdder.js: line 265, col 32, Comma warnings can be turned off with 'laxcomma'.
/home/travis/build/CenterForOpenScience/osf.io/website/static/js/contribAdder.js: line 264, col 77, Bad line breaking before ','.
/home/travis/build/CenterForOpenScience/osf.io/website/static/js/contribAdder.js: line 265, col 36, Bad line breaking before ','.

:P

Okay! An interesting result.
 The stacktrace log output looks like it encompasses multiple calls, and the failures look like they're due to conflicts between stacktrace.js and sinon.
Do we get the output we need from the above? Do we need to try stacktrace.js's exception handling mode?

 All the stack traces are the same.

Since this bug is intermittent, I'm going restart the build. If we don't get the "create new identifiers" fail it will be interesting to compare the result.

1.17.6

New plan: try to turn on Sentry reporting.

I've created a personal project in Sentry and have set SENTRY_DSN and SENTRY_DSN_JS in local.py. I'm rerunning the test suite to see if my five failures appear.

The reason to use Sentry is because I'm basically rebuilding Sentry with the stacktrace thing. Really, I want to inspect frame context, not just see the stacktrace.

👍

I'm getting messages logged, but I want stack traces from exceptions.

Boom!

Let's see if this dog can hunt ...

Blech. Looks like it's still a static trace, though. 😕  Is frame context available with Sentry under JavaScript?

Maybe with a newer JavaScript client? If it's not available at all then I guess Sentry is a bit of a dead-end.

I read through the Raven docs, upgraded the client, switched to using Raven.context ... and now I'm trying to trigger an event again from localhost.

Alright, it's a little confusing because there's separate installs for front-end and server-side. We install both. From the Karma tests we are using the client-side version.

context
managed with
package
latest version

server
npm (package.json)
raven
1.1.1

client
bower (bower.json)
raven-js
3.9.1

raven-js for the front-end, which we install with Bower (latest version, 3.9.1), and raven

I've reported "Frame context not included."

Okay! So what can we learn from what we know so far? And can we log at least a variable or two of extra context easily with Raven?

Gosh this feels dense. I can't get an interactive debugger where I need it?

How do I run exactly two tests?
I've found it.only to run exactly one test.
I'm trying to narrow down an interaction between tests, so I'd like to run a subset of the test suite that is more than one test but less than the whole thing.

https://gitter.im/karma-runner/karma?at=585bc657058ca967377b74c4

Back to https://github.com/karma-runner/karma/issues/553#issuecomment-37769505.

For the record, my contract with COS is up and we didn't renew for 2017, so this is ready for someone else to pick up! :-)

Closing, as this has become stale.


glx2scripteditor.rev is in two places in repo

you have it in both the / and in the /place these in your liveCode User Plugins folder

Yes - that's necessary because you can't download the raw binary from inside the folder.
Took quite a bit of thrashing about here to get to the bottom of that.

I could get rid of the folder and go back to way things were, but the folder seems like a good idea.

I think what you should do is get rid of the copy that is not in the folder.
On Mon, Apr 5, 2021 at 14:27 Mark Wieder @.***> wrote:

I could get rid of the folder and go back to way things were, but the
folder seems like a good idea.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mwieder/glx2ScriptEditor/issues/17#issuecomment-813559734,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACS5CSCLT25RQLBVH6EI2LDTHH6JVANCNFSM42NHLHVA
.

I'll backburner this for now - it would mean changing the update check routine.


[Feature] e2e tests for RayService high-availability without GCS FT

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
#1420
Use case
No response
Related issues
#1420
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

@kevin85421  - since you are already working on the linked issue, shouldn't this be assigned to you as well? or is this issue still looking for contributions?


Problem about make evalution: boost/numeric/ublas/matrix.hpp:

Hi, kujason：
Thank you for sharing your invaluable code! But, I encountered a problem when running run_evaluation.py which is raised by the process of making evaluate_object_3d_offline; I have tried my best to search the solution,but failed. Can you help me? thank you very much

Please post your error messages, or else I cannot help you easily. You might need to install libboost, or some other missing packages on your system.

you need to install "boost"


refactor: use @bufbuild/protoplugin

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

20 of 21 (95.24%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.3%) to 98.519%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/protoc-gen-nexus/src/plugin.ts
5
6
83.33%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
172

Relevant Lines:
175

💛  - Coveralls


Fix session bypass if more than one buffers opened

This PR is an attempt to fix session bypass if more than one buffers is opened and all opened buffers are on the bypass list. Currently the feature will not work properly if more than 1 buffers is opened

To clarify, the feature currently works exactly like it was intended as per #69. But this is a welcome addition 👍


People search functionality

Hello,
I'm trying to implement the search people function but I have an issue with the parameters to pass.
Can you help me on that please.
Please find below my code:
`router.get('/linkedin1', function(req, res) {
Linkedin.setCallback('http://localhost:3000/linkedin');
var scope = ['r_basicprofile','r_network','rw_company_admin','w_share','r_emailaddress'];
Linkedin.auth.authorize(res, scope, '2334321');

});
router.get('/linkedin', function(req, res) {
Linkedin.auth.getAccessToken(res, req.query.code, req.query.state, function(err, results) {
    if ( err )
        return console.error(err);

            var linkedin = Linkedin.init(results.access_token || results.accessToken);
	linkedin.people.search('first-name=mohamed,last-name=mohamed', function(err, $in) {
        console.log($in);
         });
});

});
`
In fact I get this issue
GET /linkedin1 302 16.900 ms - 562 { [CSRF Alert: Possible CSRF attack, state parameters do not match.] name: 'CSRF Alert' } GET /linkedin?error=invalid_scope&error_description=Your+application+has+not+been+authorized+for+the+scope+%22r_network%22 - - ms - -
Thank you for your help!

Please follow this: https://github.com/ArkeologeN/node-linkedin/blob/d2f91c903e5f540c4f5361a6d68af8cc9a36567f/lib/services/people.js#L60

yes I have followed that, I made a mistake on the options?
Thank you for your help!

or it's an autorisation issue with r_network?
error=invalid_scope&error_description=Your+application+has+not+been+authorized+for+the+scope+%22r_network%22 - - ms - -

Yes, the error you show means your application doesn't authorize to use r_network scope.

so linkedin is no more supporting r_network that is required for search people. There is other solution?


feat: import new individual learner dashboard

Description
This PR imports the new Individual Learner Dashboard.
Author concerns
I have some performance concerns however we can address them after the Redwood cut.

Thanks for the pull request, @Ian2012! Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

@Ian2012 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.


Transform jeo-maven-plugin output to PHI expressions

When we have two separate methods with the same name (method overloading), we can't transform it to EO.
EO requires all the object names to be unique.
Also we might have some different problems in PHI printing.
We should add EO printing to check that jeo-maven-plugin prints all the parts to PHI expressions successfully.

@volodya-lombrozo 5 puzzles #633, #634, #635, #636, #637 are still not solved.

@rultor release, tag is 0.5.0, title is 0.5.0.

@rultor release, tag is 0.5.0, title is 0.5.0.

@volodya-lombrozo OK, I will release it now. Please check the progress here

@rultor release, tag is 0.5.0, title is 0.5.0.

@volodya-lombrozo Done! FYI, the full log is here (took me 13min)

@volodya-lombrozo 4 puzzles #633, #634, #635, #636 are still not solved; solved: #637.

@volodya-lombrozo 4 puzzles #633, #634, #635, #697 are still not solved; solved: #636, #637.

@volodya-lombrozo 3 puzzles #633, #634, #635 are still not solved; solved: #636, #637, #697.

@volodya-lombrozo 2 puzzles #633, #635 are still not solved; solved: #634, #636, #637, #697.

@volodya-lombrozo the puzzle #633 is still not solved; solved: #634, #635, #636, #637, #697.


New exception whenever you try to log an empty message

Description
New error type is created and raised whenever you try to log an empty message. You shouldn't do that, right?
Changes
Changes proposed in this pull request:

InvalidMessageError type is created and raised in the _logger module

Pull request status

[X] Implementation
[X] Unit tests
[X] Exception Handling

not so sure about it, couldn't we just use a single error type for the whole app?


Bump inspec-core to 3.1.3

This is one we're going to need to chat about because this is pulling in a large number of new deps for Chef


Loading cudNN in docker image where tensorflow is installed via pip returns Error: libnvrtc.so: cannot open shared object file: No such file or directory

Issue type
Build/Install
Have you reproduced the bug with TensorFlow Nightly?
No
Source
binary
TensorFlow version
2.14.0
Custom code
Yes
OS platform and distribution
Ubuntu 22.04
Mobile device
No response
Python version
3.10
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
11.8/8.7
GPU model and memory
NVIDIA L40, 46BG
Current behavior?
We are building a Docker image that is running an Ubuntu 22.04. The host machine is also Ubuntu 22.04. We have chosen to not use the prebuilt tensorflow Docker image. We are trying to install tensorflow via pip in the docker image, and at the first glance it seems to work, as import tensorflow as tf; print(tf.reduce_sum(tf.random.normal([1000, 1000]))) works perfectly fine and prints something along the lines of tf.Tensor(-163.40398, shape=(), dtype=float32).
However, when we try to load cudNN by running the keras Model.train_on_batch method we get the error Could not load library libcudnn_cnn_infer.so.8. Error: libnvrtc.so: cannot open shared object file: No such file or directory. Full stack trace is in the "Relevant log ouput" cell.
If we install cuda in the docker image by running the following commands it works though. But we would prefer not installing cuda directly and only through pip.
apt-get install wget \
wget https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64/cuda-ubuntu2204.pin \
mv cuda-ubuntu2204.pin /etc/apt/preferences.d/cuda-repository-pin-600 \
wget https://developer.download.nvidia.com/compute/cuda/11.8.0/local_installers/cuda-repo-ubuntu2204-11-8-local_11.8.0-520.61.05-1_amd64.deb \
dpkg -i cuda-repo-ubuntu2204-11-8-local_11.8.0-520.61.05-1_amd64.deb \
cp /var/cuda-repo-ubuntu2204-11-8-local/cuda-*-keyring.gpg /usr/share/keyrings/ \
apt-get update \
DEBIAN_FRONTEND=noninteractive apt-get -y install cuda \
echo "export PATH=${PATH}:/usr/local/cuda/bin" >> ~/.bashrc \

nvidia-smi prints
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.104.12             Driver Version: 535.104.12   CUDA Version: 12.2     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA L40                     Off | 00000000:0B:00.0 Off |                    0 |
| N/A   37C    P0              78W / 300W |      4MiB / 46068MiB |      3%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+

+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|  No running processes found                                                           |
+---------------------------------------------------------------------------------------+

pip freeze gives us these dependencies (some dependencies stripped):
keras==2.14.0
keras-core==0.1.7
keras-cv==0.6.4
...
numpy==1.26.1
nvidia-cublas-cu11==<IP_ADDRESS>
nvidia-cuda-cupti-cu11==11.8.87
nvidia-cuda-nvcc-cu11==11.8.89
nvidia-cuda-runtime-cu11==11.8.89
nvidia-cudnn-cu11==<IP_ADDRESS>
nvidia-cufft-cu11==<IP_ADDRESS>
nvidia-curand-cu11==<IP_ADDRESS>
nvidia-cusolver-cu11==<IP_ADDRESS>
nvidia-cusparse-cu11==<IP_ADDRESS>
nvidia-nccl-cu11==2.16.5
...
tensorboard==2.14.1
tensorboard-data-server==0.7.1
tensorflow==2.14.0
tensorflow-datasets==4.9.3
tensorflow-estimator==2.14.0
tensorflow-io-gcs-filesystem==0.34.0
tensorflow-metadata==1.14.0
tensorrt==<IP_ADDRESS>

To me it seems like installing tensorflow via pip install tensorflow[and-cuda]==2.14.0 doesn't include the libnvrtc.so file? Or maybe it's some error related to keras?
Standalone code to reproduce the issue
Dockerfile:

FROM ghcr.io/osgeo/gdal:ubuntu-small-3.7.2

ARG USE_GPU

RUN apt-get update && apt-get install ca-certificates -y

# Install python dependencies
RUN apt install python3-pip -y
RUN pip install pillow==10.1.0 transformers==4.33.3 imageio==2.31.1 scipy==1.11.1 geopandas==0.14.0 dtale==3.7.0 rasterio==1.3.9 rasterstats==0.19.0  psycopg2-binary==2.9.9 sqlalchemy==2.0.22 keras-cv==0.6.4 focal-loss==0.0.7 azure-storage-blob==12.18.3

RUN if [ "$USE_GPU" = "true" ]; then \
    pip install tensorflow[and-cuda]==2.14.0; \
  else \
    pip install tensorflow==2.14.0; \
  fi

### Relevant log output

```shell
2023-10-23 05:58:21.251995: E tensorflow/compiler/xla/stream_executor/cuda/cuda_dnn.cc:9342] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
2023-10-23 05:58:21.252097: E tensorflow/compiler/xla/stream_executor/cuda/cuda_fft.cc:609] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
2023-10-23 05:58:21.252135: E tensorflow/compiler/xla/stream_executor/cuda/cuda_blas.cc:1518] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2023-10-23 05:58:21.259174: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
Using TensorFlow backend
2023-10-23 05:58:27.246915: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:894] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2023-10-23 05:58:27.284909: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:894] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2023-10-23 05:58:27.286183: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:894] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2023-10-23 05:58:27.298554: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x55b5e53fd570 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2023-10-23 05:58:27.298575: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
2023-10-23 05:58:27.298922: E ./tensorflow/compiler/xla/stream_executor/stream_executor_internal.h:124] SetPriority unimplemented for this stream.
2023-10-23 05:58:27.299033: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:894] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2023-10-23 05:58:27.300290: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:894] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2023-10-23 05:58:27.301475: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:894] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2023-10-23 05:58:27.447455: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:894] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2023-10-23 05:58:27.448893: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:894] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2023-10-23 05:58:27.450160: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:894] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
2023-10-23 05:58:27.451404: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1886] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 43412 MB memory:  -> device: 0, name: NVIDIA L40, pci bus id: 0000:0b:00.0, compute capability: 8.9
2023-10-23 05:58:27.453893: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x55b5e5f86f60 initialized for platform CUDA (this does not guarantee that XLA will be used). Devices:
2023-10-23 05:58:27.453916: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): NVIDIA L40, Compute Capability 8.9
learning_rate 0.001
2023-10-23 05:59:11.072927: I tensorflow/compiler/xla/stream_executor/cuda/cuda_dnn.cc:442] Loaded cuDNN version 8700
Could not load library libcudnn_cnn_infer.so.8. Error: libnvrtc.so: cannot open shared object file: No such file or directory

Also seeing this issue. On a system with only the driver installed, libnvrtc.so can't be found.

@maltel It seems like NVIDIA compiler runtime (NVRTC) is not installed in your Docker image.
To install the prebuilt image, run the following command:
docker pull tensorflow/tensorflow:latest-gpu

Please let us know if it helps?
Thank you!

Same issue on WSL2 on Windows 10 using installation with python3 -m pip install tensorflow[and-cuda]

@maltel Thank you for your response here!
Could you please file a new ticket for the issue you are facing?
Thank you!

@sushreebarsa I am not using the tensorflow docker image, I am using a custom one (See dockerfile above) so I am not sure pulling the tensorflow docker image is useful. Besides, based on the other comments here it seems like its not an issue with docker, but rather an issue with Ubuntu when only the driver installed.
I don't know what a new ticket is. Is it the same as a new issue?  :-)

@maltel Sorry for the mistake! I was asking @lightroomstatistics to create a new ticket for WSL2 issue.

@maltel Could you try to install NVRTC manually. This can be done by adding the following lines to your Dockerfile:
RUN apt-get update && apt-get install -y nvrtc

@sachinprasadhs Could you please have a look into this issue!
Thank you!

There are several different things going on in this issue's comment history.  As to the latter part, the nvrtc package is actually called cuda-nvrtc-X-Y for whichever specific CUDA X.Y you have (see e.g. https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64/ ).  Regarding the original post, the loading of libnvrtc.so instead of libnvrtc.so.XX (via its SONAME) was a bug in that particular build of cuDNN -- this probably will mean you need not only the cuda-nvrtc-11-8 package but also cuda-nvrtc-dev-11-8, so that the libnvrtc.so symlink is made available.
HTH

@nkinnaird - for https://github.com/tensorflow/tensorflow/issues/62194#issuecomment-1781418833 , you might want to see https://github.com/tensorflow/tensorflow/issues/61986 .  I think your issue is more likely related to that one than to this one.

Thanks for the reply @cliffwoolley! Does that mean there is no way of installing tensorflow and cuda dependencies through pip only for that particular version? (If the TF team doesn't add the cuda-nvrtc-dev-11-8 package?)

Based on the comments in ticket #61986 I tried the command mentioned there:
python3 -m pip install "tensorflow[and-cuda]==2.15" --extra-index-url https://pypi.nvidia.com
and my error Could not load library libcudnn_cnn_infer.so.8. Error: libnvrtc.so: cannot open shared object file: No such file or directory didn't occur. So far so good.
My steps:

Complete new WSL2 image
sudo apt update
sudo apt upgrade
sudo apt install python3-pip
python3 -m pip install --upgrade pip
python3 -m pip install "tensorflow[and-cuda]==2.15" --extra-index-url https://pypi.nvidia.com
pip install --ignore-installed --no-cache-dir -r requirements_win.txt
ran my keras / tensorflow / mflow interference model


Update k8s.jsonnet file to support 2023 changes to images

These are the changes I made to make it actually function for the year's run, but I would like it looked over in case I did an Oopsie somewhere in it.
Could be that's why my node's metrics where a little Weird this year, after all.

Using some more better mount options does appear to have sped things up considerably, but I suspect we won't know for sure without a proper test with backfill going and stuff.


Can only use new group DMs after reconnect

New group DMs are not picked up in the server's channels SearchList when they are originally created, so any attempts to use that group DM will fail. When I do a fresh reconnect, I get that channel information from the original channel dump and it works again. Most likely need to fix something in process_changes to pick up new group DMs.

+1, and I seem to be getting the same behavior when trying to send new DMs to individual users as well.

I think there are still some outstanding issues with having the list of channels update. I'll continue looking into it.

Thanks for reporting this issue. We'll no longer be storing and keeping data from the initial RTM request on the client. This change will take effect in the next major version. (See https://github.com/slackapi/python-slackclient/issues/384) With this changing I don't believe it makes sense for us to add any additional functionality to keep this up-to-date.


Change Lookup order in BinderUtils.TryGetConstantValue to check entitystore first

NameResolver.Lookup is a weirdly expensive operation when done from the middle of a running analysis pass.
A few functions call TryGetConstantValue from CheckTypes, which is called during analysis to get functions result types.
In JSON it was possible to move that to CheckSemantics, but in Match, we want to avoid the expensive call to Lookup if we can, so we first look in the EntityStore to resolve enums.
This doesn't meaningfully change the scenario for non PA hosts, as the entity store is a PA-only concept.

✅ No public API change.

✅ No public API change.


Bump Dependencies #3847835703

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/3847835703

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jenkins-is-staging seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Twilight Forest compat drawers don't show up

When this mod and Twilight Forest are loaded together, the drawers from this mod made of Twilight Forest wood types are nowhere to be found in the creative menu, and cannot be given with /give either.
Minecraft 1.18.2
Twilight Forest 4.1.1397
Storage Drawers 10.2.1
More Storage Drawers 1.1.2

it looks like twilight forest hadn't been updated to 1.18.2 yet when this mod last updated. whoops.


Use prepared statements + add concurrency for Cassandra

Inserts now use prepared statements. Batch size is now tunable, as is the number of concurrent requests that can be sent to Cassandra.

@jacoblee93 I've switched over to AsyncCaller, thanks for the pointers to that code.

LGTM if it's good with you!


Experimental: rewrite of the architecture section

Thank you for your contribution to the IC Developer Portal.
Before submitting your Pull Request, please make sure that:

[ ] You have updated the .github/CODEOWNERS file according to your changes.
[ ] You have registered new documents to /sidebars.js if any.

Meta: do we expect readers to be from the blockchain space? The text implicitly assumes knowledge of the following terminology: blockchain, smart contract, consensus, sharding, dapp, tokenized, dao, decentralization.

Outdated, confirmed with Björn via Slack this can be closed.


Remove gaia

What do these changes do?

Related issue number

Fixes

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: shirly121:x: BingqingLyuYou have signed the CLA already but the status is still pending? Let us recheck it.

[ ] GraphScope/Makefile also has some code related to GAIA

[ ]  GraphScope/Makefile also has some code related to GAIA

It has already been removed in commit 0b4f98e

I'm going to merge this PR to move forward, as the CI is blocked by #1389 and I'm working on that.


Will there be a version compatible with 4.0 and if so when will it get released?

Godot 4 adds a similar feature to this (POT file generation), so I'm not sure if updating this is needed. I haven't done a close look at it, but it does seem like there may be some advantages to using this addon over it though, and it probably won't be too time consuming to port, so I'll look into it when I port my game project to Godot 4 (which I think should be soon after the first beta).


Problem with German keyboards under Windows

On German keyboards under Windows, the default shortcut is the same that is used for the @ sign (AltGr-Q). This causes unwanted formatting and prevents usage of the @ sign, which is quite annoying.

This is a duplicate of atom/atom-keymap#35 - feel free to subscribe there for updates.

OK, thanks for the info.


Fix(compose): Fix compose based on Flow typing tests

As a result of Flow typing compose.spec.js more changes needed to be made to compose:

duration in the HOC needed to be optional for Flow
Component in the HOC should actually be an ElementType since it takes either intrinsic JSX or a Component
Set an actual useful displayName for enhanced component (verified by new tests)
Warn if a composite event handler isn't specified (verified by new teststests)

Coverage decreased (-1.8%) to 98.246% when pulling 37babd14ed8dfc6b8e00a992634a09d6dcf7fd3c on flow-again into 7e8e7e0d40ab9c3f82534f3956587cb94832d766 on master.

Coverage decreased (-1.8%) to 98.246% when pulling 37babd14ed8dfc6b8e00a992634a09d6dcf7fd3c on flow-again into 7e8e7e0d40ab9c3f82534f3956587cb94832d766 on master.

Coverage decreased (-1.8%) to 98.246% when pulling 37babd14ed8dfc6b8e00a992634a09d6dcf7fd3c on flow-again into 7e8e7e0d40ab9c3f82534f3956587cb94832d766 on master.

Coverage remained the same at 100.0% when pulling 5948bf9c4b763d6ac17a2d3d3ac6504f0801e416 on flow-again into 7e8e7e0d40ab9c3f82534f3956587cb94832d766 on master.


Curric/school picker bug fix CUR-255

Description

Add promotional tag to the subjects drop down
Refactors some of the components to prevent view from being truncated
Adds some styling for Mobile phone views

Issue(s)
Fixes #CUR-255
How to test

Go to https://deploy-preview-1897--oak-web-application.netlify.thenational.academy/beta/teachers/curriculum
Click on School Phase Picker
Try at variety if view ports

Screenshots
How it used to look:

How it should now look:

Checklist

[ ] Added or updated tests where appropriate
[ ] Manually tested across browsers / devices
[ ] Considered impact on accessibility
[ ] Design sign-off
[ ] Approved by product owner

Looks a lot better!
However the grey text color in the 'form fields' of the picker does not pass colour contrast - I suggest reverting it back to black.

Changed to black ✅

Grey text colour has been changed back to black 👍
From @HelenHarlow's comments, it looks like points 1 and 2 are fixed but for 3 we still need some vertical padding added for the phase options when they are vertically stacked.
<img width="965" alt="Screenshot 2023-09-13 at 09 13 24" src="https://github.com/oaknational/Oak-Web-Application/assets/3018395/05cb0c

a8-d720-4667-9074-1916b6131b63">
Additionally point 4 is still outstanding, the phase options should have text styling that looks like this, where only the phase (and not the key stage and years) are bolded:

:tada: This PR is included in version 1.240.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


🧹 Configure Renovate

Fixes #3.
Question for discussion: Do we only want to support auto-merging PRs for minor/patch updates, or do we want to enable this for major dependency upgrades (eg. for Gatsby/React), too?
Changes

Adds renovate.json configuration file to auxeng-docs
Scheduled to run on weekly basis (earlyMondays)
Groups together updates for gatsby and react
Supports both npm and github-actions updates
Currently set to automerge minor/patch updates
Adds .github/lint.yml workflow to lint config changes

@GaryPWhite what are your thoughts on this Q from the description?

Question for discussion: Do we only want to support auto-merging PRs for minor/patch updates, or do we want to enable this for major dependency upgrades (eg. for Gatsby/React), too?

Minor updates pls, major stuff is likely to break unexpectedly and I'd rather have the chance to poke at it. Being a UI-mostly app, it's not easy to build a testing framework to make sure it looks / builds right with github actions.

Minor updates pls, major stuff is likely to break unexpectedly and I'd rather have the chance to poke at it. Being a UI-mostly app, it's not easy to build a testing framework to make sure it looks / builds right with github actions.

Sweet, I believe with the way it's configured right now ("matchUpdateTypes": ["minor", "patch", "pin", "digest"],) that should achieve what we want. We can validate that theory once it's merged into main and we've given Renovate some time to do its thing. 🤞


2 vs 4 byte IEEE754 floats in power meters (IDFGH-7198)

Hello @alisitsyn, I've applied a slight variation of the fix you proposed in the esp32 modbus power metering thread, since __beswap_32 didn't seem to be an available symbol in the 4.4 esp-idf revision I'm using, so I went with __builtin_bswap32 instead which seems to do BE swapping too:
 // mbc_serial_master.c
@@ -401,6 +410,12 @@
         }
         // Set the type of parameter found in the table
         *type = reg_info.param_type;
+		if (((	reg_info.param_type == PARAM_TYPE_FLOAT)
+			|| (reg_info.param_type == PARAM_TYPE_U32))
+			&& (reg_info.param_size == 4)) {
+			// Fix endianess for FLOAT and U32 parameter here <<<<<<<<<<<<<<<<<<<
+				*(uint32_t*)value_ptr = __builtin_bswap32(*(uint32_t*)value_ptr);
+		}
     } else {
         ESP_LOGE(TAG, "%s: The cid(%u) not found in the data dictionary.",
                                                     __FUNCTION__, reg_info.cid);

But I'm not getting the same numbers as the LCD screen is displaying, so before fudging a bit further with the offsets, I just wanted to understand why you think that my meter as 4 byte floats when the PDF manual (shown in the esp32.com forum) states 2 bytes :-?

Hello @brainstorm,

I just wanted to understand why you think that my meter as 4 byte floats when the PDF manual (shown in the esp32.com forum) states 2 bytes

Page 13,  table 1 (request to read registers starting from address 0x0017) in your manual shows the example command to read 3 float values and I can. The float value contains 2 Modbus registers = 4 bytes of data. This also clarifies how the float is stored in the data field of the Modbus response (Page13, Table2).

But I'm not getting the same numbers as the LCD screen is displaying, so before

// BigEndian 32bit swap
//   just swap the two 16 bit registers since the two bytes in each
//   register are already swapped (BigEndian) as per modbus standard.
# define __beswap_32(x) \
    (__extension__							      \
     ({ uint32_t __bsx = (x);					      \
        ((((__bsx) >> 16) & 0xffff) | (((__bsx) & 0xffff) << 16)); }))

@brainstorm,
Any update on the issue? Does the above-described solution work for you?

A couple of days after your message I tried a few combinations of the macro that you outlined, but no matter how I reorder the bytes, the readout did not seem to make sense still. I'll make sure I have a stable input from a DC lab power supply and triple-check because I was using solar panels and the values where fluctuating quite a bit... the last couple of weeks it has been about moving apartments which did not help in having a stable setup, but I'll come back to this, promise, I really appreciate your input and I'll keep this ball rolling ;)
I'll continue working on branch https://github.com/brainstorm/esp-modbus-power-meter/tree/alisitsyn_suggestions_debug, I'm trimming down the example to iterate faster.

Thank you for the update and take your time. I can suggest using the modbuspoll tool to investigate the device first. It allows to send test commands (prepared according to manual) to the device and get answers as well as log the functionality of the transaction. Once we get the log for the reply of the command we can understand the actual change in Modbus protocol of your device and adopt the esp-modbus implementation.

Thanks Alex! Is there an ESP/non-windows equivalent for that tool? Looks handy but don't have physical windows machines at reach atm.

There are many tools for host machine that supports Modbus. I can recommend the pymodbus small example script. There are tools for android that can be found and they are usually using the BT-serial adapter for RTU.

@brainstorm, I am going to close the issue because do not have response for a long time. Please feel free to reopen issue once you have some feedback.

I could participate this a bit, as a total rookie. I have very little understanding about floats/integers/hex whatsoever :D
I have couple Arduino Minis in the table but so far I've tried to understand this with Raspberry Pi + CH340 RS485-USB adapter + Node-Red. My unit should be identical, part number YG899-9SY, ordered about 2020 from Aliexpress. It's up and running with 3 phase load connected.
I can get feedback from modbus, but I just cannot figure how to format the response and/or if I'm polling the right addresses?
Node-red
Based on the Chinese manual on Docs -folder + some nice hand made remarks, "Phase 1 voltage" should be at address 23+24. If I poll them I get one array and one buffer element:

I have no idea, if there is any good in these?

Converting these to Float(le) with Buffer-Parser in Node-Red doesn't do any good either:

One thing I don't get is that why it forms two separate values from each item? If you combine two values into one 32bit float, shouldn't it be just one number?

I just found that in "Include" folder cid_tables.h -file there is different address (I think..):
{ CID_HOLD_DATA_6, STR("Volts_phase_1"), STR("V"), MB_DEVICE_ADDR1, MB_PARAM_HOLDING, 0x29, 2, //             HOLD_OFFSET(holding_data6), PARAM_TYPE_FLOAT, PARAM_SIZE_FLOAT, OPTS( 0, 400, .001 ), PAR_PERMS_READ },
That 0x29 refers to decimal address 41 - right? I've tried this as well, no success.
I've done this similar float-conversion with TUF2000-M Ultrasonic flowmeter with Modbus RTU and it works like a charm, combining two values into one float.
Any ideas what I'm missing here?

Hi again, I figured it out!
I got a new manual, mostly in reasonable English.
YG899-9SY_manual.pdf
There we can see e.g. Phase A voltage is in address 9+10 with 4-bytes, float.

Some testing in Node-Red shows it's actually Big-Indian Float.

I don't get why I have to use length of 1 in parser? But like this it works.

I get a lot of CRC-errors when reading over 10 addresses at once, most likely because the RS485 fieldbus is not terminated at the moment. I will hook up some 120Ohm resistor and try it again.

https://www.kele.com/content/blog/2014/01/17/the-rs-485-network-terminator


Telis modulis remote like

Hello,
I'm using your app on  a W32-ETH01 and it works great. Thank you for the job, it's really amazing and so well integrated in home-assistant.
Now, I would like to simulate a modulis remote that can drive variated led. Is there a way to do that?
Thanks a lot again.

Wow, that's a cool remote with its scroll wheel!
https://www.youtube.com/watch?v=PDcm9XuLo-c


add GH Actions workflow to publish the docs

Ah, github.io, not RTD. The docs are available here: https://blueskyproject.io/hklpy/master/
Is there a workflow or batch file to be examined?

I think we can reuse https://github.com/bluesky/ophyd/blob/master/.github/workflows/publish-docs.yml for the docs. Is .travis.yml fully retired for now?
Originally posted by @mrakitin in https://github.com/bluesky/hklpy/issues/52#issuecomment-742787007

Workflow tested successfully with merge of #52.  Declaring victory here.


Build process in AppVeyor

It would be good if the project was build in AppVeyor and automatically deployed to nuget. Its free and easy to setup.

Given you write access to this repo. Feel free to add appveyor

Cool, I’d set it up to deploy direct to nuget, can you share the key with me you use to upload?
From: Jonathan Channon<EMAIL_ADDRESS>Sent: 05 December 2015 21:52
To: jchannon/WebAPI.Testing<EMAIL_ADDRESS>Cc: Dafydd Giddins<EMAIL_ADDRESS>Subject: Re: [WebAPI.Testing] Build process in AppVeyor (#7)
Given you write access to this repo. Feel free to add appveyor
—
Reply to this email directly or view it on GitHub https://github.com/jchannon/WebAPI.Testing/issues/7#issuecomment-162250399 .  https://github.com/notifications/beacon/AAUpyQ165kc4oLPGv_K1YRVaKLwTrSL4ks5pM1QEgaJpZM4GuBDf.gif

I can make you a nuget  co-owner and you can use yours if thats ok

That’s perfect. My account name is dafydd.giddins
From: Jonathan Channon<EMAIL_ADDRESS>Sent: 07 December 2015 13:19
To: jchannon/WebAPI.Testing<EMAIL_ADDRESS>Cc: Dafydd Giddins<EMAIL_ADDRESS>Subject: Re: [WebAPI.Testing] Build process in AppVeyor (#7)
I can make you a nuget co-owner and you can use yours if thats ok
—
Reply to this email directly or view it on GitHub https://github.com/jchannon/WebAPI.Testing/issues/7#issuecomment-162521916 .  https://github.com/notifications/beacon/AAUpyXvfJT1vP19kUzVXuSt3tRdJakVIks5pNX60gaJpZM4GuBDf.gif

all done!
On 7 December 2015 at 13:20, Dafydd Giddins<EMAIL_ADDRESS>wrote:

That’s perfect. My account name is dafydd.giddins
From: Jonathan Channon<EMAIL_ADDRESS>Sent: 07 December 2015 13:19
To: jchannon/WebAPI.Testing<EMAIL_ADDRESS>Cc: Dafydd Giddins<EMAIL_ADDRESS>Subject: Re: [WebAPI.Testing] Build process in AppVeyor (#7)
I can make you a nuget co-owner and you can use yours if thats ok
—
Reply to this email directly or view it on GitHub <
https://github.com/jchannon/WebAPI.Testing/issues/7#issuecomment-162521916>
. <
https://github.com/notifications/beacon/AAUpyXvfJT1vP19kUzVXuSt3tRdJakVIks5pNX60gaJpZM4GuBDf.gif>
—
Reply to this email directly or view it on GitHub
https://github.com/jchannon/WebAPI.Testing/issues/7#issuecomment-162522137
.


implement generates_token_for for email verification

Swaps out the custom logic used to generate and store confirmation tokens with the new Rails 7.1 generates_token_for API.
Closes #23.

This is slick @kylekeesling 💪

Not having to store anything about the token really simplifies things doesn't it?

Definitely. I've used SignedGlobalID for this before, but those don't get cleared out like this new interface. 🔥

We'll either need to cherry-pick the backport from #28 or merge this after it's merged.


PE-1136/refactor arconnect signing

Refactors arconnect wallets to use the sign function instead of getSignature function to sign any transactions and data items.
Related arweave-dart PR: https://github.com/ardriveapp/arweave-dart/pull/20

There are conflicts with the base branch RN


Can't disable desktop notifications

Reference:
https://forum.syncthing.net/t/rest-api-how-to-auto-disable-desktop-notifications-in-synctrayzor/17133/3?u=rmacyn
Desktop notifications (Syncing finished, etc....) still occur even though the "Notifications" option is unchecked.
Hint: It looks like the notifications checkbox is re-enabled when new folders area added.
Environment:
Windows 10

I can't reproduce this I'm afraid. If I make sure that no folders have notifications enabled, then add a new folder, then open Settings -> Folders again, the new folder doesn't have notifications enabled.

Can you post the exact steps you go through to repro this?


the description of realworld data shown in the paper  and the data downloaded from website seems not match

Hi~,  the description of realworld data shown in the paper  and the data downloaded from https://xskill.cs.columbia.edu/data/real_kitchen_data.zip seems not match , could you help me, thank you very much!

For example, the inference task can not be found in the dataset downloaded from https://github.com/real-stanford/xskill/issues/url

Hi!
Thanks for your comments. Could you please clarify which aspects do not align? The training data in your screenshot appears to match the description in the paper.
Regarding the inference task, we haven't uploaded the human demonstrations for the 4-subtask combinations, but you can perform inference using the 3-subtask combinations, such as 'oven draw cloth' and 'draw cloth oven'. Meanwhile, I will try to locate and upload the 4-subtask human demonstrations. It's worth mentioning that we did not capture demonstrations involving four subtasks with the robot, as our evaluation in the paper's experiment section did not include tasks with the "same embodiment" involving four subtasks.

I am  a beginner and very interested in your research. I have been studying your code carefully recently. Could you please tell me which part of the code the following two experimental parts correspond to？ Thank you！

For dataset and instructions, please see simulation dataset and training/simulation section in readme. The repo contains both pretraining and evaluation on simulation environment. Regarding to realworld, the repo provides code to do pertaining. The realworld evaluation is largely based on diffusion policy repo: https://github.com/real-stanford/diffusion_policy.


Are you planing to implement skip_audience check option?

def validate_audience
  return true if options[:skip_audience]

pretty inconvenient to have to create separate app just for development and testing purposes...

Are you able to provide a PR for this?