100 chars is too short for spec files

I have paths and other tests that end up being longer than 100 characters.  For instance
'''
pec/entity_spec.rb:68:100: C: Line is too long. [116/99]
describe file('/ xxx/xxxxx/xxxxxx/xxxx_xx/xxxx/xxx/xxxxxx/xxx/xxxxxxxx-xx/ssl/xxxxxxxx.xxxxxxxxxx.xx.xxxxxxxxx.xx.crt') do
^^^^^^^^^^^^^^^^^
spec/entity_spec.rb:72:100: C: Line is too long. [100/99]
its(:content) { should match(/MIIxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/) }
'''
Need to up that to twitter spec at least (140 chars ;)

Unfortunately, no matter what number we pick here, someone will not like it.  RuboCop, has adopted the community driven Ruby Style Guide.  However, I do not see anything specific to line length numbers in the spec.
Since these cops can be changed or disabled, feel free to submit a PR to ansible-sytem's .rubocop.yml with:
LineLength:
  Enabled: false

Actually let me think this over.  Rubocop, will probably only search for a .rubocop.yml form the current directory.

I'm leaning towards having the user manually create a .rubocop.yml that meets their requirements around linting vs us managing a default one.
So if you don't like the long lines, I suggest creating a .rubocop.yml with something like the following in the base of your role.
LineLength:
  Enabled: false

I've done this to get the role working .. however i think that many people will have paths that will require this setting and this fix is a bit nebulous .. i'd recommend disabling it entirely as the constraint isn't useful to this application.

I don't have a problem with this.  I actually like this requirement.  However, if people don't they can disable just as you did.

Please add a note about this to the molecule docs – or even just a link to an existing discussion of .rubocop.yml. Perhaps we should have a Tips/Conveniences section (both for molecule directly and for the tools molecule uses: rubocop in this case, but also, serverspec/testinfra/vagrant/etc). Since the whole point of molecule is to reduce the barrier for testing Ansible roles as part of the development process, it’s at least partly an educational project as well as a tool project.
From: John Dewey<EMAIL_ADDRESS>Sent: Wednesday, November 18, 2015 8:40 PM
To: metacloud/molecule
Subject: Re: [molecule] 100 chars is too short for spec files (#2)
I'm leaning towards having the user manually create a .rubocop.yml that meets their requirements around linting vs us managing a default one.
So if you don't like the long lines, I suggest creating a .rubocop.yml with something like the following in the base of your role.
LineLength:
Enabled: false
—
Reply to this email directly or view it on GitHubhttps://github.com/metacloud/molecule/issues/2#issuecomment-157919888.


improve getValidationRules to also retrieve wildcard rules

Previously wildcard rules such as myarray.* or myarray.*.id were discarded when retrieving the rules, this has been addressed so that all defined rules are not retrieved.

Thanks!


Configuration override updates

Synchronize code with Java buildpack. Specifically, pick up changes for:

Improve diagnostics for invalid YAML syntax in configuration
Support nil configuration values

looks good.


Logging for endpoints

@trevlenb2 please update, so we can merge

@milank7 as reviewer, please check updates, if happy you can merge.


Backport "HBASE-26663 Upgrade Maven Enforcer Plugin" to branch-2

The upgrade is to get the fix in MENFORCER-336, making beanshell evaluation safe for use with mvn -T. Also upgrade extra-enforcer-rules to 1.5.1, as per experience with HBASE-26664.
Signed-off-by: Duo Zhang<EMAIL_ADDRESS>Signed-off-by: Sean Busbey<EMAIL_ADDRESS>

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 43s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 21s
branch-2 passed

+1 :green_heart:
compile
9m 32s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  0s
the patch passed

+1 :green_heart:
compile
9m 21s
the patch passed

+1 :green_heart:
javac
9m 21s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+1 :green_heart:
hadoopcheck
8m 30s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

_ Other Tests _

+1 :green_heart:
asflicense
0m 13s
The patch does not generate ASF License warnings.

41m  3s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4131/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4131

Optional Tests
dupname asflicense javac hadoopcheck xml compile

uname
Linux 3dfdb43c3a04 5.4.0-90-generic #101-Ubuntu SMP Fri Oct 15 20:00:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4cdb380ccc

Default Java
AdoptOpenJDK-1.8.0_282-b08

Max. process+thread count
87 (vs. ulimit of 12500)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4131/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 42s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 25s
branch-2 passed

+1 :green_heart:
compile
2m 22s
branch-2 passed

+1 :green_heart:
shadedjars
4m 42s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m 13s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 50s
the patch passed

+1 :green_heart:
compile
1m 55s
the patch passed

+1 :green_heart:
javac
1m 55s
the patch passed

+1 :green_heart:
shadedjars
3m 34s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 46s
the patch passed

_ Other Tests _

-1 :x:
unit
34m 15s
root in the patch failed.

60m 13s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4131/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4131

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 94f21af6d52e 5.4.0-90-generic #101-Ubuntu SMP Fri Oct 15 20:00:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4cdb380ccc

Default Java
AdoptOpenJDK-1.8.0_282-b08

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4131/1/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-root.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4131/1/testReport/

Max. process+thread count
628 (vs. ulimit of 12500)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4131/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
9m 37s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m  7s
branch-2 passed

+1 :green_heart:
compile
2m 52s
branch-2 passed

+1 :green_heart:
shadedjars
5m  0s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
3m 36s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m  1s
the patch passed

+1 :green_heart:
compile
2m 50s
the patch passed

+1 :green_heart:
javac
2m 50s
the patch passed

+1 :green_heart:
shadedjars
4m  4s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
3m 20s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
440m 48s
root in the patch passed.

482m 57s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4131/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4131

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux<PHONE_NUMBER>e5 5.4.0-90-generic #101-Ubuntu SMP Fri Oct 15 20:00:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 4cdb380ccc

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4131/1/testReport/

Max. process+thread count
2486 (vs. ulimit of 12500)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4131/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


kube-dns crashes because it can't access Kubernetes API

@wyfligamo reported the following in #57:
(issue comments edited by @pires, in order to make things more clear here)
my kube-dns pod status is CrashLoopBackOff and kubedns container log says
[root@localhost ~]# kubectl get pods --all-namespaces
NAMESPACE     NAME                        READY     STATUS             RESTARTS   AGE
kube-system   heapster-7d7b7f4f87-brp2l   1/1       Running            0          21h
kube-system   kube-dns-6dc79b7c4-dbw5g    1/3       CrashLoopBackOff   506        21h

My k8s only start kube-dns and heapster pods, is that right? they can't communicate with api service, but I can get api response with browser outside the cluster
[root@localhost ~]# kubectl logs --namespace=kube-system heapster-7d7b7f4f87-brp2l
E0202 05:26:09.524966       1 reflector.go:190] k8s.io/heapster/metrics/heapster.go:322: Failed to list *v1.Pod: Get https://kubernetes.default/api/v1/pods?resourceVersion=0: dial tcp: i/o timeout

[root@localhost ~]# kubectl logs --namespace=kube-system kube-dns-6dc79b7c4-dbw5g kubedns
E0202 05:23:47.244936       1 reflector.go:201] k8s.io/dns/pkg/dns/dns.go:150: Failed to list *v1.Service: Get https://<IP_ADDRESS>:443/api/v1/services?resourceVersion=0: dial tcp <IP_ADDRESS>:443: i/o timeout
E0202 05:23:47.244981       1 reflector.go:201] k8s.io/dns/pkg/dns/dns.go:147: Failed to list *v1.Endpoints: Get https://<IP_ADDRESS>:443/api/v1/endpoints?resourceVersion=0: dial tcp <IP_ADDRESS>:443: i/o timeout
I0202 05:23:47.742922       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0202 05:23:48.242824       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0202 05:23:48.742850       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...
I0202 05:23:49.242879       1 dns.go:173] Waiting for services and endpoints to be initialized from apiserver...

@wyfligamo looking at your logs it seems that kube-dns can't connect to the Kubernetes API (<IP_ADDRESS>). Does your host network use any of <IP_ADDRESS>/8 or <IP_ADDRESS>/16 CIDRs?
You can reach the API from your browser because the SSH tunnel forwards to the DC/OS VIP apiserver-insecure.kubernetes.l4lb.thisdcos.directory:9000 and not the Kubernetes API (internal to the Kubernetes cluster) Service, kubernetes.default.svc.cluster.local.

@pires Thanks for follow my question.
My cluster IP is <IP_ADDRESS>-17, is that a problem? Can I change the k8s service cluster IPs CIDR ?

Yes, it's a problem. Yes, you can.

Assuming you're installing with the default options, create a JSON file with the following contents:
{
  "kubernetes": {
    "service_cidr": "<YOUR_CIDR_HERE>"
  },
}

Attention: replace <YOUR_CIDR_HERE> above with a CIDR block that is not assigned anywhere
else, e.g. <IP_ADDRESS>/16.

Save the file.

Uninstall the framework and wait for all tasks to go away.

Install the framework as follows:
dcos package install --yes beta-kubernetes --options=<JSON_FILEPATH>

Attention: replace <JSON_FILEPATH> above with the path to the JSON file you created above.

I will add a sub-section describing this in our Advanced Installation package docs.

in the case of using this quickstart, options.json gets created in .deploy folder when you e.g. do make gce, then edit that file and add service_cidr there

Thank you @rimusz.

@pires Thanks, I'll have a try and feedback in next Monday.

Hi, @pires
I change my service CIDR to <IP_ADDRESS>/16, and I'm sure that IPs are not in use, but still get the same problem

@pires , I make a mistake, the error is not same,

E0205 11:18:05.352816       1 reflector.go:201] k8s.io/dns/pkg/dns/dns.go:150: Failed to list *v1.Service: Get https://<IP_ADDRESS>:443/api/v1/services?resourceVersion=0: x509: certificate is valid for <IP_ADDRESS>, <IP_ADDRESS>, not <IP_ADDRESS>
E0205 11:18:05.419043       1 reflector.go:201] k8s.io/dns/pkg/dns/dns.go:147: Failed to list *v1.Endpoints: Get https://<IP_ADDRESS>:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for <IP_ADDRESS>, <IP_ADDRESS>, not <IP_ADDRESS>

It seems  like I need a certificate for new CIDR?

@wyfligamo correct. This is a bug on our end and I have no workaround for you at this point. We will be releasing a new beta later this week and a fix will be included. Please, bear with us.
Thank you for your feedback!

@pires That's OK, wish you success :  )


Update context hooks to simplify state/action selectors

Task Description
Proposal: Update react context hooks such as useStory to support a simpler syntax.
As per discussion here:
https://github.com/google/web-stories-wp/pull/1705/files#diff-4c52a87be51ed328b2d8709e5705240d
Before:
const {
  currentPage,
  selectedElementIds,
  toggleElementInSelection,
  setSelectedElementsById,
} = useStory(
  ({
    state: { currentPage, selectedElementIds },
    actions: { toggleElementInSelection, setSelectedElementsById },
  }) => {
    return {
      currentPage,
      selectedElementIds,
      toggleElementInSelection,
      setSelectedElementsById,
    };
  }
);

After:
const { currentPage, selectedElementIds } =
    useStoryState(['currentPage', 'selectedElementIds']);
const { toggleElementInSelection, setSelectedElementsById } =
    useStoryAction(['toggleElementInSelection', 'setSelectedElementsById']);

@cvolzke4 @barklund Hmm. While the original form is pretty verbose, I still find it pretty useful and instructing. Also, substituting symbolic property access with quoted strings might hamstring us in the future. Are we sure there are strong enough reasons for this?

@cvolzke4 @barklund Hmm. While the original form is pretty verbose, I still find it pretty useful and instructing. Also, substituting symbolic property access with quoted strings might hamstring us in the future. Are we sure there are strong enough reasons for this?

In some places I feel this is more readable as it reduces boilerplate considerably. I'm not strongly for or against this style though, I can understand that using strings to reference the properties may cause problems if we ever moved to typescript.

@cvolzke4 @dvoytenko, I know that I was the one suggesting this in the first place, but the more I work with the current system (of verbose selectors), the more I like it.
The only thing that might be relevant, is if we have some single selectors, that are heavily repeated - perhaps if we see a lot of this:
const { currentPage } = useStory(
  ({ state: { currentPage } }) => ({ currentPage })
);

It might be nice to make a single-selecting hook such as:
const currentPage = useCurrentPage();

It would be a shorthand only used for the top X most commonly used single properties across the application, and if you need any other properties, you'd have to go the longhand route.
Does that make sense? Or is it not worth it?

I think the targeted hooks is good idea imho. Alternatively, we could also have a library of selectors. I think that'd be most important for state props.
E.g.
const currentPage = useCurentPage();
// or
const {currentPage} = useStory(StorySelectors.currentPage);

both seem ok to me.

Just gonna summarize some recent conversation I had around this after doing some performance work recently.
Originally I tried out mocking what the library had:
const currentPage = useStory(v => v.state.currentPage);
const selectedElementIds = useStory(v => v.state.selectedElementIds);
const toggleElementInSelection = useStory(v => v.actions.toggleElementInSelection);
const setSelectedElementsById = useStory(v => v.actions.setSelectedElementsById);

I liked this approach for a couple of reasons:

less lines
less layers of indirection around object equality to prevent unnecessary re-renders
further leans out the number of objects to reason about, would even be of benefit to make context values flat and remove the separation of actions or state

At the time tho, I didn't realize we had written a wrapper around this library to do shallow comparison (instead of referential equality which the library defaults to). I'm curious if this was just written so we could group context value properties in our selectors return values or if there were other benefits outside of enabling api preference? Regardless, there's definitely pros and cons to having the return value from selectors shallowly compared, but if you use it right, it doesn't really matter.
At the end of the day, the current selector pattern is fine, albeit a little verbose, and a lot of this is just personal preference. The only big things that actually shoot us in the foot performance wise are:

pulling in more state than we need into components
pulling in state to derive a value off of it that changes less frequently than the state
pulling in story state to derive story actions

Pulling in more state than we need into components
The most common pitfall I see here is pulling in currentPage. Rarely do components need the entire currentPage, but it is pulled in frequently. This causes a component to have empty re-renders on most story actions even if the property it's reading off of currentPage isn't updating. Example:
const { currentPage } = useStory(({ state }) => ({ state.currentPage }));
const someMetaAttribute = currentPage.someMetaAttribute;
// vs
const someMetaAttribute = useStory(({ state }) => state.currentPage.someMetaAttribute);

Pulling in state to derive a value off of it that changes less frequently than the state
This is a big one with element specific components. We frequently pull in all elements to derive some value off of it. Consider getting the background element id, or deriving a boolean off of elements.every(...) or elements.some(..). This should all be derived in the scope of the selector, not the components body, to prevent empty rerenders:
const { currentPage } = useStory(({ state }) => ({ state.currentPage }));
const backgroundElementId = currentPage?.elements[0].id;
// vs
const backgroundElementId = useStory(({ state }) => state.currentPage?.elements[0].id);

or
const { currentPage } = useStory(({ state }) => ({ state.currentPage }));
const isSelected = currentPage?.selectedElements.includes(selectedId => selectedId === id);
// vs
const isSelected = useStory(({ state }) => state.currentPage?.selectedElements.includes(selectedId => selectedId === id));

Pulling in story state to derive story actions
We shouldn't really be referencing pulled in story state to derive a story reducer action. All referenced story state in a reducer action should be referenced in the scope of the reducer, any external state should be passed in through the payload. This is great for preventing unnecessary re-renders, but also 100% ensuring you're not referencing stale data when the action is updating state
const {
  someAction,
  anotherAction,
  currentPage
} = useStory(({ state, actions }) => ({
  someAction: actions.someAction,
  anotherAction: actions.anotherAction,
  currentPage: state.currentPage
}));

const someHandler = useCallback((evt) => {
  if(evt.metaKey && currentPage.selection?.length > 0) {
    someAction(...)
  }
  anotherAction(...)
}, [  someAction, anotherAction, currentPage ]);

// vs
const combinedAction = useStory(({ actions }) => combinedAction);
const someHandler = useCallback((evt) => combinedAction({ metaKey: evt.metaKey }), [  combinedAction ]);

In general tho, I think the nature of use-story-selector necessitates some knowledge of its inner workings to use it effectively and there's not really a pattern that eliminates this need.
I guess the only danger in shallow equality comparison functions by default is the scenario @cvolzke4 mentioned where you don't realize you're doing a shallow comparison on an object when you do:
// this would be fine with the library as is, but not with our current wrapper around it
const currentPage = useStory(({ state }) => state.currentPage);
// this is adding unnecessary object creation so that we can have shallow equality as the default comparison fn, but
// essentially just do a referential equality check. Basically our added code around the library is making us add extra code
// to get back the original functionality of `useContextSelector`
const { currentPage } = useStory(({ state }) => ({ currentPage: state.currentPage }));

although it does allow for some niceties like this. Here useContextSelector wont force a re-render unless elements are re-ordered, added, or removed:
const elementIds = useStory(({ state }) => state.currentPage?.elements.map(el => el.id));
return elementIds.map(id => <SomeMemoizedElementComponent key={id} id={id} />)


HV-1844 Upgrade Jakarta EL to 4.0.1

https://hibernate.atlassian.net/browse/HV-1844

@gsmet  - Given the recent CVE in EL, I am very glad to see this PR :)
When does this change ship?


Cannot find module @babel/runtime

I have just installed this package via npm install webpack-merge-and-include-globally and running Webpack process throws following error:
Error: Cannot find module '@babel/runtime/helpers/interopRequireDefault'
Require stack:
- /{...}/node_modules/webpack-merge-and-include-globally/index.node6-compatible.js
- /{...}/app/webpack.config.js
- /{...}/gulpfile.js
- /usr/local/lib/node_modules/gulp/node_modules/gulp-cli/lib/shared/require-or-import.js
- /usr/local/lib/node_modules/gulp/node_modules/gulp-cli/lib/versioned/^4.0.0/index.js
- /usr/local/lib/node_modules/gulp/node_modules/gulp-cli/index.js
- /usr/local/lib/node_modules/gulp/bin/gulp.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1070:15)
    at Module._load (node:internal/modules/cjs/loader:923:27)
    at Module.require (node:internal/modules/cjs/loader:1137:19)
    at require (node:internal/modules/helpers:121:18)
    at Object.<anonymous> (/{...}/node_modules/webpack-merge-and-include-globally/index.node6-compatible.js:3:30)
    at Module._compile (node:internal/modules/cjs/loader:1255:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1309:10)
    at Module.load (node:internal/modules/cjs/loader:1113:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)
    at Module.require (node:internal/modules/cjs/loader:1137:19)

seems like @bable/runtime is never requested as dependecy, but it's used in webpack-merge-and-include-globally/index.node6-compatible.js?

Same here :
[webpack-cli] Failed to load 'C:\Users\bzkd\src\smsstudio\ui\v2\webpack.config.js' config
[webpack-cli] Error: Cannot find module '@babel/runtime/helpers/interopRequireDefault'


KAFKA-15625: Do not flush global state store at each commit

Global state stores are currently flushed at each commit, which may impact performance, especially for EOS (commit each 200ms).
The goal of this improvement is to flush global state stores only when the delta between the current offset and the last checkpointed offset exceeds a threshold.
This is the same logic we apply on local state store, with a threshold of 10.000 records.
The implementation replaces the flush based on time to a flush based on the delta.
Committer Checklist (excluded from commit message)

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

@cadonna can you take a look?

Thanks for the PR @AyoubOm !
Here my feedback!

Thanks @cadonna for your review ! For your first comment please check my reply to it above.

@AyoubOm Thanks for the updates!
Here my replies.

Thanks @cadonna, I made updates accordingly

Failed tests are unrelated.


usehooks-ts patch is not applied on vercel deployment

Description :
Because of https://github.com/scaffold-eth/scaffold-eth-2/issues/419#issuecomment-1635551787, usehooks-ts patch which is at root of the repo is not applied.
This breaks the storing and retrieving of user-selected theme it always uses user system theme when the page is refreshed instead of remembering user choice.
Example : https://se2-structs.vercel.app/
Originally reported here => https://github.com/scaffold-eth/se-2-challenges/pull/131#pullrequestreview-1864823314

PS: there seems some recent relases of usehooks-ts https://github.com/juliencrn/usehooks-ts/releases maybe we try updgrading it and see if it works without patch


PITR abbreviation used without being expanded

In the middle of the text we have PITR abbreviation without explaining what it is. It is clear that it refers to Point in Time Restore but for clarity and convenience it is always better to introduce abbreviation on the first occurrence within the text and only then use it throughout the text without expanding it where necessary. I.e. first we should have "Point in Time Restore (PITR)" somewhere in the text, and only then simply "PITR".

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

ID: 18c9d161-a06b-6b68-8f54-c22fcc7088da
Version Independent ID: b215e7fa-dc6a-48ee-418b-93709813566e
Content: Cloud business continuity - database recovery - SQL Database
Content Source: articles/sql-database/sql-database-business-continuity.md
Service: sql-database
GitHub Login: @anosov1960
Microsoft Alias: sashan

@mikerodionov Thanks for reporting! I have assigned the issue to the content author to investigate and update as appropriate.

PR pending - https://github.com/MicrosoftDocs/azure-docs-pr/pull/45301

Will address

In the topic, each are defined - please explain in more detail your question regarding the "relation between ERT, RTO, and RPO".
"SQL Database provides several business continuity features, including automated backups and optional database replication. Each has different characteristics for estimated recovery time (ERT) and potential data loss for recent transactions. Once you understand these options, you can choose among them - and, in most scenarios, use them together for different scenarios. As you develop your business continuity plan, you need to understand the maximum acceptable time before the application fully recovers after the disruptive event - this is your recovery time objective (RTO). You also need to understand the maximum amount of recent data updates (time interval) the application can tolerate losing when recovering after the disruptive event - this is your recovery point objective (RPO)."

RPO and RTO are defined, I agree. However, the technical definition of ERT is not provided. Not even in its simplest term (ERT= RTO+??).

estimated recovery time (ERT) - so, for example, for recovery with Standard for Geo-restore from geo-replicated backups - the estimate is less than 12 hours - if you want an estimated recovery time less than this, use Active Geo-Replication - which has an ERT of less than 30 seconds

Estimated recovery time is the estimate of how long it will take to complete a recovery. How long it actually takes depends on a number of factors including the amount of transactions to recover. Recovery time objective is your objective for the amount of time that you can accept as the recovery time.
@anosov1960 for perhaps additional clarity


Draft: Change zarf init to always install the docker registry

@jeff-mccoy in cli/internals/util/pki.go
Change
if ip := net.ParseIP(host); ip != nil {
  template.IPAddresses = append(template.IPAddresses, ip)
} else {
  // Add localhost to make things cleaner
  template.DNSNames = append(template.DNSNames, host, "localhost", config.ZarfLocal, "*.localhost")
  if template.Subject.CommonName == "" {
    template.Subject.CommonName = host
  }
}

to
// We need to add `config.ZarfLocal` to the certificate, but the way to do that is different depending on whether it
// is a DNS name or a IP address. This really shouldn't be necessary since `config.ZarfLocal` is a const, but it
// lets us mess with the value of that const without having to change logic in this function
if ip := net.ParseIP(config.ZarfLocal); ip != nil {
  // config.ZarfLocal is an IP address
  template.IPAddresses = append(template.IPAddresses, ip)
  } else {
    // config.ZarfLocal is assumed to be a DNS name
    template.DNSNames = append(template.DNSNames, config.ZarfLocal)
  }

if ip := net.ParseIP(host); ip != nil {
  template.IPAddresses = append(template.IPAddresses, ip)
  } else {
    // Add localhost to make things cleaner
    template.DNSNames = append(template.DNSNames, host, "localhost", "*.localhost")
    if template.Subject.CommonName == "" {
      template.Subject.CommonName = host
  }
}

I have this staged if you'd like me to push it, or you can adjust to your style if you want.

@jeff-mccoy can we delete this branch?


Add missing references

Currently there is still a bunch of references missing.... (e.g. sci-kit learn etc.)

I am happy to help with this. I only started my pass of the paper. I already fixed some very German sounding formulations.

Those German sounding formulations must have been introduced by someone else ... :stuck_out_tongue_winking_eye:

I hope I didn't miss any.


data/type.yaml: Make it possible to set per-profile/type extra hiera config

The idea is to enable something like the following:
infra: ref-arch
profiles:
...
  compute:
    config:
      nova::scheduler::filter::ram_allocation_ratio: 4
      nova::scheduler::filter::cpu_allocation_ratio: 16
...

hosts:
....

:+1:

Tested locally and it worked for me.
@fredericlepied @EmilienM ok to merge the PR ?

@Spredzy ok for me

Thank you @tremble


Security

by method of "hadAccessTo" in user entities?

wouldn't symfony voters be more usefull

@sumocoders/php-team Someone still has an idea what this what about?

@jonasdekeukelaere Could you give some more context on this issue?

@jonasdekeukelaere could you give some more context on this issue?

I don't know anymore haha, it's been open for almost a year ;)


Latex support

@jackd248
Latex support is needed!

Will be added in a future release, for now there are some bugs and usability improvements, I need to improve.
Thanks for the idea. :)


Add ServiceInterop.dll fallback support for ARM64

Describe the bug
Running any SQL-based queries triggers a type load exception on ARM64 (Win 11 preview)
`An exception of type 'System.DllNotFoundException' occurred in System.Private.CoreLib.dll but was not handled in user code: 'Unable to load DLL 'Microsoft.Azure.Cosmos.ServiceInterop.dll' or one of its dependencies: The specified module could not be found. (0x8007007E)'
To Reproduce
Use Container.GetItemQueryIterator() to execute any QueryDefinition.
Expected behavior
According to docs https://docs.microsoft.com/en-us/azure/cosmos-db/sql/troubleshoot-dot-net-sdk?tabs=diagnostics-v3#common-query-issues a fallback should occur:

For Linux and other unsupported platforms where ServiceInterop.dll isn't available, an additional network call will be made to the gateway to get the optimized query.

With ARM64 being an unsupported platform, a network call should occur instead of an exception.
Actual behavior
Type load exception occurs instead of a lower-performance network call fallback.
Environment summary
SDK Version: 3.23
OS Version: Windows 11 Insider Preview ARM64

Closed by https://github.com/Azure/azure-cosmos-dotnet-v3/pull/3226. Released in 3.27.2


PGH004 (blanket-noqa) doesn't checks file-level pragmas

Hi,
If blanket noqa is used on a file level, cat test.py:
# ruff: noqa

print("Hello Astral!")

ruff will not complain about it:
ruff check --select=PGH004 test.py
All checks passed!

but probably it should, because in any case better to disable exact rules, not everything.
Same for # flake8: noqa which is also supported by ruff.
ruff --version
ruff 0.4.4

Seems reasonable to me? May need to be added in preview since it's an increase in the scope of the rule.


PHPC-444: Support options array in BulkWrite and executeInsert()

https://jira.mongodb.org/browse/PHPC-444

@bjori left a LGTM to this in IRC after general objections to the insert/update/delete convenience methods existing in the first place.


performance of filtering a large table

When filtering a table with many rows (tested with ~40000), cursor movement gets very sluggish (several secs to go to the next row).
Table setup is just table.WithFilterInputValue( somefilter)
Any idea how I can speed this up?

This is likely being recalculated way too often.  The workaround would be to filter the rows yourself and keep the cache of filtered rows to feed to the table, but there's likely something the table can do to better track/cache this.  I haven't worked with such a large row count before, this would be a good area for improvement.

I went to check this for myself, and a table with 40,000 rows will absolutely lock up if you're not using paging.  However, if you're using paging, this is extremely quick when I tested for both the filtering and the rendering/scrolling.  Are you using paging or trying to render all 40,000 rows on the screen directly?

Ahhh, I'm also seeing slowdown at higher page size counts.  Even 30 is noticeable for me.  This is a performance issue, I hadn't checked past 10.

My initial suspicion was correct, there was a function that was doing a LOT of repeated calculations that was being used all over the place.  I've turned it into a cached version and seen massive performance improvements when running the 40,000 line stress test with a page size of 100.  Before I was also getting some nasty slowdown, but now it seems quite smooth.
Released the fix as v0.15.1, please let me know if this fixes performance for you as well or if we need to do more work here.

It's definitely significantly faster.
There's a weird phenomenon, though:
Scrolling down is real-time (i.e. scrolling stops when cursor down is released)
Scrolling up is not real-time / lags (i.e. scrolling continues for a couple of rows after cursor up is released)
(terminal: kitty | terminal size: 250x100 | rows: 44000 | filtered down to: various (seems irrelevant))

Interesting... I'm unable to reproduce that.  I get the same apparent performance both up and down and switching between pages.
For the record, I'm using Alacritty at size 224x62 with 40000 rows, both with filtering and without. 🤔  I tried increasing the page size to 130 as well and ended with the same result.
https://gist.github.com/Evertras/07b78eca90f2faee45292db434505577 I'm basically just altering the base filter example for testing this.  If you run this file, do you still see the same behavior?

(sorry for the late reply)
So, I tested this with my app in both alacritty and urxvt, and it occurs in both.
Then I ran your filterstress, and it doesn't exhibit this behavior.
However, with my app, it seems to depend on the unfiltered number of rows (eg. 900 (of 1300 total) -> not noticeable, 1400 (of 45000 total) -> noticeable)
It also doesn't occur if the table is not filtered, even with 44K rows
And it's only for upward movement - rather strange.
Anyway, I just released my app here, in case you want to check if you can replicate this on your setup.
If that's too much of a hassle, we can certainly close this issue, as the performance is now much better in any case.

That's some curious behavior.  I'd be interested to try checking it out at some point, if you could also provide a sample file where you're seeing this?
Let's leave this open for now, and if it turns into too much of a goose chase then we can close this later.

I'm testing with source packages I have in my OS cache.
Examples:
go1.20.2.src.tar.gz 13283 members / filtered by .go (99 pages) → fast
rust-1.65.0-x86_64-unknown-linux-gnu.tar.xz 35251 members / filtered by .html (354 pages) → down ok, up lags
firefox-102.9.0esr.source.tar.xz 334655 members / filtered by .cpp (95 pages) → generally too slow
I usually run everything on kitty 250x100, but I tried alacritty and even urxvt and noticed the same behavior.

I'm still a little puzzled why up vs down was doing this, but it was DEFINITELY happening.  Regardless, digging around has uncovered that we should be able to be a lot more aggressive with the caching.  I've made some updates and tested them locally with your app and seen drastic improvements in performance.  Please give v0.15.2 a try and let me know if it works for you as well.

Performance is indeed significantly better. In fact, it's excellent - even for a filtered table with 330k rows, scrolling is now completely lag-free.
Thanks for fixing this!


https://i.ibb.co/MBzX4sg/Le-H3c-ED-1.png

Duplicate of #288

Please see #288: ibb.co is marked as Pornography.


Feature/update doc

update_doc for 2.2-dev

Codecov Report

Merging #742 into 2.2-dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           2.2-dev     #742   +/-   ##
========================================
  Coverage    94.11%   94.11%
========================================
  Files           92       92
  Lines         3125     3125
========================================
  Hits          2941     2941
  Misses         184      184

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 916f735...8968ebb. Read the comment docs.


How is the two streams fused ?

Hello,
I noticed in the paper (https://arxiv.org/abs/1406.2199) that they finally used svm to fuse the two softmax scores computed by the two streams. Do you know how to use svm in this scenario?

Just think softmax scores as features, so each sample is just one row for SVM training. You can refer to this codebase for how to use SVM. https://github.com/YihengZhang-CV/SeCo-Sequence-Contrastive-Learning


Weird Background Color Artifact on macOS Sierra

Since upgrading to macOS Sierra, some grey color backgrounds cause a weird block to appear in the window. In my config, I'm using #181818 but it seems to happen with a wide spectrum of grey colors. When I check the color of the box with Color Meter, it comes back as #242424. Also, the box seems to resize as you type text into the field.

Here's a copy of my config:
module.exports = {
  config: {
    fontSize: 12,
    fontFamily: 'Menlo, "DejaVu Sans Mono", "Lucida Console", monospace',
    cursorColor: 'rgba(248,28,229,0.75)',
    cursorShape: 'BLOCK',
    foregroundColor: '#F8F8F0',
    backgroundColor: '#181818',
    borderColor: '#272727',
    css: `
      .hyperterm_main {
        border: none !important;
      }
      .header_header {
        background: #272727 !important;
      }
      .tab_tab {
        border: 0;
      }
      .tab_active::before {
        border-bottom: 2px solid #FD971F;
      }
    `,
    termCSS: `
      ::selection {
        background-color: #ccc;
      },
      background-color: '#181818'
    `,
    padding: '12px 14px',

    colors: {
      black: '#272727',
      red: '#F92672',
      green: '#A6E22E',
      yellow: '#FD971F',
      blue: '#66D9EF',
      magenta: '#AE81FF',
      cyan: '#38CCD1',
      white: '#ffffff',
      lightBlack: '#808080',
      lightRed: '#F92672',
      lightGreen: '#A6E22E',
      lightYellow: '#FD971F',
      lightBlue: '#66D9EF',
      lightMagenta: '#AE81FF',
      lightCyan: '#38CCD1',
      lightWhite: '#ffffff'
    },
    shell: ''
  },

  plugins: ['hyperterm-blink'],
  localPlugins: []
};

HyperTerm 0.7.1
Electron 1.2.8
darwin x64 16.0.0

For giggles, I built the current master branch from source and tried it on Sierra. No more weird color artifacts. Was this a known issue in 0.7.1? If so I guess we can close this.

This is Chromium bug (https://bugs.chromium.org/p/chromium/issues/detail?id=633805) and it's related with non-standard color profiles. To fix it now you can: a) change color profile for that monitor, or b) run hyperterm with --enable-gpu-rasterization.

Thanks @Greenek I'll probably do the latter. How do I start hyperterm with that flag on macOS?

Sorry, I forgot to reply! The easiest way I think is add
app.commandLine.appendSwitch('enable-gpu-rasterization', 'true');

somewhere around app/index.js:19 and rebuild.

Awesome thanks @Greenek.
Looks like Chromium Canary builds are now enabling that by default. Any downside to just doing that for Hyperterm by default?

@PatrickTulskie I'm not sure. GPU rasterization is slower for text and I have seen many reports about problems on Linux (but it's not our problem, yet).
I made a simple test and after enabling GPU rasterization FPS drops from ~30 to ~20 while scrolling. At the screenshot below you can see that shape of the chart is much irregular for GPU raster enabled, but IMO it's hard to notice any difference without counter. Rendered fonts looks the same. But... it's just 5 minutes test in the single environment :)

![untitled-1](https://cloud.githubusercontent.com/assets/160300/18959584/0107870e-8667-11e6-8440-cc232e06cb0f.png)

Yeah dropping under 30fps is going to be noticeable. Probably not a good idea to add it as a default flag.

I still have the same issue with Hyper <IP_ADDRESS>8 on macOS 10.12.2 — any ideas on this besides the enable-gpu-rasterization-flag?


hack/verify-gendocs.sh is slow

The slowest part of every commit is waiting for hooks.  I added some printouts to find the culprit - see $SUBJECT.  Can we not run this test on every commit and rebase?
If we switched to using pre-commit instead of prepare-commit-msg we could force-override it (--no-verify) if needed.
@lavalamp

I'm OK with only running verify-gendocs.sh in travis/shippable. Honestly it only ever produces noise for me locally (when you switch branches and fail to make clean, it fails you for no reason). But maybe it's different if you work on the cli a lot?


implement egl device selection

Implement the EGL render device selection in issue #118
Select render GPU is a critical feature for running batch of experiments on multi-gpu servers.
Users will be able to select a gpu used for rendering by setting environment variable EGL_DEVICE_ID=x

@googlebot I signed it!

(overriding the CLA label because my review comments were made using my personal email address)

Merged manually in 7ec5a46d0152bcd024cb87eeb6052cc8bc77df7b. Thanks for your contribution!


Server.kill: use :quitall

The previous method of closing input/output unconditionally will cause
Vim to end with SIGHUP, which causes a wrapping process using Python's
subprocess module to abort:
10342      0.000166 write(1, "Vim: Finished.\r\n", 16) = -1 EIO (Input/output error)
10342      0.000169 rt_sigaction(SIGHUP, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7ff4714958f0}, {sa_handler=SIG_IGN, sa_mask=[HUP], sa_flags=SA_RESTORER|SA_REST>
10342      0.000122 rt_sigprocmask(SIG_UNBLOCK, [HUP], [HUP], 8) = 0
10342      0.000081 getpid()            = 10342
10342      0.000058 kill(10342, SIGHUP) = 0
10342      0.000103 --- SIGHUP {si_signo=SIGHUP, si_code=SI_USER, si_pid=10342, si_uid=1000} ---

Using :quitall! and waiting for Vim to finish is cleaner.
This also uses SIGTERM instead of SIGKILL.
Fixes https://github.com/AndrewRadev/vimrunner/issues/51.

Killing the server with TERM instead of KILL makes a lot of sense, for sure. If nothing else, we could do the "TERM -> wait for timeout -> KILL after 3 seconds" thing you're doing. Quitting with :quitall is a viable strategy as well, but I'd rather have it a separate method. Maybe we could have a def quitall! and a separate def kill? If nothing else, doing a kill -9 is a super fast way to get rid of the server in the tests :). With the :quitall, on my machine, tests are about 14s, from 8s with kill -9.
What do you think? Would it be good enough to have two methods?

Also, I have no idea what order the @r.close; @w.close have to be done in, whether before or after. Could you explain why you've moved them to the end? Does that solve some issue?

Your plan sounds good.

Would it be good enough to have two methods?

Sure.
I've moved @r.close; @w.close since closing input/output would send SIGHUP already.
But I was a bit confused myself, given that I run Vim wrapped in covimerage (a Python program that uses subprocess, and e.g. SIGHUP was not forwarded to Vim), and then also by having Vim segfault itself in certain situations.

With the :quitall, on my machine, tests are about 14s, from 8s with kill -9.

Depending on what you used the sleep 0.1 while Process.waitpid(@pid, Process::WNOHANG).nil? might add some overhead already timewise.
Not sure what to do here - maybe using TERM would be a good first step (waiting up to X seconds and then using KILL), without the quitall?

Depending on what you used the sleep 0.1 while Process.waitpid(@pid, Process::WNOHANG).nil? might add some overhead already timewise.
Not sure what to do here - maybe using TERM would be a good first step (waiting up to X seconds and then using KILL), without the quitall?

First off, it's not a huge deal. The Vimrunner test suite itself probably calls kill a lot more often than most Vim plugin test suites, if they set reuse_server = true in their helpers. A single Vim instance that's cleared after every test would usually work just fine.
The slowdown is probably due to whatever cleanup a Vim instance does when it's closed, maybe cleaning temporary files, maybe some other work. One extra command probably adds to it as well. With a TERM kill, the test suite is 11s, which is literally right in the middle. The waitpid is probably not a problem, since it never really gets all the way to the timeout. It might add an extra 100ms or so because of the sleep 0.1, but that's probably fine.
What I would go with is three functions:

.quitall! that runs that command, waitpids, and then hard-kills if there's a timeout
.kill (the default) that does a TERM-kill, waitpids, and then hard-kills if there's a timeout
.hard_kill  that does a kill -9, unconditionally

That way, if you really need fast relaunching of a Vim instance, you could hard-kill it, and if you want to be sure everything is cleaned up as in your case, you could use quitall. For most people, I imagine the compromise would be fine?
If you're okay with implementing that, I can then look to expose some configuration option for the test helpers, apart from start_vim, maybe a method called stop_vim, to make testing easier.


I want a share page for "legacy" lessons

Acceptance Criteria:

[ ] If a lesson is from the legacy group of lessons, then there should be a share page /share
[ ] Page title "Share Lesson: LESSON NAME"
[ ] Don't worry about components, just have a page for sharing please
[ ] Add to pa11y/percy as required

https://www.figma.com/file/LSjbzdvHo17XqXGBRNJjQP/Old-%2F-new-content?type=design&node-id=83-61233&t=eJTi8ETWxp1QqAyQ-4

notion


Add test for failed registrations

Assure registration goes through for new user registration, going through registration route

Moved to #821


Add bedrock_data_width parameter to ME, update CCE

This PR adds a new aviary param bedrock_data_width that will control the width of the LCE-CCE and CCE-MEM interface data widths at the LCE, CCE, and various related interconnections between the two. This parameter standardizes these widths and adds clarity to the ME by enabling easy assertion-based checks on data width parameters between interacting components.
The CCE is updated to use this new parameter. Additional cleanup in the CCE is performed, related mostly to parameters. The LCE will be changed to use BedRock Burst with this parameter controlling the data width in an upcoming change.

Requires merge of be_dev to dev to capture some aviary rom changes


Stable merge for week 19 of 2023

Updated Packages

koreader - 2023.04-1 (#672 #681)
display, rm2fb-client - 0.0.31-1 (#680 #686)

If rm2fb fails to start on install, disable it to avoid soft-bricking the device
Add support for the following OS versions:

<IP_ADDRESS>1
<IP_ADDRESS>5

wordlet - 0.0.2-2 (#670)

Swap M and N on keyboard
Fix image thumbnail code

harmony - 0.2.2-1 (#670)

Fix exporting individual layers

simple - 0.2.0-2 (#670)

Add "range" input widget
Add "canvas" widget
Less debug output
Make images clickable
Move 'timeout' to its own thread instead of jamming task queue
Ignore empty lines

remux - 0.2.4-1 (#670)

Add "suspend" to remux FIFO api

rpncalc - 0.0.3-2 (#670)

Make it more like the hp48

toltec-base - 1.2-1 (#685)

Only disable sys-subsystem-net-devices-usb1.device if on a reMarkable 1. On a reMarkable 2, this makes SSH over usb no longer available.
Make toltec-base properly clean itself up on uninstall

kernelctl - 0.1-6 (#691)

Reset to the default kernel on uninstall so that toltecctl uninstall will return the device to a stock state

restream - 1.2-1 (#688)
fbink, fbdepth, and fbink-doom - 1.25.0-1 (#687)

Note: This doesn't change what OS version that toltec supports, as full support still requires ddvk-hacks to be updated, and for proper testing of various other packages.

We are doing some further testing on uninstalls and managed to break something. I'm working on a break fix now that we'll include before merging this.


refactor: add access to token used for magic-link generation

Magic links often need to be customized. This PR allows folks to customize the link by providing access to the ~HashedToken~.
EDIT: We changed this to use {{ .TokenHash }} instead. You can add this in your email templates in the Supabase dashboard under the email templating section

hmm can you also add it to the RecoveryMail, InviteMail, EmailChangeMail and ConfirmationMail?

Is there documentation on how to use this feature on the client-side?

@liaujianjie we'll update our docs but you can use it to circumvent the problem where email clients preview the magiclink in the email. This can be done by adding a link in the email template which redirects a user to a page on your site that contains a button that they need to click to "confirm their email". (i.e. Click here to confirm your email!).
When the user clicks on that, they should be redirect to https://your_site_url/confirm_signup where you can grab the query params, reconstruct the actual verify endpoint: https://project_ref.supabase.co/auth/v1/verify?token={{.TokenHash}}&type=signup&redirect_to=xxx and embed the verify link in a button.

@kangmingtay

One small quality-of-life improvement suggestion: allow us to reference the site URL in the email templates so that we can construct the URL like

How will redirection work with the use of .TokenHash?

Just checked, actually the site url is already available if you do {{ .SiteURL }}.

How will redirection work with the use of .TokenHash?

Hmm yeah i'll add this to the email templates too so it can be easily referenced. For now, the only way to get it is through the {{ .ConfirmationURL }} which isn't great..


Changed how Sigma works for gp_dot_prod_cov (Issue #1246)

Summary
Fixes #1246 . @avehtari make sure and verify that this meets your needs. If I've screwed up somewhere and it isn't what you want, we should do a quick redesign.
We're switching how the gp_dot_prod_cov function works from:
k(x1, x2, sigma) = sigma^2 * x1.dot(x2.transpose())

To:
k(x1, x2, Sigma) = x1.dot(Sigma.dot(x2.transpose()));

Where Sigma is now a matrix.
Tests
The tests are all in: test/unit/math/prim/mat/fun/gp_dot_prod_cov_test.cpp . This is only a prim implementation
Side Effects
This changes the definition of gp_dot_prod_cov. That function exists at the interfaces but was never documented so I doubt it's been used much.
Checklist

[x] Math issue #(issue number)

[x] Copyright holder: Columbia University
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[ ] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

Where Sigma is now a matrix.

I did not really want it to be a matrix. Especially if this means that it's always full p x p matrix (where p is the number of columns in x1 and x2. If Sigma is matrix, we get additional p x p matrix times n x p matrix computation, while in scalar case it would be 1 scalar time n x p matrix computation, and in vector sigma case it would p times (1 scalar time n x p) computation. Matrix Sigma is fine, if scalar and vector sigma computations don't get slower.

This has been sitting here for some time now with green light on the tests. @bbbales2 do you have anyone specific in mind for the review?

@rok-cesnovar this ended up waiting long enough that it looks like ternary matrix tests are going in soon. It worked for what @avehtari was looking for, so I want to wait for the ternary tests, add them here, and then get it reviewed.

1452 is in, Ben do you want me to check this out this week?

Ah, sorry about leaving this hanging. I'm going to close this. As things have evolved, we can write the models we wanted in pure Stan and they are efficient. The interface as it is is fine.


Emit Make File Fragments

With a command line switch mdpre could skip normal processing and just pick image imbeds and =include files - and create a dependency list - in make file format.

m makeFileName is available.


Connection to locally running eventstore fails when node-eventstore-client is used in a docker container.

When attempting to connect to Eventstore running locally while running code in a docker container the connection never succeeds and after attempting to reconnect 10 times will close the connection. Server logs seem to indicate no attempt at connecting to Eventstore reached the server. Issue sounds similar to #60, however adding verboseLogging: true fixed nothing.
Repo with working example can be found here.
With that repo running building and running the container will result in the connection being closed, however running npm run build followed by node ./dist/subscribe.js results in a successful connection.
Attempting to connect to an eventstore server that isn't being hosted on my local machine results in a successful connection on both the docker container and by just running the code directly.

Please post some logs here. You are aware that EventStore binds on localhost by default, so would not be accessible by the docker VM, unless default settings are changed


Upgrade test env to Crate 3.3.3

We've recently upgraded our prod Crate cluster to Crate version 3.3.3 but we're not yet using this version in our dev test environment.
Proposed solution
Use Crate 3.3.3 in all our docker files.

let's check the matrix approach to test multiple version of crate!
https://github.com/smartsdk/mongo-rs-controller-swarm/blob/master/.travis.yml

Hi @chicco785 , Please assign this issue to me.

Raised PR#313


Parameters / json fields

The generated API doesn't seem to know anything about the fields of the structs and enums with #[api_v2_schema] annotation (for example used in a POST request, or in JSON response. Is it out of paperclip's scope?

It does, but only as long as you return a container like web::Json<T> (wrappers like impl Future and Result<T, E> are also supported). Although, note that if you return something like impl Responder or HttpResponse, then there's no way for the plugin to know (at compile time) what/how you've responded. Tackling this problem requires a bit more work, so it's not something the plugin supports at the moment. And no, it's definitely in the scope of this project (just haven't found the right way yet).

Thanks! It works well (not sure what was the problem).

I do get these
warning: skipping enum variant with named fields in schema.
  --> src/msg.rs:31:13
   |
31 |     Invalid {path: String, reason: String},

Will it be fixed some time?

It's something I'm planning to work on soon, but not immediately.


Turned on fused batch norm.

Enabling fused batch norm dropped my step time from:
INFO:tensorflow:global step 2500: loss = 4.4076 (2.17 sec/step)
to
INFO:tensorflow:global step 300: loss = 6.5134 (1.82 sec/step)

Thanks for your contribution, I will test it in the coming days.


Unable to upload a realm logo once I upload an unsupported file

steps to reproduce :

Upload the unsupported file as realm logo(eg pdf)
Try to upload a supported file (jpg or png)

@zulipbot claim

@zulipbot add "bug"

@zulipbot  "area: settings (admin/org)" "area: settings UI"

@zulipbot add "area: settings (admin/org)" "area: settings UI"


widgets in second tree is never disposed (i.e. state.dispose never called)

log
https://github.com/fzyzcjy/flutter_smooth/issues/23#issuecomment-1261766300

what is the best way to dispose?

Method 1: let widget change child to empty container


Fix proxyplugin route

There was a typo in the route name.

Production is broken and test are not covering this obviously so merging without waiting for CI


An issue regrading duplication

When I ran more than a thousand samples, there may be several identical accession numbers with different e-values and identities. It results in the inconsistency of the number of accession similarity and accession number in your script, HGT_homologs_sequence.py.

Hi,
I think the issue regarding duplication in sequence homologs searching would not occur in the script. If you want to run the program for more than one thousand samples, there are two solutions for you to consider:

you can split your samples into 1000 individual files, and then run the script like that:
python scripts/HGT_homologs_sequence.py input/gene1.fasta
python scripts/HGT_homologs_sequence.py input/gene2.fasta
python scripts/HGT_homologs_sequence.py input/gene3.fasta
It is easy to manipulate by writing scripts, which can be implemented via less than ten lines.

You can also look through the script HGT_homologs_sequence.py, and just change a few lines based on your own requirement, which is not difficult.

Best regards,
Le


[BUG] Incorrect logic statement in detection search "Detect Renamed PSExec"

Description:
The detection search "Detect Renamed PSExec" in the "Active Directory Lateral Movement" Analytic Story has an incorrect logic statement in its search query that results in all results being return with an "original_file_name=psexec.c".
Expected Result:
If process_name=psexec.exe or process_name=psexec64.exe and original_file_name=psexec.c then it shouldn't return the event. It should only return it if it doesn't equal both psexec.exe and psexec64.exe.
Actual Result:
In my case, my process_name was "PsExec.exe", which shouldn't be returned. But it was because it didn't satisfy both conditions of the OR statement. "PsExec.exe" does equal "psexec.exe" but it doesn't equal "psexec64.exe".
App version:

ESCU: 4.31.0
Splunk Security Essentials: 3.8.0

Suggested Fix:
Change this part of the query from...
(Processes.process_name!=psexec.exe OR Processes.process_name!=psexec64.exe)
to...
(Processes.process_name!=psexec.exe AND Processes.process_name!=psexec64.exe)

HI @OberAlex , I confirmed this was updated. Thank you!


ScrollView should not use RefreshControl on tvOS

Motivation: On tvOS, Flatview and other components that use ScrollView with a RefreshControl will break without this change.
Test plan: Manual testing on tvOS simulator.

@ericvicenti here is the separate PR for the ScrollView/RefreshControl fix for tvOS.

I'd rather put the TVOS check in the same check as Platform.OS === 'ios' a few lines after. I guess it would still work properly since isTVOS is probably undefined on Android but that would make it clearer.

@facebook-github-bot shipit

@facebook-github-bot shipit

plz bot :o
@facebook-github-bot shipit

@facebook-github-bot status

ur bot is broken, I think

Yea I'll bug @mkonicek

Hi guys, sorry I don't see GitHub notifications - there are too many to keep track of, and I think there's no way to filter them by mentions? Please message me on Slack like Janic did.


unable to add http://feeds.feedburner.com/99pi from InoReader

If I attempt to add this feed to Inoreader, it doesn't show up in Vienna, any future refresh of Vienna hangs, and the following is logged to the console.  It's completely reproducible for me.  This happens both when adding the feed on Inoreader directly and through Vienna.
5/4/16 10:45:27.904 AM Vienna[41022]: *** -[__NSPlaceholderArray initWithObjects:count:]: attempt to insert nil object from objects[2]
5/4/16 10:45:27.905 AM Vienna[41022]: (
0   CoreFoundation                      0x00007fff9d86f4f2 __exceptionPreprocess + 178
1   libobjc.A.dylib                     0x00007fff8d62a73c objc_exception_throw + 48
2   CoreFoundation                      0x00007fff9d761372 -[__NSPlaceholderArray initWithObjects:count:] + 290
3   CoreFoundation                      0x00007fff9d76a0d4 +[NSArray arrayWithObjects:count:] + 52
4   Vienna                              0x0000000100c81a8f Vienna + 203407
5   Vienna                              0x0000000100cea061 Vienna + 630881
6   Foundation                          0x00007fff92358f5e __NSThreadPerformPerform + 279
7   CoreFoundation                      0x00007fff9d804881 CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 17
8   CoreFoundation                      0x00007fff9d7e3fbc __CFRunLoopDoSources0 + 556
9   CoreFoundation                      0x00007fff9d7e34df __CFRunLoopRun + 927
10  CoreFoundation                      0x00007fff9d7e2ed8 CFRunLoopRunSpecific + 296
11  HIToolbox                           0x00007fff9896c935 RunCurrentEventLoopInMode + 235
12  HIToolbox                           0x00007fff9896c76f ReceiveNextEventCommon + 432
13  HIToolbox                           0x00007fff9896c5af _BlockUntilNextEventMatchingListInModeWithFilter + 71
14  AppKit                              0x00007fff9e0c1efa _DPSNextEvent + 1067
15  AppKit                              0x00007fff9e0c132a -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454
16  AppKit                              0x00007fff9e0b5e84 -[NSApplication run] + 682
17  AppKit                              0x00007fff9e07f46c NSApplicationMain + 1176
18  libdyld.dylib                       0x00007fff922d85ad start + 1
)

I could not reproduce the problem. @bwelling, could you please provide the complete crashlog ?

The process didn't crash; it hung.  There are some .hang files, but they appear to be the entire state of the machine, not the Vienna process (and they're in some binary format that I can't attach here).

You can zip them and attach them here

Vienna_2016-05-04-104954_wavelet.hang.gz

It appears that the slowdown is caused by the logging in process, which unfortunately is still running synchronously on the main thread (I plan to change this later, probably in 3.2).
I suggest that, before trying to add this particular feed, you make sure Vienna is successfully logged in to Inoreader. For instance, you could use the « File -> Update Subscriptions from Open Reader » menu command, or refresh another feed. If the problem still occurs on adding « 99% Invisible » , please upload again the .hang here.

This happened multiple times, and Vienna was connected to InoReader in all of them.  In each case, the refresh successfully updated all of the other feeds, but the new feed didn't show up, and the refresh button never switched back from the X to the normal icon.

Also, in between the failures, I restarted Vienna, and logged out and back in to InoReader.

As I said, I could not reproduce the problem with my own Inoreader account, and the .hang file you uploaded does not show interesting data.
To investigate, I need a .hand done under the conditions I described an hour ago.

I think I see why the .hang file isn't useful.
What's happening is that if I add the feed, the sync from InoReader hangs (as evidenced by the refresh button icon being an X), and the new feed doesn't show up.  If I then quit and restart Vienna, it hangs on startup (beachball spinning), and if I then Force Quit, I get the .hang file.  I'm including a new one, but I'm guessing it will be the same as before.
Is there something I could do to enable verbose logging or debugging during the initial attempt?
Vienna_2016-05-08-175106_wavelet.hang.gz

You're right, the .hang is similar to the previous one.
But I am surprised by the suspected link between the hang and this particular feed.
If you suppress the feed from the web interface of Inoreader, then relaunch Vienna, does the hang still happen ? (please be patient to be sure).
If Vienna hangs at startup, you can temporarily disable refreshes at startup by typing in Terminal :
defaults write uk.co.opencommunity.vienna2 CheckForNewMessagesOnStartup false

Relaunch Vienna, make sure Vienna is logged into Inoreader as suggested above, and try adding again the feed.

I'm not sure what you mean by suppressing the feed.  If I remove the feed from InoReader, Vienna will sometimes start, and sometimes get into a state where it can't authenticate to InoReader.  In the latter case, if I open Vienna's preferences, the InoReader password field has been cleared, and re-entering my password fixes the problem.
If I change the default and start Vienna, and then attempt to add the feed, it has the same behavior as before; it causes a connection to add the new feed, and this refresh hangs.  Vienna is still usable, but the refresh isn't completing, and the new feed isn't showing up.

Sorry, but something is not completely clear for me. Is the hang caused by :

logging Vienna in, and getting list of feeds ( « File -> Update Subscriptions from Open Reader » menu command)
refreshing this particular feed (you can refresh it individually through the contextual menu),
adding it through Vienna (try adding it through Vienna instead of through Inoreader’s web interface),
or when refreshing all feeds together ?

Step by step tests would make things clearer. Please, updload hangs with description of their circumstances.

On May 9, 2016, at 9:48 PM, Barijaona Ramaholimihaso<EMAIL_ADDRESS>wrote:
Sorry, but something is not completely clear for me. Is the hang caused by :
logging Vienna in, and getting list of feeds ( « File -> Update Subscriptions from Open Reader » menu command)
This causes Vienna to get into a state where the UI works, but refresh is disabled, and nothing updates.
refreshing this particular feed (you can refresh it individually through the contextual menu),
I can't do this, as the new feed never shows up at all.
adding it through Vienna (try adding it through Vienna instead of through Inoreader’s web interface),
This is the same as above.
or when refreshing all feeds together ?

Same as above.

Step by step tests would make things clearer. Please, updload hangs with description of their circumstances.

There are no hang files created in any of these cases, as the process isn't hung; the refresh never completes.
I'm not sure what other information to provide; I've described everything that I've done.
Vienna is in a working, connected state. If I add this feed, either using the InoReader web interface or through Vienna, it fails to add, and something in Vienna gets wedged (see the log from my original message, and the Refresh icon never comes back).
If, after some amount of time, I quit Vienna and restart, the process completely hangs. If I force quit, I get a hang file like the ones attached.

Could you try the attached development build (based on current head) ? It should be more verbose in the console log.
Just try the « File -> Update Subscriptions from Open Reader » menu command
Vienna.app.zip

With the new build, the new feed shows up (for the first time!) but with a warning icon (text: An error occurred when this feed was last refreshed).
Here are the logs, starting when I added the feed.
5/10/16 9:42:22.808 AM Vienna[36667]: GoogleReader.m:250 -[GoogleReader getToken] Start Token Request!
5/10/16 9:42:23.819 AM Vienna[36667]: GoogleReader.m:856 -[GoogleReader subscribeToFeed:] Subscribe response status code: 200
5/10/16 9:42:23.819 AM Vienna[36667]: GoogleReader.m:834 -[GoogleReader loadSubscriptions:] Firing directly
5/10/16 9:42:23.819 AM Vienna[36667]: GoogleReader.m:837 -[GoogleReader loadSubscriptions:] Token available, finish subscription
5/10/16 9:42:24.247 AM Vienna[36667]: GoogleReader.m:739 -[GoogleReader subscriptionsRequestDone:] Ending subscriptionRequest
5/10/16 9:42:24.248 AM Vienna[36667]: GoogleReader.m:935 -[GoogleReader createNewSubscription:] createNewSubscription - START
5/10/16 9:42:24.248 AM Vienna[36667]: Adding Open Reader Feed: http://feeds.feedburner.com/99pi with Title: 99% Invisible
5/10/16 9:42:24.251 AM Vienna[36667]: GoogleReader.m:953 -[GoogleReader createNewSubscription:] createNewSubscription - END
5/10/16 9:42:25.852 AM Vienna[36667]: GoogleReader.m:429 __32-[GoogleReader feedRequestDone:]_block_invoke Refresh Done: http://feeds.feedburner.com/99pi
5/10/16 9:42:25.866 AM Vienna[36667]: GoogleReader.m:462 __32-[GoogleReader feedRequestDone:]_block_invoke 42 items returned from https://www.inoreader.com/reader/api/0/stream/contents/feed/http%3A%2F%2Ffeeds.feedburner.com%2F99pi?client=ViennaRSS&comments=false&likes=false&ot=0&n=500&ck=1462898544&output=json
5/10/16 9:42:26.083 AM Vienna[36667]: GoogleReader.m:629 __32-[GoogleReader readRequestDone:]_block_invoke 2 unread items for https://www.inoreader.com/reader/api/0/stream/items/ids?ck=1462898544&client=ViennaRSS&s=feed/http%3A%2F%2Ffeeds.feedburner.com%2F99pi&xt=user/-/state/com.google/read&n=1000&output=json
5/10/16 9:42:26.301 AM Vienna[36667]: GoogleReader.m:702 __35-[GoogleReader starredRequestDone:]_block_invoke 0 starred items for https://www.inoreader.com/reader/api/0/stream/items/ids?ck=1462898544&client=ViennaRSS&s=feed/http%3A%2F%2Ffeeds.feedburner.com%2F99pi&it=user/-/state/com.google/starred&n=1000&output=json
5/10/16 9:42:26.303 AM Vienna[36667]: RefreshManager.m:105 -[RefreshManager nqQueueDidFinishSelector:] Queue empty!!!
5/10/16 9:42:27.172 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.207 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.223 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.239 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.256 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.273 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.340 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.373 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.407 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.441 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.457 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.541 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.625 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.658 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.674 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.708 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.725 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.859 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.875 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.909 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:27.926 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.210 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.243 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.293 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.310 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.376 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.444 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.510 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.561 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.594 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.611 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.627 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.645 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.745 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.761 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.878 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.894 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.912 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.929 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.962 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:28.996 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:29.011 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:29.063 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:29.130 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:29.764 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:29.782 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:29.814 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:29.847 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:30.032 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:30.133 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:30.166 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:30.216 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:30.233 AM Vienna[36667]: Uncommited CATransaction. Set CA_DEBUG_TRANSACTIONS=1 in environment to debug.
5/10/16 9:42:31.866 AM Vienna[36667]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
5/10/16 9:42:33.112 AM Vienna[36667]: RefreshManager.m:105 -[RefreshManager nqQueueDidFinishSelector:] Queue empty!!!
5/10/16 9:42:38.376 AM Vienna[36667]: RefreshManager.m:105 -[RefreshManager nqQueueDidFinishSelector:] Queue empty!!!
5/10/16 9:42:40.619 AM Vienna[36667]: RefreshManager.m:105 -[RefreshManager nqQueueDidFinishSelector:] Queue empty!!!
5/10/16 9:42:44.112 AM Vienna[36667]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

After that finished, I attempted a full refresh; that also worked, and the warning icon went away.

Mysterious 😆

There do seem to be some issues with this build, though; when moving between folders (especially using the ‘skip folder’ button, the list of articles isn’t properly refreshed.

If this persists, please open a new issue, and provide us with a log and a screenshot of your preferences.
I suggest you do a reindex database first ("Vienna" menu)


push backend to azure functions

Backend is pushed to azure. Authentication is missing at the moment. This will be needed when using the production api of osm (specially for the create endpoint).

Backend is pushed to azure. Authentication is missing at the moment. This will be needed when using the production api of osm (specially for the create endpoint).

Add also the requiered headers to the api call in the app


Command "az sf cluster node-type add" fails with unexpected error "list index out of range"

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az sf cluster node-type add
Errors:
list index out of range
Traceback (most recent call last):
python3.8/site-packages/knack/cli.py, ln 215, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 654, in execute
    raise ex
cli/core/commands/__init__.py, ln 718, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
cli/core/commands/__init__.py, ln 711, in _run_job
    six.reraise(*sys.exc_info())
...
cli/command_modules/servicefabric/custom.py, ln 765, in add_cluster_node_type
    _create_vmss(cmd, resource_group_name, cluster_name, cluster, node_type, durability_level, vm_password, vm_user_name, vm_sku, vm_tier, capacity)
cli/command_modules/servicefabric/custom.py, ln 793, in _create_vmss
    virtual_network = list(
IndexError: list index out of range

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az sf cluster node-type add --capacity {} -c {} -g {} --node-type {} --vm-sku {} --vm-tier {} --verbose --subscription {} --vm-password {} --vm-user-name {} --durability-level {}

Expected Behavior
Add a new node type to an existing Azure Service Fabric Cluster.
Environment Summary
macOS-10.14.6-x86_64-i386-64bit
Python 3.8.5
Installer: HOMEBREW

azure-cli 2.12.1

Additional Context

Same error occurs when using "az" on Ubuntu Linux 16.04 & Windows Subsystem for Linux (WSL) with Ubuntu 16.04 on Windows 10.

routing to appropriate team

Please upgrade to latest version of az cli 2.39.0


Warning msg on import

Environment information
py-solc-x==1.1.1
win10
Python 3.7.0
What was wrong?
Doing a simple import prints msg on console, this is highly unusual.
>>> import solcx
INFO: Could not find files for the given pattern(s).

How can it be fixed?
Remove print on import.

this log stmt is no longer found anywhere in the package so im going to close


added server API routes for CRUD operations

I expanded more on the server in preparation for creating a global state with Redux.
Here is what I added:
*Added route points for localhost:port/api/
*Retrieve user info
*Update user info
*Create a new user and store the password as a hash instead of plaintext. (by using bcrypt)
*Delete a user
*Login a user (check if plaintext password from client and the stored hash match)
*Add entries to a user
*Update entries of a user
*Delete entries of a user
*Basic logging middleware of requests (logs to console or to a file called serverlog.txt)
*Basic error handling for all the functionality
For more info read the readme file in /server/readme.md
For a complete list of all the routes go to /server/APIrouter.js
Start the server with
clear && PORT=3001 node index.js inside the server folder.
I welcome any suggestions for improvement or new features.

I approve. Looks solid.


Parameter 'pool_test_on_borrow' does not affect mysql dbconfig.xml

Affected Puppet, Ruby, OS and module versions/distributions

Puppet:
Ruby:
Distribution:
Module version:

How to reproduce (e.g Puppet code you use)
class { '::jira':
  version     => $version,
  installdir  => '/usr/local/atlassian/jira',
  homedir     => '/home/jira',
  user        => 'jira',
  uid         => 41,
  group       => 'jira',
  gid         => 41,
  service_manage => false,
  db          => 'mysql',
  dbtype      => 'mysql',
  dbdriver    => 'com.mysql.jdbc.Driver',
  dbuser      => $dbUser,
  dbpassword  => $dbPass,
  dbserver    => 'localhost',
  dbname      => 'jira',
  dbport      => '3306',
  mysql_connector_manage    => true,
  mysql_connector_version   => $sql_connector_version,
  mysql_connector_install   => '/usr/local/atlassian/mysql-java-connector',
  pool_test_on_borrow       => false,
  javahome    => '/opt/java/java',
   proxy          => {
      scheme       => 'https',
      proxyName    => $url,
      proxyPort    => '443',
   },
   ajp       => {
      port            =>         '8009',
      redirectPort    =>        '8443',
      protocol        =>        'AJP/1.3'
  },
}

What are you seeing
pool_test_on_borrow setting is not in dbconfig.xml
What behaviour did you expect instead
The following should be in dbconfig.xml:
false
Output log
Any additional information you'd like to impart

Bump

The PR got merged so I think we can close this?

thx


Add missing samsung tablet device

Thank you @kristinaSvobodinaSaritasa.
I'll release a newer version soon :)

@kristinaSvobodinaSaritasa , v4.0.1 has been released.

Thank you!
On Fri, Aug 19, 2022 at 4:26 AM Muhammad Ahsan Ayaz <
@.***> wrote:

@kristinaSvobodinaSaritasa https://github.com/kristinaSvobodinaSaritasa
, v4.0.1 has been released.
—
Reply to this email directly, view it on GitHub
https://github.com/KoderLabs/ngx-device-detector/pull/250#issuecomment-1219981098,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATSFDROXE2WQMO3MYLSEVBDVZ2S7RANCNFSM554CECSA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Fix YAML syntax error

The current splitTests definition is parsed as:
{
  type: 'array',
  items: null,
  '$ref': '#/definitions/splitTest'
}

Instead of:
{
  type: 'array',
  items: {
    '$ref': '#/definitions/splitTest'
  }
}

Good eye!

I actually caught it thanks to automated OpenAPI validation added by #194.


Fix console execution affecting wrong console bug.

cf. https://github.com/jupyter/jupyterlab/issues/229
cc: @fperez

Works, thanks!

Cool, thanks! Glad to hear it works, can't test in full right now, fighting too many fires :)


NVSHAS-9285 UI: drop down list button overlaps other elements

Notification part was fixed.
Proxy part still has the overlap issue.

added the fix for the proxy overlapping


feat(workload): expression selectors and pod metadata integration

Introduce a new API for workload selectors that supports both matchExpressions as well as applying the entries in matchLabels to the pod metadata for automatic selection.
BREAKING CHANGE: defaultSelector renamed to select. selectByLabel renamed to select and underwent an API change: deployment.selectByLabel('key', 'value') -> deployment.select(LabelSelector.equals('key', 'value'))
Fixes https://github.com/cdk8s-team/cdk8s-plus/issues/414
Fixes https://github.com/cdk8s-team/cdk8s-plus/issues/413

💚 All backports created successfully

Status
Branch
Result

✅
k8s-21/main

✅
k8s-20/main

Questions ?
Please refer to the Backport tool documentation


Error when trying to use connection pool

I created a connection pool and used the creds in my prometheus/promscale setup (which was working) and now i'm getting this error:
server returned HTTP status 500 Internal Server Error: Error setting series ids: Error filling labels on begin: ERROR: prepared statement \"lrupsc_21_2\" does not exist (SQLSTATE 26000)

This is the error in the promscale container
ERROR: prepared statement \"lrupsc_6_7\" does not exist (SQLSTATE 26000)

Thank you for reporting this. Was anything deleted from the database?

I don't think so.

similar issue if I connect promsale to pgbouncer
ERROR: prepared statement \"lrupsc_5_0\" does not exist

direct connect to timescaledb works


Resume template

I absolutely love the design of the resume, It's extremely elegant. I'd like to know how it was made.
Is it a template or an original design?

You may design your professional resume from Flow CV. It is very easy to build and user friendly.

+1 for the same


Notabene Error Not Handled

Bug Description
An error reported from notabene when submitting an identity object request is not handled. When the error occurs, instead of the usual flow, the request to notabene redirects to the callback URL with an error, such as:
concordiumwallettest://identity-issuer/callback/0F463571-D594-43AE-8F8D-789F84BBB5E7#error=%7B%22error%22%3A%7B%22code%22%3A%22INVALID_REQUEST%22%2C%22detail%22%3A%22Invalid%20Identity%20Object%20Request%22%7D%7D

In this case, the response should be interpreted as an error, and a message shown to the user. Instead, it is treated as if it were a successful identity issuance and a pending identity/account is created that cannot ever resolve.
(This seems at least in part to be caused by a problem with parseCallbackUri. In the case where it does not contain the string "#code_uri=", the entire URI is returned.)
Steps to Reproduce
Attempt to create an identity while notabene is failing.
Expected Result
The identity creation should fail with an appropriate error reported to the user
Actual Result
Identity creation appears to succeed without going through the full process, and a pending identity and account are created in the wallet that cannot be resolved.
Versions

Software Version 1.0 (22) Testnet
OS
Browser
Mobile device, if applicable

To be discussed: Should the user get the possibility to contact the IDP immediately, so the incident does not necessarily have to go a detour via us?

Error message also to be improved in Android: https://github.com/Concordium/concordium-reference-wallet-android/issues/61

No immediate test possible.


Provide a GitHub action for installing scala-cli

Should be pretty simple, the whole action can even be something like this probably:
name: 'Install scala-cli'
description: 'Install scala-cli'
author: 'Virtus Lab'
runs:
  using: 'composite'
  steps:
    - run: |
        curl -s --compressed "https://virtuslab.github.io/scala-cli-packages/KEY.gpg" | sudo apt-key add -
        sudo curl -s --compressed -o /etc/apt/sources.list.d/scala_cli_packages.list "https://virtuslab.github.io/scala-cli-packages/debian/scala_cli_packages.list"
        sudo apt update
        sudo apt install scala-cli
      if: runner.os == 'Linux'
    - run: brew install Virtuslab/scala-cli/scala-cli
      if: runner.os == 'macOS'

Sorry, not sure what to do for windows.
Thanks!

@armanbilge another option is to use coursier/setup-action. I do this here and it works pretty well.

@ckipp01 aha, apps: scala-cli scalafmt is exactly what I needed. Thanks for the pointer!

btw you might not even need scalafmt but can instead use scala-cli format. I only had that in there since before --check didn't work with scala-cli. It works with the latest scala-cli, I just haven't updated this yet.

Hi @ckipp01  @armanbilge  you can try to use VirtusLab/scala-cli-setup -  https://github.com/VirtusLab/scala-cli-setup. It is a fork of coursier/setup-action where we enforce to install scala-cli.
There are also available functions from coursier/setup-action such as apps and jvm
jobs:
   scala-cli:
      runs-on: ${{ matrix.OS }}
      strategy:
        fail-fast: false
        matrix:
          OS: ["ubuntu-latest", "macos-latest", "windows-latest"]
      timeout-minutes: 120
      steps:
       - uses: actions/checkout@v2
       - uses: coursier/cache-action@v6
       - uses: VirtusLab/scala-cli-setup@main
       - run: scala-cli


File at us/co/washington should actually be us/ny/washington

As reported via email.

Related issue:

#4680


Build app for Linux

This has thus far only been tried in CI. And it's failed throughout. Example:
https://github.com/Vlsir/Hdl21Schematics/actions/runs/3434967680/jobs/5726793444
Note MacOS and Windows also run for each CI commit, and generally work.

Hi, so I'm attempting to build the Schematics editor on Ubuntu 22.04 LTS. I've found that yarn.lock is loading a version of Electron-Forge which has a bug for Ubuntu. So removing yarn.lock allows npm to build with the latest dependency versions that then builds out the app with the documented instructions. Although it will leave it as naked shared object files and binary and not package them.
This is caused by the name attribute at the top of package.json somehow overriding the executableName that is explicitly stated in the packagerConfig as it I think it should be from debian packager docs. So I have no idea why that is happening, but the changing the name to match the executableName leaves me with a nice ~70MiB .deb and .rpm that I can move over to and install on a blank machine without any problems (also running Ubuntu 22.04 LTS).
I had none of these problems with the VS Code Extension due to a lack of a yarn.lock and not having this executableName issue. I am still sort of left wondering if the build worked exactly as it should have due to some issues - no dark mode, default into developer mode, disappearing side-bar (minimize once and then you'll never see it again).

OK interesting.
Our GitHub actions also try this, although I believe on the older Ubuntu v18. And as the issue intro would indicate, it fails.
You wanna put in a PR with what you changed? And what is it, the electron-forge version?
Re: the current electron-forge version - there is #24 on the topic. It largely boils down to "it's a weird version but the newer ones removed the debugging setup I like". Maybe it's time we just gotta let that debugging setup go.
Re: your observations in the VsCode extension - my guess is it "built right". While I envision VsCode as a central long-term mechanism, most debugging happens in the electron app, largely because, well, the debugging's much better. (And it's early days here! This didn't exist as of late August.) Notably we've got #3 on dark mode. More fertile ground for a PR!

AFAIK runs-on: ubuntu-latest is the latest LTS distro of ubuntu (v22 right now). The issue as far as I understand it, is a simple misconfiguration problem for package.json inside of the EditorApp - I got other issues before with yarn.lock earlier, but this was a configuration issue on my end.
For now it builds and packages on the locked version, so I'll just leave well enough alone. I'll open a PR now.


No preview color until close

For some reason I don't get a preview color until after I close the color picker. JS Fiddle (just click the grey area in the input group to open color picker and then click it again to close): http://jsfiddle.net/smoLujex/
I think colorpicker misses that the value of the input has changed .. and it doesn't respect setValue.. But when the color picker is closed, it reads the value from the input..

Hi @markusjohnsson , I found the problem, the setValue should call update with force=true https://github.com/mjolnic/bootstrap-colorpicker/blob/master/src/js/colorpicker.js#L307
I will work on a fix, but at the moment you could trigger 'updateComponent' manually
 ($(element))
    .colorpicker('setValue', ko.unwrap(valueAccessor())).colorpicker('updateComponent');

Thanks

The workaround works like a charm!
Thank you for the tip and thanks for this useful project :)


v2.2.4 xip.io "no such host" occurs randomly with pipeline

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):
Pipeline auto trigger build
Result:
Get http://registry.world<IP_ADDRESS>.10.xip.io:5000/v2/: dial tcp: lookup registry.world<IP_ADDRESS>.10.xip.io on <IP_ADDRESS>:53: no such host

This happens randomly. Sometimes it can't resolve the host, sometimes it does

Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.2.4
Installation option (single install/HA): single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): custom
Machine type (cloud/VM/metal) and specifications (CPU/memory): metal
Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-19T16:40:16Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.5", GitCommit:"2166946f41b36dea2c4626f90a77706f426cdea2", GitTreeState:"clean", BuildDate:"2019-03-25T15:19:22Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client:
 Version:           18.09.6
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        481bc77
 Built:             Sat May  4 02:35:27 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.6
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.8
  Git commit:       481bc77
  Built:            Sat May  4 01:59:36 2019
  OS/Arch:          linux/amd64
  Experimental:     false

22:58:38 stderr: fatal: unable to access 'http://gitlab.world<IP_ADDRESS>.10.xip.io/skynet/ainiml.space.git/': Couldn't resolve host 'gitlab.world<IP_ADDRESS>.10.xip.io'


Tips from another plugin not displayed in custom header until vimrc is sourced manually

Hello, I'm trying to display tips instead of quotes in the header. Alas, it only starts showing the tips after I've sourced my .vimrc and manually triggered Startify again.
If I remove the conditional from the function, I get the error E117: Unknown function: GetTip.
Note: it only diplays only one tip per vim session as well, maybe due to some optimization not to run the same code twice?
More info can be found here: https://github.com/michaelb/vim-tips/issues/3
" Custom startify header
function! s:tips_wrapper()
    redir => var
      if exists('*GetTip')
        runtime $HOME/.vim/bundle/vim-tips/plugin/vim-tips.vim
        let tip = GetTip()
        silent! echo tip
      endif
    redir END
    return map(split(var, '\n'), '"   " . v:val') + ['']
endfunction

let g:startify_custom_header = s:tips_wrapper()

See :h g:startify_custom_header_quotes instead.
Afterwards startify#fortune#quote() will give you a random tip, so you can change the header to let g:startify_custom_header = 'startify#fortune#quote()', if you only want the tip, without the cowsay around it.

Ah, just re-read this. If vim-tips only provides GetTip() to get one one-line tip at a time, you can also use this:
let g:startify_custom_header = '["   " . GetTip()]'

See the bottom of :h g:startify_custom_header. If its value is a string, its content is evaluated every time :Startify is run.

 Thank you! I guess I have some studying to do, not many things about vimscript are clear to me yet.

Hah, you're welcome. If you have VimL questions, just ask here in this issue.


Testing Block Production: Miner can produce 1 block that gets sent over the network

Acceptance Criteria

[ ] Storage Miner & Forest are able to be started up and connected to each other
[ ] Storage Miner is able to produce a block


Use chart-testing to lint the Helm Chart

Proposed changes
Problem: We want to validate all the files related to the helm chart and not just run helm lint
Solution: Use helm/chart-testing
Closes #2043
Checklist
Before creating a PR, run through this checklist and mark each as complete.

[x] I have read the CONTRIBUTING doc
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have checked that all unit tests pass after adding my changes
[ ] I have updated necessary documentation
[x] I have rebased my branch onto main
[x] I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

Release notes
If this PR introduces a change that affects users and needs to be mentioned in the release notes,
please add a brief note that summarizes the change.

NONE

This log in the pipeline run: nginx-gateway-fabric => (version: "1.2.0", path: "charts/nginx-gateway-fabric"), doesn't mean it's running on the 1.2.0 tag, does it? It just detects the latest version and prints it I hope?

yeah it prints the version in Chart.yaml


The opposite of select_keys

The select_keys function is extremely handy. However, sometimes I only know which keys I don't want, or the number of keys I don't want is significantly smaller than those I do want. I did not see a function (for example, remove_keys) that would allow for that.
Is it expected that key removal be accomplished with other functions? Would you be interested in a PR for a remove_keys function?

Maybe omit_keys is a better name

I think omit_keys is a better name. Thank you!
Your suggestion also inspired me to think of ignore_keys, or dissoc (since the select_keys function was inspired by Clojure) as possible names.