502 Bad Gateway

Hey!
Just started using this cool API yesterday and today it's giving me a 502. Did the server go down?

Same here

+1

I'm sorry guys but it think it might've been me :(
I was making a webapp and forgot to place a cooldown in my loop so it sent thousands of requests and maybe the code doesn't have a limiter so I just killed it. It was at the same time I did that that it stopped working.

ahh sh*t lol

It’s a free service and should’ve been careful not to abuse it. Anyway I hope the author adds some instructions to self host it so people can use it in whatever ways they want.

It was a finger error 😭
I would be happy to host it myself

Hey the issue has been fixed! The server is back up
The downtime seems to have been caused by excessive requests that the server was unable to handle.
Sorry for the interruption

Thanks a lot!


Encountered Unknown Service or Status

2022-05-16 14:27:27 ERROR (MainThread) [nyc311calendar.api]
Encountered unknown service or status. Please report this to the developers using the "Unknown Service or Status" bug template at https://github.com/elahd/nyc311calendar/issues/new/choose.
2022-05-16 14:27:27 ERROR (MainThread) [custom_components.nyc311] Unexpected error fetching nyc311 data:
File "/usr/local/lib/python3.9/site-packages/nyc311calendar/api.py", line 209, in __async_calendar_update
File "/config/custom_components/nyc311/init.py", line 39, in async_update_data
File "/usr/local/lib/python3.9/site-packages/nyc311calendar/api.py", line 168, in get_calendar
File "/usr/local/lib/python3.9/site-packages/nyc311calendar/api.py", line 224, in __async_calendar_update
nyc311calendar.api.NYC311API.UnexpectedEntry

Thanks for reporting this.
I ended up filing a Freedom of Information Law request with the city's IT department for the API source code (with a brief explanation). They replied with a full list of statuses, which is great.
I'll post a fix (with better error handling) soon.

Thanks so much.  Good job on the Freedom of Information request!!!

Thank you for updating.  My main Home Assistant dashboard is much happier now.

Great! Out of curiosity, how are you displaying this integration on your dashboard? Would there be any value to having this integration work with Home Assistant calendars?
Calendar card: https://www.home-assistant.io/dashboards/calendar/
Calendar integration: https://www.home-assistant.io/integrations/calendar/

I use your integration along with the garbage integration in custom mushroom cards on the main dashboard.  The alternate side info is on another dashboard.
Calendar- ABSOLUTELY!  I would like to create trigger-based automations from this info. In the release that dropped yesterday (https://www.home-assistant.io/blog/2022/06/01/release-20226/#calendar-triggers-with-offsets), we now have offsets.

Awesome -- thanks for the input!


ModuleNotFoundError: No module named 'invcryrep'

Hello,
After installing mattext I am facing the following issue:
>>> from mattext.representations import TextRep
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/asarikas/venvir/numpy/lib/python3.11/site-packages/mattext/representations/__init__.py", line 1, in <module>
    from xtal2txt.core import TextRep
  File "/home/asarikas/venvir/numpy/lib/python3.11/site-packages/xtal2txt/core.py", line 7, in <module>
    from invcryrep.invcryrep import InvCryRep
ModuleNotFoundError: No module named 'invcryrep'

I suspect that this may be related to how the xtal2txt package loads slices as mentioned here.

Hi @adosar ,
Thank you for your interest in using MatText. I was able to reproduce the error you reported and it trace back to the recent api changes in SLICES package.
The easiest option for usage now would be to pin slices to a previous version, while I update our package.
pip install slices==1.4.12
I was able to import TextRep after reinstalling slices after installing mattext.

Hi @n0w0f,
After pinning the slices version to 1.4.12, running the introductory example returns None:
from mattext.representations import TextRep
from pymatgen.core import Structure

# Load structure from a CIF file
from_file = "NaCl.cif"
structure = Structure.from_file(from_file, "cif")

# Initialize TextRep Class
text_rep = TextRep.from_input(structure)

requested_reps = [
    "cif_p1",
    "slices",
    "atom_sequences",
    "atom_sequences_plusplus",
    "crystal_text_llm",
    "zmatrix"
]

# Get the requested text representations
requested_text_reps = text_rep.get_requested_text_reps(requested_reps)   # This returns None.

This is the structure file
# generated using pymatgen
data_NaCl
_symmetry_space_group_name_H-M   'P 1'
_cell_length_a   5.69169400
_cell_length_b   5.69169400
_cell_length_c   5.69169400
_cell_angle_alpha   90.00000000
_cell_angle_beta   90.00000000
_cell_angle_gamma   90.00000000
_symmetry_Int_Tables_number   1
_chemical_formula_structural   NaCl
_chemical_formula_sum   'Na4 Cl4'
_cell_volume<PHONE_NUMBER>3
_cell_formula_units_Z   4
loop_
_symmetry_equiv_pos_site_id
_symmetry_equiv_pos_as_xyz
1  'x, y, z'
loop_
_atom_site_type_symbol
_atom_site_label
_atom_site_symmetry_multiplicity
_atom_site_fract_x
_atom_site_fract_y
_atom_site_fract_z
_atom_site_occupancy
Na  Na0  1  0.00000000  0.00000000  0.00000000  1.0
Na  Na1  1  0.00000000  0.50000000  0.50000000  1.0
Na  Na2  1  0.50000000  0.00000000  0.50000000  1.0
Na  Na3  1  0.50000000  0.50000000  0.00000000  1.0
Cl  Cl4  1  0.50000000  0.00000000  0.00000000  1.0
Cl  Cl5  1  0.50000000  0.50000000  0.50000000  1.0
Cl  Cl6  1  0.00000000  0.00000000  0.50000000  1.0
Cl  Cl7  1  0.00000000  0.50000000  0.00000000  1.0

This is the log
2024-12-09 19:17:29.833829: E external/local_xla/xla/stream_executor/cuda/cuda_dnn.cc:9261] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
2024-12-09 19:17:29.833882: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:607] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
2024-12-09 19:17:29.834747: E external/local_xla/xla/stream_executor/cuda/cuda_blas.cc:1515] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
WARNING:tensorflow:From /home/asarikas/venvir/mattext/lib/python3.11/site-packages/tensorflow/python/util/deprecation.py:588: calling function (from tensorflow.python.eager.polymorphic_function.polymorphic_function) with experimental_relax_shapes is deprecated and will be removed in a future version.
Instructions for updating:
experimental_relax_shapes is deprecated, use reduce_retracing instead
Reading file /home/asarikas/venvir/mattext/lib/python3.11/site-packages/robocrys/condense/mineDecoding objects from /home/asarikas/venvir/mattext/lib/python3.11/site-packages/robocrys/condReading file /home/asarikas/venvir/mattext/lib/python3.11/site-packages/robocrys/condense/mineral_db.json.gz: 0it [00:00, ?it/s]
Decoding objects from /home/asarikas/venvir/mattext/lib/python3.11/site-packages/robocrys/cond
>>> requested_text_reps
>>> requested_reps
requested_reps
>>> requested_reps
['cif_p1', 'slices', 'atom_sequences', 'atom_sequences_plusplus', 'crystal_text_llm', 'zmatrix']

@adosar Thanks for reporting this !
I indeed see that get_requested_text_reps() is returning none.  I would try to debug and fix this soon.
meanwhile maybe you can use text_rep.get_all_text_reps(). Which for me returned the following dict.
{'cif_p1': "data_NaCl\n_symmetry_space_group_name_H-M   'P 1'\n_cell_length_a   4.02\n_cell_length_b   4.02\n_cell_length_c   4.02\n_cell_angle_alpha   60.0\n_cell_angle_beta   60.0\n_cell_angle_gamma   60.0\n_symmetry_Int_Tables_number   1\n_chemical_formula_structural   NaCl\n_chemical_formula_sum   'Na1 Cl1'\n_cell_volume   46.1\n_cell_formula_units_Z   1\nloop_\n _symmetry_equiv_pos_site_id\n _symmetry_equiv_pos_as_xyz\n  1  'x, y, z'\nloop_\n _atom_site_type_symbol\n _atom_site_label\n _atom_site_symmetry_multiplicity\n _atom_site_fract_x\n _atom_site_fract_y\n _atom_site_fract_z\n _atom_site_occupancy\n  Cl  Cl4  1  0.5  0.5  0.5  1.0\n  Na  Na0  1  0.0  0.0  0.0  1.0\n",
 'cif_symmetrized': None,
 'cif_bonding': None,
 'slices': 'Cl Na 0 1 + + o 0 1 + o + 0 1 o + + 0 1 + o o 0 1 o + o 0 1 o o + ',
 'composition': 'ClNa',
 'crystal_text_llm': '4.0 4.0 4.0\n59 59 59\nCl\n0.50 0.50 0.50\nNa\n0.00 0.00 0.00',
 'robocrys_rep': 'NaCl is Halite, Rock Salt structured and crystallizes in the cubic Fm-3m space group. Na(1) is bonded to six equivalent Cl(1) atoms to form a mixture of corner and edge-sharing NaCl6 octahedra. The corner-sharing octahedra are not tilted. All Na(1)-Cl(1) bond lengths are 2.85 Å. Cl(1) is bonded to six equivalent Na(1) atoms to form a mixture of corner and edge-sharing ClNa6 octahedra. The corner-sharing octahedra are not tilted.',
 'wycoff_rep': None,
 'atom_sequences': 'Cl Na',
 'atom_sequences_plusplus': 'Cl Na 4.02 4.02 4.02 60 60 60',
 'zmatrix': 'Cl\nNa 1 4.9',
 'local_env': None}

Some of the representation is failing which could be the cause for get_requested_text_reps failing. But i guess you can get the representations that you wanted with this method, until i fix this.


ClusterGroup doesn't update correctly

Hi,
I'm using the last version of leaflet (1.4.0) and marker cluster (1.4.1).
I want to use the same cluster group with two maps.
For exemple, when my first map is initialized, I have this :
(50)
and when I zoom :
(10)     (30) (10)
When I initialize my second map, I want this again, because I'm using the same cluster  :
(50)
But I have this :
(10)(50)(30) (10)
I have to zoom in and to fit the same zoom and position than the one on my first map to make the cluster work normally again.
Here some parts of my code
The first map
map = new L.Map('map', {
	attributionControl: false,
	center: bounds.getCenter(),
	minZoom: 2,
	maxZoom: 20,
	zoom: 2,
	layers: [osm],
	maxBounds: bounds,
	maxBoundsViscosity: 1
});
markers = L.markerClusterGroup({
	maxClusterRadius: 40,
	iconCreateFunction: function (cluster) {
		var childCount = cluster.getChildCount();
		var c = ' marker-cluster-stw';
		return new L.DivIcon({
			html: '
' + childCount + '
',
			className: 'marker-cluster' + c,
			iconSize: new L.Point(40, 40)
		});
	},
	spiderfyOnMaxZoom: false,
	showCoverageOnHover: false,
	zoomToBoundsOnClick: true
});
for (...){
	oneMarker = L.marker([latitude, lngitude], {
		icon: iconLabel
	}).on('click', onClick);
	markers.addLayer(oneMarker);
}
map.addLayer(markers);

And the second map
map2 = new L.Map('map2', {
        attributionControl: false,
        center: bounds.getCenter(),
        minZoom: 2,
        maxZoom: 20,
        layers: [osm],
        maxBoundsViscosity: 1
    });
map_add_marina.addLayer(markers);
markers.refreshClusters();

In general, Leaflet doesn't play well when the same layer is added to two (or more) maps at once.
Create two copies of your cluster, and add each of them to each map.


TS: Resolve imports using TypeScript

Resolves ES2015 imports and import A = E-style imports using TypeScript. The extractor attaches the symbol of the imported module to the import node, and in QL we resolve imports by matching up those symbols.
The motivation for doing this is to handle path-mappings in tsconfig.json, which was needed for flagging CVE-2019-18350. I've confirmed that we now flag the vulnerability.
Still needs some form of evaluation. There are changes to the dbscheme so it needs an internal PR, which I'll open after the evaluation is done.

Both PRs are green - let's merge before it conflicts again.


[Issue 8346][Admin API] Validate retention policy

Fixes #8346
Motivation
See #8346, #8345
Modifications
Prevent setting invalid retention policy where either size or time limit is set to zero while the other limit has a non-zero value.
The reason for this is that setting either size or time limit to zero will effectively disable the retention policy.
It is confusing for the end-user if it's possible to set a value for the other limit while it's ignored when the other limit has
the value of zero. This might lead to the incorrect assumption that the value of 0 has the meaning that the limit isn't effective.
The validation will provide the Admin API end user a useful error message if the validation fails.

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

since master branch is broken atm, I cherry picked the commit from #8361 to fix the broken state of CI. That PR should be merged before this one.

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

I'm running an experiment to see if reverting 647d3c2 fixes the grpc / protobuf compatibility issues.

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks


Add Tekton pipeline for devconsole

Adds a pipeline for use in the devconsole. Will ultimately move to artifacthub.io

Note that I am finding this is not working at the moment. Working with devconsole team to figure it out.

Hi @lance , if I got it right all the task will become Cluster scoped (no longer Namespace scoped). If so I think we also need to patch tasks.go for buildpack, s2i and deploy tasks as well to make them as Cluster task.
There is already a patch file that does that for git-clone task, so I think a similar approach could be used as well.

/lgtm


Fix the error when running Yolox evaluation on COCO test-dev

This allows the following command to be run without error when database and config files are deployed:
"python -m yolox.tools.eval -n  yolox-s -c yolox_s.pth -b 64 --conf 0.001 -d 1 --test"

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

Thanks for your contribution. LGTM.

Thanks for your contribution. LGTM.

@FateScript So has it been good enough to merge?

Thanks for your contribution. LGTM.

@FateScript So has it been good enough to merge?

Don't worry, I will merge it.


util: packaging: is_develop should check if package name with _ or - has .egg-link

https://github.com/intel/dffml/blob/e13d4eb756998015e046f0846203f4fd5f0d44e6/dffml/util/packaging.py#L12

@pdxjohnny I want to work on this but am not sure as to what exactly is wanted. Could you please guide me?

@aadarshsingh191198 Python will sometimes create .egg-link files for packages that contain - in the name where the .egg-link file has the package name but with - replaced with _.
We just need to put the above block into a loop were the first iteration of the loop just does the check as it does it now, and the second iteration checks for the presence of the .egg-link file but with the package name where - has been replaced with _. This will ensure that if Python installed it with _ in the name, we still detect it successfully.

Thanks ... Now I understood the problem. Will start working on it asap!!

I see the check still hasn't been added yet. Is it okay if I take this up?
/cc @aadarshsingh191198 @pdxjohnny

Ya sure you can. I got busy in some work so will not be able to take this right now.


Added CONTRIBUTING.md

Fixes #33

Please add the labels of gssoc and level1 on this pull request and assign me this pull request as per gssoc guidelines.


[Bug]: notification not supported

Checks before filing an issue

[X] This issue doesn't reproduce on web browsers (such as in Chrome). If it does, issue reports go to the Mattermost Server repository.
[X] I have checked the issue tracker and have not found an issue that matches the one I'm filing.
[X] This issue is not a troubleshooting question. Troubleshooting questions go here: https://forum.mattermost.com/c/trouble-shoot/16.
[X] This issue is not a feature request. You can request features and make product suggestions here: https://mattermost.com/suggestions/.
[X] This issue reproduces on the most recent stable version, or the most recent prerelease version of the Mattermost Desktop App.
[X] I have read the contribution guidelines.

Mattermost Desktop Version
5.5.0
Operating System
NixOS 23.11
Mattermost Server Version
8.1.7
Steps to reproduce
Some time ago desktop notifications just stopped working. It could be an MMDesktop update or anything.
Expected behavior
Desktop notifications work as expected
Observed behavior
Desktop notifications not work and I see error messages in logs
Log Output
[2023-12-20 13:44:13.099] [error] [Notifications] notification not supported
[2023-12-20 13:45:45.560] [error] [Notifications] notification not supported
[2023-12-20 13:48:29.668] [error] [Notifications] notification not supported
[2023-12-20 13:52:48.231] [error] [Notifications] notification not supported
[2023-12-20 13:53:52.359] [error] [Notifications] notification not supported

Additional Information
NixOS + swaywm (wayland)
Chrome + web client: notifications work as expected

@Antiarchitect This message is returned by Electron by called the isSupported function on the Notification object. So it's likely that's returning false due to something not supported by your system, or potentially an issue with Electron.
Given that it used to work, it's possible support was dropped or a bug was introduced. If you can pinpoint which MM Desktop App version this used to work on, we can find the Electron version and submit a ticket.

Hmm... I see - will try to investigate if it's possible to install older package versions in NixOS somehow.

Closing issue for now, since this issue lies with Electron and not the Desktop App.

Just tried to do Hello World with Electron Fiddle. And Electron 26 and 28 notifications work just fine:
// Modules to control application life and create native browser window
const { app, BrowserWindow, Notification } = require('electron')
const path = require('path')

function createWindow () {
  // Create the browser window.
  const mainWindow = new BrowserWindow({
    width: 800,
    height: 600,
    webPreferences: {
      preload: path.join(__dirname, 'preload.js')
    }
  })

  // and load the index.html of the app.
  console.log("Notifications: " + Notification.isSupported())
  new Notification({
  title: 'Hello',
  body: 'World'
  }).show()
  mainWindow.loadFile('index.html')
  // Open the DevTools.
  // mainWindow.webContents.openDevTools()
}

// This method will be called when Electron has finished
// initialization and is ready to create browser windows.
// Some APIs can only be used after this event occurs.
app.whenReady().then(() => {
  createWindow()

  app.on('activate', function () {
    // On macOS it's common to re-create a window in the app when the
    // dock icon is clicked and there are no other windows open.
    if (BrowserWindow.getAllWindows().length === 0) createWindow()
  })
})

// Quit when all windows are closed, except on macOS. There, it's common
// for applications and their menu bar to stay active until the user quits
// explicitly with Cmd + Q.
app.on('window-all-closed', function () {
  if (process.platform !== 'darwin') app.quit()
})

// In this file you can include the rest of your app's specific main process
// code. You can also put them in separate files and require them here.

And console shows:
Electron v26.6.8 started.
Notifications: true

Electron v28.2.1 started.
Notifications: true

It seems like it's not an Electron problem at all.

@Antiarchitect Does this work with Desktop App v5.6? This might have been fixed in a patch release to Electron (v5.5.0 is on Electron v26.1.0, v5.6.0 is on v27.0.2)

Will test these exact Electron versions with Fiddle tomorrow

@devinbinnie Both (v26.1.0 and v27.0.2) works just fine. Could it be MM sends more sophisticated notification than just simple text title + text body?

I wouldn't think so. The call we make that generates the log you're seeing looks like this:
import {Notification} from 'electron';

if (!Notification.isSupported()) {
    log.error('notification not supported');
    return;
}

The only thing I can think of at this point is that there's something in the compiled version, or some permission that your OS is denying to the compiled version that is causing this. Since you were able to make it work in a Fiddle, would you be able to try running it in development mode and see if it reproduces there? If so, would you be open to looking into a fix? If not, then it's likely something with the OS blocking it.

Looking at that it looks like npm i failed somewhere since it's saying the Electron binary doesn't exist.

npm i output seems viable:
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving<EMAIL_ADDRESS>npm WARN Found<EMAIL_ADDRESS>npm WARN node_modules/webpack
npm WARN   dev<EMAIL_ADDRESS>from the root project
npm WARN   21 more (@storybook/react-docgen-typescript-plugin, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer<EMAIL_ADDRESS>|| ^3.0.0 || ^4.0.0" from<EMAIL_ADDRESS>npm WARN node_modules/webpack-filter-warnings-plugin
npm WARN<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN   node_modules/@storybook/react/node_modules/@storybook/core/node_modules/@storybook/core-server/node_modules/@storybook/builder-webpack4
npm WARN
npm WARN Conflicting peer dependency<EMAIL_ADDRESS>npm WARN node_modules/webpack
npm WARN   peer<EMAIL_ADDRESS>|| ^3.0.0 || ^4.0.0" from<EMAIL_ADDRESS>npm WARN   node_modules/webpack-filter-warnings-plugin
npm WARN<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN     node_modules/@storybook/react/node_modules/@storybook/core/node_modules/@storybook/core-server/node_modules/@storybook/builder-webpack4

><EMAIL_ADDRESS>postinstall
> node scripts/postinstall.js && electron-builder install-app-deps

  • electron-builder  version=24.12.0
  • loaded configuration  file=/home/andrey/PROJECTS/desktop/electron-builder.json
  • rebuilding native dependencies<EMAIL_ADDRESS><EMAIL_ADDRESS>platform=linux arch=x64

up to date, audited 2953 packages in 26s

304 packages are looking for funding
  run `npm fund` for details

62 vulnerabilities (24 moderate, 32 high, 6 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.

Solved with upgrade to NixOS 24.05. Don't know what exactly did the trick.


Error on original code

Hi everybody
https://github.com/pybricks/pybricks-projects/blob/master/sets/boost/droid-commander/r2-d2/main.py#L53
I get errors, until I changed the drive.settings on line 53 from drive.settings(1000, 5000) to drive.settings(500, 5000)
Is there a new limit in the latest firmware?
A half a year ago the code was running fine on my R2D2.
Best Regards
Jonas

A whole meter per second does sound quite fast. :smile:
Does it work with a lower speed?


Remove support for vespa http client protocol v2.  Always use protocol v3.

@geirst: please review

@bratseth FYI

Why u no merge?

@bjorncs FYI


Improve SpatialRuleLookup

Fixes #1077.
I extended the changes made by @karussell, mostly by adding tests and also fixing the creation of landmarks. There was an issue that the map.geo.json file was not formatted correctly.
The only thing that is missing right now is an IT that tests the execution of GraphHopperModule.createGraphHopper -> createSpatialRule. Not sure how we want to do this, though?
Other from that the change looks good and mergeable to me.

I have updated the branch...

I updated the IT, so it only uses the belarus osm file. I moved your working LM query to a different method and only kept the disconnected graphs test in the existing method. Tests already need quite long to run, so we don't need to import LM two times. The branch looks good to me now and I think we can merge it.

Thanks!

Tests already need quite long to run, so we don't need to import LM two times.

Nice idea!


A certificate error occurred in the upload-stemcell command(certificate has expired)

When executing the bosh upload-stemcell command, the following error message appears
$ bosh -e stage -n upload-stemcell https://bosh.io/d/stemcells/bosh-aws-xen-hvm-ubuntu-xenial-go_agent?v=315.64

Name               stage
UUID               8918c85c-4e34-4af1-a19f-3ad5498831a5
Version            271.2.0 (00000000)
Director Stemcell  ubuntu-xenial/621.93
CPI                aws_cpi
Features           compiled_package_cache: disabled
                   config_server: enabled
                   local_dns: enabled
                   power_dns: disabled
                   snapshots: enabled
User               admin

Succeeded
Using environment '<IP_ADDRESS>' as client 'admin'

Task 238980

Task 238980 | 07:03:22 | Update stemcell: Downloading remote stemcell (00:00:00)
                      L Error: SSL_connect returned=1 errno=0 state=error: certificate verify failed (certificate has expired)
Task 238980 | 07:03:23 | Error: SSL_connect returned=1 errno=0 state=error: certificate verify failed (certificate has expired)

Task 238980 Started  Thu Aug 25 07:03:22 UTC 2022
Task 238980 Finished Thu Aug 25 07:03:23 UTC 2022
Task 238980 Duration 00:00:01
Task 238980 error

Uploading remote stemcell 'https://bosh.io/d/stemcells/bosh-aws-xen-hvm-ubuntu-xenial-go_agent?v=315.64':
  Expected task '238980' to succeed but state is 'error'

Exit code 1

The certificate period still remains, but I don't know why this error occurred.
How to solve it?
$ bosh env --details

CERTIFICATE EXPIRY DATE INFORMATION

Certificate                         Expiry Date (UTC)     Days Left
director.ssl.cert                   2032-08-08T06:03:58Z  3635
director.config_server.ca_cert      2032-08-08T06:03:58Z  3635
director.config_server.uaa.ca_cert  2032-08-08T06:03:58Z  3635
nats.tls.ca                         2032-08-08T06:03:58Z  3635
nats.tls.client_ca.certificate      2032-08-08T06:03:58Z  3635
nats.tls.director.certificate       2032-08-08T06:03:58Z  3635
director.db.tls.cert.ca             2024-08-22T17:08:50Z  728

Succeeded

Is the issue reproducible in your environment (I was not able to reproduce it in mine)? Also is there any stacktrace you could post in the debug log (bosh task  238980 --debug)?

First of all, thank you for leaving a reply.

Reproduce the same symptoms

$ bosh -e soonwoo -n upload-stemcell https://bosh.io/d/stemcells/bosh-aws-xen-hvm-ubuntu-xenial-go_agent?v=315.64

Name               soonwoo
UUID               95089975-21ec-4cda-afb8-730c6d102c00
Version            271.2.0 (00000000)
Director Stemcell  ubuntu-xenial/621.93
CPI                aws_cpi
Features           compiled_package_cache: disabled
                   config_server: enabled
                   local_dns: enabled
                   power_dns: disabled
                   snapshots: enabled
User               admin

Succeeded
Using environment '<IP_ADDRESS>' as client 'admin'

Task 80

Task 80 | 05:29:59 | Update stemcell: Downloading remote stemcell (00:00:01)
                   L Error: SSL_connect returned=1 errno=0 state=error: certificate verify failed (certificate has expired)
Task 80 | 05:30:00 | Error: SSL_connect returned=1 errno=0 state=error: certificate verify failed (certificate has expired)

Task 80 Started  Wed Sep 14 05:29:59 UTC 2022
Task 80 Finished Wed Sep 14 05:30:00 UTC 2022
Task 80 Duration 00:00:01
Task 80 error

Uploading remote stemcell 'https://bosh.io/d/stemcells/bosh-aws-xen-hvm-ubuntu-xenial-go_agent?v=315.64':
  Expected task '80' to succeed but state is 'error'

Exit code 1

$ bosh env --details
Using environment '<IP_ADDRESS>' as client 'admin'

Name               soonwoo
UUID               95089975-21ec-4cda-afb8-730c6d102c00
Version            271.2.0 (00000000)
Director Stemcell  ubuntu-xenial/621.93
CPI                aws_cpi
Features           compiled_package_cache: disabled
                   config_server: enabled
                   local_dns: enabled
                   power_dns: disabled
                   snapshots: enabled
User               admin

CERTIFICATE EXPIRY DATE INFORMATION

Certificate                         Expiry Date (UTC)     Days Left
director.ssl.cert                   2032-08-23T07:50:25Z  3631
director.config_server.ca_cert      2032-08-23T07:50:25Z  3631
director.config_server.uaa.ca_cert  2032-08-23T07:50:25Z  3631
nats.tls.ca                         2032-08-23T07:50:25Z  3631
nats.tls.client_ca.certificate      2032-08-23T07:50:25Z  3631
nats.tls.director.certificate       2032-08-23T07:50:25Z  3631
director.db.tls.cert.ca             2024-08-22T17:08:50Z  708

Succeeded

debug log

$ bosh task 80 --debug
Using environment '<IP_ADDRESS>' as client 'admin'

Task 80

I, [2022-09-14T05:29:59.396460 #30] [0x3f926c004e78]  INFO -- TaskHelper: Director Version: 271.2.0
I, [2022-09-14T05:29:59.396548 #30] [0x3f926c004e78]  INFO -- TaskHelper: Enqueuing task: 80
I, [2022-09-14T05:29:59.951175 #27116] []  INFO -- DirectorJobRunner: Looking for task with task id 80
D, [2022-09-14T05:29:59.952696 #27116] [] DEBUG -- DirectorJobRunner: (0.000529s) (conn:<PHONE_NUMBER>6200) SELECT * FROM `tasks` WHERE `id` = 80
I, [2022-09-14T05:29:59.953318 #27116] []  INFO -- DirectorJobRunner: Found task #<Bosh::Director::Models::Task @values={:id=>80, :state=>"processing", :timestamp=>2022-09-14 05:29:59 UTC, :description=>"create stemcell", :result=>nil, :output=>"/var/vcap/store/director/tasks/80", :checkpoint_time=>2022-09-14 05:29:59 UTC, :type=>"update_stemcell", :username=>"admin", :deployment_name=>nil, :started_at=>nil, :event_output=>"", :result_output=>"", :context_id=>""}>
I, [2022-09-14T05:29:59.953420 #27116] []  INFO -- DirectorJobRunner: Running from worker 'worker_3' on director/2a254ac3-342d-4810-67a5-1800c885c2c7 (<IP_ADDRESS>)
I, [2022-09-14T05:29:59.953454 #27116] []  INFO -- DirectorJobRunner: Starting task: 80
I, [2022-09-14T05:29:59.953502 #27116] [task:80]  INFO -- DirectorJobRunner: Creating job
D, [2022-09-14T05:29:59.954457 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.000384s) (conn:<PHONE_NUMBER>6200) SELECT * FROM `tasks` WHERE `id` = 80
D, [2022-09-14T05:29:59.955321 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.000359s) (conn:<PHONE_NUMBER>6200) SELECT * FROM `tasks` WHERE `id` = 80
I, [2022-09-14T05:29:59.959818 #27116] [task:80]  INFO -- DirectorJobRunner: Performing task: #<Bosh::Director::Models::Task @values={:id=>80, :state=>"processing", :timestamp=>2022-09-14 05:29:59 UTC, :description=>"create stemcell", :result=>nil, :output=>"/var/vcap/store/director/tasks/80", :checkpoint_time=>2022-09-14 05:29:59 UTC, :type=>"update_stemcell", :username=>"admin", :deployment_name=>nil, :started_at=>nil, :event_output=>"", :result_output=>"", :context_id=>""}>
D, [2022-09-14T05:29:59.961061 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.000371s) (conn:<PHONE_NUMBER>6200) BEGIN
D, [2022-09-14T05:29:59.962195 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.000554s) (conn:<PHONE_NUMBER>6200) UPDATE `tasks` SET `state` = 'processing', `timestamp` = '2022-09-14 05:29:59', `description` = 'create stemcell', `result` = NULL, `output` = '/var/vcap/store/director/tasks/80', `checkpoint_time` = '2022-09-14 05:29:59', `type` = 'update_stemcell', `username` = 'admin', `deployment_name` = NULL, `started_at` = '2022-09-14 05:29:59', `event_output` = '', `result_output` = '', `context_id` = '' WHERE (`id` = 80) LIMIT 1
D, [2022-09-14T05:29:59.966799 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.004500s) (conn:<PHONE_NUMBER>6200) COMMIT
I, [2022-09-14T05:29:59.966882 #27116] [task:80]  INFO -- DirectorJobRunner: Processing update stemcell
D, [2022-09-14T05:29:59.968997 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.000679s) (conn:<PHONE_NUMBER>6200) SELECT * FROM `configs` WHERE (`id` IN (SELECT max(`id`) FROM `configs` WHERE (`type` = 'cpi') GROUP BY `name`))
I, [2022-09-14T05:29:59.969141 #27116] [task:80]  INFO -- DirectorJobRunner: Update stemcell
D, [2022-09-14T05:29:59.970235 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.000342s) (conn:<PHONE_NUMBER>6200) BEGIN
D, [2022-09-14T05:29:59.971032 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.000490s) (conn:<PHONE_NUMBER>6200) UPDATE `tasks` SET `event_output` = CONCAT(`event_output`, '{\"time\":1663133399,\"stage\":\"Update stemcell\",\"tags\":[],\"total\":6,\"task\":\"Downloading remote stemcell\",\"index\":1,\"state\":\"started\",\"progress\":0}\n') WHERE (`id` = 80)
D, [2022-09-14T05:29:59.975294 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.004174s) (conn:<PHONE_NUMBER>6200) COMMIT
I, [2022-09-14T05:29:59.975380 #27116] [task:80]  INFO -- DirectorJobRunner: Downloading remote stemcell
I, [2022-09-14T05:29:59.975562 #27116] [task:80]  INFO -- DirectorJobRunner: Downloading remote stemcell from https://bosh.io/d/stemcells/bosh-aws-xen-hvm-ubuntu-xenial-go_agent?v=315.64
D, [2022-09-14T05:30:00.065566 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.000329s) (conn:<PHONE_NUMBER>6200) BEGIN
D, [2022-09-14T05:30:00.072669 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.006731s) (conn:<PHONE_NUMBER>6200) UPDATE `tasks` SET `event_output` = CONCAT(`event_output`, '{\"time\":1663133400,\"stage\":\"Update stemcell\",\"tags\":[],\"total\":6,\"task\":\"Downloading remote stemcell\",\"index\":1,\"state\":\"failed\",\"progress\":100,\"data\":{\"error\":\"SSL_connect returned=1 errno=0 state=error: certificate verify failed (certificate has expired)\"}}\n') WHERE (`id` = 80)
D, [2022-09-14T05:30:00.165220 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.092383s) (conn:<PHONE_NUMBER>6200) COMMIT
D, [2022-09-14T05:30:00.214827 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.019336s) (conn:<PHONE_NUMBER>6200) BEGIN
D, [2022-09-14T05:30:00.216129 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.000930s) (conn:<PHONE_NUMBER>6200) UPDATE `tasks` SET `event_output` = CONCAT(`event_output`, '{\"time\":1663133400,\"error\":{\"code\":100,\"message\":\"SSL_connect returned=1 errno=0 state=error: certificate verify failed (certificate has expired)\"}}\n') WHERE (`id` = 80)
D, [2022-09-14T05:30:00.242705 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.026433s) (conn:<PHONE_NUMBER>6200) COMMIT
E, [2022-09-14T05:30:00.242881 #27116] [task:80] ERROR -- DirectorJobRunner: SSL_connect returned=1 errno=0 state=error: certificate verify failed (certificate has expired)
/var/vcap/data/packages/ruby-2.6.5-r0.29.0/ea52281b4d5ea6f821ce616a8ca5b181ebf1e4c9/lib/ruby/2.6.0/net/protocol.rb:44:in `connect_nonblock'
/var/vcap/data/packages/ruby-2.6.5-r0.29.0/ea52281b4d5ea6f821ce616a8ca5b181ebf1e4c9/lib/ruby/2.6.0/net/protocol.rb:44:in `ssl_socket_connect'
/var/vcap/data/packages/ruby-2.6.5-r0.29.0/ea52281b4d5ea6f821ce616a8ca5b181ebf1e4c9/lib/ruby/2.6.0/net/http.rb:996:in `connect'
/var/vcap/data/packages/ruby-2.6.5-r0.29.0/ea52281b4d5ea6f821ce616a8ca5b181ebf1e4c9/lib/ruby/2.6.0/net/http.rb:930:in `do_start'
/var/vcap/data/packages/ruby-2.6.5-r0.29.0/ea52281b4d5ea6f821ce616a8ca5b181ebf1e4c9/lib/ruby/2.6.0/net/http.rb:919:in `start'
/var/vcap/data/packages/ruby-2.6.5-r0.29.0/ea52281b4d5ea6f821ce616a8ca5b181ebf1e4c9/lib/ruby/2.6.0/net/http.rb:605:in `start'
/var/vcap/data/packages/director/d0f423a78a6482fec03562879dd6ee04b1807633/gem_home/ruby/2.6.0/gems/bosh-director-0.0.0/lib/bosh/director/download_helper.rb:23:in `download_remote_file'
/var/vcap/data/packages/director/d0f423a78a6482fec03562879dd6ee04b1807633/gem_home/ruby/2.6.0/gems/bosh-director-0.0.0/lib/bosh/director/jobs/update_stemcell.rb:156:in `download_remote_stemcell'
/var/vcap/data/packages/director/d0f423a78a6482fec03562879dd6ee04b1807633/gem_home/ruby/2.6.0/gems/bosh-director-0.0.0/lib/bosh/director/jobs/update_stemcell.rb:41:in `block in perform'
/var/vcap/data/packages/director/d0f423a78a6482fec03562879dd6ee04b1807633/gem_home/ruby/2.6.0/gems/bosh-director-0.0.0/lib/bosh/director/jobs/base_job.rb:54:in `block in track_and_log'
/var/vcap/data/packages/director/d0f423a78a6482fec03562879dd6ee04b1807633/gem_home/ruby/2.6.0/gems/bosh-director-0.0.0/lib/bosh/director/event_log.rb:105:in `advance_and_track'
/var/vcap/data/packages/director/d0f423a78a6482fec03562879dd6ee04b1807633/gem_home/ruby/2.6.0/gems/bosh-director-0.0.0/lib/bosh/director/jobs/base_job.rb:52:in `track_and_log'
/var/vcap/data/packages/director/d0f423a78a6482fec03562879dd6ee04b1807633/gem_home/ruby/2.6.0/gems/bosh-director-0.0.0/lib/bosh/director/jobs/update_stemcell.rb:41:in `perform'
/var/vcap/data/packages/director/d0f423a78a6482fec03562879dd6ee04b1807633/gem_home/ruby/2.6.0/gems/bosh-director-0.0.0/lib/bosh/director/job_runner.rb:99:in `perform_job'
/var/vcap/data/packages/director/d0f423a78a6482fec03562879dd6ee04b1807633/gem_home/ruby/2.6.0/gems/bosh-director-0.0.0/lib/bosh/director/job_runner.rb:34:in `block in run'
/var/vcap/data/packages/director/d0f423a78a6482fec03562879dd6ee04b1807633/gem_home/ruby/2.6.0/gems/bosh_common-0.0.0/lib/common/thread_formatter.rb:50:in `with_thread_name'
/var/vcap/data/packages/director/d0f423a78a6482fec03562879dd6ee04b1807633/gem_home/ruby/2.6.0/gems/bosh-director-0.0.0/lib/bosh/director/job_runner.rb:34:in `run'
/var/vcap/data/packages/director/d0f423a78a6482fec03562879dd6ee04b1807633/gem_home/ruby/2.6.0/gems/bosh-director-0.0.0/lib/bosh/director/jobs/base_job.rb:9:in `perform'
/var/vcap/data/packages/director/d0f423a78a6482fec03562879dd6ee04b1807633/gem_home/ruby/2.6.0/gems/bosh-director-0.0.0/lib/bosh/director/jobs/db_job.rb:32:in `block in perform'
/var/vcap/data/packages/director/d0f423a78a6482fec03562879dd6ee04b1807633/gem_home/ruby/2.6.0/gems/bosh-director-0.0.0/lib/bosh/director/jobs/db_job.rb:98:in `block (3 levels) in run'
/var/vcap/data/packages/director/d0f423a78a6482fec03562879dd6ee04b1807633/gem_home/ruby/2.6.0/gems/eventmachine-1.2.7/lib/eventmachine.rb:1077:in `block in spawn_threadpool'
/var/vcap/data/packages/director/d0f423a78a6482fec03562879dd6ee04b1807633/gem_home/ruby/2.6.0/gems/logging-2.2.2/lib/logging/diagnostic_context.rb:474:in `block in create_with_logging_context'
D, [2022-09-14T05:30:00.250844 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.007008s) (conn:<PHONE_NUMBER>6200) SELECT * FROM `tasks` WHERE `id` = 80
D, [2022-09-14T05:30:00.253794 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.000374s) (conn:<PHONE_NUMBER>6200) BEGIN
D, [2022-09-14T05:30:00.255470 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.001270s) (conn:<PHONE_NUMBER>6200) UPDATE `tasks` SET `state` = 'error', `timestamp` = '2022-09-14 05:30:00', `description` = 'create stemcell', `result` = 'SSL_connect returned=1 errno=0 state=error: certificate verify failed (certificate has expired)', `output` = '/var/vcap/store/director/tasks/80', `checkpoint_time` = '2022-09-14 05:29:59', `type` = 'update_stemcell', `username` = 'admin', `deployment_name` = NULL, `started_at` = '2022-09-14 05:29:59', `event_output` = '{\"time\":1663133399,\"stage\":\"Update stemcell\",\"tags\":[],\"total\":6,\"task\":\"Downloading remote stemcell\",\"index\":1,\"state\":\"started\",\"progress\":0}\n{\"time\":1663133400,\"stage\":\"Update stemcell\",\"tags\":[],\"total\":6,\"task\":\"Downloading remote stemcell\",\"index\":1,\"state\":\"failed\",\"progress\":100,\"data\":{\"error\":\"SSL_connect returned=1 errno=0 state=error: certificate verify failed (certificate has expired)\"}}\n{\"time\":1663133400,\"error\":{\"code\":100,\"message\":\"SSL_connect returned=1 errno=0 state=error: certificate verify failed (certificate has expired)\"}}\n', `result_output` = '', `context_id` = '' WHERE (`id` = 80) LIMIT 1
D, [2022-09-14T05:30:00.310775 #27116] [task:80] DEBUG -- DirectorJobRunner: (0.055184s) (conn:<PHONE_NUMBER>6200) COMMIT
I, [2022-09-14T05:30:00.310995 #27116] []  INFO -- DirectorJobRunner: Task took 0.357446045 seconds to process.

Task 80 error

Capturing task '80' output:
  Expected task '80' to succeed but state is 'error'

Exit code 1

Could you run nmap --script=ssl-cert.nse -p 443 bosh.io from the bosh director? Would be interested in the output.

bosh/0:~# nmap --script=ssl-cert.nse -p 443 bosh.io

Starting Nmap 7.01 ( https://nmap.org ) at 2022-09-16 00:55 UTC
Nmap scan report for bosh.io (<IP_ADDRESS>)
Host is up (0.0016s latency).
Other addresses for bosh.io (not scanned): <IP_ADDRESS> 2606:4700:3037::ac43:b4f0 2606:4700:3030::6815:124c
PORT    STATE SERVICE
443/tcp open  https
| ssl-cert: Subject: commonName=*.bosh.io
| Issuer: commonName=R3/organizationName=Let's Encrypt/countryName=US
| Public Key type: rsa
| Public Key bits: 2048
| Signature Algorithm: sha256WithRSAEncryption
| Not valid before: 2022-08-06T00:08:33
| Not valid after:  2022-11-04T00:08:32
| MD5:   b6be 9c87 d1e7 333e 8fe9 3465 26f3 2782
|_SHA-1: 88cc 9e28 0195 b2d2 e35c 9713 b30e 0413 e4cd f6ff

Nmap done: 1 IP address (1 host up) scanned in 7.27 seconds

bosh/0:~$ chronyc sources -v
210 Number of sources = 5

  .-- Source mode  '^' = server, '=' = peer, '#' = local clock.
 / .- Source state '*' = current synced, '+' = combined , '-' = not combined,
| /   '?' = unreachable, 'x' = time may be in error, '~' = time too variable.
||                                                 .- xxxx [ yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured offset,
||                                \     |          |  zzzz = estimated error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
^+ <IP_ADDRESS>               3   9   377    23    +42us[  +42us] +/-  382us
^- time1.google.com              1  10   377   738   -245us[ -242us] +/-   25ms
^* time2.google.com              1  10   377   564    -57us[  -53us] +/- 1388us
^- time3.google.com              1  10   377   712   -183us[ -180us] +/-   26ms
^- time4.google.com              1  10   377   274   +408us[ +408us] +/-   25ms

$ chronyc tracking
Reference ID    : <IP_ADDRESS> (time2.google.com)
Stratum         : 2
Ref time (UTC)  : Thu Sep 22 00:51:25 2022
System time     : 0.000030480 seconds slow of NTP time
Last offset     : -0.000012242 seconds
RMS offset      : 0.000053440 seconds
Frequency       : 10.297 ppm slow
Residual freq   : -0.007 ppm
Skew            : 0.015 ppm
Root delay      : 0.001875 seconds
Root dispersion : 0.001118 seconds
Update interval : 1039.2 seconds
Leap status     : Normal

$ timedatectl
      Local time: Thu 2022-09-22 01:06:55 UTC
  Universal time: Thu 2022-09-22 01:06:55 UTC
        RTC time: Thu 2022-09-22 01:06:56
       Time zone: Etc/UTC (UTC, +0000)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

Is there anything wrong with it? Or are there any additional commands I need?

The time / date seems to be okey. Could you run curl -I -L 'https://bosh.io/d/stemcells/bosh-aws-xen-hvm-ubuntu-xenial-go_agent?v=315.64'?

bosh/0:~# curl -I -L 'https://bosh.io/d/stemcells/bosh-aws-xen-hvm-ubuntu-xenial-go_agent?v=315.64'
curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.

The bosh.io site certificate seems to have expired, what should I do?

@beyhan
Thanks for reply.

It works fine on local machine(MacOS). like this

> curl -I -L 'https://bosh.io/d/stemcells/bosh-aws-xen-hvm-ubuntu-xenial-go_agent?v=315.64'
HTTP/2 302
date: Fri, 23 Sep 2022 02:15:03 GMT
content-type: text/html; charset=utf-8
location: https://s3.amazonaws.com/bosh-aws-light-stemcells/315.64/light-bosh-stemcell-315.64-aws-xen-hvm-ubuntu-xenial-go_agent.tgz
x-vcap-request-id: ce3564f9-0c97-4b61-6861-1d26fa614e72
strict-transport-security: max-age=31536000; includeSubDomains
cf-cache-status: DYNAMIC
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=dYZHI2z%2BSFisxV0Ne%2BUR97NBXWwqC4KYj%2BZ2dYPR1KelJYGwqwHUDlGDU%2FOP4Jit43ICHCdOvu0CGWePXNZ%2F9l%2F%2FnycBQW33pbh5wNpD8e008Rf3I3t7wskf"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 74efc52f1dc320c5-NRT
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

HTTP/1.1 200 OK
x-amz-id-2: SNjP1l9qh1wFoX9UGMh+sbNfDZVq/H6WW3b3/8uQZnRyyL/7OQ1a+ca9EUpYgtGzksuuHcfSe58=
x-amz-request-id: JDKV44FGETR0B2VM
Date: Fri, 23 Sep 2022 02:15:05 GMT
Last-Modified: Wed, 03 Jul 2019 00:41:41 GMT
ETag: "c4e901a7ecb5cbac60a3c2f96f995792"
x-amz-version-id: r9Zqx9NWVZzuY8iE8xu301KKrC547GS.
Accept-Ranges: bytes
Content-Type: application/octet-stream
Server: AmazonS3
Content-Length: 19909

It is not used by other IaaS providers, but only in aws.
The bosh director environment is Ubuntu 16.04.7 LTS (GNU/Linux 4.15.0-123-generic x86_64).
The environment of the instance with bosh installed is Ubuntu 16.04.5 LTS.

I think it may be the same reason as this issue.

https://github.com/cloudfoundry/bosh/issues/2396

Please update the stemcell for your bosh director 621.93 → 621.280. The stemcell you are currently running is really old and the operation system certificate bundle contained in that is really out of date.

Any info on the director stemcell version 621.280?
As a result of searching through google, only the vmware site came up.
I signed up but couldn't apply because I couldn't log in.
Instead, I redeployed the bosh director with version 621.125, the most recent version from the existing bosh.io documentation, and the same error occurs.
###################
# Upload Stemcell #
###################
/data/cf-ops /data/cf-ops
/data/config/soonwoo /data/cf-ops /data/cf-ops
/data/cf-ops /data/cf-ops
Using environment '<IP_ADDRESS>' as client 'admin'

Name               soonwoo
UUID               95089975-21ec-4cda-afb8-730c6d102c00
Version            271.2.0 (00000000)
Director Stemcell  ubuntu-xenial/621.125
CPI                aws_cpi
Features           compiled_package_cache: disabled
                   config_server: enabled
                   local_dns: enabled
                   power_dns: disabled
                   snapshots: enabled
User               admin

Succeeded
Using environment '<IP_ADDRESS>' as client 'admin'

Task 99

Task 99 | 06:23:30 | Update stemcell: Downloading remote stemcell (00:00:00)
                   L Error: SSL_connect returned=1 errno=0 state=error: certificate verify failed (certificate has expired)
Task 99 | 06:23:30 | Error: SSL_connect returned=1 errno=0 state=error: certificate verify failed (certificate has expired)

Task 99 Started  Tue Sep 27 06:23:30 UTC 2022
Task 99 Finished Tue Sep 27 06:23:30 UTC 2022
Task 99 Duration 00:00:00
Task 99 error

Uploading remote stemcell 'https://bosh.io/d/stemcells/bosh-aws-xen-hvm-ubuntu-xenial-go_agent?v=315.64':
  Expected task '99' to succeed but state is 'error'

Exit code 1

Should I update the bosh director version?

it is specifically stemcell related and not with the bosh director.
so you could upgrade only the stemcell of the bosh director

@ramonskie
I found the reason.
Before deploying the cf, I uploaded the stemcell for deploying the cf first, but the xenial version of ami did not exist in AWS.
It seems that a certificate error occurs in the xenial version of stemcell.
I have another problem.
The built-in cf is based on ubuntu-xenial 315.64 version stemcell.
To change this to the bionic version, many things need to be changed, so stability is a problem.
Is there any way to upload ubuntu-xenial version 315.64 to stemcell as a raw image?

i don't see why changing from xenial to bionic or jammy would cause any statbility issues as cf-deployment is currently tested on both.
its possible to upload full/raw stemcells to a aws deployed director.
but you cannot deploy a director with a full stemcell with bosh create-env

@ramonskie
Like I said above.
When I try to upload stemcell with bosh director, I get "ssl_connect_error" or
I get the message "stemcell does not exist in aws-region".
The reason for this is that aws does not have the xenial stemcell 315.64 version.
The xenial version that can upload-stemcell with bosh director is from version 621.93.
However, since I am using cf-deployment v9.5.0 (see github address below)
(https://github.com/cloudfoundry/cf-deployment/blob/v9.5.0/cf-deployment.yml#L1)
If it is not the xenial version 315.64, I think an error occurs when deploying the releases of cf.
What should I do in this case?
Can I make the 315.64 version of ami?
Or can I ask to recreate the 315.64 version of the ami?

the xenial-315 line is really old we don't support this anymore and most of those ami's are cleaned up on our part.
as part of a cost reduction program
the only logical route at this point is upgrading the bosh director first and go from there.
upgrading the bosh director should be easy and should not cause any issues

As per https://github.com/cloudfoundry/community/blob/main/toc/rfc/rfc-0010-stemcell-cleanup.md#proposal stemcells older then 3 years can no longer be consumed via a light stemcell.
The heavy stemcell can still be downloaded from here: https://bosh-core-stemcells.s3-accelerate.amazonaws.com/315.64/bosh-stemcell-315.64-aws-xen-hvm-ubuntu-xenial-go_agent.tgz
bosh upload-stemcell https://bosh-core-stemcells.s3-accelerate.amazonaws.com/315.64/bosh-stemcell-315.64-aws-xen-hvm-ubuntu-xenial-go_agent.tgz --fix

@ramonskie @rkoster
Thank you so much for your sincere answer.
As you said, I'll test it by applying a heavy stemcell.
If I get an error or have any questions, I'll ask again!


Add prebuilt-bindings GDAL 2.3 and GDAL 2.4.

Prebuilt-bindings for GDAL 2.3.3 and GDAL 2.4.1
Update bindgen to version 0.48.

Looks good to me!
@jdroenner: is it ok, when I merge?
@frewsxcv: who has permissions to run bors?

yes, of course. Feel free to merge :)

bors r+

@pka just granted you bors permissions – can you try again?

bors r+


build.pyd

When running the command "python main.py configs/total3d.yaml --mode demo --demo_path demo/inputs/1" on Win10 platform, I got an Import Error. Judging by build.so file under the directory /Total3DUnderstanding/external/pyTorchChamferDistance/build, you might use unix system. But for windows, I guess I need the corresponding build.pyd file for running. Could you please offer this .pyd file?

Hi,
I did not find any build.pyd files. For the chamfer distance library, please refer to https://github.com/chrdiller/pyTorchChamferDistance

Before running the command "python main.py configs/total3d.yaml --mode demo --demo_path demo/inputs/1", the build.ninja file in /Total3DUnderstanding/external/pyTorchChamferDistance/build is like the figure below:

However, after running the command (on win10), the build.ninja turned to the figure below:

In the last 2 lines, you can find the mention on build.pyd. I guess it means the pyd file is needed in windows platform just as the build.so file in linux platform.  I think the build.pyd should be compiled from cpp source codes and it is necessary for building python module.
Since there is no build.pyd file, could you please offer one?


Removing --save from README

Codecov Report

Merging #3156 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #3156   +/-   ##
=======================================
  Coverage   92.52%   92.52%
=======================================
  Files          23       23
  Lines        1177     1177
  Branches      310      310
=======================================
  Hits         1089     1089
  Misses         68       68
  Partials       20       20

Continue to review full report at Codecov.

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

@manniL Thank you 😸


Auxiliary trace column builder simplification

The structure we currently have for constructing auxiliary trace columns is very complex. The basic idea of this structure was to build a set of hints during the construction of the main trace segment, and then use these hints to make auxiliary trace generation as fast as possible.
While this may be a very efficient way to do it (though this needs to be benchmarked), the amount of complexity it introduces for recording and managing hints is probably not worth it. So, I'm thinking we could get rid of the hint structure entirely and build auxiliary columns based only on the data available in the main trace.
The exact approach should probably figured out after #982 is addressed so that we know if handling log derivative-based multiset checks has some unique requirements.
This refactoring would also eliminate the need to address #446.

Closed by #1140.


SPF testing? Per postfixer?

Hi https://github.com/sumbach/postfixer has a bunch of tests for Postfix ensuring that e.g. DNS and SPF work alongside postfix.
Is this something you would consider in the remit of chef-postfix?
Thanks,
Martin.

Do you mean adding tests to check if these work well to the cookbook? Kinda like serverspec?

Yes, indeed, something like serverspec.

This is welcome as a PR.


Background label in dataset

There seems to be a mismatch in class labels :
I've noticed a "background" category with 300 examples that wasn't part of my dataset.

Could you help clarify how it's being used or point me to the relevant code?
I am training on a new dataset with 11 classes, and I'm concerned that the model might be receiving incorrect labels during training.

I guess there is a bug in the dataloader, class4 is not coming up in the dataset.

Can you show me the meta information (category and id) of your dataset and the custom dataset definition?


Gate release of client libraries on REST API merge to main

I recently discovered that we released a "stable" version of the FormRecognizer client libraries (in September) that we built using a REST API definition that was not in the "main" branch of azure-rest-api-specs.  In fact, the PR for this version  was only merged last week, after I discovered this situation and asked Joel to merge it.
https://github.com/Azure/azure-rest-api-specs/pull/20404
There was no real damage done in this particular case -- the PR was in good shape and could be merged as is.  But in general this seems like an anti-pattern.  Our SDK Guidelines say
✅ DO only target generally available service API versions when releasing a stable version of the client library.
And I don't think an api-version sitting in a PR should qualify as "generally available".
I know we want to allow development of a stable client library to begin before the GA REST API has been merged. But I think we need a gate before release of a stable client library that ensures it only depends on REST APIs that have been fully merged to main in azure-rest-api-specs.
I did a quick scan of the azure-sdk-for-net repo and found a few more cases like this, but only a handful. So again ... not a serious issue, but something I think we should catch and prevent going forward.

Here's a script I wrote to check the autorest.md files in azure-sdk-for-net for references to commits in azure-rest-api-specs that are not merged to main:
#!/bin/bash

repo=~/Projects/Azure/azure-rest-api-specs

find sdk -name 'autorest.md' | while read f; do
    hash=$(grep -i -e '\(raw.githubusercontent\|github\).com/azure/azure-rest-api-specs/' $f \
                  | sed 's|.*azure-rest-api-specs\(/blob\)\{0,1\}/\([^/]*\).*|\2|' | sort | uniq)
    for h in $(echo $hash); do
        echo "$h $f"
    done
done | grep -v -e '^\(master\|main\|tree\|issues\)' | \
while read h f; do
    if [ -z "$(git -C $repo cat-file -t $h 2>/dev/null)" ]; then
        echo "$h $f";
    elif [ -z "$(git -C $repo branch main --contains $h)" ]; then
        echo "$h $f";
    fi
done

and here's what it found:
2fd7dcd89afa70ff5ba7be88bee987da62099a28 sdk/formrecognizer/Azure.AI.FormRecognizer/src/autorest.md
f6fab392bec9dbb3ceeb01c4604eba6d929e0074 sdk/storage/Azure.Storage.Files.DataLake/src/autorest.md
f8c3f91da6a9ed64b687711af64e8d70cb500e1d sdk/storage/Azure.Storage.Blobs.Batch/src/autorest.md
4a93ab078fba7f087116283c8ed169f9b8e30397 sdk/storage/Azure.Storage.Queues/src/autorest.md
da15318e582f0cd1ea01e7a2556190c98aa1578f sdk/appcomplianceautomation/Azure.ResourceManager.AppComplianceAutomation/src/autorest.md
75a8d8dcc9f6d0ec626bdeb32f5154f20c8c61cd sdk/devcenter/Azure.Developer.DevCenter/src/autorest.md
e30976f6ccb058a36cd2f9d5160e1fd51f6c5d95 sdk/communication/Azure.Communication.Rooms/src/autorest.md
140b5b64350c17e0900034d66cee2d6623af3ea8 sdk/communication/Azure.Communication.MediaComposition/src/autorest.md
d0d60267975bf5823a9173ce0c926659bc9775bb sdk/communication/Azure.Communication.Chat/src/autorest.md
e5bc61526e11f9b51e1e098d71a730f1494bc2f8 sdk/synapse/Azure.Analytics.Synapse.Artifacts/src/autorest.md
50adac0106ba23718cb6b736d69cf834ae37f505 sdk/quantum/Azure.Quantum.Jobs/src/autorest.md

@dw511214992 let's take this as a requirement to SDK release app

In sdk release app, we can block sdk release when the spec PR is not merged.

@josefree do you think it's necessary to check whether the spec PR is merged before release sdks?

@josefree do you think it's necessary to check whether the spec PR is merged before release sdks?

Yes. this comes from feedback about the flow and how it is important that no SDK ships from a spec PR that is not merged in main.

will  check spec pr status in step3

This will also be an issue for the new cadl-location.yaml file that is used to pin a language sdk to a specific commit of a spec for cadl.
There are one thing here that we probably want to block the release pipeline on if they exist.

If the sha is not in the main branch
a.  We will need a way to override this in the rare event we ship from a hotfix branch.

There is another thing we probably want to block commit preferably or PR merge if we can't do commit.
2. If the spec repo doesn't match the language repo.  I.e. if the language repo is azure-sdk-for-net and the spec repo is azure-rest-api-specs-pr or vice versa.

move @m-nash 's comment to a new issue: https://github.com/Azure/azure-sdk-tools/issues/5387

will check spec pr status in step3

As the spec pr status checked in step3, and deploy on product. Other questions will track in new issues.


Message "PDF is loading..." isn't displayed when PDF is loading in Preview

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Launch the app
Log in with any account
Select any conversation
Attached a PDF and sent it
After PDF is loaded click on it

Expected Result:
Message as "PDF is loading..." is displayed when PDF is loading in Preview
Actual Result:
Message as "PDF is loading..." is displayed when PDF is loading in Preview
Workaround:
None needed, visual issue.
Platform:

Where is this issue confirmed?

Android

Version Number: 1.0.91-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

https://user-images.githubusercontent.com/44479856/131754867-ff91731a-b50d-4676-8c0f-781cb8d30ff8.mp4
Expensify/Expensify Issue URL:
View all open jobs on GitHub

Triggered auto assignment to @Dal-Papa (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Tagging @parasharrajat since he worked on this. I'm pretty sure the default text is Loading PDF... from the documentation so if we don't see it in the Android platform it might be that they didn't implement it for mobile ? We never explicitly specify the text ourselves.

Issue reproducible during KI retests

Bump to @parasharrajat otherwise this might be a :donothing: since it's at the library level.

I am on vacation. Back on 8.

@Dal-Papa Whoops! This issue is 2 days overdue. Let's get this updated quick!

@Dal-Papa Sorry for catching up late here.
We can update this if you want.
On native, we have a prop activityIndicator which can be set as activityIndicator={<Text>Loading PDF…</Text>} to match the web.
Also, We can change both native and web to show the same loading indicator if Loading PDF… is not friendly.
For example,

showing our FullScreenLoadingIndicator for native
activityIndicator={<FullScreenLoadingIndicator visible />}
showing our FullScreenLoadingIndicator for web.
 loading={<FullScreenLoadingIndicator visible />}

Awesome, thanks for the pointers @parasharrajat !

Issue reproducible during KI retests.

@Dal-Papa Whoops! This issue is 2 days overdue. Let's get this updated quick!

Let me know what needs to be done here. I can send a PR.

@Dal-Papa Huh... This is 4 days overdue. Who can take care of this?

@Dal-Papa Still overdue 6 days?! Let's take care of this!

Issue reproducible during KI retests.

Was OOO last week, will provide an update soon.


selectColumn incorrect position in v1.5

Problem apear when custom "recordHeight" property is set:
http://jsfiddle.net/5ncv1rb7/6/
I would suggest to change
if (obj.show.selectColumn) {
    html1 += ''+
    '

'+
    '	';
}

to
if (obj.show.selectColumn) {
    html1 += ''+
    '

'+
    '	';
}

You are right. This fixes the problem. Problem seems to be with columnGroups. I have fixed it for both selectColomn and expandColumn.


Remove version: Cisco.CiscoWebexMeetings version <IP_ADDRESS>

All urls in manifest result in 404s, no longer available
Microsoft Reviewers: Open in CodeFlow

URL: https://akamaicdn.webex.com/client/WBXclient-41.10.4-4/webexapp.msi
Response status code does not indicate success: 404 (Not Found).
(Automated message - build 727)


Add nn.Dropout for MDN

Ref https://github.com/r9y9/nnsvs/issues/112#issuecomment-1152931858

I'm gonna revert this PR for backward compatibility.


Enhancement: gcode viewer 3D realtime while printing

Would it be possible to make this a 3D Gcode viewer like the GCode viewer tab? I think this would look much cooler than the 2D one.

I think it's possible but it sounds like a separate plugin by itself. Unfortunately I have been super busy lately so I won't be able to build that plugin... :(


Add favicon

:wave: Can i contribute a little like this? thanks.

Thanks for submitting #59! I've assigned you to this issue :D


stream out histogram fragments to HTML

Commit Message: When rendering detailed histograms for HTML, it's friendlier to browsers if we enable them to parse and render each histogram as it comes out. The histogram data can be very large, so by putting each call to render a histogram in its own script tag, we (at low cost to the C++ server) can reduce the memory stored in the browser and also enable it to begin rendering before the server finishes streaming.
Additional Description:
Additionally, a performance regression was found in a late commit as part of #28988 where we switched from a low-precision fast serialization of doubles (absl::StrCat) to a high-precision slow serialization of doubles (absl::StrFormat("%.15g", ...). This resolves that issue using std::to_chars which is faster than absl::StrCat and is also high precision. The downside is it doesn't work on all platforms, so an intermediate high-precision medium-speed solution was found for Apple and GCC. The serialize-double-to-buffer functionality is moved out of Json::Streamer and into a new Buffer::Util namespace.
Latest Json histogram serialization performance:
------------------------------------------------------------------------
Benchmark                              Time             CPU   Iterations
------------------------------------------------------------------------
BM_HistogramsJson                   16.0 ms         16.0 ms           44

Risk Level:
Testing: /test/common/json/... test/common/buffer //test/server/admin/... /test/integration/admin_html/web_test.thml
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a

I'm guilty of co-mingling 2 PRs here -- one to improve the double-serialization performance and the other to stream html. If you prefer I can split them.

Thanks Raven!  --> Greg for senior maintainer approval.

/retest

#29500 is where the buffer changes are landing.

Note -- Greg's comments are on the double-precision change, and I responded, but the code changes are in #29500 .


Add source generation for new syntax of object fields

Purpose

Update ballerina examples submodule inside composer integration tests so that we are using examples updated for new syntax
Update source gen for the new syntax

:white_check_mark: Build ballerina-lang 365 completed (commit https://github.com/ballerina-platform/ballerina-lang/commit/93fa7f82f9 by @roonyh)


RTD failure on main

What happened?
logs
sphinx.errors.SphinxParallelError: RuntimeError: Non Expected exception in `/home/docs/checkouts/readthedocs.org/user_builds/xray/checkouts/7433/doc/user-guide/interpolation.rst` line 331

This seems real

XRef #7414

I agree with @kmuehlbauer that this might be a duplicate of #7414: as detailed there, scipy changed something in the interpolation code in their most recent version, which is the cause of the errors here. That apparently has to do with a specific combination of dtypes, so I'm guessing that that's why we don't hit that bug in CI.
In any case, pinning the scipy version to a slightly older version should avoid that bug for now.


[Bug report] Why the mjs file [app.f1603bd5.mjs] is in [\docs.vuepress\dist] folder ???

Description
Why the mjs file is in [\docs.vuepress\dist] folder ???
This file is not necessary, is it?
https://github.com/MoonLord-LM/MyPages/
Reproduction
https://github.com/MoonLord-LM/MyPages/tree/github-pages
Used Package Manager
npm
System Info
v2.0.0-beta.50

Uh, thanks for reporting. It's necessary, but used to be inside the assets sub dir. We tweaked the output config for SSR build, but also changed the client build. Should be fixed.


Sporadically incomplete snapshots

Describe the bug
Sporadically within Home Assistant the Blink camera preview images are incomplete. Only half of the jpeg files seems to be generated. The preview image in the lovelace cards is incomplete, as well as the file written to the media folder by my automation. I do have some errors in the logs from blink (see below), however those do not match the time if the problem actually occurs. I couldn't find any additional information or similar reports, so I hope you can help me here. Please let me know if any additional information is required to troubleshoot the issue. Thanks!
To Reproduce
It is a sporadic error, so I can't provide detailed steps how to reproduce. However, it happens sporadically when the following automation in Home Assistant is triggered:
- id: '1602096528961'
  alias: Benachrichtigung bei Türklingel
  description: ''
  variables:
    create_path: /media/Blink/Eingang_{{ now().strftime("%Y%m%d-%H%M%S") }}.jpg
    send_path: '{{ create_path | replace(''/media'',''/media/local'') }}'
  trigger:
  - type: not_opened
    platform: device
    device_id: 06887d44070511eba0223f8f74a89d06
    entity_id: binary_sensor.openclose_doorbell
    domain: binary_sensor
  condition: []
  action:
  - service: notify.iphones
    data:
      title: Haustür
      message: Es hat geklingelt!
  - service: blink.trigger_camera
    data:
      entity_id: camera.blink_eingang
  - delay:
      hours: 0
      minutes: 0
      seconds: 8
      milliseconds: 0
  - service: blink.blink_update
    data: {}
  - delay:
      hours: 0
      minutes: 0
      seconds: 2
      milliseconds: 0
  - service: camera.snapshot
    data:
      filename: '{{ create_path }}'
    target:
      entity_id: camera.blink_eingang
  - service: notify.iphones
    data:
      title: Haustür
      message: Schau wer da ist!
      data:
        image: '{{ send_path }}'
  - service: blink.blink_update
    data: {}
  mode: single

Expected behavior
The services blink.tigger_camera and blink.blink_update should always result in a complete image download to Home Assistant.
Home Assistant version:
Home Assistant 2022.9.7
Supervisor 2022.09.1
Operating System 9.0
Frontend 20220907.2 - latest
Log Output/Additional Information
2022-09-28 14:00:49.456 ERROR (SyncWorker_0) [blinkpy.sync_module] Could not extract camera info: {'message': 'Camera not found', 'code': 500}
2022-09-28 14:00:49.458 WARNING (SyncWorker_0) [blinkpy.camera] Could not find thumbnail for camera unknown
2022-09-28 14:00:49.488 ERROR (SyncWorker_4) [blinkpy.sync_module] Could not extract camera info: {'message': 'Camera not found', 'code': 500}
2022-09-28 14:00:49.491 WARNING (SyncWorker_4) [blinkpy.camera] Could not find thumbnail for camera unknown
2022-09-28 14:00:49.852 ERROR (SyncWorker_6) [blinkpy.auth] Expected json response from https://rest-e001.immedia-semi.com/network/156379/camera/unknown/config, but received: 406: Not Acceptable
2022-09-28 14:00:49.856 ERROR (SyncWorker_6) [blinkpy.sync_module] Could not extract camera info: None
2022-09-28 14:00:49.860 WARNING (SyncWorker_6) [blinkpy.camera] Could not find thumbnail for camera unknown

Experiencing this too :(


some log messages are getting output to stdout

lines like "llama_new_context_with_model: max tensor size =    87.89 MB,," which are coming from the underlying C code are getting put into stdout instead of stderr.

This is SO frustrating. I'm very open to help figuring out how to stop this!
I think it happens with both llm-llama-cpp and llm-gpt4all.


Campaigns layout broken in Safari

Unscrollable and missing toolbar under preivew.
Campaigns in Safari:

Note there is also the same issue for safari in AssetAdmin

Ready for review


Complete the CI/CD pipelines

We would like to have online hosting for "prod" and "develop" instances of the Remix plugin. We need DNS entries and respective hosting for instances of the plugin UI app and API service (ECS hosted).
We would like to have automated CI/CD pipelines for build & deployment of remix plugin for both 'master' and 'develop' branches.
Develop instance: (hosted in "Nubia-nonprod" AWS account)

https://cairo-remix-dev.nethermind.io - plugin UI (React app) -> S3 static app
https://cairo-remix-api-dev.nethermind.io - plugin API (Rocket webserver) -> ECS hosted
https://starknet-devnet-dev.nethermind.io - devnet RPC instance (currently Python lib, want to move to Rust-based devnet) - how do we host this???
We would like to have GitHub Actions that build & upgrade points 1. and 2. above when PR is merged to develop branch.

Prod instance: (hosted in "nethermind" AWS account)

https://cairo-remix.nethermind.io - plugin UI (React app) -> S3 static app (http://starknet-remix-plugin-web.s3-website.us-east-2.amazonaws.com)
https://cairo-remix-api.nethermind.io - plugin API (Rocket webserver) -> ECS hosted
We would like to have GitHub Actions that build & upgrade points 1. and 2. above when PR is merged to master branch.

Once we have the above working, we would raise a PR to Remix project to repoint the Starknet plugin to the "prod" endpoint (point 5. above)

For point 6, maybe https://cairo-remix-api.nethermind.io/ would be best, in case we ever change rocket for something else.

Had a chat with @gehlotanish adn agreed the scope. @gehlotanish likely to get back to this task in w/c 4 Sep.

@stranger80 I have merged the PR
GH Action pipeline added.

Had a chat with @gehlotanish to align on the behaviour of the Actions. Also reported that the Deploy step for the Plugin API service is failing.

S3/ECS deployment is now operating from develop branch for dev environments.
The API service container is grinding to a halt after the first call to a functional API (eg. /cairo_version) - this is most likely due to the fact the first call to the compiler triggers "cargo run" which needs to build the cairo compiler first. This needs to be rectified:

Either build cairo during image build and try again
or redesign the api service to not call "cargo run" but instead have a respective cairo compiler installed in image and called directly


[BREAKING] Remove GlennBotList

Message by the list owner:

glenn bot list will be offline for the foreseeable future. currently i have no intention to bring it back after what apparently just happened

They changed their mind apparently, and it will come back in the future.


Treat amount and fees as u64 (positive integers)

Fixes https://github.com/breez/c-breez/issues/400

@ok300 is this ready for review? Asking because it is still marked as WIP.

@roeierez wanted to first test the new version myself, locally with c-breez. Just now finished my tests, ready for review.
Erdem already reviewed and said, from his side it's ready for merge.

FYI the scenarios I tested are:

new Android image, restore previous wallet seed

result: ok (full history shown, incoming and outgoing payments)

previous master build on an Android image, keep image but install new apk (of this PR), re-open wallet

result: ok (same as above)

with this apk version, make outgoing payment (negative entries in history)

result: ok (new negative entries appeared as expected in history)


[C++] Does the dataset API support compression & appending to existing parquet files?

Describe the usage question you have. Please include as many useful details as  possible.
I am streaming some time series data to parquet files with the following aspects:

I write the data out batch by batch in order to save memory footprint
The data can optionally partitioned by {hour, minute}.

I have been using the parquet::arrow::FileWriter::WriteRecordBatch, which can append batch to existing parquet files but doesn't support partition.
So I tried the Dataset API. It seems that

ExistingDataBehavior can only overwrite or delete existing files, instead of appending
I don't know how to turn on the Snappy compression for the dataset file writer

arrow::Status append_a_batch(const std::shared_ptr<fs::FileSystem>& filesystem, const std::shared_ptr<arrow::RecordBatch>& batch) {
    // Write using the Dataset API.
    std::vector<std::shared_ptr<arrow::RecordBatch>> batches{batch};
    auto dataset = std::make_shared<ds::InMemoryDataset>(batch->schema(), batches);
    ARROW_ASSIGN_OR_RAISE(auto scanner_builder, dataset->NewScan());
    ARROW_ASSIGN_OR_RAISE(auto scanner, scanner_builder->Finish());
    // Deliberately not partition the data, in order to append to the same file.
    auto partition_schema = arrow::schema({});//arrow::schema({arrow::field("part", arrow::utf8())});

    auto partitioning = std::make_shared<ds::HivePartitioning>(partition_schema);

    auto format = std::make_shared<ds::ParquetFileFormat>();

    // Q1. how to enable compression?
    ds::FileSystemDatasetWriteOptions write_options;
    write_options.file_write_options = format->DefaultWriteOptions();
    write_options.filesystem = filesystem;
    write_options.base_dir = base_dir;
    write_options.partitioning = partitioning;
    write_options.basename_template = "part{i}.parquet";

    // Q2. how to append to existing files?
    write_options.existing_data_behavior = ds::ExistingDataBehavior::kDeleteMatchingPartitions;
    ARROW_RETURN_NOT_OK(ds::FileSystemDataset::Write(write_options, scanner));
}

arrow::Status main() {
    ARROW_ASSIGN_OR_RAISE(auto filesystem, fs::FileSystemFromUriOrPath(base_dir));
    ARROW_RETURN_NOT_OK(filesystem->CreateDir("/tmp/sample"));
    auto& batch = some_code_generating_one_batch();

    // writes to /tmp/sample/part0.parquet
    append_a_batch(filesystem, batch);

    // can't append to /tmp/sample/part0.parquet
    append_a_batch(filesystem, batch);
}

If that's not possible, I have to wait until I have a full partition in memory before flushing to the file, which uses more memory.
Please advise. Thanks.
Component(s)
C++

Just answer the second question, for compression:
class ARROW_DS_EXPORT ParquetFileWriteOptions : public FileWriteOptions {
 public:
  /// \brief Parquet writer properties.
  std::shared_ptr<parquet::WriterProperties> writer_properties;

  /// \brief Parquet Arrow writer properties.
  std::shared_ptr<parquet::ArrowWriterProperties> arrow_writer_properties;

 protected:
  explicit ParquetFileWriteOptions(std::shared_ptr<FileFormat> format)
      : FileWriteOptions(std::move(format)) {}

  friend class ParquetFileFormat;
};

Maybe you can config compression in parquet::WriterProperties.

Just answer the second question, for compression:
class ARROW_DS_EXPORT ParquetFileWriteOptions : public FileWriteOptions {
 public:
  /// \brief Parquet writer properties.
  std::shared_ptr<parquet::WriterProperties> writer_properties;

  /// \brief Parquet Arrow writer properties.
  std::shared_ptr<parquet::ArrowWriterProperties> arrow_writer_properties;

 protected:
  explicit ParquetFileWriteOptions(std::shared_ptr<FileFormat> format)
      : FileWriteOptions(std::move(format)) {}

  friend class ParquetFileFormat;
};

Maybe you can config compression in parquet::WriterProperties.

Much appreciated!
Configured compression below seems working.
ds::FileSystemDatasetWriteOptions write_options;

auto format = std::make_shared<ds::ParquetFileFormat>();
auto pq_options = std::dynamic_pointer_cast<arrow::dataset::ParquetFileWriteOptions>(format->DefaultWriteOptions());
pq_options->writer_properties = parquet::WriterProperties::Builder()
        .created_by("1.0")
        ->compression(arrow::Compression::SNAPPY)
        ->build();

write_options.file_write_options = pq_options;
write_options.file_write_options = format->DefaultWriteOptions();
write_options.filesystem = filesystem;
write_options.base_dir = base_dir;
write_options.partitioning = partitioning;
write_options.basename_template = "part{i}.parquet";

Still don't know if Q1 is possible.

As for Q1, I guess you can:

TableScan(using dataset) with Partition
TableSink(using dataset) with Partition

But I don't know if there are more convinient way to solve it

TableScan(using dataset) with Partition
TableSink(using dataset) with Partition
But I don't know if there are more convinient way to solve it

This would be the easiest way I think.  It will require you to create a plan (scan -> write).
Otherwise you can use arrow::dataset::internal::DatasetWriter directly but it's not part of the public API and so there are no real guarantees for backwards compatibility (although there are no plans to change it at the moment that I am aware of).

https://github.com/apache/arrow/blob/apache-arrow-12.0.0/cpp/examples/arrow/execution_plan_documentation_examples.cc#L648 might be a good example.


Protect APIs

@camillemonchicourt, what do you want exactly to protect ?
We can make an exhaustive check but I think that all data accessible without login and without access rights is public data.

OK I had in mind that they shouldnt be accessible to anyone that has the URL.
Maybe something like an API KEY but indeed as public datas, it may dont make sense.
But not sure we can allow anyone to use them as he wants.
To be discussed.

OK to let it open.


feat: bridge v2 deposit

@Elaixzar This is a method to perform a deposit on the v2 bridge.
To the extent possible I've tried to reuse existing sdk logic, though my knowledge of its intricacy is not sufficient to know if some of my code is duplicating other parts of the sdk. Do let me know if you want me to refactor anything.
I've made a util to convert addresses back to their public key bytecode. It's not in the evm serializer since I think this will be used for every chains.

@easteregg Once this is merged and release you should be able to use the same evmConnect.bridge() function and passing a boolean to trigger a deposit on the v2 bridge. See my unit test for an example:
const sk=process.env.TEST_ACCOUNT!
const provider = new ethers.providers.JsonRpcProvider(process.env.TEST_RPC);
const signer = new ethers.Wallet(sk).connect(provider);
const { wait }=await evmConnect.bridge("0xEC28e6671Bcb93979DFB1734e5240c0cF52bC152", BridgeNetworks.Binance, "xGTT", "10", signer, true)
const { transactionHash }=await wait()
console.log(`successful deposit: ${transactionHash}`)


Add Greater Khingan Mountains Vocational College

The official URL http://www.dxalu.org.cn
The curricula for the Software Engineering program at http://www.dxalu.org.cn/ElectronicEngineering/contents/189/14852.html
The school email system https://yojigen.ac.cn

@mouyase I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for the understanding!


Loading characters?

Is there any way I can load the character I made in oobabooga webui?
Really nice job btw, thanks!

I will look into this 👍

This would be a massive thing, character support in general would really enhance this,

Added, enjoy!

Would it be possible for it to be set for it to post the 'Greeting' that a lot of characters make use of if a character is loaded, or as a flag? A lot of them depend on that for context and characterization.

I see what you mean. Unfortunately I don't think character greetings are accessible through oobabooga's API server (which is what my code uses). So not sure how I would do this.

It could be possible for it to load the character itself, and then pass that to ooba. I know sillytavern does it like that, instead of loading the character into ooba itself.

Beyond this it also goes against the functionality of discord-llm-chatbot. The bot is only meant to send messages when responding to a user prompt. Sending an "automatic message" for the greeting doesn't make sense as a feature IMO.
As an alternative you could change the bot's Discord status message to add character context. Just change github.com/jakobdylanc/discord-llm-chatbot to whatever you want on this line:
https://github.com/jakobdylanc/discord-llm-chatbot/blob/0d609f3474095f8826692b63394eef5370865670/llmcord.py#L48

Beyond this it also goes against the functionality of discord-llm-chatbot. The bot is only meant to send messages when responding to a user prompt. Sending an "automatic message" for the greeting doesn't make sense as a feature IMO.
As an alternative you could write some character context in the bot's Discord activity message. Just change "github.com/jakobdylanc/discord-llm-chatbot" to whatever you want on this line:
https://github.com/jakobdylanc/discord-llm-chatbot/blob/0d609f3474095f8826692b63394eef5370865670/llmcord.py#L48

I just made this easier to do with a new CUSTOM_DISCORD_STATUS config option.


build is broken

vulcan starter works

Sorry but you have to be more factual whe opening issues, otherwise we won't be able to help. Please also try to keep you initial message when you edit the issue, so we understand better


Update testdata to remove invalid dependsOn reference in cluster8

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

Project coverage is 93.57%. Comparing base (689f964) to head (7138fff).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #820      +/-   ##
==========================================
+ Coverage   93.55%   93.57%   +0.02%
==========================================
  Files          20       21       +1
  Lines        2249     2257       +8
==========================================
+ Hits         2104     2112       +8
  Misses        145      145

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


MasterKey fails when Algorithm changes

If the Symmetric Algorithm is altered after the system has been initialized, then it it cannot be correctly generated when restarting. It is possible to fix this, by manually set the Symmetric Algorithm back to the original by altering the database manually, and thus recover the system. However, a better and more robust solution must be found.
It is the goal of this bug report to fix it, by adding a custom property (CWS supports this already), and use this to control the setting of the MasterKey, and then warn that changing the Symmetric Algorithm after the system is used, can be dangerous. It is best to set the Key size at initial setup, and leave it at this. Nevertheless, the system must always be stable.

The issue has been resolved. Not quite how it was expected - but for a good reason. If the MasterKey should save the information in special settings, and thus also have them persisted, then they would still be possible to be tampered with by an administrator, since the settings request would allow that.
Adding the settings as new standard values seemed overkill, since it required that new rules should be applied, and it seemed strange that the PBE Algorithm, PBE Iterations and CharSet all were duplicated.
Finally, it also required that the MasterKey would have a dependency on the database, which again meant that it would not be tamper free. So, a simple solution was found, which was to hard code the values for the PBE Algorithm, PBE Iterations & CharSet to the system default, which already have been chosen to be fairly good, for most production environments.


Bitcanna logo

If you have logos with rounded format, they should be privileged (to keep a uniformity in the site)!
For example I could find this on the google which would be according me better :  https://pbs.twimg.com/profile_images/1258755655550238721/8prvUSqO.jpg
Without text : https://www.supmedi.com/wp-content/uploads/2020/05/Logo-BitCanna_628x628px-481x270.png
Thanks

Oh also, the name of .svg and .png is "asset_ symbol_lowercase.png", can you correct it , thanks !

Hi @IbrarMakaveli
Thank you for your answer, I will modify this and make a new PR.


Bar chart remains muted with interactive legend

This pulls in a fix from PatternFly charts to address an issue with our bar charts.
https://issues.redhat.com/browse/COST-924

Codecov Report

Merging #1826 (7eec876) into master (3d6aa59) will increase coverage by 1.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1826      +/-   ##
==========================================
+ Coverage   73.16%   74.16%   +1.00%
==========================================
  Files         327      327
  Lines        5354     5856     +502
  Branches      996     1309     +313
==========================================
+ Hits         3917     4343     +426
- Misses       1332     1495     +163
+ Partials      105       18      -87

Impacted Files
Coverage Δ

...omponents/charts/dailyCostChart/dailyCostChart.tsx
7.09% <ø> (-1.18%)
:arrow_down:

...ponents/charts/dailyTrendChart/dailyTrendChart.tsx
7.74% <ø> (-1.13%)
:arrow_down:

...sync/permissionsComponent/permissionsComponent.tsx
75.00% <0.00%> (-10.72%)
:arrow_down:

src/components/i18n/i18nProvider.tsx
57.14% <0.00%> (-9.53%)
:arrow_down:

src/pages/state/maintenance/maintenanceState.tsx
66.66% <0.00%> (-8.34%)
:arrow_down:

.../costModels/costModelsDetails/bottomPagination.tsx
82.60% <0.00%> (-7.40%)
:arrow_down:

src/store/common.ts
81.81% <0.00%> (-7.08%)
:arrow_down:

...ponents/reports/reportSummary/reportSummaryAlt.tsx
52.94% <0.00%> (-7.06%)
:arrow_down:

src/api/reports/reportUtils.ts
27.77% <0.00%> (-6.71%)
:arrow_down:

src/api/forecasts/forecastUtils.ts
28.12% <0.00%> (-6.50%)
:arrow_down:

... and 106 more

Continue to review full report at Codecov.

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


creatingRow state not able to be hoisted

Discussed in https://github.com/KevinVandy/mantine-react-table/discussions/155

Originally posted by ctretyak October  3, 2023
I found only 3 mentions and none of them is calling it. It doesn't work?
I'd like to subscribe when table.setCreatingRow / setEditingRow is called. onEditingRowChange works perfectly, but onCreatingRowChange is never called

fixed by #bab0c546836a4bb919227e4ded52a98f8399bce8


feat: report custom pre/post processing

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


Highlight to Redact Not Working

Describe the bug in current situation
An OOTB feature allows users to left-click and drag across text to select to redact it (highlight to redact). However, when selecting text to redact using this feature, the redaction isn't being applied, and no FOIPPA section model is being displayed.
Link bug to the User Story
Impact of this bug
Describe the impact, i.e. what the impact is, and number of users impacted.
Medium
Chance of Occurring (high/medium/low/very low)
High
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
Test-Marshal
Identified on EDU-2023-67435
Steps to Reproduce
Steps to reproduce the behavior:

Go to a page on the request in the document reviewer containing text
Left-click the beginning of the text, hold left-click, and drag across the text

Private Zenhub Image

Release left-click
See error - when releasing left click, the highlighted text should be redlined for redaction, and the FOIPPA section model should be displayed to apply a FOIPPA section

Actual/ observed behaviour/ results
Cannot apply redaction and FOIPPA section when using highlight to redact feature
Expected behaviour
A clear and concise description of what you expected to happen. Use the gherking language.
GIVEN a user has selected text to redact using the highlight to redact feature (left-click and drag across text)
WHEN the user releases left click
THEN the redline box should be applied, and the FOIPPA section model is displayed
Screenshots/ Visual Reference/ Source
If applicable, add screenshots to help explain your problem. You an use screengrab.

Feature disabled as part of #4565 - closing ticket.


Everything Is One Word

Review on Google Play:

I have but one greivance. It dosen't add the / , so everything I type is one word. You gotta put the slash inbetween. Example: "hello world" .... . .-.. .-.. --- / .-- --- .-. .-.. -.. "helloworld" .... . .-.. .-.. --- .-- --- .-. .-.. -..

Fixed with 101d8cd


CDAP-12079 Reduce kafka request timeout to 15 seconds, from the default of 305.

https://issues.cask.co/browse/CDAP-12079
Reduce kafka request timeout to 15 seconds, from the default of 305 seconds.

Changed base branch to release/3.0


GH-35235: [CI][Python] Pandas upstream_devel and nightlies are failing

Closes: #35235

@github-actions crossbow submit test-conda-python--pandas-


Sometimes the thread name is wrong in the log

The attachment test3.zip contains a rust project with two mods.
Each of these two modules has a "connect" function, which creates a named thread in which it connects to "wss: //echo.websocket.org" and sends a ping every second. The websocket server will response with the same message.
Except for the names, these two mods are almost the same.
log4rs is used in the project:
refresh_rate: 30 seconds
appenders:
  stdout:
    kind: console
    encoder:
      pattern: "[{d(%Y-%m-%d %H:%M:%S.%3f)} {T:>16.16} {M:16.16} {L:>4.4} {l}] {m}{n}"

root:
  level: info
  appenders:
    - stdout

Sometimes the thread name in the log is wrong as below. It only happens when receiving messages.

I have simplified the test project as much as I can, I'm sorry if it has not been minimized.
test3.zip

I don't have much experience with async_std but I think this is probably caused by it.
If you add println!("On thread: {}", std::thread::current().name().unwrap_or("unnamed")); before line 30 in mod1 and mod2. You will see that the info macros are running on the threads that they are reporting.

@ngugc did @SarthakSingh31's comment resolve your issue?

Yes, it's caused by asyn-std.
I though it was like C++'s coroutine, but it's not.
The task is not bound to the thread who creates it.
Thanks! @SarthakSingh31 . I'll try if tokio has the same behaviour.

Glad to hear it.


[ZeitBridge] Re-add paywall workaround

Additionally to the Googlebot User-Agent, a Googlebot IP address has to be used. For now, we can use X-Forwarded-For for this.

Does this workaround work for you? Here I still only get the teaser instead of the full article.

Too bad, but filtering out a single IP probably was too easy ... Thanks for the feedback and trying to fix this.


New icon should be retina-friendly

The new menu bar icon is nice, but I would like to see a retina variant as well :)

also there should be an inverted version which looks decent in OS X dark mode

Agreeeee.
But I'm still using MacBook Air(yes, non-retina), it may takes some time.
I should test it on my coworker's rMBP. :(

Fixed by #34


启动多窗口的时候非常卡顿

Found an issue or bug with electron-vue? Tell me all about it!
Questions regarding how to use electron or vue are likely to be closed as they are not direct issues with this boilerplate. Please seek solutions from official documentation or their respective communities.
Describe the issue / bug.
#启动多窗口的时候非常卡顿
How can I reproduce this problem?
#
If visual, provide a screenshot.
#
Tell me about your development environment.

Node version:
NPM version:
vue-cli version: (if necessary)
Operating System:

If you are looking to suggest an enhancement or feature, then feel free to remove everything above.

nothing about your problem? No reproduce? then you say a J8?

我曹 我说 启动多窗口的时候 启动缓慢，听不懂？

你看一下任务管理器是不是有很多electron进程 ，开发模式下 Ctrl+C 并不会杀掉进程。
看看是不是我说这个问题


Application throws an exception when partner joins

IndexOutOfRangeException
Anyone know how I can resolve this issue?

Oop, thanks for the heads-up!
I don't know where to begin with reproducing your issue, but there's a few clues that something's fricked.
This method we pulled from the LiveSplit code is where the error actually occurs. But before that, alyx-multiplayer identifies your Alyx map name as 0x7FF..., when it should be giving you a plaintext map name. Also, the localHead index # is printed twice!
A few questions:

Are you accidentially running two or more instances of HL:A or alyx-multiplayer on the same machine?
Are you running alyx-multiplayer as administrator? (you should be)
What debugging steps have you attempted so far?

If you can, try to get that map name to display correctly before having the other player connect.

Oop, thanks for the heads-up!
I don't know where to begin with reproducing your issue, but there's a few clues that something's fricked.
This method we pulled from the LiveSplit code is where the error actually occurs. But before that, alyx-multiplayer identifies your Alyx map name as 0x7FF..., when it should be giving you a plaintext map name. Also, the localHead index # is printed twice!
A few questions:

Are you accidentially running two or more instances of HL:A or alyx-multiplayer on the same machine?
Are you running alyx-multiplayer as administrator? (you should be)
What debugging steps have you attempted so far?

If you can, try to get that map name to display correctly before having the other player connect.

Are you accidentially running two or more instances of HL:A or alyx-multiplayer on the same machine?
Nope only one copy
Are you running alyx-multiplayer as administrator? (you should be)
Yes
What debugging steps have you attempted so far? Restarting your computers, checking the Alyx console log, etc etc
Restarted the host PC & partner PC, opened closed alyx multiple times on both devices, restarted the Alyx-multiplayer multiple times (again on both devices), tried over VPN (hense why I left the IP addresses visable, not a internet IP)
What does the alyx-multiplayer output look like before the exception occurs?
What you see in the screenshot

I have tried again launching the alyx-multiplayer app and the map name will not appear in plaintext.

Would you be down to debug this issue with me over Discord voice call sometime? I'm Kube # four five five six, if ya wanna shoot me a message.
Assuming we figure it out, I'll update this Issue with our solution.

Sure I will send you an invite :)

After successfully debugging the issue, we came away with a few useful commands to help trouble shoot issues.
Firstly make sure to enable the console within Half-Life Alyx, do so by right clicking Half-Life: Alyx (within Steam) > Properties > enter "-console -vconsole" to Launch Options text field. & Apply/Close.
Then once console has been enabled proceed to launch the game.
Once Half-Life Alyx is running press the tilde key to bring up the console.
First check the mod is configured correctly by typing "addon_list" within HL Alyx console
Output should be the following:

Once you have confirmed the mod is configured correctly, start a game by issuing the following command in the console: addon_play a1_intro_world
Within the console you should see your location reference & your partners location ref.

Another gotcha is if you click within the console you might pause the plugin, pressing enter can resovle this issue @ZacharyTalis perhaps you can elaborate on this nuance?


Botbuilder docs do not include MessageFactory

https://github.com/Microsoft/botbuilder-js/tree/master/doc/botbuilder
is missing MessageFactory although it is used in the wiki.

I'm going to remove those docs to help avoid further confusion. The real reference docs are over here:
https://docs.microsoft.com/en-us/javascript/api/botbuilder-core-extensions/messagefactory