questions/ideas for lowlevel/highlevel storage

some thoughts i had while working with storage.
@NikVolf, @pepyakin, @fckt what do you think? i'd really appreciate answers to my questions
and feedback on my ideas :)
currently there's a lowlevel storage API:
https://github.com/paritytech/pwasm-std/blob/a16024a03ac3edb68d68957bfe9463633ea45c13/src/storage.rs#L13
it's a 256bit to 256bit key-value store.
that's a good lowlevel interface!
contract developers however will often want to:

easily persist something under a name
use strings as keys
store arrays
store mappings
have all the storage options they are used to in solidity

with similar or better ergonomics

more...

currently those things are difficult and error prone:
persisting something under a name:
https://github.com/paritytech/pwasm-token-example/blob/870d91d6a90091fd3e0214ba6cc82498b02fa636/src/token.rs#L61
https://github.com/paritytech/pwasm-token-example/blob/870d91d6a90091fd3e0214ba6cc82498b02fa636/src/token.rs#L84
mappings:
https://github.com/paritytech/pwasm-token-example/blob/870d91d6a90091fd3e0214ba6cc82498b02fa636/src/token.rs#L86
https://github.com/paritytech/pwasm-token-example/blob/870d91d6a90091fd3e0214ba6cc82498b02fa636/src/token.rs#L70
it's easy to get key clashes the current way. those could have very bad consequences.
the current API puts a burden on the programmer to be extremely careful.
i think we should minimize the possibility for such errors in APIs for contract code that has to be extremely reliable later!
wouldn't it be great to have a more highlevel storage API that makes the above mentioned things easy?
that API could live in it's own crate and build on top of the lowlevel one.
for this it probably makes sense to extract storage into its own trait and types.
something like:
trait BasicStorage {
  fn write(key: &H256, value: &[u8; 32]);
  fn read(key: &H256) -> [u8; 32];
}

this way the highlevel API doesn't have to awkwardly depend on the entire Context.
it can just work on anything implementing BasicStorage.
following are a couple of other questions/ideas on storage.
keep in mind that i'm still learning about this.
how is the storage implemented all the way down?
...when WASM gets executed.
would another lowlevel API be possible?
just want to make sure we aren't unnecessarily limiting ourselves
by a specific lowlevel API.
is there a way to delete from storage?
i don't see any way to delete from storage.
shouldn't we add a storage_delete?
seems to me that currently a contracts storage can only ever grow and not shrink.
what happens when we read a key that hasn't previously been written to?
does it return zeroed memory?
does it return uninitialized memory?
that's a source for bugs.
can we detect (in the lowlevel implementation of storage) whether
a key has previously been written to?
maybe storage_read could return an Option. we're using rust not C.
idea: storage struct
what if a contracts storage were modeled by a struct:
#[contract_storage]
struct TokenContract {
    totalSupply: U256,
    ownerHash: H256,
    balances: Mapping<Address, U256>,
}

that could enormously improve ergonomics and prevent many errors!
it would offload a lot of checking from the programmer to the implementation
of #[contract_storage] (or similar) and the rust typesystem.
we can easily map/store such a struct into the lowlevel storage and potentially
make it very safe.
i strongly believe we should do everything reasonably possible to
make rust wasm smart contract development safe since
errors in smart contracts have the potential to be enormously expensive!

Definitely it's worth of separate crate. Feel free to sketch up your ideas.

it's actually out of scope of pwasm-std, but worth discussion anyway

thought so. still thought this would be the most appropriate repo for a discussion for now

it's all defined in the runtime behaviour (kovan/parity/whatever), not on wasm level

could someone point me to the code where that's implemented?

i believe there could be multiple implementations of storage in different crates based on the same low-level-api, user will just stick to one of them

that would be good

@snd
https://github.com/paritytech/parity/blob/master/ethcore/wasm/src/runtime.rs#L180
it uses Ext
Ext is implemented for Externalities:
https://github.com/paritytech/parity/blob/master/ethcore/src/externalities.rs

@NikVolf thanks! i looked at it a bit and things make a lot more sense

Any progess/suggestion on that? I feel it really hard to move a contract with several fields (some of which are variable-sized) on wasm. I'm trying to adopt this code, but it seems to be extremly complicated.

Some progress is done there.
Now it support arrays (with nesting!), but interface is really fragile. So it's working, but it worth to hide it under some kind of attribute, as proposed in the first post.

I am very interested.
Is there any additional information on this matter?


GEODE-3: add lib jars that will be missing in jdk9 and later

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

I updated  LICENSE to add a reference to jaxb.


{'event': 'error', 'data': {'message': 'An unexpected error occurred.', 'code': 18}}

{'event': 'error', 'data': {'message': 'An unexpected error occurred.', 'code': 18}}

I have the same problems...

{'event': 'error', 'data': {'message': 'An unexpected error occurred.', 'code': 18}}... That's the error I'm getting.

there is a topic with this error

Thanks man. A topic without answers

Bump.. anyone know where it's hanging up?  Having the identical issue and trying to see if it's an issue where the websockets are coming from a terminal prompt and it's confusing the perlego server somehow..

having the same issue, anyone having good luck making it successful?

https://github.com/evmer/perlego-downloader/issues/67#issuecomment-1685250280
consult this


Build Conda package on CI (#1166)

This PR creates a Buildkite stage to run conda build on CI (using the Anaconda docker image), which will validate our Conda package.
There are also improvements to the meta.yaml file which defines the stellargraph package:

brings in the changes from v0.11.1 which are in master, but didn't merge correctly into develop
tweaks dependencies (eg python 3.6 min, no cap on version of networkx)
expands the test section to bundle and run our unit tests on the built package which can validate issues like broken tensorflow dependencies

note that it may be more practical long-term to only run a subset of our tests - suggestions welcome

note that I've temporarily removed other stages from the pipeline to speed up development, but will restore for the final PR.
See: #1166

(I edited a reference to #1166 into the PR description because references in the title don't become links, and I think they also don't create the back-reference on the other end.)

@kjun9 I added you as a reviewer to see if you're happy with this PR as a resolution to #1166?

I added you as a reviewer to see if you're happy with this PR as a resolution to #1166?

Ah I didn't mention explicitly in #1166 but I also wasn't sure if we were using the requirements.host section correctly?
From reading the docs, it seems like we might just need python, not all of our dependencies - should we try this?

we might just need python, not all of our dependencies - should we try this?

you're right - Conda is quite intelligent here, and even selects a version of python to match the set of dependencies used later for 'run' - this works well.

I also added build kite upload of the artefact - useful currently as it can't build on Mac due to tensorflow 2.1 being unsupported.

Uploading the package is a great idea 👍 It's part of the way to #627. Should we update the release procedure to downloading from buildkite instead of a manual conda build . (or at least indicate it exists there)?


Java version of termpura

Hi @rayhanadev. Is it okay if I work on a python and java version of it? Asking just in case you don't want me to make those for copyright reasons/etc ...

By all means, go ahead! The principles behind Termpura were borrowed from Next.js 😂 so its entirely okay if you make your own version :). I wouldn't call it Termpura though, probably name and license your code with your own project name, that way its yours!
Good luck and looking forward to seeing more kewl TUIs on Github :D.

By all means, go ahead! The principles behind Termpura were borrowed from Next.js 😂 so its entirely okay if you make your own version :). I wouldn't call it Termpura though, probably name and license your code with your own project name, that way its yours!
Good luck and looking forward to seeing more kewl TUIs on Github :D.

Alright! Also, I probably will name it jTermpura for java edition and pyTermpura for the python edition if that's okay with you...

Also thx for the quick reply!

Alright! Also, I probably will name it jTermpura for java edition and pyTermpura for the python edition if that's okay with you...

Perhaps not Termpura at all :). Something unique that you come up with 😌.

Also thx for the quick reply!

No problem! :D


Feat: Adding book recommendations in each genre   (issue no: #3317)

Related Issue
Feat: Adding book recommendations in each genre
Fixes:  #3317
Description
[Please also include relevant motivation and context. List any dependencies that are required for this change.]
I have added 3 book recommendations in all 27 genres available on the website. This feature will make the website more informative, and user-friendly.
For example, in Classic Literature section, I have added the following:

Pride and Prejudice by Jane Austen
Moby-Dick by Herman Melville
3.1984 by George Orwell
I have editted 2 files: index.html (to add recommendations) and style.css (to change height and width of of the card from 200 to 700 and 300 to 400 respectively, and also .book-recommendation has been added in this file so the geading Book Recommendation: is underlined.)

Type of PR

[ ] Bug fix
[ ] Feature enhancement
[ ] Other (specify): _______________
[ ] Documentation update

Screenshots / videos (if applicable)
Before Changes: (few examples)

After Changes: (few examples)

Checklist:

[ ] I have made this change from my own.
[ ] I have taken help from some online resources.
[ ] My code follows the style guidelines of this project.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.
[ ] I have tested the changes thoroughly before submitting this pull request.
[ ] I have provided relevant issue numbers and screenshots after making the changes.

good work @shreya20v


Support for new alarm "SDVECUW"

Hi,
my installation has been migrated to a new model of alarm, identified with panel code "SDVECUW" instead of "SDVFAST". This new model is being proposed by the moment to customers with old installations (SD2000) and it seems that in the future all the customers will be moved to this.
Login is failing in this case. I have another installation with SDVFAST and works ok.  Both installations are owned by different user accounts, because according with customer support is not possible to have together both types of alarms. HomeAssistant records says:
"Hemos tenido problemas para identificarle, por favor, cierre la sesión y vuelva a iniciarla.
status 500 reading RemoteServicesFeignClient#getMain(Map,MultiValueMap)"
Anyway, I am capable to manage the new model from the website.
I will investigate a little bit on the code...
Thanks!

More info about the errors:
{'errors': [{'message': 'Hemos tenido problemas para identificarle, por favor, cierre la sesión y vuelva a iniciarla.', 'name': 'ApiError', 'time_thrown': '2022-01-10T20:24:50.140Z', 'data': {'res': 'ERROR', 'err': '60067'}, 'path': ['xSCheckAlarm']}], 'data': {'xSCheckAlarm': None}}
{'errors': [{'message': 'status 500 reading RemoteServicesFeignClient#getMain(Map,MultiValueMap)', 'name': 'ApiError', 'time_thrown': '2022-01-10T20:24:51.230Z', 'data': {'res': 'ERROR', 'err': '60067'}, 'path': ['xSCheckAlarmStatus']}], 'data': {'xSCheckAlarmStatus': None}}
Do you know how to force both calls in the website?

I think this information is returned by the API itself, when I'm listing the installations, so maybe I can get the type of alarm from there instead of having that as a constant in the API. Thanks for the heads up.

I think there is something else. With this alarm, the website hasn't the option "Actualizar alarma". The status is received using only xsStatus. I am afraid that xsCheckAlarm is not available for this alarm, or it is different, and not possible to catch it  using the web. Could be avoided in your code?

I see, I can create a type of alarm to change the code flow logic in case that we can support this new type of alarm.

that would be great! Thanks.

I just check the code and in the check_alarm_status I already sending whatever panel property I get from the installations. So that's mean that the new value SDVECUW is being sent to the API instead of the SDVFAST in my case.
So right now, I don't know what to do. Do you mind capturing the API interaction in the web application by following these guides?
https://github.com/guerrerotook/securitas-direct-new-api/tree/main/docs
Before posting them here make sure that you remove personal information like username, password, installation id, etc.
If you need help let me know. You need to know how to use the Developer Extension in your browser.

I just check the code and in the check_alarm_status I already sending whatever panel property I get from the installations. So that's mean that the new value SDVECUW is being sent to the API instead of the SDVFAST in my case.
So right now, I don't know what to do. Do you mind capturing the API interaction in the web application by following these guides?
https://github.com/guerrerotook/securitas-direct-new-api/tree/main/docs
Before posting them here make sure that you remove personal information like username, password, installation id, etc.
If you need help let me know. You ned to know how to use the Developer Extension in your browser.

Hi Luis, I think the problem is that for this alarm, the xSCheckAlarmStatus method is not available. The link "actualizar estado" is not visible on the frontend, the only method used to update the status is xSStatus. I checked this with the developer extension in the browser.
I have uncommented the following lines on _init__py to bypass the call during the setup, and with this I have the alarm panel running:
status: SStatus = self.session.check_general_status(installation)
return CheckAlarmStatus(
"OK", "OK", "Ok", installation.number, status.status, status.timestampUpdate
)
Arm and Disarm operations are now runnning ok, but after call them the status is not updated inmediately, the update comes after a while.
One solution I think could be to use only checkGeneralStauts function, but I don't know if this has other impact on the other alarm model.

I got this new panel too and tried to catch some loads following the docs, let me know what you need.
I also saw that in the payload I get a base64 image of the new photodetector, we could capture the request API call to add this to the Home Assistant dashboard.


[Fonts] Add lato bold font, lowercase & capitalize case transforms

Screenshots are taken with Lato font.
Updated case transforms menu:

"Capitalize" transform:

"Lowercase" transform:

Fonts is no longer accepting new fonts due to file size concerns. Please download the latest patch for an easy way to add a custom font.

Noted. Are you interested in the latter half of the PR; adding the rest of the CSS case transforms? If so I can PR this separately.


[Story] Create a minimal dev container definition for the CI workflow

What product(s) is this story for?
Sage Monorepo
As a user, I want
~For instance, there should be no need to install VS Code extensions when the container is run by the CI workflow.~
The VS Code extensions are currently not installed, as they should not. What takes time is the workspace-install command. This command could be extracted from the starting the container to have a better visibility on the time these two steps take each.
EDIT: The two steps are separated in the definition of the action, but appear as one when the action is imported. Anyway, GH prints the time stamp on each log line so we already have the information
Description
No response
Acceptance criteria
No response
Tasks
No response
Anything else?
No response
Have you linked this story to a GitHub Project?

[X] I have linked this story to a GitHub Project and set its metadata.

This ticket is no longer applicable.


[DigitalOcean one-click] Configurations lost after update

Is it a duplicate question?
No, was not able to find any related issues
Describe the bug
I used the one-click App option to deploy this application within DigitalOcean and was on version 1.0.7. When updating to the latest uptime-kuma all configuration options are lost. Monitors, notification settings, etc.
To Reproduce
Steps to reproduce the behavior:

Deploy the app on DigitalOcean via one-click setup
Wait for a version update
Update the app: doctl apps update <app id> --spec uptime-kuma.yaml
Load the app URL and you are requested to re-setup from scratch

Expected behavior
Settings persist between application updates.
Screenshots
N/A
Desktop (please complete the following information):

Uptime Kuma Version: v1.0.7 --> v1.1.0
Using Docker?: Yes
OS: Linux; one-click hosted on DigitalOcean
Browser: N/A

The root cause is likely that there isn't a true database.
https://github.com/louislam/uptime-kuma/blob/master/server/database.js
Ideally the configuration would either be:

Pulled out to an external SQLite database
Support other database formats (NoSQL?)
Load configs from a JSON/YAML file passed in via ENV variable(s)

OMG. I thought they are stored in persistent  storage, so sad.
And surprisingly, they do not provide any persistent storage for "Deploy Button".....

There is no direct support to attach Spaces to the App Platform as of now. You might have to implement this by using Spaces in your code via the RESTful API or existing AWS S3 tools.

https://www.digitalocean.com/community/questions/mount-space-into-apps-platform
So, I removed the DigitalOcean deploy button from our README file.
For current DigitalOcean App users, I suggest you should manually backup the monitor one by one and move to another platform.

Thanks for the update, I will work on deploying directly for the time being.
PS: Great app, thanks!


Create groups of songs

Make it possible to create a group of songs and implement their use in copyrights, page numbers, latex selection pages.

Added by 5212be62ee


[ISSUE-415] Update version to 0.2.1

Signed-off-by: safronovD<EMAIL_ADDRESS>Purpose
Issue #415
Update version to 0.2.1
PR checklist

[x] Add link to the issue
[x] Choose PR label
[ ] New unit tests added
[ ] Modified code has meaningful comments
[ ] All TODOs are linked with the issues
[ ] All comments are resolved

Testing
Link to custom CI build

@safronovD please update version for CSI Operator as well.


on arm64　arch　 run launch  failed

root@master1:/nas/kubevirt/yaml# kubectl get po
NAME                               READY   STATUS    RESTARTS   AGE
virt-api-fdc55d8cf-8wjl8           1/1     Running   0          14m
virt-controller-6574455dcc-tcgkh   1/1     Running   0          14m
virt-handler-25q45                 1/1     Running   1          16m
virt-handler-m2gjs                 1/1     Running   0          16m
virt-handler-qws56                 1/1     Running   1          16m
virt-handler-v79br                 1/1     Running   1          16m
virt-handler-znm48                 1/1     Running   1          16m
virt-launcher-testvmi-v9rjx        1/1     Running   0          2m5s
virt-operator-5c9fbfcd6c-2nbbh     1/1     Running   0          17m
virt-operator-5c9fbfcd6c-krr59     1/1     Running   0          17m

root@master1:/nas/kubevirt/yaml# cat example-vm.yaml
apiVersion: kubevirt.io/v1alpha3
kind: VirtualMachineInstance
metadata:
  name: testvmi
spec:
  terminationGracePeriodSeconds: 30
  domain:
    resources:
      requests:
        memory: 1024M
    devices:
      disks:
      - name: emptydisk
        disk:
          bus: virtio
  volumes:
  - name: emptydisk
    emptyDisk:
      capacity: "2Gi"

root@master1:/nas/kubevirt/yaml# kubectl logs virt-launcher-testvmi-v9rjx
{"component":"virt-launcher","level":"info","msg":"Collected all requested hook sidecar sockets","pos":"manager.go:67","timestamp":"2019-07-04T06:59:47.727644Z"}
{"component":"virt-launcher","level":"info","msg":"Sorted all collected sidecar sockets per hook point based on their priority and name: map[]","pos":"manager.go:70","timestamp":"2019-07-04T06:59:47.727804Z"}
{"component":"virt-launcher","level":"info","msg":"Watchdog file created at /var/run/kubevirt/watchdog-files/kubevirt_testvmi","pos":"virt-launcher.go:156","timestamp":"2019-07-04T06:59:47.729889Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon: qemu:///system","pos":"libvirt.go:348","timestamp":"2019-07-04T06:59:47.730721Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon failed: virError(Code=38, Domain=7, Message='Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory')","pos":"libvirt.go:356","timestamp":"2019-07-04T06:59:47.756163Z"}
{"component":"virt-launcher","level":"info","msg":"libvirt version: 5.4.0, package: 2.fc31 (Fedora Project, 2019-06-20-16:38:00, )","subcomponent":"libvirt","thread":"53","timestamp":"2019-07-04T06:59:47.900000Z"}
{"component":"virt-launcher","level":"info","msg":"hostname: testvmi","subcomponent":"libvirt","thread":"53","timestamp":"2019-07-04T06:59:47.900000Z"}
{"component":"virt-launcher","level":"error","msg":"internal error: Unable to get DBus system bus connection: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory","pos":"virDBusGetSystemBus:108","subcomponent":"libvirt","thread":"53","timestamp":"2019-07-04T06:59:47.900000Z"}
{"component":"virt-launcher","level":"error","msg":"internal error: Unable to get DBus system bus connection: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory","pos":"virDBusGetSystemBus:108","subcomponent":"libvirt","thread":"53","timestamp":"2019-07-04T06:59:48.596000Z"}
{"component":"virt-launcher","level":"warning","msg":"DBus not available, disabling firewalld support in bridge_network_driver: internal error: Unable to get DBus system bus connection: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory","pos":"networkStateInitialize:694","subcomponent":"libvirt","thread":"53","timestamp":"2019-07-04T06:59:48.596000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:00.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:303","subcomponent":"libvirt","thread":"57","timestamp":"2019-07-04T06:59:48.706000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:00:01.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:303","subcomponent":"libvirt","thread":"57","timestamp":"2019-07-04T06:59:48.707000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:02:00.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:303","subcomponent":"libvirt","thread":"57","timestamp":"2019-07-04T06:59:48.714000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:03:01.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:303","subcomponent":"libvirt","thread":"57","timestamp":"2019-07-04T06:59:48.715000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:03:08.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:303","subcomponent":"libvirt","thread":"57","timestamp":"2019-07-04T06:59:48.716000Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to open config space file '/sys/bus/pci/devices/0000:03:09.0/config': Read-only file system","pos":"virPCIDeviceConfigOpen:303","subcomponent":"libvirt","thread":"57","timestamp":"2019-07-04T06:59:48.717000Z"}
{"component":"virt-launcher","level":"error","msg":"internal error: Cannot probe for supported suspend types","pos":"virNodeSuspendSupportsTarget:335","subcomponent":"libvirt","thread":"53","timestamp":"2019-07-04T06:59:49.988000Z"}
{"component":"virt-launcher","level":"warning","msg":"Failed to get host power management capabilities","pos":"virQEMUCapsInit:920","subcomponent":"libvirt","thread":"53","timestamp":"2019-07-04T06:59:49.988000Z"}
{"component":"virt-launcher","level":"error","msg":"this function is not supported by the connection driver: cannot detect host CPU model for aarch64 architecture","pos":"virCPUGetHost:452","subcomponent":"libvirt","thread":"53","timestamp":"2019-07-04T06:59:50.987000Z"}
{"component":"virt-launcher","level":"error","msg":"this function is not supported by the connection driver: cannot detect host CPU model for aarch64 architecture","pos":"virCPUGetHost:452","subcomponent":"libvirt","thread":"53","timestamp":"2019-07-04T06:59:50.987000Z"}
{"component":"virt-launcher","level":"info","msg":"Connected to libvirt daemon","pos":"libvirt.go:364","timestamp":"2019-07-04T06:59:51.002514Z"}
{"component":"virt-launcher","level":"info","msg":"Registered libvirt event notify callback","pos":"client.go:283","timestamp":"2019-07-04T06:59:51.007011Z"}
{"component":"virt-launcher","level":"info","msg":"Marked as ready","pos":"virt-launcher.go:73","timestamp":"2019-07-04T06:59:51.007326Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Executing PreStartHook on VMI pod environment","name":"testvmi","namespace":"kubevirt","pos":"manager.go:689","timestamp":"2019-07-04T06:59:52.972843Z","uid":"49f5c39f-9e29-11e9-851d-00073e90a226"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Starting PreCloudInitIso hook","name":"testvmi","namespace":"kubevirt","pos":"manager.go:700","timestamp":"2019-07-04T06:59:52.972942Z","uid":"49f5c39f-9e29-11e9-851d-00073e90a226"}
{"component":"virt-launcher","level":"info","msg":"updated MAC for eth0 interface: old: 8e:73:a9:5e:a4:7b -\u003e new: 8e:73:a9:f9:1f:11","pos":"common.go:203","timestamp":"2019-07-04T06:59:52.980760Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"bridge pod interface: VIF: { Name: eth0, IP: <IP_ADDRESS>, Mask: ffffffff, MAC: 8e:73:a9:5e:a4:7b, Gateway: <IP_ADDRESS>, MTU: 1500}","name":"testvmi","namespace":"kubevirt","pos":"podinterface.go:258","timestamp":"2019-07-04T06:59:52.988140Z","uid":"49f5c39f-9e29-11e9-851d-00073e90a226"}
{"component":"virt-launcher","level":"info","msg":"Found nameservers in /etc/resolv.conf: \n\n\u0001\n","pos":"converter.go:1394","timestamp":"2019-07-04T06:59:52.988360Z"}
{"component":"virt-launcher","level":"info","msg":"Found search domains in /etc/resolv.conf: kubevirt.svc.cluster.local svc.cluster.local cluster.local","pos":"converter.go:1395","timestamp":"2019-07-04T06:59:52.988443Z"}
{"component":"virt-launcher","level":"info","msg":"Starting SingleClientDHCPServer","pos":"dhcp.go:64","timestamp":"2019-07-04T06:59:52.988591Z"}
{"component":"virt-launcher","level":"info","msg":"Driver cache mode for /var/run/libvirt/empty-disks/emptydisk.qcow2 set to none","pos":"converter.go:166","timestamp":"2019-07-04T06:59:53.061276Z"}
{"component":"virt-launcher","level":"error","msg":"invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm","pos":"virCapabilitiesDomainDataLookupInternal:752","subcomponent":"libvirt","thread":"41","timestamp":"2019-07-04T06:59:53.062000Z"}
{"component":"virt-launcher","kind":"","level":"error","msg":"Defining the VirtualMachineInstance failed.","name":"testvmi","namespace":"kubevirt","pos":"libvirt_helper.go:96","reason":"virError(Code=8, Domain=44, Message='invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm ')","timestamp":"2019-07-04T06:59:53.063088Z","uid":"49f5c39f-9e29-11e9-851d-00073e90a226"}
{"component":"virt-launcher","kind":"","level":"error","msg":"Failed to sync vmi","name":"testvmi","namespace":"kubevirt","pos":"server.go:160","reason":"virError(Code=8, Domain=44, Message='invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm ')","timestamp":"2019-07-04T06:59:53.063181Z","uid":"49f5c39f-9e29-11e9-851d-00073e90a226"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Executing PreStartHook on VMI pod environment","name":"testvmi","namespace":"kubevirt","pos":"manager.go:689","timestamp":"2019-07-04T06:59:53.088640Z","uid":"49f5c39f-9e29-11e9-851d-00073e90a226"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Starting PreCloudInitIso hook","name":"testvmi","namespace":"kubevirt","pos":"manager.go:700","timestamp":"2019-07-04T06:59:53.088712Z","uid":"49f5c39f-9e29-11e9-851d-00073e90a226"}
{"component":"virt-launcher","level":"info","msg":"Driver cache mode for /var/run/libvirt/empty-disks/emptydisk.qcow2 set to none","pos":"converter.go:166","timestamp":"2019-07-04T06:59:53.089011Z"}

kubectl logs virt-handler-25q45
{"component":"virt-handler","hostname":"node-2","level":"info","pos":"virt-handler.go:190","timestamp":"2019-07-04T06:45:31.944803Z"}
{"component":"virt-handler","level":"info","msg":"Starting collector: sharedir=/var/run/kubevirt","pos":"prometheus.go:276","timestamp":"2019-07-04T06:45:32.935049Z"}
{"component":"virt-handler","level":"info","msg":"STARTING informer configMapInformer","pos":"virtinformers.go:190","timestamp":"2019-07-04T06:45:32.935266Z"}
{"component":"virt-handler","level":"info","msg":"Starting virt-handler controller.","pos":"vm.go:499","timestamp":"2019-07-04T06:45:33.035667Z"}
{"component":"virt-handler","level":"info","msg":"Starting device plugin controller","pos":"device_controller.go:92","timestamp":"2019-07-04T06:45:33.135994Z"}
{"component":"virt-handler","level":"info","msg":"tun device plugin started","pos":"generic_device.go:156","timestamp":"2019-07-04T06:45:33.139283Z"}
{"component":"virt-handler","level":"info","msg":"vhost-net device plugin started","pos":"generic_device.go:156","timestamp":"2019-07-04T06:45:33.139317Z"}
{"component":"virt-handler","level":"info","msg":"kvm device plugin started","pos":"generic_device.go:156","timestamp":"2019-07-04T06:45:33.144077Z"}
{"component":"virt-handler","kind":"","level":"error","msg":"Synchronizing the VirtualMachineInstance failed.","name":"testvmi","namespace":"kubevirt","pos":"vm.go:871","reason":"server error. command SyncVMI failed: \"LibvirtError(Code=8, Domain=44, Message='invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm ')\"","timestamp":"2019-07-04T06:59:53.063682Z","uid":"49f5c39f-9e29-11e9-851d-00073e90a226"}
{"component":"virt-handler","level":"info","msg":"re-enqueuing VirtualMachineInstance kubevirt/testvmi","pos":"vm.go:547","reason":"server error. command SyncVMI failed: \"LibvirtError(Code=8, Domain=44, Message='invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm ')\"","timestamp":"2019-07-04T06:59:53.086823Z"}
{"component":"virt-handler","kind":"","level":"error","msg":"Synchronizing the VirtualMachineInstance failed.","name":"testvmi","namespace":"kubevirt","pos":"vm.go:871","reason":"server error. command SyncVMI failed: \"LibvirtError(Code=8, Domain=44, Message='invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm ')\"","timestamp":"2019-07-04T06:59:53.090268Z","uid":"49f5c39f-9e29-11e9-851d-00073e90a226"}
{"component":"virt-handler","level":"info","msg":"re-enqueuing VirtualMachineInstance kubevirt/testvmi","pos":"vm.go:547","reason":"server error. command SyncVMI failed: \"LibvirtError(Code=8, Domain=44, Message='invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm ')\"","timestamp":"2019-07-04T06:59:53.090595Z"}
{"component":"virt-handler","kind":"","level":"error","msg":"Synchronizing the VirtualMachineInstance failed.","name":"testvmi","namespace":"kubevirt","pos":"vm.go:871","reason":"server error. command SyncVMI failed: \"LibvirtError(Code=8, Domain=44, Message='invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm ')\"","timestamp":"2019-07-04T06:59:53.094844Z","uid":"49f5c39f-9e29-11e9-851d-00073e90a226"}
{"component":"virt-handler","level":"info","msg":"re-enqueuing VirtualMachineInstance kubevirt/testvmi","pos":"vm.go:547","reason":"server error. command SyncVMI failed: \"LibvirtError(Code=8, Domain=44, Message='invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm ')\"","timestamp":"2019-07-04T06:59:53.095056Z"}
{"component":"virt-handler","kind":"","level":"error","msg":"Synchronizing the VirtualMachineInstance failed.","name":"testvmi","namespace":"kubevirt","pos":"vm.go:871","reason":"server error. command SyncVMI failed: \"LibvirtError(Code=8, Domain=44, Message='invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm ')\"","timestamp":"2019-07-04T06:59:53.107482Z","uid":"49f5c39f-9e29-11e9-851d-00073e90a226"}

image libvirt
FROM arm64v8/fedora:31

ENV container docker

#ENV LIBVIRT_VERSION 5.1.0

RUN dnf install -y dnf-plugins-core && \
  dnf copr enable -y @virtmaint-sig/virt-preview && \
  dnf install -y \
    libvirt-daemon-kvm.aarch64 \
    libvirt-client.aarch64 \
    socat \
    genisoimage \
    selinux-policy selinux-policy-targeted \
    augeas && \
  dnf clean all

COPY augconf /augconf
RUN augtool -f /augconf

COPY libvirtd.sh /libvirtd.sh
RUN chmod a+x /libvirtd.sh

RUN setcap CAP_NET_BIND_SERVICE=+eip /usr/bin/qemu-system-aarch64

CMD ["/libvirtd.sh"]

image launcher
FROM libvirt:5.1.0

RUN dnf -y install \
  edk2-ovmf \
#  socat \
#  genisoimage \
  && dnf -y clean all && \
  test $(id -u qemu) = 107 # make sure that the qemu user really is 107

COPY virt-launcher /usr/bin/virt-launcher
#COPY .version /.version

# Allow qemu to bind privileged ports
#RUN setcap CAP_NET_BIND_SERVICE=+eip /usr/bin/qemu-system-aarch64

RUN mkdir -p /usr/share/kubevirt/virt-launcher
COPY sock-connector /usr/share/kubevirt/virt-launcher/

ENTRYPOINT [ "/usr/bin/virt-launcher" ]

I am om arm64  why x86_64??

/kind/bug

/kind bug

see #2470
/close


How to reply/forward an email by using simple-java-mail

For now, I have get the emails from INBOX of my gmail acount, is it possible to reply/forward these emails when using simple-java-mail?
I have searched the api docs, but no hits ....

No, Simple Java Mail is a SMTP client. It can only connect to an SMTP server to send emails. To retrieve emails for further processing you need a POP3 / IMAP client.


Remove build phases models

Short description 📝
Build phases are implementations details specific to Xcode that developers shouldn't have to worry about. In case of the dependencies, we had already removed the linking build phase, but the other build phases were still available (script, copy, sources, headers).
This PR removes all the build phases and exposes the following properties in the target model:

Sources: A relative glob path to the source files.
Headers:  An object that contains relative glob paths to the public, project and private headers.
Resources: A relative glob path to the resource files.
CoreDataModels: A  list of objects that refer to Core Data models.

Note that those properties limit the folders structure for each of those types of objects. That's intentional to encourage developers to keep a clean folders structure rather than spreading the files all over the place.
This PR facilitates the future work on this giving us the flexibility to set up the the targets accordingly based on the type or product.
Solution 📦

[x] Remove build phases and build files.
[x] Update all the usages.
[x] Fix and add tests.
[x] Hide the scheme-related models as well.

The script phase has been removed, what would be the recommendation for the best method of adding a custom build phase script? e.g. swiftlint


python310Packages.mkdocstrings-python: 0.8.3 -> 0.9.0

Diff: https://github.com/mkdocstrings/python/compare/0.8.3...0.9.0
Changelog: https://github.com/mkdocstrings/python/blob/0.9.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] 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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 224507 run on x86_64-linux 1

5 packages built:

netbox
python310Packages.mkdocstrings-python
python310Packages.mkdocstrings-python.dist
python311Packages.mkdocstrings-python
python311Packages.mkdocstrings-python.dist


Importing Multiclass, Features sorted incorrectly

Describe the bug
When importing a multiclass character the subclass features get sorted into the wrong group in the features tab on foundry.
To Reproduce
Steps to reproduce the behavior:

Create a multiclass character in ddb
Import it into foundry
check features tab
See disorganization

Expected behavior
Item features should be ordered into their correct class groups
Screenshots
Here are a couple screen shots of the disorganized features on a Rouge 5/Fighter 5.

Environment:

Browser: chrome
Foundry Version: 11.315
5e System Version: 3.0.3
Module Version 4.0.13
Does this behaviour occur with other modules disabled: Yes

Additional context

A Character URL, if the problem is a character import : https://www.dndbeyond.com/characters/119675084, https://www.dndbeyond.com/characters/119674837/BdfVbQ
Details of any errors in the browser console (press F12). None that I am aware of.

And how do you wish it to look?

Well a few features were sorted into the wrong group.
In the Rouge/Fighter character the Psionic Power: Psionic Energy should be in the Fighter Features. Both classes actually have that feature but both got put in the Rogue Features when created (not pictured).
In the Ranger/Fighter Fighting Style: Archery was put in the Ranger features when it is a Fighter feature. This may also be because both classes have this feature.
So after looking deeper into this I think the issue is actually that when multiclassing and both classes have the same features those features are not sorting properly.


Papi counters don't reset

Papi counters do not reset when using  hpx::evaluate_active_counters(true);

@maciekab Is that something you could look into? Is it possible to reset the counters in the first place?

If its not possible we should probably document it. I just plan on taking care of it when processing them
On Jan 14, 2016, at 12:13 PM, Hartmut Kaiser <notifications<EMAIL_ADDRESS>wrote:
@maciekabhttps://github.com/maciekab Is that something you could look into? Is it possible to reset the counters in the first place?
—
Reply to this email directly or view it on GitHubhttps://github.com/STEllAR-GROUP/hpx/issues/1960#issuecomment-171745543.

The test in "tests/regressions/performance_counters/*" uses reset function and it was working before. I won't have time to look at this before Monday, though (proposals!).

Checked out great!  Thanks @maciekab


Question about the code

Hi
Thanks for the work, really adimre that
There is a question about the code, in the follow:
https://github.com/JialianW/TraDeS/blob/3eafd249ca0f18af8000d5798d4c552a0bd627ec/src/lib/utils/tracker.py#L196
Why you invalid the last embedding while measuring the similarity?
I tried run the code without this, and the IDF1 drops (0.1), which means it is important.
Many thanks.

Because the last one is the object itself. It needs to ignore the cosine sim for itself.

Thanks for the reply.
Just one follow-up.
the cosine sim here: cos(a, b)
https://github.com/JialianW/TraDeS/blob/3eafd249ca0f18af8000d5798d4c552a0bd627ec/src/lib/utils/tracker.py#L193
The a is unmatched detections, the b should be unmatched and histoy tracks, thus I personally think that the last one may not the object itself. Besides, by debug, I found the cos[nID-1]  is not close to 1 (should be 1 for the same object).
Thanks

Sorry, I haven't been back to this code for a long time. I just remembered that I mask out the object itself. If the nID-1 is not the object itself, then that line should be removed and it should be a bug. We only need to mask out the alive tracking id and different classes tracking id. If it only drops 0.1 IDF1, it should be fine. Thanks for the reminder!

Thanks for the reply.
Really admire your work.


React/RCTBridgeModule.h not found after completing Xcode post installation steps

App was running/building fine, but after completing the Xcode post installation step below I got several errors in my build.

In Xcode menu bar, select Product > Scheme > Manage schemes. Select your project name Scheme then click on the minus sign ― in the bottom left corner, then click on the plus sign + and rebuild your project scheme.

All libraries seem to give errors on  #import <React/RCTBridgeModule.h>. Deleting and adding the scheme again wasn't enough to get the project to build again.
steps in this link however fixed it for me:
http://stackoverflow.com/questions/41477241/react-native-xcode-upgrade-and-now-rctconvert-h-not-found
Not sure if the issue is specific for my project, I misunderstood the last step, if the last Xcode post installation step is unnecessary or the instruction is rather incomplete.
using with RN 0.42.3

Same problem

yes this solution I'm using as well. I will add it to readme.

The issue may happen if you have React reference in your pod files. Try not to use pods for ReactNative modules since they normally have a native library inside corresponding node_module


Support new Optional with syntax for version 22.0

See https://github.com/dhall-lang/dhall-lang/pull/1254

Fixed in v3


can't use word2vec.load()?

I download (People's Daily News 人民日报, Word + Character + Ngram),  and use bzip2 to decompress the file.
I want to use word2vec.load(), so I rename the file name sgns.renmin.bigram-char to sgns_renmin_bigram_char.
the error is:
ValueError: could not broadcast input array from shape (299) into shape (300)

The problem is caused by strip(). Since strip() deletes all 'space' at the beginning and the end of a line, if the word is 'space', it will be removed and the first value in the line is the first dimension of the embedding rather than a word. A good python package to load embeddings is Gensim.


Unable to start the project locally

Environment

Operating System: Darwin
Node Version:     v20.14.0
Nuxt Version:     3.11.2
CLI Version:      3.11.1
Nitro Version:    2.9.6
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      -
Runtime Modules:  -
Build Modules:    -

Version
main - 2.16.0
Reproduction
I follow these steps but I have encountered an error.
https://ui.nuxt.com/getting-started/contributing#_2-local-development-setup
Description
/
Additional context
No response
Logs
ui on  main [!] is 📦 2.16.0 via ⬢ v20.14.0
➜ nr
✔ script to run › dev:prepare

><EMAIL_ADDRESS>dev:prepare /Users/esoub/dev/f/ui
> nuxt-module-build build --stub && nuxt-module-build prepare && nuxi prepare docs

ℹ Stubbing ui                                                                                10:30:35 AM
ℹ Cleaning dist directory: ./dist                                                                                10:30:35 AM

 ERROR  Cannot use 'import.meta' outside a module                                                                                10:30:35 AM

  resolve = _kit.createResolver.call(void 0, import.meta.url).resolve
  ^^^^

  SyntaxError: Cannot use 'import.meta' outside a module
  at new Script (node:vm:116:7)
  at createScript (node:vm:268:10)
  at Object.runInThisContext (node:vm:316:10)
  at evalModule (node_modules/.pnpm/jiti@1.21.0/node_modules/jiti/dist/jiti.js:1:256254)
  at jiti (node_modules/.pnpm/jiti@1.21.0/node_modules/jiti/dist/jiti.js:1:254371)
  at src/module.ts:8:40
  at evalModule (node_modules/.pnpm/jiti@1.21.0/node_modules/jiti/dist/jiti.js:1:256443)
  at jiti (node_modules/.pnpm/jiti@1.21.0/node_modules/jiti/dist/jiti.js:1:254371)
  at dist/module.mjs:10:3
  at ModuleJob.run (node:internal/modules/esm/module_job:222:25)

 ERROR  Cannot load module. Please check dist: /Users/esoub/dev/f/ui/dist/module.mjs                                                               10:30:35 AM

 ERROR  Error while requiring module /Users/esoub/dev/f/ui/src/module: SyntaxError: Cannot use 'import.meta' outside a module                      10:30:36 AM

 ERROR  Cannot use 'import.meta' outside a module                                                                                10:30:36 AM

  resolve = _kit.createResolver.call(void 0, import.meta.url).resolve
  ^^^^

  SyntaxError: Cannot use 'import.meta' outside a module
  at new Script (node:vm:116:7)
  at createScript (node:vm:268:10)
  at Object.runInThisContext (node:vm:316:10)
  at evalModule (node_modules/.pnpm/jiti@1.21.0/node_modules/jiti/dist/jiti.js:1:256254)
  at jiti (node_modules/.pnpm/jiti@1.21.0/node_modules/jiti/dist/jiti.js:1:254371)
  at src/module.ts:8:40
  at evalModule (node_modules/.pnpm/jiti@1.21.0/node_modules/jiti/dist/jiti.js:1:256443)
  at jiti (node_modules/.pnpm/jiti@1.21.0/node_modules/jiti/dist/jiti.js:1:254371)
  at requireModule (node_modules/.pnpm/@nuxt+kit@3.11.2_rollup@3.29.4/node_modules/@nuxt/kit/dist/index.mjs:2219:26)
  at loadNuxtModuleInstance (node_modules/.pnpm/@nuxt+kit@3.11.2_rollup@3.29.4/node_modules/@nuxt/kit/dist/index.mjs:2451:92)

 ERROR  Cannot use 'import.meta' outside a module                                                                                10:30:36 AM

 ELIFECYCLE  Command failed with exit code 1.

I tryed with both node v18 and v20 and nothing work.

@Barbapapazes I remember having this issue a few weeks ago but I have no clue on how to fix that :/ Is this a fresh install with pnpm?

Yes, a fresh install

@Barbapapazes Do you encounter the same thing on the default dev branch?

I will retry

Hey @benjamincanac, getting same issue on default dev.


Stepbar needs to look better on mobile

Stepbar currently looks squashed and awful on narrow displays:

We should figure out a better design. I'm imagining something like dots connected by a line without any labels. (And then when you tap on it, it'll bring up a horizontal list of the steps... maybe sliding out from the side?)

This also intersects a bit with #312 since that will change the size of the stepbar components.

How about we just have it overflow x on both sides and center on the current step? but probably with a lighter weight design than it has now


Share link detection logic with the terminal and editor

Proposal that would allow sharing link logic: https://github.com/xtermjs/xterm.js/issues/583
Related: https://github.com/microsoft/vscode/issues/34026

fyi @isidorn

This has been done for a while 🎉


removed worker-pool package

abstract
This PR removes the worker-pool package which was separated before into https://github.com/xh3b4sd/worker-pool.
fixes
This PR fixes #203.
checklist

[ ] Make sure you read and understood the CONTRIBUTING.md.
[ ] Make sure you applied sufficient labels, milestone and assignee.
[ ] Make sure all TODOs are addressed.
[ ] Make sure there is sufficient documentation.
[ ] Make sure there are sufficient tests.
[ ] Make sure all commits are squashed before merging.
[ ] Make sure to delete the feature branch after merging.

Current coverage is 96.43% (diff: 100%)

Merging #208 into master will not change coverage

Powered by Codecov. Last update 5c9993e...60a6999

LGTM


BREAKING CHANGE: bump TensorFlow dependency to 2.7.0

This fixes compatibility with TensorFlow 2.7.0, at the cost of dropping support for older versions.

Codecov Report

Merging #252 (4f8c8d9) into master (67de238) will decrease coverage by 0.94%.
The diff coverage is 96.77%.

@@            Coverage Diff             @@
##           master     #252      +/-   ##
==========================================
- Coverage   98.79%   97.84%   -0.95%
==========================================
  Files           6        6
  Lines         746      743       -3
==========================================
- Hits          737      727      -10
- Misses          9       16       +7

Impacted Files
Coverage Δ

scikeras/_utils.py
99.08% <96.29%> (-0.92%)
:arrow_down:

scikeras/__init__.py
88.23% <100.00%> (-11.77%)
:arrow_down:

scikeras/_saving_utils.py
96.55% <100.00%> (-2.30%)
:arrow_down:

scikeras/wrappers.py
97.48% <100.00%> (-0.52%)
:arrow_down:

Continue to review full report at Codecov.

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


Integrate black-parrot into LiteX and LiteX-BuildEnv

LiteX is an FPGA SoC generator that supports a wide range of FPGA boards and platforms. It currently support multiple soft-cpus, including multiple RISC-V implementations. You can find the details about supported CPUs on this wiki page -> https://github.com/enjoy-digital/litex/wiki/Soft-CPU
It would be awesome to see Black-Parrot in the LiteX system. It would let us very easily compare the resource usage of Black-Parrot to Rocket and VexRISCV.
LiteX-BuildEnv is my environment which uses LiteX to create images for many different FPGA boards. It supports Zephyr, Linux, Micropython and bare metal firmware.
You can find a diagram of this below;

There is also a Linux on LiteX VexRISCV repository which would be cool to port to use Black-Parrot as an alternative option.
You can find the existing CPUs at https://github.com/enjoy-digital/litex/tree/master/litex/soc/cores/cpu
Rocket is probably the closest configuration which can be found at https://github.com/enjoy-digital/litex/blob/master/litex/soc/cores/cpu/rocket/core.py

Nice we will take a look!
On Thu, Jul 18, 2019 at 7:26 PM Tim Ansell<EMAIL_ADDRESS>wrote:

LiteX https://github.com/enjoy-digital/litex is an FPGA SoC generator
that supports a wide range of FPGA boards and platforms. It currently
support multiple soft-cpus, including multiple RISC-V implementations. You
can find the details about supported CPUs on this wiki page ->
https://github.com/enjoy-digital/litex/wiki/Soft-CPU
It would be awesome to see Black-Parrot in the LiteX system. It would let
us very easily compare the resource usage of Black-Parrot to Rocket and
VexRISCV.
LiteX-BuildEnv https://github.com/timvideos/litex-buildenv is my
environment which uses LiteX to create images for many different FPGA
boards. It supports Zephyr, Linux, Micropython and bare metal firmware.
You can find a diagram of this below;
[image: image]
https://user-images.githubusercontent.com/21212/61498497-7f251700-a991-11e9-90a1-bb1e6595a28e.png
There is also a Linux on LiteX VexRISCV
https://github.com/enjoy-digital/linux-on-litex-vexriscv repository
which would be cool to port to use Black-Parrot as an alternative option.
You can find the existing CPUs at
https://github.com/enjoy-digital/litex/tree/master/litex/soc/cores/cpu
Rocket is probably the closest configuration which can be found at
https://github.com/enjoy-digital/litex/blob/master/litex/soc/cores/cpu/rocket/core.py
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/black-parrot/pre-alpha-release/issues/228?email_source=notifications&email_token=AEFG5AG5QKQMXUT7VAJ3SHLQAD32ZA5CNFSM4IFASBEKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HAEIXPA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEFG5AF3HKBN5LJPB56TB2LQAD32ZANCNFSM4IFASBEA
.

@taylor-bsg If you need any help figuring out how to do this, feel free to reach out.

FYI - This work in in progress at https://github.com/enjoy-digital/litex/pull/278

Completed.


Upgrade of @opentelemetry/exporter-trace-otlp-grpc cause No Connection Established

What happened?
Steps to Reproduce
I'm trying to upgrade @opentelemetry/exporter-trace-otlp-grpc library from 0.27.0 into 0.34.0 because protobufjs v6.11.3(which is being used by @opentelemetry/exporter-trace-otlp-grpc  library) is being flagged in our Nexus-IQ server,
for this vulnerability.
We are using node v16.14.2
Our backend codes are  running in ECS-Fargate(AWS), and we are using AWS distro of otel collector, v0.20.0 running as a another service , deployed in ECS-Fargate(AWS).
When I tried to upgrade @opentelemetry/exporter-trace-otlp-grpc into 0.34.0 , I get the following error message
{"stack":"Error: 14 UNAVAILABLE: No connection established\n at callErrorFromStatus (/app/node_modules/@grpc/grpc-js/build/src/call.js:31:19)\n at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client.js:192:76)\n at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:360:141)\n at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:323:181)\n at /app/node_modules/@grpc/grpc-js/build/src/resolving-call.js:93:78\n at processTicksAndRejections (node:internal/process/task_queues:78:11)\nfor call at\n at ServiceClientImpl.makeUnaryRequest (/app/node_modules/@grpc/grpc-js/build/src/client.js:160:34)\n at ServiceClientImpl.<anonymous> (/app/node_modules/@grpc/grpc-js/build/src/make-client.js:105:19)\n at OTLPTraceExporter.send [as _send] (/app/node_modules/@opentelemetry/otlp-grpc-exporter-

Appreciate any advise or recommended versions you may have on this.  Thanks in advance.
Expected Result
We expect to be able to connect to our AWS distro of otel collector.
Actual Result
Getting the following error msg in the logs
{"stack":"Error: 14 UNAVAILABLE: No connection established\n at callErrorFromStatus (/app/node_modules/@grpc/grpc-js/build/src/call.js:31:19)\n at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client.js:192:76)\n at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:360:141)\n at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:323:181)\n at /app/node_modules/@grpc/grpc-js/build/src/resolving-call.js:93:78\n at processTicksAndRejections (node:internal/process/task_queues:78:11)\nfor call at\n at ServiceClientImpl.makeUnaryRequest (/app/node_modules/@grpc/grpc-js/build/src/client.js:160:34)\n at ServiceClientImpl.<anonymous> (/app/node_modules/@grpc/grpc-js/build/src/make-client.js:105:19)\n at OTLPTraceExporter.send [as _send] (/app/node_modules/@opentelemetry/otlp-grpc-exporter-

Additional Details
Here are my package.json in our backend service, we are using node v16.11.3)
 "@opentelemetry/api": "1.0.4",
        "@opentelemetry/auto-instrumentations-node": "0.28.0",
        "@opentelemetry/exporter-trace-otlp-grpc": "0.34.0",
        "@opentelemetry/resources": "1.0.1",
        "@opentelemetry/sdk-node": "0.27.0",

This is our tracer.js code at our backend service
import { Resource } from "@opentelemetry/resources";
import { SemanticResourceAttributes } from "@opentelemetry/semantic-conventions";
import { registerInstrumentations } from "@opentelemetry/instrumentation";
import {
    ExpressInstrumentation,
    ExpressLayerType,
} from "@opentelemetry/instrumentation-express";
import { HttpInstrumentation } from "@opentelemetry/instrumentation-http";
import { WinstonInstrumentation } from "@opentelemetry/instrumentation-winston";
import { AwsInstrumentation } from "@opentelemetry/instrumentation-aws-sdk";
import { MySQL2Instrumentation } from "@opentelemetry/instrumentation-mysql2";
import { NodeTracerProvider } from "@opentelemetry/sdk-trace-node";
import { diag, DiagConsoleLogger, DiagLogLevel } from "@opentelemetry/api";
import {
    BatchSpanProcessor,
    TracerConfig,
} from "@opentelemetry/sdk-trace-base";
import { OTLPTraceExporter } from "@opentelemetry/exporter-trace-otlp-grpc";
import { JaegerExporter } from "@opentelemetry/exporter-jaeger";

const CMP_ENV_NAME = process.env.CMP_ENV || "local"; // Define the current CMP running environment

const tracerConfig: TracerConfig = {
    resource: new Resource({
        [SemanticResourceAttributes.SERVICE_NAME]: "cmp-backend",
        [SemanticResourceAttributes.DEPLOYMENT_ENVIRONMENT]: CMP_ENV_NAME,
    }),
};

//let exporter: JaegerExporter | OTLPTraceExporter;
let exporter: OTLPTraceExporter;
//if (CMP_ENV_NAME === "local") {
  //  console.log("opentelemetry: tracer init ... using jaeger exporter");
    //exporter = new JaegerExporter({
      //  endpoint: "http://localhost:14268/api/traces",
    //});
//} else {
    const hostname = process.env.CMP_OTEL_COLLECTOR_URL || "localhost:4317";

    console.log("opentelemetry: tracer init ... using otel collector exporter");
    console.log(`opentelemetry: connecting to hostname... ${hostname}`);
    exporter = new OTLPTraceExporter({
        url: `grpc://${hostname}`,
    });
//}

const provider: NodeTracerProvider = new NodeTracerProvider(tracerConfig);

diag.setLogger(new DiagConsoleLogger(), DiagLogLevel.ERROR);

provider.addSpanProcessor(new BatchSpanProcessor(exporter));
provider.register();

registerInstrumentations({
    instrumentations: [
        new ExpressInstrumentation({
            ignoreLayersType: [ExpressLayerType.MIDDLEWARE],
        }),
        new HttpInstrumentation({
            ignoreIncomingPaths: [/^.*\/version$/], // skip route used by ECS for health check to reduce noise
        }),
        new WinstonInstrumentation(),
        new AwsInstrumentation(),
        new MySQL2Instrumentation(),
    ],
});

console.info("opentelemetry: tracer init ... complete");

process.on("SIGTERM", () => {
    exporter.shutdown();
    console.info("opentelemetry: tracer shutdown ... complete");
});

We use AWS distro of the otel collector, v0.20.0. which is running as a separate service
This is our config.yaml
receivers:
  otlp/traces:
    protocols:
      grpc:
        endpoint: <IP_ADDRESS>:4317
  otlp/metrics:
    protocols:
      grpc:
        endpoint: <IP_ADDRESS>:4318
  awsecscontainermetrics:

exporters:
  otlp/elastic:
    endpoint: "${ELASTIC_APM_SERVER_ENDPOINT}"
    headers:
      Authorization: "Bearer ${ELASTIC_APM_SERVER_TOKEN}"

  awsemf:
    namespace: ECS/ContainerInsights
    log_group_name: "/aws/ecs/containerinsights/{ClusterName}/performance"
    log_stream_name: "{TaskId}"
    resource_to_telemetry_conversion:
      enabled: true
    dimension_rollup_option: NoDimensionRollup
    metric_declarations:
      - dimensions: [[ClusterName], [ClusterName, TaskDefinitionFamily]]
        metric_name_selectors:
          - MemoryUtilized
          - MemoryReserved
          - CpuUtilized
          - CpuReserved
          - NetworkRxBytes
          - NetworkTxBytes
          - StorageReadBytes
          - StorageWriteBytes
      - metric_name_selectors: [container.*]

processors:
  memory_limiter:
    check_interval: 1s
    limit_mib: 1024

  batch/traces:
    timeout: 1s
    send_batch_size: 50

  batch/metrics:
    timeout: 60s

  filter:
    metrics:
      include:
        match_type: strict
        metric_names:
          - ecs.task.memory.reserved
          - ecs.task.memory.utilized
          - ecs.task.cpu.reserved
          - ecs.task.cpu.utilized
          - ecs.task.network.rate.rx
          - ecs.task.network.rate.tx
          - ecs.task.storage.read_bytes
          - ecs.task.storage.write_bytes
          - container.duration
  metricstransform:
    transforms:
      - metric_name: ecs.task.memory.utilized
        action: update
        new_name: MemoryUtilized
      - metric_name: ecs.task.memory.reserved
        action: update
        new_name: MemoryReserved
      - metric_name: ecs.task.cpu.utilized
        action: update
        new_name: CpuUtilized
      - metric_name: ecs.task.cpu.reserved
        action: update
        new_name: CpuReserved
      - metric_name: ecs.task.network.rate.rx
        action: update
        new_name: NetworkRxBytes
      - metric_name: ecs.task.network.rate.tx
        action: update
        new_name: NetworkTxBytes
      - metric_name: ecs.task.storage.read_bytes
        action: update
        new_name: StorageReadBytes
      - metric_name: ecs.task.storage.write_bytes
        action: update
        new_name: StorageWriteBytes

  resource:
    attributes:
      - key: ClusterName
        from_attribute: aws.ecs.cluster.name
        action: insert
      - key: aws.ecs.cluster.name
        action: delete
      - key: ServiceName
        from_attribute: aws.ecs.service.name
        action: insert
      - key: aws.ecs.service.name
        action: delete
      - key: TaskId
        from_attribute: aws.ecs.task.id
        action: insert
      - key: aws.ecs.task.id
        action: delete
      - key: TaskDefinitionFamily
        from_attribute: aws.ecs.task.family
        action: insert
      - key: aws.ecs.task.family
        action: delete
      - key: TaskARN
        from_attribute: aws.ecs.task.arn
        action: insert
      - key: aws.ecs.task.arn
        action: delete
      - key: DockerName
        from_attribute: aws.ecs.docker.name
        action: insert
      - key: aws.ecs.docker.name
        action: delete
      - key: TaskDefinitionRevision
        from_attribute: aws.ecs.task.version
        action: insert
      - key: aws.ecs.task.version
        action: delete
      - key: PullStartedAt
        from_attribute: aws.ecs.task.pull_started_at
        action: insert
      - key: aws.ecs.task.pull_started_at
        action: delete
      - key: PullStoppedAt
        from_attribute: aws.ecs.task.pull_stopped_at
        action: insert
      - key: aws.ecs.task.pull_stopped_at
        action: delete
      - key: AvailabilityZone
        from_attribute: cloud.zone
        action: insert
      - key: cloud.zone
        action: delete
      - key: LaunchType
        from_attribute: aws.ecs.task.launch_type
        action: insert
      - key: aws.ecs.task.launch_type
        action: delete
      - key: Region
        from_attribute: cloud.region
        action: insert
      - key: cloud.region
        action: delete
      - key: AccountId
        from_attribute: cloud.account.id
        action: insert
      - key: cloud.account.id
        action: delete
      - key: DockerId
        from_attribute: container.id
        action: insert
      - key: container.id
        action: delete
      - key: ContainerName
        from_attribute: container.name
        action: insert
      - key: container.name
        action: delete
      - key: Image
        from_attribute: container.image.name
        action: insert
      - key: container.image.name
        action: delete
      - key: ImageId
        from_attribute: aws.ecs.container.image.id
        action: insert
      - key: aws.ecs.container.image.id
        action: delete
      - key: ExitCode
        from_attribute: aws.ecs.container.exit_code
        action: insert
      - key: aws.ecs.container.exit_code
        action: delete
      - key: CreatedAt
        from_attribute: aws.ecs.container.created_at
        action: insert
      - key: aws.ecs.container.created_at
        action: delete
      - key: StartedAt
        from_attribute: aws.ecs.container.started_at
        action: insert
      - key: aws.ecs.container.started_at
        action: delete
      - key: FinishedAt
        from_attribute: aws.ecs.container.finished_at
        action: insert
      - key: aws.ecs.container.finished_at
        action: delete
      - key: ImageTag
        from_attribute: container.image.tag
        action: insert
      - key: container.image.tag
        action: delete

extensions:
  health_check:

service:
  extensions:
    - health_check

  pipelines:
    traces:
      receivers:
        - otlp/traces
      processors:
        - memory_limiter
        - batch/traces
      exporters:
        - otlp/elastic

    metrics:
      receivers:
        - awsecscontainermetrics
        - otlp/metrics
      processors:
        - memory_limiter
        - batch/metrics
        - filter
        - metricstransform
        - resource
      exporters:
        - awsemf

OpenTelemetry Setup Code
No response
package.json
No response
Relevant log output
{"stack":"Error: 14 UNAVAILABLE: No connection established\n at callErrorFromStatus (/app/node_modules/@grpc/grpc-js/build/src/call.js:31:19)\n at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client.js:192:76)\n at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:360:141)\n at Object.onReceiveStatus (/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:323:181)\n at /app/node_modules/@grpc/grpc-js/build/src/resolving-call.js:93:78\n at processTicksAndRejections (node:internal/process/task_queues:78:11)\nfor call at\n at ServiceClientImpl.makeUnaryRequest (/app/node_modules/@grpc/grpc-js/build/src/client.js:160:34)\n at ServiceClientImpl.<anonymous> (/app/node_modules/@grpc/grpc-js/build/src/make-client.js:105:19)\n at OTLPTraceExporter.send [as _send] (/app/node_modules/@opentelemetry/otlp-grpc-exporter-

Hi, thanks for reaching out :slightly_smiling_face:
Looking at the provided tracer.js, it looks like the grpc:// in the url when setting up the TracerProvider may be what's causing the issue - could you try using http:// (if you're using an insecure endpoint) or https:// (if you're using a secure endpoint)?
did grpc:// work for 0.27.0? :thinking:

I am having a very similar problem. I have tried prefixing with http:// and the error persists.
Ive upgraded from 0.27.0 which was working with prefix grpc://

@laurencefass interesting, that should not happen - could you drop some information on which packages you're using? :thinking:
I tried reproducing the issue with the info that @laurencefass provided, and it is indeed not working with grpc://.
I looked in the history, and the reason for that is that we changed the default from insecure to secure in 0.29.0 to align it with the specification. When updating to 0.29.0 or later, you can change it over to http:// which will select insecure as per the OTel specification, or use the OTEL_EXPORTER_OTLP_INSECURE=true environment variable to change it to insecure.
I had to update some of the package versions to get the example in the OP to compile -> updated versions below
    "@opentelemetry/auto-instrumentations-node": "0.34.0",
    "@opentelemetry/exporter-trace-otlp-grpc": "0.34.0",
    "@opentelemetry/resources": "1.8.0",
    "@opentelemetry/sdk-node": "0.34.0",

With that, amazon/aws-otel-collector:v0.20.0 and using http:// I'm able to export traces.

hi @pichlermarc - it  works if I use gprc at     "@opentelemetry/exporter-trace-otlp-grpc": "0.27.0", unfortunately, I need to upgrade to 0.34.0  to fix a protobufjs vulnerability.

You mention you can export traces. Have you had any success with metrics. Im getting connection failed errors on metrics and traces.

@laurencefass were you able to resolve the problem you had with metrics? :thinking: For me, metrics and traces are exported fine now on the most recent revision (using http://) of the sample you provided. :thinking:

@pichlermarc laurencefass/opentelemetry is updated and works correctly with metrics and traces.

Happy to hear that :slightly_smiling_face:

The resolution was simply to replace the OTLPExporter urls localhost with the opentelemetry collector docker hostname (as defined in docker-compose.yml). Im still not sure why localhost causes connection issue so any insights most welcome.

@laurencefass Since the collector is running in a different container, referring to localhost on the app's container will refer to the container itself, not the host that the container is running on. This is why using the hostname of the collector's container fixes the problem. :slightly_smiling_face:

hi @pichlermarc - my issue is resolved, here are my packages.json at my backend code,
 "@opentelemetry/api": "1.3.0",
        "@opentelemetry/auto-instrumentations-node": "0.34.0",
        "@opentelemetry/exporter-trace-otlp-grpc": "0.34.0",
        "@opentelemetry/resources": "1.8.0",
        "@opentelemetry/sdk-node": "0.34.0",

and then, as suggested, I used http instead of grpc in my backend code
Weirdly, my config at  AWS distro of the otel collector, v0.20.0. which is running as a separate service, is still working, eventhough my receivers are still set in grpc :)
receivers:
  otlp/traces:
    protocols:
      grpc:
        endpoint: <IP_ADDRESS>:4317
  otlp/metrics:
    protocols:
      grpc:
        endpoint: <IP_ADDRESS>:4318
  awsecscontainermetrics:

thanks very much..

Hi @elizabethlumban, glad to hear that you could resolve the issue. :slightly_smiling_face:
Using http instead of grpc as a scheme in the url of the gRPC exporter does not change the protocol of the gRPC exporter; it remains grpc, but it's using an insecure channel instead. It's specified like that in the document I linked above - it's a bit confusing, but you can rest assured that you're still using gRPC to export. :slightly_smiling_face:


8413.6 Add install on new node option for redis

Shippable/pm#8413
Right now, no additional input prompts for Redis should show if the "single-node install" button is checked.
Add the install on new node radio button as an option for redis. If the user clicks that button, show the following for redis (in addition to the password):

A prompt and input box for IP
The ssh key to copy, with instructions to copy it and add it to their node
A checkbox saying something like "I have added this key to my node"
A save button. When clicked, this should send the IP and runInit=false in the body of the POST to /api/redis. This should be disabled if the db is not initialized.

(see drawing on the wall)

complete. closing.


Release Google.Cloud.MediaTranslation.V1Beta1 version 1.0.0-beta01

Changes in this release:
Initial beta release.

Created release for Google.Cloud.MediaTranslation.V1Beta1-1.0.0-beta01


Processor should return distinct entities.

Hi @kennethbrake, i rebased against master as you suggested. Please have a look

closed by 0870939a0c7cfb5e7724b5affb1d1fc0ef98569b - also replaced list with a set in the opennlpservice in 55f08d415c658fffa0769a1ca04757b0b608bbd7, so there is no need merge too much


Unit test added for Variable node

This unit test is testing the thrown exception is
NLogConfigurationException or not when variable node is written to wrong
place.
For #1128
Configuration validation will be done at https://github.com/NLog/NLog/issues/1174

Current coverage is 73.55%

Merging #1173 into master will decrease coverage by -0.07% as of dbb492d

@@            master   #1173   diff @@
======================================
  Files          265     265
  Stmts        15057   15057
  Branches      1651    1652     +1
  Methods          0       0
======================================
- Hit          11086   11075    -11
- Partial        417     418     +1
- Missed        3554    3564    +10

Review entire Coverage Diff as of dbb492d

Uncovered Suggestions

+0.09% via ...nternal/AspHelper.cs#206...218
+0.09% via ...nternal/AspHelper.cs#188...200
+0.09% via ...nternal/AspHelper.cs#170...182
See 7 more...

Powered by Codecov. Updated on successful CI builds.

Thanks! Can you also make a variant where the <variable> is after the <target>?

Thanks! Can you also make a variant where the  is after the ?

+1

Sure. I made it using InlineData and Theory :)

There are problems with Mono reference and Theory attribute (for Silverlight).
I am going to remove Theory attribute but I am not sure about Mono error. It is not related to this commit.

@UgurAldanmaz may be you just need to surround with conditional statements.

Fixes #1128

Thanks! It had been merged!

Thanks! I am closing related issue.


VS Code debug features randomly break with 1.57+

Issue Type: Bug
When running VS Code 1.57 (and now 1.57.1), the editor's Run and Debug panel is empty, the debug console is gone, and some plugins fail to render their UI. This appears to happen randomly each time I open the application (sometimes everything works fine, most of the time it doesn't). When I revert back to 1.56, I stop seeing these issues entirely.
I've tried manually disabling all extensions as well as launching with the --disable-extensions flag. Same behavior both ways.
I've checked VS Code's logs and while I don't know if these are related, here are a few errors I'm seeing. These occur both with all extensions enabled and all extensions disabled.
Log (Extension Host):
[2021-06-18 13:17:51.927] [exthost] [error] [ExtHostStorage] {"code":"Unknown","name":"Error (FileSystemError)"}
Log (Window):
[2021-06-18 13:29:54.035] [renderer1] [error] Handler already set!: Error: Handler already set!
VS Code version: Code 1.57.1 (507ce72a4466fbb27b715c3722558bb15afa9f48, 2021-06-17T13:28:32.912Z)
OS version: Darwin x64 20.5.0
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 x 2600)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
12, 8, 8

Memory (System)
16.00GB (0.02GB free)

Process Argv
--crash-reporter-id 220c192d-db2d-4f14-96ac-d7c741028cda

Screen Reader
no

VM
0%

Extensions (39)

Extension
Author (truncated)
Version

project-manager
ale
12.2.0

cucumberautocomplete
ale
2.15.1

ng-template
Ang
12.0.5

swagger-viewer
Arj
3.0.1

vscode-toggle-quotes
Bri
0.3.4

transformer
dak
1.11.1

vscode-eslint
dba
2.1.23

EditorConfig
Edi
0.16.4

vscode-lombok
Gab
1.0.1

gc-excelviewer
Gra
3.0.42

todo-tree
Gru
0.0.213

vscode-test-explorer
hbe
2.20.4

vscode-auto-open-markdown-preview
hnw
0.0.4

vscode-todo-highlight
jgc
2.0.2

vscode-docker
ms-
1.13.0

vscode-kubernetes-tools
ms-
1.3.3

remote-containers
ms-
0.183.0

test-adapter-converter
ms-
0.0.10

debugger-for-chrome
msj
4.12.12

gradle-language
nac
0.2.3

vscode-concourse
Piv
1.25.1

vscode-spring-boot
Piv
1.25.1

angular-karma-test-explorer
raa
1.2.8

java
red
0.79.2

vscode-commons
red
0.0.6

vscode-xml
red
0.16.1

vscode-yaml
red
0.20.0

vscode-sort-json
ric
1.20.0

jinjahtml
sam
0.16.0

vscode-checkstyle
she
1.4.0

vscode-stylelint
sty
0.86.0

markdowntable
Tak
0.6.0

vscodeintellicode
Vis
1.2.14

vscode-java-debug
vsc
0.34.0

vscode-java-dependency
vsc
0.18.4

vscode-java-pack
vsc
0.16.0

vscode-java-test
vsc
0.30.0

vscode-icons
vsc
11.5.0

whitesource-advise
Whi
21.5.2

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
vspre833:30321513
pythonptprofiler:30281270
vshan820:30294714
pythondataviewer:30285071
vscus158:30321503
pythonvsuse255cf:30323309
vscorehov:30309549
vscod805:30301674
vscextlang:30322306
binariesv615cf:30323120

I was seeing this sporadically in Insiders too, but since last week it is gone.

Thanks for filling this issue. Can you reproduce using Visual Studio Code Insiders https://code.visualstudio.com/insiders/

I was using the Insiders version all day today and I didn't see the issue even once, so it seems like 1.58 fixes the issue. Is it possible to push that fix to 1.57?

No. We will soon ship a new release.
Also take into account that maybe one of your extensions is breaking this flow.
So for now closing this as no code change is planned


⚠ Samsung has degraded performance

In d4d8f88, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2483 ms

Resolved: Samsung performance has improved in a6599c8.


fix bug of iOS 10 loop not infinitely

https://github.com/NSRare/NSGIF/issues/22

@smhjsw Just tried and this fixes the problem, even on Chrome

🚀


Flatlist example in the docs not rendering

Description
On the documentation for Flatlist, I tried running the example in the browser. I then got an error on the simulator saying "FlatListExample could not be found!"
Reproduction
Link to docs
I go onto the docs, and click "Run this example" near the bottom.
Solution
The documentation for that page needs to be updated with the latest repository.
Additional Information

React Native version: 0.43.0
Platform: Documentation, Google Chrome
Operating System: MacOS
Dev tools: None

#13053

#13053

#13053

#13045

I think this is actually affecting more than just FlatList. Other examples are not rendering. RNPlay is going away at the end of the month, so we'll need to either migrate the examples to run in Sketch, or remove the prompt entirely.

I took a further look at this. So there's two different types of runnable examples that display in a modal:

One-off examples linked from the markdown docs (e.g. https://facebook.github.io/react-native/docs/direct-manipulation.html), which is something someone uploaded to RNPlay long ago - and in some cases, the example no longer exists. In the case of Direct Manipulation, the example was created before RNPlay switched to Expo, and has been disabled: https://rnplay.org/apps/JXkgmQ

Then there's the examples in the API docs (such as StatusBar) where we use one of two UIExplorer apps uploaded to appetize.org around two years ago (iOS and Android), and pass along some params to load the correct example. This is why FlatList fails to load in this case, because the UIExplorer app being used here hasn't been updated in some time and does not contain FlatList.

For #1, we can migrate these examples to Sketch.
For #2, we can update the app on appetize to use a more up to date version of UIExplorer, but we would also need to make this more resilient as the issue will show up again when a new component is added to UIExplorer. Not to say, the examples are likely to get out of sync as the UIExplorer app gets updated in the repo.

#1 has been resolved on master, and https://github.com/facebook/react-native/pull/13644 takes care of #2.


Adding support for {individual: true} option for fetch and refresh

Per our discussion. This is my attempt at adding support for doing a refresh with individual add and remove events instead of one big refresh.
Another note, one of the tests fail, because of what I believe is a bug in the set function. The id gets set as and attribute which incorrectly triggers the change event even if no other attributes changed.
Take a look at the new collection tests and you'll know see what I mean. (I'll file an individual bug for that as well).

fetch() now takes an add: true option which will add the models to the collection (firing individual events) instead of reset-ing the collection. I believe this covers our bases, as you can fetch with add to add new models ... as well as fetching with add after doing a reset in order to get reset-like full refreshes with all individual add events.


Install kubectl binary in e2e run suite GH workflow

What this PR does / why we need it:
Install kubectl binary with specific version v1.30.0 in e2e run suite GH workflow. e2e nightly runs started failing after #659 where we set MINIMUM_KUBECTL_VERSION to v1.30.0. However, version of kubectl used in GH env (not coming from our codebase) seems to be 1.28.4 which is <  v1.30.0 MINIMUM_KUBECTL_VERSION, hence, they started failing https://github.com/rancher/turtles/actions/runs/10419056888/job/28856363769.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Tested this patch here: https://github.com/rancher/turtles/actions/runs/10421045742/job/28862355979
Checklist:

[ ] squashed commits into logical changes
[ ] includes documentation
[ ] adds unit tests
[ ] adds or updates e2e tests

#668 is similar but they are not blocking each other

I would not merge this, since #668 already fix e2e nightly, so waiting on that to merge and will close this.


RFC major release 9.0 - New entry point for controller logic

See this issue for some background: https://github.com/SocketCluster/socketcluster/issues/332
Proposal for new entry point for controllers (e.g. Workers and Brokers).
Node.js is currently rolling out ES6 modules (though it's currently still behind an --experimental-modules flag in Node.js v8.6.1+); this allows developers to import ES6 modules from inside Node.js using the import statement (as an alternative to require). See https://medium.com/dailyjs/es6-modules-node-js-and-the-michael-jackson-solution-828dc244b8b
Currently, ES6 modules are not supported by SC.
In theory, we could wait for Node.js to implement 'dynamic import' (https://github.com/tc39/proposal-dynamic-import); then SC could support ES6 modules without requiring any code changes to the backend developer API; but because Node.js is in
the middle of this transition, this gives us the opportunity to revise the current entry point for SC controllers (workers and brokers).
Although this would be a breaking change, migration to the new format should be straightforward and low risk.
The current entry point for worker processes (worker.js) looks like this:
// SocketCluster decides when the run() function is invoked.

module.exports.run = function (worker) {
    // Custom worker logic goes here.

    worker.scServer.on('connection', (socket) => {
        // Handle the new connection.
    })
};

Disadvantages of the current approach:

Doesn't work with the upcoming Node.js ES6 module import feature (at least until we have dynamic import).
Developer can't decide when or how the worker is instantiated; SC decides this.
This approach is quite unique to SC and doesn't follow any major known conventions (though it was loosely inspired by Java threads which have a run function as entry point).

The proposed alternatives will affect some of the boilerplate logic in worker.js. The approaches which are currently being considered are:
1. Function-based approach to instantiate the controller.
let SCWorker = require('socketcluster').SCWorker;

// The worker instance is created here.
SCWorker.create({
  run () {
    // Custom worker logic goes here.
    // You can reference to the worker in here with 'this'.

    this.scServer.on('connection', (socket) => {
        // Handle the new connection.
    });
  }
});

OR
2. This is a variation of the approach above using the 'new' keyword instead of 'create'.
let SCWorker = require('socketcluster').SCWorker;

new SCWorker({
  run() {
    // Custom worker logic goes here.
    // You can reference to the worker in here with 'this'.

    this.scServer.on('connection', (socket) => {
        // Handle the new connection.
    });
  }
})

OR
3. This class-based approach is closer to front-end frameworks like React.  It's also similar to how threads are used in Java (via the Runnable interface).
let SCWorker = require('socketcluster').SCWorker;

class WorkerController extends SCWorker {
  run() {
    // Custom worker logic goes here.
    // You can reference to the worker in here with 'this'.

    this.scServer.on('connection', (socket) => {
        // Handle the new connection.
    });
  }
}

new WorkerController();

All the approaches above work similarly; the question is mostly about syntax and convention - Which one makes the most sense to developers?
Which one is more future-proof?
Once this change is made, we should assume this is how it's going to stay for the foreseeable future.
The benefits of any of the three proposed approaches above are that developers will be able to:

import ES6 modules from inside the worker controller file (worker.js) as an alternative to the current require() approach.
Delay when and how the worker becomes instantiated (since it is now the developer's responsibility as part of the boilerplate).
Provide/override functions in the worker to modify default behaviour. For example, we could allow the developer to provide or override a getHTTPServer() method which will allow developers to create their own HTTP server finstead of the basic Node.js one. This might help with integrating some backend frameworks with SC.

Please vote for your favorite approach in the comments below.

Thanks for letting us know about that and asking for opinions!
I fully support this change, it would be a very welcomed feature and the breaking changes seem pretty trivial.

@gustojs Yes you can vote for all of them if you don't have a preference; it's good to know. I also think it's close. You can also suggest alternatives if you have other ideas.

I would love this!!! Currently, I have a worker class that's a wrapper and this would make things so much easier. +1!!!!

Oh, I use the static create(options = {}) { return new Worker(options) } so I would rather use create instead of new.

This has now been released to npm as socketcluster version 9.0.3 - It's also been pushed to DockerHub.
@mauritslamers The entry point supports all the formats that were put forward since they all ended up being compatible with almost no added complexity. I did not use any classes behind the scenes except for in the controller scripts themselves as defaults (the user is free to change to whatever approach they prefer).

I was using this code to run a single-process socketcluster in development:
import socketClusterServer from 'socketcluster-server'
import http from 'http'
import {run} from './worker'

const httpServer = http.createServer()
const scServer = socketClusterServer.attach(httpServer)

run({httpServer, scServer})
httpServer.listen(80)

(transpiled of course)
How should I adjust this so it works again?

@jondubois Hey man, I moved everything over and it makes everything so much easier. Thanks man!! Awesome change!!!


A portable version of the software

Description of the new feature / enhancement
Have the ability to put PowerToys onto an external disk to be used with other computers.
Scenario when this would be used?
I have worked on other people's computers, and having the ability to use a feature of PowerToys like File Locksmith on a computer where you don't want to install PowerToys would be useful.
Supporting information
No response

/dup https://github.com/microsoft/PowerToys/issues/598
We currently have no plans for a portable version


"Terminal: Run Selected Text In Active Terminal" spawns new terminal window instead use existing one WHEN "Tasks: Run Task" was run

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

VS Code Version: 1.78.2
OS Version: MacOS Venture 13.3.1 (a) (22E772610a)

Steps to Reproduce:

Run code  --disable-extensions ~/projects/tests/vscodeselectedbug
Create task file  .vscode/tasks.json with content

{
	"version": "2.0.0",
	"tasks": [
		{
			"label": "IRB",
			"type": "process",
			"command": "irb" // or any REPL you want
		}
	]
}

Create ./test.rb file with content

2 + 2

Spawn IRB task (Cntl+P => Tasks: Run Task => IRB)
Put your cursor on line 1: of test.rb (2 + 2)
Eval the line to IRB terminal (Cntl+P => Terminal: Run Selected Text In Active Terminal)

Actual behaviour: It spawn new terminal window and evaluates 2 + 2 in it (See screenshot)
Expected behaviour: It should not spawn new terminal window and evaluate 2 + 2 in IRB window

it was fixed somewhere here https://github.com/microsoft/vscode/pull/173573
and somewhere here was broken https://github.com/microsoft/vscode/pull/180467
I assume it ^^ since in previous update it was working but in current release it is broken

We changes the behavior and have since changed in back in the following version. https://github.com/microsoft/vscode/pull/173573 is only related to focus, it broke in https://github.com/microsoft/vscode/pull/180467 due to an intentional change, and then we got feedback to change it back which we did in https://github.com/microsoft/vscode/issues/182002.


add site title word task

add test case

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (develop@cd198a0). Click here to learn what that means.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             develop     #204   +/-   ##
==========================================
  Coverage           ?   62.54%
  Complexity         ?      302
==========================================
  Files              ?      120
  Lines              ?     1068
  Branches           ?       50
==========================================
  Hits               ?      668
  Misses             ?      357
  Partials           ?       43

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Select] Cursor inserted at beginning instead of end of value

Current Behavior
Sandbox: https://codesandbox.io/s/ndonk?module=/example.tsx

Select an option
Click into the Select
Notice the text cursor is inserted at the beginning of the value

I understand that this behavior may be intentional, as it allows the user to "just start typing" to choose a new value. That conflicts with the behavior of a standard text input, though, so I would encourage a different approach.

Expected Behavior

Select an option
Click into the Select
The text cursor is inserted at the end of the value

If you agree this is an issue and can provide some guidance on where to get started, I'm happy to try my hand at a fix.

Your Environment

Tech
Version

Base UI
v8.16.5

React
16.8.6

browser
Mac Chrome, Mac Firefox, (all?)

[x] I have searched the issues of this repository and believe that this is not a duplicate.

@gergelyke Can I work on this issue?

@Patil2099 are you still looking into this issue?


[BUG] JSQLParser Version : 4.9  RDBMS :  not support clickhouse quantile expression

Always check against the Latest SNAPSHOT of JSQLParser and the Syntax Diagram
Failing SQL Feature:
quantile(0.95)(cost)   not support
SQL Example:
select toStartOfDay(timestamp) AS date, count(1) as count, quantile(0.95)(cost) as 95cost from apm_log_event
Software Information:

JSqlParser 4.9
Database :Clickhouse

Greetings.
This is unsupported syntax far away from any standard and you would need to provide or sponsor an implementation to make it happen.


Code 39 Not Working

Everything works great other than barcode type code 39 on Andriod. Also very excited about the future of this project. Hope this can be resolved.

looks I forgot to add code39 checking on Android source.
I fixed in <IP_ADDRESS>, could you please help to try if it is work?
I do not have Android device right now.
Thank you

Works great! Thank you I appreciate the fast response & release.


SDK interface mutates inputs instead of returns values

I still find this a bit awkward:
aThing := &corev1.Thing{}
err := sdk.Get(aThing) // aThing is mutated, this only returns an err

vs something more like:
requestConfig = &timeToGet.Thing{}
aThing, err := sdk.Get(requestConfig) // this is more intuitive, no?

This is still pre-alpha, so seems like a good time to raise the issue as it would obviously be a breaking change.  Is there good reason to stick with the mutating convention?
Thanks!

We are currently in the process of migrating the SDK to use the controller-runtime, and we will be using the controller-runtime's client instead of our old client: https://godoc.org/sigs.k8s.io/controller-runtime/pkg/client
You can view the current status of the controller-runtime migration on the refactor/controller-runtime branch: https://github.com/operator-framework/operator-sdk/tree/refactor/controller-runtime

Ok great, I'm guessing that will change the API similar to what I mentioned.
Is this a change that will come while still in the pre-alpha state? or post 1.0? Thanks!

The change will come as soon as the controller-runtime refactor branch is merged onto the master.
We definitely won't be in pre-alpha state by that point. Whether we call it beta or 1.0 isn't decided yet.

I'm not sure that the controller-runtime actually solves the problem:
https://github.com/kubernetes-sigs/controller-runtime/blob/master/pkg/client/client.go#L125
https://godoc.org/sigs.k8s.io/controller-runtime/pkg/client#Reader
from the docs:
type Reader interface {
    // Get retrieves an obj for the given object key from the Kubernetes Cluster.
    // obj must be a struct pointer so that obj can be updated with the response
    // returned by the Server.
    Get(ctx context.Context, key ObjectKey, obj runtime.Object) error

    // List retrieves list of objects for a given namespace and list options. On a
    // successful call, Items field in the list will be populated with the
    // result returned from the server.
    List(ctx context.Context, opts *ListOptions, list runtime.Object) error
}

The fact that you are still passing in an object that will be mutated is what is concerning.
Perhaps this issue was prematurely closed?

I do not think we should implement this change IMO.

There are many changes to the object that could occur when updating it, say you have aThing and you update it twice. Instead of a user having to deal with resourceVersions and that stuff this handles it for them. This allows you to create and then update the object that you are creating/mutating.

It appears this is a pretty normal way to interact with Kube clients and I don't think that we should change.

Passing a pointer to a function is a common idiom for telling the user we are going to change your object. see json.Unmarshal.

json.Unmarshal seems generic, deliberately.  I get that, JSON is generic data.  Give it Unmarshall(data, interface) and it will parse out the data into the interface.  But I think the interface is generally an "empty thing" that gets "filled up", however, I'll admit that I am new enough to Golang that I may be mistaken.
I still favor avoiding mutation when possible, but chewing on this. Thanks!


Running images by name fails.

Create an aci with a name without a domain (reduce-worker) and a version label
or just convert it using docker2aci or running
rkt fetch docker://busybox:latest
Then try to run it by image name from the store.
# rkt run --local busybox:latest`
rkt only supports http, https, docker or file URLs (busybox:latest)

The error is caused by rkt/images.go fetchSingleImage that parses the name using url.Parse and it's interpreted as an Opaque URL with scheme busybox.
Before trying to fix it I opened appc/spec#479 to firstly understand if such name is acceptable or it must contain a domain.

Related to #715


[Starter Project - Zurb Template] Cache Bust Assets

I was wondering how do you cache bust assets in the official Zurb Template Starter Project and came up with the following solution via https://github.com/zurb/panini/issues/121#issuecomment-308880914:
Install gulp-cache-bust: npm install --save-dev gulp-cache-bust
Import it in gulpfile.babel.js: import cachebust from 'gulp-cache-bust';
Add a new function:
// Bust asset caches in index.html
function bustAssetCache(done) {
  gulp.src('./dist/index.html')
    .pipe(cachebust({
        type: 'timestamp'
    }))
    .pipe(gulp.dest('./dist'));
  done();
}

and call that function in gulp build task:
// Build the "dist" folder by running all of the below tasks
gulp.task('build',
 gulp.series(clean, gulp.parallel(pages, sass, javascript, images, copy), styleGuide, bustAssetCache));

I am closing the issue since it is resolved, maybe it will be reference for somebody searching for a similar solution in the future.


Symfony 4 - The profiler template "PixersDoctrineProfilerBundle:Collector:profiler.html.twig" for data collector "doctrine_profiler" does not exist.

By installing the library on Symfony 4 project the profiler stop loading and show this error message:
The profiler template "PixersDoctrineProfilerBundle:Collector:profiler.html.twig" for data collector "doctrine_profiler" does not exist.

The issue was fixed in the master branch, but maybe the authors could release a new tagged version of the bundle?

Please! Use tag versions!

Fixed in https://github.com/pixers/PixersDoctrineProfilerBundle/releases/tag/v1.0.6
Thx!


fix request user id retrieval

This PR fixes errors on updating the admin users role via CMS users form.

Closing this issue as it appears to be fixed in master.


outdated

This page hasn't been updated since late 2017 and there are versions as recently as September 2019.
https://cloudblogs.microsoft.com/dynamics365/it/2019/09/18/lifecycle-services-september-2019-release-2-release-notes/

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

ID: 8d8d91ac-1947-9637-3b39-53d832483355
Version Independent ID: 69495807-2269-65d3-0825-2f4174d6096c
Content: What's new in Lifecycle Services (LCS) - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/fin-ops-core/dev-itpro/lifecycle-services/whats-new-lcs.md
Service: dynamics-ax-platform
Product: ****
Technology: ****
GitHub Login: @kfend
Microsoft Alias: kfend

@kfend - Can you take a look? Thanks - Robin

Created bug 398725 to track this issue.

@zmottie - thank you for bringing this to our attention. I have updated the topic with a link to the release plans which is where we are now posting this type of information.