Apollo Query and Mutation components: JSX props should not use functions (react/jsx-no-bind)

I'm using the Apollo's <Mutation> component like this:
import gql from "graphql-tag";
import { Mutation } from "react-apollo";

const ADD_TODO = gql`
  mutation addTodo($type: String!) {
    addTodo(type: $type) {
      id
      type
    }
  }
`;

const AddTodo = () => {
  let input;

  return (
    <Mutation mutation={ADD_TODO}>
      {(addTodo, { data }) => (
        <div>
          <form
            onSubmit={e => {
              e.preventDefault();
              addTodo({ variables: { type: input.value } });
              input.value = "";
            }}
          >
            <input
              ref={node => {
                input = node;
              }}
            />
            <button type="submit">Add Todo</button>
          </form>
        </div>
      )}
    </Mutation>
  );
};

I get this error:
[eslint] JSX props should not use functions (react/jsx-no-bind)
I think it is complaining about:
onSubmit={e => {
  e.preventDefault();
  addTodo({ variables: { type: input.value } });
  input.value = "";
}}

because is an arrow function.
But it's the default in Apollo React Docs: https://www.apollographql.com/docs/react/essentials/mutations.html.
So... it's a good way or we need a function in constructor?
How can I fix this and suggest it to Apollo React team?

To satisfy the rule, you either need to configure it to allow inline arrow functions, or you need a constructor-bound instance method.

In general, it's a minor performance hazard. In this case, it's on a DOM component, so it's fine.

Can you explain it better this phrase? Thanks.

In this case, it's on a DOM component, so it's fine.

Yes - DOM/html components (ie, host nodes, like div, span, etc) don't have the same pitfalls here that custom components do. Namely, they're not PureComponents, so there can't possibly be any rendering performance hit (only the minimal hit of "creating new functions")


[WIP] Trying out self-hosted runner for running tests

Description

Fixes #

PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which has an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] If applicable, the PR references the bug/issue that it fixes in the description.
[ ] New Unit tests were added for the changes made and CI is passing.

Quality of Code and Contribution Guidelines

[ ] I have read the contribution guidelines.

Since we're moving Python 3.9 build in GitHub action, I don't think we need this change.


Add networkx tutorial and fixed vineyard version

What do these changes do?

Related issue number

Fixes

Codecov Report

Merging #1412 (99d7760) into main (88e7670) will decrease coverage by 37.70%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main    #1412       +/-   ##
===========================================
- Coverage   77.87%   40.17%   -37.71%
===========================================
  Files          88       88
  Lines        9660     9660
===========================================
- Hits         7523     3881     -3642
- Misses       2137     5779     +3642

Impacted Files
Coverage Δ

python/graphscope/tests/unittest/test_app.py
0.00% <0.00%> (-100.00%)
:arrow_down:

python/graphscope/tests/unittest/test_lazy.py
0.00% <0.00%> (-100.00%)
:arrow_down:

python/graphscope/tests/unittest/test_context.py
0.00% <0.00%> (-100.00%)
:arrow_down:

python/graphscope/tests/unittest/test_session.py
0.00% <0.00%> (-100.00%)
:arrow_down:

python/graphscope/tests/unittest/test_download.py
0.00% <0.00%> (-100.00%)
:arrow_down:

python/graphscope/tests/unittest/test_java_app.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...ython/graphscope/tests/unittest/test_cython_ast.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...ython/graphscope/tests/unittest/test_serailaize.py
0.00% <0.00%> (-100.00%)
:arrow_down:

python/graphscope/analytical/udf/patch.py
3.47% <0.00%> (-96.53%)
:arrow_down:

...thon/graphscope/tests/unittest/test_scalability.py
0.00% <0.00%> (-96.16%)
:arrow_down:

... and 47 more

Continue to review full report at Codecov.

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

I suggest this should be tutorial -03?
btw, could you add a prefix 0 for tutorials making them start with 01,02,03...
such that the tutorials can be in the right order on the left panel.


Power state vs mute state

When using either Eve Home or Home.app Mute state is prioritised over power (play/pause) state.
In Eve this means that a player that is not playing anything still appears as on in all overviews because audio is on (i.e. player is not muted).

I’ve tried to re-order the custom attributes in the eve home app but this makes no difference. Nor does hiding the audio (mute) attribute.
Any chance that the priority/order of the attributes can be changed in the plugin or will that not work either?

Very basic config for this plugin. Service is defined as speaker to avoid mixing with other switches. Works very well apart from the issue with the overview in the apps. But I guess above answers my question, when mute is only mandatory property for speaker service it makes sense that this is what is prioritised.
With regards to the Home app I think I am causing confusion. In the Apple build-in home app this plugin shows as unsupported here as well. I was referring to Matthias Hochgatterer‘s very excelente home app. Sorry about that and thanks for your clarification. Maybe I need to try using switch instead of speaker as service type and see how that works in my setup.

Love Matthias' Home app, but I don't think it allows you to sort the characteristics.
Yes, using "switch" instead should address this.


Storybook : Initial commit for Add Batch Details

Storybook : Initial commit for Add Batch Details

I have made some changes to the styling for the dropdown to better match the input fields. I have checked on chrome and firefox on windows and mac and it looks consistent.

Hi Mahie, I also made a commit to suggest using the following colors for hover effect instead of lightgreen.
input.date and input.input-text classes have #f2f2f5. I also added active mode to their style with the same colors.
dropdown button's .select-wrapper select has #f0f0f3 (because this one doesn't have inner shadow unlike others, it needed to be a little bit darker comparing others)


create broadcast performance improvements

This patch is includes the fixes I've been using to address the performance overhead from unmounting incurred by the implmentation of createBroadcast. This should fix the issue: https://github.com/styled-components/styled-components/issues/931#issuecomment-318827123 (thanks for the ping! intended to open this PR this week).
It sounds like there's some talk of switching to theming, so I wanted to open this, and another branch of perf improvements I've been trying locally for feedback.
I tried using brcast directly and then had slightly better perf using a slightly different implementation; left some notes describing the difference in commit messages.

Hiya, thanks for the PR :+1:
I think it'd be wiser to switch directly to theming. This was a longstanding plan and would achieve the same, perf-wise.
cc @mxstbr

I'm happy to switch to theming but if this implementation is advantageous over brcast I'd rather merge this for noe until we can get a patch upstream?
/cc @vesparny

@mxstbr the brcaat lib switched to this implementation a while ago :tada: With the tiny, nice detail that the unsubscribe function uses the id in a closure instead of ever passing it out: https://github.com/vesparny/brcast/blob/master/index.js

The implementation in this PR is slightly different because instead allocating the unsubscribe function it returns a subscription id.
I'd love to benchmark perf differences (how?) and change accordingly brcast implementation if
Worth.
That would be a breaking change in case.

I've already ditched the Array.forEach in favor of the more performant for loop. It has been released in<EMAIL_ADDRESS>

@philpl did you read the OP? :wink:

I tried using brcast directly and then had slightly better perf using a slightly different implementation; left some notes describing the difference in commit messages.

@mxstbr yea, but compared to the previous impl it should already be faster, and we do want to switch to theming anyway. There is no need for a step inbetween when we can fix this problem in brcast and can stop having to worry about this.
Also we're entering a territory where more accurate benchmarks are needed. Unsubscriptions are a relatively rare operation. How fast does that have to be compared to what we're optimising in v3, style injection and generation/processing?

@philpl I think making the switch to theming makes sense; however this is currently a big bottleneck in a large application I'm working in. For our use case (virtualized scrolling), this patch's perceived performance improvement is on par with the batch-updates branch branch. Is there anything I can do to help with the switch to theming?
Absolutely agree that more accurate benchmarks are needed. Do you have any recommendations for tests that are trying to measure something like GC optimizations? My intuition here would be to measure times for creating large numbers of non-trivial styled component trees.

Unsubscriptions are a relatively rare operation.

I'd like to add that this patch, if I'm understanding V8s GC strategy, also has an impact on component mount times as well. unsubscribe as implemented in brcast has to allocate a new unsubscribe callback on mount, potentially triggering GC.
I. agree that unsubscription is fairly uncommon, but I think the two biggest use-cases are performance sensitive; e.g. unmounting pages in response to routing changes (noted in https://github.com/styled-components/styled-components/issues/931), and virtualized scrolling.

@schwers

I think making the switch to theming makes sense; however this is currently a big bottleneck in a large application I'm working in. For our use case (virtualized scrolling), this patch's perceived performance improvement is on par with the batch-updates branch branch.

Hm, I actually never thought about these cases. Indeed with virtualised scolling, unsubscriptions are frequent and not as rare as what I was thinking of 😓

is on par with the batch-updates branch branch.

That is quite surprising, since there's no css injection operation during unsubscription, which makes the comparison of a benchmark with its performance purely based on the number of rules and new rules that are being injected 🤔  But that also means that you must be seeing a significant jump in perf

I'd like to add that this patch, if I'm understanding V8s GC strategy, also has an impact on component mount times as well. unsubscribe as implemented in brcast has to allocate a new unsubscribe callback on mount, potentially triggering GC.

I wasn't even thinking about this as well 😅 That is probably a good explanation of why this is more significant than what I expected.

Is there anything I can do to help with the switch to theming?

So reconsidering all the points we've discussed, I think it's fair to say that we should prefer merging this for now rather than switching over to theming. Relying on the same core libs is nice in the long run, but before v3 we won't even have any interoperability with the other component-based css-in-js libs, so it's not important right now.
So I think @mxstbr is right:

I'm happy to switch to theming but if this implementation is advantageous over brcast I'd rather merge this for noe until we can get a patch upstream?

:+1:

Yeah I watched the app @schwers is building and switching pages was super painful to watch, so I'd love to land this!

I'd be happy to implement this also in brcast.
This way also glamorous and any lib leveraging theming would benefit .

@philpl @mxstbr updated with the deprecation notice! and added some perf comparisons to theming in https://github.com/styled-components/styled-components/pull/1051#issuecomment-319249833

Moved the changes from discussion in here. I tried benchmarking in comparison, seems marginally better, but doesn't seem like a big enough change to measure reliably with my current setup (local app)

Clarification: I mean the changes in https://github.com/styled-components/styled-components/commit/b6b9eccf3f4036aeadbc59474e4f04b022d4a0d4 didn't have a noticeable impact in my test app.
@philpl did you get a chance to look at https://github.com/styled-components/styled-components/pull/1051#issuecomment-319249833 ?
Wondering if I should close this in favor of theming for now?

@schwers

I mean the changes in b6b9ecc didn't have a noticeable impact in my test app.

Stuff like delete and bind are still so fast despited deopts that it's not a big bottleneck during runtime that is noticeable.
Regarding the comment: https://github.com/styled-components/styled-components/pull/1051#issuecomment-319249833
It looks like the difference to theming is a lot bigger than what I expected, once again 😆
The problems right now are:

The bundle size is bigger than this patch (arguably a big deal since everyone's eyes are on it right now)
I'd expect it to be slightly slower based on the optimiations we've discussed here (but we don't yet have benchmarks for theming that include other optimisations here)
The GC looks like it's sawtoothing (@probablyup) but comparing the nodes (48,500 vs 16,200) looks to me like it just looks like it. Also the time spent in GC is shorter and if you can tell us whether FPS is stabler in this PR, then I'd say the performance is better on all metrics

@mxstbr It's really a question of what we're trying to get out of theming. We can still contribute our findings, but maybe we should merge this PR, and wait for them to fix these issues?

The GC looks like it's sawtoothing (@probablyup) but comparing the nodes (48,500 vs 16,200) looks to me like it just looks like it.

FWIW I think some of the sawtoothing is a bug in our app 😄

Also the time spent in GC is shorter and if you can tell us whether FPS is stabler in this PR, then I'd say the performance is better on all metrics

Yup, it does seem more stable with this patch. I notice less 'flicker' where row elements have yet to render, and overall seems a little smoother.
I'd be happy to help theming implement these changes, though I won't have much time until later this week.

@schwers That sounds really good actually! :+1:
@mxstbr Should we try to get this merged and then look into whether we can add theming on top to compare the perf with the optimisations that are already included in this PR? If theming turns out to be significantly slower, we wouldn't have to merge it right away, but can point out some sources of worse perf and wait for them to fix it up.

@philpl Did you mean #1048? :) What do you think of a slightly more incremental approach? i.e. would you be open to merging this patch first, then as changes land in theming we could have a baseline to compare against?
w.r.t the plan for: https://github.com/styled-components/styled-components/pull/1049 I'll try to split out the static styles first into a PR in the next day or so.
so I'm thinking it could really be a series of small patches

static styles optimization
faster classname generation (src from #1049)

I'm less sure about these changes:

flatten updates (src from #1049)
native array methods -> for (not a major concern for most apps, but could reduce some incremental allocations for use cases like virtualized-scrolling)

@schwers I was thinking of merging #1049 first actually, but if we can merge this PR first that's fine to me as well, as #1049 still needs some time for splitting it up, etc. It really depends on @mxstbr. I'm not too opinionated about the order of changes, and after some thinking, I don't consider the trade-offs of the theming PR worth it for now. it'll need some improvements.

flatten updates (src from #1049)

We should probably exclude them from the PR for now, and split it up into even more smaller incremental PRs. That would greatly increase my confidence in every separate change, since it's easier to see where our tests fall short, what introduces regressions, and which part of it improves perf significantly.

native array methods -> for (not a major concern for most apps, but could reduce some incremental allocations for use cases like virtualized-scrolling)

That would benefit from a separate PR as well, since we could then see how significant it actually is on its own

I don't have time to do a deep-dive on this, please go ahead and merge in the order you want to 😜

@philpl @mxstbr Can we start with merging this patch then? I've squashed the commits down to help with merging (should I not do that for this project if you use the github merge functionality?).

If @philpl is happy with this patch I say we go ahead and merge this 🛳

@mxstbr @schwers just some minor nits I wanted to address before merging this (sorry 😅 )

@philpl no worries, good ideas!

Just ran the benchmarks and they aren't super flattering at the moment:
v2.1.2
======

Results for browser
                                   styled         cssta
---------------------------------  -------------  -------------
simple component                   0.113±0.019ms  0.011±0.006ms
prop changes                       0.254±0.045ms  0.051±0.011ms
prop shorthands                    0.126±0.043ms  0.009±0.003ms
prop shorthands with prop changes  0.294±0.121ms  0.047±0.002ms

branch (rebased against master locally)
=======================================

Results for browser
                                   styled         cssta
---------------------------------  -------------  -------------
simple component                   0.174±0.044ms  0.013±0.002ms
prop changes                       0.314±0.064ms  0.053±0.010ms
prop shorthands                    0.167±0.058ms  0.011±0.002ms
prop shorthands with prop changes  0.322±0.104ms  0.044±0.003ms

That being said, benchmarks rarely reflect real-world perf.

@probablyup does that benchmark include unmounting? (doesn't look like it to me) That's what this PR improves, everything else is mostly noise.

@mxstbr doesn't. shouldn't be hard to add though. I'll make myself a note to submit a PR

Thanks!

@probablyup based on the changes and the error range of the benchmark, I'd say it's not significant. And as Max says, it doesn't include actually include in mounting. Also subscribing to theme changes is not included as well, if I'm not mistaken.
Generally the benchmark leaves a lot to be desired and hasn't been a great indicator in my experience :/

@philpl 😅 I added the propTypes because of linter errors from the react/prop-types rule. just added https://github.com/styled-components/styled-components/pull/1048/commits/83ded61434979c5acb7bbdd5df7df6566377350b to remove that and worked around it with disable comments

@schwers Weird! When did this rule become active? It never reported anything in this file before, I think

@philpl it started happening when I removed the abstract base class. Seemed like it was previously no-op'ing instead of trying to resolve the parent propTypes

@schwers OH! It didn't work anymore because we were extending the abstract class! It probably checks whether it's extending Component. Ok, anyway. Let's merge this for now and deal with that rule later


Add Timepicker

Closes #1293
📑 Description
This Pull Request adds a fully functional Timepicker.
https://flowbite.com/docs/forms/timepicker/

[x] Default timepicker
[x] Timepicker with icon
[x] Timepicker with dropdown
[x] Timepicker with select
[x] Timepicker range selector
[x] Timerange with dropdown
[x] Timerange picker with toggle
[x] Inline timepicker buttons
[x] Modal with timepicker
[x] Drawer with timepicker

Status

[] Not Completed
[x] Completed

✅ Checks

[x] My pull request adheres to the code style of this project
[x] My code requires changes to the documentation
[x] I have updated the documentation as required
[ ] I have checked the page with https://validator.unl.edu/
[ ] All the tests have passed
[ ] My pull request is based on the latest commit (not the npm version).

ℹ Additional Information

Summary by CodeRabbit
Release Notes

New Features

Introduced the Timepicker component for flexible time selection, supporting various modes such as dropdown, range, and inline buttons.
Added comprehensive documentation with detailed usage examples for the Timepicker component.

Bug Fixes

Enhanced testing coverage for the Timepicker component to ensure proper functionality.

Chores

Updated the package.json to include the new Timepicker component in the exports.
Added a new JSON file defining the Timepicker component's properties and events.

Thank you for your PR.
I had a quick look and the followings are what I found.
Default timepicker

When I click outside to close the dropdown, the selected goes back to 00:00.
Above issue happens when you change the selected time.

Inline timepicker buttons
When I select a date, it doesn't highlight. Also when I click outside, the letter primary color disappear.
Modal with timepicker
Same issues as Inline timepicker buttons
Drawer with timepicker
As you see in the following image, it has wider space between day and time.

Thank you for your PR. I had a quick look and the followings are what I found.
Default timepicker
1. When I click outside to close the dropdown, the selected goes back to 00:00.

2. Above issue happens when you change the selected time.

Default Timepicker doesn't have a dropdown, so I'm struggling to replicate it.

Inline timepicker buttons
When I select a date, it doesn't highlight. Also when I click outside, the letter primary color disappear.
Modal with timepicker
Same issues as Inline timepicker buttons

This is an issue with the Datepicker component, isSelected(day) isn't reactive, so the selected button's color isn't being updated with the component being open | inline
I'll submit a PR soon addressing this issue. (Fix below)
function isSameDate(date1: Date | null, date2: Date | null): boolean {
    if (!date1 || !date2) return false;
    return date1.toDateString() === date2.toDateString();
  }

  $: isSelected = (day: Date): boolean => {
    if (range) {
      return isSameDate(day, rangeFrom) || isSameDate(day, rangeTo);
    }
    return isSameDate(day, value);
  };

Drawer with timepicker
As you see in the following image, it has wider space between day and time.

Sorry, visual design isn't my strong suit. 😅
I've submitted a commit that should be more pleasant to the eye.

Please let me know when it is ready.

Please let me know when it is ready.

It looks okay to me. Please let me know if you have anything you want me to add/change. :)

When I click outside to close, the time selected goes back to 00:00.

When I click outside to close, the time selected goes back to 00:00.

That is weird. I'll test this out and try to stop it from happening.

Sometimes, when I click the inside field, the dropdown doesn't open. I noticed that I have to click between numbers and right icon. This means clicking a number doesn't open a dropdown. Is it possible to open the dropdown when a user clicks anywhere in the field?

Ah, by chance, are you using Google Chrome for development? I usually develop using Firefox, which means this may be a browser compatibility issue. I'll see if I can sort this out soon.

Hover doesn't change to a pointer. It needs hover:cursor-pointer.

I'll add this in tomorrow afternoon (AEDT).


SMTPSenderRefused

[2017-09-26 19:14:10,989: ERROR/MainProcess] Task app.send_async_email[619b395f-97d7-43e9-b188-fe718d9de7c5] raised unexpected: SMTPSenderRefused(530, '5.5.1 Authentication Required. Learn more at\n5.5.1  https://support.google.com/mail/?p=WantAuthError i41sm3459410uaf.2 - gsmtp'<EMAIL_ADDRESS>Traceback (most recent call last):
File "/home/msalinas/Documents/flask-mail/flask-celery-example/env/local/lib/python2.7/site-packages/celery/app/trace.py", line 240, in trace_task
R = retval = fun(*args, **kwargs)
File "/home/msalinas/Documents/flask-mail/flask-celery-example/env/local/lib/python2.7/site-packages/celery/app/trace.py", line 438, in protected_call
return self.run(*args, **kwargs)
File "/home/msalinas/Documents/flask-mail/flask-celery-example/app.py", line 38, in send_async_email
mail.send(msg)
File "/home/msalinas/Documents/flask-mail/flask-celery-example/env/local/lib/python2.7/site-packages/flask_mail.py", line 492, in send
message.send(connection)
File "/home/msalinas/Documents/flask-mail/flask-celery-example/env/local/lib/python2.7/site-packages/flask_mail.py", line 427, in send
connection.send(self)
File "/home/msalinas/Documents/flask-mail/flask-celery-example/env/local/lib/python2.7/site-packages/flask_mail.py", line 192, in send
message.rcpt_options)
File "/usr/lib/python2.7/smtplib.py", line 736, in sendmail
raise SMTPSenderRefused(code, resp, from_addr)
SMTPSenderRefused: (530, '5.5.1 Authentication Required. Learn more at\n5.5.1  https://support.google.com/mail/?p=WantAuthError i41sm3459410uaf.2 - gsmtp'<EMAIL_ADDRESS>

The error message is pretty clear. Do you have any questions for me?


Fix iptables not running disabled then enabled again

Fix issue with rules not being applied after a iptables::disable run followed by running it enabled again.
This will resolve #26

I think this also resolves #22?


Add gradle lockfile support

Add support for:

gradle.lockfile
buildscript-gradle.lockfile

Reference: https://docs.gradle.org/current/userguide/dependency_locking.html#lock_state_location_and_format

/gcbrun

Thank you for the PR!

CC @G-Rath

@G-Rath Thanks for the suggestions. I have updated the PR.

/gcbrun


Atom freezes on class-name-format option

Hello!
I'm using Atom with linter-sass-lint

Atom version: 1.20.1
linter-sass-lint version: 1.8.3
Platform: Linux

class-name-format in the listed below format cases Atom to freeze on file opening and saving.
.sass-lint.yml content
files:
  include: '**/*.scss'
options:
  formatter: stylish
  merge-default-rules: false
rules:
  bem-depth:
    - 1
    - max-depth: 2
  border-zero:
    - 2
    - convention: 0
  brace-style:
    - 2
    - allow-single-line: false
  declarations-before-nesting:
    - 2
  class-name-format:
    - 1
    - convention: strictbem

scss file content
.n1-price-list-table__column-description_media-ads__column-description {
    padding-left: 10px;
}

removing class-name-format option solves the freezing

Seems to parse fine in gonzales so will investigate further to see why this is causing a suspected infinite loop


Add link to ToU

https://github.com/OCHA-DAP/hdx-hapi/blob/d370cbe3304ca7405da6e8cafe47da03288c7e1f/docs/index.md?plain=1#L9
Add a new paragraph below the linked line.  Text should read:
Use of HDX HAPI is governed by these [Terms of Use](https://data.humdata.org/hapi/terms).

Ah, sorry. I see there was already a section for this at the bottom. Will edit the description now.


Defect when provisioning access to a deleted role assignment

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to 'FAM TEST'
Select FOM application
Click on 'Grant Access screen'
Create a new user (BCeID user) with FOM submitter role and Forest client (00082820)
Once created, delete role assignment
create user again by repeating step 3-6

Actual Result: Application Error has Occurred
Expected Result: User role assignment has been created successfully

Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

https://app.zenhub.com/files/486378283/3f084673-3e02-49ea-bebb-653a49a2dcfd/download

Added prod log from Basil.
https://app.zenhub.com/files/486378283/81d5ecb1-790e-4473-8fbc-144343c120d2/download

From the log and prod data:
Backend has a check on if user exists, based on 'user_type_code' (B or I) and 'user_name' (ilike - case insensitive), before creating a user.
For this case from production database query, it shows 2 fam_user records ("DVALK" and "DValk"). So, backend returns error when the check found more than 1 user with "the same" name and type.
famdb=> select * from fam_user where UPPER(user_name)='DVALK';
 user_id |            user_guid             |                          cognito_user_id                          | user_name |                   create_user                   |
 create_date          |  update_user  |      update_date       | user_type_code
---------+----------------------------------+-------------------------------------------------------------------+-----------+-------------------------------------------------+---------
----------------------+---------------+------------------------+----------------
     552 | FDFEE614672C4B56A3E168CD91C790F7 | prod-bceidbusiness_fdfee614672c4b56a3e168cd91c790f7@bceidbusiness | DValk     | fam_proxy_api                                   | 2023-04-
12 00:00:00+00        | fam_proxy_api | 2023-04-12 00:00:00+00 | B
     551 |                                  |                                                                   | DVALK     | prod-idir_7f27542b4f1a45478f90b967ff34d74b@idir | 2023-04-
12 18:07:59.618679+00 |               |                        | B
(2 rows)

Based on prod data:
First fam_user record "DVALK" (user_id=551) looks like is created by Julius using FAM frontend to create user/role assignment.
Second fam_user record "DValk" (user_id=552) likely is from the user login to FOM (and based on prod data, it should be user's first time and no role returned for this login user to FOM)

How the auth-lambda function created second fam_user when there exists already first fam_user (user_id=551):
Possibly, the auth-lambda function is based on unique constraint: CONSTRAINT fam_usr_uk UNIQUE (user_type_code, user_name)
and this isn't case insensitive. The user with the same user_type could have same name with different case ("DVALK", "DValk").
In this case, auth-lambda could not find and update first user.
     INSERT INTO app_fam.fam_user
         ...
         ...
         ON CONFLICT ON CONSTRAINT fam_usr_uk DO
         UPDATE SET user_guid = {user_guid},  cognito_user_id = {cognito_user_id};

Just add some notes:

When a new user has been created through the FAM UI, the username depends on whatever the user types in, we don't make changes
When a new user has been created through the first time login to the application integrated with FAM, the username will be the "custom:idp_username" from IDP

I don't understand these comments - the user name must be identical in both scenarios (or at least matched to the same user record), or FAM won't work as intended.
Scenario 1: User John Smith logs into FAM. Their IDIR is supplied as JSmith. A user record is created (if it doesn't already exist), or is updated, matching on the user id (and domain).
Scenario 2: An admin grants access to user John Smith. They likely type JSMITH or jsmith for the user id. A user record is created (if it doesn't already exist), and an access assignment is created linking to the user identified by the user id (and domain)
FAM must ensure that the user record in scenario 1 and scenario 2 are the same, irrespective of the order they occur in.

Yes, so when create user through FAM UI, we call this method to check if there is an existing user, think it's case insensitive now

But when the user has been created through the auth function, it's checking the constraint fam_usr_uk, which is case sensitive
ALTER TABLE app_fam.fam_user ADD CONSTRAINT fam_usr_uk UNIQUE (user_type_code, user_name);

I just document how we fixed the dev deployment here, we could move it to other place later:
To remove the KMS key, we need to use the terragrunt cli:

download required cli tools

terraform: https://developer.hashicorp.com/terraform/downloads
terragrunt: https://terragrunt.gruntwork.io/docs/getting-started/install/

login to terraform cloud, the token can be found through here

Go to our repository directory, for FAM DEV environment, go to the terragrunt file directory for our FAM DEV, which is at terraform/dev/terragrunt.hcl
Set up the environment variable export tfc_workspace=sfha4x-dev, 'sfha4x-dev' is our license plate for dev
Run terragrunt init and terragrunt state list  to see all the state
And then run terragrunt rm [kms_key_name]

But Basil and I both have problems run the terragrunt command, it hangs there, so we got the help from Warren Uniewski, he helped us remove that. So the key is still in the AWS scheduled for deletion, but terraform will ignore it

In order to fix this problem,

we first fixed the FOM-DEV deployment, reference my last comment
and then we create a branch for the hotfix, which includes

update the constraint that the auth function is using, update that to support case insensitive when check if the user exists or not
add flyway script to find and remove duplicate user records
update local cognito env variables, so tests can run in pipeline
merged a specific commit that we must have, which is Conrad's change for RDS postgres verison
merged a specific commit that we must have, which is FOM demo callback urls

and then we fix the hotfix release please pipeline, update the target branch to be "hotfix", so when we merge fix to the hotfix branch, it can trigger the hotfix release

Thanks all for working urgently on this, much appreciated.


Database schema updates complete with postprocessing fixes and db relationship redesign

Rebase and Squash of https://github.com/pdarg/tmlpstats/pull/41

I've already tested importing Boston's sheets up to the week after the 2nd classroom. Import and data relationships are working.
Next up is to test corner cases. Here are a few off the top of my head:

2 users with the same First Name/Last Initial from the same center
2 team members
2 registrations
1 user is a registration, 1 is a team member
1 user is a registration, 1 is an accountable (contact tab)
1 user is a team member, 1 is an accountable (contact tab)
A registration's reg_date changes
A registration changes from current to future weekend
An accountable (contact tab)'s info changes
An accountable (contact tab)'s person changes
A Team member's name changes
A registration's name changes


Update README.md

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Hello @shra1cumar,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


add net 4.5 support

changed from dotnet framework 4.5.2 to dotnet 4.5, support .NET Framework 4.5, 4.5.1, 4.5.2

Please see #256


[DAO tab] MENU is undefined

Describe the bug
Following error appears on DAO tab

To Reproduce
Steps to reproduce the behavior:

Go to https://multicall.app/#/dao
open browser dev tools
choose any DAO in the DAO selector
See error

Expected behavior
Make sure MENU is defined before
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: windows 11
Browser: firefox
Version: latest

Reason
Scenario 1 (all good): User comes from APP page to DAO page
In this case the MENU has already been mounted, so it's defined. The Dao selector will now update the Dao address, which includes changing value on cards or other stuff in the MENU. This works as intended.
Scenario 2 (error occurs): User starts off on the DAO page or refreshed
Now MENU is not mounted, but the same code from before will try to update the values in the MENU and fails (causing the error in question). This is not really a problem since the MENU will load the address from the Dao selector whenever it's mounted.
Conclusion
The error is not at all critical and can simply be caught and dismissed.


fix serialization of ignoreOrderOfSameNode for equalToXml

Fixes serialization of ignoreOrderOfSameNode property for the equalToXml body. Property was not serialized because getter was missing hence was never applied
References
https://github.com/wiremock/wiremock/pull/2747

Submitter checklist

[x] Recommended: Join WireMock Slack to get any help in #help-contributing or a project-specific channel like #wiremock-java
[x] The PR request is well described and justified, including the body and the references
[x] The PR title represents the desired changelog entry
[x] The repository's code style is followed (see the contributing guide)
[x] Test coverage that demonstrates that the change works as expected
[x] For new features, there's necessary documentation in this pull request or in a subsequent PR to wiremock.org

Thanks!


Can't build 5.11.* release on Windows

Hi @rnicholus,
Just notice changes in v5.11.* and i've got some issue when I'm trying to build bower distribution for 5.11.1. Currently I'm working on Windows 10 64 bit with node.js v6.2.1 then I got this when running npm test.
$ npm test

><EMAIL_ADDRESS>test D:\Workspaces\Codes\fineupload-dist\src
> make lint && make test

D:\Workspaces\Codes\fineupload-dist\src\node_modules\.bin/jscs client/js/*
/bin/sh: D:WorkspacesCodesfineupload-distsrcnode_modules.bin/jscs: No such file or directory
Makefile:207: recipe for target 'lint' failed
make: *** [lint] Error 127
npm ERR! Test failed.  See above for more details.

And I guess that this issue might be happen on windows only (not tested on linux yet), any advice for this issue?
Update:
It run well on Linux environment.
Regards

That's expected. You will need a Linux or UNIX filesystem to build fine uploader going forward. On Windows I imagine cygwin will work or Windows 10 bash.

Actually I'm working with cygwin, spesificly on babun.

I'm not sure what the problem might be then as I don't use Windows for development. If you find a fix, please let me know or open up a PR. Or, i you can locate the specific issue with the build, let me know so we can discuss further.

Is this preventing you from updating the bower distribution? Something definitely looks "off" in the error message above. Cygwin is supposed to be mostly POSIX compliant, but I haven't tested myself and I don't know if the flavor of cygwin you are using is suitable.

I think the problem is here, which is npm bin command will return bin directory for our current project. On linux of course it will return something like /some/project/node_modules/.bin but on windows it will return D:\some\project\node_modules\.bin which is \ (backward slash) will be escaped by POSIX it self, in that case if we call $(npm-bin)/jscs will return D:someprojectnode_modules.bin/jscs instead of D:\some\project\node_modules\.bin/jscs.

I'm not certain what the solution is here. I was under the assumption that this would work as-is in cygwin.

Created pull request to fix cygwin.
#1698

@rnicholus this can be closed I think

@SinghSukhdeep Good call.


ASP.NET Core RC2

I've upgraded from RC1 to RC2, and part of that meant targeting net452 now instead of dnx451 / net451.
I've update my jsnlog to latest version 2.17.1 and I have noticed that it no longer compiles, specifically this line:

I think this is because JsnLog doesn't support ASP.NET Core RC2 yet - but could you confirm?

You're right, I haven't updated JSNLog for ASP.NET Core RC2. Flat out at work.
A pull request to fix this would be appreciated.

Ok I have upgraded this web application to RC2 in a branch (in my fork).
I had to comment out this line:
app.UseJSNLog(new LoggingAdapter(loggerFactory), jsnlogConfiguration);

Because JsnLog itself needs to be upgraded for RC2. Once that is done we can update JsnLog in the application and add the equivalent line of code back and all should be roses.
Do you want me to submit a PR at this point - and if so should it target master?

PR submitted that upgrades to RTM now that RTM is out.


How to add different channels into one channel?

I am writing a FCN model based on Resnet. I want add three previous tensors into one channel tensor. e.g:
add [None, 256, 224,224], [None, 512, 224,224], [None, 1024, 224,224], and [None, 2048, 224,224], into [None,1,224,224]. all channel values are added.
So, how can I do this?
Thanks very much!

One option would be to concatenate the tensors along the channel axis first using a merge layer, then use a lambda layer to sum and reduce the channel axis.


[Help Wanted] Show the menu when press g

How can I configure to show menu when I press trigger key such as g key just like the space key brings up the menu the gif in vspacecode website??

Follow https://vspacecode.github.io/docs/whichkey/#standalone and replace the space key with g. Let me know if you encounter any issues

@stevenguh Sorry for I didn't clearly describe my question before. The original question is updated.

oh, I see now!
At the moment this is not possible.
The keys under <SPC> are defined by VSpaceCode or WhichKey.
Instead, the keys under g are defined by you or by https://github.com/VSCodeVim/Vim
That's why it is not possible.


corrected "tutorial repository" url

Changed "tutorial repository" url to point to the GitHub repo, rather than the SciPy schedule page.

Thanks for the correction!
Whenever you see an improvement to make in pyvideo data, it will be more than welcome.


Improved Docs

These are minor corrections and they improve the text.

This was merged by a mistake. This is a spam PR, more details here:
https://blog.domenic.me/hacktoberfest/
I changed the label to "spam".


Hacktoberfest

Description
ADDED A SEARCH DESCRIPTION AND TAP THE ICONS.
Checklist

[x] I am making a proper pull request, not spam.
[x] I've checked the issue list before deciding what to submit.

Related Issues or Pull Requests
after this changes you're website looks more real
Add relevant screenshot or video (if any)

hope you like it .

resolve conflicts

hope you like it .


Hours editing page style

The html elements look squished together.
Can we update the style to give a better visual appearance?

Hey @jdbranham
i have added PR on this card.
https://github.com/savantly-net/franchise-manager/issues/66


rouge + in sass source

https://github.com/Eonasdan/bootstrap-datetimepicker/blob/development/src/sass/_bootstrap-datetimepicker.scss#L272
There is a + here, that causes the sass to fail, when importing the file

Opened a pull request instead, see #1635


General Cleanup

Convert more examples to new I/O access format.
Add dependency for LD file.

Move attic into another repo.


two pointer documentation

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
I want to explain the usage of two pointer algorithm in the article
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
closes #75

Please review @HarshCasper @ankitaggarwal23

Please review @HarshCasper @ankitaggarwal23

can anyone review please... @HarshCasper @ankitaggarwal23

Please review @HarshCasper @ankitaggarwal23

Please review @HarshCasper

Fix the CI build as well. Do a yarn build on your local machine and push the updates only when they pass.

Please review @HarshCasper .
One thing I want to say that NeoAlgo is just awesome. Thanks for this chance to contribute here, because of this i have build yarn first time.
Thanks again..
Looking forward to contribute here.

Fix the CI build as well. Do a yarn build on your local machine and push the updates only when they pass.

Please review @HarshCasper .
One thing I want to say that NeoAlgo is just awesome. Thanks for this chance to contribute here, because of this i have build yarn first time.
Thanks again..
Looking forward to contribute here.

Please review @HarshCasper

Please review @ankitaggarwal23


Not all packages are getting cached

I think I'm missing something but none of my packages that are listed in the dependencies section of my package.json are getting cached, but modules in my devDependencies are, along with some other modules I do not have listed. I'm guessing the latter is because those modules have dependencies of their own.
Thanks.

Was there ever a resolution for this?

I'm happy to investigate if I get an example package.json file so we can look at reproducing the issue. I suspect it's specific to some particular urls being loaded that are not yet catered for.

closing to clean up the issues list a bit; this looks like it may have been either old cached files but difficult to confirm.


0px bug on iOS

The 0px bug on iOS seems to be appearing again.
https://github.com/UniqueStudio/UniqueRecruitmentDashboard/blob/31bc9c7f66b42f87bd904d1d39666d4f9315d562/src/styles/drawer.tsx#L27

Changing to 1px looks good to me.

Fixed in 343e83f. Closed


STORM-2449 Ensure same key appears only once in State iterator

also don't expose TOMBSTONE keys

This implementation is for current Redis KV state.
I also have two State related pull requests #1970 and #1950 and I need to apply this patch to both of them. I'll update both after this patch is reviewed.
@arunmahadevan Please review and comment. Thanks in advance.

+1 LGTM
Before you apply this to #1970 and #1950, you can refactor the logic to make it re-usable across the different state implementations.


Disable keyboard control

Is it possible to disable Keyboard control? i.e. Left/Right going to next

Yes use the option keyboardControl added in 0.5.2
new Driver({
    keyboardControl: false   // default: false
})


The time step doesn't seem to work. I locked the seed test. This is the same problem as their flux version model. I'm not sure if it's a model problem or something else.

开始和结束时间似乎没有生效，我锁种子测试的，这是一个和他们flux版本模型一样的问题，我不确定是模型问题还是其他问题

Yes, the time step is currently unimplemented. I'll close this issue once I
add code for it
On Sat, Dec 7, 2024, 12:55 chenpipi0807 @.***> wrote:

开始和结束时间似乎没有生效，我锁种子测试的，这是一个和他们flux版本模型一样的问题，我不确定是模型问题还是其他问题
—
Reply to this email directly, view it on GitHub
https://github.com/Slickytail/ComfyUI-InstantX-IPAdapter-SD3/issues/6,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACDXG7JXYOIZGN2EU6YAQVL2ELO2LAVCNFSM6AAAAABTGEWUU2VHI2DSMVQWIX3LMV43ASLTON2WKOZSG4ZDINJVG43TEMQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

fixed in 5031e52.


Missing requests/limits for service-discovery Job

Description

Environment
OS:
Version:
Steps To Reproduce

Expected behavior

Actual Behavior

Additional context

double #305 ?


Fix/content

Small improvements and some unit tests added.

Thanks! I've just added a few comments, please check them out :)

Hello @leonorader .
Did you mean the issue?
If yes, let's merge this one, then I open a new PR for refactoring.
Thanks

@eurafa sorry, I forgot to submit them :)

No problem, @leonorader .
Please, read my new comments :)


Update README.md

Added a few words for clarity

Great, thanks a bunch @possnfiffer cc @hobojoe1848


Some questions about the experimental setting

Thanks for your excellent work. By the way, Happy Mid Autumn Festival.
I have some questions about the experimental setting.

How many times have you run Lafite on COCO in a supervision manner? And do you report the best FID 8.12 out of all runs?
How do you pre-process the original images in COCO to 256x256 resolution? Interpolation or Center-crop?

Happy Mid Autumn Festival.

At the time of submission, I only run the experiment once (with 25000 kimg), and report that result. Actually, that results in the paper is not the best results the model can get. If you continue training, the performance will be slightly improved. See jnhwkin's reproduced result at https://github.com/drboog/Lafite/issues/4.
The COCO images are center cropped and resized to 256*256.


Cannot set sbt version from command line

[x] I've read the CONTRIBUTING guidelines

steps
mkdir test
cd test

D:\Users\user\test>sbt sbtVersion
[warn] No sbt.version set in project/build.properties, base directory: D:\Users\User\test
[info] Loading settings from idea.sbt ...
[info] Loading global plugins from D:\Users\User\.sbt\1.0\plugins
[info] Set current project to test (in build file:/D:/Users/User/test/)
[info] 1.1.1

D:\Users\User\test>sbt -Dsbt.version=1.2.1 sbtVersion

problem
Error during sbt execution: sbt version cannot be empty (omit declaration to use the default)

expectation
1.2.1

notes
sbt version: 1.1.1

@mwisnicki Thanks for the report. It works for me on macOS, but I wonder if this is something specific to the batch script.

Actually could you try double quoting?
> sbt "-Dsbt.version=1.2.1" sbtVersion

Windows treats = as whitespace iirc.

@eed3si9n wow, thanks that was it!


Publish 01/06/2023 3:30 PM PT

Learn Build status updates of commit caf1de9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/app-only-auth-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/connect-to-exchange-online-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/whats-new-in-the-exo-module.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Export-QuarantineMessage.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


GTX 1070 source install bazel build -- Unsupported gpu architecture 'compute_61'

Here are my specs:

Ubuntu 15.10 (potential conflict with CUDA 7.5?)
NVIDIA GTX 1070 (compute capability 6.1)
CUDA 7.5
Cudnn v5.0

Error message:

ERROR: /usr/local/lib/python2.7/dist-packages/tensorflow/tensorflow/core/kernels/BUILD:1496:1: error while parsing .d file: /home/volcart/.cache/bazel/_bazel_root/109ad80a732aaece8a87d1e3693889e7/execroot/tensorflow/bazel-out/local_linux-opt/bin/tensorflow/core/kernels/_objs/batchtospace_op_gpu/tensorflow/core/kernels/batchtospace_op_gpu.cu.d (No such file or directory).
nvcc warning : option '--relaxed-constexpr' has been deprecated and replaced by option '--expt-relaxed-constexpr'.
nvcc fatal   : Unsupported gpu architecture 'compute_61'
Target //tensorflow/cc:tutorials_example_trainer failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 86.269s, Critical Path: 84.86s

It is clearly complaining about the compute capability. Is a compute capability of 6.1 supported? Surely.
I am installing from source.
Some dependency versions:
volcart@volcart-Precision-Tower-7910:/usr/local/lib/python2.7/dist-packages/tensorflow_src$ bazel version
Extracting Bazel installation...
.
Build target: bazel-out/local-fastbuild/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Thu Jan 01 00:00:00 1970 (0)
Build timestamp: Thu Jan 01 00:00:00 1970 (0)
Build timestamp as int: 0

volcart@volcart-Precision-Tower-7910:/usr/local/lib/python2.7/dist-packages/tensorflow_src$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.9/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.9.3-5ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.9 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.9.3 (Ubuntu 4.9.3-5ubuntu1)

volcart@volcart-Precision-Tower-7910:/usr/local/lib/python2.7/dist-packages/tensorflow_src$ nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2015 NVIDIA Corporation
Built on Tue_Aug_11_14:27:32_CDT_2015
Cuda compilation tools, release 7.5, V7.5.17

When I execute sudo ./configure I have tried different varients. Namely, the default for all options -- I only have one version of CUDA and Cudnn installed.
I've also tried the following confirguration -- to the same end...
volcart@volcart-Precision-Tower-7910:/usr/local/lib/python2.7/dist-packages/tensorflow_src$ sudo ./configure
Please specify the location of python. [Default is /usr/bin/python]:
Do you wish to build TensorFlow with Google Cloud Platform support? [y/N] n
No Google Cloud Platform support will be enabled for TensorFlow
Do you wish to build TensorFlow with GPU support? [y/N] y
GPU support will be enabled for TensorFlow
Please specify which gcc should be used by nvcc as the host compiler. [Default is /usr/bin/gcc]:
Please specify the Cuda SDK version you want to use, e.g. 7.0. [Leave empty to use system default]: 7.5
Please specify the location where CUDA 7.5 toolkit is installed. Refer to README.md for more details. [Default is /usr/local/cuda]:
Please specify the Cudnn version you want to use. [Leave empty to use system default]: 5
Please specify the location where cuDNN 5 library is installed. Refer to README.md for more details. [Default is /usr/local/cuda]:
Please specify a list of comma-separated Cuda compute capabilities you want to build with.
You can find the compute capability of your device at: https://developer.nvidia.com/cuda-gpus.
Please note that each additional compute capability significantly increases your build time and binary size.
[Default is: "3.5,5.2"]: 6.1
Setting up Cuda include
Setting up Cuda lib64
Setting up Cuda bin
Setting up Cuda nvvm
Setting up CUPTI include
Setting up CUPTI lib64
Configuration finished

I noticed CUDA 7.5 only supports Ubuntu 15.04 -- could this be a problem since I'm on Ubuntu 15.10?

I should note that a virtual_env install works totally fine, so maybe this isn't an issue?

CUDA 7.5 doesn't support Pascal cards, so you'll need CUDA 8.0
TensorFlow doesn't support CUDA 8.0, but you can make it work with extra
tweaks like in https://github.com/tensorflow/tensorflow/issues/3431
Also CUDA 8.0 doesn't support Ubuntu 15.10, so you may need to upgrade to
16.04, or fix a bunch of compilation errors by hand during install
On Thu, Aug 4, 2016 at 3:21 PM, Kendall Weihe<EMAIL_ADDRESS>wrote:

I should note that a virtual_env install works totally fine, so maybe this
isn't an issue?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/3651#issuecomment-237701269,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABaHKYhD2RL5i0C8pEoGLbdr-R2H-ANks5qcmX5gaJpZM4JdLVk
.

Do you know if the nightly wheels support CUDA 8.0?

They do not
On Aug 5, 2016 9:04 AM, "Kendall Weihe"<EMAIL_ADDRESS>wrote:

Do you know if the nightly wheels support CUDA 8.0?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/3651#issuecomment-237891477,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABaHPxAcLw5eXPeZFQHgG3dk7AOty-xks5qc18ngaJpZM4JdLVk
.

Fort verification when I add
cxx_builtin_include_directory: "/usr/local/cuda-8.0/include"
to
third_party/gpus/crosstool/CROSSTOOL
Am I adding it to the first line of the toolchain {... block
I'm having this issue now.

Our wheel files now come built for cuda 8.0 and cudnn 5.1
I think this issue is now obsolete, thus closing.


Decompiler warnings, no output?

When running the decomp.sh shell script from the jak-project directory (scripts/shell/decomp.sh), I only get some warnings when decompiling. Here's the output:
[2021-04-27 19:57:55:620] [info] GOAL Decompiler version 4

[2021-04-27 19:57:55:654] [info] Setting up object file DB...
[2021-04-27 19:57:55:655] [info] -Loading types...
[2021-04-27 19:57:55:885] [info] -Loading obj name map file...
[2021-04-27 19:57:55:977] [info] -Loading 36 DGOs...
[2021-04-27 19:57:56:488] [info] -Loading 7 plain object files...
[2021-04-27 19:57:56:488] [info] -Loading 197 streaming object files...
[2021-04-27 19:57:56:642] [info] ObjectFileDB Initialized

[2021-04-27 19:57:56:642] [info] Processing Link Data...
[2021-04-27 19:57:56:643] [info] Processed Link Data
[2021-04-27 19:57:56:643] [info]  Total 0.699806 ms

[2021-04-27 19:57:56:643] [info] Finding code in object files...
[2021-04-27 19:57:56:645] [info] Found code:
[2021-04-27 19:57:56:645] [info]  Code 0.001 MB
[2021-04-27 19:57:56:646] [info]  Data 0.000 MB
[2021-04-27 19:57:56:646] [info]  Functions: 7
[2021-04-27 19:57:56:646] [info]  fp uses resolved: 1 / 1 (100.000 %)
[2021-04-27 19:57:56:646] [info]  Decoded 347 / 347 (100.000 %)
[2021-04-27 19:57:56:646] [info]  Total 2.458 ms

[2021-04-27 19:57:56:646] [info] Processing Labels...
[2021-04-27 19:57:56:646] [info] Processed Labels:
[2021-04-27 19:57:56:646] [info]  Total 24 labels
[2021-04-27 19:57:56:646] [info]  Total 0.238546 ms

[2021-04-27 19:57:56:646] [info] Using IR2 analysis...
[2021-04-27 19:57:56:646] [info] Processing top-level functions...
[2021-04-27 19:57:56:646] [info] Found a total of 7 functions in 0.10 ms
[2021-04-27 19:57:56:647] [info]    0 unknown 0.00%
[2021-04-27 19:57:56:647] [info]    4 global  57.14%
[2021-04-27 19:57:56:647] [info]    2 methods 28.57%
[2021-04-27 19:57:56:647] [info]    1 logins  14.29%

[2021-04-27 19:57:56:647] [info] Processing basic blocks and control flow graph...
[2021-04-27 19:57:56:650] [warn] Function looping-code loops back to the first instruction. This is rare/less tested.
[2021-04-27 19:57:56:650] [info] Found 39 basic blocks in 7 functions in 3.53 ms:
[2021-04-27 19:57:56:650] [info]  0 functions (0.00%) failed to build control flow graph
[2021-04-27 19:57:56:651] [info]  4 functions (57.14%) had exactly one basic block
[2021-04-27 19:57:56:651] [info]  0 functions (0.00%) were ignored as assembly
[2021-04-27 19:57:56:651] [info]  0 functions (0.00%) were inspect methods

[2021-04-27 19:57:56:651] [info] Finding stack spills...
[2021-04-27 19:57:56:651] [info] Analyzed stack spills: found 0 functions will spills (total 0 vars), took 0.07 ms
[2021-04-27 19:57:56:651] [info] Converting to atomic ops...
[2021-04-27 19:57:56:657] [info] 7/7/7 (successful/attempted/total) functions converted to Atomic Ops in 5.51 ms
[2021-04-27 19:57:56:657] [info] 100.00% were attempted, 100.00% of attempted succeeded

[2021-04-27 19:57:56:657] [info] Running type analysis...
[2021-04-27 19:57:56:754] [info] 7/7/7/7 (success/attempted/non-asm/total) in 96.78 ms

[2021-04-27 19:57:56:754] [info] Register usage analysis...
[2021-04-27 19:57:56:785] [info] 7/7 functions had register usage analyzed in 30.97 ms

[2021-04-27 19:57:56:785] [info] Variable analysis...
[2021-04-27 19:57:56:852] [info] 7/7 functions out of attempted passed variable pass in 66.85 ms

[2021-04-27 19:57:56:855] [info] Initial structuring...
[2021-04-27 19:57:56:861] [info] 7/7/7 cfg build in 6.10 ms

[2021-04-27 19:57:56:861] [info] Storing temporary form result...
[2021-04-27 19:57:56:874] [info] Stored debug forms for 7 functions in 12.33 ms

[2021-04-27 19:57:56:874] [info] Expression building...
[2021-04-27 19:57:56:912] [info] 7/7/7 expression build in 38.16 ms

[2021-04-27 19:57:56:912] [info] Re-writing inline asm instructions...
[2021-04-27 19:57:56:913] [info] 7/7/7 rewrote inline-asm instructions in 0.93 ms

[2021-04-27 19:57:56:915] [info] Inserting lets...
[2021-04-27 19:57:56:929] [info] Let pass on 7 functions (14/39 vars in lets) in 13.93 ms

[2021-04-27 19:57:56:929] [info] Inserting anonymous function definitions...
[2021-04-27 19:57:56:929] [info] Inserted 0 anonymous functions in 0.34 ms

[2021-04-27 19:57:56:930] [info] Writing results...
[2021-04-27 19:57:56:930] [info] Writing IR2 results to file...
[2021-04-27 19:57:56:988] [info] Wrote 1 files (0.04 MB) in 58.84 ms

[2021-04-27 19:57:56:998] [info] - Finding game text...
[2021-04-27 19:57:56:998] [info] Processed 0 text files (0 strings, 0 characters) in 0.02 ms
[2021-04-27 19:57:56:998] [info] - Finding textures in tpages...
[2021-04-27 19:57:56:998] [info] Processed 0 / 0 textures -nan% in 0.00 ms
[2021-04-27 19:57:56:998] [info] - Finding game count file...
[2021-04-27 19:57:56:998] [warn] did not find game-cnt file
[2021-04-27 19:57:56:999] [info] Disassembly has completed successfully.

Additionally, the assets folder only contains two files, game_count.txt which is empty, and game_text.txt with the text:
(language-count 0)
(group-name "common")

Lastly, the decompiler_out folder only has five files, all-syms.gc, dgo.txt, gstate_disasm.gc, gstate_ir2.asm, and obj.txt (these files are somewhat larger and as a result I won't paste their contents here).
I copied all the files from Jak 1 (SCUS-97124) into the iso_data folder before running, and I tried running it with and without the resources folder present, but the result was the same both times.
My goal is to dump the assets for the game. How would I go about this?

Right now, the config is set up for just decompling. It is not capable of decompiling everything yet, so I have the default configuration just set to decompile gstate, which is the gstate_disasm.gc file that you get
If you want to extract textures and game text, you can change this part of the config
https://github.com/water111/jak-project/blob/master/decompiler/config/jak1_ntsc_black_label.jsonc#L54
to this:
  "allowed_objects":[],

  "type_casts_file":"decompiler/config/jak1_ntsc_black_label/type_casts.jsonc",
  "anonymous_function_types_file":"decompiler/config/jak1_ntsc_black_label/anonymous_function_types.jsonc",
  "var_names_file":"decompiler/config/jak1_ntsc_black_label/var_names.jsonc",
  "label_types_file":"decompiler/config/jak1_ntsc_black_label/label_types.jsonc",
  "stack_vars_file":"decompiler/config/jak1_ntsc_black_label/stack_vars.jsonc",

  "analyze_functions":false,
  "analyze_expressions":false,
  "function_type_prop":false,
  "insert_lets":false,
  "write_disassembly":false,
  "write_hex_near_instructions":false,

  "run_ir2":false,

which tells it to look in all object files, but not to decompile. It should find the textures/game text and put them in the assets folder with these settings.

What about models/animations, does it dump those?

At the moment no. There's only the texture ripper.

Oh okay.

We have not worked on understanding the art formats yet.


revert(#17570): fix dashboard editing for dashboards with non-ascii characters

SUMMARY
The bug: When a user saved a dashboard that contained a chart with non-ascii characters, the json_metadata became malformed, causing the dashboard to fail to load. The root cause is in #17570, which added positions into the json_metadata blob. Something went wrong in the json parsing which causes json_metadata to be truncated if the positions json contains emojis or other non-standard characters.
The root cause PR is pretty large, so we had trouble figuring out where this goes wrong. I suspect the fix forward is some combination of

Fix json parsing to handle non-ascii characters correctly
Validate that json_metadata is well-formed before writing it
Don't write the positions json, since it's already contained by a different column

Opening this revert PR as a starting point. This PR reverts #17570 and the accompanying #17707.
TESTING INSTRUCTIONS

to reproduce bug:

make dashboard
add chart with emoji in title
save dashboard
see error after save
refresh and see error on load

to verify this fix:

make dashboard
add chart with emoji in title
save dashboard
verify dashboard saved
refresh and view dashboard

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@geido @etr2460 @graceguo-supercat @rusackas

@serenajiang I can't reproduce the issue with the steps that you shared on current master (07bbe84). Is there any other way to trigger the bug?
https://user-images.githubusercontent.com/15073128/146165307-da027133-b23e-4afd-b865-97775dfe3fc4.mov

Confirmed with @zhaoyongjie and @villebro that they can't repro either 🙁

@serenajiang @graceguo-supercat as hard as I tried I could not reproduce either. Do you have any additional information to help with reproducing the problem?
Please watch the video below. If we can reproduce it a fix might be a more desirable way to solve this problem and it might be as quick.
https://user-images.githubusercontent.com/60598000/146207191-82a7a9ee-8cb0-407d-abd6-2ca3ef8ea43e.mp4

for simple dashboard, once you edit dashboard and save it, you will see position_json column is inserted into json_metadata column, this is pretty easy to reproduce
for large dashboard:

set SUPERSET_DASHBOARD_POSITION_DATA_LIMIT = 16777215
create a large dashboard with charts and tabs, add emojis in tabs
make dashboard position_json > data is > 65k
edit dashboard, or save_as

Hello @graceguo-supercat Erik gave us a hint that the limit might be the problem not the non-ascii characters as you just correctly pointed out. I have released a PR that removes the positions from the metadata as they are unnecessarily saved there and tagged you there. Thank you 🙏

@geido @kgabryje  We initially thought the size was the problem too, but we realized that it was emojis from repro with small dashboard. More specific repro instructions:

create dashboard
add chart to dashboard and edit the chart title (in the dashboard) to contain an emoji, OR add a header with an emoji in it
save dashboard

Removing positions should fix this problem, since afaik, there aren't any other ways for emojis to get in. Thanks for the PR!


Storage flaky tests debug

Download file etag lock

@sima-zhu can you provide more details in this GitHub issue so it's actionable?

Closing this issue as this test hasn't been flaky for a while now.


Is the basic getting started documentation out of date?

For example, the following example does not compile.
class CustomActionHandler: StandardKeyboardActionHandler {

    init(inputViewController: KeyboardInputViewController) {
        super.init(inputViewController: inputViewController)
    }

    override func action(
        for gesture: KeyboardGesture,
        on action: KeyboardAction
    ) -> KeyboardAction.GestureAction? {
        let standard = super.action(for: gesture, on: action)
        switch gesture {
        case .longPress: return longPressAction(for: action) ?? standard
        case .release: return releaseAction(for: action) ?? standard
        default: return standard
        }
    }

    func longPressAction(for action: KeyboardAction) -> KeyboardAction.GestureAction? {
        switch action {
        case .image(_, _, let imageName): return { [weak self] _ in self?.saveImage(named: imageName) }
        default: return nil
        }
    }

    func releaseAction(for action: KeyboardAction) -> KeyboardAction.GestureAction? {
        switch action {
        case .image(_, _, let imageName): return { [weak self] _ in self?.copyImage(named: imageName) }
        default: return nil
        }
    }
}

The initializer parameter is inputController, not inputViewController and a convenience initializer call is not allowed here. It needs to be the required initializer?

Hi @iitgrad
Thank you, I may have missed updating a few places when moving to 8.0.
I will fix this 👍

Hi @danielsaidi
Can you also update example for KeyboardTextField and KeyboardTextView?

Yes, I will add examples for that, with code samples.
Until then, you have the view demonstrated in the demo app.

Hi @iitgrad and @X1opya
I have started updating the documentation, and home half-way. You can find the updated docs in the master branch.

Hi again,
I have pushed the updated documentation to the master branch. It will be live in the next version.


Support touchstone file with more than 9 ports.

Support touchstone file with more than 9 ports.
Previously we were only selecting the last digit to get the number of ports contained in the touchstone file.
Fix #928

If not done before in the code, I would suggest to lower() the touchstone_full_path somewhere, as one can often sees Touchstone files with using upper cases extentions such as : '.S2P'

If not done before in the code, I would suggest to lower() the touchstone_full_path somewhere, as one can often sees Touchstone files with using upper cases extentions such as : '.S2P'

Great suggestion @jhillairet . It is done. Thanks.


Fonts doesn't get copied and errors out

Here is the plugin configuration:
plugins: [
    libAssetsPlugin({
        limit: 1024 * 8,
        extensions: ['.otf', '.ttf', '.woff', '.woff2'],
        outputPath: 'static/fonts',
    }),
],

But I also have a custom output and it looks like:
rollupOptions: {
    output: {
        assetFileNames: (assetInfo) => {
            let extType = assetInfo.name.split('.').at(1);
            if (/png|jpe?g|svg|gif|tiff|bmp|ico/i.test(extType)) {
                extType = 'img';
            } else if (/woff|woff2/.test(extType)) {
                extType = "css";
            }
            if (assetInfo.name === 'style.css') return 'css/main.css';
            return `${extType}/[name][extname]`;
        },
        chunkFileNames: 'js/[name].[format].js',
        entryFileNames: 'js/[name].[format].js',
    }
}

When I try to build it, I get the following error:
[commonjs--resolver] Could not set source for asset "static/fonts/[contenthash].woff2", asset source needs to be a string, Uint8Array or Buffer.
error during build:
RollupError: Could not set source for asset "static/fonts/[contenthash].woff2", asset source needs to be a string, Uint8Array or Buffer.
    at error (file:///home/akshay/code/personal/gollahalli.com/node_modules/rollup/dist/es/shared/parseAst.js:337:30)
    at getValidSource (file:///home/akshay/code/personal/gollahalli.com/node_modules/rollup/dist/es/shared/node-entry.js:18113:16)
    at FileEmitter.emitAsset (file:///home/akshay/code/personal/gollahalli.com/node_modules/rollup/dist/es/shared/node-entry.js:18274:15)
    at FileEmitter.emitFile (file:///home/akshay/code/personal/gollahalli.com/node_modules/rollup/dist/es/shared/node-entry.js:18153:25)
    at emitFile (file:///home/akshay/code/personal/gollahalli.com/node_modules/@laynezh/vite-plugin-lib-assets/dist/index.js:219:15)
    at file:///home/akshay/code/personal/gollahalli.com/node_modules/@laynezh/vite-plugin-lib-assets/dist/index.js:329:27
    at Array.forEach (<anonymous>)
    at Object.resolveId (file:///home/akshay/code/personal/gollahalli.com/node_modules/@laynezh/vite-plugin-lib-assets/dist/index.js:328:21)
    at async PluginDriver.hookFirstAndGetPlugin (file:///home/akshay/code/personal/gollahalli.com/node_modules/rollup/dist/es/shared/node-entry.js:18542:28)
    at async resolveId (file:///home/akshay/code/personal/gollahalli.com/node_modules/rollup/dist/es/shared/node-entry.js:17211:26)

Not sure what this error is. Complete configuration can be found at - https://github.com/akshaybabloo/spark-hugo-theme/blob/spark-2/vite.config.mts

@akshaybabloo Thanks for your feedback. I can't get enough information from the error message to identify the source of the exception. Can you provide a minimal reproducible version?

Sorry I think I found the issue. I might have found another issue, I will open a new ticket for that. Thank you!


does not work over my corporate firewall

love the idea of this and it works well outside my place of work but not from inside. any more information you need?

Thanks, @hjlow! I imagine it is probably because your network setup is blocking the ports tty-share uses.
I can't suggest any simple workaround to that, unfortunately. Maybe using websockets for both ends, over port 80, could trick firewalls and allow the connection, but that would take some time to implement. I hope I will get time some day to get to it.


Babel transpiling failing for client.js?

Hi, I'm probably misinterpreting the error, here's why I get on npm run dev:

...
[2] ==> 🌎  API is running on port 3030
[2] ==> 💻  Send requests to http://localhost:3030
[1] ----
[1] ==> ✅  React Redux Example is running, talking to API server on 3030.
[1] ==> 💻  Open http://localhost:3000 in a browser to view the app.
[0] ./src/client.js
[0]
[0] /somedir/src/client.js
[0]   4:2  error  Parsing error: Illegal import declaration
[0]
[0] ✖ 1 problem (1 error, 0 warnings)
[0]
[0] ./src/client.js
[0] Module build failed: TypeError: Falsy value found in plugins
[0]     at /somedir/node_modules/babel-core/lib/transformation/file/options/option-manager.js:160:15
[0]     at Array.map (native)
[0]     at Function.normalisePlugins (/somedir/node_modules/babel-core/lib/transformation/file/options/option-manager.js:155:20)
[0]     at OptionManager.mergeOptions (/somedir/node_modules/babel-core/lib/transformation/file/options/option-manager.js:277:36)
[0]     at OptionManager.init (/somedir/node_modules/babel-core/lib/transformation/file/options/option-manager.js:465:10)
[0]     at File.initOptions (/somedir/node_modules/babel-core/lib/transformation/file/index.js:194:75)
[0]     at new File (/somedir/node_modules/babel-core/lib/transformation/file/index.js:123:22)
[0]     at Pipeline.transform (/somedir/node_modules/babel-core/lib/transformation/pipeline.js:45:16)
[0]     at transpile (/somedir/node_modules/babel-loader/index.js:14:22)
[0]     at Object.module.exports (***/node_modules/babel-loader/index.js:88:12)
[0]  @ multi main
[0] webpack built 7e5df70721245d333ef9 in 2836ms

Before I got to this point, I couldn't get server code to transpile as well. I had to add some options to .babelrc:
{   "presets": [     "es2015",     "react",     "stage-0"   ],   "plugins": [     "transform-decorators-legacy"   ] }
I'll post package.json if needed (added the above presets and plugin there).
npm version is 3.8.5
node is 5.10.0
What did I do wrong?

OK I have some progress.  Apparently if plugins are specified in .babelrc but not in babelrcObjectDevelopment, then dev.config.js merges them incorrectly:
combinedPlugins = combinedPlugins.concat(babelrcObjectDevelopment.plugins);

(babelrcObjectDevelopment.plugins is undefined, combinedPlugins is non empty, result is
['transform-decorators-legacy', undefined])
Quick solution:
if (babelrcObjectDevelopment.plugins !== undefined) {
  combinedPlugins = combinedPlugins.concat(babelrcObjectDevelopment.plugins);
}

Found this one as well. .eslintrc and .eslintignore weren't copied from the template to my working folder. That solves it.
Keeping the issue open for the "TypeError: Falsy value found in plugins" error, in case you want to apply the solution. I can issue a pull request.


PM_STATE_INFO_DT_ITEMS_LIST macro does not fill the pm_min_residency array

I have assigned the cpu-power-states property via overlay as stated in the example device tree fragment. However, the PM_STATE_INFO_DT_ITEMS_LIST macro does not fill the pm_min_residency array in the policy_residency.c file. It is used as stated in the macro brief.
I am using the power management subsystem in residency mode. When I compile the code, I don't get any errors. In debug mode, I see that the pm_min_residency array is not filled in the pm_policy_next_state function.
I did not make any changes to the policy_residency.c file.
Target Device: nrf52833dk_nrf52833
Overlay file:
cpus {
    cpu@0 {
        cpu-power-states = <&state0 &state1>;
    };
};

power-states {
    state0: state0 {
        compatible = "zephyr,power-state";
        substate-id = <0>;
        power-state-name = "active";
        min-residency-us = <1000>;
        exit-latency-us = <100>;
    };

    state1: state1 {
        compatible = "zephyr,power-state";
        substate-id = <1>;
        power-state-name = "runtime-idle";
        min-residency-us = <10000>;
        exit-latency-us = <100>;
    };
};

I'm using the nrf system_off sample. In addition to this sample, I added cpu power states via overlay. I was expecting a power state to be selected according to the tick count of the next thread in the pm_policy_next_state function, but I saw that there was a problem and the active state was always selected.
static volatile const struct pm_state_info pm_min_residency[] =
PM_STATE_INFO_DT_ITEMS_LIST(DT_NODELABEL(cpu0));

Then I put a breakpoint at the beginning of the pm_policy_next_state function and saw that the pm_min_residency array was not filled.
I am using Zephyr in Visual Studio Code via nRF Connect SDK. While creating the build configuration via nrf connect in Visual studio, I only gave the DTC_OVERLAY_FILE parameter. I don't have a problem during compilation, I have a problem with the macro filling the array.
Expected behavior: I was expecting the PM_STATE_INFO_DT_ITEMS_LIST macro in the policy_residency.c file to fill the processor power state definitions in the Devicetree into the pm_min_residency array.
OS: Windows
Zephyr Version: 2.6.99
NCS Version: 1.7.1

The code responsible for this part has been changed since the Zephyr version you report. There's a test that covers this part (https://github.com/zephyrproject-rtos/zephyr/blob/main/tests/subsys/pm/policy_api/src/main.c). Can you try using upstream Zephyr?

Thanks for your answer. When I examined zephyr v.3.0.0 in the Github repo, I saw that there was a change as you stated. But since this version is Pre-release yet, I will wait for it to be realese. I will let you know if there is a problem in my attempt after it is released.


Fix for rails 6.1 to delegate external_routes

This commit fixes the following error on rails 6.1:
$ bundle exec rake
Traceback (most recent call last):
  23: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:5:in `<main>'
  22: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:5:in `select'
  21: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:17:in `block in <main>'
  20: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:17:in `require'
  19: from /Users/tricknotes/src/github.com/amatsuda/routes_lazy_routes/test/routes_lazy_routes_test.rb:3:in `<top (required)>'
  18: from /Users/tricknotes/src/github.com/amatsuda/routes_lazy_routes/test/routes_lazy_routes_test.rb:3:in `require'
  17: from /Users/tricknotes/src/github.com/amatsuda/routes_lazy_routes/test/test_helper.rb:22:in `<top (required)>'
  16: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/railties-6.1.0/lib/rails/railtie.rb:207:in `method_missing'
  15: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/railties-6.1.0/lib/rails/railtie.rb:207:in `public_send'
  14: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/railties-6.1.0/lib/rails/application.rb:384:in `initialize!'
  13: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/railties-6.1.0/lib/rails/initializable.rb:60:in `run_initializers'
  12: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/2.7.0/tsort.rb:205:in `tsort_each'
  11: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/2.7.0/tsort.rb:226:in `tsort_each'
  10: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/2.7.0/tsort.rb:347:in `each_strongly_connected_component'
  9: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/2.7.0/tsort.rb:347:in `call'
  8: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/2.7.0/tsort.rb:347:in `each'
  7: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/2.7.0/tsort.rb:349:in `block in each_strongly_connected_component'
  6: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/2.7.0/tsort.rb:431:in `each_strongly_connected_component_from'
  5: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/2.7.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
  4: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/2.7.0/tsort.rb:228:in `block in tsort_each'
  3: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/railties-6.1.0/lib/rails/initializable.rb:61:in `block in run_initializers'
  2: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/railties-6.1.0/lib/rails/initializable.rb:32:in `run'
  1: from /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/railties-6.1.0/lib/rails/initializable.rb:32:in `instance_exec'
  /Users/tricknotes/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/railties-6.1.0/lib/rails/engine.rb:608:in `block in <class:Engine>': undefined method `external_routes' for #<RoutesLazyRoutes::RoutesReloaderWrapper:0x00007ff52221cab8> (NoMethodError)
rake aborted!
Command failed with status (1)
/Users/tricknotes/.rbenv/versions/2.7.2/bin/bundle:23:in `load'
/Users/tricknotes/.rbenv/versions/2.7.2/bin/bundle:23:in `<main>'
Tasks: TOP => default => test
(See full trace by running task with --trace)

@tricknotes Thank you!


Initial Template

#1 Initial template which will be the starting point for us to start the project.

Nice guys. I'm only wondering about all these files, I feel uneasy to not understand them, but maybe you have better insight. Do you think we need everything?

@MajaLinder Hey we might need to skip few files later but as of the staring point I think it's good to all the files and then we can edit some later.


[Build] Add support for static-linking to the SDK system.

Add some additional SDK variables that let us mark an SDK as supporting static linking, and/or supporting only static linking.
rdar://123503009

@swift-ci Please smoke test

@swift-ci Please smoke test Windows platform

@swift-ci Please smoke test

This got merged when I merged #71838, which had reviewed these changes as well.


Replace config.baseURL with publication.url

Separates concerns of publication data and configuration data:
Changes:
Removes config.baseURL and publication.identifier.url in favor of publication.url.
Removes config.title in favor of publication.title. Not sure why these both existed, config.title was only being used (and incorrectly) in meta tags.

@mphstudios fixed. weirdly they were resolving to strings in those contexts, but stringifying them is much more explicit


Update index.js

error flag is never raised if server available but error is returned, but empty body is returned on success, using body length to determine if all went well, and show if there is an error if data cannot be committed to database.

covered in #18


pip element doesn't make it easy to add configuration

See original issue on GitLab
In GitLab by [Gitlab user @BenjaminSchubert] on Dec 17, 2019, 11:53
Summary
Other plugins like cmake allow adding cmake-local and cmake-global args to allow expanding the command line withou rewriting it entirely. We should follow this pattern here too
What is the expected correct behavior?
I can add additional arguments to the pip element without rewriting the entire command line

In GitLab by [Gitlab user @tristanvb] on Nov 6, 2020, 07:49
We don't have a pip element in BuildStream (we do have a pip source but that is likely to be moved).
Lets close this as it is not filed in the right component, and there will be some churn around plugin locations anyway.

In GitLab by [Gitlab user @tristanvb] on Nov 6, 2020, 07:49
We don't have a pip element in BuildStream (we do have a pip source but that is likely to be moved).
Lets close this as it is not filed in the right component, and there will be some churn around plugin locations anyway.


[cleanup][doc] PIP-190: Deprecate 2.8.0/2.8.1/2.8.2/2.8.3/2.9.0/2.9.1/2.9.2/2.9.3/2.10.0/2.10.1 docs

Motivation
Refer to PIP-190.
Since 2.8.x/2.9.x/2.10.x are all in place, so this pull request is to notify contributors about the versioning changes and make sure the expected versions of docs can be maintained.
Modifications
Add -deprecated suffix to the file folders of 2.8.0/2.8.1/2.8.2/2.8.3/2.9.0/2.9.1/2.9.2/2.9.3/2.10.0/2.10.1 docs.
Checked with @urfreespace about the user impact:

Renaming these folders will not trigger the rebuild of versioned docs because these version numbers are no longer used in the versions.json file. Therefore, the URL of these versioned doc pages can keep the same.

Documentation

[x] doc

Ping @Anonymitaet @urfreespace @codelipenghui for review.

I'll update the folder name in the Update versioned docs section in the Pulsar Documentation Organization Guide after this PR gets merged.


./build.sh throws a bunch of git errors

My run of ./build.sh shows this:
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `build'.
libtoolize: copying file `build/libtool.m4'
libtoolize: copying file `build/ltoptions.m4'
libtoolize: copying file `build/ltsugar.m4'
libtoolize: copying file `build/ltversion.m4'
libtoolize: copying file `build/lt~obsolete.m4'
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
-- a bunch more of these --

I imagine the git errors are superfluous, but they are scary.

Hi @edgreenberg,
Indeed, not cool to have those errors. I will look into it. As a matter of fact you may want to jump straight to ./configure instead of running the ./build.sh. It should be safe.

On 12/18/2017 07:50 AM, Felipe Zimmerle wrote:

Hi @edgreenberg https://github.com/edgreenberg,
Indeed, not cool to have those errors. I will look into it. As a
matter of fact you may want to jump straight to |./configure| instead
of running the ./build.sh. It should be safe.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SpiderLabs/ModSecurity/issues/1630#issuecomment-352416967,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJPb47gawSvaF60skqOW1d5yrMLsJ4Bks5tBl-XgaJpZM4RDf1c.

Thanks, Felipe.  I was able to get it to build, but I didn't understand
what I was building, and I have to  wait for the apache connector.  I
was just reporting it.
Thanks for all your hard work.
Ed

Hi@zimmerle
My run of ./build.sh shows this:
[root@192-168-0-45 ModSecurity]# ./build.sh
libtoolize: putting auxiliary files in .'. libtoolize: copying file ./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, build'. libtoolize: copying file build/libtool.m4'
libtoolize: copying file build/ltoptions.m4' libtoolize: copying file build/ltsugar.m4'
libtoolize: copying file build/ltversion.m4' libtoolize: copying file build/lt~obsolete.m4'
fatal: No names found, cannot describe anything.
fatal: No names found, cannot describe anything.
fatal: No names found, cannot describe anything.
fatal: No names found, cannot describe anything.
fatal: No names found, cannot describe anything.
fatal: No names found, cannot describe anything.
and it makes my modsecurity log less than noraml,and no detects return packet error information just like bellow:
ModSecurity: Access denied with code 403 (phase 2). Matched "Operator Ge' with parameter %{tx.inbound_anomaly_score_threshold}' against variable TX:ANOMALY_SCORE' (Value: 16' ) [file "owasp-modsecurity-crs/rules/REQUEST-949-BLOCKING-EVALUATION.conf"] [line "36"] [id "949110"] [rev ""] [msg "Inbound Anomaly Score Exceeded (Total Score: 16)"] [data ""] [severity "2"] [ver ""] [maturity "0"] [accuracy "0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-generic"] [hostname "<IP_ADDRESS>"] [uri "/vulnerabilities/sqli/"] [unique_id "152983697541.972244"] [ref ""]
ModSecurity: Warning. Matched "Operator Ge' with parameter %{tx.inbound_anomaly_score_threshold}' against variable TX:INBOUND_ANOMALY_SCORE' (Value: 16' ) [file "owasp-modsecurity-crs/rules/RESPONSE-980-CORRELATION.conf"] [line "61"] [id "980130"] [rev ""] [msg "Inbound Anomaly Score Exceeded (Total Inbound Score: 16 - SQLI=8,XSS=0,RFI=0,LFI=0,RCE=0,PHPI=0,HTTP=0,SESS=0): Detects classic SQL injection probings 1/2"] [data ""] [severity "0"] [ver ""] [maturity "0"] [accuracy "0"] [tag "event-correlation"] [hostname "<IP_ADDRESS>"] [uri "/vulnerabilities/sqli/"] [unique_id "152983697541.972244"] [ref ""]
i guess the action of ./build.sh cause the question，how about your option?

Hi @Archerkong,
I don't think it is related to the build process. In any case, you may want to run the make check to confirm that everything is working as expected. If you still have trouble i wold like to invite you to open a new issue to discuss the problem.

Hi @Archerkong,
I don't think it is related to the build process. In any case, you may want to run the make check to confirm that everything is working as expected. If you still have trouble i wold like to invite you to open a new issue to discuss the problem.

# make check
make: *** No rule to make target 'check'.  Stop.

# make check
make: *** No rule to make target 'check'.  Stop.

Do you have ModSecurity v3 compiled? what is the summary for your ./configure?


Allow to load object directly (not through $ref)

if the object is directly present in the main spec, remove it from the spec, name it and load it into loaded_specs for referencing.

https://fairsharing.github.io/JSONSchema-documenter/index.html?parameters={"target":"https://fairsharing.github.io/mircat/miaca/schema/data_file_schema.json","display":"grid"}#!#project_schema

Also see https://github.com/FAIRsharing/JSONSchema-documenter/issues/34#issue-361708901

Add the link from the referencing field to the referenced item


nodejs_binary depending on ts_library should get higher-level syntax

Devs should have a way to configure ts_library 's JS target.
When ts_library is being used for Nodejs applications the target is a bit different than browser applications.
For a browser app you always want to use es5 since you don't know what browser your app is going to be run on.
But with Nodejs you can pick the Nodejs version and therefore know ahead of time what target it supports.
Therefore by picking a higher target you can often gain performance from your application, depending on use case.
Another reason for allowing variable targets is interpoerablity with other nodejs modules. One such example of not supporting es5 is the popular ORM Sequelize https://github.com/RobinBuschmann/sequelize-typescript/blob/master/lib/models/BaseSequelize.ts#L14

Currently we have exactly two output flavors from TypeScript rules, and @mprobst has pushed back when we suggested adding more (Angular has a need for "ESM5" which we have a hacky way to produce in
https://github.com/angular/angular/blob/master/packages/bazel/src/esm5.bzl
I'd rather avoid the complexity of having more output flavors. If we can keep nodejs programs using the "devmode" (non-optimizer/bundler friendly) output, this keeps our system simpler.
The simple resolution to this issue seems to be raising the --target of devmode compilations to es2015, we just need to confirm we don't break users who rely on ES5 syntax in the browser for whatever reason.
(Note, the devmode output is not intended to ship to end-user browser runtime, so there's no constraint there)

es2015 devmode is now the default, it applies to nodejs inputs too

It is awkward that why I can't use a different module and target value in my tsconfig since I'm not depending on ts_devserver. the current options prevent me from enabling resolveJsonModule because it requires a commonjs & es2015 target.  Maybe we can add an option to let the advanced user fly freely.

^ I agree.
I've gone back and thought about moving completely over to Bazel, since you can't even define the target for TypeScript...

You can specify an override the default target with devmodeTargetOverride in your tsconfig
  "bazelOptions": {
    "devmodeTargetOverride": "esnext"
  },

Also note that at runtime we use the devmode artifacts, which default to es2015 for nodejs, prodmode artifacts are used for web bundling targets.

I'm thinking increasingly that ts_library should produce the constrained output formats when consumed by the provider, but the default output should just be the JS you asked for using the --target/--module you specify

Also you can use googmodule option if you want commonjs modules instead of umd.

@alexeagle is it possible to use commonjs modules with es6_module_mappings? I mean it will target commonjs modules and at the same time we will continue to use goodness of module_name?  If it possible I can work on that

I don't see why we would support both our custom module mapping and commonjs. Either you're using our opinionated output because of its interop with downstream rules (UMDs are fine for node) or in the proposal above you would opt-out by writing whatever strange outputs from ts_library you like but then you can't expect anything downstream of that to understand what you did.

https://github.com/bazelbuild/rules_nodejs/issues/122#issuecomment-368102668

I guess I'm not sure why the ts_library rule needs to change the tsconfig at all. It seems a lot simpler to me to just let the person writing the code to also write the config.

Updating rules_typescript/rules_nodejs/rules_angular is a constant struggle for us as we have to maintain patches that disable these tsconfig overrides and give us the output we asked for in our tsconfig.json, and no output that we didn't ask for.  It would be nice to do what you suggested @alexeagle and also to get rid of this split dev/prod mode and config overriding.
I am not super experienced with aspects, but it seems like it would be possible to add something like an es5_aspect and es6_aspect that consumers can then apply as needed if they want multiple versions of output.  Or maybe providers is the correct way.
I think there are probably many solutions that let people have multiple outputs without forcing everyone to have both.
If we (@JaredNeil or I) can help make this a reality we'd be glad to help.


[WIP] Implement Persistence Services

With the Persistence API being merged, it's time for the various DataSerializable objects to actually successfully serialize their data to a DataContainer.
This has some changes to achieve this including:

Provide a new service that requires registration before world loading starts
Using SuperMixins for TileEntities
Update to latest API for simpler usage of DataViews

Nice.

To improve maintainability, I think it could internally call writeToNBT and then convert to a DataContainer, that way you won't need to add any new DataQuerys if a new tag is added in vannila. It would also allow getting data from mod tile entities too.

think it could internally call writeToNBT and then convert to a DataContainer

No. While it's decent to ensure that all data about a TE is being serialized, we shouldn't be serializing the data twice over.

It would also allow getting data from mod tile entities too.

There are changes in SpongePowered/SpongeAPI#475 that will help with this. This initial implementation is groundwork for setting up DataSerializables and DataSerializableBuilders. With this, it will be very apparent as to how the Persistence API is supposed to be used.
Also, remember that custom mod TileEntities don't extend other vanilla TileEntities (except maybe Lockable), so bringing up the point of being able to use a pre-existing vanilla specific SpongeBeaconBuilder isn't quite possible since there is no common NBTTagCompound that can be read from all TileEntity objects.


Tab dirty state wrong after reading a changed file

When

buffer contains unsaved changes
file was changed from outside
you focus Oni and get the "file was changed, press [o]k or [r]ead file" (translated)
press r

the buffer is in sync with the file but I still see the "dirty" circle in the tab. Unfortunately :buffers output is also messed up:

should look like this:

This could possibly be related to an separate issue I'm seeing, where big changes to the buffer don't seem to be reflected in the modified status.
I.e. doing a substitution or macro that changes few thousand lines seems to cause the modified status to stay static.
Once I've finished up my other PR, I'll try and have a look into both of them.

Still the case with current stable version v0.3.4.