Upload of package version of same name causes error and package removal

Anaconda Cloud seems to have changed how they handle uploads of packages where there is already a package of the same name and version on Anaconda Cloud. In the past, this simply just resulted in the artifact being uploaded overwriting the previous artifact. networkx is one of the core packages that used this approach. However, I noticed that networkx's nightly workflow is failing to do so

...
File type is "Standard Python"
Extracting standard python attributes for upload
Creating package "networkx"
Creating release "3.3rc0.dev0"
Uploading file "scientific-python-nightly-wheels/networkx/3.3rc0.dev0/networkx-3.3rc0.dev0-py3-none-any.whl"
Warning:  Distribution "networkx-3.3rc0.dev0-py3-none-any.whl" already exists. Removing.
Error:  ("release version='3.3rc0.dev0' does not exist", 404)
##[debug]Docker Action run completed with exit code 1
##[debug]Finishing: Upload nighlty wheel

(The success after failure is due to the package being removed and so there is no conflict the next upload.)
This started happening on 2024-01-04 for networkx, and was not happening before that. We know that as we're using a lock file
https://github.com/scientific-python/upload-nightly-action/blob/6f1e2b99c3148480df25d296c27ae58c446ad5d0/cmd.sh#L57-L60
that nothing has changed from the upload-nightly-action action side, and so this has to be on the Anaconda Cloud side.
cc as a heads up to @MridulS @jarrodmillman

Opened https://github.com/Anaconda-Platform/anaconda-client/issues/702 to try to get input from Anaconda.

While we are at it, could we update the token used by NetworkX? It's still using a global token instead of a personal one which is less than ideal. (Xarray is the only other one doing that, and we should also migrate)

While we are at it, could we update the token used by NetworkX? It's still using a global token instead of a personal one which is less than ideal. (Xarray is the only other one doing that, and we should also migrate)

@MridulS @jarrodmillman can you please take care of this for NetworkX? I don't remember who is responsible for the Xarray uploads, so tagging @martinfleis to see if they can do it or point us to the correct people to ask. (@tupui  if you know please tag them in. :+1:)

That's the thing I don't know who they are as the team on Anaconda is empty 😅 (sorry for hijacking the issue, him...)

@matthewfeickert I believe that @keewis is the one with right permissions over in xarray.

Also hitting this in scipy-openblas32 and scipy-openblas64, with @honno's API key, see the latest merge CI run which all failed to upload.

I wonder what permissions are missing on the existing token? Here are the possible ones. This action recommends "Allow write access to the API site" and "Allow uploads to Standard Python repositories"

See https://scientific-python.org/specs/spec-0004/#process-for-adding-new-projects:

The token should only have the “Allow uploads to Standard Python repositories”, “Allow read access to the API site” and “Allow write access to the API site” scope.

Could an admin check that the tokens in question have the "Allow read access to the API site" permission?

Also hitting this in scipy-openblas32 and scipy-openblas64, with @honno's API key, see the latest merge CI run which all failed to upload.

@mattip This is a different issue, so can you please move the discussion to Issue #61?

Are you using the --force option?
anaconda upload \     /opt/anaconda/conda-bld/osx-64/argh-0.24.1-py39_0.tar.bz2  --force

Are you using the --force option? We are able to run a command like this one. anaconda upload /opt/anaconda/conda-bld/osx-64/argh-0.24.1-py39_0.tar.bz2 --force.

@dholth, yes. This is the command that is being run
https://github.com/scientific-python/upload-nightly-action/blob/66bc1b6beedff9619cdff8f3361a06802c8f5874/cmd.sh#L75-L79

Multiple archives are being uploaded with one command?

Multiple wheels, yes. I assume that's what you mean by archives here.
The problem here is not that the command can not run, it is that there has been a behavior change in how Anaconda Cloud seems to be dealing with the isntance when there already exists a package release of the same name. To step through (the perceived order of events) for what is causing the fail/pass alternation in

First, networkx always uploads a nightly wheel with the exact same name (networkx-3.3rc0.dev0-py3-none-any.whl), so they are always going to try overwrite the previous wheels they uploaded.

In https://github.com/networkx/networkx/blob/31ef96361fc95ce8789d780cbc5bb4b3c4e27eb9/.github/workflows/nightly.yml a wheel is built and then using

      - name: Upload nighlty wheel
        uses: scientific-python/upload-nightly-action@6e9304f7a3a5501c6f98351537493ec898728299 # 0.3.0
        with:
          anaconda_nightly_upload_token: ${{ secrets.ANACONDA_NIGHTLY }}
          artifacts_path: dist/

which is going to call the anaconda upload --force command above, is run.

The uploaded creates the package and release and begins the upload to Anaconda cloud (e.g. https://anaconda.org/scientific-python-nightly-wheels/networkx/)

+ anaconda --token *** upload --force --user scientific-python-nightly-wheels --label main dist/networkx-3.3rc0.dev0-py3-none-any.whl
Uploading wheels to anaconda.org...
Using Anaconda API: https://api.anaconda.org
Using "scientific-python-nightly-wheels" as upload username
Processing "dist/networkx-3.3rc0.dev0-py3-none-any.whl"
Detecting file type...
File type is "Standard Python"
Extracting standard python attributes for upload
Creating package "networkx"
Creating release "3.3rc0.dev0"
Uploading file "scientific-python-nightly-wheels/networkx/3.3rc0.dev0/networkx-3.3rc0.dev0-py3-none-any.whl"

It detects that there already is a distribution of the same name at the upload location and removes it

Warning:  Distribution "networkx-3.3rc0.dev0-py3-none-any.whl" already exists. Removing.

This is also removing the only file under the https://anaconda.org/scientific-python-nightly-wheels/networkx package.

Anaconda cloud throws a 404 that the distribution does not exist (I don't know why this happens)

Error:  ("release version='3.3rc0.dev0' does not exist", 404)

and despite the --force option being used at this point things stop and exit out with exit code 1.
##[debug]Docker Action run completed with exit code 1
##[debug]Finishing: Upload nighlty wheel

The next day (the workflow runs on a nightly schedule) steps 1 and 2 are repeated, but as there is no existing distribution of that name given the upload failed the previous day, step 3 never happens and the upload succeeds.

+ anaconda --token *** upload --force --user scientific-python-nightly-wheels --label main dist/networkx-3.3rc0.dev0-py3-none-any.whl
Using Anaconda API: https://api.anaconda.org
Using "scientific-python-nightly-wheels" as upload username
Processing "dist/networkx-3.3rc0.dev0-py3-none-any.whl"
Detecting file type...
File type is "Standard Python"
Extracting standard python attributes for upload
Creating package "networkx"
Creating release "3.3rc0.dev0"
Uploading file "scientific-python-nightly-wheels/networkx/3.3rc0.dev0/networkx-3.3rc0.dev0-py3-none-any.whl"

  0%|          | 0.00/1.60M [00:00<?, ?B/s]
 62%|██████▏   | 0.98M/1.60M [00:00<00:00, 10.3MB/s]
1.60MB [00:00, 6.89MB/s]
Upload complete

standard python located at:
  https://anaconda.org/scientific-python-nightly-wheels/networkx

This started happening on 2024-01-04. The last change to our lock file for our software environment and upload command before 2024 (5fb764c5bce1ac2297084c0f7161b1919f17c74f) was on 2023-10-06.
You can see from the networkx workflow run history that before 2024-01-04 this exact same workflow ran without errors every day.
(Earliest successful run in this screenshot is 2023-12-24 and the first failing run at the top is 2024-01-04)

Given all this, my take away is that there was some backend (well, backend from the user point of view) change in Anaconda Cloud on 2024-01-04 that caused this breaking behavior.

If it is helpful at all, I can also provide the passing 2024-01-03 and failing 2024-01-04 full run logs (for the same workflow).

Multiple archives are being uploaded with one command?

So in https://github.com/Anaconda-Platform/anaconda-client/issues/702#issuecomment-1935022769 it seems that there is different behavior with one archive/wheel being uploaded vs. multiple. :? Or more accurately, with multiple archives being uploaded it is more unclear what is causing the original 404 error that is causing everything to break.


Formatting error for GP numbers

Country: Guadeloupe, Saint-Martin, Saint-Barthélemy (GP, MF, BL)
Example number(s) and/or range(s): +590
Number type ("fixed-line", "mobile", "short code", etc.): fixed-line, mobile
For short codes, cost and dialing restrictions: n/a
Where or whom did you get the number(s) from: synthesized from correct format
Authoritative evidence (e.g. national numbering plan, operator announcement): common usage, the formatting rules for GP numbers should be consistent with the other French overseas territories (MQ, GF, RE), all managed by the same authority (ARCEP) under a common numbering plan https://www.arcep.fr/uploads/tx_gsavis/05-1085.pdf
Link from demo (http://libphonenumber.appspot.com) showing error:

http://libphonenumber.appspot.com/phonenumberparser?number=%2B590590300000 (fixed-line)
is formatted as +590 590 30-0000
should be formatted as +590 590 30 00 00
http://libphonenumber.appspot.com/phonenumberparser?number=%2B590690000000 (mobile)
is formatted as +590 690 00-0000
should be formatted as +590 690 00 00 00
The following examples show the correct formatting for French overseas numbers (examples from Martinique, French Guiana, Reunion) that should be applied to Guadeloupe
http://libphonenumber.appspot.com/phonenumberparser?number=%2B596596300000
http://libphonenumber.appspot.com/phonenumberparser?number=%2B594594300000
http://libphonenumber.appspot.com/phonenumberparser?number=%2B262262300000

Hi jice, please follow this issue in Issue Tracker going forward as we are now closing GitHub: https://issuetracker.google.com/issues/74518936 Using Issue Tracker will enable to us to get back to you more efficiently as we align GitHub user issues with ones reported at Google.


Chatbot backend

Basic Information
Implement the backend for the chatbot. This will include:

[x] Adding API endpoints to perform ChatGPT calls
[x] Use the OpenAI "Assistants" feature to create a custom chatbot GPT which is focused on providing information about methods of donation

See here for information about Assistants
The bot should use information from the existing donations pages on Starick's site for context. We'll try aggregate this information into a single document for ease of reference (not done yet, will comment when done)

[ ] Integrating with the frontend

We will provide you with an OpenAI key upon request if you're working on this issue, let us know
Other Information
See #23 for an idea of how this will integrate into the frontend

Prompt engineering needed to finish this issue

Accidentally closed, will still require prompt engineering

Information on how to use the API is in the README.
Provides a single response (not streamed).

Due to facebook no longer continuing to support messenger plugin(and following consultation with Starick), this issue/feature will be discontinued.


Incompatibility between 2.5.1 and 2.0.1 breaks connected factory's endpoint list.

Describe the bug
Connected factory does not work with OPC Twin module 2.5.1.
To Reproduce
Steps to reproduce the behavior:

Deploy connected factory
Deploy edge with 2.5.1 and turn scan on
Once scan completes hit Endpoints button.
No endpoints shown.

Expected behavior
Endpoints should be shown.   With 2.0.1 they are shown.

Does not reproduce with Services + CLI 2.0.1 and Twin module 2.5.1.   Moving to connected factory for debugging/fix.


Show currency rate

Show currency rate used (e.g. USD/EUR) after the KiCost version and allow change it.
The change will be made at spreadsheet.py the the original currency information of each distributor should be kept before (modification at API use and local distributor code).

Marked as bug because this is will fix the issue of not available currency in the new API.

@xesscorp, this fix mine implement the correspondent functionality and solve the not got Farnell and other distributors price_tiers.
The issue is because some distributors haven't USD in the PartInfo API.
Now I express the currency rate used by KiCost in the spreadsheet. Some validation (and alignment of the text to left) should be really useful for me.
Do you have a round map plan for next issues and release?


Added Automation integration demo

LGTM, only thing I notice is that depending on if this goes in first or Upgrades go in first we will need a few tweaks to:

Read from proxy address, network-config changes
Use exact path for contract factories because now there is a name clash from the migration (also just good to do in general)

I'll let @bolekk give a re-review before we merge


ryujinx: 1.1.1358 -> 1.1.1364

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for ryujinx is: Experimental Nintendo Switch Emulator written in C#
meta.homepage for ryujinx is: https://ryujinx.org/
meta.changelog for ryujinx is: https://github.com/Ryujinx/Ryujinx/wiki/Changelog
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.1364 with grep in /nix/store/p6kd131a6fc8fwylnhcm7rld5v3hbg20-ryujinx-1.1.1364
found 1.1.1364 in filename of file in /nix/store/p6kd131a6fc8fwylnhcm7rld5v3hbg20-ryujinx-1.1.1364

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

ryujinx

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/a6b29ac954b428f06b9f59b5b24d0527a556e859#ryujinx

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

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

1 package built:

ryujinx

Maintainer pings
cc @06kellyjac @artemist for testing.

@NixOS/nixpkgs-merge-bot merge


[docs] Add v5 banner

Preview: https://deploy-preview-27070--material-ui.netlify.app/

The font size is too large: body1-> body2
The background color in dark mode can be grey

It definitely feels better with a smaller type and a little bit more padding. And also agree that the primary dark color doesn't work so well on dark mode. I've used the palette.background.paper on this tweak here.
Also, changed the emoji to the beginning just so v5 isn't too lonely there starting out.

A close button

Don't think it's needed, I believe that the type of announcements that are placed on a banner like this, persistent on the home page, are the ones we'd want to have on there for a given time-box so we can promote the news as loud as we can. We could and should make it look better though when we revamp the documentation design (maybe for the stable rollout of v5?!), the current Material Design look doesn't make me that excited about v5 😅

To leave the infrastructure in place to have other important announcement

Definitely!

For v4, we tried to align this:

but maybe it's fine

We forgot to account for the anchor offset:
https://material-ui.com/guides/minimizing-bundle-size/#option-1

I have done a quick fix: 125f3db635.


Mapping the depth image to a color image.

Is it possible to get data from the methods: get_last_color_frame and get_last_depth_frame
after mapping the depths to color and vice versa? I have a problem using ICoordinateMapper methods. It is about the get data eliminating the differences of camera positions. Something like in openni2 ONI_IMAGE_REGISTRATION_DEPTH_TO_COLOR

me too having a problem with ICoordinateMapper. any progress if you made?

Same here

Same here

I have made a library with all the ICoordinateMapper function if you would like to see:
https://github.com/KonstantinosAng/PyKinect2-Mapper-Functions

I have made a library with all the ICoordinateMapper function if you would like to see:
https://github.com/KonstantinosAng/PyKinect2-Mapper-Functions


Build(deps-dev): Bump webpack-dev-server from 4.7.3 to 4.7.4 (#2645)

Pull request opened by the merge tool on behalf of #2645

Merged in 0fea4d80eb12c092306ca2ac12c92326966d8d15


How to block .yabo-firstcol-box?

This is only visual polution. Real URL has been removed.
If you wanna block that background, you can do this in your ADP advanced rule.
// add 1 rule
hltv.org##[class*="yabo"]

I will write a function to remove similar function to those users who have not install ADP.
Check it out later. Maybe tomorrow🧐


Cover level logic is reversed with Somfy interface

Home Assistant release (hass --version):
0.59.2
Python release (python3 --version):
3.6.1
Component/platform:
cover
Description of problem:
I recently included my Somfy Z-Wave interface to hassio. This resulted in switches and level entities being added for each channel successfully. However, the level operates in the opposite logic of the switch. Specifically with the level entity, the up button lowers the shade and the down button raises it. The stop button works as expected. With the switch entity, clicking the up arrow on the switch device raises the shade and clicking the down arrow lowers it. This appears it may be related to PR #2852 / issue #2849 where it sounds like these were flipped in a commit last year but I don't understand why.
Additionally, setting position seems broken for me. Setting the cover position to anything above 1 raises the shade completely and 0 closes it.
Expected:
The level entity should follow the logic of the switch where the up button raises and the down button lowers.

Can you post your configs for the cover and switches? This is not actually an issue to be honest since you can change this behaviour by defining the cover as a template like this and simply changing the on/off parameter of the value template.
- platform: template
  covers:
    garage_door:
      friendly_name: "Garage Door"
      value_template: "{{ is_state('binary_sensor.ecolink_garage_door_tilt_sensor_sensor', 'on') }}"
#      value_template: binary_sensor.ecolink_garage_door_tilt_sensor_sensor
      open_cover:
        service: script.garage_door_open
      close_cover:
        service: script.garage_door_close
      stop_cover:
        service: script.garage_door_switch
      icon_template: >-
        {% if is_state('sensor.ecolink_garage_door_tilt_sensor_sensor', 'on') %}
          mdi:garage-open
        {% else %}
          mdi:garage
        {% endif %}

@tschmidty69 I'm simply using the created entity from the paired zwave device (I'm using hass.io) which is why I opened it as an issue. The only thing I've added to the configs myself are the group memberships for the respective entities. If it were just a matter of tweaking my own config I would have done so :) Short of creating a new cover template that performs the opposite service action, this seems like a bug IMO.

What device/model are you using?

I am using the Somfy ZRTSI to control the Somfy shade motors. Let me know if you need any kind of logs from OZW or something.

There is an invert_openclose_buttons config value you can set in you zwave configuration:
zwave:
  device_config:
    cover.my_cover:
      invert_openclose_buttons: true

Oh and position sensor is apparently broken for that device which is why there is that workaround was implemented in the PR

Thank you @tschmidty69 - this is exactly what I needed! FWIW, there is no mention of this in the https://home-assistant.io/components/cover.zwave/ unless you dig into cover/zwave.py. I'll add a blurb and submit a PR.


Fixes issue where the data from Comments were written to the canonicaliz...

Fixes issue where c-14-n# algorithm was not removing comments.
Thanks to deoxxa/xml-c14n for the render comment code.
Adds out of the box support for the c-14-n#WithComments algorithm, this fixes an issue when dealing with SAML responses from KeyCloak.
Adds tests for c-14-n#WithComments

Thanks, great stuff! I will try to get to check it next weekend and publish to npm


Do not store .cpp/.h files inside src/main/java - reactperflogger

Summary:
Current we expose native code (.h, .cpp) inside the src/main/java folder.
This is making impossible for users on New Architecture to open the project
inside Android Studio.
The problem is that the src/main/java is reserved to Java/Kotlin sources only.
AGP 7.2 also removed support for mixed source roots:
https://developer.android.com/studio/releases/gradle-plugin#duplicate-content-roots
This is essentially forcing users to write Java code without any autocompletion
as all the React Native Java classes are considered C++ files.
I'm addressing this issue folder by folder by moving them
from ReactAndroid/src/main/java/com/facebook/... to ReactAndroid/src/main/jni/react/...
This is the diff for reactperflogger
Changelog:
[Internal] [Changed] - Do not store .cpp/.h files inside src/main/java - reactperflogger
Reviewed By: cipolleschi
Differential Revision: D38584681

Will have to wait for #34388 to merge this


Update qute-web

@all-contributors add @mkouba for code

SOrry @mkouba totally forgot to add you as contributor, Roq wouldn't be possible without the awesome Qute :)

SOrry @mkouba totally forgot to add you as contributor, Roq wouldn't be possible without the awesome Qute :)

No problem at all! Thanks Andy! ;-)


Update key-vault-ovw-storage-keys.md

Added more formatting

@fhokholdMSFT,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@BrucePerlerMS please review and merge. Just more formatting issues.

@fhokholdMSFT - approved. Adding sign-off tag

#sign-off

@fhokholdMSFT : Thanks for your contribution to the Azure documentation! The author, @BrucePerlerMS, has been notified to review your proposed change.

#sign-off


[storage-resize-images] Feature request: AVIF codec support

WebP is great, but AVIF is even better, please could you add support? 🙏
Thanks

Hey @jimmyff,
Thank you for raising this issue, good idea. I think this is possible as the Sharp library support it. I'll add it to the project tracker to be considered.
https://sharp.pixelplumbing.com/#formats


filter our repositories where certain licenses are not present

Let's check the licenses of repositories and exclude those that are not MIT, BSD or Apache. The existing discover-repositories.rb script should do this, I believe.

@yegor256 Issue is resolved in #284. Please close it. It is misleading.


Looking to forward traffic to dogstatsd from other containers

Do I need to set bind_host to something other than localhost, or is non_local_traffic: yes all I need?

Looks like non_local_traffic: yes may have been what I was looking for.


Layer list in mobile is hidden at bottom of the screen

@robert-waterman pushed this fix to PROD.


chore: Add provisioner context to log line

Fixes #
Description
Add provisioner context to log line that says "3 out of 573 instance types were excluded because they would breach provisioner limits"
Now, the log message says
2023-04-24T17:29:11.174Z        ERROR   controller.provisioner  Could not schedule pod, all available instance types exceed limits for provisioner: "default"   {"commit": "eb81e26-dirty", "pod": "default/inflate2-7f745d7464-cmslc"}
2023-04-24T17:29:21.175Z        ERROR   controller.provisioner  Could not schedule pod, all available instance types exceed limits for provisioner: "default"   {"commit": "eb81e26-dirty", "pod": "default/inflate2-7f745d7464-cmslc"}
2023-04-24T17:29:31.175Z        ERROR   controller.provisioner  Could not schedule pod, all available instance types exceed limits for provisioner: "default"   {"commit": "eb81e26-dirty", "pod": "default/inflate2-7f745d7464-cmslc"}
2023-04-24T17:29:41.183Z        ERROR   controller.provisioner  Could not schedule pod, all available instance types exceed limits for provisioner: "default"   {"commit": "eb81e26-dirty", "pod": "default/inflate2-7f745d7464-cmslc"}
2023-04-24T17:29:51.176Z        ERROR   controller.provisioner  Could not schedule pod, all available instance types exceed limits for provisioner: "default"   {"commit": "eb81e26-dirty", "pod": "default/inflate2-7f745d7464-cmslc"}
2023-04-24T17:30:01.177Z        DEBUG   controller.provisioner  530 out of 627 instance types were excluded because they would breach provisioner limits        {"commit": "eb81e26-dirty", "provisioner": "default"}
2023-04-24T17:30:01.178Z        INFO    controller.provisioner  found provisionable pod(s)      {"commit": "eb81e26-dirty", "pods": 1}
2023-04-24T17:30:01.178Z        INFO    controller.provisioner  computed new machine(s) to fit pod(s)   {"commit": "eb81e26-dirty", "machines": 1, "pods": 1}
2023-04-24T17:30:01.187Z        INFO    controller.provisioner  created machine {"commit": "eb81e26-dirty", "provisioner": "default", "requests": {"cpu":"1155m","memory":"120Mi","pods":"4"}, "instance-types": "c1.medium, c3.large, c4.large, c5.large, c5a.large and 51 other(s)"}
2023-04-24T17:30:01.893Z        DEBUG   controller.machine_lifecycle    created launch template {"commit": "eb81e26-dirty", "machine": "default-jc2hs", "provisioner": "default", "launch-template-name": "karpenter.k8s.aws/17037627427987710385", "launch-template-id": "lt-0b137aae0369ad41d"}
2023-04-24T17:30:02.435Z        DEBUG   controller.deprovisioning       waiting on cluster sync {"commit": "eb81e26-dirty"}

How was this change tested?
make presubmit
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
9 unchanged lines in 2 files lost coverage.
Overall coverage remained the same at 81.774%

Files with Coverage Reduction
New Missed Lines
%

pkg/scheduling/requirements.go
2
98.5%

pkg/controllers/node/controller.go
7
70.59%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
6793

Relevant Lines:
8307

💛  - Coveralls


Possible to use ngx-perfect-scrollbar with this component?

Is it possible to use ngx-perfect-scrollbar with this component?
parentScroll prop only seems to take html elements/window. Is there any way I can tell virtual-scroll to use the scrollbar from ngx-perfect-scrollbar?

I've never tried it, but in theory it should work with parentScroll.

Scrollable content

You'd want to assign parentScroll to the div.ps elemen
If you get it working, please create a simple demo so I can post your example code here on github for future users with this question.
Thanks.

Thanks, appreciate the help but I'm not exactly sure how do I assign the parentScroll element.
I use perfect-scrollbar in component mode so it is:
<perfect-scrollbar>
      <virtual-scoll parentScroll="??">...</virtual-scroll>
</perfect-scrollbar>

 has a
 element, but how do I pass this to parentScroll as this div does not have an Angular template ref attached to it.
Is there any syntax using css selectors that I can assign this div to parentScroll?

You'll need to use the "directive usage" syntax instead.

Scrollable content

Documentation here: https://www.npmjs.com/package/ngx-perfect-scrollbar
Then you can use the angular # syntax to get a reference to that div.

Thanks, that's perfect. I just had to add the following style to get it to work perfectly. What happened otherwise is that .scrollable-content which has height: 100% and max-height: 100vh gets computed height=100% of  and  in turn gets 100% of .ps-content which is the entire scrollable section. This left some whitespace at the end of the table due to 100vh being larger than the table. But the following style fixed the issue.
virtual-scroll .scrollable-content{ 	height: auto !important; }

Closing this as the suggestion seems to have a resolved the issue. Please re-open if you continue to have problems.

I got it working like this:

  <cdk-virtual-scroll-viewport itemSize="20" class="ps" perfectScrollbar style="height: 100%;">

        ID
        Item

        {{i}}
        {{item}}

  </cdk-virtual-scroll-viewport>

maybe you'll need overwrite  opacity .ps__rail-x and .ps__rail-y to 1. it's set 0 in @import '~perfect-scrollbar/css/perfect-scrollbar.css';.


HELLO IS THIS AVAILABLE YET?

https://aws.amazon.com/blogs/aws/amazon-ecs-service-discovery/

Thank


don't add no-op DeltaSetIndexMap when not needed

Fixes https://github.com/fonttools/fonttools/issues/2800

/cc @drott

Lgtm.


Run trac-github-update hook after updating repo

Git has no option to run a hook locally when 'git remote update' fetches
new commits. In order to be able to trigger custom actions on update
(for example commit mail notifications), this adds suppport for
a 'trac-github-update' hook. This hook will be called each time the
GitHub Webhook updates the repository, and receives the JSON payload as
sent by GitHub on standard input.

Go ahead.
@rjollos @neverpanic @raimue It's your project as much as mine now. I'm super happy that you took it, ran with it, and made it better. If I'm referenced anywhere as the author, please add your names as well (or just link to the contributors stats on GitHub instead). Thanks for your great work!

Thanks for the encouraging words :)

Since GitHubMixin is a component following these changes, and GitHubPostCommitHook, GitHubBrowser and GitHubGroupsProvider inherit from it, it will need to be enabled for any of the configurations described in the README.md. The issue came up on the trac-hacks mailing list. I'll update the documentation.


No performance gain on using WebGPU

Question
I want to use the model: https://huggingface.co/Xenova/clip-vit-large-patch14 with WebGPU for quick inference in the browser. I ran the WebGPU benchmark to observe the performance increase and indeed it showed a ~7x improvement in speed on my device.
But when I run the clip model linked above, there's barely any difference between performance with and without WebGPU.

Can you include the code you are running? You may need to update the dtype to one which produces better results.

I tried the following ways:
`
const processor = await AutoProcessor.from_pretrained('Xenova/clip-vit-large-patch14');
const vision_model = await CLIPVisionModelWithProjection.from_pretrained('Xenova/clip-vit-large-patch14', {
device: 'webgpu',
dtype: 'fp16',
});
const image = await RawImage.read(url);
const time_start = performance.now();
const image_inputs = await processor(image);
const { image_embeds }  = await vision_model(image_inputs);
`
This took 17371 ms with fp16 and 17353 ms with fp32.
Second method I tried was:
`
const vision_model = await pipeline('image-feature-extraction', 'Xenova/clip-vit-large-patch14', {
device: 'webgpu',
dtype: 'fp16',
});
const image_embeds = await vision_model(url);
`
At fp16 this took 17549 ms and at fp32 it took 16576 ms.

Hmm, strange. Your code looks right. 🤔
Could you try this demo: https://huggingface.co/spaces/Xenova/webgpu-clip? It should be real-time CLIP with WebGPU. You can also try a smaller CLIP model like https://huggingface.co/Xenova/clip-vit-base-patch32, maybe the large one has some issues with the ONNX export.
https://github.com/xenova/transformers.js/assets/26504141/75a4ab6f-41f2-4a00-9967-3cd7dcaa801e

Hi @xenova could it have something to do with the fact that I'm using the model in a browser-extension? Also, would it be possible for you to provide the code for the webgpu-clip demo?

could it have something to do with the fact that I'm using the model in a browser-extension?

Hmm, good question. Just to confirm, are you sure you've installed Transformers.js v3 from the dev branch with:
npm install xenova/transformers.js#v3

? You might still be using v2.

Also, would it be possible for you to provide the code for the webgpu-clip demo?

Sure - here's the source code: https://github.com/xenova/transformers.js/tree/v3/examples/webgpu-clip

Hmm, good question. Just to confirm, are you sure you've installed Transformers.js v3 from the dev branch with:

This is it! the models are running on the same speed as the demos now. Thanks for the help!


Update quickstart-create-connect-server-vnet.md (Typo "flexible serve…

…r"→"Flexible Server")
https://github.com/MicrosoftDocs/azure-databases-docs/blob/main/articles/mysql/flexible-server/quickstart-create-connect-server-vnet.md
#PingMSFTDocs

@SudheeshGH
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@SudheeshGH - I'll merge this PR based on your approval. If this article requires further changes, please open a separate pull request.

@SudheeshGH - related #10


[Dashboard] Seamlessly Display Real-Time Locations

Description
This enhancement focuses on integrating real-time location data seamlessly into the AutoEye dashboard, providing users with up-to-date insights into the whereabouts of vehicles or assets. By visualizing real-time locations directly within the dashboard, users can make informed decisions and track operations effectively.
Tasks

Develop back-end APIs or services to retrieve and deliver real-time location updates to the dashboard.
Implement front-end components to display real-time locations dynamically within the dashboard interface.

Dependencies

Integration with mapping services or APIs to accurately display location information within the dashboard.

Acceptance Criteria

Back-end APIs or services are implemented to fetch and deliver real-time location updates to the dashboard in a timely and efficient manner.
Front-end components effectively render real-time locations within the dashboard interface, providing a seamless user experience.
Real-time location data is displayed accurately and consistently, reflecting the current status of vehicles or assets.

Back-end APIs have been developed to efficiently retrieve and deliver real-time location updates to the dashboard. Additionally, front-end components have been implemented to dynamically display these real-time locations within the dashboard interface.


Implement human-readable serde for Witness

This is @dr-orlovsky's PR picked up at his permission in the discussion thread.
I went through the review comments and implemented everything except the perf optimisations. Also includes a patch at the front of the PR that adds a unit test that can be run to see the "before and after", not sure if we want it in, perhaps it should be removed before merge.
This PR implicitly fixes 942.
Fixes: #942

Changes in force push:

Use loop suggestion from @RCasatta to remove allocation

I suspect that serializaiton could also avoid the to_hex allocation -- but yes, let's go ahead and do that in another PR :)

@apoelstra It's not a clear win - if the serializer uses the default implementation we end up having slower code. I just posted to IRLO about this

Changes in force push:

Dropped patch that added the unit test displaying Witness
Modified commit 68577dfb Witness human-readable serde by doing

Added import for serde stuff to shorten types/lines
Removed use of unwrap_or('-'), used multiple different serde error types
Used into instead of as


Can't run project with RealmSwift in iOS simulator after building with Xcode 12 (after beta 3)

Goals
My goal is to run the app in simulator (preferably iOS 14 one) to be prepared for future iOS and Xcode updates.
Something's seem broken in the mapping of arm64 to x86_64 when new build system of Xcode 12 is used.
Expected Results
Application runs in simulator.
Actual Results
Since Xcode 12 beta 3 I can no longer build my project anymore. There are few scenarios:

When the app was first build with Xcode 11.6 and the build folder wasn't cleaned prior building with Xcode 12 beta 3 build segfaults compiling the classes with RealmSwift imports.
Example error: AddressGeorecord.swift:10:8: error: could not find module 'RealmSwift' for target 'arm64-apple-ios-simulator'; found: x86_64-apple-ios-simulator, x86_64 import RealmSwift (all the long stack dump is omitted for brevity).
When the build folder is cleaned and derived data removed Xcode 12 beta 3 won't build at all showing No such module 'RealmSwift' on imports in classes importing Realm.
When the build folder is cleaned and derived data removed beforehand and then RealmSwift pod scheme built for any of iOS 14 simulators trying to build and run the app afterwards fails with segfault and the same error could not find module 'RealmSwift' for target 'arm64-apple-ios-simulator'.
Excluding x86_64 in Pods project Build settings -> Excluded Architectures and/or explicitly setting armv7 armv7s arm64 arm64e i386 in Pods project Build settings -> Architectures helps to build the project. But it can't be run in simulator with the following message: [Project name] architectures (arm64) include none that iPhone SE (1st generation) can execute (Intel 64-bit). (For whatever simulator is selected).

Steps for others to Reproduce
See 'Actual results' section above.
Code Sample
None.
Version of Realm and Tooling
ProductName:	Mac OS X
ProductVersion:	10.15.5
BuildVersion:	19F101

/Applications/Xcode-beta.app/Contents/Developer
Xcode 12.0
Build version 12A8169g

/Users/illabo/.rbenv/shims/pod
1.9.3
Realm (5.3.3)
RealmSwift (5.3.3)

/bin/bash
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin19)

carthage not found
(not in use here)

/usr/local/bin/git
git version 2.24.1

Confirmed happening on Xcode 12 b4 as well, even after a fresh install of Xcode and the CL tools, cleaning derived data, and even on a new project with just the Realm and RealmSwift pods.

We do not support the new arm64 simulators yet as they break the old "universal" simulator/device libraries hack. Currently you'll need to exclude arm64 from the simulator architectures:

Build Active Architecture Only: Yes should also sidestep this unless you're running on an ARM DTK, as that's the only place the arm64 simulator is actually used.

@tgoyne Sorry to say, but it isn't a solution. Whenever the project is attempted to be built for debug in simulator (main project and Pods targets architectures are set to ARCHS_STANDARD) excluding arm64 and i386 architectures it can't be linked as there aren't anything actually built:

None of the architectures in ARCHS (arm64, i386, x86_64) are valid. Consider setting ARCHS to $(ARCHS_STANDARD) or updating it to include at least one value from VALID_ARCHS (armv7, arm64) which is not in EXCLUDED_ARCHS (arm64, i386).

And I'm trying with no success to run the project on old simulators (10.3.1—13.6) not only 14.0, Xcode 12 seems treat them as arm64 simulators too for some reason. E.g. it is an error I'm getting trying to run on iOS 12.1 (when arm64 isn't excluded): could not find module 'RealmSwift' for target 'arm64-apple-ios-simulator'. Please check the last two bullets in "Actual Results" section in original issue. This mutually exceptional messages (saying a simulator could run x86 binary but Xcode can't find arm64 module) are present only when the project imports Realm. It is the reason to file this issue and not just wait for release of production ready Xcode 12.
Build Active Architecture Only: Yes not helping also on my Intel Mac whether I exclude arm64 from build archs or not.
I can understand this happens because of Apple tweaked the build system, but it is a coming reality to deal with. Unfortunately it seems the time for new 'hack' to force-feed simulator with the correct binary and resolve this contradiction.
For now I can perfectly fall back to building with Xcode 11, but I have some worries regarding upcoming releases.

Yes we're seeing a very similar issue. We're not attempting to use RealmSwift at all, just realm-cocoa. Tried excluding arm64 to no avail:

The error is:
ld: in /.../Pods/Realm/core/librealmcore-ios.a(bptree.o), building for iOS Simulator, but linking in object file built for iOS, for architecture arm64

Builds properly on a real device, just not on the simulator. Laptop has processor 2.9 GHz 6-Core Intel Core i9 running Catalina 10.15.6 (19G73)

Not sure if this is happening for everyone, but for us this is becoming an increasingly time-sensitive situation —  iOS 14 is coming out very soon, and we're not able to compile our app on simulators at all right now due to this issue.
Is the realm team looking into this issue or aware of what may be causing this?

When using CocoaPods you will also need to set EXCLUDED_ARCHS on the Pods project.
Supporting the arm simulators requires cocoapods 1.10, which currently is in beta. If they don't make a non-beta release before Xcode 12 leaves beta then I guess we'll just bump the minimum req to that anyway, but we'd prefer not to require everyone working on things being released now to use a beta version.

OK thanks for the update @tgoyne very helpful

As Xcode 12 is GM seed now and release is expected in hours perspective it seem the right time to revive the topic.
ProductName:	Mac OS X
ProductVersion:	10.15.6
BuildVersion:	19G2021

/Applications/Xcode.app/Contents/Developer
Xcode 12.0
Build version 12A7209

/Users/illabo/.rbenv/shims/pod
1.10.0.rc.1
Realm (5.4.0)
RealmSwift (5.4.0)

/bin/bash
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin19)

carthage not found
(not in use here)

/usr/local/bin/git
git version 2.28.0

Cocoapods 1.10  (at least rc 1) doesn't remedy this issue no matter Pods Project Base SDK and/or Supported Platform is set to macOS or iOS, Build Active Architectures Only is set to Yes for debug or to No, i386 is in Excluded Architectures or it isn't.
What steps one should take to try mitigate such an issue?
BTW: tried building older project with Realm 3.17.3 and it runs in iOS 14 simulator without any problem.

I am on the Xcode 12 GM now and non of the above is working anymore.

When using CocoaPods 1.10.rc.1, try pointing at the lm/pod-xcframework as that's the branch which relies on 1.10 changes.

Xcode 12 is not beta anymore, its oficial release and the problem persists. its not compiling anymore.

@jbarros35 what package manager & version of Realm are you using?

I was facing a similar issue on RealmSwift. Have tried Updating the project to the recommended settings and seems the issue is resolved.
Also have tested in older Xcode and the project is working fine. Seems like a possible solution for now.

Here is how I get rid of the problem, I bet this can not be termed as long term solution but interesting thing is :
Xcode 11 had Valid Architecture(VALID_ARCHS) while Xcode 12 has Excluded Architectures (EXCLUDED_ARCHS).
So if you open the project in xcode12 then if you check in build settings you will found that VALID_ARCHS is now moved to User-Defined.
So quick solution will be simply delete the entry of VALID_ARCHS from User-Defined. And this time it should work.
I am also looking for more permanent kind of solution as this solution will break everytime we perform pod install or pod update.
So somewhere I found this post pod installation change but I have not tried that yet.
post_install do |installer|
    installer.pods_project.targets.each do |target|
          target.build_configurations.each do |config|
                config.build_settings['EXCLUDED_ARCHS'] = 'arm64'
          end
    end
end

Please try and let me know if it helps

@umang-simform The Podfile snippet seems to help in our case.

Here is how I got rid of the problem, I bet this can not be termed as long term solution but the interesting thing is :
Xcode 11 had Valid Architecture(VALID_ARCHS) while Xcode 12 has Excluded Architectures (EXCLUDED_ARCHS).
So if you open the project in xcode12 then if you check-in build settings you will found that VALID_ARCHS is now moved to User-Defined.
So a quick solution will simply delete the entry of VALID_ARCHS from User-Defined. And this time it should work. I am also looking for a more permanent kind of solution as this solution will break every time we perform pod install or pod updates.
So somewhere I found this post pod installation change but I have not tried that yet.
ref: https://developer.apple.com/forums/thread/656509
post_install do |installer|
    installer.pods_project.targets.each do |target|
          target.build_configurations.each do |config|
                config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'
          end
    end
end

Please try and let me know if it helps

I tried this too and it worked great

Thanks @umang-simform, this!

So a quick solution will simply delete the entry of VALID_ARCHS from User-Defined. And this time it should work.
I'd want to say sorry to Realm team and @tgoyne for my complaints. I assumed VALID_ARCHS is just ignored by Xcode 12 as deprecated and affects nothing. Was wrong.
Perhaps there should be some kind of compile time warning or a notice in documentation (sorry if I overlooked that) for those who maintains pre XC12 projects?

Here is how I got rid of the problem, I bet this can not be termed as long term solution but the interesting thing is :
Xcode 11 had Valid Architecture(VALID_ARCHS) while Xcode 12 has Excluded Architectures (EXCLUDED_ARCHS).
So if you open the project in xcode12 then if you check-in build settings you will found that VALID_ARCHS is now moved to User-Defined.
So a quick solution will simply delete the entry of VALID_ARCHS from User-Defined. And this time it should work. I am also looking for a more permanent kind of solution as this solution will break every time we perform pod install or pod updates.
So somewhere I found this post pod installation change but I have not tried that yet.
ref: https://developer.apple.com/forums/thread/656509
post_install do |installer|
    installer.pods_project.targets.each do |target|
          target.build_configurations.each do |config|
                config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'
          end
    end
end

Please try and let me know if it helps

I tried this too and it worked great

Are you guys able to deploy to both simulators and real devices with these settings?

Here is how I got rid of the problem, I bet this can not be termed as long term solution but the interesting thing is :
Xcode 11 had Valid Architecture(VALID_ARCHS) while Xcode 12 has Excluded Architectures (EXCLUDED_ARCHS).
So if you open the project in xcode12 then if you check-in build settings you will found that VALID_ARCHS is now moved to User-Defined.
So a quick solution will simply delete the entry of VALID_ARCHS from User-Defined. And this time it should work. I am also looking for a more permanent kind of solution as this solution will break every time we perform pod install or pod updates.
So somewhere I found this post pod installation change but I have not tried that yet.
ref: https://developer.apple.com/forums/thread/656509
post_install do |installer|
    installer.pods_project.targets.each do |target|
          target.build_configurations.each do |config|
                config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'
          end
    end
end

Please try and let me know if it helps

In my case applying this as is broke several other Pods, but was otherwise helpful when just restricted to Realm Pods:
post_install do |installer|
      installer.pods_project.targets.each do |target|
            if target.name.include?('Realm')
                target.build_configurations.each do |config|
                      config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'
                end
            end
      end
end

In my case excluding arm64 brakes other pods.
Fog example:
post_install do |installer|       installer.pods_project.targets.each do |target|             if target.name.include?('Realm')                 target.build_configurations.each do |config|                       config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'                 end             end       end end
gives me the following error message:
Showing All Messages ....my_path.../Pods/RxRealm/Pod/Classes/RealmObserver.swift:9:8: Could not find module 'RealmSwift' for target 'arm64-apple-ios-simulator'; found: x86_64-apple-ios-simulator, x86_64
Any suggestions on how to exclude arm64 correctly to keep work other pods?

@codemeister64 Try maybe not excluding arm64 for RxRealm pod?

I already tried it. The following code
installer.pods_project.targets.each do |target|       if target.name != 'RxRealm' && target.name.include?('Realm')           target.build_configurations.each do |config|           config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'         end       end     end
excludes arm64 arch only for Realm and RealmSwift pods, but there is still the same error for RxRealm. Also, I tried to clean DerivedData

BUILD Settings -> VALID_ARCHS. add "X86_64" on your project (Prolly you might have arm* series. put it with them to work)

Hi @codemeister64 !
Did you find any solution ? i have the same issue

Anyone find any solution? I have the same issue

Hi @danielrobleM, yes I`ve resolved the issue.
In my case the following steps works:

add following code to post_install section of your podfile:

post_install do |installer|
installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
        config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'
      end
    end
end

open your project settings and manually for each of your targets set Excluded Architectures setting (in my case I have two targets - main and push notification extension). Check this screenshot

Anyone has this issue right now?
Every time I tried 'pod lib lint' and this is always the error
~/Pods/Realm/core/librealmcore-ios.a(bptree.o), building for iOS Simulator, but linking in object file built for iOS, for architecture arm64     clang: error: linker command failed with exit code 1 (use -v to see invocation)
The following build commands failed:     	Ld /Users/~/Library/Developer/Xcode/DerivedData/App-bcahkoasabrxnhbthdoimxoxletm/Build/Intermediates.noindex/Pods.build/Release-iphonesimulator/Realm.build/Objects-normal/arm64/Binary/Realm normal arm64     (1 failure)

I've added exclusion for arm64 on all my targets
I've set 'ONLY_ACTIVE_ARCH' to yes to both Debug and Release on all my targets
I've added both exclusion for arm64 and ONLY_ACTIVE_ARCH in podfile in post install
I've added the following code to my podspec
s.user_target_xcconfig = { 'EXCLUDED_ARCHS[sdk=iphonesimulator*]' => 'arm64' }
s.user_target_xcconfig = { 'ONLY_ACTIVE_ARCH' => 'YES' }
s.pod_target_xcconfig = { 'EXCLUDED_ARCHS[sdk=iphonesimulator*]' => 'arm64' }
s.pod_target_xcconfig = { 'ONLY_ACTIVE_ARCH' => 'YES' }
I've checked and there is no VALID_ARCH setting in my build setting

And yet I still cannot pass pod lib lint
Xcode: 12.2
Pod: 1.10.0

Hello, I have similar problems.
When building our project I get the error:
could not find module 'RealmSwift' for target 'arm64-apple-ios-simulator'; found: i386, x86_64-apple-ios-simulator, x86_64, i386-apple-ios-simulator
This happens when I'm building on the CI (azure). I've tried all solutions from the previous comments but no luck.
Now I'm actually adding the Realm and RealmSwift sdks as XCFrameworks to the project, instead of with Cocoapods. But the error remains the same.
Xcode 12.2
latest release of Realm.
Any suggestions are much appreciated

I've encountered the same issue in #6968. The Realm project excludes the arm64 architecture when building for the iOS simulator. Please change the following line in your Realm project
https://github.com/realm/realm-cocoa/blob/af4b201bb955736f250f5af1c1b6bc335a43c385/Configuration/Base.xcconfig#L65
to REALM_ARM_ARCHS_1200 = ; and build again with sh build.sh xcframework ios

Hi Felixll,
in your case you are building on a simulator on a M1 machine right? So you need the arm64 architecture.
It's strange that I'm having the same error while I'm not building on simulator running on an M1 machine.
So in that case removing the line:
REALM_ARM_ARCHS_1200 = arm64 arm64e;
would not help right?
Or did I misinterpret your suggestions?

Yes, I'm building for the arm64 simulator on an M1 Mac.
Your error message
could not find module 'RealmSwift' for target 'arm64-apple-ios-simulator'
suggests that your machine tries to build this architecture as well and cannot find the correct slice for RealmSwift. Of course, this could also be due to a configuration problem in your project.
My approach allows you to build a xcframework with the full set of architectures and therefore fix this error. I haven't tried it on an Intel Mac yet, but I see no reason why it shouldn't work there as well. I can send you the precompiled xcframework files if you want to give it a try.
I'm not Realm developer and have limited experience with this project. There may be better solutions to this problem, but this one has worked for me so far.

The latest Realm version 10.4.0 has fixed the arm64-apple-ios-simulator compiler issue for me. My workaround in #6968 should no longer be necessary.

I have an MacBook Air M1, What  do you suggest if I include Realm using Swift Package Manager?

For SwiftPM, use Realm version 10.5.0.


Implement PixieDust

PixieDust seems to be a very good library to display table and charts with some interesting tools.
https://github.com/ibm-watson-data-lab/pixiedust

at this moment pixiedust doesn't match to the projetct expectative.

pixiedust require java, so it should be avoided ...


Error when hosting a new session

Temporary workaround commit:
0f71fcf8f87e0ac2b1933a37ef1b6455ed55e965
Description:
When no save file is available, pressing the "Host Game" button was crashing the game.
It seems like the cause for this is the following if-statement:
	-- add some buildings before adding fuel
	if LANDERS[1] == nil then

	else
		addBuildings(LANDERS[1].x + 6000)	-- an arbitrary 'draw ahead' distance
		-- add fuel bases after the buildings so they can draw layered if need be
		addFuelBases(LANDERS[1].x + 6000)	-- an arbitrary 'draw ahead' distance
	end

that has been introduced with #234. I posted some details in a comment a couple hours ago.
What do we want to do about this? I think if we keep it like this we'll run into issues again at some point. Imo we need to encapsulate the lander object to be independent from other modules.

Fixed in PR #245


OPNVpn Stale PID fix

This patch checks that the instnace of OpenVPN that should have shut down has shut down, if not it forces it down.
It then checks to see if the PID is still there and deletes it if required,

I've not had ant feedback on this from my tester who reports he has the issue, seems he has gone AWOL!
However, lets put the patch out there and see what gives.

ok to test, needs some work if this fixes the issue (psr/style cleanup)

Hi,
Thanks, I tried it, unfortunatly I got an error on the Webgui after installing the patch
[13-Feb-2019 18:43:28 Europe/Vienna] PHP Parse error:  syntax error, unexpected ';' in /usr/local/etc/inc/plugins.inc.d/openvpn.inc on line 1010
 [13-Feb-2019 18:43:50 Europe/Vienna] PHP Parse error:  syntax error, unexpected ';' in /usr/local/etc/inc/plugins.inc.d/openvpn.inc on line 1010
Crash report has been sent with link to this issue
br

Sorry... my typo.. Updated try b2cc0ae

Same, no change. Reboot required?
Feb 13 20:20:14 | openvpn[44247]: Exiting due to fatal error
Feb 13 20:20:14 | openvpn[44247]: Cannot open TUN/TAP dev /dev/tun1: Device busy (errno=16)
Feb 13 20:20:14 | openvpn[44247]: TUN/TAP device ovpns1 exists previously, keep at program end

Yes, reboot and then try it.

Hi,
patched and reboot, issue is partially solved.
I've two OpenVPN Instances running, one TCP one UDP. The first (TCP) is ok now, but the second suffers still the same issue.
Feb 14 18:11:52 | openvpn[14952]: Exiting due to fatal error
Feb 14 18:11:52 | openvpn[14952]: Cannot open TUN/TAP dev /dev/tun3: Device busy (errno=16)
Feb 14 18:11:52 | openvpn[14952]: TUN/TAP device ovpns3 exists previously, keep at program end
br

I've added https://github.com/opnsense/core/commit/f10b710a58 -- the SIGKILL is equal to the first SIGTERM and OpenVPN says SIGINT or SIGTERM should be used:
https://openvpn.net/community-resources/controlling-a-running-openvpn-process/
If the SIGKILL succeeds it means there is a stray process being created after SIGTERM, so someone else is already restarting OpenVPN.


Restore entry-level tutorials for IoT

This is a duplicate issue. Presented here to show the scale if the problem.
My goal was to explore the potential of managing devices through Azure IoT Hub.
I am particularly attracted because the barrier to entry is miniscule; all/most tutorials include instructions for Raspberry Pi - a ubiquitous device.
Unfortunately, it is no longer possible to use the tutorials:

#104979 Cannot use the current version of the Raspberry OS because Device Updates is too old.
#105041 Cannot use the previous version of the OS because the IoT agent cannot be installed.
#105047 Cannot use the premade image because it is too old for the current Raspberry Pi models.

Please consider refreshing the documentation to work with a current Raspberry Pi model (suggestion: RPi 4B 4GB).

Since this issue has served its purpose, and tied the other issues together, I am closing this issue.

@LaudixGit Thanks for sharing the feedback about the docs. We will look into it and update as earliest.


Hardcoded path length in landing_zone_move flow

While working on #1882 and #1883 I noticed that we use a hardcoded value to split iRODS collections to subpaths in the landing_zone_move flow: '/'.join(p.split('/')[10:])
This works if SODAR data is placed directly under /yourZone/, but if IRODS_ROOT_PATH is set it will fail horribly. This is a simple case of a sloppy developer (that's me).

Fixed.


chore(main): release 1.6.0

:robot: I have created a release beep boop
1.6.0 (2024-09-12)
Features

update readme (a416bd6)

Bug Fixes

add async msg for async calls without original msg (fc19528)
apex, aura creation command failure (c7e79f3)
cmd wrong name (72d62dc)
create lwc (32cdb3b)
keys not enabled in sf project sub folder (082a740)
keys not enabled in sf project sub folder (1b27dee)
metadata pull command ill-formatted (ef04a37)
remove debug_print (6aa7809)
show once warning when md file is not found locally (291881b)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.6.0
:sunflower:


[IMPROVEMENT] UI show error when backup target is empty for system backup

Is your improvement request related to a feature? Please describe (👍 if you like this request)
UI system backup page doesn't show any error when the backup target is invalid.
Describe the solution you'd like
See https://github.com/longhorn/longhorn/issues/5055#issuecomment-1350182125
Describe alternatives you've considered
Let the validator return error from the backend when creating a system backup.
Additional context
None

/cc @smallteeths

The ui does not need to be modified and will directly display the error message returned by the back-end.
 @c3y1huang

The ui does not need to be modified and will directly display the error message returned by the back-end.

/cc @longhorn/qa

@khushboo-rancher let's check this together with https://github.com/longhorn/longhorn/issues/5056.
cc @longhorn/qa

Validation - Pass
Verified on v1.4.x-head


Add notebook for using qualification user tools in Databricks

Fixes https://github.com/NVIDIA/spark-rapids-tools/issues/571. This PR adds a new example notebook for using qualification user tools in Databricks
Changes:

Added a new dropdown field csp to choose between aws and azure (defaults to aws).
Install spark-rapids-user-tools
Run qualification on user tools

Output:

Signed-off-by: Partho Sarthi<EMAIL_ADDRESS>

Hi @parthosa , thanks for the contributing, could you help re-target the pr to branch-23.12?

Hi @parthosa , seems the branch is still main.
And is the notebook specific to some Databricks runtime version?
I hit below error while running on 10.4ML:

I hit below error while running on 10.4ML:

The error will not show up if I run the cell for the second time. Another issue is FileNotFoundError, I checked the folder and confirmed there are output files in the dbfs, any idea?

Thanks @nvliyuan. I have updated the base branch to branch-23.12 and fixed the issues related to output folder: The notebook now creates a separate virtual environment and installs spark-rapids-user-tools package in it. See description for updated UI.

LGTM


code sharing with NCDatasets?

@tcarion  Thank you for sharing this nice package! I am developping with NCDatasets.jl packages and it seems that we have similar goals :-)
Would it be useful that I factor out some code of the of NCDatatasets.jl in a separate package (maybe AbstractDatasets.jl in JuliaGeo) to share common functionalities? "AbstractDatasets.jl" would be a pure julia package (without dependency to NetCDF_jll) with some abstract type definition, so that a use can more easily write code that seamless work with both packages.
Maybe also the multi-file support could be part of this package?
The idea is that GRIBDatasets.jl and NCDatasets.jl would have this package as a dependency and that our main types (like dataset) would derive from it.

Hi! That's a very good idea, this could simplify the integration of netcdf and GRIB files into Rasters.jl (GRIB support is ongoing, see https://github.com/rafaqz/Rasters.jl/pull/283), which I think is a good point. I tried to follow the structure of NCDatasets.jl for developing GRIBDatasets.jl, so it shouldn't be too difficult to make them work together!

Thank you so much for your positive feedback! This is great!
Sometimes, I need to know all the dimensions defined in a datasets, and I currently use ds.dim for this.
Some small difference, that I am seeing is that GRIDDatasets uses the pluralized form ds.dims:
https://github.com/JuliaGeo/GRIBDatasets.jl/blob/main/src/dataset.jl#L69
Even if there are several typically several dimensions, I uses the singular form in  (like ds.attrib). Would you welcome a PR changer ds.dims -> ds.dim or should be rather have a function like some_function(ds) which would the underlying ds.dim(s) ?

You're right, it's better to be consistent and change this to ds.dim. I can try to prepare the PR when I have a little bit of time!

Another small difference is that ds.dims["dim_name"] returns a GRIBDatasets.Dimension while in NCDatasets case it is just a number. That might be more difficult to change has you have the types Vertical, Horizontal, ....

By the way, I can make such PR as well :-)

I actually had in mind to simplify the implementation of dimensions in GRIBDatasets, I think I made it pointlessly complicated. There's the new-dims-impl branch where I started to work on it, but I got deviated from it because of more urgent other projects. I'll try to get back to it, keeping the NCDasatets logic in sight to make it more consistent!

Meanwhile working more in-depth on the reimplementation of Dimensions, I made the few changes mentioned above and open the pull request

This is great, thank you so much. I just tested the PR, and I did not see any difference relative to the use of the dim.

Yes that sounds great! Should this package be created directly on JuliaGeo?

Yes, I think having this package on JuliaGeo would be good so that it is easier for you to make changes if necessary.

Here is it:
https://github.com/JuliaGeo/AbstractDatasets.jl
If this is ok for you, I go ahead an try to register this package so that we can depend on it.

Awesome, thanks! I'll keep implementing the interface once it's registered (I think I'll push new stuff to #8 )

In the end, I had to choose a different name of this package:
https://github.com/JuliaGeo/CommonDataModel.jl
As a proof concept, I used your approach (using a non-netcdf data format, accessing it with a the NetCDF/CommonDataModel API) for GeoTIFFs. It helped a lot to find out which functions needs to be factor-out from NCDatasets:
https://github.com/Alexander-Barth/TIFFDatasets.jl
TIFFDatasets.jl uses now the show methods in CommonDataModel.jl (previously from NCDatasets) and query various metadata. Obviously, you can still use your current show methods. But you can delegate this to CommonDataModel.jl if you want :-)

That's great, thanks! I see in the tests of CommonDataModel that you can easily convert a GRIB file to NetCDF, that's pretty amazing! Probably not as efficient as using the dedicated grib_convert binary, but being able to do it in Julia is very nice.
I started implementing the interface for GRIBDatasets, but I'm facing a little issue (#8 )

Yes, not sure if it would be as efficient as grib_convert (could be :-)) but I think it is a good test to see if the general approach works and if all information is accessible via the CommonDataModel API.

I guess this is solved by https://github.com/JuliaGeo/GRIBDatasets.jl/pull/8. But I propose to close this when we are sure that the conversion from GRIB to netCDF works :)


Hash Table: Add First Missing Positive in C++

Given an unsorted integer array nums, return the smallest missing positive integer.
You must implement an algorithm that runs in O(n) time and uses O(1) auxiliary space

Can I solve this in c++ and go

can i solve this?


Slick Moves: Set up tBTC config by chain id

Rather than using isMainnet, provide a config indexed by chain id, and
use the already-looked-up chain id to determine which config to use at
load time. Config also now includes the local network.
Spinoff of keep-network/local-setup#40, though it doesn't block that PR.
In draft because I haven't had a chance to give it a full test yet, but if the
reviewer tests it satisfactorily I think we can land it. Whoever gets to it
first can review :wink:

Looks good but the linter isn't happy:
/home/circleci/project/src/wrappers/web3.js
  3:16  error  'EthereumHelpers' is defined but never used  no-unused-vars
  3:33  error  'BitcoinHelpers' is defined but never used   no-unused-vars

🤔 must have missed setting up pre-commit locally. Will fix!

Oh yeah, I missed setting up pre-commit because I was working in the local-setup checkouts :grimacing: Might be useful to make initialize-repositories also set up pre-commit for completeness 🤔 Anyway, later haha.

This should be ready to go.

I approved but don't have write permissions to merge.


getStats test fails with firefox (all)

CC @nils-ohlmeier

You mean the failed web platform test?

i took it from the excel sheet emmanuel shared with me.
On Sun, May 27, 2018 at 9:40 PM, Nam<EMAIL_ADDRESS>wrote:

You mean the failed web platform test?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/webrtc/KITE/issues/55#issuecomment-392417232, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AagY7SLtLLD4vcdbNfBUy-6meosULqEkks5t23-lgaJpZM4UPCT-
.

getStats works well on Firefox with KITE 2.0


variables doesn't work

I read all documentation and wrote this code:
{
  followAuthor: 'Author %(author) added your subscription list',
}

Language.translate('followAuthor', { author: 'test' });
```
and get:
```
SyntaxError: [sprintf] unexpected placeholder
```

@anorudes See https://github.com/martinandert/counterpart/issues/11

Thanks. but it's really strange)


⚠ Bofrost.de has degraded performance

In 4b62dc2, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 994 ms

Resolved: Bofrost.de performance has improved in 8f86a61 after 48 minutes.


Don't classify bridging casts as WillSucceed if the object-to-value cast can fail.

When casting from an object type to a bridged Swift value type, classifyDynamicCast would use the cast classification for the target type's bridged object type, which would be trivially WillSucceed for thinks like NSNumber-to-Int or NSError-to-SomeError, even though the bridging itself could fail. Fixing this fixes SR-2920|rdar://problem/31404281.

@swift-ci Please test

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - c797bd843940d1036f451ad56fde8cc1f77665b9
Test requested by - @jckarter

@swift-ci Please test

@swift-ci Please test


ESM5/FESM5 imports are incorrect after updating to 3.0.0

Type of Issue
[ X] Bug Report
[ ] Feature Request

Description
When building Angular library using ng build some of the resulting imports in ESM5/FESM5 bundles are incorrect after updating from 3.0.0-rc.5 to 3.0.0. ESM2015/FESM2015 imports are fine.
How To Reproduce
For example, I have the following generated using version 3.0.0:
...
import { ApiServices, ApiServiceSupport } from '@triu/common/api';
...
import { ApiServices as ApiServices$1 } from '@triu/common/api/src/api-services';
...

var CoreAccountService = /** @class */ (function (_super) {
    __extends(CoreAccountService, _super);
    ...
    CoreAccountService.decorators = [
        { type: Injectable, args: [{
                    providedIn: 'root'
                },] },
    ];
    /** @nocollapse */
    CoreAccountService.ctorParameters = function () { return [
        { type: ApiServices },
        { type: LocalStorageService }
    ]; };
    CoreAccountService.ngInjectableDef = defineInjectable({ factory: function CoreAccountService_Factory() { return new CoreAccountService(inject(ApiServices$1), inject(LocalStorageService)); }, token: CoreAccountService, providedIn: "root" });
    return CoreAccountService;
}(ApiServiceSupport));

And the following generated using version 3.0.0-rc.5:
...
import { ApiServices, ApiServiceSupport } from '@triu/common/api';
...
var CoreAccountService = /** @class */ (function (_super) {
    __extends(CoreAccountService, _super);
    ...
    CoreAccountService.decorators = [
        { type: Injectable, args: [{
                    providedIn: 'root'
                },] },
    ];
    /** @nocollapse */
    CoreAccountService.ctorParameters = function () { return [
        { type: ApiServices },
        { type: LocalStorageService }
    ]; };
    CoreAccountService.ngInjectableDef = defineInjectable({ factory: function CoreAccountService_Factory() { return new CoreAccountService(inject(ApiServices), inject(LocalStorageService)); }, token: CoreAccountService, providedIn: "root" });
    return CoreAccountService;
}(ApiServiceSupport));

Notice the second import in 3.0.0 version and how it is used in the generated service.
Also, the issues arises when I build an Angular app that references the generated libraries in tsconfig.json's 'paths' attribute:
{
  "compileOnSave": false,
  "compilerOptions": {
    "baseUrl": "./",
    "outDir": "./dist/out-tsc",
    "sourceMap": true,
    "declaration": false,
    "moduleResolution": "node",
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "allowUnreachableCode": false,
    "noFallthroughCasesInSwitch": true,
    "noImplicitAny": true,
    "noImplicitReturns": true,
    "noImplicitThis": true,
    "noUnusedParameters": true,
    "noUnusedLocals": true,
    "skipLibCheck": true,
    "strictFunctionTypes": true,
    "strictNullChecks": false,
    "target": "es5",
    "typeRoots": [
      "node_modules/@types",
      "@custom_types"
    ],
    "lib": [
      "es2017",
      "dom"
    ],
    "paths": {
      ...
      "@triu/ng-cms-core-api-service": [
        "dist/@triu/ng-cms-core-api-service"
      ]
      ...
    }
  }
}

The error is something like this:
ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve '@triu/common/api/src/api-services' in '[project_directory]/dist/@triu/ng-cms-core-api-service/fesm5'

Version Information
$ node_modules/.bin/ng-packagr --version
ng-packagr:            3.0.0
@angular/compiler:     6.0.3
rollup:                0.59.4
tsickle:               0.29.0
typescript:            2.7.2

Do you think you can provide an reproduction?

@alan-agius4 Unfortunately, the project I'm working on uses a bunch of private npm libraries and quite large. Once I have some time I'll try to create a repo, but I can't promise when this is going to happen. Meanwhile, we can see if anyone else hits the same issue. Worst case we can switch target in compileOptions to es2015 for now. Thank you for your support.

Changing the target shouldn’t have any effect.  As the compilation target is set internally.

Ah that version, I though the target version in the lib tsconfig.

I tried to replicate this, with no luck

Let me add some source code extracts, may be it'll help understand the issue better.
This is the class that was used to generate the code from above:
...
import {Injectable} from '@angular/core';
import {ApiServices, ApiServiceSupport} from '@triu/common/api';
...

// @dynamic
@Injectable({
  providedIn: 'root'
})
export class CoreAccountService extends ApiServiceSupport {
  ...
  constructor(services: ApiServices,
              private localStorageService: LocalStorageService) {
    super(services, '/[some_endpoint_url]');
  }
  ...

Now, this class extends ApiServiceSupport class from  @triu/common/api that is installed as npm dependency.
The public_api.d.ts in node_modules/@triu/common/api has something like this:
/**
 * @module
 * @description
 * Entry point for all public APIs of this package.
 */
...
export { ApiServices } from './src/api-services';
export * from './src/api-service-support';
...

<EMAIL_ADDRESS>contains the following:
import { HttpClient } from '@angular/common/http';
import { Injector } from '@angular/core';
import { Logger } from '@triu/common/logger';
export declare class ApiServices {
    private injector;
    private _httpClient;
    private _logger;
    constructor(injector: Injector);
    getBaseUrl(): string;
    isApiUrl(url: string): boolean;
    isPublicApiUrl(url: string): boolean;
    readonly httpClient: HttpClient;
    readonly logger: Logger;
}

Finally<EMAIL_ADDRESS>for the parent class has the following:
import { HttpClient, HttpHeaders, HttpParams } from '@angular/common/http';
import { Logger } from '@triu/common/logger';
import { ApiServices } from './api-services';

export declare abstract class ApiServiceSupport {
    protected services: ApiServices;
    protected endpointPath: string;
    protected httpClient: HttpClient;
    protected logger: Logger;
    constructor(services: ApiServices, endpointPath: string);
    getApiPath(): string;
   ...
}

Here ApiServices are exported using a relative path: import { ApiServices } from './api-services'.  I think for some reason this is the cause of the duplicate import in the generated code from above. But, I'm not sure why it works with ng-packagr 3.0.0-rc.5 and not with 3.0.0

Without a reproduction, this will be hard to track down.
And you mentioned that the duplicate import is happing both in FESM5 and ESM5 correct, not just the FESM file?

Yes, for ESM imports look a little bit different, but there is a duplicate still:
import { Injectable } from '@angular/core';
import { ApiServices, ApiServiceSupport } from '@triu/common/api';
...
import * as i0 from "@angular/core";
import * as i1 from "@triu/common/api/src/api-services";
...

this tranformation is quite strange
import * as i0 from "@angular/core";
import * as i1 from "@triu/common/api/src/api-services";

As the output should be something like
/**
 * @fileoverview added by tsickle
 * @suppress {checkTypes} checked by tsc
 */
import { Injectable } from '@angular/core';
import { ApiServices, ApiServiceSupport } from '@triu/common/api';

Also, I understand that there is a lot of things involved in the building process. So, we can wait until someone else hits the same issue and can reproduce it in a repo if necessary.

Let me add the parent tsconfig.lib.json we use for the libraries:
{
  "compilerOptions": {
    "declaration": true,
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,
    "allowUnreachableCode": false,
    "noFallthroughCasesInSwitch": true,
    "noImplicitAny": true,
    "noImplicitReturns": true,
    "noUnusedParameters": true,
    "noUnusedLocals": true,
    "skipLibCheck": true,
    "strictNullChecks": true,
    "stripInternal": true,
    "sourceMap": true,
    "inlineSources": true,
    "importHelpers": true,
    "pretty": true,
    "moduleResolution": "node",
    "module": "es2015",
    "target": "es2015",
    // don't auto-discover @types/node
    "types": [],
    "lib": [
      "es2017",
      "dom"
    ]
  },
  "angularCompilerOptions": {
    "annotateForClosureCompiler": true,
    "fullTemplateTypeCheck": true,
    "skipTemplateCodegen": true,
    "strictMetadataEmit": true,
    "strictInjectionParameters": true,
    "flatModuleId": "AUTOGENERATED",
    "flatModuleOutFile": "AUTOGENERATED"
  },
  "exclude": [
    "src/test.ts",
    "**/*.spec.ts"
  ]
}

And this is the one for the library itself:
{
  "extends": "../../../tsconfig.lib.json",
  "compilerOptions": {
    "baseUrl": "",
    "paths": {
      ...
    }
  }
}

Not sure if it's the same issue, but I was having the same error message with my Angular 6 private repo.
For me it was because I had cd'd into /projects/mylib and done npm installing for the lib in the package.json there instead of the project root one, which created a separate node_modules folder that isn't found by the files in the /dist folder.

@Judgeja, I think it is not the same case here. I'm building libraries from the root project of the folder and I don't use npm install/link - instead I have dependencies specified in the "paths" option of app's tsconfig.json.

@alan-agius4 Ok, I finally was able to figure out the issue with our setup. We have a custom tsconfig.lib.json in the root folder of the project that all our library tsconfig.lib.json files extend from. But, according to this issue https://github.com/angular/angular-cli/issues/8336 "angularCompilerOptions" section of the config is not extended. So, we had to copy "angularCompilerOptions" to all of our library  tsconfig.lib.json files and that fixed ESM5/FESM5 module generation.
Thank you all for the help.


Settings > MQTT Settings (shows disabled when enabled)

Hello @omersiar
just found out while testing mqtt that the settings page is always showing "disabled" even when the mqtt is enabled (freshly restarted after applying settings) and publishing messages to my local mqtt server.

Done.


404 loading icon

This issue has been moved from a ticket on Developer Community.

I have the latest community edition of Visual Studio (16.3.10). I have two branches of code. the code was initialy generated from a ASP.NET MVC + Angular template. One branch has no problem loading the favicon.ico on debug (F5). The other branch gives out in text to the browser "Cannoy GET /". On refreshing the page with the Chrome debug tools active I see that the error is that favicon.ico violates "Content Security Policy". Between the two branches I cannot see any code that has anything to do with "Content Security Policy". Where do I look to see why one branch violates "Content Security Policy" and the other doesn't?

Original Comments
Visual Studio Feedback System on 12/3/2019, 02:06 AM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Visual Studio Feedback System on 12/3/2019, 07:08 PM:
Thank you for sharing your feedback! Our teams prioritize action on product issues with broad customer impact. See details at: https://docs.microsoft.com/en-us/visualstudio/ide/report-a-problem?view=vs-2017#faq. In case you need answers to common questions or need assisted support, be sure to use https://visualstudio.microsoft.com/vs/support/. We’ll keep you posted on any updates to this feedback.

Original Solutions
(no solutions)

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


fix: limit number of tweets in the list in the newsroom

Description

added tweetLimit in options props to limit the number of tweets displayed in TwitterTimelineEmbed Component.
Fixed Output:

Related issue(s)
Resolves #907

Hi @karancoder! Thank you for raising this PR 😄
Can we just remove the following classes from the outer container of the twitter iframe? It looks like some things have changed in the twitter view since we updated it, and it is causing some of the styling to look weird:
rounded-lg py-2 border border-gray-200 shadow-md
Removing the above classes should take away the extra space and extra styling that is now unneeded as shown below:

Hi @karancoder! Thank you for raising this PR 😄
Can we just remove the following classes from the outer container of the twitter iframe? It looks like some things have changed in the twitter view since we updated it, and it is causing some of the styling to look weird:
rounded-lg py-2 border border-gray-200 shadow-md
Removing the above classes should take away the extra space and extra styling that is now unneeded as shown below:

Hey @mcturco, since @jitulteron7 wanted to work this, kindly review his PR. Closing this PR to remove duplicates.


Feat (UI): Give the user the option to download the output of a function for a graph and an invocation.

UX -
The user should be able to navigate inside a graph and view the output of any function for an invocation by downloading the output file with a click of a button. This is a follow up of https://github.com/tensorlakeai/indexify/pull/1026

Closing wrt above PR


Uptake VC Media Types

As per https://github.com/w3c/vc-data-model/pull/1000
Support media types for different representations of credentials

consider use of https://transmute-industries.github.io/vc-jws/ in place of vc-jwt


Add installation link

Installation instructions make it easier for users to enjoy the software.

Thanks for your contribution!
I do not want to encourage users to use nix-env as it goes against the declarative nature of Nix.
An example using nix-shell would be useful though.

Definitely, this approach would be much better.
Sadly, I'm not sure how to do it so I think we should leave it hanging until someone with better experience picks it up :)


Accept HashMap<(), ()> as object

Hey i'm generating structures from the docker openapi spec and for some field they use HashMap<(), ()> for example:
volumes: HashMap<String, HashMap<(), ()>>

To define an empty object see for volumes as example.
But if i want to convert it back using utoipa i get the following error:
error[E0277]: the trait bound `AdditionalProperties<Schema>: From<Schema>` is not satisfied
    --> codegen/swagger/src/models.rs:6637:39
     |
6637 | #[cfg_attr(feature = "utoipa", derive(utoipa::ToSchema))]
     |                                       ^^^^^^^^^^^^^^^^ the trait `From<Schema>` is not implemented for `AdditionalProperties<Schema>`
     |
     = help: the following other types implement trait `From<T>`:
               <AdditionalProperties<Schema> as From<()>>
               <AdditionalProperties<Schema> as From<ObjectBuilder>>
               <AdditionalProperties<Schema> as From<utoipa::openapi::Ref>>
     = note: required for `Schema` to implement `Into<AdditionalProperties<Schema>>`
note: required by a bound in `ObjectBuilder::additional_properties`

I tried to do it, but i'm not familiar enough with macro

In docker OpenAPI spec the Volumes field is defined as follows:
Volumes:
  description: |
    An object mapping mount point paths inside the container to empty
    objects.
  type: "object"
  additionalProperties:
    type: "object"
    enum:
      - {}
    default: {}

But utoipa will render the volumes differently becuase of the unit type (). Unit type is by default rendered as null with serde and utoipa will create schemas for both types of the HashMap by the way of using additionalProperties resulting strictier interpretation of OpenAPI schema than what is defined in the docker OpenAPI schema.
{
    "properties": {
        "volumes": {
            "additionalProperties": {
                "additionalProperties": {
                    "type": "object",
                    "default": null,
                    "nullable": true,
                },
                "type": "object"
            },
            "type": "object"
        },
    },
    "required": [
        "volumes"
    ],
    "type": "object"
}

I created a PR #580 that fixes the support. However it does not render exactly 1 to 1 with the docker OpenAPI spec. Most fundamentally the additionalProperties will look different. after serialization and re-deserialization.

That's good enought! Thx for your great for on the library!


EnderIO combined with AE2 and ThermalExpansion

Issue Description:
EnderIO does not replace all Flour-Items from AppliedEnergistics2. The Pulverizer from ThermalExpansion normally produces AppliedEnergistics2 Flour, but in combination with EnderIO it just produces AppliedEnergistics2 Disabled Item. All other grinders (like SAG-Mill, Grindstone, etc.) produce the EnderIO dustWheat.
What happens:
ThermalExpansion's Pulverizer produces AppliedEnergistics Disabled Item.
What you expected to happen:
ThermalExpansion's Pulverizer should produce EnderIO's dustWheat.
Steps to reproduce:

Install AppliedEnergistics2, ThermalExpansion and EnderIO
Place a Pulverizer, power it and put Wheat in it.
AppliedEnergistics2 Disabled Item is produced
...

Affected Versions (Do not use "latest"):

EnderIO: 1.12.2-5.0.21
EnderCore: 1.12.2-0.5.18
Minecraft: 1.12.2
Forge: <IP_ADDRESS>55
AppliedenErgistics2: rv5-stable-11
ThermalExpansion: 1.12.2-<IP_ADDRESS>-universal

Your most recent log file where the issue was present:
https://pastebin.com/j70dXmY2

https://github.com/AppliedEnergistics/Applied-Energistics-2/issues/3437


Breaking build - Optimize leveldb block seeks to utilize the current iterator location

Hi,
I was trying to build LevelDB with the updates to master and noticed that my build is breaking.
On a quick look, I noticed that there was a commit made a couple of hours ago and that might be the reason for the breaking build.
Here is the link to that commit
Here's the failure log from my machine:
/home/odesai/leveldb/benchmarks/db_bench.cc:152:40: error: use of deleted function ‘std::atomic<long unsigned int>::atomic(const std::atomic<long unsigned int>&)’
  152 |   mutable std::atomic<size_t> count_ = 0;
      |                                        ^
In file included from /home/odesai/leveldb/benchmarks/db_bench.cc:7:
/usr/include/c++/9/atomic:824:7: note: declared here
  824 |       atomic(const atomic&) = delete;
      |       ^~~~~~
/usr/include/c++/9/atomic:828:17: note:   after user-defined conversion: ‘constexpr std::atomic<long unsigned int>::atomic(std::atomic<long unsigned int>::__integral_type)’
  828 |       constexpr atomic(__integral_type __i) noexcept : __base_type(__i) { }
      |                 ^~~~~~
make[2]: *** [CMakeFiles/db_bench.dir/build.make:89: CMakeFiles/db_bench.dir/benchmarks/db_bench.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:245: CMakeFiles/db_bench.dir/all] Error 2
make: *** [Makefile:141: all] Error 2

I also noticed that travis has the same build failure: https://travis-ci.org/github/google/leveldb/jobs/753958518
Is there anything that I am missing?

@pwnall

@pwnall

I can confirm this on a macOS 11.1 computer, with slightly different notices (but of the same error), showing
/Users/zhxq/Downloads/testing/leveldb/benchmarks/db_bench.cc:133:7: error: 'Compare' overrides a member function but is not marked 'override' [-Werror,-Winconsistent-missing-override]
  int Compare(const Slice& a, const Slice& b) const {
      ^
/Users/zhxq/Downloads/testing/leveldb/include/leveldb/comparator.h:28:15: note: overridden virtual function is here
  virtual int Compare(const Slice& a, const Slice& b) const = 0;
              ^
/Users/zhxq/Downloads/testing/leveldb/benchmarks/db_bench.cc:152:40: error: copying member subobject of type 'std::atomic<size_t>' (aka 'atomic<unsigned long>') invokes deleted constructor
  mutable std::atomic<size_t> count_ = 0;
                                       ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/atomic:1643:7: note: copy constructor of 'atomic<unsigned long>' is implicitly deleted
      because base class '__atomic_base<unsigned long>' has a deleted copy constructor
    : public __atomic_base<_Tp>
      ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/atomic:1562:7: note: copy constructor of '__atomic_base<unsigned long, true>' is implicitly
      deleted because base class '__atomic_base<unsigned long, false>' has a deleted copy constructor
    : public __atomic_base<_Tp, false>
      ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/atomic:1542:5: note: '__atomic_base' has been explicitly marked deleted here
    __atomic_base(const __atomic_base&) = delete;
    ^
2 errors generated.
make[2]: *** [CMakeFiles/db_bench.dir/benchmarks/db_bench.cc.o] Error 1
make[1]: *** [CMakeFiles/db_bench.dir/all] Error 2
make: *** [all] Error 2

I can confirm this on a macOS 11.1 computer, with slightly different notices (but of the same error), showing
/Users/zhxq/Downloads/testing/leveldb/benchmarks/db_bench.cc:133:7: error: 'Compare' overrides a member function but is not marked 'override' [-Werror,-Winconsistent-missing-override]
  int Compare(const Slice& a, const Slice& b) const {
      ^
/Users/zhxq/Downloads/testing/leveldb/include/leveldb/comparator.h:28:15: note: overridden virtual function is here
  virtual int Compare(const Slice& a, const Slice& b) const = 0;
              ^
/Users/zhxq/Downloads/testing/leveldb/benchmarks/db_bench.cc:152:40: error: copying member subobject of type 'std::atomic<size_t>' (aka 'atomic<unsigned long>') invokes deleted constructor
  mutable std::atomic<size_t> count_ = 0;
                                       ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/atomic:1643:7: note: copy constructor of 'atomic<unsigned long>' is implicitly deleted
      because base class '__atomic_base<unsigned long>' has a deleted copy constructor
    : public __atomic_base<_Tp>
      ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/atomic:1562:7: note: copy constructor of '__atomic_base<unsigned long, true>' is implicitly
      deleted because base class '__atomic_base<unsigned long, false>' has a deleted copy constructor
    : public __atomic_base<_Tp, false>
      ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/atomic:1542:5: note: '__atomic_base' has been explicitly marked deleted here
    __atomic_base(const __atomic_base&) = delete;
    ^
2 errors generated.
make[2]: *** [CMakeFiles/db_bench.dir/benchmarks/db_bench.cc.o] Error 1
make[1]: *** [CMakeFiles/db_bench.dir/all] Error 2
make: *** [all] Error 2