Create an self-hosted filter on the interactive version

Please add a filter to show which software can be completely built and run on self-hosted/on-premise datacenters

Alternatively following filters could be suggested:

can be run on an airgapped network
can be built on an airgapped network
can be built only with opensource tools/systems
can be run with only opensource-systems
can be run without license management system

perhaps this is easier to filter.

Sorry for the long delay in my response. Note that adding new filters at this point is quite challenging, as we need to back-fill the information across 581 cards: https://landscape.cncf.io/category=provisioning,runtime,orchestration-management,app-definition-and-development,platform,serverless,observability-and-analysis&format=card-mode&grouping=category
However, nearly all of the open source projects will meet your criteria. They can be run on airgapped networks. They all depend on only open source components, so if you watch the build, you can locally cache any dependencies. None of them need license management systems.
That is these 338 cards: https://landscape.cncf.io/category=provisioning,runtime,orchestration-management,app-definition-and-development,platform,serverless,observability-and-analysis&format=card-mode&grouping=category&license=open-source
The only exception I see is items like https://landscape.cncf.io/selected=kops that is explicitly designed for installing on to AWS.

Well, Travis-CI is there, too. And you cannot self-host That as far as i am aware.
AND: Though most may be buildable and installable and runnable on an airgapped network, it is often not sustainable. Did you ever try to build and run Hadoop or Gitlab (just an example) on your virtual machine which is a current debian, centos or ubuntu lts? This is one HUGE undertaking, where every upgrade is an Major Painpoint.
From my POV the CNCF can not say it prevents an vendor-lockin when the opensource-software-vendors create an lockin where you cannot really build the software environment for yourself.
It would be the next logical step to track and tag all Projects if they can be run and BUILT on an air-gapped network.
jm2c

My understanding is that Travis is 100% open source so you could self-host, though no one bothers to do so because it is not competitive with the alternative offerings. If that's not the case, we'd remove the repo_url and show it as closed source.
I think you may be conflating support for an airgapped network with not being able to build for yourself. 100% of the open source projects listed on the landscape are buildable with only open source tools. You're correct that they often assume network access, but all of the software, dependencies, and build tools are available under an open source license.
By contrast, airgapping is an unusual special case, but many important projects support it. For example: https://www.google.com/search?q=kubernetes+airgap


Not an Issue But a Question

Will the script work in uBlock Origin or will I have to install tampermonkey?

User scripts (.js) are needed to be installed into a user script manager, such as TamperMonkey or ViolentMonkey.


About download weights

Why do I download weights again every time I run inference.py ?

You can change what encoders you want to use here.
The default code will download image, video, depth and thermal encoder.
There are some instructions about how to use different branch of LanguageBind if you only use a single modality.


Double render when use Hooks

Current behaviour
When use 'switch render' scene inside of the hooks function - I get two renders (when we just start app)
  const _renderScene = ({ route }) => {
    switch (route.key) {
      case 'login':
        return <FirstRoute />;
      case 'sign_up':
        return <SecondRoute />;
      default:
        return null;
    }
  };

index.js:17  FirstRoute
index.js:28 SecondRoute
index.js:17 FirstRoute
index.js:28 SecondRoute

When switch between tabs - also received two render - every time!
index.js:17 FirstRoute
index.js:28 SecondRoute

Expected behaviour
When use the same code but with this method
  const _renderScene = SceneMap({
    login: FirstRoute,
    sign_up: SecondRoute,
  });

All as expected (when we just start app)
index.js:17 FirstRoute
index.js:28 SecondRoute

Code sample
import React, { useState } from 'react';
import {
  Text,
  View,
  Keyboard,
} from 'react-native';
import EStyleSheet from 'react-native-extended-stylesheet';
import { TabView, TabBar, SceneMap } from 'react-native-tab-view';

import { DEVICE_WIDTH } from 'config/constants';

import styles from './styles';

const FirstRoute = () => {
  console.log('FirstRoute');
  return (
    <View>
      <Text>
        Lorem ipsum dolor sit amet
      </Text>
    </View>
  );
};

const SecondRoute = () => {
  console.log('SecondRoute');
  return (
    <View>
      <Text>
        Lorem ipsum dolor sit amet
      </Text>
    </View>
  );
};

const INITIAL_STATE = {
  index: 0,
  routes: [
    {
      key: 'login',
      title: 'Login',
      icon: '',
      accessibilityLabel: 'Login',
      testID: 'loginTab',
    },
    {
      key: 'sign_up',
      title: 'Register',
      icon: '',
      accessibilityLabel: 'SignIn',
      testID: 'signInTab',
    },
  ],
};

const LoginScreen = () => {
  const [state, setState] = useState(INITIAL_STATE);

  const _renderScene = SceneMap({
    login: FirstRoute,
    sign_up: SecondRoute,
  });

  // const _renderScene = ({ route }) => {
  //   switch (route.key) {
  //     case 'login':
  //       return <FirstRoute />;
  //     case 'sign_up':
  //       return <SecondRoute stings={[]} />;
  //     default:
  //       return null;
  //   }
  // };

  const _handleIndexChange = (index) => {
    Keyboard.dismiss();
    setState({ ...INITIAL_STATE, index });
  };

  const _renderTabBar = props => (
    <TabBar
      {...props}
      activeColor={EStyleSheet.value('$primaryColor')}
      inactiveColor="black"
      style={styles.tabBar}
      indicatorStyle={styles.indicatorStyle}
    />
  );

  return (
    <View style={styles.container}>
      <TabView
        // lazy
        navigationState={state}
        renderScene={_renderScene}
        renderTabBar={_renderTabBar}
        onIndexChange={_handleIndexChange}
        // swipeEnabled={false}
        initialLayout={{
          height: 0,
          width: DEVICE_WIDTH,
        }}
      />
    </View>
  );
};

export default LoginScreen;

Your Environment

software
version

ios or android
both

react-native
0.59.4

react-native-tab-view
^2.2.0

react-native-gesture-handler
kmagiera/react-native-gesture-handler#ff74e0e

react-native-reanimated
^1.0.1

node
v10.15.3

npm or yarn
yarn

I encountered this recently. The problem is that your scenes are re-created every time the Login screen re-rendered.
You should wrap the scene map creating function in a useCallback hook like this:
const _renderScene = useCallback(SceneMap({
    login: FirstRoute,
    sign_up: SecondRoute
}));

Yep, thx
i have solved this also with
const firstRoute = useMemo(() => (<LoginUser />), []);
or
const LoginUser = React.memo(() => (<LoginUser />));

Closing since this seems to be resolved.

Hm, I think it is still an issue, I have tried @Akyna and @tranhoangduong1994  solutions, but the useEffect hook inside on scene components gets called 3 times.

The library doesn't treat function components or hooks in a special way. So if there is different behaviour in your component, there's likely some error in your code. If you believe it's actually a bug in the library, please open an issue with a runnable repro.

@satya164 you are right


Remove GUC for setting migration mode for TestSpatialPoint testfiles

Description
As part of https://github.com/babelfish-for-postgresql/babelfish_extensions/pull/3096, we ignored these files to revisit the migration mode testing.
With this commit we have:

Removed GUC for setting migration mode to multi-db for TestSpatialPoint testfiles.

Authored-by: Anikait Agrawal<EMAIL_ADDRESS>Signed-off-by: Anikait Agrawal<EMAIL_ADDRESS>Check List

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 74.807%

Totals

Change from base Build<PHONE_NUMBER>9:
0.01%

Covered Lines:
46446

Relevant Lines:
62088

💛  - Coveralls


Tweak closure return type annotation to eliminate future limitations for type grammar

Rendered version.

One obvious alternative: "always require braces"? It would make closures more synchronous with function definitions, but is of course an annoying breaking change.

I'm fine with this niko.

Looks good. Always requiring braces would probably be too heavy.

Minor uncontroversial fix. Merged.
Tracking issue.


Added drum-kit

Description
I have added drum-kit website which plays different instruments on click of buttons.
Fixes #24
Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

@siddhi-244 plss add screenshot of output in README file

Ok !


Fixed typo in README.md

fixed typo

Replace this with a summary of what you've changed and why, followed by a list of issues it affects, if any.
Fixes #0000
References #0000
Replaces #0000

[ ] I searched the issue tracker and this hasn't been PRed before.
[ ] My changes are not on the do-not-PR list for this project.
[ ] My commits conform to the git conventions.
[ ] My changes are visual; I've included before and after screenshots.
[ ] I am blindly checking these off.
[ ] Any relevant issues or PRs have been linked to.
[ ] This a draft PR; I need more time to finish it.

Simple typo fix in the README so that the discord link doesn't return a 404.


marshal/unmarshal for overlay multiple subnets

Fixes #592
Signed-off-by: Santhosh Manohar<EMAIL_ADDRESS>

@sanimej One general question on the PR. If a node (where the network was not created) joins the network it will get the network from store. But if a vxlan id got allocated subsequently by another node and it updates the network object in store how does the other node get this information. We don't watch on any network store change. so the other nodes will never get that update

@mrjana When one node allocates the vxlan id for a subnet and the container joins the network other nodes will eventually get the serf join update. When processing that we will check the subnet and try to retrieve the vxlan id for that subnet from the store. If this is the first peer update for a subnet it will trigger the setting up of the required plumbing..

@sanimej got it.  One more thing. You still need to install the route for all the subnets in all the containers. Right?

@mrjana yes. Looks like we need a per sub-net route, all pointing to interface on the overlay network. Otherwise because of the default gateway service inter-subnet packets will end up going to the bridge network. I am looking into this issue..

@sanimej yes. I thought that is the design. the default-gateway will handle the default route, while individual routes are managed by the driver directly.

@mrjana @mavenugo pushed the change to add the static route for all the subnets when the container first joins one of the subnets in the network. PTAL

LGTM.
Lets add proper IT once the dnet UX is enhanced to accept (multiple) subnets.

LGTM


[Bug]: Crash when used with rubidium

Minecraft Version
1.20.1
Forge Version
47.1.0, 47.1.44
Mod Version
<IP_ADDRESS>
Modpack or other Mod
Simpleores2 - <IP_ADDRESS> - https://www.curseforge.com/minecraft/mc-mods/simpleores
SimpleCore API - <IP_ADDRESS> - https://www.curseforge.com/minecraft/mc-mods/simplecore-api
JEI - <IP_ADDRESS> - https://www.curseforge.com/minecraft/mc-mods/jei
Rubidium - 0.7.0a - https://www.curseforge.com/minecraft/mc-mods/rubidium
Describe the Issue
I was trying to play with the rubidium mod and it crashes when I render a copper lava cube from the simpleOres mod. You can see it just typing lava in the creative tab.
Logs
log: https://pastebin.com/UE2XSm91
Do you use any performance-enhancing mods (e.g. OptiFine)?
Rubidium

Also this is the failure log in case it is useful: https://pastebin.com/D4cNu5YM

Thanks for your report.
it looks like this issue: https://github.com/Asek3/Rubidium/issues/577

As a workaround: Don't use Rubidium :)

Fixed in Rubidium 0.7.1


Fix range error for srt format

Fix issue RangeError: Value not in range: 11 when using srt format subtitles

@MuhmdHsn313 Because currently the lib is almost unworkable, so I rollback the srt format's regex back to the previous version. Please help me check this PR.

Dear @thinhnd-nal
Thank you for your PR


Implement Settings Module for Android

@belemaire
Motivation
The pull request implements the Android SettingsModule. The native code utilizes the SharedPreferences to read,write and watch the key value pairs. Appropriate unit tests have been added. js file is attched that tests all the methods implemented , please check the logs to examine the output.

Note implementation doesn't alter the existing iOS API's.
Implemented the methods to

set the values
read the values
watch the keys that changed value, return the key that changed
clear the watch

Test plan

Appropriate Unit tests have been added for the native code
Attaching the sample js file that validates the implemented method
To Run the sample project

Build the Project from source
For the sample project created , replace index.android.js (rename from .txt)
run npm run start -- --root .
run adb reverse tcp:8081 tcp:8081
view android logcat

Logs
01-16 14:35:44.444 19906-19940/com.rnsharedpref I/ReactNativeJS: Watch Key :mapStr
01-16 14:35:44.444 19906-19940/com.rnsharedpref I/ReactNativeJS: Watch Key :mapInt
01-16 14:35:44.444 19906-19940/com.rnsharedpref I/ReactNativeJS: Watch Key :mapFloat
01-16 14:35:44.489 19906-19940/com.rnsharedpref I/ReactNativeJS: Watch Key :mapStr
01-16 14:35:44.490 19906-19940/com.rnsharedpref I/ReactNativeJS: Watch Key :mapFloat
01-16 14:35:44.490 19906-19940/com.rnsharedpref I/ReactNativeJS: Watch Key :mapInt
01-16 14:35:44.517 19906-19940/com.rnsharedpref I/ReactNativeJS: true
01-16 14:35:44.519 19906-19940/com.rnsharedpref I/ReactNativeJS: 789.09
01-16 14:35:44.520 19906-19940/com.rnsharedpref I/ReactNativeJS: 999
01-16 14:35:44.522 19906-19940/com.rnsharedpref I/ReactNativeJS: updateValue
01-16 14:35:44.523 19906-19940/com.rnsharedpref I/ReactNativeJS: 1233489
01-16 14:35:44.528 19906-19940/com.rnsharedpref I/ReactNativeJS: [ 'mapA', 'mapB' ]

On Back Arrow press , when component is unmounted
01-16 14:36:22.557 19906-19940/com.rnsharedpref I/ReactNativeJS: 'clearing : ', 0
01-16 14:36:22.563 19906-19940/com.rnsharedpref I/ReactNativeJS: 'clearing : ', 1

index.android.txt

@mkonicek How is this module used internally at FB? What are the benefits / trade offs of using this instead of AsyncStorage?

Yeah, why do we need something like this in core?

@mkonicek @satya164
Prerequisite
For an existing Android app that contains few/several submodules & these submodules currently read/ write preferences/settings in the SharedPreference. Goal is to introduce/migrate a new/existing submodule as a react native module.
Summary
In the following situation AsyncStorage doesn't provide a way to retrieve the preferences. Assuming the iOS Settings module was implemented for the similar purposes, this Pull request aims to let the existing modularize app's to migrate to new react native modules without breaking business logic that may depend on the <K,V> pairs stored in SharedPreferences.
SharedPreferences is the de-facto way on Android to store Settings for an an application, so it makes sense for it to be the iOS Settings equivalent implementation.
Please let me know your thoughts.

In the following situation AsyncStorage doesn't provide a way to retrieve the preferences.

Why is that?

Assuming the iOS Settings module was implemented for the similar purposes,

We've implemented some things by mistake in the past, especially a long time ago when React Native was just starting. Maybe this was one of the mistakes?

Might be worth implementing this as an 3rd party, as the use case is pretty specific. If you do that we could deprecate the iOS settings module and point to your library.

In the following situation AsyncStorage doesn't provide a way to retrieve the preferences.

Probably makes sense to implement a way to be able to use asyncstorage from native instead of introducing a new module.
I agree with @janicduplessis that this use case is pretty specific, and not lots of people will need it. So it is better for this to be a 3rd party module than in core.

Bumping this thread.
AsyncStorage works fine if working on a 100% react native application. However for integrating with existing native apps (if this is still a use case for react native) this is not a viable solution.
Indeed, a large majority of Android native applications are using SharedPreferences as the de-facto way to store settings/preferences for the application and persist them (as @krunalsshah was mentioning). If integrating some react native apps in these native applications means asking the native developers to forget about SharedPreferences and move all of their preferences/settings in an SQLLite database so that it can be properly accessed if needed from a react native app, that's a no go.
If for pure react-native applications this is not the way to go and AsyncStorage should be favored for storing Settings/Preferences, it would make sense indeed to deprecate the iOS Settings module as leaving it with no Android counterpart does more harm than anything and render it pretty much useless. Problem is that it is a breaking change for users using the iOS Settings module if it suddenly disappear.
Once again, AsyncStorage is nice, and probably should be the way to go for pure react native applications. The Settings class (even on iOS) is more fitted for integration of react native apps into pre-existing native applications that rely on standard platform constructs for storing settings (Settings on iOS, SharedPreferences on Android).
If core mission is not to emphasize integration support into existing large native application codebase but just to support "pure" react native applications, then Settings should be fully deprecated and removed. However if supporting integration into native application is still a thing for react native core and needs to be improved, then it probably make sense to integrate this in core instead of redirecting people to a third party module.
That was my two cents.

I agree this module definitely has some use cases, my question is whether it should be a third party module or not since a large portion of RN apps probably won't use it.

@mkonicek Do you know about internal usage of this module and if it would be worth pulling it out of core?

Problem is that it is a breaking change for users using the iOS Settings module if it suddenly disappear.

We usually put warnings before deprecating something. Also if we deprecate the iOS module, we'll publish it separately or link to a compatible module.

then it probably make sense to integrate this in core instead of redirecting people to a third party module.

It definitely has use cases, but I think most of RN apps won't need it.
Regardless, since FB doesn't use it, nobody would maintain it in core FB team, it´ won't get enough attention, and bugs won't be fixed quickly. Do you really want that?
I think being in core means it should be high quality and stay high quality. I think this module better be a third party one.

If it's deemed high quality from the start after thorough review and well tested beofre merging, it should not require much attention. SharedPreferences has been introduced in API Level 1 and has not much changed since then (only mostly adding string set support in API level 11). Looks to me like a very stable API that won't drastically change any time soon (that being said I'm not a psychic but well ^^).
So yes, if it's working and fully tested, I see no reason to forecast heavy maintenance work for this module. That being said, even if a bug was found by someone, it would mean that someone is actually using it ;) Also are bugs only fixed by FB core team ? It's an open source project so I would assume if someone find a bug and really need it fixed, well they can fix it and contribute back or ping it back to @krunalsshah ;P
That'll be my final arguments, just trying to weigh in a little bit on the "put in core side" :)
I don't really care what gets decided in the end, I think both "parties" have meaningful arguments and our react native app development team can just keep using our module for Android, we'll just make it on parity with iOS so that they can use the same module for both iOS/Android. Will then make this module as an open source third party module.
If not merged in core, +1 on deprecating Settings iOS module in core as it makes no sense to have it then. I don't think a lot of people are using it anyway considering it has no Android counterpart (and using react native to create an app targeting only a single platform defy a bit its purpose).

If it's deemed high quality from the start after thorough review and well tested beofre merging, it should not require much attention.

You can't just test once and forget about it.

That being said, even if a bug was found by someone, it would mean that someone is actually using it ;) Also are bugs only fixed by FB core team ? It's an open source project so I would assume if someone find a bug and really need it fixed, well they can fix it and contribute back or ping it back to @krunalsshah ;P

Well, if we're relying on only the community to update it anyways, what's the point of being in core? Why not just publish as a third party component somewhere like https://github.com/react-native-community/ where it'll get the attention it deserves, and the original author will stay in full control.

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with Canny! Check out its new home: https://react-native.canny.io/feature-requests/p/implement-settings-module-for-android

After further review, it does not look like this PR will be accepted in its current state.


Update pipeline\conf.py

Fix deprecated import, who will stop working in python 3.8.
$ python -Wa manage.py check
C:\Program Files\Python3.7\lib\site-packages\pipeline\conf.py:94: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
  class PipelineSettings(collections.MutableMapping):

Coverage remained the same at 82.133% when pulling f46f8123934e7d43cbbde33aeb8d8962269883db on TheBuky:deprecationcollections into d6b495505c7c01be10e4bcb672747c073ee7d6b3 on jazzband:master.

Let me test #671 first, because that will make this more straightforward on CI instances.

test and it looks good.


MAINT/STY: lint: ignore E501 (line length) by subpackage

Reference issue
Towards gh-19479.
What does this implement/fix?

Ignore E501 (max line length 88 chars) by submodule instead of project wide

Additional information

@mdhaber here are the changes to just lint.toml

The lint check won't actually fail unless you remove one of the exceptions and make a change in one of impacted files. To apply ruff to the whole codebase without having to make spoof changes you can run ruff check . --config='tools/lint.toml'


Replace Unnested Link Templates With One Link Element

Thank you very much for sharing this solution. We took most of it and will include it in our next version.


Move OrderBy after Where

Details of Changes
Performance improvements as OrderBy will operate on a smaller collection.

@meziantou thank you!


some animation that indicates that the dial is about to spin again

via louh

Is this still something that needs to be done? @mstem If so - do we have some reference that shows what this could look like?

Deemed unnecessary unless someone says otherwise


Plugin does not return valid async return value when called with options obj (probably)

This is using gulp-bower 0.0.13, Gulp 4, and node 6.10.0 on Windows 10.
We've got a gulpfile with two different bower tasks - one installs standard lib dependencies based on a bower.json in the root folder (alongside the gulpfile), and the other installs polymer dependencies in a folder within our /scripts directory.
The root bower task we have is just this (we have our tasks separated out as individual commonJS modules, so the format looks a little weird, but I promise they're valid tasks):
return function() {
	return plugins.bower();
};

It runs perfectly fine, and completes with no issues.
This other task, however...
return function() {
        return plugins.bower({
            cwd: './ui/src/elements/ai-common-elements'
        });
};

Gives the following error every time:
[12:54:05] Starting 'bower-elements'...
[12:54:06] Using cwd: ./ui/src/elements/ai-common-elements
[12:54:06] Using bower dir: ./bower_components
[12:54:08] The following tasks did not complete: bower-elements
[12:54:08] Did you forget to signal async completion?

After doing some google searches, I found that many others are having the same issue, but so far I haven't found a solution.  The common thread among all of the reported issues is that in all cases they're being called with an options object as a parameter - either CMD or CWD.  I haven't done any debugging or anything, which is why I qualified the issue title with (Probably), but it seems to be the most likely culprit based on what I've seen thus far.

I should add that the first task (that runs against the bower.json in the root) works as expected even when called with a string param, i.e. return plugins.bower('./bower_components');.  It's only when an object is passed as the param that the 'async completion' errors start showing up.

Okay, now I've had this problem occur when calling with both no params and with just the string param.  This is starting to be a major issue, as none of our bower-related tasks work properly, and thus our build never completes.


model viewer test page crashes Chrome, Edge

Description
When I visit the page (https://modelviewer.dev/examples/tester.html), my screen flashes black and I see this:

My DXDIAG:

Live Demo
https://modelviewer.dev/examples/tester.html
Browser Affected

[x ] Chrome
[x ] Edge
[ ] Firefox
[ ] Helios
[ ] IE
[ ] Safari

OS

[ ] Android
[ ] iOS
[ ] Linux
[ ] MacOS
[x ] Windows

Versions
Live deployed at: https://modelviewer.dev/examples/tester.html

Also happens on my macbook air (~5 years old). Specs:

@stevesan Can you check some other non-chromium browsers like Safari and Firefox? If they work properly, then I'm thinking this may be an offscreenCanvas issue. Also, do you get the same behavior on all of our docs pages? Particularly those with a single model-viewer element vs several?

This seems to happen even with the astronaut in modelviewer.dev. Also with the animation example
However, it's not totally broken: I still see the animations and real time shadows. It's just all the shading is black:

Tried Firefox. Even more severe: my computer locks up a bit, then Firefox doesn't show anything at all.
Confirmed that after restarting Firefox, threeJS examples and Poly do work fine.

@stevesan Can you try again, this time appending ?model-viewer-debug-mode to the end of any URL? That will cause it to spit out any shader compilation errors to the console. If you find any, please paste them here. Also, are you getting a context loss on all browsers on all model-viewer page loads? We surface a context loss event, so you might be able to set a breakpoint there and figure out what's causing that. Your help is much appreciated since I don't have a machine I can repro this on yet.

(followed up offline with debug log)
Another data point: Today, everything started working just fine on my MacBook Air. Interesting..maybe I had too many tabs open? GPU memory issue?

Ah, very interesting. I'm not really sure what happens when you run out of
GPU memory, but my guess is it's not good. We should probably try to find a
way to detect it and fail more gracefully. Meanwhile, please keep me posted
on anything you find where it does repro consistently.
Thanks!
-Emmett
On Thu, Mar 19, 2020 at 8:57 AM Steven An<EMAIL_ADDRESS>wrote:

(followed up offline with debug log)
Another data point: Today, everything started working just fine on my
MacBook Air. Interesting..maybe I had too many tabs open? GPU memory issue?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/model-viewer/issues/1089#issuecomment-601260336,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMS2LCI6ECAQ4OQII533LDRII6GTANCNFSM4LNSK35A
.

OK this was determined to be caused by the PMREMGenerator in threeJS. A PR is in progress: https://github.com/mrdoob/three.js/pull/18935


[flink] Support remove-orphan-files action

Purpose

Linked issue: close #1571

Tests

RemoveOrphanFilesActionITCase
API and Format

Documentation
Understand Files - Remove Orphan Files

Some codes have referenced #2223


Revised INSTALL script, fix #1394.

Fixes issue #1394
Brief summary of changes

Removed duplicated code.
Fixed problem with minimum version checking.
Fixed problem with user/group retrieval.

Testing I've completed

Tested on Ubuntu and Debian.

CHANGELOG.md

No need to update because we don't officially support Linux.

@AlbertoCasasOrtiz Trying to use the script to fix an issue on the sprint I ran into these 2 problems:

Requiring Ninja seems too strict especially that Ninja likely ends up using Make underneath
The swig built fails in CMake because of libpcre.so.1 is not found, maybe it needs to be installed first.

@aymanhab I have tested the Linux script in a clean Ubuntu 22.04 and it works for me. libpcre3 and libpcre3-dev are installed in line Line 67. What OS version are you using? Maybe I missed something when testing it.
Regarding ninja, I agree. Should we go back to cmake?

I'm using 22.04.1 LTS according to lsb_release -a.
I'd use ninja if available otherwise use make. Goal is that internal dev. builds and ci builds are identical so issues/can be detected as early as possible. I'll look into build log to find out about pcre issues

@aymanhab I think we can merge this PR since it is related to the file
https://github.com/opensim-org/opensim-gui/blob/c60b07fa6ed992e2221af2050daac74d67d6e62c/Gui/opensim/installer_files/Linux/INSTALL
and not to the build scripts. I tested this on Ubuntu and Debian and it works.


Steempy Addkey

Learning my way around and getting the following error for the steem conductor Wallet installation
https://steemit.com/steem/@furion/introducing-conductor-a-simple-steem-witness-toolkit
root@steemWitness123:~# steempy addkey
Traceback (most recent call last):
File "/usr/local/bin/steempy", line 9, in
load_entry_point('steem==0.18.93', 'console_scripts', 'steempy')()
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 542, in                                                                                load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 2569, in                                                                                load_entry_point
return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 2229, in                                                                                load
return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 2235, in                                                                                resolve
module = import(self.module_name, fromlist=['name'], level=0)
File "/usr/local/lib/python3.5/dist-packages/steem/init.py", line 2, in
from .steem import Steem
File "/usr/local/lib/python3.5/dist-packages/steem/steem.py", line 1, in
from .commit import Commit
File "/usr/local/lib/python3.5/dist-packages/steem/commit.py", line 20, in
from .account import Account
File "/usr/local/lib/python3.5/dist-packages/steem/account.py", line 8, in
from funcy.simple_funcs import rpartial
ImportError: No module named 'funcy.simple_funcs'
root@steemWitness1223:~#

dupe of #50


Sync eng/common directory with azure-sdk-tools for PR 899

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/899  See eng/common workflow

/check-enforcer override


Backport 0.1.0 release patches

Backports the patches from the release branch for the 0.1.0 release to the master branch.

bors merge


Where is the code?

Hey, Where's the implementation code and project?

Never mind I saw the Coming Soon™

I'd suggest to keep this issue opened as it is indeed not yet available. I imagine others, like me, would have the same question so might avoid duplication.


Tracking issue: Create validator for values hashed by SHA-3 384 algorithm

Original issue: https://github.com/RedHatInsights/insights-data-schemas/issues/65

Implemented in https://github.com/RedHatInsights/insights-data-schemas/pull/71

Implemented in https://github.com/RedHatInsights/insights-data-schemas/pull/71


Add "Run on Replit" badge

Glitch is already there, but Replit is another important business in the same market. And some individuals may prefer Replit because of the additional resources it provides, as well as the ease with which it can be set up and a thousand other features I could list. @shaydewael

I don't know where you got your information but they in fact CAN run v13 discord bots, I run a few bots on there. A few months ago, they couldn't because the wrong node version was installed but they've updated the node version on their servers.

@hackermondev I'm not against having Replit as another option (I was originally using it when writing the guide because of its TypeScript support), but I'll need to test it and add instructions about getting the interactions endpoint URL. Stay tuned!

@KK-Designs I don't know where you got your information but they in fact CAN run v13 discord bots, I run a few bots on there. A few months ago, they couldn't because the wrong node version was installed but they've updated the node version on their servers.

They can?? I didn't know that lol

Sorry this took longer than anticipated 😓
But I updated this project (I needed to do a couple of other updates and custom configs, and wanted to change some Replit-specific project stuff, so ended up making a different PR) and the Getting Started guide


Add autocomplete to add members to a group by name

https://user-images.githubusercontent.com/21087624/173921681-d248cd1a-a822-4971-9665-d3bae8fa1393.mov

Hi @mgorkove,
Thanks for working on this!
Just a few smaller nits, the linter had some feedback, and then one main comment is -
The query service can throw for the cases where the user has either no profile or has not consented to sharing their data.
This has the following implications -

need to try/catch
need to still accommodate adding users by member ids directly

Let me know if the comments aren't sufficient and you have more questions!

@simonkernel do we really need to accommodate still adding by member ids directly? Wasn't the whole point of the autocomplete to be able to get rid of that?

Hi @mgorkove,
Yes we do need adding members by id. Also, we actually also need to display the member id so members with the same name can be distinguished. We can just add it in parentheses ex Rory (1234567).
Thanks,
Simon


Bump dependencies

"@spotify/prettier-config": "^15.0.0"

yarn install
yarn upgrade

Tested in there https://github.com/htc-kubecon-na-2024/backstage/commit/9f995e9424703df9fce55371a92c4feed575e213.

Ready for your review, thanks!


Improve Getting Started doc

User feedback on Getting Started doc:

I found it difficult to follow the “Getting Started” doc. It does a good job introducing TypeSpec concepts and builds upon the previous section(s) but it didn’t get me to running code like I was expecting.
For example, it didn’t include any instructions on creating the TypeSpec project, compiling the project, or using emitters to produce OpenAPI output.
I ended up using a combination of the playground, GitHub repo, and docs to get up and running with my first project.
Suggestion: E2E doc on getting started, building a simple TypeSpec API, compiling, and emitting to OpenAPIv3

est: 5


Completion Handler of FirebaseRemoteConfig fetch is never called in Simulator

[REQUIRED] Step 1: Describe your environment

Xcode version: 12.2
Firebase SDK version: 7.6
Installation method: Zip file
Firebase Component: RemoteConfig

[REQUIRED] Step 2: Describe the problem
Remote config fetch completion is never called. Console logs sometimes indicate an SSL connection issue.
Steps to reproduce:
The app is launched in the simulator and after FirebaseApp.configure() is called a call to fetch fails never results in the completion being executed  This is first time seeing this during development but during CI we often have seen similar symptoms in CI but not been able to understand cause.
The app was likely deleted from the simulator and reinstalled prior to this occurring. Have not reset the device yet which I suspect would fix the issue. Other simulators on same computer are working.
The following is what often shows up in console
2021-04-21 21:24:21.250831-0400 ShopThing[75574:2195780] Connection 1: received failure notification
2021-04-21 21:24:21.251269-0400 ShopThing[75574:2195780] Connection 1: failed to connect 3:-9816, reason -1
2021-04-21 21:24:21.251649-0400 ShopThing[75574:2195780] Connection 1: encountered error(3:-9816)
2021-04-21 21:24:21.260031-0400 ShopThing[75574:2195780] Task <22DC5FA7-1A41-4730-97CD-14E2A78D48AF>.<1> HTTP load failed, 0/0 bytes (error code: -1200 [3:-9816])
2021-04-21 21:24:21.267550-0400 ShopThing[75574:2195780] Task <22DC5FA7-1A41-4730-97CD-14E2A78D48AF>.<1> finished with error [-1200] Error Domain=NSURLErrorDomain Code=-1200 "An SSL error has occurred and a secure connection to the server cannot be made." UserInfo={NSLocalizedRecoverySuggestion=Would you like to connect to the server anyway?, _kCFStreamErrorDomainKey=3, NSErrorPeerCertificateChainKey=(
    "<cert(0x7fc29281fc00) s: upload.video.google.com i: GTS CA 1O1>",
    "<cert(0x7fc29281a200) s: GTS CA 1O1 i: GlobalSign>"
), NSErrorClientCertificateStateKey=0, NSErrorFailingURLKey=https://device-provisioning.googleapis.com/checkin, NSErrorFailingURLStringKey=https://device-provisioning.googleapis.com/checkin, NSUnderlyingError=0x60000050d740 {Error Domain=kCFErrorDomainCFNetwork Code=-1200 "(null)" UserInfo={_kCFStreamPropertySSLClientCertificateState=0, kCFStreamPropertySSLPeerTrust=<SecTrustRef: 0x60000399c3f0>, _kCFNetworkCFStreamSSLErrorOriginalValue=-9816, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9816, kCFStreamPropertySSLPeerCertificates=(
    "<cert(0x7fc29281fc00) s: upload.video.google.com i: GTS CA 1O1>",
    "<cert(0x7fc29281a200) s: GTS CA 1O1 i: GlobalSign>"
)}}, _NSURLErrorRelatedURLSessionTaskErrorKey=(
    "LocalDataTask <22DC5FA7-1A41-4730-97CD-14E2A78D48AF>.<1>"
), _kCFStreamErrorCodeKey=-9816, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <22DC5FA7-1A41-4730-97CD-14E2A78D48AF>.<1>, NSURLErrorFailingURLPeerTrustErrorKey=<SecTrustRef: 0x60000399c3f0>, NSLocalizedDescription=An SSL error has occurred and a secure connection to the server cannot be made.}

Relevant Code:
FirebaseRemoteConfig.RemoteConfig.remoteConfig().fetch(withExpirationDuration: 60) { [weak self] status, error in
    // code here is never reached
}

Hi @ryanmcdonald77, I've tried to reproduce the issue, but I was able to successfully call the fetch(). With this, did you use the activate() after calling the fetch()?


People img card radius

@fykaa Please add hacktoberfest-accepted label
Description:
Added border radius and border colour for perople imgs card in footer
Issue: #8
Screenshot:

Hi @jsvigneshkanna , This issue wasn't recommended, We're going to change the sites team section. Hence closing.


Added OnNewTag, allows to react to Return key in TagTextField, fixed fatal problem with landscape mode

Added possibility to trigger action when tapped on tag.
Fixed an issue with geometry reader in landscape mode.

Hi @Vithanco
Thank you for the PR.
To help me understand, why is the geometry reader thing needed? What are the problems in landscape? Please clarify, since I don't want to use GeometryReader unless explicitly needed.
In the tag list, the idea is that you can add everything you need to the view builder, so adding an additional action parameter should not be necessary.
The text field also should not need the action parameter, since you can just add the onSubmit to the tag text view. You do not need to specify that within that view.

you are absolutely right, Daniel! I guess the way how you can use SwiftUI are still not internalised on my side. I removed tap gesture and on submit. Thanks!
I am not a fan of geometry reader neither. But please notice that I didn't introduce it, I only refactored your code. The problem that your code has is that it lead to a program abortion, and the updated version seems to work (and hopefully is better to read).

this fixes issue generated here https://github.com/danielsaidi/TagKit/issues/4

Sorry for completely dropping the ball on this @Vithanco!
If this solves the problem with Swift 6, I will give it a try, then merge it and re-enable Swift 6 👍

Sorry for completely dropping the ball on this @Vithanco!
If this solves the problem with Swift 6, I will give it a try, then merge it and re-enable Swift 6 👍

sorry i used his repo directly which didnt have swift 6 so maybe thats why it worked. Ill check his commit with swift 6 and let you know!

Sorry for completely dropping the ball on this @Vithanco!
If this solves the problem with Swift 6, I will give it a try, then merge it and re-enable Swift 6 👍

sorry i used his repo directly which didnt have swift 6 so maybe thats why it worked. Ill check his commit with swift 6 and let you know!

Thank you!

sorry i used his repo directly which didnt have swift 6 so maybe thats why it worked. Ill check his commit with swift 6 and let you know!

Thank you!

this pr doesnt fix that error.


cannot compile code_ad in lab_sea setup.

I can successfully test the lab_sea adjoint setup using testreport
./testreport -ad -t lab_sea

But if I try to compile using the standard method,
../../../tools/genmake2 -mods=../code_ad -of=../../../tools/build_options/linux_amd64_gfortran

The adjoint code does not compile after coming back from taf.
the_model_main.o: In function `the_model_main_':
the_model_main.f:(.text+0x14d): undefined reference to `mdthe_main_loop_'
collect2: ld returned 1 exit status
make[1]: *** [mitgcmuv_ad] Error 1
make[1]: Leaving directory `/home/ifenty/MITgcm/verification/lab_sea/build'
make: *** [ad_exe_target] Error 2

Ou Wang @owang01 pointed out that testreport uses a different default adjoint options file (the divided adjoint option?) that includes the -pure flag.  If I hack Makefile and insert the -pure flag in the make ad option, then the adjoint code compiles.  Here are the original ad_taf_flags:
AD_TAF_FLAGS         = -server fastopt.net -f77 -reverse -i4 -r4 -intrinsic system,flush -l taf_ad.log -toplevel

with -pure added:
AD_TAF_FLAGS         = -server fastopt.net -f77 -reverse -pure -i4 -r4 -intrinsic system,flush -l taf_ad.log -toplevel

This problem was verified on two different machines by myself and Ou Wang @owang01.

I have the impression that there is a simple explanation for this, but it needs to be confirmed:
When you run testreport, you run the genmake2 command in "lab_sea/build" where a "genmake_local" file
is found. If you try the "standard" method in the same "lab_sea/build" dir with the same genmake_local file
I guess it will work the same way, with no error, as it does for me (just checked). However, if you try to
compile in an other dir where there is no (or not the same) genmake_local file, then it will miss a couple of specific AD flag and will not finish the compilation normally.
There has been some efforts in documenting this "genmake_local" feature, both in term of what
genmake2 print as it run:
a) if it's there:
===  Processing options files and arguments  ===
getting local config information:  using genmake_local
b) or when it's not:
===  Processing options files and arguments  ===
getting local config information:  none found
and also in the manual (see section 3.5.2).
but suggestions on how to improve this are welcomed.

I think @jm-c is right. The file genmake_local (attached below) in the build directory of the lab_sea experiment explicitly uses adjoint_diva that has the -pure flag. I did a test by removing the genmake_local file and then used testreport to recompile. It generates the same error message as @ifenty described, since the adjoint option file adjoint_default that does not have the -pure flag is used.
#!/bin/bash
#-- This is the local options file for the "new" version of genmake
AD_OPTFILE='../../../tools/adjoint_options/adjoint_diva'
#TAF_EXTRA='-version 2.9.3'

@jm-c,
Before I can think of any suggestions can you explain why pointing to adjoint_diva is required for this setup?  What is the use of the -pure flag?   The staf doc isn't very helpful.  Why do we need to use -pure for the lab-sea setup and not for other verification setups, for example  1D_ocean_ice_column?  @owang01 said that for the ecco llc90 he doesn't think he uses -pure.
A long time ago (!) one didn't need a special adjont_diva AD_OPTILE to compile the lab_sea code_ad directory in a non default build directory.

I guess this has changed when lab_sea has been modified to test the divided adjoint (in 2013), this is the commit: 2ea80bbf4e14b77183bf64ecfdcf2f569854443a (I don't know how to create link here),
and for that you need the mdthe_main_loop which will only be generated with -pure option (it says so in the documentation that I have, but I agree that the name of this flag does not imply this).

Martin is right: A while back we decided to use this verification to test the divided adjoint.
adjoint_diva isn't required for this setup, but has been chosen to be used for this setup.
Choosing the divided adjoint requires the TAF flag -pure.
That has nothing to do of whether that flag is needed or not in conjunction with ECCO (it is needed also for ECCO if you wish to use DIVA with the ECCO setup).
The "-pure" option is described in the manual, section 5.5.2:
http://mitgcm.org/public/sealion/online_documents/node191.html
and there is a brief description of why mdthe_main_loop is generated for this case.
p.

On Apr 3, 2019, at 10:34 AM, Martin Losch<EMAIL_ADDRESS>wrote:
I guess this has changed when lab_sea has been modified to test the divided adjoint (in 2013), this is the commit: 2ea80bb (I don't know how to create link here),
and for that you need the mdthe_main_loop which will only be generated with -pure option (it says so in the documentation that I have, but I agree that the name of this flag does not imply this).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Short answer is that lab_sea is (the only experiment) using divided adjoint (DIVA).
If you need more details, you will need to ask @heimbach (or someone familiar with DIVA)
since I don't know much there.
On Wed, Apr 03, 2019 at 07:42:32AM -0700, Ian Fenty wrote:

@jm-c,
Before I can think of any suggestions can you explain why pointing to adjoint_diva is required for this setup?  What is the use of the -pure flag?   The staf doc isn't very helpful.  Why do we need to use -pure for the lab-sea setup and not for other verification setups, for example  1D_ocean_ice_column?  @owang01 said that for the ecco llc90 he doesn't think he uses -pure.
A long time ago (!) one didn't need a special adjont_diva AD_OPTILE to compile the lab_sea code_ad directory in a non default build directory.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/MITgcm/MITgcm/issues/232#issuecomment-479519805

OK.  I updated the README of lab sea verif. experiment since this whole DIVA thing was not mentioned there or in the MITgcm github docs.
I can understand why a DIVA setup would want to use -pure


Fix flow by allowing optional chaining

Summary
Turns out the optional chaining PR (#2330) also broke flow. We should run a flow check automatically before we build, not just strip the types.
Test Plan
flow .

+1


[question] how to get code silently just using username and password(without ui and redirect)?

how to get code silently just use username and password(without ui and redirect)?

@radiorz see: https://casdoor.org/docs/basic/public-api#4-by-username-and-password or see what HTTP APIs are called by web UI in Chrome F12 debug tool.


Top of screen cut off and mouse Y position off (Windows 10, Intel drivers regression)

Windows 10 PRO
Godot 2.1.3 & Latest 3.x
Intel 620 graphics card
When opening a project the top of the screen is cut off. You can't see the top bar where Scene, Import, Tools, etc are.
Mouse y position is off by like half a button width. This happens in the project list and when you open a project. You have to move the mouse below the buttons to click on them.
I also tried running in self contained mode by create ._sc_

Update
It appears rolling back to a previous video driver made the problem go away
Good: Intel driver version <IP_ADDRESS>65 12/10/2016
Bad: Intel driver version <IP_ADDRESS>39 3/22/2017

Any thoughts on where I could start looking to track down this bug?
Looking at release notes for the driver it doesn't say anything was really changed except for a fix when plugging into a dock I believe. I did notice this newer drive has the Vulkan API. Not sure if that is relevant or not.

Well, to me it seems like the whole picture somehow gets scaled over both the window and its titlebar, instead of being just constrained to the window.
So, it might be windows-related somehow, though I'm not sure how exactly.
Proof:

(done with GIMP using the image in the first comment)

I have the same issue with the latest version of the Intel drivers on my XPS 13 9360. Is there any way to fix this on the application end. Using the old drivers is buggy and causes issues on my laptop.

Unless we can get Intel to fix their drivers, we'll have to find a workaround so that Godot 3.0 isn't broken for half the Windows 10 users.

On my XPS 13 9360 updated yesterday with latest (<IP_ADDRESS>64) Intel drivers i have the same issue.

I installed the latest version of the Intel drivers and it seems fine now. I had to manually install the drivers via the INF file because of Dell's restrictions, but it works.

@fkossyvas According to @Unholypanda Intel fixed the drivers, any idea if this works for you?

I don't know what @Unholypanda means by latest. The latest i found by Dell was the <IP_ADDRESS>64 version (for my Windows 7, the default OS for this notebook is Windows 10). At the Intel site i've only found for the HD 520 graphics card these  updates which means that what i have tied to install was the latest one but i doesn't work ok with Godot that is why i had to downgrade it to the previous one.

I can confirm as well. I just installed the latest (15.4602.4729 driver version  is <IP_ADDRESS>29) Generic Video Drivers from intels website manually and it seems to have resolved the issue. This is on my Yoga 2 from Lenovo with an intel 620.
@fkossyvas If you are installing the latest version from Intels website, perhaps its not fixed for the 520 ?
im closing this as its fixed for me and in my opinion isn't a Godot Issue.

@willt : from what i see you are right : Intel has't fixed it for the 520. I've installed all the latest upgrades for my notebook (including Bios) but i had to downgrade the graphics update (again) to make Godot work.
I agree that this is not a Godot bug (but an Intel one) and should have been closed but the existence of this (closed) issue is helpful for others with the same problem.

For what it's worth Dell released a driver update on August 14th that fixed it for me. Check you drivers on the website and see if they have an updated version for you card. If there isn't an Intel update though I doubt that dell will have drivers yet.

Why this issue is flagged as closed?

What is your card? Have you checked with the Dell website that your driver is indeed the newest (Windows loves to misrepresent 'newest')

@Zireael07 Dell laptop with intel iGPU. Windows 8.1, with latest updates (including latest drivers. Still having this issue.


Indicate logged in

Solves issue: https://github.com/opensim-org/opensim-viewer/issues/138

@aymanhab This PR should take care of #138.
If the user is not logged in, Share is always disabled (removed from GUI).
If the user is logged in, Share is only enabled if the file is on S3, and never if it is just a local gltf file.
If you upload a local gltf file, and then open a built-in model (or any model with a link to S3), share should be visible again.


PMM crashes only when analyzing series

Version Number
1.18.3
What branch are you on?
master
Describe the Bug
Once PMM starts processing the first show, it freezes for a minute then the container exists. This is only for analyzing series or anime series. It works perfectly for movies and anime movies.
Relevant Collection/Overlay/Playlist Definition
No response
Logs
https://gist.github.com/ShanaryS/10048b52d6b979560a482336c3d4d967

Can you run with --trace at the end of your Run Command and provide those logs?
Generally speaking, if PMM exits iself due to an issue, you will see an error message and the normal end-run summary. This seems like something else is killing it.
I see that your host only has 2GB of RAM, are you able to increase that and see if it helps?

I used the env variable PMM_TRACE=True so it was on in the logs.
The RAM was the issue. I'm using docker on windows and WSL2 had it's ram limited to 2GB. I upped it to 16GB (32GB system) and it now works. RAM went to 3GB where it froze above and went as high as 9.1GB later on when applying overlays. This is the WSL2 total memory, docker strangely says the specific container only uses 2.5GB but nothing else is running.
Might be a good idea to add a note about RAM requirements in the setup so others can avoid this in the future.

Thanks for confirming - we will look to add some guidance around this in the docs.


Tap Postgres

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/166
Originally created by @iroussos on 2018-11-19 16:15:08

Make sure that the existing tap-postgres is working properly with the Databases we fetch data from:

[x] GitLab Profiler DB
[x] Pings (Customer, License, Version)
[ ] Domains
[x] CI Stats

If updates are required, try to make it work by updating tap-postgres.
If everything else fails, build a new Tap for Postgres

View 12 previous comments from the original issue on GitLab


[Performance] Refactor withWindowDimensions to drop event subscription in each instance.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

ISSUE
withWindowDimensions subscribe to Dimension change directly in each instance. There is no apparent issue with this. But It is really not necessary and delays react updates. This component will cause a series change in React components instead they can be updated at once.
There is also a performance drop due to having multiple subscriptions. I suggest we use Context-based state sharing for this. This is a new pattern for our app. But we already using with some vendor Libs already.
There are some good points by @jsamr  https://github.com/Expensify/Expensify.cash/issues/4106#issuecomment-881498413 & https://github.com/Expensify/Expensify.cash/issues/4106#issuecomment-881609891. A little more context https://github.com/Expensify/Expensify.cash/issues/4106#issuecomment-881481909. There was an old case where the app crashed due to this https://github.com/Expensify/Expensify.cash/issues/2902.
I insist to do this change as if there is a way to improve this code and it is giving an advantage without too much overhead then we should do this.
Expected Result:
Describe what you think should've happened
Remove multiple Dimension change subscriptions.
Platform:
Where is this issue occurring?
Web :heavy_check_mark:
iOS :heavy_check_mark:
Android :heavy_check_mark:
Desktop App :heavy_check_mark:
Mobile Web :heavy_check_mark:
Version Number: latest
View all open jobs on Upwork
cc: @marcaaron

Triggered auto assignment to @sakluger (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

Thanks @parasharrajat this sounds pretty similar to the issue opened here by @kidroca.
Are you proposing something different?

There is also a performance drop due to having multiple subscriptions.

What are the impacts? Is it something we can benchmark and prove? And is it something we should prioritize?

Also is there some specific experience metric we can tie this to and apply it as a solution... e.g. does it make chat switching faster? Does it make the app boot faster? Does it make report actions load faster? These are the areas we are prioritizing. So it would be nice see this presented as a solution to one of our open issues.

ok. I will try to match it with something but I guess we can close it and continue there if there is an existing issue. Please feel free to close it if you agree.

Let me know how it goes. I've put a Planning label on this for now and raised some discussion in Slack. I think a good issue title should be something like:
[Performance] Improve [insert actual feature] time by refactoring withWindowDimensions

Actually going to close this. If you have some new metrics or benchmarks feel free to reopen the other issue.


[Transmission] Usability improvements

Description
Use the password type for a field storing a password.
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@FezVrasta Ready for another look. I've bumped dependencies in order to fix a bunch of type-checking issues, the Raycast API is a bit more flexible on the types for example. I've made some UI tweaks as well, open to any feedback you have.

Note with the above that the partial markdown field is necessary for rendering the progress SVG (nice one with that by the way!), and the divider can't be set at a custom height.

And here, I've just pulled the instructions out of the placeholder so that the placeholders are more accurate. Alternatively the descriptions could be put in the info fields, but that requires a hover to reveal the details.

Strange, it was failing the CI check.
Is it just that this package was using an old version that was not cross platform?

@pernielsentikaer could you advise please?

Hey @FezVrasta @danpalmer
We had to take a closer look at this issue - apparently, our check on RayCLI was a bit too aggressive, which was the main reason for the react DOM failing.
We are deploying a new CLI version right now and we would like to test it against your changes and make it work with the newer react-dom dependency.
Do you mind "breaking it" agaig using the newest react-dom as it was originally, so we can make sure it works properly? :) Thanks in advance

Hey @FezVrasta @danpalmer
We had to take a closer look at this issue - apparently, our check on RayCLI was too aggressive, which was the main reason for the react DOM failing. Sorry for the inconvenience.
We just deployed a new CLI version right now and we would like to test it against your changes and make it work with the newer react-dom dependency.
You can see here it worked for the one that was failing.
Do you mind “breaking it” again and use the newest react-dom as originally, so we can ensure our fix works properly? :)
Thanks in advance

@grzegorzkrukowski I just tried this and despite bumping versions for the Raycast CLI it didn't work, and actually failed earlier in the flow as I could no longer build successfully locally.

I see that checks are passing correctly now - what type of error do you get locally ?

I see that checks are passing correctly now - what type of error do you get locally ?

The checks are passing correctly because I backed out the change again. Locally I got the same error as I was seeing in CI before:

build failed (node_modules/react-dom/server.js:3:25 module.exports = require('./server.node');): native bindings (e.g., .node files) are not supported because they are neither cross-platform nor cross-architecture; for example, native bindings built on a M1 mac would not work on an Intel mac

@danpalmer I think it may be related to the fact that you are using the CLI embedded into Raycast API.
The fix will be shipped to the official CLI on the next release, meanwhile, you can try downloading the version with the fix that is used on CI from here.
If you don't want to mess up with this - just push the locally breaking version to the CI - and we can iterate on it if something will still be wrong.

@grzegorzkrukowski re-pushed the changes restoring react-dom.


[muti-line-strings] Fixed regex, it did not parse multiple multi-line-st...

I've fixed the regex, cause it did not parse multiple strings correctly, also modified the test.
stringA = """
content here
"""

stringB = """
content here
"""

stringA resulted in
content here
"""

stringB = """
content here

fwiw, although this is closed, multiline strings are part of the toml spec now: https://github.com/toml-lang/toml#string

@shadowmint That's correct; support was introduced in 8f230bbb373e6ad5716d8b4bdcfd3f4046dceb76 and is works in v2.1.1+.


"Burdeni" and "Tecuci" are listed in the drop-down menu

Description:
"Burdeni" and "Tecuci" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Burdeni" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Burdeni, TELEORMAN (Balaci)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Tecuci" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Tecuci, TELEORMAN (Balaci)".


Add support for incremental testing

Original idea from @olafurpg.
I want to add support for incremental testing. I'd like the following to happen:

I run ~incrementalTest.
My project and their tests get compiled. All the tests are executed.
I do a change in a source file.
Zinc compiles incrementally that change for both the project and the tests.
Only the test files affected by that change are run.

This is an important feature for fast edit/compile/test workflows. We only run tests that are in some way affected by some change.  Why run the rest?
To implement this feature, we need Zinc to expose the recompiled test classes to the build tool. We can provide their fully qualified names and use them as the parameter of testOnly. However, not all those arguments will be runnable (you can recompile top-level classes in a test file that just provide helpers). Therefore, we'll need a way to filter out those who are not.
Current test frameworks detect runnable tests via reflection. If we want Zinc to know what it's runnable and what it's not, we can:

Look into the inherited classes of a given top-level class and check it against common FQN of Scalatest, Specs2, uTest, etc. An example would be org.scalatest.Suite. The drawback of this approach is that we check for concrete FQNs, so if there's a new testing suite we'll need to add it and ship it in the next release. This is not something that happens every day, so we could bear with it.
Make the build tool provide the subclasses that are runnable via IncOptions. Build tools already know what testing framework they're using (or they provide ways to find it out), so they can pass in those expected FQN to Zinc and Zinc will match super classes of any top-level class against it. We can get this information from API where the all the super classes (including transitive) are accessible.

This information can then be spit into a TestAnalysis file that would expose the runnable files that can be executed with testOnly. The build tool will read it and run them.
I lean towards the second option since it's Scala testing frameworks agnostic. Making Zinc check for concrete frameworks could get out of hand sooner than expected.
WDYT @smarter @romanowski @dwijnand @eed3si9n ?

What you're describing sounds like testQuick - http://www.scala-sbt.org/0.13/docs/Testing.html#testQuick

See also https://github.com/sbt/sbt/issues/2048

testQuick only works at the file level by detecting changes in the file stamps. My following example shows why it doesn't work:

Run ~compilerBridge/testQuick
Add a whitespace in a bridge source file and save.

testQuick runs all the testing suite when it shouldn't run any test at all. Logs here:
Have a look at it:
> ~compilerBridge/testQuick
[info] Formatting 6 Scala sources {file:/data/rw/code/scala/zinc/}compilerBridge(test) ...
[info] Formatting 1 Scala source {file:/data/rw/code/scala/zinc/}compilerInterface(test) ...
[info] Formatting 3 Scala sources {file:/data/rw/code/scala/zinc/}zincClassfile(test) ...
[info] Formatting 2 Scala sources {file:/data/rw/code/scala/zinc/}zincApiInfo(test) ...
[info] Compiling 104 Java sources to /data/rw/code/scala/zinc/internal/compiler-interface/target/classes...
[warn] /data/rw/code/scala/zinc/internal/compiler-interface/src/main/java/xsbti/compile/ScalaInstance.java:35: deprecated item is not annotated with @Deprecated
[warn] 	File libraryJar();
[warn] /data/rw/code/scala/zinc/internal/compiler-interface/src/main/java/xsbti/compile/ScalaInstance.java:38: deprecated item is not annotated with @Deprecated
[warn] 	File compilerJar();
[warn] /data/rw/code/scala/zinc/internal/compiler-interface/src/main/java/xsbti/compile/ScalaInstance.java:41: deprecated item is not annotated with @Deprecated
[warn] 	File[] otherJars();
[info] Writing version information to /data/rw/code/scala/zinc/internal/compiler-interface/target/resource_managed/incrementalcompiler.version.properties :
[info] version=1.0.0-X8-SNAPSHOT
[info] timestamp=20170308T224844
[info] Packaging /data/rw/code/scala/zinc/internal/compiler-interface/target/compiler-interface-1.0.0-X8-SNAPSHOT.jar ...
[info] Done packaging.
[info] Compiling 17 Scala sources to /data/rw/code/scala/zinc/internal/compiler-bridge/target/scala-2.12/classes...
[info] Compiling 3 Scala sources to /data/rw/code/scala/zinc/internal/zinc-classfile/target/scala-2.12/classes...
[info] Compiling 1 Scala source to /data/rw/code/scala/zinc/internal/compiler-interface/target/test-classes...
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/Analyzer.scala:10: Unused import
[warn] import scala.tools.nsc.{ io, plugins, symtab, Global, Phase }
[warn]                                       ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/Analyzer.scala:10: Unused import
[warn] import scala.tools.nsc.{ io, plugins, symtab, Global, Phase }
[warn]                                               ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/Analyzer.scala:11: Unused import
[warn] import io.{ AbstractFile, PlainFile, ZipArchive }
[warn]             ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/Analyzer.scala:11: Unused import
[warn] import io.{ AbstractFile, PlainFile, ZipArchive }
[warn]                           ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/Analyzer.scala:11: Unused import
[warn] import io.{ AbstractFile, PlainFile, ZipArchive }
[warn]                                      ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/Analyzer.scala:12: Unused import
[warn] import plugins.{ Plugin, PluginComponent }
[warn]                  ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/Analyzer.scala:12: Unused import
[warn] import plugins.{ Plugin, PluginComponent }
[warn]                          ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/Analyzer.scala:13: Unused import
[warn] import scala.collection.mutable.{ HashMap, HashSet, Map, Set }
[warn]                                   ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/Analyzer.scala:13: Unused import
[warn] import scala.collection.mutable.{ HashMap, HashSet, Map, Set }
[warn]                                            ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/Analyzer.scala:13: Unused import
[warn] import scala.collection.mutable.{ HashMap, HashSet, Map, Set }
[warn]                                                     ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/Analyzer.scala:13: Unused import
[warn] import scala.collection.mutable.{ HashMap, HashSet, Map, Set }
[warn]                                                          ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/Analyzer.scala:15: Unused import
[warn] import java.io.File
[warn]                ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/Analyzer.scala:16: Unused import
[warn] import java.util.zip.ZipFile
[warn]                      ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/Analyzer.scala:17: Unused import
[warn] import xsbti.AnalysisCallback
[warn]              ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/Command.scala:11: Unused import
[warn] import Compat._
[warn]               ^
[warn] /data/rw/code/scala/zinc/internal/zinc-classfile/src/main/scala/sbt/internal/inc/classfile/Analyze.scala:17: Unused import
[warn] import java.lang.annotation.Annotation
[warn]                             ^
[warn] /data/rw/code/scala/zinc/internal/zinc-classfile/src/main/scala/sbt/internal/inc/classfile/Analyze.scala:220: private method in object Analyze is never used
[warn]   private def isTopLevel(classFile: ClassFile) = classFile.className.indexOf('$') < 0
[warn]               ^
[warn] /data/rw/code/scala/zinc/internal/zinc-classfile/src/main/scala/sbt/internal/inc/classfile/Analyze.scala:224: private method in object Analyze is never used
[warn]   private def isMain(method: Method): Boolean =
[warn]               ^
[warn] /data/rw/code/scala/zinc/internal/zinc-classfile/src/main/scala/sbt/internal/inc/classfile/ClassFile.scala:14: Unused import
[warn] import java.io.File
[warn]                ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/CompilerInterface.scala:13: Unused import
[warn] import scala.tools.nsc.util.ClassPath
[warn]                             ^
[warn] /data/rw/code/scala/zinc/internal/zinc-classfile/src/main/scala/sbt/internal/inc/classfile/Parser.scala:157: local val in method getConstant is never used
[warn]           val kind = in.readByte()
[warn]               ^
[warn] /data/rw/code/scala/zinc/internal/zinc-classfile/src/main/scala/sbt/internal/inc/classfile/Parser.scala:158: local val in method getConstant is never used
[warn]           val ref = in.readUnsignedShort()
[warn]               ^
[warn] /data/rw/code/scala/zinc/internal/zinc-classfile/src/main/scala/sbt/internal/inc/classfile/Parser.scala:161: local val in method getConstant is never used
[warn]           val descriptorIndex = in.readUnsignedShort()
[warn]               ^
[warn] /data/rw/code/scala/zinc/internal/zinc-classfile/src/main/scala/sbt/internal/inc/classfile/Parser.scala:164: local val in method getConstant is never used
[warn]           val bootstrapIndex = in.readUnsignedShort()
[warn]               ^
[warn] /data/rw/code/scala/zinc/internal/zinc-classfile/src/main/scala/sbt/internal/inc/classfile/Parser.scala:165: local val in method getConstant is never used
[warn]           val nameAndTypeIndex = in.readUnsignedShort()
[warn]               ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/ConsoleInterface.scala:11: Unused import
[warn] import scala.tools.nsc.{ GenericRunnerCommand, Interpreter, ObjectRunner, Settings }
[warn]                                                ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/ConsoleInterface.scala:11: Unused import
[warn] import scala.tools.nsc.{ GenericRunnerCommand, Interpreter, ObjectRunner, Settings }
[warn]                                                             ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/ConsoleInterface.scala:14: Unused import
[warn] import scala.tools.nsc.util.ClassPath
[warn]                             ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/ConsoleInterface.scala:99: local method in method sync is never used
[warn]       implicit def compat(s: Settings): Compat = new Compat
[warn]                    ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/DelegatingReporter.scala:12: Unused import
[warn] import Compat._
[warn]               ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/ExtractAPI.scala:128: private setter in object existentialRenamings is never used
[warn]     private var renameTo: Map[Symbol, String] = Map.empty
[warn]                 ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/ExtractAPI.scala:223: private method in class ExtractAPI is never used
[warn]   private def printMember(label: String, in: Symbol, t: Type) = println(label + " in " + in + " : " + t + " (debug: " + debugString(t) + " )")
[warn]               ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/ExtractAPI.scala:628: local method in method staticAnnotations is never used
[warn]     implicit def compat(ann: AnnotationInfo): IsStatic = new IsStatic(ann)
[warn]                  ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/ExtractUsedNames.scala:11: Unused import
[warn] import Compat._
[warn]               ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/ExtractUsedNames.scala:135: private setter in object TypeDependencyTraverser is never used
[warn]       private var ownersCache = mutable.Map.empty[Symbol, mutable.HashSet[Type]]
[warn]                   ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/LocateClassFile.scala:11: Unused import
[warn] import scala.tools.nsc.symtab.Flags
[warn]                               ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/ScaladocInterface.scala:24: Unused import
[warn]   import forScope._
[warn]                   ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/ScaladocInterface.scala:62: Unused import
[warn]             import doc._
[warn]                        ^
[info] Packaging /data/rw/code/scala/zinc/internal/compiler-interface/target/compiler-interface-1.0.0-X8-SNAPSHOT-tests.jar ...
[info] Done packaging.
[warn] 9 warnings found
[info] Compiling 3 Scala sources to /data/rw/code/scala/zinc/internal/zinc-classfile/target/scala-2.12/test-classes...
[info] Compiling 10 Scala sources to /data/rw/code/scala/zinc/internal/zinc-apiinfo/target/scala-2.12/classes...
[warn] /data/rw/code/scala/zinc/internal/zinc-classfile/src/test/scala/sbt/internal/inc/classfile/ParserSpecification.scala:6: Unused import
[warn] import scala.util.Try
[warn]                   ^
[warn] /data/rw/code/scala/zinc/internal/zinc-apiinfo/src/main/scala/sbt/internal/inc/ClassToAPI.scala:27: local val in method process is never used
[warn]       val pkgs = packages(classes).map(p => new api.Package(p))
[warn]           ^
[warn] /data/rw/code/scala/zinc/internal/zinc-apiinfo/src/main/scala/sbt/internal/inc/ClassToAPI.scala:29: local val in method process is never used
[warn]       val defs = classes.flatMap(toDefinitions(cmap))
[warn]           ^
[warn] /data/rw/code/scala/zinc/internal/zinc-apiinfo/src/main/scala/sbt/internal/inc/ClassToAPI.scala:136: private val in object ClassToAPI is never used
[warn]   private val lzyEmptyStructure = lzyS(new xsbti.api.Structure(lzyEmptyTpeArray, lzyEmptyDefArray, lzyEmptyDefArray))
[warn]               ^
[warn] /data/rw/code/scala/zinc/internal/zinc-apiinfo/src/main/scala/sbt/internal/inc/ClassToAPI.scala:418: private method in object ClassToAPI is never used
[warn]   private[this] def superclassType(c: Class[_]): Type = try c.getGenericSuperclass catch {
[warn]                     ^
[warn] /data/rw/code/scala/zinc/internal/zinc-apiinfo/src/main/scala/sbt/internal/inc/ClassToAPI.scala:421: private method in object ClassToAPI is never used
[warn]   private[this] def interfaces(c: Class[_]): Array[Type] = try c.getGenericInterfaces catch {
[warn]                     ^
[warn] /data/rw/code/scala/zinc/internal/zinc-apiinfo/src/main/scala/xsbt/api/APIUtil.scala:11: Unused import
[warn] import scala.collection.mutable.HashSet
[warn]                                 ^
[warn] /data/rw/code/scala/zinc/internal/zinc-apiinfo/src/main/scala/xsbt/api/SameAPI.scala:31: local val in method apply is never used
[warn]       val start = System.currentTimeMillis
[warn]           ^
[warn] /data/rw/code/scala/zinc/internal/zinc-apiinfo/src/main/scala/xsbt/api/SameAPI.scala:40: local val in method apply is never used
[warn]       val end = System.currentTimeMillis
[warn]           ^
[warn] one warning found
[warn] 8 warnings found
[info] Compiling 2 Scala sources to /data/rw/code/scala/zinc/internal/zinc-apiinfo/target/scala-2.12/test-classes...
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/API.scala:82: method isImplClass in class Symbol is deprecated (since 2.12.0): trait implementation classes have been removed in Scala 2.12
[warn]         !sym.isImplClass &&
[warn]              ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/Analyzer.scala:54: method isImplClass in class Symbol is deprecated (since 2.12.0): trait implementation classes have been removed in Scala 2.12
[warn]           if (sym.isModuleClass && !sym.isImplClass) {
[warn]                                         ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/ClassName.scala:58: method isImplClass in class Symbol is deprecated (since 2.12.0): trait implementation classes have been removed in Scala 2.12
[warn]       sym.isModuleClass && !sym.isImplClass && !sym.isNestedClass
[warn]                                 ^
[warn] /data/rw/code/scala/zinc/internal/zinc-apiinfo/src/test/scala/xsbt/api/NameHashingSpecification.scala:223: private method in class NameHashingSpecification is never used
[warn]   private def simpleClassDef(name: String, dt: DefinitionType = DefinitionType.ClassDef,
[warn]               ^
[warn] /data/rw/code/scala/zinc/internal/zinc-apiinfo/src/test/scala/xsbt/api/NameHashingSpecification.scala:223: private default argument in class NameHashingSpecification is never used
[warn]   private def simpleClassDef(name: String, dt: DefinitionType = DefinitionType.ClassDef,
[warn]                                            ^
[warn] /data/rw/code/scala/zinc/internal/zinc-apiinfo/src/test/scala/xsbt/api/NameHashingSpecification.scala:224: private default argument in class NameHashingSpecification is never used
[warn]     access: Access = publicAccess): ClassLikeDef = {
[warn]     ^
[warn] /data/rw/code/scala/zinc/internal/zinc-apiinfo/src/test/scala/sbt/internal/inc/ClassToAPISpecification.scala:80: match may not be exhaustive.
[warn] It would fail on the following inputs: (??, _), (_, ??), (_, _)
[warn]     inherits.map {
[warn]                  ^
[warn] four warnings found
[warn] 32 warnings found
[info] Packaging /data/rw/code/scala/zinc/internal/compiler-bridge/target/scala-2.12/compiler-bridge_2.12-1.0.0-X8-SNAPSHOT.jar ...
[info] Done packaging.
[info] Compiling 6 Scala sources to /data/rw/code/scala/zinc/internal/compiler-bridge/target/scala-2.12/test-classes...
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/test/scala/xsbt/ClassNameSpecification.scala:3: Unused import
[warn] import xsbti.api.ClassLike
[warn]                  ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/test/scala/xsbt/ClassNameSpecification.scala:4: Unused import
[warn] import xsbti.api.Def
[warn]                  ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/test/scala/xsbt/ClassNameSpecification.scala:5: Unused import
[warn] import xsbt.api.SameAPI
[warn]                 ^
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/test/scala/xsbt/ScalaCompilerForUnitTesting.scala:178: local val in method prepareCompiler is never used
[warn]     val scalaReporter = new ConsoleReporter(settings)
[warn]         ^
[warn] four warnings found
[info] Packaging /data/rw/code/scala/zinc/internal/compiler-bridge/target/scala-2.12/compiler-bridge_2.12-1.0.0-X8-SNAPSHOT-tests.jar ...
[info] Done packaging.
[info] ExtractUsedNamesSpecification:
[info] Used names extraction
[info] - should extract imported name
[info] - should extract names in type tree
[info] - should extract symbolic names
[info] - should extract type names for objects depending on abstract types
[info] - should extract names in the types of trees
[info] - should extract used names from an existential
[info] - should extract used names from a refinement
[info] - should extract used names from the same compilation unit
[info] - should extract names of constants (pending)
[info] - should extract names from method calls on Dynamic (pending)
[info] ExtractUsedNamesPerformanceSpecification:
[info] - should be executed in reasonable time
[info] - should correctly find Out0 (not stored in inspected trees) both in TuplerInstances and TuplerInstances.<refinement>
[info] - should correctly collect used names from macro extension (pending)
[info] DependencySpecification:
[info] Dependency phase
[info] - should extract class dependencies from public members
[info] - should extract class dependencies from local members
[info] - should extract class dependencies with trait as first parent
there was one deprecation warning (since 2.11.0)
there was one deprecation warning (since 2.12.0)
there were two deprecation warnings in total; re-run with -deprecation for details
[info] - should extract class dependencies from macro arguments
[info] - should extract class dependencies from a refinement
[info] - should extract class dependency on a object correctly
[info] - should handle top level import dependencies
[info] ClassNameSpecification:
[info] ClassName
[info] - should create correct binary names for top level object
[info] - should create binary names for top level companions
[info] - should create correct binary names for nested object
[info] - should create a binary name for a trait
[info] - should not create binary names for local classes
[info] ExtractAPISpecification:
[info] ExtractAPI
[info] - should give stable names to members of existential types in method signatures
[info] - should extract children of a sealed class
[info] - should extract correctly the definition type of a package object
[info] - should extract nested classes
[info] - should not extract local classes
[info] - should extract flat (without members) api for a nested class
[info] - should extract private classes
[info] - should make a stable representation of a self variable that has no self type
[info] - should make a different representation for an inherited class
[info] - should handle package objects and type companions
[info] - should represent a self type correctly
[info] ScalaTest
[info] Run completed in 14 seconds, 519 milliseconds.
[info] Total number of tests run: 33
[info] Suites: completed 5, aborted 0
[info] Tests: succeeded 33, failed 0, canceled 0, ignored 0, pending 3
[info] All tests passed.
[info] Passed: Total 33, Failed 0, Errors 0, Passed 33, Pending 3
[success] Total time: 45 s, completed Mar 8, 2017 11:49:25 PM
1. Waiting for source changes... (press enter to interrupt)
[info] Formatting 1 Scala source {file:/data/rw/code/scala/zinc/}compilerBridge(compile) ...
[info] Reformatted 1 Scala source {file:/data/rw/code/scala/zinc/}compilerBridge(compile).
[info] Compiling 1 Scala source to /data/rw/code/scala/zinc/internal/compiler-bridge/target/scala-2.12/classes...
[warn] /data/rw/code/scala/zinc/internal/compiler-bridge/src/main/scala/xsbt/Command.scala:11: Unused import
[warn] import Compat._
[warn]               ^
[warn] one warning found
[info] Packaging /data/rw/code/scala/zinc/internal/compiler-bridge/target/scala-2.12/compiler-bridge_2.12-1.0.0-X8-SNAPSHOT.jar ...
[info] Done packaging.
[info] ExtractUsedNamesSpecification:
[info] Used names extraction
[info] - should extract imported name
[info] - should extract names in type tree
[info] - should extract symbolic names
[info] - should extract type names for objects depending on abstract types
[info] - should extract names in the types of trees
[info] - should extract used names from an existential
[info] - should extract used names from a refinement
[info] - should extract used names from the same compilation unit
[info] - should extract names of constants (pending)
[info] - should extract names from method calls on Dynamic (pending)
[info] ExtractUsedNamesPerformanceSpecification:
[info] - should be executed in reasonable time
[info] - should correctly find Out0 (not stored in inspected trees) both in TuplerInstances and TuplerInstances.<refinement>
[info] - should correctly collect used names from macro extension (pending)
[info] DependencySpecification:
[info] Dependency phase
[info] - should extract class dependencies from public members
[info] - should extract class dependencies from local members
[info] - should extract class dependencies with trait as first parent
there was one deprecation warning (since 2.11.0)
there was one deprecation warning (since 2.12.0)
there were two deprecation warnings in total; re-run with -deprecation for details
[info] - should extract class dependencies from macro arguments
[info] - should extract class dependencies from a refinement
[info] - should extract class dependency on a object correctly
[info] - should handle top level import dependencies
[info] ClassNameSpecification:
[info] ClassName
[info] - should create correct binary names for top level object
[info] - should create binary names for top level companions
[info] - should create correct binary names for nested object
[info] - should create a binary name for a trait
[info] - should not create binary names for local classes
[info] ExtractAPISpecification:
[info] ExtractAPI
[info] - should give stable names to members of existential types in method signatures
[info] - should extract children of a sealed class
[info] - should extract correctly the definition type of a package object
[info] - should extract nested classes
[info] - should not extract local classes
[info] - should extract flat (without members) api for a nested class
[info] - should extract private classes
[info] - should make a stable representation of a self variable that has no self type
[info] - should make a different representation for an inherited class
[info] - should handle package objects and type companions
[info] - should represent a self type correctly
[info] ScalaTest
[info] Run completed in 14 seconds, 774 milliseconds.
[info] Total number of tests run: 33
[info] Suites: completed 5, aborted 0
[info] Tests: succeeded 33, failed 0, canceled 0, ignored 0, pending 3
[info] All tests passed.
[info] Passed: Total 33, Failed 0, Errors 0, Passed 33, Pending 3
[success] Total time: 16 s, completed Mar 8, 2017 11:49:46 PM
2. Waiting for source changes... (press enter to interrupt)
[info] ScalaTest
[info] Run completed in 25 milliseconds.
[info] Total number of tests run: 0
[info] Suites: completed 0, aborted 0
[info] Tests: succeeded 0, failed 0, canceled 0, ignored 0, pending 0
[info] No tests were executed.
[info] Passed: Total 0, Failed 0, Errors 0, Passed 0
[info] No tests to run for compilerBridge/test:testQuick
[success] Total time: 0 s, completed Mar 8, 2017 11:49:47 PM
3. Waiting for source changes... (press enter to interrupt)

What I'm proposing in this ticket is more fine-grained than testQuick and would have all the knowledge that Zinc does. This will accomodate all the use cases of "incremental testing".

Current test frameworks detect runnable tests via reflection. If we want Zinc to know what it's runnable and what it's not, we can:

I was sure that APIs generated by zinc are used.

To implement this feature, we need Zinc to expose the recompiled test classes to the build tool
All required information are present in Analysis (e.g. stamps) or you can get information about generated/deleted files using ClassFileManager (and there it will reports files generated/deleted for each compilation cycle).

However I agree that we need a simple callback that will give a list of recompile sources (even for testing purposes).

I was sure that APIs generated by zinc are used.

I don't understand, what do you mean?

Zinc generates api representation of all classes. E.g. #264 changing type representation there.
@eed3si9n commented there:

I agree that it's not a breaking change to the public Zinc API, but note that the API info does get persisted into gzip file, and is extracted by sbt to do things like test detection.

Of course it does. I'm not discussing that.
What we're discussing is a way to know which of the recompiled classes are tests and can be run. Currently, test discoverability is done via reflection, but we'll need to do it at compile time by checking FQNs. I explain how in the description of this ticket.

Currently, test discoverability is done via reflection

Actually, it's done using the incremental compilation Analysis output, at least for junit: see https://github.com/sbt/junit-interface/blob/master/src/main/java/com/novocode/junit/JUnitFingerprint.java and grep for fingerprint in https://github.com/sbt/sbt, I had to make some changes to the dotty sbt phases to explicitly support this: https://github.com/lampepfl/dotty/pull/1763/commits/9411539eac8aaa8f052b7e6701d5d1d2b833d409
It's something that I would very much like to see replaced by some other mechanism like callbacks for the same reason that I'd like to change main class detection(https://github.com/sbt/zinc/issues/102): it exposes zinc implementation details to the outside world, therefore making it much harder to change the internal API.

In terms of "do only the follow-on work necessary because of this change", see also https://github.com/sbt/sbt/issues/2976.

Actually, it's done using the incremental compilation Analysis output

Interesting, scalatest does it with reflection IIRC.

It's something that I would very much like to see replaced by some other mechanism like callbacks

I will definitely do so. I agree this should not be exposed. I'd like a very small public API that gives build tools this information for free.

Implemented in https://github.com/sbt/sbt/pull/7644
Albeit the implementation still has rooms for refinement it does seem to meet the criteria in https://github.com/sbt/zinc/issues/265#issuecomment-285197975, for example a whitespace change should not cause any test to retrigger.


[DSSD-50] - Second attempt at rolling back the durability feature.

Coverage remained the same at 83.942% when pulling 6ef21361bebf7acddc39083cd38ed506cb0da8f9 on DSSD-50-Rolling-back-feature into 6a360e38d0b325a5ec35ace87088767a7b1a659b on master.


Star Catching Game

Prerequisites

[X] I am a GSSoC-22 Participant
[X] I checked to make sure that this issue has not already been filed

Description
I want to add a js game of star catching where an alien can be made to jump or move back and forth to collect stars falling from the sky.
Tech Stack
Web Development

@manisha-27 Kindly assign this issue to me

close with #307


Points of Information

During the elections phase of an AGM, make it possible to give a point of information about a candidate. This could be a reason why the candidate should not be elected. They must be factual and not opinion-based.
Benefits:

Makes it less likely for people to be elected on false premises
Makes the electorate better informed

Negatives:

May cause arguments and rifts between members
Cannot un-say something, so if someone says something breaking the rules the electorate will know it and not be able to forget it. This leads to an incentive to break the rules

I'm not sure on what limitations/conditions to put on this. A few things to consider in that ilk:

Should the person be in the room?
Should the person be able to dispute it?
How do we prevent arguments?
When should POIs be raised?
Should they be submitted in advance?
Should we require evidence?
How do we prevent people breaking the rules of what you are allowed to say?

This is based on amendment 2b from the most recent AGM which was not passed. The motion is attached to this comment.
ammendment-2b.pdf


fix GEARPUMP-117 add scripts to start and stop the cluster

[Current coverage][cc-pull] is 62.86%

Merging [#23][cc-pull] into [master][cc-base-branch] will increase coverage by 1.17%

2 files (not in diff) in ...rpump/cluster/master were modified. more

Misses +75
Hits -75

1 files (not in diff) in ...che/gearpump/cluster were modified. more

Misses +1
Hits -1

1 files (not in diff) in .../org/apache/gearpump were modified. more

Misses +8
Hits -8

7 files (not in diff) in ...apache/gearpump/util were modified. more

Misses -52
Hits +52

2 files (not in diff) in ...rpump/cluster/client were modified. more

Misses -47
Hits +47

2 files (not in diff) in ...mp/cluster/appmaster were modified. more

Misses -9
Hits +9

7 files (not in diff) in ...che/gearpump/cluster were modified. more

Misses -42
Hits +42

1 files (not in diff) in .../org/apache/gearpump were modified. more

Misses -1
Hits +1

File ...ntStoreFactory.scala (not in diff) was modified. more

Misses -2
Partials 0
Hits +2

File ...cutor/Executor.scala (not in diff) was modified. more

Misses -1
Partials 0
Hits +1

@@             master        #23   diff @@
==========================================
  Files           180        180
  Lines          5950       5950
  Methods        5671       5671
  Messages          0          0
  Branches        279        279
==========================================
+ Hits           3670       3740    +70
+ Misses         2280       2210    -70
  Partials          0          0

[][cc-pull]

Powered by Codecov. Last updated by [a1b2352...c903f13][cc-compare]
[cc-base-branch]: https://codecov.io/gh/apache/incubator-gearpump/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/apache/incubator-gearpump/compare/a1b23525207f86b1a12e3106d98217844df7f762...c903f13b45e953ba0084263763d017ad1c59e68f
[cc-pull]: https://codecov.io/gh/apache/incubator-gearpump/pull/23?src=pr

Updated

LGTM +1

+1.


Update Datadog policies. Allow attaching SecurityAudit policy to the Datadog IAM role

what

Update Datadog policies
Allow attaching SecurityAudit policy to the Datadog IAM role

why

Datadog has updated the required permissions for the "All" and 'Core" IAM policy configurations - keep up to date
Attaching the SecurityAudit policy allows Datadog to collect information about how AWS resources are configured (used in Datadog Cloud Security Posture Management to read security configuration metadata)
Datadog Cloud Security Posture Management (CSPM) makes it easier to assess and visualize the current and historic security posture of cloud environments, automate audit evidence collection, and catch misconfigurations that leave your organization vulnerable to attacks
Cloud Security Posture Management (CSPM) can be accessed at https://app.datadoghq.com/security/compliance/home

notes

The process to enable Datadog Cloud Security Posture Management (CSPM) consists of two steps (one automated, the other manual):

Enable SecurityAudit policy and provision it with terraform
In Datadog UI, perform the following manual steps:

Go to the Datadog AWS integration tile
Click on the AWS account where you wish to enable resource collection
Go to the Resource collection section for that account and check the box "Route resource data to the Cloud Security Posture Management product"
At the bottom left of the tile, click Update Configuration

references

https://docs.datadoghq.com/integrations/amazon_web_services/?tab=roledelegation#datadog-aws-iam-policy
https://docs.datadoghq.com/security_platform/cspm/
https://docs.datadoghq.com/integrations/amazon_web_services/?tab=roledelegation#resource-collection

/test all