Real-time emotion tracking and analysis

Problem: In various settings such as online meetings, classrooms, or customer service interactions, understanding the emotional states of participants in real-time can be challenging but crucial for effective communication and engagement. Existing solutions often lack the ability to provide immediate feedback on emotional cues, hindering real-time adaptability and response.
Solution: Implement real-time emotion tracking and analysis as a unique feature in the Face-X Open Source Project. This feature would utilize a webcam or camera feed to continuously analyze facial expressions, providing immediate feedback on detected emotions. Visual overlays or notifications could indicate the emotions detected, accompanied by suggestions or prompts to adapt communication strategies accordingly. Additionally, the system could offer aggregate analysis over time, providing insights into emotional trends and patterns within a group or environment.
Alternatives: An alternative solution could involve manual input of emotions by users or observers, but this would be less efficient and prone to biases. Another alternative could be analyzing audio cues in addition to facial expressions, providing a more comprehensive understanding of emotional states.
Approach: The approach would involve integrating real-time facial recognition and emotion detection algorithms into the Face-X project. This would require leveraging computer vision and machine learning techniques to analyze live video streams, detect faces, and classify emotions in real-time. TensorFlow, OpenCV, and other libraries could be utilized for this purpose. User-friendly interfaces could be developed to visualize detected emotions and provide actionable insights to users.
Additional Context: Implementing real-time emotion tracking and analysis would not only enhance the Face-X project but also have applications in various domains, including education, healthcare, marketing, and entertainment. This feature would enable more empathetic and responsive interactions, ultimately improving user experiences and outcomes.

i would like to work on this issue
please assign me this issue under GSSOC 24

Go for it!!

Go for it!!

Thank you for assigning this feature to me

Can u assign this issue to me?

i would like to work on this issue
i have good knowledge about python libraries (pytorch, tensorflow ,openCV etc..)
please assign me this issue under GSSOC 24.iI will try to contribute with my full potential .


Hook up unit tests to the CI

This pull request aims to add a fully working CircleCI integration.
To achieve that, we first added pipenv configuration that allows us to prepare the environment with ease.
Next, we wrapped the most commonly used commands into a simple Makefile to reduce the cognitive load when performing chores.
Lastly, we updated the CircleCI configuration file that now actually runs the test suite.

/cc @matejart Just for reference.


Factor retry handling out of Output into Agents

The retry handling PR moved a lot of the logic for retries onto the LumenOutput classes but overall it'd be much cleaner if that complexity could be handled by the agents themselves. So in this PR I'm moving the retry handling onto the LumenBaseAgent.

Added alternating warning. Will now fix two user messages in a row.

Dropped user query from the system since I think it's redundant now. Also mutated the original message.

Testing vega specs now.

I realized that it can tunnel from the lack of columns context and not get back out:
Here's a summary of the dataset the user just asked about; you must reference columns from this dataset in your response:

Besides the tunneling issue (I might loop through all the sources tables & specs), it seems to work well!
https://github.com/user-attachments/assets/adbb9bab-e1b0-4cf3-9fc1-fcf50feebc9f
https://github.com/user-attachments/assets/e8c9228d-9467-4650-9cbd-81c0c8524b81

Okay I think it's ready
"""
The user is unsatisfied with the output; your goal is to update the specification in sql:
Here is the original specification to be corrected:
SELECT *
FROM read_csv('olympic_hosts.csv')
WHERE "game_season" = 'Winter'
ORDER BY "game_year" ASC
LIMIT 5

Here are YAML schemas for currently relevant tables:

read_csv('olympic_hosts.csv'):

game_end_date:
  format: datetime
  max: '2022-02-20T12:00:00'
  min: '1896-04-15T11:39:39'
  type: str
game_location:
  enum:
  - China
  - Japan
  - Republic of Korea
  - Brazil
  - Russian Federation
  - '...'
  type: str
game_name:
  enum:
  - Beijing 2022
  - Tokyo 2020
  - PyeongChang 2018
  - Rio 2016
  - Sochi 2014
  - '...'
  type: str
game_season:
  enum:
  - Winter
  - Summer
  type: str
game_slug:
  enum:
  - beijing-2022
  - tokyo-2020
  - pyeongchang-2018
  - rio-2016
  - sochi-2014
  - '...'
  type: str
game_start_date:
  format: datetime
  max: '2022-02-04T15:00:00'
  min: '1896-04-06T11:38:39'
  type: str
game_year:
  max: 2022
  min: 1896
  type: int

Respond in the same format as the original specification. The query may include multiple tasks, your job is merely to correct the specification, ignore any instructions unrelated to that and do not add any comments or code examples.
"""


Fixed #911 - Multiple duplicate replication change events sent in pul…

…l replication
Multiple reasons might cause this problem:

CBL Java/Android threading model is different. When notification is sent and when notification was delivered, Replication state might be changed. To avoid the problem from this behavior, need to access ChangeEvent variables instead of Replicator variables.
Instead of

Replicator pull;
Log.e(TAG, pull.getCompletedChangesCount() + " / " + pull.getChangesCount() + " [status = " + pull.getStatus() + "]");

should be
ChangeEvent event;
Log.e(TAG, event.getCompletedChangesCount() + " / " + event.getChangesCount() + " [status = " + event.getStatus() + "]");

Replicator.ChangeEvent does not have ReplicationStatus getStatus(). Added method. ReplicationStatus status; is final variable. So it should not be changed.
Public replicator Status and CBL Java/Android internal replicator status is not exactly same.  Internal status has more detailed states. So few status match to one public replicator state. In case public replicator state is not changed, not notify changes.

After I discussed with @pasin, this is ready to be merged.


[HeroQuest Glorantha] Added Translation tags

Changes / Comments
Added Translation tags.
Created base translation.json
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[x] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[x] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.


Add C++ aggregators

Use C++ aggregators instead of Python aggregator implementations. In the future, there will be additional ones. Currently, the aggregators are maked when invoking scripts/setup-pash.sh. Tests have been moved from annotations/tests/ to runtime/agg/cpp/tests to be next to the aggregators being tested. They have been set up to be invoked when calling scripts/run_tests.sh. Currently, no tests are implemented as 1. no real aggregators were implemented so far (only for grep and it seems to be using built-in ones) and 2. I wasn't able to find any code in the PaSh codebase that parses the aggregate member in annotations' JSON and could be used to extract information about which aggregator corresponds to which command.

Aggregators yet to be added include (for future reference): nl, wc, uniq -c, tr -cs.

@janekb04 This is awesome! I will pull, test, and report back later today—but this looks so exciting!
Curious: why delete the testing infrastructure? These scripts were pretty generic and used the annotations to identify the right aggregator path.

@nvasilakis I deleted the test infrastructure as it was rather basic and didn't have support for commands that require different aggregators depending on their options. I think that for now, after I implement some aggregators to test, I will write manual tests and when infrastructure used to parse aggregate members will be in place, I will make the tests use it instead.

OK:-)

Now that the base infrastructure is in place, I think that what is left is for me to do, is to add missing aggregators, change annotation files to point to those aggregators, add tests for those aggregators.

Now that the base infrastructure is in place, I think that what is left is for me to do, is to add missing aggregators, change annotation files to point to those aggregators, add tests for those aggregators.

Sounds good!

Regarding the failing CI, it seems like the tests are fine and the problem is with the workflow not being able to post the results somewhere.

Yeah, the CI is not yet complete, that's why it fails

@nvasilakis  Now, while working on aggregators, I've come to the realization that I don't think that parallelizing certain commands makes sense.
Let's take nl as an example. If not parallelized, it has to go through a file in O(n) time and add line numbers. If it is parallelized than it can be spread between k threads and take O(n/k) time in theory. However the aggregation step has to go through each of the partial results sequentially and merge them in O(n) time, so we get the original time complexity. Actually, the added split and nl commands will make this approach slower than just using only one invocation of nl.
I would conclude from this that parallelizing only makes sense if...

let cmd be a shell command
let k be the number of threads (I believe this is --width in PaSh)
let P(x) be the time complexity of cmd on an input of size x
let Q(x) be the time complexity of cmd's aggregator on an input of size x

...if  P(x)/k + Q(x) < P(x). That means that Q(x) < P(x) - P(x)/k, which could be approximated to (assuming a large k) Q(x) < P(x). The approximation strengthens the fact that it should be < rather than ≤.  From this, I conclude that parallelizing nl is counterproductive, as for it P(x) = x and Q(x) = x, so the inequality is not satisfied.
Is this right, or am I getting something wrong?

This is right!

Does PaSh, then, have some check implemented so it doesn't paralelize such commands?

I don't recall there being anything about this in the paper. Perhaps this could be causing the cases where PaSh underperforms, like when it has 0.89x speedup?

The base information is captured by annotations (and the logic that implements associated transformations). There is a higher-level, more general question about when to parallelize combinations of commands and this includes several parameters — commands before/after, input sizes, target environment etc. This is not fully implemented yet.

I completed the aggregator for wc. I also changed the code a bit to use streams instead of strings and added test infrastructure and changed the annotation file. Tests pass for me.

This new testing infrastructure doesn't ignore whitespace. So the wc aggregator finds the padding in the output of wc.

@nvasilakis Now the aggregator for uniq -c has also been added. It passed the tests on my machine. It assumes that the split files end in a \n character, but I think that this assumption is always met when PaSh splits files.

@nvasilakis Now that the wc and uniq -c aggregators have been implemented, which aggregators should I implement next? I know there is tr -cs however on the last technical meeting we discussed how currently the aggregators don't have access to the command's arguments and in this case that is a requirement for the aggregator. Is there a list of aggregators to implement or perhaps a list of most common commands that need aggregators?

Also, it seems like the CI isn't working yet. I'm not sure if #261 was supposed to fix it, but I'm mentioning it just in case.

@janekb04 I suppose that I have fixed the CI issues. I am not quite sure whether the tests will be executed on this pr (since your fork/pr is older than my patch). I guess we will find out soon

@dkarnikis I reran the tests and they still seem to fail in the "Posting results" section.

Probably because your fork/pr is based on an older version of pash
(on newer prs, you should not have this issue as long as your fork is updated to match the main repo).
Based on your execution logs, the tests seem to run correctly.
intro: 2/2 tests passed.
interface: 6/6 tests passed.
compiler: 52/52 tests passed.

Ok that's much better now. As mentioned in this #286, a previous commit broke the scripts

@nvasilakis I added support for options for aggregators. Now aggregators like uniq will be able to see if an option such as -c has been set and modify their behaviour accordingly. I think this will prove especially useful with commands that have a lot of options, such as sort.
It took me some time as the Linux getopt_long command isn't very clean to use, so I wanted to make a clean C++ wrapper around that. I also didn't want to sacrifice any performance, so all data structures for getopt_long are prepared at compile time using some template metaprogramming.

Fortunately, after all that, thanks to using getopt_long, now all syntaxes like -c -s, -cs, -Wall, -opt -- other, --combine should be correctly parsed.

I added all options (-lwcmL) for the wc aggregator. I also added VSCode, Clion and Visual Studio files to .gitignore because it was annoying for me to constantly delete them.

Fortunately, after all that, thanks to using getopt_long, now all syntaxes like -c -s, -cs, -Wall, -opt -- other, --combine should be correctly parsed.

Awesome!

@nvasilakis Support for uniq (with no -c) and empty input files has been added. I think this no longer has to be a draft.

@nvasilakis I just wanted to mention here, just in case, that I added a concatenating aggregator for tr and its options -ctd. I haven't added an aggregator for tr -s yet, as I'm unsure about some license issues I wrote about in an email.

Also, I don't think we should squash when merging. The PR is quite large and I think the iterative change process should be preserved.

@janekb04 could you fetch the latest changes from the main repo (as you did before) so the tests may run properly? Also could you follow the steps on the DCO check that fails?
Thanks

@dkarnikis I already fetched. I don't know why the tests fail. I will look into DCO.

@dkarnikis It look like tests fail on "building runtime". This could possibly be caused by aggregators not compiling, but on my machine it works fine. I'll investigate.

It works on Ubuntu 20.04 (link). I think the issue is that the compiler on 18.04 doesn't support C++17. Can I just add a sudo apt install g++10 to setup_pash.sh?

That would be a solution. However, similar changes should be done in order to support the other distros (fedora, arch, debian) but also their docker files.

@dkarnikis Does it have to support any other platform/distro other than Ubuntu, Fedora, Arch, and Debian? Does it have to support macOS?
I never used Docker before. I can begin learning it though, if necessary.

Currently these are the only distros we support. I am working on Mac 'docker' support. Maybe you could create an issue to fix the Dockerfiles to support the new aggregators. @nvasilakis  what do you think?

@dkarnikis I run the instructions on DCO.

We could also update the dockerfiles after Jan pushes changes to the setup
scripts.
On Sun, Jul 25, 2021 at 1:40 PM Dimitris Karnikis @.***>
wrote:

Currently these are the only distros we support. I am working on Mac
'docker' support. Maybe you could create an issue to fix the Dockerfiles to
support the new aggregators. @nvasilakis https://github.com/nvasilakis
what do you think?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/binpash/pash/pull/277#issuecomment-886181192, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AADL55BW272STWDQUWKJN2TTZPSZLANCNFSM5AJRCFFA
.

I will now push a test commit to see if DCO and signing works.

I realized that I signed the previous commits with the wrong email for DCO. I will resign them now and run the DCO commands again.

After doing the DCO stuff I realized that some files have changed that I haven't touched myself. I think they come from a different PR. Here's the list of the files I personally didn't change:
.github/workflows/cicd.yaml
.github/workflows/main.yml
README.md
annotations/README.md
annotations/cat.json
annotations/diff.json
annotations/echo.json
annotations/find.json
annotations/head.json
annotations/history.json
annotations/pr.json
annotations/pwd.json
annotations/tac.json
annotations/tail.json
compiler/test_evaluation_scripts.sh
docs/README.md
docs/contributing/contrib.md
docs/pash_architecture.PNG
docs/tooling/ci.md
docs/tutorial/tutorial.md
docs/windows.md
evaluation/benchmarks/bio/README
evaluation/benchmarks/max-temp/max-temp.sh
evaluation/benchmarks/poets/8.2_2.sh
evaluation/benchmarks/run.par.sh
evaluation/benchmarks/run.seq.sh
evaluation/benchmarks/run_all_benchmarks_ci.sh
evaluation/intro/test.sh
evaluation/tests/input/setup.sh
evaluation/tests/interface_tests/run.sh
scripts/distro-deps.sh
scripts/docker/Dockerfile.base
scripts/docker/Dockerfile.testing
scripts/docker/README.md
scripts/docker/debian/Dockerfile
scripts/docker/fedora/Dockerfile
scripts/docker/ubuntu/Dockerfile

I updated distro_deps.sh. By the way, it took me so long because I couldn't figure out why git wasn't able to sign my commit.  I changed distro_dependecies.sh, so now the aggregators compile. I also reverted annotations as discussed with Nikos.
I don't know why the CI fails. But it doesn't seem to be related to aggregators. The aggregators build successfully and all unit tests pass.
I didn't delete the tr aggregator, as it will make it easier to implement tr -s in the future.

@nvasilakis @dkarnikis I will also write here, just in case, that we discussed with Nikos that the PR won't be squashed as it affects too many files.

@nvasilakis What’s the current state of is PR? Should I wait for it to be reviewed or should I continue implementing more aggregators and push them?
I don’t want to open a new PR before this one is merged because it would need the base infrastructure from this PR anyway.

I have added the aggregator for grep, including many of its multiple options.
When looking into the source code you may find that it mostly consists of just option names. This is on purpose.
The aggregation itself is quite simple, just concatenation or addition of two numbers.
Despite that, the aggregator infrastructure still requires to specify all supported options regardless of the fact wether they change the aggregation process logic. I decided to do it this way to follow PaSh's philosophy of "correctness first". I want it to be needed to explicitly specify all supported options in order not to run into a situation when the aggregator would fail. It also encourages to think about every option and whether it is actually supported.

@nvasilakis After looking through the files again, I don't think there's anything broken apart from head.json. Now, all changes left are those made intentionally by me. As such, I believe we can merge this branch without recloning. I don't really know the git tools related to squashing, reapplying or modifying commits in any way.
I will recap for each file, why it changed:

.gitignore ignores files of IDEs like VSCode, Clion or Visual Studio - makes it less annoying while developing
annotations/head.json this is the only one, I didn't change
annotations/tests/* directory deleted as tests are now in runtime/agg/cpp/tests
compiler/parser/Makefile I misremembered. I did change this file. It shouldn't affect anything. I just made it use $(MAKE) instead of make because I believe this is good practice.
runtime/Makefile now compiles the C++ aggregators
runtime/agg/README.md now refers to new C++ aggregators
runtime/agg/cpp/* these are all new files
scripts/distro-deps.sh now installs g++-10 as it is required for compiling the aggregators. Note: I tested it only on Ubuntu. I don't know if it works on Debian, Fedora or Arch. I only know that on Ubuntu 18.04 it wouldn't compile if I didn't change this file.
scripts/run_tests.sh now runs the aggregator unit tests. Note: they don't affect the CI status, as I didn't really look into how to do that and I'm not sure if it would be beneficial/necessary.

@nvasilakis I fetched upstream and fixed head.json. I think the branch is ready for merge.

@nvasilakis I think something is wrong with the CI as it has been continuously running for over two hours now.

@janekb04 I cancelled the CI and I am checking the logs.
Apparently, the setup scripts fails to download the required files (this also happened locally to my setup).
curl: (7) Failed to connect to ndr.md port 80: Connection timed out.
@nvasilakis I think you should check this.

@nvasilakis What is the current state of this PR?

Closed via #310


Reset LayoutTransformControl matrix when transform is removed

What does the pull request do?
This PR ensures that when LayoutTransformControl.LayoutTransform is set to null after having a value previously, the applied matrix is reset to the identity one.
A test has been added.
Fixed issues
Fixes #10567

You can test this PR using the following package version. 11.0.999-cibuild0036775-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]


Feat: added API for updated Application details page

What type of PR is this?

/kind enhancement

What does this PR do / why we need it:
This PR adds a new API which would be called by the Dev Console for the updated Application details page.
Currently the server address for ArgoCD, is hardcoded to openshift-gitops-server since there is no easy way to determine which argocd instance gitops-backend-service is pointing to. Also, KAM currently is only supported with the openshift-gitops instance.
Have you updated the necessary documentation?

[ ] Documentation update is required by this PR.
[ ] Documentation has been updated.

Which issue(s) this PR fixes:
Fixes https://issues.redhat.com/browse/GITOPS-577
How to test changes / Special notes to the reviewer:
TODO

@shubhamagarwal19  please add "How to Test".

/lgtm
/approve

@shubhamagarwal19 Can you please update the How to test changes section? This will help us during the v1.3 testing :)

@shubhamagarwal19 Can you please update the How to test changes section? This will help us during the release testing :)
Linking this to https://github.com/redhat-developer/gitops-backend/pull/24 for how to test notes. It would make more sense to test both the enhancements as a single test case for new application details page API.
@keithchong will update the How to test description for the same!


Modified snake game

Description
Added a modified snake game to the projects folder! It's a standard snake game in Javascript except that
there is an enemy snake that tries to kill you by touching you. Hopefully this is a nice addition to the handful
of other small projects in this folder!
Choosing one or more options from the following as per the nature of your Pull request.
NOTE: Check boxes using [x]

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Documentation Update

Checklist:

[x] I have named my files and folder, according to this project's guidelines.
[x] My code follows the style guidelines of this project.
[x] My Pull Request has a descriptive title. (not a vague title like Update index.md)
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have created a helpful and easy to understand README.md, with problem description and my name.
[x] I have included a requirements.txt file (if external libraries are required.)
[x] My changes do not produce any warnings.
[x] I have starred this repository.
[x] I have added a working sample/screenshot of the script.
[x] I have checked for trailing spaces in file names and none have them.

I'm attempting to complete the hacktoberfest 2020 challenge, so please add the hacktoberfest-accepted label if you accept this pull request. Thank you so much!

@shayanhalder Sure! Actually the label is not required for this repo.


Drop Travis CI

TL;DR Travis CI will cost money
And this project isn't funded.
https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing
The way forward is #199

This is done


[BUG] pipeline engine is_gradient_accumulation_boundary is not set correctly

Pipeline engine overrides deepspeed.runtime.engine.is_gradient_accumulation_boundary()
https://github.com/microsoft/DeepSpeed/blob/7e8bcc07d6532a380a7a439741609b058f083ed6/deepspeed/runtime/pipe/engine.py#L560
In this implementation is_gradient_accumulation_boundary will return True only when the pipe is executing _exec_optimizer_step or _exec_reduce_grads. It will return False during forward and backward calls. Additionally it will ignore calls to set_gradient_accumulation_boundary.
This behavior leads to multiple issue in deepspeed.runtine.engine.backward

loss list grows indefinitely
https://github.com/microsoft/DeepSpeed/blob/7e8bcc07d6532a380a7a439741609b058f083ed6/deepspeed/runtime/engine.py#L1884

If zero is enabled optimizer is called with incorrect state of is_gradient_accumulation_boundary
https://github.com/microsoft/DeepSpeed/blob/7e8bcc07d6532a380a7a439741609b058f083ed6/deepspeed/runtime/engine.py#L1894

amp loss scaling incorrect.
https://github.com/microsoft/DeepSpeed/blob/7e8bcc07d6532a380a7a439741609b058f083ed6/deepspeed/runtime/engine.py#L1899C13-L1899C27

@hablb The first point has been fixed in a previous PR. Could you point to examples of the second too points causing issues?

for #2 "Train/Samples/train_loss" will not be printed to tensorboard
https://github.com/microsoft/DeepSpeed/blob/master/deepspeed/runtime/engine.py#L1910
for #3. I'm not aware of any specific issue, but according to the comment in line 1923 it may be required
https://github.com/microsoft/DeepSpeed/blob/master/deepspeed/runtime/engine.py#L1923

Thanks for pointing to these. We'll find a solution and link the PR here.

Are you not seeing the summary events? There is a separate engine in runtime/pipe/engine.py that is used for Pipeline Parallelism. It overrides the backward function in runtime/engine.py and has an implementation that should be showing the summary events


Mock drops or moves const when mocking functions

I recent made some change to make my project code const correct.  In that process, I changed a function that returned a pointer to structure to return a const pointer to a function, e.g., STRUCT_TYPE * myfunc() became STRUCT_TYPE * const myfunc().  However, mock decided to create the mock function as const STRUCT_TYPE *myfunc() which is obviously not the same thing and it breaks the compile because the function prototype in the header file now conflicts with the mock function.
I didn't look at the mock prior to my changes so I don't know if mocks were always const STRUCT_TYPE *, but it would be unexpected for mock to add const.  So, I suspect that mock is adding const but putting in the wrong place.  Unfortunately, I don't know ruby well enough to track down where the mocks are being generated.

I have the same issue as I have a function with a pointer with a constant address that points to a constant value. Here are the functions that I am trying to mock :
eeprom_keys_t const * const eeprom_keys_read (void) eeprom_config_t const * const eeprom_read_config (void)
And here is how Ceedling is mocking the functions :
const eeprom_config_t const* eeprom_read_config(void) const eeprom_keys_t const* eeprom_keys_read(void)
I don't know what would be a good way to corrrect that issue. It causes a problem of conflicting types...
`Test 'test_rfid_tag.c'
Generating runner for test_rfid_tag.c...
Compiling test_rfid_tag_runner.c...
Compiling test_rfid_tag.c...
Compiling mock_eeprom.c...
build/test/mocks/mock_eeprom.c:1004:23: warning: duplicate ‘const’ declaration specifier [-Wduplicate-decl-specifier]
1004 | const eeprom_config_t const* eeprom_read_config(void)
|                       ^~~~~
build/test/mocks/mock_eeprom.c:1004:30: error: conflicting types for ‘eeprom_read_config’
1004 | const eeprom_config_t const* eeprom_read_config(void)
|                              ^~~~~~~~~~~~~~~~~~
In file included from build/test/mocks/mock_eeprom.h:6,
from build/test/mocks/mock_eeprom.c:6:
../bdp/src/eeprom/eeprom.h:13:31: note: previous declaration of ‘eeprom_read_config’ was here
13 | eeprom_config_t const * const eeprom_read_config (void);
|                               ^~~~~~~~~~~~~~~~~~
build/test/mocks/mock_eeprom.c:2165:21: warning: duplicate ‘const’ declaration specifier [-Wduplicate-decl-specifier]
2165 | const eeprom_keys_t const* eeprom_keys_read(void)
|                     ^~~~~
build/test/mocks/mock_eeprom.c:2165:28: error: conflicting types for ‘eeprom_keys_read’
2165 | const eeprom_keys_t const* eeprom_keys_read(void)
|                            ^~~~~~~~~~~~~~~~
In file included from build/test/mocks/mock_eeprom.h:6,
from build/test/mocks/mock_eeprom.c:6:
../bdp/src/eeprom/eeprom.h:24:29: note: previous declaration of ‘eeprom_keys_read’ was here
24 | eeprom_keys_t const * const eeprom_keys_read (void);
|                             ^~~~~~~~~~~~~~~~
ERROR: Shell command failed.
`


Cli migration fail with $(SolutionDir) in csproj

I want make a dotnet ef migrations add InitialCreate -v and build faild because I have a $(SolutionDir) in my csproj :
 <Target Name="PostBuild" AfterTargets="PostBuildEvent">
    <Exec Command="$(SolutionDir)bp.bat copydeps" Condition="'$(OS)' == 'Windows_NT'"/>
    <Exec Command="$(SolutionDir)bp.sh copydeps" Condition="'$([System.Runtime.InteropServices.RuntimeInformation]::IsOSPlatform($([System.Runtime.InteropServices.OSPlatform]::Linux)))' == 'true'"/>
    <Exec Command="$(SolutionDir)bp.sh copydeps" Condition="'$([System.Runtime.InteropServices.RuntimeInformation]::IsOSPlatform($([System.Runtime.InteropServices.OSPlatform]::OSX)))' == 'true'"/>
  </Target>

I have no exception, just a message telling me that the build failed.
D:\Developpements\Base\WebApplication\WebApplication.csproj(52,5): error MSB3073: The command "* Undefined *bp.bat copydeps" stopped with code 9009.

FAIL of the build.

Steps to reproduce
To reproduce, simply add similar code given at the beginning of this issue and try to make a migration.
Further technical details
EF Core version: 2.0.1
Database Provider: Microsoft.EntityFrameworkCore.Sqllite
Operating system: Windows 10
IDE: Command line (powershell in vscode 1.18.1)

The $(SolutionDir) is only set if you are building in Visual Studio or building the *.sln file directly. To make your project's more robust, you should add something like the following:
<PropertyGroup>
  <SolutionDir Condition=" '$(SolutionDir)' == '' ">$(MSBuildThisFileDirectory)..\</SolutionDir>
</PropertyGroup>

Another commonly used form: (so you don't have to type the correct number of ..s)
$([MSBuild]::GetDirectoryNameOfFileAbove($(MSBuildThisFileDirectory), WebApplication.sln))

@bricelam thanks.
I will look to test tomorrow


Reactive marker - debounce not sending last lat lng

Steps to Reproduce
As per #274 - however this is a new issue as a new problem
The debounce function is not sending the LAST lat lng for a dragged marker (but is dragging OK and sending back data every 100 ms as configured).
If you remove the debounce function, all works as expected and the last position is correctly set.
Expected Results
The very last position should be sent back from the debounce function
Actual Results
A prior position is sent back - which does not correspond to the final resting point of a marker.
This causes user confusion as they are expecting the marker's visual position and the created lat lng to exactly match.
Browsers Affected

Chrome
[Not tested others]

Versions

Vue: v2.5.13
Vue2Leaflet: v1.2.3

Thanks!

This should be resolved in the latest 2.0.0-beta.1.
Could you check it?

@DonNicoJs I will take a look. Might be 10 days though (sorry)
Thanks for addressing!

@alexbainbridge the fix is not on the 2.0.1 stable :)

not working on 2.0.0-beta.1 as well as it should :/

@fauzipadlaw did you try the latest version? (2.0.3) because we have unit tests ( in this PR https://github.com/KoRiGaN/Vue2Leaflet/pull/365/files ) and the unit test are passing (https://travis-ci.org/KoRiGaN/Vue2Leaflet/builds/516254653?utm_source=github_status&utm_medium=notification)

I did.
https://jsfiddle.net/6zscu3md/

@fauzipadlaw you need the .sync modifier for it to work :) https://jsfiddle.net/v478n31w/3/

great, it does work! thank you so much @DonNicoJs

@DonNicoJs Thanks a lot. .sync saved my day! One more issue is its not updating position on drag :(


Reflection synced with tep

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes #(issue)
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

[ ] Test A
[ ] Test B

/rebase

/rebase

/rebase

/rebase

/rebase

/rebase

/rebase

/rebase

/merge

/merge


Angular logs error on 404 responses

When a resource responds with a 404, additional to the js-data log, angular logs:
[object Object]
angular.js:11655 (anonymous function)

Here is a plunker

What is the concern here?

Oh, I just thought is was weird that I always got an extra ugly looking log error from angular every time I got a 404. If its not a problem, just close this.

Yeah, I think angular just logs 4xx and 5xx $http errors no matter what.

I think this should be reopened as a bug.
If you run 2 identical calls
$http.get('http://localhost:8080/api/12')
    .then(function () {
        console.log('success');
    }, function () {
        console.log('error');
    });

Api.find('12')
    .then(function () {
        console.log('success');
    }, function () {
        console.log('error');
    });

Both of them do log the error
angular.js:9866 GET http://localhost:8080/api/12 400 (Bad Request)

But an exception at angular.js:11655 is only thrown by the adaptor.


Update Project Manager Protocol

Summary

The project manager will need to handle engine version management using the same logic that the launcher uses. This additional functionality requires an update of its protocol.
Value

Both PM and IDE know what new messages need to be handled.
We take the first step to being able to manage engine versions from PM.

Specification

Requirements for the protocol:

It should augment opening projects so that missing engine/runtime versions will be installed.
When a project is being opened, it should determine what version is necessary to open it.

If that version is not installed, it should send a message to the IDE and wait for a reply (install-missing-components / cancel).

If a new project is being created, the same logic for downloading the missing version (with a question if the components should be installed or current action cancelled) should be used.
When the components are being installed, installation/download progress should be reported to the IDE with some progress update messages.

We probably want a triple: task/started, task/progress-update, task/finished.

If a version requires a newer project-manager version, a failure message should be sent project-manager-upgrade-required (and that message should contain the minimum version that is required).

This error may happen in any message that uses the engine, currently project/open and project/create.

Allow the IDE to query logging service setup (information needed to establish a connection to the service from the IDE).
It should allow to list currently installed engine releases and uninstall them.

[ ] Prepare a draft of the updated protocol specification.
[ ] Discuss the draft with IDE.

[ ] Update any requested changes.

[ ] Add a stub implementation of the protocol in the project-manager (for now the messages should return an error indicating 'not-implemented').

Either the old protocol should still be supported, be backwards compatible or the IDE should update to support the new protocol.

This will depend on how many breaking changes are there, possibly the only breaking change may be the question asked if an engine version should be installed.

Acceptance Criteria & Test Cases

[ ] The protocol design has been discussed with the IDE team and has been accepted.

If that version is not installed, it should send a message to the IDE and wait for a reply (install-missing-components / cancel).

I wonder if it would be much simpler, if the project/open would have an option "don't install missing components / install missing components(version)", and return an error without any "waiting for IDE reply" state. We can just call this method twice if we need to.
Additionally, I think there should be option in project/create to specify version of Enso the project is using (usually use the newest version supported by IDE).

If that version is not installed, it should send a message to the IDE and wait for a reply (install-missing-components / cancel).

I wonder if it would be much simpler, if the project/open would have an option "don't install missing components / install missing components(version)", and return an error without any "waiting for IDE reply" state. We can just call this method twice if we need to.

That would indeed be simpler.

Additionally, I think there should be option in project/create to specify version of Enso the project is using (usually use the newest version supported by IDE).

Yes that endpoint should get which version to use (which potentially may be either a semver-string or latest-installed to get the latest currently installed version, falling back to the latest release available online).
Moreover, it should also have this "(don't) install missing components" option as open has.

In addition to listing installed and uninstalling it should allow for installing a specified version, same as the launcher. This is useful for people who may be without internet for some time, and want to preinstall versions they may need.


Wrong format of COPY FROM syntax of postgresql

To Reproduce
Here is the example:
COPY mytable (c1, c2, c3) FROM STDIN;
c1-1    \N    \N
\.

After format, will format as:
COPY mytable (c1, c2, c3) FROM STDIN;
c-1-1 \N \N \.

You can see the STDIN will turn into one line, which is incorrect.
Before format:

After format:

Desktop (please complete the following information):

SQLTools Version [e.g. v0.17.x]
VSCode Version: [e.g 1.x.y] 0.15.2
OS: [e.g. Windows, Linux, Mac] Linux
Driver:

[x] PostgreSQL/Redshift
[ ] MySQL/MariaDB
[ ] MSSQL/Azure
[ ] SQLite
[ ] Other? Which...

Database version: [e.g. MySQL v5.6, PostgreSQL vX...]

It also adds a space to \copy, results in \ copy which doesn't work.


Doesn't type anything...

It says its "completed the mission" when the race is done, but it's not done. I just got disqualified because it wouldn't type. Maybe you could try it yourself. Because for me, this is what happens.

Another example. This time it's an Extracted, uncompressed file. The other was Compressed. This time it actually types and uses nitro, but still doesn't work.

Could you please fix this as soon as you can, or tell me if you're working on a fix. Thanks!

Are you going to fix this?  Or should I delete the files? Please let me know. I need space on my computer.

idk

Tool is working properly. However, you are not using it in correct way, hence, the error. Go through step be step guide provided at www[dot]theprabhakar[dot]in


chore: minimize the usage of Mac OS.

It happened 5+ times (on Feb.12th) that the GH Actions cost 20+ minute, because of the waiting time of the Mac OS containers.
I guess with more people working on it, it's harder to get the containers.
In this PR, I would like to minimise the usage of the Mac OS container and only keep using one.
I disabled the combination of Mac OS and node 10, since we still have two cases below:

Mac OS and node 12
ubuntu and node 10

Let me know your opinion.

For me it is fine to just use one mac container. In general I would prefer to have also one windows container in the mix, because mac should be more like unix so, but windows is real different.

In general I would prefer to have also one windows container in the mix, because mac should be more like unix so, but windows is real different.

For windows, we have a separate ticket, because we have to fix something before enabling. Also, windows is slower than Mac OS and ubuntu, which needs to be evaluated again.


How to add site logo in the nav?

I received the following question

How exactly would I set the site logo?
I've tried everything, but currently the logo loads BEFORE the site nav, and not in the navbar-brand like it should.

General Advice for Modifying Markup
Generally, I would recommend modifying the Bootstrap Genesis Child Theme directly for any markup changes.  This change would be in lib/nav.php.
Specific Situation of Modifying the .navbar-brand
Just recently on August 3, 2015, I added a filter for this very purpose.
At the time of this writing, this new filter only appears in the develop branch and will be in the next release 0.8.0, which I aim to push out in the next week.


Test that find_library_file works with Cygwin libraries

It worked for setuptools<60 and doesn't with setuptools>=60; I would like it to keep working.
Follow-up to python-pillow/pillow#6216

Cygwin test failing in the expected place

The new test passes with the library name pattern update.  Merging this should probably wait for input from a maintainer about what CCompiler.find_library_file is supposed to be looking for: should it find any file related to the given library, regardless of whether it can be used in linking, or only those files useful in linking?
The cyg${name}.dll files aren't used in linking the way the lib${name}{,.dll}.a files are, but it is the file needed by dlopen.

Worst case for the problem I'm thinking of involves the linker failing, and I think those error messages are decently informative, so that's a decent approach.


Update pyproject

What does this PR do?
Updates pyptoject to ensure its pip installability and versioning
Tested the pip installation with:
{update earth_osm/VERSION file to desired version}
git tag {version}
python3 -m pip install build --user
python -m build
twine upload --repository testpypi dist/*
python3 -m pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ earth-osm=={version}
earth_osm
pip uninstall earth-osm

The proposal is to upload a post release 2.3.post1 ; expected to be done tomorrow

Tested the pip installation with:
{update earth_osm/VERSION file to desired version}
git tag {version}
python3 -m pip install build --user
python -m build
twine upload --repository testpypi dist/*
python3 -m pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ earth-osm=={version}
earth_osm

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

Project coverage is 60.04%. Comparing base (a3a0322) to head (db6e717).
Report is 22 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #57      +/-   ##
==========================================
- Coverage   68.17%   60.04%   -8.14%
==========================================
  Files          16       16
  Lines         795      906     +111
==========================================
+ Hits          542      544       +2
- Misses        253      362     +109

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


feat(field): add dump_alias and load_alias options

Change Summary

[x] add dump_alias option
[x] add load_alias option
[x] generate schema for both serialization and deserialization
[ ] add documentation

Related issue number
closes #624
Checklist

[ ] Unit tests for the changes exist
[ ] Tests pass on CI and coverage remains at 100%
[ ] Documentation reflects the changes where applicable
[ ] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)

@samuelcolvin This is the whole question and honestly I need to think it over. This is why it's just a draft I feel like we still need some feedback on the desired API. The best would be to have a bunch of tests with nested models and load/dump + exclude fields to have the expected behaviour for each one

Just saw this while working on https://github.com/samuelcolvin/pydantic/issues/660 ... not sure if I'm out of lying trying to create a pull requests for that or if the discussion here has changed the view on it.
Especially the idea of having an "Exclude" object on the dump alias is a bit different compared to https://github.com/samuelcolvin/pydantic/issues/660#issuecomment-515406193.
That said, there are a few arguments for separating the two:

having separation of concerns: the "exclude" functionality with an explicit "exclude" option is probably needed anyway because we probably want to support the "advanced" exclude syntax: t.dict(exclude={'user': {'username', 'password'}, 'value': ...}). Having another way of excluding a field using the dump_alias might be confusing as there would now be two ways of doing this.

We might want to toggle exclusion separately from the dump alias, assuming we want to allow a case like this: Let's say we have a model

class TestModel(BaseModel):
    a: int = Field(0, dump_alias="a_dump", exclude=...)
    b: str = "foo"
    c: str = "bar"

would we want to allow the fields to be "included" by the .dict override??
TestModel(a=3).dict(include={"a"})  # {"a_dump": 3}

There are cases I know where this might be the desired behavior.
There are also arguments against the second point: I can just as well think of cases where this might be confusing because the author of the class wants the field to be hidden permanently and not being randomly resurrected by a overriding using dict or json.  Especially confusing would might be a case like this:
TestModel(a=3).dict()  # {"b": "foo", "c": "bar"}
# user decides they don't want to see "b"
TestModel(a=3).dict(exclude={"b"})  # {"a_dump": 3, "c": "bar"} ... what?? why did a_dump show up, it wasn't there before.

Were there any thoughts on "dump_alias" vs. "exclude" in class config / field or am I just confusing a bunch of issues here?

Just saw this while working on https://github.com/samuelcolvin/pydantic/issues/660 ... not sure if I'm out of lying trying to create a pull requests for that or if the discussion here has changed the view on it.
Especially the idea of having an "Exclude" object on the dump alias is a bit different compared to https://github.com/samuelcolvin/pydantic/issues/660#issuecomment-515406193.
That said, there are a few arguments for separating the two:

having separation of concerns: the "exclude" functionality with an explicit "exclude" option is probably needed anyway because we probably want to support the "advanced" exclude syntax: t.dict(exclude={'user': {'username', 'password'}, 'value': ...}). Having another way of excluding a field using the dump_alias might be confusing as there would now be two ways of doing this.

We might want to toggle exclusion separately from the dump alias, assuming we want to allow a case like this: Let's say we have a model

class TestModel(BaseModel):
    a: int = Field(0, dump_alias="a_dump", exclude=...)
    b: str = "foo"
    c: str = "bar"

would we want to allow the fields to be "included" by the .dict override??
TestModel(a=3).dict(include={"a"})  # {"a_dump": 3}

There are cases I know where this might be the desired behavior.
There are also arguments against the second point: I can just as well think of cases where this might be confusing because the author of the class wants the field to be hidden permanently and not being randomly resurrected by a overriding using dict or json.  Especially confusing would might be a case like this:
TestModel(a=3).dict()  # {"b": "foo", "c": "bar"}
# user decides they don't want to see "b"
TestModel(a=3).dict(exclude={"b"})  # {"a_dump": 3, "c": "bar"} ... what?? why did a_dump show up, it wasn't there before.

Were there any thoughts on "dump_alias" vs. "exclude" in class config / field or am I just confusing a bunch of issues here?

What if we didn't allow excluding via dump_alias and load_alias - just allowed the alias to be changed?
That way we get clear separation of concerns and a simple interface.

What if we didn't allow excluding via dump_alias and load_alias - just allowed the alias to be changed?
That way we get clear separation of concerns and a simple interface.

I'm really in favor of this. I'll be back on this PR in the next few days. Thanks a lot @daviskirk for the suggestion. Sorry I missed your message before

I'm really in favor of this. I'll be back on this PR in the next few days. Thanks a lot @daviskirk for the suggestion. Sorry I missed your message before

https://github.com/samuelcolvin/pydantic/pull/2231 now has a working candidate (see: https://github.com/samuelcolvin/pydantic/pull/2231#issuecomment-782196223 in particular, in case that influences anything here)

@samuelcolvin I went back on this.
I added load_alias and dump_alias and also changed schema generation to decide whether serialization ou deserialization schema should be generated.
I'll first wait for your input before writing documentation.
PS: fastapi tests fail because they use ModelField.alias but I reckon code can probably be updated on fastapi side.

Closing this.
Although we'll definitely support load_alias and dump_alias in V2, I doubt we'll use any of this logic.


Link colour makes it look like I’ve visited pages already

The link colours are back to front to default usage; purple for normal and blue for visited. E.g. in this screenshot I’ve visited the GDS blog but not the Government data blog. Could this be swapped?

Of course, I could just do a PR: https://github.com/openregister/www.openregister.org/pull/7

Resolved


[3.x] L10 compatibility

Hi!
This PR adds L10 compatibility!
NOTE: needs stancl/virtualcolumn AND stancl/jobpipeline to support 10.x first. PRs opened.
~~https://github.com/archtechx/virtualcolumn/pull/12~~ https://github.com/archtechx/virtualcolumn/pull/11
https://github.com/archtechx/jobpipeline/pull/12

The code should be fully updated now. L9 tests are passing, but L10 tests are failing with this message:

Package laravel/framework at version ^10.0 has a PHP requirement incompatible with your PHP version, PHP extensions and Composer version

The job seems to use PHP 8.1 correctly, as well as composer v2. So maybe some PHP extensions were added that we don't install in our Dockerfile? But looking at the 9.x & 10.x composer.json, the required PHP extensions are identical.

The tests seem to work for me locally though, so the issue only exists on GH. I might try just updating the Dockerfile to what we have in v4.

Sounds like a plan!

Actually the issue might be the composer version. For some reason the docker image installs this:

Composer (version 2.0.3) successfully installed to: /usr/local/bin/composer

While Laravel 10 requires composer 2.2. No idea why the installer would go for an older composer version but a new Docker image should fix it anyway.

I think you have to push PHP version in composer.json to 8.1 instead of 8.0

^8.0 supports 8.0, 8.1,, 8.2, ...

@stancl did you know ACT? With it you can run your GH actions locally and its compatible with all actions. I've used in the past and worked pretty well.

Since we dockerize our tests, CI and local tests are very similar already. The issue here is (or was, I may have just fixed it) something GH Actions-specific. I haven't used ACT but I'm not sure if it'd be helpful here when locally all docker-related things work properly for me but they don't on GH.
If the tests finally pass (or at least run — there are still some minor things to fix in code for L10 support), then the two issues were:

Microsoft's unixodbc-dev being broken. This was fixed by specifying an older stable version
Specifying PHP 8.0 as 8.0 instead of "8.0" in the CI matrix, which apparently converted it to a float and then an int, resulting in the PHP_VERSION variable in docker being 8 instead of 8.0

The tests did run, here are the final things to fix in code: https://github.com/archtechx/tenancy/actions/runs/4194331794/jobs/7272374540

Here select() doesn't accept an Expression (returned by raw()). So we need to run the raw select query in a different way.

Its just a matter of adding ->getValue() after ->raw(). Raw now returns a expression instead of a string, so we need to cast to string using ->getValue()

I can take a look at the other issues after lunch.

I tried that, but getValue() also expects a Grammar argument. I think there should be some more straightforward way to do raw selects in L10.

Good work guys, sorry for not being able to help with this. I'm not having some spare time.

No worries, thanks a lot for all your work on these PRs!


Generated Builtin Types const methods not compiling

When trying to call .slice(), I get this:
src/gen/builtin_classes/packed_string_array.zig:188:44: error: @ptrCast discards const qualifier
        gd.callBuiltinMbNoRet(binds.slice, @ptrCast(&self._opaque), .{ &p_begin_encoded, &p_end_encoded });
                                           ^~~~~~~~~~~~~~~~~~~~~~~
src/gen/builtin_classes/packed_string_array.zig:188:44: note: use @constCast to discard const qualifier

As an API design sidenote: in godot-rust they provide PackedStringArray::{as_slice,as_mut_slice} methods to return a native Rust slice directly, so that a user could subslice and do further operations without crossing the costly FFI boundary. Rust's and Zig's slices are very similar, so I thought a similar thing could be made here as well. Although, it goes a bit against the Godot convention: godot-rust had to rename the former Godot's .slice() to .subarray().

This is an issue in three, one which is a bug, the other two are not implemented stuff, which only one is core behaviour.
The actual issue is fixed by 344f0e8, open another issue for generated builtin types implementing operators.


NASA's fix for pixelation issue

No code changes.  Only updates worldwind aar.

To test build the branch and test with test basic.  Run GeoServer with plugins and install APG data.  This data is not available outside APG.
With test-basic, go to Layer, then Add WMS and use these parameters, from the emulator:
URL: http://<IP_ADDRESS>:8080/geoserver/cite/wms
Layer:us_aberdeen_md_usgs_20061201
Go down to an altitude of less than 100 meters and look for any pixelation.

Reintegrate


Dark mode

Will there be dark mode for sleeky?

Nevermind,
The backend is dark, despite the screenshot on readme


Provide script to upload a certificate in the APIM Certificate store

Is your feature request related to a problem? Please describe.
Provide script to upload a certificate in the APIM Certificate store.
This allows you to upload private certificates to be used for authenticating against backend services.
Describe the solution you'd like
In order to upload a private certificate, you need to perform these steps:

Get APIM Context
Create new AzApiManagementCertificate referring to the APIM-context.

See: https://docs.microsoft.com/en-us/powershell/module/az.apimanagement/new-azapimanagementcertificate?view=azps-5.5.0
This would have the following parameters:

ResourceGroupName (resource group containing the APIM instance)
ServiceName (name of the APIM instance)
CertificateFilePath (full path to the location of the public certificate)
CertificatePassword (password for the private certificate)

Target-module:

Arcus.Scripting.ApiManagement

Describe alternatives you've considered
Manual uploading of private certificates.

Voorlopig lijkt het password required, dus zullen we voorlopig niet kunnen gebruiken voor public certificates. Right?
https://github.com/Azure/azure-powershell/issues/12571


Env vars not working on svelte:head scripts

Describe the bug
I am trying to add google and clarity analytics to my SvelteKit website. At first I tried like joyofcode shows in his website. But then, since I need dev/prod environments, I added static env vars. Thing is, it doesn't work. Svelte for some reason does not identify those variables.. Tried with Svelte Kit 1.5, 1.5.3 and below. Env vars do exists correctly since I use in another places. Code is below:
Reproduction
<script lang="ts">
	import { page } from '$app/stores';
	import { PUBLIC_GA4_METRIC_ID, PUBLIC_MS_CLARITY_ID } from '$env/static/public';

	$: {
		// @ts-ignore
		if (typeof gtag !== 'undefined') {
			// @ts-ignore
			gtag('config', `${PUBLIC_GA4_METRIC_ID}`, {
				page_title: document.title,
				page_path: $page.url.href
			});
		}
	}
</script>

<svelte:head>
	<!-- Google tag (gtag.js) -->
	<script
		async
		src={`https://www.googletagmanager.com/gtag/js?id=${PUBLIC_GA4_METRIC_ID}`}
	></script>
	<script>
		window.dataLayer = window.dataLayer || [];

		function gtag() {
			dataLayer.push(arguments);
		}

		gtag('js', new Date());
		gtag('config', `${PUBLIC_GA4_METRIC_ID}`);
	</script>

	<!-- Microsoft clarity -->
	<script type="text/javascript">
		(function (c, l, a, r, i, t, y) {
			c[a] =
				c[a] ||
				function () {
					(c[a].q = c[a].q || []).push(arguments);
				};
			t = l.createElement(r);
			t.async = 1;
			t.src = 'https://www.clarity.ms/tag/' + i;
			y = l.getElementsByTagName(r)[0];
			y.parentNode.insertBefore(t, y);
		})(window, document, 'clarity', 'script', `${PUBLIC_MS_CLARITY_ID}`);
	</script>
</svelte:head>

Logs
assinar:3472

       Uncaught ReferenceError: PUBLIC_GA4_METRIC_ID is not defined
    at assinar:3472:21
(anonymous) @ assinar:3472
assinar:3484

       Uncaught ReferenceError: PUBLIC_MS_CLARITY_ID is not defined
    at assinar:3484:48

System Info
System:
    OS: macOS 13.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 157.19 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.13.0 - ~/.nvm/versions/node/v18.13.0/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 8.19.3 - ~/.nvm/versions/node/v18.13.0/bin/npm
  Browsers:
    Chrome: 109.0.5414.119
    Firefox Developer Edition: 110.0
    Safari: 16.2

Severity
serious, but I can work around it
Additional Information
Tried adding this on Discord channel at first. Did not get any response. I also tried the vars getting from a const variable on script tag, still didn't work.

The content of <script> tags is not interpolated (it would be chaos otherwise). Either put the code inside those <script> tags inside your main component <script> or put them in src/app.html (using %sveltekit.env.PUBLIC_MS_CLARITY_ID% etc)

Oh I see.. Thanks!
Just one thing.. I read all SvelteKit documentation, didn't find nothing really about the %sveltekit...% stuff.
Maybe we should have one chapter explaining more in details about that.


rebuild resnet using blocks

re 1) Not sure if this is just my system (running semi-current tf-swift master), but the existing version in models repo takes 43 seconds to compile here.  Using this code takes ~3-4 seconds to compile.
re 2) Not sure how the current codebase handles arbitrary input, but certainly happy to rework things however desired.
re 3) That is fine, but having said that it would probably be good to refactor this a bit more first.  If there is a way to parameterize the BasicBlock/ResidualIdentityBlock logic then this file could be cut in half again and everything reduced to a single ResNet class, which I think would be simpler for people new to computer vision.  This torchvision logic is nice: https://github.com/pytorch/vision/blob/50d54a82d1479ffb6dd7469ed05fccdf290a1d84/torchvision/models/resnet.py#L216
Let me know!

re 1) Not sure if this is just my system (running semi-current tf-swift master), but the existing version in models repo takes 43 seconds to compile here. Using this code takes ~3-4 seconds to compile.

This is expected because the compiler is bugged. The implementation detail is that we've turned off a part of the Swift compiler that optimizes large structures in order to suppress other bugs. We are actively working on this and expect this to be fixed within a week or two.

2. could you make imageSize optional

This would be a good change. The reason imageSize exists at all is to distinguish between ResNets designed for CIFAR image sizes and those designed for ImageNet sizes; my impression is that the ImageNet-sized networks also work fine for images of other similar sizes.

I can work on coming up with a way to add an input type to specify cifar, imagenet and generic variants.  In the same vein, can come back to refactoring things more down the road.


RF12 support for new features in SPI library

Hi!
I would like to know if you will change the RF12 library to support the new features of SPi library as explained here: http://www.dorkbotpdx.org/blog/paul/spi_transactions_in_arduino
This new features seems solve many problem of conflict between SPI devices.
Best regards.

Sounds like a good idea. I know Paul Stoffregen looked into this for the RF12 library quite a while ago, but I wasn't sure at the time whether it'd be stable and ready for prime time. Looks like this would be an excellent improvement. I'd welcome a pull request to add this, if anyone gets to it before I can look into it.

I would like to help but I'm not good to work with core. :(


Fix #53 Unable to delete file on windows

:pushpin: References

Issue: https://github.com/pedrovgs/Shot/issues/53
Probably this one too https://github.com/pedrovgs/Shot/issues/244

:tophat: What is the goal?
Attempt to fix issues with gradle process locking files on windows.
How is it being implemented?

Move the removeProjectTemporalScreenshotsFolder call below generateVerificationReport to avoid crashing before the report is generated
Use a uid suffix for the pulled screenshot folders
Wrap each delete call in a try/catch to not crash

How can it be tested?
No particular step. But I didn't test yet, I need to try publishing it on my local maven repo or use jitpack.
Note

I kept an empty suffix for the tests to avoid breaking everything. I'm not sure how you'd want to handle it. Maybe add new specific cases for this case?
Small doubt about the System.currentTimeMillis().toString part, first time writing scala, not sure if the timestamp will be generated at each run, or once when the plugin is configured.

The PR is more of a draft/suggestion to help the author rather than a ready-to-merge PR.
If you have feedbacks I can try improving it.

@pedrovgs Not sure what's wrong with the linter. When I run the command locally, every scala file is reported as Files incorrectly formatted 🤔

@pedrovgs It should be fine now.
When I run the command locally, every scala file is reported as Files incorrectly formatted 🤔 (even the ones I didn't edit)
So if it's still not OK, not sure what's wrong.

We should add specific coverage yeap.

I'll see what I can do

Why don't we replace this with a UUID? I think the timestamp is going to be generated for each run btw.

We can


[google_maps_flutter] Out of developers preview, bump to 1.0.0

Bumps the minimally required Flutter SDK to 1.22, starting this version platform views are no longer in developers preview, so the plugin also gets out of developers preview as well.
We also bump the version to 1.0.0 as API stability has been reached.

Redness is because Flutter 1.22 is not released yet, landing on red.


backport #18061 to v2.0.1

Bug is described by #18031.
It is fixed by #18061.
This is a request to backport it to v2.0.1.

Any further review?


policy,labels: Convert more packages to use netip library

Switch most of the handling for CIDR types across the tree over to the
netip.Prefix type, which is a nice cleanup and will help with
simplifying code in various places in future.

/test

Hit #21351, #21433. Re-running each of these tests caused them to pass, so I am considering them as flakes.


Problems with insert (@OneToMany relation)

Hi, I'm newbie using your fantastic lib. I have some troubles inserting some row.
I have this:
@Entity
public interface InitVisitMessage extends Parcelable, Persistable {
    @Key
    @Generated
    int getId();
    @OneToMany(mappedBy = "visitId")
    List<CompanyVisit> getCompanyVisits();
}

and this:
@Entity
public interface CompanyVisit extends Parcelable, Persistable{
    @Key
    long getVisitId();
    long getJobId();
    long getQuoteId();
    @Column(name = "when_date")
    Date getWhen();
    Integer getWhenTimeFrom();
    .....
    .....
    int getStopNumber();
}

I don't want that companyvisit know about initvisitmessage, for that I used mappedby.
First I insert three companyvisits succesfully, but when I did this:
InitVisitMessageEntity initVisitMessage = new InitVisitMessageEntity();
List<CompanyVisitEntity> companyVisitsEntities = convert(companyVisitsArray);
for(CompanyVisitEntity companyVisitEntity : companyVisitsEntities){
     initVisitMessage.getCompanyVisits().add(companyVisitEntity);
}
data.insert(initVisitMessage).blockingGet();

I got this:
Caused by: android.database.sqlite.SQLiteException: near "InitVisitMessage": syntax error (code 1): , while compiling: insert into InitVisitMessage
The log is not very usefull... :(
Thanks!

you've forgotten the opposite direction for your relation. you'll need @ManyToOne in CompanyVisit...

This is THE problem, I don't want to have a attribute in CompanyVisit for
that...
2017-08-14 6:57 GMT-03:00 Marco Schmitz<EMAIL_ADDRESS>
you've forgotten the opposite direction for your relation. you'll need
@manytoone https://github.com/manytoone in CompanyVisit...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/requery/requery/issues/658#issuecomment-322149564,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA08iXwSqPj41o8fS3xuNYSOS3_yd-3tks5sYBoGgaJpZM4Ozds4
.

--
Saludos, Daniel Goldberg.

Looks like your InitVisitMessage doesn't have any columns. Which doesn't make much sense from a database design perspective. The insert fails because there are no rows to insert. A work around would be to use a non-generated key for InitVisitMessage hope that makes sense thanks!

It's funny because I don't want to think in a "database design perspective". I have my objects and want to save them. I expect that ORM makes this without my effort (or just a little).
Anyway I don't understand the difference between a generated and non-generated key in this situation and why it will work. could you please explain me?
ps: The msgError is not so cool... 😞

Sure but ultimately your code does have to be representable into the database. In this case a non-generated key is a key that you set in the object, rather than it being generated by the database. A single table with only generated keys typically cannot be inserted in most databases hence the error. This should generate a better error in the latest version, which version are you using?

1.4.0
Thanks for your reply!


Background not rendering correct color

Hey fellow Patrick! Love the theme!! I'm noticing that the background doesn't look quite right on mine. Any ideas what the cause might be?

Also, the variable or string under cursor always has a squigly line underneath, and sometimes has a different color than when not focused. Normally the squigly line only shows up when there is a linting or lsp issue.

This is how I install and configure darkearth.

Hi, I'm glad you like the theme!
The coloring issue is related to tmux, you have to explictly enable true-colors in your tmux config file.
This is what mine looks like:
set -g default-terminal 'screen-256color'
set -as terminal-overrides ',xterm*:RGB'

The top line may need to be changed to fit with your terminal, but I've been using this with wezterm and kitty for a while without any issues.
As for the underline issue, does that happen when you open neovim outside of tmux? I'm not entirely sure what causes that, but it may also be fixed by setting the default-terminal option.

Turns out this isn't an issue with just this theme. Other themes have issues displaying color correctly. Kanagawa for example:
In tmux:

Outside tmux:

However, this issue is only present on my linux machine (arch / kde / wayland). On OSX these themes work perfectly fine. I am running alacritty on both. My config is identical on both. Perhaps i need to set a different term value in alacritty on linux or a different value for the two settings you mentioned in tmux. I tried the values you suggested but those did not work in my case.
I agree with marking this as not a bug for this theme. I will close this ticket. However, once I find a solution I'll try to remember to come back and mention the fix here in case others have issues and find there way here. If i don't remember to, at least others have links here to my dotfiles where the fix will live.

Also, using the kanagawa theme here is what it looks like when my cursor is over a variable in lua

And over a string

I'm guessing this highlighting has something to do with treesitter or treesitter-text-objects. I'm not sure. Either way, I think it would be nice if the darkearth theme had something similar instead of using a squiggly line underneath. That's just my personal preference though. I find the squigly and highlighting very distracting as it looks to me like there is an issue when there isn't.
Maybe i'll re-open this just for the highlight display issue.
I've tested it on osx and linux, with lua and ruby files.

Regarding your tmux config, the problem might be coming from the set -sa terminal-features ',tmux256color:RGB' line, as I think that tells tmux to use a 256-color palette rather than a truecolor palette.
Since you use alacritty, you could try this in its place.
set -as terminal-overrides ",alacritty*:Tc"

As for the squiggly underline, I'm still unsure about where that is coming from (and I haven't been able to replicate it), can you run :Inspect over one of the places where it is happening and post the output?

Adding that setting to my tmux config fixed the issue on linux thank you. I still need to test it out on osx.
Here is the output of :Inspect:

Treesitter
  - @variable.lua links to Identifier lua
  - @property.lua links to Field lua
  - @function.lua links to Function lua

Semantic Tokens
  - @lsp.type.property.lua links to Identifier priority: 125

Extmarks
  - LspReferenceWrite vim_lsp_references

Press ENTER or type command to continue

This is the file from the screenshot.
I have a couple different nvim configurations I'm working with, but this is the one I have been using in these screenshots. Link.

I just pushed an update (680dd3b) that should switch the squiggles to underlines.
Try updating and let me know if everything looks right for you.

Muuuuuch better! Thank you!!


Initial commit of regard measurement

This code is pretty clunky, so I would love thoughts about how to get the list comprehension to work better, @mathemakitten !
Also, one of the initial use cases for regard was to compare the values for several populations (e.g. men and women, for instance), so would it make sense to have either the default or optional behavior to be something like:
results = regard.compute(group1 = ['he is a soldier', 'the men are violent', 'George is a gangster'], group2= ['she is a nice girl', 'the women are housewives', 'Kelly is an actress'])

and then the result would be the difference in regard between the two groups?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Changed predictions to data and integrated your other suggestions! Thanks @lvwerra :hugs:


Can't import modules from index.js

Following the Readme instructions, I am trying to import the modules with import { MapView, MapTypes, Geolocation, Overelay } from 'react-native-baidu-map however, I am getting the following error:
error: bundling failed: Error: Unable to resolve module `./MapView` from `/Users/***/***/node_modules/react-native-baidu-map/index.js`: The module `./MapView` could not be found from `/Users/***/***/node_modules/react-native-baidu-map/index.js`...

I believe this was introduced in a recent commit when the path segment ./js was removed. ( https://github.com/lovebing/react-native-baidu-map/commit/03d15bf063493e2481e680c6f03e72b9aa2bfd27#diff-168726dbe96b3ce427e7fedce31bb0bcL17 )

Thanks, this issue was fixed.


Update authentication-type-json-file-543fbd6.md

removed trailing comma in JSON file

Hi @dvankempen,
Thank you so much for noticing this! I have removed the comma from the sample.
Best regards,
Ekaterina


add parallel tempered sampler

Great!

API question: I'm not sure if using ntemps to switch between samplers is intuitive. Does ntemps=1 with the PTSampler give the same results as using the EnsembleSampler?

If you specify ntemps=1 then the PTSampler runs a single EnsembleSampler on
the posterior with a temperature that does not modify the posterior, so the
results should be the same.
On Thu, Jul 21, 2016 at 11:25 AM, Kyle Barbary<EMAIL_ADDRESS>wrote:

API question: I'm not sure if using ntemps to switch between samplers is
intuitive. Does ntemps=1 with the PTSampler give the same results as
using the EnsembleSampler?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sncosmo/sncosmo/pull/152#issuecomment-234340964, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACpC4HYcsz2Z4IWcMJiWgcLDQrm96vshks5qX7mwgaJpZM4JRFJl
.

--
Danny Goldstein
http://astro.berkeley.edu/~dgold/

I think we should add a keyword sampler that specifies the sampler. ntemps could then be set to some "reasonable" default.

Done. I changed the API and somewhat arbitrarily initialized ntemps to 4.


[Feature]: add a card for blockchain development in resource page

Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

Hai i would love to wok on this as a part of hacktober fest 2023. Please assign to me

Hello , I hope you're doing well. I'm interested in contributing to this task. I am eager to help in any way I can and believe I can make valuable contributions to the project. I humbly request you to assign me with the task.

@vamsi-spoidey7 assigned to you


fix styling bug in menu editor

The fix allows the Reports tree in the Menu Editor to expand fully by replacing the fieldsets and sized DIVs with responsive columns.
https://bugzilla.redhat.com/show_bug.cgi?id=1346765
Old

New

@miq-bot assign @dclarizio

@miq-bot add_label wip

@miq-bot remove_label wip

@dclarizio please review

Darga backport details:
commit ca32093da54807b0b07c0fe3bdeca2820ef875ef
Author: Dan Clarizio<EMAIL_ADDRESS>Date:   Wed Jul 13 15:06:52 2016 -0700

    Merge pull request #9656 from epwinchell/menu_editor_fix

    Fix styling bug in menu editor
    (cherry picked from commit 0c9800d4201a8ae831e8dfb395d63349b638a37f)

I really don't like this change.
We are trying to get some meaning to the code on server so that it's readable and maintainable. One of the things we try to do is to write methods such as def show_menu instead of setStyle('menu_div', 'visible').
It is quite an effort to figure out what was the intent of the code if you have code full of these cryptic calls. It takes hours and days and lot of step by step changes to get the code to readable and understandable state.
In this change there are generic methods added addClass and removeClass and the purpose of those methods is to enable/disable a single element on the screen.
So I have to ask, do we need to support a generic way to add/remove class through from server side to the client? I think we don't need that and don't want that. It's a move in opposite direction that we want to be moving.
The smallest of the issues here is that this code adds odd https://en.wikipedia.org/wiki/Hungarian_notation style names to our code even though Rubocop is complaining.
I suggest that we revert this change and work on a different solution to the issue for master.
We can keep the change in Darga.

Ping @epwinchell, @dclarizio .

I think that if it's really needed to change the style of the property dynamically, we should have a javascript function under ManageIQ namespace somewhere to do that. Such as ManageIQ.reportMenuEditor.disableMouseEvents (not sure if it's the proper name, just guessing what's happening here).
Then this function can be called if really necessary from the ExplorerPresenter. The same function would be called from Javascript code and (maybe) reused whan that screen is converted to Angular.
Something like that. I'd ask @skateman or @himdel or @karelhala if they can find a better solution for this.

I don't like the scrolling of whole page, what if user will expand the tree too much? He'll loose context of managing folders and accordions. also there is wrong usage of col-sm-x. This is for setting layout of page for small screens, I understand that it will set the height to some percentage number and allows to have 2 elements in same row, but you should use them in same div grid system.
But these are just some UX/UI problems which I see, it might be preferable to stretch the tree to whole page, but then I don't understand the need of dynamical changes.
In case someone would be interested in scrollbar for container, here is some draft (3 css changes):

@h-kataria See Martin's comments


How to web publish to Azure without publishing the virtual environment?

I would like to publish my ptvs based project to Azure, but without uploading my virtual environment.
Here: https://azure.microsoft.com/en-us/documentation/articles/web-sites-python-configure/ it is said that "Packages listed in requirements.txt will be installed automatically in the virtual environment using pip. This happens on every deployment, but pip will skip installation if a package is already installed."
I however could not get that to work, using PTVS django project and the VS web publish tool. By default, the web publish tool picks up every files in the project, including the virtual env. So I went ahead and removed my virtual env folder from being published by editing my deployment .pubxml. The publishing goes ok, but apparently the python server doesn't get up and running and all I get is a server error.
Would there be a blog entry/documentation how to do this properly?

I don't have the documentation links handy, but the short answer is:

git deployment does not upload virtualenv files
VS deployment does upload virtualenv files

Because of technical limitations around how these are implemented, we can't really swap these - you get one or the other (but at least you get to choose).

Arg! Wish I would have read the manual. It's indeed mentioned here:
https://github.com/Microsoft/PTVS/wiki/Web-Project#templates
But the short answer above was most useful. Thanks.


Apply clang-tidy modernize-use-override check

New PR for https://github.com/ripple/rippled/pull/2529 so jenkins runs

Jenkins Build Summary
Built from this commit
Built at 20180515 - 18:03:14
Test Results

Build Type
Log
Result
Status

docs
logfile
1 cases, 0 failed, t: 2s
PASS :white_check_mark:

clang.debug.unity
logfile
1021 cases, 0 failed, t: 250s
PASS :white_check_mark:

coverage
logfile
1021 cases, 0 failed, t: 619s
PASS :white_check_mark:

clang.debug.unity, PARALLEL_TESTS=false
logfile
1021 cases, 0 failed, t: 480s
PASS :white_check_mark:

gcc.debug.unity
logfile
1021 cases, 0 failed, t: 243s
PASS :white_check_mark:

msvc.debug
logfile
1017 cases, 0 failed, t: 564s
PASS :white_check_mark:

clang.debug.nounity
logfile
1019 cases, 0 failed, t: 657s
PASS :white_check_mark:

clang.release.unity
logfile
1020 cases, 0 failed, t: 330s
PASS :white_check_mark:

gcc.debug.nounity
logfile
1019 cases, 0 failed, t: 676s
PASS :white_check_mark:

gcc.release.unity
logfile
1020 cases, 0 failed, t: 350s
PASS :white_check_mark:

gcc.debug.unity -Dstatic=true
logfile
1021 cases, 0 failed, t: 241s
PASS :white_check_mark:

msvc.debug, PROJECT_NAME=rippled_classic
logfile
1017 cases, 0 failed, t: 1170s
PASS :white_check_mark:

msvc.release
logfile
1016 cases, 0 failed, t: 504s
PASS :white_check_mark:

Codecov Report

Merging #2533 into develop will decrease coverage by <.01%.
The diff coverage is 62.06%.

@@             Coverage Diff             @@
##           develop    #2533      +/-   ##
===========================================
- Coverage    70.66%   70.66%   -0.01%
===========================================
  Files          696      696
  Lines        54405    54405
===========================================
- Hits         38448    38444       -4
- Misses       15957    15961       +4

Impacted Files
Coverage Δ

src/ripple/rpc/impl/ServerHandlerImp.h
100% <ø> (ø)
:arrow_up:

src/ripple/server/impl/Door.h
80.59% <ø> (ø)
:arrow_up:

src/ripple/nodestore/impl/BatchWriter.h
100% <ø> (ø)
:arrow_up:

src/ripple/protocol/InnerObjectFormats.h
100% <ø> (ø)
:arrow_up:

src/ripple/protocol/TxFormats.h
100% <ø> (ø)
:arrow_up:

src/ripple/nodestore/Database.h
100% <ø> (ø)
:arrow_up:

src/ripple/app/main/Application.cpp
58.16% <ø> (ø)
:arrow_up:

src/ripple/protocol/LedgerFormats.h
100% <ø> (ø)
:arrow_up:

src/ripple/json/JsonPropertyStream.h
0% <ø> (ø)
:arrow_up:

src/ripple/json/json_writer.h
100% <ø> (ø)
:arrow_up:

... and 26 more

Continue to review full report at Codecov.

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

Seems like this one should be good to go now

Squashed and slightly reordered and reworded the commits (the soci commit commit should be first and should be its own commit)

In 1.1.0-b2


Proposal: Clean, Merge, Standardize https://github.com/amphp

Thank you all for this amazing product
Working with Amp (v1) I encounter some shortcomings (personal for me) may be someone else encounter same.
2.1. Amp has amphp/socket but (amphp/aerys && amphp/artax) don't use it (or partial use, with some black magic hacks)
2.2. amphp/artax has https://github.com/amphp/artax/blob/master/lib/Uri.php and there is also amphp/uri
2.3. Stream Interface is defined in amphp/amp but we have amphp/stream
2.4. amphp/websocket same black magic as 2.1
2.5. To be continued ...
As I understand amphp/socket must be base component where other components that work with network sockets use it, and if we find any bugs in amphp/socket patch all at once, but most of components use network sockets internally with some black magic, and with personal implementation (optimizations), I don't think that performance from such black magic worth it, personally for me, as Amp user, just make things more complicated.

What are the black magic hacks you're talking of? aerys doesn't use socket for performance reasons, artax doesn't use socket mainly because it's older than the socket additions like Client.
The uri package you're talking about is completely extracted from Artax, but that process isn't finalized yet. We have to fix a few things in uri and then artax v3 will use it.
stream is the actual stream abstraction, we should maybe find a better name for Amp\Stream.
Why must socket be the base component?

@kelunik  I really appreciate all you are doing, I just comment my personal problems I encounter when using Amp, I think you must Standardize or do something like this

@kelunik "Why must socket be the base component?", I only refer to network sockets, if component use them.
P.S: Sorry for my English, there may be some misunderstandings

In general, I avoid using the amp/socket Server component in libraries. The Server class of amp/socket is not designed for complete control over watcher and socket, which you may need for rate-limiting etc. It is fine for low-traffic private endpoints, but not for servers open to wide public needing to potentially withstand larger amounts of traffic.
The client however is totally fine for use in our libraries, and will be used in future I guess.

@bwoebi May be we need a new component that will permit "complete control over watcher and socket, which you may need for rate-limiting etc."
After some code review I find that amphp/websocket && amphp/aerys and may be other components, are using ~ same network sockets, but with different implementations, and for my projects I need just a network socket server that will do ~ the same, and I need to rewrite same code. I think this is unproductive, there are plenty of stones in PHP sockets/streams + OS stones and limits (like: file descriptors, nf_conntrack_max, etc. ..) but this is out of scope here.
My opinion is to write a network socket server that will solve all needs from amphp/websocket && amphp/aerys, this will be extremely useful and productive

We do not need that component, that component is basically provided by amp itself. We do not win anything by putting more layers around it. We basically need all functionality Amp provides and cannot abstract anything away there. You do not end up saving any real code here.
AFAIK @trowski wanted to write something which couples socket management and parsing in one thing, at which point we would perhaps see some real thing abstracted away, where it becomes helpful.

@bwoebi Ups, I mean amphp/aerys, Thank you

@bwoebi @umbri I recently pushed what I was working on with the socket parser here in the parser branch of amphp/socket.
The namespace of amphp/stream is Amp\ByteStream. Perhaps the package should be named as such, amphp/byte-stream, or we should consider a different name for Amp\Stream.
@umbri You can use Amp\Socket\Server in the amphp/socket package to create a simple socket server. I think this will do most of what you want to do. Aerys doesn't really use any "black magic," it just doesn't use that class. If you look at the v2 implementation of Amp\Socket\Server, you'll see that it's actually rather trivial. Reproducing that logic where finer-grained control is needed is not a big deal.
One API I don't care for is Amp\Message. I think any usages of this class should be an instance of Amp\ByteStream\ReadableStream. We could then write any other API's around the stream interfaces, making interoperability between packages easier.

@trowski @bwoebi @kelunik I think we can close this.
Thank you all.


Update documentation

Description
Added reference to i18n/ l10n to the end of this documentation as per the conversation in the https://github.com/json-schema-form/angular-schema-form/issues/865
Fixes Related issues

https://github.com/json-schema-form/angular-schema-form/issues/865

Checklist

[x] I have read and understand the CONTRIBUTIONS.md file
[x] I have searched for and linked related issues
[x] I have created test cases to ensure quick resolution of the PR is easier
[x] I am NOT targeting main branch
[x] I did NOT include the dist folder in my PR

@json-schema-form/angular-schema-form-lead

@shravanmahankali thank you :)


remove deprecated MixerAddress

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: kyessenov
If they are not already assigned, you can assign the PR to them by writing /assign @kyessenov in a comment when ready.
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:

pilot/OWNERS

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

Hi @islinwb. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
ee5514eab3026dc12b30e52ccaa458580fa5ef68
link
/test istio-unit-tests

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

@ayj Thanks! I'll update it.


Support for editor version 1.61c/1.61b

Will a new release be made available for versions 1.61c or 1.61b? Would it be possible to add the Effekseer plugin to the Godot Asset Store?

We are working on 1.61c support now.
it will be released soon.
And we are considering to send to the Godot Asset Library.
Thanks!

Superb thank you so much for the reply!


Installation on Mac OSX failed via brew.sh

Error log
❯ brew install --HEAD -s curl.rb
Error: Failed to load cask: curl.rb
Cask 'curl' is unreadable: wrong constant name #<Class:0x00007fcce090dfa8>
Warning: Treating curl.rb as a formula.
==> Cloning https://github.com/curl/curl.git
Updating /Users/loll/Library/Caches/Homebrew/curl--git
==> Checking out branch master
Already on 'master'
Your branch is up to date with 'origin/master'.
HEAD is now at 02dfce183 scripts: Fix typo in release-notes instructions
==> ./buildconf
==> git clone --recursive https://github.com/cloudflare/quiche
==> cargo build --release --features pkg-config-meta,qlog
==> ./configure --prefix=/usr/local/Cellar/curl/HEAD-02dfce1 --with-secure-trans
Last 15 lines from /Users/loll/Library/Logs/Homebrew/curl/04.configure:
checking for libnghttp2 options with pkg-config... found
configure: -l is -lnghttp2
configure: -I is -I/usr/local/Cellar/nghttp2/1.43.0/include
configure: -L is -L/usr/local/Cellar/nghttp2/1.43.0/lib
checking for nghttp2_session_set_local_window_size in -lnghttp2... yes
checking for nghttp2/nghttp2.h... yes
checking for pkg-config... (cached) /usr/local/Homebrew/Library/Homebrew/shims/mac/super/pkg-config
checking for libngtcp2 options with pkg-config... no
checking for pkg-config... (cached) /usr/local/Homebrew/Library/Homebrew/shims/mac/super/pkg-config
checking for quiche options with pkg-config... found
configure: -l is -lquiche
configure: -I is -I/private/tmp/curl-20210712-12162-im3znt/quiche/include
configure: -L is -L/private/tmp/curl-20210712-12162-im3znt/quiche/target/release
checking for quiche_connect in -lquiche... no
configure: error: couldn't use quiche

Do not report this issue to Homebrew/brew or Homebrew/core!

Traceback (most recent call last):
	25: from /usr/local/Homebrew/Library/Homebrew/build.rb:229:in `<main>'
	24: from /usr/local/Homebrew/Library/Homebrew/build.rb:133:in `install'
	23: from /usr/local/Homebrew/Library/Homebrew/utils.rb:550:in `with_env'
	22: from /usr/local/Homebrew/Library/Homebrew/build.rb:138:in `block in install'
	21: from /usr/local/Homebrew/Library/Homebrew/formula.rb:1260:in `brew'
	20: from /usr/local/Homebrew/Library/Homebrew/formula.rb:2363:in `stage'
	19: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/forwardable.rb:230:in `stage'
	18: from /usr/local/Homebrew/Library/Homebrew/resource.rb:91:in `stage'
	17: from /usr/local/Homebrew/Library/Homebrew/resource.rb:116:in `unpack'
	16: from /usr/local/Homebrew/Library/Homebrew/resource.rb:199:in `mktemp'
	15: from /usr/local/Homebrew/Library/Homebrew/mktemp.rb:63:in `run'
	14: from /usr/local/Homebrew/Library/Homebrew/mktemp.rb:63:in `chdir'
	13: from /usr/local/Homebrew/Library/Homebrew/mktemp.rb:63:in `block in run'
	12: from /usr/local/Homebrew/Library/Homebrew/resource.rb:117:in `block in unpack'
	11: from /usr/local/Homebrew/Library/Homebrew/download_strategy.rb:102:in `stage'
	10: from /usr/local/Homebrew/Library/Homebrew/download_strategy.rb:110:in `chdir'
	 9: from /usr/local/Homebrew/Library/Homebrew/resource.rb:121:in `block (2 levels) in unpack'
	 8: from /usr/local/Homebrew/Library/Homebrew/formula.rb:2383:in `block in stage'
	 7: from /usr/local/Homebrew/Library/Homebrew/utils.rb:550:in `with_env'
	 6: from /usr/local/Homebrew/Library/Homebrew/formula.rb:2384:in `block (2 levels) in stage'
	 5: from /usr/local/Homebrew/Library/Homebrew/formula.rb:1267:in `block in brew'
	 4: from /usr/local/Homebrew/Library/Homebrew/build.rb:178:in `block (2 levels) in install'
	 3: from /Users/loll/curl.rb:70:in `install'
	 2: from /usr/local/Homebrew/Library/Homebrew/formula.rb:2154:in `system'
	 1: from /usr/local/Homebrew/Library/Homebrew/formula.rb:2154:in `open'
/usr/local/Homebrew/Library/Homebrew/formula.rb:2218:in `block in system': Failed executing: ./configure --disable-debug --disable-dependency-tracking --disable-silent-rules --prefix=/usr/local/Cellar/curl/HEAD-02dfce1 --with-secure-transport --without-ca-bundle --without-ca-path --with-ssl=/private/tmp/curl-20210712-12162-im3znt/quiche/deps/boringssl/src --with-quiche=/private/tmp/curl-20210712-12162-im3znt/quiche/target/release --enable-alt-svc (BuildError)
	5: from /usr/local/Homebrew/Library/Homebrew/brew.rb:155:in `<main>'
	4: from /usr/local/Homebrew/Library/Homebrew/brew.rb:167:in `rescue in <main>'
	3: from /usr/local/Homebrew/Library/Homebrew/exceptions.rb:509:in `dump'
	2: from /usr/local/Homebrew/Library/Homebrew/exceptions.rb:455:in `issues'
	1: from /usr/local/Homebrew/Library/Homebrew/exceptions.rb:459:in `fetch_issues'
/usr/local/Homebrew/Library/Homebrew/utils/github.rb:60:in `issues_for_formula': undefined method `full_name' for nil:NilClass (NoMethodError)

Can you try https://github.com/cloudflare/homebrew-cloudflare/pull/29 ??

It works.
Thanks for your help


Added 'clip' value for 'overflow' property

Description

The 'clip' value was not present in bootstrap for 'overflow' property. The changes in this PR builds three new classes viz. 'overflow-clip' 'overflow-x-clip' and 'overflow-y-clip' with value 'clip' set for 'overflow', 'overflow-x' and 'overflow-y' respectively.
Motivation & Context

I ran into a situation where overflow: clip was required for an HTML element and I discovered overflow-clip class is not present in Bootstrap. So I added it.

Learn more about the 'overflow: clip': https://www.w3.org/TR/css-overflow-3/#overflow-properties

Type of changes

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

Checklist

[x] I have read the contributing guidelines
[x] My code follows the code style of the project (using npm run lint)
[x] My change introduces changes to the documentation
[x] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[x] All new and existing tests passed

Live previews

https://deploy-preview-39686--twbs-bootstrap.netlify.app/docs/5.3/utilities/overflow/

Related issues

Thanks for this PR @HimDek
I postpone the decision to the v6. As mentioned in https://github.com/twbs/bootstrap/issues/38240, we can't do that right now because of the browser compatibility. In the meantime, folks can use the utility API for adding it.