[BUG] On the Drive Failure Recovery page, step 4 is mislabeled step 1

Describe the bug
On the Drive Failure Recovery page, step 4 is mislabeled step 1.  Honestly, this is a small enough bug that it doesn't have mucb more of a desciption.
To Reproduce
Steps to reproduce the behavior:

Click on the Remount The Drive step
Notice that the step is labelled as 4, when it should be 1.
The issue is also in the right hand side TOC area (but is probably auto-gennerated from the main content anyway)

Expected behavior
Well, it'd be nice if it was step 4.
Screenshots

Desktop (please complete the following information):

OS: macOS
Browser: Chrome
Version: 116

Anyone performing this procedure with a Delorean and enough runway to hit 88MPH could do this tutorial in the stated order, but I see your point @wdinyes . We'll patch this up


STAR-1314 Homogenize to use public getters

There are public methods to get table and keyspace names from CFS and
they are already in use in some places. So use them consistently
instead of direct access to the attributes.
Introduce and use getter to retrieve KeyspaceMetrics from CFS, so it
can be mocked.

Coverage issues:

ActiveRepairService.getPendingStats contains the refactored line and is used in NodeTool.

My concern about this is that the cassandra code style is to not use getters where possible and to prefer public final fields. I understand the reasoning behind these changes but I am concerned that this is causing more divergence from the OS codebase than is strictly necessary.


Rename idea and_is -> which_is

It always bothered me that and_is isn't very explicit that it'll apply something on the parser itself and not the rest.
I've recently though about renaming it to which_is, which (not pun intended) I think is more explicit about the fact it's going to re-parse self
Also I think it reads a lot better, compare:
any().and_is(not(just('\n'))) (using not directly as suggested at #386)
compared to:
any().which_is(not(just('\n')))
What do you think?

I'm not opposed to this change, but I think we should remember that it's used in contexts other than just any().
Additionally, which heavily implies that the same input parses as the second pattern, but this is not necessarily true: the second parser is permitted to parse more than the first.

Closable?


Add support for Decapode processing

This PR implements initial support for ingesting Decapodes from JSON.

Closing this one since #260 subsumes this.


Fix Tag "Name" is always follow fqdn value

Fix an issue where fqdn might contains value that is not allowed as part of tag value: https://docs.aws.amazon.com/directoryservice/latest/devguide/API_Tag.html which the user need to override the tag value in order to be deployed successfully.
Related to: https://github.com/riboseinc/terraform-aws-s3-cloudfront-website/issues/39

Thank you @vKongv for this!
@phuonghuynh could you help review, merge and release a new version if it's okay? Thanks!

Thanks @vKongv


[BUG] Restore action fails with OpenEBS cstor CSI Driver

Describe the bug
When running the Backup and Restore for MySQL app using CSI Snapshot functions at path ./examples/stable/mysql-csi-snapshot, following error is observed;

Warning ActionSetFailed Action: restore 14s Kanister Controller Failed to execute phase: v1alpha1.Phase{Name:"restoreCSISnapshot", State:"pending", Output:map[string]interface {}(nil)}: PersistentVolumeClaim "demo-cstor-vol5-restored" is invalid: spec.resources[storage]: Invalid value: "0": must be greater than zero

This bug is in continuation of the discussion that happened here
To Reproduce
Steps to reproduce the behavior:

Install OpenEBS cStor CSI Driver on the kubernetes environment
Execute the steps mentioned in the example as is (Only update the snapshotClass and storageClass fields in the blueprint before running it)
After running backup action, inspect the event logs by describing the backup actionset. Check for the restoreSize in outputArtifacts.
After running restore action, inspect the event logs by describing the restore actionset. Here is where you see the above error.

Expected behavior

restoreSize field in create actionset should be a non-zero and non-negative value (equal to PVC resource storage request)
Restore actionset should pass without any failure

Environment
Kubernetes Version/Provider: ...
Storage Provider: OpenEBS cStor CSI Driver
Cluster Size (#nodes): ...
Data Size: ...

I tried installing openebs cStor driver on a kind cluster (Ubuntu machine), but, it looks like the pods are not transitioning to Running state since a long time. Followed the steps mentioned here: https://openebs.io/docs/user-guides/cstor
$ kubectl get pod -n openebs
NAME                                                                             READY   STATUS                    RESTARTS   AGE
openebs-cstor-admission-server-5d7c9d7669-rssgp    0/1        ContainerCreating   0                 86m
openebs-cstor-csi-controller-0                                      0/6        ContainerCreating   0                 86m
openebs-cstor-csi-node-bm5ml                                    0/2        ContainerCreating   0                 86m
openebs-cstor-cspc-operator-6bc968744c-bdldb        0/1        ContainerCreating   0                 86m
openebs-cstor-cvc-operator-78c6c6c886-5bhhm        0/1        ContainerCreating   0                 86m
openebs-localpv-provisioner-68cdbf6645-9nw5n        0/1        ContainerCreating   0                 86m
openebs-ndm-fpshw                                                     0/1        ContainerCreating   0                 86m
openebs-ndm-operator-68c5465857-2j44t                  0/1        ContainerCreating   0                 86m

@oliverblaha Could you mention the platform that you used for installing iSCSI client? https://openebs.io/docs/user-guides/prerequisites

This is a bug. We can't use args.RestoreSize in the restored PVC spec if it's 0.

We can reproduce this with a sample YAML like:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: test-0
spec:
  accessModes:
  - ReadWriteOnce
  storageClassName: gp2 // on eks
  resources:
    requests:
      storage: "0"

@shlokchaudhari9 I'm going to submit a PR to update the RestoreCSISnapshot function to return an error, if restoreSize is empty or equal to zero. Per my testing below, Kubernetes requires the restoreSize in the restored PVC to be non-empty or greater than zero. If the cstor CSI driver returns a zero value, then it's a bug on their end.
Steps To Reproduce
Follow the instructions here to set up the CSI snapshot controller and the CSI hostpath driver:
Deploy this Nginx statefulset workload:
cat<<EOF | kubectl apply -f -
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: nginx
  labels:
    app: nginx
spec:
  serviceName: nginx
  replicas: 3
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx
  volumeClaimTemplates:
  - metadata:
      name: www
    spec:
      accessModes: ["ReadWriteOnce"]
      storageClassName: csi-hostpath-sc
      resources:
        requests:
          storage: 1Gi
EOF

Confirm that the pods and their persistent volume claims are ready:
kubectl get po,pvc

Deploy this VolumeSnapshot resource to snapshot the PVC:
cat<<EOF | kubectl apply -f -
apiVersion: snapshot.storage.k8s.io/v1
kind: VolumeSnapshot
metadata:
  name: nginx-sts
spec:
  volumeSnapshotClassName: csi-hostpath-snapclass
  source:
    persistentVolumeClaimName: www-nginx-0

Confirm that the VolumeSnapshot and VolumeSnapshotContent resources are ready:
kubectl get vs,vsc

Attempts to restore these PVCs will fail because Kubernetes require the restoreSize to be non-empty and greater than zero:
cat EOF<< | kubectl apply -f -
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: restore-www-nginx-1
spec:
  storageClassName: csi-hostpath-sc
  dataSource:
    name: nginx-sts
    kind: VolumeSnapshot
    apiGroup: snapshot.storage.k8s.io
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: "0"
EOF
The PersistentVolumeClaim "restore-www-nginx-1" is invalid: spec.resources[storage]: Invalid value: "0": must be greater than zero

cat EOF<< | kubectl apply -f -
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: restore-www-nginx-1
spec:
  storageClassName: csi-hostpath-sc
  dataSource:
    name: nginx-sts
    kind: VolumeSnapshot
    apiGroup: snapshot.storage.k8s.io
  accessModes:
    - ReadWriteOnce
The PersistentVolumeClaim "restore-www-nginx-1" is invalid: spec.resources[storage]: Required value


Fixes around preserving user configuration

This PR:

Fixes #30
Retains the original user configuration and uses it to override generated configuration values with the same name.

Adds linting and type checking to the test task

I thought this was going to be trivial, but due to the task shorthand (i.e. task > dep1 dep2), the true configuration can't be finalized until after tasks are parsed. But because things like the config block in apex.yaml are also used by plugins, the configuration structure needs to be reset in multiple places at different times to keep things true.


nil: 2023-01-01 -> 2023-02-03

Diff: https://github.com/oxalica/nil/compare/2023-01-01...2023-02-03
Changelog: https://github.com/oxalica/nil/releases/tag/2023-02-03
Description of changes

Things done

Built on platform(s)

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

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

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.


Failed to cast media (YouTube Music)

What version of Music Assistant has the issue?
2023.6.0b1
The problem
When attempting to play a playlist or track through the YouTube Music provider the add-on seems to connect to the chromecast device (Google Nest Mini) but shortly after the player returns to Idle state. An error is thrown in the Add-on logs, and in the HA logs.
The Add-on logs are similar to #1377 but the symptom is different.
How to reproduce
Fresh install of addon
Set up YT Music connection
Attempt to cast playlist/track to any Google Nest Mini
Error occurs
Relevant log output
Addon Logs:
2023-07-20 10:01:53.947 INFO (ThreadPoolExecutor-0_1) [pychromecast.controllers] Receiver:Launching app CC1AD845
2023-07-20 10:01:59.318 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
resp = await request_handler(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_app.py", line 504, in _handle
resp = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/controllers/streams.py", line 467, in serve_queue_item_stream
streamdetails = await get_stream_details(self.mass, queue_item=queue_item)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/helpers/audio.py", line 268, in get_stream_details
streamdetails: StreamDetails = await music_prov.get_stream_details(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/providers/ytmusic/init.py", line 500, in get_stream_details
url = await self._parse_stream_url(stream_format=stream_format, item_id=item_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/providers/ytmusic/init.py", line 775, in _parse_stream_url
signature = await self._decipher_signature(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/providers/ytmusic/init.py", line 801, in _decipher_signature
self._cipher = await asyncio.to_thread(_decipher)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/asyncio/threads.py", line 25, in to_thread
return await loop.run_in_executor(None, func_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
result = self.fn(self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/providers/ytmusic/init.py", line 796, in _decipher
cipher = pytube.cipher.Cipher(js=ytm_js)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/pytube/cipher.py", line 37, in init
self.transform_map = get_transform_map(js, var)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/pytube/cipher.py", line 245, in get_transform_map
transform_object = get_transform_object(js, var)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/pytube/cipher.py", line 227, in get_transform_object
raise RegexMatchError(caller="get_transform_object", pattern=pattern)
pytube.exceptions.RegexMatchError: get_transform_object: could not find match for var for={(.?)};
2023-07-20 10:01:59.355 WARNING (Thread-10) [music_assistant.providers.chromecast] Load media failed: 1 - error code: 104

HA Logs:
2023-07-20 09:44:41.901 ERROR (Thread-9) [homeassistant.components.cast.media_player] Failed to cast media http://<IP_ADDRESS>:8096/a22e76ef-0e94-b04a-2ab5-c8e03593e549/single/14e3511e402e4628a55c00defd1f12f0.flac. Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address
2023-07-20 09:47:00.719 ERROR (Thread-9) [homeassistant.components.cast.media_player] Failed to cast media http://<IP_ADDRESS>:8096/a22e76ef-0e94-b04a-2ab5-c8e03593e549/single/14e3511e402e4628a55c00defd1f12f0.flac. Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address
2023-07-20 09:56:23.731 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Music Assistant' for mass integration not ready yet: Failed to connect to music assistant server; Retrying in background
2023-07-20 10:01:59.370 ERROR (Thread-9) [homeassistant.components.cast.media_player] Failed to cast media http://<IP_ADDRESS>:8096/a22e76ef-0e94-b04a-2ab5-c8e03593e549/single/14e3511e402e4628a55c00defd1f12f0.flac. Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address
Additional information
Attempting to access the URL in the HA logs throws an internal server error, unsure if this is expected behaviour after a the addon has attempted to provision a track for streaming and failed*
What version of Home Assistant Core are your running
2023.7.2
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Linux

Do other media providers work?

I noticed https://github.com/KoljaWindeler/ytube_music_player/issues/253 looks to be similar. Not a music assistant user, but thought I'd point it out since the underlying issue seems to be in pytube.

Do other media providers work? It looks like you have a network problem but if something works then that can be discounted.

I agree that's what it looks like, but this function was working a few days ago and no (intentional*) network related changes have been made that would cause this issue. The local filesystem provider works, so I'm inclined to think the endpoint returning a 500 is causing the network exception.

I noticed KoljaWindeler/ytube_music_player#253 looks to be similar. Not a music assistant user, but thought I'd point it out since the underlying issue seems to be in pytube.

I noted this too, with the lowest level exception being thrown by that regex module in pytube.

Ok sounds good. The YT provider works at the whim of YT who can change their system in ways which can break MA. Will just have to wait for the devs to have a look at this.

The YT dev is onto this and a fix should be available in the next beta. Google changed something…..

Please confirm this is fixed in beta 59

Please confirm this is fixed in beta 59

Confirmed able to play manually
Getting an error trying to run via automation.
websocket_api script: Error executing script. Unexpected error for call_service at pos 1: Invalid uri: database://playlist/7
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 468, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 703, in _async_call_service_step
    response_data = await self._async_run_long_action(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 665, in _async_run_long_action
    return long_task.result()
           ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 1965, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2005, in _execute_service
    return await cast(
           ^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 235, in handle_service
    return await service.entity_service_call(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 848, in entity_service_call
    response_data = task.result()  # pop exception if have
                    ^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1192, in async_request_call
    return await coro
           ^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 892, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/config/custom_components/mass/media_player.py", line 358, in async_play_media
    await self.mass.players.play_media(queue.queue_id, media_id, queue_opt, radio_mode)
  File "/usr/local/lib/python3.11/site-packages/music_assistant/client/players.py", line 282, in play_media
    await self.client.send_command(
  File "/usr/local/lib/python3.11/site-packages/music_assistant/client/client.py", line 168, in send_command
    return await future
           ^^^^^^^^^^^^
music_assistant.common.models.errors.MediaNotFoundError: Invalid uri: database://playlist/7

Unsure if it's related, have tried reading the media action a few times without success
Happy to raise a new issue if needed

Are you using beta 3 of the integration? Look for updates in HACS

Are you using beta 3 of the integration? Look for updates in HACS

Can confirm this error was occurring on 2023.6.0b3
Is there another component I should look for an update in?

Your playlist uri looks wrong. Just use the name of the playlist.

Your playlist uri looks wrong. Just use the name of the playlist.
I was using the automation GUI to avoid any unintended typos or incorrect linking.

I've just tested the same process again and it seems to be working now regardless so I think we're good to close.
Thanks again for all your help and diligent response to my issue - your work is very much appreciated :)


Unable to change Tabs border bottom color

react-native, react and native-base version
"native-base": "^2.1.2",
"react": "16.0.0-alpha.6",
"react-native": "0.43.3",
Expected behaviour
Able to change the bottom border color.
Actual behaviour
The bottom border color always appear in white color.
Steps to reproduce (code snippet or screenshot)
const tabProps = {
  underlineStyle: {borderColor: '#f65857'}
};

return (
  <Tabs>
    <Tab heading="Tab 1" {...tabProps}>
      <Tab1 />
    </Tab>
    <Tab heading="Tab 2" {...tabProps}>
      <Tab2 />
    </Tab>
    <Tab heading="Tab 3" {...tabProps}>
      <Tab3 />
    </Tab>
  </Tabs>
);

Screenshot of emulator/device

Is the bug present in both ios and android or in any one of them?
Only tested in Android.
Any other additional info which would help us debug the issue quicker.
None.

@feelinc it should be tabBarUnderlineStyle: { backgroundColor: '#f65857' }

@shivrajkumar still not working. re-compiled and restart the npm, but still not working.

@feelinc tabBarUnderlineStyle needs to be applied to  not

applied to not?

Ah! my bad.
Applied to <Tabs> not to <Tab>

Thanks a lot, it's working :)

@prasanthlrb Hi, you have to paste it to braces { } and use = after tabBarUnderlineStyle
example:
 <Tabs tabBarUnderlineStyle={{ backgroundColor: '#f65857' }}>

hi, can anyone tell how to change border color for other tabs (tabs other than current selected one)?
tabBarUnderlineStyle works for the active tab but for the rest of tabs, how to change their body color?

Check NativeBase Docs https://docs.nativebase.io/


Example for using a lambda inside ShapeList.filter_by

Question that came up in the Discord server was how to filter faces by being parallel to a given axis, as there is no built-in filter for it:
part.faces().filter_by(lambda f: abs(f.normal_at(None).dot(axis)) < 1e-6)

Jern noted that there are no examples showing this feature (lambda as filter), so we should probably add one / a few.

Thank you! Would be good to add this to page https://build123d.readthedocs.io/en/latest/key_concepts.html#custom-sorting-and-filtering

shape = Box(1, 1, 1)
f_parallel = shape.faces().filter_by(lambda f: abs(f.normal_at().dot(Axis.X.direction)) < 1e-6)
f_perpendicular = shape.faces().filter_by(Axis.X)

Might want to clarify that the dot method expects a Vector and not an Axis.


Generate SBOM for go distribution

To implement Paketo RFC0038, this buildpack will need to move from storing SBOM information in layer metadata to storing it in files that the CNB lifecycle can manipulate during the build. The RFC outlines what these files are and what they should contain.

@paketo-buildpacks/go-maintainers can you assign this to me please?


Regarding auto-run feature

#466 added auto-run for Playground only. Should we add this feature for all missions in the assessment workspace as well?
Also, student's autorun setting is preserved after closing the browser. Should it be defaulted to off whenever a workspace is freshly rendered?
https://github.com/source-academy/cadet-frontend/pull/466#issuecomment-468760971

I think the auto-run feature should be available for missions, and that we should preserve the autorun setting after closing the browser. These two decisions will maximize the exposure we have to the feature so that we can decide which way to go before the semester.

Answered in https://github.com/source-academy/cadet-frontend/issues/468


Add BitcoinBlue

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

[x] Filename in the lowercase format
[x] Image format: png
[x] Image size: 256 by 256 px

Please follow requirements

Please follow requirements

What are the requirements?
Tokens are active and functional.

Please follow requirements

What are the requirements?
Tokens are active and functional.

https://developer.trustwallet.com/add_new_token_image#add-custom-image

Please follow requirements

What are the requirements?
Tokens are active and functional.

https://developer.trustwallet.com/add_new_token_image#add-custom-image

I followed the procedure.
I'll try again.
Thank you.

Please follow requirements

What are the requirements?
Tokens are active and functional.

https://developer.trustwallet.com/add_new_token_image#add-custom-image

I followed the procedure.
I'll try again.
Thank you.

error again.

Please follow requirements

What are the requirements?
Tokens are active and functional.

https://developer.trustwallet.com/add_new_token_image#add-custom-image

"0x279a3BCcc607412fD11C6E33d0A3EaF1c16319eE image must be in lowercase"
I send the image in lowercase, and why does it appear that it is in capital letters?

Please follow requirements

What are the requirements?
Tokens are active and functional.

https://developer.trustwallet.com/add_new_token_image#add-custom-image

"0x279a3BCcc607412fD11C6E33d0A3EaF1c16319eE image must be in lowercase"
I send the image in lowercase, and why does it appear that it is in capital letters?

You did not remove previously uploaded in uppercase.

Please follow requirements

What are the requirements?
Tokens are active and functional.

https://developer.trustwallet.com/add_new_token_image#add-custom-image

"0x279a3BCcc607412fD11C6E33d0A3EaF1c16319eE image must be in lowercase"
I send the image in lowercase, and why does it appear that it is in capital letters?

You did not remove previously uploaded in uppercase.

So I need to delete the files I sent so I can send a new one?

Please follow requirements

What are the requirements?
Tokens are active and functional.

https://developer.trustwallet.com/add_new_token_image#add-custom-image

"0x279a3BCcc607412fD11C6E33d0A3EaF1c16319eE image must be in lowercase"
I send the image in lowercase, and why does it appear that it is in capital letters?

You did not remove previously uploaded in uppercase.

So I need to delete the files I sent so I can send a new one?

You need remove uppercase instances

Please follow requirements

What are the requirements?
Tokens are active and functional.

https://developer.trustwallet.com/add_new_token_image#add-custom-image

"0x279a3BCcc607412fD11C6E33d0A3EaF1c16319eE image must be in lowercase"
I send the image in lowercase, and why does it appear that it is in capital letters?

You did not remove previously uploaded in uppercase.

So I need to delete the files I sent so I can send a new one?

You need remove uppercase instances

How do I do this?
Delete I can not anymore, the previous files?

You need remove uppercase instances

"You need remove uppercase instances"
How do I do this?


Magenta background

Hey! Trying out glow, but for some reason the background is magenta. It's persisent across both the built in light and dark theme and other colour schemes for my terminal. Any ideas why? Here's a screenshot. Using neovim on arch. Terminal is alacritty.

do you have the same output using it directly in the terminal?

No, there it's fine.

I had the same issue here. One thing I noticed is that the same background color is on the menu that appears when I type " : " (bottom-left of the printscreen) (I also want to change that but don't know how)

hey guys, can you share some configs please? i am wondering if this is a missing termguicolors option issue

We were closing this since we still got no response so far. If the issue still persists, please open a new one


Likelihoods not matching when using Length comps vs. generalized size comps

I tried converting a model with length comps to use generalized size comps instead. In theory, these likelihoods should match, but I couldn't get them to, even though the parameter estimates and derived values are similar. Attached are the model input files and their summary files.
gensize_length_issue.zip

@Rick-Methot-NOAA , I see this is marked as resolved (which is great!) - could you add a little context here about what was done?

???  Did my write-up end up in only an email and not github?  I will check.
Issue is just that the length comps were using tail compression and tail compression is not an option for generalized size comp.  Turh=ning off tail compression for length comps results in a match.


Rewrite README

Fixes https://github.com/0xW1sKy/Stitch-For-Roku/issues/27.
I'm sure there are other changes that could be made, but this should be fine as a preliminary rewrite.
Obviously, feel free to make any changes you would like before merging this.
(I tried to use my best "professional technical writer" voice here lol... though, as I have mentioned, maintaining a certain presentation and tone, at least up front, can make a project more trustworthy for end users and potential collaborators.)

As an aside: I tend to prefer using Markdown versions of license text, and you can find a Markdown version of the Unlicense here. (Using a Markdown version of the Unlicense would involve renaming ./LICENSE to ./LICENSE.md, so be sure to change all the links in the README accordingly.)


Update cargo deps

Opt in to nightly features for a few, and update others to get bitrig support

@bors: r+ 54d1ac3

:hourglass: Testing commit 54d1ac3 with merge 3721b63...

r? @huonw
(rust_highfive has picked a reviewer for you, use r? to override)

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-32, cargo-win-64


added pathlib usage to spiceypy to help out user

Coverage decreased (-0.03%) to 99.762% when pulling 5be7ec1f428e25f1f76c534ce199ff717896f42a on add_pathlib into fc20a9b9de68b58eed5b332f0c051fb343a6e335 on master.

Coverage decreased (-0.03%) to 99.762% when pulling 42ad497a7928171455e9f5ceb82240e89d10df86 on add_pathlib into fc20a9b9de68b58eed5b332f0c051fb343a6e335 on master.

Coverage decreased (-0.03%) to 99.762% when pulling 42ad497a7928171455e9f5ceb82240e89d10df86 on add_pathlib into fc20a9b9de68b58eed5b332f0c051fb343a6e335 on master.

closing for now due to some ambiguity about how I feel exceptions from spice are handled at the moment.


Quick cleanup

@dakq would it be very inconvenient to you to split this PR into several smaller ones? I would suggest something like this:

a PR where you add linters (and use them) and where you fix logging (btw it's so cool you noticed that string concatenation in logger should be done in a particular way)

a separate PR where you add you fixes to the code (everything which is not done by linters)

I know it sound like an extra work, but it would be much easier to review smaller PRs


Adds support for Nexo

Description
Adds support for Nexo, a new custom items plugin created by the old maintainer of Oraxen.

What has changed?

Adds a J21 addon module
Adds the Nexo addon
Reworks the EMFPlugin interface into an abstract class to make things look cleaner
Fixes the relocation of BoostedYAML

Related Issues
None

Checklist

[ ] I have added tests that prove my fix is effective or that my feature works.
[x] I have updated the documentation as needed.
[ ] I have added any labels that fit this PR.

I cannot test this myself as i do not own Nexo. I'd like if somebody who does can test it before this is merged.

I also can't add labels, so i cannot check that box either.

I also can't add labels, so i cannot check that box either.

Ah yes, I'll add an action and an updated PR template for that. Sorry about that.

Converted this to a draft until it can be tested. I have to wait for Nexo's source code to be released.


Input V3_0_0.wav not recognized

Now training /Users/mixondaw/Desktop/output.wav
Strong hash: 36cd1af62985c2fac3e654333e36431e
Provided input file /Users/mixondaw/Downloads/v3_0_0.wav does not strong-match any known standard input files.
Falling back to weak-matching...
Weak hashes:
Start (v1) : 9f36f71c6a76d2c36144e8cd8a34f5ef
End (v1)   :<PHONE_NUMBER>a3f9d8e19a53554eb1fd52
Start (v2) : 8f7b431a879e229d733d220442a8df16
End (v2)   : 364b536bcd4f74d8e13c42d20c095861
Exception in Tkinter callback
Traceback (most recent call last):
File "/opt/anaconda3/lib/python3.12/tkinter/init.py", line 1968, in call
return self.func(*args)
^^^^^^^^^^^^^^^^
File "/opt/anaconda3/lib/python3.12/site-packages/nam/train/gui.py", line 351, in _train
trained_model = core.train(
^^^^^^^^^^^
File "/opt/anaconda3/lib/python3.12/site-packages/nam/train/core.py", line 833, in train
input_version, strong_match = _detect_input_version(input_path)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/anaconda3/lib/python3.12/site-packages/nam/train/core.py", line 153, in _detect_input_version
raise ValueError(
ValueError: Input file at /Users/mixondaw/Downloads/v3_0_0.wav cannot be recognized as any known version!

Strange: the hash there matches the strong hash for v3_0_0.wav, so it should be recognized.
Can you run the tests?

These tests in specific:
https://github.com/sdatkinson/neural-amp-modeler/blob/6a610ec9cb89f47d57b2d1d30779c21a642e649b/tests/test_nam/test_train/test_core.py#L46
If they don't pass, then something is odd with your setup--they pass on my computer. If they do pass, then that would be very odd.

Aha, I see the problem: your trainer is out of date: where it's computing weak hashes...

...I see that it's only computing for v1 and v2, but not v3. That's probably because you're out of date.
Update with
pip install --upgrade neural-amp-modeler

and you should be set!


v0.8.4 doesn't work

the plugin crashes here when starting. I'm using node v9.6.1, going back to v0.8.3 worked without problems.
Here is the log:
Mar 10 13:57:17 raspberrypi3 homebridge[19217]: [2018-3-10 13:57:17] [Hue] TypeError: Cannot read property 'sType' of undefined Mar 10 13:57:17 raspberrypi3 homebridge[19217]: at parseServiceJSON (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/AccessoryLoader.js:103:26) Mar 10 13:57:17 raspberrypi3 homebridge[19217]: at /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/AccessoryLoader.js:69:19 Mar 10 13:57:17 raspberrypi3 homebridge[19217]: at Array.forEach (<anonymous>) Mar 10 13:57:17 raspberrypi3 homebridge[19217]: at Object.parseAccessoryJSON (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/AccessoryLoader.js:68:17) Mar 10 13:57:17 raspberrypi3 homebridge[19217]: at Server._createAccessory (/usr/lib/node_modules/homebridge/lib/server.js:395:28) Mar 10 13:57:17 raspberrypi3 homebridge[19217]: at Server.<anonymous> (/usr/lib/node_modules/homebridge/lib/server.js:374:32) Mar 10 13:57:17 raspberrypi3 homebridge[19217]: at /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:16:19 Mar 10 13:57:17 raspberrypi3 homebridge[19217]: at request.then.catch.then.then.then (/usr/lib/node_modules/homebridge-hue/lib/HuePlatform.js:301:5) Mar 10 13:57:17 raspberrypi3 homebridge[19217]: at Function.then (/usr/lib/node_modules/homebridge-hue/node_modules/deferred/_ext.js:67:13) Mar 10 13:57:17 raspberrypi3 homebridge[19217]: at Deferred._settle (/usr/lib/node_modules/homebridge-hue/node_modules/deferred/deferred.js:97:26) Mar 10 13:57:17 raspberrypi3 homebridge[19217]: at Deferred.resolve (/usr/lib/node_modules/homebridge-hue/node_modules/deferred/deferred.js:142:15) Mar 10 13:57:17 raspberrypi3 homebridge[19217]: at fs.writeFile (/usr/lib/node_modules/homebridge-hue/lib/HuePlatform.js:372:11) Mar 10 13:57:17 raspberrypi3 homebridge[19217]: at /usr/lib/node_modules/homebridge-config-ui-x/node_modules/graceful-fs/graceful-fs.js:43:10 Mar 10 13:57:17 raspberrypi3 homebridge[19217]: at FSReqWrap.oncomplete (fs.js:153:20)

I don't know what's happening here.  It's actually homebridge choking on something it gets from homebridge-hue.  What version of homebridge are you running?  Does the error also occur with node v8.10.0?  Does the error also occur when you don't have homebridge-config-ui installed?
Could you please attach the full debug log file (see https://github.com/ebaauw/homebridge-hue#debug-log-file) and the debug dump file (see https://github.com/ebaauw/homebridge-hue#debug-dump-file).

Fixed 311 in v0.8.6.  Please re-open and attach files if there's still an issue with that version.

Thank you, v0.8.6 works here!


Fix iter long fix leak

Hi, this is a wild attempt to fix issue in #187. I'm on Mac so I couldn't check with Valgrind but I'll try to do that as soon as I can.
Hope that at least tests pass!

closing, send something else later


publically expose KnownEntid

I need this to use the EntityBuilder from outside of Mentat.

TermBuilder::add takes KnownEntid as the e arg and on update i I already have that arg as an Entid rather than fetching it as a temp_id so I need to convert it to a KnownEntid first.


⚠ ETF has degraded performance

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

HTTP code: 200
Response time: 7600 ms

Resolved: 마켓맵 performance has improved in f715420.


Alter table → add primary key/index

JSqlParser can not parse statements like this here:
ALTER TABLE animals
  ADD PRIMARY KEY (id);

ALTER TABLE `schema_migrations`
  ADD UNIQUE KEY `unique_schema_migrations` (`version`);

Sorry for creating a lot of issues

No problem. This is the way to do it, to create issues.

Are you positive that alter table ... add unique key ... does work? All documentation stats
alter table ... add unique ...   (without the key keyword).

Yes, ADD UNIQUE KEY works. And the documentation states this too:
  | ADD [CONSTRAINT [symbol]]
        UNIQUE [INDEX|KEY] [index_name]
        [index_type] (index_col_name,...) [index_option] ...

Also without the KEY it does not parse.
ALTER TABLE `schema_migrations`
  ADD UNIQUE `unique_schema_migrations` (`version`);

Yields to
ParseException Encountered " <S_IDENTIFIER> "UNIQUE "" at line 3, column 7.
Was expecting:
    "COLUMN" ...

If I see it correctly the Alter parser supports only modifying columns.


Things to fix in beta

[x] Evan whatshisname (Toledo) should be on site contacts?
[x] OWC past data (1980 etc)

Evan whatshisname (Toledo)

@stephpenn1 do you know this person, and whether we should add him?

Yes, Evan Grammenidis<EMAIL_ADDRESS>The site contact sheet should be up to date and he us marked as "Evan G."

We're good here I think


Mouseover on FocusFrame stop working.

Hello Ike!
FocusFrame mouseover doesnt work with the last FocusFrame release: https://github.com/wardz/FocusFrame/releases/tag/v1.2.1
Could you PLEASE fix it?
Thank you in advance!

Hey!
I'm afraid FocusFrame works fine for me. Have you tried without any other Addons enabled to make sure there's nothing else that might be causing this problem? Also, did you get any error messages after logging in? Or does it just not work?

Damnd voodoo magic... reinstalled both addons and its working now. Sooooory.
Thanks!

No worries I'm glad it's working!


Set TeX typesetting parameters to make sure all paragraphs are well typesetted

Before this PR, sometimes paragraphs may be typesetted as follows which is not acceptable:

This PR addresses this issue and fixes it.

Note: due to the change of the parameters to the underlying TeX typesetting engine, this commits should be well tested before merging.

说好的多测试一下呢，主要我担心调整了底层的参数会产生什么奇怪的副作用

（我其实之前自己给自己论文加上了……主要是为了让参考文献那里两端对齐，应该没啥大问题）

OK，那就没问题了


[VI] Remove announcement and deprecationwarning shortcodes

Umbrella issue: #21616

/lgtm
/approve
Thank @celestehorgan for raising the issue #21616
Thank @huynguyennovem for you PR


Use environment variable for custom rayImage

Use environment variable for custom rayImage
Merge criteria:

[X] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[X] The developer has manually tested the changes and verified that the changes work

@ChughShilpa It seems to me like you are trying to do duplicate work. See #233

This is not duplicate of 233

As discussed, it is better to close this PR and you can bring the changes in your PR directly
@jiripetrlik


DSA 2.1.15 String Matching Algorithms

Description 📜
Added a file with proper documentation for String Matching Algorithms.
Fixes #4309

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] DSA

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

The material looks about right. I am merging this to DSA branch now. Thanks for being so patient with us, Gotta appreciate that.


unexpected '?'

I downloaded latest release and uploaded to my ftp when I tried to install got such error:
Parse error: syntax error, unexpected '?' in /home/users/l/lextorg/domains/sneakbug8.com/cockpit/bootstrap.php on line 196

Okey. Problem was solved by updating php from 5.6 to 7.4


DOCS-4 Add release notes for Ironic.

Issue: DOCS-4

"Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?"
recheck_cit_xenial_swift_deploy
recheck_cit_trusty_swift_deploy

recheck_cit_xenial_swift_deploy
recheck_cit_trusty_swift_deploy

recheck_cit_xenial_swift_deploy
recheck_cit_trusty_swift_deploy

recheck_cit_xenial_swift_deploy
recheck_cit_trusty_swift_deploy


Packaging: place staslib in arch-independent path

https://github.com/linux-nvme/nvme-stas/blob/3b8e8d948c935fb7d2aeb5d48d83924a0e284649/staslib/meson.build#L31-L35
One more issue found during packaging - as this is a pure Python project with no architecture-specific code, we aim for a single package for all architectures (i.e. noarch in rpm world). However, the meson project places staslib in architecture-specific directory (e.g. /usr/lib64) and also ignores any supplied libdir meson argument.
Setting pure: true in the code snippet above seems to do the trick, although I'm not sure what else would it break.
Also, per https://mesonbuild.com/Python-3-module.html the python3 meson module is deprecated.

Thanks for pointing this out. I will try with "pure: true" to make sure it doesn't break anything.

@tbzatek - I tried the change on Ubuntu, Fedora, and SLES. On Ubuntu it makes no difference, but on Fedora/SLES it moves the packages from /usr/lib64/ to /usr/lib/. Everything still works normally, so I should be able to go ahead with the change.
I noticed that the same change will be needed for libnvme as well.
This change will need to be released with a different version number, probably v1.0.1.

I noticed that the same change will be needed for libnvme as well.

It's a different scenario - libnvme is architecture-dependent, while nvme-stas is pure Python code and any arch-dependent code lies in one layer below. I suppose the meson module might have some detection logic though.

It's a different scenario - libnvme is architecture-dependent, while nvme-stas is pure Python code and any arch-dependent code lies in one layer below. I suppose the meson module might have some detection logic though.

Ok got it. Because the libnvme Python bindings are SWIG-generated C++ code, they are in fact architecture-dependent. Makes sense.

Also, per https://mesonbuild.com/Python-3-module.html the python3 meson module is deprecated.

BTW, I am not using the deprecated Python module. python3 is just the name of a variable, which is defined in the top-level meson.build as follows:
python3 = import('python').find_installation('python3')

Issue resolved by this pull request: https://github.com/linux-nvme/nvme-stas/pull/104
Once all the tests have completed, I will release v1.0.1.

@tbzatek - v1.0.1 has been released


NUXT 3 support?

Can I use this component in NUXT 3? If yes, how? If no, when is NUXT 3 support planned?

yes it works in nuxt 3.
https://github.com/ismail9k/vue3-carousel#basic-using

Here is a working example with<EMAIL_ADDRESS>

Hello @ismail9k i have created a nuxt module for your library :)
https://github.com/gaetansenn/vue3-carousel-nuxt


Backport 17.06

Reverted patch that was introducing the channel, there was a deadlock
Simply skip the logic of the updateSandbox if we are in swarm mode

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "backport-17.06" git@github.com:fcrisciani/libnetwork.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842353901168
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.


[ic-accordion] accordion sizes don't match Figma designs

Summary of the bug
In the Figma designs, the different size variations have an impact on the width of the accordion as well. But in the implementation, all accordions are full width and only the height changes.
📸 Screenshots or code
Figma:

Implementation:

🧐 Expected behaviour
The accordion sizes should match figma.
📝 Acceptance Criteria
If relevant, describe in full detail the different interactions and edge cases that the component or patterns needs to fulfil.
Given a accordion exists
When  it is small
Then it should have a 300px width
Given a accordion exists
When  it is default
Then it should have a 600px width
Given a accordion exists
When  it is large
Then it should have a 800px width
Additional info
Current accordions could be a full width size variant.

Design brought this up to ask why it was moved to design, which I was unsure why. Therefore, I have moved it back to refinement so we can discuss at refinement on if it needs design

Design to update all the Figma widths to the same size, as we will be following the dev implementation

Changes made in Figma and now merged.


No display of the table in mobile mode.

The table is not displayed in the mobile view and can only be recognized as a narrow bar. If the table is opened in the editor, the display is also defective here.
Tested under Chrome 121 for macOS

And here is another video of the error.
https://github.com/bogdancondorachi/kirby-table-field/assets/140849227/5c9a5825-42a6-4a1d-9430-73a2f52c910c

@gbdesign2023 Thanks for reporting this. I'll investigate this and come up with a fix in the coming days.
Regarding the align request I can easily make it possible inside the panel but it won't reflect in the rendered table on page.

Since it is generally difficult to edit tables on mobile devices, I don't see any urgency in rushing to fix the error with the breakpoint.
Yes, I mean only the display in the panel. In the backend, I add the alignment of the columns in the template.

This has been fixed in the latest patch release. It includes an align prop for setting the text alignment :)


Parser ignores "."

PathCodec's parse methods ignore directories called ., which is really a posix-specific feature and doesn't make sense for other codecs.
Much worse, parsing a file called . will actually produce a path with a non-sensical type:
@ posixCodec.parseAbsFile("/foo/bar/.").map(posixCodec.unsafePrintPath)
res1: Option[String] = Some(/foo/bar/)

After further consideration, I don't think the PathCodec abstraction is even usable for URI paths (the intended use) because it's not clear what should happen if you try to print a path that contains ParentIn or Current if the codec has no representation analogous to .. and .. Unless we think it makes sense to make printPath partial, we'll probably have to roll our own parsing for URIs in quasar.

@jdesah: just noticed this sitting in my review queue and figured I'd ping you and see if you're still planning to take it over.

Fixed by #27


[BUG] Can't view video datasets with metadata in App

When trying to load a video dataset with fiftyone.core.labels.VideoMetadata values in its metadata field, I get the following error:
Traceback (most recent call last):
  File "main.py", line 108, in wrapper
    return func(self, *args, **kwargs)
  File "main.py", line 316, in on_get_frame_labels
    field_labels = _make_image_labels(k, v, frame_number)
  File "main.py", line 156, in _make_image_labels
    fol.ImageLabel.from_dict(label).to_image_labels(name=name),
AttributeError: 'VideoMetadata' object has no attribute 'to_image_labels'

After setting the metadata to None, I can then visualize the dataset.

Update: this happens when working with the attached dataset from a remote session, but not from a local session...
pip-175k-sample.zip
Here's what I did:
import fiftyone as fo

dataset = fo.Dataset.from_dir(
    "/path/to/pip-175k-sample",
    fo.types.FiftyOneDataset
)

dataset.compute_metadata()

session = fo.launch_app(dataset)

Update: this happens when working with the attached dataset from a remote session, but not from a local session...

This is a likely duplicate of #208, in that case.

Update to the update: this just happened in a local session too


Option to support clippy's semicolon_if_nothing_returned

Hi,
Is there an option to properly format code to adhere to https://rust-lang.github.io/rust-clippy/beta/index.html#semicolon_if_nothing_returned?
Thanks !

No, not unless I'm forgetting something. However, it's important to keep in mind that rustfmt is not designed/intended to satiate clippy's rules nor vice versa, so it's not really a surprise.
rustfmt strictly operates at an earlier phase (AST pre-expansion, lowering, etc.) but we may have enough info available to support such an option.
If anyone is sufficiently interested then certainly feel free to submit a PR, but I don't see this being something that the rustfmt team will ever work on due to priority/bandwidth constraints.

Understood. I think this could be useful as it would adhere to the recommended style.
Could you share some pointers? I'd be happy to take a look if no-one more qualify can.

I suspect the problem that you're going to run into is that rustfmt isn't going to have the information needed to be able to safely make that determination due the level it operates at as I mentioned earlier.
Not sure off hand where to best point you, but perhaps inspecting where the trailing_semicolon option is utilized, as well as how/where is_last_expr() helper function to see if there's anything there that helps


fails w/o initial zeros

.5 * 2 comes out as 10
fix is
var fp_rx = regexp.MustCompile(([0-9]*\.?[0-9]+))
I believe.
(and add a test like):
{".5 * 2", big.NewRat(1, 1), true},           // no leading zero
tried to submit, but I clearly dont know how to use github yet...so submitting as issue.
-s

Thanks @stevesmoot  and sorry about the years-long delay. Anyway, I've merged in some code that fixes this.


Docker-compose fails

docker-compose fails at starting invenioils_flower_1
Error
invenioils_db_1 is up-to-date
invenioils_mq_1 is up-to-date
invenioils_cache_1 is up-to-date
invenioils_es_1 is up-to-date
invenioils_backend_1 is up-to-date
Starting invenioils_flower_1 ...
invenioils_worker_1 is up-to-date
invenioils_frontend_1 is up-to-date
Starting invenioils_flower_1 ... error

ERROR: for invenioils_flower_1  Cannot start service flower: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "--broker=amqp://guest:guest@mq:5672/": stat --broker=amqp://guest:guest@mq:5672/: no such file or directory: unknown

ERROR: for flower  Cannot start service flower: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "--broker=amqp://guest:guest@mq:5672/": stat --broker=amqp://guest:guest@mq:5672/: no such file or directory: unknown
ERROR: Encountered errors while bringing up the project.

Hello @Grustamli !
Thank you for your interest in invenio-app-ils :)
I have checked the issue on my side, and it seems to me that it is connected with your environment, not with the docker template. Please check the proposed solutions in: https://github.com/docker/cli/issues/297

@kprzerwa. Thank you.


@onclick No Longer Functions After Upgrade

If you believe you have an issue that affects the security of the platform please do NOT create an issue and instead email your issue details to<EMAIL_ADDRESS>Your report may be eligible for our bug bounty but ONLY if it is reported through email.
Describe the bug
A clear and concise description of what the bug is.
The method is never called when using the @onclick attribute.
To Reproduce
Steps to reproduce the behavior:

Using this version of ASP.NET Core : 3.0.100 Preview 8 (8/13/2019)
Run this code : Create Server-Side Blazor app via template
With these arguments: Click the Counter's page "button" to increment count
See error: nothing happens

Expected behavior
I expect my method to be called when a button with @onclick="methodName" is pressed.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Include the output of dotnet --info
I first realized this on my custom Blazor Page Component, then went back and tested this on the default template Counter page -- error persists.

Thank you for filing this issue. In order for us to investigate this issue, please provide a minimalistic repro project that illustrates the problem.

This ended up being a change I didn't realize I made while debugging.
app.UseEndpoints(endpoints =>
            {
                endpoints.MapBlazorHub<App>(selector: "app");
                endpoints.MapFallbackToPage("/_Host");
            });

The MapBlazorHub had a modification and this was a crucial piece.


Update: README

Description
Update the path for the .env.sample file in the README

The update that this PR intended to include was already done.


[No QA] Remove duplicate subscription in Report.js file

Details
Just some clean up. I'm not sure if this has any performance benefits, but it reduces the initial number of callbacks that Onyx has to do when it initializes. There's no point in having two separate Onyx.connect() calls hooked up to the same key.
Fixed Issues
None
Tests
QA Steps
No QA
Tested On

[x] Web
[ ] Mobile Web
[ ] Desktop
[ ] iOS
[ ] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @deetergp in version: 1.0.85-10 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Is activity logs part of Azure Monitor?

Hi,
In this article this is mentioned:
"To store this data for longer periods, collect it in Azure Monitor".
As I understand it activity logs and metrics are default stored in Azure Monitor. How it is stored is unknown but it is an internal thing.
If you want to keep activity logs or metrics longer than 90 days you can stream them to an Analytics workspace (aka. Azure Monitor Logs).
Is this correct or am I missing something? :-)
Regards Peter
storage account or an Event hub.
So to be

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

ID: 74856982-ee13-cbab-28c8-0f57d95e98cd
Version Independent ID: edfb1257-26ee-813c-88a6-f95b4198b6ca
Content: Overview of the Azure Activity Log
Content Source: articles/azure-monitor/platform/activity-logs-overview.md
Service: azure-monitor
Sub-service: logs
GitHub Login: @bwren
Microsoft Alias: bwren

@theheatDK Thanks for the comment. We are actively investigating on the issue and will get back to you shortly with an update.

@theheatDK Your understsanding is correct.  We show this in Data Sources where we show that the Activity Log is kept in its own store where you can look at them in the portal but not much else. To take advantage of Azure Monitor features like log queries, you need to collect them in Azure Monitor Logs.
This question of how to describe the scope of Azure Monitor is actually a question that we've been struggling with a bit since we consolidated the services a year ago.  At the very least, we should clear up confusion like this by specifying "Azure Monitor Logs" instead of just using the general "Azure Monitor".  I'll get this one updated.

#please-close


cargo test fails with same-named extern crate

cargo new --vcs none alloc
cd alloc
cat > src/lib.rs <<EOF
#![feature(alloc)]
#![feature(heap_api)]

extern crate alloc;

pub unsafe fn xyz() {
    alloc::heap::allocate(8, 8);
}
EOF
cargo build
cargo test

Output:
   Doc-tests alloc
alloc/src/lib.rs:7:5: 7:26 error: failed to resolve. Could not find `heap` in `alloc` [E0433]
alloc/src/lib.rs:7     alloc::heap::allocate

Note that the cargo build step succeeds.

Seems... odd? Maybe we're missing a flag to rustdoc? Not sure

From running cargo test --verbose, it seems that the extern passed to rustdoc is the cause of this problem.

Should this be moved to rust-lang/rust as a rustdoc issue?
example output:
cargo test --verbose
   Compiling alloc v0.1.0 (file:///Users/becker/trash/alloc)
     Running `rustc --crate-name alloc src/lib.rs --crate-type lib --emit=dep-info,link -g -C metadata=de5e28f1acf88955 -C extra-filename=-de5e28f1acf88955 --out-dir /Users/becker/trash/alloc/target/debug/deps -L dependency=/Users/becker/trash/alloc/target/debug/deps`
     Running `rustc --crate-name alloc src/lib.rs --emit=dep-info,link -g --test -C metadata=1483b69725b1e82b -C extra-filename=-1483b69725b1e82b --out-dir /Users/becker/trash/alloc/target/debug/deps -L dependency=/Users/becker/trash/alloc/target/debug/deps`
    Finished debug [unoptimized + debuginfo] target(s) in 0.28 secs
     Running `/Users/becker/trash/alloc/target/debug/deps/alloc-1483b69725b1e82b`

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured

   Doc-tests alloc
     Running `rustdoc --test /Users/becker/trash/alloc/src/lib.rs --crate-name alloc -L dependency=/Users/becker/trash/alloc/target/debug/deps --extern alloc=/Users/becker/trash/alloc/target/debug/deps/liballoc-de5e28f1acf88955.rlib`
error[E0433]: failed to resolve. Could not find `heap` in `alloc`

Looking back at this, I don't think there's anything we can do about it. You simultaneously want a --extern flag pointing at your local crate to find it but you also want to use sysroot crates, so this is a case where we just shadow the sysroot crate. As a result I don't think there's any way to solve this...

As a result I don't think there's any way to solve this...

Closing then!


DoOnEach operator

DoOnEach operator: allows  to establish a callback that the resulting Observable will call each time it emits an item
Please note this PR is based on https://github.com/ReactiveX/RxGo/pull/109.

Pull Request Test Coverage Report for Build 191

178 of 188 (94.68%)  changed or added relevant lines in 3 files are covered.
19 unchanged lines in 3 files lost coverage.
Overall coverage increased (+5.8%) to 89.802%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

observablecreate.go
125
135
92.59%

Files with Coverage Reduction
New Missed Lines
%

optional/optional.go
3
100.0%

options/options.go
7
100.0%

errors/errors.go
9
100.0%

Totals

Change from base Build 179:
5.8%

Covered Lines:
863

Relevant Lines:
961

💛  - Coveralls

Pull Request Test Coverage Report for Build 191

178 of 188 (94.68%)  changed or added relevant lines in 3 files are covered.
19 unchanged lines in 3 files lost coverage.
Overall coverage increased (+5.8%) to 89.802%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

observablecreate.go
125
135
92.59%

Files with Coverage Reduction
New Missed Lines
%

optional/optional.go
3
100.0%

options/options.go
7
100.0%

errors/errors.go
9
100.0%

Totals

Change from base Build 179:
5.8%

Covered Lines:
863

Relevant Lines:
961

💛  - Coveralls

@avelino I'm kind of lost with the test coverage results. The only difference with the current v2 branch is a single method (DoOnEach) which has a 100% test coverage and Coverrals says the overall project rate decreased from 5%...

@avelino I'm kind of lost with the test coverage results. The only difference with the current v2 branch is a single method (DoOnEach) which has a 100% test coverage and Coverrals says the overall project rate decreased from 5%...

I found it strange the result too, I will do merge (must be some inconsistency of them)


Requestify Witness Resolution

Witness matching is a source of a lot of ad-hoc cycles, and mixes the
logic that performs resolution, caching, validation, and cycle breaking into one
place.  To make matters worse, some checkers kick off other checks in
order to cache work for further declarations, and access an internal
cache on their subject conformance for many requirements at once, or
sometimes just one requirement.
None of this fits into the request evaluator's central view of
caching.  This is further evidenced by the fact that if you attempt to
move the caching step into the evaluator, it overcaches the same
witness and trips asserts.
As a start, define requests for the resolution steps, and flush some
hacks around forcing witness resolution. The caching logic is mostly
untouched (the requests don't actually cache anything), but some cycle
breaking is now handled in the evaluator itself.  Once witness matching
has been refactored to cache with the evaluator, all of these hacks can
go away.
My urge to destroy the LazyResolver outweighs the compromises here.

@swift-ci please test

@swift-ci please test source compatibility

@DougGregor I think the right way to do this is to make a checker that acts like a pure function from a top-level target requirement and a (partial) NormalConformance to a [Type]Witness.  If further requirements need to get validated, then we can spawn sub-checkers with those requirements as targets.  Each checker would be responsible for caching only its target requirement on the conformance.

Build failed
Swift Test Linux Platform
Git Sha - db6b24c91105eb1b7c6e28b12c44e2e541222a31

Build failed
Swift Test OS X Platform
Git Sha - db6b24c91105eb1b7c6e28b12c44e2e541222a31

@swift-ci please smoke test

@swift-ci please smoke test


Move context to options

Landed in https://github.com/metarhia/metavm/commit/f3123e7e0b3ced2f033c293541b0652460cd9b29


Use new version of rust-openssl

v0.9.0 should make it significantly easier to get rust-openssl to compile on Windows and macOS devices, a problem many Windows users using Hyper have had.

It will also allow people to actually compile rust-openssl (and thus hyper) if they have openssl 1.1 installed

Unfortunately porting to the new API either means not making use of all the new improvements (SslConnector / SslAcceptor), or breaking public API.

Updating it would be a breaking change anyways, since you can only have 1 version of openssl-sys, so this could conflict with out dependencies.

I'm curious, since I believe that the majority of people who need openssl are using the client. Is this correct?

Question is also which branch to work on, master and 0.9.x are somewhat different in that regard (and I have a simple port for master here that compiles but is otherwise untested)

Well, master is where asynchronous IO work is happening, and that will take advantage of tokio-tls, which wraps the new openssl and native-tls in Futures.
If people are in need of this for a Client, I have a higher level crate (https://github.com/seanmonstar/reqwest) that works with native-tls, and is just waiting on that crate to be published (which should be early this week).

I'm curious, since I believe that the majority of people who need openssl are using the client. Is this correct?

Yes, it's correct, but it's very desired change - without it it's impossible to use openssl 0.9.0 and it, therefore, makes impossible to use ssh2 0.3.14 and other things.

If people are in need of this for a Client, I have a higher level crate

For us it will mean rewrite all code, related to hyper::client, for contributors of this crate it would mean just fix few lines to achieve compatibility with openssl 0.9.0. At least I hope so :)
As I can see, master and tokio are far from stable, so it's not a replacement.

For us it will mean rewrite all code, related to hyper::client

I really hope not! I've made the reqwest::Client API very very similar to hyper::Client, so the only changes required should be a replacement of your extern and use lines. I wanted reqwest to be a drop-in replacement, as much as possible.

for contributors of this crate it would mean just fix few lines to achieve compatibility with openssl 0.9.0. At least I hope so :)

It's true that the amount of code required in hyper to make the change is small. However, with hyper being core to web development, I've found that when a new breaking change version is published, it takes a while for the community to catch up. And in the meantime, people have conflicts of 1 framework using hyper 0.9, and another using hyper 0.10. It seems like a shame to make that ripple through the community and then not too long from now make a newer version to introduce async IO.
My thought has been that people can use the reqwest crate, and then there isn't that ripple. Maybe I'm wrong. Maybe it is better to just release hyper 0.10 with openssl updated (or using native-tls even), and then let asynchronous hyper be 0.11.

I agree that this approach is more flexible. Thank you, will try reqwest.

Sorry, @seanmonstar , but reqwest is some experimental code with 0.0.0 version and it has hyper 0.9 in dependencies so there is no point to replace.

Sorry, the code for reqwest is not published on crates.io yet, because it
uses the native-tls crate, which is also not published. The author of that
said he'd be able to publish it this week, as he cleaned up the updates for
the new OpenSSL. Once it is, reqwest will be published after.
You can try the crate now by using a git dependency, and I'll update this
issue when it is published.
It's using hyper 0.9 is not an issue, it disables the ssl feature of hyper.
That removes the dependency on openssl 0.7 and openssl-verify. Reqwest then
uses the native-tls crate to implement a new https connector.
On Wed, Nov 9, 2016, 6:27 AM Evgeniy OZ<EMAIL_ADDRESS>wrote:

Sorry, @seanmonstar https://github.com/seanmonstar , but reqwest is
some experimental code with 0.0.0 version and it has hyper 0.9 in
dependencies so there is no point to replace.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hyperium/hyper/issues/949#issuecomment-259426645, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AADJF6Y9amS-3VmYuMpPe5IZhAa_I0CVks5q8dhAgaJpZM4Kqf0O
.

And, it's now published as 0.1.0! I'll have an article explaining it tomorrow, but if you wish to grab it now, it's there: https://crates.io/crates/reqwest

@seanmonstar
works fine, thank you very much! Just few lines were changed, now all tests are green.
To use openssl 0.9 I still need to vendor hyper, because hyper have dependency on older openssl and even if I write default-features=false, features=[], Cargo adds it to Cargo.lock anyway.
But at least it compiles :)

To use openssl 0.9 I still need to vendor hyper, because hyper have dependency on older openssl and even if I write default-features=false, features=[], Cargo adds it to Cargo.lock anyway.

That shouldn't be the case. Try a cargo clean. I know it doesn't, because otherwise reqwest could not work, since it depends on the newer openssl 0.9, after disabling hyper's.

That's exactly what happens and that's why I need to vendor hyper. "cargo
clean" was the most often used line these days, but now everything is fine.
Thank you for help.
On Fri, 11 Nov 2016 at 03:08, Sean McArthur<EMAIL_ADDRESS>wrote:

Closed #949 https://github.com/hyperium/hyper/issues/949.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hyperium/hyper/issues/949#event-855310431, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgIEE1uPo8flw6Usa0f8WoIrNkTKasSks5q87H5gaJpZM4Kqf0O
.

I'm using hyper through iron. The rust-openssl version 0.7.x fails to build on my Windows machine, even if I use it in a standalone project:
error: failed to run custom build command for `openssl-sys-extras v0.7.14`
process didn't exit successfully: `C:\...\iron-test\target\debug\build\openssl-sys-extras-4d40c2369b784529\build-script-build` (exit code: 101)

rust-openssl version 0.9.x works fine. What should I do?

@Philipp91 if you don't use tls connections in your app, you can try to declare dependency as
hyper = { version = "0.9", default-features=false, features=[] }

If it will not help, try to fork repo and in your version of Hyper remove dependency of openssl (as I did here: https://github.com/e-oz/hyper/blob/0.9.13/Cargo.toml - don't rely on my repository, it can be removed).
If you do use tls connections, you can use reqwest crate for them and again remove openssl dependency from Hyper (see above). But it will work only on mac and windows, not on linux.


Keep GitHub Actions workflows up to date with Dependabot

This configures Dependabot to automatically bump GitHub Actions workflows, just as we do with .NET packages.
This may well automatically sort out #556 - but I'm not certain!

[x] Did you write/update appropriate tests
[x] Release notes updated (if appropriate)
[ ] Appropriate logging output
[ ] Issue linked
[ ] Docs updated (or issue created)
[ ] New package licenses are added to ThirdPartyNotices.txt (if applicable)

Oooohh, never tried this feature before, Exciting!


feat: support writing kubeconfig to a stream

What
Add a new func for writting kubeconfig to a stream.
Why
In my use case, I want to return the kubeconfig content in an API. But I don't want to create a temporary file then delete it. Such new function could let the code be clean.
Implications

Tests passed locally - thank you for the contribution!


test(types): added types spec

Description

added type definition spec

Related Issue

None

Motivation and Context

we love typescript
I want to consider using it in a production :)

How Has This Been Tested?

Screenshots (if appropriate):

@9renpoto thank you very much for this big improvement!


br_table size is out of bounds

I have a yara rule file with 131,517 strings and when using the yr compile command, it is crashing with the following error:
RUST_BACKTRACE=full yr compile --output rule.yarc rule.yar

thread 'main' panicked at lib/src/compiler/mod.rs:695:10:
WASM module is not valid: WebAssembly translation error

Caused by:
    Invalid input WebAssembly code at offset 271360: br_table size is out of bounds

Stack backtrace:
   0: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from
   1: core::ops::function::FnOnce::call_once{{vtable.shim}}
   2: <alloc::vec::Vec<T,A> as alloc::vec::spec_extend::SpecExtend<T,I>>::spec_extend
   3: rayon::iter::plumbing::bridge_producer_consumer::helper
   4: rayon_core::join::join_context::{{closure}}
   5: rayon_core::registry::in_worker
   6: rayon::iter::plumbing::bridge_producer_consumer::helper
   7: rayon_core::join::join_context::{{closure}}
   8: rayon_core::registry::in_worker
   9: rayon::iter::plumbing::bridge_producer_consumer::helper
  10: rayon_core::join::join_context::{{closure}}
  11: rayon_core::registry::in_worker
  12: rayon::iter::plumbing::bridge_producer_consumer::helper
  13: rayon_core::join::join_context::{{closure}}
  14: rayon_core::registry::in_worker
  15: rayon::iter::plumbing::bridge_producer_consumer::helper
  16: rayon_core::join::join_context::{{closure}}
  17: <rayon_core::job::StackJob<L,F,R> as rayon_core::job::Job>::execute
  18: rayon_core::registry::WorkerThread::wait_until_cold
  19: rayon_core::registry::ThreadBuilder::run
  20: std::sys::backtrace::__rust_begin_short_backtrace
  21: core::ops::function::FnOnce::call_once{{vtable.shim}}
  22: std::sys::pal::unix::thread::Thread::new::thread_start
  23: start_thread
             at ./nptl/pthread_create.c:442:8
  24: __GI___clone3
             at ./misc/../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
stack backtrace:
   0:     0x564e7164fd95 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h1b9dad2a88e955ff
   1:     0x564e716792db - core::fmt::write::h4b5a1270214bc4a7
   2:     0x564e7164d40f - std::io::Write::write_fmt::hd04af345a50c312d
   3:     0x564e71651411 - std::panicking::default_hook::{{closure}}::h96ab15e9936be7ed
   4:     0x564e716510ec - std::panicking::default_hook::h3cacb9c27561ad33
   5:     0x564e70bb188e - yr::main::{{closure}}::heb4a2c6a70fffb9f
   6:     0x564e71651caf - std::panicking::rust_panic_with_hook::hfe205f6954b2c97b
   7:     0x564e716518d7 - std::panicking::begin_panic_handler::{{closure}}::h6cb44b3a50f28c44
   8:     0x564e71650259 - std::sys::backtrace::__rust_end_short_backtrace::hf1c1f2a92799bb0e
   9:     0x564e71651564 - rust_begin_unwind
  10:     0x564e70b23553 - core::panicking::panic_fmt::h3d8fc78294164da7
  11:     0x564e70b23a26 - core::result::unwrap_failed::hfa79a499befff387
  12:     0x564e70ec3ba4 - yara_x::compiler::Compiler::build::h87040e3e9d74f796
  13:     0x564e70bc137a - yr::commands::compile_rules::hb614a5faf462acc8
  14:     0x564e70badba4 - yr::commands::compile::exec_compile::hf8b13c7379073c56
  15:     0x564e70bb0d80 - yr::main::h6dd8825c4f911447
  16:     0x564e70bc63b3 - std::sys::backtrace::__rust_begin_short_backtrace::h68179dc5cb28cf2f
  17:     0x564e70bc630d - std::rt::lang_start::{{closure}}::hcdcc5b54aa3d2cb3
  18:     0x564e71643e00 - std::rt::lang_start_internal::h5e7c81cecd7f0954
  19:     0x564e70bb18c5 - main
  20:     0x7f966f2bed90 - __libc_start_call_main
                               at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16
  21:     0x7f966f2bee40 - __libc_start_main_impl
                               at ./csu/../csu/libc-start.c:392:3
  22:     0x564e70b23da5 - _start
  23:                0x0 - <unknown>

I am building yr using the main branch on the latest commit (e7f636343d7ca632778d630b126e8c56f0502ac2)
I understand that this is a ridiculous amount of strings to have in a single rule, but in yara 4, I was able to set --max-strings-per-rule and compile the file successfully.

What's the condition in the rule?

What's the condition in the rule?

any of them
I was able to recreate this bug using a (poorly written) python script:
#!/usr/bin/env python
import random
import string

def main():
    file_content = ['rule big_rule : big_rule {\n', '  strings:\n']
    for count in range(131533):
        file_content.append(f'    ${count} = "{''.join(random.sample(string.ascii_letters, 16))}" wide ascii nocase fullword\n')
    file_content.extend(['  condition:\n', '    any of them\n', '}'])
    with open('big_rule.yar', 'w') as rule_handle:
        rule_handle.writelines(file_content)

if __name__=="__main__":
    main()

I'm afraid there's little I can do about this, except limiting the number of patterns per rule to a reasonable number in order to prevent the crash. YARA and YARA-X have different constraints, and their own set of advantages and disadvantages. This is an extreme edge case that hits a limit that is hard or impossible to circumvent.


Scheduled message forwarding processor create form doesn't mandate the message store field

Description:
When a user creates a Scheduled message processing store, he is not required to provide the message store. Hence, when the message processor is created, the field messageStore is left empty. If the user happens to run the code as it is, he will run in to a Null Pointer Exception due to the missing message store.
Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

The latest pre-release v1.1.0 has resolved the issue. Please reopen if the problem persists.


[Feature] Nuke Password (Password to delete database)

Is your feature request related to a problem? Please describe.
In some circumstances deleting database needs to be stealthy
Describe the solution you'd like
The best way to silently delete a database is by entering a password giving the impression you are trying to unlock the database when in fact you are deleting it!
Additional context
It would be highly recommended to replace the deleted database with a new fake one with a predetermined password and with some random data or just empty to make the process stealthy.

I think just giving support for Ripple is a better idea.

@VioletFalcon good idea, I dont know it yet, but will have a look into it.

@VioletFalcon Yes that would be good but Ripple hasn't been updated for years now and even if it still works it's not guaranteed to still work in future android releases so having an In-app solution is always better in this case!

@fux0r2009 Well, probably you're right, because anyways official F-Droid client has the feature to uninstall any app you want with the panic trigger.

@VioletFalcon Uninstalling the app will always delete the whole database, since backups of the internal files are turned of.

@VioletFalcon @fux0r2009 I dont really know ripple. Is it still known and used.
If so, we can add ripple support additionally.

@VioletFalcon @fux0r2009 I dont really know ripple. Is it still known and used?
If so, we can add ripple support additionally.

Idk, the maintainer is a F-Droid contributor, sure they can give a better response.
As I said, official F-Droid client already has the option to uninstall Photok + data with the panic trigger so, not really needed IMO

@VioletFalcon @fux0r2009 I dont really know ripple. Is it still known and used?
If so, we can add ripple support additionally.

Idk, the maintainer is a F-Droid contributor, sure they can give a better response.
As I said, official F-Droid client already has the option to uninstall Photok + data with the panic trigger so, not really needed IMO

Maybe, but Photok is also available on Gplay and so on. I think, I will give it a try.

This looks pretty easy to implement and supports many panic buttons. Maybe I will do something like this in addition.

This looks pretty easy to implement and supports many panic buttons. Maybe I will do something like this in addition.

Yeah sure why not, If it's easy to implement it won't hurt thank you @leonlatsch for your work as always :)

@fux0r2009 @VioletFalcon Do you guys think support for panic buttons is enough?
I don't know if I like the nuke password.
Maybe I could add a button on the lock page to reset the app. But I already had this dilemma before release. Someone could just reset your app without the password. Which is not nice. BUT, they can do it anyway, because they could uninstall the app, soooo.
Whats your opinion?

@leonlatsch Yes the panic button support is nice to have but please don't give the option to put a button that could reset the app without a password as this would be catastrophic for the Non-saved data!


Tasks not executed by the Compute Nodes in Ubuntu Cfncluster image

Hi,
I'm trying to use CfnCluster 1.2.1 for GPU computing and I'm using a custom AMI based on the Ubuntu 14.04 CfnCluster AMI.
Everything is created correctly in the CloudFormation console, although when I submit a new test task to Oracle Grid Engine using qsub from the Master Server, it never gets executed from the queue according to qstat. It stays always in status "qw" and never enters state "r".
It seems to work fine with the Amazon Linux AMI (using user ec2-user instead of ubuntu) and the exact same configuration. Also, the master instance announces the number of remaining tasks to the cluster as a metric, and new compute instances are auto-scaled as a result.
What mechanisms does CfnCluster or Oracle Grid Engine provide to further debug this? I took a look at the log files, but didn't find anything relevant. What could be the cause for this behavior?
Thank you,
Diego

I think I found the solution. It seems to be the same issue as the one described in #86.
I fixed it by adding the following line to the CfnCluster configuration file:
    base_os = ubuntu1404
If a custom_ami is specified but no base_os is specified, it defaults to use the Amazon Linux, which uses a different method to configure SGE. There may be problems in the SGE configuration performed by CfnCluster if base_os and custom_ami os are different.
I would suggest to clarify this in the configuration documentation (either as part of the base_os or the custom_ami parameter). Maybe one of this parameters need to be compulsory for the cluster to boot?

Thanks for raising the issue. We'll make updates to the documentation.

Hi,
does cfncluster support ubuntu1404 clusters now? From this issue I understood yes but when we tried to create a cluster with the following configuration parameters:
base_os = ubuntu1404
custom_ami = ami-38e80e57
on the region eu-central-1 it failed to create the cluster.
The failure was a ROLLBACK after the SQS-CREATE_IN_PROGRESS event and during the create user or so it seemed from the logs.
Should we assume ubuntu1404 is not supported yet? Or should we persist and try to make it work.
We are using cfncluster version  1.2.1 installed with pip.
Thank you for any light you can shed on this to save us time.
Andy

Hi Andy,
Ubuntu 1404 is absolutely supported. Can you provide some more details regarding your issue. The AMI id you have provided is the base AMI from CfnCluster, so you do not need to put it in the config.
What is your AWS Account Number and I can see if I can determine from problem.
-Dougal

Hi Doug,
thanks a lot for this +ve answer. Our account number is<PHONE_NUMBER>52. I have attached the cfncluster config file.
config.txt
Any help you can offer us to get an ubuntu cluster up and running would be highly appreciated.
Andy

If you run cfncluster status fdmtest2, you should see the errors reported by CloudFormation before it did the rollback.
At a high level, you are attempting to launch into a VPC which does not have the required networking configured. I see that you are attempting to use a HTTP proxy however the VPC does not have any way to access anything because either a) it has not IGW or b) it has no VGW. Also you do not need to specify custom_ami.
I would recommend configuring your VPC with an IGW to get comfortable with CfnCluster and it's config options.

Thanks for the quick answer. I will have to learn more about IWG and VGW to solve the problem. We will get back to you once we have understood the networking aspects better and if we have still not solved the problem.
Kind regards
Andy

You can email me at dougalb at amazon dot com, and I can probably connect you will our local team.


[BACKPORT] stm32f40xxx_i2c isr processing

Due to some errant condition (I2C error or code)
The ISR was being rentered until the end of the
frame. Causing other ISR to not run for 280 uS.
Backport of Alexander Oryshchenko comits
d1cfcab, 643234d, 9b812e3 fixes this condition.
Tested with this file using an arduino nano and a BS170 FET.
DUT was FMUv4 RC15 with 3DR HMC5885+GPS (Both cables connected)
Nano connected as follows:
GND = DUT GND pin 4 I2C Cable
D3 = DUT SDA     pin 3 I2C Cable
D2 = DUT SCL      pin 2 I2C Cable
BS170 Drain (1)   to D3 (DUT SDA)
BS170 Gate (2)  to  D13
BS170 Source (3) to  GND
See https://github.com/PX4/Firmware/issues/7968 and https://github.com/PX4/Firmware/issues/7951 for reference.
Reset is called as needed and there are no extra interrupts.

Bad 926 us.

Fixed: 858 us.

@dagar to answer your question the delta was typically 68 us. I am not sure that would have been picked up. Some longer operation had deltas of 234 uS - that might be detectable.

@LorenzMeier PX4/Firmware PR is here https://github.com/PX4/Firmware/pull/10714


LWT support

We need to support and test LWT (lightweight transaction) queries - the ones that have conditions within them, e.g. IF EXISTS.
We also have a Scylla-specific optimization, which returns a flag when preparing a statement that this statement is a lightweight transaction. We can then reduce the number of paxos conflicts by trying to always send the requests of the same key to the same node, which is assumed to be the paxos coordinator.
We should also have tests for LWT queries.

More info about the LWT optimization which might be useful:
Here's a PR to gocql which adds support for it: https://github.com/scylladb/gocql/pull/49
Discussion in a gocql issue about this optimization: https://github.com/scylladb/gocql/issues/40
Commit in Scylla which provides support for it: https://github.com/scylladb/scylla/commit/6028588148c556151d764f2a987c276cb4a21eb0

Currently still missing the "applied" flag when executing LWT requests. Is there anything planned for this or shall we look for a workaround?


Proper Documentation

First i appreciate to make this kind of simulator for project purpose, which helps us a lot by making it open source. But there is only one problem which is proper documentations not available. and yours python and ROS api is not working. i have tried all the ways still it connect to simulator but didn't work. if you can't tell me here then reply me in my mail<EMAIL_ADDRESS>I need your help for making my project successful and complete my graduation project.

Thanks a lot for your appreciation for AutoDRIVE! This project is very close to our heart for several reasons and we will keep trying our best to make sure that a lot of people benifit from it.
Regarding documentation, we have currently included instructions that can help people (having some experience working with similar platforms/ecosystems) get started easily. That being said, we are currently working on creating a comprehensive documentation for all the components of AutoDRIVE ecosystem, releasing the technical report and even writing a paper on it. Please understand that this may take some time since it is just the two of us working on this (among other things), but it will defenitely be available very soon!
Regarding the APIs, we have extensively verified that the C++ and Python APIs as well as the ROS package are all working as expected in single as well as distributed computing settings. Could you please share the exact problem/error that you are encountering?  We can also help you over a video call (over a weekend) if you are not able to get going.

Hi, Thanks for replying
We can connect anytime whenever you guys are available. I am from India so
do mention time and date when you are available.
My system specs are :-
Ubuntu 20.04
Ros Neotic full
Python 3.7 and 3.8 both
Thank You
Smit Savaliya
On Wed, 28 Sept 2022, 6:40 am Tinker Twins, @.***>
wrote:

Thanks a lot for your appreciation for AutoDRIVE! This project is very
close to our heart for several reasons and we will keep trying our best to
make sure that a lot of people benifit from it.
Regarding documentation, we have currently included instructions that can
help people (having some experience working with similar
platforms/ecosystems) get started easily. That being said, we are currently
working on creating a comprehensive documentation for all the components of
AutoDRIVE ecosystem, releasing the technical report and even writing a
paper on it. Please understand that this may take some time since it is
just the two of us working on this (among other things), but it will
defenitely be available very soon!
Regarding the APIs, we have extensively verified that the C++ and Python
APIs as well as the ROS package are all working as expected in single as
well as distributed computing settings. Could you please share the exact
problem/error that you are encountering? We can also help you over a video
call (over a weekend) if you are not able to get going.
—
Reply to this email directly, view it on GitHub
https://github.com/Tinker-Twins/AutoDRIVE/issues/1#issuecomment-1260265250,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMVMOZJYYE2A2XCMU5TBVOTWAOLHBANCNFSM6AAAAAAQVISOPY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hope today's discussion was helpful!
Following is a quick review of today's discussion:

AutoDRIVE Simulator Paper hosts details that can serve as potential documentation in addition to the various README files in this repository.
AutoDRIVE Python API has the following dependencies (tested with Python 3.6.5):

Package
Version

eventlet
Infrastructure

eventlet
Infrastructure

eventlet
Infrastructure

eventlet
Infrastructure

eventlet
Infrastructure

eventlet
Infrastructure

Package                Version
eventlet               0.25.0
Flask                  1.1.1
Flask-SocketIO         4.1.0
python-engineio        3.13.0
python-socketio        4.2.0
numpy			1.13.3
pillow			5.1.0
opencv-contrib-python	<IP_ADDRESS>

Thanks, for helping and solving the issue for me.
On Sun, 2 Oct 2022 at 22:56, Tinker Twins @.***> wrote:

Hope today's discussion was helpful!
Following is a quick review of today's discussion:

AutoDRIVE Simulator Paper https://arxiv.org/pdf/2103.10030.pdf
hosts details that can serve as potential documentation in addition to the
various README files in this repository.
AutoDRIVE Python API has the following dependencies (tested with
Python 3.6.5):

Package Version
eventlet Infrastructure
eventlet Infrastructure
eventlet Infrastructure
eventlet Infrastructure
eventlet Infrastructure
eventlet Infrastructure
Package Version
eventlet 0.25.0
Flask 1.1.1
Flask-SocketIO 4.1.0
python-engineio 3.13.0
python-socketio 4.2.0
numpy 1.13.3
pillow 5.1.0
opencv-contrib-python <IP_ADDRESS>
—
Reply to this email directly, view it on GitHub
https://github.com/Tinker-Twins/AutoDRIVE/issues/1#issuecomment-1264693498,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMVMOZMFK7GKT3AXQUMOKRDWBHAVHANCNFSM6AAAAAAQVISOPY
.
You are receiving this because you authored the thread.Message ID:
@.***>


fixes #8

Issue #, if available:
fixes #8
Description of changes:
configure DDB to use on-demand billing
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Great call out!


Hollow oceans

Chunker Version
cli-1.1.1
Input World Version
1.20.1 "Modded" Java (see more details in description)
Output World Version
Bedrock 1.20.0
Platform / Operating System
Linux Debian 11
Issue Description
I generated a whole 15k (radius) map on Java 1.20.1 based on neoforge using some custom generation mods (Mod list: Chunky, Flat bedrock, journeymap(should be only client), tectonic, terralith).
Tectonic & Terralith are mods that can generate beautiful maps but using only vanilla content.
After generation I figured out I only needed 10k of radius so I decided to shrink it while converting to bedrock using chunker.
Here's the used command:
java -Xmx16G -Xms1G -jar chunker-cli-*.jar -i inputs/$1 -o outputs/$2 -f BEDROCK_1_20_0 -m block_mappings.chunker.json -p pruning.chunker.json
Files:
block_mappings.chunker.json
pruning.chunker.json
After this I checked if everything was fine using a Pocketmine server (that does not converted the map at any time nor altered its content) and saw this :

For comparison on the java map :

It seems that subchunks that were only filled with water were just removed from the map (first separation at y16; second one at y32 etc..) The one with kelp stayed there and the surface is still there too.
I could be able to upload the map but the original java map is 40GB and the converted one is 7GB (that's a huge difference btw ?) so if you want it just ask me I will upload it on my drive.

Just to remove an issue factor I tried directly in vanilla bedrock, it's exactly the same

If you're able to send a region file (.mca) impacted by this to either attach or send it to<EMAIL_ADDRESS>with relevant co-ordinates of the missing chunk(s). In the case you don't know how to do this, just move forward to the impacted chunks and look in the F3 under Chunk for the mca file name then look in region/r.x.x.mca

If you're able to send a region file (.mca) impacted by this to either attach or send it to<EMAIL_ADDRESS>with relevant co-ordinates of the missing chunk(s). In the case you don't know how to do this, just move forward to the impacted chunks and look in the F3 under Chunk for the mca file name then look in region/r.x.x.mca

Here's the file corresponding to the screenshot above https://drive.histeria.fr/f/84cbb88befb44771825a/

If you're able to send a region file (.mca) impacted by this to either attach or send it to<EMAIL_ADDRESS>with relevant co-ordinates of the missing chunk(s). In the case you don't know how to do this, just move forward to the impacted chunks and look in the F3 under Chunk for the mca file name then look in region/r.x.x.mca

Here's the file corresponding to the screenshot above drive.histeria.fr/f/84cbb88befb44771825a

Thanks, we'll get this fixed for the next patch release

This should be fixed in the new release :)


Data files for GGR and GZC have different cases for features

The EXIF and FTR files for GGR and GZC are in different cases. The headers of the fields need to match.
Preferably, everything should be in UPPER CASE

This issue is resolved since the features will now be pulled from MongoD instance and it will all have an uniform interface.


Fix/normalize primary color login screen

Before submitting this PR, please make sure:

[x] Your code builds clean without any errors or warnings
[x] You are using approved title ("feat/", "fix/", "docs/", "refactor/")

A description of the changes proposed in the pull request:
This fix was required to keep consistency at the color palette of the application as pointed out in https://github.com/hummingbot/hummingbot/issues/4905. It would be good to use not only the default value but also ensure that future new configuration values could be handled.
Tests performed by the developer:
The test performed consisted of opening the application in a second run and observing that the input password dialog text color is the same as in the console. A screenshot is attached as evidence.

Tips for QA testing:
No extra steps are needed for QA testing.

Hello @sisco0
A Pull Request Proposal was created related to this PR: https://snapshot.org/#/hbot.eth/proposal/0x003194b105a0f09f9ae52ebe4b3fb5a79e7abfe9dac8d5bdea6dc19aae1bc23d
Make sure to keep an eye on community reviews for the following days.
Thank you for contributing with Hummingbot Client!


domd: Remove product specific packages

sndbe and camerabe are product specific things, so should
be added in product's bbappend-files.
Signed-off-by: Ruslan Shymkevych<EMAIL_ADDRESS>

Must be merged ONLY AFTER merge of https://github.com/xen-troops/meta-xt-prod-devel-rcar/pull/41

Successfully tested with https://github.com/xen-troops/meta-xt-prod-devel-rcar/pull/41 on h3ulcb-4x2g-kf.

Reviewed-by: Andrii Chepurnyi<EMAIL_ADDRESS>

RB is added.
Successfully tested with https://github.com/xen-troops/meta-xt-prod-devel-rcar/pull/41.
Ready to be merged ONLY AFTER https://github.com/xen-troops/meta-xt-prod-devel-rcar/pull/41


EOG and ECG channels added to the bottom of ICA plot.

Proposed at https://github.com/mne-tools/mne-python/pull/2251.

looks clean to me! I see a bit of code reduplication. Maybe worth a small function. Other than that do you thinki we should add a test?

is this a MRG PR?

Ready for merge?

not yet... why is this not captured by tests?
In [2]: ica.plot_sources(epochs)
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-2-99fbf26e752b> in <module>()
----> 1 ica.plot_sources(epochs)

/Users/alex/work/src/mne-python/mne/preprocessing/ica.py in plot_sources(self, inst, picks, exclude, start, stop, title, show, block)
   1389         return plot_ica_sources(self, inst=inst, picks=picks, exclude=exclude,
   1390                                 title=title, start=start, stop=stop, show=show,
-> 1391                                 block=block)
   1392
   1393     def plot_scores(self, scores, exclude=None, axhline=None,

/Users/alex/work/src/mne-python/mne/viz/ica.py in plot_ica_sources(ica, inst, picks, exclude, start, stop, show, title, block)
    116         fig = _plot_sources_epochs(ica, inst, picks, exclude, start=start,
    117                                    stop=stop, show=show, title=title,
--> 118                                    block=block)
    119     elif isinstance(inst, Evoked):
    120         sources = ica.get_sources(inst)

/Users/alex/work/src/mne-python/mne/viz/ica.py in _plot_sources_epochs(ica, epochs, picks, exclude, start, stop, show, title, block)
    693                                n_epochs=n_epochs, scalings=scalings,
    694                                title=title, picks=picks,
--> 695                                order=['misc', 'eog', 'ecg'])
    696     params['hsel_patch'].set_x(params['t_start'])
    697     callback_close = partial(_close_epochs_event, params=params)

/Users/alex/work/src/mne-python/mne/viz/epochs.py in _prepare_mne_browse_epochs(params, projs, n_channels, n_epochs, scalings, title, picks, order)
    660     inds = np.concatenate(inds).astype(int)
    661     if not len(inds) == len(picks):
--> 662         raise RuntimeError('Some channels not classified. Please'
    663                            ' check your picks')
    664     ch_names = [params['info']['ch_names'][x] for x in inds]

RuntimeError: Some channels not classified. Please check your picks

works like a charm.
thanks @jaeilepp  !


[PE-D][Tester B] Activity diagram: difficult to read due to font size

The font size of the words in the diagram is small, making it hard for reader to analyse the diagram without needing to zoom in a lot.

Labels: severity.VeryLow type.DocumentationBug
original: SherniceSng/ped#9

try wrapping


Fix presenter flapMapLatest

📜 Description
add filterUiState function on LbReducer since the as? cast does work with weird generic behaviour,
Prevent wrong uiState to enter wrong reduce function
💡 Motivation and Context
Crash in DMP
💚 How did you test it?
No more crash in DMP
📝 Checklist

[x] I reviewed the submitted code
[x] I launched ./gradlew detekt
[x] I filled the changelog

🔮 Next steps
📸 Screenshots / GIFs

          1 Warning

:warning:
Please add labels to this PR

  Generated by :no_entry_sign: Danger


French translation

Thank you for this! Could you please add translations for other platforms as well so I could merge it? JDA, Velocity, Sponge, etc., though on the good side many of them are repeated.

Thank you for this! Could you please add translations for other platforms as well so I could merge it? JDA, Velocity, Sponge, etc., though on the good side many of them are repeated.

Done!

Thank you!


Update undefined values to be explicit

The existing function calls were subtly passing along undefined values; this update makes it explicit.
(either way, the 3 values are being set to '; Expires=Thu, 01 Jan 1970 00:00:00 GMT')
Fixes: #89

LGTM


Nar-Sheptha

text: Will not trigger FBI Special Affairs Division because the attached vampire is not the acting minion during the combat.
link: http://www.vekn.net/forum/rules-questions/76998-narsheptha-fbi?start=6#90588

The ruling is already registered under FBI. It makes more sense, I think, than having the ruling under Nar-Sheptha, as it's more about the FBI effect than about Nar-Sheptha's.