Fix yarn workspace

Tracking issue for https://github.com/prisma/prisma/issues/5266#issuecomment-767656190
Clone blitz-js/blitz
yarn
yarn build
cd examples/auth
blitz start
# Open page in browser
# See Error: @prisma/client did not initialize yet. Please run "prisma generate" and try to import it again.

Hey @flybayer, I have tried to reproduce this by following your instructions but I receive the following error when running yarn start in /examples/auth.
blitz/examples/auth on  canary  via ⬢ v14.15.3 on ☁  (eu-central-1) on ☁<EMAIL_ADDRESS>❯ yarn start                                                                                (base)
yarn run v1.22.10
$ blitz start
You are using beta software - if you have any problems, please open an issue here:
      https://github.com/blitz-js/blitz/issues/new/choose

warn  - You have enabled experimental feature(s).
warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use them at your own risk.

Error: Could not find a production build in the '/home/will/Prisma/blitz/examples/auth/.blitz/caches/build/.next' directory. Try building your app with 'next build' before starting the production server. https://err.sh/vercel/next.js/production-start-no-build-id
    at Server.readBuildId (/home/will/Prisma/blitz/node_modules/next/dist/next-server/server/next-server.js:146:355)
    at new Server (/home/will/Prisma/blitz/node_modules/next/dist/next-server/server/next-server.js:3:120)
    at createServer (/home/will/Prisma/blitz/node_modules/next/dist/server/next.js:2:638)
    at start (/home/will/Prisma/blitz/node_modules/next/dist/server/lib/start-server.js:1:323)
    at nextStart (/home/will/Prisma/blitz/node_modules/next/dist/cli/next-start.js:19:233)
    at /home/will/Prisma/blitz/node_modules/next/dist/bin/next:27:115
'next start' failed with status code: 1
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I have also tested the yarn workspace behaviour with our e2e test and upon running yarn in the workspace root prisma does get generated. If this is still an issue for you, could you please try provide a minimal reproduction.

@williamluke4 the command to start the server is now yarn dev or blitz dev. This just changed last week on canary, sorry about that!

Ok, so I've done some digging and added a log to our postintall hook (Postinstall Trigger:). It seems that our postinstall hook is correctly being trigger once when running yarn, but it seems that something else is also calling prisma generate.
The only thing I can assume is that Blitz is also trying to generate the client on install (@flybayer can you confirm this).
[sqlite3] Success: "/home/will/Prisma/blitz/node_modules/sqlite3/lib/binding/napi-v3-linux-x64/node_sqlite3.node" is installed via remote
node-pre-gyp info ok
verbose<PHONE_NUMBER>64 Prisma schema loaded from examples/auth/db/schema.prisma

✔ Generated Prisma Client (2.17.0-integration-postinstall-test.1) to ./examples/auth/node_modules/@prisma/client in 129ms
You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client

import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()

warn Versions of<EMAIL_ADDRESS>and<EMAIL_ADDRESS>don't match.
This might lead to unexpected behavior.
Please make sure they have the same version.
verbose<PHONE_NUMBER>04 Prisma schema loaded from examples/auth/db/schema.prisma

✔ Generated Prisma Client (2.17.0-integration-postinstall-test.1) to ./examples/auth/node_modules/@prisma/client in 131ms
You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client

import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()

warn Versions of<EMAIL_ADDRESS>and<EMAIL_ADDRESS>don't match.
This might lead to unexpected behavior.
Please make sure they have the same version.
verbose<PHONE_NUMBER>54 Prisma schema loaded from examples/auth/db/schema.prisma

✔ Generated Prisma Client (2.17.0-integration-postinstall-test.1) to ./examples/auth/node_modules/@prisma/client in 151ms
You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client

import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()

warn Versions of<EMAIL_ADDRESS>and<EMAIL_ADDRESS>don't match.
This might lead to unexpected behavior.
Please make sure they have the same version.
verbose<PHONE_NUMBER>41 Prisma schema loaded from examples/auth/db/schema.prisma

✔ Generated Prisma Client (2.17.0-integration-postinstall-test.1) to ./examples/auth/node_modules/@prisma/client in 142ms
You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client

import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()

Postinstall Trigger:yarn --verbose
success Saved lockfile.
$ npm rebuild husky && patch-package
rebuilt dependencies successfully
patch-package 6.2.2
Applying patches...
<EMAIL_ADDRESS>✔
Done in 387.60s.

full log; relevant output is right at the end

@williamluke4 interesting. Blitz definitely isn't generating the client. Maybe a bug in yarn where it's calling postinstall twice?

Maybe a bug in yarn where it's calling postinstall twice?

Don't think so because the postinstall trigger is only logged :point_up: once

https://github.com/williamluke4/blitz/tree/fix/prisma-postinstall

I just tried out @williamluke4's fix with the following steps:
yarn install
yarn build
cd exmaples/auth
yarn
yarn build
yarn dev

and it works.
Without the yarn build in the examples/auth folder, it errored that the manifest could not be found.

yes, I confirmed his fix works for me too


Dagger installation options: Drop the shell script

I think the executable script used with curl isn't really deserving that project as there were many fuds back in the days when Docker was installable using the same mechanism.
Having, brew, binary and source method is by far enough IMHO
putting also the fact that this method (shell script) will definitely raise at some point, security concerns

Curious to know what other people think regarding the trade-off between convenience and security. I am fine to deprecate if enough think the binaries + homebrew are enough.

Closing this here, we'll track it from https://github.com/dagger/dagger/issues/702 instead (this is about dagger/dagger, not examples).


TabBar background changed to "white" then how to change Tab bar title color from default white to another color

Current behaviour

Expected behaviour

Code sample
For Syntax Highlighting check this link

Screenshots (if applicable)

What have you tried

Your Environment

software
version

ios or android

react-native

react-native-tab-view

react-native-gesture-handler

react-native-reanimated

node

npm or yarn

by setting labelStyle prop of TabBar


Pass extra keyword arguments to format_names

My use case is to be able to pass the et_al argument to limit the number of names

Thanks! I'll have to deal with #78 and #80, but then, this can be merged and released


[CI] Add a Conda/AArch64 build

Punting on this since there's some odd cross-compile build (both for linux-64 -> linux-aarch64 and osx-64 -> osx-aarch64).

This was for testing the conda package, I don't think we'll end up doing this for now. It does work upstream.
The conda package builds in this repo need updating anyways since they're way out of sync with the actual feedstock


The 4th image is hard to understand

This image is difficult to understand:

The article describes that we have the following entities:

CA
factory
technician
device

The CA signs the factory's cert, the factory signs the technician's cert, and the technician sign's the device's cert.
Does the image show that both the Factory and the Technician sign certificates of the device(s)?
Does it mean that the device has 2 certificates - only issued by the Factory, and the other one issued by the Technician?
Or does the Device certificate have two parents?
My request is to provide a better description of this image explaining the raised issues.

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

ID: 4229389d-0ea1-9f7b-db38-049ab3beecc1
Version Independent ID: 2d979405-e7cc-a522-d736-2fa563a777ff
Content: Concepts of Azure IoT Hub X.509 security
Content Source: articles/iot-hub/iot-hub-x509ca-concept.md
Service: iot-hub
GitHub Login: @eustacea
Microsoft Alias: eustacea

Hi @marcinjahn , thanks for bringing this to our attention. I have assigned the issue to the content author to evaluate and update this doc

Hello @marcinjahn, thank you for the question. The device has the full certificate chain, which it presents to IoT Hub. This certificate chain contains the root CA and all the intermediate CAs down to the unique device certificate. So the device will have a record from each step of the process and can trace its history back to the root: Company CA -> Factory CA -> Technician CA -> device certificate.
Does that clarify the diagram?
I'm also working on updates to the article to explain these concepts better and am asking for clarification about exactly who would put what on each device when, but in general the device needs to have all of the certs in its chain to be able to authenticate to IoT Hub.

Hi @kgremban, thanks for the answer :) The most confusing part for me is in the middle of the picture, where the arrow goes from Factory's private key to the devices. It looks like the factory signs the device's certificate. The same kind of arrow is drawn on the technician's side. It is not clear if both of them (factory and technician) sign the device's certificate, or if it is just the technician who does that. From your response I understand that the factory does not actually sign device's cert. It only signs technician's cert. In such case, the diagram is a bit confusing :)

Hi again @marcinjahn. I got some more information on the diagram and your interpretation is correct in that both the factory and the technician sign the device's certificate. The device has its public key which is presents at each step of the supply chain to get signed by the private keys of the factory and the technician. These signatures get included in the final certificate chain along with the device's public key.
In this scenario, a device connecting to IoT Hub would present a certificate chain with all the following information:

Company X public key
Factory Y public key, and SignatureYX (public key Y signed by private key X)
Technician Z public key, and SignatureZY (public key Z signed by private key Y)
device A public key, and SignatureAY (public key A signed by private key Y), and SignatureAZ (public key A signed by private key Z)

Thanks for sticking with me as I track down all these nitty details.
#reassign:kgremban

I've updated the article based on this discussion and the information I gathered about certificate chain of trust flows. I'm going to close this issue as resolved. If you have any follow-up questions, please comment here and we can reopen the issue.
#please-close


Strange shading with imported fbx models

Godot version: 3.2.4beta5
Hi everyone,
I want to import the polygon city fbx models (https://syntystore.com/products/polygon-city-pack) I bought.
But the shading looks very strange. It seems, that godot is not using the normals from the fbx file. I also imported the model into blender, to show the difference:

So, I've created a little test sphere in blender and try to import that. But with the same result.
TestSphere.zip

Is there something, I'm doing wrong or is this a bug?
Regards
abgenullt

cc @RevoluPowered

cc @RevoluPowered

i tried with a smooth shaded sphere from blender and it looked broken the same way as flat shading as in the OP.
Also, can reproduce on godot 4.0.dev ( b24c24f ) as well, but differently: mostly smooth (even if exported with shade flat) but a weird bias causing a seam.

if I remove uv seams (e.g. by scaling uv to 0 along the x axis in blender), the normal seam disappears and normals become smooth, even if exported with flat shading
So, on godot 4, it seems almost like it's recalculating normals on import (but incorrectly, taking uv seams into account), which I do not want.

This is probably fixed with the new FBX importer using FBX2glTF.
You can test it in Godot 4.0 alpha 6: https://godotengine.org/article/dev-snapshot-godot-4-0-alpha-6
This new importer might also be backported for the 3.x branch eventually.
If you still find issues with these models using the new importer, we suggest opening a new issue with details about the problems in Godot 4.0 alpha 6 or later.


Add ability to label hosts as non-schedulable unless explictly requested

Add ability to tag hosts as "non-schedulable" unless there is an explicit host affinity rule to place containers on those hosts.

Implemented with labels in the external scheduler.
Semantically should work like this:
Host A only allows containers with labels key1=val1, key1=val2, or key2=val3 to be schedule on them.
User should add a label like this to the host:
io.rancher.host.scheduler_label_whitelist: key1=val1,key1=val2,key3=val3
The result should be that only containers with label key value pairs matching one of the ones specified in the host label get deploy.

Seems like it should be io.rancher.scheduler.[something] to match other labels.
You say OR, but is there some use-case where I want AND / only containers which have all the labels?  Perhaps:
io.rancher.scheduler.require_any: key1=val1, key2=val2
io.rancher.scheduler.require_all: key1=val1, key2=val2

io.rancher.scheduler.require_any,
io.rancher.scheduler.require_all,
io.rancher.scheduler.require_more_than_one,
io.rancher.scheduler.require_more_than_two,
...
io.rancher.scheduler.require_more_than_X, Is that also true? Are we extending the idea the concept here?

When specifying the rules , is there a need to support other conditional parameters like "!=","or","in","not in" .. like we support for  selectorLink in services?
In the absence of io.rancher.host.scheduler_label_whitelist label , we will allow for deployment of any containers. Once user sets this label on the host (or even in the case where we have edited the label on the host), we will continue to have the containers that does not satisfy the current rule (deployed before the label was set/edited) to be present in the host ? In the event of stopping the container and would starting the container fail ?

I would like to err on the side of spring only the simpler use cases that can be easily explained and maybe show a summary of on the host list.

n [or more] of m, in/not in seems excessive...
or would be the same as any
!= can be _none
in/not inalso sounds excessive to me... But the all/some/nice could allow the input to just be a key instead of a key=value to match just that a label exists (or not).
if there is no label the host acts as today, eligible for any container.
-"allow no containers" is basically deactivate, don't need a new label for that.
existing containers are where they are, they're not moved because you change the host label or start/stop them.   On upgrade/reconcile they could be rescheduled.
global consists all the scheduler rules and press one on each eligible host.  So hosts that don't match will not get a container.

@vincent99 @will-chan  @ibuildthecloud has brought up a different use case that he wants to know if users wants. It would be a different interpretation of this feature that would thusly semantically:
Through a label, Host A indicates that services with Label X MUST be deployed to it.
So, the result is that it prevents services with a certain label (or potentially some other requirement) from deploying anywhere else in the environment.
The use case, as stated by @ibuildthecloud, is to allow admins to control where services get deployed in an environment. But honestly I don't quite see how this feature accomplishes that because it is still dependent upon users adding a certain label to their service.

@cjellick @ibuildthecloud I think this generally satisfy the requirement.  What are you thinking that the label looks like?  In our original scheduling rules, we label host(s) with X=Y, and the add the hard host affinity rule on the service for X=Y.
Can we keep the rule the same on the service so it's not confusing to users and add a special label on host with something like OnlyDeployOnHostWithLabel=true to enable this?  That way nothing changes and this special label will now indicate that only services with a host affinity rule (soft or hard) can deploy on these hosts, and nothing else.

Current implementation https://github.com/rancher/scheduler/pull/35 works as following:

Host A has label: `io.rancher.sheduler.require_any: foo=bar, infra=true, Host B has nothing.
Launching a service with label foo=bar or infra=true, It will go to the Host A and Host B. Launching a service with no label, it will only go to Host B.
This does not guarantee Host affinity, but guarantee that Host A only accept service with label foo=bar or infra=true, and will reject any service without one of those labels.

Global services need to take into account  `io.rancher.sheduler.require_any``` flag set on the host. This should be similar to what is being tracked in  - https://github.com/rancher/rancher/issues/7772
Additionally , when host labels in `io.rancher.sheduler.require_any``` get edited/deleted/added   , we should be able to reconcile instances in the global services accordingly.

close in favor of https://github.com/rancher/rancher/issues/7795


Update presubmit e2e to use pod local ip

Quick fix to unblock every one. I'll create another fix to actually use the service like kuat mentionned.
NONE

@sebastienvas: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
3d66ab5d2adbd3580b109c1d96e490af26d68ef9
link
@istio-testing bazel test this

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test all

/lgtm

https://github.com/istio/istio/issues/537


Added items to Schema equals and hashcode

Fixed a problem where Schema was not using the items property in the equals() or hashcode() method. This appears to have been missed when moving the items property off of the ArraySchema class and onto the Schema class.

@jeff-miller-cfa Thanks a lot!


Fix: fix the wrong value of scaler active and the failure of paused value in Opentelemetry

fix the wrong value of scaler active and the failure of paused value in Opentelemetry
Checklist

[ ] I have verified that my change is according to the deprecations & breaking changes policy
[X] Tests have been added
[X] Changelog has been updated and is aligned with our changelog requirements
[ ] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
[ ] A PR is opened to update the documentation on (repo) (if applicable)
[X] Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes (https://github.com/kedacore/keda/issues/5705)

/run-e2e sequential

/run-e2e sequential

/run-e2e sequential

/run-e2e sequential

Thanks for the fix. Could you please resolve conflicts? We merged some related stuff recently: #5687
Btw just checking, isn't there a similar problem with Prometheus?

No. As the lib of Prometheus doesn't use callback func to collect metric, it doesn't have the same issue as Opentelemetry.

/run-e2e sequential


Attempt to fix getTerminalContents bug

Description
[ What changed? Feel free to be brief. ]
Checklist

[ ] The base branch of this PR is preview, rather than main

#133

hm. seems like its fine. it just invokes the vscode workbench.action.terminal.selectToPreviousCommand function. i restarted the app and cannot recreate


Stop_all() problem when lot of audios is play

I don't know why but if you have multiples sound in playing and you call stop method, All sounds is not properly pause. It's very strange behavior and totally random.

Hrm. That was a tough one!
Turns out 2 things were wrong:

You forgot to add the braces to the for loop (or I removed them by accident, I can't remember)
We need to shallow-clone the instances array before iterating over it if we're going to fire the ended event artificially, as in the ended event instances remove themselves, changing the legngth of the array and preventing the iterator from iterating over the entire array and messing things up, as the browser is single-threaded (unless you use web workers, which don't have access to the DOM anyway).

Does the latest master there fix the issue for you too? If so I'll release v0.3.4 to fix it.

Yes it's good for me, tested and approved on master ;)

Awesome! I'll get releasing v0.3.4 then.

No problem, if you are interested to see usage of your library you can find in my github ;)
https://github.com/MyTheValentinus/soundbox
Thanks !

Hello,
I re-open this issue, the problem is not resolved. After lot of try the bug reppear.
When i play for example 10 songs, and call stopAll, all song are not pause.
Thanks

I can't reproduce this currently with my example test. Could you perhaps provide some additional information please?
For example, what does <soundbox_variable_name>.instances contain when the bug occurs?
Is there a particular way that you have to do it in order for the bug to occur? Maybe it's a specific sequence of events that cause it to break?

Do you have a email ? I send you link of my current usage and test page ?
Thanks

Yep! It's sbrl {at} starbeamrainbowlabs (dot) com.

Hom i'm so confused, after full refresh of my cache, is working like a charm. I re-close this issue.
I'm sorry

Ah, awesome! Glad it's working. It's no problem at all!
In the future, you may wish to keep the developer tools open in your browser, and tick the "disable cache" box on the network tab when working on a project.

Yes i know, but forget this time. Grrr

Ah, we all do that! I've done it several times and spent 1/2 hour figuring out which cache is responsible for holding on to the old file - when in actuality I've got the wrong file open or forgot to clear my browser's cache..... lol :P

#MyDevelopperLife


fix issue #2804: hide link to create plan, when not logged in

Fixes #2804 .
Someone might have to translate that one line for other languages.

merging a fix for our broken GitHub actions test that was causing this PR to fail


Revive OpenACC support in ARTED part.

In old ARTED, we were supported GPU system with OpenACC which the code was implemented by Mr. Akira Naruse (NVIDIA). This PR resumes the OpenACC support.
I verified the result of single-cell mode by testsuite, but this PR wants the test case for multi-scale mode.
Would you please add a test case for multi-scale mode?
Software/Hardware requirement

OpenACC: PGI compiler
MPI: MVAPICH2 and OpenMPI
GPU: Kepler and Pascal GPU (e.g. K40 and P100)

Test environment

PGI compiler 2017.4
P100 GPU with CUDA 8.0
MVAPICH2-GDR 2.2, OpenMPI 1.10.6 and 2.1.0
SLURM job scheduler

How to build
We provide OpenACC build configuration under CMake.
GNU Make version does not support it.
$ ${SALMON_SRC_DIR}/configure.py --arch=pgi-openacc
$ make

How to execute
We provide wrapper script mpirun.gpu to achieve the good performance.
This script sets CPU/GPU affinity (bind to MPI process) for SLURM job scheduler.
In the following command, SLURM execute the application under 2 nodes with 4 processes per node (total 8 processes).
$ srun -N 2 --ntasks-per-node=4 -- ${SALMON_SRC_DIR}/tools/mpirun.gpu -v ${SALMON_BIN_DIR}/salmon.pgi_acc < inputfile

Jenkins: Automatic build-test is triggered.

Jenkins: Automatic build-test is started.

Jenkins: Automatic build-test is successfully finished.

Thank you @yhirokawa san for fixing OpenACC routines. Presently, I am trying to check this modification by using SYSTEM-B@ISSP and I guess it costs a bit more time. I am sorry for the late reply...

@yhirokawa san! Sorry for the late reply!
I have checked the multiscale calculation between OFP(KNL) and System-B@ISSP (Tesla K40). I confirmed the both results shows agreement with ignoreble small numerical errors.
I think this modifiaction is available to merge into the developer branch.
Thank you for contribution!

@uemoto1 san, thank you for verifying/merging. I will improve the performance under GPU later.


fix event change permission check

So that really annoys me: All the get_perms and has_perm functions, if used with an obj, don't seem to regard the non-object permissions. So if a user was in a management group and had general change_event permissions without having change_event for a particular event, it would never get recognized. This way it does.
Should we built our own version of those functions? Seems complicated to get into sadly: would require us to roll our own ObjectPermissionChecker and everything that stems from it :/

coverage: 84.779% (-0.09%) from 84.87%
when pulling 5acc74682ddc5efdf731a30d04dede9a23c6db79 on fix-event-change-permission-check
into 6a86a2b75bbfedc69d84c438127500359ceeef5c on main.


Add a script to setup new survey project

Project repositories can be quite complicated. To avoid to the user the hassle of creating a new project himself and adding git submodule. this repo could add a tool that bootstraps the new project.

Steps this script will need to do:

Setup a new git repository in the target repository with gitsubmodule initialized
add a README.md explaining steps to start
Create a .env.example with the right config file
Add a package.json file in the root of the repository, with the workspaces set, as well as default script commands
Copy the template survey directory to the target repository, with all scripts and directory properly configured
At the end of the script, it should be possible to cd to the new directory and follow the instructions in the README to have a completely working empty survey. So running yarn, yarn compile, yarn build:dev and yarn start should work, without any additional configuration. [But the survey planner will have to configure the project according to their needs]

I suggest to add a template directory in this repo, with all files to create containing placeholders that can be replaced when copied with the project name and directory.
The script would receive as argument the name of the project and the path to where to create it.

@tahini Do we want a script or a templateSurvey (or ExampleSurvey) repo with a project that people can start working on ?


Custom data should be visible at different zoom levels

Description
In ID if you choose Custom data (Nodes for example with data), those are depicted as a Magenta Circle that could be seen at quite different zoom levels, including levels that do not allow any map edition. But help a lot for localization.
In Rapid you choose the same Custom data and you get the light blue solid node, the problem is if you zoom out you quickly lost the node viewing.
It could be quite helpfull if Rapid mimic ID so zooming do not affect the viewing of the custom data localization.
Version
2.0.3
What browser are you seeing the problem on? What version are you running?
Version 114.0.5735.199 (Official Build) (64-bit)
The OS you're using
No response
Steps to reproduce
Just choose any Custom data (json, gpx, kml) and once loaded zoom out. Examples attached.

The browser URL at the time you encountered the bug
https://rapideditor.org/rapid#background=Bing&datasets=fbRoads,msBuildings&disable_features=boundaries&map=15.40/-17.7361/-67.9209
The auto-detected useragent string for your browser (leave blank if you're manually filling this form out)
No response

It is possible to work on this issue? In ID you can see the custom data well above the 1000 ft view high. This data are NOT supposed to be in the map just overlapped or floating


fix: issue 2536

This is a commit to fix issue 2536 and 2529.
When I was fixing 2529, I declared slotMetrics as a global variable, which caused all DayColumn instances to use the same instance of slotMetrics. This is also the reason why bug  issue 2536 appears.
In this commit, I only modified the update timing of slotMetrics.Now both issues are resolved!
https://github.com/jquense/react-big-calendar/assets/63057542/756fc1b7-972e-4ef3-bb72-516e068218ac

Loading your changes in Storybook, if I go to the onSelectSlot story and begin a selection, it immediately changes it to begin at the beginning of the day up to my selection point.

This is an issue that exists in version 1.11.1 and is not caused by this commit.

Loading your changes in Storybook, if I go to the onSelectSlot story and begin a selection, it immediately changes it to begin at the beginning of the day up to my selection point.

This is an issue that exists in version 1.11.1 and is not caused by this commit.

@forceddd You are correct, but it was your previous PR that appears to have introduced this issue in the first place.

This bug should have existed a long time ago. The issue 2290 seems to be the bug described.
I will try to fix it next week, if I successfully solve this issue, I will create another PR.

@forceddd Thanks for looking into this. An you are partly right. That issue you pointed out was for dragging up. Now it is also doing it even if dragging down (which was not an issue before your change).

@cutterbl After each slotMetrics update, a new slots array will be created, but the _initialSlot object in DayColumn remains unchanged, so nextSlot becomes 0:00.
I modified nextSlot to handle this case. This video shows the performance after the modification.
https://github.com/jquense/react-big-calendar/assets/63057542/49a17560-6e0f-47c6-bfbb-b93e92cc010e

Is the margin-right here intentionally designed this way? Because when I'm selecting, there is no such spacing, but the rendered result has spacing. This makes me a little confused.

@cutterbl Would you please check this PR again? I submitted some new file changes.I think now this PR should be able to solve these related problems.

@forceddd Another defect (#2565 ) has come up around your changes. Not only is the onSelectSlot no longer returning a slotInfo.action of 'doubleClick', but the onDoubleClickEvent handler function no longer fires either.

@forceddd Another defect (#2565 ) has come up around your changes. Not only is the onSelectSlot no longer returning a slotInfo.action of 'doubleClick', but the onDoubleClickEvent handler function no longer fires either.

@cutterbl Ok, today I will look at this issue and try to fix it.


[Bug] Logged user cannot edit its profile with personal information (tested on Mobile device and Desktop)

As a registered user I cannot change information in my personal profile (Mobile device and Desktop)
To Reproduce
Steps to reproduce the behavior:

Open podkrepi.bg site
Click on Вход/ Регистрация бутон
Enter valid credentials
A personal profile opens
Go to second menu "Личен профил" and try to change your name
It cannot be changed

Expected behavior
The user must be able to change/ edit personal info - email, password, etc.
Smartphone (please complete the following information):

Device: [e.g. Samsung]
OS: [e.g. iOS8.1]
Browser [e.g. Google chrome)
Version

Cannot reproduce this one on OS X nor iOS.
Both desktop and

mobile work well.

On the top of what @kabaivanov said, I can confirm that it's working just fine, if you use a user which is registered via an email address, because you're forced to type in the password in the modal, when you try to update your first or last name.

Actually, yesterday I was looking at what I think is the cause for this issue (and other related ones)
I noticed that we do such checks in order to distinguish whether the current user is logged in via google or not:
const isAuthenticatedByGoogle = session?.user?.iss.includes('google')
This seems to be faulty, at least on my dev setup. If I am logged in via google, the token issuer is 'http://localhost:8180/auth/realms/webapp' and hence the above check is wrong and then we wrongly display and require the password field.
I might be wrong but I couldn't easily find a way to determine (strictly in the client), whether a user was registered via google or not, so maybe there could be some backend changes?


Revert ".travis.yml: remove osx from build matrix."

Recent changes seem to have gotten OS X back on track, so we should be
able to run our tests there again.
This reverts commit e12e903e9ac675d08f9dd0db1f0c1a2049232c21.

Refs:
https://github.com/travis-ci/travis-ci/issues/7304#issuecomment-361602004
https://www.traviscistatus.com/

... the fact that there are errors in the OS/X builds indicate that we do need to enable this

Merged.  a6da6b73ca480cfa6fe8d0a882f4ff549d46fcff

Recent changes seem to have gotten OS X back on track, so we should be able to run our tests there again.

@levitte it seams that also the appveyor jobs are suffering from an an extremely long startup time. This job here is listed as Queued for almost an hour now: https://ci.appveyor.com/project/openssl/openssl/build/master.15503

With Appveyor, we usually see a 1-2 hour backlog during high activity...  that's at least my experience, and I usually don't even notice these days.  It usually catches up during low activity.  The Mac OS/X backlog was worse than that, the turnaround time there was much larger when it was really bad, as I recall...

Problem with MacOS X was that it is common Travis queue, so that it didn't start new linux builds till osx were ready, which could take your all working hours. Appveyor is independent queue and one can tolerate throughput variations. In the nutshell one needs at least one queue with low turn-around times for requests.

Thanks for the information, @levitte and @dot-asm!


Cleanup the XML namespaces

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] If you're unsure, you can format the pull request title like [CAMEL-XXX] Fixes bug in camel-file component, where you replace CAMEL-XXX with the appropriate JIRA issue.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Run mvn clean install -Psourcecheck in your module with source check enabled to make sure basic checks pass and there are no checkstyle violations. A more thorough check will be performed on your pull request automatically.
Below are the contribution guidelines:
https://github.com/apache/camel/blob/master/CONTRIBUTING.md

Test results of this branch are:
https://ci-builds.apache.org/job/Camel/job/Camel JDK11/job/xml-namespace-cleanups/2/#showFailuresLink
Compared to the current master branch:
https://ci-builds.apache.org/job/Camel/job/Camel JDK11/job/master/442/#showFailuresLink

Test results of this branch are:
https://ci-builds.apache.org/job/Camel/job/Camel JDK11/job/xml-namespace-cleanups/2/#showFailuresLink
Compared to the current master branch:
https://ci-builds.apache.org/job/Camel/job/Camel JDK11/job/master/442/#showFailuresLink


Implement a method of keeping track of variable bindings

As unification-fd has a BindingMonad class to aid with keeping track of variable bindings, a similar typeclass would be useful for this library.

This is being worked on in the monad-unify branch.


feat: add result for monitoring on job run

This PR is to add results on job run for monitoring purposes. Changes:

update dag template and __lib.py to pull result through XCOM
add migration to add monitoring column on job run
update repository to fetch and update monitoring column for job run
update service to set monitoring

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

9 of 11 (81.82%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 92.021%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

core/scheduler/service/job_run_service.go
9
11
81.82%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
8373

Relevant Lines:
9099

💛  - Coveralls


Add ui.EDITOR_EOL setting and use ist instead of monaco's detection

Fixes: https://github.com/go-gitea/gitea/issues/28097
Replaces: https://github.com/go-gitea/gitea/pull/28101
Assuming we consider it a bug that people on Windows get CRLF endings without a editorconfig, we should backport this to 1.21.

I do not think this is right.
See the discussion https://github.com/go-gitea/gitea/pull/27141#discussion_r1331139585
Even if you set model.setEOL(monaco.editor.EndOfLineSequence.LF);, you still get \r\n when submitting the form

I believe the best choice is to revert #27141 at the moment, make 1.21 users happy. At least, "\n" is more widely used but "\r\n" causes problems in POSIX.

If that's because of textarea behaviour, we can fix this by setting the textarea value.

Added the previous server-side eol convertion back, but it now respects the user setting of LF vs. CRLF too:
https://github.com/go-gitea/gitea/pull/28119/commits/e58dcc03437dca23ed8bc24c8b7434ac088e14be

I guess the only thing missing here is to respect editorconfig on server-side as well, but for all intends, this will restore the previous replacement to LF that was done server-side.

I guess the only thing missing here is to respect editorconfig on server-side as well, but for all intends, this will restore the previous replacement to LF that was done server-side.

Done as well, now the server also respects the editorconfig file for this replacement. I guess it's still good to retain the client-side stuff so that copy out of monaco copies with the correct line endings.

If there is no "editorconfig", it should use the original EOL. eg: if the file was stored in "\n", the newly saved file should also use "\n"; if the file was stored in "\r\n", the newly saved file should also use "\r\n"
The config option "EDITOR_EOL" is not necessary (not used in most cases, according to the behavior above), the newly created file could just use "\n", which is widely used and doesn't cause problem in modern days.
I guess the JS trick for data-initial-value="{{JsonUtils.EncodeToString .FileContent}}" is a no-op now, it should work well by using <textarea>{{.FileContent}}</textarea> ?

If there is no "editorconfig", it should use the original EOL. eg: if the file was stored in "\n", the newly saved file should also use "\n"; if the file was stored in "\r\n", the newly saved file should also use "\r\n"

The same problem as BOM: https://github.com/go-gitea/gitea/pull/28935#issuecomment-1912115491

if the file was stored in "\n", the newly saved file should also use "\n"; if the file was stored in "\r\n", the newly saved file should also use "\r\n"
(and more) if the file was stored with some BOM, the newly saved file should also use that BOM

if the file was stored in "\n", the newly saved file should also use "\n"; if the file was stored in "\r\n", the newly saved file should also use "\r\n"

Yes, like with BOM we should just round-trip the file unmodified. The only problem is new files and files with equal amount of CRLF and LF, for those we need to bias towards one format, which could come from this config.
I think the approach here is not correct and we should actually avoid backend convertion completely. So I think it's better to make a new PR, maybe I will have a look later, but feel free to raise something @wxiaoguang.

I think the approach here is not correct and we should actually avoid backend convertion completely.

IMO at the moment, backend convertion can't be avoided. Because HTML textarea always passes "\r\n" to backend, it is the standard.

I think the approach here is not correct and we should actually avoid backend convertion completely.

IMO at the moment, backend convertion can't be avoided. Because HTML textarea always passes "\r\n" to backend, it is the standard.

Yeah, but we can at least avoid altering the content until the point where it reaches frontend.


Update 'peers connected' UI to reflect active channels

Fixes #1973

What happens when a channel closes? Does numChannels decrement?

Yes


Release v0.3.1

Updates all crates to v0.3.1.
The alternative is to only update the changed crates:

defmt-macros
defmt-decoder
defmt-rtt

bors r+


Update player current server on client/auth_with_server

fixes a very bad involving pdata
doesn't even fully fix it, i'm actually cringing at the thought
exploit is untested but the logic of the program means it almost certainly works

Cpone came up with a good solution, will implement shortly
(ref: https://discord.com/channels/920776187884732556/922954389415686185/933380294315212832)

added further protection, might fully prevent this problem

Table script: https://gist.github.com/barnabwhy/d8f101840ea94a6d56870eeffbe65db6

Tested just now, fix works as intended and prevents any exploits 👍


Type 'SRT' does not conform to protocol 'Hashable'

When I build Demo, see this error

One of the dependencies changed and it wasn't used a pinned Package file. I'll look into it.

I'm not able to reproduce at all actually. I can build just fine from main and If I update dependencies I can still build. What version you building and what Xcode version?

I use Xcode 14.3.1.

Umm, maybe SIMDSupport library need fixing. SRT have not hash method

public struct SRT: Hashable {
    public var scale: SIMD3<Float> = .unit
    public var rotation: simd_quatf = .identity
    public var translation: SIMD3<Float> = .zero

    public init(scale: SIMD3<Float> = .unit, rotation: simd_quatf = .identity, translation: SIMD3<Float> = .zero) {
        self.scale = scale
        self.rotation = rotation
        self.translation = translation
    }

    public var matrix: simd_float4x4 {
        let scaleMatrix = simd_float4x4(scale: scale)
        let rotationMatrix = simd_float4x4(rotation)
        let translationMatrix = simd_float4x4(translate: translation)
        return translationMatrix * rotationMatrix * scaleMatrix
    }

    public func hash(into hasher: inout Hasher) {
        // Your code
    }
}

This should be solved by tag/release 0.0.4 - you're going to want to pin your Package.swift to NOT use  anything newer as 0.0.4 is the last release I'll be supporting an older SDK.


DXCDT-600: Show active tenant in auth0 tenants list

🔧 Changes
Adds a tabular structure  to the auth0 tenants list command including an indicator for the currently active tenant.

🔬 Testing
Added slightly stronger assertions to the existing test case.
📝 Checklist

[x] All new/changed/fixed functionality is covered by tests (or N/A)
[x] I have added documentation for all new/changed functionality (or N/A)

Given that there can only be a single active tenant at a time (so only a single ✓ among N ✗), would it make sense to simply append a green, bold  current (or  (current)) to the domain of the current tenant?

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

Comparison is base (ad469a7) 72.59% compared to head (54c1f1f) 72.58%.
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #910      +/-   ##
==========================================
- Coverage   72.59%   72.58%   -0.02%
==========================================
  Files          93       93
  Lines       12393    12399       +6
==========================================
+ Hits         8997     9000       +3
- Misses       2874     2876       +2
- Partials      522      523       +1

Files
Coverage Δ

internal/cli/root.go
90.90% <100.00%> (ø)

internal/display/tenants.go
77.77% <100.00%> (+6.34%)
:arrow_up:

... and 1 file with indirect coverage changes

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


[WelcomeUX] Peek and Find All References don't seem to like small spaces

Testing #18091

Tracked as #18875


feat: change tests pattern from i18n

A problem faced in the tests regarding the translation, was that the keys were not loaded for the components, as well as the language.
As a solution, the I18nProvider was inserted to provide the translations and effectively test if the keys exist and if the component is displaying correctly.
What do you think?
reference PR: https://github.com/GeekHunter-Brasil/geekhunter-frontend/pull/840

Do we really need to test translations in every component test?
As far as I see, we want to ensure that the translations work. That's one thing. But we don't have to ensure the translations work when we are testing, let's say, an <Input /> component. They are different tests. If we enforce translation in component tests we are adding a whole new layer of complexity that add's little to know safety.
If we don't have a correct namespace on a render, the component will render the namespace key by default. We could just use the key in the tests. It will keep the tests more straightforward and less verbose without loosing safety.

Do we really need to test translations in every component test?
As far as I see, we want to ensure that the translations work. That's one thing. But we don't have to ensure the translations work when we are testing, let's say, an <Input /> component. They are different tests. If we enforce translation in component tests we are adding a whole new layer of complexity that adds little to no extra safety.
If we don't have a correct namespace on a render, the component will render the namespace key by default. We could just use the key in the tests. It will keep the tests more straightforward and less verbose without loosing safety.
If we don't have the ChakraProvider wrapping the test renders, the component will not behave as expected, and the tests should fail. If we don't have the ApolloProvider, the graphQL queries will not be made and the test should fail. But if we don't have the i18n provider the only change is that the text will not be translated. I think this is completly fine.

I understand your view, but I see a problem that if someone changes the locale files like deleting a key or changing the key itself, not the value, there would be no way to detect this error other than already in production or in manual tests.
And a key will appear in place of the text.

I understand your view, but I see a problem that if someone changes the locale files like deleting a key or changing the key itself, not the value, there would be no way to detect this error other than already in production or in manual tests.
And a key will appear in place of the text.

Indeed, if a translations were to change, or a key were to be deleted, it wouldn't be spotted by the tests.
But wouldn't it also be true for almost any text in the application? We don't usually test every text in the application, because texts are one of the most volatile aspects of a web page.
Also, to make a complete translation insurance, we would have to test each namespace, or else we are only ensuring the key is present and being used in the PR-BR namespace we are importing (as suggested by your PR).
I tend to think this insurance is not worth the extra complexity and length in the code base. But I would love to hear more opinions on this matter!


travis: Build and use anchor-cli on current branch for build

Currently, CI uses the latest commit on master for building the anchor-cli. See here. This means that a bug when introducing changes to the CLI might not be caught until after merging. It would be preferable to build and use the current branch when testing in travis.

Should also do this for the @project-serum/anchor ts package as well.

Addressed by #202.


Ring width dependent on the optical efficiency of the system

Brought up during a presentation in the last ASWG meeting (https://indico.cta-observatory.org/event/1686/contributions/15776/), there was an issue with the optical efficiency-dependence of the muon ring width. One of the proposed causes of this dependence was the fact that muons rings were fitted after applying image cleaning, which could get rid of some tails in the fits. I implemented the option of performing the analysis without applying the cleaning #736 and run the analysis again (it takes way longer than before so a crosscheck would be appreciated). Here are the results (top applying cleaning, bottom without):

Meaning that without applying image cleaning we still get an optical efficiency-dependence on the muon ring width. My bet is that somehow the likelihood fit performed in the likelihood fit_muon in muon_integrator.py is not doing the job completely right, maybe also related to #647. Anybody had a look to that issue?

Meaning that without applying image cleaning we still get an optical efficiency-dependence on the muon ring width.

Actually, what you see here is probably the ring width being dependent on the ring radius, right?  And this relationship is different for different efficiencies.
I suspect this line in the muon tool is at fault:
https://github.com/cta-observatory/ctapipe/blob/a633e0fb7d0620266c77d6fd68cf085314976b42/ctapipe/tools/muon_reconstruction.py#L164
The mask around the ring which pixels enter the fit is dependent on the fitted ring radius. This is probably not a good idea and might lead to this effect.

I agree there is no obvious reason to use a maximum distance to the ring (along the radius) proportional to the radius itself.
However, the fact that smaller-R rings have larger fitted widths is (I think) due both to larger ring fit parameter uncertainties for smaller rings (fewer pixels, less light) and also due to physics (fig 22 of https://arxiv.org/pdf/1907.04375.pdf). In any case, I think the 0.4 R value is pretty wide, I would not expect it affects much the result of the fitted width.


Will there be a C++/C version of this?

Seems the MLPerf app is using C++, so if you already have a C++ version of MLPerf inference, Will it go open source? Not an issue, just a question, Many thanks.

sorry guys, I just saw the cc files, will check it out.

@Charleshzhang You could also study the TFLite program we used to get over a hundred results for our v0.5 submission.


enh: Temporary chat toggle keyboard shortcut

Tiny Enhancement
Please add a keyboard shortcut for enabling/disabling temporary chat. Currently, it takes at least 5 clicks with a mouse to enable and disable it for the next chat.
Thanks for your consideration!

Ctrl + Shift + ' added to dev! This the keyboard shortcut combination may change without notice.

Ctrl + Shift + ' added to dev! This the keyboard shortcut combination may change without notice.

Hello Mr. Tim. I have version 0.4.8 and wanted to check if it differs from the development branch. On Windows, the shortcut Ctrl + Shift + ' doesn't seem to be working. Could this be because the development branch hasn’t been merged with the stable version yet? Thank you for your help!


Adding modified files for the Arduino Nano Every

Hi Nathan,
I don't think this actually should be merged. I just wanted to let you know it's there, in case you're or anyone else is interested.
Plus I wanted to take the opportunity to commend you on the nice library. I've been looking for something similar for my project and none of the other popular ones (e.g. Serial Transfer) match the simple elegance of Camino.
Anyway I needed it to work on the Arduino Nano Every, which uses the ATMega4809. It has a different register structure. I tried to insert it elegantly into the #define decision tree, but changes go deeper than that. E.g. the serial data register is different for RX and TX. So I just ended up removing all of that and replacing most of the init code with effectively what's in the native Serial.begin().
Doesn't look too good, but functions great.
Thanks again for your work and for sharing.

This is awesome, thanks for sending it over! Glad you found camino to be helpful :)
I'll keep this as a PR for now, hopefully other people can use it. It would be fantastic to  get it merged with the normal library, but you're right my naive #define tree is not designed for extensibility like this...

I'd love to improve the config UX and add support for more architectures. Ideally:

Default options should respect any #defines that were written prior to the #include. This should be how users configure the library--not by manually including and editing the file.

Values should be driven by architecture flags. There is one special case for UNO but there should be more

Extensibility for various architectures. Allow specifying a set of implementations for each pair of arch/port. Looking at your code, I think a minimal interface would be to #define these macros:
InitializePort()

ByteReadable_vect  # like USART3_RXC_vect
byte = ReadByte()

ByteSent_vect      # like USART3_DRE_vect
EnableByteSentISR()
DisableByteSentISR()
SendByte(byte)

If you're willing to test some changes on your end with your board, I might take a crack at these improvements and try to merge this PR

I'll test the heck out of it if you implement any of that.
I dug up the basement, but I only have Nano Everys and one Due, but that's ARM based. I'll check at work if I can find any newer AVR units that have a different register map.

Release 1.7.0 refactored the way camino supports architectures. Please take a look at src/arch.h--I hope it's abstract enough
If you could modify this PR (or create another) to add ATMega4809 support, I'll be happy to merge :)

That's awesome. It looks straightforward enough.

Allrighty... it's 4am here, but I made it work on the Due, which is SAM3 based.
The Every Nano wasn't difficult but this gave me a challenge.
On the Due It uses the Serial library as opposed to low level, but I guess that's not that big of a deal considering it's a much faster mcu. Miraculously, with a bit of creativity, it fits in your #define tree. I need to clean it up a lot, but I'll upload it after.

That’s awesome! This will be a great addition the library, thanks for figuring it out :)

I'm not going to lie, I had doubts when I saw your .h only implementations.  Maaan, Arduino is not making it easy.
Anyway after another couple of hours down the drain I think I have a reasonably ... wonky in a different way? ... solution. I'll try to submit it tomorrow and you can decide if you want to blow up the whole thing again.
On a different note. In the python module, like 134. Is that "list" on purpose? Am I missing something? The call itself is marked with out=bytes, so I'd expect a bytes object, but this way I have to put that in a list. (I can open an issue if you want me to.)

Yeah, not a fan of using only .h, but pretty sure it's required by Arduino IDE if I want to let people #define prior to #include...
In camino.Callable.call(*args), args is the list of unnamed arguments passed to the function. The args need to be translated to an input list of bytes, which are then sent to the Arduino. The code (starting on line 126) is kinda hacky:

if an integer, add to list
if a string, append to list
if a list, send the list

Some examples:

digital_write(12, 1) turns into data = [12, 1]
echo("hi") turns into data = [104, 105]
add([1, 2, 3]) turns into data = [1, 2, 3]

The out=bytes is just declaring the named argument out, and setting the default value to bytes. out controls the output format, and is used starting on line 146
You're right I should add an input case for bytes (although wrapping the bytes in a list does work: s = b'abc'; add(list(s)))


Coinbase returns false when querying account info

Hello,
can someone test that coinbase account info query is correct?
Btce and Kraken queries are working well. But when I try coinbase it returns
{"success":false,"error":"ACCESS_KEY not matched with a user"}
But I am sure that my api key, secret key and login with password are set well.
Can I view a request to the coinbase server to check the JSON? How?
If the library worked, where could be another problem? Thanks for advice
v3.0.0

Try the latest snapshot jars. Also, see the Wiki pages for how to view the raw JSON.

Hello, in 3.1 it returns
"HTTP status code was not OK: 401"

I have solved my problem. I did not set specific echxange parameter "passphrase" for Coinbase account


Error: Pandoc Export Failed

OS: ElementaryOS Hera (based on Ubuntu 18.04.4 LTS)
Issue: I cannot get working the plugin in Linux although I use pandoc CLI very often without any problem. The output of which pandoc command inside the terminal is right: /usr/bin/pandoc. I've install pandoc from a .deb package and I'm wondering if it's because some path divergence from the installation method; but I'm lost. I attached the Obsidian console output of the errors for every path I have find a pandoc file.
Any idea of what is going wrong?

Hmm, that's odd! Works fine on my Linux machine. What happens if you manually set the Pandoc path setting to /usr/bin/pandoc?

Got the same problem I'm using gnome 40, It tried both/usr/bin/pandocand which pandoc.

OS: Mac OS 14.1.2 (166<IP_ADDRESS>.3) Obsidian 0.12.12. Pandoc Plugin v0.2.5 Pandoc Installer pandoc-2.14.1-macOS
I have the same error "Pandoc Export Failed:" Attached are screenshots of my parameters.
Installation:

I used the standard Pandoc installer package (see above for version)
I checked that the relevant .obsidian folder had all of the requisite files
In parameters I referenced the style.css folder.

I am stumped!

@abrahambahez Looks like the plugin does not work if you have Obsidian installed using snap.
Installing using deb and then using the aut upgrade solved the issue for me

@abrahambahez Looks like the plugin does not work if you have Obsidian installed using snap.
Installing using deb and then using the aut upgrade solved the issue for me

Yes, indeed! It seems to work with the AppImage installation too, but not with the flatpak nor the snap ones

OS: Mac OS 14.1.2 (166<IP_ADDRESS>.3) Obsidian 0.12.12. Pandoc Plugin v0.2.5 Pandoc Installer pandoc-2.14.1-macOS
I have the same error "Pandoc Export Failed:" Attached are screenshots of my parameters.
Installation:

I used the standard Pandoc installer package (see above for version)
I checked that the relevant .obsidian folder had all of the requisite files
In parameters I referenced the style.css folder.

I am stumped!

In your case I see that you put the literal words 'which pandoc' but you shuld put the output of that command in a terminal.
You could try to:

Leave the "Pandoc path" field empty to use the default, or
Open a terminal in your Mac, write 'which pandoc' in it, press enter, copy the output and paste it in the "Pandoc path" field

I think this should solve that issue

why is the issue closed? the fact that the plugin fails for snap and flatpack installs is still there?

Thanks David - It worked!
--
Peter Sheffield
On 17 Aug 2021, 13:09 +0100, David Soff @.***>, wrote:

@abrahambahez Looks like the plugin does not work if you have Obsidian installed using snap.
Installing using deb and then using the aut upgrade solved the issue for me
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.


Start bit should LSB for both little-endian and big-endian

Hello,
The description for the start bit of DBC file is not correct when it is big-endian signal. LSB is considered as the startbit for DBC.  In this line, startbit should be 14, not 2. On the other hand, the value 0 should be considered as a startbit, not 4. Can you please fix this issue. Thanks, :smile:

Well, the description in signal.py is the cantools internal format, not the DBC format. It might not be the most intuitive format, but I guess we'll have to live with it. You can make the change in a PR and if it turns out well I can merge it.

@eerimoq okay. I will make a pull request.

Hey @eerimoq, I think it is your right. Once we load a CAN configuration file, it is not any of the specific format. I think it is better to deal with it locally. I am closing the issue. Thank you. This is just a great library to use. Thank you :smile:


Implement Action Servers and Client

I already implemented much of this functionality. (Following the code in nodejs implementation for the most part).
I was about to test it, when I ran into some type errors with the generated messages. Most of the action message generation process is still in the gendart repository, there should just be a little work required to understand and make this work.
@knuesel
I won't be able to get to this myself in the near future, since we aren't currently using actions in my lab. Totally willing to accept PRs for this though. Let me know if you need some pointers in the right direction for getting this implemented.

OK I'll try to get it working! For gendart would you be open to a substantial refactoring? I was investigating a problem with packages that define a service but no message (msg_list throws in this case because the -I flag doesn't pass the package directory) and I think the logic could be made more robust by better using the information available from CMake. This could also avoid regenerating the same files for every message file. But there might be a reason why gennodejs does it like that, so I'm not sure it will work... but I'd like to try 😊

Yeah, I'm open to a substantial refactoring. The current is based off of gennodejs, and I wasn't too familiar with the CMake process for generating messages and how it specified message dependencies, so I just changed what I needed to to get it working. It seems like rosnodejs has switched to a more dynamic message serialization / deserialization process rather than relying much on the generation process anymore. Just make sure that when you test it out that you test it with a message package that depends on another message package, and make sure that it generates both. Now that we depend on the pub versions of sensor_msgs and geometry_msgs it can't be one of those though. Also try deleting the old messages every once in awhile while you are testing to make sure that there are no errors when generating messages from stratch.
I have a workspace repository called dartros_ws which contains a .rosinstall file with the repositories I use to test changes to dartros. Feel free to use that, and update the workspace with whatever you need to test message generation more fully. Also make sure you pull the most recent changes to gendart. I made some this morning before generating and publishing geometry_msgs and sensor_msgs.

If you are going to be updating the message generation, we might also want to look into running dart format on the generated files in case any user tries inspecting the generated classes. I think I did pretty well on formatting manually, but it might improve it just slightly.


Class/create generic view

How test:
curl --location --request GET '<IP_ADDRESS>:7010/custom/hello_world'

Rename branch to https://github.com/saengate/django-docker-compose/pull/4


upstream connect error or disconnect/reset before headers. reset reason: connection failure

i followed all the instructions in below docs ,https://docs.microsoft.com/en-us/azure/aks/istio-scenario-routing
but when i open the IP address of the Istio Ingress Gateway ,
facing the above errors can you help me on this?
kubectl
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-25T15:53:57Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.7", GitCommit:"6f482974b76db3f1e0f5d24605a9d1d38fad9a2b", GitTreeState:"clean", BuildDate:"2019-03-25T02:41:57Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}
istioctl version
version.BuildInfo{Version:"1.1.3", GitRevision:"d19179769183541c5db473ae8d062ca899abb3be", User:"root", Host:"fbd493e1-5d72-11e9-b00d-0a580a2c0205", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Clean", GitTag:"1.1.2-56-gd191797"}

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

ID: 35b1812f-e2f3-f798-2788-611787994794
Version Independent ID: 3c593804-a3ef-24dc-cc82-0c4af12eb833
Content: Intelligent routing and canary releases with Istio in Azure Kubernetes Service (AKS)
Content Source: articles/aks/istio-scenario-routing.md
Service: container-service
GitHub Login: @paulbouwer
Microsoft Alias: pabouwer

@jayaprakashkamaraj, Thank you for using Azure docs feedback channel to raise this question! Since you have closed the issue, I presume you have figured out the issue or if the issue still persist and you need further assistance on this topic kindly let us know.

@AjayKumar-MSFT -- that issue have solved today i have facing another issue can you help me on this?
kubectl apply -f istio/step-1-create-voting-app-gateway.yaml --namespace voting
Error
unable to recognize "istio/step-1-create-voting-app-gateway.yaml": no matches for kind "VirtualService" in version "networking.istio.io/v1alpha3"
unable to recognize "istio/step-1-create-voting-app-gateway.yaml": no matches for kind "Gateway" in version "networking.istio.io/v1alpha3"

@jayaprakashkamaraj, Glad the issue is resolved. Thanks for the update!
For a specialized on the other issue, could you please open a new GitHub issue if it is document related or since this channel is reserved for documentation questions, we recommend posting technical questions on the technical forum where one of our specialized engineers in the subject or any Azure community members can provide the best possible answer to your scenario or question.
We will now close this issue in GitHub but hope to engage with you via our technical forums shared above.

@AjayKumar-MSFT -- that issue have solved today i have facing another issue can you help me on this?

How did you solve this issue?


Business Logic for entire domain

[In the article you mentioned that API gateway shouldn't implement business logic. Each microservice is independent but there may scenario where one service need to call other service to fulfill the functionality or there may be service which will just call other services to fulfil the functionality in that case what is best practice to do so. If one service is calling other service then involving services can be tightly coupled?]

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

ID: 78a7e7bd-23f3-a39f-9015-b77f14bb43e5
Version Independent ID: 0ac34e7e-315f-2452-bf0a-74e9b1068c38
Content: Microservices architecture style - Azure Application Architecture Guide
Content Source: docs/guide/architecture-styles/microservices.md
Service: architecture-center
Sub-service: guide
GitHub Login: @doodlemania2
Microsoft Alias: pnp

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 360207

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 360207

I think this documentation addresses your question: https://docs.microsoft.com/azure/architecture/microservices/model/microservice-boundaries


chore(dependencies): Update actions/setup-node action to v3.8.0

This PR contains the following updates:

Package
Type
Update
Change

actions/setup-node
action
minor
v3.7.0 -> v3.8.0

Release Notes

actions/setup-node
v3.8.0
Compare Source
What's Changed
Bug fixes:

Add check for existing paths by @dmitry-shibanov in https://github.com/actions/setup-node/pull/803
Resolve SymbolicLink by @dmitry-shibanov in https://github.com/actions/setup-node/pull/809
Change passing logic for cache input by @dmitry-shibanov in https://github.com/actions/setup-node/pull/816
Fix armv7 cache issue by @louislam in https://github.com/actions/setup-node/pull/794
Update check-dist workflow name by @sinchang in https://github.com/actions/setup-node/pull/710

Feature implementations:

feat: handling the case where "node" is used for tool-versions file. by @xytis in https://github.com/actions/setup-node/pull/812

Documentation changes:

Refer to semver package name in README.md by @olleolleolle in https://github.com/actions/setup-node/pull/808

Update dependencies:

Update toolkit cache to fix zstd by @dmitry-shibanov in https://github.com/actions/setup-node/pull/804
Bump tough-cookie and @azure/ms-rest-js by @dependabot in https://github.com/actions/setup-node/pull/802
Bump semver from 6.1.2 to 6.3.1 by @dependabot in https://github.com/actions/setup-node/pull/807
Bump word-wrap from 1.2.3 to 1.2.4 by @dependabot in https://github.com/actions/setup-node/pull/815

New Contributors

@olleolleolle made their first contribution in https://github.com/actions/setup-node/pull/808
@louislam made their first contribution in https://github.com/actions/setup-node/pull/794
@sinchang made their first contribution in https://github.com/actions/setup-node/pull/710
@xytis made their first contribution in https://github.com/actions/setup-node/pull/812

Full Changelog: https://github.com/actions/setup-node/compare/v3...v3.8.0

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.1.7 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Validation(), specifically setDataAtCell(), can be made much more efficient by eliminating re-render on each column.

DataHarmonizer freezes up / times out on validation of long, wide rows of data.  In fact for the GRDI template, validating even 50 rows even if they are almost empty, times out, and from Chrome performance report below, it appears that its because of unnecessary rendering in the setDataAtCell() call.

We might be able to dramatically increase performance by switching a cell value update call in the /lib/DataHarmonizer.js script validate() -> getInvalidCells() function which currently is called on each data table column (and GRDI template has 200+ columns). According to HandsOntable docs  “Performance issue with instance.setDataAtCell()” , if we can switch from setDataAtCell() to updateData() (rather than loadData which seems to mess with cell/row states) - that looks promising to solve the performance issue.  Note that the populateFromArray() method appears to RENDER just like setDataAtCell() so avoid that solution.
Involves replacing "this.hot.setDataAtCell(row, col, update, 'thisChange');" at 2338 and 2346 and the  doUniqueValidation() call line 2145 "this.hot.setDataAtCell(provenanceChanges);"

Related pull request: https://github.com/cidgoh/DataHarmonizer/pull/409


VSIX installer for VS2017

Reported on the forum.

Well the new visual studio 2017 has been released, but unfortunately the .vsix installer for Bridge.NET does not work with Visual Studio 2017 RC. Is there a way to get by this? And will the next version for Bridge.NET be compatible with Visual Studio 2017?

Temporary workound

Download as vsix
Extract as zip
Goto extension.vsixmanifest.
Change

<InstallationTarget Version="[11.0,15.0)" Id="Microsoft.VisualStudio.Pro" />

to
<InstallationTarget Version="[11.0,15.0,17.0)" Id="Microsoft.VisualStudio.Pro" />

I've updated the upcoming Bridge 15.5.0 .vsix to support installation into Visual Studio 2017.
Here's an updated .vsix version of the Bridge 15.4.0 release if you want to test installation into Visual Studio 2017. I would recommend uninstalling Bridge from all versions of Visual Studio before testing the .vsix (inside the following .zip file):
Bridge.NET.15.4.0.vsix.zip
The installation process is smooth and will prompt to install Bridge into any Visual Studio versions (minimum Visual Studio 2012) you have on your machine.
Installation runs fine, but there is an annoying issue with uninstallation.
In previous Visual Studio releases, the Extension uninstallation happens immediately. With Visual Studio 2017, the uninstallation does not occur until all instances Visual Studio 2017 are closed and all related processes (eg. in the Task Manager) have been terminated (either automatically or manually).
After you close all instances of Visual Studio 2017, the following VSIX Installer dialog box might open.

The dialog lists processes that must be shut down before the vsix will fully uninstall. A note regarding this dialog is also provided in the Visual Studio 2017 Extensibility documentation.
If you click Cancel the extension will not be uninstalled.
On my machine the processes eventually terminated on their own, but it took a while. After one minute, I clicked Retry.

I let it sit for about another minute, and clicked Retry again. Fewer options, but still waiting...

I let it sit for another minute, and clicked Retry. This time only the VBCSCompiler.exe (ID 8232) process remained. This one stuck around for a while. I clicked Retry again about every minute.

On my machine, after about five minutes, the VBCSCompiler.exe (ID 8232) process finally terminated on its own and the uninstallation of the extension was successful.

I'm not sure there's anything we can do to improve the installation experience. Microsoft has changed the vsix uninstallation process and in my opinion the uninstallation process should be improved.
If you're dead set on removing the Bridge vsix extension from Visual Studio 2017 (RC), use the following steps:

From within Visual Studio 2017, select Tools > Extensions and Updates... > Installed > Find Bridge.NET > click Uninstall
Close the Extensions and Updates... window
Close all instances of Visual Studio 2017
The VSIX Installer dialog should automatically open
If the uninstaller doesn't uninstall the extension immediately, wait a few moments, then click Retry
Keep repeating Step 5 until something happens
Eventually the processes should terminate and uninstallation of the extension will run

NOTE: You can manually terminate the process by jumping into the Task Manager by right-clicking on Taskbar, then select Task Manager. Find each process in the list and End task.
I'll see if we can get the attention of someone from the Visual Studio team to provide feedback on this issue. Starting with the documentation authors: @gregvanl @ghogen. I'll dig around and try to find who has ownership of this functionality.

Closing this issue and will deal with the uninstallation process in a separate issue.


Alert:Deploy script is very dangerous！

the delpoy script given in "https://shipyard-project.com/deploy" is very dangerous ,
It binds the docker api port"2375" to <IP_ADDRESS>,
So bad guys can bypass the web authorization easily and control the docker by this api.
What's more terrible is attacker can create a new containter and mount your /root/.ssh/ directory and add an authrized_keys to your host,then they can control your machine!
Please change this script immeditely.

Yes this is why there is a warning.  Please use TLS.

But I searched the Internet and there are still lots of shipyard servers open their 8080 and 2375 port.I don't think this note is enough beacuse deafult setting is unsafe.


chore(release): 2.67.0

See CHANGELOG

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 0ff749e393bd26a1f440907f29f732e74adad27c
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Support for scale out coordinators in K8s

Currently we only support the one coordinator. To get logs from a scale out coordinator in K8s we'd need a unique pod label and be able to add it as a argument  under the collection
Ideally we need to just have a list of labels and then collect everything from a list of labels and IPs and delete if the node's role from config or some other means

So looking more closely at this, we currently do actually support this. Unless we can come up with a case where this breaks then I will reopen the issue


Can we apply styles like classnames

I stumbled upon a use case where I have to override a default library style applied inline to a component.
In this case the following doesn't work as inline styles applied by library have a higher precedence:
import Component from 'library';
import { c } from 'classy-ui';

...

<Component className={c('my-class')} />

...

Is it possible to have something like this where one can apply styles directly on a component instead of classnames:
import Component from 'library';
import { s } from 'classy-ui';

...

<Component style={s('my-class')} />

...

Hi there @afzalsayed96 !
Technically we could do something like that, though it might be better to rather allow an important version. So:
<Component className={important('my-class')} />

That would keep things consistent and things like autoprefixer etc. would still operate on that CSS definition 😄

Yes! An important decorator could also solve this.

Okay, cool! I am in the middle of implementing something now, but will keep this in mind. Will not close until we have some solution to this. Thanks for bringing it up! 👍

I can help in implementing this if you could point me in the right direction

Thanks a bunch for wanting to contribute! We are still making big changes to the codebase, so just need to settle on the core first. We should be ready for contributions very soon 😄

Hi there!
So things are settling now. This important decorator needs a custom implementation as it operates differently than all other decorators. It also needs some refactoring of the codebase as there is currently not possible to override to access the value at the point of decorators being applied. So yeah, it is on the list, but needs bigger worker to get it in 😄 Will keep you posted!


The superuser cannot obtain lastMessageId

partition-0 get lastMessageId 401 Authentication required

partition-1 get lastMessageId is ok

The number of partitions for topic is 4.in java client  parition-0 and partition-3  is ok ,but partition-1 and partition-2 like this 401 Authentication required

@Xlingxiao are you using JWT authentication?
Which version of pulsar are you using?

@sijie Im using JWT authentication。Pulsar version is pulsar-2.3.1

Can I use Chinese ？
this is new problem：
这里又有新的问题出现了：
[zx@slave107 ~]$ pulsar-admin clusters list
lx_cluster_1
[zx@slave107 ~]$ pulsar-admin clusters get lx_cluster_1
Cluster does not exist

Reason: Cluster does not exist
[zx@slave107 ~]$

@Xlingxiao :

Im using JWT authentication。Pulsar version is pulsar-2.3.1

I looked at your screenshots - it seems that you are issuing the lastMessageId directly to the admin endpoint. it seems your JWT authentication is lost when the http request is redirected. There is a similar issue in java admin client : https://github.com/apache/pulsar/pull/3869 .
I would suggest you using admin cli or the java admin api. It handles the authentication header during redirections happen.

Can I use Chinese ？

I would suggest using English if possible. If you are interested in talking to Chinese contributors, there is a slack channel #china in Pulsar's slack, where people chat in Chinese though.

pulsar-admin clusters list

Interesting. It looks like the second command talks to a broker whose didn't find the metadata. How do you setup you the clusters? Can you describe a bit more about your setup?

@sijie

using admin cli or the java admin api.
Yesterday I also made errors using Java cli，but today I deleted the topic and used the new topic. Now there is no problem with Java cli
Can you describe a bit more about your setup?
What configuration do you need to see ?
and this problem

[zx@slave107 pulsar-2.3.1]$ pulsar-admin namespaces list lx
lx/java
lx/java2
[zx@slave107 pulsar-2.3.1]$ pulsar-admin persistent list lx/java
HTTP 500 Internal Server Error

Reason: HTTP 500 Internal Server Error
[zx@slave107 pulsar-2.3.1]$ bin/pulsar-admin topics list lx/java
HTTP 500 Internal Server Error

Reason: HTTP 500 Internal Server Error

Talked with @Xlingxiao offline. The issue that cluster doesn't show up was due to a misconfiguration in zookeeper. It was gone after fixing the zookeeper setup.
The Authentication error seems to still happen. I guess it is related to the redirection problem similar to   #3869 . will keep working on this. @merlimat if you have any quick idea, please comment to help.

@Xlingxiao any luck about this issue?

sorry,no


flutter doctor does not show Android ToolChain check info and can not link anroid devices

Is there an existing issue for this?

[X] I have searched the existing issues
[x] I have read the guide to filing a bug

Steps to reproduce
The installation processes mentioned below are all new installations. Yes, I have tried to reinstall the system, but it still appears.

Operating system: Windows 11, 21H2, 22000.2245
Install Android Studio and open it, then download SDK 34, 33

Install flutter sdk, and the Android Studio installation location, SDK 34, 33 location and license are set correctly.

Actual results
Flutter can not read android devices, contains avd, but it can be read by execute adb devices.

Then I execute flutter doctor -v, console log does not show Android ToolChain check info, like this.

Logs

Logs

<!-- Paste your logs here -->

Flutter Doctor output

Doctor output

<!-- Paste your output here -->

[✓] Flutter (Channel stable, 3.10.6, on Microsoft Windows [版本 10.0.22000.2245], locale zh-CN)
• Flutter version 3.10.6 on channel stable at D:\APPs\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision f468f3366c (4 weeks ago), 2023-07-12 15:19:05 -0700
• Engine revision cdbeda788a
• Dart version 3.0.6
• DevTools version 2.23.1
• Pub download mirror https://mirror.sjtu.edu.cn/dart-pub/
• Flutter download mirror https://mirror.sjtu.edu.cn/
[✓] Windows Version (Installed version of Windows is version 10 or higher)
[✓] Chrome - develop for the web
• Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe
[✓] Visual Studio - develop for Windows (Visual Studio Community 2022 17.2.5)
• Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
• Visual Studio Community 2022 version 17.2.32616.157
• Windows 10 SDK version 10.0.19041.0
[✓] IntelliJ IDEA Community Edition (version 2023.2)
• IntelliJ at C:\Users\root\AppData\Local\JetBrains\Toolbox\apps\IDEA-C\ch-0\232.8660.185
• Flutter plugin version 75.1.4
• Dart plugin version 232.8660.129
[✓] VS Code (version 1.81.0)
• VS Code at C:\Users\root\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.70.0
[✓] Connected device (3 available)
• Windows (desktop) • windows • windows-x64    • Microsoft Windows [版本 10.0.22000.2245]
• Chrome (web)      • chrome  • web-javascript • Google Chrome 115.0.5790.170
• Edge (web)        • edge    • web-javascript • Microsoft Edge 115.0.1901.188
[✓] Network resources
• All expected network resources are available.
• No issues found!

Finally, I has solved this problem.
Edit flutter config:
flutter config --enable-android

But I'm still puzzled why this parameter needs to be turned on manually. I used to turn on this option by default when I used Flutter in MacOS and Win11.

Finally, I has solved this problem.
Edit flutter config:
flutter config --enable-android

But I'm still puzzled why this parameter needs to be turned on manually. I used to turn on this option by default when I used Flutter in MacOS and Win11.


E1 includes holds?

in the "before you begin" section of this article, it states that you need an exchange online plan 2 or archiving license to get an office 365 retention policy, however this article now seems to state that this is included in E1: https://docs.microsoft.com/en-us/office365/servicedescriptions/office-365-platform-service-description/office-365-securitycompliance-center#security--compliance-center-availability-for-business-and-enterprise-plans

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

ID: 7108464d-597a-c79d-cac8-94e35d9dd3d0
Version Independent ID: ba0d3744-707d-c506-47f4-83519022d4cb
Content: Create and manage inactive mailboxes in Office 365
Content Source: microsoft-365/compliance/create-and-manage-inactive-mailboxes.md
Service: o365-seccomp
GitHub Login: @markjjo
Microsoft Alias: markjjo

@Mike-Crowley No, there's been no change. You still need and EXO Plan 2 license to apply a retention policy to a mailbox (as per the inactive mailbox topic). If you're referring to the "Manual retention policy" row in the service description, then the "Yes" value in the E3 column is incorrect. Also, the idea of "Manual retention policy" is odd. This might really be referring to the publishing of retention labels which then allows users to manually apply them to content. In any case, thanks of the heads up. We'll fix this.

Yes, that was the column I was referring to. thanks for clarifying that the other document is wrong.

I opened a bug on the other page and they are saying that they are right. Can you two please sort this out?
https://github.com/MicrosoftDocs/OfficeDocs-O365ServiceDescriptions/issues/211#event-2742038160


Live sync only works with the last open source buffer

Currently, live sync uses script level variables to store its state – this needs a refactoring.

This plugin is officially EOL as I no longer use Vim (much), much less Unite. Sorry.


:sparkles: feat(icons): add local currency icon

Description
Adds "Local Currency" SVG icons (48x48 and 36x36 variants, to support full range of Coral image sizes) to Coral Spectrum
Related Issue
https://jira.corp.adobe.com/browse/AD-1497
Motivation and Context
The "Local Currency" icon is required for workflows within Admin Console.
Note: The icon is new and not present Spectrum Icons: https://spectrum.adobe.com/page/icons/.
How Has This Been Tested?
Made changes to ./examples/index.html to surface icons and test all sizes across various browsers (see screenshot from Mac/Firefox; below).
Screenshots (if appropriate):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.

Closing and Reopening for Adobe CLA


Add libsql as a dependency

This PR updates our Homebrew formula to include libsql as a dependency. The final generated formula looks like following:
# typed: false
# frozen_string_literal: true

# This file was generated by GoReleaser. DO NOT EDIT.
class Turso < Formula
  desc ""
  homepage "https://github.com/tursodatabase/homebrew-tap"
  version "0.87.6"

  depends_on "libsql/sqld/libsql-server"

  on_macos do
    if Hardware::CPU.arm?
      url "https://github.com/tursodatabase/homebrew-tap/releases/download/v0.87.6/homebrew-tap_Darwin_arm64.tar.gz"
      sha256 "915ca542f0c9b8ce2e65b7583ce360f23bc90ca31e4cc6392162f3b30c8328ef"

      def install
        bin.install "turso"
        bash_completion.install "completions/turso.bash" => "turso"
        zsh_completion.install "completions/turso.zsh" => "_turso"
        fish_completion.install "completions/turso.fish"
      end
    end
    if Hardware::CPU.intel?
      url "https://github.com/tursodatabase/homebrew-tap/releases/download/v0.87.6/homebrew-tap_Darwin_x86_64.tar.gz"
      sha256 "d27c43f9e0854eab5bd12e4d237884f07d88a671f8872146d82f12c9f38e2eb1"

      def install
        bin.install "turso"
        bash_completion.install "completions/turso.bash" => "turso"
        zsh_completion.install "completions/turso.zsh" => "_turso"
        fish_completion.install "completions/turso.fish"
      end
    end
  end

  on_linux do
    if Hardware::CPU.arm? && Hardware::CPU.is_64_bit?
      url "https://github.com/tursodatabase/homebrew-tap/releases/download/v0.87.6/homebrew-tap_Linux_arm64.tar.gz"
      sha256 "7d3290dd8cb46e87dd5d3cf8478cb32c61890a34dcfc95d75234f577635d978e"

      def install
        bin.install "turso"
        bash_completion.install "completions/turso.bash" => "turso"
        zsh_completion.install "completions/turso.zsh" => "_turso"
        fish_completion.install "completions/turso.fish"
      end
    end
    if Hardware::CPU.intel?
      url "https://github.com/tursodatabase/homebrew-tap/releases/download/v0.87.6/homebrew-tap_Linux_x86_64.tar.gz"
      sha256 "71da7f47fa84ef210d165d124e7f3da0b4e8de288a6e0ea0b2e4072711b3dd96"

      def install
        bin.install "turso"
        bash_completion.install "completions/turso.bash" => "turso"
        zsh_completion.install "completions/turso.zsh" => "_turso"
        fish_completion.install "completions/turso.fish"
      end
    end
  end

  def post_install
    exec('turso quickstart')
  end
end

Only one line is the diff:
+ depends_on "libsql/sqld/libsql-server"

This is generated by doing a goreleaser dry run:
goreleaser --skip-validate --skip-publish --clean

Here is a sample run which shows it works! - https://github.com/avinassh/homebrew-tap/actions/runs/7490817373

@avinassh When I upgrade with either brew upgrade turso or the auto-update I get this message:

tursodatabase/tap/turso 0.88.5 -> 0.88.6
Error: No available formula with the name "libsql/sqld/libsql-server".
Please tap it and then try again: brew tap libsql/sqld

Is this expected and I should run that command, or should this be covered by the turso install?

@dan-lee can you tell me which OS you are using? Also, are you on latest version of brew (with brew update) done? I just tried and it worked as expected. that is, it did not require manual tap:

==> Upgrading 1 outdated package:
tursodatabase/tap/turso 0.88.0 -> 0.88.6
==> Fetching dependencies for tursodatabase/tap/turso: libsql/sqld/libsql-server
==> Fetching libsql/sqld/libsql-server
==> Downloading https://github.com/tursodatabase/libsql/releases/download/li
==> Downloading from https://objects.githubusercontent.com/github-production
##################################################################### 100.0%
==> Fetching tursodatabase/tap/turso
==> Downloading https://github.com/tursodatabase/homebrew-tap/releases/downl
==> Downloading from https://objects.githubusercontent.com/github-production
##################################################################### 100.0%
==> Upgrading tursodatabase/tap/turso
0.88.0 -> 0.88.6
==> Installing dependencies for tursodatabase/tap/turso: libsql/sqld/libsql-server
==> Installing tursodatabase/tap/turso dependency: libsql/sqld/libsql-s
🍺  /usr/local/Cellar/libsql-server/0.22.17: 5 files, 31.0MB, built in 2 seconds
==> Installing tursodatabase/tap/turso
==> Caveats
zsh completions have been installed to:
/usr/local/share/zsh/site-functions
==> Summary
🍺  /usr/local/Cellar/turso/0.88.6: 6 files, 18.8MB, built in 3 seconds
==> Running brew cleanup turso...
Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see man brew).
Removing: /usr/local/Cellar/turso/0.88.0... (6 files, 18.8MB)
Removing: /Users/avi/Library/Caches/Homebrew/turso--0.88.0.tar.gz... (5.8MB)
==> Caveats
==> turso
zsh completions have been installed to:
/usr/local/share/zsh/site-functions

Alternatively, can you try tapping manually and see if it works? Ideally this step is not required:
brew tap libsql/sqld
brew upgrade turso

I'm running macOS 14.3. When tapping the formula it works as expected, just wanted to report in any case :)


Applications hang and time out when reading cached items from S3 (no errors reported)

Sometime after version 1.0.20, applications using cache data began to time out if a cached item was stored in S3. If an item was small enough to be stored in DynamoDb, it was fine. (Typically, cache-data stores items larger than 16K in S3)
If the item is freshly written to S3 but not read from, it is okay. Examination of S3 objects through the AWS Web Console shows they are properly written and contain the expected JSON data. Troubleshooting shows they are successfully retrieved, but something happened between retrieving and returning the object data.
No errors were logged from the try/catch block, it was only hanging and timing out.
After heavy troubleshooting and logging, the issue was traced to the internal S3Cache.read() function cache-data uses to convert the raw S3 object from a buffer to a string (and then to an object). Adding 'utf-8' to the .toString() method worked. An AWS SDK update must have broken the empty parameter for .toString(), requiring 'utf-8' to be explicit.
const result = await s3.getObject(params).promise();
item = JSON.parse(result.Body.toString();

Became:
const result = await s3.getObject(params).promise();
item = JSON.parse(result.Body.toString('utf-8'));

The next release will be updated to fix the issue.

While the initial tests before the 1.0.24 release seemed to work, the new release failed to produce the desired response once deployed in an application.
I lengthened the amount of time to allow the Lambda function to run (60 seconds), and the function finished execution after about 13 seconds, allowing about 10 seconds for the JSON.parse() to take place.
I developed a local script to run iterations and execution calculations on JSON.parse, which runs as expected. 1000 iterations on the same file from S3 (locally stored, 23K in size) ran for a total of 885.958ms. (AVG: 0.512ms | MIN: 0ms | MAX: 4ms) much less than the 10 seconds it is running in the Lambda function.
I ran the iteration test in Node v14, v16, v18, and v20 with no noticeable changes in execution time. The next step will be to run the test within a Lambda function.

Ran the test in a dedicated Lambda function. 1,000 iterations took 2272ms, max 58ms.
I then inserted the test code into the data-cache code and ran it async within the S3 read code. The 1000 iterations took 959.9ms to complete. The regular parsing code for just 1 iteration took exactly 7 seconds--right down to the millisecond. (2023-09-09T22:13:17.622-05:00 to 2023-09-09T22:13:24.622-05:00)
Both pieces of code parsed the same data, yet the 1000 iterations took the usual amount of time, and the previous code still took 7 seconds. Why?

I continued testing and ended up creating a separate method to turn the Buffer into a string and then parse into a JSON object. I put the method outside of the S3Cache.read() method, and it seemed to speed things up. I was getting results before the function and API gateway timed out.
I've removed the tests.
One final thing I tried out was to not store the data as encrypted. This improved processing greatly, and the application works as expected.
While I can separate and modularize the processing, I cannot expect encryption to be turned off in production. The question is, why was the encrypted data processing fast in my test instances but not in the following JSON.parse(), which was EXACTLY the same.
	/**
	 * @param {Buffer} s3BodyBuffer
	 * @returns {object} a parsed JSON object
 	*/
	static bufferToObject(s3BodyBuffer) {
		let str = s3BodyBuffer.toString('utf-8');
		return JSON.parse(str);
	}

	/**
	 * Read cache data from S3 for given idHash
	 * @param {string} idHash The id of the cached content to retrieve
	 * @returns {Promise<object>} Cache data
	 */
	static async read (idHash) {

		return new Promise(async (resolve, reject) => {

			const objKey = `${S3Cache.getPath()}${idHash}.json`;
			const objFullLocation = `${S3Cache.getBucket()}/${objKey}`;
			tools.DebugAndLog.debug(`Getting object from S3: ${objFullLocation}`);

			let item = null;

			try {

				let params = {
					Bucket: S3Cache.getBucket(),
					Key: objKey,
					ResponseContentType:'application/json'
				};

				let result = await s3.getObject(params).promise();
				tools.DebugAndLog.debug(`Success getting object from S3 ${objFullLocation}`, result);

				item = S3Cache.bufferToObject(result.Body);

				tools.DebugAndLog.debug(`Success parsing object from S3 ${objFullLocation}`, item);

				resolve(item);

			} catch (error) {
				tools.DebugAndLog.error(`Error getting object from S3 (${objFullLocation}): ${error.message}`, error.stack);
				reject(item);
			}

		});

	};

v1.0.32 has been released, but there is still no fix for this, BUT AWS SDK v3 S3 objects are returned with a readable stream body, which is promising for using a streaming JSON parser.

RESOLVED: The test applications were running in Lambda with the memory set at the default of 128MB. Once the memory was increased to 512MB, function runtime decreased by over half, and the JSON parse no longer caused timeouts. The functions used for testing had been set to 256MB but accidentally reduced to 128MB prior to experiencing the timeout issues. There were no issues with the Cache-Data package itself; it was purely a user (my) error.
For Lambda functions, increasing allocated memory will improve performance. I should have looked into this sooner.
THEREFORE: As pointed out in many online resources, including AWS's own documentation, Lambda applications should be given more than the default 128MB when using network resources and processing data. I recommend trying 512MB and adjusting depending on your workload and execution experiences. See Lower AWS Lambda bill by increasing memory. Optimal performance is probably between 256MB and 1024MB.
I will update the documentation to reflect this recommendation of 512MB with adjustments to anywhere between 256MB and 1024MB.
Example: The charts below reflect 1 million requests over a seven-day period. As you can see, the invocations remained at a high level throughout the seven-day period. There was a dramatic drop in execution time once the memory was increased. Latency was also improved. This also reduced the number of concurrent executions taking place.


Remove the deprecation warning PropTypes from React v15.5+

React.PropTypes is deprecated as of React v15.5, Convert this to import PropTypes from 'prop-types'; click here more detail.

The issue has been fixed.
Thanks


Outdated string documentation in io.read_spikeglx()

The following link in the documentation seems broken.
https://github.com/SpikeInterface/probeinterface/blob/196f203dc22fcdd788e27a61c77d0bd83b2ed418/probeinterface/io.py#L715
@samuelgarcia

seems fixed! :)


endpoint: Take read lock while accessing Consumable

Parallel policy recomputations can update Consumable, so the reader
has to protect against that.
Signed-off-by: Jarno Rajahalme<EMAIL_ADDRESS>

test-me-please