DSP Hydrogen Calculation Incorrect

Describe the bug
This recipe is showing a surplus of hydrogen, but it is incorrect. There is a deficit. It seems to be triggered by choosing not to 'include' hydrogen on the main screen.
https://factoriolab.github.io/list?z=eJxNxrkKwlAUhOG3OcWA4oLaT8TrgiJIMLEJxAVCBMWgJM08u.dY-cN8zPOB2cDKpVU8Y1iw56TOwamcvtNFmrg2LgNW9uIVmBcs3fR3t27nJAtgbTcEa4CpOBLH4k5MxUzMxVq8Kwna66hcJ11U660WsQ3-CvaZfAHtjC9L
Scroll to the Matrix - it shows a surplus of 3.168 per second. The sankey flow diagram also shows the 'correct' behavior and shows an unbalanced negative hydrogen (even being mindful to exclude the 'fake' stream to the fractionators).
The actual production and consumption of hydrogen in this factory is:

Process
Hydrogen

Plasma Refining
1.2

X-Ray (Input)
-1.7

X-Ray (Output)
2.55

Deut (Net H Out)
-2.987

Casimir
-7.8

NET
-8.73 per sec

Note that the behavior changes drastically if you 'include' Hydrogen in the list tab. It seems to recognize there is a net hydrogen deficit and rearranges the factory to produce more.
What I Expected
Choosing not to include hydrogen is great - this production line should be a net consumer of hydrogen. I wanted the calculator to tell me how much, but it was showing an (incorrect) surplus instead.

The issue is that the calculator assumes it already has all the hydrogen it needs, and thus any extra hydrogen produced by any of the other recipes required is thus treated as surplus.
I'll see if I can make an exception in this case and treat the amount as not surplus if the item is ignored.

Pushing a potential fix to https://factoriolab.github.io/staging/dsp
Let me know if this seems to give you the expected result. I think it still needs some refining for more potential edge cases but it seems to give the expected result in your specific case now.

Pushing a potential fix to https://factoriolab.github.io/staging/dsp
Let me know if this seems to give you the expected result. I think it still needs some refining for more potential edge cases but it seems to give the expected result in your specific case now.

I'm not seeing the fix.
https://factoriolab.github.io/staging/matrix?z=eJxNxs0KglAYhOG7OYuBIotqP0anH4ogDmkbQSsQgyIpdDPX3vla9cI8zPOB-ciVK1ezQlJwYATjaNTG0OgjbVwGrIsOiXvxCiwKlmb43Z3ZG-kS2LgbvGuBmTgWJ-JeDGIm5mIj3pV6HXRSrrMuavRWh9gWf3n3mX4B7OIvSw__
I'm still seeing a surplus of hydrogen when it's ignored as an input.

So to be clear, the fix is for the list tab, not the matrix tab. The matrix tab will still list hydrogen as a surplus, there's really no way to avoid that. The matrix tab is kind of a peek under the hood, and under the hood the simplex solution tells us that to produce the desired products in this case we end up with a surplus of hydrogen (we produce more than what is required to feed the recipes).
I deleted my original comment because I am not 100% sure I understand the problem here yet and I don't want to assume too much; even the statement above may be wrong. I hope to investigate more today or tomorrow and get to the bottom of it. My intent with the fix in the staging environment was only to correct the List tab, though.


Refactor ocr.py to scrape for immigration court cases instead of BIA cases

Description
This pull request is submitted to change the name of the BIACase class to IJCase class to reflect the decision that the application will not receive BIA appellate cases but will focus on initial immigration court cases.
In addition, the PR refactors the code in the following functions in ocr.py:
get_date
get_outcome
get_application
These refactors are designed to more accurately scrape data from immigration court cases (as those cases follow a different pattern than BIA cases).
Fixes # (no number assigned)

Fixes a bug in ocr.py due to path change from BIA cases to immigration cases

Co-authored with @EmilyAFlener and @mathewmahoneyds20 in pair-programming session.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have removed unnecessary comments/console logs from my code
[ ] I have made corresponding changes to the documentation if necessary (optional)
[x] My changes generate no new warnings
[x] I have checked my code and corrected any misspellings
[x] No duplicate code left within changed files
[x] Size of pull request kept to a minimum
[x] Pull request description clearly describes changes made & motivations for said changes

https://www.loom.com/share/cebfe73b51fc4bf5946a7ba02ef7f0e0

To confirm in writing: what was formerly lines 335-354 is now a nested if statement, seen in lines 333-349, and the newly created primary if statement is now a negation. This move should proactively address the prior blocker that multiple protected grounds were be produced when only one can be in real life.

Emily, this PR does not address the protected_grounds issue . We discussed it during our session but since this requires more extensive code refactor (writing a new function and adding it to lines 335-354), we did not include it in this PR. We will work on this later today and submit a separate PR.


Add static publishing support

"Present" now links to the static publishing domain, and that link is
externalizable and usable by any user.

+1 this feature so much

It looks like there's some trouble with python3 and spk dev's tracing behavior when actually producing an .spk, so I've added a second commit here that fixes some issues I was having when I was testing an spk pack'd artifact.
There's some more discussion in the commit message, but the gist of it is "alwaysInclude things we know are relevant, and try to avoid putting large useless things in those folders."  It's possible we'll adjust spk dev's tracing to try to work around this sort of thing in the future, but for now, this makes Hacker Slides work as packed again. :)
FYI, you'll probably want to vagrant-spk destroy and vagrant-spk up and test before publishing the next package, to ensure things are working cleanly in a fresh environment.

This is awesome :) Sorry it took me so long to get to it. I will try to put out a release tomorrow. :+1:


Cannot able to create new object of System.Text.Json.JsonDocument

Issue Title
I started exploring new json apis and found out that this is useful only if I have class model with me.
In some cases where I might need to create new jsondocument, it seems to be no option.
Using Newtonsoft.json I can create new json object using JContainer, there is not option to create object from AdHoc JsonDocument.
Can you please add option to create new JsonDocument without using streams.
General
Version : 3.0.100

@ahsonkhan can you help here?

@ahsonkhan do you need any information about this?

@tinyVishal - the JsonDocument APIs that were shipped in .NET Core 3.0 are "read-only", so the only way to build one up is to call the static Parse API on it, passing in the JSON payload.
It looks like you are looking for a way to build up a JsonDocument from scratch, and we are working on a solution for such a capability for 5.0 ("writable DOM", similar to JContainer/JObject/JArray in Newtonsoft.Json).
See this issue to track that feature:
https://github.com/dotnet/corefx/issues/39922
Here's the current spec (see type hierarchy around JsonNode):
https://github.com/dotnet/runtime/blob/master/src/libraries/System.Text.Json/docs/writable_json_dom_spec.md
Feel free to re-open this issue. Otherwise, please give those types a try (they are available in the 5.0 nightly builds) and provide feedback by filing issues in https://github.com/dotnet/runtime.

You have to be kidding me, right? You just now realize that this is needed?
I am not kidding best of my knowledge. I feel you are

@tinyVishal My comment wasn't directed at you, but at @ahsonkhan and Microsoft. I find it ridiculous that they shipped an API that is hobbled in such an obvious way, and that they think it fine to push it to a "Future" milestone, rather than hide their faces in shame at being called out for such a glaring design flaw.

@tinyVishal My comment wasn't directed at you, but at @ahsonkhan and Microsoft. I find it ridiculous that they shipped an API that is hobbled in such an obvious way, and that they think it fine to push it to a "Future" milestone, rather than hide their faces in shame at being called out for such a glaring design flaw.

Let's try to be constructive here. I understand that this is a limitation, but it's not "hobbled together". It was a deliberate design decision to make the DOM APIs read0only in order to provide a very low memory footprint for a DOM. We have been thinking about read/write access as well, but we didn't have time this release as we worked on other features.

@tinyVishal My comment wasn't directed at you, but at @ahsonkhan and Microsoft. I find it ridiculous that they shipped an API that is hobbled in such an obvious way, and that they think it fine to push it to a "Future" milestone, rather than hide their faces in shame at being called out for such a glaring design flaw.

Let's try to be constructive here. I understand that this is a limitation, but it's not "hobbled together". It was a deliberate design decision to make the DOM APIs read0only in order to provide a very low memory footprint for a DOM. We have been thinking about read/write access as well, but we didn't have time this release as we worked on other features.

I know the design philosophy, but to produce a "standard" api which does not at least equal in functionality that of the "de-facto standard" it purports to replace without a pre-determined plan to reach parity is a recipe for chaos and confusion. It would have been better to leave Newtonsoft as the favored API until such time as you had something that was feature-complete, rather than push as standard something which is inferior.  The fact that you say it was "deliberately designed" that way doesn't change that fact; it may even make it worse.
You have to understand that architects and development leads have to make decisions as to the stacks they use and impose on their teams. Those decisions are made more complex every time there's a conflict between a standard "effort" and a non-standard one which advanced developers may not have any difficulties handling, but which lead to steeper learning curves for more junior developers, especially when they have to try to find proper resources to ramp on new technologies. It's much easier to provide training on the official standards than on a host of "de-facto" alternatives, but this is defeated when the standard is so deeply inferior.
Microsoft has had a long history of this kind of shenanigans, and has caused people in positions of leadership within development no end of unnecessary evaluations of alternatives and the development of transitional learning plans and technology introductions. This is only the latest in such controversies.

I know the design philosophy, but to produce a "standard" api which does not at least equal in functionality that of the "de-facto standard" it purports to replace without a pre-determined plan to reach parity is a recipe for chaos and confusion. It would have been better to leave Newtonsoft as the favored API until such time as you had something that was feature-complete, rather than push as standard something which is inferior.

We never said we're planning to replace JSON.NET. We have said very openly from the beginning that our goal is to focus on performance.

You have to understand that architects and development leads have to make decisions as to the stacks they use and impose on their teams.

I totally agree with this point.

It's much easier to provide training on the official standards than on a host of "de-facto" alternatives, but this is defeated when the standard is so deeply inferior.

While I agree that we have feature gaps, I think inferiority is also a function of desired properties, which aren't uniform across all our customers. And most of the time you can't build an API that is good at everything that is being asked of it without making compromises somewhere. For example, we heavily optimized the lower layers (reader/writer) to be performant, without sacrificing security/spec compliance. Unfortunately, this comes with complexity in API design which hurts usability and, as it is with the DOM, sometimes feature set as well.

Microsoft has had a long history of this kind of shenanigans, and has caused people in positions of leadership within development no end of unnecessary evaluations of alternatives and the development of transitional learning plans and technology introductions. This is only the latest in such controversies.

What you call shenanigans I call design and design comes with trade offs. In my opinion, the best we can do is being transparent in our design process, share previews, collect customer feedback, and address it accordingly. As I said, our goal wasn't to put JSON.NET inbox. If that would have been it, we would have just done that.


Added Lebanese American University (LAU) Domain

Added the Lebanese American University (LAU) Domain

@fchamieh I am sorry, the domain lau.edu is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Update assignment.md

[
report summary nypost.pdf
report summary nypost.pdf
](https://nypost.com) 12 April 2021 on notebook 15" screen
paragraph because site is inadequate
Most of background is white, sports-metro-entertainment-business-opinion-fashion-shopping-living-real estate-tech-media have the same format (dimension, type of character) so they are little distinguishable among them and they are set in 2/3 width so there is lot of space white.
There are many pictures, but description inside of pictures in white are not very visible. There are 3 kind of popup. Sections aren't in alphabetical order so you have to look for the right item in the list. by reading.
If i write "Tech" in search, it doesn't go to tech section
Lighthouse analysis attached in report summary nypost.pdf file.
-Performance is very low 12, so the storage need to be improved to not load all at the same time or by eliminating render-blocking resources, or by Reduce JavaScript execution time — 28.4 s , or by Minimize main-thread work — 44.4 s, Reduce the impact of third-party code — Third-party code blocked the main thread for 14,140 ms.
Some URLs require tot of time to load /scripttemplates/otSDKStub.js 5.8 KiB 370 ms; …css/jetpack.css?ver=9.4.1 13.8 KiB 90 ms; /nc-nypost/op.js 14.3 KiB 840 ms
Serve static assets with an efficient cache policy — 79 resources found
Avoid an excessive DOM size — 1,951 elements
-Accessibility 80
Background and foreground colors do not have a sufficient contrast ratio.
-Navigation with keyboard can be improved:
[id] attributes on active, focusable elements are not unique, Heading elements are not in a sequentially-descending order
-Names and labels — These are opportunities to improve the semantics like a screen reader.
Image elements do not have [alt] attributes, Links do not have a discernible name
Image elements do not have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS.  Show 3rd-party resources (1) URL
Failing Elements …04/alaska-woman-covid-twice-hp.jpg?quality=… img;  …04/britt-reid-charged-hp3.jpg?quality=… img
Trust and Safety:
Links to cross-origin destinations are unsafe, Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Browswe/console Browser errors were logged to the console
SEO 92 These checks ensure that your page is optimized for search engine results ranking
Format HTML for images elements which do not have [alt] attributes
There aren't Interactive elements like buttons
PWA Web app manifest or service worker do not meet the installability requirements — 2 reasons
Does not register a service worker that controls page and start_url
Is not configured for a custom splash screen
Failures: Manifest does not have background_color, Manifest does not have theme_color.
Does not set a theme color for the address bar.
Failures: Manifest does not have theme_color, No <meta name="theme-color"> tag found.
Manifest doesn't have a maskable icon
Web page is powered by WordPress.com VIP

Hi @Giulia-Caldato please don't post assignment solutions here as it degrades the course experience for other students. If you are a part of a cohort please submit assignments on Moodle. Are you enrolled in our school? Please reach out at<EMAIL_ADDRESS>so I can understand your situation


Error when requesting a new account

Hi All,
I'm trying to request a new account but I keep on getting this info "Something went wrong. Please try again later.". Is there any issue with the platform right now?
Thanks,
Greg

Our service works normally. But we do not offer the service in the specific countries. Please refer the following FAQ.
https://studiolab.sagemaker.aws/faq

Are you getting this error with the CAPTCHA challenge? If so please try upgrading your browser or trying a different one.  We have seen some issues with an older version of FireFox.

Can we close this ?

Dear @GregLed , we close this issue but feel free if you still have the problem.

The same for me and my country is not banned.

I tried everything for the past few days I haven't been able to access an instance once. I tried everything. I even deleted the account and made a new one which was approved once again. When I went to finish the registration in the link the same error occurs. It seems to be a backed error or something

I have tried the same things for the past few days I am not able to login to my account. I have changed the browser, cleared the cache tried login in incognito.

Also, a week ago the error occurred rarely when logging in, the captcha did not come up, and it was refreshing the page. But yesterday it doesn't let me log in anymore, I tried with other browsers and it didn't work either.

For the recent issue about "Something went wrong. Please try again later.", we are handling this error in the following issue. Please refer to get the recent status and temporary solution.
https://github.com/aws/studio-lab-examples/issues/254

Hi All,
I'm trying to request a new account but I keep on getting this info "Something went wrong. Please try again later.". Is there any issue with the platform right now?
Thanks,
Ameer Hamza


Remove suspend lambda rule with CoroutineScope receiver due to not de…

…fined behaviour https://youtrack.jetbrains.com/issue/KTIJ-21167
Fixes #4746

@schalkms Nope, the lambda behavior wasn't documented :D


WIP: Consolidate reuse

Initial commit. Initial design gave too many cascading errors. Verbose code currently, will work on simplifying.

Replaced by PR #1548


Implement render mode property for iOS

Upgrade lottie-ios to v3.4.1, which included fixes such as https://github.com/airbnb/lottie-ios/pull/1660
Implement render mode for iOS, so we can switch render engine by set renderMode prop

AUTOMATIC: Select Core Animation and fallback to Main Thread if not supported
HARDWARE: Core Animation (More info)
SOFTWARE: Main Thread

Update renderMode in API documentation
Example: Add render mode picker

Resolved the conflicts.
For example, I also changed the render mode picker to use a dropdown, which reduces the height used.


tests: For ldap tests, give each ldap user a unique password.

This is the last remaining follow-up from the ancient https://github.com/zulip/zulip/pull/13256#issuecomment-545194215 - specifically the point:

We should rework the self.ldap_password function to accept the username as an argument and give the users different passwords. Having every LDAP user possess the same password is a bug land mine where the test isn't testing what one thinks it is.

This is great, merged, thanks @mateuszmandera!


Support opening multiple selected articles in the browser at once

This pull request implements #857.
My approach was to look for all interactions open an article in the browser, and replace that with an implementation supporting multiple. Since a collection can contain a single item, this enabled the new functionality while preserving the existing.
All these interactions start with the user selecting one or more articles in the TimelineView. Then one of the following things can be done:

Press Article in the menu bar, and select Open in Browser.
Press ⌘ + →.
Press enter.
Right-click and select Open in Browser from the context menu.
Press the globe icon in the right corner of the application.
Double-click on one of the selected articles. I was uncertain whether this should open all selected items or only the one that is double-clicked. To make a decision I looked at how the built-in applications behave – they do the former (see for example Mail.app or Finder).

Before I consider this implementation to be done I need some advice about when to consider an article to be read. Today when an article is selected it is shown in the DetailView and therefore marked as read. When multiple articlesare selected, only the first one (that was shown in the DetailView before it says "Multiple selection") is marked as read.
Do we consider an article opened in the browser to be read? Today's "Open in Browser" functionality does not care about read status at all – which leads to it to for example be possible to right click an article, open it in the browser and it will still be marked as unread in the app.
Selecting and opening multiple articles in the browser makes this behaviour more prominent in more interactions, and I think it would be wise to make a decision on how it should be handled for future implementations involving this too.

Thanks!
This needs two more things:

If the number of selected articles is above a certain number, then just ignore it entirely. Assume it’s an error. Let’s go with 500 for that number.

If the number of selected articles is above 20, then we need a confirmation sheet along the lines of: “Are you sure you want to open [number] pages in your browser?” [Cancel] [Open [number] pages]

Will fix, both things seem really reasonable 👍 Thanks!
How about marking them as read when opened in the browser?

@hugolundin Are you still working on @brentsimmons changes?  I'm just trying to figure out if this is a zombie pull request or if you are still interested in it.

Yes, sorry. I started my first year at a computer engineering program 4 weeks ago and haven't had time to complete it. Looking to do it soon, if it is OK? :)

Absolutely!  Take your time.  I just don't like leaving dead pull requests laying around, so I asked.

I haven’t and probably won’t have time to work in this for a while. Happy to let someone else work in it if they want to.

Thanks for letting us know!  I'll close this pull request.


Change "paste" to "type"

Copy-pasting into a terminal can be dangerous. See this. Thus I've changed "paste" to "type". People are probably going to do this anyway but there is not need to suggest copy-pasting sudocommands.
sudo is not required to do a global npm install (of course you can do it). Thus I've removed the "sudo" for the flow install command. This is consistent with the general getting started page where sudo isn't used in front of npm install -g either.

By analyzing the blame information on this pull request, we identified @DavidYKay and @clickthisnick to be potential reviewers.

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.


ansible-lint exits when using newer role dependency dict structure

Issue Type

Bug report

Ansible and Ansible Lint details
ansible --version: <IP_ADDRESS>
ansible-lint --version: 3.1.2

ansible installation method: homebrew
ansible-lint installation method: pip

Desired Behaviour
Command should not exit with error when role dependency is in newer dictionary format
Actual Behaviour (Bug report only)
When a role dependency in meta/main.yml is defined like so:
dependencies:
  - name: my-role
    src: https://example.com/my-role.git
    scm: git

Errors with with:
role dict {u'src': u'https://example.com/my-role.git', u'name': u'my-role', u'scm': u'git'} does not contain a "role" key
Defining a role dependency providing the rolespec format in the role key appears to be deprecated in ansible <IP_ADDRESS>.

I'm seeing the same bug.  This is the ansible code that seems to be used for parsing such declarations.  https://github.com/ansible/ansible/blob/devel/lib/ansible/playbook/role/requirement.py#L122  It looks like the logic around parsing these is complicated.   Would it make sense to use the ansible RoleRequirement parser here if it's available?  Obviously that would only work if ansible 2.x were installed.

@azenk, RoleRequirement is used for the requirements.yml file when installing roles through ansible-galaxy. RoleDefinition's _load_role_name is all we need here, and the current code just needs an equivalent to https://github.com/ansible/ansible/blob/devel/lib/ansible/playbook/role/definition.py#L116 to work.

Pushed test release as 3.3.0rc1

Fixed in released 3.3.0

REGRESSION
Successfully installed MarkupSafe-1.0 ansible-<IP_ADDRESS> ansible-lint-3.4.12 asn1crypto-0.22.0 cffi-1.10.0 cryptography-1.8.1 idna-2.5 jinja2-2.9.6 paramiko-2.1.2 pyasn1-0.2.3 setuptools-35.0.2
demo:buildserver bas$ ansible-lint provision.yml
role dict {u'src': u'base_java8'} does not contain a "role" or "name" key


Congrats on being put "in the box"!

Cool to see this awesome extension bundled with vscode now! (How'd ya pull that one off?) ;)

Thanks @eamodio! The team reached out to me last week about merging the extension, so I was all for it. I work at Microsoft, so it was awesome to go over to Redmond and spend the day with the team, meet them and work on merging the code in.
Thanks for your contributions to the extension, and for the PR to fix the compare changes title in the vscode code base 👍


Errors when decoding with language model in wav2vec2.0

🐛 Bug
I am trying to reproduce the number in wav2vec2.0 paper with the released model.  The code works well when I set --w2l-decoder=viterbi to reproduce the CTC results. However, when I set --w2l-decoder='kenlm' or 'fairseqlm'. I met the following errors:
For Kenlm, I download the lm_librispeech_kenlm_word_4g_200kvocab.bin in https://github.com/facebookresearch/wav2letter/tree/master/recipes/models/sota/2019. Running command
'python examples/speech_recognition/infer.py /path/to/manifest/ --task audio_pretraining --nbest 1 --path /path/to/mymodel --gen-subset dev_clean --results-path /path/to/results --w2l-decoder kenlm --lm-model /path/to/lm_librispeech_word_transformer.pt --lm-weight 2 --word-score -1 --sil-weight 0 --criterion ctc --labels ltr --max-tokens 4000000 --post-process letter'
The code reports error in line 137 "self.lexicon = load_words(args.lexicon)" in fairseq/examples/speech_recognition/w2l_decoder.py as args.lexicon is None. I can't find lexicon file in model repository. Can you upload it?
For Transformer, I download the released transformer language model and dictionary in wav2letter repository.
My command is
'python examples/speech_recognition/infer.py /path/to/manifest/ --task audio_pretraining --nbest 1 --path /path/to/mymodel --gen-subset dev_clean --results-path /path/to/results --w2l-decoder fairseqlm --lm-model /path/to/lm_librispeech_word_transformer.pt --lm-weight 2 --word-score -1 --sil-weight 0 --criterion ctc --labels ltr --max-tokens 4000000 --post-process letter'
There are several issues:

The arguments in the released model do not match the arguments defined in transformer_lm.py. For example, there is no args.decoder_layers_to_keep in lm_librispeech_word_transformer.pt. It seems the language model is not trained with the code in master branch.
I have tried to replace fairseq/models/transformer_lm.py and fairseq/models/transformer.py with the same files in branch v0.7.0.  The command didn't report errors. However, the hypothesis is too too bad (much worse than viterbi decoding)! Can you upload the pretrained model that compatible with master branch and give more details of hyperparameters?

Environment
I use the docker wav2letter/wav2letter:cuda-latest

fairseq Version : master
PyTorch Version :  1.4.0
OS : Ubuntu18.04
How you installed fairseq (pip, source): pip
Build command you used (if compiling from source):
Python version: 3.6.9
CUDA/cuDNN version: 10.0

Additional context

Hi @cywang97 , I'm actually trying to use this wav2vec 2.0 model, to use as ASR, so that it can listen to the audio files and give an transcript of it as output, can you suggest how can I proceed with it ?
Thanks in advance..

Hi @cywang97 , I'm actually trying to use this wav2vec 2.0 model, to use as ASR, so that it can listen to the audio files and give an transcript of it as output, can you suggest how can I proceed with it ?
Thanks in advance..

Hi, I think you can simply run the proposed decoding command with --w2l-decoder viterbi to get the raw number without language model.

Please make sure you have python binding of wav2letter.
In your /path/to/manifest, you need to prepare the following files (take dev_clean subset as an example):
dev_clean.ltr
dev_clean.tsv
dev_clean.wrd.txt
dict.ltr.txt

Here's the lexicon:
https://dl.fbaipublicfiles.com/fairseq/wav2vec/librispeech_lexicon.lst
I will link it in the readme soon

Thanks @cywang97 for your response. I'll try it but have some doubts if you may help. In the command, how will I add my raw audio file without any labels, so that the model can create the transcript by itself and about " dev_clean.ltr, dev_clean.tsv, dev_clean.wrd.txt " are these the files that were created by "manifest" command using the pretrained Librispeech model ?

that error is a bug recently introduced by constraints-based decoding. i'll push a fix through, meanwhile you can just checkout a copy of the code before that commit or you can change the signature of "generate" in w2l_decoder.py to
def generate(self, models, sample, **unused):

@alexeib thanks for the suggestion, it's working.
But I'm still facing issue while trying to use kenlm LM. I've downloaded the librispeech_lexicon.lst as suggested by you, but my problem is still not solved, can you please help me on that

Thanks @alexeib for quick response, really helped.

Thanks @alexeib for quick response, really helped.

@MrityunjoyS What were the content for dev_clean.ltr,  dev_clean.wrd.txt . I could get tsv file from manifest but not able to know what will be content of these file. I am also trying to get text from raw audio file. Could you help with sample command or file?

Hi @cywang97 , I'm actually trying to use this wav2vec 2.0 model, to use as ASR, so that it can listen to the audio files and give an transcript of it as output, can you suggest how can I proceed with it ?
Thanks in advance..

Hi, I think you can simply run the proposed decoding command with --w2l-decoder viterbi to get the raw number without language model.

Please make sure you have python binding of wav2letter.
In your /path/to/manifest, you need to prepare the following files (take dev_clean subset as an example):
dev_clean.ltr
dev_clean.tsv
dev_clean.wrd.txt
dict.ltr.txt

@cywang97 Do you need the  wav2letter binding even when you do not use LM? I have finetuned the Wav2Vec 2.0 Base on 100h and it worked well. For inferenceI am running a similar command to yours but I do not have wav2letter binding
python examples/speech_recognition/infer.py examples/wav2vec/data/ --task audio_pretraining --nbest 1 --path examples/wav2vec/outputs/2021-01-03/21-08-21/checkpoints/checkpoint_best.pt --gen-subset dev_other --results-path examples/wav2vec/results/ --w2l-decoder=viterbi --word-score -1 --sil-weight 0 --criterion ctc --labels ltr --max-tokens 4000000 --post-process letter
and I am getting the following error
main(args)
File "examples/speech_recognition/infer.py", line 240, in main
task.load_dataset(args.gen_subset, task_cfg=saved_cfg.task)
File "/alt-arabic/speech/amir/fairseq/fairseq/tasks/audio_pretraining.py", line 135, in load_dataset
task_cfg.autoregressive = not task_cfg.criterion == 'ctc'
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/dictconfig.py", line 297, in getattr
self._format_and_raise(key=key, value=None, cause=e)
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/base.py", line 101, in _format_and_raise
type_override=type_override,
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/_utils.py", line 629, in format_and_raise
_raise(ex, cause)
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/_utils.py", line 610, in _raise
raise ex  # set end OC_CAUSE=1 for full backtrace
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/dictconfig.py", line 295, in getattr
return self._get_impl(key=key, default_value=DEFAULT_VALUE_MARKER)
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/dictconfig.py", line 353, in _get_impl
node = self._get_node(key=key)
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/dictconfig.py", line 375, in _get_node
self._validate_get(key)
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/dictconfig.py", line 128, in _validate_get
key=key, value=value, cause=ConfigAttributeError(msg)
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/base.py", line 101, in _format_and_raise
type_override=type_override,
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/_utils.py", line 694, in format_and_raise
_raise(ex, cause)
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/_utils.py", line 610, in _raise
raise ex  # set end OC_CAUSE=1 for full backtrace
omegaconf.errors.ConfigAttributeError: Key 'criterion' is not in struct
full_key: task.criterion
reference_type=Any
object_type=dict

Hi @cywang97 , I'm actually trying to use this wav2vec 2.0 model, to use as ASR, so that it can listen to the audio files and give an transcript of it as output, can you suggest how can I proceed with it ?
Thanks in advance..

Hi, I think you can simply run the proposed decoding command with --w2l-decoder viterbi to get the raw number without language model.

Please make sure you have python binding of wav2letter.
In your /path/to/manifest, you need to prepare the following files (take dev_clean subset as an example):
dev_clean.ltr
dev_clean.tsv
dev_clean.wrd.txt
dict.ltr.txt

@cywang97 Do you need the  wav2letter binding even when you do not use LM? I have finetuned the Wav2Vec 2.0 Base on 100h and it worked well. For inferenceI am running a similar command to yours but I do not have wav2letter binding
python examples/speech_recognition/infer.py examples/wav2vec/data/ --task audio_pretraining --nbest 1 --path examples/wav2vec/outputs/2021-01-03/21-08-21/checkpoints/checkpoint_best.pt --gen-subset dev_other --results-path examples/wav2vec/results/ --w2l-decoder=viterbi --word-score -1 --sil-weight 0 --criterion ctc --labels ltr --max-tokens 4000000 --post-process letter
and I am getting the following error
main(args)
File "examples/speech_recognition/infer.py", line 240, in main
task.load_dataset(args.gen_subset, task_cfg=saved_cfg.task)
File "/alt-arabic/speech/amir/fairseq/fairseq/tasks/audio_pretraining.py", line 135, in load_dataset
task_cfg.autoregressive = not task_cfg.criterion == 'ctc'
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/dictconfig.py", line 297, in getattr
self._format_and_raise(key=key, value=None, cause=e)
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/base.py", line 101, in _format_and_raise
type_override=type_override,
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/_utils.py", line 629, in format_and_raise
_raise(ex, cause)
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/_utils.py", line 610, in _raise
raise ex  # set end OC_CAUSE=1 for full backtrace
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/dictconfig.py", line 295, in getattr
return self._get_impl(key=key, default_value=DEFAULT_VALUE_MARKER)
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/dictconfig.py", line 353, in _get_impl
node = self._get_node(key=key)
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/dictconfig.py", line 375, in _get_node
self._validate_get(key)
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/dictconfig.py", line 128, in _validate_get
key=key, value=value, cause=ConfigAttributeError(msg)
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/base.py", line 101, in _format_and_raise
type_override=type_override,
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/_utils.py", line 694, in format_and_raise
_raise(ex, cause)
File "/home/local/QCRI/ahussein/anaconda3/envs/espnet/lib/python3.7/site-packages/omegaconf/_utils.py", line 610, in _raise
raise ex  # set end OC_CAUSE=1 for full backtrace
omegaconf.errors.ConfigAttributeError: Key 'criterion' is not in struct
full_key: task.criterion
reference_type=Any
object_type=dict


linux: update header used for major macro

Newer versions of glibc indicate that they intend to move the major
macro from sys/types.h to sys/sysmacros.h.  Add a check for the
header and include that earlier to ensure that the macro is provided by
the newer header when available/possible.  This avoids an unnecessary
warning from the system headers.

CC: @das @dgrove-oss

Since I put this up on a weekend, a gentle ping during the work week!

swift-corelibs-libdispatch/os/linux_base.h:16:10: fatal error: 'config/config_ac.h' file not found
#include <config/config_ac.h>
^

huh, my bad for suggesting that then, but why is that not working, we have
AC_CONFIG_HEADER([config/config_ac.h])
in configure.ac, that was supposed (we really don't want config/config.h to be used on Linux since that is the static Darwin config)

looks like it is the latter, from (3138)[https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04/3818/console]:
[554/850] Building CXX object tools/SourceKit/lib/Support/CMakeFiles/SourceKitSupport.dir/Concurrency-libdispatch.cpp.o
FAILED: tools/SourceKit/lib/Support/CMakeFiles/SourceKitSupport.dir/Concurrency-libdispatch.cpp.o
/usr/bin/clang++   -DCMARK_STATIC_DEFINE -DGTEST_HAS_RTTI=0 -D_DEBUG -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Itools/SourceKit/lib/Support -I/home/buildnode/disk2/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/swift/tools/SourceKit/lib/Support -I/home/buildnode/disk2/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/swift/tools/SourceKit/include -Iinclude -I/home/buildnode/disk2/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/swift/include -I/home/buildnode/disk2/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/llvm/include -I/home/buildnode/disk2/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/llvm-linux-x86_64/include -I/home/buildnode/disk2/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/llvm-linux-x86_64/tools/clang/include -I/home/buildnode/disk2/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/llvm/tools/clang/include -I/home/buildnode/disk2/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/cmark/src -I/home/buildnode/disk2/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/buildbot_incremental/cmark-linux-x86_64/src -I/home/buildnode/disk2/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/swift-corelibs-libdispatch -Wno-unknown-warning-option -Werror=unguarded-availability-new -fno-stack-protector -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -Werror=date-time -std=c++11 -fcolor-diagnostics -ffunction-sections -fdata-sections -Werror=switch -Wdocumentation -Wimplicit-fallthrough -Wunreachable-code -Woverloaded-virtual -DOBJC_OLD_DISPATCH_PROTOTYPES=0 -O3    -UNDEBUG  -fno-exceptions -fno-rtti -target x86_64-unknown-linux-gnu -O2 -g0 -UNDEBUG -fblocks -MMD -MT tools/SourceKit/lib/Support/CMakeFiles/SourceKitSupport.dir/Concurrency-libdispatch.cpp.o -MF tools/SourceKit/lib/Support/CMakeFiles/SourceKitSupport.dir/Concurrency-libdispatch.cpp.o.d -o tools/SourceKit/lib/Support/CMakeFiles/SourceKitSupport.dir/Concurrency-libdispatch.cpp.o -c /home/buildnode/disk2/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/swift/tools/SourceKit/lib/Support/Concurrency-libdispatch.cpp
In file included from /home/buildnode/disk2/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/swift/tools/SourceKit/lib/Support/Concurrency-libdispatch.cpp:19:
In file included from /home/buildnode/disk2/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/swift-corelibs-libdispatch/dispatch/dispatch.h:30:
/home/buildnode/disk2/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/swift-corelibs-libdispatch/os/linux_base.h:16:10: fatal error: 'config/config_ac.h' file not found
#include <config/config_ac.h>
         ^

the existing HAVE_SYS_CDEFS_H case almost certainly has the same issue and should be fixed the same way

Okay, Ill create a new PR to change it over.


Improve metric markdown generation

Support to generate markdown for metrics from yaml was added in open-telemetry/build-tools#79.
I'm currently moving the existing "hard-coded" metric semantic convention from the markdown files to yaml and I noticed a few things that can be improved:

Generate metric name/header/description automatically:

For example, in the runtime-environment-metrics the metrics are organized as such:
### Metric: `process.runtime.jvm.memory.usage` (1)

This metric is [recommended][MetricRecommended]. (2)
...

When moving the metrics to YAML, to be able to achieve the same output as above, I need to manually add the (1) header and the recommendation.

The header we can generate, since we have all the information
The "This metric is recommended.." I don't think we have this field in the data model, so we might need to include it

In the end, it would be great if the only thing required to generate consistent markdown, are the placeholders such as
<!-- semconv metric.system.cpu.time(metric_table) -->
<!-- endsemconv -->

<!-- semconv metric.system.cpu.time(full) -->
<!-- endsemconv -->

And that would generate
### Metric: `process.runtime.jvm.memory.usage`

This metric is [recommended][MetricRecommended].

<metric table>

<metric attribute table>

@joaopgrassi I think you should be able to expand support for metric tables directly in semconv via the JINJA templates now.


Repo transfer

HI @6ui11em
Can you transfer this repo to me please ? Or add me as a contributor ? I have a couple of patches I'd like to make. Thanks!

Hi @nitriques,
I just transfered this repo. Thank you to take care of it!

Thanks a lot! Do you want push access ? I'll be moving it to Deux Huit Huit.

It’s not necessary, Thank you.

On May 18, 2016, at 4:52 PM, Nicolas Brassard<EMAIL_ADDRESS>wrote:
Thanks a lot! Do you want push access ? I'll be moving it to Deux Huit Huit.
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub

Perf! Thanks again!


cmd/cue: executing the import command twice does not give the same result

Originally opened by @juanjoku in https://github.com/cuelang/cue/issues/850
What version of CUE are you using (cue version)?
It can be reproduced with cue-v0.2.2 and cue-v0.3.0beta.7.
Does this issue reproduce with the latest release?
Yes
What did you do?
We have found a strange behavior in the command cue import.
Suppose this directory structure:
├── dir1
│   ├── dir2
│   │   └── file3.json
│   └── file2.json
└── file1.json

The first time cue import is executed, only file3.json is converted:
$ cue import -f -p mypackage ./dir1/dir2
$ tree
.
├── dir1
│   ├── dir2
│   │   ├── file3.cue
│   │   └── file3.json
│   └── file2.json
└── file1.json

But, if the same command is executed again, file1.json and file2.json are converted !!
$ cue import -f -p mypackage ./dir1/dir2
$ tree
.
├── dir1
│   ├── dir2
│   │   ├── file3.cue
│   │   └── file3.json
│   ├── file2.cue
│   └── file2.json
├── file1.cue
└── file1.json

The workaround to avoid this behaviour is specify "files" instead of "directory" as source for cue import:
$ cue import -f -p mypackage ./dir1/dir2/*
$ cue import -f -p mypackage ./dir1/dir2/*  # twice
$ tree
.
├── dir1
│   ├── dir2
│   │   ├── file3.cue  # only file3.json has been converted
│   │   └── file3.json
│   └── file2.json
└── file1.json

What did you expect to see?
The same result in both executions (it is not clear to me which is expected)

I think this issue has been resolved, or at least I have not reproduced it with CUE v0.4.3.


cmd/go: -compiler gccgo should allow specifying the compiler to use

Currently, if you specify -compiler gccgo, go build and friends will just invoke the
'gccgo' binary that's found on $PATH.  This is limiting -- in particular it makes using
a cross-compiling gccgo harder.

(You can always put a symlink to your cross-gccgo called "gccgo" in some
tmpdir and stick it on the front of $PATH... but ick)

Fixed by 8b836fa8; use $GCCGO to control the compiler.


Customizable ID is not working in collapsible

Bug Report
Use Customizable ID inside collapsible is not working.
Example of Collection Config
const Examples: CollectionConfig = {
  slug: "examples",
  admin: {
    useAsTitle: "someField",
  },
  fields: [
    {
      label: "Page Info",
      type: "collapsible",
      fields: [
        {
          name: "id",
          type: "text",
        },
        {
          name: "someField",
          type: "text",
        },
      ],
    },
  ],
};

Expected Behavior
It should use the user input id instead of auto gen
Current Behavior
It auto generated the id after saved.

Currently it is only possible to have a custom ID at a top level on a collection. This is a known limitation. We would consider accepting a PR that allows the custom ID to exist in a row, collapsible or tab with no name assigned.


feat(array-methods-2): news flash challenge

rendered: https://github.com/neuefische/web-exercises/tree/feat/js-array-methods-2/news-flash/sessions/js-array-methods-2/news-flash
CSB
refers to neuefische/web-curriculum-new-format#131

Nice work! Here's my solution. :)
I think it might be a little easier to tell if the second part of the exercise worked if the lengths of the bodies were a little more dramatically different ( - or add a check/test of some sort, something similar to my own maybe). I'm also unsure if we need mock data that's 100 objects heavy at first, then 51 objects after filtering. Perhaps it would be better to have a smaller number after the filtering, like 20 or so?
Just some thoughts. :)


Ajust style, and bug in button

Ajust style of button to align center, and ajust bug on connect github button o profile page.

PR tá com conflito com a nossa main

Resolved


add animation color and scale Favorite icon

@sajjad-dehnavi And again, thanks for. this amazing PR! 😍🤝🏻


Yeoman Sharepoint generator always creates Preview project

Category

[ ] Issue :  After installing latest Yo @microsoft generator when i try to create a project, even if i select the type of client side component as Webpart, the next option appears as Which type of Client side extension to create.

Steps to Reproduce
Please refer to the screenshot for the issue. I am selecting the component type as Webpart, the next option presented is with the component type as Extension.

The sharepoint generator version i have is 1.2.0
Please help!
Also, i need instructions to remove and uninstall the yeoman Sharepoint generator from my system to do clean install. I tried to execute npm -uninstall -g generator<EMAIL_ADDRESS>nothing happens.

Hi @kspranesh,
we can't seem to reproduce the issue with the given information, so would double check following things.
Ensure that you have uninstalled old package and reinstalled new version
Uninstall old version by executing npm uninstall --global @microsoft/generator-sharepoint, which will clean up any old version of the generator. You can then double check all the installed packages globally by using npm list -g --depth=0 to confirm that uninstallation has been completed.
After this you can then simply install the latest package by executing npm install -g @microsoft/generator-sharepoint.
Version details
if this does not resolve your issue, we would need additional details to get your issue resolved, which would be following:

What OS you're using?
What's your Node version?
What's your npm version?

This way we can potentially reproduce the issue, which is a prerequisite to get it resolved based on facts.
Thanks for the additional details advance.

Hi @VesaJuvonen
Many thanks for looking into my request. I followed the steps you mentioned to ensure i have removed and re-installed latest version of sharepoint generator and verified that issue still persists. Please find attached are few screenshots from my testing. I am executing this on Windows 10 OS.

Kindly let me know if you need any further details.
Regards,
Pranesh

I'm seeing the same issue here.

Can't reproduce with Win 10 so we would need more details around the setup what you're using.
What's your Node version? - node -v
What's your npm version? - npm -v
This helps on doing a repro for the issue.

Hmm... I'm running exactly the same versions locally on my machine without any issues, tested with different console UIs as well. Let me test this with clean Win10 in Azure for trying to do repro.

Hi,
It worked for me 2 days back and when yesterday i tried to add new webpart to the same project i started seeing this issue. Later on i created an entirely new project to verify and this issue occurred even there.
Regards,
Pranesh

From: Vesa Juvonen<EMAIL_ADDRESS>Sent: Wednesday, August 30, 2017 5:41 PM
To: SharePoint/sp-dev-docs
Cc: kspranesh; Mention
Subject: Re: [SharePoint/sp-dev-docs] Yeoman Sharepoint generator always creates Preview project (#816)
Hmm... I'm running exactly the same versions locally on my machine without any issues, tested with different console UIs as well. Let me test this with clean Win10 in Azure for trying to do repro.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/SharePoint/sp-dev-docs/issues/816#issuecomment-326065767, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMQKeOhbapZwRXiAOyi5W4wDIQ97uVz4ks5sdZ7SgaJpZM4PGyp7.

@VesaJuvonen , what is the best way to recognize if RC0 is used or an earlier version? Is the RC0 version still marked with all the Preview warnings?

You can see this from the package.json of the outcome projects after the template is executed, but unless mistaken, in this case, you can't even execute the flow for some reason. This is a tough one since we can't reproduce it on a clean computer with matching version numbers.

Hi, I uninstalled everything including npm and re-installed everything from scratch and it seems to have resolved the issue. Thanks for your attention in this regard.


Allow later versions of google-cloud-storage

What this PR does / why we need it:
Currently, the google-cloud-storage dependency is fixed to version 1.41.1. This is restrictive, and can constrict usage of this library in other projects. There appears to be no good reason not to allow a range of versions, such as >=1.41.1 as proposed in this PR.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #1977
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:
NONE

@aodahl Can you help sign off the commit with following instruction ?

@yuzisun - I have followed the instruction to sign off on the commit, thanks!

/ok-to-test

Thanks @aodahl !
/lgtm
/approve


[NO-MERGE] New prover architecture updates

To be pulled into update-deps branch

Incorporated: https://github.com/runtimeverification/evm-semantics/pull/1728


Wish to add a gift card redemption interface

https://www.binance.com/zh-CN/gift-card

Hello @lovezm,
Are you referring to this API? https://developers.binance.com/docs/gift_card/market-data/Redeem-a-Binance-Gift-Card


Slow Down Sparky

Why are we getting multiple updates per day for this addon, that require a restart.  I appreciate the attention the author puts into the project, but maybe only 1-2 updates per week???

It's in full development. Then it's logical it gets more than the regular updates. You don't have to install every update. Just skip a few if you've got no issues.
I'm for one am happy about this development after being a bit irritated about the lack of development of the Circiadian Lighting addon.
So full steam ahead sparky!

If you are going to release 3-4 updates a day, then why not start a beta version and then lab rats like Jeltel can spend their day giving feedback.  Then make a public release when necessary.
I also used and still have installed the Circadian Lighting addon and it worked great without being updated multiple times per day.
I appreciate the authors enthusiasm for this project, but if you are going to make 3-4 changes per day then perhaps releasing them via a beta channel is the way to go.  I see a lot of other HA addon authors follow this route.

Or how about stick with circadian lighting until this is released if you can’t handle the updates. Consider this a beta channel since the full release will be part of core. This is the silliest issue, “you’re doing too much work on this”

You are right, I deleted this train wreck and went back to Circadian Lighting

Sorry, I didn't get notified of these issues, I am only seeing it now.
@WeaselBreath, no one is forcing you to click the update button...


Updated dependency.

Snyk reported a vulnerability in a request dep :
<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>Upgrade direct dependency<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(triggers upgrades to<EMAIL_ADDRESS>
A simple version bump takes care of it.

Thanks @PierreLvx!


Scanner FW Update doesn't work via Solum - Play Store Beta is not newer then the default build

Hello,
I want to update the firmware of my Scnner to 11.3. After my initial question I subscribed to the Beta version of the Clarius App, as I hoped this might be the easiest way. However. Even I am in the Android Beta Repository for the Clarius App, I do not get any Update for the App (I am in the Beta program for a few days now).
So I tried to implement the software Update function in solum. Following the Guide in the Readme I got the .zip file with the firmware. I am not sure which file I should use. I tried to push the .zip to my Scanner, but that didn't work.
I receive the Error: undetermined hardware version
When I do specify the Hardware Version (hwVer=2 for the L15HD Scanner) I do receive the Error: undetermined hardware version, falling back to user provided version. After a few seconds the software then crashes.
I do use a custom Python Wrapper with ctypes for solum 11.3.0.
After initialising I do wait until the probe is connected and the certificate is validated. I then convert my path to a ctypes c_char_p (which should be compatible with const char*. If not the error message should indicate an issue with the filepath(?)).
For the CusSWUpdateFn and CusProgressFn I wrote a simple print function to show the progress and the status of the Update.
For hwVer I tried 0 and 2 as an int (I tried c_int, which should not be necessary in that case. But that didn't help either).
The function solumSoftwareUpdate returns -1, which indicates that the update failed. Do you have any suggestions to solve this issue?

Beta Program is not needed anymore


[1.18.2] Rendering overlay error since 5.3.6 and newer versions

The game crashed since I installed Apotheosis 5.3.6 (and newer versions) with a Rendering overlay error. This problem never happens in 5.3.5 and older versions with 1.18.2.
Forge version: 40.1.52 or 40.1.73 (with JDK 17.0.0)
crash-2022-08-23_17.35.02-client.txt

This crash report states sound control is the offending mod, apoth is not even in the stacktrace.


Collected data record: General UI refinements

Starting a UI refinements checklist for this page. Some other open tickets involving this page are #294  #295 and #264.

[x] 1. Page title should be H2.
[x] 2. Change the page title from "Collected Data" to "Results".
[x] 3. For helpful context, let's include "(Level) indicator: Indicator name" underneath the page title, just like we do in the Indicator setup form, like so:

[x] 4. Move the "Project" dropdown menu out of the Evidence section, to the section above. (No idea why it's in the Evidence section, but it doesn't belong there.)

5. "Standard Disaggregations" updates

[x] 5.1. Change to sentence case -- Standard disaggregations.

[x] 5.2. Turn "Standard disaggregatoins" into an expandable/collapsable interaction similar to what we use to open and close program indicator rows, like so:

[x] 6. Action bar at the bottom should be consistent in styling with Indicator setup form:

For helpful context, let's include "(Level) indicator: Indicator name" underneath the page title, just like we do in the Indicator setup form, like so:

@axoplasm Please add the word indicator between the level and the colon. For example:
Activity indicator: Blah
Output indicator: Blah
Intermediate outcome indicator: Blah
etc.

Can you align the check box with its corresponding label, and move both under the form field immediately above it? (It is a secondary option related to the TolaTable menu.)
Here's how it looks to me now:

Versus in production -- in that example there's too big of a vertical gap between the drop down menu and the check box, but the basic alignment of the check box with the menu above is what we're going for.

Wondering why the Measure against target label is a different size. Is there a hot fix to make it match?

As discussed in Slack, the correct spelling for this field label is TolaTable.
If it's a quick fix, can we also align the label with the drop down menu?

haha there are no easy fixes in this markup!
Re: Measure against target label… this looks the same size to me. Can you send a screenshot?

here's where I'm at with the Evidence form elements but what is supposed to happen when I click "Import evidence from TolaTables?" It looks like it might be trying to open a modal behind this modal.

here's where I'm at with the Evidence form elements but what is supposed to happen when I click "Import evidence from TolaTables?" It looks like it might be trying to open a modal behind this modal.

Good question! Maybe you can knock off #239 while you're at it. If you try clicking that link on production, right now it launches a modal that looks like this:

Here's what that looks like in the code:

I split the modal z-index issue into #396

Oops, I included the wrong link... I had captured it in #249 not 239. I'll close one of them as duplicate.

@axoplasm Ah, found an example -- I wonder if the smaller text happens when there is a message under the dropdown?

This was the clue I needed! The has-error class has font-sizing in it & there are a few other problems there. Hot fixed with #5bdcda8

Bam! Validated.


Create new date-time package with DatePicker

Story: https://deploy-preview-574--comet-admin.netlify.app/?path=/story/comet-admin-date-time--date-picker

Created a new date-time package to contain all date and time related components, for use in forms, such as DatePicker, DateRangePicker, TimePicker, DateTimePicker.
Implemented the DatePicker and FinalFormDatePicker, for now, using the default styling, provided by 'react-date-range' and without allowing text-input by the user.
Created the InputWithPopper component in the admin package to use as a base for the DatePicker and other future pickers.
It renders the input and handles the opening and closing logic of the popper, preventing inconsistencies in the behaviour of the different picker components.

This picker is currently not usable with a keyboard (= setting 01.01.1950 using the keyboard). Is this something we need / want?

This picker is currently not usable with a keyboard (= setting 01.01.1950 using the keyboard). Is this something we need / want?

As we discussed in our meeting, the initial implementation will be without text-input, to allow for a fast replacement of the old package.
Parsing, validating with the correct locale and rendering errors without direct access to the Field's error-prop is a bit difficult and time intensive.
https://vivid-planet.atlassian.net/wiki/spaces/COM/pages/91586569/2022-02-23+comet-admin+JFX+Sprint+8

Initialer Ersatz: Wir machen jeweils einen Date-Picker und Date-Range-Picker, ohne Text-Input.
Wäre relativ einfach/schnell umgesetzt.

Alright 👍

The style of the calendar doesn't seem to be in line with our Comet theme. Do you plan to change that in a future PR?

The style of the calendar doesn't seem to be in line with our Comet theme. Do you plan to change that in a future PR?

Yes, that's a future PR 🙂


SQL Server 2000?

We reference "SQL Server 2000" on this page, surely that cannot be intentional?
That SQL version has been out of support for a LONG time.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: e7b382ac-a815-8623-3d48-f1a67a16eada
Version Independent ID: f1edfa59-688e-344b-7f84-033405028c9f
Content: Network Policy Server Best Practices
Content Source: WindowsServerDocs/networking/technologies/nps/nps-best-practices.md
Product: windows-server
Technology: networking
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

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


BoringSSL integration

This is an initial cut.
We currently ignore asm files, and the C code doesn't yet build.
I expect we should also import boringssl tests into our suites.
Our build files are generated using code existing in the boringssl repo. The integration could be cleaner with a change to boringssl, but for prototyping this works.
This is a start.

This LGTM... likely we'll tweak as we go, but merge at will.

The buildgen step fails if "go" is not a command in the host system (see third_party/boringssl/util/generate_build_files.py):
  with open('err_data.c', 'w+') as err_data:
    subprocess.check_call(['go', 'run', 'err_data_generate.go'],
                          cwd=os.path.join('src', 'crypto', 'err'),
                          stdout=err_data)

Full error from running tools/buildgen/generate_projects.sh
Traceback (most recent call last):
  File "src/boringssl/gen_build_yaml.py", line 151, in <module>
    generate_build_files.main([g])
  File "/home/dgq/grpc/forks/tmp/third_party/boringssl/util/generate_build_files.py", line 465, in main
    stdout=err_data)
  File "/usr/lib/python2.7/subprocess.py", line 535, in check_call
    retcode = call(*popenargs, **kwargs)
  File "/usr/lib/python2.7/subprocess.py", line 522, in call
    return Popen(*popenargs, **kwargs).wait()
  File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1327, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory

Yeah... that's going to be a thing unfortunately.
We might want to add better detection.
On Mon, Dec 21, 2015 at 12:40 PM David G. Quintas<EMAIL_ADDRESS>wrote:

The buildgen step fails if "go" is not a command in the host system (see
third_party/boringssl/util/generate_build_files.py):
with open('err_data.c', 'w+') as err_data:
subprocess.check_call(['go', 'run', 'err_data_generate.go'],
cwd=os.path.join('src', 'crypto', 'err'),
stdout=err_data)
Full error from running tools/buildgen/generate_projects.sh
Traceback (most recent call last):
File "src/boringssl/gen_build_yaml.py", line 151, in
generate_build_files.main([g])
File "/home/dgq/grpc/forks/tmp/third_party/boringssl/util/generate_build_files.py", line 465, in main
stdout=err_data)
File "/usr/lib/python2.7/subprocess.py", line 535, in check_call
retcode = call(*popenargs, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 522, in call
return Popen(*popenargs, **kwargs).wait()
File "/usr/lib/python2.7/subprocess.py", line 710, in init
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1327, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/4502#issuecomment-166411356.

@jboeuf - PTAL
@nicolasnoble - if you get a chance

It looks like every C# interop test is failing.

Yeah. Will take a peek. Surely a build problem.
On Tue, Dec 22, 2015, 9:29 AM Michael Lumish<EMAIL_ADDRESS>wrote:

It looks like every C# interop test is failing.
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/4502#issuecomment-166680569.

LGTM for TSI.

Please also change tools/jenkins/grpc_jenkins_slave_32bits

Done

OK, everything was fine before that last commit, which didn't change anything significant for the tests.


Charts[Network Node]: Add support for targeting node labels, taints, and affinity/anti-affinity

Description
Add support to our Helm chart for node labels, taints, affinity, and annotations along the lines of the following:
podAnnotations: {}

podLabels: {}

nodeSelector: {}

tolerations: []

affinity: {}

# Only one of minAvailable or maxUnavailable can be set
podDisruptionBudget:
  enabled: false
  # minAvailable: 1
  # maxUnavailable: 3

# Leverage a PriorityClass to ensure your pods survive resource shortages
# ref: https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/
# PriorityClass: system-cluster-critical
priorityClassName: ""

Need a bit more clarity on the requirements of the following before I update the charts:

podDisruptionBudget
priorityClassName

:tada: This issue has been resolved in version 0.12.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Update expressroute-nat.md

updated incorrect Public peering reference under Microsoft Peering section.

@duongau
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Add NousResearch/Nous-Hermes-2-Mixtral-8x7B-DPO

Thank you for the PR! Would you please help confirm if the conversation template mapping would work for the model?
Link: https://github.com/allenai/WildBench/blob/main/src/fastchat_conversation.py#L11
Please add the changes here if needed. Thanks again!


operations are not being processed after updating thin-edge.io

Describe the bug

Due to an unfortunately combination of the following two ticket, the existing c8y-bridge mosquitto file will lack the devicecontrol topic subscription, however the tedge-mapper only listens to this devicecontrol topic thus resulting in the mapper not reacting to any of the operations.

https://github.com/thin-edge/thin-edge.io/issues/2192
https://github.com/thin-edge/thin-edge.io/pull/2482

Only the unofficial releases since >= 0.13.2~223+g9e20481 are affected.
To Reproduce

Install any thin-edge.io version older than 0.13.2~223+g9e20481
Upgrade thin-edge.io to version 0.13.2~223+g9e20481
Try to send any operation to thin-edge.io via the Cumulocity IoT UI

The bug is present if the operation remains in PENDING state despite the thin-edge.io having a healthy bridge connection to Cumulocity IoT.
Expected behavior

Operations should be processed by thin-edge.io
Screenshots

Environment (please complete the following information):

OS [incl. version]: Any
Hardware [incl. revision]: Any
System-Architecture [e.g. result of "uname -a"]: Any
thin-edge.io version [e.g. 0.1.0]: >= 0.13.2~223+g9e20481

Additional context

Fixed in >= 0.13.2~241+g9ff6d57

QA has thoroughly checked the feature and here are the results:

[ ] Test for ticket exists in the test suite.
[x] QA has tested the function and it's functioning according description.


Making existing tests location-agnostic; add conditional check for server static path before mounting

Updated tests in test_core.py, test_app_runner.py, and test_serve.py to use dynamic paths derived from test_app_dir in __init__.py of the tests directory. This ensures consistent path resolution across different environments.

Implemented a check to verify the existence of the server static path before mounting it in the ASGI app. Added an error message guiding users on how to resolve the issue if the path is not found.


net/http: TestClientCallsCloseOnlyOnce failures with "host has failed to respond" on Windows

--- FAIL: TestClientCallsCloseOnlyOnce (21.04s)
    client_test.go:2063: dial tcp <IP_ADDRESS>:51357: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
FAIL
FAIL	net/http	25.262s

greplogs --dashboard -md -l -e '(?m)FAIL: TestClientCallsCloseOnlyOnce.*\n.*host has failed to respond'
2021-11-05T22:03:24-035963c/windows-arm64-10
2020-12-23T02:10:51-b0b0d98/windows-arm-zx2c4
CC @neild

cc @bufflig
This test creates 50 HTTP client connections, in sequence, to the same server. The error seems to indicate that one of them failed. I don't know what might cause this, but the fact that the failure has happened once in a year and only on Windows makes this hard to diagnose; I suspect it's an issue on the builder, but I don't know what. Something applying a rate limit to connection attempts?
Given the rarity of the failure, this is probably not a priority.

I wonder if the fact that it happens on both arm 32 and 64 bit is significant? I agree that it seems really hard to diagnose when it happens this rarely. I can attempt to get it to happen with brute force running on my parallels VM, but I can not leave any guarantees of success.

If the cause isn't easy to spot, I suggest that we give it a while to look for more occurrences. (I agree with Damien that this doesn't seem worth prioritizing at the moment.)

There have been a lot of net/http fixes since this issue was filed, and watchflakes will file a new issue should it recur. Closing as obsolete.


Fix integrations tests to work with prompt_toolkit 1.0.4

prompt_toolkit updated to version 1.0.4 which adds an assertion that the input/output given to a CommandLineInterface be a TTY. This assertion happens at object instantiation which affects the way we do some of our integration tests.
We currently have some tests in integration\test_keys.py and integration\test_selectmenu.py that instantiate CLIs and simulate key presses to them by calling feed and process_keys. This is used to test that key bindings are properly registered and have the correct results on the state of the CLI. However, the CLI's run method is not called, meaning that the actual input and output streams seem to not be used. This is what allowed the tests to function previously. Now that there are assertions to verify that the input and output are TTYs at instantiation the tests fail immediately. This can be fixed by passing Input and Output objects that don't rely on stdin and stdout.
This is what the fix would like. For test_keys.py we would next to change the AWSShell to pass a pluggable input and output when it creates it's CLI.
@JordonPhillips @jamesls

--    .-""-.
   ) (     )
  (   )   (
     /     )
    (_    _)                     0_,-.__
      (_  )_                     |_.-._/
       (    )                    |_--..\
        (__)                     |__--_/
     |''   ``\                   |
     |        \                  |      /b.
     |         \  ,,,---===?A`\  |  ,==y'
   ___,,,,,---==""\        |M] \ | ;|\ |>
           _   _   \   ___,|H,,---==""""bno,
    o  O  (_) (_)   \ /          _     AWAW/
                     /         _(+)_  dMM/
      \@_,,,,,,---=="   \      \\|//  MW/
--''''"                         ===  d/
                                    //
                                    ,'__________________________
   \    \    \     \               ,/~~~~~~~~~~~~~~~~~~~~~~~~~~~
                         _____    ,'  ~~~   .-""-.~~~~~~  .-""-.
      .-""-.           ///==---   /`-._ ..-'      -.__..-'
            `-.__..-' =====\\\\\\ V/  .---\.
                      ~~~~~~~~~~~~, _',--/_.\  .-""-.
                            .-""-.___` --  \|         -.__..-


Move from setup.cfg to pyproject.toml

Apparently this is the new way to do things, and will help when setting up CI. I'll fix this now.

Worth reading what @lentinj wrote about this a while back, as he led me more toward setup.cfg: https://github.com/OneZoom/tree-build/issues/3#issuecomment-1473509727

I presume the latest debian now support this. It's what we are using for testing, I think.


Add zsh completion for new 'docker daemon --log-opt syslog-tls-ca-cer…

…t syslog-tls-cert syslog-tls-key syslog-tls-skip-verify' options
Ref #18998
Feature present in the 1.10 release.
@albers Thanks for the ping
Signed-off-by: Steve Durrheimer<EMAIL_ADDRESS>

LGTM 🐯

LGTM


Fix ETIMEDOUT error in IE11

added new configuration option - sessionQuitTimeout which is responsible for closing browsers sessions

/cc @j0tunn @eGavr @sipayRT @tormozz48 @rostik404

Coverage increased (+0.2%) to 81.588% when pulling ca918db71edf80c70bbf7cead57e764b0ff609c1 on fix/etimedout.error into 7f4de57257bcb92e09a4464c493c7979fb5bbfff on master.

Coverage increased (+0.2%) to 81.588% when pulling 1d51f27298da94b44e3538c99137e65b6141301a on fix/etimedout.error into 7f4de57257bcb92e09a4464c493c7979fb5bbfff on master.

В остальном :ok:

Coverage increased (+0.2%) to 81.607% when pulling 84593b1ba401012ca80ce8fa018c72730b27639d on fix/etimedout.error into 7f4de57257bcb92e09a4464c493c7979fb5bbfff on master.

Coverage increased (+0.2%) to 81.607% when pulling 84593b1ba401012ca80ce8fa018c72730b27639d on fix/etimedout.error into 7f4de57257bcb92e09a4464c493c7979fb5bbfff on master.

Coverage increased (+0.2%) to 81.607% when pulling 84593b1ba401012ca80ce8fa018c72730b27639d on fix/etimedout.error into 7f4de57257bcb92e09a4464c493c7979fb5bbfff on master.

Coverage increased (+0.2%) to 81.607% when pulling 84593b1ba401012ca80ce8fa018c72730b27639d on fix/etimedout.error into 7f4de57257bcb92e09a4464c493c7979fb5bbfff on master.

Coverage increased (+0.2%) to 81.607% when pulling 84593b1ba401012ca80ce8fa018c72730b27639d on fix/etimedout.error into 7f4de57257bcb92e09a4464c493c7979fb5bbfff on master.

Coverage increased (+0.2%) to 81.607% when pulling 84593b1ba401012ca80ce8fa018c72730b27639d on fix/etimedout.error into 7f4de57257bcb92e09a4464c493c7979fb5bbfff on master.

Coverage increased (+0.2%) to 81.615% when pulling 998276cdea6d4556952a0f4d37ec893dfe67b3d2 on fix/etimedout.error into 7f4de57257bcb92e09a4464c493c7979fb5bbfff on master.

Coverage increased (+0.2%) to 81.615% when pulling 998276cdea6d4556952a0f4d37ec893dfe67b3d2 on fix/etimedout.error into 7f4de57257bcb92e09a4464c493c7979fb5bbfff on master.

Coverage increased (+0.2%) to 81.615% when pulling 998276cdea6d4556952a0f4d37ec893dfe67b3d2 on fix/etimedout.error into 7f4de57257bcb92e09a4464c493c7979fb5bbfff on master.

Coverage increased (+0.2%) to 81.615% when pulling 998276cdea6d4556952a0f4d37ec893dfe67b3d2 on fix/etimedout.error into 7f4de57257bcb92e09a4464c493c7979fb5bbfff on master.

/ok

Coverage increased (+0.2%) to 81.624% when pulling d1cd7195e320a78b2832b7772e478473eebc00e9 on fix/etimedout.error into b4a4032c73bc1a2b565a45067557cea975f8fffa on master.


Implement owner and status fields

Components

Added a read-only display label

Housekeeping

Dead code removal
Some typescript errors in Zod Flaw Schema (types used as values)

Reacting to changes in API

Re-generated client open api
Updated type definitions for Flaws

https://github.com/RedHatProductSecurity/osim/pull/44 seems like it would resolve the failing check issue


Upgraded Jackson/Joda causes breaking change on DataTime

I see RC4-SNAPSHOT has upgraded jackson library to the latest 2.6.0 and withit comes a breaking change where previously 2015-07-28 would be perfectly serialized into a joda DataTime object, now any request containing Resource in this format is denied by dropwizard as 400: Bad Request. It requires a full ISO format string like 2015-07-28T22:30:35Z.
Was this discussed previous? Personally I can't think of any reason why this change is required and especially since RC3 works just fine.
/cc @cowtowncoder

Quick comment: is this:
https://github.com/FasterXML/jackson-datatype-joda/issues/70
the root cause?
Breakage is unintentional and surprising; I assume the joda issue is the root cause and will add more information there. We should be able to fix this for 2.6.1.

Yikes. Thanks, @kilemensi, for testing release candidates and reporting this.
@cowtowncoder, do you plan to release jackson-datatype-joda 2.6.1 soon? If not, we will probably rollback to 2.5.* stream and move 2.6.* update to Dropwizard 1.0.

@arteam What I can do very quickly is to release a micro-patch of <IP_ADDRESS>, both for Joda and jsr-310 (java 8 time). I don't know when full 2.6.1 will be released, but I usually will try to pack in a few more fixes.
Micro-patch just means that it is not part of full patch release, and is done for critical breakages. This one would qualify.
I will actually go ahead and cut the micro-release, just in case.

With that, there's now 2.6.0-1:
http://repo1.maven.org/maven2/com/fasterxml/jackson/datatype/jackson-datatype-joda/2.6.0-1/
of Joda module. I will release 2.6.0-1 of jsr-310 module later tonight as well.
I understand if decision is made to stay with 2.5(.4), for DropWizard 0.9, but wanted to make sure there is an alternative.

Okay, thanks. I've updated jackson-datatype-joda to 2.6.0-1 in master.
@kilemensi, could you test the latest RC4 snapshot?

@arteam Tested and works as expected. Thanks @cowtowncoder

Thank you for reporting the problem, apologies for causing it.


About the "shift_tokens"

Thank you for your amazing code.
In the class of FLASH, I find a flag: shift_tokens, and the corresponding code is as following:
if self.shift_tokens:
x_shift, x_pass = normed_x.chunk(2, dim = -1)
x_shift = F.pad(x_shift, (0, 0, 1, -1), value = 0.)
normed_x = torch.cat((x_shift, x_pass), dim = -1)
Assume we have normed_x in the shape [1024, 512], the x_shift/x_pass is the shape of [1024, 256]. Then it adds a row (with all 0 value) and remove the last row in the x_shift, and concat x_shift and x_pass to get the normed_x.
In my opinion, the F.pad operation will make the row in x_shift and x_pass do not match again.
May I know why it works?
Kang

@kangzhao2 so there's actually a -1 in the padding, which removes one from the sequence dimension

It's “smeared key" architecture mentioned in https://transformer-circuits.pub/2022/in-context-learning-and-induction-heads/index.html


Bug:keyd bind reset throws error

The command keyd bind reset emits bind is not a valid key or alias.

oops. Looks like I forgot to update the arg handling. Should be fixed in the latest commit.


Can't start scheduleR [Mac OSX]

Great tool and idea. Sadly, scheduleR won't start on my Mac.
Imho all components have been correctly installed.
Error logs are attached.
npm-debug.log:
0 info it worked if it ends with ok
1 verbose cli [ 'node', '/usr/local/bin/npm', 'start' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info prestart<EMAIL_ADDRESS>6 info start<EMAIL_ADDRESS>7 verbose unsafe-perm in lifecycle true
8 info<EMAIL_ADDRESS>Failed to exec start script
9 verbose stack Error<EMAIL_ADDRESS>start: `node bin/scheduler.bin.js`
9 verbose stack Exit status 8
9 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:213:16)
9 verbose stack     at EventEmitter.emit (events.js:98:17)
9 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:14:12)
9 verbose stack     at ChildProcess.emit (events.js:98:17)
9 verbose stack     at maybeClose (child_process.js:766:16)
9 verbose stack     at Process.ChildProcess._handle.onexit (child_process.js:833:5)
10 verbose pkgid<EMAIL_ADDRESS>11 verbose cwd /Users/mhn/scheduleR
12 error Darwin 14.1.0
13 error argv "node" "/usr/local/bin/npm" "start"
14 error node v0.10.35
15 error npm  v2.6.1
16 error code ELIFECYCLE
17 error<EMAIL_ADDRESS>start: `node bin/scheduler.bin.js`
17 error Exit status 8
18 error Failed at the<EMAIL_ADDRESS>start script 'node bin/scheduler.bin.js'.
18 error This is most likely a problem with the scheduler-for-r package,
18 error not with npm itself.
18 error Tell the author that this fails on your system:
18 error     node bin/scheduler.bin.js
18 error You can get their info via:
18 error     npm owner ls scheduler-for-r
18 error There is likely additional logging output above.
19 verbose exit [ 1, true ]

Hardware:

    Hardware Overview:

      Model Name: MacBook Air
      Model Identifier: MacBookAir4,2
      Processor Name: Intel Core i5
      Processor Speed: 1,7 GHz
      Number of Processors: 1
      Total Number of Cores: 2
      L2 Cache (per Core): 256 KB
      L3 Cache: 3 MB
      Memory: 4 GB

Software:

    System Software Overview:

      System Version: OS X 10.10.2 (14C109)
      Kernel Version: Darwin 14.1.0
      Boot Volume: Macintosh HD
(...)

Thanks for testing @mhnierhoff.
Could you also post the output printed in the console when starting scheduleR? You're sure you have a running mongodb instance and the url specification for it in user.config.json is correct?

Mongodb is up and running, user.config.json is correctly specified, attached you'll find the console output.
Maximilians-MacBook-Air:scheduleR mhn$ npm start

><EMAIL_ADDRESS>start /Users/mhn/scheduleR
> node bin/scheduler.bin.js

module.js:340
    throw err;
          ^
Error: Cannot find module 'glob'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/Users/mhn/scheduleR/config/init.js:6:12)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)

npm ERR! Darwin 14.1.0
npm ERR! argv "node" "/usr/local/bin/npm" "start"
npm ERR! node v0.10.35
npm ERR! npm  v2.6.1
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `node bin/scheduler.bin.js`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'node bin/scheduler.bin.js'.
npm ERR! This is most likely a problem with the scheduler-for-r package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node bin/scheduler.bin.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls scheduler-for-r
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/mhn/scheduleR/npm-debug.log
Maximilians-MacBook-Air:scheduleR mhn$ open npm-debug.log

this seems like the glob module hasn't been installed.
Did you run npm install while in the scheduleR directory (could require admin rights)? What was the output?

Okay I installed glob, then I got the error message for the following packages and installed them all: lodash, mongoose, express, morgan, body-parser, express-session, compression, method-override, cookie-parser, helmet, passport, connect-mongo, connect-flash, consolidate, connect-multiparty, cron, temp, async, node mailer, swig, marked, request and finally passport-local.
Now I get this error message:
undefined:25
    "url": "mongodb://abcd:abcd@ds039351.mongolab.com:39351/scheduler“
                                                                      ^
SyntaxError: Unexpected token

Connecting to this mongodb via shell works fine. (abcd is not the real dbuser and password) ;)

The last error (Error: listen EADDRINUSE) is thrown because the address scheduleR uses is already in use. Please check if the node is running (ps aux | grep node) and kill it (kill -9 [pid-of-node-process], then try npm start again. I got this same error after upgrading scheduleR because I forgot to stop the running node process beforehand.

Agreed @mjlassila, this seems like some other process in running on the specified port. I'll add error handling for these situations (so that a clear output is given on what is going on) to my TODOs.
@mhnierhoff, can you verify that this is indeed the problem?

@mjlassila You were right. After killing the node process and restarting it finally works. Thanks a lot for the great help - @Bart6114 & @mjlassila

Thanks for verifying


Creation of the betterdoors folder

Could I recommend you create the data/betterdoors folder when the addon starts up or define in the readme that it needs to be created before group data can be saved?
I had a hell of time-saving group data until I created the betterdoors folder. I had no idea it doesn't do it automatically and I didn't see any mention that It needs to be manually created.

Just tested it. You're right, the directory won't get created automatically, only files within such and as better doors never checks if writing is successful and keeps an in-memory copy, it all seems fine until you restart the server.
Thanks for finding this (and actually using GitHub to save my sanity)! I'll fix this very soon and add a minor convenience server concmd on top.

No worries mate, awesome addon.


WIN 11可以帮做一个rdpwrwp.ini吗

WIN 11可以帮做一个rdpwrwp.ini吗

WIN 11可以帮做一个rdpwrap.ini吗

Wrong language in title and first message
What is your termsrv.dll version (Where RDPConf screenshot?)


Doesn't seem to work

Doesn't work on any website, even the test website provided in the Firefox addon description.
Extension doesn't seem to activate, even if there's a rule for * or the website name itself. The icon always remains grey.
On Firefox 74.0

The interface is a bit confusing. Make sure you click the Save button to activate it.


Can we use Mongo-connector to index MongoDB Atlas document into Amazon Elasticsearch Service

We have a requirement to connect and index AWS MongoDB Atlas document into Amazon Elasticsearch Service.
@llovett
is it possible using Mongo-connector ?
Thanks

Its working fine.

Hi @GirdhariAtGit
Can you please help me with steps or any info which can help me?
I'm trying to use Mongo-connector to index MongoDB Atlas document into Elasticsearch cloud stack.
However getting below error.
Logging to /root/mongo-connector.log.
Exception in thread Thread-2:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/threading.py", line 812, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/site-packages/mongo_connector/util.py", line 107, in wrapped
    func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/mongo_connector/connector.py", line 353, in run
    self.main_conn = self.create_authed_client()
  File "/usr/lib/python2.7/site-packages/mongo_connector/connector.py", line 337, in create_authed_client
    client["admin"].authenticate(self.auth_username, self.auth_key)
  File "/usr/lib64/python2.7/site-packages/pymongo/database.py", line 1274, in authenticate
    connect=True)
  File "/usr/lib64/python2.7/site-packages/pymongo/mongo_client.py", line 604, in _cache_credentials
    raise OperationFailure('Another user is already authenticated '
OperationFailure: Another user is already authenticated to this database. You must logout first.


add Yandex Search Api Wrapper Integration

PR Title: "community: add Yandex Search API integration"
PR Message:
Description: This PR introduces a new integration with the Yandex Search API, allowing users to perform web searches directly through LangChain. The integration includes a new YandexSearchAPIWrapper class, which handles queries to the Yandex Search API and processes the responses.
Issue: N/A
Dependencies: Requires requests for sending HTTP requests to the Yandex API.

there are a lot of lint issues. going to close this until they more throroughly resolved. feel free to reopen once fixed!


Make changes required for patreon currency API changes

https://support.patreon.com/hc/en-us/articles/360047287991
deadline is 31.9.2020

I think I got all of the required changes done, I guess we'll see if things works when new patrons join.


[2.0] Implements Vector3FlowItem and Trait

Fixed CALCULATE2_ROUND
BCBreak: "level" to "world"
Organize actions into subdirectories by category

Thank you!


FINAL SPRINT: CREATE USER -> BIRTHDAY BELOW 18 ERROR

BIRTHDAY IS 3/14/2000
DATE TODAY IS 3/15/2018
PROMPTS THIS ERROR

https://github.com/ploidddddd/purplekeep/pull/282

45b67c4


add height:100% on swipe

Please makes sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow the contributing guide.
[ ] Rebase before creating a PR to keep commit history clear.
[ ] Add some descriptions and refer relative issues for you PR.

#283


Allow wifi interfaces configuration without requiring a network_key,

i.e. allow unencrypted wifi network configuration.
Update specs to reflect that change, add a few more wifi interfaces
I own and reorder them alphabetically. Add a little test.
Travis fails, due to :lint test in Rakefile,
removing that :lint test, tests are passing.
Don't know why it is failing, but puppet-lint also fails for me on
my local box with the same error on your master branch, without
me doing any changes :(

I'm sorry I missed this.  Reviewing the travis failure now.

I've no real idea about those failures.  Do the tests run locally with a bundle install && bundle exec rake test ?  Maybe a rebase is in order.

Tests have been a bit improved in https://github.com/xaque208/puppet-bsd/pull/37

btw, tested running the tests locally with bundle exec rake test, and figured, that the syntax check test was/is fine, same as the specs test, however, the second test, the lint is where it bails out.

Once the issue above is fixed and the test passes, I'll merge.

with the test indentet, the linter doesn't seem to fail anymore, and tests managed to be greeen again., or one of your other changes did that.

Excellent, thanks for the PR.


Complete the implementation of the LoadImage function

Change the load_image to be a full implementation of the respective UEFI call.
My usecase is launching the linux efistub - without the device_path argument,
which is not implemented in the load_image_from_buffer it does not work. My
best guess is that it need to know the device the buffer was loaded from to load
the initrd.
I've removed the existing load_image_from_buffer function as it's current
behavior can be fully replicated with the full one - although probably can bring it back as a shortcut and for backwards compatibility.

Thanks for the patch! What do you think about keeping load_image_from_buffer, and adding a separate load_image_from_device_path? If I understand correctly that covers the actual two uses of load_image, and should make the call sites clearer.

the actual two uses

The thing is that my use is not the 'second use' - I do load the image from a buffer, it's just that I also have to give it a device path for it to work - see my guess about why it needs that;
So there are no two distinct 'give it a buffer pointer and null device path' vs 'give it null buffer and a device path' uses, in my case I give it both things - so load_image_from_device_path which I assume would not take a buffer argument is not enough.
I am up to leaving the old function in place as a shortcut and adding a full version as I've said, although technically it would be cleanest to just have the full version (as I've pushed it initially).

Gotcha, I misunderstood the initial description. I think you are probably right then that a single function is the way to go, I will take another look at it.

Followed up on this in https://github.com/rust-osdev/uefi-rs/pull/383.


Terminal tab background is broken since the latest VSC update (1.82.0)

Describe the bug
After updating to the latest Visual Studio Code update (1.82.0), when you reapply the background, the terminal tab doesn't have the background set, however the rest of the tabs have the background. This issue still appears even when I unset my custom background.
To Reproduce

Ensure you are on the latest version (atleast 1.82.0)
Set the background for your Visual Studio Code

Expected Behavior
All views should have the background set correctly, like before the update
Environment
Version: 1.82.0 (user setup)
Commit: 8b617bd08fd9e3fc94d14adb8d358b56e3f72314
Date: 2023-09-06T22:07:07.438Z
Electron: 25.8.0
ElectronBuildId: 23503258
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.23536
Doki theme version: v88.1.15
Screenshots

Same issue here for a while now. I'm considering downgrading my VSCode just for it.
Enviornment:
Version: 1.82.2
Commit: abd2f3db4bdb28f9e95536dfa84d8479fleb312d
Date: 2023-09-14T05:51:20.9812 (3 wks ago)
Electron: 25.8.1
ElectronBuildid: 23779380
Chromium: 114.0.5735.289
Node.js: 18.15.0
ve: <IP_ADDRESS>-electron.0
OS: Linux x64 5.15.0-84-generic

Same problem here, but in 1.18.0 instead.
Version: 1.84.0-insider (user setup)
Commit: 4678919d52909efc7c4ab958a2e5c8f45d50ffc3
Date: 2023-10-13T05:34:13.175Z
Electron: 25.8.4
ElectronBuildId: 24154031
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621


docs(clone): add promise example

It took me some time to figure out how to properly create a pipeline and know
when it's done, while https://github.com/lovell/sharp/issues/524 provides an
example about listening to the finish event, I needed one for toFile.
Now I think we should also document the example from
https://github.com/lovell/sharp/issues/524 but I'd like you the maintainer to
create it because I am not 100% sure this is the most elegant way.
Thanks for the awesome library! It helped me build this: https://coronamaison.net/ (https://github.com/vvo/coronamaison/blob/549a807aea1e2034a0a5821dff6ea89488be46a3/prepareData.js#L153)

Coverage remained the same at 100.0% when pulling df97a9cb7e5df61213a3d2953d3e79611fcbe8bb on vvo:docs/add-clone-promise-example into 6ed1f49ad37105b728aab3256328e949b04bd76e on lovell:master.

Landed in commit 1eedb22 - merci beaucoup!


Unify Model $dates property with $casts

This removes the Model $dates property as it has become antiquated by the $casts property.
Laravel as well as other community packages have adopted using casts directly for dates. Unifying these properties will remove ambiguity and give developers a single place for casting their date attributes, as well as other attributes.
Before
class Person extends Model
{
    protected $casts = [
        'age' => 'integer',
    ];

    protected $dates = ['birthday'];

After
class Person extends Model
{
    protected $casts = [
        'age' => 'integer',
        'birthday' => 'datetime',
    ];

This refactor is a bit shallow - simply removing references to $dates and, where necessary, adding columns to $casts instead (i.e. SoftDeletes).
This refactor could go deeper by removing methods like HasAttributes::getDates and others to add these default columns to $casts.
However, felt this would get the :fire: started.

Can we deprecate this first before directly removing it?

Deprecation feels unnecessary to me as all these properties and methods are
protected. Which should limit the impact.
But I’m open and glad to adjust the PR to honor an existing property for L8
with eventual removal in L9.
Either way, I’d build a community Shift which would sniff and convert
dates to casts.

We probably need to sniff out if the dates property and cast = datetime is the exact same behavior.

I did some initial investigating and to me it looks like their behavior is currently totally unified. The only difference between them being that the datetime cast allows you to specialize a custom serialization format directly on the cast. This format is used when converting the model to an array / JSON.

Absolutely. I made a few assumptions based on the current code, default
migration types, and existing test.
Let me know what y’all have in mind and I’ll tweak this up.

What about $dateFormat? Guess it should be included in datetime cast like datetime:format

$dateFormat is already respected by the datetime cast if no custom format is specified on the cast.

Decided to leave the $dates property in place and mark it as deprecated with a note to use $casts instead. Left tests updated and SoftDeletes updated so that we are using casts internally.

What do people think about adding a @deprecated marker to the $dates property in 7.x, preferable with some link to more info?
This would already signal people a change is coming.

No, it is not deprecated in 7.x. The replacement only exists (in full) in master.

Gotcha, I missed that in fact the $dates property was added back in master => https://github.com/laravel/framework/commit/2bcb1e477484c1f5a203e3517a93174b155c0302
This PR did remove it.