[Bug]: "500 Internal Server Error" after upgrade to v0.5.4

Your current environment
The output of `python collect_env.py`

🐛 Describe the bug
After I upgraded to v0.5.4, got "500 Internal Server Error".
My manifest snippet to start vllm:
      containers:
      - name: 8x7b-open
        image: vllm/vllm-openai:v0.5.4
        command: ["python3", "-m", "vllm.entrypoints.openai.api_server"]
        args: ["--model", "hugging-quants/Meta-Llama-3.1-70B-Instruct-AWQ-INT4", "--host", "<IP_ADDRESS>", "--port", "8080", "--tensor-parallel-size", "2", "--seed", "42", "--trust-remote-code"]
        securityContext:
          privileged: true
        ports:
        - containerPort: 8080
        env:
        - name: OMP_NUM_THREADS
          value: "2"
        volumeMounts:
          - mountPath: "/root/.cache"
            name: ceph-volume
        resources:
          limits:
            cpu: '12'
            memory: 200Gi
            nvidia.com/gpu: '2'
          requests:
            cpu: '12'
            memory: 200Gi
            nvidia.com/gpu: '2'

Backtrace log:
INFO:     <IP_ADDRESS>:59936 - "POST /v1/chat/completions HTTP/1.1" 500 Internal Server Error
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/uvicorn/protocols/http/httptools_impl.py", line 399, in run_asgi
    result = await app(  # type: ignore[func-returns-value]
  File "/usr/local/lib/python3.10/dist-packages/uvicorn/middleware/proxy_headers.py", line 70, in __call__
    return await self.app(scope, receive, send)
  File "/usr/local/lib/python3.10/dist-packages/fastapi/applications.py", line 1054, in __call__
    await super().__call__(scope, receive, send)
  File "/usr/local/lib/python3.10/dist-packages/starlette/applications.py", line 123, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/usr/local/lib/python3.10/dist-packages/starlette/middleware/errors.py", line 186, in __call__
    raise exc
  File "/usr/local/lib/python3.10/dist-packages/starlette/middleware/errors.py", line 164, in __call__
    await self.app(scope, receive, _send)
  File "/usr/local/lib/python3.10/dist-packages/starlette/middleware/cors.py", line 85, in __call__
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.10/dist-packages/starlette/middleware/exceptions.py", line 65, in __call__
    await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
  File "/usr/local/lib/python3.10/dist-packages/starlette/_exception_handler.py", line 64, in wrapped_app
    raise exc
  File "/usr/local/lib/python3.10/dist-packages/starlette/_exception_handler.py", line 53, in wrapped_app
    await app(scope, receive, sender)
  File "/usr/local/lib/python3.10/dist-packages/starlette/routing.py", line 756, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/usr/local/lib/python3.10/dist-packages/starlette/routing.py", line 776, in app
    await route.handle(scope, receive, send)
  File "/usr/local/lib/python3.10/dist-packages/starlette/routing.py", line 297, in handle
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.10/dist-packages/starlette/routing.py", line 77, in app
    await wrap_app_handling_exceptions(app, request)(scope, receive, send)
  File "/usr/local/lib/python3.10/dist-packages/starlette/_exception_handler.py", line 64, in wrapped_app
    raise exc
  File "/usr/local/lib/python3.10/dist-packages/starlette/_exception_handler.py", line 53, in wrapped_app
    await app(scope, receive, sender)
  File "/usr/local/lib/python3.10/dist-packages/starlette/routing.py", line 72, in app
    response = await func(request)
  File "/usr/local/lib/python3.10/dist-packages/fastapi/routing.py", line 278, in app
    raw_response = await run_endpoint_function(
  File "/usr/local/lib/python3.10/dist-packages/fastapi/routing.py", line 191, in run_endpoint_function
    return await dependant.call(**values)
  File "/usr/local/lib/python3.10/dist-packages/vllm/entrypoints/openai/api_server.py", line 189, in create_chat_completion
    generator = await openai_serving_chat.create_chat_completion(
  File "/usr/local/lib/python3.10/dist-packages/vllm/entrypoints/openai/serving_chat.py", line 185, in create_chat_completion
    return await self.chat_completion_full_generator(
  File "/usr/local/lib/python3.10/dist-packages/vllm/entrypoints/openai/serving_chat.py", line 436, in chat_completion_full_generator
    async for res in result_generator:
  File "/usr/local/lib/python3.10/dist-packages/vllm/entrypoints/openai/rpc/client.py", line 196, in generate
    with self.socket() as socket:
  File "/usr/lib/python3.10/contextlib.py", line 135, in __enter__
    return next(self.gen)
  File "/usr/local/lib/python3.10/dist-packages/vllm/entrypoints/openai/rpc/client.py", line 59, in socket
    socket = self.context.socket(zmq.constants.DEALER)
  File "/usr/local/lib/python3.10/dist-packages/zmq/sugar/context.py", line 354, in socket
    socket_class(  # set PYTHONTRACEMALLOC=2 to get the calling frame
  File "/usr/local/lib/python3.10/dist-packages/zmq/_future.py", line 218, in __init__
    super().__init__(context, socket_type, **kwargs)  # type: ignore
  File "/usr/local/lib/python3.10/dist-packages/zmq/sugar/socket.py", line 156, in __init__
    super().__init__(
  File "_zmq.py", line 690, in zmq.backend.cython._zmq.Socket.__init__
zmq.error.ZMQError: Too many open files

Also ulimit and lsof info:
root@8x7b-open-deployment-9fb777c9d-mwq8b:/vllm-workspace# lsof | grep pt_main_t | wc -l
26295
root@8x7b-open-deployment-9fb777c9d-mwq8b:/vllm-workspace# ulimit -n
1048576
root@8x7b-open-deployment-9fb777c9d-mwq8b:/vllm-workspace#

cc @robertgshaw2-neuralmagic

@tonyaw  if you want a quick solution, you can try to add --disable-frontend-multiprocessing

What's the side effect by adding this parameter "--disable-frontend-multiprocessing"?
It isn't caused by OMP_NUM_THREADS=2, right?
I have two A100, so OMP_NUM_THREADS shall be 2 right?
Thanks in advance!

--disable-frontend-multiprocessing will be slower
usually people don't need to set OMP_NUM_THREADS for vLLM

Thanks, I will do an analysis of how many unix sockets are opened up and see if there is anything we can do to reduce the amount

--disable-frontend-multiprocessing will be slower
usually people don't need to set OMP_NUM_THREADS for vLLM

@youkaichao I have set this param --disable-frontend-multiprocessing, but still get the error as follows:
File "/data/tangjiakai/anaconda3/envs/agentscope/lib/python3.11/site-packages/openai/_base_client.py", line 1074, in _retry_request
    return self._request(
           ^^^^^^^^^^^^^^
  File "/data/tangjiakai/anaconda3/envs/agentscope/lib/python3.11/site-packages/openai/_base_client.py", line 1026, in _request
    return self._retry_request(
           ^^^^^^^^^^^^^^^^^^^^
  File "/data/tangjiakai/anaconda3/envs/agentscope/lib/python3.11/site-packages/openai/_base_client.py", line 1074, in _retry_request
    return self._request(
           ^^^^^^^^^^^^^^
  File "/data/tangjiakai/anaconda3/envs/agentscope/lib/python3.11/site-packages/openai/_base_client.py", line 1026, in _request
    return self._retry_request(
           ^^^^^^^^^^^^^^^^^^^^
  File "/data/tangjiakai/anaconda3/envs/agentscope/lib/python3.11/site-packages/openai/_base_client.py", line 1074, in _retry_request
    return self._request(
           ^^^^^^^^^^^^^^
  File "/data/tangjiakai/anaconda3/envs/agentscope/lib/python3.11/site-packages/openai/_base_client.py", line 1026, in _request
    return self._retry_request(
           ^^^^^^^^^^^^^^^^^^^^
  File "/data/tangjiakai/anaconda3/envs/agentscope/lib/python3.11/site-packages/openai/_base_client.py", line 1074, in _retry_request
    return self._request(
           ^^^^^^^^^^^^^^
  File "/data/tangjiakai/anaconda3/envs/agentscope/lib/python3.11/site-packages/openai/_base_client.py", line 1041, in _request
    raise self._make_status_error_from_response(err.response) from None
openai.InternalServerError: Error code: 500 - {'detail': ''}

my vllm version is latest 0.5.5, and the cmd is
python -m vllm.entrypoints.openai.api_server \
        --model /data/pretrain_dir/Meta-Llama-3-8B-Instruct \
        --trust-remote-code \
        --port $port \
        --dtype auto \
        --pipeline-parallel-size 1 \
        --enforce-eager \
        --enable-prefix-caching \
        --enable-lora \
        --disable-frontend-multiprocessing

The interesting thing is that even when I enter only one prompt at a time (to ensure the LLM isn't overloaded) during a certain period for testing the large model, it can still sometimes generate successfully and sometimes fail. The error when it fails is still "Error code: 500 - {'detail': ''}".

@TangJiakai  this looks like a client side error. do you have the server side error trace?

@TangJiakai this looks like a client side error. do you have the server side error trace?

Yes, you are right! It's happened on client side.


Monitor forever Process

Add automated monitoring to ensure http://subscriptions.dosomething.org is functional. The application lives at 10-100-25-44/usr/bin/nodejs mbc-user-subscriptions-server.js which runs as a daemon:
$ PORT=4711 forever start mbc-user-subscriptions-server.js

https://app.ghostinspector.com/suites/565f1b51811dd7846273df6f


e2e flake: failed to create 3 members etcd cluster: still failing after X retries

From the logs, it looked like flaky:
time="2017-01-03T23:02:27Z" level=info msg="added member (test-etcd-gzogq-0002)" cluster-name=test-etcd-gzogq pkg=cluster
time="2017-01-03T23:02:32Z" level=info msg="skip reconciliation: running ([test-etcd-gzogq-0000 test-etcd-gzogq-0001]), pending ([test-etcd-gzogq-0002])"
time="2017-01-03T23:02:35Z" level=info msg="deleting cluster" cluster-name=test-etcd-gzogq pkg=cluster

Happened again:
This time it's a little different:

it successfully created the first cluster, deleted the cluster, and restored the seed.
it failed to create the third member of the second cluster (restored)

restore_test.go:126: failed to create 3 members etcd cluster: still failing after 18 retries

I looked at the logs. The whole thing seems to take very long.
This is where the first cluster was deleted
time="2017-01-06T17:59:27Z" level=info msg="deleting cluster" cluster-name=test-etcd-selbd pkg=cluster

This is where the second cluster was failed and deleted
time="2017-01-06T18:02:28Z" level=info msg="deleting cluster" cluster-name=test-etcd-selbd pkg=cluster

It roughly matches 3 mins = 3*60s = 18 (retry) * 10s.
The cluster was starting to restore at
time="2017-01-06T18:00:57Z" level=info msg="restoring cluster from existing backup (test-etcd-selbd)" cluster-name=test-etcd-selbd pkg=cluster

That's already 90s passed! Then nothing seems to be wrong but no enough time left!

Conclusion:

We need to add timestamp to e2e test log
We need to measure how long each operation takes, have better expectation, and understanding distribution

Cause:

The reason why it took so long between deleting previous cluster and receiving a new cluster to restore is that our test is concurrent but operator is blocking. In our test, we have two restore cases to do, each creation of seed member will take 90s. This will likely cause another to fail.

I actually think this should be the issue of #588. Moving there.

This is similar to #588
fixed via #639
Never seen this after we fix the bug.


Add missing navbar links to std.csv.

This appears to have been missing since the previous release, so update both navbars.

How many more pull requests with module list inconsistencies are we going to get?
Did you notice that std.csv was missing, or did you compare the displayed and actual module list?

Somebody mentioned it on the forum.
I do know that there's at least one broken link, namely
std.windows.charset. AFAIK that one has never worked, since posix.mak
never built docs for it, and even if it did, it wouldn't help 'cos it's
all version(Windows) anyway. I don't know how to solve this in a way
that isn't horribly ugly and unmaintainable.


Any chance you could change the name of this to "nanocurrency"?

pynanocurrency is just confusing, because you see it installed as pynanocurrency, but you must import nanocurrency to use it
or nanolib, something shorter to make using it faster

I originally named it pynanocurrency instead of nanocurrency because:

It makes it clear it's a Python library. Popular packages on PyPi have the py prefix, such as PyYAML which is imported using import yaml in actual Python code.
To prevent confusion with the GitHub organization name used by the NANO team.

The confusion between the package name and the module name is understandable and I think the current name is a bit on the long side.
nanolib would actually fit the bill between being short and snazzy, following a convention (eg. urllib, contextlib, matplotlib, ...) and having a name that doesn't conflict with any existing packages. And the package is still on 0.x, so changing the name is still OK.

Please nanolib then. It's not taken on pypi: https://pypi.org/search/?q=nanolib

I've renamed the project to nanolib. The same name is used for both the package name on PyPI and the actual module developers import in Python code.

This is glorious. What's your ID on Discord btw, in the Nano group?

This is glorious. What's your ID on Discord btw, in the Nano group?

It's Matoking#1943. I lurk there for the most part, though.


[BugFix] CTE exhange column prune error

What type of PR is this：

[ ] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

[FE PR Coverage check]
:heart_eyes: pass : 5 / 5 (100.00%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/plan/PlanFragmentBuilder.java
3
3
100.00%

:large_blue_circle:
com/starrocks/planner/ExchangeNode.java
2
2
100.00%


fix(docs): Update description for flushIntervalMillis

Amplitude Developer Docs PR
Description
Type in description. Says millionseconds when it should be milliseconds.
Deadline
The instructions are confusing and change is low risk. Should update now.
Change type

[x] Doc bug fix. Fixes #810 . Amplitude contributors include Jira issue number.
[ ] Doc update.
[ ] New documentation.
[ ] Non-documentation related fix or update.

PR checklist:

[x] My documentation follows the style guidelines of this project.
[ ] I previewed my documentation on a local server using mkdocs serve.
[ ] Running mkdocs serve didn't generate any failures.
[x] I have performed a self-review of my own documentation.

@amplitude-dev-docs

Thanks @tmchow!


Cassandra-19010 Remove sstable format 'nc' and make 5.0 'nb' and 'oa'

Thanks for sending a pull request! Here are some tips if you're new here:

Ensure you have added or run the appropriate tests for your PR.
Be sure to keep the PR description updated to reflect all changes.
Write your PR title to summarize what this PR proposes.
If possible, provide a concise example to reproduce the issue for a faster review.
Read our contributor guidelines
If you're making a documentation change, see our guide to documentation contribution

Commit messages should follow the following format:
<One sentence description, usually Jira title or CHANGES.txt summary>

<Optional lengthier description (context on patch)>

patch by <Authors>; reviewed by <Reviewers> for CASSANDRA-#####

Co-authored-by: Name1 <email1>
Co-authored-by: Name2 <email2>

The Cassandra Jira

Ci j11
CI j17

Note to self: Remove test/data/legacy-sstables/nc

+1, the remaining issues are to be discussed in https://issues.apache.org/jira/browse/CASSANDRA-19012

Rebased and squashed j11 and j17. Only an unrelated Circle env problem


content shell failing on Travis with  1.20.0-dev.7.0

stdout: content_shell: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.18' not found (required by content_shell)
https://travis-ci.org/dart-lang/test/jobs/162079680#L687
Description: Ubuntu 12.04.5 LTS
Release: 12.04
Codename: precise

There is an existing issue filed on this.  You have to use a trusty Travis image, not a precise one.

I thought we did the dance with this last milestone and went back to the older GLIBC version.
Did we go back to the new one?

Yes, we did go back, so it may be a sign of something broken that content shell is now needing 2.18.  But other travis users are compiling the SDK themselves, so they need to go to trusty to get at C++11 compiler.
So if it was only travis, I would say to go to trusty.  But we didn't intend released builds to have the higher libc yet - I'll look into it.  But you should use trusty on travis.

Sadly, if we go to trusty on travis our builds will get A LOT slower.
It feel really weird that this just changed – should investigate, me thinks.

@whesse updates here? This will bork us on Travis for 1.20

Yes. I'll fix this. Fixed other things today.
On Sep 26, 2016 19:12, "Kevin Moore"<EMAIL_ADDRESS>wrote:

@whesse https://github.com/whesse updates here? This will bork us on
Travis for 1.20
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/sdk/issues/27418#issuecomment-249633935,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AErap5lm--5TwuXON8G16ly4vP97Up9pks5qt_0FgaJpZM4KEmM4
.

The 32-bit builds of dartium, content_shell, and chromedriver are all from Precise 12.04, so they should work fine.  The 64-bit build is being built on a Trusty machine, so that is where the new glibc requirement is coming from.  Can you use 32-bit content_shell for your testing?
You can even use 32-bit dartium with the 64-bit SDK, with no problem.
I would prefer not to downgrade the builders to Precise 12.04 if possible, and since our plan is to drop support for precise after the long-term support period ends next spring, I think the current setup is OK.  The SDKs are built on trusty, using a sysroot, but that would be harder to make work for a dartium build.

Per release meeting discussion: It would be preferable to stay with Precise for Dart 1.x and then make the upgrade once we get to Dart 2.

Verified that the dartium 64 builder is again producing builds with only a 2.14 glibc requirement.  Will wait until we publish a dev build that works on travis before closing.

Verified fixed in 1.20-dev.10 – on travis!

https://blog.travis-ci.com/2016-11-08-trusty-container-public-beta/

We are super happy to announce the open public beta of container-based Ubuntu 14.04 "Trusty" job execution, which may be used by ensuring the presence of the following fields in one's .travis.yml:

sudo: false
dist: trusty

See also https://github.com/travis-ci/travis-ci/issues/5695#issuecomment-259221773

Just tried this w/ the AngularDart repo
https://travis-ci.org/dart-lang/angular2/builds/174294337
It seems we don't get backward compat – so we need to decide if we're going to jump all the way in.


Adding Difficulties Updated

Describe your problem here.
Hi I'm trying to see how to add custom difficulties to psych engine and the source seems to be different can you help me add it?
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
Yes, I edited CoolUtil.hx and made changes.

This might help you.
https://github.com/ShadowMario/FNF-PsychEngine/wiki/Adding-a-New-Difficulty

I did not help.

i sorry and idk then

did you do it correctly?

if u did all the steps from the Adding a New Difficulty correctly, check if u got mistakes with commas at CoolUtil.hx or anything, it is really important

That tutorial is outdated now, all you should need to do is go to coolutil, and add your difficulty.

Should look something like that. Remember to put the comma after hard


Update report service search function

There was an issue with the old search function where it sometimes didn't return the full list of dtid's that have nfr data.

Your Pull Request code is being promoted!  Please follow the link below.
Main Merge Workflow


Update Adobe CMaps URL and license

They are now using Apache 2.0 as well.
I also checked the 2015 version of all the resources. They are unchanged to the version currently checked in, besides the license change.

Can we update this without also updating about:license#adobecmap in Firefox (https://dxr.mozilla.org/mozilla-central/source/toolkit/content/license.html)?
If the CMaps are now licensed under Apache 2.0, do we even need an about:license entry any more?

I don't think we need it anymore since we already have an Apache 2.0 entry.

Forgot to add: should I make a patch to mozilla-central then? Or will someone else do it?

Before moving forwards with this patch, and any subsequent ones, I think that we should wait for the developers to sign off on the changes.

Looks good. I agree we should patch mc on the next uplift so I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1179358


Fix an issue in: "Modify Array Data With Indexes"

Challenge http://www.freecodecamp.com/challenges/waypoint-modify-array-data-with-indexes has an issue when submitting the solution.
To re-produce the issue, add this line to the editor, right after // Only change code below this line.:
myArray[0] = 3;

Running the code will pass the first test, but the next test will fail.
Adding the same line twice will make the both tests pass:
myArray[0] = 3;
myArray[0] = 3;

The proposed solution is by changing the second test to look for only one [0] index as the challenge only asks to change the first item of the array.
Thanks!

We've already fixed this but thanks for you proactive fix!


UI Add /manage_users admin page with a list of users

This adds /manage_users page accessible to admins, which allows to search within the user table without having to manually do DB queries.

Thanks @rth , the code LGTM. This is a very useful feature on xianti, I think it will also be for ramp.studio. @agramfort ?

LGTM provided that CI issue is resolved. Thanks @rth.

Thanks @rth


Graph view showing notes connected to filtered out notes

Please select the area your bug applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

[ ] Workspace.  VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
[ ] Lookup.  Dendron's Lookup Command
[x] Views.  Dendron Preview, Tree View, Side Panels in the UI
[ ] Schema.  Dendron Schemas
[ ] Pod.  Data import from / export to Dendron
[ ] Publish.  External Site Publish
[ ] Markdown.  Markdown features, such as syntax support and features

Describe the bug
I have a note that links to a User Note, which links to several other notes. When I activate Backlinks, I see all of those connections. But then I choose to filter out "user" notes. The user note than vanishes, but the connections to the user note still applies.
I would like for when it is connected directly to the user note, or the note i am filtering out, it should not be shown. Especially in the Local Graph View.

The image shows a cluster of notes that link to a user note, which is linked to the note in the bottom left corner.
To Reproduce
Steps to reproduce the behavior:

Create user note
create anote note that links to the user note (@theName)
create yet another note that links to the user note, but not directly to the previous note
look at the locale graph view and filter out user
see something similar like the screenshot above

Expected behavior
To not show notes that are connected to my filtered out notes.
Screenshots
See image above.
Desktop (please complete the following information)

OS: macOS v 12.6.1
Browser (if with published websites; include version): no
Versions (all that apply to bug):

Dendron Extension: 0.118.0
VS Code version: 1.73.1 (Universal)
Dendron CLI: i don't know where to check

Additional context
Add any other context about the problem here.
Dendron Log file
Please attach the output of > Dendron:Dev: Open Logs here

Thanks for reporting the issue @Braweria.
Followup question: What is the depth set for your graph view?
Let me know if I reproed your issue correctly in this video or if is there something I'm missing.
https://www.loom.com/share/86077ecc827442648c2b995cda9bb590

Hi @Harshita-mindfire .
Your test case is exactly what I am talking about, I have also set it to 2.
I have just tried setting it back and forth between 1, 2 and 3 and it is the same issue. The graph view also goes quite crazy because of all those nodes there, after a second or so it calms down and stays put.

got it. So presently, the graph only hides the links to the entries added in blocklist and does not re-render the entire graph.
This did make sense back when the depth was not configurable and was always set to 1. I understand your issue and will update here when we have a fix for this edge case.


Named slots lose classes

This might be intentional, but is never mentioned in the docs.
The use case is in the repro: https://jsfiddle.net/simplesmiler/ersbymbu/

Component defines layout (centering with margin: 0 auto)
Content defines the width

This particular use case can be solved using .modal-component > * instead of .modal-slot.
I think it would be better if named slots followed the rules of normal instances vs fragment instances. I.e. if content for the named slot is a normal instance, then slot attributes (including styles, classes, directives, etc) are merged onto the instance root.
Open for discussion.

Related to https://github.com/vuejs/vue/issues/2128

... the only directives respected on <slot>s are terminal directives like v-if. Normal ones ... are not copied onto the inserted elements. This should be mitigated once we have programatic access to the slots. For now, you can wrap the <slot> in an additional element ...

Except for the cases where this will not work, like with margin: auto and fixed width.

Related to https://github.com/vuejs/vue/issues/1281
.modal-component > [slot="content"] is pretty much .modal-slot except for the specifity.

It seems [slot="content"] serves the purpose as a hook for styling the inserted slot content - are there any particular use case where merging directives would be useful? In general I want to limit what a component can do to inserted content - it's compiled and inserted by the parent, the child just displays it, but doesn't modify it.

A potential use case I've stumbled upon recently is detecting changes in dimensions of the slotted element for layout purposes (and in general, detecting when an element enters or leaves the slot). I worked around this by exposing a method and detecting changes on the other side.
I guess programmatic slot API would solve that too. I think the issue can be closed for now and reviewed when the API lands.

I want to add classes to slots for ease of styling. I have existing CSS components that I use on other components that I also want to use on this component that happens to have slots. My CSS components use variant classes to modify the look of an element.
class='button -blue'
class='button -red -shiny'
Because of how I structure my CSS it's difficult to work around a div you can't style using classes. I have to copy all of my styles to the attribute selector in this case because I can't use any variant classes.
I really hope you decide to add classes to named slots. This would help me a ton. And thanks for all the work on Vue! It's great!

I ended up making a bunch of components to drop into slots. So I can do something like
<grid-item>
    header content

    <data-panel slot="body">

stuff

    </data-panel>
</grid-item>

with a mixin to provide access to common components. I can set the styling in the <data-panel> component and drop it in where I need it instead of having to remember the exact styling of
 and all that stuff.
For my use case that's a decent compromise, my slotted component doesn't need to know about what's being slotted and I don't have to keep dropping the same classes into my components all the time.

This hack worked for me :
I have a bootstrap panel component that works with slots - for panel-heading, panel-title, panel-body and panel-footer.  This is what it looks like (its in Jade - you can convert it @ [http://html2jade.org] (http://html2jade.org)

I believe you can do:
 div.panel-body(:v-bind="panelTitleConfig")
    slot(name="panel-body")

That way, you can send any property in panelTitleConfig such as data-title="bob" and it will show up in the div.panel-body.
(You can see this in the vue docs with the $attrs value)


Pin openai version

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

Comparison is base (b47aecb) 79.93% compared to head (f8cbb3e) 79.93%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #75   +/-   ##
=======================================
  Coverage   79.93%   79.93%
=======================================
  Files          17       17
  Lines         937      937
=======================================
  Hits          749      749
  Misses        188      188

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


Add forecast module

@Moonraker and I created a forecast module for pvlib. The initial discussion of this was in issue #86.
Here's a link to the documentation and our PVSC abstract:
http://wholmgren-pvlib-python-new.readthedocs.org/en/fx-master/forecasts.html
https://forecasting.uaren.org/media/pvlib_fx_pvsc_43.pdf
Basically, we use Unidata's Siphon library to pull data from Unidata's THREDDS server, standardize the variable names, and calculate irradiance components from cloud cover forecasts.
I think this PR fairly complete already, but there are plenty of opportunities for refinements and refactoring before or after merging.
The module was developed based on pvlib 0.2.1, so we'd need to make some minor changes to accommodate the work done in #93.
Let me know if you think that this idea and implementation would be a valuable addition to pvlib. I would consider packaging it separately, too, either under the pvlib organization or my own account. I'd probably squash some/all of the git history before merging.
To do:

[ ] Add notes about geographic extent of models
[ ] Add note about who is making the models (NCEP and NWS, both part of NOAA)
[ ] Figure out how to allow model tests to fail due to random down time.

Nice stuff.
What is the geographical coverage of the Unidata forecasts?
If it is limited for North America, then maybe a separate package for each region would be a possibility. Maybe the same approach works with ECMWF data. There is a python api for their data as well.
The the last section of the documentation also shows that adding the output indicators performance ratio and specific yield would be beneficial. This would make the ac power values a bit more independent of the module rating.

Regarding the abstract:
The first paragraph  is a bit unclear. I suggest defining which forecast models is referred to. I assume the ones of national or regional weather services. Universities or commercial providers may targeting specifically solar power have fairly good models. Then, it depends also on the type of forecast. Empirical, physical, etc. What type do we have here?
Is the aerosol modelling methodology mentioned? Does is play a role at the location?
I would add an outlook towards validation to the conclusion. The rest is quite well readable. Ideally, the plots could include some past days and then use lighter, dashed colours for the forecast.

Thanks.

What is the geographical coverage of the Unidata forecasts? If it is limited for North America, then maybe a separate package for each region would be a possibility.

GFS is global, the rest range from US (NDFD) to most of North America (NAM). I'll make a couple of notes about this in the documentation. I'll also clarify who is actually making the forecasts (not Unidata).

Maybe the same approach works with ECMWF data. There is a python api for their data as well.

I know of their API but I don't think that it provides access to their forecast data, only related products like reanalysis.

Ok.
Maybe also state what frequency is used and what cell dimension in the weather model used as input. This is often a difference criteria.

This looks great. I do agree with DaCoEx about not understanding the
current and future state of validation of these forecasts. Is that the next
stage of your grant?
Random note on abstract, isn't the second sentence reversed from the intent
of the first sentence? "On standard meteorology metrics, the ECMWF is
superior to the GFS by about a day. In other words, the accuracy of the GFS
at 6 days out is comparable to the ECMWF at 5 days out."
Tangentially related, I just was reminded about the MERRA historical
dataset, and even tracked down a PVSC paper comparing its accuracy to Solar
Prospector, only to discover that the work had been done by our own
@calama-consulting. It looks like the MERRA radiation flux dataset
(tavg1_2d_rad_Nx) is not yet available through the MERRA API, but that
would be a good addition to data sources when it is.
https://cds.nccs.nasa.gov/wp-content/test/MASOverview.html#Order
I am ambivalent as to whether the forecast module should be in a separate
package. I definitely think it would be good to keep it associated with
pvlib, but if it has some esoteric dependencies, maybe a second package is
a good idea.
On Thu, Feb 18, 2016 at 11:38 PM, DaCoEx<EMAIL_ADDRESS>wrote:

Ok.
Maybe also state what frequency is used and what cell dimension in the
weather model used as input. This is often a difference criteria.
—
Reply to this email directly or view it on GitHub
https://github.com/pvlib/pvlib-python/pull/124#issuecomment-186103946.

@dacoex good/bad is subjective, but I'd say that the state of solar power forecasting is bad. Of course, people trying to sell forecasts say that their model is the best and people trying to get grant funding say that their model is great but would be so much better if you'd just give them a little bit of money, please, please, please. The problem is that weather is so complicated and varies so much across the world that it becomes very difficult to make objective comparisons without quickly getting lost in the details. This is perhaps even more true for clouds and thus irradiance.
My proposal is that the new code can make the objective comparisons a little more rigorous and a little bit easier. First, it makes it trivial to access the data related to PV generation from many U.S. weather models. Then you can use the preexisting pvlib functions on that data, or you can do whatever you want with it. If you choose the latter, hopefully you'll now be in an open source mindset and publish (in some form) your analysis code in addition to the results. Either way, it establishes a traceable, open benchmark tool for forecast comparisons.
So, like the rest of pvlib, what I'm proposing is a tool. I'm not making any claims as to the accuracy of the weather models, or the Liu Jordan model, or the SAPM, or the combinations of them. The tool certainly does not solve all problems related to objective, reproducible research in the solar power forecasting field, but I think/hope that people will find it useful.
Quick notes regarding a few other points above...

All weather models are a mix of approximated physics, plus a lot of parameterizations, so, they're both empirical and physical. pvlib adds another layer of empiricism: the Liu Jordan cloud-cover-to-irradiance model. This is, to me, the least interesting part of the proposal. We just picked an old, standard reference model to get started, but there's an infinite number of ways to improve this.
The interesting MERRA discussion perhaps suggests that much of the "forecasting" code actually belongs in a new io module (see #29), with the forecast data being just another data source along with TMY and other standard datasets. Much of the motivation for the forecasts is similar to the motivation for standard datasets such as TMY, which further suggests that they could be grouped together. I'll have to think about this more.
All of this is helpful feedback for how to develop the PVSC abstract into a talk or poster and a paper. I'll be the first to admit that we need to add a lot more references to the literature in the final paper. And yes, @jforbess, that is an embarrassing mix up, thank you for pointing it out.

On to the dependencies and packaging... The main new optional dependency, Siphon, is a bit esoteric at this point, but Unidata has made developing Python tools a priority for the foreseeable future, so I'm not too worried about it. Installing Siphon itself is not a big deal, but it depends on NetCDF, which requires slightly more experience/luck to compile (though not nearly as bad as scipy). The anaconda packages for NetCDF have been reliable, though. The forecast module is not imported in the __init__.py file, so if you don't install the optional dependencies then you can continue to use pvlib as if it never existed. These are not arguments for including the code in pvlib, only that it's not making it any harder to install pvlib.
Thanks again for your feedback.

Yes, I brought up the MERRA data partly because this forecasting paired
with it does suggest an io module might be useful, despite my lack of
enthusiasm previously.
But let me just say, wow, a solar forecasting tool in open source! Awesome!
On Fri, Feb 19, 2016 at 12:31 PM, Will Holmgren<EMAIL_ADDRESS>wrote:

@dacoex https://github.com/dacoex good/bad is subjective, but I'd say
that the state of solar power forecasting is bad. Of course, people trying
to sell forecasts say that their model is the best and people trying to get
grant funding say that their model is great but would be so much better if
you'd just give them a little bit of money, please, please, please. The
problem is that weather is so complicated and varies so much across the
world that it becomes very difficult to make objective comparisons without
quickly getting lost in the details. This is perhaps even more true for
clouds and thus irradiance.
My proposal is that the new code can make the objective comparisons a
little more rigorous and a little bit easier. First, it makes it trivial to
access the data related to PV generation from many U.S. weather models.
Then you can use the preexisting pvlib functions on that data, or you can
do whatever you want with it. If you choose the latter, hopefully you'll
now be in an open source mindset and publish (in some form) your analysis
code in addition to the results. Either way, it establishes a traceable,
open benchmark tool for forecast comparisons.
So, like the rest of pvlib, what I'm proposing is a tool. I'm not making
any claims as to the accuracy of the weather models, or the Liu Jordan
model, or the SAPM, or the combinations of them. The tool certainly does
not solve all problems related to objective, reproducible research in the
solar power forecasting field, but I think/hope that people will find it
useful.
Quick notes regarding a few other points above...

All weather models are a mix of approximated physics, plus a lot of
parameterizations, so, they're both empirical and physical. pvlib adds
another layer of empiricism: the Liu Jordan cloud-cover-to-irradiance
model. This is, to me, the least interesting part of the proposal. We just
picked an old, standard reference model to get started, but there's an
infinite number of ways to improve this.
The interesting MERRA discussion perhaps suggests that much of the
"forecasting" code actually belongs in a new io module (see #29
https://github.com/pvlib/pvlib-python/issues/29), with the forecast
data being just another data source along with TMY and other standard
datasets. Much of the motivation for the forecasts is similar to the
motivation for standard datasets such as TMY, which further suggests that
they could be grouped together. I'll have to think about this more.
All of this is helpful feedback for how to develop the PVSC
abstract into a talk or poster and a paper. I'll be the first to admit that
we need to add a lot more references to the literature in the final paper.
And yes, @jforbess https://github.com/jforbess, that is an
embarrassing mix up, thank you for pointing it out.

On to the dependencies and packaging... The main new optional dependency,
Siphon, is a bit esoteric at this point, but Unidata has made developing
Python tools a priority for the foreseeable future, so I'm not too worried
about it. Installing Siphon itself is not a big deal, but it depends on
NetCDF, which requires slightly more experience/luck to compile (though not
nearly as bad as scipy). The anaconda packages for NetCDF have been
reliable, though. The forecast module is not imported in the init.py
file, so if you don't install the optional dependencies then you can
continue to use pvlib as if it never existed. These are not arguments for
including the code in pvlib, only that it's not making it any harder to
install pvlib.
Thanks again for your feedback.
—
Reply to this email directly or view it on GitHub
https://github.com/pvlib/pvlib-python/pull/124#issuecomment-186394059.

Will, I’d like to applaud your efforts here.  We started PVLib to improve PV modeling by promoting transparency and rigor.  We don’t want to make any particular model into a standard, rather, we want the modeling process to become standardized, and make available a wide variety of models.
Your vision of the forecasting module is precisely in this spirit.  The danger is that once a free solar forecasting tool is available, people will use it and stop questioning the tool itself.  For this reason, I’d recommend building options which present the user choices.  The specific choice (e.g., weather data source, irradiation decomposition and/or transposition models, etc.) may not be as important as having the choice presented.
Cliff
From: Will Holmgren<EMAIL_ADDRESS>Sent: Friday, February 19, 2016 1:31 PM
To: pvlib/pvlib-python
Subject: [EXTERNAL] Re: [pvlib-python] Add forecast module (#124)
@dacoexhttps://github.com/dacoex good/bad is subjective, but I'd say that the state of solar power forecasting is bad. Of course, people trying to sell forecasts say that their model is the best and people trying to get grant funding say that their model is great but would be so much better if you'd just give them a little bit of money, please, please, please. The problem is that weather is so complicated and varies so much across the world that it becomes very difficult to make objective comparisons without quickly getting lost in the details. This is perhaps even more true for clouds and thus irradiance.
My proposal is that the new code can make the objective comparisons a little more rigorous and a little bit easier. First, it makes it trivial to access the data related to PV generation from many U.S. weather models. Then you can use the preexisting pvlib functions on that data, or you can do whatever you want with it. If you choose the latter, hopefully you'll now be in an open source mindset and publish (in some form) your analysis code in addition to the results. Either way, it establishes a traceable, open benchmark tool for forecast comparisons.
So, like the rest of pvlib, what I'm proposing is a tool. I'm not making any claims as to the accuracy of the weather models, or the Liu Jordan model, or the SAPM, or the combinations of them. The tool certainly does not solve all problems related to objective, reproducible research in the solar power forecasting field, but I think/hope that people will find it useful.
Quick notes regarding a few other points above...

All weather models are a mix of approximated physics, plus a lot of parameterizations, so, they're both empirical and physical. pvlib adds another layer of empiricism: the Liu Jordan cloud-cover-to-irradiance model. This is, to me, the least interesting part of the proposal. We just picked an old, standard reference model to get started, but there's an infinite number of ways to improve this.
The interesting MERRA discussion perhaps suggests that much of the "forecasting" code actually belongs in a new io module (see #29https://github.com/pvlib/pvlib-python/issues/29), with the forecast data being just another data source along with TMY and other standard datasets. Much of the motivation for the forecasts is similar to the motivation for standard datasets such as TMY, which further suggests that they could be grouped together. I'll have to think about this more.
All of this is helpful feedback for how to develop the PVSC abstract into a talk or poster and a paper. I'll be the first to admit that we need to add a lot more references to the literature in the final paper. And yes, @jforbesshttps://github.com/jforbess, that is an embarrassing mix up, thank you for pointing it out.

On to the dependencies and packaging... The main new optional dependency, Siphon, is a bit esoteric at this point, but Unidata has made developing Python tools a priority for the foreseeable future, so I'm not too worried about it. Installing Siphon itself is not a big deal, but it depends on NetCDF, which requires slightly more experience/luck to compile (though not nearly as bad as scipy). The anaconda packages for NetCDF have been reliable, though. The forecast module is not imported in the init.py file, so if you don't install the optional dependencies then you can continue to use pvlib as if it never existed. These are not arguments for including the code in pvlib, only that it's not making it any harder to install pvlib.
Thanks again for your feedback.
—
Reply to this email directly or view it on GitHubhttps://github.com/pvlib/pvlib-python/pull/124#issuecomment-186394059.

Thanks, Jessica and Cliff. Good points regarding the need for people to keep questioning the tools. I will make a few options available for the forecast irradiance data here and keep this in mind elsewhere.

closed in favor of #180.


Check if you can speed up the shots

I'm not really a coder but I've been trying to learn how all this works by looking at your code and the decompiled code in dnSpy so, please, forgive me for being a bit clueless. I happened across this snippit and remembered that you were looking for a way to speed the shots up:
	// Token: 0x06005D4C RID: 23884 RVA: 0x001CADA8 File Offset: 0x001C8FA8
	protected void SetupBullets()
	{
		this.currentBullet = 0;
		if (this.shotDelay <= 0f)
		{
			this.shotDelay = 0.5f;
		}
		this.rate = 1f / this.shotDelay;
		this.ClearBullets();
		for (int i = 0; i < this.weapon.ProjectilesPerShot; i++)
		{
			GameObject gameObject = this.Combat.DataManager.PooledInstantiate(this.bulletPrefab.name, BattleTechResourceType.Prefab, null, null, null);
			if (gameObject == null)
			{
				WeaponEffect.logger.LogError("Error instantiating BulletObject " + this.bulletPrefab.name, this);
				return;
			}
			gameObject.transform.parent = null;
			BulletEffect component = gameObject.GetComponent<BulletEffect>();
			if (component == null)
			{
				WeaponEffect.logger.LogError("Error finding BulletEffect on GO " + this.bulletPrefab.name, this);
				return;
			}
			this.bullets.Add(component);
			component.Init(this.weapon, this);
		}
	}

Could shotDelay possibly be what you're looking for?

Yea looks good, might try around with that, but fear this will out sync the sound and animations, but who knows it's worth a try.

Ah damnit this is sadly only for the projectiles :( Not the actual shots ;-/

Oh, well shit... thought I had found something good. :(

Was a good idea but i think the real problem lies in how i "fixed" balistic weapons, i basicly jsut tell the game to fire twice so it behaves like each shot is a new weapon :(

Is that how the game handles missiles and MG's?


[NFT-03M] Incorrect Ownership Change Maintenance

NFT-03M: Incorrect Ownership Change Maintenance

Type
Severity
Location

Logical Fault

NFTPermissions.sol:L157

Description:
The NFTPermissions::_update function will cause an NFT that is burned to retain the permissions it last assigned as the _assignedPermissions mapping could still point to valid AssignedPermissions structures with non-zero lastUpdated entries.
While the present NFTPermissions::hasPermission implementation would properly fail in such a case due to the ERC721::ownerOf invocation, containing permission entries that would otherwise succeed is an invalid trait that can misbehave in a variety of ways - including the re-creation of a particular NFT that has been burned.
Impact:
Given that this exhibit represents a potential compromise of the permission system the NFTPermissions contract is meant to establish, we consider it of "major" severity.
In the code, we have demonstrated how this particular vulnerability can manifest in a supported case by EIP-721 (a burn and consequent mint of the same NFT ID). A case whereby a burned NFT would remain usable for permissions would solely arise if derivative contracts of NFTPermissions would implement some form of pre-mint system and override the NFTPermissions::hasPermission or NFTPermissions::ownerOf function to not fail for un-minted NFTs.
Example:
/// @dev We are overriding this function to update ownership values on transfers
function _update(address _to, uint256 _positionId, address _auth) internal override returns (address _from) {
  _from = super._update(_to, _positionId, _auth);
  if (_to == address(0)) {
    // When token is being burned, we can delete this entry on the mapping
    delete lastOwnershipChange[_positionId];
    _burnCounter++;
  } else if (_from != address(0)) {
    // If the token is being minted, then no there is no need to need to write this
    lastOwnershipChange[_positionId] = block.number;
  }
}

Recommendation:
We advise the code to instead assign the maximum value possible for a block.number in the NFTPermissions system (which would be represented by type(uint64).max) to ensure that any previously-assigned permissions before an NFT is burned do not remain active.
Additionally and to avoid this vulnerability manifesting in re-minted NFTs, we advise the else if block present in the NFTPermissions::_update function to be set to a simple else block ensuring that the lastOwnershipChange is correctly overwritten from the previously-set maximum.

While this issue is technically true, after we fixed #12, it's no longer possible to call _mint directly from a contract that inherits NFTPermission. That means that there is no way to re-mint a token that has been burned, since all minting goes through _mintWithPermissions, and it assigned a new id each time
Since tokens cannot be re-minted, I would argue that this is no longer an issue

After discussing it with the team, we decided to go ahead and set the max value. This would revoke all previous permissions, regardless of how ownerOf is implemented


Installation Complete but doesn't boot on Systems with 32-bit firmware

Some Windows 8 devices use 64-bit CPU but with 32-bit firmware.
These devices can be initially identified from checking if windows is 32-bit
Devices reported:
Acer Iconia W4-820
Trekstor Surftab Wintron 10.1

This issue requires

Checking for if windows is 32-bit
Compile i386-efi version of grub

grub should be compiled with the following cmdline:
grub-mkimage -d . -o bootia32.efi -O i386-efi -p "" boot chain configfile cpio echo efi_gop efi_uga fat linux ntfs ntfscomp part_gpt part_msdos sfs search search_fs_file read reboot help hfsplus normal gfxmenu png


How to send commands to a container after creating and running it

I created a container like so:
Dictionary<string, IList<PortBinding>> portBindings = new Dictionary<string, IList<PortBinding>>();
        PortBinding portBinding = new PortBinding();
        portBinding.HostPort = "3001";
        portBinding.HostIP = null;
        List<PortBinding> pList = new List<PortBinding>();
        pList.Add(portBinding);
        portBindings.Add("3001/tcp", pList);
        var response = await _dockerClient.Containers.CreateContainerAsync(new CreateContainerParameters()
        {
            Image = "images/myemulator:version1",
            HostConfig = new HostConfig()
            {
                PortBindings = portBindings,
                Binds = new[] { @"C:\My\emulator:/data" }
            },
            Name = "MyEmulator",
            Platform = "linux/i386",
            Tty = true
        });

Then I started it:
await _dockerClient.Containers.StartContainerAsync(response.ID, new ContainerStartParameters());
Now, I want to execute two commands:
cd data
and
./myemulator_1200 -E1 -G1 -H1 -FTestScript.txt
How would I go about executing those commands?

You need to create the command via ExecCreateContainerAsync and read the response with InspectContainerExecAsync, here is an example.

Thank you. I now have an error. Here is my code and the error:
List<string> commands = new List<string>();
        commands.Add("cd data");
        commands.Add("./myemulator_1200 -E1 -G1 -H1 -FTestScript.txt");

        var execCreateParameters = new ContainerExecCreateParameters
        {
            Cmd = commands,
            AttachStdout = true,
            AttachStderr = true,
        };

        var execCreateResponse = await _dockerClient.Exec.ExecCreateContainerAsync(response.ID, execCreateParameters, default(CancellationToken));

        using (var stdOutAndErrStream = await _dockerClient.Exec.StartAndAttachContainerExecAsync(execCreateResponse.ID, false, default(CancellationToken)))
        {
            var (stdout, stderr) = await stdOutAndErrStream.ReadOutputToEndAsync(default(CancellationToken));

            var execInspectResponse = await _dockerClient.Exec.InspectContainerExecAsync(execCreateResponse.ID, default(CancellationToken));

            Console.WriteLine($"Standard Out: {stdout}");
            Console.WriteLine($"Standard Out: {stderr}");
            Console.WriteLine($"Standard Out: {execInspectResponse.ExitCode}");
            Console.Read();
        }

I get the following response:
Standard Out: OCI runtime exec failed: exec failed: unable to start container process: exec: "cd data": executable file not found in $PATH: unknown
Standard Out:
Standard Out: 126

You are using the API wrong. It receives a single command, where each list item is an argument. You need to send two commands, they look something like:
command1.Add("cd");
command1.Add("data");

// Either the binary is in the PATH env variable or you need the absolute path.
command2.Add("myemulator_1200");
command2.Add("-E1");
command2.Add("-G1");
command2.Add("-H1");
command2.Add("-FTestScript.txt");

!NOTE!: I do not think changing the directory to the binary will work. You probably need the absolute path, like command2.Add("/data/myemulator_1200");.

What I ended up doing that worked:
List<string> commands = new List<string>();
commands.Add("/data/hid_aero_emulatorx32_1_29_1_0633");
commands.Add("-E1");
commands.Add("-G1");
commands.Add("-H1");
commands.Add("-F/data/TestScript.txt");

No cd data bits at all.
Thank you for your help. Closing this now.


Add option to not fail on vulnerability

Codecov Report
Attention: 62 lines in your changes are missing coverage. Please review.

Comparison is base (86cf40f) 78.37% compared to head (cda0dc9) 78.39%.
Report is 13 commits behind head on main.

Files
Patch %
Lines

pkg/osvscanner/osvscanner.go
36.11%
23 Missing :warning:

cmd/osv-reporter/main.go
0.00%
8 Missing :warning:

cmd/osv-scanner/main.go
41.66%
5 Missing and 2 partials :warning:

internal/sourceanalysis/rust.go
14.28%
6 Missing :warning:

internal/sourceanalysis/go.go
0.00%
5 Missing :warning:

internal/local/check.go
25.00%
3 Missing :warning:

pkg/reporter/gh-annotations_reporter.go
50.00%
2 Missing :warning:

pkg/reporter/json_reporter.go
50.00%
2 Missing :warning:

pkg/reporter/sarif_reporter.go
50.00%
2 Missing :warning:

pkg/reporter/void_reporter.go
33.33%
2 Missing :warning:

... and 2 more

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #12      +/-   ##
==========================================
+ Coverage   78.37%   78.39%   +0.01%
==========================================
  Files          85       85
  Lines        6035     6040       +5
==========================================
+ Hits         4730     4735       +5
- Misses       1098     1100       +2
+ Partials      207      205       -2

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


Add ability to set default roles

Problem:
Currently when a new user, cluster or project is created the roles are defaulted. This can cause higher than expected access for the user who created the resource.
Solution:
Add the ability to set the default roles as follows:
Global role for the auto created user when an auth provider is activated. The UI can also trigger off this and not default to the 'User' role when creating a new user.
Project creation
Cluster creation
Issue: rancher/rancher/issues/12737
Dependency: https://github.com/rancher/types/pull/495

LGTM


More distro kernel fixes

My last PR fixed one bug and introduced another, despite my testing. This one should fix that bug, and also adds some more logging to help trace future issues.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.ceph.com//job/teuthology-pull-requests/1520/
Tests passed for this pull request.


Python: 3.2 Operators: arithmetic & assignment operators #249

Description 📜
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes # <issue_number_here>

Type of change 📝

[x] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x] Doc#umentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] Java#Script
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[x] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

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

Screenshots / Gif (Optional) 📸

Add issue number to your PR template. Next this PR has total of 102 files which are irrelevant to your issue. Kindly check on the workflow and follow in right format to avoid this issue. @anjalikumawat2002


Method to free Map resources

Is your feature request related to a problem? Please describe.
Currently, there is no method to free up resources other than map.setTarget(null) which is not intuitive nor is it mentioned in the documentation. This causes a common bug related to memory leak when you don't destroy the map on component unmount in SPAs.
Describe the solution you'd like
Would be nice to have a method like map.destroy() or a mention in the documentation that passing null to setTarget frees up the resources.

@ahocevar related to this I have quite some use cases where it would be nice to know when a Disposable is disposed. (e.g. cleaning up some related objects etc.)
I think the following additions would make this a lot easier:

a public isDisposed() on Disposable
dispatching a dispose event on disposal (dispose before disposeInternal is called and / or disposed after disposeInternal is called)

If you'd agree with these additions I'd be happy to make a PR for them.

@sebakerckhof I don't think this would make much sense, because OpenLayers internally does not call dispose() on anything but layer renderers, and dispose() is only part of the API for the WebGLTile layer and the Raster source.


Application-factory

[x] Create an application factory pattern for initalizing FastAPI app
[x] Configure celery to work with the database applcation factory pattern
[x] Manage changes to the database with sqlalchemy and Alembic

All tested and going well!


No resource identifier found for attribute 'dotType' in package 'com.cyrilmottier.android.gdcatalog'

I've tried differnet approaches, but still this problem raises.
When building project i get this error:
myproject\res\layout\paged_view.xml:29: error: No resource identifier found for attribute 'dotType' in package 'com.cyrilmottier.android.gdcatalog'
myproject\res\layout\paged_view.xml:29: error: No resource identifier found for attribute 'gravity' in package 'com.cyrilmottier.android.gdcatalog'
myproject\res\layout\paged_view.xml:41: error: No resource identifier found for attribute 'dotType' in package 'com.cyrilmottier.android.gdcatalog'
myproject\res\layout\paged_view.xml:41: error: No resource identifier found for attribute 'gravity' in package 'com.cyrilmottier.android.gdcatalog'
I've added Greendroid as library to my project, and added tag
android:name="greendroid.app.GDApplication" into

Project has same API level.
Tested on
Eclipse Indigo and
Netbeans 6.9.1.

Have you tried clearing your project?
I can't reproduce this behavior.

The most likely cause of this is that the projects have not been imported into the workspace. For some reason Eclipse has problems references library projects if they are not in the workspace along with referencing projects.


Fix bug where Documentation was set active when on the Libraries page

I think this will break the breadcrumbs on the page; we want to see Documentation as the parent page for Libraries. CC @chrisdone

Indeed, this is intentional.


vg call throwing error from tabix

REFFASTA="/home/data/reference/GRCh38_full_plus_hs38d1_analysis_set_minus_alts.fa"
VCFFILE="/home/devsci4/Graph_Genomes_CSHL/examples/vgInput.vcf.gz"
VGOUTFILE="/home/devsci4/Graph_Genomes_CSHL/examples/vgoutput.vg"
vg/bin/vg construct -r $REFFASTA -v $VCFFILE > $VGOUTFILE

Returns:
[tabix++] the index file is older than the vcf file. Please use '-f' to overwrite or reindex.

tabix –p vcd $VCFFILE
?
—Nancy
From: Jeff Oliver <notifications<EMAIL_ADDRESS>Reply-To: NCBI-Hackathons/Graph_Genomes_CSHL <reply<EMAIL_ADDRESS>Date: Wednesday, October 26, 2016 at 5:36 PM
To: NCBI-Hackathons/Graph_Genomes_CSHL <Graph_Genomes_CSHL<EMAIL_ADDRESS>Subject: [NCBI-Hackathons/Graph_Genomes_CSHL] vg call throwing error from tabix (#9)
REFFASTA="/home/data/reference/GRCh38_full_plus_hs38d1_analysis_set_minus_alts.fa"
VCFFILE="/home/devsci4/Graph_Genomes_CSHL/examples/vgInput.vcf.gz"
VGOUTFILE="/home/devsci4/Graph_Genomes_CSHL/examples/vgoutput.vg"
vg/bin/vg construct -r $REFFASTA -v $VCFFILE > $VGOUTFILE
Returns:
[tabix++] the index file is older than the vcf file. Please use '-f' to overwrite or reindex.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/NCBI-Hackathons/Graph_Genomes_CSHL/issues/9, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACQX094F7ZJgugO6rAvDD8HrJ9cqyYXQks5q38fNgaJpZM4KhssL.

Yep! That's right. Fixed on commit eee79b4 .


Fix msrv CI: Check for --all-features

To make sure that enabling parallel feature would not require bumping msrv.

@thomcc Pinging since I'd like this PR to merge first.
I would need this to be merged so that I can bump MSRV (and possibly re-enable macos msrv check) sas otherwise it would cause a merge conflict.
This PR is quite simple so it won't take you long to review it.

so that I can bump MSRV

Not that my opinion matters, I'm just a user, but I would like to speak up against bumping MSRV if it goes above 1.56 [which matches 2021 edition].

@dot-asm I planned to bump it in 1.53 https://github.com/rust-lang/cc-rs/pull/889#issuecomment-1788887737


Typings out of date in 2.11.0 for renderInput property

renderInput works great - just as I wanted it to.  Its just the typings seem out of date and are telling me it isn't available.
working around it in the short term by manually updating typings in package, will watch for update. I can see by github commits this feature is under active development.

closing again - although my just installed version doesn't have typings I can see them in the project.
It would be nice though to have the renderInput function return React.ReactNode, and be a bit more explicit on the properties it will pass


TST: fix test issue for stats.pearsonr

Fixes this:
>       assert_allclose(p, 0.0)
E       AssertionError:
E       Not equal to tolerance rtol=1e-07, atol=0
E
E       Mismatch: 100%
E       Max absolute difference: 1.34157586e-08
E       Max relative difference: inf
E        x: array(1.341576e-08)
E        y: array(0.)

Testing for "close to zero" should always have atol > 0

LGTM too, merged. Thanks Ralf, Eric

Thanks, Ralf.  I should have caught that in the original pull request.
Where did that failure show up?

Just me running the tests locally. Standard 64-bit Linux install, but with conda compilers. Not sure why it's not showing up in other places.


basic setup/install documentation

Hi! I know this is a work in progress, but I'm wondering if you could create a basic installation/run section in the readme?

yea, it'll be there when its ready

You should probably leave this issue open until the documentation is ready...


SSL error

Error in update please fix Jio V2.0.19
Kodi version 20.0

Uninstall and reinstall kodi


Shared by filter broken

In groups resources, the default should be "checked" to filter by "shared by". Also, clicking in the box has opposite from intended. Also, seems to just filter all items, anyway.


docker dependencies should use pinned versions by default

With --docker-metrics, subtle changes in grafana behavior have cause confusion for users.

We should allow for both --docker-metrics-stable or --docker-metrics-latest, with the former being the default behavior for the current --docker-metrics option.
The startup message for --docker-metrics should tell users about the location of the state files, so they can remove them if needed.
add a --docker-metrics-purge option, to completely remove the state associated with the nosqlbench dockers state.

This is superseded by a new approach to be documented in a separate issue.


Enderian Pumpkin Shadow Glitch

When another player wheres a pumpkin the enderian can still see the shadow

Fixed in 0.6.0


Make TypeScript itself ESM-only, made possible by require(ESM)

https://github.com/nodejs/node/pull/51977 (behind --experimental-require-module in Node 22) enables Node to require ESM so long as that ESM does not make use of top-level await. TypeScript would only need top-level await to construct ts.sys at startup, which must be defined when the environment is detected to be Node. Via https://github.com/nodejs/node/issues/52599 and https://github.com/nodejs/node/pull/51977, we can synchronously access Node's built-ins, and therefore can offer up a TLA-free public API, enabling TypeScript to ship as ESM-only without breaking CJS users, once require(ESM) is unflagged.
The bulk of this change is just the extension rewriting, which we may want to consider taking to main just to make a PR like this one clearer.
For casual onlookers, I don't think this PR is going to "happen" any time soon (where "now" is currently May 2024); require(ESM) is new, flagged, and TS will likely need to support versions of Node until they're sufficiently EOL for us to feel comfortable dropping them. But it's incredible that this is possible.
TODO:

[ ] Fix public API dts
[ ] Figure out __esModule

The real question is the context of require(ESM) having __esModule. But I suspect that exporting default fixes this.

[x] Consider looking for require if process.getBuiltinModule is not found
[ ] Export maps? Actually make the package importable? (does this work?)
[ ] Maybe still ship CJS behind a condition to get this out sooner?

Dual package hazard is very scary here. Maybe acceptable with module condition/top-level prop?

[ ] Stop bundling? Share code between tsc.js/typescript.js?
[ ] Probably a billion other things
[ ] Is this even a good idea before we figure out a better public API than our current huge omnibus?
[x] @types/diff is typed wrong

This has been rebased now that we're using extensions on main, condensing this down to a pretty small change (though there's still stuff not working).

There are still a bunch of TODOs, but this is actually green! Wow!

https://github.com/nodejs/node/pull/52762 was merged a bit ago; I should be able to retarget this PR at nightly.

@typescript-bot perf test this faster<EMAIL_ADDRESS>

Huh, where is the perf hit coming from here...?


Handling figures with multiple plots

Currently matplotcheck can't easily handle figures with multiple plots (unless I'm missing something!). PlotTester accepts an axes object, so if you have multiple plots in same figure you would need to create multiple instances of PlotTester and test each.
For example, if we create a figure with two subplots and try to check the titles of both, the current set up just looks at the most recent axis. Could be set up to iterate over list of axes, or to run on a figure and its sub-axes.
Recreate issue:
import pandas as pd
import numpy as np
import matplotlib.pyplot as plt
from matplotcheck.base import PlotTester

df = pd.DataFrame({"A": np.arange(100), "B": np.random.randint(0, 100, size=100)})

# Create figure with two subplots
fig, ax = plt.subplots(ncols=2)
df.plot("A", "B", kind="line", ax=ax[0])
df.plot("A", "B", kind="scatter", ax=ax[1])
ax[0].set_title("Line")
ax[1].set_title("Scatter")

# Create plot tester object from current axes
pt_line_scatter = PlotTester(plt.gca())

# Contains title will fail, doesn't find "Line" title
pt_line_scatter.assert_title_contains(["Line", "Scatter"], title_type="axes")

ok i have thought about this a good bit. I think what we need to do here is to test this on some homework assignments. my guess is as we figure out how we need to iterate, we will create some helper wrapper functions to handle the iteration. but i think we need to implement it first manually a few times to understand the use cases better so that these wrappers can be generic enough to be broadly useful.

update: forgot about the notebook module
ax1 = nb.convert_axes(plt) <- i think this will grab ALL axes but needs more testing.

update: the way to handle subplots is to grab each ax object independently and then test against that. we should create a vignette that shows how to do this but i think we don't have to address any bugs in this case! i'll close this!


Error when I try to install pyconcorde no Windows

Hello,
It gives me the next error when trying to install on Windows. In Linux, It works whell. Any plano to solve this issue?
Thankx in advance.
Using cached Cython-3.0.0-cp39-cp39-win_amd64.whl (2.8 MB)
Building wheels for collected packages: pyconcorde
Building editable for pyconcorde (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building editable for pyconcorde (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [110 lines of output]
running editable_wheel
creating C:\Users\bruno\AppData\Local\Temp\pip-wheel-_4983t8b.tmp-i4xqn6k4\pyconcorde.egg-info
writing C:\Users\bruno\AppData\Local\Temp\pip-wheel-_4983t8b.tmp-i4xqn6k4\pyconcorde.egg-info\PKG-INFO
writing dependency_links to C:\Users\bruno\AppData\Local\Temp\pip-wheel-_4983t8b.tmp-i4xqn6k4\pyconcorde.egg-info\dependency_links.txt
writing requirements to C:\Users\bruno\AppData\Local\Temp\pip-wheel-_4983t8b.tmp-i4xqn6k4\pyconcorde.egg-info\requires.txt
writing top-level names to C:\Users\bruno\AppData\Local\Temp\pip-wheel-_4983t8b.tmp-i4xqn6k4\pyconcorde.egg-info\top_level.txt
writing manifest file 'C:\Users\bruno\AppData\Local\Temp\pip-wheel-_4983t8b.tmp-i4xqn6k4\pyconcorde.egg-info\SOURCES.txt'
reading manifest file 'C:\Users\bruno\AppData\Local\Temp\pip-wheel-_4983t8b.tmp-i4xqn6k4\pyconcorde.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'COPYING'
writing manifest file 'C:\Users\bruno\AppData\Local\Temp\pip-wheel-_4983t8b.tmp-i4xqn6k4\pyconcorde.egg-info\SOURCES.txt'
creating 'C:\Users\bruno\AppData\Local\Temp\pip-wheel-_4983t8b.tmp-i4xqn6k4\pyconcorde-0.1.0.dist-info'
C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\normal\Lib\site-packages\wheel\bdist_wheel.py:100: RuntimeWarning: Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
if get_flag("Py_DEBUG", hasattr(sys, "gettotalrefcount"), warn=(impl == "cp")):
creating C:\Users\bruno\AppData\Local\Temp\pip-wheel-_4983t8b.tmp-i4xqn6k4\pyconcorde-0.1.0.dist-info\WHEEL
running build_py
running build_ext
Traceback (most recent call last):
File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\command\editable_wheel.py", line 155, in run
self._create_wheel_file(bdist_wheel)
File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\command\editable_wheel.py", line 344, in _create_wheel_file
files, mapping = self._run_build_commands(dist_name, unpacked, lib, tmp)
File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\command\editable_wheel.py", line 267, in _run_build_commands
self._run_build_subcommands()
File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\command\editable_wheel.py", line 294, in _run_build_subcommands
self.run_command(name)
File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools_distutils\cmd.py", line 318, in run_command
self.distribution.run_command(command)
File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\dist.py", line 1234, in run_command
super().run_command(command)
File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools_distutils\dist.py", line 988, in run_command
cmd_obj.run()
File "", line 119, in run
File "", line 76, in download_concorde_qsopt
KeyError: 'Windows'
C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools_distutils\dist.py:988: _DebuggingTips: Problem in editable installation.
!!
          ********************************************************************************
          An error happened while installing `pyconcorde` in editable mode.

          The following steps are recommended to help debug this problem:

          - Try to install the project normally, without using the editable mode.
            Does the error still persist?
            (If it does, try fixing the problem before attempting the editable mode).
          - If you are using binary extensions, make sure you have all OS-level
            dependencies installed (e.g. compilers, toolchains, binary libraries, ...).
          - Try the latest version of setuptools (maybe the error was already fixed).
          - If you (or your project dependencies) are using any setuptools extension
            or customization, make sure they support the editable mode.

          After following the steps above, if the problem still persists and
          you think this is related to how setuptools handles editable installations,
          please submit a reproducible example
          (see https://stackoverflow.com/help/minimal-reproducible-example) to:

              https://github.com/pypa/setuptools/issues

          See https://setuptools.pypa.io/en/latest/userguide/development_mode.html for details.
          ********************************************************************************

  !!
    cmd_obj.run()
  qsopt is missing, downloading
  Traceback (most recent call last):
    File "C:\Users\bruno\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 353, in <module>
      main()
    File "C:\Users\bruno\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 335, in main
      json_out['return_val'] = hook(**hook_input['kwargs'])
    File "C:\Users\bruno\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 273, in build_editable
      return hook(wheel_directory, config_settings, metadata_directory)
    File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\build_meta.py", line 445, in build_editable
      return self._build_with_temp_dir(
    File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\build_meta.py", line 401, in _build_with_temp_dir
      self.run_setup()
    File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\build_meta.py", line 487, in run_setup
      super(_BuildMetaLegacyBackend,
    File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\build_meta.py", line 338, in run_setup
      exec(code, locals())
    File "<string>", line 146, in <module>
    File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\__init__.py", line 107, in setup
      return distutils.core.setup(**attrs)
    File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\_distutils\core.py", line 185, in setup
      return run_commands(dist)
    File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\_distutils\core.py", line 201, in run_commands
      dist.run_commands()
    File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\_distutils\dist.py", line 969, in run_commands
      self.run_command(cmd)
    File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\dist.py", line 1234, in run_command
      super().run_command(command)
    File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\_distutils\dist.py", line 988, in run_command
      cmd_obj.run()
    File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\command\editable_wheel.py", line 155, in run
      self._create_wheel_file(bdist_wheel)
    File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\command\editable_wheel.py", line 344, in _create_wheel_file
      files, mapping = self._run_build_commands(dist_name, unpacked, lib, tmp)
    File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\command\editable_wheel.py", line 267, in _run_build_commands
      self._run_build_subcommands()
    File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\command\editable_wheel.py", line 294, in _run_build_subcommands
      self.run_command(name)
    File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\_distutils\cmd.py", line 318, in run_command
      self.distribution.run_command(command)
    File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\dist.py", line 1234, in run_command
      super().run_command(command)
    File "C:\Users\bruno\AppData\Local\Temp\pip-build-env-erltztqz\overlay\Lib\site-packages\setuptools\_distutils\dist.py", line 988, in run_command
      cmd_obj.run()
    File "<string>", line 119, in run
    File "<string>", line 76, in download_concorde_qsopt
  KeyError: 'Windows'
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building editable for pyconcorde
Failed to build pyconcorde
ERROR: Could not build wheels for pyconcorde, which is required to install pyproject.toml-based projects

im having the same problem, have you solved it now?

No, unfortunately


Remove attr_accessible.

attr_accessible is not available in Rails4, and is not necessary for
usage of this gem.
See upstream commits where this was already done:

https://github.com/phatworx/devise_security_extension/commit/693b56171e1b4d8e02275ffd63ec522c7af87d9e
https://github.com/phatworx/devise_security_extension/commit/1642da84469ee0da3b289e0a7a35f84fe66f5b52

Cool. Thanks.


bodyfetcher.py: give up if post doesn't have data

Recent ValueError failures from attempting to decode JSON which
wasn't there, apparently because SO is now killing off hung sockets
after a timeout.

This is somewhat tentative, see comments in chat around http://chat.stackexchange.com/transcript/message/33557162#33557162

At the moment, this is just a workaround around the actual problem. It still means we may miss posts because smokey is going to spam  Recovered from WebSocketConnectionClosedException: Connection is already closed. because the root cause of the problem is that we don't handle the {'data': 'hb', 'action': 'hb'} message correctly (it should respond back with a hb message


No aks version specified so example fails on deployment.yml

When following the example documentation for azure environments deployments the Deploy to Kubernetes cluster step will fail on the error

no matches for kind "Deployment" in version "apps/v1beta1"

which is due to the default aks version as of time of writing using kubernetes 1.16 which takes Deployment out of version apps/v1beta1 and into apps/v1
kubernetes versions have been updated making the ./manifests/deployment.yml out of date. it currently
Workaround
update the ./manifests/deployment.yml to reference apps/v1 instead of apps/v1beta1 adn add a selector field that matches the template metatdata label. example:
#./manifests/deployment.yml
apiVersion : apps/v1
kind: Deployment
metadata:
  name: raboleypipelinesjavascriptdocker
spec:
  replicas: 1
  selector:
    matchLabels:
      app: raboleypipelinesjavascriptdocker
  template:
    metadata:
      labels:
        app: raboleypipelinesjavascriptdocker
    spec:
      containers:
        - name: raboleypipelinesjavascriptdocker
          image: rabenvcr.azurecr.io/raboleypipelinesjavascriptdocker
          ports:
          - containerPort: 8080

Fix
Pin the version the kubernetes cluster will use, and then update the Deployment version to whatever works in that version.

wrong place, will put this issue in the documentation


task(FDS-524): sets selection context via selections prop

PR Author Checklist

[x] PR title adheres to Conventional Commits
[x] I have finished reviewing the contents of this PR for accuracy
[x] If needed, I have included a Changeset and it follows Semantic Versioning principles
[x] I have completed all of the above and have enabled auto-merge for this PR

Messages

:book:

packages/cascara/src/components/Table/fixtures/Selection.fixture.js: This fixture has been changed.

  Generated by :no_entry_sign: dangerJS against e838ec594fa3fc1be6bef6e99535e1c822c075de

bad source branch


Next.js examples update to fix duplicate meta tags

Improve both next.js examples by following best practices that have been recommended by the next.js lead

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Next.js examples have duplicate meta data:

As you can see in my screenshot but the meta charset and the viewport tags are twice in the souce code
Expected Behavior 🤔
Only have each meta tag once in the head, as recommended here: https://github.com/zeit/next.js/issues/6919#issuecomment-500471583
Steps to Reproduce 🕹
https://codesandbox.io/s/quizzical-wildflower-xop10?fontsize=14&hidenavigation=1&theme=dark
Steps:

Just use your developer tools and inspect the head element of the produced document, it contains two viewport meta tags and twice the charset tag

Context 🔦
I was creating a prototype with MUI to find out if it is suited for my project. I also want to use Next.js. That's when I bumped into the problem. I fixed it in my prototype and thought it might be helpful for others if I also update the MUI examples.
Your Environment 🌎

Tech
Version

Material-UI
v4.8.2

React
v16.12.0

Next.js
v9.1.7

I did a pull request to fix what's mentioned above, I moved the meta tags of the next.js examples from the _document file to the _app file as it is recommeded to do: https://github.com/zeit/next.js/issues/6919#issuecomment-500471583
I also
removed  altogether, as it is added by default: https://github.com/zeit/next.js/issues/237

They are a bunch of demos that put it into the _document. I doubt it's better. Won't it create a new font load request at each page load? https://github.com/zeit/next.js/search?p=3&q=viewport&unscoped_q=viewport

@oliviertassinari hmmm I don't know, good question, I will check this out

Do "fonts / stylesheets / scripts / ..." that are in the head element of the _app page get loaded on every nextjs page?
no, I verified this using my prototype, the css for the font only gets loaded once, for the font there were two requests one on index and again for the about page but the requests were different so I assume it's just different parts of the font that got loaded, but again only once per page, visiting any page more than once resulted in no requests
the behavior does not change if the font css meta tag is the head of _document vs the head of _app
also the observed behavior was the same in chrome v79 as well as firefox v71
I re-read the following documentations:
https://nextjs.org/docs/advanced-features/custom-app
https://nextjs.org/docs/advanced-features/custom-document
https://github.com/zeit/next.js#custom-app
https://github.com/zeit/next.js#custom-document
They clearly state that both _document as well as _app get rendered on the SSR, but the difference is that _document is not being used on the client side, while _app is
I however found another best practice concerning the title element: "why title should not be in _document but _app": https://github.com/zeit/next.js/issues/4596
So personally what I would put in _document based on what I know so far, is:

a getInitialProps that should fetch data while the page is being SSR
code to alter the html or body element, for example to change the lang="en" of the html tag to something other than lang="en" or to manually add classes to the body element

what I would put in _app:

a getInitialProps that should fetch data for all the pages but only on the client side
and everything I want to be in head element

I did some runs using bombardier to measure if there is a difference by putting a lot of meta tags (>100) into _app vs putting them into _document, but my results were not conclusive on my windows machine, they were fluctuating all the time, sometimes _document with all the meta was faster and sometimes the opposite was true

By performance I had in mind between two client side pages. I don't think it will have any impact on SSR.

Yes you are right. As you mentioned there is probably not a big if any, speed difference for SSR ... but I just realized that by adding a lot of meta tags to the _app (page) I would potentially add several kilobytes of data to both the initial rendered html page (SSR) and have those tags again in _app.js which is being transfered to the client too. As opposed to putting most meta tags in _document, which means they are only being transfered in the initially rendered html page but not in _app.js, so less overhead.
Thx for the interesting exchange, I'm glad I learned a lot about nextjs

@chrisweb Thanks for sharing your exploration of the problem. I happen to have used it quite extensively in the past, it's solid. If you care about SSR performance, be very careful with Apollo 😆. It was our first performance bottleneck, in an older project, prior to the hook area (we had >1m pages crawled by google bot a day).

@oliviertassinari thank you for your insight, yes playing around with apollo is next on my list, I'm eager to learn how it works and if find out if switching from a traditional REST / redux system to Apollo (with websockets?) will increase or decrease development time, maintabillity, performance, ...


Make hide the window (close to tray) work on all platforms if "Close …

It works when building from source, but not when I'm running a binary version of the same code
Can you confirm this?

It works, it closes to tray if Close to tray" is checked. If it is unchecked, closing yields error:
Uncaught Exception:
Error: Attempting to call a function in a renderer window that has been closed or released. Function provided here: trayicon.js:47:17.
    at Tray.callIntoRenderer (/opt/yakyak/dist/linux-x64/resources/electron.asar/browser/rpc-server.js:190:19)
    at emitTwo (events.js:106:13)
    at Tray.emit (events.js:191:7)

arghhhh you are experiencing the same  thing :(
I think this will correct it: https://github.com/averissimo/yakyak/commit/ef9597da0d72c7847dba99f1e8898b1b2e603ed5
Nevertheless, I think it makes sense to handle all events in app.coffee, maybe @davibe has some insight why it was in main.coffee
@nerijus can you test this? and maybe add to your PR if it works

I get blank screen now when starting app (even without your patch). I suspect because of too new Electron version. How do I use an older version?

you have to merge #403 (or my branch) if you are using yakyak/yakyak master. I screwed up on a PR with a typo on the menu.coffee that might be causing that

With #403 blank screen is fixed, and closing works as expected. I added your commit to the PR.


Enable (optionally?) google cloud logging when on GCE

http://googlecloudplatform.blogspot.com/2015/02/gain-business-and-operational-insight-into-your-applications-using-Google-Cloud-Logging.html

related to #592

Iiuc, this is what we would need if we wanted to write application specific (camlistored) entries to GC Logging:
https://cloud.google.com/logging/docs/install/compute_install
And apparently CoreOS is not supported for now, so I think it's a no go for now.
Just for kicks I tried it on an instance though:
mathieu_lonjaret_gmail_com@camlistore-server ~ $ sudo bash google-fluentd-install.sh
Starting installation of google-fluentd
Unidentifiable or unsupported platform.

No, we wouldn't use the agent daemon.  No Python/Ruby server running in our Docker container.
We'd just use the Cloud Logging HTTP API and log directly from camlistored.

hmm ok. the docs lead me to believe the agent was somehow still needed since it was in "Getting started".

ok, it was as tedious as usual with the google apis, but I've managed to write a log entry and it shows up in the logs I can see from the devolopers console, so it's probably good enough for us.
More news when I get the whole thing working for https://camlistore-review.googlesource.com/#/c/4887/

Done, but it's not optional. We'll reopen if it needs to be.


feat: Add pydantic v2 servicex client to requirements

Resolves https://github.com/iris-hep/idap-200gbps-atlas/issues/60

Description:

Add servicex v3.0.0a16 to requirements.txt.
Require func_adl_servicex_xaodr22 v<IP_ADDRESS>.2.107a12.
Rebuild the lock file.

cc @gordonwatts

Love seeing that build going! :-)

@gordonwatts Give things about 10 minutes for the build to propagate throughout the GitOps triggers and get into the OSG Harbor container registry and then you should be good to go with a new AB-dev image.


feat: migrate to null safety

The purpose of this pull request is to migrate the package to null safety.

Thanks for your PR :ok_hand:
But the project is already migrated to null safety on this branch https://github.com/Golapadeog/string-similarity/tree/null-safety-migration
The new package version will be available tomorrow

@chimon2000
:tada: The new version of string_similary with null safety compatibility is avialable https://pub.dev/packages/string_similarity
:bulb: Please note that null can be used by methods to compare string and doesn't throw exception

null / null = 1.0
null / "a" = 0.0
"a" / null = 0.0

:pencil: the documentation has been updated accordingly


Setting keep_warm: false after a default deployment leaves the old keep_warm_callback around

Zappa 0.44.3.
On default settings, keep_warm is set to true. If you do a zappa deploy with that, the keep_warm_callback will be created:

Scheduling..
Scheduled example-app-dev-zappa-keep-warm-handler.keep_warm_callback with expression rate(4 minutes)!

But then, setting keep_warm to false in the zappa settings will leave the callback lying around which can be confusing.

Yeah, this is the expected behavior. deploy will never remove event sources, only unschedule will do that. I know it's a little bit wonky.

@Miserlou Can this be either documented, or detected with a warning or something? This seems like a gotcha that a lot of people could hit without even knowing it.

(Either that or not setting keep_warm by default, YMMV on whether that's a good idea)

Add to doc

@Miserlou I just noticed that unschedule does not delete its matching Cloudwatch Rules. Caveat to either fix or keep in mind.


Add 3D visualization components

Describe the desired feature

App Inventor does not really provide any capabilities for manipulating/rendering 3D models.
Give an example of how this feature would be used

With new extensions like Facemesh, it would be useful to provide tools for manipulating 3D models based on inputs provided by other components.
Why doesn't the current App Inventor system address this use case?

While it may be possible to simulate 3D rendering using a component like the Canvas, execution will be much slower in the blocks vs taking advantage of the GPU rendering pipeline.
Why is this feature beneficial to App Inventor's educational mission?

This feature will enhance our AI offerings and also opens the avenue to make more games, which is often a way to introduce students to computational thinking concepts.

@ewpatton I want to work on this issue.

This is a new capability for App Inventor.  Whoever works on this should create not only the components, but also a few apps that demonstrate how kids and teachers might use it.   Also, look at other methods for doing this before creating something ad hoc.   For example, what if anything does Google MLKit do in Facemesh (which has versions both for Android and iOS)?

@halatmit sir,
I discussed with @ewpatton when I was looking for an Internship with MIT App Inventor, at that time he suggested me to read some thesis and also suggest me to implement it using OpenGL.
then I started exploring OpenGL and I found that it will not only help to draw and render 3D components also in the future we can implement Augmented Reality using AR Core.

@preetvadaliya You should probably start with a design document for what components you would add, what blocks they have, and how they work together.

@preetvadaliya
AR Core sounds like a good thing to build on, since it supports both Android and iOS.
I agree with Evan that this should start with a design document.
Also, start with just a piece of AR Core and use it to implement an app that might be made by a kid.
That's better than starting by working to implement the entire platform.
PS: One drawback of AR Core is that it apparently can't run on older phones.
But we can deal with that issue. when we get there.
Also, as Evan recommended, read Nichole Clarke's thesis
Accepted thesis

@halatmit I started writing disign document for this, I already read the Nichole Clarke's thesis Evan sir suggested me this too.
This one thing can open lots of door for development in ML and AI because it is compatible with Tensorflow Lite, AI Core, ML kit.


Resolve errors are swallowed

https://github.com/rollup/rollup-plugin-node-resolve/blob/master/src/index.js#L162
Shall err be handled first? For example, if I require('non-existed-pkg'), this plugin just throws nothing.

I tried it.
Console output:
$ rollup -c

src/index.js → dist/bundle.js...
(!) Unresolved dependencies
https://rollupjs.org/guide/en#warning-treating-module-as-external-dependency
nonexistentmodule (imported by src/index.js)
created dist/bundle.js in 97ms
Done in 0.60s.

I think is OK behavior. Modules compiled with rollup can use external dependencies that can be called in runtime later.
Can be closed now. Repen if need.

Seems fixed by #183 and released in v4.0.1. Thanks.


Please clarify the ownership parameter under ms-device-enrollment

Please clarify what the 1,2, and 3 correspond with under the ownership parameter of ms-device-enrollment. Only 2 options are discussed in the description so the reader has no way to know which option corresponds with which ownership type. Thanks.

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

ID: 39ae2ccd-9f3f-dcb5-3a20-46b1b4fd3d53
Version Independent ID: b381c208-94b1-2d22-ef16-a57c138a7d72
Content: MDM enrollment of Windows 10-based devices - Windows Client Management
Content Source: windows/client-management/mdm/mdm-enrollment-of-windows-devices.md
Product: w10
Technology: windows
GitHub Login: @ManikaDhiman
Microsoft Alias: dansimp

Hello,
if I understand it correctly, the ownership parameter can have three possible values - corporate owned, private device or ask during enrollment. However, I didn't find on any public source which value means which number (1, 2 or 3).
Dear @manikadhiman,
Could you please advise?
Thank you

Hello,
if I understand it correctly, the ownership parameter can have three possible values - corporate owned, private device or ask during enrollment. However, I didn't find on any public source which value means which number (1, 2 or 3).
Dear @manikadhiman,
Could you please advise?
Thank you

It apparently means nothing.  In fact, it may hurt other things.  I tried this today on 3 different VM's:
ms-device-enrollment:?mode=AADJ&ownership=1
ms-device-enrollment:?mode=AADJ&ownership=2
ms-device-enrollment:?mode=AADJ&ownership=3
Each of these came in as Personal devices and none of these actually prompted me to select.  But here's the problem: when I DON'T add the ownership, then the devices register in AAD as Azure AD Joined.  When I add ownership, then the devices register as Azure AD Registered.
So since I want all of these to be corporate owned, it looks like I will have to skip the ownership parameter and then run a PowerShell script after the fact to change ownership.

@MaratMussabekov should we close this Issue now?

I am fairly certain this ticket is resolved in PR #9407 .


Box warp routes

Boxing the warp routes improves build times dramatically.
Test Plan
functionality didn't change -> no new tests

Ref #1562.