Ubuntu - not possible to create rectangle - application crash

OS: Ubuntu
PyQt version:

dpkg -l | grep "pyqt"
ii  python3-dbus.mainloop.pyqt5                                 5.14.1+dfsg-3build1                                                  amd64        D-Bus Qt main loop support for Python 3
ii  python3-pyqt5                                               5.14.1+dfsg-3build1                                                  amd64        Python 3 bindings for Qt5

Python 3.10
Traceback:
  File "/home/vzeman/anaconda3/envs/py10/lib/python3.10/site-packages/libs/canvas.py", line 530, in paintEvent
    p.drawLine(self.prev_point.x(), 0, self.prev_point.x(), self.pixmap.height())
TypeError: arguments did not match any overloaded call:
  drawLine(self, QLineF): argument 1 has unexpected type 'float'
  drawLine(self, QLine): argument 1 has unexpected type 'float'
  drawLine(self, int, int, int, int): argument 1 has unexpected type 'float'
  drawLine(self, QPoint, QPoint): argument 1 has unexpected type 'float'
  drawLine(self, Union[QPointF, QPoint], Union[QPointF, QPoint]): argument 1 has unexpected type 'float'
Aborted (core dumped)

Error occured, when I wanted to create rectangle and moved mouse over the image - application always crash

Update: with python 3.8 is application not crashing

I have this error with Python 3.10.4

Can not reproduce this bug on Debian GNU/Linux with following software versions:
~/src/labelImg (git)-[master] % python3 --version
Python 3.10.5

~/src/labelImg (git)-[master] % dpkg -l | grep "pyqt"
ii  pyqt5-dev-tools                                  5.15.6+dfsg-1+b2                    amd64        Development tools for PyQt5
ii  python3-pyqt5                                    5.15.6+dfsg-1+b2                    amd64        Python 3 bindings for Qt5
ii  python3-pyqt5.sip                                12.10.1-1                           amd64        runtime module for Python extensions using SIP

same error on Windows, installed with pip

python 3.10.5
labelimg 1.8.6

Same issue with me. Solution was to use python3.8 for me.
conda create -n labelImg python=3.8
pip3 install labelImg
python3 $HOME/miniconda3/envs/labelImg/bin/labelImg

i am having same problem
pls someone help me to resolve it .
Question

how can i downgrade the python version 3.10 to 3.9.?

same. Windows 10, python 3.10.5

https://github.com/heartexlabs/labelImg/issues/811#issuecomment-977605722

Solution.
Error in Qt5.
float to int conversion
Changed:
x:\xxxxx\python-310\Lib\site-packages\libs\canvas.py
526 line:
default:
p.drawRect(left_top.x(), left_top.y(), rect_width), int(rect_height)
new:
p.drawRect(int(left_top.x()), int(left_top.y()), int(rect_width), int(rect_height))
530 line:
default:
p.drawLine( self.prev_point.x(), 0, self.prev_point.x(), self.pixmap.height())
new:
p.drawLine( int(self.prev_point.x()), 0, int(self.prev_point.x()), int(self.pixmap.height()))
531 line:
default:
p.drawLine( 0, self.prev_point.y(), self.pixmap.width(), self.prev_point.y())
new:
p.drawLine( 0, int(self.prev_point.y()), int(self.pixmap.width()), int(self.prev_point.y()))
Changed:
x:\xxxxx\python-310\Lib\site-packages\labelImg\labelImg.py
965 line:
default:
bar.setValue(bar.value() + bar.singleStep() * units)
new:
bar.setValue(int(bar.value() + bar.singleStep() * units))
Good work.

Please refer to this comment


Confine rich-text mention listbox to viewport

Pull Request
🤨 Rationale
Fixes #2217
👩💻 Implementation
Upon opening, the rich-text mention listbox now sets a availableViewportHeight property based on the distance between the bottom of the anchor element and the bottom of the window. Like with select and combobox, that property is bound to a CSS variable, which factors into the max-height for the listbox. I had to parameterize that CSS calculation with a couple new CSS variables to account for differences between the mention listbox and select/combobox.
🧪 Testing
Created a new test for the rich-text mention listbox, plus modified the existing select test to ensure that the test wasn't passing due to the default 10.5 item height limit.
✅ Checklist

[x] I have updated the project documentation to reflect my changes or determined no changes are needed.

@mollykreis could I get a buddy, please?


Retryable error for workflow rate limits in task processing

What changed?
New error that will be introduced when task processing requests are ratelimited

Why?
Task processing limits will be ratelimited based on wf-id based rate limits and needs to be retried

How did you test it?
Unit tests

Potential risks
error is still not in use

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 018e40f8-a5ba-41e9-ac0d-c8bd5be9014a
Details

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
20 unchanged lines in 4 files lost coverage.
Overall coverage increased (+0.1%) to 64.928%

Files with Coverage Reduction
New Missed Lines
%

service/history/task/transfer_standby_task_executor.go
2
86.6%

common/task/weighted_round_robin_task_scheduler.go
2
89.05%

common/persistence/historyManager.go
2
66.67%

service/history/execution/mutable_state_task_refresher.go
14
57.59%

Totals

Change from base Build 018e3638-cb8a-4a67-a257-018409c002ad:
0.1%

Covered Lines:
94662

Relevant Lines:
145795

💛  - Coveralls


Cannot get rid of "BetterBibTeX: Ready for business" notification

NB: Using test build 4201. Was also present in 4165.
On starting Zotero, there is a notification to say that BBT is initializing, etc. When complete, it gets to "BetterBibTeX: Ready for business". However, I cannot get rid of this notification. It doesn't disappear on its own and I can't click it away. Therefore, it persists while Zotero is open and is always on top, which is obviously rather annoying.
The bug reporting guidance says:

If your issue is a bug report, but not for exports, please enable extended debugging in the BBT preferences, reproduce your problem, and select "Report Better BibTeX error" from the Zotero gear menu, and post the resulting report ID (shown in red after you submit) here.

However, I cannot see an option to enable extended debugging in the BBT preferences. Am I missing something? If you can tell me how to get the debug report, I will of course post the error message as a comment below.

I have not problems with the "ready for business" notes, but a similar problem with
the "import file" notice, if I try to read a biibtex file creating problems (see side remark in #715).
After testing many files with problems, I get a stack of persistent notices, see
,
which shown up on all of my virtual desktops (kde)

@OlafKleinBerlin please file a separate issue for the import notices.
@steve-biggs extended debugging is gone (where did I leave that? I had meant to remove that from all descriptions); you can now go to Help -> Debug Output Logging -> Restart with Logging enabled and then send a debug report.

@steve-biggs I really need a debug report, without it I can't address the issue; I haven't been able to replicate it here.

Hi. Sorry - got distracted yesterday. And then today, I can't reproduce it either! I will send a debug report if it arises again but for now we will have to assume it's "fixed".

That's OK -- if it occurs again, please open a new issue.


CryptoID Coin

Hi there I'm looking for a bit of guidance at how your carboncoin api works on https://coinb.in/api/
I'm trying to setup a new coin and wondering if there is anything extra needed to run this on my own domain, other than changing the links from https://coinb.in/ to my own domain. CryptoID.info is already setup and ready to go and I have an api key for their site. Any guidance is greatly appreciated.

Hi,
I would appreciate that as well

C
@CryptoidCoin did you find any solution ? I am near to find but still need help.


crashes

The code crashes every time more or less here, regardless of what YouTube video link I give it.

TypeError                                 Traceback (most recent call last)
 in <cell line: 155>()
216         with open(outpath,'w') as f:
217             # to do: upstream PR to control verbosity
--> 218             writer.write_result(
219                 whispers[k],
220                 file=f,
TypeError: write_result() missing 1 required positional argument: 'options'

Seems that the API for whisper has changed again, I changed the code accordingly and this worked:
options = dict(
highlight_words=False,
max_line_width=None,
max_line_count=None
)
writer.write_result(
whispers[k],
f,
options
)


Vue 2 support

Any plans to support vue 2?
I have this error in a vite project with vue 2:
Uncaught SyntaxError: The requested module '/node_modules/.vite/vue.js' does not provide an export named 'Fragment
Thanks

@jpkleemans With vite-plugin-vue2 vite can be used with Vue 2. Would you consider adding support for Vue 2? Will be a while before Vue 3 becomes used by everyone.

See https://github.com/pakholeung37/vite-plugin-vue2-svg for an alternative.

Both vue2 and vue3 are supported https://www.npmjs.com/package/unplugin-svg-vue-component


When deploying project to RTD we need different project names

The default behavior is to use the same name as the repository name but this will fail for everybody except perhaps 1 person if we use the same fork name.

I close this issue as it is clearly explained to rename the project to user-word-count (with own user github name).


Add unit tests for debugging with source references

Closing this, as this has been done in PTVSD.


OPNSense v24.1.2

Has anybody upgraded to v24.1.2 yet?  Does the script still work?  I see the following in the changelog:

wireguard: key constraints should only apply on peers and not instances
wireguard: peer uniqueness should depend on pubkey + endpoint
wireguard: skip attached instance address routes
wireguard: remove duplicate ID columns

works for me ... even though I get some errors in the Log:

Those logs are to be expected, I didn't see those changes as they would cause issues, but glad to see it's working nicely.

I upgraded my instance, and it appears to be working properly as well.


The Great Typescript Refactor

This PR introduces a ~rewrite~ refactor of Primer Components into TypeScript.
We've discussed moving to TypeScript for a while now; I won't spend time discussing rationale here, but given the bugs we've had in the past around our (manually-created) typings as Primer Components has grown, and given the increasing number of TypeScript projects using PC, I believe it is well past time we made this change.
One issue with moving to TypeScript is that we want to keep propTypes; React prop types are for runtime, dev-mode checking of passed types, whereas TypeScript is only used at compile time. In order for us to keep both and not have to continue to maintain a set of propTypes as well as a set of TS interfaces, we need a way to infer one of those from the other.
Thankfully, the PropTypes package exposes a type called InferProps, which creates a TypeScript type out of a set of existing propTypes. The major challenge here is that we make heavy use of @styled-system/prop-types, which does not have an associated @types package.
For this reason, this PR includes a new script, script/create-css-prop-types.ts, which will iterate through the styled-system prop categories and create a .d.ts file that we can include in the project. This file gets checked in as src/styled-system__prop-types.d.ts.
Combined with some TS hackery in constants.ts, we have all the pieces we need to generate appropriate types. Here's an example of converting a JS component into a TS one:
Before (JS):
const Box = styled.div`
  ${COMMON}
  ${FLEX}
  ${LAYOUT}
  ${sx};
`

Box.defaultProps = {theme}

Box.propTypes = {
  ...COMMON.propTypes,
  ...FLEX.propTypes,
  ...LAYOUT.propTypes,
  ...sx.propTypes,
  theme: PropTypes.object
}

export default Box

After (TS):
const boxPropTypes = {
  ...COMMON.propTypes,
  ...FLEX.propTypes,
  ...LAYOUT.propTypes,
  ...sxPropTypes,
  theme: PropTypes.object
}

export type BoxProps = PropTypes.InferProps<typeof boxPropTypes>

const Box: React.FC<BoxProps> = styled.div`
  ${COMMON}
  ${FLEX}
  ${LAYOUT}
  ${sx};
`

Box.defaultProps = { theme }

Box.propTypes = boxPropTypes

export default Box

This PR also updates Jest settings for testing TS files (and eventually writing tests in TS), and updates the Gatsby config in the docs/ folder to ensure that live editing of docs and components still works.

@BinaryMuse so excited for this! I have one question that I've been mulling over - does this approach limit the kinds of types we can use of our components to the constraints of the React.propTypes API? Are there things that we can do in TS that we can't do using React.propTypes? Will you have any recommendations for writing good prop types that will be easily translated to TS?

does this approach limit the kinds of types we can use in our components to the constraints of the React.propTypes API?

I'm still exploring but from what I can tell, InferProps handles most of the basic cases. For situations where we want additional information in our TS types (aka, we actually want the TS types to diverge from propTypes), we can do our own thing. For example, here's a change to Box.tsx that typechecks:
diff --git a/src/Box.tsx b/src/Box.tsx
index 58e71ca4..a8ff783c 100644
--- a/src/Box.tsx
+++ b/src/Box.tsx
@@ -10,10 +10,15 @@ const boxPropTypes = {
   ...FLEX.propTypes,
   ...LAYOUT.propTypes,
   ...sxPropTypes,
+  onClick: PropTypes.func,
   theme: PropTypes.object
 }

-export type BoxProps = PropTypes.InferProps<typeof boxPropTypes>
+export type BoxProps = Omit<PropTypes.InferProps<typeof boxPropTypes>, "onClick">
+  & {
+    onClick?: (event: React.MouseEvent<HTMLDivElement, MouseEvent>) => void
+  }

 const Box: React.FC<BoxProps> = styled.div`
   ${COMMON}
@@ -22,6 +27,8 @@ const Box: React.FC<BoxProps> = styled.div`
   ${sx};
 `

+const b = <Box onClick={true} />
+
 Box.defaultProps = { theme }

 Box.propTypes = boxPropTypes

I guess my worry is that we are obscuring using actual TS too much by compiling the types from our prop types and that could lead to unintentionally compiling the wrong types

I think this is a reasonable worry, but given how seldom we actually do anything fancy with the TS types, I believe it will be far easier to deal with InferProps and handle edge cases ourselves.
Also, similar to the way I manually typed the styled-system propTypes, we can create our own propTypes that have both runtime checking and inferable TS types.

given how seldom we actually do anything fancy with the TS types, I believe it will be far easier to deal with InferProps and handle edge cases ourselves.
I agree! I think we should continue forward with this approach, only thing I think we'll need to make sure we have before shipping is some way to know if InferTypes is working as we expect it to before shipping changes + maybe some Do's & Dont's for folks around what kinds of things will get translated fine by InferTypes and what things won't. My worry is that right not it's not super clear what output you're going to get from InferTypes unless you manually spot check in the file like you did in your example. Would you be able to hover over the component declaration to see what InferTypes outputs?

One thing to add: I think the name InferProps is a little misleading; it uses the TypeScript type inference but the actual prop types themselves are strongly typed.

So, as long as you know the associated propType has the correct PropTypes.Requirable or PropTypes.Validator type attached, you should be good to go.
How would you check this? Do all values on the React.propTypes object have these?

Similarly, one can use the same mechanism for building your own more complex propTypes with more detailed TS types that infer correctly. For example:
type MouseEventHandler = (event: React.MouseEvent<T, MouseEvent>) => void
// a more specific PropTypes.func; only difference is the associated type
const divClickHandlerPropType = PropTypes.func as PropTypes.Requireable<MouseEventHandler>

This is awesomeeeeee 😻

How would you check this? Do all values on the React.propTypes object have these?

Yes, all the built-in prop types from @types/prop-types have TS types that work as you'd expect them to work given how they work at runtime in JS

Closing in favor of https://github.com/primer/components/pull/959

Closing in favor of https://github.com/primer/components/pull/959


Request on LAN error, V1.4.9

Hey,
While I make a post request to LAN address(like <IP_ADDRESS>),it post to localhost.
This happens on Nexus 4/5/6.I find out the problem in httpclient lib.
Class SchemeSocketFactoryAdaptor, line 65,here u should
invoke connectSocket(Socket, InetSocketAddress, InetSocketAddress, HttpParams)
instead of the deprecated method.
if u confirm or solve this issue, please comment here.
Thanks for this great lib!

I should make it more clearly,on my device (Nexus 5, Android 6.0),InetSocketAddress.getHostName();
returns wrong result "localhost"  for address like <IP_ADDRESS>. Hope this helpfull.

I get the same error .I request <IP_ADDRESS>:8081, java.net.ConnectException: failed to connect to localhost/<IP_ADDRESS> (port 8081) after 10000ms: isConnected failed: ECONNREFUSED (Connection refused).

I get the same error.
java.net.ConnectException: failed to connect to localhost/<IP_ADDRESS> (port 8080) after 3000ms: isConnected failed: ECONNREFUSED (Connection refused).
how to solve it?

Questions related to requests to local/ip addresses, that fail, will be tracked under #998


Adds the default maven repositories if extra ones are added

Avoids the default maven repositories being removed from the maven settings by the new specified repositories

Release Note

When overriding the maven repository settings, the default repositories should still be retained to avoid losing the base
dependencies.

This should be in 1.10.x too I guess.

I'd prefer not to mention ENTESB in a commit log for upstream Camel projects. Otherwise all look good.

No worries. Repushed commits in this and backport PRs.


Error during installation of deps

Any suggestion to fix this error?
Collecting xformers
  Using cached xformers-0.0.23.post1-cp310-cp310-manylinux2014_x86_64.whl (213.0 MB)
  Using cached xformers-0.0.23-cp310-cp310-manylinux2014_x86_64.whl (213.0 MB)
  Using cached xformers-0.0.22.post7-cp310-cp310-manylinux2014_x86_64.whl (211.8 MB)
  Using cached xformers-0.0.22-cp310-cp310-manylinux2014_x86_64.whl (211.6 MB)
  Using cached xformers-0.0.21-cp310-cp310-manylinux2014_x86_64.whl (167.0 MB)
  Using cached xformers-0.0.20-cp310-cp310-manylinux2014_x86_64.whl (109.1 MB)
  Using cached xformers-0.0.19-cp310-cp310-manylinux2014_x86_64.whl (108.2 MB)
Collecting pyre-extensions==0.0.29
  Using cached pyre_extensions-0.0.29-py3-none-any.whl (12 kB)
Collecting xformers
  Using cached xformers-0.0.18-cp310-cp310-manylinux2014_x86_64.whl (123.8 MB)
Collecting pyre-extensions==0.0.23
  Using cached pyre_extensions-0.0.23-py3-none-any.whl (11 kB)
Collecting xformers
  Using cached xformers-0.0.17-cp310-cp310-manylinux2014_x86_64.whl (123.6 MB)
  Using cached xformers-0.0.16-cp310-cp310-manylinux2014_x86_64.whl (50.9 MB)
  Using cached xformers-0.0.13.tar.gz (292 kB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [6 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-mu60tz0e/xformers_4aa19d62bcc44da58b0f254d6573d196/setup.py", line 18, in <module>
          import torch
      ModuleNotFoundError: No module named 'torch'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

Can you share the commands you ran leading upto this error please?

Commands are from your Environment setup.

For running the code, I used RunPod instance with Python 3.10 and Cuda 11.8.0.
Deps are installed using python virt env.

Sorry, a bit unsure what's going on here...
Can you run the following and give us the results please?
wget https://raw.githubusercontent.com/pytorch/pytorch/main/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py

(for security, reference of this is from PyTorch bug reporting template)
by the way, I've always had some issue getting torch/torch dependencies working on runpod :( can you try somewhere else like vast.ai or jarvis cloud?

@vatsalaggarwal it looks like that error is raised if deps is installed using virtual env.
When I install deps using system python, it's fine. I've attached logs while it's virtual env:
env_info.txt

Had exactly the same issue on Runpod. @Subuday : Were you able to get it running after installing with system python?

Taking my question back. I managed to run it on Runpod. Not using the venv worked. Thank you

I think this is a runpod specific issue, with the resolution being to not use venv, so I'm going to close this issue.


[DS-3967] 6x - Migrate Dockerfile to DSpace/DSpace

https://jira.duraspace.org/browse/DS-3967

The local.cfg can be gerated at build time as shown here: https://github.com/ppmdo/dspace-docker/blob/93bb794e97b9fa90ed00981721b3de809f1cf5f5/Dockerfile#L52
Although I think that approach can get quite complicated if the dspace.cfg many modifications.
Also, It could be useful to build with Mirage2 included and the let the user select what theme to use via an ENV variable as shown here: https://github.com/ppmdo/dspace-docker/blob/93bb794e97b9fa90ed00981721b3de809f1cf5f5/Dockerfile#L63

@ppmdo , thanks for the comments.  I had not thought about Mirage2 support.
I am going to test building the images with Mirage2 enabled by default.  It will slow the build down a bit, but it should give the end user more flexibility with theme selection.  I will share my progress on this.
I envision that the user will use a volume mount in the docker compose file to override any additional properties at runtime (local.cfg, xmlui.xconf).  My hope is to minimize the number of variant Docker images that the project will support.
Now that the Dockerfile will exist on each supported branch of DSpace, I have customized the Dockerfiles to provide a minimal local.cfg or build.properties file within each branch.  If you take a look at the related PR's you will see that I am providing the files to be overridden.

https://github.com/DSpace/DSpace/pull/2137 - 4x (build.properties)
https://github.com/DSpace/DSpace/pull/2136 - 5x (build.properties)
https://github.com/DSpace/DSpace/pull/2135 - 7x (local.cfg)

I agree with the files being overridden instead of generated. It's makes it simpler yet flexible.

Tested on Fedora 27. Works flawlessly.

Tested in Windows 10 with the following docker-compose file: https://github.com/DSpace-Labs/DSpace-Docker-Images/pull/51/files#diff-e437aab83f63209d609c14191f498e5e
Works without problems, with and without the Mirage2 option.


Fix Failing Tests on Windows (WIP)

This is in line with #8
I'm working on getting the test cases to pass for Windows.
Upon installation, 6 of the 70 existing tests were failing. Here's a short summary of them:
=================================================== short test summary info ===================================================
FAILED test/test_open.py::TestSafer::test_file_perms - AssertionError: -rw-rw-rw-
FAILED test/test_open.py::TestSafer::test_symlink_directory - OSError: [WinError 1314] A required privilege is not held by the client: 'sub' -> 'sub.sym'
FAILED test/test_open.py::TestSafer::test_symlink_file - OSError: [WinError 1314] A required privilege is not held by the client: 'one' -> 'one.sym'
FAILED test/test_open.py::TestSafer::test_tempfile_perms - assert 33206 in (33188, 33204)
FAILED test/test_writer.py::test_wrapper_bug2 - PermissionError: [WinError 32] The process cannot access the file because it is being used by another process: 'C:\\Users\\...
FAILED test/test_writer.py::test_wrapper_bug3 - PermissionError: [WinError 32] The process cannot access the file because it is being used by another process: 'C:\\Users\\...

Fixed tests

[x] test_file_perms
[x] test_symlink_directory
[x] test_symlink_file
[x] test_temlpfile_perms
[ ] test_wrapper_bug2
[ ] test_wrapper_bug3

Summary by Sourcery
Bug Fixes:

Fix the test_file_perms test to handle file permission checks correctly on Windows by adjusting the logic to account for Windows-specific file handling.

@rec
The symlink directory and files tests will work only on the condition that the tests are being run in a terminal that contains admin privileges. Unfortunately, admin privileges are not given to terminals by default (but can be changed). I set the test to skip for Windows if admin privileges are not given (instead of failing), but they will pass if given (or will fail if the source of errors is not from privileges).

Looks good for another round of reviews

So it's very natural to demonstrate that you comprehend and are keeping up, but a magic secret to appearing to be a more senior programmer is only talking about operative or actionable questions.
Overall, you don't need to respond to comments if you agree with them, or say what you are going to do, unless there's a question!  :-D  (Also, you should use the review feature to group together comments in one email, not that it's a big deal, particularly with such a small project.)
Computer programming is a very noisy occupation so I spend extra care in only sending people messages which are actionable, i.e., ask them to do something, or ask a question, or give them information they asked for.
Otherwise, people simply miss stuff in the traffic.
This also leaves more time for actual chat. 🔈
As I said, it's extremely natural, so don't think it's some sort of sin. Mostly you discover this somewhat later, when you have multiple junior programmers each trying to out-volume the other in progress reports... 😈

@rec A pending workflow approval

Voila: https://github.com/rec/safer/pull/28
I'll add you as a reviewer once you've accepted my invitation on this repo...


How to use with Remixjs?

i'm getting this error below when loading the root of my web app.  code editor is on a separate route.
and i'm getting this same error after following the advice here: https://remix.run/docs/en/v1/pages/gotchas#importing-esm-packages
that is, adding this package to my remix.config.js isn't helping.  any suggestions would be greatly appreciated! ty for an awesome component
Error [ERR_REQUIRE_ESM]: require() of ES Module /Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/rehype/index.js from /Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/api/index.js not supported.
Instead change the require of /Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/rehype/index.js in /Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/api/index.js to a dynamic import() which is available in all CommonJS modules.
    at<EMAIL_ADDRESS>(/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/api/index.js:819:118)
    at /Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/api/index.js:7:50
    at<EMAIL_ADDRESS>(/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/api/index.js:1058:362)
    at /Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/api/index.js:7:50
    at Object.<anonymous> (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/api/index.js:17853:49)
    at /Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/@remix-run/serve/dist/index.js:43:17
    at Layer.handle [as handle_request] (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/layer.js:95:5)
    at next (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/route.js:144:13)
    at next (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/route.js:140:7)
    at next (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/route.js:140:7)
    at next (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/route.js:140:7)
    at next (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/route.js:140:7)
    at next (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/route.js:140:7)
    at next (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/route.js:140:7)
    at Route.dispatch (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/route.js:114:3)
    at Layer.handle [as handle_request] (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/layer.js:95:5)
    at /Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/index.js:284:15
    at param (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/index.js:365:14)
    at param (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/index.js:376:14)
    at Function.process_params (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/index.js:421:3)
    at next (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/index.js:280:10)
    at logger (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/morgan/index.js:144:5)
    at Layer.handle [as handle_request] (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/index.js:328:13)
    at /Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/index.js:286:9
    at Function.process_params (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/index.js:346:12)
    at next (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/express/lib/router/index.js:280:10)
    at SendStream.error (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/serve-static/index.js:121:7)
    at SendStream.emit (node:events:513:28)
    at SendStream.error (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/send/index.js:270:17)
    at SendStream.onStatError (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/send/index.js:417:12)
    at next (/Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/send/index.js:759:28)
    at /Users/stuartrobinson/repos/mailpotato/frontend/mk-remix-supabase-public-demo/node_modules/send/index.js:767:23
    at FSReqCallback.oncomplete (node:fs:190:21)

https://github.com/uiwjs/react-md-editor/issues/446#issue-1417594634

Not sure if there is a similar solution
@stuartcrobinson

This is a bit belated, but a guy on my team was able to work around that error by using Lazy and Suspense:
import React, { Suspense } from "react";

const LazyCodeEditor = React.lazy(() => import("@uiw/react-textarea-code-editor"));

export const CodeEditor: React.FunctionComponent<Parameters<typeof LazyCodeEditor>[0]> = (
  props
) => (
  <Suspense>
    <LazyCodeEditor {...props} />
  </Suspense>
);

And then import CodeEditor from this file when I want to use


Async partyinfo requests

Codecov Report

Merging #956 into master will increase coverage by 0.06%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #956      +/-   ##
============================================
+ Coverage     99.31%   99.38%   +0.06%
  Complexity     2088     2088
============================================
  Files           320      320
  Lines          5709     5705       -4
  Branches        328      323       -5
============================================
  Hits           5670     5670
  Misses            5        5
+ Partials         34       30       -4

Impacted Files
Coverage Δ
Complexity Δ

.../com/quorum/tessera/partyinfo/PartyInfoPoller.java
100% <100%> (ø)
9 <1> (ø)
:arrow_down:

...a/config/cli/admin/subcommands/AddPeerCommand.java
100% <0%> (+2.63%)
11% <0%> (ø)
:arrow_down:

.../quorum/tessera/sync/SyncResponseMessageCodec.java
100% <0%> (+3.22%)
5% <0%> (ø)
:arrow_down:

...ain/java/com/quorum/tessera/p2p/RestP2pClient.java
100% <0%> (+6.89%)
9% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


Add Parameter Information/Params to Quartz API Endpoints

Hey there, I don't have time to fix this or add the feature so I figured I'd log some things that would be good additions to the project.
Now that JobParameters can be specified for scheduled jobs, it would be pretty straightforward via the structures you've setup to expose these via the API, so you can see the parameters that a scheduled job is configured to run for.
Would also be pretty cool to add an optional parameter/body to specify job parameters for a scheduled job that you're initiating via the REST API.

Great ideas. I will have a look as soon as I get a chance. Pull request
always welcome :-)
On Thu, Jun 4, 2020, 20:07 jblayneyXpanxion<EMAIL_ADDRESS>wrote:

Hey there, I don't have time to fix this or add the feature so I figured
I'd log some things that would be good additions to the project.
Now that JobParameters can be specified for scheduled jobs, it would be
pretty straightforward via the structures you've setup to expose these via
the API, so you can see the parameters that a scheduled job is configured
to run for.
Would also be pretty cool to add an optional parameter/body to specify job
parameters for a scheduled job that you're initiating via the REST API.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/chrisgleissner/spring-batch-rest/issues/18, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6JA6YCAHGLVKVSV7EEC33RU7PE3ANCNFSM4NS3Q5PA
.


Fix classroom form state

This does two things:

Fixes a possible regression I introduced that I noticed while debugging #74

The classroom create/edit form wasn't clearing out the form fields on unmount, so when you created a classroom and then clicked to create another (or edit), the form field had the previous content.

This also adds a consistent sort order for the I2A assignments

Note: I'm not really sure why all those commits are showing up... It looks like something odd happened while rebasing. I can squash those if you want me too... or we can squash on merge.

At the moment, I'm encountering an error loading I2A Assignments:

master looks OK, so it seems to be some issue with this bit here...
props.assignments[classroom.id].map((assignment) => {
  const projectUrl = (assignmentsMetadata && assignmentsMetadata[assignment.workflowId]) ?
    `${config.zooniverse}/projects/${assignmentsMetadata[assignment.workflowId].slug}/classify?group=${classroom.attributes.zooniverse_group_id}` :
    null;

...where, for some reason, there are cases where assignment is null/undefined. (Specifically, props.assignments['316'] = [undefined, undefined, undefined] - whuuuh?)

@shaunanoordin thanks for catching that. There is an edge case of I2A classrooms that do not have assignments. These may have been created while there was that issue with the API with linking assignments correctly. zootester1 has one of these classrooms. I moved the code to sort the assignments out into its own function and do a existential check on the assignments first before returning the sorted assignments.


Error: Cannot find module 'webpack/schemas/WebpackOptions.json'

When runing docz I get an  Error: Cannot find module 'webpack/schemas/WebpackOptions.json'.
How can I solve that?

@Jole83 Execute the yarn  yarn docz dev, with npm happened the error

I have the same question. So this is strictly an issue with using npm vs. yarn?

Issue #56 may also be a good reference. So far I have tried to install webpack as a dev-dependency through npm. I've gotten a new error, and saw docz try to compile which is promising:
Note: portfolio is simply the name of the repo I'm working in.
 ERROR  Failed to compile with 1 errors                                 09:36:17

 error  in ./.docz/app/index.jsx

Module build failed (from ./node_modules/happypack/loader.js):
Error: Plugin/Preset files are not allowed to export objects, only functions. In /Users/alex/Repos/portfolio/node_modules/babel-preset-react/lib/index.js
    at createDescriptor (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-descriptors.js:178:11)
    at items.map (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-descriptors.js:109:50)
    at Array.map (<anonymous>)
    at createDescriptors (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-descriptors.js:109:29)
    at createPresetDescriptors (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-descriptors.js:101:10)
    at passPerPreset (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-descriptors.js:58:96)
    at cachedFunction (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/caching.js:33:19)
    at presets.presets (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-descriptors.js:29:84)
    at mergeChainOpts (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-chain.js:315:26)
    at /Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-chain.js:278:7
    at buildRootChain (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-chain.js:68:29)
    at loadPrivatePartialConfig (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/partial.js:57:55)
    at Object.loadPartialConfig (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/partial.js:82:18)
    at Object.<anonymous> (/Users/alex/Repos/portfolio/node_modules/docz-core/node_modules/babel-loader/lib/index.js:105:26)
    at Generator.next (<anonymous>)
    at step (/Users/alex/Repos/portfolio/node_modules/docz-core/node_modules/babel-loader/lib/index.js:3:221)

 @ multi<EMAIL_ADDRESS>./.docz/app/index.jsx

So I chased this down to yet another issue. Issue #304.
If you've managed to get to the point where you are getting the Plugin/Preset error, I'm thinking your configuration has to do with Babel 7.
As @pedronauck stated in that thread,

@whoisryosuke this happen because we have some babel plugin/preset that's using an older version of babel, deleting your node_moduels or yarn.lock can resolve this maybe... If this doesn't fix your bug, try to see if the version of your babel-preset-react is using babel 7 🙏

I tried deleting my package-lock.json, and npm i-ing, but still no luck.
I also tried installing @babel/preset-react following the official documentation, but I'm still receiving the same error.

Ah shoot. I forgot that I copied my package.json after I uninstalled Docz because it wasn’t working. I can install it again, but I’m 99% sure it still won’t work.

This error is probably due to @babel/core v7 trying to use babel-preset-react that is in v6.
Do you have any dependencies that rely on babel 6?

Recently I updated react-scripts to v2.0.0 as create-react-app was recently updated. I'm not sure how much this had to do with it, but I just tried installing Docz as a dev-dependency again. Still got an error, but it's a different one. Maybe @mpivaa or @pedronauck could assist?
Output
again, any reference to portfolio is just the project I'm working on.
><EMAIL_ADDRESS>docz:dev /Users/alex/Repos/portfolio
> docz dev

 ERROR  Failed to compile with 1 errors                                 14:32:50

 error  in ./.docz/app/index.jsx

Module build failed (from ./node_modules/happypack/loader.js):
Error: Cannot find module 'babel-preset-env' from '/Users/alex/Repos/portfolio'
- Did you mean "@babel/env"?
    at Function.module.exports [as sync] (/Users/alex/Repos/portfolio/node_modules/resolve/lib/sync.js:40:15)
    at resolveStandardizedName (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/files/plugins.js:101:31)
    at resolvePreset (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/files/plugins.js:58:10)
    at loadPreset (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/files/plugins.js:77:20)
    at createDescriptor (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-descriptors.js:154:9)
    at items.map (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-descriptors.js:109:50)
    at Array.map (<anonymous>)
    at createDescriptors (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-descriptors.js:109:29)
    at createPresetDescriptors (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-descriptors.js:101:10)
    at passPerPreset (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-descriptors.js:58:96)

 @ multi<EMAIL_ADDRESS>./.docz/app/index.jsx

 WAIT  Compiling...                                                     14:32:50

 ERROR  Failed to compile with 1 errors                                 14:32:50

 error  in ./.docz/app/index.jsx

Module build failed (from ./node_modules/happypack/loader.js):
Error: Cannot find module 'babel-preset-env' from '/Users/alex/Repos/portfolio'
- Did you mean "@babel/env"?
    at Function.module.exports [as sync] (/Users/alex/Repos/portfolio/node_modules/resolve/lib/sync.js:40:15)
    at resolveStandardizedName (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/files/plugins.js:101:31)
    at resolvePreset (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/files/plugins.js:58:10)
    at loadPreset (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/files/plugins.js:77:20)
    at createDescriptor (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-descriptors.js:154:9)
    at items.map (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-descriptors.js:109:50)
    at Array.map (<anonymous>)
    at createDescriptors (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-descriptors.js:109:29)
    at createPresetDescriptors (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-descriptors.js:101:10)
    at passPerPreset (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-descriptors.js:58:96)
    at cachedFunction (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/caching.js:33:19)
    at presets.presets (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-descriptors.js:29:84)
    at mergeChainOpts (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-chain.js:315:26)
    at /Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-chain.js:278:7
    at buildRootChain (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/config-chain.js:68:29)
    at loadPrivatePartialConfig (/Users/alex/Repos/portfolio/node_modules/@babel/core/lib/config/partial.js:85:55)

 @ multi<EMAIL_ADDRESS>./.docz/app/index.jsx

You're trying to use babel-preset-env instead o @babel/env. The first one is deprecated since is preset from an older version of Babel. You need to update your babel packages using babel-upgrade

Fixed! Thanks @pedronauck . Installed babel-upgrade, ran it, and it re-installed Docz.
.babelrc
{
-  "presets": ["env", "react"]

+  "presets": [
+    "@babel/preset-env",
+    "@babel/preset-react"
+  ]
}


Unique name for Collectible Token(s)

The default in contracts from the Rarible branch is set like this: ERC721("YourCollectible", "YCB")
Propose changing to ERC721("Grapheme", "PHEME").
That's for a "Letter". Then for the "Word", how about ERC721("GraphemeCombo", "PHEMEBO").

("Grapheme", "PHEME"). sure
why PHEMEBO ?

I was thinking:
graPHEME -> PHEME
graPHEME comBO -> PHEMEBO
Just the last syllable of each word.

Do we need seperate contracts for Letter and Word? There will be only one of each anyway.

word needs to contain links to a bunch of letters, would seem cleaner to separate them?
or are you thinking of putting multiple features into one contract and the client just uses different functions on diff pages?

am thinking of the latter. Unless its gets too messy with naming, keeping it in one contract is better.
Also, helps in listing a single contract for marketplaces.

Looks like it's 1 contract that contains both Letters and Words. Maybe not ideal but if it works...
I think it should be 2 contracts, thus having 2 names, "PHEME" and something like "PHEMEBO" or "WORD".


Avoid superfluous entries in the TOC

If pages are excluded, this will remove them from the TOC

Thanks, LGTM!

Released https://github.com/timvink/mkdocs-print-site-plugin/releases/tag/v2.6.0


Named parameters in logger message template not working correctly

I don't know if this is a library bug or a documentation mistake. The docs in the Log Message Template section indicate that you can pass in parameters out of order and it will still output them in the correct order based on the names in the string template and the passed in variables. I've been scouring the source code to figure out how the heck you managed to make that work given that the parameters are passed in via an object[] array as I was interested in utilizing similar behavior if this was possible but I can't find anything to indicate that's what is happening. I then tried to run the sample code in the docs that supposedly demonstrates this capability and it outputs the parameters in the wrong order.
To Reproduce
Steps to reproduce the behavior:

Using version 3.1.0 of packages Microsoft.Extensions.Logging/Abstractions/Debug
Run this code:

var loggerFactory = LoggerFactory.Create(builder =>
    builder.AddDebug());

var logger = loggerFactory.CreateLogger<Program>();
string p1 = "parm1";
int p2 = 2;
logger.LogInformation("Parameter values: p2: {p2}, p1: {p1}", p1, p2);

See output:

Information: Parameter values: p2: parm1, p1: 2

I thought that maybe the sample code had a mistake and it should have been like this, which would make more sense as to how it worked:
logger.LogInformation("Parameter values: p2: {p2}, p1: {p1}", new { p1, p2 });

But alas that throws an exception.
Expected behavior
Output should be:
Information: Parameter values: p2: 2, p1: parm1

Hi @mikernet. The document actually states that the names of placeholders has nothing to do with values.

The order of placeholders, not their names, determines which parameters are used to provide their values.

Oh boy, I read that wrong...my bad :)


Google basemap API signature fail on image export

Context
Image export on with Google basemaps fails because of missing signature on the API key string.
Steps to Reproduce

Login with an account with GMaps support enabled
Try and export an image
You'll get this error:

Inspecting network tab:
The Google Maps API server rejected your request. Unable to authenticate the request. Missing the 'signature' parameter. Learn more: https://developers.google.com/maps/documentation/business/webservices/auth
Following that link, looks like we need to use the client's private key to generate a signature for each URL

I think this is still valid: https://github.com/CartoDB/support/issues/650#issuecomment-297433048?

We already commented yep, closing it.


pr template with checklist

I liked the one in the hyperledger/fabric repo, so I used that as a base.
All the links seem to work correctly.
I like checklists.
I am sure most people will just start off by doing a select-all, delete, but I think this is good for people coming in.

[Current coverage][cc-pull] is 44.39%

Merging [#80][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master        #80   diff @@
==========================================
  Files            29         29
  Lines          3548       3548
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1575       1575
  Misses         1973       1973
  Partials          0          0

Powered by Codecov. Last updated by [613828d...8620f31][cc-compare]
[cc-base-branch]: https://codecov.io/gh/cloudviz/agentless-system-crawler/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/cloudviz/agentless-system-crawler/compare/613828dde2792912c66def9ffd6c2ec92db896a2...8620f31a8ba13461f794df662761aad8ac84cbc6?src=pr
[cc-pull]: https://codecov.io/gh/cloudviz/agentless-system-crawler/pull/80?src=pr

lgtm


Received status code 401 from server: Unauthorized

Could not GET 'https://jitpack.io/com/github/smarteist/autoimageslider/1.4.0/autoimageslider-1.4.0.pom'. Received status code 401 from server: Unauthorized
While building the project.

Did you recently update the Android studio version to 4.x.x or later?

Did you recently update the Android studio version to 4.x.x?

I updated the Android Studio to Arctic version. What is the solution?

Have the same problem. Adding jcenter inside repositories in build.grade can temporarily fix it

Did you recently update the Android studio version to 4.x.x?

Yes

Did you recently update the Android studio version to 4.x.x?

Yes, Arctic Version

Did u get any solution?

I ended up deleting this library.
But I think you can resolve it this way!
allprojects {
    repositories {
        google()
        jcenter() << add this line! (A warning pops up saying that 'jcenter' is deprecated.)
        ...

I ended up deleting this library. But I think you can resolve it this way!
allprojects {
    repositories {
        google()
        jcenter() << add this line! (A warning pops up saying that 'jcenter' is deprecated.)
        ...

I added this. After doing I got more errors.

getting the same issue but have not fine any solution in this how to acces this repo or how we get the full access of this repo

I am Also Getting the same error

My Android studio version Koala-2024.1.1 Patch 1

How Can i Resolve it

I Don't know why developer make some these type of libraries whey are not able to manage them and other dev struggling to resolve , if you have not any solution for you library so please make it private don't make it public

How Can i Resolve it

I made it local lib and used it. If you want, I can give the access!!!

It will be great help if you can share

It will be great help if you can share

Could you please try the older version:
com.github.smarteist:autoimageslider:1.3.7-appcompat

please share @misbahazmi

please share @misbahazmi
Could you please try the older version:
com.github.smarteist:autoimageslider:1.3.7-appcompat

Could you please try the older version:
com.github.smarteist:autoimageslider:1.3.7-appcompat

Could not GET 'https://jitpack.io/com/github/smarteist/autoimageslider/1.3.7-appcompat/autoimageslider-1.3.7-appcompat.pom'. Received status code 401 from server: Unauthorized
please anyone help me i facing this issue @misbahazmi


Standard Toolkit Item for JSON?

I'd suggest adding a tool like jq to the standard toolkit for working with JSON. Its my go to utility for working with JSON and getting data from APIs that I need to load into another system or tool.
Fits in very nicely to my command line toolset.

Cool - I haven't used qj before. We tend to stick with CSV files as they are smaller, more common, and support streaming (which really helps with the big stuff).
Still, this may just be because we haven't had to do much work ingesting JSON data. Feel free to add something on jq via a PR!

Will do.
My typical use case with jq is pulling JSON from a CKAN API and converting to CSV. Here's an example of doing that for data that is formatted to conform to the LIVES standard (in this case, for the City of Evanston).


HOCS-2493 : detect pushes to hotfix branches

Previous behaviour was to push an image on every build as opposed to on a build to a nominated branch (the new behaviour). This is probably fine and brings it in line with the other repos, but it's something to bear in mind.


Copy shift feature

I manually tested this, all good!
(I did notice a funny thing where since shifts are the same time, shift 2 can end up on top of shift 1 if shift 2 is copied first, but I think this is irrelevant because shifts won't be called 1 and 2).


WIP: Get rid of FixedSize

What was wrong?
FixedSize makes the type system more complex which makes it harder to add new features.
How was it fixed?
Not yet, just exploring
To-Do

[ ] OPTIONAL: Update Spec if applicable

[ ] Add entry to the release notes (may forgo for trivial changes)

[ ] Clean up commit history

Codecov Report

Merging #702 (af154d0) into master (d580097) will decrease coverage by 0.06%.
The diff coverage is 76.27%.

@@            Coverage Diff             @@
##           master     #702      +/-   ##
==========================================
- Coverage   82.03%   81.96%   -0.07%
==========================================
  Files         125      125
  Lines       10891    10905      +14
==========================================
+ Hits         8934     8938       +4
- Misses       1957     1967      +10

Impacted Files
Coverage Δ

crates/analyzer/src/db.rs
100.00% <ø> (ø)

crates/analyzer/src/errors.rs
79.59% <ø> (ø)

crates/analyzer/src/traversal/utils.rs
81.25% <ø> (-1.11%)
:arrow_down:

crates/yulgen/src/db/queries/contracts.rs
100.00% <ø> (ø)

crates/analyzer/src/db/queries/structs.rs
77.47% <42.85%> (+2.73%)
:arrow_up:

crates/analyzer/src/namespace/types.rs
71.51% <48.00%> (-1.14%)
:arrow_down:

crates/lowering/src/names.rs
61.11% <50.00%> (-5.56%)
:arrow_down:

crates/yulgen/src/types.rs
76.76% <56.52%> (-4.56%)
:arrow_down:

crates/analyzer/src/db/queries/events.rs
74.46% <66.66%> (ø)

crates/analyzer/src/traversal/types.rs
79.13% <66.66%> (ø)

... and 37 more

Continue to review full report at Codecov.

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


vueApp.config.compilerOptions.isCustomElement should be used when resolving components

For accessibility reasons, I prefer to use rehype-katex in HTML mode rather than SVG mode.
However, this causes MDC (through @nuxt/content) to spam the console with [Vue warn]: Failed to resolve component warnings, which has caused me to miss various legitimate warnings during development.
This is despite having defined isCustomElement() because, to my understanding, it is not used when directly calling resolveComponent()
Related: https://github.com/nuxt/nuxt/issues/24104

Vue 3.5 now has built-in support for MathML, and will not warn anymore with MathML elements. However, this issue still applies to those wanting to use custom elements within their markdown documents. Therefore, I'm not going to close this issue.

For anyone following this issue because of MathML tags (annotation, semantics, mfrac, etc), please follow #258 instead as that is the main issue affecting MathML usage with MDC (Vue has supported MathML since 3.4).
I won't close this issue though as it affects custom component usage with MDC regardless.


[Backport 1.21] Bump ingress controller version from 1.0.5 -> 1.2.0

please do not merge yet, still testing


Fix groupBy docs to reflect that 'v2' is default.

The groupBy docs weren't fully updated in #3953. Should probably backport to 0.10.0 too since otherwise the docs will be confusing.

👍

:+1:

skipping travis since these are only doc changes


Using data-size-mapping parameter

Hi!
How to use data-size-mapping parameter?
Could you provide an example, please?
Thanks

Maybe Try this : data-size-mapping="same as data-dimensions" data-dimensions="unit-value"

Thanks
On Feb 18, 2015 6:35 AM, "memory-d"<EMAIL_ADDRESS>wrote:

Maybe Try this : data-size-mapping="same as data-dimensions"
data-dimensions="unit-value"
—
Reply to this email directly or view it on GitHub
https://github.com/coop182/jquery.dfp.js/issues/89#issuecomment-74810593
.

is it working?

I've found yesterday an example in internet and it works. Thanks
On Feb 18, 2015 7:30 AM, "memory-d"<EMAIL_ADDRESS>wrote:

is it working?
—
Reply to this email directly or view it on GitHub
https://github.com/coop182/jquery.dfp.js/issues/89#issuecomment-74814985
.

Cool, Can you show me your markup? Boz Sometime my ads is not show the correct size.

You can view the source of mame.Co.il . Or I can answer you later..
On Feb 18, 2015 8:41 AM, "memory-d"<EMAIL_ADDRESS>wrote:

Cool, Can you show me your markup? Boz Sometime my ads is not show the
correct size.
—
Reply to this email directly or view it on GitHub
https://github.com/coop182/jquery.dfp.js/issues/89#issuecomment-74820426
.

On Wed, Feb 18, 2015 at 8:41 AM, memory-d<EMAIL_ADDRESS>wrote:

Cool, Can you show me your markup? Boz Sometime my ads is not show the
correct size.
—
Reply to this email directly or view it on GitHub
https://github.com/coop182/jquery.dfp.js/issues/89#issuecomment-74820426
.

This approach seems to work, however, it would be nice to have it explained in the documentation


remove unneede impl Default

https://rust-lang.github.io/rust-clippy/master/index.html#derivable_impls

Codecov Report

Merging #527 (243be9f) into main (7bf065d) will decrease coverage by 0.04%.
The diff coverage is 70.00%.

@@            Coverage Diff             @@
##             main     #527      +/-   ##
==========================================
- Coverage   61.14%   61.09%   -0.05%
==========================================
  Files          85       85
  Lines       12612    12532      -80
==========================================
- Hits         7711     7657      -54
+ Misses       4901     4875      -26

Cool!


Make path to LINQPAD.exe independent from source location

Thank you for your awesome work! When checking out the source code compilation failed because the path to LINQPAD in the csproj files was defined in a relative path that did not resolve on my system (my source code is not on c:).
This environment variable - once set - would make it work for arbitrary LINQPAD install locations.

Thanks, glad that you like it :) Good idea using an environment variable instead of the relative path. I've merged your changes.


Docs do not lineup with 1.0.2?

mailerlite-ruby: 1.0.2
rails: 6.1.5
ruby: 2.7.6
I'm having difficulty following the README docs. For starters, the docs namespace every call with Mailerlite, but I don't even have Mailerlite defined; for me it is MailerLite.
Next, the first "List all subscribers" call results in the following error:
> subscribers = MailerLite::Subscribers.new
> response = subscribers.list(filter: { status: 'active' })
Traceback (most recent call last):
        1: from (irb):21
NoMethodError (undefined method `list' for #<MailerLite::Subscribers:0x00007fe2f9e40ca8>)

And getting a single subscriber results in this error:
><EMAIL_ADDRESS>Traceback (most recent call last):
        2: from (irb):22
        1: from (irb):23:in `rescue in irb_binding'
NameError (uninitialized constant MailerLite::VERSION)

Happening for me as well

Thank you for pointing this out, new version is now available and the documentation has been fixed as well.


added input field for privatePlus channels

Description of change
Added input field for identity file for unlocking privatePlus channels.
Type of change

Enhancement (a non-breaking change which adds functionality)

Change checklist

[x] I have followed the contribution guidelines for this project
[x] I have performed a self-review of my own code
[x] I have updated the CHANGELOG.md, if my changes are significant enough

key has object inside:
"[object Object]-53795ac143a7fee183ffa82359cc78d70d2907cefb17baa1849be7b2e04cf6070000000000000000:e00b05152e51a318f3c84149"

logout does not remove cached shared keys


DX: Add composer keywords

as per https://github.com/composer/composer/pull/10960 this allows composer to warn the user, when installing the tool as a project dependency instead of a dev-dependency

Thank you :+1:


documentation not working

documentation not working
i tried to follow this prediction but i was not able to make it work at al... class module or weights always having problems.
https://idealo.github.io/image-super-resolution/tutorials/prediction/
please update it.

Thanks for pointing it put. Yes, it is massively outdated, please refer to the readme for now. If then you still have any specific issues, let me know


Development: Reduce the length of the commit_hash column in the submission table to 60

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[ ] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] I chose a title conforming to the naming conventions for pull requests.

Changes affecting Programming Exercises

[ ] I tested all changes and their related features with all corresponding user types on Test Server 1 (Atlassian Suite).
[ ] I tested all changes and their related features with all corresponding user types on Test Server 2 (Jenkins and Gitlab).

Motivation and Context

While working on #4732 I noticed that the commit_hash column of the submission table was set to the type varchar(255). As the commit hash is always 40 characters long this, therefore, wastes unnecessary space in the database.
Description

After talking with @krusche we decided that this should be reduced to varchar(60). The overhead of 20 characters is just a safeguard in case the commit hash is for some reason suddenly a bit longer. While should never happen, and I also checked that Bitbucket and Gitlab always return a commit hash of 40 chars, it's better to be safe than sorry.
Steps for Testing

Prerequisites:

1 Instructor

Log in to Artemis
Check that the existing submissions are still working properly
Test that new submissions can be created

Review Progress

Code Review

[ ] Review 1
[ ] Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

I was not able to deploy this PR to TS1 or TS2. The deployment to TS2 fails (here). Tried restarting it, didn't help.
Deployment to TS1 is green (here), but Artemis is stuck on "Artemis is starting up.."

I was not able to deploy this PR to TS1 or TS2. The deployment to TS2 fails (here). Tried restarting it, didn't help. Deployment to TS1 is green (here), but Artemis is stuck on "Artemis is starting up.."
EDIT: It seems that exactly the same is with other PRs, probably something is down, not PR related.

Not sure why this happened. I tested it locally (with an Atlassian setup) and it worked fine. So I guess the issue was somewhere else.


feat(shared-data): annotate labware with format +other metadata

overview
This PR adds a few metadata fields to labware definitions. The format key is the most important -- from this key, consumers of labware definitions can derive information about what behaviors to use with respect to a given labware.
Guide to info that can be derived from the new format key

FORMAT
Multichannel access ok?
Touch tip currently safe?
Is tiprack?
With multichannel, are all tips in the same well?
safe to aspirate from (ie, is a source of liquids)?

96-standard
yes
yes
no
no
yes

384-standard
yes
yes
no
no
yes

irregular
no
yes
no
n/a
yes

trough
yes
no
no
yes
yes

tiprack-96
yes
n/a
yes
n/a
no

tiprack-irregular
no
n/a
yes
n/a
no

trash
dispense only
no
no
n/a, is trash
no

Related to #1499 (WIP ticket / discussion)
Credit to @btmorr for helping come up with the formats. Ben, LMK if my modifications/additions seem OK.
Other metadata fields added

display-category: Unlike format, this should not be used to derive behavior, should only be used for user interfaces / documentation - eg in PD when adding labware to the deck, there's a modal that displays labware by category. Run App and maybe Protocol Library or our labware documentation might use this in the future too.

display-name: Human-readable version of labware name. I don't know what actual names we want to use so I didn't actually annotate any yet, I only added the field to the labware JSON schema. @pantslakz is working on the names.

tip-volume: This one will be used for behavior in PD soon. Instead of parsing the labware name string, this is a cleaner way to tell a labware def consumer how much liquid a tip can hold. Also may be used to determine if a pipette model can use a tiprack or not (eg, p10 format can only use 10uL tips, same with p1000, any pipette model >10 and <1000 can use any tips inside that range.)

changelog

annotate labware with format, display-name, display-category, tip-volume
BREAKING CHANGE: removed half "-H" tipracks

review requests
Good ideas? Alternatives?
Are my new annotations correct for all labware I touched?
OK to remove the H- tipracks?

I wasn't present for these discussions, so I'm not sure if this was discussed, but was using atomic markers for each of the "derived" behaviors considered instead of a string that encapsulates everything?
{
  format: '96-standard'
}

// vs
// (aside: booleans aren't correct for some/all of these fields, but this is an example)

{
  multichannelSafe: true,
  touchTipSafe: true,
  isTiprack: false,
  oneWellMulti: false,
  aspirateSafe: true
}

While the latter is way more verbose, it strikes me as easier to reason with and less brittle, especially if any of this behavior needs to change (or needs to change for just some labware within a single "format"). Philosophically, this reminds me of the "Twelve-factor App" section on config:

In a twelve-factor app, env vars are granular controls, each fully orthogonal to other env vars. They are never grouped together as “environments”, but instead are independently managed for each deploy. This is a model that scales up smoothly as the app naturally expands into more deploys over its lifetime.

@mcous at first I liked this idea and saw a benefit how consumers of labware definitions wouldn't each have the responsibility of deriving atomic-behavior info from the format themselves. If any format's meanings change, or a new format is added, then every consumer would need to update how that format is interpreted. That seems bad. However, after thinking about it, I feel that it probably should be the responsibility of the consumers of labware definitions to derive behaviors from formats, because those consumers all have their own differing concerns & sets of behaviors.

These aren't quite behaviors. While aspirateSafe directly informs whether a specific behavior is allowed, the others don't have a direct connection to any behavior. isTiprack isn't a behavior at all, behaviors are derived from it just like they would be from format: "tiprack" (same for oneWellMulti which could also be isTrough).

And they're not quite atomic b/c only a limited set of combinations of atoms are possible. They are mutually exclusive, or codependent. There's no isTiprack: true, aspirateSafe: true. Verbose behavior flags make it easier to add labware definitions that will cause bad behavior, probably by typo, which is easy to make across 40+ files and growing.

If Python API later on makes it safe to touch tip on a trough, someone would have to go in and update the labware definitions for all troughs. The troughs didn't change, rather the behavior of a consumer of labware definitions changed, so it seems like the wrong place to make an update. Here a consumer (Python API) is advertising its own capabilities through an annotation on the labware definitions, which seems wrong. (Also a case against denormalizing the individual files to be less verbose).

I imagine that over time, we might have to account for even more behaviors and expand this list. Every time we do that, we'll have to touch every labware file those new behaviors affect, so the update would be hard to make without errors/omissions. (To be fair, that's just an argument against a denormalization/verbosity).

Since most of these arguments are about denormalization/verbosity, how would you feel about keeping the format and adding a formats.json file like:
"96-standard": {
  multichannelSafe: true,
  touchTipSafe: true,
  isTiprack: false,
  oneWellMulti: false,
  aspirateSafe: true
},
/* etc... */

???

Something I'm very uncertain about is what kind of information we will have to add to support labware that interacts with modules...

@IanLondon following up:

isTiprack isn't a behavior at all, behaviors are derived from it just like they would be from format: "tiprack"

This is a good point, and from the app's perspective, I don't have a strong preference between isTiprack: true and format: 'tiprack'.

Verbose behavior flags make it easier to add labware definitions that will cause bad behavior, probably by typo, which is easy to make across 40+ files and growing.

I imagine that over time, we might have to account for even more behaviors and expand this list. Every time we do that, we'll have to touch every labware file those new behaviors affect, so the update would be hard to make without errors/omissions

Preventing bad labware definitions (typos, missing new fields, etc.) is the job of the schema / schema tests and whatever tooling we build to generate / update new labware definitions. I don't think this concern should really drive any data formatting decisions (or at least, they are way less important than data consumption concerns).

I feel that it probably should be the responsibility of the consumers of labware definitions to derive behaviors from formats

This is a good point, so perhaps we should look at the "behaviors" the consumers are deriving:

Multi-channel access ok?

I think this should be derived from well locations and sizes, not format

Touch-tip currently safe?

I'm not sure what determines this
Is this really the type of thing we can "switch on" for an entire class of labware at once?
Might actually belong in shared-data; see below

Is tiprack?

Mostly ambivalent

With multichannel, are all tips in the same well?

Should be derived from well locations and sizes, not format

Safe to aspirate from?

Feels wrong to me pull this from format, but I don't love safeToAspirate: true either
Maybe some sort of liquid field that can be source, destination, both, or null?
Combining with "Is tiprack?", maybe some sort of field that says what kind of resource (e.g. tips or liquid) the wells of a given labware can source or sink?

And to expand on the case of touch-tip individually, it's true that this is a capability that is driven by the consumer (the API). However, it's a behavior that multiple consumers are concerned with (e.g. PD needs to know whether to allow setting touch-tip: true in a given protocol step for a given labware). So, if the behavior is shared, at what point do we decide the behavior itself belongs in shared-data? If it doesn't live in shared-data, we need some other mechanism for preventing mismatches in derived behavior.

Since most of these arguments are about denormalization/verbosity, how would you feel about keeping the format and adding a formats.json file...

It would be a step in the right direction, provided the points above about derived behavior are addressed. I would also feel better if, in addition to formats.json, a given field was overridable in an individual labware's definition:
{
  metadata: {
    name: 'crazy-96',
    format: '96-standard',
    // touch tip doesn't work on this specific labware for some reason
    touchTipSafe: false,
  }
}

(3) from @IanLondon 's notes is the biggest reason for going this way, but I could see a compromise position where instead of saying either "isTrough" or "touchTipSafe", we said something like "rectangularWells" and then it would be an atomic marker but instead of an atomic marker for a behavior it would be a marker for some other factor and then the API could still change in terms of supporting more behaviors. Does that make sense?

Derivation Process

I think this should be derived from well locations and sizes, not format

I like the idea of deriving as much as we can, but I'm not 100% sure what that would look like. Would there be a "source" JSON schema and a "result" JSON schema with derived data? And make build would create new .json's in the build/ dir? (Right now, build.js is just merging all the files into one big JSON keyed by filename, but not deriving anything.)
Where in shared-data/ is API behavior described? Example of rectangularWells
touchTipSafe can be derived in most cases with !(touchTipSafe || rectangularWells || isTiprack || isTrash). When/if rectangular wells are supported, that will need to be updated. Makes more sense to do it on this external "annotation deriving mechanism" than inside of each individual labware defs. I guess the "annotation deriving mechanism" is the build.js script. Is that right place for Python API to describe its capabilities?

notes to self
It looks like rectangularWells can be derived as true when wells have no diameter key. Dunno what happens if ever some wells have diameter and others don't in the same labware... but I'm pretty sure that right now they're never mixed. Maybe that could be enforced in the data integrity tests in shared-data/.
I have some of the geometric logic set up to derive multichannelSafe and oneWellMulti already, in share-data/js/computeWellAccess.
isTiprack / isTrash cannot be derived, it needs to be annotated. We could do resourceType: tiprack | trash or role or whatever key

Keep format metadata field

Remove tiprack-96, tiprack-irregular, trash

Remove "touch tip safe" and safe to aspirate columns
Add top level metadata fields

isValidSource
isTiprack
deprecated

Keep validation in code for touch-tip invalid with trough and !isValidSource
Revert removal of -H
Set deprecated: true on -H and 96-PCR-flat


Pitfalls of Vue dependency detection may cause redundant dependencies

Version
2.4.2
Reproduction link
https://jsfiddle.net/sbmLobvr/9/
Steps to reproduce
click the button，then App component will update twice！
What is expected?
App component updates only once
What is actually happening?
App component updates twice

When props used in child component initialization，they will be detected as dependencies of parent component, Is there possible to stop dependency detection when entering child component initialization。

@javoski I don‘t think this would be the best solution，not just data option，but the whole child component initialization.
And I think it should be reactive, but as dependency of child component ?

@xiaodemen Sorry about that there's an ambiguity in the PR's title, component props are reactive, but they shouldn't collect dependencies during initialization of data option.

@javoski I know, but data option is NOT the only situation that shouldn't collect dependencies, e.g. component created hook, before mount hook and immediate watch ...

@xiaodemen Yes, you are right, didn't aware of that, and will try to figure out a better solution.


querystring.unescape is not a function

It's a question whether this issue should be followed up in this project as it holds the default webpack configurations or in another place?
The method is needed for example when using aws4 to sign a request.

Please file this in webpack and ask them to update the Node polyfill they're using.
When they update it, we'll get it automatically when we update webpack 😛
Thanks!


Bump native provider to version 5.15.0

Description of your changes
Bump native provider to version 5.15.0
I have:

[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

/test-examples="examples/budgets/budget.yaml"

Breaking CRD schema changes

package/crds/acmpca.aws.upbound.io_certificateauthorities.yaml
Manually:
package/crds/apigateway.aws.upbound.io_restapis.yaml
Manually:
package/crds/autoscaling.aws.upbound.io_attachments.yaml
Manually:
package/crds/autoscaling.aws.upbound.io_autoscalinggroups.yaml
Manually:
package/crds/autoscaling.aws.upbound.io_launchconfigurations.yaml
Manually:
package/crds/budgets.aws.upbound.io_budgets.yaml
Uptest: https://github.com/upbound/provider-aws/actions/runs/6089878111
package/crds/connect.aws.upbound.io_hoursofoperations.yaml
Uptest:
package/crds/connect.aws.upbound.io_queues.yaml
Uptest:
package/crds/connect.aws.upbound.io_routingprofiles.yaml
Uptest:
package/crds/directconnect.aws.upbound.io_connections.yaml
Uptest:
package/crds/dms.aws.upbound.io_endpoints.yaml
Manually:
package/crds/ec2.aws.upbound.io_defaultvpcs.yaml
Uptest:
package/crds/ec2.aws.upbound.io_routes.yaml
Uptest:
package/crds/ec2.aws.upbound.io_routetables.yaml
Uptest:
package/crds/ec2.aws.upbound.io_vpcpeeringconnectionaccepters.yaml
Uptest:
package/crds/ec2.aws.upbound.io_vpcpeeringconnectionoptions.yaml
Uptest:
package/crds/ec2.aws.upbound.io_vpcpeeringconnections.yaml
Uptest:
package/crds/ec2.aws.upbound.io_vpcs.yaml
Uptest:
package/crds/ecs.aws.upbound.io_clusters.yaml
Uptest:
package/crds/elasticache.aws.upbound.io_clusters.yaml
Uptest:
package/crds/elasticache.aws.upbound.io_replicationgroups.yaml
Uptest:
package/crds/firehose.aws.upbound.io_deliverystreams.yaml
Uptest:
package/crds/iam.aws.upbound.io_roles.yaml
Uptest:
package/crds/kafka.aws.upbound.io_clusters.yaml
Manually:
package/crds/lightsail.aws.upbound.io_instances.yaml
Uptest:
package/crds/medialive.aws.upbound.io_channels.yaml
Manually:
package/crds/networkmanager.aws.upbound.io_corenetworks.yaml
Uptest:
package/crds/rds.aws.upbound.io_instances.yaml
Manually:
package/crds/redshift.aws.upbound.io_clusters.yaml
Uptest:
package/crds/secretsmanager.aws.upbound.io_secrets.yaml
Uptest:
package/crds/transfer.aws.upbound.io_servers.yaml
Uptest:

Native schema version changes

aws_autoscaling_group
aws_db_instance
aws_dx_connection
aws_lambda_provisioned_concurrency_config

/test-examples="examples/connect/hoursofoperation.yaml"

/test-examples="examples/directconnect/connection.yaml"

/test-examples="examples/ec2/defaultvpc.yaml"

/test-examples="examples/connect/queue.yaml"

/test-examples="examples/ec2/route.yaml"

/test-examples="examples/connect/routingprofile.yaml"

/test-examples="examples/ec2/routetable.yaml"

/test-examples="examples/ec2/routetableassociation.yaml"

/test-examples="examples/ec2/vpcpeeringconnectionaccepter.yaml"

/test-examples="examples/elasticache/cluster.yaml"

/test-examples="examples/iam/role.yaml"

/test-examples="examples/ec2/vpcpeeringconnectionoption.yaml"

/test-examples="examples/elasticache/replicationgroup.yaml"

/test-examples="examples/lightsail/instance.yaml"

/test-examples="examples/networkmanager/corenetwork.yaml"

/test-examples="examples/redshift/cluster.yaml"

/test-examples="examples/secretsmanager/secret.yaml"

/test-examples="examples/transfer/server.yaml"

/test-examples="examples/ec2/vpcpeeringconnectionoptions.yaml"

/test-examples="examples/ec2/vpcpeeringconnection.yaml"

/test-examples="examples/elasticache/replicationgroup.yaml"

/test-examples="examples/firehose/deliverystream.yaml"

/test-examples="examples/rds/instance.yaml"

/test-examples="examples/lambda/provisionedconcurrencyconfig.yaml"

/test-examples="examples/ec2/vpc.yaml"

/test-examples="examples/elasticache/replicationgroup.yaml"

/test-examples="examples/rds/instance.yaml"

/test-examples="examples/kafka/cluster.yaml"

When I test resource Instance.rds with the current configuration and example in this PR, I get the following error:
    message: 'observe failed: cannot run refresh: refresh failed: only lowercase alphanumeric
      characters and hyphens allowed in "identifier": '

This issue seems to be caused by this change on the terraform side.
I did not get any successful results in my tests with the current external name configuration config.ParameterAsIdentifier("identifier"). When I use the config.IdentifierFromProvider configuration, since the identifier parameter comes spec.forProvider, there is a conflict with the identifier_prefix parameter. When I moved the identifier_prefix parameter to IgnoredFields, the resource could be created successfully.
NAME                                       READY   SYNCED   EXTERNAL-NAME                          AGE
key.kms.aws.upbound.io/sample-key-tftest   True    True     d5f6f817-5a3a-48e4-a8f9-424cb87ba7c7   88m

NAME                                                    READY   SYNCED   EXTERNAL-NAME                   AGE
instance.rds.aws.upbound.io/example-dbinstance-tftest   True    True     db-DVG3KOZWALZJBAQE5CSQULB3QU   88m

Here I need confirmation to make this change, I'm not sure this issue can be solved without changing the external name configuration.

/test-examples="examples/autoscaling/autoscalinggroup.yaml"

/test-examples="examples/autoscaling/launchconfiguration.yaml"

While testing the Cluster.kafka resource, there were deprecated parameters in the connected resources. After fixing this resource and its dependencies, I got the following error:
    message: |-
      observe failed: cannot run refresh: refresh failed: Missing required argument: The argument "arn" is required, but no definition was found.
      Missing required argument: The argument "revision" is required, but no definition was found.

Although the configurationInfo parameter is not required, we need to pass the arn and revision (required for the configurationInfo block) parameters because it comes as an empty set.
    configurationInfo:
    - {}

So I added the Configuration.kafka resource to the Cluster.kafka example, manually filled in the arn and revision parameters and added a manual intervention.
Here, this solution can be applied as a temporary solution, but it may need to be investigated further. Since it takes more than 120m to create and delete the Cluster.kafka resource, I leave it this way for now.

I think you ran into https://github.com/upbound/provider-aws/issues/489

@turkenf Do you think something like this would work to make a selector for the Configuration?
Also, I'd love it if you could bump to native provider 5.16.2, which contains a bugfix I contributed which solves #748

@mbbush, thank you for your review and contributions 🙏

@turkenf Do you think something like this would work to make a selector for the Configuration? I haven't tested it, but I'd be happy to do so if you think it's a worthwhile approach to try.

I need to do more investigation and talk to the team to find the correct solution to the error received for the Cluster.kafka resource. Maybe we can also consider moving the configurationInfo block to IgnoreFields. But in both cases, there is no harm in adding selectors for these two parameters, regardless of this PR.

Also, I'd love it if you could bump to native provider 5.16.2, which contains a https://github.com/hashicorp/terraform-provider-aws/pull/33380 I contributed which solves https://github.com/upbound/provider-aws/issues/748

I will evaluate this and check if we can upgrade to version 5.16.2

I'd love to be able to have a single selector that extracts both the arn and revision from the status of the Configuration, but I can't see how to do that within the current structure. I guess configurationInfo.arnSelector and configurtationInfo.revisionSelector is still an improvement over the current state.

@turkenf do you think this provider upgrade is going to make it into this month's release, or likely slip to next. Is there anything I can do to help it along?

@turkenf do you think this provider upgrade is going to make it into this month's release, or likely slip to next? Is there anything I can do to help it along?

@mbbush, thank you for your interest.
We will upgrade the native provider version to v5.18.1, seems that this PR will be included in the next release.

/test-examples="examples/ec2/vpc.yaml"

Hi @turkenf,
While rebasing the PR, I resolved a conflict in examples/kafka/cluster.yaml by accepting the @mbbush's changes. Changes from the feature branch were adding the manual-intervention annotation whereas Matthew has added the Configuration.kafka resource as a dependency. I assume Matthew's changes make the resource uptestable. Will trigger an uptest below.

/test-examples="examples/kafka/cluster.yaml"

/test-examples="examples/kafka/cluster.yaml"

/test-examples="examples/ec2/vpc.yaml"

After bumping version 5.15.0 to 5.19.0:
Breaking CRD schema changes

package/crds/sesv2.aws.upbound.io_emailidentities.yaml

Native schema version changes

aws_servicecatalog_principal_portfolio_association

/test-examples="examples/sesv2/emailidentity.yaml"

/test-examples="examples/rds/instance.yaml"

/test-examples="examples/sesv2/emailidentity.yaml"

/test-examples="examples/servicecatalog/principalportfolioassociation.yaml"

/test-examples="examples/docdb/cluster.yaml"

test-examples="examples/docdb/clusterparametergroup.yaml"

test-examples="examples/docdb/clusterparametergroup.yaml"

/test-examples="examples/docdb/clustersnapshot.yaml"

Covered in https://github.com/upbound/provider-aws/pull/1037


[easy] Remove python3.4 (EOL) testing.

Addresses #412 .

Codecov Report

Merging #413 into master will increase coverage by 1.35%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #413      +/-   ##
==========================================
+ Coverage   85.46%   86.81%   +1.35%
==========================================
  Files          39       39
  Lines        1844     1995     +151
==========================================
+ Hits         1576     1732     +156
+ Misses        268      263       -5

Impacted Files
Coverage Δ

hca/dss/__init__.py
94.44% <0%> (+3.79%)
:arrow_up:

Continue to review full report at Codecov.

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

Python 3.4 is still listed in setup.py.   If we're not testing it against a release, shouldn't we stop declaring support for that release?


MAUI Blazor template name change

Fixes #28644
✔ Preview 3 is out now. I'll be moving to take screenshots ~and get this merged by EOD, Tuesday, 4/11~.
UPDATE (4/12): I have the Windows screenshots, but I wasn't able to get the new template with Preview 3 and latest VS4Mac on the Mac. On the Mac, I'll try that workload reinstall trick that worked on Windows to see if I can get the new template to load/name to show.

Internal previews

📄 File
🔗 Preview link

aspnetcore/blazor/hybrid/class-libraries.md
Share assets across web and native clients using a Razor class library (RCL)

aspnetcore/blazor/hybrid/developer-tools.md
Use browser developer tools with ASP.NET Core Blazor Hybrid

aspnetcore/blazor/hybrid/reuse-razor-components.md
Reuse Razor components in ASP.NET Core Blazor Hybrid

aspnetcore/blazor/hybrid/root-component-parameters.md
Pass root component parameters in ASP.NET Core Blazor Hybrid

aspnetcore/blazor/hybrid/tutorials/maui.md
Build a .NET MAUI Blazor app

@danroth27 ... I'm stuck on the Mac side of this. I have latest preview of VS4Mac with Preview 3 installed, and I can see Preview 3's SDK showing up in the VS4Mac preferences as an installed SDK (and Pre3 runtime is indicated). On the Mac, I tried the dotnet workload install maui command with a restart that worked on Windows ... no 🎲🎲.
Do you know why I can't get the updated templates on the Mac? Do you want me to proceed with this without updating the Mac guidance at this time and circle around later to address the Mac template name and screenshots?

@guardrex There are some known issues with .NET 8 and VS4Mac right now. You should probably hold off on dealing with the VS4Mac side for the time being.

Converting to "addresses" the issue PR. Will circle around for Mac updates to fix the issue later.


@ExampleProperty not working properly with redoc

springfox version: 3.0.0-SNAPSHOT
I want to manually specify a json for my example response. My code is
@ApiResponses({
        @ApiResponse(code = 200, message = "",
            examples = @Example(value =
                {
                    @ExampleProperty(
                        mediaType = "application/json",
                        value = "{\n" +
                            "  \"resourceType\": \"Parameters\",\n" +
                            "  \"parameter\": [\n" +
                            "    {\n" +
                            "      \"name\": \"basis-of-calculation\",\n" +
                            "      \"valueString\": \"projected\"\n" +
                            "    }\n" +
                            "  ]\n" +
                            "}")
                }
            ))
    })

It is working well in swagger UI:

However in redoc the input is just read as a string rather than parsed correctly as json:

Do you know why this would be the case?

Not really sure as I dont know much about redoc


404 error while downloading /img/icons/apple-touch-icon-152x152.png

Thanks for filing a bug report :-)
Steps to Reproduce

Disable cache
Open the dApp

Expected Result

No 404 errors

Actual Result

404 error while downloading /img/icons/apple-touch-icon-152x152.png

Additional Infos (Optional)
- Browser & version
- Browser console errors
- Device / OS

@taleldayekh this issue is not really reproducible by me, infact at this point there is no apple-touch-icon-152x152.png image
but yes I have got these errors
these are
401 --> displayname
429 --> avatar_url
errors and not serious errors that we should look into. They do not affect the functioning of the app at all.

Seems like only happens for apple devices
https://stackoverflow.com/questions/12480497/why-am-i-getting-error-for-apple-touch-icon-precomposed-png
https://statamic.com/forum/1488-how-to-get-rid-of-apple-touch-iconpng-fl

Ok, thank you @agatsoh . Then we will keep the issue open, I'll assign myself and look into it on my mac.

Ok, I cannot reproduce this either. I tried disable the cache and loaded the dApp in Safari, Chrome, Brave and Firefox. Also, we don't have any touch icon defined in the header tag. In fact, I am not getting any 404s.
Closing issues, open again if anyone encounters this.


Cannot run on a Hyper-V VM

Hello
I am trying to run this command on an Hyper-V VM ( Windows 10 ), I am running using an Administrator account. When I run the command I receive  the following message
TPM Virtual Smart Card management cannot be used within a Terminal Services session.
(0x800704d3) The request was aborted.
Connecting to a VM running on Hyper-V appears to be a 'terminal service session'
Therefore I tried creating a scheduled tasks and run as a schedule task (but still did not word, no virtual smart card present)
The scheduled tasks history tab shows the following information
Task Scheduler successfully completed task "\CreateVSC" , instance "{598d612b-82f6-4bf8-b8e6-c5a299bf3882}" , action "tpmvscmgr.exe" with return code<PHONE_NUMBER>.
I also tried PowerShell remoting from another computer and running as an administrator I get access denied
Any ideas, please?
Thanks

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

ID: cd394c7d-fdbf-a600-3d3a-8c89afe8f8b9
Version Independent ID: c12170b3-f5be-c0d6-36a3-05ce33f3bea0
Content: tpmvscmgr
Content Source: WindowsServerDocs/administration/windows-commands/tpmvscmgr.md
Product: windows-server
Technology: windows-commands
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

Hello,
Will the issue be fixed please, and an new download available or if there a way around this?
Thank you

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


[Feature] Allow proxy for ConnectAsync and ConnectOverCdpAsync

My employer (an enterprise organization) requires most outgoing traffic to use a proxy.
One of our requirements is to connect to an existing browser that hosted outside our network. (i.e. BrowserStack)
Currently it's not possible to configure a proxy when using the BrowserType.ConnectAsync and BrowserType.ConnectOverCdpAsync methods.
A workaround is available when using node by using a npm package to configure the proxy, but I haven’t found a similar solution for the .net version.
I’ve also found similar issues but these don’t seem to apply to my case.

Unable to pass Proxy over ConnectAsync
How to use proxy with ConnectOverCDPAsync

Folding into https://github.com/microsoft/playwright/issues/26985.


Allow devices to be added for all spheres

The "current" sphere is automatically selected using information about someone's position. However, that has quite a few issues:

The Homey has to be in the sphere where your smartphone resides.
If there are connectivity issues (e.g. you didn't install the Crownstone app yet, or you didn't enable Bluetooth), it is not possible to detect which sphere this would be.
If you want to change sphere, you will need to allow the user to change this.

In Alexa or Home Assistant by default all devices are shown. It is up to the user to make use of this. For example, if the user wants to turn off the lights at the office when they arrive home, this should not be made impossible by us. In Home Assistant, if devices are not available to the user they are still present, but they are set to unavailable.
In practice, what this means if you have been invited to multiple spheres, you can control those depending on the rights given by the sphere owner. If we need to filter the Crownstones for a particular Homey device, then we can similarly to Home Assistant set them to "unavailable". If really necessary, we can simplify deletion of all devices in a particular sphere afterwards.

All spheres are now shown and all devices are added by default (the user can deselect them if they don't want them to be added).


How to use "oneOf" extension configuration?

Inside package.json of my VS Code extension:
"contributes": {
  "configuration": {
    "properties": {
      "mysetting": {
        "type": "oneOf", // what attributes work with this type
        // let say the choices are: "aaa", "bbb", "ccc"
        "default": "aaa"
      }
    }
  }
}

Another question, I have another config which its value can be either boolean or array of string. How can I write that in extension config?
Thank you in advance.
I'm really desperate as I could not find detailed explanation of the extension configuration schema in the docs of the official site.

It is better to ask questions on Stackoverflow with the tag "vscode".
I'll try to help, though. If I have a configuration that has a set of valid values, such as "on" and "off", I use the enum attribute to specify what those values can be.
"myconfig.setting": {
    "type": "string",
    "enum": ["on", "off"]
    "default": "on"
}

Regarding multiple types, you can pass an array to type and then specify the type of the items like this:
"myconfig.setting": {
    "type": ["boolean", "array"],
    "default": true,
    "items": {
        "type": "string"
    }
}

Much appreciated!

Just tip for future: also you can read – http://json-schema.org

Oh, I didn't realize it was JSON-schema.  Thank you, mrmlnc


Automator: update istio/api@master dependency in istio/istio@master

Generated by Automator - 2020-11-19T00:10:49+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
966a4c6f4e2dbbd79600da61be64cf53fa415083
link
/test integ-pilot-k8s-tests_istio

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.


deploying is failing "missing public directory"

Hi, can you include a log output for me to see?

aha, thanks for guiding.

aha, thanks for guiding.

You're welcome. Thanks to you, i improved the code as well as the readme. It's now easier to deploy or run locally.
Have a great day!


Bot doesn't start

My bot just stays like this, he used to work but now I don't know why it stopped working :/

even when i type the commands given on help he doesn't do anything, please help :/
and debugging says this....

Do you by any chance have a peer blocker like peerguardian running? I have that and got into the same problem, had to disable it to continue using steambot.

No I don't think I have a peer blocker on my computer, the one thing that comes to my mind is that I installed Win8.1 latelly and previously on win7 the bot was fine, so since I had to reinstall everything maybe something on my pc is missing? :/ the solution compiles fine though, no erros or warnings, just doesnt work, configs are fine and all :/

Found fix for it: Turn off your firewall on PC


add <svelte:options immutable> recipe

closes https://github.com/svelte-society/sveltesociety.dev/issues/66 with an initial attempt - feel free to add or modify!

Nice work Shawn!

hmm. is CI/CD broken?

@sw-yx the site uses a staging branch now, you can see it at https://staging.sveltesociety.dev/recipes/svelte-language-fundamentals/options-immutable

Link to https://svelte.dev/docs#svelte_options doesn't work (Chrome 88, Win 10).


Add remove_account_right function to win32/security

Description
#4321 introduced the ability to add and get account rights; it'd be great if they could be removed as well
I'm working on https://github.com/chef-cookbooks/windows/issues/228 but the resource will be limited to only adding rights until this is implemented.
Chef Version
13.6.4

win32/security now has this function added (Chef >=14.4.10).