Aot compiler prototype

I'm overall pretty pleased with the prototype. I think the main thing I want to think about some more is the config file. I think it's very usable as-is, but I worry users may think it's too verbose. If we go for a config file, is there a way to have only one section per kernel?
Another option is to not use a config file and have the user manually compile all possible options before "linking" them.
ttc file.py --kernel _matmul --sig "f32*,f32*,f32*,i32,i32,i32,i32,i32,i32" --div=a_ptr:16 --div=b_ptr:16 --div=c_ptr:16 --div=stride_xm:8 --output-dir matmul
ttc file.py --kernel _matmul --sig "f32*,f32*,f32*,i32,i32,i32,i32,i32,i32" --div=a_ptr:1 --div=b_ptr:16 --div=c_ptr:16 --div=stride_xm:1 --output-dir matmul
ttld matmul/*.o

One way to do this is to have all the calls to tcc write some metadata in comment at the top of the file, which the linker would then use to generate "dispatching" functions. I suspect this approach would work pretty well with cmake/scons, but how would this work with common rust build systems?

I'm overall pretty pleased with the prototype. I think the main thing I want to think about some more is the config file. I think it's very usable as-is, but I worry users may think it's too verbose. If we go for a config file, is there a way to have only one section per kernel?

Agree on the verbosity thing, the multiple section per kernel is a toml thing (the YAML version doesn't have that, but more verbose in my opinion)

Another option is to not use a config file and have the user manually compile all possible options before "linking" them.
ttc file.py --kernel _matmul --sig "f32*,f32*,f32*,i32,i32,i32,i32,i32,i32" --div=a_ptr:16 --div=b_ptr:16 --div=c_ptr:16 --div=stride_xm:8 --output-dir matmul
ttc file.py --kernel _matmul --sig "f32*,f32*,f32*,i32,i32,i32,i32,i32,i32" --div=a_ptr:1 --div=b_ptr:16 --div=c_ptr:16 --div=stride_xm:1 --output-dir matmul
ttld matmul/*.o

One way to do this is to have all the calls to tcc write some metadata in comment at the top of the file, which the linker ttld would then use to generate "dispatching" functions. I suspect this approach would work pretty well with cmake/scons, but how would this work with common rust build systems?

I think the writing meta-data idea is a good direction.  Though I'm not following your example. Could you say more about it?
They way I see it we have 2 kinds of configs, "slow" and "fast". "slow" being the input data types. I thought about using type annotations in the python code (e.g. x_ptr: '<f32*>'). The "fast" config we can pass as cmd arguments, and maybe have a config file if you want to do some fancy auto size generation.
we can also have something that tries to infer as much as possible from a script and generates a config file (that might need some manual additions)

Replaced by #490


Change $

Hello, quick question: would it be possible to have a credits symbol instead of the dollar sign for skill purchases? It would feel more Star Wars-like.

 Having the symbol be customizable is a better, albeit likely more complex and hard to implement, solution.


How to broadcast  Audio and Video at once？

I find  broadcast  Audio or broadcast  Video ,but how to broadcast  Audio and Video at once?
build two RTCPeerConnection, one transfer Audio  and the other transfer Video ?
Have better solution?

Hey @DehaiWang
You can use one PeerConnection! play-from-disk demonstrates how.

@Sean-Der
Hey,
as https://github.com/pion/webrtc/blob/master/examples/broadcast/main.go
i remove
if _, err = peerConnection.AddTransceiverFromKind(webrtc.RTPCodecTypeVideo); err != nil { 	 	panic(err) 	 }
and add
`videoCodecs := mediaEngine.GetCodecsByKind(webrtc.RTPCodecTypeVideo)
if len(videoCodecs) == 0 {
panic("Offer contained no video codecs")
}
videoTrack, err := peerConnection.NewTrack(videoCodecs[0].PayloadType, rand.Uint32(), "video", "pion")
if err != nil {
	panic(err)
}

if _, err = peerConnection.AddTrack(videoTrack); err != nil {
	panic(err)
}

audioCodecs := mediaEngine.GetCodecsByKind(webrtc.RTPCodecTypeAudio)
if len(videoCodecs) == 0 {
	panic("Offer contained no audio codecs")
}

audioTrack, err := peerConnection.NewTrack(audioCodecs[0].PayloadType, rand.Uint32(), "audio", "pion")
if err != nil {
	panic(err)
}

if _, err = peerConnection.AddTrack(audioTrack); err != nil {
	panic(err)
}

`.
And as https://github.com/pion/webrtc/blob/master/examples/broadcast/jsfiddle/demo.js
i set video: true, audio: true.
then  '  Join a Broadcast ', the web video show nothing.

@Sean-Der
Thanks very much.
In the web ,i add
      pc.addTransceiver('video');
      pc.addTransceiver('audio')
and it work fine.

after add
pc.addTransceiver('video');
pc.addTransceiver('audio')；
in web js  ,
then web video only play audio;

I can call AddTrack on the PeerConnection as many times as Iwant.But there is a question，different browser has different payload type. For exsample，chrome is 102:h264,but firefox is 126:h264. If set the answer,102:h264,the firefox will not show the video.So is there a solution? Maybe change the payload type before Track.WriteSample ?

Hey @fayfive
This is no longer an issue! In /v3 we internally manage the SSRC/PayloadType for you

And now，how to Achieve One-to-many?  I create a new peer while a new request, but the cpu performance is full.
Is the function that manage the SSRC/PayloadType in the v3 beta 11?

@fayfive How many PeerConnections are you serving when you reach resource exhaustion? Is this on a specific host?
To see an example of fanout we have https://github.com/pion/webrtc/tree/master/examples/broadcast and https://github.com/pion/example-webrtc-applications/tree/master/sfu-ws

@Sean-Der
I download v3 and see the sample.But it dose not work in local network. I usb nginx to see the web.  I set peerConnectionConfig := webrtc.Configuration{}, is there any problem?

@Sean-Der
I download v3 and see the sample.But it dose not work in local network. I usb nginx to see the web.  I set peerConnectionConfig := webrtc.Configuration{}, is there any problem?


Linkfix: Biztalk (2021-08) - 1

This PR is the result of running a Link Repair script on the included content. This script is primarily being run to clean up links to function correctly in Air Gapped Clouds (AGC). Here's a breakdown of what the script that generated the changes in this PR fixes:

docs.microsoft.com Fully Qualified Domain Name (FQDN) Links to either Relative (if in same Repo/DocSet/ContentSet) and Site Relative if not
azure.microsoft.com/documentation/articles that reflect to Docs to either Relative (if in same Repo/DocSet/ContentSet) and Site Relative if not
All known flavors of MSDN/TechNet domains (we know of 8 or 9 now) that reflect to Docs to either Relative (if in same Repo/DocSet/ContentSet) and Site Relative if not

This also includes cleanup of the appended query string for MSDN (redirectedfrom=MSDN).

Fixes articles that are redirected in .openpublishing.redirection.json and updates the link to the current final location (this has a lot of customer usability fixes).

Please note the Contributor Guide: Links has been updated with the following link-type preference order:
By order of preference, links hosted on Docs should be Relative if they are in the same repository and docset. If they are in a different docset, even if in the same repository, they should be Site Relative. Links to content hosted on Docs shouldn't use a complete URL, otherwise known as Fully Qualified Domain Names (FQDN). Using a complete URL from Docs to other content on Docs will cause that link to be non-functional in air-gap environments.

Docs Build status updates of commit 0c2f5e5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/core/considerations-for-installing-biztalk-server-on-a-windows-server-cluster2.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/adding-artifacts-to-an-application.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/best-practices-for-managing-certificates2.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/best-practices-for-monitoring.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/best-practices-for-updating-applications.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/biztalk-server-2010-hyper-v-guide.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/biztalk-server-2010-operations-guide.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/biztalk-server-64-bit-support1.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/biztalk-server-roles-and-responsibilities.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/bottlenecks-in-the-biztalk-server-tier.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-best-practices-to-install-and-configure-biztalk-server-on-hyper-v.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-configuring-internet-information-services.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-configuring-sql-server.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-configuring-windows-server.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-deploying-an-application.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-getting-started-with-biztalk-server.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-increasing-availability-with-disaster-recovery.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-maintaining-and-troubleshooting-biztalk-server-databases.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-measuring-performance-on-hyper-v.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-monitoring-biztalk-server-with-operations-manager-2007.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-optimizing-performance-on-hyper-v.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-performing-daily-maintenance-checks.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-performing-monthly-performance-checks.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-performing-weekly-maintenance-checks.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-performing-weekly-performance-checks.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-planning-for-operations-in-a-secure-environment.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-providing-high-availability-with-fault-tolerance-or-load-balancing.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-updating-an-application-using-side-by-side-versioning.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-updating-an-assembly.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-updating-an-orchestration-using-side-by-side-versioning.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/checklist-updating-artifacts-in-a-biztalk-application.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/clustering-receiving-hosts.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/clustering-the-master-secret-server.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/configuring-a-dedicated-tracking-host.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/configuring-biztalk-server-log-shipping.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/configuring-certificates-for-mime-or-smime-messages.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/configuring-hosts-and-host-instances.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/configuring-the-source-system.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/considerations-while-using-biztalk-server-on-a-64-bit-windows-operating-system.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/create-a-new-management-pack-for-customizations.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/creating-an-application.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/defining-auto-growth-settings-for-databases.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/deploying-an-application.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/deploying-an-assembly.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/deploying-and-exporting-an-application.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/designating-a-new-master-secret-server-manually.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/disabling-windows-server-2003-sp1-and-sp2-denial-of-service-checking.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/establishing-performance-criteria.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/general-biztalk-server-optimizations1.md
:white_check_mark:Succeeded
View

biztalk/technical-guides/general-biztalk-server-optimizations2.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

#sign-off (bulk updates to links)


API supports git archive?

The title says the most, but i basically want to use the archive function to fetch out a specific file from a specific repo and in a specific branch, in a nodemodule

No, this functionality is not implemented in NodeGit.

Plans on implementing it?

Actually, I'm not quite sure what you are trying to do. As far as I know, git archive lets you retrieve a tree of files, not a particular file. You seem to want the ability to retrieve the contents of an arbitrary file from some random remote repository.

Yeah, i have found out that archive can do exactly this.
git archive --remote=${url} ${branch} ${path}/${file}
feks you can try
git archive --remote=git@github.com:nodegit/nodegit.git HEAD vendor/openssl/buildinf.h
This will give you the tar of the file. You can then do this:
git archive --remote=git@github.com:nodegit/nodegit.git HEAD vendor/openssl/buildinf.h | tar -xO
This will print the contents of the file. Im using this to fethc jsonfiles from repos during my buildprosess. Currently i have just doen this straight through shelljs, but maybe its faster with this git implementation. And can look smoother in the code.

Closing because found a fix

@vongohren what was the fix?

The fix was what mentioned earlier. Im using this directly through shelljs.


[Update]: Remove the Blog section and add Github Checks

@sanjay-kv I feel that the Blog section is not necessary and is left empty for a long time. With your due permission would like to replace the Blog section and add a section called Github Checks that will educate new contributors about different github checks and how to resolve those when they come across such kind of issue.
I have seen many contributors overlooking the check and their PR not getting considered.
Mentioning some 10 issues that I would like to add :

DCO (Developer Certificate of Origin)

Resolution: Ensure that your commit messages include a "Signed-off-by" line.

CI/CD Pipeline Checks

Resolution: Review the logs from your Continuous Integration/Continuous Deployment (CI/CD) tool (like GitHub Actions, Travis CI, etc.) to identify errors. Fix the code or configuration issues as indicated in the logs.

Code Coverage

Resolution: Increase your test coverage by writing additional tests for untested code paths. Use tools like Istanbul or Coveralls to analyze coverage reports.

Linting Errors

Resolution: Run your linter (e.g., ESLint, Prettier) locally to identify and fix style and syntax issues in your code. Ensure your code adheres to the defined style guide.

Security Vulnerabilities

Resolution: Use GitHub's Dependabot or other security tools to identify and update vulnerable dependencies. Regularly check for security advisories related to your project.

Merge Conflicts

Resolution: Pull the latest changes from the base branch and resolve any conflicts in your local branch. Use git merge or git rebase to integrate changes and fix conflicts.

Build Failures

Resolution: Check the build logs for errors. Common issues include missing dependencies or incorrect configurations. Fix the errors and push your changes again.

Test Failures

Resolution: Investigate the failing tests by reviewing the test output. Debug the code or tests as necessary to ensure they pass before pushing your changes.

Branch Protection Rules

Resolution: Ensure that your branch meets the protection rules set by the repository (e.g., requiring reviews, passing checks). You may need to request reviews from team members.

Code Review Requests

Resolution: Address any comments or requested changes from reviewers. Engage in discussions to clarify any points and make the necessary adjustments to your code.

Off Topic Discussion
Also would like to connect with you on Linkedin and take some tips to progress in my Data Engineering learning. I you could guide me it would be of great help to me. For now I have just completed with the learnings and projects related to a role of Data Analyst

Hi , Thats a good insights,
Please watch this video : https://www.loom.com/share/c76fd45e629e40aba53fb1446ab1bdf1?sid=666253d3-ef88-4e76-8b52-b7238af8ab8e

The Blog page looks informative and great and for now I will remove the loader animation.
Just like here we have a section called Githubbadges which shows which badge is awarded when on how much and what kind of contribution. Similarly I wanted to add a section which tells contributors the issues they might face on github while committing, merging for which they can take help from the specific section.
And for the CI/CD pipelining I'm just starting out and learning it so that I can implement in my projects, currently I am not aware of it completely.
And sure I will connect with you over Linkedin chat, thanks for considering my Connection request.

awesome bro, you can do the same.


Minimal synchronous script problem

Running sample synchronous script on recent version (1.2)
from fieldclimate import FieldClimateClient

if __name__ == '__main__':
    client = FieldClimateClient(private_key='xxx, public_key='yyy')
    client.get_user()

raises this error:
...
File "/home/robert/miniconda3/envs/fieldclimate/lib/python3.6/asyncio/base_events.py", line 425, in run_forever
    raise RuntimeError('This event loop is already running')
RuntimeError: This event loop is already running

What can be the reason?

Sorry for the late reply! Need to turn on notifications for my own repository I guess.
get_user() internally opens and closes an asyncio event loop if you're running it with the synchronous syntax. Maybe there's some other code opening a loop that you're not aware of? Personally I have not tested this (or anything) with miniconda, maybe that is the issue.
Using it in a fresh environment works for me:
$ pyenv virtualenv 3.6.8 fc
(fc) $ pip install python-fieldclimate
(fc) $ python << EOF
from fieldclimate import FieldClimateClient
client = FieldClimateClient(public_key="x", private_key="y")
print(client.get_user())
EOF
{'message': 'Unauthorized. The request requires user authentication, refer to documentation for more information.'}

Thank you for reply and your explanation. I will check it.


SIMSBIOHUB-562: Export Survey Data

Links to Jira Tickets
https://apps.nrs.gov.bc.ca/int/jira/browse/SIMSBIOHUB-562
Description of Changes
API
New endpoint that fetches and uploads survey data to s3, and returns a pre-signed url to download it.
APP
New dialog (under survey settings dropdown button) that allows users to execute an export. Currently restricted to project coordinators and collaborators (and system/data admins).
Testing Notes
Pre-req: S3 credentials in .env
Export works.

Codecov Report
Attention: Patch coverage is 12.32877% with 128 lines in your changes are missing coverage. Please review.

Project coverage is 52.68%. Comparing base (2c9d4c4) to head (68f30e7).

Files
Patch %
Lines

api/src/services/export-service.ts
0.00%
64 Missing :warning:

...es/surveys/view/survey-export/SurveyExportForm.tsx
7.69%
24 Missing :warning:

...ject/{projectId}/survey/{surveyId}/export/index.ts
0.00%
18 Missing :warning:

.../surveys/view/survey-export/SurveyExportDialog.tsx
52.00%
12 Missing :warning:

api/src/utils/file-utils.ts
16.66%
5 Missing :warning:

app/src/features/surveys/view/SurveyHeader.tsx
25.00%
3 Missing :warning:

app/src/hooks/api/useSurveyApi.ts
33.33%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##              dev    #1273      +/-   ##
==========================================
- Coverage   53.03%   52.68%   -0.35%
==========================================
  Files         560      564       +4
  Lines       16390    16536     +146
  Branches     2545     2556      +11
==========================================
+ Hits         8692     8712      +20
- Misses       7116     7241     +125
- Partials      582      583       +1

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


pytest file opens on "assert" despite "JustMyCode" set to true.

Hello, my config is bare minimum and I only want my code debugged.
keymap("n", "<Leader>dt", ":lua require('neotest').run.run({strategy = 'dap'})<CR>", opts)
require("neotest").setup({
    adapters = {
        require("neotest-python")({
            dap = { justMyCode = true },
            python = venv_dir .. "python",
            runner = "pytest",
        })
    }
})

Take this test for example:
def test_addition():
    dic = {"name": "cat"}
    json.dumps(dic)
    assert 2 + 3 == 5

When I go past the line with "assert",  then file "~/.local/share/nvim/lazy/neotest-python/neotest_python/pytest.py" and function "pytest_runtest_makereport" opens. I just want to debug my code. Interestingly if I try to "step in" at "json.dumps(dic)", I correctly get this message:
Note: may have been skipped because of "justMyCode" option (default == true).

When I go past the line with "assert"

by doing this you get out of "my code". After this line where error is thrown out of your code, it is catched by the pytest framework.

{ justMyCode = true },

you want DAP to handle your code only.
So they conflict by definition?

When I go past the line with "assert"

by doing this you get out of "my code". After this line where error is thrown out of your code, it is catched by the pytest framework.

{ justMyCode = true },

you want DAP to handle your code only.
So they conflict by definition?

I am inclined to agree with @chaudry-786  here in that the behavior was unexpected for me too.  If justMyCode is set to true, I would expect the debugger to not put me into pytest, since pytest is library code, not my code.  I'd expect to just have the behavior of the test passing or failing with the Note: may have been skipped because of "justMyCode" option (default == true). message displayed.


Fix unordered application registration messages

Motivation

Sending messages to multiple applications could lead to non-deterministic execution outcomes (issue #2615).
This was caused by the incorrect usage of FuturesUnordered, which led to a non-deterministic order of application registration messages.
Proposal

Use FuturesOrdered instead in order to provide a deterministic order.
Test Plan

TODO.
Release Plan

These changes should be backported to the latest devnet branch, then

be released in a new SDK,
be released in a validator hotfix.

These changes should be backported to the latest testnet branch, then

be released in a new SDK,
be released in a validator hotfix.

Links

reviewer checklist
Closes #2615

@jvff Please fill the test plan (it doesn't need to be a new unit test)


Add basic usage to README

Forgive me if this the wrong place to put this.
If we have a really basic example of how to use VX, it might make it a little easier for new folks to get started using it.
I took the SimpleBar chart in the gallery and stripped it down of everything I could so it would be simple enough to just glance over without causing too much information overload.

Lovely! Thank you 🙌


[REQ] Update pattern handling to disallow /pattern/ and /pattern/flags

Is your feature request related to a problem? Please describe.
Update pattern handling to disallow /pattern/ and /pattern/flags
Describe the solution you'd like
Those inputs should be disallowed because the 2020-12 json schema spec describes regexes as the pattern value only and does not include slashes and flags
This was discussed in the json schema slack group
Describe alternatives you've considered

Additional context

No need right now


Enhancement: Give an option to consider indention/block deep.

Don't provide ElasticTabstop over lines with different indent deep.
expected:
f(x, y):
[->]if x > y:
[->][->]temp[->]:= x
[->][->]x[---->]:= y
[->][->]y[---->]:= temp
[->]start[->]:= 1
[->]end[--->]:= 10
[->][...]

unexpected:
f(x, y):
[->]if x > y:
[->][------>]temp[->]:= x
[->][------>]x[---->]:= y
[->][------>]y[---->]:= temp
[->]start[->]:= 1
[->]end[--->]:= 10
[->][...]

Sorry, I should have replied to this earlier.
I did think about doing this back in 2006  as can be seen in the comment section of this blog post:

Without using knowledge of the language being edited (block delimiters, etc) perhaps it could be fixed by taking note of which lines contain leading tabs and treating them slightly diferently.

I've had that idea at the back of my mind for weeks but I'm a little reluctant to implement it. The problem is that I don't want the system to be too complicated or users may think it's unpredictable.

but I never did it!
That was silly of me. I'll make it a configurable setting, and then we can all try it out! 😀

another counter example
multi-line statements
foo(↔ aVeryLongParameter,
↔     anotherParameterWithLongName,
↔     lastParamterWithWiiiideName)
{
	...
}

Another good reason why you want to use this feature is for transitioning. While your text editor may support elastic tabstops and everything looks good, in all other tools it probably won't.
in a text viewer with no elastic tabstop support (tabsize=4)
def foo(x, y):
→   if x > y:
→   →   temp→   = x→# store temp
→   →   x→  = y→# swap
→   →   y→  = temp→# restore temp
→   start→  = 0→# set start
→   end→= 12345→# set end

Now you may be tempted to replace the elastic tabstops in the file with alignment spaces and revert them back in the viewer:
def foo(x, y):
→   if x > y:
→   →   temp··= x······# store temp
→   →   x·····= y······# swap
→   →   y·····= temp···# restore temp
→   start·····= 0······# set start
→   end·······= 12345··# set end

This only works under the following assumptions:

there can be no multiple spaces in strings(!) or the implementation needs language aware features for quotes: print('Hello  ,  World!')
there were no manual alignment spaces inserted by the user (e.g. to align numbers)
padding is larger than 2 (at least for saving in the file)

The best solution for this is to insert a tabs after alignment spaces to denote "spaces aligned elastic tabstops".
in a text viewer without elastic tabstop support (tabsize=4):
def foo(x, y):
→   if x > y:

→   →   temp··→ = x······→  # store temp
→   →   x·····→ = y······→  # swap
→   →   y·····→ = temp···→  # restore temp
→   start·····→ = 0······→  # set start
→   end·······→ = 12345··→  # set end

For the sake of the argument let's assume we actually wanted the equalsigns to line up like this. In a text viewer with no elastic tabstop support and tabsize=6 it will look like this:
def foo(x, y):
→   if x > y:
→   →   temp··→       = x······→  # store temp
→   →   x·····→       = y······→  # swap
→   →   y·····→       = temp···→  # restore temp
→   start···→ = 0······→  # set start
→   end·····→ = 12345··→  # set end

A tabsize=6 is exotic but the general problem here is that the indent tabs change the visual position of any following tabs and under certain circumstances will change the way it was aligned in the elastic tabstops situation.
However with "indentaware spaces aligned elastic tabstops":
def foo(x, y):
→   if x > y:
→   →   temp··= x·····# store temp
→   →   x·····= y·····# swap
→   →   y·····= temp··# restore temp
→   start··= 0······# set start
→   end····= 12345··# set end

using tabs before alignment spaces in a text viewer with no elastic tabstop support (tabsize=4):
def foo(x, y):
→   if x > y:
→   →   temp··→ = x·····→   # store temp
→   →   x·····→ = y·····→   # swap
→   →   y·····→ = temp··→   # restore temp
→   start··→= 0······→  # set start
→   end····→= 12345··→  # set end

using tabs before alignment spaces in a text viewer with no elastic tabstop support (tabsize=6):
def foo(x, y):
→     if x > y:
→     →     temp··→     = x·····→   # store temp
→     →     x·····→     = y·····→   # swap
→     →     y·····→     = temp··→   # restore temp
→     start··→    = 0······→  # set start
→     end····→    = 12345··→  # set end

Now because the elastic tabstops were aligned with the indentation level in the first place their relative position won't change.

@nick-gravgaard because of all these reasons, and most notably because the "braces on same line code style" is so commonplace, I would even argue that this option should be the official definition of elastic tabstops by the Gravgaard Committee.


Add redis storage

Add a redis implementation of a BaseStore

Merging and following up with PR to address remaining issues (since they were not blocking)


People not being able to queue up YouTube playlists

Please tick all applicable boxes.

[x] I am using Python 3.5 or higher (run python --version on the command line)
[x] I have followed the official guides to install the bot for my system
[x] I have updated my dependencies to the latest version using the appropriate update_dependencies script

Which version are you using?

[x] The latest master version (1.9.7)
[ ] The latest review version

What type of issue are you creating?

[ ] Bug
[ ] Feature request
[x] Question

Description of issue
Everyone but me (because I am the owner) cannot queue up YouTube playlists. Whenever they try it gives the error "You don't have permission to use that command. Reasons: You do not have permissions to play media from this service." I have triple checked the permissions.ini file along with options.ini just to make sure. I have allowed the default group to queue up playlists that come from YouTube, Soundcloud, and also generic. I didn't touch the extractors line. So I am questioning if I am not changing a value of something that I should be to allow the default group to queue up playlists.
Steps to reproduce

Simply coded the bot step by step changing or leaving values the way I would want my bot to run. Everything works but this.

Log file
Please attach your MusicBot log file (located at logs/musicbot.log) to this issue. You can do so by dragging and dropping the file here. If you do not include your log file, you WILL be asked to provide one.
musicbot.log

have you made it so they are able to queue playlists in permissions.ini . If you have gone through and changed them make sure "AllowPlaylists" is yes but also check "MaxPlaylistLength" if its green then its fine and doesnt matter, If not then change that to 0 for unlimited songs. Please also check that you have done this in Default or have added there role ID or user ID to the other roles in the right place in permissions.ini

Yes I have gone through these changes within Default.

now just run update.bat and let it finnish then run run.bat. Please also make sure that they are using the right url
https://www.youtube.com/watch?v=P_84rA1KupM&list=PLe8jmEHFkvsYuYm1x5t3RZ5WyGrfF8bkg
will not work
https://www.youtube.com/playlist?list=PLe8jmEHFkvsYuYm1x5t3RZ5WyGrfF8bkg
this will. Its the same playlist but there is a different. Look for ".com/playlist?list" and not ".com/**watch?**v". Also youtube auto "mix" will not work.

I've actually tried this before, probably should have mentioned it within the post. This popped up and I didn't want to say yes because I am paranoid. Do I need to say yes?

if you have changed the bot(the program) then "n". If you have only changed the options and permissions then click "y"

So I asked a friend of mine to test it again and it still says the same thing. This is getting quite..frustrating.
(;﹏;)

can you send a picture of the cmd

if you have "UseExperimentalEqualization" on in config turn that off restart the bot and give it a go

Nope..

This is going to sound a bit dumb but I have to make sure. One re check your permissions file. two make sure that once you have changed them save them. three redo the update.bat and run.bat. and last get your friend to do !perms and send me what it comes up with

change "Extractors = " to blank in permissions and do the restart processes again. Then give it another go

Woo, finally works! Guess it was extractors this entire time. Thank you for telling me to change that value. I was afraid that if I messed with it it would break the bot. Ha-ha. Thank you!!!!! (ﾉ´ヮ´)ﾉ*:･ﾟ✧


Error persistence in cycles

Consider the simple cycle A <-> B, where B is async and where A also imports the synchronous module C after B.
If, while B is executing we get a sync failure on C, this causes the error of C to populate the error along the whole stack which includes B thus setting B.[[EvaluationError]] to the C error (along with A and C).
But B is still executing, and can later reject, which currently would cause the evaluation error on the B module record to be replaced by the B failure error, instead of the previously set C failure error.
Should we:

Be overwriting the [[EvaluationError]] on B with its async rejection, or
Should we allow the [[EvaluationError]] of C to persist on B?

In these types of cases, typically sticking to the most well-defined behaviour as in (2) probably makes the most sense I think?
(2) is also effectively what the current ES module specification does in that any import to B at any later point in the application will get the error from C reported.

Closing as (2) above was merged in #114.


Switching out references of Iterative Studio to DVC Studio

This swaps out all the Iterative Studio references in the Docs with DVC Studio to correct branding discrepancies.
Happy Hacktoberfest! 🎃

@jendefig I think we also have a bunch of Studio mentions without Iterative/DVC. Do we want to change those also?

@jendefig I think we also have a bunch of Studio mentions without Iterative/DVC. Do we want to change those also?

Good point! Maybe.  As a company we have a bad habit of calling it Studio.  I think it's fair to say "Studio" in the rest of a paragraph as long as the first mention in every paragraph is "DVC Studio."  If all of them are DVC Studio it might be conversationally annoying.  An alternative would be to replace it with "the tool" in some places, but that feels awkward and not specific enough.
One question I had was regarding the "Studio access token" section here.  I didn't change those references because I figured that would mean changes needed to be made in the platform.  Should we change to "DVC Studio access token" on the platform?  My feeling is yes, but that seems to open a can of worms more challenging than these changes in the docs so I left that one alone.

Thanks @jendefig for making these changes.
I've added a commit with changes in 2 more places.

One question I had was regarding the "Studio access token" section

In the Studio user profile page, this field is called Studio Access Token. For DVC/DVCLive, it's called studio.token and DVC_STUDIO_TOKEN. Considering all this, I'd suggest not changing it in the docs for now. At some point, it would be good to sync the names.
@iterative/platform It looks like the only remaining part is the Self Hosting docs pages. These pages extensively use the name Studio (and not Iterative Studio, unlike the rest of the docs). Is it okay to replace the name  Studio with DVC Studio in these pages or could it cause confusion to users (such as if the images are called "Studio" images)?

@jendefig For the test failures, merging this PR should resolve it.

. Considering all this, I'd suggest not changing it in the docs for now. At some point, it would be good to sync the names.

Ok. Makes sense! 👍

@iterative/platform It looks like the only remaining part is the Self Hosting docs pages. These pages extensively use the name Studio (and not Iterative Studio, unlike the rest of the docs). Is it okay to replace the name Studio with DVC Studio in these pages or could it cause confusion to users (such as if the images are called "Studio" images)?

Oh.  I see what you mean.  I didn't find these because I searched for "Iterative Studio" to find the other.  Yes, absolutely these should be changed.  No one will ever find this content through a search with the headers this way.  There are way to many things in our industry alone named Studio (Azure ML Studio, Label Studio, Sagemaker studio,...) let alone the rest of the world to ever find this content.  Self-hosting Studio could be a ballet studio that gives members access any time they want.  We need to have the brand tied into all of this.

In the Studio user profile page, this field is called Studio Access Token. For DVC/DVCLive, it's called studio.token and DVC_STUDIO_TOKEN. Considering all this, I'd suggest not changing it in the docs for now. At some point, it would be good to sync the names.

This was actually intentional. I believe all DVC environment variables start with DVC_ (since environment variables are global to the environment) and config options do not (since they are already inside DVC-specific config files). This is a common practice (for example, you can use env var AWS_PROFILE or use profile inside ~/.aws/config).

https://github.com/orgs/iterative/teams/platform It looks like the only remaining part is the Self Hosting docs pages. These pages extensively use the name Studio (and not Iterative Studio, unlike the rest of the docs). Is it okay to replace the name Studio with DVC Studio in these pages or could it cause confusion to users (such as if the images are called "Studio" images)?

Yes, totally. Feel free to swap them out as part of this PR :+1:

Yes, totally. Feel free to swap them out as part of this PR 👍

@jendefig Do you want to add this here or should we leave it out?
@tapadipti Is there anything else you feel needs to be updated in the PR?

I've had to prioritize conference things.  I will run a search on "Studio" and do those corrections in  the next couple days.

@jendefig merged the restyling changes, resolved conflicts, and created a new PR on top of this one. This new PR should address your comment I will run a search on "Studio" and do those corrections in the next couple days. I've requested your review on that PR.


Change API to make configureDragDrop static

I propose we make configureDragDrop static, and pass current component as the first argument to each method. This change is a stepping stone to fix endDrag not firing on unmounted component (#38, we'll pass null as component) and also a stepping stone to allow “resurfacing” drag sources (#53, we'll pass another component as component).
I'd like this change to be implemented in a backward-compatible way with a deprecation warning. We will make it a breaking change in 1.0 with #48.

[ ] Support static configureDragDrop and pass component as the first argument to all methods
[ ] Update the docs to use the new way
[ ] Add a deprecation warning with upgrade instructions but still allow old-style configureDragDrop definitions (without component parameter)
[ ] Make sure deprecation warning is logged once per class and includes class name (like React's own warnings)
[ ] Prepare a separate PR that removes deprecation warning and makes it a breaking change. We will do that on 1.0 branch.

Any comments or volunteers?
@hakanderyal @nelix

To clarify. Before:
var Card = React.createClass({
  mixins: [DragDropMixin],

  configureDragDrop(registerType) {
    registerType(ItemTypes.CARD, {
      dragSource: {
        beginDrag() {
          return {
            item: {
              id: this.props.id,
              children: <Card {...this.props}/>
            }
          };
        }
      },

      dropTarget: {
        over(item) {
          this.props.moveCard(item.id, this.props.id);
        }
      }
    });
  },

After:
var Card = React.createClass({
  mixins: [DragDropMixin],

  statics: {
    configureDragDrop(registerType) {
      registerType(ItemTypes.CARD, {
        dragSource: {
          beginDrag(component) {
            return {
              item: {
                id: component.props.id,
                children: <Card {...component.props}/>
              }
            };
          }
        },

        dropTarget: {
          over(component, item) {
            component.props.moveCard(item.id, component.props.id);
          }
        }
      });
    }
  }

We may want to have a less nested API later, but this is not the point. The point is using component instead of this so we can later be free to pass null or another component if we wish so.
This breaks the use case when this is accessed directly in configureDragDrop but it's a rare use case and seems only useful in contrived examples.

Released in<EMAIL_ADDRESS>


Draft: basic web app, containerized and ruff happy

[x] app.py
[x] filtering.py

[ ] kwargs

[x] check_availability.py

[ ] date_id/room

[ ] build_hut_database.py

Closes #8 - availability csv is now precomputed with cron job

#26 should be merged before this PR continues, IMO
Issues remaining in #26

[ ] flask production server
[ ] react production server


Module initialization error on using Sharp in AWS lambda

I create Lambda function (Node.js 6.10)
Basically, I'm trying to resize the S3 image and upload it again to another bucket. I chose Sharp for the resize method.
exports.handler = function(event, ctx, callback) {
...
function resizeImg(url, width, height) {
        request.get(url, function(err, res, body) {
            if (err) {
                reject(err);
            }
            sharp(body)
                .resize(width, height, { kernel: sharp.kernel.nearest })
                .toBuffer()
                .then(function(resizedBuffer) {
                    console.log('Resize image Successfully');
                }).catch(function(error) {
                    console.log(error);
                    return;
                });
        })
    }

...
}

I got error:

module initialization error: Error
at Error (native)
at Object.Module._extensions..node (module.js:597:18)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/var/task/edg-image-resizer/node_modules/sharp/lib/constructor.js:10:15)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)

Here's my log of install the sharp:
$ npm i sharp
><EMAIL_ADDRESS>install /Users/xxxxx/Documents/Node/lambda-functions/abc-image-resizer/node_modules/sharp
> (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)

info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.6.1/libvips-8.6.1-darwin-x64.tar.gz
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

+<EMAIL_ADDRESS>added 75 packages from 93 contributors and audited 178 packages in 10.707s
found 0 vulnerabilities

Any suggestion is appreciated

Where you building sharp? I know it must me in Amazon Linux right?

Hi,
I'm getting exactly the same error and I used Linux for building. What could be the issue?

Hello, the mention of "darwin" in the line:

info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.6.1/libvips-8.6.1-darwin-x64.tar.gz

suggests OS X is being used at npm install time but Linux is used at runtime.
Please see http://sharp.pixelplumbing.com/en/stable/install/#aws-lambda

remove sharp and run: env npm_config_arch=x64 npm_config_platform=linux npm_config_target=8.10.0 npm install --save sharp
Change npm_config_target if you run node 6.10

Hi, thanks for all suggestions, I followed an instruction to deploy the function (nodejs) using Sharp to AWS Lambda:

Install run Docker
in package, add : "dockerbuild": "rm -rf node_modules/sharp && docker run -v \"$PWD\":/var/task lambci/lambda:build-nodejs8.10 npm install" in script
Run npm run dockerbuild
Zip content and upload to Lambda

It worked for me. Share it here for ref

For windows using cmd, you can try this in package.json:
  "scripts": {
    "dockerbuild": "del /S /Q \"node_modules/sharp\" && docker run -v \"%cd%\":/var/task lambci/lambda:build-nodejs8.10 npm install"
  }

Then you can run npm run dockerbuild

@lovell I tried running the equivalent cmd above, when I deployed and tried to execute in Lambda (which has Node.js 8.10 runtime), I got this:

Something went wrong installing the "sharp" module
/var/task/node_modules/sharp/build/Release/../../vendor/lib/libvips-cpp.so.42: invalid ELF header

Ensure "linux" is used at install time as well as runtime

I believe the idea of using the pre-compiled binaries mentioned in #312 is to avoid having to use docker workarounds right? How can we solve this?

https://sharp.pixelplumbing.com/en/stable/install/#aws-lambda


Added preview 'mercy'

To access the topics property for repositories the Accept header must contain a custom media type referencing the mercy-preview.

Sorry @piccobit for making you wait!


Convert online articles to PDF

Pull Request Template
script name - articles_to_pdf.py
Convert online articles to PDF.
Issue no.(must) - #213
Self Check(Tick After Making pull Request)

[x] This issue was assigned to me.
[x] One Change in one Pull Request
[x] My file is in proper folder (Name of folder should be in lowercase with no space in between)
[x] I am following clean code and Documentation and my code is well linted with flake8.
[x] I have added README.md and requirements.txt with my script

If issue was not assigned to you Please don't make a PR. It will marked as invalid.

Please add the hacktoberfest-accepted .

@pawangeek  Please check once.

Unsure why 'Greetings' check is failing. Let me know if I should correct anything. @pawangeek

Perfect @funbeedev and really appreciable for that headless arg


Slightly modernize the FontLoader.isSyncFontLoadingSupported getter

This is very old code, which is unused (by default) in browsers nowadays since the Font Loading API will always be preferred.
For Node.js environments we use the same constant as elsewhere throughout the code-base, and we can also simplify the Firefox-specific check given that the lowest supported version is 102 (as of this writing).
Finally the old TODO is removed, since the general availability of the Font Loading API has made it redundant.

/botio-linux preview

Thanks!


new feature: support AWS Container credential provider

Feature Description
via AWS_CONTAINER_CREDENTIALS_RELATIVE_URI environment variable in ECS/container settings: see https://docs.aws.amazon.com/sdkref/latest/guide/feature-container-credentials.html
Problem and Solution
load credentials in ecs environment
Additional Context
No response
Are you willing to contribute to the development of this feature?

[ ] Yes, I am willing to contribute to the development of this feature.

Hi, @Samrose-Ahmed, does this issue related to https://github.com/apache/opendal/issues/4964?

Yes it's the same.

Thank you! I will redirect the discussion here.

Hi, @Samrose-Ahmed, I expect to add this feature in our next release.

General question regarding this, would it be a good idea to wrap the AWS SDK with the credentials provider to do this job? This has been my current workaround for this issue and might be a better long-term solution for managing all the various ways you can authenticate with AWS.

General question regarding this, would it be a good idea to wrap the AWS SDK with the credentials provider to do this job? This has been my current workaround for this issue and might be a better long-term solution for managing all the various ways you can authenticate with AWS.

Thanks for the suggestion. We previously had a discussion here: https://github.com/apache/opendal/discussions/139.
The various methods for authentication are limited and rarely change, so we can ultimately support them all. I believe it isn't worth introducing the AWS SDK for authentication.


podman run, with -a stdin: inconsistent exit status

This one is weird:
# for i in $(seq 1 10); do podman run -a stdin --tty=false fedora false </dev/null;echo $?;done
493440fe37f79f3f3904d5d2535114e14e9ff1abb84b5d128a2ae316f5807c4e
1
6c1bf90b206e62fa57cab2f7a0ffca9865f85e7f62227672a5c1507bdab7d3a4
0
92d4adb28dfdc0b806091deed606cb4eac272fd6c81f9f1dbad408695331b43e
1
aacf93cb4d6a4dc7a9d040accd13fdfc0c7bb03da72cd1a07f33bfbb22a5249c
1
c50d8334c64f32ca4aa6abd69f9118e44bf42855ff3ea9b72525652ab3b6872a
1
d17aea655844c025c607e292a8a074e896887ca2b67ba5fd008974a8010557de
1
1d9842c3152631c6f6104f2138e4ad0029aa9b3d97049340b1d1dcb1ba4c2e06
1
c7092af7ec0cb79a5cb776efc26f1213146a603d6ae916f0d53ef7e433f88305
0
f7bc4f79f3674b96ba4507556b0cc66f0ab27e6cae503ac058160825ceeadfe7
0
292d7452fed468554a901c64dbe988c8fde07aa78d95760a7a3de5218c6a9ba2
1

I'm actually not sure what the correct behavior should be. FWIW docker is consistently 0.
podman-0.7.1-1.git802d4f2.fc28

I can only reproduce inside of the bash loop, it seems to always return 0 if not. Some sort of timing issue setting up attach?

You're right, though it seems less consistent without - 1 time out of 4 versus 1 out of 2.
Running with --log-level=debug gets me an exit code of 127 and a broken pipe error, which is probably a separate issue.

So the key factor here is the -a stdin
Running without this I dont see an issue.

PR Merged this should be fixed.


ext_proc fuzzer test exposed a race issue which leads to ENVOY_BUG

ext_proc fuzzer test exposed a race issue which leads to ENVOY_BUG() get triggered when opening a gRPC stream.
The issue is that

when onData() is called, it first open a gRPC stream to send the body to the ext_proc server.
when ext_proc server sends back a spurious response, which leads to the gRPC stream is closed, and processing_complete_ is set to true.
onData() later on will try to send the just added trailer. Before that it will try to call openStream() again with processing_complete_ already set to true.  This triggers ENVOY_BUG().

The solution is that:
openStream() actually already has the check for processing_complete_ then return error.  Just needs to move that check to front.

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

This is the fuzzer crash traceback:
./bazel-bin/test/extensions/filters/http/ext_proc/unit_test_fuzz/ext_proc_unit_test_fuzz  test/extensions/filters/http/ext_proc/unit_test_fuzz/ext_proc_corpus/crash-232906f11069ff930e29c13c1a3ae5a2c3202c57 -l trace
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from CorpusExamples/FuzzerCorpusTest
[ RUN      ] CorpusExamples/FuzzerCorpusTest.RunOneCorpusFile/0
[2023-05-25 18:54:41.621][154380][info][misc] [test/fuzz/main.cc:47] Corpus file: test/extensions/filters/http/ext_proc/unit_test_fuzz/ext_proc_corpus/crash-232906f11069ff930e29c13c1a3ae5a2c3202c57
[2023-05-25 18:54:41.629][154380][warning][misc] [source/common/protobuf/message_validator_impl.cc:35] message 'envoy.extensions.filters.http.ext_proc.v3.ExternalProcessor' is contained in proto file 'envoy/extensions/filters/http/ext_proc/v3/ext_proc.proto' marked as work-in-progress. API features marked as work-in-progress are not considered stable, are not covered by the threat model, are not supported by the security team, and are subject to breaking changes. Do not use this feature without understanding each of the previous points.
[2023-05-25 18:54:41.629][154380][warning][misc] [source/common/protobuf/message_validator_impl.cc:35] message 'envoy.extensions.filters.http.ext_proc.v3.ProcessingMode' is contained in proto file 'envoy/extensions/filters/http/ext_proc/v3/processing_mode.proto' marked as work-in-progress. API features marked as work-in-progress are not considered stable, are not covered by the threat model, are not supported by the security team, and are subject to breaking changes. Do not use this feature without understanding each of the previous points.
[2023-05-25 18:54:41.630][154380][warning][misc] [source/common/protobuf/message_validator_impl.cc:35] message 'envoy.service.ext_proc.v3.ProcessingResponse' is contained in proto file 'envoy/service/ext_proc/v3/external_processor.proto' marked as work-in-progress. API features marked as work-in-progress are not considered stable, are not covered by the threat model, are not supported by the security team, and are subject to breaking changes. Do not use this feature without understanding each of the previous points.
[2023-05-25 18:54:41.630][154380][warning][misc] [source/common/protobuf/message_validator_impl.cc:35] message 'envoy.service.ext_proc.v3.HeadersResponse' is contained in proto file 'envoy/service/ext_proc/v3/external_processor.proto' marked as work-in-progress. API features marked as work-in-progress are not considered stable, are not covered by the threat model, are not supported by the security team, and are subject to breaking changes. Do not use this feature without understanding each of the previous points.
[2023-05-25 18:54:41.630][154380][warning][misc] [source/common/protobuf/message_validator_impl.cc:35] message 'envoy.service.ext_proc.v3.CommonResponse' is contained in proto file 'envoy/service/ext_proc/v3/external_processor.proto' marked as work-in-progress. API features marked as work-in-progress are not considered stable, are not covered by the threat model, are not supported by the security team, and are subject to breaking changes. Do not use this feature without understanding each of the previous points.
[2023-05-25 18:54:41.630][154380][warning][misc] [source/common/protobuf/message_validator_impl.cc:35] message 'envoy.service.ext_proc.v3.HeaderMutation' is contained in proto file 'envoy/service/ext_proc/v3/external_processor.proto' marked as work-in-progress. API features marked as work-in-progress are not considered stable, are not covered by the threat model, are not supported by the security team, and are subject to breaking changes. Do not use this feature without understanding each of the previous points.
[2023-05-25 18:54:41.630][154380][warning][misc] [source/common/protobuf/message_validator_impl.cc:35] message 'envoy.extensions.filters.http.ext_proc.v3.ProcessingMode' is contained in proto file 'envoy/extensions/filters/http/ext_proc/v3/processing_mode.proto' marked as work-in-progress. API features marked as work-in-progress are not considered stable, are not covered by the threat model, are not supported by the security team, and are subject to breaking changes. Do not use this feature without understanding each of the previous points.
[2023-05-25 18:54:41.630][154380][info][misc] [test/test_common/test_random_generator.cc:20] TestRandomGenerator running with seed 228576712
[2023-05-25 18:54:41.702][154380][debug][misc] [./test/extensions/filters/http/common/fuzz/http_filter_fuzzer.h:144] Decoding headers (end_stream=false):
':path', '/foo'
':method', 'GET'
':authority', 'foo.com'
'(', ''
'test_uri', ''
[2023-05-25 18:54:41.702][154380][trace][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:189] decodeHeaders: end_stream = false
[2023-05-25 18:54:41.702][154380][debug][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:123] Opening gRPC stream to external processor
GMOCK WARNING:
Uninteresting mock function call - taking default action specified at:
test/extensions/filters/http/ext_proc/unit_test_fuzz/ext_proc_unit_test_fuzz.cc:90:
Function call: start(@0x616000060fa8 8-byte object <50-5D 77-07 00-00 00-00>, @0x616000061038 64-byte object <50-A2 9A-07 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 01-00 00-00 01-00 00-00 90-64 0F-00 20-60 00-00 00-00 00-00 00-00 00-00 00-B0 01-00 B0-60 00-00 00-00 00-00 02-00 00-00>, @0x9eb0050 8-byte object <20-B8 76-07 00-00 00-00>)
Returns: 0x61100007ca00
NOTE: You can safely ignore the above warning unless this call should not happen.  Do not suppress it by blindly adding an EXPECT_CALL() if you don't mean to enforce the call.  See https://github.com/google/googletest/blob/master/googlemock/docs/cook_book.md#knowing-when-to-expect for details.
[2023-05-25 18:54:41.704][154380][debug][ext_proc] [source/extensions/filters/http/ext_proc/processor_state.cc:30] Traffic direction INBOUND: 200 ms timer enabled
[2023-05-25 18:54:41.704][154380][debug][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:181] Sending headers message
[2023-05-25 18:54:41.705][154380][debug][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:606] Processing mode overridden by server for this request
[2023-05-25 18:54:41.705][154380][debug][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:611] Received request headers response
[2023-05-25 18:54:41.705][154380][debug][ext_proc] [source/extensions/filters/http/ext_proc/processor_state.cc:84] applying headers response. body mode = BUFFERED
[2023-05-25 18:54:41.705][154380][trace][ext_proc] [source/extensions/filters/http/ext_proc/mutation_utils.cc:60] Removing header f
[2023-05-25 18:54:41.705][154380][trace][ext_proc] [source/extensions/filters/http/ext_proc/mutation_utils.cc:60] Removing header f
[2023-05-25 18:54:41.705][154380][debug][ext_proc] [source/extensions/filters/http/ext_proc/processor_state.cc:52] Traffic direction INBOUND: timer disabled
[2023-05-25 18:54:41.705][154380][trace][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:201] decodeHeaders returning 1
[2023-05-25 18:54:41.705][154380][debug][misc] [./test/extensions/filters/http/common/fuzz/http_filter_fuzzer.h:103] Finished with FilterHeadersStatus: 1
[2023-05-25 18:54:41.705][154380][debug][misc] [./test/extensions/filters/http/common/fuzz/http_filter_fuzzer.h:185] Decoding data (end_stream=true): 𸸸𸸸𸸸𸸸𸸸𸸸𸸸𸸸𸸸𸸸𸸸𸸸踸
[2023-05-25 18:54:41.705][154380][trace][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:419] decodeData(51): end_stream = true
[2023-05-25 18:54:41.705][154380][trace][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:225] Creating new, empty trailers
[2023-05-25 18:54:41.705][154380][debug][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:274] Sending request body message
[2023-05-25 18:54:41.705][154380][debug][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:524] Sending a body chunk of 3 bytes
[2023-05-25 18:54:41.705][154380][debug][ext_proc] [source/extensions/filters/http/ext_proc/processor_state.cc:30] Traffic direction INBOUND: 200 ms timer enabled
[2023-05-25 18:54:41.705][154380][debug][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:606] Processing mode overridden by server for this request
[2023-05-25 18:54:41.705][154380][debug][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:611] Received request headers response
[2023-05-25 18:54:41.705][154380][warning][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:660] Spurious response message 1 received on gRPC stream
[2023-05-25 18:54:41.705][154380][debug][ext_proc] [source/extensions/filters/http/ext_proc/ext_proc.cc:140] Calling close on stream
GMOCK WARNING:
Uninteresting mock function call - taking default action specified at:
test/extensions/filters/http/ext_proc/unit_test_fuzz/ext_proc_unit_test_fuzz.cc:106:
Function call: close()
Returns: false
NOTE: You can safely ignore the above warning unless this call should not happen.  Do not suppress it by blindly adding an EXPECT_CALL() if you don't mean to enforce the call.  See https://github.com/google/googletest/blob/master/googlemock/docs/cook_book.md#knowing-when-to-expect for details.
[2023-05-25 18:54:41.705][154380][debug][ext_proc] [source/extensions/filters/http/ext_proc/processor_state.cc:52] Traffic direction INBOUND: timer disabled
[2023-05-25 18:54:41.705][154380][debug][ext_proc] [source/extensions/filters/http/ext_proc/processor_state.cc:413] Continuing processing
[2023-05-25 18:54:41.705][154380][error][envoy_bug] [source/extensions/filters/http/ext_proc/ext_proc.cc:121] envoy bug failure: !processing_complete_. Details: openStream should not have been called
[2023-05-25 18:54:41.705][154380][error][envoy_bug] [./source/common/common/assert.h:38] stacktrace for envoy bug
[2023-05-25 18:54:41.738][154380][error][envoy_bug] [./source/common/common/assert.h:43] #0 Envoy::Extensions::HttpFilters::ExternalProcessing::Filter::openStream() [0x28f7999]
[2023-05-25 18:54:41.770][154380][error][envoy_bug] [./source/common/common/assert.h:43] #1 Envoy::Extensions::HttpFilters::ExternalProcessing::Filter::onData() [0x28fe17b]
[2023-05-25 18:54:41.802][154380][error][envoy_bug] [./source/common/common/assert.h:43] #2 Envoy::Extensions::HttpFilters::ExternalProcessing::Filter::decodeData() [0x29014e5]
[2023-05-25 18:54:41.834][154380][error][envoy_bug] [./source/common/common/assert.h:43] #3 Envoy::Extensions::HttpFilters::HttpFilterFuzzer::sendData<>() [0x288e6d9]
[2023-05-25 18:54:41.866][154380][error][envoy_bug] [./source/common/common/assert.h:43] #4 Envoy::Extensions::HttpFilters::HttpFilterFuzzer::runData<>() [0x276139e]
[2023-05-25 18:54:41.898][154380][error][envoy_bug] [./source/common/common/assert.h:43] #5 LLVMFuzzerTestOneInput [0x274dcb6]
[2023-05-25 18:54:41.930][154380][error][envoy_bug] [./source/common/common/assert.h:43] #6 Envoy::(anonymous namespace)::FuzzerCorpusTest_RunOneCorpusFile_Test::TestBody() [0x4ff4a7b]
[2023-05-25 18:54:41.962][154380][error][envoy_bug] [./source/common/common/assert.h:43] #7 testing::internal::HandleExceptionsInMethodIfSupported<>() [0x76bd508]
[2023-05-25 18:54:41.995][154380][error][envoy_bug] [./source/common/common/assert.h:43] #8 testing::Test::Run() [0x76934fc]
[2023-05-25 18:54:42.028][154380][error][envoy_bug] [./source/common/common/assert.h:43] #9 testing::TestInfo::Run() [0x7694b31]
[2023-05-25 18:54:42.062][154380][error][envoy_bug] [./source/common/common/assert.h:43] #10 testing::TestSuite::Run() [0x769614b]
[2023-05-25 18:54:42.094][154380][error][envoy_bug] [./source/common/common/assert.h:43] #11 testing::internal::UnitTestImpl::RunAllTests() [0x76af34c]
[2023-05-25 18:54:42.127][154380][error][envoy_bug] [./source/common/common/assert.h:43] #12 testing::internal::HandleExceptionsInMethodIfSupported<>() [0x76c0d58]
[2023-05-25 18:54:42.160][154380][error][envoy_bug] [./source/common/common/assert.h:43] #13 testing::UnitTest::Run() [0x76ae8fe]
[2023-05-25 18:54:42.192][154380][error][envoy_bug] [./source/common/common/assert.h:43] #14 main [0x4ff2db6]
[2023-05-25 18:54:42.193][154380][error][envoy_bug] [./source/common/common/assert.h:45] #15 UNKNOWN [0x7fa3e50cd18a]
Aborted

This is the test case:
cat test/extensions/filters/http/ext_proc/unit_test_fuzz/ext_proc_corpus/crash-232906f11069ff930e29c13c1a3ae5a2c3202c57
config {
grpc_service {
google_grpc {
target_uri: "test_uri"
channel_credentials {
ssl_credentials {
private_key {
inline_string: "/"
}
}
}
stat_prefix: "test_uri"
credentials_factory_name: "test_uri"
config {
}
}
initial_metadata {
key: "test_uri"
}
}
failure_mode_allow: true
processing_mode {
response_header_mode: SKIP
}
request_attributes: "("
response_attributes: "test_uri"
response_attributes: "9\000\000\000\000\000\000\000"
stat_prefix: "\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000."
}
request {
headers {
headers {
key: "("
}
headers {
key: "test_uri"
}
}
http_body {
data: "\360\270\270\270\360\270\270\270\360\270\270\270\360\270\270\270\360\270\270\270\360\270\270\270\360\270\270\270\360\270\270\270\360\270\270\270\360\270\270\270\360\270\270\270\360\270\270\270\350\270\270"
}
}
response {
request_headers {
response {
header_mutation {
remove_headers: "f"
remove_headers: "f"
}
}
}
dynamic_metadata {
fields {
key: ""
value {
}
}
fields {
key: ""
value {
}
}
}
mode_override {
request_header_mode: SKIP
request_body_mode: BUFFERED
response_body_mode: BUFFERED
request_trailer_mode: SEND
}
}

The fuzzer can easily trigger this race since it sends back and handles the spurious response right within onData() when the body request is sent to the ext_proc server.  This is after the first openStream() but before the 2nd openStream() / sendTrailers() in onData() function.

@yanavlasov @tyxia

@stevenzzzz @mpwarres

The test is failed with the issue addressed by: https://github.com/envoyproxy/envoy/pull/27619. So wait for that PR to be merged first.


Add FlowFuse Dedicated to pricing page

Description
Add "FlowFuse Dedicated" as a third option alongside "Cloud" and "Self-Hosted" on the pricing page.
Inspiration
https://about.gitlab.com/pricing/
Key points
Everything from Enterprise Tier, plus:

Fully managed by FlowFuse
Data residency in region of your choice
Full data and source code isolation
Enterprise grade security
Regular upgrade cadence

If need be, we can have a more extensive landing page etc on /pricing/dedicated/?

similar to the gitlab pricing page you can also link the new landing page to "Learn more"


User action form for voting_information_researched action

closes
fixes
What changed? Why?
Adds the userActionFormVotingInformationResearched form & dialog to be used in the Voter Guide page

PlanetScale deploy request

Notes to reviewers
Added initOnMount: false to the usePlacesAutocomplete hook to fix the undefined maps error. We are manually initializing the hook once the GoogleMapScript  status is ready.
How has it been tested?

[ ] Locally
[ ] Vercel Preview Branch
[ ] Unit test
[ ] Functional test

@eduardopicolo-cb please add the issue on this PR


js-ipfs 0.25.0 blog post

That makes sense, I'm ok with punting until later. Maybe we can hack on it
during lab week :)
On Wed, Jul 12, 2017 at 12:11 PM, David Dias<EMAIL_ADDRESS>wrote:

@diasdavid commented on this pull request.
In content/post/28-js-ipfs-0.25.md
https://github.com/ipfs/blog/pull/128#discussion_r127000188:

+The JavaScript implementation of libp2p received a lot of love recently, including the addition of Tutorials. You can consult all the details on the Log entry of libp2p's Captain.log - https://github.com/libp2p/js-libp2p/issues/6#issuecomment-313970615
+
+### 🏎 SPDY is out of the mix and there goes browserify-zlib special shimming.
+
+SPDY has been removed from the default browser bundle in favor of supporting libp2p-multiplex only. SPDY was the Stream Muxer of js-ipfs since almost the beginning, but since go-ipfs never got a complete implementation of SPDY, we ended up switching to libp2p-multiplex to guarantee interop between implementations. What this means is that you will continue to see the interop, but now your browser bundle will be significantly lighter.
+
+### 📞 wrtc, the WebRTC module for Node.js is now optional
+
+wrtc, a module that enables js-ipfs Node.js nodes to speak WebRTC, has been excluded from the default list of modules so that Linux users can have a better time when using js-ipfs natively. You can still bring it back and now not only use wrtc but you can also use electron-webrtc, the other WebRTC module for Node.js See how to achieve that in the project's README - https://github.com/ipfs/js-ipfs#advanced-options-when-creating-an-ipfs-node.
+
+Note, this doesn't change the behavior in the browser. Browser nodes will still continue to use WebRTC by default.
+
+
+If you run into any hurdles, please open an issue on ipfs/js-ipfs/issues.
+
We can create a list but at the risk of being incomplete. (Which would be
a bummer if someone is left out).
I really want to do that though, to make that work extremely well it would
be important to have:

lint the commit messages to follow the same standard
have a tool that tracks all the contributions in the dep tree

—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/ipfs/blog/pull/128#discussion_r127000188, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABPtpCWMpWY2USRh-mUR-x0qJc7Npb0mks5sNPAZgaJpZM4OVQjf
.


[Event Request] codeunit 1521 "Workflow Response Handling" - OnPostDocument

Hi,
Is it possible to add OnPostDocument publisher to "Workflow Response Handling" codeunit?
    local procedure PostDocument(Variant: Variant)
    var
        RecRef: RecordRef;
        // <<new
        Handled: Boolean;
        // new>>
    begin
        RecRef.GetTable(Variant);

        case RecRef.Number of
            DATABASE::"Purchase Header":
                CODEUNIT.Run(CODEUNIT::"Purch.-Post", Variant);
            DATABASE::"Sales Header":
                CODEUNIT.Run(CODEUNIT::"Sales-Post", Variant);
            // <<old
            else
                Error(UnsupportedRecordTypeErr, RecRef.Caption);
            // old>>
            // <<new
            else begin
                    OnPostDocument(RecRef, Handled);
                    if not Handled then
                        Error(UnsupportedRecordTypeErr, RecRef.Caption);
                end;
           // >>new

        end;
    end;

    // <<new
    [IntegrationEvent(false, false)]
    local procedure OnPostDocument(RecRef: RecordRef; var Handled: Boolean)
    begin
    end;
    // >>new

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 42495.


Cosmetic improvements v2

Notable changes
Closes: #588

Click top left logo to go to trade page
Frontier

Update toast color
Mobile - improve banner spacing
Show banner once per browser

Trade page

Token select:

Sort tokens by fiat value descending
Display chain name, and channel if channel not canonical
Search by chain name, min denom ("basecro"), peg mechanism ("collateralized," "hybrid," "algorithmic")

Remove denom in from field, max 8 decimals

Pool detail page

Requery superfluid validator data after sending go superfluid msg
14 day gauge uses one osmosis icon for sfs tooltip
Add liquidity tokens scroll for pools with 3+ tokens
Bond modal stays open with button loading animation for bond msgs
Pool catalyst shows decimal precision even for > 1 amounts

Pools page

Search pools by network names (appended: "Cosmos Hub Akash Network") and peg mechanism

Assets page

Sorting by balance sorts by fiat value, not amounts

@jonator What peg mechanism is for? Did users want to search pools by peg mechanism?

@delivan Peg mechanism is used to label the type of stable asset for the info box in the add liquidity modal, as well as for searchiing

@delivan made a few last minute changes. Feel free to review again

[ ] I think the font size of the 'Available LP Token' section(label and value) looks small. Why don't you make it bigger so that users can see it more clearly?

[ ] 'Hide zero balances' is unavailable for me

[ ] The amount of token shrinks whenever switching token on token select

The amount of token shrinks whenever switching token on token select

This is how the old app functioned and it makes sense given that fee is subtracted

I think the font size of the 'Available LP Token' section(label and value) looks small. Why don't you make it bigger so that users can see it more clearly?

IMO the font size is fine, I'm letting @victortokaito determine if there needs to be a change here.


not compatible with VueI18n

when I use both kazupon/vue-i18n and vue2-datatable. It got conflict and shown  Error in render function: "TypeError: _vm.$i18n is not a function".
I rename $i18n -> $i18n2 in index.js and index.vue in vue2-datatable, it is working fine.

well, it's a coincidence...i will rename it in next version

@fatb0000 v1.1.9 is for you!

thanks!


update podfile to use pods_project method

Update the Podfile to use pods_project method instead of project for newer versions of Cocoa Pods as per https://github.com/smileyborg/guides.cocoapods.org/commit/094ee66f4e589f4709b36fbc6b0f6d9bfe47fe31

LGTM


Delete unused gamm invariants, fix pool account invariant

Closes: #833
Description

For contributor use:

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer

Codecov Report

Merging #1198 (b855e5a) into main (eed3294) will increase coverage by 0.00%.
The diff coverage is 26.66%.

@@           Coverage Diff           @@
##             main    #1198   +/-   ##
=======================================
  Coverage   21.03%   21.04%
=======================================
  Files         196      196
  Lines       25349    25365   +16
=======================================
+ Hits         5332     5337    +5
- Misses      19054    19067   +13
+ Partials      963      961    -2

Impacted Files
Coverage Δ

x/gamm/keeper/pool_service.go
56.61% <23.07%> (-0.61%)
:arrow_down:

x/gamm/keeper/invariants.go
29.41% <29.41%> (+29.41%)
:arrow_up:

Continue to review full report at Codecov.

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


Suggest Amazing Tic Tac Toe

Project URL
Amazing Tic Tac Toe by Aries Sciences LLC Repo on GitHub
Category
Games (ID: games)
Description
Following all the guidelines I added the Mac OS app Amazing Tic Tac Toe to the applications.json file.
Why it should be included to Awesome macOS open source applications  (optional)
Checklist

[x] Edit applications.json instead of README.md.
[x] Only one project/change is in this pull request
[x] Screenshots(s) added if any
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

yea


Investigate organizing deployment build logic

Should this all be in the root project or somewhere else (another project, another git file, a gradle plugin, etc)

#47


CI for Node

Contains the compiled JavaScript

Contains the compiled JavaScript

Initializes with two players

Initializes with two players


fix(vue-model-api): do not evict ReactiveINodeJS from cache when objects manged by it are still used

The effect of this issue was that subscribed Vue elements didn't update when a change happened in Modelix data.
Fixes MODELIX-1041
To be verified by reviewers

[ ] Relevant public API members have been documented
[ ] Documentation related to this PR is complete

[ ] Boundary conditions are documented
[ ] Exceptions are documented
[ ] Nullability is documented if used

[ ] Touched existing code has been extended with documentation if missing
[ ] Code is readable
[ ] New features and fixed bugs are covered by tests

It still has issues. I have to look at it.


There is no logo on print preview

On the print preview, no logo of the swiss administration is displayed.

@desobryc can you please specify where? There's a logo in print preview i.e. in the homepage:
Print preview screenshot on IE11

You have to use the print icon of the webguidelines


Some questions about running.

Hello, I have some questions when running your code:
For PPI data, I downloaded your ppi.zip, which has .npy file. when Runing code，
ValueError: File suffix must be .json, .json.gz, .pkl or .pkl.gz: data / ppi \ train_feats.npy
How can I fix it ?

Now, I load it using np.load

I believe the error message here is wrong (it comes from https://github.com/microsoft/dpu-utils/blob/master/python/dpu_utils/utils/richpath.py#L189, but .npy is actually supported in the two lines above).
To debug this further, can you include the exact invocation of train.py you tried, show the content of data/ppi (either using ls or dir) and tell me what platform you are using? The \ in the path looks like you are on Windows? Can you also check what version of dpu-utils you have installed (with pip show dpu-utils)?

Thanks for your helping！
When I checked the version of dpu-utils, I found that it did not meet the requirements of require.txt. After Updating the version and then solve the problem. I debug under windows, thank you very much for your help!


[GOBBLIN-1640] add an API in AbstractBaseKafkaConsumerClient to list selected topics

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[ ] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-XXX

Description

[ ] Here are some details about my PR, including screenshots (if applicable):

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #3501 (e538f71) into master (48b25a2) will decrease coverage by 3.21%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3501      +/-   ##
============================================
- Coverage     46.67%   43.46%   -3.22%
+ Complexity    10405     2038    -8367
============================================
  Files          2078      405    -1673
  Lines         81289    17454   -63835
  Branches       9078     2133    -6945
============================================
- Hits          37945     7586   -30359
+ Misses        39846     9024   -30822
+ Partials       3498      844    -2654

Impacted Files
Coverage Δ

...a/org/apache/gobblin/cluster/GobblinHelixTask.java
60.21% <0.00%> (-2.16%)
:arrow_down:

.../kafka/client/AbstractBaseKafkaConsumerClient.java

...re/filesystem/FsDatasetStateStoreEntryManager.java

.../gobblin/util/limiter/stressTest/MRStressTest.java

...tention/profile/ManagedCleanableDatasetFinder.java

...ava/org/apache/gobblin/metrics/metric/Metrics.java

...n/google/webmaster/GoogleWebmasterDataFetcher.java

...n/runtime/troubleshooter/JobIssueEventHandler.java

...ta/management/trash/NoopSnapshotCleanupPolicy.java

...gobblin/writer/commands/MySqlBufferedInserter.java

... and 1667 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 48b25a2...e538f71. Read the comment docs.


failed to load smarthome devices: "Cannot convert undefined or null to object"

Since this morning, I'm getting the following error message on initialisation:
failed to load smarthome devices: "Cannot convert undefined or null to object"
I'm using version 5.0.22 of node-red-contrib-alexa-remote2-applestrudel
All existing non-smart-home device related Alexa nodes are working properly. But the smart home device list is (obviously) empty and existing smart-home automations fail too.
Edit: I've tried to delete the credentials file and login again, but that didn't help either. Apart from the smart home device list, the initialisation is working fine (even when I restart node-red)

I've now tried to add a get devices smart home node and this one worked - shortly afterwards the smart home device list re-appeared.

Can´t get it to work either. Same Message:
13.11.2022, 16:55:38node: Amazon
msg : string[27]
"Initialisation was aborted!"
13.11.2022, 16:55:38node: Amazon
msg : string[78]
"failed to load smarthome devices: "Cannot convert undefined or null to object""

same issue here!
not working since  3 or 4 days

Hi all,
I think the problem here is related to my issue:
https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/96
The device list seems not loadable as the API points on the wrong host.


Shall the Chapter Lexical structure Introduce Keyword Operators Properly?

Describe the bug

In the section 6.4.4 Keywords, some keywords are also operators. For example, new and as. The spec doesn't mention it.
In the section 6.4.6 Operators and punctuators, only those non-keyword operators are listed.
In the section 12.8.16 The new operator, the spec formally says new is an operator.

Somehow it might be a logic loophole.

@TimothyLiuAtGoogle.
Thanks for your input.
My initial reaction is, “No further explanation is necessary!”
Yes, new (as well as sizeof, and typeof) is an operator that is spelled as a keyword, but, first, let’s look at specs for several other (very popular) languages to see how they handle this:

Java: new is an expansion of the grammar rule Keyword. Like the C# spec, the grammar rule Operator does not include new. And like the C# spec, there is no mention in either the “Keywords” or “Operators” sections about operators spelled as keywords.
C++: new is an expansion of the grammar rule keyword. Like the C# spec, the grammar rule operator-or-punctuator does not include new. Like the C# spec, there is no mention in either the “Keywords” or “Operators and punctuators” sections about operators spelled as keywords. That said, C++ has the oddity of alternate spellings for some operators; e.g., and being equivalent to && and bitand being equivalent to &. While the identifier versions are mentioned in the Keywords section, they are not expansions of the keyword grammar rule.

So, I think the C# spec is in good company by not saying more!
Keep in mind that the purpose of Chapter 6 is to describe the lexical grammar; that is, how to form source tokens. Chapter 12 then covers the syntactic grammar and semantics of operators.
To be sure, there are complexities; for example, some operators consist of multiple tokens (>>, >>=, (), and []), yet only the first two of these are called out in the C# spec’s “Operators and punctuators” section.
What is the problem you are looking to solve? Is there confusion/ambiguity here?

@RexJaeschke
Thank you so much for the quick response!
When teaching students and writing books, I often refer to the C# spec. The problem is I have to explain to the students that new is an operator and we will use it to form expressions, but it's not listed in 6.4.6 Operators and punctuators. As same as what you mentioned, I also tell the students - event ISO:14882 (C++ Spec) does the similar thing.

@TimothyLiuAtGoogle.
The important thing for readers of the spec to understand is that 6.4.6, "Operators and punctuators" is not about operators, per se, but rather, it's a list of source tokens that are classified as operator tokens, separate from 6.4.4, "Keywords," which is a list of source tokens that are classified as keyword tokens.
Closing this issue, without action.


Remapping the ROG button often launches it minimized

About 20% of the time it will launch the G14control minimized.

Yeah, it was tough to get it to work at all, because windows 10 doesn't like to let a process running in the background to be able to gain focus. It works when minimized, because I put in many hours lol.

I added this feature in version 0.1.33.

I mean, I fixed issue where it would launch minimized. You can toggle whether you want it to minimize to tray or taskbar on the settings page.


Check triangle mesh before attempting to bake it for physics

This PR checks if a triangle mesh contains at least three vertices before trying to bake it into a physics mesh. This catches an error that can come from loading data with degenerate triangles:

It's not a perfect solution, but at least it will prevent the app from crashing in play mode. Maybe we should Debug.LogWarning something about it?

Thank @j9liu!


BLE UART example and IOS disconnecting

Hi,
Has anyone got this to stay stable, mine runs sporadically and randomly disconnects?
(W (25699) BT_APPL: bta_gattc_conn_cback() - cif=3 connected=0 conn_id=3 reason=0x0008)
Which i guess is the iphone disconnecting ?
Using the BluePixel BLE scanner, also a custom flying app, both do the same. ( Iphone 4S )
Using a HM-10, it stays connected.....
Log
V (25524) FreeRTOS: Semaphore giving: name: ConfEvt (0x3ffe71cc), owner: <N/A>
D (25542) GeneralUtils:      00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f  ----------------
D (25547) GeneralUtils: 0000 7c                                               |
D (25554) FreeRTOS: Semaphore taking: name: ConfEvt (0x3ffe6c30), owner: <N/A> for notify
D (25562) FreeRTOS: Semaphore taken:  name: ConfEvt (0x3ffe6c30), owner: notify
V (25569) FreeRTOS: >> wait: Semaphore waiting: name: ConfEvt (0x3ffe6c30), owner: notify for notify
V (25570) FreeRTOS: Semaphore giving: name: ConfEvt (0x3ffe6c30), owner: notify
V (25585) FreeRTOS: << wait: Semaphore released: name: ConfEvt (0x3ffe6c30), owner: notify
V (25585) FreeRTOS: Semaphore giving: name: ConfEvt (0x3ffe71cc), owner: <N/A>
D (25603) GeneralUtils:      00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f  ----------------
D (25608) GeneralUtils: 0000 7d                                               }
D (25615) FreeRTOS: Semaphore taking: name: ConfEvt (0x3ffe6c30), owner: <N/A> for notify
D (25623) FreeRTOS: Semaphore taken:  name: ConfEvt (0x3ffe6c30), owner: notify
V (25630) FreeRTOS: >> wait: Semaphore waiting: name: ConfEvt (0x3ffe6c30), owner: notify for notify
V (25632) FreeRTOS: Semaphore giving: name: ConfEvt (0x3ffe6c30), owner: notify
V (25646) FreeRTOS: << wait: Semaphore released: name: ConfEvt (0x3ffe6c30), owner: <N/A>
V (25646) FreeRTOS: Semaphore giving: name: ConfEvt (0x3ffe71cc), owner: <N/A>
D (25664) GeneralUtils:      00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f  ----------------
D (25669) GeneralUtils: 0000 7e                                               ~
D (25676) FreeRTOS: Semaphore taking: name: ConfEvt (0x3ffe6c30), owner: <N/A> for notify
D (25684) FreeRTOS: Semaphore taken:  name: ConfEvt (0x3ffe6c30), owner: notify
V (25691) FreeRTOS: >> wait: Semaphore waiting: name: ConfEvt (0x3ffe6c30), owner: notify for notify
W (25699) BT_APPL: bta_gattc_conn_cback() - cif=3 connected=0 conn_id=3 reason=0x0008
V (25699) FreeRTOS: Semaphore giving: name: ConfEvt (0x3ffe6c30), owner: notify
V (25715) FreeRTOS: << wait: Semaphore released: name: ConfEvt (0x3ffe6c30), owner: <N/A>
V (25715) FreeRTOS: Semaphore giving: name: ConfEvt (0x3ffe71cc), owner: <N/A>
V (25730) FreeRTOS: Semaphore giving: name: ConfEvt (0x3ffe6c30), owner: <N/A>
D (25733) GeneralUtils:      00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f  ----------------
V (25737) FreeRTOS: Semaphore giving: name: ConfEvt (0x3ffe71cc), owner: <N/A>
D (25745) GeneralUtils: 0000 7f                                               .
start advertising
Thanks for any help!

No one ? :(
Surely someone must be using BLE with the Iphone ! :)
I have tried pcbreflex example aswell, same problem.
Tried increasing and decreasing  the Min and Max interval times, still same issue.
Anyone ? :)

Im pretty sure all of them are using iPhone brick:
https://github.com/nkolban/esp32-snippets/issues/430
offtop: sorry but i am iPhone hater

tried alsorts of values in
esp_ble_gap_set_prefer_conn_params();
Still disconnecting with the same problem .
think this one has beaten me :(

You can try to use nRF connect on android to get those values from logs.
This is my advice about iPhone: flash it in the toilet. But seriously, try to add security layer to your application. Its a chance that iPhone is security sensitive or try to contact with apple devs community.

Thanks
I wish I could do that regarding the Iphone, but my project is a full flying computer and people use kobos, android phones and unfortunately iphones and theres a lot with iphones wanting to use the system.
So I am stuck.
Any examples on adding a security layer ? Have spent a few days hacking at this and getting nowhere :(

https://github.com/nkolban/esp32-snippets/tree/master/cpp_utils/tests/BLETests/Arduino/security

Well, the hm10 doesnt require a security layer, I am trying to emulate this but can try !
Thanks


fixed typo error

@tsurdilo Please, do you think, that this PR can be cherrypicked into the master branch?


Treasure Chest

A tutorial on how to create an additional NPC, a talking treasure chest,

Dupe of #22


Print environment variables for commands executed by swift-syntax-dev-utils

Environment variables are as much input to the executed subprocess as the parameters and we should be logging them as well in verbose mode.

@swift-ci Please test


Editor: Contact Text Set

Summary
This adds the Contact Text Set (https://www.figma.com/file/bMhG3KyrJF8vIAODgmbeqT/Design-System?node-id=837%3A2564)
User-facing changes
N/A
Testing Instructions
Enable the text sets flag in experiments and see the new text sets in the story editor.
Partial for #4078

@miina Thanks for flagging all this.

In regards to contact sets being centered versus left align, please do ensure that it's left aligned. For the optimal aspect ratio, I have the text box stretched out to 332px (when possible) giving the overall layout a 40px left and right buffer on the page. 332px is also the same width of the design safe zone (which we'll implement soon). So what Minna is suggest is perfect!

For how much room should we leave between text sets and the bottom of the page, I created bounding boxes for each text element and we should use those to place the text sets on the page. This should ensure that the set is within the safe zone.

Use box fill where possible and don't use a separate rectangle shape as minna suggested

In general, ensure we follow the harmonic type scale. This is what makes the type layout look nice :)

@miina All of the above should have been addressed!

@miina I forgot to push my changes on Friday 🤦 Spacing should be correct now

@dmmulroy Good to go from my side. 👍


Elixir: Use a bag ETS table

👋🏻 Hi!
I am not very familiar with the problem but are all of those additional tables really needed? Can this be solved with :bag tables, like in this PR?
Additionally I optimized the inserts/lookups slightly by inserting/fetching multiple elements at once.

I changed it to a duplicate_bag because it's much faster for loading stop times, and reverted loading multiple items to the tables at once - it didn't make a significant difference, and caused higher memory usage

@michallepicki my suggestion would be to rather use :persistent_term and keep it as a single map. :) It will be the simplest API and the most performant too. :) I was planning to look at it but I can't download the MBTA archive!

@josevalim I agree that :persistent_term would be best for read-only data but I saw mentions in the repo that this benchmark might be extended to add more features like adding/modifying routes or stop times, so I'm not sure whether it should be used or not.
I also couldn't download the MBTA.zip file, I get a 403 error - maybe because we're in Europe? I downloaded one from https://transitfeeds.com/p/mbta/64 , hopefully it's fresh enough

Most of the CPU time is taken by JSON, so I don’t think such small changes will matter here, unfortunately.


Revise the documentation

Proposed Changes

(Describe the changes and rationale behind them)

Related Issues

(Github link to related issues or pull requests)

Just a thought, but what do you say we recommend the remote managed tunnel and classify the local managed tunnel as advanced?

Just a thought, but what do you say we recommend the remote managed tunnel and classify the local managed tunnel as advanced?

Not sure, since I guess for most users it is still easiest to just use it for HA with the external hostname and are done. This way, they do not have to create the Zero Trust Account (which requires payment methods, though they are not charging anything).
I suggest to leave it for now and reconsider regularly if they introduce new features at Cloudflared


feat: allow bundlesize check optout

Adds a way to opt-out of the bundle size checks. E.g. in ipfs-cli we just target node and attempts to do size checking fail.

I think a better way to do this would be to just read the .aegir.js from the root of the package and if it exports a bundlesize.maxSize value, run the size check.  If not or there's no .aegir.js present, skip it.
This makes it opt-in rather than opt-out and avoids the proliferation of tiny files.

Sorry, I guess we should have talked this through first!

Actually, take a look at https://github.com/ipfs/aegir/pull/652 - it allows the same matrix approach as the typechecking being added to js-ipfs.  I think this is preferable as we can run everything in parallel and get a nicer view on what's failing as each package that's had it's bundle size checked has a dedicated job on the PR checks page.

Yep #652 makes more sense, closing this.


Cf nginx letsencrypt redis

This is the last work from myself that will Adobe ColdFusion. Further work on any CF server engine will be with Lucee, mostly because of Adobe's difficult licensing structure for Adobe ColdFusion server.

I need to abandon this PR

While I understand your sentiment, first, do you realize that my repo here accepts offers of PRs for Lucee (and already has some Lucee examples I've put in)?
Second, are you saying you don't want this cf-nginx-letsencrypt-redis example to remain for others to see?

Evening Sir! I appreciate your attentiveness and engaging even after i closed the PR! :)
I did not fully test out the cf-nginx-letsencrypt-redix example, and my intention was to PR it to the master branch in my fork of your repo. I didn't want to lose the code, but also felt it wasn't appropriate to ask you to include it in your repo.
I did see the Lucee examples that you provided, and will be using them!
My intention was to do a proof of concept on Lucee replacing Adobe CF server. Was going to determine if it's possible to compose a container that runs commandbox lucee, based on a cfconfig export from an existing Adobe CF instance.

Glad to help, and I may well consider bringing it forward into the main. Thx.
As for the last goal, that will work, and I certainly welcome Commandbox image examples as well--as I indicate at the top of the readme and in fact already have one l've put in.
I really was hoping that after I "primed the pump" with so many examples, others might pick up the ball and run with it. Sadly, it's gotten hardly any traction or attention (I rarely see anyone else mention it).
In fact, I'm thinking of renaming/rebranding as awesome cf containers, to change the focus from compose, to include k8s, and of course just dockerfiles, and more.
I suppose some might argue "awesome cfml" may be better than "cf". I see pros and cons. Maybe I should just go "whole hog" and name it "awesome coldfusion and lucee containers". I'd not be averse to that, really. Whaddya think? And that's open to anyone reading this thread, of course.


Bugfix: The load operation can fail after a create is done, because load useskwargs and those kwargs may cause the BigIP get request to fail.

@zancas
Issues: Issue #233
Problem: Load for a service will fail after create is called because all kwargs are passed from create to load
Analysis: Decided to make a resource meta_data property called 'disallowed_load_parameters' that will be stripped from kwargs passed into load if they are present.
Tests: Added the trafficGroup to one of the functional tests to ensure this does not fail on a real BigIP. Still testing at 100%

LGTM


upload to Google play error, Other developers are using the following content provider authorization: com. Microsoft. cognitiveseervices. speed. util InternalContentProvider

upload to Google play error：

Please remove the conflicting items from the list first before uploading. Other developers are using the following content provider authorization: com.microsoft.cognitiveservices.speech.util.InternalContentProvider

sdk version:
implementation("com.microsoft.cognitiveservices.speech:client-sdk:1.38.0")

Duplicate of https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/2407


Enhance discussion of affected[].version formats

Based on query raised in https://github.com/google/osv.dev/issues/2135

@yashrsharma44  tagging you in from https://github.com/google/osv.dev/issues/2135. Would this clarify the question you had in that?

Thanks, this should be helpful :)


Agregado FCYT

@Equinox766 First stage of verification passed, official domain is unca.edu.py as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://iris.unca.edu.py/?type_0=gallery&album_gallery_id_0=2&bwg_search_0