no superclass method `google_maps_private_key'

Hello, when running ./scripts/create_dev_user I get the following error: "no superclass method `google_maps_private_key' for #User:0x007f194fd1ab18". However the error disappeared  after running the script again.
What is the source of the problem?

Hey @sabala12 make sure you have migrated your database before running the script.
Make sure you've run migrations at least up to db/migrate/20150609083856_add_google_maps_private_key_to_users_and_orgs.rb without any errors.

Thanks

Np! open this issue again if you have further questions


feat: extra pixels eraser

[x] issue #101
[x] follows contribution guide
[ ] code change includes tests
[ ] breaking change

This PR implements a feature for erasing extra pixels from the canvas

Thank you! Awesome feature!

Thank you!


Failing tests

Test Summary Report
-------------------
t/00-basic.t     (Wstat: 1280 Tests: 5 Failed: 5)
  Failed tests:  1-5
  Non-zero exit status: 5
  Parse errors: Bad plan.  You planned 16 tests but ran 5.
t/01-ordinal-en.t (Wstat: 3328 Tests: 13 Failed: 13)
  Failed tests:  1-13
  Non-zero exit status: 13
  Parse errors: No plan found in TAP output

The tests still fail. And looking at output, they fail to find json files that this distro stuffs into lib instead of using resources/
===> Testing: Lingua::Number:auth('github:labster')
Testing with plugin: Zef::Service::TAP+{<anon|75983168>}
t/00-basic.t ....... Dubious, test returned 1
No subtests run
t/01-ordinal-en.t .. Dubious, test returned 1
No subtests run
All tests successful.

Test Summary Report
-------------------
t/00-basic.t  (Wstat: 256 Tests: 0 Failed: 0)
Non-zero exit status: 1
  Parse errors: No plan found in TAP output
t/01-ordinal-en.t (Wstat: 256 Tests: 0 Failed: 0)
Non-zero exit status: 1
  Parse errors: No plan found in TAP output
Files=2, Tests=0,  1 wallclock secs
Result: FAILED
===> Testing [FAIL]: Lingua::Number:auth('github:labster')
Reporting with plugin: Zef::CPANReporter+{<anon|75983168>}
Encountered problems sending test report for Lingua::Number:auth('github:labster')

Use of uninitialized value of type Zef::CPANReporter in string context.
Methods .^name, .perl, .gist, or .say can be used to stringify it to something meaningful.
  in method report at /home/cpan/.rakudobrew/moar-nom/install/share/perl6/site/sources/643D88410EFE62A5D6F3C68A2811502A3DD01FF4 (Zef::CPANReporter) line 13
===SORRY!===
Failed to open file /home/cpan/.zef/store/p6-Lingua-Number.git/e7d8a7c848ea0cd7dac7a5d8756bf490507decd5/lib/Lingua/Number.pm (Lingua::Number)/digitformat.json: No such file or directory
===SORRY!===
Failed to open file /home/cpan/.zef/store/p6-Lingua-Number.git/e7d8a7c848ea0cd7dac7a5d8756bf490507decd5/lib/Lingua/Number.pm (Lingua::Number)/digitformat.json: No such file or directory
Use of uninitialized value of type Zef::CPANReporter in string context.
Methods .^name, .perl, .gist, or .say can be used to stringify it to something meaningful.
  in method report at /home/cpan/.rakudobrew/moar-nom/install/share/perl6/site/sources/643D88410EFE62A5D6F3C68A2811502A3DD01FF4 (Zef::CPANReporter) line 13
Aborting due to test failure: Lingua::Number:auth('github:labster') (use --force-test to override)
  in code  at /home/cpan/.rakudobrew/moar-nom/install/share/perl6/site/sources/5CBAAFEFAAB1740958A5BF3BCD5E24C04D43EEB5 (Zef::Client) line 373
  in method test at /home/cpan/.rakudobrew/moar-nom/install/share/perl6/site/sources/5CBAAFEFAAB1740958A5BF3BCD5E24C04D43EEB5 (Zef::Client) line 351
  in code  at /home/cpan/.rakudobrew/moar-nom/install/share/perl6/site/sources/5CBAAFEFAAB1740958A5BF3BCD5E24C04D43EEB5 (Zef::Client) line 528
  in sub  at /home/cpan/.rakudobrew/moar-nom/install/share/perl6/site/sources/5CBAAFEFAAB1740958A5BF3BCD5E24C04D43EEB5 (Zef::Client) line 525
  in method install at /home/cpan/.rakudobrew/moar-nom/install/share/perl6/site/sources/5CBAAFEFAAB1740958A5BF3BCD5E24C04D43EEB5 (Zef::Client) line 631
  in sub MAIN at /home/cpan/.rakudobrew/moar-nom/install/share/perl6/site/sources/EC4CB3A653760AFCB434D28800A3F559EA8634E0 (Zef::CLI) line 152
  in block <unit> at /home/cpan/.rakudobrew/moar-nom/install/share/perl6/site/resources/007D5E5A61B87BAA8B85A58771E235214AFADB77 line 1

Yeah, well, when I wrote it resources/ didn't actually exist.  And Panda was still the most adorable module installer.  Let's see if I can fix this now.

more failures today
===> Testing: Lingua::Number:auth<github:labster>
[Lingua::Number] # Failed test 'basically works in english'
[Lingua::Number] # at t/00-basic.t line 7
[Lingua::Number] # expected: 'three million one hundred twenty-three thousand four hundred fifty-six'
[Lingua::Number] #      got: '  million'
[Lingua::Number] # Failed test 'español también'
[Lingua::Number] # at t/00-basic.t line 8
[Lingua::Number] t/00-basic.t .......
[Lingua::Number] # expected: 'tres millones ciento veintitrés mil cuatrocientos cincuenta y seis'
[Lingua::Number] Dubious, test returned 5 (wstat 1280, 0x500)
[Lingua::Number] #      got: '  millones'
[Lingua::Number] Failed 5/5 subtests
[Lingua::Number] # Failed test 'also nihongo'
[Lingua::Number] # at t/00-basic.t line 9
[Lingua::Number] # expected: '三百十二万三千四百五十六'
[Lingua::Number] #      got: ' 万'
[Lingua::Number] # Failed test 'zero is okay'
[Lingua::Number] # at t/00-basic.t line 10
[Lingua::Number] # expected: 'zero'
[Lingua::Number] #      got: ''
[Lingua::Number] # Failed test 'english first'
[Lingua::Number] # at t/00-basic.t line 13
[Lingua::Number] # expected: 'five hundred sixty-seven point eight nine'
[Lingua::Number] #      got: '  hundred point  '
[Lingua::Number] Too few positionals passed; expected 2 arguments but got 1
[Lingua::Number]   in sub rule2text at /Volumes/BUKKIT/Users/coke/.zef/store/p6-Lingua-Number.git/8e95e557897804f6e7b379ceabb6411e37ea9c93/lib/Lingua/Number.pm6 (Lingua::Number) line 124
[Lingua::Number]   in block  at /Volumes/BUKKIT/Users/coke/.zef/store/p6-Lingua-Number.git/8e95e557897804f6e7b379ceabb6411e37ea9c93/lib/Lingua/Number.pm6 (Lingua::Number) line 103
[Lingua::Number] t/01-ordinal-en.t ..
[Lingua::Number]   in sub rule2text at /Volumes/BUKKIT/Users/coke/.zef/store/p6-Lingua-Number.git/8e95e557897804f6e7b379ceabb6411e37ea9c93/lib/Lingua/Number.pm6 (Lingua::Number) line 100
[Lingua::Number] Dubious, test returned 13 (wstat 3328, 0xd00)
[Lingua::Number]   in sub cardinal at /Volumes/BUKKIT/Users/coke/.zef/store/p6-Lingua-Number.git/8e95e557897804f6e7b379ceabb6411e37ea9c93/lib/Lingua/Number.pm6 (Lingua::Number) line 226
[Lingua::Number] Failed 13/13 subtests
[Lingua::Number]   in block <unit> at t/00-basic.t line 14
[Lingua::Number] Test Summary Report
[Lingua::Number] # Failed test '0 is zeroth'
[Lingua::Number] -------------------
[Lingua::Number] # at t/01-ordinal-en.t line 12
[Lingua::Number] t/00-basic.t     (Wstat: 1280 Tests: 5 Failed: 5)
[Lingua::Number] # expected: 'zeroth'
[Lingua::Number]   Failed tests:  1-5
[Lingua::Number] #      got: ''
[Lingua::Number]   Non-zero exit status: 5
[Lingua::Number] # Failed test '1 is first'
[Lingua::Number]   Parse errors: No plan found in TAP output
[Lingua::Number] # at t/01-ordinal-en.t line 13
[Lingua::Number] t/01-ordinal-en.t (Wstat: 3328 Tests: 13 Failed: 13)
[Lingua::Number] # expected: 'first'
[Lingua::Number]   Failed tests:  1-13
[Lingua::Number] #      got: ''
[Lingua::Number]   Non-zero exit status: 13
[Lingua::Number] # Failed test '2 is second'
[Lingua::Number]   Parse errors: No plan found in TAP output
[Lingua::Number] # at t/01-ordinal-en.t line 14
[Lingua::Number] Files=2, Tests=18, 15 wallclock secs ( 0.06 usr  0.02 sys + 16.40 cusr  1.49 csys = 17.97 CPU)
[Lingua::Number] # expected: 'second'
[Lingua::Number] Result: FAIL
[Lingua::Number] #      got: ''
[Lingua::Number] # Failed test '3 is third'
[Lingua::Number] # at t/01-ordinal-en.t line 15
[Lingua::Number] # expected: 'third'
[Lingua::Number] #      got: ''
[Lingua::Number] # Failed test '4 is fourth'
[Lingua::Number] # at t/01-ordinal-en.t line 16
[Lingua::Number] # expected: 'fourth'
[Lingua::Number] #      got: ''
[Lingua::Number] # Failed test '5 is fifth'
[Lingua::Number] # at t/01-ordinal-en.t line 17
[Lingua::Number] # expected: 'fifth'
[Lingua::Number] #      got: ''
[Lingua::Number] # Failed test '6 is sixth'
[Lingua::Number] # at t/01-ordinal-en.t line 18
[Lingua::Number] # expected: 'sixth'
[Lingua::Number] #      got: ''
[Lingua::Number] # Failed test '7 is seventh'
[Lingua::Number] # at t/01-ordinal-en.t line 19
[Lingua::Number] # expected: 'seventh'
[Lingua::Number] #      got: ''
[Lingua::Number] # Failed test '8 is eighth'
[Lingua::Number] # at t/01-ordinal-en.t line 20
[Lingua::Number] # expected: 'eighth'
[Lingua::Number] #      got: ''
[Lingua::Number] # Failed test '9 is ninth'
[Lingua::Number] # at t/01-ordinal-en.t line 21
[Lingua::Number] # expected: 'ninth'
[Lingua::Number] #      got: ''
[Lingua::Number] # Failed test '10 is tenth'
[Lingua::Number] # at t/01-ordinal-en.t line 24
[Lingua::Number] # expected: 'tenth'
[Lingua::Number] #      got: ''
[Lingua::Number] # Failed test '11 is elventh'
[Lingua::Number] # at t/01-ordinal-en.t line 25
[Lingua::Number] # expected: 'eleventh'
[Lingua::Number] #      got: ''
[Lingua::Number] # Failed test '12 is twelfth'
[Lingua::Number] # at t/01-ordinal-en.t line 26
[Lingua::Number] # expected: 'twelfth'
[Lingua::Number] #      got: ''

Now living as a Raku Community Module, awaiting someone to fix the breakage that apparently happened during the GLR


Inconsistent labeling for breaking change review

The labeling for breaking change review appears to be inconsistent between the internal azure-rest-api-specs-pr repo and the public azure-rest-api-specs repo.  PR 2300 in the public repo was flagged for breaking change review

as it should have been because the Swagger BreakingChange PR check failed -- found 7 errors.  But this PR was just applying changes already reviewed and approved in the internal repo in PR 9489 which targeted the RPSaaSMaster branch.

The Swagger BreakingChange check in PR 9489 also failed (in this case only 6 errors ... not sure why one is missing but that's not important) but the PR was never labeled BreakingChangeReviewRequired.

@mikekistler @weshaggard I think there is a chance this issue has since been fixed, because the validation of referenced PR seem to be old - the PR 9489 is from October 26, 2022, so almost 6 months ago. That PR has Swagger Generation Artifacts comment with SDK Breaking Change Tracking but the newer PRs have Swagger Validation Report with Breaking Change and Breaking Change(Cross-Version) as e.g. seen here.
I am assigning it medium priority because if this is still valid, then this seems to be nontrivial gap to me. However, @mikekistler I would be grateful if you would be able to find recent occurrence of this problem. If not, I will be on a lookout for it too. If I won't find anything in the next few weeks I will close this as "can't reproduce".

Can check with azp run if still an issue


docs: deprecate old alerts and dash/charts reports

SUMMARY
Deprecates the old alerts and reports feature

Adds deprecation comments to the config keys
Adds deprecation comments on the code modules
Adds deprecation log warnings when the feature is enabled
Adds a flash message on the MVC list for all the 3 views

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

@dpgaspar looks like this just needs a lint fix.


Migrated surrounding pair scope handler

Checklist

[x] I have added tests
[/] I have updated the docs and cheatsheet
[ ] I have not broken the cheatsheet
[ ] Add @disqualifyDelimiter for all languages
[ ] Add plural form of surrounding pair scopes.py

@pokey I'm not sure why all the scope provide tests are failing.

This is really interesting
if the file is over 30MB or over 300k lines, we consider it to be a very large file and proceed to turn off very many features, including tokenization, word wrapping, indent guides, anything that would consume additional memory, etc.

https://github.com/Microsoft/vscode/issues/32118#issuecomment-320952246
That means that Cursorless can never encounter a file with over three hundred thousand lines. I just did a test with the surrounding pair regex on a file with just below three hundred thousand lines and that clocked in at 274ms. I would say that is a bit on the high side so we might want to do some windowing, but we definitely don't need to be as careful as we was before. Doing it at tens of thousand lines at the time probably is fine.

is there a reason this is still marked as draft?

Yes the checkboxes in the description are not done. I wasn't sure this implementation was going to get your approval so I didn't go further originally.

Got it. So would it make sense to knock those out now that we're aligned on the high-level direction or did you want me to take a look first?

Please have a look first. Some of the implementation details I'm not sure off myself. The single line strings is one thing that come to mind.

@pokey That simplification looks great! :)

Ok I've now fully reviewed this PR. I made a bunch of changes. I think what remains are:

[ ] Review my changes to make sure you're happy
[ ] Finish the checkboxes in the description
[ ] Address my remaining unresolved comments, as well

Getting really close tho! Very excited to have this one

Ready for review. I have added @disqualifyDelimiter to all the languages that have boolean expressions to my knowledge.

@pokey I have now gone through all the grammar json files an added all the operators I can find that clashes. I might have missed something some of these files are quite long and complicated, but I done my best.

wow that disqualify stuff looks like it was a lot of work. Nice job. We should prob have some negative tests, ie that we're not disqualifying delimiters that we do want, but I think we have some tests for those and this PR is growing long in the tooth so I'd be happy to leave those for now.
As discussed, let's drive this for a couple days and then ship it

It was definitely some effort. We have a few tests. If anything comes to mind please record a few. Otherwise I would like to just get this in at the stage.
I've been running it for this entire day and except for the bug that was fixed earlier it has been working fine.

I wonder if we should make iteration scope be "line". I think being able to say "first string" / "last string" will be really useful

I wonder if we should make iteration scope be "line". I think being able to say "first string" / "last string" will be really useful

Why not?


HWKAPM-483 Fix JMS retry mechanism to avoid publishing retry messages…

… to all subscribers of a topic. This fix uses message selectors that initially will process messages not associated with a specific subscriber, but if a retry is triggered then the message will be published to the same topic, but with a 'subscriber' name to ensure only the appropriate subscriber processes the retried message

Review notes:

the event management mechanism works by passing around a batch of events to be processed, the ones that succeed (i.e. derive new events) and published on a new destination, but if any in the batch fail, they are resubmitted back to the source durable topic - based on a retry count. After the max retries, an error is reported.
issue with previous mechanism is that the resubmitted messages were simply being returned to the original topic, so if there are multiple durable subscribers, then each would get the resubmitted messages, instead of just the subscriber that suffered the failures - note when talking about durable subscribers here, they are the 'load balanced' subscribers supported by artemis, that enables a topic to be effectively treated like a queue, i.e. the source is a topic publisher, but multiple distinct (and load balanced) subscribers can be established.
so there are two solutions - (1) use a separate queue per retry requirement (or single queue with selectors), but this requires more destinations to be managed, or (2) use the same original topics, but leverage message selector to only return the retried message to the actual subscriber that requested the retry.
solution that has been implemented is (2) - potentially it results in a performance hit due to the use of selector, but from initial tests does not seem too bad

@jmazzitelli Hi Mazz  - would it be possible to take a quick look at this JMS related PR?

I did a brief review in the code and I did not find any obvious issue.
I am afraid I do not have proper background on the design.
Just one comment, message selectors are dependent of the implementation, so that means that on clustering scenarios or durable topics, selector may be applied only on memory messages (that happened in previous JMS implementations).
So, just in case that in future clustering scenarios that could affect on the desired behaviour.
Artemis is a new implementation and probably this does not affect to it, but just leaving a small note here.

So, LGTM unless anyone else has additional comments.

Thanks @lucasponce


Couldn't install Skype for Business 2019

How strange. I use the config xml to install Skype for Business 2019. Always failed. Could you take a look?
<Configuration>
<Add OfficeClientEdition="64">
<Product ID="Lync">
<Language ID="en-us" />
</Product>
</Add>
<Updates Enabled="TRUE" />
<Display AcceptEULA="TRUE" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>

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

ID: 95a0b1ff-0498-505a-6024-b813980d310f
Version Independent ID: b8057930-b4bd-1304-17ce-5561f837e901
Content: Configuration options for the Office Deployment Tool
Content Source: DeployOffice/configuration-options-for-the-office-2016-deployment-tool.md
Service: o365-proplus-itpro
GitHub Login: @jwhit-MSFT
Microsoft Alias: jwhit

I don't think Lync is the correct Product ID to use in your xml file.  Go to Product IDs that are supported by the Office Deployment Tool and scroll to the bottom of the article. That lists the IDs to use for Skype for Business 2019. Hope that helps.

Mr Bilyoungs  ,what error message you getting , will you please upload screenshot of error.
I think Lync.exe is aapplication and part of  office suites.
so you must include any one of the office suites as primary product id.
for example i used configured.xml included office2016pro plus with visio and project
products.
here is my configuration files
https://1drv.ms/u/s!AmZoRRusRV59lGktbjsyzDzQvWU0

@RAJU2529 -- you don't have to specify a suite as the product ID to get Skype for Business 2019 installed. Skype can be purchased and installed separately from Office. Since the original poster closed the issue, I'm presuming my answer solved his issue.


Add option to flatten JSON field

Hey,
In my Nova instance I needed dynamic fields so someone recommended me this package (awesome) The JSON field was exactly what I was looking for, however the one downside was that the fields were 'nested'
So I created a simple flatten method on the JSON field allowing fields to render at top level like regular fields. (mostly to see if I could)

By doing this you are able to put the fields in a Panel

Now I don't like the solution in the Vue template (duplicate data) but it does work.
Is this something that could be useful for other people as well? And do you have a nice solution for the template?
edit:
Usage:
new Panel('Settings', [
    Json::make('Settings', [
        Text::make('Information'),
        Number::make('Some number')
    ], 'settings')
        ->flatten()
]);

Cheers

Thank you! This is an awesome feature. Available in 0.7.0 🎉


Visualize deprecated operations

Hi
I've tried to mark some operations as deprecated like it's documented for operation objects. This option is not handled in ReDoc. Swagger UI rendered it with text-decoration: line-through.

Maybe we could add this too. What do you think?

+1

I faced similar needs, however, I have got deprecation on per field basis, not per operation. Also, deprecation style may require rendering of a note on what the alternative / new method which replaces the deprecated stuff.

+1
I'd be fine with a simple "Warning: Deprecated" text beneath the operation header, but before the description. I think the schema object ReDoc already supports this, so should just be a matter of passing it through the controller/view and agreeing on style/text to add.
I think the suggested/new operation to use (if applicable) would need to be in the operation description itself, since the deprecated field is just a boolean (though .


msdeploy not logging

Expected Behavior
Generate the zip file, in the end of the msdeploy, or show the error that avoid the generation of the package
Current Behavior
Not generation the zip file, but the process fail without errors; logs:
2018-12-10 02:10:26,471 [28] INFO  Amazon.AWSToolkit.VisualStudio.AWSToolkitPackage - ...building deployment package 'C:\Users\USER\AppData\Local\Temp\AWSDeploymentArchive_cartao-servidor_v20181210041008.zip'
2018-12-10 02:10:26,472 [28] INFO  Amazon.AWSToolkit.VisualStudio.Shared.VSWebProjectInfo - EnvDTEProject.FullName lookup yielded 'C:\Users\USER\Desktop\workspace\project-folder'
2018-12-10 02:10:26,474 [28] INFO  Amazon.AWSToolkit.VisualStudio.AWSToolkitPackage - ...probing to find msdeploy.exe
2018-12-10 02:10:26,474 [28] INFO  Amazon.AWSToolkit.VisualStudio.AWSToolkitPackage - ......inspecting registry path HKLM\SOFTWARE\Microsoft.NETFramework\AssemblyFolders\MSDeploy
2018-12-10 02:10:26,474 [28] INFO  Amazon.AWSToolkit.VisualStudio.AWSToolkitPackage - ...using msdeploy found at: C:\Program Files\IIS\Microsoft Web Deploy V3\msdeploy.exe
2018-12-10 02:10:26,474 [28] INFO  Amazon.AWSToolkit.VisualStudio.AWSToolkitPackage - ...invoking 'C:\Program Files\IIS\Microsoft Web Deploy V3\msdeploy.exe -verb:sync -source:manifest="C:\Users\vitor\AppData\Local\Temp\tmpADD8.tmp" -dest:package="C:\Users\vitor\AppData\Local\Temp\AWSDeploymentArchive_cartao-servidor_v20181210041008.zip" -declareParam:name="IIS Web Application Name",kind="ProviderPath",scope="IisApp",match="^C:\Users\vitor\Desktop\workspace\work\amef\cartao-servidor",defaultValue="Default Web Site/",tags=IisApp -declareParam:name="IIS Web Application Name",kind="ProviderPath",scope="setAcl",match="^C:\Users\vitor\Desktop\workspace\work\amef\cartao-servidor",tags=IisApp', working folder 'C:\Users\vitor\Desktop\workspace\project-folder'
2018-12-10 02:10:32,464 [28] INFO  Amazon.AWSToolkit.VisualStudio.AWSToolkitPackage - ...error, package 'C:\Users\USER\AppData\Local\Temp\AWSDeploymentArchive_cartao-servidor_v20181210041008.zip' could not be found
2018-12-10 02:10:32,464 [28] INFO  Amazon.AWSToolkit.MobileAnalytics.SimpleMobileAnalytics - Queuing analytics event in local queue with timestamp: 12/10/2018 04:10:32
2018-12-10 02:10:32,464 [26] INFO  Amazon.AWSToolkit.VisualStudio.AWSToolkitPackage - ..build of project archive failed, abandoning deployment
Possible Solution
Show the complete Output of the msdeploy command

Hi @vitorecomp, thank you for reporting this.  I am marking this issue as a feature-request for now, but we may change it to a bug as we investigate more.
Some customers report issues with loading credentials and profiles with IIS.  There isn't much in your logs to indicate this is the issue for you, but would you mind verifying that your credentials are loading properly?  If they're not, that would at least be a good starting place to try to get this deployment working for you.


schedule form updates

trello ticket
don't default schedule form to "now"
disable button until date and time are set

:+1:


Use the org.jboss.slf4j:slf4j-jboss-logmanager binding to allow slf4j…

… to bind to the jboss-logmanager
It looks like the Artemis server uses the JBoss Log Manager as it's log manager. Added a dependency to the slf4j binding to avoid the slf4j binding error.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

The org.jboss.slf4j:slf4j-jboss-logmanager library is under the Apache license.
The dependency may also be needed by any other executable that uses jboss-logmanager, including tests. I only added it to the distribution however for simplicity and to keep the change at a minimal.

It failed.  Not available on maven central :/

Weird. I never realized it was not synched. I'll look at getting it on Maven central. In a pinch using using org.slf4j:jul-to-slf4j may work.

@jamezp thanks a lot


chore: pull request template

Motivation
Pre-fill PR.
Changes

same template as in nns-dapp added

I am generally not a big fan of templates, as I have never seen it actually work in practice at DFINITY. When we used to have a template in the ic repo, most people just ignored it, or left parts of it blank, but no strong opinions here and won't object.

@ielashi we've got the exact same template in nns-dapp, since both projects are really closed and both get some PRs these days, I thought it makes sense to follow the same pattern.
if we notice it will be not used, I'll be happy to provide a PR to remove it.


Set appropriate default setting for kernel bytecode in D27 Dart sdk release

kernel bytecode is currently turned on by default in the Dart SDK and Flutter for the AOT pipeline but turned off in Google3 both in Dart SDK and Flutter.
It has not yet been turned on by default in the JIT pipeline.
For the D27 and Flutter 1.12 release this setting shoujld be consistent across both Dart SDK and Flutter.

bytecode has been turned off by default consistently in AOT/JIT and G3 for the D27 release
https://dart-review.googlesource.com/c/sdk/+/124469


[Storage] Fix documentation for start_copy_from_url

The documentation for start_copy_from_url() was specific to asynchronous copy and mentioned a return object that could be used to block until the operation was complete. I believe this was carried over from Track1 but is not accurate for Track2, especially now that synchronous copy has been added. Updating the documentation to discuss what is actually returned in sync/async case.
Resolves #23843

API change check for azure-storage-blob
API changes are not detected in this pull request for azure-storage-blob


Flow interface incorrectly determined to be undefined

Similar to #66 but for interfaces.
// @flow
interface Foo {
  m(): number;
}

export function f(foo: Foo): Foo {
  return foo;
}

$ npm ls babel-eslint
└──<EMAIL_ADDRESS>
$ node_modules/.bin/eslint foo.js

.../foo.js
  2:11  error  "Foo" is not defined  no-undef
  6:24  error  "Foo" is not defined  no-undef
  6:30  error  "Foo" is not defined  no-undef

✖ 3 problems (3 errors, 0 warnings)

Is there any news on that?

Until this is fixed, this workaround is available: https://github.com/zertosh/eslint-plugin-flow-vars

https://github.com/babel/babel-eslint#known-issues - This isn't really something we can fix because there are conflicts between no-undef and no-unused-vars. We recommend ^ like in the readme


Enrollment Complete plist/setting

This is not a problem with SYM but a feature that will make it better when integrating into Jamf/other MDM's. We ran into a problem where we use the Enrollment Complete trigger to launch SYM. When your MDM renews the MDM cert every 2 years, it can trigger another enrollment.
To remedy this on our end we took 2 measures. The first is to run the script only once at enrollment, we also have a custom plist to state the enrollment is complete into an EA.
it would be helpful if there was a native SYM component to complete this task.

… just leave a trail of breadcrumbs …


Release 0.5.2 on npm

The npm website still shows 0.5.1 as the latest release. https://www.npmjs.com/package/grunt-uncss
Please npm publish the 0.5.2 tag. https://github.com/addyosmani/grunt-uncss/releases/tag/v0.5.2

No need for a new issue. I have already pinged @addyosmani.


Hey I added DFS java program .

I hope this helps and thank you so much for this repository , this is my first time contributing to open source for hacktoberfest. Please do consider my contribution.

I've made all the changes. Can you please review if it's ok or not.

Thank you so much, it means a lot. Thank you for helping me out and for this repository. Learned a lot.


Fix MPU9250 compilation with Mahony / Madgwick enabled

Thank you TinyOra on Discord for pointing this out!

Hi DevMinerTV. Wondering if you can help. Have compiled with Mahony, but not getting any raw mag data (0,0,0). Does it require interrupt connected? Seems like gy-91 version of 9250 does not present this externally.

Make to that you have calibrated your IMU with the procedure described in the README. If you have any further questions, please ask in our Discord server.


Everytime when try to connect, get "Connection to dotnet was terminated (code: 0)" immediately and disconnect

Hi @ruidfigueiredo, thank for your great work. I'm new to electron. Trying to develop a combination with electron , angular and C#. I'm facing a issue everytime when electron run code below. I get "null", "lost", "Connection to dotnet was terminated (code: 0)" on my console log. And of course, there is no connections between electon & c# console. electron-cgi.log is created but the content is empty.
Any idea, why this issue happen? Any help would be greatful!
Electron side:
const { ConnectionBuilder } = require("electron-cgi");

  let connection = new ConnectionBuilder()
  .connectTo("dotnet", "run", "--project", "./core")
  .build();

connection.onDisconnect = () => {
  console.log("lost");
};

connection.send("greeting", "Jack", (response: any) => {
  console.log(response);
  connection.close();
});

C# console side:
static void Main(string[] args)
{
    var connection = new ConnectionBuilder()
    .WithLogging()
    .Build();

    connection.On<string, string>("greeting", name => "Hello " + name);

    connection.Listen();
}

Hey @KiloZak
The first argument for the send callback is the error (if any). That's why you see null, that's the error value (no error). Just change this line:
connection.send("greeting", "Jack", (response: any) => {
To:
connection.send("greeting", "Jack", (err: any, response: any) => {
And you'll see the message arriving successfully.
Also you can turn on trace logging (you'd be able to see the messages that were exchanged between node and dotnet in electroncgi.log this way): var connection = new ConnectionBuilder().WithLogging(minimumLogLevel: Microsoft.Extensions.Logging.LogLevel.Trace).Build();
Sometimes this helps to debug instances when something is off.


Why does it give bad certificates

Hello, evilgnix is working fine, everything goes as it should until the moment when I enter the phishing domain in the console with evil running, it gives this:
2021/02/12 18:43:56 [051] WARN: Cannot handshake client abs.twimg.com remote error: tls: bad certificate
2021/02/12 18:43:58 [054] WARN: Cannot handshake client abs.twimg.com remote error: tls: bad certificate
2021/02/12 18:43:58 [056] WARN: Cannot handshake client abs.twimg.com remote error: tls: bad certificate
2021/02/12 18:43:58 [055] WARN: Cannot handshake client abs.twimg.com remote error: tls: bad certificate
2021/02/12 18:43:58 [057] WARN: Cannot handshake client abs.twimg.com remote error: tls: bad certificate
2021/02/12 18:43:59 [058] WARN: Cannot handshake client abs.twimg.com remote error: tls: bad certificate
2021/02/12 18:44:00 [059] WARN: Cannot handshake client abs.twimg.com remote error: tls: bad certificate
2021/02/12 18:44:00 [060] WARN: Cannot handshake client abs.twimg.com remote error: tls: bad certificate
2021/02/12 18:44:00 [061] WARN: Cannot handshake client abs.twimg.com remote error: tls: bad certificate

im having this exact problem too. I think this happened after the new update

А как установить прошлую версию подскажи?

How to install the previous version, tell me?

im having this exact problem too. I think this happened after the new update

How to install the previous version, tell me?

im having this exact problem too. I think this happened after the new update

How to install the previous version, tell me?

wouldnt matter because im still having the same problem with the old version too lol

im having this exact problem too. I think this happened after the new update

How to install the previous version, tell me?

try connecting to a vpn and see if your page works

@kgretzky please help

@kgretzky please help

+++ I support

This is not a help desk or support portal.

This is not a help desk or support portal.

everything was working fine until the new update tho :(


Missing license

Please add license.

No license. My part is free to use for whatever you want to including commercial products. The low level methods are copy&paste from wikipedia, so i think they should be free as well.


Upgrade to mattermost 3.10.0

Mattermost official release day is 16th (10am San-Francisco time). I'll wait until a changelog entry (so in about 33 hours :wink: ) before merging, just to be sure there is no breaking changes or other modifications to do.


Contact details pattern examples

[ ] Add examples to storybook
[ ] Migration QA to StackOverflow

8 Dec - started working, examples being added to storybook

11 Dec - adding last variant

18 Dec - making changes based on PR feedback.

@bhoppers2008 asked me to pick up the site doc for this, cc @lukeac123 @dplsek

20 Dec - Reviewed and ready to merge.


Adds a Dogstatsd Tag Filter

What does this PR do?
Adds a filtering capability to the dogstatsd server that removes or modifies undesirable tags.
Motivation
Many statsd clients out there add undesirable tags to their metrics that result in inaccurate histograms and financial burden.  For example, some libraries add an extremely high cardinality tag called request_id.  Some libraries add UUID's into tag values.  Tags with empty string values also mess up the Datadog UI.   The use cases for this are plentiful.
Additional Notes
No.
Describe your test plan
Run the agent with:
DD_DOGSTATSD_TAG_FILTERS='[":$", "^undesirable_tag:", ":undesirable_value"]'

Hey Chris,
Thank you for this good PR.
That's indeed a solution for a few use-cases, especially since it's nearly free when not used (as you're just testing a nil pointer) 👌 .
I'm adding a couple labels and a milestone and we will look into this soon.

Anyone know if there a bot command or something to trigger a CI build run? I'd like to see the tests pass (works locally) and get docker image for the dogstatsd agent.

Could you eventually catch-up master? The AppVeyor issue should have been fixed in master, and that would trigger a CI run.

Hi @chrisleavoy, apologies for not reviewing your PR in time for 7.24. We are reviewing similar use cases internally to understand how to best address them. I'll update this PR in the next few weeks accordingly

Hi @olivielpeau , a few questions on this PR feature
does this only cover dogstatsd only?
if not, could it be extended / modified to cover metrics from any source eg. openmetrics?
It would be useful to link this PR to issues in the repo for metric tag filtering, which include
https://github.com/DataDog/datadog-agent/issues/13588 and
https://github.com/DataDog/datadog-agent/issues/3130
The last one has 10 teams requesting it and 66 'likes' currently.
This may provide a motivation to progress the feature request / and/or discussion on it.
Many thanks!

Are there any estimations when this feature can be released (or similar one)? It is a blocking issue for DataDog/Spark integration since by default DataDog includes even stageId/jobId into tags which leads to 10^5 custom metrics in real production environments.

Thank you for your pull request. While we appreciate your initiative, we're currently prioritizing caution and thoughtfulness in adding features to the Datadog agent to ensure optimal solutions for our users' needs.
As of now, we already have existing solutions to help customers safely remove tags from metrics while preserving mathematical accuracy of those metrics' queries.
We encourage you and our users to explore these existing options such as Metrics without Limits. For any further inquiries or specific needs, please reach out through our support channel (https://www.datadoghq.com/support/ ) or contact your Customer Success Manager (CSM).

As of now, we already have existing solutions to help customers safely remove tags from metrics while preserving mathematical accuracy of those metrics' queries.

Could you elaborate which kind of problems this would cause? Maybe the PR author could address them. #3130 has around a hundred thumbs-up. It seems like a quite important feature for many of us.


Schema stitching does not work with apollo server 2.0

A change that landed in apollo server 2.0 blocked sending parsed gql to /graphql
https://github.com/apollographql/apollo-server/pull/1097/files#diff-17f6f98b3651dd6b1ef91c515b0ff1daR530
graphql-tools is parsing the introspection query before sending it to the server which causes the endpoint to 400
https://github.com/apollographql/graphql-tools/blob/master/src/stitching/introspectSchema.ts#L7

Sending a parsed graphql-js AST instead of a query string to Apollo Server is definitely not a supported scenario, and worked before by accident. So this will have to be fixed in graphql-tools.

Is this because we're using apollo-fetch instead of apollo-link?
From what I can tell (I am not an expert), it looks like the latter will serialize/print a gql AST, while the former will not.

@martijnwalraven I've had a chance to play around with this, and can confirm that apollo-fetch never calls print on the parsed GraphQL AST that gets passed into it, and therefore (incorrectly) sends that that parsed introspection query the remote server.
I think you just need to remove the apollo-fetch example from your docs.  apollo-fetch is deprecated, and the subsequent node-fetch example actually calls print on the query, therefore resulting in the correct behavior.

Folded into #1316


getNext on pagingObject for PlaylistTracks failing

Thank you for creating such an awesome Spotify Client! There's a small issue with getNext being called on a pagingObject dealing with tracks fetched for a playlist. Spartan.getPlaylistTracks() works fine and loads 20 tracks. However after retrieving the pagingObject and calling getNext on it I get fatal error: unexpectedly found nil while unwrapping an Optional value 2017-07-09 19:55:16.220157-0500 Sink[12993:3968613] fatal error: unexpectedly found nil while unwrapping an Optional value. To confirm I called getNext right after fetching the pagingObject as follows ` let _ = Spartan.getPlaylistTracks(userId: userId, playlistId: playlistId, success: { (tracksPage) in
        if tracksPage.canMakeNextRequest {
            tracksPage.getNext(success: { (trackpage) in
                print("successfully fetched \(trackpage)")
            }, failure: { (error) in
                print(error.description)
                print(error.errorMessage)
            })
        }
         //completionHandler(tracksPage)
    }) { (error) in
        print(error.description)
        print(error.errorMessage)
    }

` and I get the error. I've also attached the stack trace below.
I am quite certain you'd be able to recreate the error if you fetch tracks for playlist that has number of songs over the the limit of 1 pagingObject and calling getNext on the pagingObject. Any fix or direction would be greatly appreciated!

Hi @kinshukJ! 😄 Thanks for providing such a detailed issue! I have fixed this in the v1.0.2 release! All you need to do is run pod update and you should be good to go! Thanks again! 👍

Thanks for such a speedy fix Daltron!

Hi Daltron, it doesn't give an error, however it doesn't load more tracks either. The paging object I get after calling getNext on it returns the same set of the first 20 tracks. Any direction or update would be much appreciated!

@kinshukJ I just tried to reproduce and am unable to. I have a playlist with a lot of tracks and getNext is returning the next set of tracks without any issues. Can you provide a code example that shows the error?

My bad Daltron. It was a thread issue. It's all fixed and working :). Thanks again!


AI-generated background music

Since AI-generated music is not amazing yet (and no easy+inexpensive APIs exist), I instead opted for randomly pulling music from freepd.com


Would you be against me releasing my fork on Modrinth?

I have recently forked this project such that I can add it to my Modrinth modpack.
Modrinth have quite strict rules, and I needed to patch the mod to remove noclip in order to add it to my modpack.
Now that it has been approved in my modpack, I am wondering if you would be against me uploading the patched fork to Modrinth as it's own project?
It will have a link to this original repo, and make it clear that the code was not written by me.

I have plans to do something similar in the future, so I would prefer you not upload it.

Sweet thx. I have updated my modpack accordingly.


Smoke test

Merge after #263
Fixes #242

If we schedule this, or something like it, to run regularly, we may want to make sure the traffic can be excluded in GA. If there something we can stuff in a header or something?


Workflows executions are getting stuck

Describe the bug
Workflow executions are getting stuck due to tasks taking too long to schedule.
Further debugging details:

In sweeper flow, If a task is in SCHEDULED state, the un-ack time is set as workflowTimeout if taskDefinition is not present. In other words the sweeper will now only sweep this workflow after workflowTimeout.
Note: I am not sure if we re-set the un-ack timeout once task moves from SCHEDULED to IN_PROGRESS
Now a workflow execution whenever reaches a state where it depends on sweeper to trigger the decide would remain stuck.

Details
Conductor version: 3.20.0
Persistence implementation: Postgres
Queue implementation: Dynoqueues
Lock: Redis
Workflow definition: N/A
Task definition: N/A
Event handler definition: N/A
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
Sweeper to continue sweeping a workflow once a task moves from SCHEDULED to IN_PROGRESS
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

I'd like to add some additional context to this issue.
As noted above,

In sweeper flow, If a task is in SCHEDULED state, the un-ack time is set as workflowTimeout if taskDefinition is not present.
In other words the sweeper will now only sweep this workflow after workflowTimeout.

This issue has been observed for async System Tasks, but could also occur for SIMPLE tasks if the timeouts are not set on the TaskDefinition but a timeout is set on the Workflow. These types of tasks do not transition from SCHEDULED to IN PROGRESS within a "decide", so the Sweep can pick them up in the SCHEDULED state.
Having a timely workflow sweep is critical in the cases where an execution lock cannot be obtained for some reason, as the decide is deliberately deferred to the sweep in this case. Furthermore, we have seen issues with the JOIN when it was set to synchronous as it does not trigger a decide when it completes (this was resolved when it was reverted to async).
It seems like there should be another setting "maxSweepDelay" to use as the fallback unack time, set either at the workflow level, system level or both.


replace long and repetitive sql queries

A number of queries could be more legible and debuggable as procedural sql. for example:
https://github.com/MetropolitanTransportationCommission/RegionalTransitDatabase/blob/master/sql/process/step_3_build_headway_am_pm_views.sql
https://github.com/MetropolitanTransportationCommission/RegionalTransitDatabase/blob/master/sql/process/step_5_insert_weekday_am_pm_headway_into_single_table.sql

this might be a more compact way to do this:
https://github.com/MetropolitanTransportationCommission/RegionalTransitDatabase/blob/master/etl/RTD Data Processing.R#L109-L171

closing this since we are doing this work in R now.


react-native依赖问题

"react-native": "0.38.0",should change the version of it top than 0.38.0, or it will build fail, and alert the following errors:
“SyntaxError: Strict mode does not allow function declarations in a lexically nested statement ”。
And can you give me the permission to create new branch(for example dev or bug branch;),so I can apply merge request.

You can fork it and request a pull request.

Just tested, I think I would update the version to 0.42.0.

ok，thanks


Assets Only Deferred Component not working at all

Steps to reproduce

pubspec.yaml

flutter:
  deferred-components:
    - name: gameAssets
      assets:
        - assets/images/animations/
        - assets/images/animations/guider/
    - name: gameAssets1
      assets:
        - assets/images/animations/magic/lw/
        - assets/images/animations/magic/lw/weapons/
    - name: gameAssets2
      assets:
        - assets/images/parallax/
        - assets/images/parallax/bg_7/

main.dart

await services.DeferredComponent.installDeferredComponent(componentName: "gameAssets");
await services.DeferredComponent.installDeferredComponent(componentName: "gameAssets1");
await services.DeferredComponent.installDeferredComponent(componentName: "gameAssets2");

Expected results
download assets success
Actual results
not working
Code sample
Code sample

pubspec.yaml

flutter:
  deferred-components:
    - name: gameAssets
      assets:
        - assets/images/animations/
        - assets/images/animations/guider/
    - name: gameAssets1
      assets:
        - assets/images/animations/magic/lw/
        - assets/images/animations/magic/lw/weapons/
    - name: gameAssets2
      assets:
        - assets/images/parallax/
        - assets/images/parallax/bg_7/

main.dart

await services.DeferredComponent.installDeferredComponent(componentName: "gameAssets");
await services.DeferredComponent.installDeferredComponent(componentName: "gameAssets1");
await services.DeferredComponent.installDeferredComponent(componentName: "gameAssets2");

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[Paste your output here]

Assets Only Deferred Component not working at all

Please describe how it's not working in detail. Does it have any symptoms (exception log or debugging info you can trace)?
Can you produce the issue locally? If it's possible, please provide a completed and minimal reproducible code sample that doesn’t include 3rd party plugins or complex production code. Also, please provide the output of flutter doctor -v as well. Thank you!

sorry it is working now.
Kind regards,
Hejun Deng
在 2024年7月8日，16:16，Huy @.***> 写道：

Assets Only Deferred Component not working at all
Please describe how it's not working in detail. Does it have any symptoms (exception log or debugging info you can trace)?
Can you produce the issue locally? If it's possible, please provide a completed and minimal reproducible code samplehttps://stackoverflow.com/help/minimal-reproducible-example that doesn’t include 3rd party plugins or complex production code. Also, please provide the output of flutter doctor -v as well. Thank you!
—
Reply to this email directly, view it on GitHubhttps://github.com/flutter/flutter/issues/151368#issuecomment-2213329641, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAQEJ7YOBXOG6N3PAGYOH3ZLJDEBAVCNFSM6AAAAABKOKOE4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJTGMZDSNRUGE.
You are receiving this because you authored the thread.Message ID: @.***>

Closing the issue as it doesn't persist.


Can no longer build hlint

With the 0.8 release of ansi, I'm having issues while building sbv via cabal:

CallStack (from HasCallStack):
die', called at ./Distribution/Client/Install.hs:240:21 in main:Distribution.Client.Install
cabal: Could not resolve dependencies:
trying: ansi-terminal-0.8 (dependency of hlint-2.0.12)
trying: optparse-applicative-<IP_ADDRESS> (dependency of tasty-golden-<IP_ADDRESS>)
next goal: ansi-wl-pprint (dependency of optparse-applicative-<IP_ADDRESS>)
rejecting: ansi-wl-pprint-<IP_ADDRESS> (conflict: ansi-terminal==0.8,
ansi-wl-pprint => ansi-terminal>=0.4.0 && <0.8)
rejecting: ansi-wl-pprint-0.6.8, ansi-wl-pprint-<IP_ADDRESS>,
ansi-wl-pprint-<IP_ADDRESS>, ansi-wl-pprint-<IP_ADDRESS>, ansi-wl-pprint-0.6.7,
ansi-wl-pprint-0.6.6 (conflict: ansi-terminal==0.8, ansi-wl-pprint =>
ansi-terminal>=0.4.0 && <0.7)
rejecting: ansi-wl-pprint-0.6.4, ansi-wl-pprint-0.6.3, ansi-wl-pprint-0.6.2,
ansi-wl-pprint-0.6.1, ansi-wl-pprint-0.5.1, ansi-wl-pprint-0.5.0,
ansi-wl-pprint-0.4.0, ansi-wl-pprint-0.3.1, ansi-wl-pprint-0.3.0,
ansi-wl-pprint-0.2, ansi-wl-pprint-0.1 (conflict: optparse-applicative =>
ansi-wl-pprint>=0.6.6 && <0.7)
Backjump limit reached (currently 2000, change with --max-backjumps or try to
run with --reorder-goals).

Full logs here: https://travis-ci.org/LeventErkok/sbv/jobs/321887094
This is hard to interpret, but looking through the only change is a new release of ansi. Any help how I should go about fixing this would be great!

Well, ansi-wl-pprint puts an arbitrary upper bound on ansi-terminal, and for some reason Cabal doesn't get around to trying older versions of ansi-terminal.
Have you tried the flags suggested at the end of that output?

No, I haven't. This is all CI builds, so I'm messing with flags is neither easy nor desirable. Perhaps we should ping ansi-wl-pprint folks to remove the upper bound?

Just filed: https://github.com/ekmett/ansi-wl-pprint/issues/17


Pre-Ico Tiers from White list

Organiser performs KYC data collection with the White-List from the crowd before starting private Pre-Ico-Tier and pick up a group from the crowd who meet the requirements (could be > 2000 people) to set up Tiers (1, 2 or 3 pre-ico tiers with different params).
Selected group get the private link to the private Pre-ICO-Tier with specified by organiser params of the Tier:
– hard cap;
– min / max check for one investor;
– dates;
– discount.

Added to Whitelist with cap


Ask hidden for admin password

1. Why is this change necessary?
Asking for admin-password should use the recommended mehtod by symfony for asking for sensitive data. - search for askHidden()
2. What does this change do, exactly?
the admin-password for a Admin-User created through bin/console sw:admin:create will now don't show the password typed by the user, but hide it from all eyes. The user will have to confirm his password to avoid saving passwords with typos
3. Describe each step to reproduce the issue or behaviour.
create a admin-user through the sw:admin:create-command and follow the steps. When typing your password you - and everyone else who is maybe passing by - will see the typed password
4. Please link to the relevant issues (if any).
found none
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[x] I have written tests and verified that they fail without my change <-- No tests for Commands could be found, but the build.xml was changed where the admin:create-Command is used
[x] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

WHY IS THIS CHANGE NECESSARY?

Asking for admin-password should use the recommended mehtod by symfony
for https://symfony.com/doc/2.8/console/style
    @import url("https://magento.21w.pl/pub/static/version1528704381/frontend/Wm21/light/pl_PL/css/email-fonts.css");

/*#f4f4f4; */
html {
font-size: 62.5%;
-webkit-text-size-adjust: 100%;
-ms-text-size-adjust: 100%;
font-size-adjust: 100%;
}
body {
color: #333333;
font-family: 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif;
font-style: normal;
font-weight: 400;
line-height: 1.42857143;
font-size: 14px;
}
p {
margin-top: 0;
margin-bottom: 10px;
}
abbr[title] {
border-bottom: 1px dotted #cccccc;
cursor: help;
}
b,
strong {
font-weight: 700;
}
em,
i {
font-style: italic;
}
mark {
background: #f6f6f6;
color: #000000;
}
small,
.small {
font-size: 12px;
}
hr {
border: 0;
border-top: 1px solid #cccccc;
margin-bottom: 20px;
margin-top: 20px;
}
sub,
sup {
font-size: 71.42857143000001%;
line-height: 0;
position: relative;
vertical-align: baseline;
}
sup {
top: -.5em;
}
sub {
bottom: -.25em;
}
dfn {
font-style: italic;
}
h1 {
font-weight: 300;
line-height: 1.1;
font-size: 26px;
margin-top: 0;
margin-bottom: 20px;
}
h2 {
font-weight: 300;
line-height: 1.1;
font-size: 26px;
margin-top: 25px;
margin-bottom: 20px;
}
h3 {
font-weight: 300;
line-height: 1.1;
font-size: 18px;
margin-top: 20px;
margin-bottom: 10px;
}
h4 {
font-weight: 700;
line-height: 1.1;
font-size: 14px;
margin-top: 20px;
margin-bottom: 20px;
}
h5 {
font-weight: 700;
line-height: 1.1;
font-size: 12px;
margin-top: 20px;
margin-bottom: 20px;
}
h6 {
font-weight: 700;
line-height: 1.1;
font-size: 10px;
margin-top: 20px;
margin-bottom: 20px;
}
h1 small,
h2 small,
h3 small,
h4 small,
h5 small,
h6 small,
h1 .small,
h2 .small,
h3 .small,
h4 .small,
h5 .small,
h6 .small {
color: #333333;
font-family: 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif;
font-style: normal;
font-weight: 400;
line-height: 1;
}
a,
.alink {
color: #232323;
text-decoration: none;
}
a:visited,
.alink:visited {
color: #232323;
text-decoration: none;
}
a:hover,
.alink:hover {
color: #232323;
text-decoration: underline;
}
a:active,
.alink:active {
color: #ff5501;
text-decoration: underline;
}
ul,
ol {
margin-top: 0;
margin-bottom: 25px;
}
ul > li,
ol > li {
margin-top: 0;
margin-bottom: 10px;
}
ul ul,
ol ul,
ul ol,
ol ol {
margin-bottom: 0;
}
dl {
margin-bottom: 20px;
margin-top: 0;
}
dt {
font-weight: 700;
margin-bottom: 5px;
margin-top: 0;
}
dd {
margin-bottom: 10px;
margin-top: 0;
margin-left: 0;
}
code,
kbd,
pre,
samp {
font-family: Menlo, Monaco, Consolas, 'Courier New', monospace;
}
code {
background: #f6f6f6;
color: #111111;
padding: 2px 4px;
font-size: 12px;
white-space: nowrap;
}
kbd {
background: #f6f6f6;
color: #111111;
padding: 2px 4px;
font-size: 12px;
}
pre {
background: #f6f6f6;
border: 1px solid #cccccc;
color: #111111;
line-height: 1.42857143;
margin: 0 0 10px;
padding: 10px;
font-size: 12px;
display: block;
word-wrap: break-word;
}
pre code {
background-color: transparent;
border-radius: 0;
color: inherit;
font-size: inherit;
padding: 0;
white-space: pre-wrap;
}
blockquote {
border-left: 0 solid #cccccc;
margin: 0 0 20px 40px;
padding: 0;
color: #333333;
font-family: 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif;
font-style: italic;
font-weight: 400;
line-height: 1.42857143;
font-size: 14px;
}
blockquote p:last-child,
blockquote ul:last-child,
blockquote ol:last-child {
margin-bottom: 0;
}
blockquote footer,
blockquote small,
blockquote .small {
color: #333333;
line-height: 1.42857143;
font-size: 10px;
display: block;
}
blockquote footer:before,
blockquote small:before,
blockquote .small:before {
content: '\2014 \00A0';
}
blockquote cite {
font-style: normal;
}
blockquote:before,
blockquote:after {
content: '';
}
q {
quotes: none;
}
q:before,
q:after {
content: '';
content: none;
}
cite {
font-style: normal;
}
.shipment-track th {
text-align: left;
}
.shipment-track > tbody > tr > th,
.shipment-track > tfoot > tr > th,
.shipment-track > tbody > tr > td,
.shipment-track > tfoot > tr > td {
vertical-align: top;
}
.shipment-track > thead > tr > th,
.shipment-track > thead > tr > td {
vertical-align: bottom;
}
.shipment-track > thead > tr > th,
.shipment-track > tbody > tr > th,
.shipment-track > tfoot > tr > th,
.shipment-track > thead > tr > td,
.shipment-track > tbody > tr > td,
.shipment-track > tfoot > tr > td {
padding: 0 10px;
}
.email-items th {
text-align: left;
}
.email-items > tbody > tr > th,
.email-items > tfoot > tr > th,
.email-items > tbody > tr > td,
.email-items > tfoot > tr > td {
vertical-align: top;
}
.email-items > thead > tr > th,
.email-items > thead > tr > td {
vertical-align: bottom;
}
.email-items > thead > tr > th,
.email-items > tbody > tr > th,
.email-items > tfoot > tr > th,
.email-items > thead > tr > td,
.email-items > tbody > tr > td,
.email-items > tfoot > tr > td {
padding: 0 10px;
}
@media only screen and (max-width: 479px) {
.header,
.main-content,
.footer {
padding: 25px 10px !important;
}
.footer td {
display: block;
width: auto !important;
}
.email-features > tbody > tr > td {
clear: both;
display: block;
padding-top: 20px;
width: auto !important;
}
.email-summary h1 {
font-size: 24px !important;
}
.order-details .address-details,
.order-details .method-info {
display: block;
padding: 10px 0 !important;
width: auto !important;
}
.order-details .address-details h3,
.order-details .method-info h3 {
margin-bottom: 5px !important;
margin-top: 0 !important;
}
.button .inner-wrapper {
width: 100% !important;
}
.button .inner-wrapper td a {
font-size: 16px;
}
}
@media only screen and (max-width: 639px) {
html,
body {
background-color: #ffffff;
width: 100% !important;
}
.main {
max-width: 100% !important;
min-width: 240px;
width: auto !important;
}
.rma-items td,
.rma-items th {
font-size: 12px !important;
padding: 5px !important;
}
}
body,
table,
td,
a {
-ms-text-size-adjust: 100%;
-webkit-text-size-adjust: 100%;
}
img {
-ms-interpolation-mode: bicubic;
}
table,
td {
mso-table-lspace: 0pt;
mso-table-rspace: 0pt;
}
a:visited {
color: #232323 !important;
text-decoration: none !important;
}
a:hover {
color: #232323 !important;
text-decoration: underline !important;
}
a:active {
color: #ff5501 !important;
text-decoration: underline !important;
}
.no-link a,
.address-details a {
color: #333333 !important;
cursor: default !important;
text-decoration: none !important;
}
.button .inner-wrapper td:hover {
background-color: #fc5e10 !important;
}
.button .inner-wrapper a:active,
.button .inner-wrapper td:active {
background-color: #232323 !important;
}
.button a:active,
.button a:hover,
.button a:visited {
border: 1px solid #fc5e10;
color: #ffffff !important;
text-decoration: none !important;
}
.email-items {
overflow-x: auto;
overflow-y: hidden;
width: 100%;
-ms-overflow-style: -ms-autohiding-scrollbar;
-webkit-overflow-scrolling: touch;
}
##- please type your reply above this line -##
        Dear shopware/shopware,
        Dziękujemy za skontaktowanie się z nami!

        This is an automated response confirming the receipt of your ticket. One of our agents will get
            back to you
            as soon as possible.

                Nr zadania
                MGU-406-27244

                Temat
                [shopware/shopware] Ask hidden for admin password (#1675)

                Dział
                CEO

                Status
                Nowe zadanie

                Priorytet
                Low

                Wiadomość
                1. WHY IS THIS CHANGE NECESSARY?

Asking for admin-password should use the recommended mehtod by symfony
for https://symfony.com/doc/2.8/console/style.html

WHAT DOES THIS CHANGE DO, EXACTLY?

the admin-password for a Admin-User created through bin/console
sw:admin:create will now don't show the password typed by the user,
but hide it from all eyes. The user will have to confirm his password
to avoid saving passwords with typos

DESCRIBE EACH STEP TO REPRODUCE THE ISSUE OR BEHAVIOUR.

create a admin-user through the sw:admin:create-command and follow the
steps. When typing your password you - and everyone else who is maybe
passing by - will see the typed password

PLEASE LINK TO THE RELEVANT ISSUES (IF ANY).

found none

WHICH DOCUMENTATION CHANGES (IF ANY) NEED TO BE MADE BECAUSE OF
THIS PR?

CHECKLIST

I have written tests and verified that they fail without my change
<-- No tests for Commands could be found, but the build.xml was
changed where the admin:create-Command is used
I have squashed any insignificant commits
This change has comments for package types, values, functions, and
non-obvious lines of code
I have read the contribution requirements and fulfil them.

YOU CAN VIEW, COMMENT ON, OR MERGE THIS PULL REQUEST ONLINE AT:
https://github.com/shopware/shopware/pull/1675
COMMIT SUMMARY

added method for asking for sensitive data
ask for the password twice to ensure the correct password is saved,
because user will now not see the chosen password

FILE CHANGES

M https://github.com/shopware/shopware/pull/1675/files#diff-0 (1)
M https://github.com/shopware/shopware/pull/1675/files#diff-1 (1)
M https://github.com/shopware/shopware/pull/1675/files#diff-2 (43)

PATCH LINKS:

https://github.com/shopware/shopware/pull/1675.patch
https://github.com/shopware/shopware/pull/1675.diff

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly,
https://github.com/shopware/shopware/pull/1675, or
https://github.com/notifications/unsubscribe-auth/ATq1jOmKGY2WdZcJbtliN5jWTE3LVF4fks5t7my6gaJpZM4Uiqx3.
        Możesz sprawdzić status odpowiedzi na to zadanie online na stronie:
            https://magento.21w.pl/helpdesk/ticket/external/id/7cecb5c07ad373ab2cf71e81fbee41d7/

                                         +48 608012047

                                        Godziny pracy: 9:00 - 18:00.

                                    21w.pl

Dobrzechów 509
Strzyżów,  38-100,
Polska

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-21937
Please use this issue to track the state of your pull request.

I kinda don't like that both options --password and --password-confirm are required. If I have some script that automatically creates backend-users using the --no-interaction-flag, I'd have to pass the same password twice. Is there a way to make password-confirm mandatory when interacting through stdin, but optional as command line option?

@oktupol Yeah, I can think about that. But for now I have no idea how to achieve that. In a script I would probably solve this by assigning the password to a variable or an environment-variable and bind it to the command-line parameters...

Hey @solutionDrive-Alt,
can you just remove the password-confirm function again?
While we understand why you implemented this change in the first place, this would also lead to BC breaks and comes with several other issues.
Just leave the "password hidden" functionality in there, that's a nice addition.

@solutionDrive-Alt Still working on it?

At the moment, I don't have the time. I try to get this done this week though. But I think removing the password-confirm - option will lead to other issues, like I can not log into admin or something like that..

Hey @solutionDrive-Alt,
in this case one could simply create a new user, shouldn't be too much of an issue.

This PR was closed due to inactivity. If this change is still important to you, feel free to create a new pull request.
For more information about our contribution guidelines, see https://developers.shopware.com/contributing/contribution-guideline/.


Feat(Revit) : load missing types on receive

Description & motivation

Changes:

added elementTypeMapper class whose job is to either create or update a type map between incoming "types" and element types that exist in the project

The TypeMap's job is just to store the data

added familyImporter class whose job is to walk the user through importing family symbols into the active project
created interfaces IHostTypeAsStringContainer and ITypeMap that get passed to the DUI viewModel and allow DUI to access the data that is in the document
created IRevitElementTypeRetriever and implemented it on the converter. This allows the connector to pass objects to the converter and allows the converter (who knows about Objects) to query the objects for their types. It also exposes a couple element type retreival methods that cache the retrieved values in a new cache class
create ElementTypeInfo class to consolidate a bit of information about different categories and IElementTypeInfoExposer to let the converter expose that category info to the mapper (in the connector)
created new missingIncomingType dialog that pops up by default when there are incoming types that don't exist in the project
created conversionCache object to store elementTypes (and eventually other things) during mapping so we can retrieve them faster during conversion
deleted a lot of old code that did the same thing but worse

Screenshots:

Validation of changes:
manual sending and receiving. The tests project is no longer in the speckle sharp repo so we'll definitely need to figure out what to do about that and run / create some tests

Checklist:

[x] My pull request follows the guidelines in the Contributing guide?
[x] My pull request does not duplicate any other open Pull Requests for the same update/change?
[x] My commits are related to the pull request and do not amend unrelated code or documentation.
[x] My code follows a similar style to existing code.
[ ] I have added appropriate tests.
[ ] I have updated or added relevant documentation.

References
https://github.com/specklesystems/speckle-sharp/issues/1240

As discussed on discord, we need to ensure that loadable family instances are supported too. Since the family name is missing from the UI it could be confusing for the user to know what is missing and what to map to (some families of the same category would have the same type name eg window1-50x100cm, window2-50x100cm).


add pubsub redis config docs

Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:

[x] Read the contribution guide
[ ] Commands include options for Linux, MacOS, and Windows within codetabs
[ ] New file and folder names are globally unique
[ ] Page references use shortcodes instead of markdown or URL links
[ ] Images use HTML style and have alternative text
[ ] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description
add some config that can be set from metadata for redis client.
Issue reference

@Taction Please create a docs issue and link this PR to that ...

@Taction - since the relevant feature is going in v1.2 (not the upcoming v1.1) I rebased the PR so it is merged to the v1.2 docs branch


[BUG] cannot restore session using Autosession search

Describe the bug
When opening nvim and trying to restore session using Autosession search, nothing happened, the session was not restored.
To Reproduce
Steps to reproduce the behavior:

Open nvim
Open a file
In command mode, enter Autosession search and select session number
Press enter, nothing happens.

Expected behavior
The expected session should be restored.
Screenshots
Baseline (please complete the following information):

Result of set sessionoptions?:
sessionoptions=blank,buffers,curdir,folds,help,tabpages,winsize,winpos,terminal,localoptions
OS. e.g uname -a:
Darwin K1F6JWK7KT 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:49 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6020 arm64
Neovim version nvim --version
NVIM v0.9.5
Build type: Release
LuaJIT 2.1.1692716794
URL to your current config (if public)
https://github.com/swahpy/dotfiles/blob/main/.config/nvim/lua/plugins/auto-session.lua

Additional context
I can delete session using Autosession delete.

The Autosession search command is using vim.ui.select version of session switching (for those who don't have Telescope).
local function open_picker(files, prompt, callback)
  vim.ui.select(files, {
    prompt = prompt,
    kind = "auto-session",
    format_item = function(item)
      return item.display_name
    end,
  }, function(choice)
    if choice then
      callback(choice)
    end
  end)
end

The issue is that this is merely changing the cwd, which means the CwdChangeHandling feature needs to be set for session switching to happen.
local function handle_autosession_command(data)
  local files = AutoSession.get_session_files()
  if data.args:match "search" then
    open_picker(files, "Select a session:", function(choice)
      -- Change dir to selected session path, the DirChangePre and DirChange events will take care of the rest
      vim.fn.chdir(choice.display_name)
    end)
  elseif data.args:match "delete" then
    open_picker(files, "Delete a session:", function(choice)
      AutoSession.DeleteSessionByName(choice.display_name)
    end)
  end
end

If you're using Telescope.nvim you can just call require("auto-session.session-lens").search_session() which currently does more handling.
The picker callback should be able to call the same behaviour that the telescope based handlers do, this is a bug indeed 👍

Hi @rmagatti, thank you for your reply. Yes I can implement the same functionality using require("auto-session.session-lens").search_session(). That's great!


plumbing: use LookPath instead of Stat to fix Windows executables

When git-core isn't in the user's PATH, we need to use LookPath to
verify the existence of the executable, rather than os.Stat, so that
on Windows it will search for files with executable suffixes.

@mcuadros @erizocosmico this is ready for review/merge too, if you get the chance.  The file transport protocol is currently broken on Windows without this.


BREAKING CHANGE(lib): Use u64 for Printer::display_offset and Squeezer::process, not usize

Soft dependency on #93.
Technically a breaking change for architectures where size_of::<usize>() > size_of::<u64>(), but that strikes me as extremely unlikely.
This change is important because most file seek offsets, even on older architectures with word sizes smaller than u32, accept a u64. In particular, Rust's own std acknowledges this. So, we're actually going against prior art in Rust by using a usize.

Closing, as all changes have been merged with #95


Create a "markdownlint" binary that's invokable as a shell command

A markdownlint binary that,

with no parameters runs on all markdown files found recursively from the current folder
chooses the set of files to run against based on parameters
Recognises and uses .markdown.(json|yaml), if it's present

There is already a CLI project mentioned in the README https://github.com/igorshubovych/markdownlint-cli

I link to markdownlint-cli at the top of the README - I think that does everything you want?
https://github.com/igorshubovych/markdownlint-cli

Didn't realize there was another tool. I was expecting it as part of the same repo.
That satisfies what I'm looking for. Thanks!


Fix Visual Studio proj files

Due to moving tests.

Codecov Report

Merging #3854 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3854   +/-   ##
=======================================
  Coverage   70.94%   70.94%
=======================================
  Files         426      426
  Lines       26910    26910
  Branches     4095     4095
=======================================
  Hits        19092    19092
- Misses       6575     6578    +3
+ Partials     1243     1240    -3

Impacted Files
Coverage Δ

src/azure-cli-core/azure/cli/core/util.py
70.06% <0%> (ø)
:arrow_up:

...dback/azure/cli/command_modules/feedback/custom.py
31.25% <0%> (ø)
:arrow_up:

...nent/azure/cli/command_modules/component/custom.py
16.23% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


A few questions on your Plugin please!

Hello, I've searching like a mad woman for markdown support in Explorer preview pane (and all other softwares that use the same pane).
I coud not get your software to work sadly but you was kind enough to link to Microsofts Power Toys which did work but its very limited with no linked image support and no means of clicking on links to open in browser. They have been promising a fix for 2 years now.
I will try extra hard to get your software to work on my machines but if If I may ask first, Does your version display linked images? Can you also click on markdown links and have them open in your browser?
Opening links is not a must but being able to see images is a must for me!
If its possible to see to linked images what about other linked media (such as Giffs and SVG)
Please if you can asnwer these questions I would be so happy, Thanks!

Hi Hellen,
Honestly: I don't remember, but I think it didn't.
For me the frustration of the failure out consistently installing the sharpshell extension outweighed the lack of features in Powertoys, so I stuck with powertoys.
I originally opened the feature request, see https://github.com/microsoft/PowerToys/issues/1837
I did not bother (yet) to get into creating the feature myself and make a pull request.
If you can find some way into making my little app stable and predictably installable, I will try to revive these feature request in my extension.
( What about other wonderfully things like mermaid charts, table of contents etc?)

Hey Thanks so much for getting back to me, I really appreciate it.

I originally opened the feature request, see https://github.com/microsoft/PowerToys/issues/1837
I had commented on that a few days ago. This not realise you created it, it would have answered my question lol. I am noob in this world of Github, a true Git as the brits would say.

If you can find some way into making my little app stable and predictably installable, I will try to revive these feature request in my extension.
I was planning to do this past weekend but things got in the way but I will get around to it, come friday.

( What about other wonderfully things like mermaid charts, table of contents etc?)
Ohh one can dream! You have on your hands a tool that is very usefull. As far I know, only you and Microsoft are offering a solution!

Hi Hellen,Honestly: I don't remember, but I think it didn't.For me the frustration of the failure out consistently installing the sharpshell extension outweighed the lack of features in Powertoys, so I stuck with powertoys.I originally opened the feature request, see https://github.com/microsoft/PowerToys/issues/1837I did not bother (yet) to get into creating the feature myself and make a pull request.If you can find some way into making my little app stable and predictably installable, I will try to revive these feature request in my extension.( What about other wonderfully thinks like mermaid charts, table of contents etc?)On Apr 5, 2022 16:34, hellen-dorandt89 @.***> wrote:
Hello, I've searching like a mad woman for markdown support in Explorer preview pane (and all other softwares that use the same pane).
I coud not get your software to work sadly but you was kind enough to link to Microsofts Power Toys which did work but its very limited with no linked image support and no means of clicking on links to open in browser. They have been promising a fix for 2 years now.
I will try extra hard to get your software to work on my machines but if If I may ask first, Does your version display linked images? Can you also click on markdown links and have them open in your browser?
Opening links is not a must but being able to see images is a must for me!
If its possible to see to linked images what about other linked media (such as Giffs and SVG)
Please if you can asnwer these questions I would be so happy, Thanks!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>


Include filter props

What:
Added filterProps to the glamorousOptions interface and the propsAreCSSOveridesOptions interface.
Also changed the forwardProps on both interfaces so it is typed to string[]

Why:
They are methods missing on the interfaces, and are causing compiler errors when running with typescript

How:

Checklist:

[ ] Documentation N/A
[x] Tests
[x] Ready to be merged
[x] Added myself to contributors table

I added the pre-commit line in the opt-in file, but didn't actually get told why my commits failed so I ended up commiting under the -no-verify flag.

Failed because the snapshot was updated? But the contributing log said to run 'npm run test:update' and commit any snapshot changes...
Also, I don't really understand why the snapshot changed when I only added types to some interfaces

Whoops! Wrong button!

The snapshot changes look totally unrelated to your changes. I'm not sure why you needed to update the snapshots locally 🤔

I'll back them out, but here https://github.com/paypal/glamorous/blob/master/CONTRIBUTING.md it does say to run the tests locally, I guess I misunderstood the direction and you only need to run with the update flag if you are meant to be updating snapshots?

No, I think you didn't do anything wrong. There's something messed up with glamorous's tests right now. I'm working on it.

I'm afraid that I've run out of time to work on this. I'll try to get back to it eventually, but I can't make any promises (we just had baby # 4 and my kids are wondering why daddy isn't playing with them while Mom takes care of the baby).
If anyone wants to step in here to figure out what's going on that'd be great.

Just had a look into this, the snapshot mismatchs look like they are related to the version of node you run the tests with.
If you run them with node 6 you get the output as seen in this PR, if you run them with node 8 you get the output as seen on the current master branch.
@johnjesse would you be able to rerun the tests with node 8 to redo the snapshots?

@luke-john, thanks for looking into it. I'll re-run the tests with node 8 as soon as I get the chance

Hey, so nothing has happened on this for a while, I know the checks haven't reported, do you want me to do anything else, squash the commits etc...

Codecov Report

Merging #340 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #340   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          10     10
  Lines         174    174
  Branches       48     48
=====================================
  Hits          174    174

Continue to review full report at Codecov.

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


Shorten the route for shipment info to remove the queue name

Description
This has bugged me for a while.  The way to get to a shipment should always be independent of the queue its associated with.  This will make more sense when we also have the shipments/:shipmentId/documents and shipments/:shipmentId/documents/:moveDocumentId routes.
Code Review Verification Steps

[ ] End to end tests pass (make e2e_test).
[x] Request review from a member of a different team.

I think e2e tests would work if the branch was built on this: https://github.com/transcom/mymove/pull/1019/files


container.rows should be rows and container.cols should be columns

Current
from opentrons import containers
plate = containers.load('96-flat', 'A1')
print(plate.rows(0))

outputs <WellSeries: <Well A1><Well B1><Well C1><Well D1><Well E1><Well F1><Well G1><Well H1>>
Expected
A1..A12

If we invert them i,e plate.rows() is now A1-12 instead of A1-H1 that will create huge backwards compatibility issues for OT1 users and all past protocols written. Maybe we should have a meeting to discuss?

Happy to discuss. We should keep in mind that for these kinds of changes we can automatically convert protocols. Also we should think about development experience for new protocols when writing a protocol we will be using rows instead of cols and vice versa.

@IanLondon reassigning this to you since you are consolidating OT1->OT2 changes


Matching arguments with RSpec matchers

It's just an improvement in the doc. It's base on my problem that I didn't realize that we could use RSpec matcher in matching arguments on this page https://www.relishapp.com/rspec/rspec-mocks/v/3-2/docs/setting-constraints/matching-arguments
Base on conversation with @myronmarston [1], I suggest to add another scenario to make it clearer even those there is no any different from using custom matcher which is we already have scenario in term of behavior correctness.
https://twitter.com/samnangchhun/status/586069627207192576

Thanks, @samnang!  I'll be happy to merge once you address the two comments above.

Updated base on feedbacks. Thank @myronmarston for you help and explanation.

Thanks!


Fix tsconfig error

Hi @HoHieuLuc,
This pull request is to fix a small issue I encountered with this project, the problem is in my environment when building with Webpack I'd get the following error:
Error: File 'tsconfig/react-library.json' not found.
    at Be (..\node_modules\get-tsconfig\dist\index.cjs:754:15)
    at ie (..\node_modules\get-tsconfig\dist\index.cjs:806:19)
    at le (..\node_modules\get-tsconfig\dist\index.cjs:847:30)
    at Object.Le [as getTsconfig] (..\node_modules\get-tsconfig\dist\index.cjs:851:15)
    at Object.ESBuildLoader (..\node_modules\esbuild-loader\dist\index.cjs:65:36)
    at LOADER_EXECUTION (..\node_modules\loader-runner\lib\LoaderRunner.js:132:14)
    at runSyncOrAsync (..\node_modules\loader-runner\lib\LoaderRunner.js:133:4)
    at iterateNormalLoaders (..\node_modules\loader-runner\lib\LoaderRunner.js:250:2)
    at ..\node_modules\loader-runner\lib\LoaderRunner.js:223:4
    at ..\node_modules\webpack\lib\NormalModule.js:920:15

Which is because that file doesn't exist, but is referenced by packages\tiptap-resizable-image\tsconfig.json. To fix this I modified package.json to only include /dist/ when publishing.

Thanks for the pull request! I started looking at it, but I ran into some issues on my side. I’ll review it properly this weekend.


Label in Smoothstep

The label in smoothstep is not positioned properly. This occurs if you have a path from left to top direction.

Getting the same issue when connecting default nodes to custom nodes:

Issue doesn't arise when connecting custom nodes to each other:

Tried messing around with the custom nodes handles but nothing worked.

Hey! Could you check v9.4.0?

Yep, I have the same issue with an edge from the left to top handle. Upgrading to 9.4.2 didn't help.

hey @denis-yasnitsky thanks for the feedback here. Could you try 9.4.3?
@obaid and @DovahBrownies could you check the label position for your cases with the latest version?

9.4.3 is close to perfection, but there is one little detail remains: line is not perpendicular to a box, seems like several degrees rotation clockwise:

@denis-yasnitsky thanks. Could you check 9.4.4?

Nailed it! Thanks a lot!


fn DisjointMut::{,mut_}{slice,element}_as: Replace u8 with U: AsBytes for more flexibility

This way we can allow the underlying data to be larger than just bytes (e.x. AlignedPixelChunk), allowing us to avoid lots of alignment checks.

It's difficult to translate the ranges when doing this (I think it's incorrect here), and I figured out how to get around this a different way.


Hash

@rodowi - For your consideration.

Sets the hash in the address bar so you can bookmark and quickly visit specific locations
Sets the maxZoom to 30 to allow for deeper zooming, useful with dense data

We've recently merged a PR for setting the template's maxzoom as defined in the tileset metadata. I think we should respect that parameter coming from the mbtiles. Any comments?

I think a higher maxzoom on the template is ideal for inspecting data.


Errors trying to write pagination pages with Jekyll v4

Using the Pr #167  which relaxes the Jekyll dependency to allow v4, I'm seeing the following error which crashes the build.
I can see in the verbose --trace that my post tags are all being read correctly before this, but when it tries to write autopages for tags it breaks.
It's possible it's something related to the paper-for-ios tag it seems to be failing on since a couple of category paginated pages write fine. But as far as I can tell there's nothing unique or "wrong" with this tag other than it's on a lot of posts.
...
Writing: E:/test-repo/_site/mastering-paper/index.html
Writing: E:/test-repo/_site/mastering-paper/page/2/index.html
Writing: E:/test-repo/_site/notes/index.html
Writing: E:/test-repo/_site/notes/page/2/index.html
Writing: E:/test-repo/_site/notes/page/3/index.html
Writing: E:/test-repo/_site/tag/paper-for-ios/index.html
E:/Ruby24-x64/lib/ruby/2.4.0/fileutils.rb:230:in `mkdir': File exists @ dir_s_mkdir - E:/test-repo/_site/tag/paper-for-ios/index.html (Errno::EEXIST)
        from E:/Ruby24-x64/lib/ruby/2.4.0/fileutils.rb:230:in `fu_mkdir'
        from E:/Ruby24-x64/lib/ruby/2.4.0/fileutils.rb:208:in `block (2 levels) in mkdir_p'
        from E:/Ruby24-x64/lib/ruby/2.4.0/fileutils.rb:206:in `reverse_each'
        from E:/Ruby24-x64/lib/ruby/2.4.0/fileutils.rb:206:in `block in mkdir_p'
        from E:/Ruby24-x64/lib/ruby/2.4.0/fileutils.rb:191:in `each'
        from E:/Ruby24-x64/lib/ruby/2.4.0/fileutils.rb:191:in `mkdir_p'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-4.0.0/lib/jekyll/convertible.rb:225:in `write'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-4.0.0/lib/jekyll/site.rb:219:in `block in write'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-4.0.0/lib/jekyll/site.rb:344:in `block (2 levels) in each_site_file'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-4.0.0/lib/jekyll/site.rb:343:in `each'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-4.0.0/lib/jekyll/site.rb:343:in `block in each_site_file'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-4.0.0/lib/jekyll/site.rb:342:in `each'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-4.0.0/lib/jekyll/site.rb:342:in `each_site_file'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-4.0.0/lib/jekyll/site.rb:218:in `write'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-4.0.0/lib/jekyll/site.rb:78:in `process'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-4.0.0/lib/jekyll/command.rb:28:in `process_site'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-4.0.0/lib/jekyll/commands/build.rb:65:in `build'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-4.0.0/lib/jekyll/commands/build.rb:36:in `process'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-4.0.0/lib/jekyll/command.rb:89:in `block in process_with_graceful_fail'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-4.0.0/lib/jekyll/command.rb:89:in `each'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-4.0.0/lib/jekyll/command.rb:89:in `process_with_graceful_fail'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-4.0.0/lib/jekyll/commands/build.rb:18:in `block (2 levels) in init_with_program'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `block in execute'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `each'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `execute'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/mercenary-0.3.6/lib/mercenary/program.rb:42:in `go'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/mercenary-0.3.6/lib/mercenary.rb:19:in `program'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-4.0.0/exe/jekyll:15:in `<top (required)>'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/bin/jekyll:23:in `load'
        from E:/Ruby24-x64/lib/ruby/gems/2.4.0/bin/jekyll:23:in `<main>'

Will test on macOS to see if it's a Windows thing when I get a chance.

Is this test repo on GitHub?

Yeah, it's a big complicated mess. Let me do some further testing and push up a smaller repro site since my build workflow uses Gulp to kickoff the Jekyll build.
It seems isolated to autopages.tags. When I disable that module in _config.yml everything builds fine... just with no paginated tag pages.

Looking like this plugin is working correctly. I took all my posts and put them into a jekyll new site with Autopages configured as I have and it built the tag pages.
I'm using some other plugins for tag sorting and related posts via tags so perhaps there's something in there causing a ruckus.

Noticing that when I disable pagination with Autopage it will build.
Looking at some of the links that {{ paginator.next_page_path }} generates I'm seeing things like /tag/apple/index.html/page/2/index.html which would explain why it may be having trouble writing files.
No idea what could have changed in the last couple of commits to do this though.
pagination:
  enabled: true
  per_page: 15
  permalink: "/page/:num/"
  title: ":title"
  sort_field: "date"
  sort_reverse: true

autopages:
  enabled: true
  categories:
    enabled: false
  collections:
    enabled: false
  tags:
    enabled: true
    slugify:
      mode: raw
      cased: true
    layouts:
      - "autopage_tags.html"
    title: ":tag" # :tag is replaced by the tag name
    permalink: "/tag/:tag"

I've so many PRs open here and they've been sitting idle for so long that I don't remember if this was fixed by one of them..... :man_shrugging:

@ashmaroli No worries, I'm in no rush to upgrade.

@ashmaroli Does seem that you fixed it in this PR #151

Thanks for investigating. I see that the bug eventually points a finger at the v2.1.0, that was yanked.
I would just checkout v2.0.0 tag, fork a new branch from that point, add Jekyll 4.0 support to that branch and use that.

@ashmaroli You read my mind. This issue seemed very familiar as the same thing happened when I updated to 2.1.
So I think you're right, whatever commits came after 2.0.0 introduced a bug and this has nothing to do with Jekyll 4.

Its a shame that I authored all the commits after 2.0.0 :disappointed:

should we use @mmistakes  fork if we want to update to jekyll 4 with pagination? @ashmaroli  ? this repo wont be fixed ?

@hosnas I'm not the maintainer of this repo.

@ashmaroli I know the maintainer is someone else. But I'm asking you as an expert and perhaps @mmistakes can also guide me. Should we use @mmistakes fork for Jekyll 4? Cause I haven't updated my jekyll to version 4 for a long time, only because of this repo.

@hosnas I'd try the fork and see if your site builds. If it does use it. If it doesn't, don't wait to upgrade.
You're not missing much with Jekyll 4 right now other than some nice performance gains.

@mmistakes - couple of quick questions. I'm looking to use the Autopages feature for a site I'm developing which is currently on Jekyll v4. Can I downgrade to v3 by specifying it in my gemfile?
Secondly, can Autopages create index pages for a custom taxonomy? As I understand, categories and tags are for posts only, but I see on your site you have categories in your work section.
I posted on Jekyll Talk but basically I wanted to create archives for a taxonomy on an Event collection (be it built in categories or a custom front matter field).
https://talk.jekyllrb.com/t/collections-and-categories-question-about-autopages
Thanks!

@curious-toad You'll want to downgrade jekyll-paginate-v2 to 2.0.0 and not use the latest release of 2.0.1 as it introduced some sort of defect with the autopages module. I had this issue with Jekyll v3.
If you want to use Jekyll v4 you can use my fork of the gem, which is pretty much 2.0.0 but with one small change to allow it to support Jekyll v4.
Not sure if Autopages can create index pages for custom taxonomies. I'm pretty sure it only works with site.tags and site.categories. My site is a bit misleading... the works.md page and _work collection isn't generated or paginated via the plugin. I'm using it just to build an index page that combines some collection documents along with work "posts" found in this folder.
These are part of my work category, which is why you might see that in the front matter but it's not used for Autopages. I'm doing this because tags and categories are only available via the site objects when used on posts... and not collection documents. That might have changed in Jekyll v4 but I'm not sure.

@mmistakes thanks so much for your help, I've followed your blog for a while so it's really appreciated!
Ahh cool, I wondered if that would be the case. I may have to set things up as much as possible so it's relatively automated - adding a few index pages (as you have in your work section) isn't too taxing, it just increases the chance of things being missed and 404ing.
Re. Global categories and tags in v4 - I've seen a few feature requests and a suggested implementation but doesn't look to have made the cut.
It's a shame, as I'm really enjoying jekyll but it's the one thing that other tools like Hugo or WP make so easy and for the sites I build is pretty essential.

Hello everyone !
@mmistakes' advises work well, so here is a straightforward way to achieve this technically on your own :
# Remove the Gem previously installed from repositories
gem uninstall jekyll-paginate-v2
gem cleanup

# Download official Jekyll-Paginate-v2 (v2.0.0), and extract it
wget https://github.com/sverrirs/jekyll-paginate-v2/archive/v2.0.0.tar.gz
tar xvzf v2.0.0.tar.gz
cd jekyll-paginate-v2/

Apply @mmistakes' "patch" (👌) :
diff --git a/jekyll-paginate-v2.gemspec b/jekyll-paginate-v2.gemspec
index 6c5fb8b..5cb933a 100644
--- a/jekyll-paginate-v2.gemspec
+++ b/jekyll-paginate-v2.gemspec
@@ -23,8 +23,7 @@ Gem::Specification.new do |spec|
   spec.require_paths = ["lib"]

   # Gem requires Jekyll to work
-  # ~> is the pessimistic operator and is equivalent to '>= 3.0', '< 4.0'
-  spec.add_runtime_dependency "jekyll", "~> 3.0"
+  spec.add_runtime_dependency "jekyll", ">= 3.6", "< 5.0"

   # Development requires more
   spec.add_development_dependency "bundler", "~> 1.5"

# Build and install the Gem locally
gem build jekyll-paginate-v2.gemspec
gem install jekyll-paginate-v2 --local

# Cleanup
cd -
rm -rf jekyll-paginate-v2/

# Let's rock !
jekyll <...>

Bye 👋

Repo restored to last known good state with selective cherrypicks, please upgrade to https://rubygems.org/gems/jekyll-paginate-v2/versions/3.0.0


Actor State TTL

Dapr Actor state TTL is a feature that was added in Dapr 1.12.
Adds support for Actor State TTL. TTL of actor state is set by using the ttlInSeconds metadata option when saving actor state. The actor state cache uses the ttlExpireTime return metadata field to determine whether the key is still valid, which is important as the cache may become populated with TTL keys which were not created by the current manager.
SDK developers are encouraged to use TTLs when storing any actor state in order to prevent stale data accumulating in the actor state store over time.
Closes https://github.com/dapr/dotnet-sdk/pull/1164

@philliphoff do you understand why the integration tests are failing? I'm not too sure what the problem is.

@philliphoff do you understand why the integration tests are failing? I'm not too sure what the problem is.

Dunno.  Maybe retry the job in case it was just a transient issue?

@philliphoff Doesn't seem to be the case. Struggling to understand what is going wrong here.. at the limit of my .NET knowledge :grimacing:

@philliphoff Doesn't seem to be the case. Struggling to understand what is going wrong here.. at the limit of my .NET knowledge 😬

Poked around this morning and found a couple of issues where existing state was ignored in favor of default values (see above suggestions), which were causing the E2E to fail.  It might be good to add some unit tests for DaprHttpInteractor, ActorStateManager, and DaprStateProvider, if reasonably possible, to ensure that all the cases are covered (e.g. when values are cached vs. non-cached), pre- and post-expiration, etc.).

Thank you @philliphoff, really appreciate your help with this!
I've gone ahead and added those fixes, expanded the E2E state tests and added unit tests for those classed. Please take another look :slightly_smiling_face:

Hi @philliphoff, please let me know what you think when you have time


ModuleNotFoundError: No module named 'sklearn.metrics._dist_metrics'

ModuleNotFoundError: No module named 'sklearn.metrics._dist_metrics'
It should be sklearn.neighbors._dist_metrics???

I encounter the same problem as you. May I ask about the solution of the problem?

ModuleNotFoundError: No module named 'sklearn.metrics._dist_metrics'
It should be sklearn.neighbors._dist_metrics???

I encounter the same problem as you. May I ask about the solution of the problem?


Logproc output JSON

Mentoring instructions:
logproc is our tool for parsing, filtering, and pretty-printing the sexps that Logger outputs. Currently, it can only pretty print messages. It should also be able to output machine-readable JSON. There are two parts to this issue:

Add Message.to_yojson in Logger.

We use yojson as our JSON library. ppx_deriving_yojson makes it very easy to serialize values of a type. Unfortunately, unlike sexp, most modules don't already support JSON serialization. This makes it annoying to use for complex types. Fortunately, Message.t isn't too bad! The general pattern is this:

Add ppx_deriving_yojson to the preprocess config in jbuild eg
Add yojson and ppx_deriving_yojson.runtime to the libraries config in jbuild eg
Make sure to add -39 to the -warn-error config eg. ppx_deriving_yojson emits code with warnings.
Add [@@deriving yojson] to Message.t in logger.mli eg
In logger.ml, make a new type that is  [@@deriving yojson]. We'll be mapping to this type before using the derived yojson serialization. The idea is to replace the fields that don't already have yojson derivings with a string or some other type that yojson already knows how to handle. eg
Implement to_yojson and of_yojson by mapping to/from this type eg and using this type's to_yojson.

Once that is done...

Use it in logproc

Add a boolean flag -output-json  (default false) to logproc around here. Pass it through to the main function, and if it's true, instead of using pretty_print_message, use Yojson.of_string (Message.to_yojson m).

We've replaced all the sexp stuff with JSON already.