text:
flyway migrated modules causing "Inconsistent Line Endings" popup when Modifying in SSMS

Which version and edition of Flyway are you using?
5.0.7
If this is not the latest version, can you reproduce the issue with the latest one as well?
(Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
DOS command line
Which database are you using (type & version)?
SQL Server 2016
Which operating system are you using?
Windows 7 Professional
What did you do?
(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
What is happening is that I scripted code (tables, procedures, etc.) from a SQL Server database storing it with ANSI encoding (SQL Server gives you options for Unicode and ANSI).
Then migrated it to another SQL Server database which was successful.
Then, when I try to Modify a procedure module in the new database, I get a popup error
saying "Inconsistent Line Ending" and "The line endings in the following file are not consistent. Do you want to normalize the line endings?"
I have tried the following flyway encoding options and none of the them fix the issue:
flyway.encoding=ISO-8859-1
flyway.encoding=Windows-1252
flyway.encoding=UTF-8
Examining file with Notepad++ shows all lines in the file have consistent CR+LF endings in the migration file.  It seems like flyway is doing something to the end of lines during migration.  I have examined many of the reported issues and do not see this addressed.
What did you expect to see?
No error message.
What did you see instead?
The "Inconsistent Line Endings" popup message.

Duplicate to #1420
This has now been fixed. Please try again with the latest code by building from master. Things should now work as expected.

authors: axelfontaine gitnature

repo: flyway/flyway


text:
Validate migration encoding

V5.0.7, Free
Command Line Client
MSSQL 2012 Enterprise
Windows 10
What did you do?
I work with SQL developers who, somehow, manage to create and add a multitude of variously encoded .sql files. For many these do "Fail Fast" but in particular ANSI-encoded files will still execute... with botched characters. This is particularly dangerous.
What do you want to see?
I have loved flyway so far and hope this doesn't come across as entitled. I think an encoding check for the migrations folder would be a great idea especially for these corner cases that can seriously ruin a whole migration. For teams that have automated fully and can't manage to enforce encoding, this will help avoid problems.
Right now my workaround will be to write a powershell script that performs this as part of our Pull Request, Gated Commit process.

Thanks for the suggestion. I can see how this could be useful as an additional safeguard as part of the validate step for example.

We have now addressed this at least partially. Flyway will now complain when it is configured for UTF-8 and being fed a windows-1252 file for example. However when bytes are valid in both encodings like for example UTF-8 and ISO-8859-1 it isn't able to reliably report this and I am honestly not sure it is possible to fix this.

Awesome, thanks for the work and the product!

source: gharchive/issue

authors: Ryanman axelfontaine

license_type: permissive

license_source: github-api


text:
shouldExecute causes issues on subsequent migrations for at least the Docker images

Which version and edition of Flyway are you using?
7.5.2
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command Line
Which database are you using? (Type & version)
SQL Server 2014
Which operating system are you using?
Both Docker images, the base 7.5.2 version and the 7.5.2-alpine
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
We used shouldExecute which worked perfect.  It ignored the migration when it should have and executed when it should have.  However, the subsequent migrations that did not contain shouldExecute failed with the following error:
ERROR: java.lang.IllegalArgumentException: Comparison method violates its general contract

Note: we have tried both the 7.5.2 Docker image and 7.5.2-alpine.
What did you expect to see?
It to execute subsequent migrations successfully
What did you see instead?
ERROR: java.lang.IllegalArgumentException: Comparison method violates its general contract

Note that this error only occurs if the previous migration was not applied.  For example, if migration 1 shouldExecute at server 1 but not server 2, when migration 2 comes along and does not have shouldExecute, it will succeed at server 1 and fail with this error at server 2.

Could you attach sample scripts and script config files that reproduces this? I haven't been able to reproduce this, so there might be subtle differences in the script or environmental differences that are causing this (and possibly https://github.com/flyway/flyway/issues/3071 too)

I'm trying to do a minimal repro but struggling.  I have a suspicion this could be because our placeholder name is "serverName" and that appears to be a reserved placeholder.  Because locally if I have a Docker container running SQL Server and I plugin a URL pointed at localhost and set a placeholder serverName of "test123" then Flyway tried to connect to "test123" instead of localhost.
I will try using a different placeholder tomorrow and report back.

Any update on this?

@DoodleBobBuffPants we haven't had time to circle back to it yet.  It's on our list.  It definitely broke for us, and when we tried it completely new it did not break.  So now we're trying to figure out why it broke.  Clearly something with our setup.

Thanks for letting us know, will be closing until further activity

authors: DoodleBobBuffPants esauser scottsauber


text:
modification of Yolo v2

Hello Felix,
in the article of "Detect and Classify Species of Fish from Fishing Vessels ..." you mentioned:

I used an improved version of YOLO called YOLO v2. It made several small but important changes inspired by Faster R-CNN, such as assigning bounding box coordinate “priors” to each partitioned region and replacing the fully connected layers with convolutional layers, hence making the network fully convolutional. Essentially, YOLO v2 works very similarly to RPN.

May I ask you where you have made this modifications? inside the yolo-voc.cfg file isn't it?
I want to follow you and make these modifications. Would you please help me?

Hello, I used the original implementation in Darknet (https://pjreddie.com/darknet/yolo/). You can follow this guide: http://guanghan.info/blog/en/my-works/train-yolo/ to train YOLO with your own dataset. I also hack into the C code to get the program output predicted bounding boxes.

Thank you.
The article dated at 15/12/22. seems to be for YOLO V1?

Besides, Do you think YOLO v2 or SSD-300 (7++12+COCO) will have less detection errors? in Fine-Tuning.
Although I think we can not Fine-Tune in YOLO. The provided weights is as an initial classification weights and we train from scratch actually.

Yes, the article is slightly outdated. It is for YOLO v1. However, the config files of YOLO v2 and v1 are very similar so long as I recall, so if you can follow that of v1 I am sure you can do the same for v2.
YOLO v2 should outperform SSD-300. Resolution plays an important part in detector performance (can refer to this paper: https://arxiv.org/pdf/1611.10012.pdf). YOLO v2 takes 448x448 inputs while SSD takes 300x300. Speaking from my personal experience, YOLO v2 outperformed SSD-300 in the kaggle competition. In this regard, YOLO v2 vs SSD-512 should be a more fair comparison.
Yes, the provided weights for YOLO v2 (DarkNet19 with 448x448 input resolution pre-trained on ImageNet) is for classification. But it's still very useful as good feature extractor for the detection layers. I used that for my kaggle dataset and it worked quite well.

one missing feature in Yolo v2 is that they have not implemented the angle in training, it is a useful feature when the target objects might rotate in practice, which of course does not apply for the VOC dataset, and that's the reason why they have not implemented it completely.

authors: VanitarNordic flyyufelix

license: MIT


text:
packet browser protocol vlan ignore

When in packet browser selecting protocol decode splits. The split should ignore the vlan header.

bugfixed
fmadio/fmadio20@09f7019
regression pending

new regression for protocol splits
fmadio/fmadio20_regression@179fb13

FW released: 20160927_2347

repo: fmadio/issues


text:
fix all error with scipy sparse matrix

bug here https://github.com/fmfn/UnbalancedDataset/issues/26
all  test passed except Neighboorhood Cleaning Rule and CNNfor now

cnn error fixed

can not just convert sparse to dense in concatenate, roll back to 6df9758, so at least sparse can work on smote.

source: gharchive/pull-request

repo: fmfn/UnbalancedDataset

license: mit

license_source: bigquery


text:
[Algorithm] Euclidean GCD [Java]

This adds the Euclidean algorithm for computing the greatest common
divisor (GCD) of two natural numbers, the largest number that divides
both of them without leaving a remainder.
Closes https://github.com/fnplus/interview-techdev-guide/issues/139

Thanks for contributing.

repo: fnplus/interview-techdev-guide


text:
add DELETE to allowed cors methods

Default cors allowed headers is missing DELETE method, this change sets the AllowMethods explicitly, doesn't rely on cors middleware default.
/cc @adoublebarrel @rdallman

I'll wait for second endorsement before I hit that merge button though.

authors: adoublebarrel kppk

repo: fnproject/fn


text:
Account address is different while use same Mnemonic by starknet.dart BraavosAccountDerivation  and braavos wallet

Describe the bug
Account address is different while use same Mnemonic by starknet.dart and braavos wallet
To Reproduce
Steps to reproduce the behavior:

import Mnemonic to braavos wallet: smoke clock senior verb tube steak wealth cram absorb robust long mutual
wallet show account address: 0x002b945db72c8bb7361ca7457fc3dd3b35831d359c99ee03fddc24f847326d6d
create account by same Mnemonic with Account.fromMnemonic,

 final account = Account.fromMnemonic(
      mnemonic: mnemonic,
      provider: provider, // mainnet
      chainId: chainId, // mainnet chainId
      index: index, // 0
      accountDerivation: accountDerivation, // default to  BraavosAccountDerivation
    );

address is  0x17524b0b247a01969d21d626175d449fc0fb7d3b5fc467a9d22c16f58abc4fd

Expected behavior
same  Mnemonic should have same address with Braavos wallet and BraavosAccountDerivation on starknet.dart

Hi, this is caused because braavos change their class_hash a few months ago. Also, their calldata only needs public key. I sent PR #407 to fix this issue. Please check...thanks.


text:
Fog::Errors::Error (Failed put_object ~~ is too busy)

Fog::Errors::Error (Failed put_object, status = 503 {"code"=>"service_unavailable", "message"=>"c002_v0001111_t0059 is too busy", "status"=>503}):
When user upload any images to b2 bucket, errors occur sometimes.
I found this article
https://www.backblaze.com/b2/docs/integration_checklist.html
But I don't know what should i do.       :-(

Also running into this problem far more often than I'd like. Seems to be an "expected" issue with Backblaze - something I never experienced with S3. I wonder if a rescue/retry built into this gem when this error is seen might help.

authors: HiBTD jonbuda

repo: fog/fog-backblaze


text:
Implement pair wise iso lens.

The abstract view is easy to deal with (lens:p). However, it is hard
to maintain when you need to stich data structures together. Therefore
pair-wise lens [{lens(), lens()}] is compromise for two separate
lists [lens()], [lens()]. It targets practical data transformation
applications.

Coverage decreased (-0.2%) to 43.379% when pulling 6174e3f2a5b5b1317601ba278659ead4f29635f8 on pair-wise-iso-lens into ece7c92034b94826076b208d5ac1044872ec47d7 on master.

authors: coveralls fogfish

repo: fogfish/datum


text:
feature: Jump to search pattern outside of view

Did you check the docs?

[X] I have read all the flash.nvim docs

Is your feature request related to a problem? Please describe.
Thanks for a great plugin!
When searching, I often search for an instance of a keyword that isn't currently on the screen, and it would have been helpful to be able to scroll up/down a page through the buffer
Describe the solution you'd like
I haven't used EasyMotion for years, but with its easymotion-sn and easymotion-tn you can search for a pattern and, while still in the search prompt, use Tab and S-Tab to scroll down/up a page and see targets there.
The description of the feature in the EasyMotion repo can be found here
Describe alternatives you've considered
¯\(ツ)/¯
Additional context
No response

You can use the incremental option for this.

Thanks for the suggestion. I already have incremental turned on and c-g and c-t are nice, but a bit different to what I mean. They jump to the next result, and there could be many in a page. The feature I had in mind is more like a pager (like c-f and c-b), allowing you to select targets in that page

authors: TxHawks folke


text:
fix(groups): changing the transparent option now correctly invalidates the cache

Description
this PR fixes the issue where changing "transparent" option wasn't taken into account when cache was active due to cache not being invalidated properly for "transparent" value changes.
Related Issue(s)

Fixes #561

ty!

authors: folke massimans


text:
Docs say source name is required, implementation doesn't match

https://fonttools.readthedocs.io/en/latest/designspaceLib/xml.html#source-element says name is required. https://github.com/cmyr/norad, used by fontc, adheres to this. However, designspaceLib apparently doesn't actually treat it as required, it generates names where it's missing ("when not present, designspacelib inserts "temporar_master#" or some such").
Could we please update either the docs or the implementation? Since existing projects observably rely on lack of name perhaps the docs is the wiser choice?

@justvanrossum, IIUC you are one of the owners of this?

No, I don't own this. @LettError authored, @belluzj is a major contributor. Etc.

Since existing projects observably rely on lack of name

Indeed, a quick look at some projects here and there reveal not a single one that has a name attribute on <source> elements.
Suggest changing the doc.
(Embarrassed to admit: I didn't really know name existed. Could be useful for Fontra, but it doesn't even attempt to read it.)

I'm ok to make source.name optional, but note that there is a pattern in designspaceLib (which we inherited when the original code was moved to fonttools) whereby basically every attribute (regardless of whether they are deemed "required" by the DS spec) is de-facto optional in the designspaceLib code that reads them? I.e. set to None when missing, and client is left to check for None-ness and wonder what to do with missing values
https://github.com/fonttools/fonttools/issues/1219

authors: anthrotype justvanrossum rsheeter

repo: fonttools/fonttools


text:
[WIP] TTFont: Use mmap if possible

As discussed here:
https://github.com/behdad/fonttools/issues/580#issuecomment-211110222
Before:
$ python -m timeit 'from fontTools.ttLib import TTFont; TTFont("sazanami-gothic.ttf")'
10 loops, best of 3: 66.9 msec per loop
After:
$ python -m timeit 'from fontTools.ttLib import TTFont; TTFont("sazanami-gothic.ttf")'
10000 loops, best of 3: 110 usec per loop
That's a 600x speedup!
Fixes https://github.com/behdad/fonttools/issues/482
HOWEVER, it reintroduces https://github.com/behdad/fonttools/issues/302
Or worse, we'll crash when overwriting:
$ cp Lobster.ttf t.ttf
$ ./ttx -o ./t.ttf ./t.ttf
Dumping "./t.ttf" to "./t.ttf"...
Dumping 'GlyphOrder' table...
Bus error (core dumped)
IMO we should fix this by changing both XML and font output routines to,
instead of calling open, use os.tmpfile(), create output in a new file
and then rename it to the final destination.  It has the benefit of not
leaving a half-written output file behind if an exception occurs.  The
tempfile.NamedTemporaryFile also comes handy.
While checking those out, tempfile.SpooledTemporaryFile also comes handy,
when it's available, to replace BytesIO in the following part of TTFont.save():
# write to a temporary stream to allow saving to unseekable streams
tmp = BytesIO()

Looks like we need to start misc.fileTools to abstract the details away.

This is not ready to be merged; uploaded for discussion.
That's enough playing with this issue instead of getting started on filing taxes...  @anthrotype Feel free to finish it!

Wow! That’s impressive.

Coverage increased (+0.002%) to 70.403% when pulling 02e023e2b8561a7dc63c88346bff4fe1e0401fa2 on mmap into 2312880d798c327686f962121869022629f00014 on master.

Coverage decreased (-0.03%) to 70.372% when pulling fb11587a8fe3d5a36c8890aeaf8a0fea549ea10b on mmap into 2312880d798c327686f962121869022629f00014 on master.

I've never used the mmap module, but your timing example can't be right: mmap reads lazily, so your before and after test pretty much compare reading the entire file into memory vs. not reading the entire file into memory. A fair comparison would be to parse all glyph data after creating the TTFont().

Also: it's a little (read: very) scary that mmap can cause a core dump...

Ah ok, I think I was misunderstanding what you're trying to do. But I think the whole exercise is a little backwards, and your proposal to use temp files (so we can overwrite loaded fonts) is probably much better. (It would also solve #536.)

Right, the goal of this exercise was to make the font loading be lean again, like it used to be when we didn't read the whole file.  @justvanrossum you are right that when we do the temp file, then we can go back to not reading the font file at all, like before.  That said, mmap() is still a more efficient way than reading the file, so I suggest we keep this as well.  I know this is not common in Python, but since there is a mmap module we might as well use it, as it saves a copy.

Not at all convinced of using mmap in this case. How much speed can be gained? Let's measure that. I doubt data copying and file io is contributing much to any lack of performance. mmap is less portable, and can cause core dumps (that's actually pretty disgusting all by itself). Remember, even a huge TTF is a small file by today's standards.

I haven't used mmap either, and would like to read a bit more about it.
As far as I understand, it uses the operating system's virtual memory to access the data on the filesystem directly. It feels a bit risky. Instead of making sys calls like open, read etc., it puts the file data into memory and allows one to directly manipulate that in memory.
I quite like the fact that it works the same as both a bytearray and a file object though. However, I see it has different interfaces for Unix and Windows. And It feels quite low-level in general... 😕

Exactly. Btw. FontTools has never been about performance. It's about being flexible and reliable in accessng and manipulating font data. Sure, if things can be rewritten in a way that improves performance, great, but it should not make the code more complicated. Might as well rewrite the whole thing in C++ then, and that's not why we're here.

I don't insist in this going on.  Definitely not.  But want to share my perspective as well:

HarfBuzz and FreeType both mmap() the font file and use it.  If they didn't, every app on an Android device would have consumed many megabytes more memory.

I understand FontTools was not originally design for the kind of work that is latency-critical.  However, Google Fonts is using it to subset fonts on demand, and when I added the subset module two years ago, I significantly sped up many parts, most in loading.

I do want to measure this more as well.

If the use of mmap can be abstract and reliable (no core dumps!) and portability isn't at stake, and brings us measurable advantages, then by all means, go ahead.

looks like mmap does not work with standard I/O streams:
http://stackoverflow.com/questions/6510819/using-mmap-with-popen
(we haven't implemented it yet, but I think it's nice if fonttools scripts could read/write from stdin/stdout -- binary data, not just text).

(we haven't implemented it yet, but I think it's nice if fonttools scripts could read/write from stdin/stdout -- binary data, not just text).

That already works in my implementation.   It falls back to the code that was there before.

Can this be merged?

Ugh, I’ve pressed the “Update branch” button in GitHub, assuming this would rebase to master; instead, it merged master into the branch and now the branch is messed up.
Anyhow, what should be done with this pull request? Personally I don’t see any disadvantages with trying to mmap (and falling back to normal I/O in case of failure), as the pull request already does. So I think we should merge it. My only concern is what happens on Windows. @anthrotype, do you know what it would take to make this work on Windows? See the TODO in the code.

Anyhow, what should be done with this pull request if it actually worked? Personally I don’t see disadvantages with trying to mmap (and falling back to normal file I/O in case of failure), like the pull request already does. So I think we should merge it. My only concern is what happens on Windows. @anthrotype, do you know what it would take to make this work on Windows? See the TODO in the code.

Windows is not a concern.  We either implement using mmap on Windows, or it will just fallback to non-mmap.
This cannot be merged yet however, as we need to clean up all places where we write to files to write to a temp file and rename it.  Right now, with the mmap branch, if source and destination of ttx are the same file, we crash.  That's not acceptable.

I still think this is a good idea, but closing since others don't :).

authors: anthrotype behdad brawer coveralls justvanrossum moyogo


text:
Text placeholder in Delegate page

Browsing inside the Delegate section, I've found out that hoovering over Status display a text placeholder "lore ipsum"

This has been updated and aligned with BD.

authors: bragaz kwunyeung

repo: forbole/forbole-x


text:
Return codes are different when calling sfdx force:create:org using Windows sfdx cli and the npm installed sfdx cli

Summary
Return codes from the "sfdx force:org:create" command differ if performed using the Windows SFDX CLI (see instructions Install the CLI on Windows) versus the npm equivalent set up using the Install the CLI with npm instructions. The Windows SFDX CLI will return 1 once the command has completed and the NPM equivalent will return 0. Both will create the org as expected however the Windows SFDX CLI version causes our setup script to exit.
Steps To Reproduce:
For each of Windows SFDX CLI and NPM SFDX CLI perform the following ensuring that your path is picking up the correct version of sfdx each time:

Inside a known good project run: sfdx force:org:create --setalias test1 --definitionfile config/project-scratch-def.json --durationdays 1 --wait 10
The scratch org should have been created successfully
Once this has finished run: echo $?

Expected result
Both Windows SFDX CLI and NPM SFDX CLI should exit with a return code of 0
Actual result
Windows SFDX CLI exits with a return code of 1
System Information
sfdx version --verbose --json
{
"cliVersion": "sfdx-cli/7.155.1",
"architecture": "win32-x64",
"nodeVersion": "node-v16.15.1",
"pluginVersions": [
"@oclif/plugin-autocomplete 0.3.0 (core)",
"@oclif/plugin-commands 1.3.0 (core)",
"@oclif/plugin-help 3.3.1 (core)",
"@oclif/plugin-not-found 1.2.6 (core)",
"@oclif/plugin-plugins 1.10.11 (core)",
"@oclif/plugin-update 1.5.0 (core)",
"@oclif/plugin-warn-if-update-available 1.7.3 (core)",
"@oclif/plugin-which 1.0.4 (core)",
"@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)",
"alias 2.0.1 (core)",
"apex 0.13.0 (core)",
"auth 2.1.0 (core)",
"community 2.0.0 (core)",
"config 1.4.12 (core)",
"custom-metadata 2.0.0 (core)",
"data 2.0.3 (core)",
"generator 2.0.1 (core)",
"info 2.0.1 (core)",
"limits 2.0.1 (core)",
"org 1.13.2 (core)",
"salesforce-alm 54.5.1 (core)",
"schema 2.1.1 (core)",
"sfdx-cli 7.155.1 (core)",
"signups 1.1.2 (core)",
"source 1.10.2 (core)",
"telemetry 2.0.0 (core)",
"templates 54.8.0 (core)",
"trust 2.0.0 (core)",
"user 2.0.2 (core)"
],
"osVersion": "Windows_NT 10.0.19044"
}

Hi @waterfif, which shell or terminal are you using?
The fact that you state to use echo $? makes me think you might be using git bash or WSL? If so, we don't support either of those, unfortunately.
I just tried and can't reproduce this on Powershell or cmd.exe.
npm version:

installer version:

Hi RodEsp,
Thanks for the response. You are correct, I'm using Git Bash locally. The script we use to setup scratch orgs on our Ubuntu CI environment is also used to setup our scratch orgs locally hence the use of Git Bash on Windows. I'll close the ticket as Git Bash is not supported.

authors: RodEsp waterfif

repo: forcedotcom/cli


text:
ERROR running force:source:convert:  Unexpected child metadata  [.../force-app/main/default/obje ctTranslations/npo02__Household__c-de/npo02__OppAmountLastNDays__c.fieldTranslat ion-meta.xml] found for parent type [CustomObjectTranslation]

Summary
We get an error when creating a package version with SFDX 7.172.0. The creation of package version with same content works as expected with 7.171.0
Steps To Reproduce:

cci flow run build_feature_test_package (CumulusCI) which basically runs force:package:version:create

Expected result
Package version is created
Actual result
ERROR running force:source:convert:  Unexpected child metadata
[/.../force-app/main/default/obje
ctTranslations/npo02__Household__c-de/npo02__OppAmountLastNDays__c.fieldTranslat
ion-meta.xml] found for parent type [CustomObjectTranslation]
System Information
sfdx 7.172.0
CumulusCI 3.67.1
Additional information
Same works with sfdx 7.171.0 and CumulusCI 3.67.1

This also affects force:source:deploy and now broke our pipeline

I think we got all the COFT bugs fixed last year.  Is this still reproducible on newer CLIs?

authors: fabioAtANT j-schreiber mshanemc


text:
Salesforce Code Analyser is not working

whenever I'm trying to run code analyser its not working even after re-installation so please resolve this ASAP

@nitinsen05 , can you give us any more information about this? E.g., what version of the VSCode extension you're using; what version of Code Analyzer itself you're using; what the actual behavior you're observing is; etc?
We need a little more to go on than what you're currently providing here.

hi I've shared the necessary details below and shared the screen shot of my
issue(code analyzer seems stuck not processing), please resolve this issue
as soon as possible.
Vs code version:- 1.95.3 (Universal)
Code analyzer version V1.3.0
On Mon, Nov 25, 2024 at 9:32 PM Josh Feingold @.***>
wrote:

@nitinsen05 https://github.com/nitinsen05 , can you give us any more
information about this? E.g., what version of the VSCode extension you're
using; what version of Code Analyzer itself you're using; what the actual
behavior you're observing is; etc?
We need a little more to go on than what you're currently providing here.
—
Reply to this email directly, view it on GitHub
https://github.com/forcedotcom/sfdx-code-analyzer-vscode/issues/149#issuecomment-2498421186,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAXJG6PSW7RQXHJQ2JZ3UDT2CNCYRAVCNFSM6AAAAABSNDSABSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJYGQZDCMJYGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

@nitinsen05 , Code Analyzer v1.3.0 is an extremely old version and won't work with the VSCode Extension. Please try upgrading to v4.7.0 with sf plugins install @salesforce/sfdx-scanner@latest, and let us know if that resolves the issue.

I used the above command but still its showing the old version and code
analyzer is not working
On Mon, Nov 25, 2024 at 10:45 PM Josh Feingold @.***>
wrote:

@nitinsen05 https://github.com/nitinsen05 , Code Analyzer v1.3.0 is an
extremely old version and won't work with the VSCode Extension. Please try
upgrading to v4.7.0 with sf plugins install
@@.***, and let us know if that resolves the
issue.
—
Reply to this email directly, view it on GitHub
https://github.com/forcedotcom/sfdx-code-analyzer-vscode/issues/149#issuecomment-2498593155,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAXJG6KV5NOYDMU76TNAWQL2CNLLVAVCNFSM6AAAAABSNDSABSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJYGU4TGMJVGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

@nitinsen05 , can you do sf -v?

i need your assistance so can you please connect with me via google meet or
something else it will be really helpful for me
On Mon, Nov 25, 2024 at 10:54 PM Josh Feingold @.***>
wrote:

@nitinsen05 https://github.com/nitinsen05 , can you do sf -v?
—
Reply to this email directly, view it on GitHub
https://github.com/forcedotcom/sfdx-code-analyzer-vscode/issues/149#issuecomment-2498615531,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAXJG6LPFFGCIKZ2FUQKA6T2CNMOVAVCNFSM6AAAAABSNDSABSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJYGYYTKNJTGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Manually resolved via meeting. The problem was that the machine didn't have viable versions of Node or Java installed.

hi @josh thanks for the support my issue has resolved
On Mon, Nov 25, 2024 at 11:06 PM Josh Feingold @.***>
wrote:

Sure. My work email is @.*** Please email me at that
address and we can work something out.
—
Reply to this email directly, view it on GitHub
https://github.com/forcedotcom/sfdx-code-analyzer-vscode/issues/149#issuecomment-2498640324,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAXJG6NF3DZCCS6RYYNQT3L2CNNYPAVCNFSM6AAAAABSNDSABSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJYGY2DAMZSGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

repo: forcedotcom/sfdx-code-analyzer-vscode


text:
cli ConfigBuilder is complex, and breaks encapsulation

the cli's ConfigBuilder is complex, and a little 'inside out'. Also it's not a 'builder'.
the way it works currently is,

CargoMsrvOpts is parsed from the user's input
the options are passed in turn to a set of 'configurators'
each configurator knows the internal structure of the options struct
each configurator sets the appropriate value by calling a method on the builder

this is quite hard to follow
the 'configurators' shouldn't need to 'know' the internal structure of the options (breaks encapsulation)
this isn't a 'builder' api at all. The 'builder' does use a fluent api (where methods take self, but it might as well be a plain struct.

The solution I would propose is to move the logic for parsing the 'options' into the options struct itself.

you can see an example of what i mean in #355 (there's a fair bit more to do)

Thanks for the feedback and considerations.
I believe ConfigBuilder is a builder. It follows a style which is described by the Rust book as a consuming builder.
Notably, the 'configurators' themselves are not part of the builder. They're only used to configure it, by handling some of the more complex cases where changing the CLI would break backwards compatibility, and I wasn't yet willing to do so.
Yes, the configurators aren't strictly necessary, I could also written some plain functions, instead of boxing them in per input, or kept it like it was before: one huge function which configured everything. Something needs to call the builder and its methods after all.

each configurator knows the internal structure of the options struct
This is probably indeed not necessary, but sometimes practicality wins from purity =). One way to fix the encapsulation problem you describe would be by added getter methods on the Opts struct, and removing the pub(in cli::). However, it's a rather marginal win, since the visibility is already scoped to the cli module, and adds a bunch of getter methods which would only be used to configure the builder again. Encapsulation can be important, but I don't think it's truly an issue here.

ConfigBuilder is certainly getting more complex :). I've noted as much when I last worked on this part. Below is an excerpt from the source:
https://github.com/foresterre/cargo-msrv/blob/ede4adaa76691bda7b2e4927afc5f09669390343/src/config.rs#L203-L206
While it's getting lengthy, and doesn't integrate very well with some ideas I've been working on recently (layered configuration), I don't think it's too complicated; in my opinion it's rather straightforward.

The solution I would propose is to move the logic for parsing the 'options' into the options struct itself.

I'm not necessarily against this, but something to consider is the following: the more subcommands, options, and flags are added, the more methods will be added to CargoMsrvOpts. I think that moving all cli 'parsing' methods to CargoMsrvOpts does just that, move the logic to some other place.

authors: danieleades foresterre

repo: foresterre/cargo-msrv


text:
是否可以加前置快捷键呢？

是否可以增加按下某个按键比如ctrl才能触发划词的选项呢，因为很多情况下可能划词不需要搜索什么的，因为之前用过一个这样扩展，感觉体验稍微好点

是的，我也正是这样计划的。
正在开发中，骚等几天

@lyphol 已经增加Ctrl/Control, Alt, Shift 按键及鼠标左,中,右键的划动

@lyphol 去插件中心直接下载，或者等待自动更新
有问题，请及时反馈，谢谢

authors: foreverglory lyphol

repo: foreverglory/selection-popup


text:
A working example of the MultistepWizard for react native

Hi, could someone provide me with a working example of the multistepwizard for react native ? https://github.com/jaredpalmer/formik/blob/master/examples/MultistepWizard.js
I'm trying for a week now and still can't get a perfect result. I can go forth and back in steps. Still here are some of things I'm intending to achieve:

update the state with value from TextInputs, pickers (custom) and other field types;
a Yup validation of each step;
get values after submit and process them and send them with an API call to server.

EXTRA : one step consist of inviting the user to take  images with his camera, or select images from camero roll, and choose one of them as cover image (Radio button involved or a check on the selected image ?) Any help on that side would be highly appreciated too. Thanks in advance.

Closing as being tracked in https://github.com/formium/formik/issues/1315

authors: maddhruv sunviwo

repo: formium/formik


text:
Field validate doesn't mark as touched on submit

🐛 Bug report
In our product we use validationSchema to validate our form but we also allow customers to add their own form fields to it. Since we have no idea what their validation will be it can't be included in our Yup validation, so they need to validate at the Field level. When the form is submitted Formik shows the field as invalid but not as touched like it does with validationSchema.
Current Behavior
Fields with validate don't get marked as touched so the error isn't shown as you can see below. Email is Yup validation and Age field validation.
props = {
  "values": {
    "email": ""
  },
  "errors": {
    "age": "Age is required",
    "email": "Required"
  },
  "touched": {
    "email": true
  },
  "isSubmitting": false,
  "isValidating": false,
  "submitCount": 1,
  "dirty": false,
  "isValid": false,
  "initialValues": {
    "email": ""
  },
  "validateOnChange": true,
  "validateOnBlur": true
}

Expected behavior
Field marked as touched and error shows.
Reproducible example
Click on the Submit button and look at the Formik state. Email is validated by Yup and has error and is touched. Age is validated at the field and has an error but is NOT touched.

Your environment

Software
Version(s)

Formik
1.5.7

React
16.8.6

Yup
0.27.0

Hey @MikeSuiter, this is a dup of #691 and #738.
In your particular case the workaround is just to specify both fields in initialValues option:
"initialValues": {
  "email": "",
  "age": "",
}

Closing due to long inactivity

authors: MikeSuiter maddhruv sigerello


text:
Documention Update : Write use techstack in the project

in readme file i will add usetechstacklogo .it will be look attractive then

I am new a Gssoc24 can you assign it to me


text:
Event Card Animation doesn't occur

The slideup animation of events doesn't occur

Working on it :+1:

please attach a gif of what you are trying to say

repo: fossasia/open-event-android-general


text:
Web Manifest + icons

Added Web Manifest and some basic icons + favicon

Thanks for the PR @MaxBorsch
If there is a corresponding GCI instance that has not been approved, please link it here in the comments and someone from FOSSASIA will approve it

authors: MaxBorsch championswimmer

repo: fossasia/open-event-webapp


text:
Simplify Form: Take out API version, pre-select options, fix spelling

Please simplify the form as follows:

Choose Session Style - pre-select "Expandable"
Choose Map Integration - pre-select "Open Street Map"

Get rid of the underscore in the map names

Get rid of "Choose your API version". After the transfer to open event v2 we are only using API v2
Choose your data source - pre-select API

Change text "Choose your data source" to "Choose Your Data Source"
Change text "API endpoint of event on OpenEvent" to "API Endpoint"
Change text "Link to Open Event API endpoint" to "Link to Open Event API Endpoint"
currently the text below "Link to Open Event API endpoint" is build, change to not bold
for the JSON option currently the text "Zip file containing resources for the event" is bold, change it to non-bold

Change text of the form field of Google Analytics and Calendar as follows

"google analytics id" to "Google Analytics ID"
"google calendar..." to "Google Calendar ..."

Please provide a test link to allow reviewers to test changes quickly.

@mariobehling I would love to work this issue. Please assign it to me.

repo: fossasia/open-event-wsgen


text:
Fully Structured Repo

In this PR, I have edited the repo as per @mariobehling  guidelines of making three different folders of images, schematics and experiments and merging Experiments.md with README.md
Solves issue : #3

@mariobehling   @CloudyPadmal   Please review this PR and suggest changes if needed.

Thanks. Let's also add links on the reader.

repo: fossasia/pslab-experiments


text:
Nested Reducers in @redux-eggs/next

Really, really promising library here!
I am putting together a POC to replace an existing solution for dynamic reducers and modular-redux.  I have a working nextjs sample application working with redux-eggs but I have a question about nested redux state.  Do you have any ideas on how to handle it?
I am looking to achieve the following redux state shape:
{
  section1: {
    foo: 'bar',
  },
  section2: {
    bar: 'baz'
  }

I was hoping that I would be able to set these in my eggs via the reducersMap property but it doesn't look like it works as I had hoped
export const myEgg= () => {
    return {
      id: 'my-egg',
      keep: true,
      reducersMap: {
          section1: {
            foo: () => 'bar',
          }
      },
    }
  }

I found I could update as expected using the following nested-combine-reducers utility in your store example in place of combineReducers but if the reducers share the same parent key then the updates seem to break.
// store.js
import { combineReducers } from 'redux';
import { createWrapperInitializer } from '@redux-eggs/next'
import { createStore } from '@redux-eggs/redux-toolkit'

/**
 * Takes a Reducers maps with multiple levels of nesting and turns it into in a single reducing function.
 function nestedCombineReducers(map) {
    if (!map) { throw new Error('You must specify a reducers map.'); }
    const flatReducersMapObject = {};
    const recursiveMapKeys = Object.keys(map);

    // eslint-disable-next-line no-restricted-syntax
    for (const recursiveMapKey of recursiveMapKeys) {
        const recursiveMapValue = map[recursiveMapKey];
        if (recursiveMapValue === null) {
            // eslint-disable-next-line no-continue
            continue;
        }
        if (recursiveMapValue === undefined) {
            // eslint-disable-next-line no-continue
            continue;
        }
        // Hopefully a reducer function, let's store it to combine it later
        if (typeof recursiveMapValue === 'function') {
            const reducer = recursiveMapValue;
            flatReducersMapObject[recursiveMapKey] = reducer;
        }
        // Nesting found, let's go deeper !
        if (typeof recursiveMapValue === 'object') {
            const nestedRecursiveReducersMapObject = recursiveMapValue;
            flatReducersMapObject[recursiveMapKey] = nestedCombineReducers(nestedRecursiveReducersMapObject);
        }
    }

    // Once all the properties have been processed, the ReducersMap is no longer incomplete and can be combined one last time
    return combineReducers(flatReducersMapObject);
}

const HYDRATE = '@eggs/hydrate';

const combiner = reducersMap => {
  const combinedReducer = combineReducers(reducersMap)

  return (state = {}, action) => {
    if (action.type === HYDRATE && action.payload) {
      return combinedReducer({ ...state, ...action.payload }, action)
    }

    return combinedReducer(state, action)
  }
}

const createAppStore = () => createStore({ combiner })

export const wrapperInitializer = createWrapperInitializer(createAppStore, {
    hydrationActionType: HYDRATE,
})

Again this is really great work.  Any help would be appreciated!

I am not fully convinced that there isn't a flaw in my nested combined function but any advice is appreciated if the issue is resolvable on your side in anyway :)

I have pushed an example repo from a create-next-app of what I am trying to achieve if it helps
https://github.com/dptoot/next-redux-eggs
Any installation will need the --peer-legacy-deps flag as there are some peer dependency issues with some of the @redux-eggs packages and the latest redux and react packages

After some poking around I "think" the issue has something to do with the way the reducer map is currently constructed.  Logging out the reducerMap argument here  on the page where 2 eggs are loaded with the same nested reducer parent node shows that only the first in the eggs array passed to the page wrapper makes it to the reducer map.
I believe its due to this line that checks for no egg count before adding.
https://github.com/fostyfost/redux-eggs/blob/5479182935d6f0d3e97fceaa94218ce494fd214d/packages/core/src/reducer-tray/index.ts#L38
@fostyfost Apologies for the spam and if this is not helpful or a feature that you are interested in adding but this library is currently solving all my problems except this one little thing :D

@dptoot hello! Thank you for your question. I currently have no plans to add support for nested reducers to the library.

authors: dptoot fostyfost

repo: fostyfost/redux-eggs


text:
Can't find a way to follow jsonapi spec for the 'included' field

Hello thanks for this awesome gem!
I'm having an issue when trying to define the schema following jsonapi spec, particularly with the "included" array where someone can specify objects related to the primary data, an array that can have different model/schema types.
I currently have a schema defined for an Article and then a schema for the Author and the Comments. If i try to relate this two last schemas (Author and Comments) on the 'included' array of the Article block it doesn't work. I tried with bot these two forms
      property :included, type: :array do
        items do
          key :'$ref', :Comment
        end
        items do
          key :'$ref', :Author
        end
      end

And with
      property :included, type: :array do
        items do
          key :'$ref', :Comment
          key :'$ref', :Author
        end
      end

The full Article, Comment and Author schemas are something like these
module Swagger::ArticleSchema
  extend ActiveSupport::Concern
  include Swagger::Blocks

  included do
    swagger_schema :Article do
      property :id do
        key :type, :integer
      end
      property :type do
        key :type, :string
      end
      property :attributes, type: :object do
        property :text do
          key :type, :string
        end
      end

      property :included, type: :array do
        items do
          key :'$ref', :Comment
        end
        items do
          key :'$ref', :Author
        end
      end #end included
    end
  end
end

module Swagger::CommentSchema
  extend ActiveSupport::Concern
  include Swagger::Blocks

  included do
    swagger_schema :Article do
      property :id do
        key :type, :integer
      end
      property :type do
        key :type, :string
      end
      property :attributes, type: :object do
        property :text do
          key :type, :string
        end
      end
    end
  end
end

module Swagger::AuthorSchema
  extend ActiveSupport::Concern
  include Swagger::Blocks

  included do
    swagger_schema :Article do
      property :id do
        key :type, :integer
      end
      property :type do
        key :type, :string
      end
      property :attributes, type: :object do
        property :full_name do
          key :type, :string
        end
      end
    end
  end
end

Is there any way to get them working with $ref? Or i need to manually specify all the 'included' relations manually?
Thanks!

Same issue here: https://github.com/fotinakis/swagger-blocks/issues/122

repo: fotinakis/swagger-blocks


text:
Accordion Deep Linking scrolls to top of accordion when using smudge

What should happen?
The window should scroll down to the accordion list item identified in the hash.
What happens instead?
It scrolls down only to the top of the entire accordion.
Possible Solution
Test Case and/or Steps to Reproduce (for bugs)

Test Case:

How to reproduce:

Paste the doc example deep linked accordion onto a page with basic smudge options enabled.
Add a bunch more list items so that there is room to scroll (and maybe put stuff above the accordion so that if it wants to scroll to the top of the accordion, it has room to move)
Open a list item so that you can copy the url
Navigate away and then paste the url with the deep linked hash into the url bar and press enter
Behold as it scrolls to the top of the accordion rather than down to a list item.

Context

...
Your Environment

Foundation version(s) used: 6.6.3
Browser(s) name and version(s): Chrome 84.0.4147.105
Device, Operating System and version: Macbook Pro Catalina 10.15.6
Link to your project:

Checklist

[x] I have read and follow the CONTRIBUTING.md document.
[x] There are no other issues similar to this one.
[x] The issue title and template are correctly filled.

Hi @brimby,
thanks for reporting this. Please provide a woriking codepen which reproduces / demonstrates this issue.
You can use and fork this (CSS and JS are already in there and Foundation is already initialized): https://codepen.io/DanielRuf/pen/NWNjPbz

I think this issue still exists. For an example see the foundation docs site. The following link to the same place
https://get.foundation/sites/docs/accordion.html#deeplink1
https://get.foundation/sites/docs/accordion.html#deeplink3

authors: DanielRuf audave brimby

repo: foundation/foundation-sites


text:
<<$FREE!>@>Xbox Gift Card Codes [Updated] 50+ New Redeem Code 2024✔How to get Xbox Gift Cards FOR FREE

Hey there, Xbox fans! Are you ready to level up your gaming experience with some exciting news? We've got something special in store for you - introducing the Xbox Gift Card Generator 2024! That's right, we're bringing you the latest and greatest way to score free Xbox gift cards and elevate your gaming adventures.With the Xbox Gift Card Generator, you can say goodbye to spending your hard-earned cash on game purchases.
🔴👉 👉CLICK HERE TO FREE GENERATOR
🔴👉 👉CLICK HERE TO FREE GENERATOR
Our innovative tool allows you to generate free Xbox gift card codes, giving you access to a world of thrilling games, add-ons, and more, without breaking the bank.
But wait, there's more! We're not just stopping at the Xbox Gift Card Generator - we're also hosting epic Xbox Gift Card Giveaways! Get ready to participate in exciting contests and sweepstakes for a chance to win free Xbox gift cards and unlock a treasure trove of gaming goodness.
And that's not all - we understand the value of in-game currency, which is why we've introduced the Xbox Money Generator. Say hello to a hassle-free way of earning free Xbox money to power up your gaming experience. Whether it's purchasing in-game items or expanding your gaming library, the Xbox Money Generator has got you covered.
For those of you looking for the ultimate gaming treat, the Xbox Free Gift Card is here to make your day. Yes, you heard that right - free gift cards for the Xbox community! It's our way of showing appreciation to our dedicated gamers and making sure you have all the resources you need to conquer new gaming challenges.
Redeeming your Xbox gift cards has never been easier, thanks to the Xbox Gift Card Redeem feature.
Simply enter your gift card code and unlock a world of gaming possibilities. Whether you're a seasoned gamer or new to the Xbox universe, the Xbox Gift Card Redeem feature is designed to make your gaming journey seamless and enjoyable.
So, what are you waiting for? Dive into the excitement of the Xbox Gift Card Generator 2024 and elevate your gaming experience like never before. With free gift cards, giveaways, and a money generator at your fingertips, the possibilities are endless. Get ready to level up and unleash the full potential of your gaming adventures with Xbox!

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card

.
.
.
.
.
.
.
.
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card
.
.
.
.
.
.
.
.

🔴📺📱👉 Click here Free Xbox Gift Card
🔴📺📱👉 Click here Free Xbox Gift Card


text:
Forge Crashes running forked tests

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (4e141e7 2022-07-21T00:11:34.699666Z)
What command(s) is the bug in?
forge test -f $INFURA -vvvvv --match-contract LandNFT --match-test testSafeMintWithETH
Operating System
macOS (Apple Silicon)
Describe the bug
This comes up occasionally when I am running forked tests.
Compiler run successful
The application panicked (crashed).
Message:  could not instantiate forked environment:
Failed to get block for block number: 15186082
latest block number: 15186082
Location: evm/src/executor/opts.rs:68

This is a bug. Consider reporting it at https://github.com/foundry-rs/foundry

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
Abort trap: 6

looks like an rpc issue
does
curl -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method": "eth_getBlockByNumber", "params": ["latest", false],"id":67}' "$INFURA"

work?

Yes it does
On Thu, 21 Jul 2022 at 18:55, Matthias Seitz @.***>
wrote:

looks like an rpc issue
does
curl -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method": "eth_getBlockByNumber", "params": ["latest", false],"id":67}' "$INFURA"
work?
—
Reply to this email directly, view it on GitHub
https://github.com/foundry-rs/foundry/issues/2427#issuecomment-1191587101,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH773DX7GB7NWIV76AJ7WYTVVFQGHANCNFSM54HTGC6Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

does this happen consistently? maybe just a flake and the node didn't feel like sending the block -.-

Sounds reasonable. Closing this and will keep monitoring the situation. It
might be helpful to handle the error and not panic.
On Thu, 21 Jul 2022 at 20:23, Matthias Seitz @.***>
wrote:

does this happen consistently? maybe just a flake and the node didn't feel
like sending the block -.-
—
Reply to this email directly, view it on GitHub
https://github.com/foundry-rs/foundry/issues/2427#issuecomment-1191693598,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH773DUXMYALCCN5TUSTVVLVVF2Q5ANCNFSM54HTGC6Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

authors: Genysys mattsse

repo: foundry-rs/foundry


text:
Filter for spell range in the spell compedium

Adding a filter for spell range in the spell compedium, for example for sorting out touch spells for spellstrike

Closing in favor of the consolidated issue #6588


text:
Bestiary Redirects

Issue: As of version 6.5.0, Bestiary creatures that have equivalents in Monster Core are being redirected to the Monster Core version in both the compendium navigator and the compendium search. What's worse, some creatures appear to have been completely removed from the Bestiary compendia (e.g., Guard Dog, Animated Broom, Shadow, Greater Shadow, all of the Zombies, etc).
This makes Legacy play extremely uncomfortable at best, for creatures that have to be sourced directly from the compendium rather than through search or the compendium navigator, or impossible at worst, for creatures that have been removed from the compendia altogether. Note that this also reduces the value of the Legacy module, since it does not affect the redirects, nor does it contain the original (full) versions of the Bestiary compendia themselves
It also restricts the flexibility of the Bestiary and Monster Core token packs, since some creatures that have different art across the two packages have now been removed from the compendia, making one of the art options completely redundant
Solutions: A radical solution would be to undo the redirect altogether, since as far as I can tell it seems to only be removing data and choice without adding any value. A more compromising and likely preferable alternative would be to add a toggle to switch between allowing redirects and blocking them.
Edit: The changes appear to have been started before 6.5.0, but the issue remains the same - what is the need in purging the Bestiary compendia?

We are not keeping duplicate actors or undoing the redirects. I am working on an update to the legacy module to add the bestiary 1-3 actors to it, but have not had time to finish it yet.

@TikaelSol Thanks, it's good to know that the data won't be gone completely!

authors: TikaelSol pinkflumph


text:
IWR does not cover splash damage

The iwr doesn't account for the splash weakness of swarms.

me stupid


text:
Feature request: Add an option to keep the better result with hero points

It's a fairly common house rule that can't easily be handled from a macro or module, but is simple to implement in the system

Sorry, this is module territory.

authors: alexbrault stwlam


text:
Fix overlapping images in compendium browser

Also slightly reduces padding and removes unnecessary margin from rarity tags in compendium browser to keep within 2em height.
Before:

After

Could also set aspect-ratio: 1/1; and object-fit: contain; on the image itself if keeping a uniform height across all rows is desired, though some images will be hard to see.

How does everything look in item results now?

Looking through equipment, feats, spells, etc. everything seems to look fine. Items with two lines of text get 2px taller, looks like the text was previously overflowing into the padding. As an added benefit, text remains readable when wrapping to 3+ lines on a narrow window.
Before:

After:


text:
Allow thrown weapons to have reload 0

Currently, a weapon is defined as being thrown if it is ranged and has reload of - or null. Also, thrown weapons' reload times are forcibly set to - as this is the value that almost all thrown weapons use. However, the shuriken has a reload of 0. This is currently impossible to set in the system, as even if one tries to manually alter it, it is set back to -.
I've changed four things:

The reload value is set to - only if it is not already set to something else. This allows setting thrown weapons to have a different reload value.
The definition of a thrown weapon is now a ranged weapon with the "thrown" trait. This removes the dependency on the reload value.
The definition of a weapon requiring ammunition is now a ranged weapon that is not thrown and has a non-- reload time.
The shuriken now has a reload of 0.

I'm not seeing a reason to consider the shuriken case as anything other than an obvious error.

I'm not sure what you mean exactly.
If you mean that a user will easily spot it as an error, and should know that it should be reload 0, then I don't agree since the Foundry system should give them the correct information.
If you mean that the shuriken is a data entry error and should be corrected, that's impossible without the rest of this change because the reload value is current reset to - during data preparation because it's a thrown weapon.

I think shark means that shuriken should be -

Ah, I see. I don't see any evidence that it is an error. After three printings of the CRB, the shuriken still has reload 0 and I've seen no discussions around it being an error.
There is also precedence for this from 1st edition, where the shuriken was "...treated as ammunition for the purposes of drawing them...", which I think is what Paizo was going for by making it reload-0.

Ah, I see. I don't see any evidence that it is an error. After three printings of the CRB, the shuriken still has reload 0 and I've seen no discussions around it being an error.
There is also precedence for this from 1st edition, where the shuriken was "...treated as ammunition for the purposes of drawing them...", which I think is what Paizo was going for by making it reload-0.

A lot of errors persist in the CRB despite errata. Some even get worse. Actually giving it a reload value of zero opens a massive can of worms that have no clear solutions. I'd like to get official clarification on it and all its ramifications before moving forward on treating it differently than any other thrown weapon.

I've tried to have a look and I can't find any discussions around this rule being an error, apart from one off-hand comment back in November on the Discord server about it possibly being a typo (there was no further discussion I don't think). Usually errors like this are fairly well-documented on forums.
I doubt it'll be possible to get anyone official to state that this isn't a typo, since that claim could be made about any ruling someone disagrees with. However, I've asked the question on the Paizo forum so maybe something will come out of it.

authors: CarlosFdez JDCalvert stwlam


text:
Add intimidation bonus to hellknight signifier dedication.

Addresses part of #4447. I'm not sure if we can do the rest, and not sure if we should add a toggle.

Superseded by #4592, closing

authors: TMunsie TikaelSol


text:
DRUP-13: Front page config

Sets up a 'frontpage' content type.
Testing:

[ ] Pull down the project builder: git clone git@github.com:fourkitchens/sous-project.git
[ ] Edit the composer.json from the 'sous-project' to use this branch. ~Line 30 should read: "fourkitchens/sous": "dev-drup-13--front-ct",
[ ] Run lando start
[ ] Run lando composer install
[ ] Visit the site: https://sous-project.lndo.site/ and run through install process.
[ ] Verify that you can create a frontpage: https://sous-project.lndo.site/node/add/frontpage

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

authors: americkson ccjjmartin

repo: fourkitchens/sous-drupal-distro


text:
Bug in string->url of sack server

I've found a bug in Sack, the procedure string->uri is not handling empty values
example:

(string->uri "/foo?x=1&y=1")
#<uri #93 scheme: #f userinfo: #f host: #f port: #f path: "/foo" query: (("x" . "1") ("y" . "1")) fragment: #f>
(string->uri "/foo?x=1&y=")
Value: 0
Predicate: (lambda (len) (fx> len 0))
Reason: The input u8vector is not proper UTF-8.
*** ERROR IN #<procedure #94> -- Failed argument check in 'utf-u8vector->string
1>

the result is that the request hangs

Thank you @ovenpasta
This needs a fix. Having a couple of hectic weeks here. But I think a good way to start is to add a bunch of tests to sack. Spheres' libraries are ready for that next step at the moment.

the problem is with  (check-arg (lambda (len) (fx> len 0)) len 'utf-u8vector->string "The input u8vector is not proper UTF-8.")  in spheres/u8vector.scm.
a possible fix maybe allowing to have a (fx>= 0 len) vector (to me seems reasonable)
or fixing it in net/sack/url.scm like this:
diff --git a/spheres/net/sack/uri.scm b/spheres/net/sack/uri.scm
index 792856f..6ea5fc1 100644
--- a/spheres/net/sack/uri.scm
+++ b/spheres/net/sack/uri.scm
@@ -377,7 +377,9 @@
                   (loop (+ i 1)
                         (+ j 1)))))
           ;; result now contains the u8vector with the extracted bytes, so let's UTF8-decode them.
-          (utf8-u8vector->string result)))))
+          (if (fx> (u8vector-length result) 0)
+             (utf8-u8vector->string result)
+             "")))))

 ;; Extract a substring out of a URI / URI component string, depending on current decoding settings.
 ;;

I think this is the solution anyway :)
diff --git a/spheres/string/u8vector.scm b/spheres/string/u8vector.scm
index 71c0457..3147e87 100644
--- a/spheres/string/u8vector.scm
+++ b/spheres/string/u8vector.scm
@@ -139,7 +139,7 @@
1)))))))
;; It could be that we get a negative length because the string was very short and ended
;; with only the first 1-2 bytes of a 2-3 byte multibyte UTF-8 character.

(check-arg (lambda (len) (fx> len 0)) len 'utf-u8vector->string "The input u8vector is not proper UTF-8.")

(check-arg (lambda (len) (fx>= len 0)) len 'utf-u8vector->string "The input u8vector is not proper UTF-8.")
;; (print "output string length = " len " (u8vector length=" u8v-len ")\n")
;; Compiled with (declare (safe))
(let ((s (make-string len)))

Great! Can you open a PR please?

authors: alvatar ovenpasta

repo: fourthbit/spheres


text:
Update mdoc, sbt-mdoc to 2.5.3

About this PR
📦 Updates

org.scalameta:mdoc
org.scalameta:sbt-mdoc

from 2.5.0 to 2.5.3
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #446.


text:
hspec-wai 0.8.0

hspec-wai-0.8.0 (Simon Hengel sol@typeful.net @sol) is out of bounds for:

[ ] servant-mock-0.8.1.1 (< 0.8). Haskell Servant jkarni@gmail.com. @SoenkeHahn @jkarni

Stackage nightly builds will soon move to hspec-wai-0.8.0. The servant-mock test suite will be skipped until it is updated to hspec-wai-0.8.*.

authors: DanBurton bergmark

repo: fpco/stackage


text:
Add eventstore

eventstore-0.9.1.1 should fix stackage integration issue. Related to #1000

:+1: thanks for fixing that.

authors: DanBurton YoEight


text:
Follow Lint recommandation and Java best-practices

Wont be merged here

Add a "try/catch" block for "xxxxxx".
Add a default case to this switch.
Add a nested comment explaining why this method is empty, throw an UnsupportedOperationException or complete the implementation.
Add a private constructor to hide the implicit public one.
Add a type test to this method.
Add the missing @deprecated Javadoc tag.
Cast one of the operands of this multiplication operation to a "long".
Cast one of the operands of this subtraction operation to a "long".
Change "xxxxxx" to the type handled by the Collection.
Change this "try" to a try-with-resources.
Check the return value of the "skip" call to see how many bytes were read.
Combine this catch with the one at line 104, which has the same body.
Constructor has 9 parameters, which is greater than 7 authorized.
Convert this Map to an EnumMap.
Declare "xxxxxx" on a separate line.
Define a constant instead of duplicating this literal "xxxxxx" 4 times.
Define and throw a dedicated exception instead of using a generic one.
Description
Do something with the "boolean" value returned by "xxxxxx".
xxxxxx is already a string, there's no need to call "toString()" on it.
Extract this nested code block into a method.
Immediately return this expression instead of assigning it to the temporary variable "xxxxxx".
Introduce a new variable instead of reusing the parameter "startElement".
ldapAttrValue is already a string, there's no need to call "toString()" on it.
Make xxxxxx a static final constant or non-public and provide accessors if needed.
Make this "xxxxxx" field final.
Make this final field static too.
Make this member "protected".
Make xxxxxx a static final constant or non-public and provide accessors if needed.
Merge this if statement with the enclosing one.
Method has 10 parameters, which is greater than 7 authorized.
Move "ALL" to a class and lower its visibility
Move constants to a class or enum.
Move the array designator from the variable to the type.
Move this method into "OutputStream".
Move this method into the anonymous class declared at line xxx.
Null is returned but a "Boolean" is expected.
Override the "equals" method in this class.
Provide an override of "read(byte[],int,int)" for this class.
xxxxxx is already a string, there's no need to call "toString()" on it.
Reduce the total number of break and continue statements in this loop to use at most one.
Refactor this method to not always return the same value.
Refactor this method to reduce its Cognitive Complexity from 99 to the 15 allowed.
Refactor your code to get this URI from a customizable parameter.
Remove the "config" field and declare it as a local variable in the relevant methods.
Remove the "factory" field and declare it as a local variable in the relevant methods.
Remove the "logger" field and declare it as a local variable in the relevant methods.
Remove the "secondSelect" field and declare it as a local variable in the relevant methods.
Remove the "volatile" keyword from this field.
Remove the declaration of thrown exception 'java.io.IOException' which is a subclass of 'java.lang.Exception'.
Remove the declaration of thrown exception 'java.sql.SQLException', as it cannot be thrown from method's body.
Remove the declaration of thrown exception 'xxxxxx', as it cannot be thrown from method's body.
Remove the declaration of thrown exception 'xxxxxx' which is a runtime exception.
Remove the literal "false" boolean value.
Remove the literal "true" boolean value.
Remove the parentheses around the "assertionType" parameter
Remove this "clone" implementation; use a copy constructor or copy factory instead.
Remove this "String" constructor
Remove this array creation.
Remove this duplicated import.
Remove this empty class, write its code or make it an "interface".
Remove this empty statement.
Remove this method and declare a constant for this value.
Remove this method to simply inherit it.
Remove this redundant "static" qualifier.
Remove this redundant jump.
Remove this unnecessary cast to "Iterator".
Remove this unnecessary import: same package classes are always implicitly imported.
Remove this unnecessary null check; "instanceof" returns false for nulls.
Remove this unused "xxxxxx" local variable.
Remove this unused import 'xxxxxx'.
Remove this unused method parameter "xxxxxx".
Remove this unused private "xxxxxx" method.
Remove this use of "xxxxxx"; it is deprecated.
Remove this useless assignment to local variable "status".
Remove usage of generic wildcard type.
Remove useless curly braces around statement
Rename "xxxxxx" which hides the field declared at line xx.
Rename field "VERSION"
Rename method "decode" to prevent any misunderstanding/clash with field "DECODE" defined on line 164.
Rename this constant name to match the regular expression '^[A-Z][A-Z0-9](_[A-Z0-9]+)$'.
Rename this field "xxxxxx" to match the regular expression '^[a-z][a-zA-Z0-9]*$'.
Rename this generic name to match the regular expression '^[A-Z][0-9]?$'.
Rename this local variable to match the regular expression '^[a-z][a-zA-Z0-9]*$'.
Rename this method name to match the regular expression '^[a-z][a-zA-Z0-9]*$'.
Replace "Collections.EMPTY_LIST" by "Collections.emptyList()".
Replace "Collections.EMPTY_SET" by "Collections.emptySet()".
Replace charset name argument with StandardCharsets.UTF_xxx
Replace the type specification in this constructor call with the diamond operator ("<>").
Replace these toUpperCase()/toLowerCase() and equals() calls with a single equalsIgnoreCase() call.
Replace this use of System.out or System.err by a logger.
Return an empty array instead of null.
Swap these 2 arguments so they are in the correct order: expected value, actual value.
This block of commented-out lines of code should be removed.
This branch's code block is the same as the block for the branch on line 280.
Use the "equals" method if value comparison was intended.

Was not supposed to be merged


text:
Option to disable the need to use the Xbox streaming app

There are some cases where this would come in handy. For exemple: The PC port of Resident Evil: Revelations 2 has local splitscreen co-op, but only if both players use gamepads. The game ignores mouse input completely when this mode is active. Having the option to disable the foreground app check and the mouse lock/hide functions would be tremendous.

Should not be that hard, I'll create a option when I get up, as for now if you would like you can disable it your self in
https://github.com/fqlx/XboxKeyboardMouse/blob/84f6da191a96a08abb21d2d658835c3034eff3c6/XboxKeyboardMouse/XboxController/Emulation/XboxStream.cs

Awesome. Thank you!

It works perfectly with RE R2! I've also tried with GTA V, since it accepts both controller and keyboard at the same time. Working perfectly there as well.

authors: CallumCarmicheal brunibunny

repo: fqlx/XboxKeyboardMouse


text:
Grid randomizations

Wrote an example notebook to cleanly perform the first 2 steps of omics integration. Also added R visualization directly to the notebook.
Added grid search for randomization experiments. In fact, the new function _grid_randomization is a generalization of grid_search.

@iamjli this is looking quite nice. I think we're getting close to merging.

Thanks for the comments, @zfrenchee . There are a few functions in the example notebook that may belong in graph.py. Mind taking a look?

Seems to me like all three functions, summarize_grid_search, get_networkx_subgraph_from_randomizations, prune_network_graph all belong in graph.py.
But that would mean more back-and-forth. Are you alright with that?

Sorry it took so long to get back to you!

@zfrenchee I don't have write access.

authors: iamjli zfrenchee


text:
frames.js giving error on using this under scaffold-eth-project-2

what should be the folder structure and code I follow in that as scaffold-eth uses nextjs 14.0.4 there

Please provide minimum reproducible example.
Also here are:

examples https://github.com/framesjs/frames.js/tree/main/templates/next-starter-with-examples/app/examples/basic
fetchMetadata usage https://github.com/framesjs/frames.js/blob/84ccd1252312fc7a962b7eab497c0ed67c92a116/templates/next-starter-with-examples/app/examples/basic/page.tsx#L10

Also our library doesn't support nextjs 14.0.x and 14.2.x because of build caused by nxt, so make sure you are on 14.1.x.

Also here is a guide for nextjs https://framesjs.org/reference/core/next

I would recommend looking at the network requests - it's possible you have vercel authenticated deploys enabled for example


text:
🛑 SIU Guarani is down

In f395be9, SIU Guarani (https://siufai.uncoma.edu.ar/informatica) was down:

HTTP code: 500
Response time: 1963 ms

Resolved: SIU Guarani is back up in 1a33b78.


text:
🛑 Debian FAI is down

In eb849f4, Debian FAI (http://debianfai.fi.uncoma.edu.ar/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Debian FAI is back up in 8cddf8c after 1 hour, 13 minutes.


text:
Error No loader is configured for ".html" files: src/#foo/index.html

Hi, I have a problem when a directory be prefixed with # and in that directory contains .html files.
To reproduce, make a directory called #foo, create a file index.html in that directory, run pnpm dev, then you got this:
Error `No loader is configured for ".html" files: src/#foo/index.html`

I've tried the original vite template, works fine, not sure why...

@yaquawa I'm not even sure how Vite works with HTML files other than the root 🤔
How are you importing and using that file in your project? Or are you just moving your root file to a subfolder?

How are you importing and using that file in your project? Or are you just moving your root file to a subfolder?
I even didn't import it, if you removed the # prefix, it works... the directory be prefixed with # was generated by external libarary(amplify.js) and I can't change the name of it🤥

@yaquawa I could reproduce it but it also happens with pnpm dev:spa, which is using pure Vite internally without SSR. Also, it happens in the original vitesse template, which does not use vite-ssr.
Therefore, I think there's nothing we can do in this repo or even in vite-ssr.
The stack trace says it's esbuild, but it might be vite itself passing some configuration to the former. I've tried with the latest versions of these two dependencies, perhaps it actually worked in earlier versions, not sure 🤔

Thanks for reproducing! I could confirm that it also happens in the very original template(not the vitesse one) of vite.
strange.. I'm going to report this issue in the upstream repo.

that's because your whole dir include "#" ,just remove it and fixed ):

that's because your whole dir include "#" ,just remove it and fixed ):

this helped me, thankyou

@yaquawa Did you ever find a fix for this? I am also using Amplify and it generates a strange directory with '#'

@yaquawa I'm using Nuxt3 now.

authors: evilArsh frandiox inemtsev radonisme yaquawa

repo: frandiox/vitesse-ssr-template


text:
Sponsor links broken

Hi! I noticed that your sponsor links are broken in the README. It looks like maybe you changed your GitHub username but forgot to update your links. Also, the link to your GitHub page is broken on the JetBrains plugin site: https://plugins.jetbrains.com/vendor/523271e3-0c24-492c-93aa-e01e9a49ae7a

Thanks for the information, you are absolutely right. There I updated you =)

Nice! I don't see it yet but I will keep an eye out.


text:
fix(payments): separate redirect constructor from authorization hook

Reincarnation of frappe/erpnext#37502 for the same reasons
Sister PR: https://github.com/frappe/webshop/pull/36
This is a prerequisite for PayZen IPN implementation, potentially current IPN implementations harbor a slient bug.

@s-aga-r May you find some time to look at this and the companion in https://github.com/frappe/webshop/pull/36, this curreently "blocks" (I'm branching, but it gets ever more complex) me from migrating (and thus eventually contributing) PayZen.

@s-aga-r could we maybe, once again, discuss this change? Not merging appears to force me into maintaining an eternal fork, while the change itself seems reasonable and generic.

Superseded by https://github.com/frappe/payments/pull/53

repo: frappe/payments


text:
Fix #61: Link to blog post in README

This is a minimal fix for #61.
Of course, it would be great to link to real-world uses of this action.
But I don't know of these, so I delegate this to an expert.

Thanks!

authors: andreasabel pbrisbin

repo: freckle/stack-cache-action


text:
Prepare DBTrans class for dependency injection

TODO: Test to avoid exceptions

Implement a new interface IDBTrans
Ensure all callers are using the interface instead of the implementation class.
Instantiate DBTrans using try-with-resources.
Allow DBTrans to control the lifetime of its own SQL Connection, and to share the same connection (implicitly) across all methods
Remove connection parameter from all methods of IDBTrans.
Allow DBTrans.createDB to control the lifetime of its own SQL Statement, and remove it from the parameters.
Build fixes for gradle and IntelliJ IDEA on my system

Fred made incompatible changes to DBTrans, and besides, this is his project. I guess I got a little too excited. :-)


text:
chaining if else statements

Challenge Chaining If Else Statements has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

function testSize(num) {
  // Only change code below this line
  if (num<5)
    return "Tiny";
  else if(num<10)
    return "Small";
  else if(num<15)
    return "Medium";
    else if (num<20)
      return "Large";
     else if(num>=20)
       return "huge";

  // Only change code above this line
}

// Change this value to test
testSize(20);

my test size 20 and 25 both = huge when i run them, but its not passing me on those two factors

i figured it out, needed to capitalize "H" in huge

@cpereversoff: Please close the issue when you figure out what's wrong.

I intended to but I couldn't see how
On Sep 18, 2016 6:27 AM, "Ujjwal Sharma" notifications@github.com wrote:

@cpereversoff https://github.com/cpereversoff: Please close the issue
when you figure out what's wrong.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/10790#issuecomment-247847577,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVIVVnmKCLUjl-R-JG_4toLc_ESzMzK5ks5qrTxZgaJpZM4J_39D
.

@cpereversoff
Thanks for reporting this. But your code is incorrect.
GitHub Issues are for reporting bugs on the website only.
Please use the HelpJavaScript chat room for getting challenge related help.
Happy Coding.

just check your word's, what code you have written !!
Like :
Tiny - tiny
Small - small
WRIGHT CORRECTLY :)

authors: CoderBug Preeetrockz cpereversoff ryzokuken texas2010

repo: freeCodeCamp/freeCodeCamp


text:
TypeError: str.split(...).toLowerCase is not a function

Challenge Title Case a Sentence has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

function titleCase(str) {

  var i = 0;
  var s = str.split(' ').toLowerCase();

  while(i <= s.length) {

    s[i][0].toUpperCase();
    i++;
  }

  return s.join(' ');
}

titleCase("I'm a little tea pot");

Thanks @yorgos-dimitriadis
From the helpful link provided in the challenge for String.prototype.split:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/split

Return value
An array of strings split at each point where the separator occurs in the given string.

Please reach out to the Help Chat for further assistance.

This could help:
str.split() alternative


text:
Brazilian Portuguese translation of Basic HTML and HTML5

Pre-Submission Checklist

[x] Your pull request targets the staging branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[ ] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[x] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Closes currently open issue (replace XXXX with an issue no): Closes https://github.com/freeCodeCamp/TranslationExpansion/issues/92

Description

Adds Brazilian Portuguese translation of "Basic HTML and HTML5"

@nmdoliveira thanks for the pull request, would you mind tagging anyone who would be interested in a peer review?
Will merge if no one comes up in 7 days.

I asked @aferreira44 to review in the issue

Reviewed with the PR nmdoliveira/freeCodeCamp#1
Great job @nmdoliveira! I change just few things, not very important.

authors: aferreira44 nmdoliveira raisedadead


text:
Mentioned "Knowledge required for robotics"

[ x] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)
[x ] My pull request targets the master branch of freeCodeCamp.
[x ] None of my changes are plagiarized from another source without proper attribution.
[x ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Hi,
Thanks for this pull request (PR).
Unfortunately, we are marking this PR invalid for hacktoberfest. We believe it does not follow the recommended guidelines:

Quality Standards
In line with Hacktoberfest value #2 (Quantity is fun, Quality is key), we have provided examples of the quality standards we encourage. This applies mainly to beginners.

PRs that are automated e.g. scripted opening PRs to remove white space / optimize images.
PRs that are disruptive e.g. taking someone else's branch/commits and making a PR.
PRs that are regarded by a project maintainer as a hindrance vs. helping.
Something that's clearly an attempt to simply +1 your PR count for October.

Learn more at https://hacktoberfest.digitalocean.com/details


text:
added some info about System.out.printf() method

printf() method uses a stringbuilder wich is more efficient in memory

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@BrentWillems thanx for your contribution. We look forward to future pr's :balloon:

authors: BrentWillems nikrb


text:
Add the text "my changes" to  article

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


text:
book-recommendations - Books to Read on Linux

Added 4 books to read on Linux kernel

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

authors: RandellDawson prashantchikhalkar


text:
True and False  interpretion

How true and false is  interpreted by python.

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

@Sarvesh-yadav Please tick all the checkboxes to let us know that you've gone over them.

@Sarvesh-yadav Please fill out the checkboxes next time

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


text:
[Fix] Remove all book recommendations folders

[X ] I have read freeCodeCamp's contribution guidelines.
[X ] My pull request has a descriptive title (not a vague title like Update index.md)
[X ] My pull request targets the master branch of freeCodeCamp.
[X ] None of my changes are plagiarized from another source without proper attribution.
[X ] My article does not contain shortened URLs or affiliate links.

This PR removes all the book-recommendations folders currently in the guide folder for each language.

@RandellDawson Thanks for taking care of the removal of these.

authors: QuincyLarson RandellDawson


text:
chore(i18n): update German forum links

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

We do not have German on the forum yet.

Tag the PR as blocked instead of a change request, which is misleading?

Tag the PR as blocked instead of a change request, which is misleading?

Will do. I just did not because a label does not prevent the PR from being merged.

because a label does not prevent the PR from being merged.

If and when that happens, the maintainer is not paying attention and should not even be merging PRs, in the first place.

I have created https://forum.freecodecamp.org/c/german - but someone will need to create the actual sub-categories in there.

authors: Sboonny ShaunSHamilton raisedadead


text:
feat: add submodule tests

This adds five actions that run our tests using the submodule. They're identical to the existing tests of the same name except for two lines, the with: submodules: 'recursive' in the checkout source files step, and adding the BUILD_WITH_SUBMODULE=true env variable.
This also updates the submodule to the latest commit.
Adds the i18n-curriculum to prettierIgnore
And adds the english dictionary comments to the comment map in a different way. There was an issue with them not getting added after removing the English stuff from the i18n-curriculum repo.
With these tests, we should be confident to change our builds to use the submodule.
Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Do you think we can get this in as-is @naomi-lgbt, or do you still have some concerns? I'd really like to keep this moving. We can always add the actions to the other repo to validate the downloads at any time. This will still catch any issues with the download, just maybe a little later than is ideal.

And we need to run these on every PR? Sorry for being the squeaky wheel, but this is effectively doubling our already overburdened CI.

Yeah, that's right, but (hopefully) only briefly. The idea is that these will replace the existing workflows soon - once we're building using the i18n repo.
Also, if we see the CI building up, we can revert this this PR until the queue gets processed.

That's... not ideal. 🫤

True. How about this:

Create a second PR to delete the old workflows
Make sure pipeline changes are good to go (I think Tom may already be ready)
Merge this PR
Deploy straight after
Merge second PR

That should keep the action queue under control.

authors: moT01 naomi-lgbt ojeytonwilliams