Not Reading Entities

I am getting the following error whenever having entities in a level. Not sure what exactly it's trying to say, but no entities load in the nodes section of the level...most of the time. Sometimes on re-import it will show the entity layer with nothing in it but most of the time it doesn't show at all.
Would greatly appreciate any help! Thank you for the awesome addon!
EDIT:
Just figured out that the only time I get the issue is when resolve entity placeholders is selected! Otherwise I get no errors and the entity layer shows as an array with 1 item in it...what am I supposed to do with this?

I had to disable entity refs and enable packing, that seemed to do the trick. My entities show up now!


Added ability to publish a private test version of the package

To aid testing the UI, i've added commands and broken out the manifest to allow for two packages to be built, a release version, and a test version. The only difference between the two being one is private.

Publishing locally seems to be broken:
error: The task.json for contribution TerraformCLI could not be deserialized.Could not convert string to integer: #{GitVersion.Major}#. Path 'version.Major', line 15, position 39.

Investigating a fix.


Check if all docs have domain attribute

I looked through the newest CI errors and could reproduce them locally. The failure of test_dataset::test_process_to_text occurs when wmt22 is chosen (since this test randomly selects 10 datasets, the failure doesn’t always happen). The failure is because the domain files are shorter than the other files in some language pairs. For example, ru-en has this problem:
$ pwd
~/.sacrebleu/wmt22

$ wc -l wmt22.ru-en.domain wmt22.ru-en.src wmt22.ru-en.ALMAnaCH-Inria
    1512 wmt22.ru-en.domain
    2016 wmt22.ru-en.src
    2016 wmt22.ru-en.ALMAnaCH-Inria
    5544 total

Then, I checked the original file at https://github.com/wmt-conference/wmt22-news-systems/blob/main/xml/wmttest2022.ru-en.all.xml, and found that not all doc elements have the domain attribute.
_unwrap_wmt21_or_later should check if the length of domains matches the lengths of the other data.

Thanks for finding the source of the CI errors. I agree it is our priority to fix them, so we should perhaps merge this as soon as possible.
That said, I think I have fixed this already in March in a more general way.
Unfortunately, I didn't have time to polish it into a PR and since then @mjpost pushed another solution (not so general) and I have forgotten all the details.
I am still too busy to look at this, but if there is a volunteer, please try to merge (and review) https://github.com/martinpopel/sacreBLEU/tree/xml-domains

Thank you for the detailed explanation. I will review the branch you have been working on.

Thank you for merging my commits. Please, fix also the failing test, i.e. add domain=ALL  to the expected output.

I'm trying to fix the errors, but it might take some time.

I would hope it is a matter of adding domain=ALL to the two lines here and here (or alternatively prevent the printing). Unfortunately, I am not capable to try it now.

Thank you for your advice. I was able to pass the tests by adding domain=ALL to the four lines and removing a couple of lines. I’m not sure if removing those lines is acceptable. I’ll look for another way to solve the CI failures.

The CI errors are fixed. Could you please review this PR?

Thank you very much, once again. The last commits were exactly the missing pieces which prevented me to finish the PR in March. I am happy I could merge it into the master now.

My pleasure.


feat(rust): node create can be used with custom vault and identity

Add new arguments to node create to pass a custom vault and identity that will be set as the default for the new node.
Open questions
If the user runs the command ockam node create --vault v1 --identity idt1 on a fresh install:
a. should the command return an error telling the user that the passed vault/identity don't exist?
b. or the command should create the vault/identity?
I would say a because b could lead to errors if the user mistypes the vault/identity name.

yes,  agree that if the user specify some identity/vault and it doesn't already exist, it must be an error :+1:


discrepancy between manually setting needs_extra_options and use of add_extra_option

I am using add_extra_option to add custom fields to needs.
If I define needtable I can see values for those fields and they are part of the needs.json.
In another document, using needs_external_needs to reference multiple external needs sources, I want to create the same needtable  but here the values for custom fields are empty.
When running with debugger it shows that as the fields are not part of the app.config.needs_extra_options value (which is empty) at line 83 in external_needs
Thus when adding the fields with needs_extra_options directly, the issue does not appear and I can see custom fields for external needs in needtable.

Thanks for reporting.
For me, this is the expected behavior.
There is only one master for the configuration, the conf.py file.
If you import needs from an external source, your conf.py must also contain a configuration that supports the imported data.
There is no automatic way to analyze imported data, extract missing configuration parts and add them to the one given by conf.py.
There were some discussions in the past to export also the used configuration, so that a project, which imports these data, can update its configuration with the missing parts. But it was just an idea, with no implementation yet.
In all of my bigger projects, this behavior is wanted by the responsible project leaders/teams. As they are importing data from 5-10 different docs and they want to keep their config under their control.
So for me, this is not a bug, more a feature ;)
I close this issue already. If you see it differently feel free to reopen it.

My concern was initially that add_extra_option says in its doc that it is equivalent to manually using app.config.needs_extra_options. Thus to configure my document I preferred to use the api way instead of using more internal functions.
I agree the configuration cannot be automatic, just I would have thought using add_extra_option would have the same behavior and would be the cleanest way of adding extra options.

Argh, got your problem now.
And you are right, this is a bug.
add_extra_option adds the new config to our internal Config class.
But the external_needs code is taking it from the app.config.needs_extra_option config value, which gets not updated by the API call.
I reopen the issue. And thanks for the clarification.

not sure if it's a separate issue or an incidence of this bug, but when using e.g. sphinx-test-reports which uses add_extra_option() to add some fields such as result, those fields are not directly usable by expicitly written
.. need::
  ...
  :result: something

directives because add_extra_option doesn't seem to be updating the NeedDirective.option_spec in the way that sphinx_needs.load_config does.


Warning: Encountered known unsupported method torch.Tensor.format

Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
I know it's an issue caused by the unrealized method.
But I really don't understand where on earth did I use the "Tensor.format", because I have read every single line of my model code and I didn't find any use of "{}".format(model)
Could anyone help me...Thanks so much...
My environment:

NVIDIA Jetson nano
tensorrt <IP_ADDRESS>

All the warning are listed here:
Warning: Encountered known unsupported method torch.is_grad_enabled
Warning: Encountered known unsupported method torch.get_default_dtype
Warning: Encountered known unsupported method torch.get_default_dtype
Warning: Encountered known unsupported method torch.Tensor.has_names
Warning: Encountered known unsupported method torch.is_grad_enabled
Warning: Encountered known unsupported method torch.is_grad_enabled
Warning: Encountered known unsupported method torch.Tensor.iter
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.item
Warning: Encountered known unsupported method torch.Tensor.format
Warning: Encountered known unsupported method torch.Tensor.tolist
Warning: Encountered known unsupported method torch.Tensor.has_names
Warning: Encountered known unsupported method torch.is_grad_enabled
Warning: Encountered known unsupported method torch.Tensor.repr

I have found where such warnings come from: in xxx/site-packages/torch/tensor.py(411)format()
def __format__(self, format_spec):          if self.dim() == 0:              return self.item().__format__(format_spec)
But I dont't know where I use the format function...

I've got it, the only reason is that I called print(inputs) in torch2trt_dynamic.py line 514

Thanks for the report, I will add some warnings about print Tensor.


LVM datastore migration does not work

Description
Here is specific check for that
https://github.com/OpenNebula/one/blob/release-5.8.0/src/tm_mad/fs_lvm/mv#L86-L88
if [ "${TYPE}" != "BLOCK" ]; then
    exit 0
fi

But disk type is always
TYPE = "FILE"

To Reproduce

Configure lvm datastore according the documentation
Instantiate new VM
Shutdown it, and try to migrate datastore

Expected behavior
VM will be migrated with all data
Actual behavior
Only metadata directory will be moved, VM will continue use logical volume from the old datastore
Details

Affected Component: Storage drivers
Hypervisor: KVM
Version: 5.6 5.8

Additional context
Add any other context about the problem here.

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

There is more detailed discussion about this issue:
https://forum.opennebula.org/t/why-images-ds-parameters-affects-system-ds/7072

Closing as duplicate of #2359


Problem: Expression sharing

Sometimes it is necessary be able to give the same expression to two
different parties, while avoiding potentially hairy lifetime management
issues.
Solution: derive Clone for Expression

Any chance of getting this into upstream? Thanks! Please let me know if you have any questions or concerns.

Thanks!


Config error connecting to clickhouse on port 80

Hello, we are trying to connect to our clickhouse cluster via chproxy which we have exposed on port 80.
However when we try to do that, we are seeing the following error:
        PUT /connectors/clickhouse-sink.cdc.structured-trait-updates.v0/config
        returned 400 (Bad Request): Connector configuration is invalid and
        contains the following 1 error(s):

        Invalid value 80 for configuration port: Value must be at least 1024

        You can also find the above list of errors at the endpoint
        `/connector-plugins/{connectorType}/config/validate`

Seems like the port number is restricted here:
https://github.com/ClickHouse/clickhouse-kafka-connect/blob/f408f62ba0d380d29b44eac7e1636103e5d826bb/src/main/java/com/clickhouse/kafka/connect/sink/ClickHouseSinkConfig.java#L108
Is there a reason for these bounds or can the range be expanded?
In meantime we will build from source, bumping that range from 1to Integer.MAX_VALUE
Thanks!

In Linux, in order to bind to port less than 1024 you need root access, so if you running chproxy internally I would recommend binding it to another port. I will fix it

ok, thank you for the info, i suppose we will have to update our networking to work within this limitation


Auto start doesn't work for native notebooks

Makes startup take all that much longer.

This is actually not working correctly. It puts up errors on auto start. The old code would ignore errors.

This is actually not working correctly. It puts up errors on auto start. The old code would ignore errors.

Meaning if you have an error starting a kernel, it shouldn't just show up randomly. It should only show if you click run a cell.

Meaning if you have an error starting a kernel, it shouldn't just show up randomly. It should only show if you click run a cell.

puts up errors on auto start. The old code would ignore errors.

Can you let me know what you did to get errors? Is it an invalid kernel or what?

puts up errors on auto start. The old code would ignore errors.

Can you let me know what you did to get errors? Is it an invalid kernel or what?

I have a kernel without ipykernel installed. Well just an interpreter. It's set a the default for a notebook. On opening the notebook an error pops up.

I have a kernel without ipykernel installed. Well just an interpreter. It's set a the default for a notebook. On opening the notebook an error pops up.

This still isn't working? I believe I merged your latest changes. I still get the error to come up without clicking on anything.

This still isn't working? I believe I merged your latest changes. I still get the error to come up without clicking on anything.

Unable to replicate, please could you re-test.

I believe I fixed it with the subsequent submission. We should probably have somebody else validate.

@DonJayamanne @rchiodo This didn't validate for me. When I start up VS Code with a native notebook I see the message that it's looking to start a server due to preload conditions. But I don't see an actual server start. When I execute the first cell, I actually see the message for the server starting hit:
[I 10:31:22.120 NotebookApp] The Jupyter Notebook is running at:
[I 10:31:22.121 NotebookApp] http://localhost:8888/?token=5578ca9da346e3451deb88eefcb727316bbef761f33788ce

@IanMatthewHuff  does it work for raw?

Validated and seems to work for me:

Raw

Open a notebook and kernel will get selected by VS Code
A kernel is auto started
Test: Wait for a few seconds, then run a cell it should run immediately

Jupyter (non-Raw)

Open a notebook and kernel will get selected by VS Code
Jupyter server is auto started auto started
Test: Wait for a few seconds, then run a cell it should not start jupyter, but Kernel will get started (this cannot be avoided, unless we start Jupyter server with the exact same default kernel).
We should not have to start the server, but use existing server

I managed to validate both while debugging, i.e. confirming at a lower level that it works as expected.

Validated


Implement SpurResource class

As per #58
Additional changes:

Added a custom SpurRequest class as well that inherits SimPy's Request class; this custom class also takes in the agent making the request, so that in the _do_put() method of SpurResource, the associated component's check_usage_eligibility() method could be called with the specific agent.
The accept_agent() method is now called directly within the _do_put() method, such that if the request is successful, the agent is added into both the resource's list of users and also the component's own data structures as well; this synchronized update eliminates event ordering issues arising from concurrency.
Related to the above, release_agent() is now invoked in the main tour traversal loop of the Train class, instead of being part of the transfer_to() method.

If you want to commit/push the two small changes (method name and type hinting) we can wrap this one up.

If you want to commit/push the two small changes (method name and type hinting) we can wrap this one up.

Renamed to can_accept_agent()


OpenScan Integration

I would like to work on this;
Initially I want to build a separate MacOS app that packages OpenScan data in the zip/manifest format used by Obture.
I built an OpenScan mini recently. https://en.openscan.eu/
The iPhone camera is amazing, but OpenScan has a couple advantages.
OpenScan Pros:

Polarization of light source opposite camera nearly eliminates all reflections in capture
Easier to take LOTS of photos of single object since it’s automated
No accelerometer, but can calculate gravity from known location of camera

OpenScan Cons:

Can’t handle large objects
Gotta 3Dprint/solder/build it

After MVP possible big wins:

Focus stacking processing

Generate depthmap with focus stacking
Always in-focus images https://github.com/PetteriAimonen/focus-stack

After some investigation and now that PhotogrammetrySession is available on iOS... I think trying to use the OpenScan hardware controlled by an iPhone is what I'm gonna attempt to play with


Slashes in property names are treated as path delimiters in path objects for nested locations

Hi,
In the documentation, there are three examples of using store.attachReducers():
store.attachReducers({
    some: {
        path: {
            to: {
                dynamicReducer
            }
        }
    }
} )

store.attachReducers({ 'some.path.to': { dynamicReducer } } } })
store.attachReducers({ 'some/path/to': { dynamicReducer } } } })
The last two examples use a string to specify the path and in the last one, slash is used as the delimiter. But when using the first approach to describe the path of a nested location, it seems like slashes in the property names of the path object are treated as path delimiters as well. The thing is that we're using slashes in some of the property names in the state tree.
Here's an example of what's happening for us:
store.attachReducers({
    routes: {
        '/route1/section1': dynamicReducer
    }
} )

...will end up like this:
{
    routes: {
        '': {
            route1/section1': {...}
        }
    }
}

Hi @anndroow,
I can see how this might be causing you some headaches... Sorry about that!
The problem here is how we store the structure internally.  Basically, the object and / syntax are helpers for us to get to the . format.  You can see how we convert them here.  So for your example, it should be no different than calling attachReducers like so
store.attachReducers({
  'routes..route1.section1': dynamicReducer
} )

Obviously the double . is not what was intended here.  I've also just noticed a bug on this line where it's only going to replace the first occurrence of the slash and not all of them (although I think this would actually make your particular scenario worse).
So what can we do about it?
The option that comes to mind are to change the logic to only consider slashes when the whole structure is slash delimited paths.  The logic for dot delimited paths would probably change to be consistent with the slash version and then the logic for the object structure would not consider either of them when resolving the structure.
Here are some examples:

store.attachReducers({
  'routes.route1.section1': dynamicReducer
} )

becomes:
{
  routes: {
    route1: {
      section1: {...}
    }
  }
}

store.attachReducers({
  'routes/route1/section1': dynamicReducer
} )

becomes:
{
  routes: {
    route1: {
      section1: {...}
    }
  }
}

store.attachReducers({
  routes: {
    route1: {
      section1: dynamicReducer
    }
  }
} )

becomes:
{
  routes: {
    route1: {
      section1: {...}
    }
  }
}

store.attachReducers({
  'routes./route1/section1': dynamicReducer
} )

becomes:
{
  routes: {
    '/route1/section1': {...}
  }
}

store.attachReducers({
  routes: {
    '/route1/section1': dynamicReducer
  }
} )

becomes:
{
  routes: {
    '/route1/section1': {...}
  }
}

I would consider this a breaking change and would need to be a major version bump.
My biggest concern with this is that there might be some unexpected behaviour when calls are made with structures that themselves have dynamic shapes.
For example, consider this call:
store.attachReducers({
  'routes/route1/section1': dynamicReducer1
} )

The result of this call would change dramatically if this second reducer was optionally attached at the same time:
store.attachReducers({
  'routes/route1/section1': dynamicReducer1,
  admin: {
    'routes/route2/section2': dynamicReducer2,
  }
} )

This isn't a deal breaker on a change like this for me, but it would need to be considered whether which would be the more common use case and be carefully documented what the behaviour is.
As always, I'm open to anyone's ideas on these types of things.

Hi,
Thanks for the quick response. Your examples of the fixes for this issue make sense for me and I understand that it needs to be a new major for these changes.
Regarding the last concern, maybe introducing a configuration for this could be something so you could choose the behavior you want.
Another thing related to this, when using withReducer(), is it supposed to not be able to use the object approach to describe the path? Looks like just withReducer(reducer, "some/path") is supported right now :)
Also, I have another question regarding the usage of withReducer, but I'll add another issue for that to not go off-topic :)
Thanks again for the support.
Cheers!


Execution failed for task ':react-native-navigation:compileReactNative63DebugKotlin'.

Description
while running npx react-native run-android
Version
0.63.5
Output of npx react-native info
System:
OS: macOS 12.5
CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Memory: 65.30 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 8.17.0 - ~/.nvm/versions/node/v8.17.0/bin/node
Yarn: Not Found
npm: 6.14.10 - ~/Desktop/Work/RNMobileApp/node_modules/.bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 15.0, DriverKit 20.4, macOS 11.3, tvOS 15.0, watchOS 8.0
Android SDK: Not Found
IDEs:
Android Studio: 2021.2 AI-212.5712.43.2112.8609683
Xcode: 13.0/13A233 - /usr/bin/xcodebuild
Languages:
Java: 11.0.17 - /usr/bin/javac
Python: Not Found
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: ^0.63.5 => 0.63.5
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
npx react-native run-android
Snack, code example, screenshot, or link to a repository
my package.json file :
{
"name": "@halaplaytech/androidapp_india",
"version": "1.1.0",
"private": true,
"scripts": {
"android": "react-native run-android",
"ios": "react-native run-ios",
"start": "react-native start",
"test": "jest",
"lint": "eslint .",
"postinstall": "patch-package"
},
"dependencies": {
"@react-native-async-storage/async-storage": "^1.13.4",
"@react-native-community/art": "^1.2.0",
"@react-native-community/clipboard": "^1.5.1",
"@react-native-google-signin/google-signin": "^6.0.0",
"@react-native-picker/picker": "^1.16.1",
"@twotalltotems/react-native-otp-input": "^1.3.11",
"antd-mobile-rn": "2.3.3",
"appcenter": "4.1.0",
"appcenter-analytics": "4.1.0",
"appcenter-crashes": "4.1.0",
"axios": "^0.26.1",
"crypto-js": "3.3.0",
"expo": "40.0.0",
"fetch": "^1.1.0",
"form-data": "^3.0.0",
"html-entities": "^2.0.2",
"install": "0.13.0",
"lodash.debounce": "4.0.8",
"mobx": "6.0.4",
"mobx-react": "7.0.5",
"moment": "2.29.1",
"native-echarts": "0.5.0",
"npm": "6.14.10",
"numeral": "2.0.6",
"patch-package": "^6.4.7",
"payu-non-seam-less-react": "^2.4.0",
"react": "17.0.1",
"react-native": "^0.63.5",
"react-native-android-location-enabler": "^1.2.2",
"react-native-android-sms-listener": "^0.8.0",
"react-native-backdrop": "^2.1.2",
"react-native-chart-kit": "^6.11.0",
"react-native-checkbox": "2.0.0",
"react-native-code-push": "^7.0.1",
"react-native-collapsible": "1.5.3",
"react-native-datepicker": "1.7.2",
"react-native-device-info": "^7.3.1",
"react-native-document-picker": "^8.1.1",
"react-native-elements": "3.4.1",
"react-native-exit-app": "1.1.0",
"react-native-fbsdk-next": "4.2.0",
"react-native-fetch-blob": "0.10.8",
"react-native-firebase": "5.6.0",
"react-native-flash-message": "^0.1.23",
"react-native-geocoding": "0.5.0",
"react-native-geolocation-service": "^5.3.0-beta.2",
"react-native-gesture-handler": "^1.10.3",
"react-native-heic-converter": "1.3.0",
"react-native-image-crop-picker": "^0.35.2",
"react-native-image-picker": "3.2.1",
"react-native-iphone-x-helper": "1.3.1",
"react-native-keyboard-aware-scroll-view": "0.9.3",
"react-native-linear-gradient": "2.5.6",
"react-native-loading-spinner-overlay": "2.0.0",
"react-native-material-menu": "~1.2.0",
"react-native-material-ui": "1.30.1",
"react-native-message-bar": "2.0.10",
"react-native-modal": "^11.10.0",
"react-native-moengage": "^7.4.1",
"react-native-navigation": "^7.14.0",
"react-native-onesignal": "^4.4.1",
"react-native-pager-view": "5.1.8",
"react-native-picker-select": "^8.0.4",
"react-native-popup-dialog": "0.18.3",
"react-native-progress": "4.1.2",
"react-native-progress-circle": "^2.1.0",
"react-native-simple-radio-button": "2.7.4",
"react-native-sms-retriever": "^1.1.1",
"react-native-snap-carousel": "3.9.1",
"react-native-splash-screen": "^3.2.0",
"react-native-svg": "^12.1.1",
"react-native-svg-charts": "^5.4.0",
"react-native-swiper": "^1.6.0-nightly.5",
"react-native-vector-icons": "7.1.0",
"react-native-view-more-text": "^2.1.0",
"react-native-webview": "^11.26.0",
"react_native_mqtt": "^1.3.1",
"realm": "10.1.2",
"rn-content-loader": "0.0.6",
"rn-sliding-up-panel": "1.3.1",
"rn-viewpager": "^1.2.9",
"singular-react-native": "^3.1.10",
"socket.io-client": "2.4.0",
"victory-native": "^35.5.5"
},
"devDependencies": {
"@babel/core": "^7.12.10",
"@babel/plugin-proposal-decorators": "^7.12.13",
"@babel/runtime": "^7.12.5",
"@react-native-community/eslint-config": "^2.0.0",
"babel-jest": "^26.6.3",
"eslint": "^7.18.0",
"jest": "^26.6.3",
"jetifier": "^2.0.0",
"metro-react-native-babel-preset": "^0.64.0",
"react-test-renderer": "16.13.1"
},
"jest": {
"preset": "react-native"
}
}

Hey @arihantop I am facing the same issue.
Could you please share with me what fix did you apply? 😄


Proposal : Get text with screenshot

Description of the new feature / enhancement
Implement a way to copy text into the clipboard doing a screenshot. May be a different command from regular screenshot because it can be annoying.
Scenario when this would be used?
When you see some text in a photo / video and you don't have the change to copy it.
Supporting information
No response

There's a browser plugin that can do this: project Nafta. Maybe that's a quick solution?


Use generics to limit event types in on(), once() and un()

This pull request adds another improvement regarding type safety: The ol/Observable methods on(), once() and un() now only accept the event types that are actually available for the respective class.
In a code-aware editor, registering a listener on a Modify interaction would now look like this:

My medium term goal with changes like this is to get rid of the *EventType enums (which are not part of the API anyway), and use string constant union types instead. Another possible improvement along these lines would be to use generics to show the correct signature of the listener function in on(), once() and un(), i.e. the correct *Event of the listener argument.
@simonseyock I think you might want to take a look at this pull request, and maybe you are also interested in working towards the goals I mentioned above.

The correct signature would be great. I liked that about working with the @hanreev/ol-types. There for each event exists a method overload in the declaration somewhat like this:
on('singleclick', (e: MapBrowserEvent) => void);
on('postcompose', (e: RenderEvent) => void);

This might not possible at all with jsdoc, as the overloading capabilities are different in declaration and implementation mode in typescript.
If it is possible it is probably not possible to do this by generic parameters.
The best alternative I see at the moment is probably a second generic parameter that defines the actual types of the event objects. This could then result in something like this:
on('singleclick' | 'postcompose', (e: MapBrowserEvent | RenderEvent) => void);

or (maybe better as you maybe  would not need a guard inside the function):
on('singleclick' | 'postcompose', (e: MapBrowserEvent) => void |  (e: RenderEvent) => void);

Thanks for sharing your experience here @simonseyock. What's missing in TypeScript's JSDoc support is function overloads. One thing I have in mind that will make it easier is a refactoring of how we handle events. I'm envisioning that each class that fires events has a dedicated event object (does not need to be a class like it is now), instead of the map having MapEvent, MapBrowserEvent, ObjectEvent etc.. This will also allow us to remove a lot of custom JSDoc plugin code.

Yes I can definitely do that. I played around a little with typescript typing, and something like this is possible:

But I don't think this will really help as there still is no way to iterate over multiple of these tuples and then generate overloaded functions out of that.

If there is just one type for every class, the typing would get fuzzier or not? We would need to have many optional properties on the events and subsequently have a check for every property in strictly typed code.

If there is just one type for every class, the typing would get fuzzier or not? We would need to have many optional properties on the events and subsequently have a check for every property in strictly typed code.

Fuzzier for sure. Not sure about the checks for the properties though. But maybe not such a good idea anyway, as it just shifts the fuzziness to a different place.

I looked a little bit into how to type this, and this form probably is not really posssible:
on('singleclick' | 'postcompose', (e: MapBrowserEvent) => void |  (e: RenderEvent) => void);

(maybe with more compicated stuff like this: https://stackoverflow.com/questions/59535995/parameters-generic-of-overloaded-function-doesnt-contain-all-options/59538756#59538756 )
Overall from a strictly typed perspective It would be nice to have distinctive methods for every event. But I am not sure if I really like that:
onSingleClick(listener: (e: MapBrowserEvent) => void));
onPostCompose(listener: (e: RenderEvent) => void));

This would also need then the corresponding un variants. Internally it could be implemented by calling a protected register function that works with strings like before. Or this methods could be additions.

Fuzzier for sure. Not sure about the checks for the properties though. But maybe not such a good idea anyway, as it just shifts the fuzziness to a different place.

I was thinking about the user code.
map.on('singleclick', (e: MapEvent) => {
  const coordinate = e?.coordinate;
  const dragging = e?.dragging;
});

But worse in my opinion is that the IDE cannot be sure anymore that e has either coordinate and dragging or frameState and context but never a mixture of those.

@simonseyock Maybe it is possible to define overloads for our on(), once() and un() signatures. https://github.com/microsoft/TypeScript/issues/25590#issuecomment-561493756 appears to be very related.

Ah that looks promising indeed!
I will look into that.
One question arises immediately is how or if this will affect the produced documentation.

Just a quick try, and it appears to work correctly:
diff --git a/src/ol/PluggableMap.js b/src/ol/PluggableMap.js
index 578d924f98..939754837b 100644
--- a/src/ol/PluggableMap.js
+++ b/src/ol/PluggableMap.js
@@ -126,13 +126,17 @@ import {removeNode} from './dom.js';
  * {@link module:ol/Map~Map#setView}.
  */

+/** @typedef {(type:import("./MapBrowserEventType").Types, listener:(event:MapBrowserEvent) => boolean) => import("./events.js").EventsKey|Array<import("./events.js").EventsKey>} MapBrowserEventSignature */
+/** @typedef {(type:import("./MapEventType").Types, listener:(event:MapEvent) => boolean) => import("./events.js").EventsKey|Array<import("./events.js").EventsKey>} MapEventSignature */
+/** @typedef {MapBrowserEventSignature & MapEventSignature} EventSignature */
+
 /**
  * @fires import("./MapBrowserEvent.js").MapBrowserEvent
  * @fires import("./MapEvent.js").MapEventl/PluggableMap.js
  * @fires import("./render/Event.js").default#precompose
  * @fires import("./render/Event.js").default#postcompose
  * @fires import("./render/Event.js").default#rendercomplete
- * @extends BaseObject<'change:layergroup'|'change:size'|'change:target'|'change:view'|'precompose'|'singleclick'|'click'|'dblclick'|'pointerdrag'|'pointermove'|'postrender'|'movestart'|'moveend'|'postcompose'|'rendercomplete'>
+ * @extends BaseObject<'change:layergroup'|'change:size'|'change:target'|'change:view'|'precompose'|'postcompose'|'rendercomplete'|import("./MapBrowserEventType").Types|import("./MapEventType").Types>
  * @api
  */
 class PluggableMap extends BaseObject {rEventType").Types, listener:(event:MapBrowserEvent) @@ -144,6 +148,9 @@ class PluggableMap extends BaseObject {("./events.js").EventsKey>} MapBro serEventSignature */
     const optionsInternal = createOptionsInternal(options);r:(event:MapEvent) => boolean) => import("./events.js").EventsKey|Array<import("./events.js").EventsKey>} MapEventSignature */
+    /** @type {EventSignature} */ature & MapEventSignature} EventSignature */
+    this.on;
+/**
     /** @private *//MapBrowserEvent.js").MapBrowserEvent
     this.boundHandleBrowserEvent_ = this.handleBrowserEvent.bind(this);
  * @fires import("./render/Event.js").default#precompose
@@ -448,6 +455,10 @@ class PluggableMap extends BaseObject {
     );res import("./render/Event.js").default#rendercomplete
   }

+  /** @type {MapBrowserEventSignature} */
+  /** @type {MapEventSignature} */
+  /** @function on */
+
   /**
    * @abstract
    * @return {import("./renderer/Map.js").default} The map renderer

I think with this approach, we can even revert this pull request.
To make it work with the documentation, no change should be needed. Just use
/***
 */

syntax (3 asterisks) for all added comments from the above diff, then JSDoc will ignore the comments, but TypeScript will still respect them.

Nice.
I would use then some helper type like this (should work, not tested):
/**
 * @template Types, Event
 * @typedef {(Types, listener:(event: Event) => boolean) => import("./events.js").EventsKey|Array<import("./events.js").EventsKey>}
 */

@simonseyock Sounds good to me. Would be great if you could start a pull request. No problem is the first commit is git revert b6c143deb294a12c49a2b76e9643e3bc37d9e169 -m1.

I encountered a problem with this. If the base class already contains a method with the same name but broader signature, it won't create declarations for the new signatures. The autocompletion seems to work, though. But this is probably not true for a typescript project that would just import the declaration file.
This produces a .d.ts that has the desired typings:
Example 1
While this doesn't:
Example 2
I will think more about this later.

I tried this in a typescript project and this is true - as the typescript project will only consider the declaration but not the implementation.
A solution for this would be to rename the on function in Observable and make it protected. And then work like this:
constructor() {
  /** @type {Signature} */
  this.on = (type, listener) => this._on(type, listener);
}

But then the ApiDoc is missing.

Is there a possibility to insert apidoc for a function that is only declared in the constructor like that?

Not without a custom plugin, I'm afraid.

I am still thinking about the onSingleClick syntax. It would also make documenting certain events easier. I think it would be a very straight forward approach with easy type syntax while producing boiler plate code.
I will think about a custom plugin.

@simonseyock To document something like
/** @type {Signature} */
this.on = (type, listener) => this._on(type, listener);

you could try something like
/**
 * @type {Signature}
 * @param {string|Array<string>} type Type.
 * @param {ListenerFunction} listener Listener.
 * @return {EventsKey|Array<EventsKey>} Event key for `Observable.unByKey`.
 */
this.on = (type, listener) => this._on(type, listener);

I agree that dedicated methods like onSingleClick() would make everything more straightforward, but I have mixed feelings about actually doing it. It would be better if we could make it work with the function overload approach.

I was thinking maybe adding some plugin that adds methods to the apidoc for annotations like this:
class SomeClass {
  /**
   * @function on
   * @param {import("./MapBrowserEventType").Types|import("./MapEventType").Types} type Type.
   * @param {(e: MapBrowserEvent) => boolean|(e: MapEvent) => boolean} listener Listener.
   * @return {EventsKey|Array<EventsKey>} Event key for `Observable.unByKey`.
   */
}

This would a function to the apidoc without needing to have a corresponding symbol in the actual code.
Then it might even be possible to add the same function multiple times to document them differently:
class SomeClass {
  /**
   * @function on
   * @param {'singleclick'|'click'} type Type.
   * @param {(e: MapBrowserEvent) => boolean} listener Listener.
   * @return {EventsKey|Array<EventsKey>} Event key for `Observable.unByKey`.
   */

  /**
   * @function on
   * @param {'movestart'|'moveend'} type Type.
   * @param {(e: MapEvent) => boolean} listener Listener.
   * @return {EventsKey|Array<EventsKey>} Event key for `Observable.unByKey`.
   */
}

@ahocevar we would need a plugin for your approach as well to have that appear in the apidoc.

A solution for this would be to rename the on function in Observable and make it protected.

This actually does not really solve the problem as we still can have have base classes that would define an on function like Interaction. And then again the .d.ts files only pick up the typing of the base class.
See Example 3

I agree that dedicated methods like onSingleClick() would make everything more straightforward, but I have mixed feelings about actually doing it. It would be better if we could make it work with the function overload approach.

I don't love it either. This would be a really big change in the API. But it might be possible to deprecate on before removing it in a later version.

This actually does not really solve the problem as we still can have have base classes that would define an on function like Interaction. And then again the .d.ts files only pick up the typing of the base class.

I would consider this a bug in the declaration generation of TypeScript. Would you mind creating an issue on https://github.com/microsoft/typescript with a reproducible test case?

This would a function to the apidoc without needing to have a corresponding symbol in the actual code.

The @function on approach works already, you just have to add an @api annotation.

I would consider this a bug in the declaration generation of TypeScript. Would you mind creating an issue on https://github.com/microsoft/typescript with a reproducible test case?

https://github.com/microsoft/TypeScript/issues/44693
This actually started to appear somewhere around v3.9.7

This actually works:
/**
 * @function
 * @param {import("./MapBrowserEventType").Types} type Type.
 * @param {import("./events").ListenerFunction<import("./MapBrowserEventType").default>} listener Listener.
 * @return {EventsKey|Array<EventsKey>} Event key for `Observable.unByKey`.
 * @api
 *//**
 * @function
 * @param {import("./MapEventType").Types} type Type.
 * @param {import("./events").ListenerFunction<import("./MapEventType").default>} listener Listener.
 * @return {EventsKey|Array<EventsKey>} Event key for `Observable.unByKey`.
 * @api
 */
PluggableMap.prototype.on;

Should I create this multiple entries?

Should be enough to remove the @api annotation from the existing one.

Also note that the above syntax for overloading is only understood by JSDoc, not by TypeScript.

Also note that the above syntax for overloading is only understood by JSDoc, not by TypeScript.

Yeah, I wanted to use that fact. But if I indeed assume that the overriding in the declaration file is a bug, then we can just keep the documentation on Observable.
But I just want to note that this would be possible as well:
    /**
     * @param {import("./MapBrowserEventType").Types} type Type.
     * @param {function(import("./MapBrowserEventType").default): (void|boolean)} listener Listener.
     * @return {import("./events").EventsKey|Array<import("./events").EventsKey>} Event key for `Observable.unByKey`.
     * @api
     *//**
     * @param {import("./MapEventType").Types} type Type.
     * @param {function(import("./MapEventType").default): (void|boolean)} listener Listener.
     * @return {import("./events").EventsKey|Array<import("./events").EventsKey>} Event key for `Observable.unByKey`.
     * @api
     *//***
     * @type {EventSignature}
     */
    this.on;


Cleanup remote config

🗃 Github Issue Or Explanation for this PR. (What is it supposed to do and Why is needed)
No Issue. Tech Task
✅ Checklist

[x] Github issue details are up to date for people to QA.
[x] I have tested all my changes.

🕵♂ Notes for Code Reviewer
Remote Config singleton is now up to date and ready to be used.
This is what we will be using for endpoints, feature flags, etc
👯♀ Paired with
Solo

@n13  I made important changes here to our default URLs and endpoint etc.
Please review this PR and make sure the remote config we have in Firebase are correct.
@buildc0de  This is potential breaking code. We need some sanity test on this task before we can merge it.
How are we doing on the manual tests ?

Closing for now.
Ill redo this when we are done making changes to remoteConfig

@buildc0de This is potential breaking code. We need some sanity test on this task before we can merge it.
How are we doing on the manual tests ?

So far, I've been doing manual testing of each specific resolved issue and posting test cases in the tickets. I don't have any more generic release test cases just yet 🤓 Sounds like this change provides enough inspiration to start on those 😜 I am planning to connect with Jason some time this week.

@buildc0de This is potential breaking code. We need some sanity test on this task before we can merge it.
How are we doing on the manual tests ?

So far, I've been doing manual testing of each specific resolved issue and posting test cases in the tickets. I don't have any more generic release test cases just yet 🤓 Sounds like this change provides enough inspiration to start on those 😜 I am planning to connect with Jason some time this week.

This should be priority, we have a release coming up tomorrow and we need to test the release.
Sounds like a good opportunity to write down the test scenarios used in the release.


added windows 11

added windows 11

Learn Build status updates of commit 258b27e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows/security/threat-protection/security-policy-settings/administer-security-policy-settings.md
:white_check_mark:Succeeded

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


Feature Request: Objects > Custom Objects

Request to create a provider to create Custom Objects as defined below (taken from GUI):
Objects > Custom Objects:

Data Patterns
Spyware
Vulnerability
URL Category

Reference:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-web-interface-help/objects/objects-custom-objects.html

Currently need this feature too, if pango supports it, I could try to fork this provider to add it

+1

+1

Custom data patterns added in v1.7.0.

Custom data patterns added in v1.7.0.

Really need to be be able to create URL Categories with this provider.


Created ShareRepo and ShareRepoTest

Hi @myothiha09, thanks for the pull request. Before we can merge it, we need you to sign our Contributor License Agreement. You can do so electronically here: http://opensource.box.com/cla
Once you have signed, just add a comment to this pull request saying, "CLA signed". Thanks!


Add VelenPublicWebCrawler to bots list

See github issue: https://github.com/WhichBrowser/Parser-PHP/issues/540

Coverage increased (+0.02%) to 99.97% when pulling 940bb4498f6948b2e2cb2bea4347b8fa66b4e243 on ayumi-cloud:VelenPublicWebCrawler into 880b9fa797401d14b28956442944c3daa70240ff on WhichBrowser:master.

Fixed in eae6bd124253665019c7544be8217a7375f59606

Fixed in eae6bd124253665019c7544be8217a7375f59606


Installation fails on JuliaPro Windows (<IP_ADDRESS>)

I've tried on two different computers (windows 10) to install Makie, which failed. I did the following; install a fresh installation of JuliaPro build 426, and then directly firing up Juno and trying to install Makie, which errored:
(JuliaPro_v<IP_ADDRESS>) pkg> add Makie
ERROR: The following package names could not be resolved:
 * Makie (not found in project, manifest or registry)
Please specify by known `name=uuid`.

When I tried to install it directly from github, it fails in a similar way:
(JuliaPro_v<IP_ADDRESS>) pkg> add https://github.com/JuliaPlots/Makie.jl
   Cloning git-repo `https://github.com/JuliaPlots/Makie.jl`
  Updating git-repo `https://github.com/JuliaPlots/Makie.jl`
[ Info: Assigning UUID fa4ef387-2a53-5d25-8973-a11c97d17949 to Makie
 Resolving package versions...
ERROR: The following package names could not be resolved:
 * AbstractPlotting (not found in project, manifest or registry)
 * FreeType (not found in project, manifest or registry)
 * FreeTypeAbstraction (not found in project, manifest or registry)
 * GeometryTypes (not found in project, manifest or registry)
 * GLFW (not found in project, manifest or registry)
 * ModernGL (not found in project, manifest or registry)
 * QuartzImageIO (not found in project, manifest or registry)
 * UnicodeFun (not found in project, manifest or registry)
Please specify by known `name=uuid`

Installing other packages works. Is it just me or is it a known problem? Thanks!

that must be a juliapro issue... @aviks, is juliapro using a curated list nowadays, or how could this happen?!


Add set definition from Hiera

Currently, rules can be defined in Hiera. This is very good.
The same should be done for sets, for symmetry purposes and to be able to define in Hiera rules that depend on sets.
It seems that the following addition to init.pp should be enough:
  $sets.each |$n,$v| {
    nftables::set{
      $n:
        * => $v
    }
  }

I could implement this but I'd personally actually do the opposite. I'd remove nftables::rules (the parameter). Users wanting to provide rules or sets via Hiera can do so today by using create_resources()

create_resources was a workaround for what @LionelCons proposes back in the day when the splat operator did not yet exist.
It comes with multiple problems. E.g. no linenumber and manifests file reference where it was created and thus problems with such resources are hard to debug.
Since the language has loops and the splat operator, this is the way to go. Also how can they create resource with create_resources() when it nobody calls that function (in this module).

Ok by me. Will wait until the patch queue clears out a bit to send something.


Use full requirement when serializing receipt

Summary
The current receipt doesn't capture quite enough information. For example, it doesn't differentiate between editable and non-editable requirements. This PR instead uses the full Requirement type. I think we should use a custom representation like we do in the lockfile, but I'm just using the default representation to demonstrate the idea.

Please just focus on the concept here (example) and ignore the code and exact representation for now.

I think this makes sense to me. My only concern is that I want users to be able to declare tools declaratively eventually. I don't think that's in conflict though — I think the receipt can be considered "machine read / write" and "human inspectable" like the lock file. We can iron out a separate schema for users to declaratively request tools later.

I'm not terribly familiar with tool receipts yet. Can you say more at a high level about what problem this is trying to solve?
(Insomuch as I understand what this PR is doing, I think it LGTM.)

Copying from Discord:
Yes sorry
When a user installs a tool (like cargo install), we save a receipt alongside it enumerating the input requirements
When they run uv tool upgrade, we respect those input requirements
...
It was using PEP 508 so...
If a user did tool install -e ./black, we didn't capture that it was installed as editable, for example
Since that can't be expressed in PEP 508
But our requirement type is richer

Ok happy with how this turned out.

Ready for review @zanieb @BurntSushi at your convenience.


bootil: fix eval

Description of changes
No idea why it's only hitting us now, but OK.
https://hydra.nixos.org/build/213510971/nixlog/17/tail
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

This gets the tarball job building, at least.

commented in https://github.com/NixOS/nixpkgs/pull/213780

Maybe this is really the only package with badPlatforms and without platforms...


How to change the X-axis of curve from Query over time.

Describe the bug
1.My X-axis seems be zero when I set X-axis in Query over time options as time and cycle, but timestep is ok.
2.I hope my X-axis is not timestep but the normalized time obtained by multiplying the time step and other parameters.  How should I get it in proper way?
Helpful additional information

Did VisIt crash: no
Did you get wrong results: yes

Attachments
The curve with time and timestep as X-axis.

File information tells ''All Times are NOT Accurate'' , I don't know if it's the reason.

Desktop

OS and version: [Win10]
VisIt Version: [3.3.0]
Server info (if applicable):

If you enable  'Try harder to get accurate cycles/times`,  from the Options->Preferences window, do you get better results? If your databases is already open when you enable this preference, you will need to reopen it.

Hmmm..It's still not ok after I enable the option.

https://drive.google.com/file/d/17DikyBr2XGQuT9zNJiE8hVQM0fpfaZos/view?usp=sharing
Here is the data.

Thank you for the sample.
I looked at the root files and a few individual files using Silo's silex tool.
'cycle' is defined as a variable, but it is always 0.
'time' is not defined, nor is 'dtime' (either of which is valid for defining time in the Silo file).
That is why 'Try harder to get accurate cycles/times' didn't help for the query-over-time.
For a query-over-time to use Cycle or Time as the variable for the x-axis, it needs to be able to read a valid cycle or time from the files.
I recommend ensuring valid cycle values are written to your silo files. You may also want to have time written as well.
Regarding the information shown in the 'File Information' window:
If the 'Try harder' option is turned on, then cycle/time are read from each timestep, and what is displayed is considered accurate.
Otherwise, the first value displayed is from the first timestep (if available in the file), the other values are a 'guess' that is determined by parsing the filename.  That is why  'Cycle' showed '0' for the first timestep (it was read from the file), and other cycles matched the numbers in the filenames (they were 'guessed' from the filename).
When displaying time/cycle info in the plot window or performing a Query (or query-over-time), the time/cycle info is obtained from the file (if available).

We should print out an error message when either all the times or cycles are zero and the user requests using time or cycle instead of creating a vertical line.

I've attached user's data here. I removed a slew of UNinteresting domains here keeping only domain 0 (that is where it gets its notion of all its variables) and 26,27,33 and 24. So, when plotting turn off all domains except 26,27,33,34 to get it to plot.
silo_hdf5.tar.xz.gz
I noticed something else odd, I re-opened at first time step and then at last time step. I noticed in File Information window that it would change its understanding of cycles. Opening at first timestep gives cycles of 0, 15000 and opening of last timestep gives 10000, 0. Yet, all the cycle values stored in the files are zero.
What I think is happening is contention between VisIt's guesses for cycles (from filenames) and the data actually stored in the files. It appears to take the value from whatever file it opened at (makes sense because it is indeed actually reading data from that file and we think the file's cycle value actually stored there is more reliable than guessing from the file's name) and then takes its guesses from all other file names in the sequence.


Improve pull request merge box when pull request merged and branch deleted.

This PR hide the pull request merge box totally if it's merged and branch deleted.
It's also add a bold for merge base commit id in merged message comment
Before:

After:

Why introduce the duplicate hash again in the message? It is visible in the timeline entry above, isn't it?

Why introduce the duplicate hash again in the message? It is visible in the timeline entry above, isn't it?

Reasonable. I have adjusted the pull request.

Thanks. BTW, Is it possible to inject <script>alert('xss')</script> via translation string or is there sanitization to prevent this? It's not a new issues but I suspect all translations may be vulnerable to attacks like this.


Remove commented-out sample for jacoco aggregation of all Test tasks

The commented out code that is shown in the sample is not correct. tasks.withType(Test) will not realize all the test tasks, but rather iterate over an empty list and yield nothing in this case if the tasks have not yet been configured. An alternative would be to wrap this code in afterEvaluate {}.

@bot-gradle test and merge

OK, I've already triggered a build for you.


Missing dbo.SynapseToSQLUpdatedTables script

Hi I'm trying to implement FactsTrack SynapseToSQL but it seems I'm missing the script for the table dbo.SynapseToSQLUpdatedTables.
Can somebody help?
Thx

Is there any update on this? I also am running into this issue and I am not seeing an updated SQL destination file.

We updated the solution of the Synapse to SQL ADF/Synapse pipeline template.. this no longer user any source or target sql scripts to be deployed separately .. pipeline uses all the scripting within the pipeline and simplified pipelines. Try this out
https://github.com/microsoft/Dynamics-365-FastTrack-Implementation-Assets/tree/master/Analytics/SynapseToSQL_ADF


memory

When I ask a few questions in a conversation, there is no context between questions. So I have to include all the details in every prompt manually. I asked a question about Bainbridge Island, but after the response, it forgot and couldn't refer to it later in the conversation:

#77 is an initial stab at this


Harvesting user email addresses without any form of consent is against GDPR regulation

The SponsorLink addin is sending user email addresses without any consent to a cloud API. When used inside a corporate environment is is unacceptable. Next to this its also against EU GDPR regulations and probably most corporate environments.
Developers won't use their private github account to do contributions to the corporate git repository, so the sponsorlink will never work for them either

@kzu a SHA256 of the email is not sufficient for GDPR compliance:

Personal data which have undergone pseudonymisation, which could be attributed to a natural person by the use of additional information should be considered to be information on an identifiable natural person.

https://www.privacy-regulation.eu/en/recital-26-GDPR.htm


Create definition file truffleruby-<IP_ADDRESS>

I noticed that there is new version for truffleruby and created a file for installing it.

Thanks @hsbt


Culture: Add section on Strong Opinions loosely held

Add section on Strong Opinions loosely held

https://www.linkedin.com/posts/martinjk_embracing-the-idea-of-having-a-strong-foundation-activity-7131238490222010368-rEwI?utm_source=share&utm_medium=member_desktop


Using Win10's built-in SSH returns "Timed out while waiting for handshake"

Do you read the FAQ?

[X] Yes, even similar issues (suggesting higher timeout of 20s instead of 10s; didn't help)
[x] I am going to read now.

Describe the bug
Setting up everything just like on my Win7 machine, but uploading a modified file fails on Win10 using built-in OpenSSH client, no matter which key format (PuTTY, SSH2, SSH.COM) is used and with or without password on the private key.
Maybe it's related to #507?
To Reproduce
Steps to reproduce the behavior:

Go to any file within your setup workspace, e. g. file.ext
Having auto-save set to true, modify the file, e. g. type x and wait a second.
See error

Expected behavior
Upload should happen just as it does on my Win7 machine.
Screenshots
Not needed, log posted above.
Desktop (please complete the following information):

OS: Win 10 Pro (RS5,<PHONE_NUMBER>)
VSCode Version 1.32.3 (user setup)
Extension Version 1.12.1

Extension Logs from Startup - required
[info] config at X:\WS\Code {"remotePath":"/var/www/me/htdocs/sub.domain.net",
  "uploadOnSave":true,"downloadOnOpen":false,"ignore":[],"concurrency":4,
  "protocol":"sftp","connectTimeout":20000,"interactiveAuth":false,"secure":false,
  "remoteTimeOffsetInHours":0,"algorithms":{"kex":["ecdh-sha2-nistp521"],
    "cipher":["aes256-gcm","aes256-gcm@openssh.com"],"serverHostKey":["ssh-rsa",
      "ecdsa-sha2-nistp521"],"hmac":["hmac-sha2-512"]},"host":"domain.net",
  "ignoreFile":".gitignore","name":"me","passphrase":"******","port":22,
  "privateKeyPath":"X:\\WS\\Private.key","username":"******"}
[info] [file-save] X:\WS\Code\file.ext
[trace] handle upload file for X:\WS\Code\file.ext
[debug] Local ident: 'SSH-2.0-ssh2js0.3.1'
[debug] Client: Trying domain.net on port 22 ...
[debug] Client: Connected
[debug] Remote ident: 'SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u7'
[debug] Outgoing: Writing KEXINIT
[debug] DEBUG: Comparing KEXINITs ...
[debug] (local) KEX algorithms: ecdh-sha2-nistp521
[debug] (remote) KEX algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
[debug] KEX algorithm: ecdh-sha2-nistp521
[debug] (local) Host key formats: ssh-rsa,ecdsa-sha2-nistp521
[debug] (remote) Host key formats: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ssh-ed25519
[debug] Host key format: ssh-rsa
[debug] (local) Client->Server ciphers<EMAIL_ADDRESS>[debug] (remote) Client->Server ciphers: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm<EMAIL_ADDRESS>[debug] Client->Server Cipher<EMAIL_ADDRESS>[debug] (local) Server->Client ciphers<EMAIL_ADDRESS>[debug] (remote) Server->Client ciphers: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm<EMAIL_ADDRESS>[debug] Server->Client Cipher<EMAIL_ADDRESS>[debug] (local) Client->Server HMAC algorithms: hmac-sha2-512
[debug] (remote) Client->Server HMAC algorithms: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
[debug] Client->Server HMAC algorithm: hmac-sha2-512
[debug] (local) Server->Client HMAC algorithms: hmac-sha2-512
[debug] (remote) Server->Client HMAC algorithms: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
[debug] Server->Client HMAC algorithm: hmac-sha2-512
[debug] (local) Client->Server compression algorithms: none,zlib@openssh.com,zlib
[debug] (remote) Client->Server compression algorithms<EMAIL_ADDRESS>[debug] Client->Server compression algorithm: none
[debug] (local) Server->Client compression algorithms: none,zlib@openssh.com,zlib
[debug] (remote) Server->Client compression algorithms<EMAIL_ADDRESS>[debug] Server->Client compression algorithm: none
[debug] Outgoing: Writing KEXECDH_INIT
[debug] DEBUG: Checking host key format
[debug] DEBUG: Checking signature format
[debug] DEBUG: Verifying host fingerprint
[debug] DEBUG: Host accepted by default (no verification)
[debug] DEBUG: Verifying signature
[debug] Outgoing: Writing NEWKEYS
[debug] Outgoing: Writing SERVICE_REQUEST (ssh-userauth)
[debug] Outgoing: Writing DISCONNECT (BY_APPLICATION)
[error] Error: [domain.net]: Timed out while waiting for handshake
    at Client.module.exports._connectSSHClient.e.on.on.e (C:\Users\me\.vscode\extensions\liximomo.sftp-1.12.1\dist\extension.js:70:106943)
    at Client.emit (events.js:187:15)
    at Timeout._onTimeout (C:\Users\me\.vscode\extensions\liximomo.sftp-1.12.1\node_modules\ssh2\lib\client.js:678:14)
    at ontimeout (timers.js:427:11)
    at tryOnTimeout (timers.js:289:5)
    at listOnTimeout (timers.js:252:5)
    at Timer.processTimers (timers.js:212:10) download X:\WS\Code\file.ext

Update:
Using the new sshCustomParams parameter with a value of -i X:\\Keys\\Private.key within my sftp.json file, I pressed CTRL + SHIFT + P, selected SFTP: Open SSH in Terminal, the profile, typed my private key's password at the newly created terminal and BOOM, connection established! - though, any file change still results in the same error as shown in the log above (hanging at SERVICE_REQUEST (ssh-userauth) for a couple of seconds, then failing with Timed out while waiting for handshake). 😭
Nonetheless, this eliminates both, key and password, from the list of potential errors. 😎

@Eagle3386  Please try 1.12.2.

@liximomo Downloaded, installed, run, worked:
[debug] register command "Cancel All Transfer" from "./commandCancelAllTransfer.ts"
(...)
[many more `register command` lines]
(...)
[unchanged config print log]
[warn] ENOENT: no such file or directory, open 'C:\Users\me\.ssh\config' load C:\Users\me\.ssh\config failed
[info] [file-save] X:\WS\Code\file.ext
[trace] handle upload file for X:\WS\Code\file.ext
[debug] Local ident: 'SSH-2.0-ssh2js0.4.2'**
[debug] Client: Trying domain.net on port 22 ...
[debug] Client: Connected
[debug] Remote ident: 'SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u7'
[debug] Outgoing: Writing KEXINIT
(...)
[unchanged key exchange debug log]
(...)
[debug] Outgoing: Writing KEXECDH_INIT
[debug] DEBUG: Checking host key format
[debug] DEBUG: Checking signature format
[debug] DEBUG: Verifying host fingerprint
[debug] DEBUG: Host accepted by default (no verification)
[debug] DEBUG: Verifying signature
[debug] Outgoing: Writing NEWKEYS
[debug] Outgoing: Writing SERVICE_REQUEST (ssh-userauth)
[debug] Outgoing: Writing USERAUTH_REQUEST (none)
[debug] Client: none auth failed
[debug] Outgoing: Writing USERAUTH_REQUEST (publickey -- check)
[debug] Outgoing: Writing USERAUTH_REQUEST (publickey)
[debug] Outgoing: Writing CHANNEL_OPEN (0, session)
[debug] Outgoing: Writing CHANNEL_REQUEST (0, subsystem: sftp)
[debug] Outgoing: Writing CHANNEL_DATA (0)
[debug] Outgoing: Writing MKDIR
[debug] Outgoing: Writing CHANNEL_DATA (0)
[debug] Outgoing: Writing LSTAT
[debug] Outgoing: Writing CHANNEL_DATA (0)
[debug] Outgoing: Writing OPEN
[debug] Outgoing: Writing CHANNEL_DATA (0)
[debug] Outgoing: Writing FSTAT
[debug] Outgoing: Writing CHANNEL_DATA (0)
[debug] Outgoing: Writing FSETSTAT
[debug] Outgoing: Writing CHANNEL_DATA (0)
[debug] Outgoing: Writing WRITE
[debug] Outgoing: Writing CHANNEL_DATA (0)
[debug] Outgoing: Writing FSETSTAT
[debug] Outgoing: Writing CHANNEL_DATA (0)
[debug] Outgoing: Writing CLOSE
[debug] Outgoing: Writing CHANNEL_DATA (0)
[info] local -> remote X:\WS\Code\file.ext
[debug] Outgoing: Writing ping (GLOBAL_REQUEST<EMAIL_ADDRESS>
So, updating ssh2js from 0.3.1 to 0.4.2 was everything needed or is there more to it?
Also, what about these two warnings (extracted from log above):

[warn] ENOENT: no such file or directory, open 'C:\Users\me\.ssh\config' load C:\Users\me\.ssh\config failed
[debug] Client: none auth failed (just after Writing USERAUTH_REQUEST (publickey -- check))

Lastly, can you give an ETA for 1.12.2's official (i. e. "non-debug version") release date? 😎

V1.12.2 has been released.

No answers to my questions? 🤔😥

Don't worry about them. SFTP try different ways to connect server. It's normal that some fails.

I'm not worried. Instead, I - as a developer myself - would like to know what actually fixed my issue.
So, if possible, please provide such details.
Thanks in advance! ☺


suggestion: Broccoli

https://github.com/broccolijs/broccoli/blob/master/logo/broccoli-logo.svg

added f753888db6162ce86d9ecbc0c1fe7abbe5e3f7c8
Thanks


[stable/ghost] <.name>: can't evaluate field name in type interface {}

Is this a request for help?:
Yes,
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Version of Helm and Kubernetes:
Tried on Helm 2.9.1 (and) 2.11.0 (and) 2.11-rc.3
Kubernetes 1.12.1
Which chart:
stable/ghost
What happened:
When running:
sudo helm install --name testapp \
    -f values.yaml \
    stable/ghost

The following error occurs:
Error: render error in "ghost/templates/ingress.yaml": template: ghost/templates/ingress.yaml:6:28: executing "ghost/templates/ingress.yaml" at <.name>: can't evaluate field name in type interface {}

What you expected to happen:
Successful chart installation
How to reproduce it (as minimally and precisely as possible):
Follow exact steps in What happened
Anything else we need to know:
Our values.yaml file:
ghostHost: ghost.test.cooby.online
ingress:
  enabled: true
  annotations:
    kubernetes.io/ingress.class: nginx
    kubernetes.io/tls-acme: "true"
  hosts:
    - ghost.test.cooby.online
  tls:
   - secretName: test-app-tls
     hosts:
       - ghost.test.cooby.online
mariadb:
  replication:
    enabled: true

Basically it's the last step in Alens' blog post here: https://akomljen.com/get-automatic-https-with-lets-encrypt-and-kubernetes-ingress/
Cheers, Dave

Alen updated the post to work with the new stable/ghost helm chart. All good now.


add Brazilian grades

https://en.wikipedia.org/wiki/Grade_(climbing)#Brazilian
they seem similar to but more complex than British trad or aid+mandatory free.  Do those first:

https://github.com/OpenBeta/sandbag/issues/97
https://github.com/OpenBeta/sandbag/issues/80

We have started Brazilian grades, but there are more layers

https://github.com/OpenBeta/sandbag/pull/158/files#r1388446690

Yeah, to make it as brief as possible: the brazilian grade standard actually has two grades for any route that IS NOT a single pitch/sports route:
the general grade of the route
the grade of the hardest move (crux)
for the general grade, an arabic number is used: i.e. 6th
for the crux grade, it's roman. so a route that is generally graded in 5th grade but has a 6sup grade crux, it reads like:
5º 6sup5º VIsup
for sports climb/single pitch, we use only the second form because there's no point in having two assignments.
I have focused my implementation in just the second form. However, later we could expand to enable the whole aspect of the brazilian specification, which has more to it: duration, aid grade, exposition grade.

https://github.com/OpenBeta/sandbag/pull/158/files#r1388568954

I have focused my implementation in just the second form. However, later we could expand to enable the whole aspect of the brazilian specification, which has more to it: duration, aid grade, exposition grade.

Yes, makes sense to start with the common case.
We will need a system to handle this for other scales too. I haven't worked out the details, but I plan to allow hybrid/combined grades that combine complementary scales. For example, a British trad grade could be constructed from a grade on each of the adjectival and technical scales, e.g. BritishAdjectival("E6") + BritishTechnical("6a"). Likewise, an aid route with mandatory climbing could get a grade of 5.8 A1 , which would be parsed as Aid("A1") + YosemiteDecimal("5.5").
If I understand the spec you shared, most Brazilian grades would be represented by a combination of
BrazilianGeneral ~ [1º, 2º, 3º, 4º, 5º, 6º, 7º, 8º,…]
BrazilianTechnical ~ ['I', 'Isup', 'II', 'IIsup',...] <- this PR
BrazilianAid == Aid?
BrazilianDuration ~ ['D1', 'D2', ..., 'D7']
BrazilianExposure ~ ['E1', 'E2', ..., 'E5']
Does this general idea make sense for Brazilian grades?


Autoplay Dots

If you select a dot it goes dark and the selected slide appears all just as it should.  When the slide loses focus and the Autoplay resumes the black dot on the selected display stays behind.  I think this is a bug.
Kind of funky but not a bug is that once selected and the dots still have focus that the autoplay continues to run.  I would think as long as the dots still have hover the autoplay would be paused kind of like hover on a slide.  To be clear hover pause would only be in effect after the dots are selected.  Hover before selection would not cause a pause.

Thats the focus styling. You can override that with css.


[WIP] TimeSeries

When you added a new program / programs , put a cross on the  OS that you have test it on

(Example: [ X ] Windows  )
[  ] Windows
[  ] Linux Ubuntu
[  ] Mac
[  ] Others  (State here -> xxx )
Assign a reviewer to review your code.

Closing this as time series exercises will be maintained in another repo https://github.com/CertifaiAI/time-series-labs

Closing this as time series exercises will be maintained in another repo https://github.com/CertifaiAI/time-series-labs


how use calendar feature

Hello,
have an example to use calendar API ?

Please refer to the PHP quickstart for Google Calendar. If you still have questions, we advise searching or asking on Stackoverflow.

how sky
пн, 29 июн. 2020 г. в 20:12, John Pedrie<EMAIL_ADDRESS>
Closed #1862
https://github.com/googleapis/google-api-php-client/issues/1862.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/googleapis/google-api-php-client/issues/1862#event-3492930963,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APNECNN6SDIZCVLN55ZDQPDRZCOORANCNFSM4OLGUUNA
.


Disable stack protector on system-probe build

What does this PR do?
Make it buildable on the environments which stack protector is enabled by default.
Some linux distributions like Alpine Linux enables stack protector by default which is not available on eBPF.
Motivation
To make system-probe buildable on Alpine Linux.
Related issues: https://github.com/DataDog/datadog-agent/issues/1788 https://github.com/DataDog/datadog-agent/issues/2669
Additional Notes
Describe your test plan
We made an Alpine linux based docker images.
git clone https://github.com/seqsense/datadog-agent-alpine.git
cd datadog-agent-alpine
make docker-build ENABLE_SYSTEM_PROBE=1

to check build on Alpine Linux.

Thanks for your contribution @at-wat, could you rebase your PR on top of the current tip of master so that it includes https://github.com/DataDog/datadog-agent/pull/6407 (and fixes the dependency issue)?

@at-wat Does the Alpine Linux system-probe build fail without this flag? Or does the error manifest in other ways?

@brycekahle Build without the flag on Alpine Linux fail with following errors.
checking for clang executable...
/usr/bin/clang
error: <unknown>:0:0: in function kprobe__tcp_sendmsg i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kprobe__tcp_sendmsg__pre_4_1_0 i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kretprobe__tcp_sendmsg i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kprobe__tcp_cleanup_rbuf i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kprobe__tcp_close i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kretprobe__tcp_close i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kprobe__udp_sendmsg i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kprobe__udp_sendmsg__pre_4_1_0 i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kprobe__udp_recvmsg i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kprobe__udp_recvmsg_pre_4_1_0 i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kretprobe__udp_recvmsg i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kprobe__tcp_retransmit_skb i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kprobe__tcp_set_state i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kretprobe__inet_csk_accept i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kprobe__tcp_v4_destroy_sock i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kprobe__udp_destroy_sock i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function tracepoint__sys_enter_bind i32 (%struct.syscalls_enter_bind_args*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kprobe__sys_bind_x64 i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kprobe__sys_bind i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function tracepoint__sys_exit_bind i32 (%struct.syscalls_exit_args*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kretprobe__sys_bind i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function tracepoint__sys_enter_socket i32 (%struct.syscalls_enter_socket_args*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kprobe__sys_socket_x64 i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kprobe__sys_socket i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function tracepoint__sys_exit_socket i32 (%struct.syscalls_exit_args*): A call to built-in function '__stack_chk_fail' is not supported.
error: <unknown>:0:0: in function kretprobe__sys_socket i32 (%struct.pt_regs*): A call to built-in function '__stack_chk_fail' is not supported.
found clang

(bin/system-probe/system-probe is not created)
Related: https://www.spinics.net/lists/netdev/msg556400.html Arch Linux seems also enabling the stack protector by default and causes same error on BPF build.

@brycekahle the build error can be reproduced on any environments by applying below:
diff --git a/tasks/system_probe.py b/tasks/system_probe.py
index e320fa9db..04d0e6150 100644
--- a/tasks/system_probe.py
+++ b/tasks/system_probe.py
@@ -312,6 +312,7 @@ def build_object_files(ctx, bundle_ebpf=False):
         "-include {}".format(os.path.join(c_dir, "asm_goto_workaround.h")),
         '-O2',
         '-emit-llvm',
+        '-fstack-protector',
     ]

     # Mapping used by the kernel, from https://elixir.bootlin.com/linux/latest/source/scripts/subarch.include


brms can use RStan (in fact that's the default)

Currently it says that brms requires CmdStanR but it can use RStan (in fact RStan is the default backend). This PR updates the two places I found where it said that.

in theory, yes, users can use RStan.
RStan is difficult to install.  the long-term plan is to not have to maintain two versions of an interface.   I don't see a problem telling folks to use CmdStanR.   unless we no longer want to maintain CmdStanR.

It's not just that users can use RStan in theory, lots of them do and it's actually the default behavior of brms to use RStan. I don't think it's a problem to tell users that we prefer CmdStanR (I think it's good to tell them that!), but the current text explicitly says CmdStanR is required, which is not true.

We could maybe say something like "Requires an R interface to Stan (preferably CmdStanR) and C++ compiler" but I think it's simpler to just say "Requires CmdStanR or RStan and C++ compiler".

Closing since it looks like this is included in #19


Implement the for of statement

JerryScript-DCO-1.0-Signed-off-by: Robert Fancsik<EMAIL_ADDRESS>

@LaszloLango Thanks for the review, I've updated the PR.


Fix description and add return value and remarks

The description was the one for bind. I copied the correct one from the Option module page.
The return value and remarks were missing.
An example is still missing, but I can't add it from GitHub's web UI...

Docs Build status updates of commit 5681797:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/conceptual/option.filter['t]-function-[fsharp].md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


How get  the list of fields + types on a query?

I'm building a small ORM-like library and wish to use diesel to handle the low-level stuff. All need to be using only raw sql, but I need to know in query, which names + types is returning:
SELECT *, 1, now(), 'hello' as world
so I can map dynamically. Is this possible with diesel? All the info assume is using the custom DSL, not much in how use sql directly (like https://github.com/StackExchange/Dapper?)

We don't expose anything that parses your SQL queries for you. You'll likely need to use something much lower level which exposes specific details about its prepared statements


Change to make h2ogpt work on Mac M2 chip

These are the changes I involved to make llama 3.1 gguf work on Mac M2.
I had to downgrade Bitsandbytes to 0.42.0 (from 0.43.1) because of a similar issue to this one : https://github.com/axolotl-ai-cloud/axolotl/issues/1436
I also had to bump some package versions :

llama-cpp-python==0.2.85
torch==2.3.1

Please note that I still have these warnings from llama_cpp when generating answers, but it doesn't seem to affect quality too much:
h2ogpt/lib/python3.10/site-packages/llama_cpp/llama.py:1129: RuntimeWarning: Detected duplicate leading "<|begin_of_text|>" in prompt, this will likely reduce response quality, consider removing it...

I hope that it does also work on other platforms but I am not able to test

I'll merge and make those changes since other changes required.  Thanks!


[otbn] Fix silly memory leak in ISS wrapper

The std::string constructor takes a copy of its char* argument, so we
need to delete the original afterwards. Thank you, Valgrind!

Try again, this time after running clang-format. Sigh...


RC Test: Friction 1.5.0-rc.3

@emily-phet @terracoda @ariel-phet @jbphet  @jessegreenberg  friction/1.5.0-rc.3 is ready for RC testing. This release has full a11y auditory descriptions, keyboard navigation, and sonification. Document issues in https://github.com/phetsims/friction/issues and link to this issue. This is the third RC for this sim, and the last test yielded only two issues. Please consider this a spot check issue, to verify those as fixed.
Assigning to @ariel-phet for prioritization.

General RC Test

What to Test

Click every single button.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.
Test all keyboard inputs. ( I think this comes later though)

If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Test all query parameters on all platforms. (See QA Book for a list of query parameters.)
Download HTML on Chrome and iOS.
Make sure the iFrame version of the simulation is working as intended on all platforms.
Make sure the XHTML version of the simulation is working as intended on all platforms.
Complete the test matrix.
Don't forget to make sure the sim works with Legends of Learning.
Check this LoL spreadsheet and notify AR if it not there.
If this is rc.1 please do a memory test.

Issues to Verify

[ ] https://github.com/phetsims/friction/issues/168
[ ] https://github.com/phetsims/friction/issues/171

These issues should have the "status:fixed-pending-testing" label. Check these issues off and close them if they are fixed. Otherwise, post a comment in the issue saying that it wasn't fixed.

Link(s)

Simulation
iFrame
XHTML
Legends of Learning Harness

Accessibility (a11y) RC Test

What to Test

Specific instructions can be found below.
Make sure the a11y feature doesn't negatively affect the sim in any way.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.
Test all keyboard navigation inputs (if applicable).
Test all forms of input with a screen reader (if applicable).

Focus and Special Instructions
The "grab" interaction with both the book and zoomed in book is brand new. Please test thoroughly both for keyboard navigation as well as with a screen reader. This is only the third sim to receive sonification, so that deserves attention as well.

Link(s)

a11y View
Simulation

Keyboard Navigation
This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a screen reader.
Final Requests

[ ] If this sim is in this list, make an issue in website to ask if PhET research page links need updating. Please assign to @terracoda and @emily-phet.

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

@zepumph How does this sound for platforms?

[ ] Win 10 chrome (with and without jaws)
[ ] Win 10 firefox (with and without NVDA
[ ] Win 10 Edge

[ ] Mac 10.14 safari
[ ] Mac 10.14 firefox

[ ] Mac 10.12 safari
[ ] Win 7 IE
[ ] Chrome OS

[ ] iOS 12
[ ] iOS 11

Sounds good. Could you test with voice over on a version of safari too please?

QA is done.


Search excludes is broken in 1.48.2?

VSCode Version: 1.48.2
OS Version: Windows 10 2004 update

Steps to Reproduce:

Add something to "search.exclude" param, "**/node_modules" for example
Make sure vscode still searching for something in this excluded folder

Does this issue occur when all extensions are disabled?: Yes

Got it, it is search setting, thanks for this post https://github.com/microsoft/vscode/issues/95757#issuecomment-617087019.


Register each instance of a display, group/bunch displays by parent device

Host 1 can have 3 differently set up displays, Connected device 2 can have 2 different displays. If we register each display to it's respective parent we can control the settings individually.
Related to #15

Closing without resolution. This issue either affects too few users or there are too many issues with higher impact to be working on. It is possible to re-open or re-visit this issue at a later time. If you feel this issue is important, please give a thumbs-up reaction to the first post. You may track this issue from the pinned meta-tracker at the top of the issues home page.


Bump golang to 1.23.1

Bump golang to 1.23.1.

:tada: This PR is included in version 3.16.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


StringFlag splits on $ sign

Hello!
When reading input from string flag it splits on $ sign. E.g. running
go run main.go --myflag foo$bar
and then in code
myFlag := c.String("myflag")
returns foo
I was wondering if this is intended behaviour? Or is there a way to tell flag to parse it's value literally?

@dkns thanks for reporting this. I'll be taking a look into this shortly

Hi @dkns
I have taken a look at this issue and I can confirm this is not a bug. What happens here is that your shell tries to parse $bar as a variable and as it is not defined, it evaluates to blank.
 Wrap it in quotes!
go run main.go --myflag 'foo$bar'
// foo$bar

Regards,
Ajitem

@asahasrabuddhe thanks, that works! I tried passing string but wrapped in " which for some reason didn't work. Wrapping string in single quote works perfectly.


Cannot handle grapqhl error properly because client is returning DecodingError.keyNotFound

Describe the bug
I'm trying to send a graphql request but when my query returns this response:
{
  "errors": [
    {
      "extensions": {
        "code": "unexpected",
        "path": "$"
      },
      "message": "Incorrect username or password."
    }
  ]
}

The client just returns a CombinedError.unknown(DecodingError.keyNotFound). Instead of returning the error described in the response object.
Take note that the GraphQL server is running on Hasura and my graphql selector is shaped as:
Selection.QueryRoot<Auth.Session> {
  try $0.login(
    email: emailAddress,
    password: password,
    selection: SelectorSessionResponse.nonNullOrFail
  )
}

let SelectorSessionResponse = Selection.SessionResponse {
    Auth.Session(
        accessToken: try $0.accessToken(),,
        expiresIn: try $0.expiresIn(),
        user: Auth.User(
            uid: try $0.uid()
        )
    )
}

Thank you for reporting the issue. Could you describe what your schema looks like and what you were expecting?

I think this was related to #144.


Style: Add Scrolling Animations to the Website.

Category

[ ] Documentation
[ ] Resource Addition
[ ] Codebase
[X] User Interface
[ ] Feature Request

Description
Add Scrolling Animations to the Website.

@SohanRC Good idea, but we don't want to implement it for now. So, we're closing this issue.


Inn

Inn can be used for recovering health.
Different suite concept is appled

Wow. Very nice Zhili!


Fix CI URL for PRs

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


hmr does not work after project reloading

Expected Behavior
Expect hmr is working
Actual Behavior
After reloading project in VSCode hmr does not work (while changes are loaded in browser in dev tools)
Is an error being thrown?
no
Steps to Reproduce
here is the repo

run project with start command (hmr works well)
reload VSCode and try to run the project with start command and try to modify App.tsx

(if remove /node_project/.cache and rerun the project - hmr works)
here is my config
new HardSourceWebpackPlugin({
   cacheDirectory: path.resolve('./node_modules/.cache/hard-source/[confighash]'),
   recordsPath: path.resolve('./node_modules/.cache/hard-source/[confighash]/records.json'),
   configHash: function(webpackConfig) {
      return require('node-object-hash')({ sort: false }).hash(webpackConfig);
   },
}),

Operating System, Node, and NPM dependency versions
Mac OS 10.13.6
Node 10.9.0

close & remove due to inactivity


ITO investors can't legally be allowed to see tokens in their wallets yet

Given that the ITO investors investment is a convertible loan which they have to manually exchange into tokens once the PTO has started we can not show any tokens in their wallets for now. This is clearly stated in the Investor Agreement but as always people do not read all T&Cs. Andreas suggests to use the TF App news section to tell ITO investors.
In their wallet we can put "your convertible loan value is $xxx". Exact wording has to be approved by legal.
Once a CNA has been processed, we can display the amount in the user's wallet. This requires some work from the IYO and the TF team for the backend implementation (Bart-at-mobicage is a good entry person there), Andreas and Pierre will choose wording.

Put on hold until we have a permanent answer

To make this more explicit: We are looking at the legal options to do show nr of tokens in amount, by changing the process by which TFF collects money from convertible loans (back) to prepurchases of tokens.

"iTFT" make this point moot.


aarch64-apple-darwin test failure

aarch64-apple-darwin rustc 1.54.0-nightly (6d395a1c2 2021-05-13) commit 4e7867d1b591439
RUNNING ALL TESTS
bad VM_FLAGS_USER_ALLOCATE value at byte 0: rust: 31 (0x1f) != c 159 (0x9f)
bad VM_FLAGS_USER_MAP value at byte 0: rust: 31 (0x1f) != c 159 (0x9f)
thread 'main' panicked at 'some tests failed', /Users/username/github/libc/target/debug/build/libc-test-621539cf11e10654/out/main.rs:12:21
stack backtrace:
   0: std::panicking::begin_panic
             at /rustc/6d395a1c2946c79966490f5b1e6e619d3a713e6b/library/std/src/panicking.rs:519:12
   1: main::main
             at /Users/crb002/github/libc/target/debug/build/libc-test-621539cf11e10654/out/main.rs:12:21
   2: core::ops::function::FnOnce::call_once
             at /rustc/6d395a1c2946c79966490f5b1e6e619d3a713e6b/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
error: test failed, to rerun pass '--test main'

They are declared on the deprecated_mach macro, which means the libc doesn't support the use of these values anymore. I think it's okay to just ignore them on tests or move to the x86_64 module if it works.


remove reference to image

confirmed with @DaniEASmith
closes https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/9166

Docs Build status updates of commit 19e5177:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Teams/teams-add-on-licensing/virtual-user.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 19e5177:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Teams/teams-add-on-licensing/virtual-user.md
:white_check_mark:Succeeded

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


NavigationDuplicated: Avoided redundant navigation to current location

Thanks for filing a bug report :-)
Steps to Reproduce

Navigate to https://lightclient.raiden.network/staging/
I don't know ;)

Expected Result

No console error/warning

Actual Result

The following console error is shown

Uncaught (in promise) NavigationDuplicated: Avoided redundant navigation to current location: "/transfer/0x59105441977ecD9d805A4f5b060E34676F50F806".

Additional Infos (Optional)
- Firefox 80.0.1

To reproduce:

Make a transfer
After a transfer close the dialog before it closes itself

Timer redirecting to the same route you are already at.

@christianbrb I fail to reproduce this issue. Can you please help me?
Here is what I do:

I have an open channel with the hub that is funded
I'm on the /transfer/<token-of-channel> route
I'm entering the hub as direct transfer target and any small amount
I follow the progress by clicking on transfer and then accept the "path" and fees
The transfer progresss dialog pops up and shows me the steps that have become completed
Before the transfer is done, I close the dialog (using the X button and/or just click outside of the dialog)
The console never shows an error, never mind how often I try

I am not able to reproduce it. Closing.


Adding "-g" to Rust explorer causes code generation differences

Specifically the -g I use to get the colourise information adds frame setup to all functions (!)

This is now resolved on the nightly compiler.

https://godbolt.org/g/dCPJyK

Was fixed in Rust 1.27, so...calling this done. Thank @CryZe


Use the right image name in README

Overlooked in https://github.com/jenkinsci/docker-ssh-slave/pull/22

cc @alecharp @oleg-nenashev @MRamonLeon


Firebase functions to track user usage

Summary
This pull request is the first step towards implementing feature Firebase functions to track user usage.
I added firebase functions to track the following

number of users
number of semesters per user
number of future semesters
number of past and current semesters

Test Plan
1.) run npm install in the functions folder
2.) run firebase deploy -P staging --only functions:TrackUsers
3.) Go to the deployed link
4.) Go the function link on the firebase project in the functions sections
5.) The response should be a JSON of the users and their fields.

Could you also please remove the season images you accidentally added to this commit?


How to serialize the SupplementaryFileContainer?

Is there a way to serialize and deserialize an AAS shell and at the same time keep the file's content?
The method object_store_to_json() creates a json serialization of a set of AAS objects within an object store.
When the json is parsed back to AAS objects, the content of the Submodel Element (File) is missing.

Hi, thank you for your question.
The specification of the AAS is a bit tricky with supplementary files:
A File SubmodelElement does not contain a file, just a Reference to it. Therefore, the referenced file is not serialized when writing an AAS to JSON.
The idea behind the JSON format is to only transfer AAS data, not supplementary files.
If you want to transfer files together with an AAS, I would suggest looking at the AASX Package format (here's the tutorial).
Alternatively, you could use a Blob SubmodelElement to store the binary data of a file inside the AAS itself, which in turn gets serialized directly to JSON. However, you should be aware that that bloats the size of the JSON accordingly, of course.
I hope this helps, feel free to ask if you have further questions!

Thank you for the explanation, @s-heppner
The background for the question is that we are looking into going from Type 1 AAS (using AASX files) to an infrastructure that uses Type 2 AAS (API) like the AAS Environment — Eclipse BaSyx™.
I guess this should be more of a question to IDTA, but I wonder how they are thinking of working with the Handover Documentation submodel in a Type 2 AAS API setup? The solution would probably be to use some kind of AASX endpoint.

That's indeed a good question and is being discussed in the IDTA, as far as I know.
From my understanding, the AAS does not want to reinvent file transfer, as that is a solved issue. It is therefore expected that you use an existing solution like Amazon S3, FTP, etc. for the file transfer (However, I'm no expert on the field, so I'm not advocating for any of these technologies). The File SubmodelElement could then be a reference to the download endpoint.
What does happen quite often in practice at the moment is that people simply keep transferring AASX, yes.