env_prefix Ignored in Some Cases in Pydantic Settings

Environment:

Pydantic version: 2.9.2
Pydantic settings version: 2.5.2
Python version: 3.12.5

Description:
I encountered an issue where the env_prefix seems to be ignored under specific circumstances when using SettingsConfigDict in a nested settings structure.
Code to Reproduce:
from pydantic_settings import BaseSettings, SettingsConfigDict

class InnerSettings(BaseSettings):
    port: int = 5432

class Settings(BaseSettings):
    model_config = SettingsConfigDict(env_prefix="SETTINGS__", env_nested_delimiter="__")

    inner_settings: InnerSettings = InnerSettings()
    port: int = 5433

settings = Settings()
print(settings.model_dump())

Steps to Reproduce:

Run the following test cases:

# Execution 1: Without env vars
poetry run python test.py
# Output: {'inner_settings': {'port': 5432}, 'port': 5433}

# Execution 2: With SETTINGS__PORT
SETTINGS__PORT=42 poetry run python test.py
# Output: {'inner_settings': {'port': 5432}, 'port': 42}

# Execution 3: With nested SETTINGS__INNER_SETTINGS__PORT
SETTINGS__INNER_SETTINGS__PORT=42 poetry run python test.py
# Output: {'inner_settings': {'port': 42}, 'port': 5433}

# Execution 4: With PORT and nested SETTINGS__INNER_SETTINGS__PORT
PORT=666 SETTINGS__INNER_SETTINGS__PORT=42 poetry run python test.py
# Output: {'inner_settings': {'port': 42}, 'port': 5433}

# Execution 5: With only PORT
PORT=666 poetry run python test.py
# Output: {'inner_settings': {'port': 666}, 'port': 5433}

# Execution 6: With both PORT and SETTINGS__PORT
PORT=666 SETTINGS__PORT=42 poetry run python test.py
# Output: {'inner_settings': {'port': 666}, 'port': 42}

Expected Behavior:
The env_prefix should correctly apply to nested settings and non-prefixed environment variables should be ignored.
Actual Behavior:
In some cases, the non-prefixed PORT variable overrides the prefixed settings.

Thanks @bolshakov for reporting this. you have to change the InnerSettings to inherit from BaseModel not BaseSettings.
It is already mentioned in the docs:
Sub model has to inherit from pydantic.BaseModel, Otherwise pydantic-settings will initialize sub model, collects values for sub model fields separately, and you may get unexpected results.
https://docs.pydantic.dev/latest/concepts/pydantic_settings/#parsing-environment-variable-values

@hramezani you are right, I missed this part and it kind of make sense. Thank you for taking the time to answer 🙇♂


Adds more documentation

Adds installation notes to the README file
Adds License information to the README file
Changes the hooks section in the README file to conform to the format the Craft manual uses
Changes wording for the sake of clarity

Fixes #36

Also thanks!


Firewall

Would you happen to have any directions for setting this up on a firewalla gold? simular to the items listed here: Firewalla Tutorial: Expanding With Docker Containers

Nope, sorry.
My recommendation is start with open firewall between the VLANs and the slow restrict it.
In general if it is sonos on the IoT VLAN the sonos needs to make a TCP connection back into your LAN to the client requesting the streaming (yes i know that seems backwards but thats how it works) - basically you have to give the permission to make any connection it wants.  At which point IMHO its pointless putting it on a vlan....

no reply, closing


Problem about group convolution when NSC2

Openvino version: openvino_2020.1.023
Device: NSC2
Problem:  When I test the infer time of mobilenetv1, I find out that there exists some bugs with group convolution. For example, for a group convolution, the input tensor is 64HW, and the group convolution parameters are(in_channels=64, out_channels=128, kernel=(3,3), group=64//2 ), ATTENTION!, When the group is 64//2, not 64, the infer time is so slow and loading network needs more time. And the group is 64//4, it also causes some problem.

BTW, the input resolution is 320*320, for original mobilenetv1, infer time is about 40ms.
And I changed the group parameter to half, which means 64->32, 512->256, etc. The infer time is 120ms. (SO weird!). Group parameter to 1/4, 81ms; Group parameter to 1/8, 58ms; mobilenetv1_without any group convo, 116ms

Help

Can you provide more information to allow reproduction, please?
Where to get the model from, have you converted it, how?
Which sample application have you used, how? Can you share the command lines (with a camera? With images, with a video?), please?

I get the model from MXnet and converted it.
I changed the params of group conv in mobilenetv1. For example, group=64 -> 32 (half of original params number). I tested with a random image. The sample application is
/opt/intel/openvino_2020.1.023/deployment_tools/inference_engine/samples/python/classification_sample


better use of IsCaseSensitive

Should be able to check case-sensitive on IFileSystem and any file system object IFileSystemInfo.
Also, test should only need to happen once during execution; cache the result.

callers can cache if they want; Api here is stateless.


Finish basic gRPC / gRPC Gateway service

This allows you to do:
$ go run main.go
$ curl localhost:10000/v1/echo/foo
{"content":"this is a foo message"}

Also, while I'm here, generate and serve swagger.json

I'm reading through this. I don't immediately understand why we'd want to keep two copies of the swagger (api.swagger.go and api.swagger.json) both checked in.


Highlight embedded variables in strings

Description:
Embedded variables could be highlighted. Eg: "${ballerina.home}/bre/security/ballerinaKeystore.p12"
Affected Versions:
0.974.0
OS, DB, other environment details and versions:
vscode and composer

Fixed with #9305


Server Source Code

Will the server source be made available at any time soon? Like, maybe allow people who are actually going to put an effort into the app and community can make Howlr, ya know, not be terrible. Oh, and importantly, maybe they can make a fork that has some sort of community support, but hey, having complete radio silence works too.

They clearly have other things on their plate and releasing the backend code would significantly increase their security risks in the short term requiring their full attention and long term full time project management.  It is obviously not something they are ready to do.  The front end code is right there and AWS has a free tier there is nothing stopping you from writing your own clone.

I would believe that, but it doesn't seem anything about this has been updated in a long while. They went radio silent in about 2018, the app still looks like it was build forever ago, there is no means of support, the last commit was close to a year ago at this point. It just seems like the project is being neglected, and on their site (which was updated god knows when) they said they are going to release the server source ... I just wonder if GTA 6 will release before they actually release it.

Hello @yiffboy16 !
We are still planning on releasing it, not sure when though. Here are the steps we want to follow:

cleanup the code (it's really small, but it lacks comments) and make the server easily installable on a development environment
write an installation and deployment guide
have some kind of closed preview if anyone wants to look for security issues before we release it, our unit tests covers most logical errors we could think of and we try to follow the best practices as well as we can, but you never know.

I'll close this issue when the backend part is released.

[ ] Cleanup the legacy stuff
[ ] Write a README in English (it's currently in French) with installation instructions
[ ] Publish our reverse-geocoding server code (it can be done before we release the backend)
[ ] Write a better seed script so that people don't have to manually add every groups, genders, etc
[ ] Push the code coverage to 100% (it's currently at 99.87)
[ ] Add sample config and credentials files


Initial windows support

Issue Link :link:
#3461
Goals :soccer:
To add support to Alamofire for Windows
Implementation Details :construction:
A Windows specific mutex wrapper had to be created. Otherwise, the same changes that apply to Linux apply here as well.
Testing Details :mag:
I’ve added Windows CI, but haven’t been able to test it yet because I need maintainer approval

@jshier this should be ready for review


Border windows invisible in Mission Control

When the border is on a window, and mission control is activated, the focused window is invisible in the space thumbnail. Not sure if there is a way around this.

Is anything focused when Mission Control is activated? Wouldn't there be no focused border if there was nothing focused?
Have I misunderstood the issue?

Nevermind, I have misunderstood the issue. You're talking about what the focused window was, not the border.

Right to clarify, when using a the focused border, the focused window will always be invisible in mission control.

On the left side of the thumbnail there should be a tall window.
Seems like OS X is thinking the border-window is the focused window, not the window behind it.

Right, yeah

I took a look at this and this is probably a limitation (maybe a bug) of mission control.
Probably for performance reasons they just ignore the alpha value of windows when rendering them in these thumbnails.
If we can track when we enter/exit mission control we could probably clear the border so the window become visible again.

Related: the border should get moved to the new space when you switch spaces from mission control.

Related: the border should get moved to the new space when you switch spaces from mission control.

Can't be fixed. After switching space through mission control, re-enter missionc ontrol and exit again, and the border will be shown.
This appears to be a side-effect of fixing the side-effect of the fix for #131.
I'm sure cHoco can fill you in if necessary.
The point I guess is, there will always be side-effects due to OSX.

This is actually no longer an issue with the latest master. I've gone back to having kwm-overlay 'join all spaces', instead of Kwm moving it from space to space.


Data uploader: Allow schema to be specified for each data subset

It would be useful if one could explicitly specify the database schema that a dataset should be uploaded to in an input config json file, e.g.:
        {
            "type": "...",
            "skip": false,
            "schema": "public",
            "subdirectory": "...",
            ...
        }

This would also make the upload process more robust against (accidental or intentional) changes of the default schema in the database.

linked with #411


Helm 3 uninstall --purge by default

With Helm 3, the decision was made to include --purge by default when running helm uninstall. I'm curious how the decision was made, and if this was the best option for the default.

Feedback from the Helm community suggested that people used --purge more often than not and people new to the helm were confused that helm delete did not remove the history as well. This was the main reason behind the decision and why we thought it was the best option. Refer to #5283 for more details.

Actually, now that I think of it, I have used --purge so many times and the
times I have not used, it was always because I forgot and then got an
"release already exists" error during next installation and had to rerun
delete command with --purge
On Tue, May 28, 2019, 2:40 PM Martin Hickey<EMAIL_ADDRESS>wrote:

Feedback from the Helm community suggested that people used --purge more
often than not and people new to the helm were confused that helm delete
did not remove the history as well. This was the main reason behind the
decision and why we thought it was the best option. Refer to #5283
https://github.com/helm/helm/pull/5283 for more details.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/helm/helm/issues/5804?email_source=notifications&email_token=ADBXB2CW5C3LLX6VLZWBDXLPXTZIJA5CNFSM4HP7KAT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWLPLLY#issuecomment-496432559,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADBXB2HV5BNLLJPHWVQXAG3PXTZIJANCNFSM4HP7KATQ
.


Blazor tutorial UE pass

Addresses #19286
Internal Review Topic

@captainsafia ... Same thing on this one ... just a batch of UE nits. It looks good locally, and I'll make sure it displays well when live.


[Plugin] Add Authentication using IMAP server

This plugin enables the authentication with an IMAP server. It's tested and being used in https://blog.leinelab.org/
In order to achieve this some changes in the core were necessary.
2 new hooks were introduced in bl-kernel/boot/rules/60.plugins.php

beforeVerifyUser
afterVerifyUser

These hooks are used in the bl-kernel/login.class.php.
These core changes enable more plugins to hook into the authentication process and work complimentary with the default (database) authentication.
The plugin has 2 DB fields in which the server and the encryption is saved. It uses imap_open to connect to the IMAP server and verify the given credentials.

Hello, with the new version of Bludit v4.0 rc1, I would like to close the old Github issues. If you feel that your issue is not resolved in the latest version, create a new ticket.

Help and Support use the Forum https://forum.bludit.org
Bugs and new requests here in Github https://github.com/bludit/bludit/issues


[Tick] The component is receving not recognize props causing a console warning

Create a bug report to help us improve Bold 💪
Depends on:

#863

Describe the bug
The component is having problems with not recognize props, as "vertichalAnchor" and "visibleTickCount"
To Reproduce
Steps to reproduce the behavior:

Using the component Tick calling inside a Chart Component

Expected behavior
Do not throw warning console to a not recognize props
Screenshots

Issue
Console warning
Console warnings are still thrown when using the Range Area and the Composed Chart components.
Range Area:

Composed Chart:

[ ] Developed
[ ] Tested


Use Tesseract 4

With an option to switch back to 3.04 in case of emergencies.

@rhiaro I'm trying to compile tesserocr against tesseract 4 in a docker container right now. Do you recall how you did that?

I don't remember specifics, but I think tesseract in this aleph branch was working when I left it: https://github.com/alephdata/aleph/commit/4668ca8d28edb506c60acbee1f6bf1138b0dbeed

Oh, I didn't realise it actually shipped with bionic. In that case it's been auto-solved. Thanks!


Improving the Biographies page !!

Related Issue
[Cite any related issue(s) this pull request addresses. If none, simply state “None”]
Fixes:  #4603
Description
This PR introduces several enhancements to the Romance Books page to improve the overall user experience and aesthetics.
Improvements Made

Title Bar: Enhanced with a clear title and improved typography.
Icon Integration: Added a unique literature-themed icon for better branding.
Navbar: Redesigned for responsiveness and added hover effects.
Footer: Updated with links, social media icons, and copyright information.
Card Design: Improved layout, high-quality images, and interactive flip effect for book cards.
Responsive Design: Ensured optimal display on various devices using CSS media queries.
Visual Consistency: Established a cohesive color palette and consistent typography.
Accessibility Features: Added descriptive alt text for images and ensured good color contrast.

Type of PR

[ ] Bug fix
[x] Feature enhancement
[x] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
BEFORE:

AFTER:

Checklist:

[x] I have made this change from my own.
[x] I have taken help from some online resources.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

Please add level 3 label , i have enhanced the total page !!

@abhi03ruchi , please review it


Optional example /dummy app in the tests folder?

First up - thank you for such a great OSS project! This looks great and will save me a TON of time otherwise spent reinventing the wheel :)
I see a lot of modern ember-cli addons use the built in dummy app (under tests) to show an example of the addon. This also helps from a testing standpoint because you can integration test the addon using that app (full stack). Would you be up to add something like this (if I submit a PR lets say).
Do you currently have a living "example app" that you'd prefer I use to port this with or will this be all new dev work?

:+1: I am also interested in using this app and haven't figured out how to use it yet.  A working example would be wonderful.

Because I never heard back I actually wrote a simple auto complete /type ahead that is HTMLbars friendly (requires ember 1.11)
https://github.com/toranb/ember-cli-auto-complete

@toranb I hadn't seen yours yet. I'll give it a try. Thanks!

@toranb I'm sorry that we dropped the ball on this. I admit, we end up fighting with twitter typeahead on every project, and the effort to extract this component was difficult since it was heavily customized.
I'm not sure what the future is for this plugin, and we'll also give yours a try.

@cowboyd sorry to cross promote my addon in your very project :( but as I didn't see much activity I thought it was worth mentioning to help others who (like me) needed a simple type-ahead

No it's fine, there are about 10 different typeahead solutions out there, and not more than a few based on twitter typeahed,  and it can be difficult to make heads or tails out of them. I actually think I'd like to move us behind a single typeahed solution that can get some proper love.


Improve creation of devices

Now that we have several plans using the same devices, they are being created and connection waited for several times at the beginning of artemis main - see test_when_blueskyrunner_initiated_then_plans_are_setup_and_devices_connected in test_main_system
we should fix this in main which, in init, instead of:
        for plan in PLAN_REGISTRY:
            PLAN_REGISTRY[plan]["setup"]()

should collect a list of devices to initialise, ignoring duplicates, and then do them all once
and fix test_when_blueskyrunner_initiated_then_plans_are_setup_and_devices_connected to test devices once

I think that this means there should be a global list of all instantiated and connected devices, probably in dodal

In the end I think it's intractable to manage at the device level (how many epicsmotors can there be?), but beamline modules should ensure beamline devices aren't created twice (either as global vars at the beamline model level, or as singletons returned from i03.aperture_scatterguard() or similar)


Allow override of FIRST_CALL reset_camera in show_all(...)

I suggest a fix/enhancement to allow override of the "reset_camera" option on FIRST_CALL that is happening in show_all(...)
I often run/debug/re-run via the "Run Python FIle" function (which I mapped to F5 key to be closely aligned with OpenSCAD workflow) rather than through a debug interface.  But this has the result of always resetting the camera on each run.  To mitigate this, I've changed my local copy of ocp-cad-viewer this way to disregard the FIRST_CALL setting if any "reset_camera" option is provided by the caller:
    if FIRST_CALL:
        if kwargs.get("reset_camera") is None:
            kwargs["reset_camera"] = Camera.RESET

and then in my b123d script, I call show_all(reset_camera=Camera.KEEP) which solves the problem for me and keeps the view consistent between runs.  And it doesn't seem to interfere with any of the provisions in place for debugging.  Perhaps you could add this fix or something similar to override the FIRST_CALL behavior if desired by the caller.
As an added feature, if calling this way, it would be nice if the "Reset View" button in the viewer would behave as an on-demand reset_camera.RESET action and reset the view based on the bounding box.  Currently if/when I actually do want a camera reset, I have to add a parameter-less show_all() and re-run to achieve it.

disregard the FIRST_CALL setting if any "reset_camera" option is provided

I'll have a look. I added this behaviour, since when showing different objects in different runs and their bounding box is very different, strange things could happen. So a proper reset before each run seems appropriate.
How about using the Jupyter approach with separating code parts by # %% and then use Ctrl-Run or Shift-Run again and again on the same same piece of code?
It looks like you are trying to simulate that.

the "Reset View" button in the viewer would behave as an on-demand reset_camera.RESET action

This was a design decision that the reset button gets you back to your initial camera position in case you wanted to check something under a different angle. I use this very often and don't want to change this behaviour.
I would really recommend to look at the interactive way of working. Just add # %% at the top of your file and then press Shift-Enter. Another advantage is that it only loads build123d and OCP once. Very fast!

btw. , when you use the buttons "switch to iso view" and the "fit view", you should by back to the "reset" view

I sometimes use the Jupyter approach also; I just prefer the full-run approach.  Allowing some provision to override FIRST_CALL seems to support both approaches without one impacting the other.  I wouldn't expect it to be a common use case to override it, but it's nice to support it if the user desires to do so.
I didn't think about "switch to iso view" followed by "fit view" accomplishing a reset, but I agree that's a sufficient solution.  I'm not sure if it's just my installation, but I seem to get into the situation pretty often where "fit view" doesn't seem to do anything, so I haven't gotten into the habit of using it until now.

Allowing some provision to override FIRST_CALL seems to support both approaches without one impacting the other.

I need to think about whether your approach works in all corner cases (reset_camera is a bit of a nasty thing) or if I prefer to add (yet another) parameter or enum flag

"fit view" doesn't seem to do anything

Fit view simply sets the zoom factor back to 1. So if you haven't zoomed in or out, the zoom factor is 1 and "Fit view" does nothing. If the zoom factor is not 1 and  "Fit view" does nothing, then it is a bug.
You can check with status() or more explicit status()["zoom"] (this command asks the viewer about all current settings)

In 2.0.13 KEEP will retain the view across sessions.
FIRST_CALL is removed.
If one needs to have a reset for the first call, reset_camera=Camera.RESET needs to be added to show


Add provider ID to context v2

This will be used in future PRs.
Summary
Provide a brief overview of the changes and the issue being addressed.
Explain the rationale and any background necessary for understanding the changes.
List dependencies required by this change, if any.
Fixes #(related issue)
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[x] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 52.476%. remained the same
when pulling 97e454f5a45133399e81f0b2a149e566a8d7f140 on context-v2-provider-id
into 3aae27127789ec3aa2400b391019854311c205c8 on main.

Punting on this for now.


Version 0.4.0 broke the UI

What happened?
ERROR: No Lock Code Manager configuration with ID [redacted] found!
Steps to reproduce the issue

install 0.4.0

...
Home Assistant Version
2024.3.1
What version of Lock Code Manager are you running?
0.4.0
Lock make and model
Kwikset 916 zwave
Relevant log output
No response
Screenshots
No response
Anything else?
Yaml:
strategy:
  type: custom:lock-code-manager
  include_code_slot_sensors: true

views:
  - strategy:
      type: custom:lock-code-manager
      config_entry_title: Home Locks
      include_code_slot_sensors: true
    icon: mdi:lock-smart
    title: Lock Code Manager

does https://github.com/raman325/lock_code_manager/pull/88 fix your issue?

So I removed the following from custom_components/lock_code_manager/providers/zwave_js.py:
from zwave_js_server.client import Client (line 9) and

line (147 through 149)
        client: Client = self.hass.data[ZWAVE_JS_DOMAIN][
            self.lock_config_entry.entry_id
        ][DATA_CLIENT]

and added 146 through 152:
       if (
            client := self.hass.data.get(ZWAVE_JS_DOMAIN, {})
            .get(self.lock_config_entry.entry_id, {})
            .get(DATA_CLIENT)
        ) is None:
            return False
        _LOGGER.error(client)

And it did not fix the error and it had problems connecting to my zwavejs-ui instance

Start up times are also greatly increased on 0.4.0.  I havent had time to check if this was the case on the previous version

OK then I need more information in order to chase down this issue because everything is loading correctly on my side. Two things:

Please try a different browser and make sure it's not Chrome caching the bad result
Open dev tools and share what you see on the console tab. There's likely an error that will hint at what's going wrong

It was a chrome caching issue, may bad, I should have known better.  Thanks


fix(ngClick): subract processing time of the click action

subract the time it takes for the browser to process the click action for preventing the ghost click. long running processes or slower devices where a lot of rendering is happening would get the ghost click every time.

I feel like this way of calculating the processing time is not reliable, since it depends on factors that vary over time.
E.g. due to the asynchronicity of $timeout and click events, the current processing load will determine the processing time for a future click event (by which time the processing time may be totally different).

I'm not sure I understand what you mean by "the current processing load will determine the processing time for a future click event". It should calculate independently for each tap, it doesn't store the time and reuse it for future events.
I added a test to show what I mean for the long running process.
Thanks for taking the time to look though :)

calculateProcessingTime() is called upon touchend, but processingTime (which is used upon click) is calculated using a $timeout (i.e. asynchronously). There is no guarantee (afaict) that the timeout will have been triggered before the click event has been dispatched on the element.
Do I miss something ?

I don't think you are missing anything...
It is true that there is no guarantee(because it depends on the browser for how timeouts are queued up), but in theory it should be added to the timeout queue to be executed before the click(which is something like 300 milliseconds). In the case that the browser executes click without respecting the timeout queue, it has a processing time of 0(which is how it worked before).
I'm really not sure which way to go with this... because timeout and events are so dependent on the browser. I just know that this is an issue that I have run into(only when doing things inefficiently though).
Sorry for the long delay. Holidays...


Update instance and model when record_as_success

When we record the command as SUCCESS (exit_code=0) we also need to
update the current instance of BuildCommand because self.exit_code
is used to calculate BuildEnvironment.successful. The later is part of
the decision of update_on_success, and as the command was marked as
failed, we were updating the status.
This looked as a random failure, but it was happening always that any
of the record_as_success command failed, but it wasn't easy to see
it because it the jQuery request has to be done exactly after the
Build was marked as FAILED and before the next command was executed,
since the state was changed immediately to "Building"
Fixes #3644

I found another edge case:
When we use record=False, for example to run git status, that command is not recorded in the database, but it's added to the list of command that the BuildEnvironment has executed:
https://github.com/rtfd/readthedocs.org/blob/01bcfe4f1ddcafd62b815ca9bb8a5ca06116ea41/readthedocs/doc_builder/environments.py#L345-L347
So, we have the same problem than I explained in the description: this command is add to the commands list of the instance with exit_code=128 (the repository didn't exist), we don't record it in the db, but then to check update_build we use the commands from the instance:
https://github.com/rtfd/readthedocs.org/blob/01bcfe4f1ddcafd62b815ca9bb8a5ca06116ea41/readthedocs/doc_builder/environments.py#L560-L567
and self.successful returns False in this case because the first command has failed (git status).

I just fixed the last edge case that I found.
This PR will need some review since it seems simple and coeherent but its touching an important chunk of code.
Also, the solution proposed here is not the best regarding desing or code style. Although, implementing another solution will take too much refarctoring since we will need to adjust/discuss other concepts probably.

@stsewd could you help me by testing this PR in your local instance and trying to reproduce the issue? Thanks!

I was able to reproduce the issue on the current master, but on this branch on several build everything looks good!
p.s: kind of I was fixing this on other pr without knowing https://github.com/rtfd/readthedocs.org/pull/3687/files#diff-ca52b098301dd315a834b3556ab9a7d5R363 haha


newer/maintained syntax highlighting

Migrates highlighter to highlight.js, which is maintained and supports more languages. Hope you like it.

you can see what it looks like here https://bin.st5ve.com/

Let me know if this addressed your comment. Happy to do the work. Kinda went on a coding bender. :)

Yep, everything looks good now! Merging...


NTR: progenitor cell

Hello, we would like to request a term for "progenitor cell". Right now a lot of progenitor cells (e.g. CL_0000038, https://www.ebi.ac.uk/ols/ontologies/cl/terms?iri=http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FCL_0000038) can be traced back up to "precursor cell" (CL_0011115) which we feel is too broad of a description and lacks the connection to a "progenitor cell" term. The "progenitor cell" term can be a subclass of "precursor cell" (CL_0011115)  like "stem cell" (CL_0000034) is currently.
From our understanding: "A progenitor cell is a biological cell that, like a stem cell, has a tendency to differentiate into a specific type of cell, but is already more specific than a stem cell and is pushed to differentiate into its "target" cell," (Lawrence, B.E.; Horton, P.M. (2013). Progenitor Cells : Biology, Characterization and Potential Clinical Applications. Nova Science Publishers, Inc. p. 26.). "Progenitors are typically the descendants of stem cells, only they are more constrained in their differentiation potential or capacity for self-renewal, and are often more limited in both senses" (https://doi.org/10.1016/B978-0-12-409503-8.00002-0).
Thank you for your help and consideration.

To clarify - are you proposing the hierarchy:
precursor cell
-stem cell
--progenitor cell (develops from stem cell)
Does this look correct?

Hi @nicolevasilevsky, yes that looks correct to me. However, I don't know if there are exceptions or cases where progenitor cells do not develop from stem cells that we should be wary of.

In my understanding, a progenitor cell is a type of 'precursor cell' that has a develops_from relationship with 'stem cell'
'precursor cell'

'stem cell'
'progenitor cell'

logical definition of 'progenitor cell'
'precursor cell' and 'develops from' some 'stem cell'
Alex

@addiehl - I added this term, would you mind reviewing the PR?
Thanks!


Support executing run_codenarc.py directly in pipeline library

This PR adds a new option to the groovylint singleton: resourcesDir. When specified, it will extract run_codenarc.py and its associated resources there and then execute run_codenarc.py using the system's built-in Python interpreter. This can be useful for projects which are very large, and thus take a long time for the Dockerized groovylint to examine due to the reduced I/O.

@dgl-ableton Sorry, this PR is not quite ready for review just yet. :sweat_smile:


allowForwardedTraffic description no consistance

https://docs.microsoft.com/en-us/rest/api/virtualnetwork/virtualnetworkpeerings/createorupdate

properties.allowForwardedTraffic
boolean
Whether the forwarded traffic from the VMs in the local virtual network will be allowed/disallowed in remote virtual network

and this doc status flow from remote to local is allow/disallowed so which one is correct ? pls amend the wrong statements in both doc and keep the definition consist

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

 We are currently investigating and will update you shortly.

@yull1860 These 2 explain the same thing, only doc does a more lengthy explanation.
When making a VNET Peering, you have to peer VNET A to VNET B, and then VNET B to VNET A. If you want forwarded traffic to flow from A to B, then this setting needs to be enabled on the peering from VNET A to B.

The key is which direction it is controlled , say peering from A -> B , my understanding for allowForwardedTraffic is allow traffic from B->A when it is from outside of B . https://docs.microsoft.com/en-us/rest/api/virtualnetwork/virtualnetworkpeerings/createorupdate is not reflect this.

@yull1860 Thanks for clarifying. This statement in the doc is quite misleading:

'to allow traffic forwarded by a network virtual appliance in a virtual network to flow to this virtual network through a peering'

Would changing this statement to

'to allow traffic forwarded by a network virtual appliance in a virtual network to flow FROM this virtual network through a peering'

be enough to clarify?

No , the doc https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/virtual-network/virtual-network-manage-peering.md is CORRECT , but https://docs.microsoft.com/en-us/rest/api/virtualnetwork/virtualnetworkpeerings/createorupdate stated WRONGLY (can't find feedback button on the page so raise the question here)

a@yull1860 I checked the definitions for the CLI and PowerShell, and they also conflict:
CLI: Allows forwarded traffic from the local VNet to the remote VNet.
PowerShell: Indicates that this cmdlet allows the forwarded traffic from the virtual machines in the remote virtual network.
Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.
@altambaw @allegradomel FYI, conflicting definitions on 'Allow Forwarded Traffic'

@yull1860 Thanks for your dedication to our documentation. We've created an internal work item to incorporate your suggestions in the swagger for API/SDK/CLI to update the flag description. It will take sometime for the changes to be updated and reflected in the docs. We are closing this issue for now, but feel free to comment here as necessary. #please-close


mac link inside linux machine doesn't work with docker command

Describe the bug
This was working in version 1.7.3 but stopped working in 1.7.4
To Reproduce
matt.schurenko@devbox ~ $ mac link docker
symlink /opt/orbstack-guest/bin/macctl /opt/orbstack-guest/data/bin/cmdlinks/docker: no such file or directory

Expected behavior
mac link docker should work and then we should be able to run docker inside the linux machine
Diagnostic report (REQUIRED)
OrbStack info:
Version: 1.7.4
Commit: e03df71b90121e11c379c6273bd0a63166b33957 (v1.7.4)
System info:
macOS: 15.0 (24A335)
CPU: arm64, 8 cores
CPU model: Apple M3
Model: Mac15,3
Memory: 16 GiB
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2024-09-25T20-56-28.907201Z.zip

Screenshots and additional context (optional)
No response

Already fixed for v1.7.5.

Released in v1.7.5.


GitHub workflow deprecated GitHub actions #535

Pull Request for Issue https://github.com/microsoft/dev-proxy/issues/535 - Workflow Enhancements and Dependency Updates
Here are the key changes:
Node Version Specification:
I have explicitly set Node.js version 20 in the YAML configurations of the following workflows:
codeql-analysis.yml
create-release.yml
dotnet.yml
This update ensures that our workflows use Node.js version 20, enhancing the project's compatibility and keeping our tools up-to-date.
Workflow Version Updates:
I've upgraded the workflow actions to their latest versions:
actions/checkout@v4 (from v3)
actions/upload-artifact@v4 (from v3)
actions/setup-dotnet@v4 (from v3) # Use the latest version that supports Node.js 20
Checks and Validations:
I've tested these changes, and the automated checks confirm that the pull request is free from issues.
Please take a moment to review this pull request, ensuring that everything aligns.
Thank you.
### Sorry for so many pull requests; there's been too much confusion. It's been 7 days, and I am new to GitHub. I mistakenly deleted my branch. Sorry for that. This is a new pull request.


feat: init operator project & add webhook

Purpose of the PR

close #256
close #258

Main Changes

Re-initialize go project (operator).
Add Webhook to deny update.  Launch pod with two containers (original controller and new manager).
(I will describe detailed changes in few days.)

List some TODO here:

[ ] Add doc.
[ ] Modify CI and build workflow.
[x] Make sure how to generate CRD for <1.16. Currently, meet incompatible api, here are error logs: apiVersion "apiextensions.k8s.io/v1beta1" is not supported when executing make gen-all under crd-generate

Verifying these changes

[ ] Trivial rework / code cleanup without any test coverage. (No Need)

[ ] Already covered by existing tests, such as (please modify tests here).

[ ] Need tests and can be verified as follows.

[ ]  Nope
[ ]  Dependencies (add/update license info)
[x]  Modify configurations
[ ]  The public API
[x]  Other affects (typed here)

Documentation Status

[x]  Doc - TODO
[ ]  Doc - Done
[ ]  Doc - No Need

Hi @coderzc  @imbajin  @simon824  @javeme ,
Now, hugegraph-computer-operator-controller-manager pod will launch two containers: manager and controller.

controller remains the same which contains controller logic.
manager is launched for creating Webhook to deny update, cuz java client does not have convenient api, so this part is implemented in go, that's why we have to declare two containers.

We have to update doc, images, resource yaml file, I will be appreciated if you can instruct me how to finish these :D

We have to update doc, images, resource yaml file, I will be appreciated if you can instruct me how to finish these :D

Good job！
BTY，I think we should consider rewriting controller in the future using the Go API.

Hi @coderzc , I have updated deployment guide in PR description. Can you help test it when you are available?

@imbajin PTAL


isError only identifies literal errors when extending Error and targeting IE

Version
3.0.1
Reproduction link
https://codesandbox.io/s/o8v2plnoz
Steps to reproduce
Make a custom error using the class-extends syntax.
Throw error during a route transition.
What is expected?
Error is caught and sent to Router.onError handler.
What is actually happening?
Error is being identified as a plain object.

Have a custom error to carry notifications with uncaught errors in an application.
No notifications were showing up in production where we support IE11.
The custom error correctly identifies as an instanceof Error, but the util/isError function deems it an object.
I'm currently using some snippets from https://github.com/onury/custom-error-test to get the Error prototype on my custom error.

Codesandbox doesn't work on IE11...
Anyway, I tested using babel: https://babeljs.io/repl#?babili=false&browsers=&build=&builtIns=false&spec=false&loose=false&code_lz=MYGwhgzhAEByCmB3AogJ1Qe1deAPALvAHYAmMam2A3gL5A&debug=false&forceAllTransforms=false&shippedProposals=false&circleciRepo=&evaluate=true&fileSize=false&timeTravel=false&sourceType=module&lineWrap=true&presets=es2015%2Creact%2Cstage-2&prettier=false&targets=&version=6.26.0&envVersion=
class NewError extends Error {}

and our isError function works properly to detect errors. Maybe you are not configuring babel correctly

You are correct. I updated my babel packages and everything works fine now.
I must have been in that weird error vortex where I did the same thing on the babeljs website and it wasn't working for me. But today, lo and behold.
Thanks, and sorry @posva


Cilium API handler panicked at url /v1/identity/12345

Cilium v1.6.3
Using etcd for identity propagation, not CRD.
level="warning" msg="Cilium API handler panicked" client=@ method=GET panic_message="runtime error: invalid memory address or nil pointer dereference" subsys=api url=/v1/identity/12345

Digging around in the API handler for identity labels fetch, I found that PR https://github.com/cilium/cilium/pull/9138 makes a bunch of changes in this area. It is intended to clean up casting in conjunction with the kvstore, and it may inadvertently fix the issue.

There were identity releases occurring 8 seconds prior to this log message, but unfortunately the identity number is not known, only the labels. So there's no way to determine whether they are related to this message or not.

Not sure why I linked #9636, in context the comment seems to be entirely unrelated to this issue.

@joestringer do you have more info regarding this? A stacktrace? Can we add more debug messages into Cilium that allow us to easily find the issue in the future?

There is a backtrace, I pinged you on Slack with deeper links.
The failure is actually on line 123 of identity.go where the Identity is dereferenced to fetch its NumericIdentity:
https://github.com/cilium/cilium/blob/e6233255ff3b9f30acdc445784413f9964612cb9/pkg/identity/identity.go#L117-L126
The weird part is that there's a nil check just before the dereference which apparently passes, so that suggests that this code is being executed with the receiver being a shared pointer which gets reset or something?
The identity in this case appears to be a local identity.

Given the new information above, I now doubt that #9138 fixes the issue and expect that this bug is still present on master.

@joestringer @aanm What are the next steps on this issue? Do we need more information?

probably related to https://github.com/cilium/cilium/issues/8816

@aanm Do you know if we've seen this in any recent releases?

@joestringer no, I think we can close this. It was probably related with #8816


Username as default

[ ] Show the username instead of the full name
[ ] Make username a field during registration

I would like to work on this one if is ok :)

Go for it!

As I was working on this I realized that there are some unknowns:

Should we make the username field a required one meaning users cannot register without a username and we do not automatically generate it.
If we make the field required, I guess we do not need the saving hook on the User model
If we don't make the field required and we keep this logic of automatically generating a username, we need to do it on the front-end side, meaning as the user types his name we somehow display what the username will be, then the user has the chance to accept the automatically generated one or just write it's own.
Should we allow users to change their username after the account was created?

This are some unknowns for me and I don't really want to chose by myself some solution.

Should we make the username field a required one meaning users cannot register without a username and we do not automatically generate it.

Yes

If we make the field required, I guess we do not need the saving hook on the User model

True

If we don't make the field required and we keep this logic of automatically generating a username, we need to do it on the front-end side, meaning as the user types his name we somehow display what the username will be, then the user has the chance to accept the automatically generated one or just write it's own.

Would be nice to have, but not necessary. Feel free :)

Should we allow users to change their username after the account was created?

Let's not allow that for now, as it might have unforeseen consequences. For example: I'm debating whether it's worth allowing comments on arguments, where people can tag eachother. It will be easier to have fixed usernames for the time being, we can always expand on it later.

Thanks for clarifying things a bit. I also agree that we can keep it as simple as possible initially and build upon this later as we understand how this will all work.


Add pull request feature to Board. - [closed]

In GitLab by @wknet123 on Apr 16, 2018, 03:10
Merges dev-pull-request -> dev

In GitLab by @wknet123 on Nov 13, 2019, 10:49
The test coverage for backend is  %   and for frontend is 38.11%   check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:49
the it is failed check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:49
closed


Store version in NBCLI class and display on some log messages

Solves #16
How to display the version was subject to interpretation. Please suggest improvements.

Only one urgent fix. The version format that is native to the artifact coordinates works for me.

The getVersion() call is identical to what is done to generate the artifact coordinates. I'm not sure what else you are asking to change?

Let me clarify:

The format is not that consequential. The fact that it is identical to the internal coordinate format works for me!
There is another comment which is an urgent request for this PR, which is to fix the order of initialization in the static block.

There is another comment which is an urgent request for this PR, which is to fix the order of initialization in the static block.

Did you look? Because that request was resolved?


Bump insecure versions

Description
Changes proposed in this pull request:

Bump package.json dependencies due to their vulnerability.

Related issue(s)

/retest


Update main.go

add some note

PRs to improve client-go should be opened against https://github.com/kubernetes/kubernetes
source in this repo is published from https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/client-go


Amend api specs

Update repo root readme
Review and update API spec descriptions

Resolved all conflicts and checked spelling (fixed where needed). Please approve.

And its says 1 changed is still requested. I don't understand which one...


Make zebra-script wrap the C++ script implementation in zcashconsensus

Adds a wrapper for the C++ script implementation in zcashconsensus.
Link to discord discussion: https://discordapp.com/channels/676527656170160146/716086297210650634/735255389892771892

blocked by https://github.com/ZcashFoundation/zebra/issues/452 and then https://github.com/ZcashFoundation/zebra/issues/724

Updated description to reflect that UTXO management is out-of-scope.

Currently blocked, more details here: https://github.com/ZcashFoundation/zebra/pull/868#issuecomment-673708142

yea, unsafe is unavoidable with the extern.


Correcting the terraform apply retry logic

#1354
kubetest2-plugin failed to rerun the tf when tf apply failed first time for the following reason:
For loop that does the retry has a break command to stop the iteration when tf apply is successful.
This break of loop is happening at the first iteration itself (irrespective of tf apply being successful or not) and thus the flow is exiting the For loop and there by having no retry.
Hence placed the print of tf state and break command in else block so that it occurs only when there is tf apply success i.e when err= nil for tf apply.
+               } else {
+                       fmt.Printf("terraform state at: %s\n", path)
+                       break
                }
-               fmt.Printf("terraform state at: %s\n", path)
-               break
        }

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Rajalakshmi-Girish
To complete the pull request process, please assign mkumatag after the PR has been reviewed.
You can assign the PR to them by writing /assign @mkumatag in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/cc @mkumatag

/lgtm
/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mkumatag, Rajalakshmi-Girish
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [mkumatag]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Tried the usual stuff But clicking on tweets still sends it to a person's profile

For 2 days everytime i click on a person's tweet it sends me back to their profile and it's very annoying i've tried most things like logging off and back on /cleaning up search history/removing cookies/restarting computer but it still stays like this sometimes i am able to click on a person's tweet without the thing but when i go to their profile or my own it does the thing again and my google chrome is up to date Does anyone know what to do? if not i really hope this issue will be fixed

Try the goodtwitter beta https://chrome.google.com/webstore/detail/goodtwitter-beta/ehjbcokpmfbmpjlldihlcbkoakikcomd


fix(jest-circus): explicit require('detox') should not fail

[x] This is a small change

Description:
This is a common use case, when users explicitly destructure our facade:
const { device, expect, /* ... so on ... */ } = require('detox');

It appears that our demo-react-native-jest example project had no e2eExplicitRequire checks, and a bug slipped into production:

The new DetoxCircusEnvironment relies on the existence of global.detox variable, to prevent creating new and new Detox facade instances every time the require sandbox is reset by Jest for every next test file.
https://github.com/wix/Detox/blob/53d46b9a31d88f224b6593d89800cdf96e6485b6/detox/src/index.js#L1-L3
That's why this PR:

Fixes the issue by setting detox global variable after environment setup, like it was planned initially in #2009. It simply was never set, or more precisely it got lost after a few implementation rewrites. :man_shrugging:
Adds CI checks to never let this bug slip in again.

Pull Request Test Coverage Report for Build 2307

0 of 0   changed or added relevant lines in 0 files are covered.
1673 unchanged lines in 84 files lost coverage.
Overall coverage decreased (-10.7%) to 62.702%

Files with Coverage Reduction
New Missed Lines
%

detox/src/artifacts/log/ios/SimulatorLogPlugin.js
1
73.58%

detox/src/configuration/composeSessionConfig.js
1
86.36%

detox/src/devices/DeviceRegistry.js
1
91.46%

detox/src/devices/DriverRegistry.js
1
79.55%

detox/src/devices/drivers/android/tools/AppInstallHelper.js
1
96.08%

detox/src/invoke.js
1
96.0%

detox/src/utils/customConsoleLogger.js
1
88.24%

detox/src/utils/encoding.js
1
69.23%

detox/src/utils/fsext.js
1
91.67%

detox/src/artifacts/templates/artifact/FileArtifact.js
2
79.29%

Totals

Change from base Build 1232:
-10.7%

Covered Lines:
7846

Relevant Lines:
13044

💛  - Coveralls


Bump glocaltokens to 0.6.3 and adding google-api-python-client dep

Bumps glocaltokens to 0.6.3 (that fixes the dependency issues)
and add google-api-python-client dep.
@KapJI, maybe you have some good thoughts about it. SInce latest HA is using pip v22.0 which has it's revolver changed we have dep issues (that's the reason why glocaltokens was failing to install to HA). However now that glocaltokens got fixed during the integration installation I have got an unexpected error that google dependency is missing:

With the same UI error message Configuration flow could not be loaded: [Object Object] as in https://github.com/leikoilja/ha-google-home/issues/467
A quick search has led me to this, so adding a new dependency google-api-python-client does indeed fix the issue. Could that be right? I don't see how it's fighting together. Or maybe we should move this google-api-python-client dependency to glocaltokens instead?
Closes https://github.com/leikoilja/ha-google-home/issues/467
Closes https://github.com/leikoilja/ha-google-home/issues/470

Tested the changes with 2022.3.b1 and it resolved the issues successfully.

Fixed and released in v1.9.8


Problem: Impossible to keep tests for different extensions in the same directory

At the moment, pg_yregress expects to find tests in the tests folder. We also scan the test folder only once when looking for tests. This makes it impossible to have tests for different extensions in the same tests folder since we end up using the same setup script for both extensions.
Proposed Solution
During scanning, we set a "cache"/global property to mark the directory as "scanned" https://github.com/omnigres/omnigres/blob/761446d11ccd775f32ab7026c4ac4b9041b60ecb/cmake/PostgreSQLExtension.cmake#L128
We can extend this cache key to include the extension name:
set_property(GLOBAL PROPERTY "find_pg_yregress_tests:${dir}:${NAME}" "CALLED")

I think you're onto something here. Perhaps we can make it similar to what we're doing with migrations, where for multi-extension directory, the convention is to put them into migrate/name/... as opposed to migrate/... with both methods supported?
So, similarly we would make every test suite scan in tests/ and tests/${NAME} and in most (all?) cases we won't put any tests right into tests/ for this case.
And yes, this would probably be best paired with your suggested extension of the format of the property.

Created a PR at #382.

So, similarly we would make every test suite scan in tests/ and tests/${NAME} and in most (all?) cases we won't put any tests right into tests/ for this case.

Cool, I think considering that we're only seeing multi-extension tests with omni_ext at the moment, we can keep scanning tests (instead of moving all the test files into the corresponding extension name).


Dev

bootstrap-styled
Thank you for contributing! Please take a moment to review our contributing guidelines
to make the process easy and effective for everyone involved.
Please open an issue before embarking on any significant pull request, especially those that
add a new library or change existing tests, otherwise you risk spending a lot of time working
on something that might not end up being merged into the project.

[x] Code is well-commented, linted and follows project conventions
[x] Documentation is updated (if necessary)
[x] Description explains the issue/use-case resolved and auto-closes related issues

Be kind to code reviewers, please try to keep pull requests as small and focused as possible :)
IMPORTANT: By submitting a patch, you agree to allow the project
owners to license your work under the terms of the  License.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update font-kayases to latest

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Merged as d7166b29e63746b3227548f1ec8a41c2d96898d9.


hibernate sequences table is broken for app db (since 17.0)

[Version]
17.0 2017/05/11
[How to reproduce]

install 17.0
work with app by creating subscriptions to provisioning services e.g. aws/openstack

[Expected result]
hibernate sequences are generated correctly, no duplicate key problems
[Observed result]
duplicate key errors occur, no more operations possible in APP
[Details]
Before upgrade to 17.0, app hibernate_sequence table values:
ServiceInstance	86
InstanceAttribute	18
InstanceParameter	87
Operation	64
After working with 17.0, app hibernate_sequence table values:
ServiceInstance	2086
InstanceAttribute	2018
InstanceParameter	2087
Operation	64
My guess is that the incorrect value hibernate_sequence sequence_next_hi_value is stored.
In my case I added 2 subscriptions (aws) and got two new (bad) values for tkey values for serviceinstance
See attached file.
(Note: bes db is ok, hibernate_sequence table values for sequence_next_hi_value  are between 10 and 197)

The id generator was changed from:
@SequenceGenerator(name = "do_seq", allocationSize = 1000)
to
@TableGenerator(table = "hibernate_sequences", name = "do_seq", allocationSize = 1000, valueColumnName = "sequence_next_hi_value").
@DawidCh do you know the reason?

Yes, it had to be changed because it didn't work properly. I can't remember the details now.

@StavrevaS @DawidCh This bug is blocking me from testing with my DB. Please take care of it asap.

I found there is a slight difference of persistence.xml hibernate configuration between  OSCM core and APP. Especially, I am concerned about the following property missing for APP persistence.xml.

Note that the default is true here.
Check also https://docs.jboss.org/author/display/WFLY8/JPA+Reference+Guide#JPAReferenceGuide-Hibernateproperties
"New applications should let this default to true, older applications with existing data might need to set to false (see note below).  It really depends on whether your application uses the @GeneratedValue(AUTO) which will generates new key values for newly created entities.  The application can override this value (in the persistence.xml)."
Maybe related?

The issue is fixed by adding the mentioned property. Verification tests are in progress.

As agreed, we will provide a hot fix release for this issue.
@gertipoppel
The fix requires an update to the version numbers in the manuals - 17.0.1 and a short note about this issue in the release notes.

[Details of fix]
Added property for app, which is mandatory to glassfish4 to get number generators to work properly:
hibernate.id.new_generator_mappings
The property has been set to bes domain but forgotten to set to app.

Added the following to the Release Notes of V17.0.1 (What's New --> GlassFish 4.1.1 Application Server --> Update Installation of APP and/or Service Controllers):
GlassFish 4 requires a change to its default configuration so that numbers are generated correctly
(needed, for example, for the IDs of the search index). In the persistence.xml file, the following
property must be set to false instead of the default true:

Adjusted the version number of the manuals to 17.0.1

Verified with 17.1


Briefly describe major objects by providing str() functions

I'm a newbie to stix, just trying to parse a stix file I ran across.  It would be much easier to explore the file, the format and the API if the objects would describe themselves when I print them, rather than just getting something like <stix.indicator.indicator.Indicator at 0x7f80481c0050>
Perhaps the output could look something like these:
Malicious FQDN Indicator: example.com
Malicious IPv4 Indicator (IP Watchlist in Netherlands): <IP_ADDRESS>

Add types and/or ids if they seem useful enough.
Providing a summary description of a whole package, e.g. via some sort of package.summary() function that summarizes the numbers of different types of objects or something like that, would also be handy.

Thanks, @nealmcb . That's a great suggestion.
Unfortunately, we don't have a lot of time to put into this library; we are instead focusing on Python libraries for STIX 2.
I would be happy to accept a PR with these changes if you (or anyone else) has the time and interest to work on them, though.


fixed some links

fixed link to session-1.md
fixed link to lesson 8 readme

I see my fixed link to session-1 is already deprecated...


rename a misnamed method in Azure.ResourceManager.Network

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.Network


Compile with nacl-clang

So far we've been using nacl-gcc, but there is some documentation about using nacl-clang to compile executables. Unfortunately all the documentation is for pnacl, which doesn't use libc. Despite this, I think it may be possible to compile nexes with nacl-clang and include nacl-libc as a shared library. This would be useful for two separate problems.

We've been having some problems on the iPC project because the compiled user code is slow. If we can get any gains here using clang over nacl that would be incredible.

For the library isolation project, we've seen some paper that use LLVM-IR code to analyze memory placement for libraries. If we have a working nacl-clang/nacl-llvm we could possibly apply these strategies to this project as well.

@kuzeyardabulut has been working on getting nacl-clang to work and has made some progress, but is stuck getting libc to be loaded as a shared library. He's going to attach some more details to this issue.

Hello,
I've prepared a Google document addressing this issue. You can access it through the provided link.

@moyix Kuzey has updated the document at the above link to be a bit clearer about where we are in this process. It looks like we've come pretty far but its still erroring when we try to compile as an executable.
If you have any thoughts we'd love to hear them.

From speaking a bit with @moyix  about this, he had a nice idea to try and break this down and isolate the linker stage more.
@kuzeyardabulut let's try to see if we can compile to asm with nacl-clang, but do the linking stage with nacl-gcc. Since we know we can make asm with nacl-clang, and know we can link with nacl-gcc this may be a workaround.

Finally, we successfully compiled the object files with nacl-clang and linked them using nacl-gcc to obtain a dynamically linked .nexe file, thereby gaining access to LLVM Intermediate Representation (IR).

You can compile your own .c files like this:
[root@6717f1c8e245 ~]# /nacl_sdk/pepper_49/toolchain/linux_pnacl/bin/x86_64-nacl-clang -target "x86_64-nacl" hello_world.c -o hello-libc.o -c
[root@6717f1c8e245 ~]# /nacl_sdk/pepper_49/toolchain/linux_x86_glibc/bin/x86_64-nacl-gcc hello-libc.o -o kk.nexe
[root@6717f1c8e245 ~]# cd /nacl_sdk/pepper_49/tools/
[root@6717f1c8e245 tools]#  python2.7 sel_ldr.py ~/kk.nexe
('CMD:', ['/nacl_sdk/pepper_49/tools/nacl_helper_bootstrap_x86_64', '/nacl_sdk/pepper_49/tools/sel_ldr_x86_64', '--r_debug=0xXXXXXXXXXXXXXXXX', '--reserved_at_zero=0xXXXXXXXXXXXXXXXX', '-q', '-a', '-B', '/nacl_sdk/pepper_49/tools/irt_core_x86_64.nexe', '/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/x86_64-nacl/lib/runnable-ld.so', '--library-path', '/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/x86_64-nacl/usr/lib:/nacl_sdk/pepper_49/lib/glibc_x86_64/Release:/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/x86_64-nacl/lib', '/root/kk.nexe'])
['/nacl_sdk/pepper_49/tools/nacl_helper_bootstrap_x86_64', '/nacl_sdk/pepper_49/tools/sel_ldr_x86_64', '--r_debug=0xXXXXXXXXXXXXXXXX', '--reserved_at_zero=0xXXXXXXXXXXXXXXXX', '-q', '-a', '-B', '/nacl_sdk/pepper_49/tools/irt_core_x86_64.nexe', '/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/x86_64-nacl/lib/runnable-ld.so', '--library-path', '/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/x86_64-nacl/usr/lib:/nacl_sdk/pepper_49/lib/glibc_x86_64/Release:/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/x86_64-nacl/lib', '/root/kk.nexe']
Hello, World!
['/nacl_sdk/pepper_49/tools/nacl_helper_bootstrap_x86_64', '/nacl_sdk/pepper_49/tools/sel_ldr_x86_64', '--r_debug=0xXXXXXXXXXXXXXXXX', '--reserved_at_zero=0xXXXXXXXXXXXXXXXX', '-q', '-a', '-B', '/nacl_sdk/pepper_49/tools/irt_core_x86_64.nexe', '/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/x86_64-nacl/lib/runnable-ld.so', '--library-path', '/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/x86_64-nacl/usr/lib:/nacl_sdk/pepper_49/lib/glibc_x86_64/Release:/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/x86_64-nacl/lib', '/root/kk.nexe']
Hello, World!
['/nacl_sdk/pepper_49/tools/nacl_helper_bootstrap_x86_64', '/nacl_sdk/pepper_49/tools/sel_ldr_x86_64', '--r_debug=0xXXXXXXXXXXXXXXXX', '--reserved_at_zero=0xXXXXXXXXXXXXXXXX', '-q', '-a', '-B', '/nacl_sdk/pepper_49/tools/irt_core_x86_64.nexe', '/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/x86_64-nacl/lib/runnable-ld.so', '--library-path', '/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/x86_64-nacl/usr/lib:/nacl_sdk/pepper_49/lib/glibc_x86_64/Release:/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/x86_64-nacl/lib', '/root/kk.nexe']
Hello, World!
['/nacl_sdk/pepper_49/tools/nacl_helper_bootstrap_x86_64', '/nacl_sdk/pepper_49/tools/sel_ldr_x86_64', '--r_debug=0xXXXXXXXXXXXXXXXX', '--reserved_at_zero=0xXXXXXXXXXXXXXXXX', '-q', '-a', '-B', '/nacl_sdk/pepper_49/tools/irt_core_x86_64.nexe', '/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/x86_64-nacl/lib/runnable-ld.so', '--library-path', '/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/x86_64-nacl/usr/lib:/nacl_sdk/pepper_49/lib/glibc_x86_64/Release:/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/x86_64-nacl/lib', '/root/kk.nexe']
Hello, World!
['/nacl_sdk/pepper_49/tools/nacl_helper_bootstrap_x86_64', '/nacl_sdk/pepper_49/tools/sel_ldr_x86_64', '--r_debug=0xXXXXXXXXXXXXXXXX', '--reserved_at_zero=0xXXXXXXXXXXXXXXXX', '-q', '-a', '-B', '/nacl_sdk/pepper_49/tools/irt_core_x86_64.nexe', '/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/x86_64-nacl/lib/runnable-ld.so', '--library-path', '/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/x86_64-nacl/usr/lib:/nacl_sdk/pepper_49/lib/glibc_x86_64/Release:/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/x86_64-nacl/lib', '/root/kk.nexe']
Hello, World!
0.0137880325317

We are now trying to cross compile the application "grep", here are the breakdown steps:

export CC="/nacl_sdk/pepper_49/toolchain/linux_pnacl/bin/x86_64-nacl-clang -target x86_64-nacl -fPIC"
export CXX="/nacl_sdk/pepper_49/toolchain/linux_pnacl/bin/x86_64-nacl-clang++ -target x86_64-nacl -fPIC"
Using x86_64-nacl-clang to compile source code and obtain object file.
export LD="/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/bin/x86_64-nacl-gcc"
export CCLD="/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/bin/x86_64-nacl-gcc"
Linking object files with x86_64-nacl-gcc
Above steps will generate "undefined reference" error, such as:
/home/lind/lind_project/tests/applications/grep/lib/chdir-long.c:126: undefined reference to __assert_func' /home/lind/lind_project/tests/applications/grep/lib/chdir-long.c:145: undefined reference to __errno'
/home/lind/lind_project/tests/applications/grep/src/grep.c:393: undefined reference to _impure_ptr' grep.o: In function fwrite_errno':
searchutils.o: In function kwsinit': /home/lind/lind_project/tests/applications/grep/src/searchutils.c:48: undefined reference to __locale_mb_cur_max'
/home/lind/lind_project/tests/applications/grep/src/searchutils.c:51: undefined reference to __locale_mb_cur_max' /home/lind/lind_project/tests/applications/grep/src/searchutils.c:53: undefined reference to ctype_ptr'
collect2: ld returned 1 exit status
make: *** [Makefile:1307: grep] Error 1
I have diagnosed that the error is due to clang and gcc generate different symbols, take grep.o as an example, clang generate "errno" as "__errno" in object file, but gcc generate "errno" as "__errno_location" in object file

In general, the problem is gcc cannot recognize some symbols in object file that generated by clang compiler. And the current solution I am using is replacing some object files (grep.o and searchutils.o) with gcc version, and the rest 4 object files (.o), which are dfasearch.o, kwsearch.o, kwset.o, pcresearch.o using clang version. And then linking with x86_64-nacl-gcc. Please share any advice or opinions you have regarding the above approach. Thank you!

@moyix any ideas here ^
Im guessing that compiling objects with clang is adding the wrong symbols for libc? I'm not sure what we would need to add to alleviate that

Hmm, I don't feel like that's exactly the issue – the object file format is independent of the compiler and the naming is standardized. So if there are different names being generated by the two compilers, it's (at some level) a difference in names in the source code.
However, that might not be something obvious. For example, clang and gcc might have different search paths for the system header files, and so compiling with one could be pulling in a different definition of errno than when compiling with the other.
For errno specifically:
The __errno variant seems to be the version used by newlib:
https://github.com/eblot/newlib/blob/master/newlib/libc/include/sys/errno.h#L13C1-L16C7
Whereas glibc uses __errno_location:
https://github.com/bminor/glibc/blob/master/stdlib/errno.h#L36-L38
So at a guess, nacl-gcc is trying to use glibc headers, and nacl-clang is trying to use newlib headers.

By changing the include path of x86_64-nacl-clang, we are now able to compile "grep" with clang, and link with gcc:
export CC="/nacl_sdk/pepper_49/toolchain/linux_pnacl/bin/x86_64-nacl-clang -target x86_64-nacl \
-I/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/bin/../lib/gcc/x86_64-nacl/4.4.3/include \
-I/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/bin/../lib/gcc/x86_64-nacl/4.4.3/include-fixed \
-I/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/bin/../lib/gcc/x86_64-nacl/4.4.3/../../../../x86_64-nacl/include"
export CFLAGS='-DO_BINARY=0 -DO_SEARCH=0 -DO_TEXT=0 -DS_TYPEISTMO\(p\)=0 -g -fno-pie'

But we still need to manually define some Macros and change variables name, due to the compiler's difference. To make it easier, I used "sed" as shown below:
sed -i 's/gettimeofday (struct timeval \*restrict tv, void \*restrict tz)/gettimeofday (struct timeval *__restrict tv, struct timezone *__restrict tz)/g' ./lib/gettimeofday.c
sed -i 's/static void _GL_ATTRIBUTE_FORMAT_PRINTF (3, 0) _GL_ARG_NONNULL ((3))/\/\/ &/' ./lib/error.c
sed -i '1i typedef size_t __re_size_t;' ./lib/regex_internal.h
sed -i 's/_Restrict_/restrict/g' ./lib/regcomp.c
sed -i 's/_Restrict_/restrict/g' ./lib/regexec.c
sed -i '1i\
#ifndef _GL_ATTRIBUTE_FORMAT_PRINTF\n\
#define _GL_ATTRIBUTE_FORMAT_PRINTF(x,y)\n\
#endif\n' ./src/grep.c
sed -i 's|CCLD = $(CC)|CCLD="/nacl_sdk/pepper_49/toolchain/linux_x86_glibc/bin/x86_64-nacl-gcc"|' ./src/Makefile.in

It seems like we're able to do this. I'm not sure when we'll need to use this in the near future but we should save all the information on how to compile programs with clang in one place so we don't lose it. @yzhang71 can you do that? Otherwise this issue can be closed.

Yes, this issue can be closed. I have documented the compilation process.


Please do not use the "spring" namespace for configuration keys

As requested in our developer guide please do not use our namespace for configuration keys.

Done


publish_message throws Unable to identify task type because key was not found in the mesasge header: ''

I am using Django 2.1 and django-carrot 14.2 (latest available in PyPi). I have based my code on the instructions in the docs.
def my_task(**kwargs):
    return 'hello world'

publish_message(my_task, hello=True)

The task is correctly identified and pushed to Rabbit MQ, but I get the following error in monitor:
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/carrot/consumer.py", line 300, in on_message
task_type = self.get_task_type(properties.headers, body)
File "/usr/local/lib/python3.6/site-packages/carrot/consumer.py", line 117, in get_task_type
return properties[self.serializer.type_header]
KeyError: ''

I have been digging in the code a bit, and it looks like there might be a discrepancy in how the type_header is called in the two message serializers. I have not validated this by pulling this repo and trying to debug, but I believe DefaultMessageSerializer is meant to override the BaseMessageSerializer https://github.com/chris104957/django-carrot/blob/35ec132ec07d4600035e2008c0d2db0e77335cc1/carrot/objects.py#L196 but for some reason that is not happening. It might be a discrepancy between calling variables with self and without in BaseMessageSerializer get_task:
class BaseMessageSerializer(object):
    """
    A class that defines how to convert a RabbitMQ message into an executable python function from your Django project,
    and back again
    :param Message message: the RabbitMQ message
    """
    content_type = 'application/json'
    type_header, message_type = ('',) * 2
    task_get_attempts = 20

    def get_task(self, properties: pika.BasicProperties, body: bytes) -> Callable:
        """
        Identifies the python function to be executed from the content of the RabbitMQ message. By default, Carrot
        returns the value of the self.type_header header in the properties.
        Once this string has been found, carrot uses importlib to return a callable python function.
        """
        mod = '.'.join(properties.headers[self.type_header].split('.')[:-1])
        task = properties.headers[self.type_header].split('.')[-1]
        module = importlib.import_module(mod)
        func = getattr(module, task)
return func

This is mostly a guess and I have not validated it. I have not found anything listing this error in closed issues or in the documentation. It seems a lot of files got reset recently, so the history on github is also not very helpful. Any pointers would be greatly appreciated, I quite like the simplicity of this project and would love to use it!

Can reproduce - will investigate

So the problem was actually in carrot.consumer, this bit:
class Consumer(threading.Thread):
    """... """
    serializer: Type[BaseMessageSerializer] = BaseMessageSerializer

The BaseMessageSerializer is not actually meant to be used like this, just extended. This issue got introduced when we added mypy and type checking. It's now been changed to this:
class Consumer(threading.Thread):
    """... """
    serializer: Type[BaseMessageSerializer] = DefaultMessageSerializer

This fix has been made on a dev release, 1.4.3a1. Can you install it (using the below command) and let me know if this fixes it?
pip install django-carrot==1.4.3a1 --no-cache

I'll remove the dev flags from this version number if it works

That looks to be the thing, many thanks for looking into it so quickly!
On Tue, Mar 26, 2019 at 11:22 AM Christopher Davies <
<EMAIL_ADDRESS>wrote:

So the problem was actually in carrot.consumer, this bit:
class Consumer(threading.Thread):
"""... """
serializer: Type[BaseMessageSerializer] = BaseMessageSerializer
The BaseMessageSerializer is not actually meant to be used like this,
just extended. This issue got introduced when we added mypy and type
checking. It's now been changed to this:
class Consumer(threading.Thread):
"""... """
serializer: Type[BaseMessageSerializer] = DefaultMessageSerializer
This fix has been made on a dev release, 1.4.3a1. Can you install it
(using the below command) and let me know if this fixes it?
pip install django-carrot==1.4.3a1 --no-cache
I'll remove the dev flags from this version number if it works
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/chris104957/django-carrot/issues/106#issuecomment-476583437,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEuK98ZeQ_ejqLM1cOSx1mIlSZq5-s_lks5vagLlgaJpZM4cGaBJ
.


feat(dashboard-table): Improve dashboard table from overview page

Description
Overview table is improve by adding more info.

License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

closed by #4015


Ret val

Change return value style of some methods to simplify code and improve readability and performance. Also add return value to worldBackup for error handling.

Thanks for the patches.  I'll go ahead and accept these patches, but I would have preferred that patch 305ab21a805b8a397691748cdc447d9eadd0cfae was merged into<PHONE_NUMBER>53aba70807b86256c2526ee395202f to avoid the needless code churn.


Fix broken flamegraph interaction with egui 0.27.1

Checklist

[x] I have read the Contributor Guide
[x] I have read and agree to the Code of Conduct
[x] I have added a description of my changes and why I'd like them included in the section below

Description of Changes
This PR cancels the revert (#208) of egui 0.27.1 update (#201) and fix the flamegraph interaction bug it introduced whenever the flamegraph's scroll area was active.
Related Issues

Closes https://github.com/EmbarkStudios/puffin/pull/207

I've tested this on Windows and MacOs, in neither case the issues described in #205 are solved.

I guess I misread the comment… well, this fixed all the problems I could find

I guess I misread the comment… well, this fixed all the problems I could find

My bad, I should've phrased it better. I'll see what I can find!

I don't know how this was tested but I can only echo what @tosti007 said that the flamegraph selection still has issues for me when scrolling even after this was merged. I think I have located the source of the issue and tried to describe relevant parts here #219


Feat: Add auto comment to enhance user collabration

Describe the feature
implementing an auto-comment feature would greatly enhance collaboration and communication within the project. This feature would automatically generate comments in response to specific events, such as when an issue is opened, a pull request is created, an issue is assigned, or an issue is unassigned.
Feature Details:
When an issue is opened, the auto-comment should greet the author and provide a brief acknowledgement and request for additional context.
When a pull request is opened, the auto-comment should greet the author, express gratitude, and remind them to follow the project's contributing guidelines.
When an issue is closed, the auto-comment should thank the author for their contribution and encourage further engagement.
When an issue is assigned to someone, the auto-comment should notify the assignee and encourage them to start working on it.
When an issue is unassigned from someone, the auto-comment should notify the assignee about the change and suggest reassignment if they are offline.
Add ScreenShots
Assign this issue to me under GSSOC'23
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'23 contributor
[X] I want to work on this issue

Not needed


Add API documentation via yuidoc

add ember-cli-yuidoc and yuidoc-ember-theme as dependencies
fix documentation in classes

TODO before next release (not in this PR)

improve travis build so gh-pages branch is automatically updated
add link to docs in dummy app

/cc @jgwhite

👍


Update connectivity-settings.md

It is either "any existing private endpoints" or "an existing private endpoint".

@sidesw1pe : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good; merging.


Tesseract not able to recognize sentences

My bot is running fine but it detects wrong sentences.

try to adjust coordinates in screen_grab()

I adjusted the coordinates and they are alright

Then maybe the text is too small

I was trying to use this bot on Loco Trivia
Can you suggest me something other loco trivia

Use this app for loco and other quiz https://play.google.com/store/apps/details?id=com.tanuj.android.hackslash.hackquiz

Can you suggest me some another that works without OCR

i don't think its possible to do it without OCR

https://github.com/Exaphis/HackQ-Trivia
Tanuj refer to this
This HQ Trivia bot work without ocr
But I want one for Loco

Have you tried it? Does it work?

No I haven't tried it but people gave 17 stars to this project

It requires USERID and BEARER token, to call their API

Yaa they are providing free on user id and bearer token
Can't be this like bot used for loco

depends on their implementation

If I use loco trivia user id and bearer token will that work

haha NO

Can you make that type of bot for Loco Trivia?

@tanujyadav97  please can you such bot for loco trivia

@bertu159 check the captured image and change the coordinates accordingly


Allow opting out of returning focus on close

Summary:
I use react-modal to display a search box with autocompletion. When I find a suitable option and hits enter key, I'm navigated to corresponding view, and the modal should be closed. Unfortunately, button that opens the modal gets re-focused, and a click event is fired on it (because that's how enter key works with buttons), so the modal gets open again.
It helps if I add some closeTimeoutMS, but then it starts depending on how long do I hold the key. So I'd prefer just to opt out of refocusing in such cases.
Link to example of issue:
https://codesandbox.io/s/kZmzPBLGX

Is this resolved? @Hypnosphi @diasbruno
https://github.com/storybooks/storybook/blob/7b996460cab90d1af953e20f10fe1236baf850ba/lib/ui/src/modules/ui/components/search_box.js#L73

@ndelangen Not yet. Perhaps we are giving back the focus to earlier and some event is firing. Also, I can reproduce this issue on Chrome - Safari and Firefox are working ok.
Maybe It's related to #494.

Released v3.1.0 with an option to avoid the 'return focus on close'.

Still not completely fixed, see https://github.com/reactjs/react-modal/pull/540/files#r148984350


Update Gradle version to 4.2.1

update and support new dependencies command implementation and api

Thanks for this pull request @Werb
Can you please join our contributors community by signing JFrog's CLA so that we can merge your code?

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


When using for in, check hasProperty

Change where for (var in obj) { is used to ensure that the obj is checked that it has a property of var first.

Coverage increased (+0.07%) to 91.53% when pulling 1474d0108293d5f3dbb369cc1477782fbbbcd37e on nick/ensure-has-property into 126dbedd32d585051fe446721c98ad17e6421679 on master.


Do not destroy if the world did not init

Fixes
2024-10-28 17:20:47,425 - root - INFO - Estimating memory usage...
2024-10-28 17:20:47,426 - root - INFO - Tensor parallelism and pipeline parallelism are not supported yet.
Traceback (most recent call last):
  File "/home/ubuntu/carlos/torchtitan/estimation.py", line 219, in <module>
    torch.distributed.destroy_process_group()
  File "/home/ubuntu/.pyenv/versions/titan/lib/python3.10/site-packages/torch/distributed/distributed_c10d.py", line 2014, in destroy_process_group
    assert pg is not None
AssertionError

thanks for the fix!


Add disk tests

Addresses #7

Pull Request Test Coverage Report for Build 27

33 of 37 (89.19%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+15.0%) to 41.379%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/metrics/aggreagtor.rs
0
2
0.0%

src/metrics/mod.rs
0
2
0.0%

Totals

Change from base Build 25:
15.0%

Covered Lines:
192

Relevant Lines:
464

💛  - Coveralls


Classes with generic mixins applied to base do not highlight correctly

Consider this file:
interface C {}
class B<T, U> {}

function F(s: any) { return class G<T, U> extends s {} }

export class A extends F(B)<D, E> implements C {}

export class A extends B<D, E> implements C {}

Expected: both instances of the word implements highlight as modifier keywords
Actual: only the second instance highlights properly

debug info with package info
{
  "atom": "1.54.0",
  "platform": "darwin",
  "release": "18.7.0",
  "activeCommunityPackages": [
    "dracula-syntax: 3.0.2",
    "framer-ui: 2.0.0",
    "api-docs: 0.0.6",
    "atom-ide-debugger-node: 0.7.3",
    "atom-ide-debugger-python: 0.7.3",
    "atom-ide-javascript: 1.5.0",
    "atom-import-cost: 1.2.0",
    "atom-inline-blame: 0.0.10",
    "atom-jq: 0.7.0",
    "atom-typescript: 14.1.2",
    "audio: 1.5.7",
    "autocomplete-module-import: 0.3.0",
    "autocomplete-paths: 2.12.18",
    "busy-signal: 2.0.1",
    "choose-pane: 0.8.0",
    "color-picker: 2.3.0",
    "counter: 0.3.5",
    "custom-title: 1.0.1",
    "docblockr: 0.13.7",
    "emmet: 2.4.3",
    "file-icons: 2.1.46",
    "gitlab-integration: 0.4.8",
    "haskell-debug: 0.3.6",
    "haskell-pointfree: 0.2.0",
    "highlight-column: 0.5.4",
    "highlight-line: 0.12.0",
    "highlight-selected: 0.17.0",
    "ide-bash: 1.0.11",
    "ide-cpp: 0.1.0",
    "ide-haskell-hoogle: 0.1.2",
    "ide-html: 0.6.2",
    "ide-json: 0.2.1",
    "indent-guide-improved: 1.4.13",
    "intentions-colorpicker: 1.0.1",
    "intentions-numbers: 1.0.4",
    "javascript-drag-import: 0.1.13",
    "language-haskell-scoped: 0.1.2",
    "less-than-slash: 0.20.0",
    "linter-coverage: 0.3.0",
    "linter-docker: 0.3.2",
    "linter-eslint: 8.5.5",
    "linter-jsonlint: 1.4.0",
    "linter-pylint: 2.1.1",
    "linter-sass-lint: 1.9.0",
    "linter-stylelint: 4.5.1",
    "linter-write-good: 0.9.3",
    "minimap-split-diff: 0.3.7",
    "modular-snippets: 0.1.3",
    "npm-outdated: 0.6.0",
    "pane-browser: 1.6.0",
    "pigments: 0.40.6",
    "plantuml-viewer: 0.7.2",
    "regex-railroad-diagram: 0.19.4",
    "relative-numbers: 0.9.1",
    "remember-folds: 0.3.0",
    "split-diff: 1.6.1",
    "teletype: 0.13.4",
    "terminal-tab: 0.6.0",
    "todo-show: 2.3.2",
    "tree-ignore: 0.6.2",
    "vim-mode-plus: 1.36.4",
    "vim-mode-plus-keymaps-for-surround: 0.2.1",
    "language-graphql: 1.0.0",
    "language-plantuml: 0.2.0",
    "language-markdown: 0.37.0",
    "language-github-actions: 0.1.0",
    "language-fish-shell: 1.1.0",
    "language-haml: 0.32.1",
    "language-ini: 1.23.0",
    "language-haskell: 1.21.0",
    "language-liquid: 0.7.0",
    "language-mermaid: 0.6.0",
    "language-nunjucks: 4.2.1",
    "language-patch: 1.2.0",
    "language-confluence-wiki: 0.2.0",
    "language-vue: 0.26.0",
    "react: 0.18.0",
    "atom-beautify: 0.33.4",
    "atom-ide-base: 2.3.2",
    "atom-ide-datatip: 0.23.2",
    "atom-ide-definitions: 0.4.1",
    "atom-ide-hyperclick: 1.0.9",
    "atom-ide-markdown-service: 2.0.0",
    "atom-ide-outline: 1.17.0",
    "atom-ide-signature-help: 0.15.1",
    "linter: 3.3.0",
    "linter-ui-default: 3.2.3",
    "minimap: 4.39.7",
    "minimap-find-and-replace: 5.0.8",
    "minimap-git-diff: 4.3.6",
    "minimap-linter: 2.2.2"
  ]
}

Edit: having submitted this issue I'm now noticing that GitHub's highlighter appears to have the same issue, so maybe it's upstream. However note VSCode's rendering:

@bennyp#9878  I think you opened the issue in the wrong repository
This is a syntax highlighting issue and it should be opened here:
https://github.com/atom/language-typescript


Migrate to common Governor

Streamloader also uses the Governor and is being update with new functionality. G2Loader should use the same Governor to benefit from this and future changes are encapsulated in one code base.

The common Governor is at https://github.com/Senzing/governor-postgresql-transaction-id


Fix parentheses warnings for Elixir 1.4

Elixir 1.4 gives warnings like the following:
warning: variable "driver" does not exist and is being expanded to "driver()",
please use parentheses to remove the ambiguity or change the variable name
  lib/wallaby.ex:25

Looks great :tada:


Node modules vendoring?

cf push logs out this warning:
         PRO TIP: It is recommended to vendor the application's Node.js dependencies
         Visit http://docs.cloudfoundry.org/buildpacks/node/index.html#vendoring

Yeah, I think you just need to run npm install before doing a cf push, so that the local copy of the node_modules are uploaded rather than the buildpack downloading the packages itself. (I think)


chore: add 'status: in triage' label to issue templates and docs

PR Checklist

[x] Addresses an existing open issue: fixes #5092
[x] That issue was marked as status: accepting prs
[x] Steps in CONTRIBUTING.md were taken

Overview
Mentions the newly added label and updates the contributing & maintenance guidelines for it.
Also trims down the maintenance guidelines a bit so that this doesn't net make them more wordy.

coverage: 94.335%. remained the same
when pulling 1b66258cf6091dbf52e4c1176de7533d93aa4369 on JoshuaKGoldberg:status-in-triage-label
into ba37586326bb6c6113e95ead615bf53326243b4e on mochajs:master.


What is the segmentation head of the model?

Hello, I'm trying to use the model to segment my custom data. But there seems only the classification head. Do you use the same seg_head as PTv2 or something else?

Sorry, I didn't get the question. Our default config is for semantic segmentation.

Sorry for the confusion. I mean when I set "cls_mode=False", the output is a Point whose feat is of shape (N, C) where C is 64 instead of num_classes like PTv1 and PTv2. I was wondering how to generate the semantic mask from this feature tensor

Hi, I move it here (https://github.com/Pointcept/Pointcept/blob/main/pointcept/models/default.py#L45)


Need style mixin

No mixing named --px-modal for styling.
Cannot set default width, and it does not allow you to place styles for buttons, headings, etc.

In v1.2.10 of the component, I've added style mixins so you can customize many aspects of the modal. The latest documentation describes which mixins are available.


Ngen roslyn bits

To improve the cold startup perf of website which uses DotNetCompilerPlatform, we need to do the following things in aspnet base image:

Download microsoft.net.compilers nupkg and NGen the relevant binaries
set environment variable ROSLYN_COMPILER_LOCATION

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

@shirhatti  @HongGit @mcy94w

@MichaelSimons Can you take a look?

What is the plan on releasing these changes?  Is there going to be a tag change?  I don't think this should be released this without a tag change.

@MichaelSimons found a way to do that. :)

LGTM


Update README.md

Correct some grammatical mistakes in Documentation.

Hello, most of these corrections are unnecessary, thank you


running-coreos: update cloud-config for etcd2

@crawford Snuck a network-online.target commit in here for ECS

LGTM

Please rebase to remove that merge commit.

:+1:


appcrash when attempting to run arangod.exe in Windows 7

I get an appcrash when attempting to install arangoDB in on a windows 7 machine. I have also tried the XCOPY version and have the same issue. The APPCRASH gives the following:
 Problem signature:
  Problem Event Name:   APPCRASH
  Application Name: arangod.exe
  Application Version:  <IP_ADDRESS>
  Application Timestamp:    59704d12
  Fault Module Name:    arangod.exe
  Fault Module Version: <IP_ADDRESS>
  Fault Module Timestamp:   59704d12
  Exception Code:   c000001d
  Exception Offset:<PHONE_NUMBER>200f77
  OS Version:   6.1.76<IP_ADDRESS>.256.1
  Locale ID:    2057
  Additional Information 1: caa2
  Additional Information 2: caa2bb545c0b7fee68e5ff27d1b7f78d
  Additional Information 3: 95f8
  Additional Information 4: 95f82d1cb337322ec0f22184a0acdc62

I do not believe it even attempts to access the arangod.conf file let alone object to something inside it. I used Windows debugger to try and get some additional clues but I'm left stumped The results are attached.
I have tried running it in safe mode with the same result. I have run chkdsk /f also (I have an ssd drive).
arangod-windbg.txt
I'm clutching here but must the disk with arango executable be separate to that running the OS ?

What kind of processor to you have? Intel or AMD?

Its an Intel processor. 64 bit Pentium dual core. I eventually resorted to Ubuntu.

We have released ArangoDB 3.2.1 today. This release potentially fixes the startup crash on Windows.
Can you give it a try and let us know if it is fixed now? Thanks!


Incorrect show some of smileys

Hi. I use emojionearea 2.1.4 with emojione 2.1.1 also with some changes....
I change smileys list is filters and add some other emoji codes from emoji one.
When i insert some (multiple emojies like multi person emojies or husbends) emojies like ( :family_man_girl_boy:  or :family_man_boy: ) and some other... these show correct in emoji list and also in emojionearea but when i get text from emoji area it convert to unicode and in another hand when show it these will explode and show like this => :woman: :man: :girl: :boy:
How can i fix it?

Sorry i fixed it.
For someone may have this question:
First set Options.shortnames = true and get area text then convert text from shortname to image by emojione.shortnameToImage(":family_mwgb:"); it fixed!


[3.0.1-prepare][cherry-pick][Bug] [Resource Center] Fix hdfs can only use local mode, not cluster mode #11823

Purpose of the pull request

this issue: #11821
this pr: #11823
Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

@SbloodyS Please help review, thanks.


homu-ify

@homunkulus r+

:pushpin: Commit 637afcd has been approved by japaric

:hourglass: Testing commit 637afcd with merge 637afcd...

:sunny: Test successful - status-travis
Approved by: japaric
Pushing 637afcddd8d2666adc12455bff1ef823a9675268 to master...


⚠ Bofrost.at has degraded performance

In 9dd3243, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2654 ms

Resolved: Bofrost.at performance has improved in bb929be.


Error in the test to check :experimental:

ERROR: files contain UI macros but the :experimental: tag not found in the following files:
rhel-8/assemblies/assembly_customizing-the-boot-menu.adoc
I see nothing there :X

@soulcharmer pushed the fix


Incompatible with latest HDT 1.22.3

Great addon. Any chance of a fix? :)
Hearthstone Quest Overlay 1.5.8 is not compatible with HDT 1.22.3.
Make sure you are using the latest version of the Plugin and HDT.
System.MissingMethodException: Method not found: 'HearthMirror.ProcessView HearthMirror.Mirror.get_View()'.
at action, Boolean clearCache)
at HSReflection.Reflection.GetQuests()
at QuestOverlayPlugin.Util.QuestDataUtil.UpdateQuestData(Boolean force)
at QuestOverlayPlugin.Overlay.QuestListViewModel.Update(Boolean force)
at QuestOverlayPlugin.Plugin.ShowBattlegroundsQuests()
at QuestOverl ayPl ug i n.Overlay.QuestListButton. < On Mouse Enter> .MoveNext()
End of stack trace from previous location where exception was thrown
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.< state)
at System.Windows.Threading.ExceptionWrapper.lnternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper,TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

kind of fixed, but the new way HSDT does value reading is quite heavy on the cpu, so I still have to fix that (and images)


main-maintainer change from t9md to jrajav

t9md/atom-lazy-motion#16

Published and done, closing (Main discussion in original repo issue linked above).

Thanks!

I want make my stance clear, I'm glad you give me credit original package on readme(as you add at footer of readme).
Other than that, you can remove/change any code, any comment, any documentation as you like.
Don't pay too much respect for the history of this package, please change it as you like!

@t9md Noted, thanks! It works pretty solidly already so the most I'd do is a few extra quality-of-life improvements like that one open issue for now.


w07d02 HW

Comfort: 3
Completeness: 3
Notes: Will need to run through code again to ensure working model.  Events and DOM is challenging.
Will run through this HW again.

Hey John, I'm marking this as complete, since it looks like you gave it a good shot, but definitely focus on solving smaller problems, one step at a time!
Let me know if you have any questions.


Add Babel Typecheck

https://github.com/codemix/babel-plugin-typecheck

Hi, I think is off topic. But
When using "piping" + "babel/register" in my project,
The dev server restart (for about 0.5 to 1 second) after every changes that we make.
I think that is because piping "hot" reloading and babel slow compilation?
Will this make the compilation even slower?

0.5 to 1 second is considered fast, for restarting node server-side :) "babel/register" allows us to write modern Javascript (ES5/6/7) and Babel Typecheck will allow static + runtime type checking, which prevents an entire class of bugs. So it's worth it. But you can turn it off.
Also, perhaps I should bring back the production build for the server, so Babel-transformations are pre-compiled for production.

@ericfong Do you think webpack hot-loading for the server (https://github.com/webpack/hot-node-example) would be a faster solution?

The problem of "piping" + "babel/register":
Step 1: file changed
2: restart
3: compile
4: finally can be used
If webpack way:
Step 1: file changed
2: compile
3: restart after compile (browser HMR is like that, not sure about server)
4: Can be used
Pros: faster?
Cons: stack trace is ... the friend of flux (fuXk)

I'll have to experiment with server-side HMR. Never done that before. If you have the time, a Pull Request is welcome :)

On-topic: I added Babel Typecheck plugin. It works quite well for regular functions et cetera but unfortunately doesn't support ES6 classes yet.


[WebUI] Add TextToSpeechComponent

Implements the "speak" button
Clicking the button triggers a call to the /tts route to retrieve the
audio waveform

This supports custom voices and flexible volume control

The base64-encoded audio waveform is then attached to the src
attribute of a hidden HTML audio element to enable audio playback
Error messages are displayed on the top-right corner of the UI
when error occur

@antonkast-google Please review. Thanks!