Map Not appearing at all

So I load up both single and multiplayer ets2 and the route advisor is not showing the map at all, even if I let it sit for longer than 5 minutes  skin is version 3.3.0 and the telemetry server is 3.1.0  any ideas on how to force it to show the map or get it to in the first place

I'd suggest updating ETS2 Telemetry Server. It should work at version 3.2.4 and above.

@Koenvh1 thanks, upgraded to 3.2.5 and that got it working

ok got it working by downloading the master fork and using that which is 3.2.5 and its now working


[BUGFIX] FORCE_PERSISTENCE_IN_CI should not override persist option

For issue exposed by https://github.com/ember-cli/broccoli-lint-eslint/pull/140

@Gaurav0 thanks for fixing this!

released as v1.4.6 🎉
released as v2.1.1 🎉


Facing CORS error while uploading file from another domain

Hi,
While trying to implement your code, everything works with Tus JS clinet, as long I don't need CORS. By using another url for upload services and another domain for client-side app, I face 404 error on PATCH request.
How can I fix this error?

Hi!
What you need to do is enable CORS on the server. I think the easiest way to do this is to install the Nuget package Microsoft.Owin.Cors and then set it up as below:
`	var corsPolicy = new CorsPolicy
{
AllowAnyHeader = true,
AllowAnyMethod = true,
AllowAnyOrigin = true,
ExposedHeaders = { "Location" },
SupportsCredentials = true
};
		app.UseCors(new CorsOptions
		{
			PolicyProvider = new CorsPolicyProvider
			{
				PolicyResolver = context => Task.FromResult(corsPolicy)
			}
		});

// app.UseTus(...) goes here
`
Please note that you need to add Location as "Exposed headers" as it is not exposed by default.

Thanks for your reply!
I used your js file and instead of 404, I get 405 Method Not Allowed on PATCH requests. OPTIONS and POST request are working by the way. 404 happens when X-HTTP-Method-Override is set to true and tus uses POST instead of PATCH.

I used your js file and instead of 404, I get 405 Method Not Allowed on PATCH requests. OPTIONS and POST request are working by the way. 404 happens when X-HTTP-Method-Override is set to true and tus uses POST instead of PATCH.

@smatsson Thanks for your reply. I'm still having the same problem. My tus server is running on <IP_ADDRESS>:81 and my front-end application is running on <IP_ADDRESS>:82, all I get is CORS errors in console.

@mjpournassari  X-HTTP-Method-Override is not yet implemented as per the roadmap so that will not work. Are you running the site as a web application? In that case you need to update your web.config to run your code for all types of HTTP verbs:
<system.webServer>
		<validation validateIntegratedModeConfiguration="false"/>
		<handlers>
			<remove name="ExtensionlessUrlHandler-Integrated-4.0" />
			<remove name="OPTIONSVerbHandler" />
			<remove name="TRACEVerbHandler" />
			<add name="ExtensionlessUrlHandler-Integrated-4.0" path="*." verb="*" type="System.Web.Handlers.TransferRequestHandler" preCondition="integratedMode,runtimeVersionv4.0" />
		</handlers>
		<modules runAllManagedModulesForAllRequests="true">
			<remove name="ApplicationInsightsWebTracking"/>
			<remove name="WebDAVModule" />
		</modules>
	</system.webServer>

@faridv Please try the answer to @mjpournassari and see if that helps. Otherwise, please provide the code you have so that I can have a look. I tested the same thing earlier this morning with two sites running on localhost:8080 and localhost:9000. Both of these were console apps (the OwinTestSite in the repo).

@smatsson  Hi
My project is Web Api. In the web.config file  handlers are exists.
You can test my client by below address:
http://<IP_ADDRESS>:82/upload.html

@mjpournassari Can't connect to the site. Did you add runAllManagedModulesForAllRequests="true"? If so, please provide me with the code that is not working (i.e. your solution) and I'll have a look.

@smatsson  Yes runAllManagedModulesForAllRequests="true.
I attached my Web Api project.
SERVICE.zip

@smatsson Please try again to connect to http://<IP_ADDRESS>:82/upload.html

@mjpournassari Still can't connect but it doesn't really matter. Viewing your upload page does not give me any info that your solution won't give me. I'll have a look at it when I get the time.

@smatsson  Thank you

@mjpournassari I have looked at your code and this is not related to CORS. I have opened issue #3 were we can continue, so that @faridv can get help with his CORS issues in this issue. I have moved our comments to #3

@faridv Did you manage to solve the issue?

@smatsson No, I couldn't. But it seems that me and @mjpournassari are facing the same issue.
server config is OK but PATCH requests are being sent to my localhost/null.

@faridv I don't think the two issues are related at all. @mjpournassari's issue was that he was using an old version of tus-js-client that did not properly support relative URLs for cross domain (i.e. /files/ from localhost:82 was sent to localhost:81/files/id if the tus-js-client was hosted on localhost:81). This was fixed in an update to the client.
In your case, there seems to be an issue reading the Location header. Does your browser console contain any CORS related warnings?

No answer for 21 days. I'll consider this one solved. F
or any other readers of this issue, the problem with the localhost/null address might be an issue with an old broken URL. tus-js-client will save URLs it receives for a specific file (otherwise it doesn't know if it should continue the upload or start a new one). If this URL is broken then future uploads for the same file will also be broken. Clear the sites local storage to remove all existing urls.


Add Read receipts feature

🚀Feature Request
I want to implement read receipts feature in this project.
Level - medium
Key Points -
1)Whenever a sender send a message to the receiver first the message reaches server you must get an acknowledgement that message has been sent to server.
2)When the message reaches from server to receiver you must get a delivered acknowledgement.
3)Whenever the receiver opens the application and your chat you must get an acknowledgement that the message is read by the receiver.
This feature will give you assurance whether your message is successfully delivered to the receiver or they have read your message.

I'd like to contribute
Can you assign me this issue

Can you assign this issue to me

Dear @harshshukla1609, I have successfully set up your project locally and have experience with Socket.io; could you kindly assign the issue to me?

i m working on this issue.

@nandani-01 is ṭḥe issue assigned to you from the contri hub website ?


@ashfurrow => Added a blog post about licensing

Had to wait for my computer to update to 11.2 - it's taking a while.
@alloy would love a one over too

Cool, generally looks great! I'm a bit concerned about the "public domain" bit – we can chat irl if you want.

Alright, gone over it all.

Looks great! Merge when you're ready.

:+1:

@orta There's a few more questions/comments/suggestions that I made in the original google doc which still apply.


Make Publish actually publish

The Publish stage of the Jenkins build doesn't actually publish. The environment variables we've tried testing against are null during the master build (but not during the pr build). This prevents master builds from ever successfully pushing to quay.

These are the env.* available during the master build.
Name: BRANCH_NAME -> Value master
Name: BUILD_DISPLAY_NAME -> Value #11
Name: BUILD_ID -> Value 11
Name: BUILD_NUMBER -> Value 11
Name: BUILD_TAG -> Value jenkins-k2-jj-master-11
Name: BUILD_URL -> Value https://common-jenkins.kubeme.io/job/k2-jj/job/master/11/
Name: CLASSPATH -> Value
Name: HUDSON_HOME -> Value /var/jenkins_home
Name: HUDSON_SERVER_COOKIE -> Value 6007e83f66d1eaa8
Name: HUDSON_URL -> Value https://common-jenkins.kubeme.io/
Name: JENKINS_HOME -> Value /var/jenkins_home
Name: JENKINS_SERVER_COOKIE -> Value 6007e83f66d1eaa8
Name: JENKINS_URL -> Value https://common-jenkins.kubeme.io/
Name: JOB_BASE_NAME -> Value master
Name: JOB_DISPLAY_URL -> Value https://common-jenkins.kubeme.io/job/k2-jj/job/master/display/redirect
Name: JOB_NAME -> Value k2-jj/master
Name: JOB_URL -> Value https://common-jenkins.kubeme.io/job/k2-jj/job/master/
Name: RUN_CHANGES_DISPLAY_URL -> Value https://common-jenkins.kubeme.io/job/k2-jj/job/master/11/display/redirect?page=changes
Name: RUN_DISPLAY_URL -> Value https://common-jenkins.kubeme.io/job/k2-jj/job/master/11/display/redirect

Still didn't work even though the correct strings were being tested against.

Fixed in PR #656


[Feature] Need to extends the body behind the appbar and the footer

I have requirement to show the bottom tabbar and the footer with borderradius
but when I don't have the body in the back of behind the footer / bottomtabbar.

I did the change, I create a new branch and I wanted to do a pull request but I was not able to push.
so I forked it here: https://github.com/yelkamel/we_slide

Hi @yelkamel 👋
Have you tried to fork, edit, commit and submit a pull request?
There is no restrictions to make pull request.


dtill issies - why is this so difficult

Espressif/frameworks/esp-idf-v5.1.1-3/components/xtensa
-- --------------Compile Info------------
-- IDF_PATH = C:/Espressif/frameworks/esp-idf-v5.1.1-3
-- IDF_TARGET = esp32s3
-- PROJECT_NAME = ESP32-TUX
-- PROJECT_DIR = E:/__dev/ESP32-TUX
-- BUILD_DIR = E:/__dev/ESP32-TUX/build
-- SDKCONFIG = E:/__dev/ESP32-TUX/sdkconfig
-- SDKCONFIG_DEFAULTS = E:/__dev/ESP32-TUX/sdkconfig.defaults
-- CONFIG_LV_CONF_SKIP =

-- CMAKE_SOURCE_DIR = E:/__dev/ESP32-TUX
-- CMAKE_BINARY_DIR = E:/__dev/ESP32-TUX/build
-- ---------By Sukesh Ashok Kumar---------
-- Configuring done
-- Generating done
-- Build files have been written to: E:/__dev/ESP32-TUX/build
E:/__dev/ESP32-TUX/components/LovyanGFX/src/lgfx/v1/platforms/esp32/common.cpp: In function 'void lgfx::v1::i2c::i2c_set_cmd(i2c_dev_t*, uint8_t, uint8_t, uint8_t)':
E:/__dev/ESP32-TUX/components/LovyanGFX/src/lgfx/v1/platforms/esp32/common.cpp:643:14: error: 'struct i2c_dev_t' has no member named 'comd0'; did you mean 'comd'?
643 |       (&dev->comd0)[index].val = cmd_val;
|              ^~~~~
|              comd
ninja: build stopped: subcommand failed.
ninja failed with exit code 1, output of the command is in the E:__dev\ESP32-TUX\build\log\idf_py_stderr_output_31640 and E:__dev\ESP32-TUX\build\log\idf_py_stdout_output_31640
PS E:__dev\ESP32-TUX>
#if defined (CONFIG_IDF_TARGET_ESP32S3)
(&dev->comd0)[index].val = cmd_val;
#else
dev->command[index].val = cmd_val;
#endif
}

E:/__dev/ESP32-TUX/components/LovyanGFX/src/lgfx/v1/platforms/esp32/common.cpp:643:14: error: 'struct i2c_dev_t' has no member named 'comd0'; did you mean 'comd'?
643 | (&dev->comd0)[index].val = cmd_val;

Error is coming from LovyanGFX library. So not sure. You need to check on their github repo
E:/__dev/ESP32-TUX/components/LovyanGFX/src/lgfx/v1/platforms/esp32/common.cpp:643:14: error: 'struct i2c_dev_t' has no member named 'comd0'; did you mean 'comd'? 643 | (&dev->comd0)[index].val = cmd_val;
Also make sure you are using released version of ESP-IDF and not from the main branch which is the working branch.


[Menu] Component appear far from their original position when the zoom style is applied

Order ID 💳
48778
Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

The problem in depth 🔍
Current behavior :
The pagination component appears far from its original position when the zoom style is applied like the screenshots below from my local computer.

Here is the condition before the zoom style applied (height dimension > 500px)

Here is the condition after the zoom style applied (height dimension < 500px)

Expected behavior :
The pagination component appeasr from its original position whether the zoom style is applied or not.
Steps to reproduce :
Steps:

Run the codesandbox above
Test the appearance of the pagination components
The case appears

Context :
What I want to do is to apply the zoom property on smaller screen sizes so I create this code :

apply no zoom style to the body and some container components
apply the zoom style to all component contents

The zoom style is only applied for specific screen sizes (code from my local computer) :
// 1.176470588 = 1 / 0.85

'@media only screen and (max-height: 820px)': {
  'body': {
    zoom: 0.85,
  },
  '.zoom': {
    zoom: 0.85,
  },
  '.no-zoom': {
    zoom: 1.176470588,
  },
}

Here is the codesandbox demo : https://codesandbox.io/s/mui-floating-issues-lsimnx
I also have almost the same problem, but this problem occurs in some components like Menu and Tooltip. I've raised this issue in here, but haven't found a solution yet. I hope you can help solve this problem, thank you.
Environment

Dependencies
"dependencies": {
  "@emotion/react": "^11.9.0",
  "@emotion/styled": "^11.8.1",
  "@mui/icons-material": "^5.6.2",
  "@mui/lab": "^5.0.0-alpha.63",
  "@mui/material": "^5.7.0",
  "@mui/styles": "^5.7.0",
  "@mui/x-data-grid": "^5.10.0",
  "@mui/x-data-grid-pro": "^5.10.0",
  "@testing-library/jest-dom": "^5.16.1",
  "@testing-library/react": "^12.1.2",
  "@testing-library/user-event": "^13.5.0",
  "react": "^17.0.2",
  "react-dom": "^17.0.2",
  "react-router-dom": "^6.2.1",
  "react-scripts": "5.0.0",
  "web-vitals": "^2.1.3"
},

@yusufvalid @m4theushw can i pick up this issue?

@mbayucot
Please feel free to!

@hbjORbj Thanks

@m4theushw ok sir thank you.
@mbayucot yes sir, please feel free to.

Hi all
I think this issue is not from the MUI or @popperjs/core or React Js library but from the CSS zoom property itself.
I also faced the same issue on the React Leaflet and Leaflet Js libraries without using any MUI or @popperjs/core library.
Here is the full explanation https://github.com/mui/material-ui/issues/32777#issuecomment-1249211426
CC @yusufvalid @m4theushw @mbayucot @hbjORbj

Temporary Solution
This is not a bug of mui.
So you have to edit another dependency called @popperjs.
https://github.com/floating-ui/floating-ui/issues/3032 (Same Issue. @popperjs was renamed to floating-ui)
Edit your<EMAIL_ADDRESS>like below. (line number should be different by version)
Line 84
Before
y -= offsetY - popperRect.height;

After
y -= offsetY/parseFloat(window.getComputedStyle(document.body).zoom) - popperRect.height;

Line 92
##@# Before
x -= offsetX - popperRect.width;

After
x -= offsetX/parseFloat(window.getComputedStyle(document.body).zoom) - popperRect.width;


Allow overriding of keycloak root credentials for 2024.11.1 upgrade path

Reference Issues or PRs

What does this implement/fix?
Put a x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing

[ ] Did you test the pull request locally?
[ ] Did you add new tests?

How to test this PR?

Any other comments?

needs to be validated if the keycloak_admin.get_server_info works as a first layer credential check

This is how it looks like now:


tensorflow error

As issued WJluluxiu on the other issue page, there is a tensorflow error and I got the following error messages.

My server has 4 x 1080Ti GPUs on CentOS7.

What is your CUDA version? Is it 11.1.105 or more?

Thank you. the Cuda version is 9.2, I think.
nvcc: NVIDIA (R) Cuda compiler driver Copyright (c) 2005-2018 NVIDIA Corporation Built on Tue_Jun_12_23:07:04_CDT_2018 Cuda compilation tools, release 9.2, V9.2.148

Because install_colabfold_linux.sh installs tensorflow-gpu 2.5.0 which depends on CUDA 11, your environment may not be sufficient to run localcolabfold. See https://www.tensorflow.org/install/source?hl=en#gpu .
Please upgrade your cuda driver to 11.1, 11.2 or more and try the installation again.

I too experienced errors which ended up being due to not having version 11.1 or higher of the CUDA drivers.  In my case, the relevant portion of the traceback looked like:
2021-09-15 22:06:36.025661: W external/org_tensorflow/tensorflow/stream_executor/gpu/asm_compiler.cc:81] Couldn't get ptxas version string: Internal: Couldn't invoke ptxas --version
2021-09-15 22:06:36.026239: F external/org_tensorflow/tensorflow/compiler/xla/service/gpu/nvptx_compiler.cc:479] ptxas returned an error during compilation of ptx to sass: 'Internal: Failed to launch ptxas'  If the error message indicates that a file could not be written, please verify that sufficient filesystem space is provided.

However, typing nvidia-smi on the Ubuntu terminal yielded
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.63.01    Driver Version: 470.63.01    CUDA Version: 11.4     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  Off  | 00000000:01:00.0 Off |                  N/A |
|  0%   35C    P8     9W / 350W |     98MiB / 24245MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      1219      G   /usr/lib/xorg/Xorg                 85MiB |
|    0   N/A  N/A      1425      G   /usr/bin/gnome-shell               10MiB |
+-----------------------------------------------------------------------------+

which rather made it looked like I did have CUFA Version 11.4.  Then I noticed that typing nvcc --version gave
(/home/lupo/Workspace/colabfold/colabfold-conda) lupo@SV-91L-002:~/Workspace/colabfold$ nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2019 NVIDIA Corporation
Built on Sun_Jul_28_19:07:16_PDT_2019
Cuda compilation tools, release 10.1, V10.1.243

Which left me rather confused as an inexperienced GPU user.  Why does one command show a version 11.4 and the other a version 10.1?  I ran both sudo apt install nvidia-cuda-toolkit (which I now think was a mistake) and updated the CUDA drivers according to the instructions in https://developer.nvidia.com/cuda-downloads?target_os=Linux&target_arch=x86_64&Distribution=Ubuntu&target_version=20.04&target_type=deb_local.  But nvcc --version still showed version 10.1, and i still got the compilation error when launching runner.py.
The solution came from stumbling upon https://stackoverflow.com/a/53504578 where it is explained that what I had been looking at were two different things under the CUDA umbrella.  It turned out there are some "Mandatory post-installation actions" listed in https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#post-installation-actions which I had not performed after updating CUDA.  After performing them, nvcc --version also shows version 11.4 and I am able to run my first localcolabfold experiment!
I hope this story can be of help.

Yes, the return values nvidia-smi and nvcc --version are different. We have to make sure the value of nvcc --version, not nvidia-smi.

Thanks for the reply @YoshitakaMo!

Yes, the return values nvidia-smi and nvcc --version are different. We have to make sure the value of nvcc --version, not nvidia-smi.

Indeed.  Do you think it would be good to add this detail to the README?

Do you think it would be good to add this detail to the README?
Yes, I've added it. I appreciate your examination and kind proposal!


Cosmos: Confirm and Claim reward

When a user clicks confirm, they are prompted to sign the tx on their connected wallet

“Confirm” button goes into a “Confirm on Wallet” pending state (right now it says “Broadcasting Transaction” but we should fix this) until tx is signed and broadcasted
If user rejects tx on their wallet, the ‘Confirm’ button goes back to the active “Confirm” state and user sees a toast message, “Transaction Rejected”

After a user confirms a tx on their wallet, the transaction is broadcasted

If tx is broadcasted successfully, user is routed to the Pending Claim step with their TXID linked to a block explorer in the new tab

Confirm Details icon becomes a Check icon
Broadcast TX icon becomes an animated spinner

If tx is not broadcast successfully, user sees a toast message, “Error sending. Try again.”, and the button goes back to the active “Confirm” state

If tx is not broadcast successfully, user sees a toast message, “Error sending. Try again.”, and the button goes back to the active “Confirm” state

will work on this one


Overconstrained implementation of Serialize

When deriving Serialize, the resulting code seems to overconstrain the implementation.
playground example of this problem
The derive macro seems to require that T: Serialize instead of Foo<T>: Serialize for some reason. This makes it impossible to write wrappers for implementing Serialize in terms of other trait.

The defaults of the derive are simple and always add the Serialize bound for each generic type. However, you can overwrite the trait bounds like #[serde(bound = "T: MyTrait")].
https://serde.rs/container-attrs.html#bound

Glad to hear there's a usable workaround. Doing the right thing by default would be nicer though.

Duplicate of #370.

See https://github.com/dtolnay/syn/issues/370 -- we tried less constrained bounds in 0.7 and it turned out to be worse.

Damn, that sucks, thanks for pointers!


Support banning a site only from image search

Annoyingly, there is a ton of CEO spam on image searches, mainly from Redbubble and other shopping sites that makes finding a original image for a meme almost impossible these days. I also have a feeling that Google prioritizes them to get you to buy crap. But even worse, it has affected more reputable brands like eBay and Amazon. So banning Amazon would be too extreme, but I would like to ban them from image searches since in my opinion it is completely irrelevant when I am looking for a image 99% of the time.
Issue with Amazon:

Issue as a whole without banning any sites from search:

As you can see half of them are just tshirts, cups, mugs, prints, prints that are cropped, and sites that don't even own the copyright likely adding watermarks to try to scam you into buying it, and everything but what I actually want which is the original image

This is important to me

v8.8 or later supports this feature.
*://*.amazon.com/* @if($category="images")


Path to main file is incorrect in bower.json

Since the file paths in "main" are relative to the package's root directory, the current bower.json:
{
  "name": "Chart.js",
  "version": "2.0.0",
  "description": "Simple HTML5 Charts using the canvas element",
  "homepage": "https://github.com/nnnick/Chart.js",
  "author": "nnnick",
  "main": [
    "Chart.js"
  ],
  "devDependencies": {
    "jquery": "~2.1.4"
  }
}

incorrectly sets the path Chart.js. That points to the root directory, rather than the dist directory where the file lives.

PR here: https://github.com/nnnick/Chart.js/pull/2237

Fixed in #2237.

v2.0.1 was released. closing.


Android version not work on Samsung S6

Hi,
i have this component:
import React, {
  PropTypes,
  Component,
} from 'react';
import {
  Platform,
  StyleSheet,
  View,
  Text,
  Image,
  TouchableOpacity,
} from 'react-native';
import Colors from '../Styles/Colors';
import Fonts from '../Styles/Fonts';
import ImagePicker from 'react-native-image-picker';

const styles = StyleSheet.create({
  container: {
    margin: 16,
    alignItems: 'center',
  },
  circle: {
    width: 95,
    height: 95,
    borderRadius: 95 / 2,
    backgroundColor: Colors.colorBgTwo,
    borderWidth: 13,
    borderColor: 'white',
    alignItems: 'center',
    justifyContent: 'center',
  },
  avatar: {
    width: 82,
    height: 82,
    borderRadius: 82 / 2,
  },
});

const propTypes = {
  options: PropTypes.object,
};

const defaultProps = {
  options: {
    title: 'Select Avatar', // specify null or empty string to remove the title
    cancelButtonTitle: 'Cancel',
    takePhotoButtonTitle: 'Take Photo...', // specify null or empty string to remove this button
    chooseFromLibraryButtonTitle: 'Choose from Library...', // specify null or empty string to remove this button
    cameraType: 'front', // 'front' or 'back'
    mediaType: 'photo', // 'photo' or 'video'
    quality: 0.5, // 0 to 1, photos only
    angle: 0, // android only, photos only
    allowsEditing: false, // Built in functionality to resize/reposition the image after selection
    noData: false, // photos only - disables the base64 `data` field from being generated (greatly improves performance on large photos)
    storageOptions: { // if this key is provided, the image will get saved in the documents directory on ios, and the pictures directory on android (rather than a temporary directory)
      skipBackup: true, // ios only - image will NOT be backed up to icloud
      path: 'images', // ios only - will save image at /Documents/images rather than the root
    },
  },
};

class ImageUpload extends Component {

  constructor(props) {
    super(props);

    this.state = {
      avatarSource: null,
    };
    this.selectPhotoTapped = this.selectPhotoTapped.bind(this);
  }

  selectPhotoTapped() {
    ImagePicker.showImagePicker(this.props.options, (response) => {
      console.log('Response = ', response);

      if (response.didCancel) {
        console.log('User cancelled photo picker');
      } else if (response.error) {
        console.log('ImagePicker Error: ', response.error);
      } else if (response.customButton) {
        console.log('User tapped custom button: ', response.customButton);
      } else {
        var source;

        // You can display the image using either:
        // source = { uri: `data:image/jpeg;base64, ${response.data}`, isStatic: true };
        if (Platform.OS === 'android') {
          source = { uri: response.uri, isStatic: true };
        } else {
          source = { uri: response.uri.replace('file://', ''), isStatic: true };
        }

        this.setState({
          avatarSource: source,
        });
      }
    });
  }

  render() {
    return (
      <View style={styles.container}>
        <TouchableOpacity onPress={() => { this.selectPhotoTapped(); }} >
          <View style={styles.circle}>
            {this.state.avatarSource === null ? <Text style={Fonts.h7ButtonPrimary}>Photo</Text> :
              <Image style={styles.avatar} source={this.state.avatarSource} />
            }
          </View>
        </TouchableOpacity>
      </View>
    );
  }
}

ImageUpload.propTypes = propTypes;
ImageUpload.defaultProps = defaultProps;

export default ImageUpload;

On IOS it works, on Android i have this:

Can you help me?

I run the Example and i don't get this issue. Can you try the Example and tell me if it work for you ?
Are you sure that you use the last version of this package ?

@yfuks yes, i have<EMAIL_ADDRESS>Something went wrong with the installation...so i have deleted android folder and i have reinstalled the component:
react-native android
rnpm link react-native-image-picker
react-native run-android

but i have this error:
Unknown source file : UNEXPECTED TOP-LEVEL EXCEPTION:
Unknown source file : com.android.dex.DexException: Multiple dex files define Landroid/support/v7/appcompat/R$anim;
Unknown source file : 	at com.android.dx.merge.DexMerger.readSortableTypes(DexMerger.java:596)
Unknown source file : 	at com.android.dx.merge.DexMerger.getSortedTypes(DexMerger.java:554)
Unknown source file : 	at com.android.dx.merge.DexMerger.mergeClassDefs(DexMerger.java:535)
Unknown source file : 	at com.android.dx.merge.DexMerger.mergeDexes(DexMerger.java:171)
Unknown source file : 	at com.android.dx.merge.DexMerger.merge(DexMerger.java:189)
Unknown source file : 	at com.android.dx.command.dexer.Main.mergeLibraryDexBuffers(Main.java:502)
Unknown source file : 	at com.android.dx.command.dexer.Main.runMonoDex(Main.java:334)
Unknown source file : 	at com.android.dx.command.dexer.Main.run(Main.java:277)
Unknown source file : 	at com.android.dx.command.dexer.Main.main(Main.java:245)
Unknown source file : 	at com.android.dx.command.Main.main(Main.java:106)

:app:dexDebug FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:dexDebug'.
> com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command '/Library/Java/JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/bin/java'' finished with non-zero exit value 2

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Well since something went wrong i recommend you to link the module manualy (steps are in the README)
I don't know any of the files in your stack error.
Make sure you updated RN

@yfuks
After

rnpm link react-native-image-picker

i have found this in settings.gradle
rootProject.name = 'Example'

include ':app'
include ':react-native-image-picker'
project(':react-native-image-picker').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-image-picker/android')

but in README there is this
rootProject.name = 'Example'

include ':app'
include ':react-native-image-picker'
project(':react-native-image-picker').projectDir = new File(settingsDir, '../node_modules/react-native-image-picker/android')

and in AndroidManifest.xml there isn't this:```

```
I want fix it but I do not know how rnpm works...

I don't know either. If the Example work fine for you try to find all the diff with your project.

i have same problem, you need to delete node_modules/react-native-image-picker/android/build/, it's works

@deming1990 Can you send a PR?

after you run sh npm install react-native-image-picker@latest --save
node_modules/react-native-image-picker/android/build/
delete original /android/build/
@sarovin

Is there another way? Can we fix it in this repo?

I'm able to reproduce. Investigating...

Are you sure you followed the README instructions? What you're seeing is exactly what would happen if you failed to link the native project. I just react-native init a new project, npm install react-native-image-picker@latest, followed the steps to link the native library, and it built and launched the picker fine.

Should be fixed in 0.19.5. Let me know.

Hi,

android {
compileSdkVersion 23
buildToolsVersion "23.0.2"
defaultConfig {
applicationId "com.XXX"
minSdkVersion 16
targetSdkVersion 22
versionCode 1
versionName "1.0"
ndk {
abiFilters "armeabi-v7a", "x86"
}
}

"react-native-image-picker": "^0.22.1"

,
it's work fine other device but not with Samsung galaxy tab, s3


Share code between Kafka Source and Channel

Expected Behavior
code shared between source and channel for kafka
Actual Behavior
It's not really the case. both are fairly indepdent implementations. a bit of consumer code is shared, but we could have done better there.
Additional Info
Design document, including a CloudEvents binding for kafka:
https://docs.google.com/document/d/1ve1pAfs1uPRQVi8VxrUbpchrbSf7S3N2_seoIU9XBx4/edit#

related #682

The proposal is almost what we're doing in https://github.com/knative-sandbox/eventing-kafka-broker
@slinkydeveloper, can we close this?

This issue is invalid


Remove alphabetically ordered imports checkstyle rule

Fixes #34

@tuesmiddt  Will we be graded on style? It may cost us some marks if we remove checkstyle and we're graded on it.

Lets wait for a responses to this issue before proceeding: https://github.com/nus-cs2103-AY1819S1/forum/issues/64

looks like they expect consistent import ordering so... I guess we'll just have to configure intellij to do it.


SAML 2.0 for Auth integration into Chainlit

Currently, I want to pass off authentication to my SAML 2.0 provider, but cannot do that directly within Chainlit.
Describe the solution you'd like
Similar to the use of GitHub for SSO, the use of external SAML 2.0 IdPs.
Describe alternatives you've considered
Tried using Auth0, but to no avail.

+1


Depend on semigroups only on GHC < 8.0

It is not needed on newer GHC.

Thanks, and sorry for the delay!


Completion and linting not working in an unity project

I use ALE for linting and when I open my script this appears
csharp CS0246] [E] The type or namespace name 'UnityEngine' could not be found (are you missing a using directive or an
assembly reference?)

completion with coc-omnisharp works but I don't get the completion for unity imports like Rigidbody2D for example
I know this is a common problem but I haven't found a solution yet
OS: arch linux
Editor: neovim

Have you looked at the other Unity issues? The most recent is #707 and it looked like the solution there worked.
I suspect this is a duplicate.

it didn't solve it, I realized it is probably because of these errors
Failed to load project: [a lot of .csproj files
I have tried a few solutions but  they didn't work


potential loop in ChatGPT chat.openai website when you ask certain question

i was coding
asked for help rewriting function
it started replying with my question 3-5 times in row repeat same then stop

on so this also bugs out here too when you post this code: async register(     userId: string,     initialTask: Task,     additionalTasks: Task[],     settings: TaskSettings,     score: Score,     tree: TaskTree   ): Promise<RegisterUserResult> {

gpt 3.5 btw


Fixing another bug with ids

Description of changes
Using reserved keywords as ids could cause the parser to panic instead of failing gracefully
Issue #, if available
N/A
Checklist for requesting a review
The change in this PR is (choose one, and delete the other options):

[X] A bug fix or other functionality change requiring a patch to cedar-policy.

I confirm that this PR (choose one, and delete the other options):

[X] Does not update the CHANGELOG because my change does not significantly impact released code.

I confirm that cedar-spec (choose one, and delete the other options):

[X] Does not require updates because my change does not impact the Cedar formal model or DRT infrastructure.

Disclaimer
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closed at my git history got messed up, resubmitting in a second


:recycle: refactor(navigation): main + flyout

Summary

widescreen and bigger the main nav bar is detached from the meta

1 row
tab carousel is active

before widescreen the main nav bar is attached to the meta no space

2 rows if the tabs needs more space
if tabs are on second row activate  tab carousel

Widescreen

Desktop

Desktop with 2 rows

Additional Information
No response
Code of Conduct

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

/cib


Update how-to-authentication-sms-supported-apps.md

SMS Sign-in is not supported on Auth app (which requires MFA) as Azure AD doesn't support any 2nd factor for SMS sign-in

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/MicrosoftDocs/{docs-repo}
Private repo URL: https://github.com/MicrosoftDocs/{docs-repo-pr}
We have closed this pull request. Please resubmit the updates through the private repo. For more information, [see the contributor guide].(https://docs.microsoft.com/en-us/contribute/)

#sign-off


[WIP] Implement bandit

This PR adds bandit as a dependency and makes appropriate changes to the codebase to address security concerns raised by bandit
Adresses #264

With #273 and #275 , this PR is no longer necessary.


[WebOS] Add a Header file for fixing build error

Change

Added a header file in WebOS Platform to fix build error

Testing

Tested done on WebOS

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


TimeZone problems

The code I run in DBeaver (via JDBC) and the result (wrong, timezone left +3 hours)

The same code that I run in Tabix and the result (correct, timezone left +0 hours)

What is it?

Nothing wrong here.
Java displays time in your local timezone.

Regardless what server time zone is and use_time_zone is set to, JDBC driver always format timestamp in local timezone, which is very confusing and this is inconsistent with clickhouse-client. Let's take it as a bug. I'll add more test cases to cover this and get it fixed in next release.
Server TimeZone: UTC
Berlin  : [JDBC] 2021-03-25 08:50:56 [Server]<PHONE_NUMBER> [clickhouse-client] 2021-03-25 01:50:56
Shanghai: [JDBC] 2021-03-25 08:50:56 [Server]<PHONE_NUMBER> [clickhouse-client] 2021-03-25 08:50:56
UTC     : [JDBC] 2021-03-25 08:50:56 [Server]<PHONE_NUMBER> [clickhouse-client] 2021-03-25 00:50:56
default : [JDBC] 2021-03-25 08:50:56 [Server]<PHONE_NUMBER> [clickhouse-client] 2021-03-25 00:50:56

which is very confusing and this is inconsistent with clickhouse-client. Let's take it as a bug.

So you are going to break the current behavior? I guess thousands of users will be shocked.

So you are going to break the current behavior? I guess thousands of users will be shocked.

Not all of a sudden, of course :D
In 0.3.x, we can introduce another connection setting to enable the changed behavior(disabled by default). Flip in 0.4, and retire the connection setting and old behavior in 1.0.
Let me know if you have better idea to reduce the impact.

Which method does DBeaver use?

As I recalled, it's just a thin wrapper in DBeaver for ClickHouse, so I guess it uses getTimestamp. In order to reproduce the issue, you can use native command-line to issue the query, and then compare the results with what you saw in DBeaver.
TZ='Asia/Shanghai' clickhouse-client --use_client_time_zone true
...
ch-server :) select toDateTime(1616633456), toDateTime(1616633456, 'Etc/UTC'), toDateTime(1616633456, 'America/Los_Angeles'), toDateTime(1616633456, 'Asia/Chongqing'), toDateTime(1616633456, 'Europe/Berlin'), toUInt32(toDateTime('2021-03-25 08:50:56')), toUInt32(toDateTime('2021-03-25 08:50:56', 'Asia/Chongqing'))

SELECT
    toDateTime(1616633456),
    toDateTime(1616633456, 'Etc/UTC'),
    toDateTime(1616633456, 'America/Los_Angeles'),
    toDateTime(1616633456, 'Asia/Chongqing'),
    toDateTime(1616633456, 'Europe/Berlin'),
    toUInt32(toDateTime('2021-03-25 08:50:56')),
    toUInt32(toDateTime('2021-03-25 08:50:56', 'Asia/Chongqing'))

Query id: 4a6eede6-9dfa-4dcc-92fc-3ee5f3dae8d9

┌─toDateTime(1616633456)─┬─toDateTime(1616633456, 'Etc/UTC')─┬─toDateTime(1616633456, 'America/Los_Angeles')─┬─toDateTime(1616633456, 'Asia/Chongqing')─┬─toDateTime(1616633456, 'Europe/Berlin')─┬─toUInt32(toDateTime('2021-03-25 08:50:56'))─┬─toUInt32(toDateTime('2021-03-25 08:50:56', 'Asia/Chongqing'))─┐
│    2021-03-25 08:50:56 │               2021-03-25 00:50:56 │                           2021-03-24 17:50:56 │                      2021-03-25 08:50:56 │                     2021-03-25 01:50:56 │<PHONE_NUMBER> │<PHONE_NUMBER> │
└────────────────────────┴───────────────────────────────────┴───────────────────────────────────────────────┴──────────────────────────────────────────┴─────────────────────────────────────────┴─────────────────────────────────────────────┴───────────────────────────────────────────────────────────────┘

1 rows in set. Elapsed: 0.038 sec.

On DBeaver(with default settings, local timezone is Asia/Shanghai), same query gives you below:

toDateTime(1616633456)
toDateTime(1616633456, 'Etc/UTC')
toDateTime(1616633456, 'America/Los_Angeles')
toDateTime(1616633456, 'Asia/Chongqing')
toDateTime(1616633456, 'Europe/Berlin')
toUInt32(toDateTime('2021-03-25 08:50:56'))
toUInt32(toDateTime('2021-03-25 08:50:56', 'Asia/Chongqing'))

2021-03-25 08:50:56
2021-03-25 08:50:56
2021-03-25 08:50:56
2021-03-25 08:50:56
2021-03-25 08:50:56
1616662256
1616633456

@enqueue, my memory didn't serve me well. After taking a closer look at DBeaver code, I think it we probably don't need to change anything in the driver. I'll download the code and submit a PR to fix this.

Now the new JDBC driver com.clickhouse.jdbc.ClickHouseDriver provides same output as cli client:

by default it uses server time zone
change use_server_time_zone to false, it will use client time zone(same as default time zone in JVM)
change use_time_zone to Asia/Chongqing(and use_server_time_zone=false), it will use the specified time zone


install.sh does not include python3-zeroconf

$ ./run.sh
python3 is /usr/bin/python3
Debugging enabled.
Called with system args: ['main.py']
Python version: 3.5.3 (default, Jan 19 2017, 14:11:04)
[GCC 6.3.0 20170118]
Python3 Zeroconf module could not be loaded.
Please ensure you have it installed.
Could not import own classes.
Non-Zero exit status.
Program quit.

apt-get install python3-zeroconf fixes the problem and should be added to install.sh.
(By the way, I very much like that your install.sh is simple enough that I can run each command by hand instead of executing it. And I appreciate that you're using the python3 libraries builtin to the system (using apt-get) instead of grabbing them from some third-party site.)

:+1:


Specifying other exchanges doesn't work

The given example /stocktopus tse:are
Returns: There's nothing here

Thanks for pointing that out. That feature degraded when Google shutdown their API service and I had to move stocktopus to use IEX (which doesn't seem to support other exchanges). PR #39 adds support for alphaAdvantage as the provider, which does support the TSE exchange. However due to the number of users on stocktopus it would quickly run into the rate limit of 5 req/min. So I don't plan to deploy it to the live instance of stocktopus, but others will be able to build and run their own using it. I will update the readme accordingly.

I'm leaving this issue open because I would still like to add this feature back into the main app.
However since stocktopus will forever remain free adding a premium API Key from alphavantage isn't something that can be afforded. If I can find a provider that implement this feature for free I will add that instead.


Question about the model.p file

Dear authors:
Thank you very much for building this code base.  I have one question about the model.p file. I want to learn more about how this environment works. However, the current powergrid use the model.p files which have been compiled. I'll appreciate it if you could share the corresponding model.m files. Thank you very much!

Hi,
Thank you for your interests! I believe we have provided a repo mentioned in readme: https://github.com/xuwkk/gen_pandapower_pv.
Hope it would be helpful!

Hi,
Thank you for your interests! I believe we have provided a repo link in readme: https://github.com/xuwkk/gen_pandapower_pv.
Hope it would be helpful!

Thank you for your reply! I have tried this repo and encountered a new problem. I found that in the case of bus33 and bus141, the size of the generated p file and the corresponding model.p file in voltage_control_data.zip are basically the same. However, in the case of bus322, the size of the p file generated by myself using this repo and the bus322.p file provided in this repo both exceed 600KB, while the size of model. p file in voltage_control_data.zip is 112KB. I'm really confused and hope you could help me. Thank you very much!

Dear authors,
I use the p files generated by this repo https://github.com/xuwkk/gen_pandapower_pv to replace the model.p files in the voltage_control_data.zip  to run the experiment. It can run normally under case33 and case141, but I will encounter this error under case322.
Traceback (most recent call last):
  File "train.py", line 62, in <module>
    env = VoltageControl(env_config_dict)
  File "/root/MAPDN/environments/var_voltage_control/voltage_control_env.py", line 52, in __init__
    self.base_powergrid = self._load_network()
  File "/root/MAPDN/environments/var_voltage_control/voltage_control_env.py", line 402, in _load_network
    base_net = pp.from_pickle(network_path)
  File "/root/miniconda3/envs/mapdn/lib/python3.7/site-packages/pandapower/file_io.py", line 145, in from_pickle
    net = pandapowerNet(io_utils.get_raw_data_from_pickle(filename))
  File "/root/miniconda3/envs/mapdn/lib/python3.7/site-packages/pandapower/io_utils.py", line 242, in get_raw_data_from_pickle
    net = read(f)
  File "/root/miniconda3/envs/mapdn/lib/python3.7/site-packages/pandapower/io_utils.py", line 232, in read
    return pickle.load(f, encoding='latin1')
ModuleNotFoundError: No module named 'scipy.sparse._csr'

I'll appreciate it if you could tell me how to solve it. Thank you very much!


error about organization_id in gateway table

Hi~
I'm wonder why below error appeared when i execute lora-app-server.exe.
*level=error msg="gwmigrate: list gateways error (will retry): rpc error: code = 2 desc = missing destination name organization_id in []gateway.Gateway"

I think  that problem is associated with the  gateway table in postgresql database.
Must i write the organization_id in gateway table?
If so, how can i decide organization_id and put it in gateway table?

How can i fix this problem?

Could you check the following?

Make sure that Both LoRa Server and LoRa App Server are using different databases
Make sure you're starting both services with --db-automigrate flag


pleas change request.resourceType ==='Document' instead document

Steps to reproduce
Tell us about your environment:

Puppeteer version:
Platform / OS version:
URLs (if applicable):

What steps will reproduce the problem?
Please include code that reproduces the issue.

What is the expected result?
What happens instead?

Lowercase was intentional to be consistent throughout the API. See https://github.com/GoogleChrome/puppeteer/commit/c3fb3671480af81b24cb9902e5e8912764e493d1


Adding rescanned CMS data

I noticed that the lumi and TAA were not folded into the previous scanned CMS data points.  Now the systematic uncertainties are a bit larger because of it

Maybe it got lost in plotting, but I included the TAA and lumi separately in the comment since they're constant (at least as far as I could tell). Did you combine them in quadrature?

(It looks like you probably scanned it better than I did, so it still looks like it would be an improvement regardless)

Yes, they are added in quadrature.  In the original text file that was used in the plotting script (not the sys.txt in the folder), I see that the systematic numbers are sometimes smaller than the TAA+Lumi, which is why I suspect it is not added.  The "rescanning" should be quite close to the actual points ;)

Very good! :-)

Thanks! Yes I think in the initial version of the plot I didn't include the lumi/TAA (which were in the headers or somewhere)
@raymondEhlers maybe you can have a double check again on the ATLAS hadron scanned points since we now know these figures will directly go in the paper?

@jdmulligan I double checked by plotting similarly (same scale, etc). See the link. I'd say that it looks pretty reasonable (I checked point-by-point by eye). One issue we need to sort out: I can only see some of the statistical errors for points above 100 GeV. I think the statistical error is small until the last two points (I can see it starting at 100 for central), but I can't really tell. Thoughts on how to handle those? Truncate?
atlas_hadron_RAA_comparison.pdf (original plot is embedded below)

Great, thanks!! Can you even see the statistical uncertainties for the central case for the highest two points? The third and fourth highest I can see...but perhaps we should just ignore all of them -- since this anyway isn't a very rigorous comparison, and they are preliminary results. For sake of time that's what I'd vote for -- although if you think you can scan them, then we can of course add in quadrature for those points that you can scan -- your call.

Agreed - I can only see the third and fourth points, but not the two highest where it really matters. For the fourth point, it's so small that adding in quadrature won't really make a difference, I think (although have to be careful with log plots). For the third point, it will matter more, but still seems to be subleading compared to the systematic. So basically only the third stat error from the highest would be meaningful, and we can't assign them for the two highest.
Given that, and that it's preliminary, and that it's going to be quite difficult to explain which points have stat errors and not (we included those we can see is kind of an odd metric, although accurate here), I would learn towards just neglecting them. However, if we can think of a concise way to describe it, I can scan those two points.
Regardless, we'll probably get questions about the last 30-40% point, but there's really nothing we can do about that


h3: 3.7.1 -> 3.7.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/uber/h3/releases.
meta.description for h3 is: "Hexagonal hierarchical geospatial indexing system"
meta.homepage for h3 is: "https://github.com/uber/h3"
meta.changelog for h3 is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/00j9h3wr8g9c4dz9xshqizc31bizy3wm-h3-3.7.2/bin/geoToH3 passed the binary check.

/nix/store/00j9h3wr8g9c4dz9xshqizc31bizy3wm-h3-3.7.2/bin/h3ToComponents passed the binary check.

/nix/store/00j9h3wr8g9c4dz9xshqizc31bizy3wm-h3-3.7.2/bin/h3ToGeo passed the binary check.

/nix/store/00j9h3wr8g9c4dz9xshqizc31bizy3wm-h3-3.7.2/bin/h3ToLocalIj passed the binary check.

/nix/store/00j9h3wr8g9c4dz9xshqizc31bizy3wm-h3-3.7.2/bin/localIjToH3 passed the binary check.

/nix/store/00j9h3wr8g9c4dz9xshqizc31bizy3wm-h3-3.7.2/bin/h3ToGeoBoundary passed the binary check.

/nix/store/00j9h3wr8g9c4dz9xshqizc31bizy3wm-h3-3.7.2/bin/hexRange passed the binary check.

/nix/store/00j9h3wr8g9c4dz9xshqizc31bizy3wm-h3-3.7.2/bin/kRing passed the binary check.

/nix/store/00j9h3wr8g9c4dz9xshqizc31bizy3wm-h3-3.7.2/bin/h3ToGeoBoundaryHier passed the binary check.

/nix/store/00j9h3wr8g9c4dz9xshqizc31bizy3wm-h3-3.7.2/bin/h3ToGeoHier passed the binary check.

/nix/store/00j9h3wr8g9c4dz9xshqizc31bizy3wm-h3-3.7.2/bin/h3ToHier passed the binary check.

11 of 11 passed binary check by having a zero exit code.

11 of 11 passed binary check by having the new version present in output.

found 3.7.2 with grep in /nix/store/00j9h3wr8g9c4dz9xshqizc31bizy3wm-h3-3.7.2

found 3.7.2 in filename of file in /nix/store/00j9h3wr8g9c4dz9xshqizc31bizy3wm-h3-3.7.2

directory tree listing: https://gist.github.com/966949fd784dabb5df9ccad6370c4be6

du listing: https://gist.github.com/0e2c82feab8c65884ad1aa3909172ce3

Rebuild report (if merged into master) (click to expand)

9 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
h3
python38Packages.h3
python39Packages.h3

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/00j9h3wr8g9c4dz9xshqizc31bizy3wm-h3-3.7.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A h3 https://github.com/r-ryantm/nixpkgs/archive/79a40e5afc4d1e714e6558ba3373ffc2401e230b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/00j9h3wr8g9c4dz9xshqizc31bizy3wm-h3-3.7.2
ls -la /nix/store/00j9h3wr8g9c4dz9xshqizc31bizy3wm-h3-3.7.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

h3
python38Packages.h3
python39Packages.h3

Maintainer pings
cc @kalbasit for testing.

Result of nixpkgs-review pr 130711 at 79a40e5a run on aarch64-linux 1

2 packages built successfully:

python38Packages.h3
python39Packages.h3


Compile error in VS 2015 and CUDA 10.0

I failed to compile the project in the recent environment, VS 2015 and CUDA 10.0 in my case.

Is there any solution about that?

I'm trying to solve this issue, but I guess it takes more time.
Sorry about that.
If you let me know your environment, it may help to fix this compile error.

Thanks for your replying.
My environment is the same as yours, VS2015+CUDA 10.0.


Add "projects" to the site map under "articles"

please!

What should the top level label ("Projects") link to?
What children items should be listed under it?
What should they link to?

Let's say it should link to
https://crimethinc.com/categories/projects
with this item:
https://crimethinc.com/2017/01/31/help-us-publish-books-about-borders-and-democracy-no-wall-they-can-build-from-democracy-to-freedom
We can add more to it soon?


[ZEPPELIN-2979] Fix links to zeppelin website in README

What is this PR for?
Fixes the broken links in the README under the sections "Install binary package" and "Build from Source" . Also changes http to https for all links to the zeppelin website
What type of PR is it?
[Documentation]
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-2979
Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

LGTM.

merging if no more comment

Thank you for the review guys! I have no more comments


ESPnow mode switching?

can we get a feature so that we can switch espnow modes? like between short and long range mode?

Hi, maybe I guess.


⚠ Elibs has degraded performance

In 7cbd02d, Elibs (https://elibs.unmer.ac.id) experienced degraded performance:

HTTP code: 200
Response time: 8253 ms

Resolved: Elibs performance has improved in 8b8bd68.


Pipeline application command

Create ecs pipeline command to enable CI/CD using Archer.
Subcommands include:

[ ] pipeline init: creates a CodePipeline that links project environments
[ ] pipeline update: updates pipeline for a given project
[ ] pipeline show: displays pipeline information
[ ] pipeline ls: shows all pipelines for all (?) projects

Dependent on deploy command? (See #13 )
Related: #210

I think pipeline init should create the pipeline.yml and then ask if we want to deploy it. What do you think?

Related: https://github.com/aws/amazon-ecs-cli-v2/issues/249

Resolving this higher level pipeline issue as we're creating separate issues per command


In finding duplicate reactions, other than the names, reactants, and products. It should also look for species reference?

Fixed in #27


Failed BDI Import - Error for missing ID on New and Exisiting Contact Imports

Error: The Contact Custom Unique ID setting field Id_15__c must have matching fields in the NPSP Data Import object whose API Names are Contact1_Id_15__c and Contact2_Id_15__c.
Trigger 1: DemandTools BDI import of new donor contacts who wouldn't have an ID to map to
Trigger 2: DemandTools BDI import of existing donor contacts who do have an ID to map to
We do this BDI import once a week on Monday (8/8) mornings and it sounds like last release was pushed last Monday night. We have not changed any part of our process and I don't see anything in documentation to indicate a change that would effective about ability to do BDI imports.
I've attached a screenshot of our BDI settings page in case something there needs to be changed based on new update.

thanks for reporting.  we've already identified it in issue #2690 and will have a fix available this week for sandbox push, that you can manually install in production if you can't wait until the following week's production push.


remove 'IPRO flow uses cache as expected' from flaky-list, ...

but strip out 'Fetch timed out' from log-warning check

LGTM


site: experiment with no solving blink of unstyled content

Observed no blink in a brand new create-react-app using Button.  Wondering if this is a nextjs issue.

Looking at the examples/with-glamor example on nextjs.  Oddly, getting build/startup errors there.

using import { speedy } from glamor; speedy(true) on pages/index.js did nothing.  Is there a "more first" "first" page to do this on?


Merge style

How about using only squash merge and changing the default merge message to "Default to pull request title and description"?
In general, one pull request has one logical change. So squashing commits in a pull request will not loss useful information.  And a merge commit will be meaningless.
In general, each pull request has meaningful title and description. So they will be suitable commit title and message too.

I agree!

@ashie What do you think about this?

Basically I agree with you.
The remaining concern is that how to conform to DCO style.
Since this project is Fluentd's sub project I think this project should follow the DCO style.

All trailers includingSigned-off-by are kept with "Default to pull request title and description".
So we can keep the DCO style with this change.

I see, thanks.
I've changed the repository setting.


Debugging go functions works with VS Code but not Goland

Description
I can debug go functions with VS Code but not with Goland.
Is it related to api-version ?
Steps to reproduce

generated a basic sample with serverless framework (basic hello world),
followed the tutorial on this page Step-through Debugging Golang Functions Locally
generated the template.yml.
removed the CodeUri in template.yml
created a configuration in goland (Go remote) with localhost and 5986 as port
launched sam local start-api -d 5986 --debugger-path my-delve-folder-path
launch a curl http://localhost:3000/hello
launch goland debugger

Observed result
It works on VS Code but I had to change the api-version to 1 in VS Code Settings (Default 2 : got a warning from VS Code). If not the function run but does not stop at breakpoint.
{
    "go.delveConfig": {
        "apiVersion":1
    }
}

Inside container
ps :
/tmp/lambci_debug_files/dlv --listen=:5986 --headless=true --api-version=1 --log exec /var/task/bin/hello
Console output
2018-12-26 11:24:41 Invoking bin/hello (go1.x)
2018-12-26 11:24:41 No environment variables found for function 'Hello'
2018-12-26 11:24:41 Environment variables overrides data is standard format
2018-12-26 11:24:41 Loading AWS credentials from session with profile 'default'
2018-12-26 11:24:41 Resolving code path. Cwd=/d/go/src/myserverless, CodeUri=.
2018-12-26 11:24:41 Resolved absolute path to code is /d/go/src/myserverless
2018-12-26 11:24:41 Code /d/go/src/myserverless is not a zip/jar file
2018-12-26 11:24:41 Skipping building an image since no layers were defined
2018-12-26 11:24:41 Trying paths: ['/home/myuser/.docker/config.json', '/home/myuser/.dockercfg']
2018-12-26 11:24:41 No config file found
2018-12-26 11:24:41 Trying paths: ['/home/myuser/.docker/config.json', '/home/myuser/.dockercfg']
2018-12-26 11:24:41 No config file found
2018-12-26 11:24:41 http://<IP_ADDRESS>:2375 "GET /v1.35/images/lambci/lambda:go1.x/json HTTP/1.1" 200 None
2018-12-26 11:24:41 Looking for auth config
2018-12-26 11:24:41 No auth config in memory - loading from filesystem
2018-12-26 11:24:41 Trying paths: ['/home/myuser/.docker/config.json', '/home/myuser/.dockercfg']
2018-12-26 11:24:41 No config file found
2018-12-26 11:24:41 Looking for auth entry for 'docker.io'
2018-12-26 11:24:41 No entry found
2018-12-26 11:24:41 No auth config found
2018-12-26 11:24:42 http://<IP_ADDRESS>:2375 "POST /v1.35/images/create?tag=go1.x&fromImage=lambci%2Flambda HTTP/1.1" 200 None

Fetching lambci/lambda:go1.x Docker container image......
2018-12-26 11:24:42 Mounting /d/go/src/myserverless as /var/task:ro inside runtime container
2018-12-26 11:24:42 Starting new HTTP connection (1): <IP_ADDRESS>:2375
2018-12-26 11:24:42 http://<IP_ADDRESS>:2375 "POST /v1.35/containers/create HTTP/1.1" 201 90
2018-12-26 11:24:42 http://<IP_ADDRESS>:2375 "GET /v1.35/containers/5783a6cd6cfffcc66a25362980c4b7cc7fbd86c8b91458c0157f655293a3624f/json HTTP/1.1" 200 None
2018-12-26 11:24:42 http://<IP_ADDRESS>:2375 "GET /v1.35/containers/5783a6cd6cfffcc66a25362980c4b7cc7fbd86c8b91458c0157f655293a3624f/json HTTP/1.1" 200 None
2018-12-26 11:24:43 http://<IP_ADDRESS>:2375 "POST /v1.35/containers/5783a6cd6cfffcc66a25362980c4b7cc7fbd86c8b91458c0157f655293a3624f/start HTTP/1.1" 204 0
2018-12-26 11:24:43 Setting up SIGTERM interrupt handler
2018-12-26 11:24:43 http://<IP_ADDRESS>:2375 "GET /v1.35/containers/5783a6cd6cfffcc66a25362980c4b7cc7fbd86c8b91458c0157f655293a3624f/json HTTP/1.1" 200 None
2018-12-26 11:24:43 http://<IP_ADDRESS>:2375 "POST /containers/5783a6cd6cfffcc66a25362980c4b7cc7fbd86c8b91458c0157f655293a3624f/attach?stream=1&stdin=0&logs=1&stderr=1&stdout=1 HTTP/1.1" 101 0
Could not create config directory: mkdir /home/sbx_user1051: permission denied.API server listening at: [::]:5986
time="2018-12-26T10:24:43Z" level=info msg="launching process with args: [/var/task/bin/hello]" layer=debugger

Expected result
Expect to work on Goland as well
If the reason is the api-version change it to 2 ? Or add an args ?
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

OS : Windows + WSL (Ubuntu 18.04)
sam --version : SAM CLI, version 0.10.0
IDE : latest VS Code an Goland

I get the same error with golang 1.11.4 linux/amd64 and sam 0.10.0:
~/go/src/picapp$ sam local start-api -d 5986 --debugger-path /home/cfx/go/bin/
2019-01-03 15:49:48 Found credentials in shared credentials file: ~/.aws/credentials
2019-01-03 15:49:48 Mounting ListPicsFunction at http://<IP_ADDRESS>:3000/list [GET]
2019-01-03 15:49:48 You can now browse to the above endpoints to invoke your functions. You do not need to restart/reload SAM CLI while working on your functions changes will be reflected instantly/automatically. You only need to restart SAM CLI if you update your AWS SAM template
2019-01-03 15:49:48  * Running on http://<IP_ADDRESS>:3000/ (Press CTRL+C to quit)
2019-01-03 15:49:53 Invoking list-pics (go1.x)

Fetching lambci/lambda:go1.x Docker container image......
2019-01-03 15:49:55 Mounting /home/cfx/go/src/picapp/list-pics as /var/task:ro inside runtime container
Could not create config directory: mkdir /home/sbx_user1051: permission denied.API server listening at: [::]:5986
time="2019-01-03T14:49:56Z" level=info msg="launching process with args: [/var/task/list-pics]" layer=debugger

I am facing same issue and it is related with api-version.
Inside Docker container i can see two processes running:

/var/runtime/aws-lambda-go -debug=true -delvePort=5986 -delvePath=/tmp/lambci_debug_files/dlv main
/tmp/lambci_debug_files/dlv --listen=:5986 --headless=true --api-version=1 --log exec /var/task/main

And Goland is using api-version = 2.
Can someone from support advise if we can pass api-version = 2 somehow?

To start this process off for this solution, I have done some digging, before AWS SAM GO lambda's can support delve API version '2', we require this PR bump Go debugger Delve API via flags to be merged first.
We will then need to create a PR for this repository to support to allow to pass a DELVE API verison via CLI and set default debugging API VERISON params in code, i.e. add the ability to provide the param '--debuggerAPI' which would translate to '-delveAPI' within code.
Use this PR as a reference on how to add new GO debugging params
Anyone interested in collaborating with me to achieve this?

@jackmcguire1 There isn't a need to add an Option in SAM CLI for this, as you can pass it through the --debug-args. I haven't yet validate this works but looking at the code, there shouldn't be anything stopping it.

@jfuss I’m of the opinion we still need a PR to add the default parameter, at the very least ... as I’m sure everyone will not want to have to declare the environment variable.
I.e add parameter here

The container defaults to a value already. I don’t see the value in adding it, if the containter controls the default api version.

The default value set by the container will be Devle API version 1 for backwards compatibility reasons, this whole issue here is regarding being able to apply API version 2, to which we can simply default ourselves within this repo...

Hi,
I managed to connect to dlv debugger from Golang using bellow command:
sam local start-api -d 5986 --debugger-path  --debug-args "-delveAPI=2"
Tnx

Great thanks for the update! @sekulid

Great !

#1050

Hello everyone, I'm very new to sam-cli. Following https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-using-debugging-golang.html
Fetching lambci/lambda:go1.x Docker container image......... 2019-03-18 21:45:46 Mounting /Users/x/go/src/x/x/invite-bp/bin as /var/task:ro inside runtime container Could not create config directory: mkdir /home/sbx_user1051: permission denied.API server listening at: [::]:5858 time="2019-03-19T01:45:47Z" level=info msg="launching process with args: [/var/task/invite]" layer=debugger could not launch process: fork/exec /var/task/invite: no such file or directory

Following this article aws-sam-setup
I was able to start the sam cli only to get a permission issue while attempting to curl at it.
Fetching lambci/lambda:go1.x Docker container image......... 2019-03-18 21:45:46 Mounting /Users/x/go/src/x/x/invite-bp/bin as /var/task:ro inside runtime container Could not create config directory: mkdir /home/sbx_user1051: permission denied.API server listening at: [::]:5858 time="2019-03-19T01:45:47Z" level=info msg="launching process with args: [/var/task/invite]" layer=debugger could not launch process: fork/exec /var/task/invite: no such file or directory
sam version - SAM CLI, version 0.13.0
GoVersion - go version go1.12 darwin/amd64
Commands I run -

GOARCH=amd64 go build -gcflags='-N -l' -o bin/main invite/main.go
GOOS=linux GOARCH=amd64 go build -o bin/dlv ~/go/src/github.com/go-delve/delve/cmd/dlv
sam local start-api -d 5858 --debugger-path ./bin --debug-args "-delveAPI=2"

But Im stuck, been attempting to find a solution for a while now. I think I'm totally blind but any support on this would be much appreciated.

Hi @petrogdev, it appears this is more of an issue with SAM not being able to find the your invite binary correctly.

Please also build your invite/main.go file also using the Linux flag, like you’re with building the delve package!

Can we see your template, perhaps you have not specificed codeURI properly?

@jackmcguire1 - This would be template. Using this based on some examples I've seen on the net.
`
AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31
Description: >
invite-bp
Sample SAM Template for invite-bp
More info about Globals: https://github.com/awslabs/serverless-application-model/blob/master/docs/globals.rst
Globals:
Function:
Timeout: 5
Resources:
InviteGetFunction:
Type: AWS::Serverless::Function # More info about Function Resource: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#awsserverlessfunction
Properties:
CodeUri: ./bin
Handler: dlv
Runtime: go1.x
Tracing: Active # https://docs.aws.amazon.com/lambda/latest/dg/lambda-x-ray.html
Events:
CatchAll:
Type: Api # More info about API Event Source: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#api
Properties:
Path: /invite
Method: ANY
Environment: # More info about Env Vars: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#environment-object
Variables:
PARAM1: VALUE
InvitePostFunction:
Type: AWS::Serverless::Function # More info about Function Resource: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#awsserverlessfunction
Properties:
CodeUri: ./bin
Handler: dlv
Runtime: go1.x
Tracing: Active # https://docs.aws.amazon.com/lambda/latest/dg/lambda-x-ray.html
Events:
PutRequest:
Type: Api # More info about API Event Source: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#api
Properties:
Path: /invite
Method: POST
Environment: # More info about Env Vars: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#environment-object
Variables:
PARAM1: VALUE
Outputs:
ServerlessRestApi is an implicit API created out of Events key under Serverless::Function
Find out more about other implicit resources you can reference within SAM
https://github.com/awslabs/serverless-application-model/blob/master/docs/internals/generated_resources.rst#api
InviteAPI:
Description: "API Gateway endpoint URL for Prod environment for First Function"
Value: !Sub "https://${ServerlessRestApi}.execute-api.${AWS::Region}.amazonaws.com/Prod/invite/"
InviteGetFunction:
Description: "Fetching Invite"
Value: !GetAtt InviteGetFunction.Arn
InviteGetFunctionIamRole:
Description: "Implicit IAM Role created for Invite function"
Value: !GetAtt InviteGetFunctionRole.Arn
InvitePostFunction:
Description: "Creating Invite"
Value: !GetAtt InvitePostFunction.Arn
InvitePostFunctionIamRole:
Description: "Implicit IAM Role created for Invite function"
Value: !GetAtt InvitePostFunctionRole.Arn
`
I will also rerun with linux and see if that fixes anything. Thanks for the tip.

@petrogdev All of the Handler values are dlv. They should be the binary of each of your functions.

@jfuss - Thank you for responding.
So this may be crazy, but I'm attempting to have multiple functions / httpMethods point to a single lambda. I've seen the approach for every method being blown out into separate files but Im wondering if its possible to stick it into one. Have not seen any examples of this anywhere.
So for the purposes of this getting to work, I've switched back to a simple template for now following another tutorial. The following template is from that, also same issue occurs.
`
AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31
Description: >
hello-sam
Sample SAM Template for hello-sam
More info about Globals: https://github.com/awslabs/serverless-application-model/blob/master/docs/globals.rst
Globals:
Function:
Timeout: 5
Resources:
HelloWorldFunction:
Type: AWS::Serverless::Function # More info about Function Resource: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#awsserverlessfunction
Properties:
CodeUri: hello-world/
Handler: hello-world
Runtime: go1.x
Tracing: Active # https://docs.aws.amazon.com/lambda/latest/dg/lambda-x-ray.html
Events:
CatchAll:
Type: Api # More info about API Event Source: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#api
Properties:
Path: /hello
Method: GET
Environment: # More info about Env Vars: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#environment-object
Variables:
PARAM1: VALUE
Outputs:
ServerlessRestApi is an implicit API created out of Events key under Serverless::Function
Find out more about other implicit resources you can reference within SAM
https://github.com/awslabs/serverless-application-model/blob/master/docs/internals/generated_resources.rst#api
HelloWorldAPI:
Description: "API Gateway endpoint URL for Prod environment for First Function"
Value: !Sub "https://${ServerlessRestApi}.execute-api.${AWS::Region}.amazonaws.com/Prod/hello/"
HelloWorldFunction:
Description: "First Lambda Function ARN"
Value: !GetAtt HelloWorldFunction.Arn
HelloWorldFunctionIamRole:
Description: "Implicit IAM Role created for Hello World function"
Value: !GetAtt HelloWorldFunctionRole.Arn
`

@petrogdev You can do that. What I was pointing out is your example above (the one with many lambda's) had all of the Handler fields as dlv. So you were saying that your function code binary is thedlv binary.
What OS are you on?
Are the permissions of the binaries set correctly?
Are you sharing the correct drive or folders to Docker?
Are you able to invoke the function normally sam local invoke?

@petrogdev
ok firstly, within your template you're providing the handlers Handler: hello-world, when
it should be 'main' as you're running GOARCH=amd64 go build -gcflags='-N -l' -o bin/main invite/main.go which produces a binary file main...
furthermore this is no longer the place to discuss your issue, as the one at hand has been resolved.

@jfuss - valid questions and Im glad that single lambda should be achievable.

Mac OS - Mojave - 10.14.3
by permissions, are you referring to the arn? or reads/writes to the binary? The binary and directory has 775 which was bumped from 755.
I'm a little confused by this one; I don't believe I am manually specifying the drive/folders to docker.
Have not attempted this yet.

@jackmcguire1 - Fair point, I can definitely create another issue for this.
But to your point about hello-world point to main. I switched templates for the purpose of getting a sample to work instead of my original code. Sorry if I didn't make that clear.
For the context of pointing the right binaries in the template, I have followed examples and suggestions by you guys. Unfortunately the outcome is the same.

This was solved by Docker-Lambda supporting an option to configure which dlv-api version to use. You can now control this in sam cli by sam local start-api -d 5986 --debugger-path <delve folder path> --debug-args "-delveAPI=2".
Closing as the initial issue was solved.

@jfuss  As discussed I raised a new PR in the aws-docs REPO to publish official documentation about this, but it appears it has not been picked up, I would be happy if this functionality is atleast documented within this REPO as prior to the last PR i did but we abandoned.

I just tried this and I am seeing the behavior Could not create config directory even with the debug-args set as suggested here.


[FEATURE] Create APK dependency graph app

Transform the current tool project to be a desktop application, for making it easier to use. With support for Unix and windows platforms.

Currently, I have worked in a solution for making it into an application to run in Unix and Windows platforms. In following video link, you can see a video presenting this POC on Linux:
apk dependency graph app video
@alexzaitsev, I don't know what your objectives for this project if you have plans to make it into an application one day or only a terminal tool as it is today. I created this issue/feature to ask you if you have an interest in make it into a desktop app? for making it easier to use.

@victorrattis I'm very glad seeing that the project is evolving. I'm concentrated on another projects and therefore have no possibility to spend my time here.
Feel free to create any desktop app you need on the top of this :)

Thank you, I am going to work in my fork and after completing it I can do a pull request in your project to transform it into an app. =)

Closing as obsolete.


lab or exercise with cobol-java-calling

Course Details
GitHub
Description
The moment you update to COBOL 6.4 please add an exercise or lab how to call java from cobol (in batch without OO-COBOL) and vice versa.
It will be helpful for COBOL-starters to see that this is possible and how to do it.
experienced COBOL-devolopers will get value from this, too. It is much harder than shown in many presentations to this.
But it is very usefull, cause COBOL has features java will not get that quick and java has features cobol will definitely not get. To get to know how to connect the worlds will give COBOL-developers abbilities they couldn't imagine.
Currently using java is done with writing info from cobol to file. In a second step (new job or jobstep) java reads that file to work with that information. There are many reasons why java doesn't access the same data-files like COBOL did before. The most common is, that in COBOL is the business-logic is and no one will rewrite that to java 1:1.
With COBOL 6.4 there will be more flexibility - but people need to get to know it.
Problems
No response
Additional Context
No response

Hi,
Thank you for the feedback. We are currently running Enterprise COBOL for z/OS V6R4 on the lab system. However, Java and COBOL interaction are still in our roadmap as something we can look into in the future.
Will keep this in mind when there are progress being made for COBOL Communications with Java Methods.


Use Hive ANTLR grammar to parse HiveQL

This patch uses Hive ANTLR grammar to parse HiveQL instead of relying on the generated sources directly. This change enables improving the grammar to support additional constructs, functions, or clauses, and also upgrading to newer HiveQL grammars. It also integrates ANTLR plugin into Coral for general future reuse for other front-end languages.

+1. LGTM.

+1. LGTM.


⚠ ETF has degraded performance

In 5681880, ETF (https://markets.hankyung.com/equity-product/etf) experienced degraded performance:

HTTP code: 200
Response time: 7557 ms

Resolved: 거래대금 performance has improved in bd3401e.


[BUG] - An experiment that compiles but can not be serialized.

Describe the bug
We make use of the serializer in laboneq to send experiments to a queue for execution. However, some experiments do not serialize even though they can be compiled without error. This is because of how we create the oscillators for the signal calibration. We purposefully set the same uid to two oscillators that we know (because of how we generate them) are the same. However the serializer does not allow two different instances with same uid.
To Reproduce
from laboneq.simple import *
descriptor = \
"""
instruments:
  HDAWG:
  - address: DEV8755
    uid: flux
  SHFSG:
  - address: DEV12210
    uid: drive
  SHFQA:
  - address: DEV12216
    uid: readout
  PQSC:
  - address: DEV10095
    uid: device_pqsc
connections:
  flux:
    - rf_signal: q0/flux_line
      ports: [SIGOUTS/0]
  drive:
    - iq_signal: q0/drive_line
      ports: [SGCHANNELS/0/OUTPUT]
    - iq_signal: q0/drive_line_ef
      ports: [SGCHANNELS/0/OUTPUT]
  readout:
    - iq_signal: q0/measure_line
      ports: [QACHANNELS/0/OUTPUT]
    - acquire_signal: q0/acquire_line
      ports: [QACHANNELS/0/INPUT]
  device_pqsc:
    - to: flux
      port: ZSYNCS/0
    - to: drive
      port: ZSYNCS/1
    - to: readout
      port: ZSYNCS/3

"""
# device setup
device_setup = DeviceSetup.from_descriptor(yaml_text = descriptor,
                                           server_host= 0,
                                           server_port= 0)
# experiment signals
qubit = 0
signals = []
signals += [ExperimentSignal(f'drive_{qubit}'),
            ExperimentSignal(f'drive_{qubit}_ef'),]
exp_calib = Calibration()

# We set the uid of the local oscillators because we know they are the same.
lo = Oscillator(
    uid="mu_uid",
    frequency=1e9,
)
lo2 = Oscillator(
    uid="mu_uid",
    frequency=1e9,
)
osc = Oscillator(
        frequency=200e6,
        modulation_type=ModulationType.HARDWARE,
    )
exp_calib[f"drive_0"] = SignalCalibration(
    oscillator=osc,
    local_oscillator=lo,
)
exp_calib[f"drive_0_ef"] = SignalCalibration(
        oscillator=osc,
    local_oscillator=lo2,
)

exp.set_calibration(exp_calib)

#map signal
lsg = device_setup.logical_signal_groups[f"q{qubit}"].logical_signals
exp.map_signal(f"drive_{qubit}", lsg["drive_line"])
exp.map_signal(f"drive_{qubit}_ef", lsg["drive_line_ef"])

#--------------------------
# The generated experiment compiles without any error.
#--------------------------
session = Session(device_setup=device_setup)
session.connect(do_emulation=True)
result = session.run(exp)

#--------------------------
# The generated experiment does not serialize.
#--------------------------
from laboneq.dsl.serialization.serializer import Serializer
Serializer.to_json(exp) # This raises error.

Expected behavior
Experiments that can be compiled should be serializable.
Versions used:

laboneq - latest
zhinst-core 23.2

Context

[ ] Do you know a workaround for the issue?
We cache the generation of these oscillators so that they are the same.
[ ] Does the issue block your experiments?

Hi @AGaliciaMartinez, we're looking into a solution for this. In the meantime, as a workaround, is it possible to just use the lo = Oscillator(uid="mu_uid", frequency=1e9) for both the drive and drive_ef LOs in your experiment?

This is indeed the current workaround we have. It is a little inconvenient though as we would rather not keep track of the already created oscillators.


Add gateway WIP - do not merge

Codecov Report

Merging #30 (331a4ea) into develop (a44796d) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 331a4ea differs from pull request most recent head 143cbc6. Consider uploading reports for the commit 143cbc6 to get more accurate results

@@           Coverage Diff            @@
##           develop      #30   +/-   ##
========================================
  Coverage    73.42%   73.42%
========================================
  Files           64       64
  Lines         2186     2186
  Branches       310      310
========================================
  Hits          1605     1605
  Misses         581      581

Flag
Coverage Δ

batch-submitter
59.59% <ø> (ø)

contracts
91.28% <ø> (ø)

core-utils
56.91% <ø> (ø)

data-transport-layer
37.68% <ø> (ø)

message-relayer
71.69% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Ubuntu 14.10

I updated Ubuntu to Ubuntu 14.10 and glfwCreateWindow does nothing, no window, program still running. I rebuilt 3.1 from source but the problem persists. I know this is proberbly a problem with me upgrading to 14.10 as 3.1 worked previously, but I was wondering if anyone else has experienced this or knows anything about this, and/or can help me to fix this, or has any advice on debugging. I'm not sure if I can roll back. All else on the operating system seems fine but GLFW.

I wonder why there is no glfw error or any exception

I'm using x11 - is this related? https://github.com/glfw/glfw/issues/368

Hi, imaginationcoin!
I've recompiled my project on Xubuntu 14.10 (previous version was 13.10) 64-bit. GLFW 3.1 works fine.
Check that you've installed proprietary drivers after installing system (if they are needed). My card is Nvidia GeForce GTX 560Ti, so I installed proprietary nvidia driver (331.113).
Then check what OpenGL version supported by the driver and which context version your project tries to create.
Regards.

ubuntu-drivers devices
== /sys/devices/pci0000:00/0000:00:03.0/0000:02:00.0 ==
model    : GF106M [GeForce GT 445M]
vendor   : NVIDIA Corporation
modalias : pci:v000010DEd00000DD2sv00001028sd0000046Cbc03sc00i00
driver   : xserver-xorg-video-nouveau - distro free builtin
driver   : nvidia-331-updates - distro non-free
driver   : nvidia-304 - distro non-free
driver   : nvidia-331 - distro non-free recommended
driver   : nvidia-304-updates - distro non-free

ubuntu-drivers list
nvidia-304-updates
nvidia-331-updates
nvidia-331
nvidia-304
context version is default

apt-get update; apt-get upgrade; sudo apt-get install nvidia-current
Now I get an error - Xlib:  extension "NV-GLX" missing on display ":0".

I don't have "nvidia-current" installed.
331.113 driver was installed through the "Additional drivers" in the "Settings" (Ubuntu must have something similar), not using command line.
And one note. After driver installation there was some error on my system. Solution was to use:
sudo dpkg-reconfigure nvidia-331
then
sudo dpkg-reconfigure nvidia-331-uvm

It's easy to verify with a debugger if the issue is #368.
Drivers shouldn't matter unless you're requesting a version not supported by that driver. What version are you requesting?

if its nothing to do with the driver, i have the same issue, glfwCreateWindow never returns. however im on Manjaro, so a fix from ubuntu probably isnt going to help.
sorry if im hyjacking, i assumed this is the correct place.


feat(import-target): Add resolution error reason

closes #182

I was also thinking something along the lines of:
exports.messages = {
    notFound: '{{resolveError}}',
}

SGTM! 👍

mmm, these failures are interesting, as on a mac the file did resolve as that os is case insensitive 🤔

This error is getting triggered:
// This should never happen... this is just a fallback for typescript
target.resolveError ??= `"${target.name}" is not found`

can we just assert the messageId, not message?

There was no error:
https://github.com/scagood/eslint-plugin-n/blob/muted-resolution-errors/lib/util/check-existence.js#L20-L21
What is tripping the error is:
https://github.com/scagood/eslint-plugin-n/blob/muted-resolution-errors/lib/util/check-existence.js#L59
https://github.com/scagood/eslint-plugin-n/blob/muted-resolution-errors/lib/util/check-existence.js#L81

we can just assert the messageId, not the full message. wdyt?

The issue is that ./A.js will resolve sometimes, OS dependent :eyes:

ops, I misunderstood. Is there an option to config it?

But when I look at the execution results, it is returning different error messages under some os. So I suggest to only assert the messageId. am I missing something?

The issue is that on your machine, ./A does actually resolve in require
On my linux machine (which is case sensitive) it does not, so the error is correct:

I have just stripped out everything except for the enhanced-resolve checks (https://github.com/eslint-community/eslint-plugin-n/pull/231/commits/f9e454d1a24aeb168ca786ed7f41ad0e80778a8a)
(Clicking the image should take you to the tests from which the screen shot is taken)
On linux (that is case sensitive), everything is fine:

On mac (that is case insensitive), the ./A.js is resolvable:

This means that on linux, its correct that .tests/fixtures/no-missing/A.js does not get loaded:

And its correct on mac that .tests/fixtures/no-missing/A.js does get loaded:

we can ask the enhanced-resolve to support a case-sensitive option.
Up until that point, it seems that we can only ignore these test cases under certain os. The rule tester does support only property, but not skip, we will need to implement it in our side. wdyt?


Feature: Add an access denied error when drive/folder is block with security permissions

What's the Problem?
I have set on drive permistions page for a user account not be able to allow access it, that works but is not very clear why, i presume this happends for folders too. Currently it will just show as a drive with no storage and when opening says the folder is empty.
Solution/Idea
Add a popout saying that Security permistions denied access to this folder/drive
Alternatives

Priorities
No response
Files Version
No response
Windows Version
No response
Comments
No response

@Josh-65 can you add steps t reproduce?


Use default https 443 port for backend endpoint

It is better to use 443 because some network firewall policies may block access other than 443 port.

my router does not support 443 port mapping :(


Take latest Core reference and prep for Release

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.