Add support for Solr 5.x

It would be really helpful if support for Solr was updated to include version 5

Upstream issue: https://github.com/geerlingguy/ansible-role-solr/issues/10

Did one better and also got Solr 6.x support added!
I will update the role requirements file for 3.0.0 soon, or I might finish adding automatic core provisioning and tag a new release of the upstream role before adding (therefore I'll leave this issue open until that's complete).
The alternative (if I use the current version of the role) is to just have the post-install script example also create a custom core to be used by the Search API Solr module.

3.1.0 includes automatic core setup/generation, as well as memory configuration, so I'll be moving to that version for Drupal VM 3.1.0, and also updating the default version in default.config.yml to the latest 5.x Solr release.
It looks like Solr 6 support is already in 8.x (https://www.drupal.org/node/2704383), but not yet in 7.x (https://www.drupal.org/node/2711685).
Once this is in, you could change solr versions by destroying and rebuilding the VM, switching the solr_version between solr_version: "5.5.1" and solr_version: "6.0.1"—or really any version between 3.5.x and the latest 6.x!


Prevent helpers being loaded for Rails API’s

Extends logic from https://github.com/plataformatec/devise/pull/3732 to get Rails API working

I just got my rails 5 api working with this PR! :smile:

Great! Thanks!


Move to signing service v2

@onovotny I had problems signing locally (I used user+pass from LastPass, but still no luck). So I thought I'll just push a PR and ask for help 😄
This is the output I get:
========================================
Sign-Binaries
========================================
Executing task: Sign-Binaries
Executing: "C:/Program Files/dotnet/dotnet.exe" --version
2.0.2
Signing C:/Users/mb/src/gh/bakery/BuildArtifacts/Packages/NuGet/Cake.Bakery.0.2.0-new-signing-serv0001.nupkg...
Executing: "C:/Program Files/dotnet/dotnet.exe" "C:/Users/mb/src/gh/bakery/tools/SignClient.0.9.0/tools/netcoreapp2.0/SignClient.dll" sign -c "C:/Users/mb/src/gh/bakery/signclient.json" -i "C:/Users/mb/src/gh/bakery/BuildArtifacts/Packages/NuGet/Cake.Bakery.0.2.0-new-signing-serv0001.nupkg" -f "C:/Users/mb/src/gh/bakery/signclient.filter" -s "[REDACTED]" -r "[REDACTED]" -h "dual" -n "Cake" -d "Cake (C# Make) is a cross platform build automation system." -u "https://cakebuild.net"
Server returned non Ok response: 400 Bad Request
An error occurred when executing task 'Sign-Binaries'.

Can you try getting rid of -h "dual", you don't need it currently.

@onovotny Thanks, that worked! I guess no one needs dual signing these days anymore?

XP was the only reason for dual signing left


Add support for raw script addresses

This PR adds support for a new type of addresses which encode raw scripts.
A new rpc command has been added createrawscriptaddress.
Example: createrawscriptaddress 6ac1 outputs 3HnzbJ4TR9. Sending coins to 3HnzbJ4TR9 would send them to the DAO Fund.
This enables to easily redirect stake rewards to any special script (like the DAO fund).

I think the new functionality is useful, especially for experimenting with smart contracts more easily.
However, it seems to me that in its current form is a bit risky, the user does not know if the address obtained expresses a correct script.
Using an invalid script in a transaction you risk "burning" the coins sent, without the possibility of recovery.
Currently the user could get an address that is actually based on an input:
    1) Invalid or not correctly interpreted as hexadecimal value.
        Example: createrawscriptaddress 0x6ac1
                 7rLnRLD
    2) valid, but the script it represents is incorrect and cannot be decoded.
        Ex: createrawscriptaddress "216ac1"
            B4LorUWVZ8x
            decodescript "216ac1"
            {
            "asm": "[error]",
            "type": "nonstandard",
            "p2sh": "2MziQuEaXPo8MvB7QXW5Ck3icaThAa4cYSD"
            }

    3) formally decodable, but which uses OP_CODE still undefined or removed
        Ex: createrawscriptaddress "f06ac1"
            BCBnKiqpbsY
            decodescript "f06ac1"
            {
            "asm": "OP_UNKNOWN OP_RETURN OP_CFUND",
            "type": "nonstandard",
            "p2sh": "2NChNGPMEnBaTcjAoc2JhBfLfgnVhD7JTDD"
            }
Case three could be useful in testing (devnet, testnet), but it should never be allowed in the main chain.
IMHO, If the RPC was expanded so as to return addresses only when the scripts are totally valid, for example by integrating the decodescrip function, it will be an excellent improvement.

@aguycalled I think @R-Marino has a good point about integrating the decode script into this :+1:

thanks for the feedback. even if additional checks are implemented, an user will still be able to create addresses for unspendable scripts (OP_RETURN the most obvious example)
@R-Marino  i find your suggestions greatly valuable. I've just added a few sanity checks in line with your comments

Very well, great job.
You are absolutely right. We as users, will always be able to find new, more sophisticated and "smart" ways of burning our money. ;-P
However, one thing is to do this fully aware of what one does, another thing is to make mistakes just for a little carelessness.
So thanks to you for promptly taking care of this.

Shortly after writing, I read a bitcoin news, which in some way could be linked to this PR.
The news talk about Miniscript, a kind of formal language for creating bitcoin smart contract scripts.
It is here:
https://www.coindesk.com/pieter-wuille-unveils-miniscript-a-new-smart-contract-language-for-bitcoin
http://bitcoin.sipa.be/miniscript/
Surely this extension goes far beyond the scope of this PR, and I imagine that its possible inclusion in NAV core wallet would also require some work for integration and adaptation to some specific NAV_OP_Codes.
I also think that being a very technical topic, surely the users really interested in using it would only be a few dozen.
So I don't think it's a priority, but in some way it could be very interesting for the future.
IMHO, The proper integration of that commit into another rpc, or even into an external module could be the perfect complement to this PR.

if i understand it correctly, miniscript is just a higher level language for the traditional bitcoin script language. think miniscript is javascript and script is assembly. miniscript translates a set of combined logic conditions into the shortest/cheaper script code. the first is easier to construct for a common human.
as this happens in higher layers, there's nothing needed to implement at the node layer more than maybe adding an interpreter for the sake of facilitating user interaction as long as the set of needed op codes is shared between bitcoin and navcoin.

Well, more than assembler, the script reminds me more of Forth, or RPN,
but you're right, it is a interpreter after all.
But the OP_CODE code set is not totally shared between Bitcoin and NavCoin,
for example we have OP_COINSTAKE, OP_CFUND. etc. until OP_POOL.
Even now we could think of singular things, for example by combining
OP_COINSTAKE and OP_CHECKLOCKTIMEVERIFY we could obtain something analogous
to a kind of coldstake with "long-term storage", that is capable of producing
stakes, but that cannot be spent before a certain date.
Or by combining differently, a "Slow ColdStake", which can always be spent
but unable to produce stakes before a given time has passed.
This would already be something, but if you then create OPCODE able to give
information on the present state, or the status of the other transactions,
then you would see really smart contracts.
Try to imagine for example a opcode that is able to verify if the coinbase
votes for a proposal, after all it is an internal state regarding the same
block.
Already this would open up other opportunities, for example you could have
a "ColdStake for a cause", so as to be certain that a pool could produce one
stakes, only when it reflects enterely the type of vote of the owner.
If instead the opcode could control the outputs of the stake, you could get
a "ColdStake for charity", I mean that the stake would be possible only when
a part of the reward went with absolute certainty to a given address.
These hypotheses probably do not all have a practical sense, or they may have
more opposed than positive aspects, but they are only examples of types of
smart contract based on OP_COINSTAKE that could be quite unique,
unique to Nav.
Sorry, maybe I have digress a little too much.

@aguycalled  @R-Marino are there more changes to be added to this branch? Or is it ok to review now?

@aguycalled build and tested on Ubuntu 19.10, works fine, I also tested this merged with master and set the contribution address to Community Fund and it was sending the stakes correctly to CFUND

Tested sending, receiving, staking and generating block in QT and all were working fine.

Added needed for final release tag as the staking split feature is kinda missing this PR to work 100%.

@mxaddict the sanity checks on the RPC command added here https://github.com/navcoin/navcoin-core/pull/587/commits/0088e93ca2cf03432e8baee523841ba16c795a92 should be enough for now. It at least checks the parsed script is valid hex and exists in the OP_CODE list.

Tested on OSX,

compiles & runs
unit test passes
RPC rejects non hex values
RPC rejects hex values which are not mapped to an OP_CODE
wallet recognises addresses as valid to send to.


The prerequisites are not precise

The pages describe the prerequisites. But it is not precise.

You do not need Power Platform Service admin, Dynamics 365 admin, or Microsoft 365 Global admin but system administrator.
Could you kindly update the descriptions of the prerequisites?

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

ID: 88890037-f7de-6084-f506-dc917adc0508
Version Independent ID: 95103288-f976-3b83-d089-be6d315e563f
Content: Set up exporting to Application Insights - Power Platform
Content Source: power-platform/admin/set-up-export-application-insights.md
Service: power-platform
Sub-service: admin
GitHub Login: @TJVass
Microsoft Alias: tjvass

Thanks for your comment, @fumi11. This issue has been assigned to the doc author for review.


namuwiki-importer.js

namuwiki-importer.js에서 json 파일은 어떤 파일로 입력해야 하나요?

node:events:492
      throw er; // Unhandled 'error' event
      ^

Error: Top-level object should be an array.
    at StreamArray._wait (/Users/alpha123/imitated-seed-2/node_modules/stream-json/streamers/StreamArray.js:24:23)
    at Transform._write (node:internal/streams/transform:175:8)
    at writeOrBuffer (node:internal/streams/writable:556:12)
    at _write (node:internal/streams/writable:490:10)
    at Writable.write (node:internal/streams/writable:494:10)
    at Parser.ondata (node:internal/streams/readable:985:22)
    at Parser.emit (node:events:514:28)
    at addChunk (node:internal/streams/readable:545:12)
    at readableAddChunkPushObjectMode (node:internal/streams/readable:521:3)
    at Readable.push (node:internal/streams/readable:376:5)
Emitted 'error' event on Chain instance at:
    at StreamArray.<anonymous> (/Users/alpha123/imitated-seed-2/node_modules/stream-chain/index.js:146:71)
    at StreamArray.emit (node:events:526:35)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

오류가 납니다.

두 번째 댓글은 뭔가요?

어떤 화일을 사용해야 하나요?

화일을 찾을 수 없다고 나옵니다.

네


Check if there are files to generate cscope DB

Recently I've got the gutentags: cscope job failed, returned: 1 message quite a lot, so I've dug into it. The main reason is the empty file list for cscope.
I use a custom file list command, something like git ls-files '*.c' '*.h' '*.cpp' '*.hpp'. When I open a Vim in a project doesn't have such files, the file list ("${DB_FILE}.files") is empty, and cscope complains about it: cscope: no source files found.
I think this shouldn't be an error, so I added the checking logic to return early. Unfortunately, I didn't test on Windows, I would appreciate it if someone check this patch.

Merged with 932b8cb2f8e9816c9b5be82ada2e27564deb4d2e, thanks for figuring this out!

Thanks!


fix(jsc): prevent crashes when using jsc runtime

While trying to get this library working in an environment where we are unable to use hermes for 𝓇ℯ𝒶𝓈ℴ𝓃𝓈, I encountered two issues which this PR fixes.

NativeState is unimplemented in the react-native JSC shim before react-native 0.74.x.
When hostFunctions are called, JSC attempts to provide globalThis as the 'this' context causing crashes (hermes provides undefined).

Should hopefully resolve https://github.com/margelo/react-native-worklets-core/issues/137
As far as I can tell, the entire test suite passes in iOS. It seems like it's also passing in android but I am unable to get consistent results.

you are a hero @maxpowa


Does not define a graphics card

Hi, can you please help. I have i5 9400f processor without UDH graphics and have radeon RX 550 card, but os does not correct define the card.

Found a solution to add faked device id. I know how to do it in clover, but I don't know how to do it in opencore. Can you help?

RX 550 not supported is macOS:
https://khronokernel-3.gitbook.io/gpu-buyers-guide/modern-gpus/amd-gpu#unsupported-amd-gpus
Read this guides:
https://github.com/khronokernel/Opencore-Vanilla-Desktop-Guide/blob/master/extras/hardware.md


Create EnsembleMixin

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Before submitting (must do checklist)

[x] Did you read the contribution guide?
[x] Did you update the docs? We use Numpy format for all the methods and classes.
[ ] Did you write any new necessary tests?
[x] Did you update the CHANGELOG?

Type of Change

[ ] Examples / docs / tutorials / contributors update
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Improvement (non-breaking change which improves an existing feature)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Proposed Changes

Related Issue

Closing issues

closes #561

Codecov Report

Merging #574 (dc4f19e) into master (09a7938) will decrease coverage by 32.78%.
The diff coverage is 93.75%.

@@             Coverage Diff             @@
##           master     #574       +/-   ##
===========================================
- Coverage   87.27%   54.48%   -32.79%
===========================================
  Files         118      119        +1
  Lines        5727     5712       -15
===========================================
- Hits         4998     3112     -1886
- Misses        729     2600     +1871

Impacted Files
Coverage Δ

etna/ensembles/base.py
92.59% <92.59%> (ø)

etna/ensembles/__init__.py
100.00% <100.00%> (ø)

etna/ensembles/stacking_ensemble.py
81.63% <100.00%> (-16.69%)
:arrow_down:

etna/ensembles/voting_ensemble.py
95.00% <100.00%> (-5.00%)
:arrow_down:

etna/commands/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

etna/commands/backtest_command.py
0.00% <0.00%> (-96.43%)
:arrow_down:

etna/commands/forecast_command.py
0.00% <0.00%> (-92.00%)
:arrow_down:

etna/commands/__main__.py
0.00% <0.00%> (-87.50%)
:arrow_down:

etna/commands/resolvers.py
0.00% <0.00%> (-80.00%)
:arrow_down:

etna/analysis/outliers/density_outliers.py
22.44% <0.00%> (-75.52%)
:arrow_down:

... and 71 more

Continue to review full report at Codecov.

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


How can I get free coins

          How can I get free coins

Originally posted by @Jiibraaxayste in https://github.com/TikTokCo1n/TikTok-Ultimate-Free-Coins/issues/15#issuecomment-2374726107

Give face coin


report-jtreg

Repository URL
https://github.com/judovana/jenkins-report-jtreg
New Repository Name
report-jtreg-plugin
Description
This plugin is  built on top of chart.js api - https://github.com/jenkins-infra/repository-permissions-updater/issues/3172
It was following msot of the steps from  https://github.com/jenkins-infra/repository-permissions-updater/issues/3221 and https://github.com/jenkins-infra/repository-permissions-updater/issues/3222; hopefully correctly.
It is comaptible with junit/xunit/jtreg/jck and tck results.  Is optimised for suites with 1 000 000 and more results and on is known to be super fast on 10M testbases.
If there are queries the optimised plugin view do not answer,  it includes cli, able to blazingly quickly do various comparisons and dig more informations out of the results.
GitHub users to have commit permission
@judovana
@pmikova
@RadekCap
@zzambers
@andrlos
Jenkins project users to have release permission
judovana
Issue tracker
GitHub issues

Security audit, information and commands
The security team is auditing all the hosting requests, to ensure a better security by default.
This message informs you that a Jenkins Security Scan was triggered on your repository.
It takes ~10 minutes to complete.
Commands
The bot will parse all comments, and it will check if any line start with a command.
Security team only:

/audit-ok => the audit is complete, the hosting can continue :tada:.
/audit-skip => the audit is not necessary, the hosting can continue :tada:.
/audit-findings => the audit reveals some issues that require corrections :pencil2:.

Anyone:

/request-security-scan => the findings from the [Jenkins Security Scan](https://www.jenkins.io/doc/developer/security/scan/) were corrected, this command will re-scan your repository :mag:.
/audit-review => the findings from the audit were corrected, this command will ping the security team to review the findings :eyes:.
	It's only applicable when the previous audit required changes.

Only one command can be requested per comment.

(automatically generated message, version: 1.17.22)

The Jenkins Security Scan discovered 2 finding(s) :mag:.
For each of them, either apply the recommended correction, suppress the warning or provide a justification.
Once you're done, either re-run the scan with /request-security-scan or request the Security team to review your justifications with /audit-review.

Remoting: Unsafe Callable
You can find detailed information about this finding here.
ReportParserCallable.java#82
Potentially unsafe Callable implementation ReportParserCallable#checkRoles

Jenkins: Generally unsafe method calls
You can find detailed information about this finding here.
ArgumentsParsing.java#12
Potentially unsafe invocation of System#exit

/request-security-scan

/request-security-scan

The Jenkins Security Scan did not find anything dangerous with your plugin, congratulations! :tada:

:bulb: The Security team recommends that you are setting up the scan in your repository by following our guide.

Gosh... the adjuncts are not done....wip

Hello, while reviewing your plugin, I have some comments on it:

why do you need Jenkins 2.407 (https://github.com/judovana/jenkins-report-jtreg/blob/a4cea683ed2c1f7b86485a1ed5f9c7f3c2108e76/pom.xml#L19). It would be probably better to rely on an LTS version
it is probably better to have a specific version for woodstox-core rather than LATEST https://github.com/judovana/jenkins-report-jtreg/blob/a4cea683ed2c1f7b86485a1ed5f9c7f3c2108e76/pom.xml#LL131C22-L131C28
I don't really understand why you have the profiles in https://github.com/judovana/jenkins-report-jtreg/blob/a4cea683ed2c1f7b86485a1ed5f9c7f3c2108e76/pom.xml#L51-L102. Could you explain the use case for the jar profile?
https://github.com/judovana/jenkins-report-jtreg/blob/a4cea683ed2c1f7b86485a1ed5f9c7f3c2108e76/.github/workflows/release-drafter.yml#L7-L8 and https://github.com/judovana/jenkins-report-jtreg/blob/a4cea683ed2c1f7b86485a1ed5f9c7f3c2108e76/.github/workflows/jenkins-security-scan.yml#L7-L8 which default branch will you be using?
I understand this is a legacy thing but most of the classes have a problematic license header: https://github.com/judovana/jenkins-report-jtreg/blob/a4cea683ed2c1f7b86485a1ed5f9c7f3c2108e76/src/main/java/io/jenkins/plugins/report/jtreg/JckStyles.java#L4 for example.

Hello, while reviewing your plugin, I have some comments on it:

Hi! thanx for the hints!

* why do you need Jenkins `2.407` (https://github.com/judovana/jenkins-report-jtreg/blob/a4cea683ed2c1f7b86485a1ed5f9c7f3c2108e76/pom.xml#L19). It would be probably better to rely on an LTS version

There was indeed LTS which was not compatible with this plugin. In that time I switched to STS.  Its year or two old issue, and We are currently back on LTS, so It will be ok to move. to LTS.

* it is probably better to have a specific version for `woodstox-core` rather than `LATEST` https://github.com/judovana/jenkins-report-jtreg/blob/a4cea683ed2c1f7b86485a1ed5f9c7f3c2108e76/pom.xml#LL131C22-L131C28

This is similar issue. I got breakages caused by woodstox updates, so I was rather in mode to fix them immediately.
But it is indeed in past. I do not have strong opinion for LATEST or simply latest stable bumped by depnda bot.

* I don't really understand why you have the profiles in https://github.com/judovana/jenkins-report-jtreg/blob/a4cea683ed2c1f7b86485a1ed5f9c7f3c2108e76/pom.xml#L51-L102. Could you explain the use case for the `jar` profile?

The codebase have two main methods. If you built it as a jar, they serve as CLI able to access the local (this)plugin metadata and resolve complex queries.  They can run also as service, and then you can setup the plugin to use those services directly from jenkins.
Although in jenkins settings this is just service's url to set up, it is not trivial to set the services running.
The cli/services are using 100% of plugin codebase and are connectable from jenkins so should remain in close neighbourhood.
However they are cli/service, not easy to deploy, and may be exploitable if deplyed wrongly. So they shoudl be at least a bit separated at least on field of maven modules to plugin, lib and services. I never found cycles to properly cut this dilema.

* https://github.com/judovana/jenkins-report-jtreg/blob/a4cea683ed2c1f7b86485a1ed5f9c7f3c2108e76/.github/workflows/release-drafter.yml#L7-L8 and https://github.com/judovana/jenkins-report-jtreg/blob/a4cea683ed2c1f7b86485a1ed5f9c7f3c2108e76/.github/workflows/jenkins-security-scan.yml#L7-L8 which default branch will you be using?

Tbh I was not aware of this record. Its master now if I see correclty. Will it be master after move to jenkins, or it will become main?

* I understand this is a legacy thing but most of the classes have a problematic license header: https://github.com/judovana/jenkins-report-jtreg/blob/a4cea683ed2c1f7b86485a1ed5f9c7f3c2108e76/src/main/java/io/jenkins/plugins/report/jtreg/JckStyles.java#L4 for example.

I do not have strong prefference on this. I can do any of following:

replace "user" by "report-jtreg contributors"
remove  headers completely (as it is not 100% appearing), and keep an eye they do not reappear
correctly spread  fixed headers(so it  is 100% appearing), and keep an eye so they are kept

I would vote for b) - removal of the headers, and keeping just License file as it is only fixing "Copyright (c) 2016 Stanislav Baiduzhyi" by  "Copyright (c) 2016-2023  report-jtreg contributors"
Thanx!
J.

* why do you need Jenkins `2.407` (https://github.com/judovana/jenkins-report-jtreg/blob/a4cea683ed2c1f7b86485a1ed5f9c7f3c2108e76/pom.xml#L19). It would be probably better to rely on an LTS version

I have downgraded it, But I htink Wrongly. What is proepr number here?

* it is probably better to have a specific version for `woodstox-core` rather than `LATEST` https://github.com/judovana/jenkins-report-jtreg/blob/a4cea683ed2c1f7b86485a1ed5f9c7f3c2108e76/pom.xml#LL131C22-L131C28

fixed.

* https://github.com/judovana/jenkins-report-jtreg/blob/a4cea683ed2c1f7b86485a1ed5f9c7f3c2108e76/.github/workflows/release-drafter.yml#L7-L8 and https://github.com/judovana/jenkins-report-jtreg/blob/a4cea683ed2c1f7b86485a1ed5f9c7f3c2108e76/.github/workflows/jenkins-security-scan.yml#L7-L8 which default branch will you be using?

Fixed

* I understand this is a legacy thing but most of the classes have a problematic license header: https://github.com/judovana/jenkins-report-jtreg/blob/a4cea683ed2c1f7b86485a1ed5f9c7f3c2108e76/src/main/java/io/jenkins/plugins/report/jtreg/JckStyles.java#L4 for example.

Fixed so it be at least not wrong.
One adjunct done, second to go. TY!

Both adjuncts done . blacklist/whitelist in progress

whitelist and balcklist repaled by allowlist and deny list. I think the plugin is now ready for review. TY!

/request-security-scan

/hosting re-check

The Jenkins Security Scan did not find anything dangerous with your plugin, congratulations! :tada:

:bulb: The Security team recommends that you are setting up the scan in your repository by following our guide.

https://github.com/judovana/jenkins-report-jtreg/blob/fa334f77bc44067f2c5794f8e07d6d667edb3233/pom.xml#L15 -> "JTReg Plugin"

Otherwise LGTM, I'd say.

https://github.com/judovana/jenkins-report-jtreg/blob/fa334f77bc44067f2c5794f8e07d6d667edb3233/pom.xml#L15 -> "JTReg Plugin"

renamed, ty.

Edit: It's not. https://github.com/judovana/jenkins-report-jtreg/tree/master/src/main/resources/io/jenkins/plugins/report/jtreg/main/web violates the content security policy. I recommend refactoring the files and outsourcing all <script> tags to dedicated .js files, loading them directly. Inline block contents are banned.

Those two files are not accessible from plugin. Only way how to reach them is to build the cli via -Pjar and then wrap that cli as CGI service.
Do yo still insits on separating the JS?

/hosting re-check

/request-security-scan

The Jenkins Security Scan did not find anything dangerous with your plugin, congratulations! :tada:

:bulb: The Security team recommends that you are setting up the scan in your repository by following our guide.

/hosting host

https://github.com/judovana/jenkins-report-jtreg/blob/fa334f77bc44067f2c5794f8e07d6d667edb3233/pom.xml#L15 -> "JTReg Plugin"

renamed, ty.

Edit: It's not. https://github.com/judovana/jenkins-report-jtreg/tree/master/src/main/resources/io/jenkins/plugins/report/jtreg/main/web violates the content security policy. I recommend refactoring the files and outsourcing all <script> tags to dedicated .js files, loading them directly. Inline block contents are banned.

Those two files are not accessible from plugin. Only way how to reach them is to build the cli via -Pjar and then wrap that cli as CGI service. Do yo still insits on separating the JS?

All good

ty!


258695 - Jay Singh - Added link to repo with completed assignment

Wrote functions to compute Sum, Difference, Product and Division of two Complex numbers. Added unit tests. Added hard coded values in main function to check execution instead of using scanf().

Can add badges to the REAME.md file under your repo.


Chenweifeng

Hello @Weifeng-Chen! Thanks for opening this PR.

In the file fengshen/examples/clip_finetune/clip_finetune_flickr.py:

Line 115:1: W293 blank line contains whitespace
Line 259:28: E261 at least two spaces before inline comment
Line 261:28: E261 at least two spaces before inline comment
Line 262:1: W391 blank line at end of file

Do see the Hitchhiker's guide to code style


Quick-start deployment buttons not working

New Feature / Enhancement Checklist

[x] I am not disclosing a vulnerability.
[x] I am not just asking a question.
[x] I have searched through existing issues.

Current Limitation
The Parse Server deployment buttons to quickly set-up a Parse Server instance are not working or outdated.
Feature / Enhancement Description
Update deployment button.
Example Use Case
n/a
Alternatives / Workarounds
n/a
3rd Party References
n/a

Remote Deployment section in read me.
None of the deployment buttons worked. Had to create accounts with many of the cloud services to then realize that none of options the buttons for deployment worked.
I think AWS would be the top contender. Is there anything that can be done?


Store (versioned) tool binaries relative to project root directory

Based on my comment in https://github.com/akuity/kargo/pull/1515#discussion_r1499139130
At present, we are doing a mixture of assuming certain tool binaries are present (globally) on a contributor their system, in combination with an additional assumption of them having a certain version.
In #1515, this is somewhat improved -- by at least ensuring there is a way to install the tools at their expected version. However, as this is still done globally this can create the new issue of it unexpectedly downgrading existing tools on a user their system.
To further improve this, I would suggest to install tool binaries relative to the project root directory (e.g. /hack/bin, see referred comment). Which can be combined with some Make magic to ensure the binaries are updated any time a version is updated in go.mod.
For some of the Node dependencies, a likewise approach could likely be used as I had to explore this to solve #1517.

I agree this would be a positive improvement.
I'll note that anyone wanting a guarantee of using the correct tools has options for executing most tasks, including unit tests, linting, codegen, and more in containers using hack- variants of most make targets.
Even so, there is no harm in improving the situation for those who do not wish to use those containerized options for whatever reason. (Speed could be a factor on some local stacks.)
@hiddeco feel free to assign to yourself if this is something you're especially intent on improving.


Removed unused variables, add some constants numbers

I added check storage->frame.current_rt in rasterizer_scene_gles2.cpp, because this variable was checked later in code e.g. line 3319 or 3335
Also there are also new return checked from function unzGoToNextFile
0.7071 was changed to Math_SQRT12
Changes in text_edit are caused because in Valgrind I got more than hundred reports about using uninitialised variables

==18375== Conditional jump or move depends on uninitialised value(s)
==18375==    at 0x2D38FBB: TextEdit::times_line_wraps(int) const (text_edit.cpp:4327)
==18375==    by 0x2D39EDE: TextEdit::cursor_set_line(int, bool, bool, int) (text_edit.cpp:4491)
==18375==    by 0x2D3B6CA: TextEdit::set_text(String) (text_edit.cpp:4801)
==18375==    by 0x27D61DC: VersionControlEditorPlugin::VersionControlEditorPlugin() (version_control_editor_plugin.cpp:534)
==18375==    by 0x27D194A: VersionControlEditorPlugin::get_singleton() (version_control_editor_plugin.cpp:83)
==18375==    by 0x217B00D: EditorNode::EditorNode() (editor_node.cpp:6074)
==18375==    by 0x14251D3: Main::start() (main.cpp:1677)
==18375==    by 0x13E4957: main (godot_x11.cpp:55)
==18375==
==18375== Conditional jump or move depends on uninitialised value(s)
==18375==    at 0x2D3AA0B: TextEdit::get_column_x_offset_for_line(int, int) const (text_edit.cpp:4645)
==18375==    by 0x2D39937: TextEdit::cursor_set_column(int, bool) (text_edit.cpp:4449)
==18375==    by 0x2D3B6E0: TextEdit::set_text(String) (text_edit.cpp:4802)
==18375==    by 0x27D61DC: VersionControlEditorPlugin::VersionControlEditorPlugin() (version_control_editor_plugin.cpp:534)
==18375==    by 0x27D194A: VersionControlEditorPlugin::get_singleton() (version_control_editor_plugin.cpp:83)
==18375==    by 0x217B00D: EditorNode::EditorNode() (editor_node.cpp:6074)
==18375==    by 0x14251D3: Main::start() (main.cpp:1677)
==18375==    by 0x13E4957: main (godot_x11.cpp:55)

Thanks!


match no-leading-zero floats, e.g. '.2', as a number

Related to issue https://github.com/thedersen/backbone.validation/issues/340

This is fixed in a fork i'm maintaining (tried contact this repository admins without luck): https://github.com/blikblum/backbone.validation
The updated package can be found at https://www.npmjs.com/package/backbone.validation
To use with node: npm install backbone.validation


WebMoney

In module webmoney, please add function processTransaction

I have updated WebMoney processTransaction method - https://github.com/boxbilling/boxbilling/commit/a6b62fbce2d8cf92307bda19498dc09e6b532243 Could you check if the problem persists?

$data['LMI_SUCCESS_URL'] =	$this->config['success_url']; maybe return_url ?
and
Invoice status:
Unpaid
[14-Jan-2015 12:37:32 UTC] 8 Undefined index: secretWord /home/netengi/domains/new.netengi.com/public_html/bb-library/Payment/Adapter/WebMoney.php 186

I changed URL https://github.com/boxbilling/boxbilling/commit/d5c3e1bb684e4b69c61bbc3db38135a92a0738bf and added new field to WebMoney settings where you can enter secret word https://github.com/boxbilling/boxbilling/commit/c0208dcf4440e26c7f1df7797d2a65da6687294b. Could you check if it fixes your problem?

I see that both transactions are $0.00. Is it intentional or a bug in BoxBilling?

bug

Could you submit ticket from members area providing your IPN and/or credentials so that we could check what is causing the problem.

ticket 5819

Thanks to your cooperation I was able to resolve this issue. It seems that WebMoney changed their validation hash algorithm from md5 to sha256 ant it was the reason why it was failing to process. Please check and confirm if it fixed the problem once you will do that I will merge fixes to master branch and release new version.

Thanks, works


caption.download throw errors

Hi, I've installed pytubefix version 5.1.2. Here's the test code:
from pytubefix import YouTube
from pytubefix import Channel

url = 'https://www.youtube.com/watch?v=JRAUvWLULEk' # caption failed

def test_YouTube():
    yt = YouTube(url, on_progress_callback=show_download_progress
                    , use_oauth=True, allow_oauth_cache=True)
    video_stream = yt.streams.get_highest_resolution()

    output_path = r"./"
    # video_title_file = "test.mp4"
    # video_stream.download(output_path=output_path, filename=video_title_file, max_retries=5)

    for caption in yt.captions:
        caption_code = caption.code
        if 'en' in caption_code:
            print(f':{caption} {caption_code}...')
            caption.download(title=yt.title,output_path=output_path)
            print(f'{caption_code} downloaded successfully.')

if __name__ == '__main__':
    test_YouTube()

Below is the error message I get when running the code:
PS D:\code\python\project\some-reverse-works\examples\pytube> python .\test_pytubefix.py
:<Caption lang="English (auto-generated)" code="a.en"> a.en...
Traceback (most recent call last):
  File "D:\code\python\project\some-reverse-works\examples\pytube\test_pytubefix.py", line 62, in <module>
    test_YouTube()
  File "D:\code\python\project\some-reverse-works\examples\pytube\test_pytubefix.py", line 19, in test_YouTube
    caption.download(title=yt.title,output_path=output_path)
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python310\lib\site-packages\pytubefix\captions.py", line 179, in download
    file_handle.write(self.generate_srt_captions())
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python310\lib\site-packages\pytubefix\captions.py", line 61, in generate_srt_captions
    return self.xml_caption_to_srt(self.xml_captions)
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python310\lib\site-packages\pytubefix\captions.py", line 101, in xml_caption_to_srt
    for child in list(root.iter("body"))[0]:
IndexError: list index out of range

Originally posted by @jinhang87 in https://github.com/JuanBindez/pytubefix/issues/69#issuecomment-2080351497

try pytubefix==5.2rc1

Seriously, you're the best!

Thanks to @JuanBindez for the quick update, but after updating to 5.2rc1, I still can't get the a.en caption for the videos. I've tried several videos, even changed a few IPs, but it doesn't work.

hello, try using this pytubefix==5.6rc2, where @felipeucelli made PR #85 that fixes this problem, and see if it is normalized and tell us if it is resolved.


Feedback (Japanese language)

The versions of Python that support auto-instrumentation are 3.11 and below.

The Japanese documentation states "以降" (ikou), which implies versions greater than 3.11 to Japanese readers.
Therefore, it would be more accurate to use "以下" (ika) instead of "以降" to convey the correct meaning.

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

ID: de899739-e7a0-9b31-bd40-e08d0b2af1d6
Version Independent ID: 340b0e92-5052-eb01-7850-3871b2cce5a5
Content: Monitor Azure app services performance Python (Preview) - Azure Monitor
Content Source: articles/azure-monitor/app/azure-web-apps-python.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @AaronMaxwell
Microsoft Alias: aaronmax

@jun110
Thank you for bringing this to our attention.
I've delegated this to content author, who will review it and offer their insightful opinions.


Add Scorecard Github Action

It'd be nice to use this to see if changes we are making are affecting our 'score'
https://github.com/ossf/scorecard?tab=readme-ov-file#scorecard-github-action

Thanks for reminding me about this, I wanted to look back at the action and allstar to compare them. I think what we have is fine.


Fix P4RT-5.2: Traceroute Packetout test

The commit fixes the following issues in the Traceroute packetout test

Modify the test to use router MAC for dst MAC in the packet. For the traceroute packet to be forwarded correctly, the dst MAC should be set to the router/system MAC instead of a random value
Set the TTL to be 2 instead of 1 in the traceroute packet so that packet does not get resent to the CPU and instead gets forwarded correctly to the ATE.

Please note the following changes in the test only causes the ipv4 test to pass and not the ipv6 test with Arista. There is a pending fix in EOS that has been validated to fix the ipv6 traceroute packetout test. @

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 56.88%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1236

Relevant Lines:
2173

💛  - Coveralls

/gcbrun

Hello @Ankur19 did we ensure that this PR will successfully run for all NOS? Google doesnt require to query the router mac address through gNMI.Get() before performing a traceroute. This seems to be a requirement for just one implementation. If so, why is this not a deviation? Since merging of this PR deviates from the original requirements shared w/ different implementations, this PR has now pushed a breaking change for other implementations. Hence I insist that this PR is rolled back and replaced w/ a deviation for the implementation that needs it.

@prakashbadri-arista, I request you to create a deviation instead for this change. This deviation then should be tracked via a Google vendor bug to track long term fix. @rszarecki for vis.

@sachendras What is the exact regression here with the other vendor ? I would like to avoid introducing a deviation if we could find a test input that works for everyone. The test currently uses a random dmac for the traceroute packet. I was assuming using the router mac should not break another implementation.


Fix license headers in pinot-kafka-3.0

License header fixes and some other minor formatting corrections.

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

Project coverage is 0.00%. Comparing base (59551e4) to head (6a71e4d).
Report is 1101 commits behind head on master.

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (6a71e4d). Click for more details.
HEAD has 53 uploads less than BASE

Flag
BASE (59551e4)
HEAD (6a71e4d)

integration
7
1

integration2
3
1

temurin
12
1

java-21
7
1

skip-bytebuffers-true
3
1

skip-bytebuffers-false
7
0

unittests
5
0

unittests1
2
0

java-11
5
0

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #14112       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436        3     -2433
  Lines        133233        6   -133227
  Branches      20636        0    -20636
=============================================
- Hits          82274        0    -82274
+ Misses        44911        6    -44905
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <ø> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <ø> (ø)

java-11
?

java-21
0.00% <ø> (-61.63%)
:arrow_down:

skip-bytebuffers-false
?

skip-bytebuffers-true
0.00% <ø> (-27.73%)
:arrow_down:

temurin
0.00% <ø> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Create a Getting Started for new devs

Since we decided to make F3D a project open to everyone of all levels, we should provide a getting started guide that makes no assumption on the knowledge and skills of the developper using the guide

fixed by #999


feat: support datadog rum for browser client

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

Project coverage is 85.91%. Comparing base (a6b4364) to head (966e8c7).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #291   +/-   ##
=======================================
  Coverage   85.91%   85.91%
=======================================
  Files          11       11
  Lines        3281     3281
=======================================
  Hits         2819     2819
  Misses        462      462

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


Use React to Render Nested Components - Editor locks up and crashes browser

Describe your problem and - if possible - how to reproduce it
Completed the challenge and clicked "Run The Tests", the editor locked up, and then the browser crashed.
I reloaded the challenge and my code was still in there.
This time the editor was locked up and crashed out as soon as I loaded the challenge page.
I cleared my browser cache/cookies and restarted my computer, but the challenge is still locked up.
Add a Link to the page with the problem
https://learn.freecodecamp.org/front-end-libraries/react/use-react-to-render-nested-components
Tell us about your browser and operating system

Browser Name: Chrome
Browser Version: Version 66.0.3359.181 (Official Build) (64-bit)
Operating System: Mac OS 10.13.4

Works fine on my PC too.
Try with another explorer and see if it does the same. Chrome Extentions can also be the problem here. Deactivates all of them and try again. Good luck !

Cleared cache three times and then it worked in Chrome.


Documentation for Xcode 8

Hoping to get feedback for this preliminary, working set of instructions for building for Swift 3 and/or Xcode 8.
Some questions:

Where should these instructions live?
Are we going to allow people to use CocoaPods today to build Realm for Swift 3?

@jpsim @tgoyne @bdash

Building Realm from source for Xcode 8 Beta
Important: Realm for Xcode 8 is not officially supported; the instructions below are intended for developers who are working to port their applications to Swift 2.3 or Swift 3, or otherwise using Xcode 8. During the preview period, the only way to obtain Realm for Xcode 8 is by building from source; we are not supporting dependency managers or providing pre-packaged binaries.
Prerequisites: you must have a valid Apple Developer account, with certificates for iOS and/or macOS. Go to https://developer.apple.com and update your certificates if necessary.

Clone the Realm Cocoa repository. (Run the Terminal command git clone git@github.com:realm/realm-cocoa.git in whatever directory you want the repository to be stored in.)
Open build.sh (it is located in the root project directory).
Find the line that reads: CODESIGN_PARAMS="CODE_SIGN_IDENTITY= CODE_SIGNING_REQUIRED=NO", and change it to just read CODESIGN_PARAMS="". (It is line 29 in the file.)
Open the Realm Cocoa Xcode project (Realm.xcodeproj).
If a dialog window appears asking whether to "Convert to Current Swift Syntax?", press the "Later" button.
Click on the Realm project in the Project Navigator.
Click on the "Realm" target.
Click on the "Build Settings" tab (make sure "All" options are shown, not just "Basic"), and scroll down to the "Signing" section.
Expand the "Code Signing Identity" field by clicking the triangle.
For the "Debug" and "Release" sub-options, choose a "Mac Developer" identity from the drop-down menu (in most cases, just choose the one within the "Automatic" section).
If you wish to build Realm for an iOS app (iPhone, Apple TV, Apple Watch), for the "iPhone* SDK" sub-options choose an "iPhone Developer" identity from the drop-down menu (in most cases, choose an appropriate identity from within the "Identities in Keychain" section).
Click on the "General" tab.
Under the "Signing" category, press the"Enable Development Signing" button, and then uncheck the "Automatically Manage Signing" checkbox.
Under "Signing (Debug)" and "Signing (Release)", choose the Apple Developer team associated with the certificates you chose in steps 10 and 11 from the drop-down menus. (If there is only one team listed, just choose that one.)
If you want to build Realm Swift, repeat steps 6 through 14 for the "RealmSwift" target. (If you want to build for Swift 2.3, activate the "Use Legacy Swift Language Version" build setting.)
Choose the correct scheme (Realm or RealmSwift) and device. If you want to build Realm for an OS X application, choose "My Mac". Otherwise choose the appropriate "Generic *OS Device".
Build the project.
In the Project Navigator, under the "Products" group, right-click on "Realm.framework" and select "Show in Finder" to open up the folder containing the built frameworks.
Drag Realm.framework (and, if using Realm Swift, RealmSwift.framework) into your Xcode project. Follow the instructions at https://realm.io/docs/objc/latest/#dynamic-install to complete setup.

Where should these instructions live?

Our installation instructions are kept in one place for consistency. It's in https://realm.io/docs/swift/latest/#installation
The source is in https://github.com/realm/realm.io-middleman/blob/master/source/en/docs/objc/latest/index.html.md.erb

Are we going to allow people to use CocoaPods today to build Realm for Swift 3?

Yes why wouldn't we?

I realized that this works with CocoaPods (if you do the same types of permission munging as described above). But on #3752 people are having trouble even getting their projects to compile.

I realized that this works with CocoaPods (if you do the same types of permission munging as described above).

Why would that be necessary? CocoaPods doesn't reuse our Xcode project.

It doesn't, but you get the same code signing errors if you try to build a project in Xcode 8 that has the development versions of Realm or RealmSwift as a dependency. If you have any ideas about how to suppress them without having to modify the code signing settings for the Pods project, I would love to hear them.

Does this mean that CocoaPods in general doesn't work with Xcode 8 right now? If this is unique to our podspecs, what in there is causing this to happen?

Well, I just set up an empty pods-based project that depends only on the Alamofire pod and I got the same error. So it doesn't look like a Realm-specific issue.

Looks like they are aware of the issue: https://github.com/CocoaPods/CocoaPods/pull/5528
Not sure if we want to give our users workaround instructions or have them use a development version of CocoaPods?

Just point to CocoaPods support being blocked on a CocoaPods update.

CocoaPods has released support for Xcode 8 in 1.10.beta.1.
Can you guys confirm if this issue still exists?

Between Xcode 8b3 and 1.10.beta1, the issue should be gone. We should have 'official' instructions up shortly; I'll post a link when they are live.

@austinzheng Thanks for the update Austin. This helps us time our migration efforts accordingly since we are currently blocked on some new feature dev leveraging new iOS 10 SDKs with this.

I talked to our other engineers and we've decided we won't be posting "official" installation instructions until Xcode 8 is released. However, anyone who wishes to build from source can try the instructions here, which should work with Beta 3 (and 4).

I ran into a few issues with this, using the advised instructions from @austinzheng. Some additional details that may help some people:

To run build.sh using the XCode beta, you need to set the default xcode version to beta using the command
sudo xcode-select -switch /Applications/Xcode-beta.app

This obviously has nothing to do with Realm.

After I cloned the realm repo, I had to update the submodules via
git submodule init && git submodule update

This is documented somewhere but not on the instructions above or the main source at https://realm.io/docs/swift/latest/#installation

The xcode project file has a number of duplicate devices available, and xcodebuild was unable to determine which was supposed to be built. I had to remove all duplicate simulator devices (so that only one remained for each type, e.g, iphone 6, iphone 6s, etc.

The last step in particular wasn't documented anywhere and I was unable to run build.sh until removing those devices.

Thanks @algoterranean !
FYI you can use gem install snapshot; snapshot reset_simulators to reset all your simulators, answer from http://stackoverflow.com/questions/27614197/duplicate-iphone-simulators-appeared-on-my-xcode

Hey everyone. Xcode 8 GM is out and this still doesn't seem to be resolved.
Any notes on how to get RealmSwift compling under Xcode 8 for either Swift 2.3 (Legacy) or 3.0 ?

Was able to use the intstructions posted by @austinzheng to make it compile and run the app on my iOS Device. Problem is, I can't get it to work on the Simulator. I'm guessing because this isn't a Universal framework ? Thoughts on how to achieve that?

@freak4pc please wait until our official Xcode 8 support with a finalized API, installation instructions and documentation later this week.

I eventually was able to build it yesterday with some playing around, but I'll still wait for a more solid build plan before proceeding further. Thanks @jpsim .

Hi,
The steps didn't work with me, I got 5 errors as shown in the attached image:

Any help?

@Maryom  git submodule update --init --recursive

@jpsim Thanks for your fast reply. It worked perfectly. Thanks again.

Hey,
I'm getting the following error from sh build.sh ios-swift
error: @escaping attribute only applies to function types
    public func addNotificationBlock(block: @escaping NotificationBlock) -> NotificationToken {
                                             ^
/Path/Realm/realm-cocoa/RealmSwift/Migration.swift:180:57: error: @escaping attribute only applies to function types
internal func accessorMigrationBlock(_ migrationBlock: @escaping MigrationBlock) -> RLMMigrationBlock {
                                                        ^

** BUILD FAILED **

The following build commands failed:
	CompileSwift normal arm64
	CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler

@helloandrewpark you're not on the latest version of master...

Hi again 😅
I got another error:
ld: framework not found Realm for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation)
Any help?

Hey Guys,
Seems like the latest version of CocoaPods solves the "workarounds" of setting swift version.
Just do :
sudo gem update --pre cocoapods (should update you to v<IP_ADDRESS>.rc.2)
Your Podfile should still include an explicit reference to the GitHub repo e.g.
  pod 'Realm', git: 'https://github.com/realm/realm-cocoa.git', branch: 'master', submodules: true
  pod 'RealmSwift', git: 'https://github.com/realm/realm-cocoa.git', branch: 'master', submodules: true

Also, you might want to add the new .swift-version file with the appropriate version you would be using (defaults to 2.3)
More info here:
https://github.com/CocoaPods/CocoaPods/pull/5841

Hey @freak4pc,
My cocoa pods version is v<IP_ADDRESS>.rc.2:
/Users/mariam/.rvm/gems/ruby-2.2.1/gems/cocoapods-1.1.0.rc.2/lib/cocoapods.rb
I added these lines to my podfile:
pod 'Realm', git: 'https://github.com/realm/realm-cocoa.git', branch: 'master', submodules: true   pod 'RealmSwift', git: 'https://github.com/realm/realm-cocoa.git', branch: 'master', submodules: true
And I got these errors 😖👇🏼

Any help?
Thanks.

Uhm, interesting. That worked fine for me.
Do you mind trying pod deintegrate and pod install again ? @mamaral

We've maintained support for Realm Swift across Xcode 8 betas since WWDC, making adjustments to continue compiling and passing tests for Swift 2.2, 2.3 and 3.0 as new betas came out.
However, due to the amount of churn Swift 3 has seen in the last 3 months, we held off on thoroughly reviewing all our Swift 3 API changes and accommodating both Xcode 7.3.1 and Xcode 8 into our continuous integration, testing, docs and release packaging processes.
With Xcode 8 GM last week, we decided to make a push to finalize our Swift 3 APIs along with the other integration points mentioned above.
That work is now mostly complete and we're preparing a 1.1.0 release for tomorrow, at which point our Swift 3 APIs will be final, binaries will be made available for Swift 2.3 and 3.0 in our release zips, and docs will be updated to reflect the new APIs.
Thanks for your patience.
JP

Woohoo! that's amazing @jpsim! Thanks :)

@freak4pc Yes I tried and I got the same error. Anyways, thanks for your help. I think it's better to wait for tomorrow release :)

@jpsim That's awesome news :)


Bump Rust edition to 2021

There's a bunch of quality of life changes and cleanup that can happen after this goes in. I can get those in with this if desired but they aren't necessary and it will touch a LOT of stuff.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I'm going to update cargo at the same time as merging this... Which will require me updating the build servers and CMakeLists first. Not sure if that's required to merge this PR or not.

Updating Cargo shouldn't be required unless you're running a version so old it doesn't support edition 2021 but that would be REALLY old.


Please change the URL in the Wiki build instructions

On this repo's Wiki, the section titled “How to get the MacVim source code” still references @b4winckler's repo. I can see this tripping up some unfortunate soul who doesn't pay attention.
Please edit that URL to point to macvim-dev/macvim ☺.

Thanks, done.


How to include multiple container name in single expresion

as in alert rule you specified absent(container_memory_usage_bytes{name="jenkins"})  how to include multiple names in single expression so i don't repeat the step again for another container , is there any step where we can include all container in one expression like absent(container_memory_usage_bytes{name="jenkins", name="nginx", name="nginx2"}) to reduce line of code . if yes please provide sample code .TQ

I do not believe this is possible, you would need a rule for each container.
You could use a regex to match multiple containers like absent(container_memory_usage_bytes{name=~"alerthub|authelia|jenkins"}) but this will not provide the intended result because the absent query will return false if any results are found.


WFLY-15401 Simplify NonFunctionalTimerService and exclude it from Tim…

…erServiceRegistry
https://issues.redhat.com/browse/WFLY-15401

we should wait for https://github.com/wildfly/wildfly/pull/14757 to be merged and retest this PR.

@tadamski  please review.


expose more postgresql initdb flags

The line https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/databases/postgresql.nix#L208
Does not use the value of i18n.defaultLocale but maybe it should?

Probably not (you don't always init new DB, sometime you want to start postgres with existsing DB, and locale guaranties are lost). But exposing initdb additional flags as nixos options would be an improvement.

Nevermind, it does set it correctly, I made a mistake.
I'll rename this issue to be about exposing additional flags.

This would be nice as you can pass -k (if I remember correctly) and this enabled data checksums in postgresql and can be done only on cluster init.

Are there any updates to this issue, please?

@mmahut the PR https://github.com/NixOS/nixpkgs/pull/65245 is aimed to fix that, but it is still in review phase

Going to close as it has been a long time and I'm not sure if this is relevant anymore.


TypeScript type declaration file

If you want I can write a TypeScript type declaration file for this package so that TS developers can utilise the type-checking feature of the language as they use this package. Let me know if you are interested.

Hey！
thanks for your issues.
I'm really interested about  type-checking feature.
Yes, I'll be happy with that.
My English may be a little strange, because I am Japanese.
I'm sorry if my English is difficult to understand.

I will start on it then.


Apina mp4 regex fails

If the apina url contains mp4, regex ends with .mp leaving out the number.

Fixed in 0a7dd09b72c354d60c6b3f9ac13cd5a2fef63402


cargo build updates Cargo.lock?

Originally reported in this tweet: https://twitter.com/duelinmarkers/status/795313099477762049
if you:
$ git clone https://github.com/sunng87/cargo-release.git
$  cd cargo-release/
$  cargo build
$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   Cargo.lock

A diff: https://gist.github.com/duelinmarkers/fcb8b0da4e905c9c5d6f0590f1219399
Given that Cargo.lock exists and we didn't cargo update, the lockfile shouldn't be modified. I can't tell why this is happening.
/cc @sunng87 since it's their library.

Yeah cargo build will update the lock file if the manifest has also changed as part of routine cargo build. If though the manifest was the exact same as before and there was a lock file then this is definitely a bug!
To clarify, are we sure there were no updates to the manifest since the lock file was created?

-rw-r--r-- 1 steve steve  8582 2016-11-07 10:19:51.015593067 -0500 Cargo.lock
-rw-r--r-- 1 steve steve   443 2016-11-07 10:19:43.643657517 -0500 Cargo.toml

so yeah, lockfile was created 8 minutes later?

On a fresh clone:
$ ls -a --full-time
-rw-r--r-- 1 steve steve  3299 2016-11-07 18:05:47.723095806 -0500 Cargo.lock
-rw-r--r-- 1 steve steve   443 2016-11-07 18:05:47.723095806 -0500 Cargo.toml

they have the exact same time. which everything does, since it's a fresh clone

I can reproduce this issue too. Cargo updates my dependencies to latest version even when I hard-coded a version number in Cargo.toml. I was using a crate.io mirror provided by ustc.edu.cn as you can see from Cargo.lock. Not sure if it has something to do with this issue. Cargo.lock got modified on cargo build on both mirror and original repository.

@sunng87 to clarify, was Cargo.lock modified after generation if Cargo.toml was not changed? Or did you find that when changing Cargo.toml it then later changed the lock file? (the latter is expected where the former would be a bug)
Also, do you have the exact diff in the manifest that's happening?

@alexcrichton I did a clean git clone and then cargo build without changing anything in Cargo.toml, the Cargo.lock changed.
All crates seems to be updated to latest version and mirror url is changed to default central repository:
https://gist.github.com/sunng87/8b5dfca7d46625c4b459a8f460d791b2

@sunng87 do you have a repo I can poke around in? A fresh git clone doesn't necessarily imply Cargo shouldn't modify Cargo.lock because it could be in a checked-in state that Cargo.toml and Cargo.lock are out of sync

@alexcrichton does the repo in the OP not reproduce for you?

Ah! Sorry I must have missed that...
@sunng87 it looks like you have a number of non-crates.io URLs in your Cargo.lock:
dependencies = [
 "clap 2.2.5 (registry+git://crates.mirrors.ustc.edu.cn/index)",
 "quick-error 0.1.4 (registry+git://crates.mirrors.ustc.edu.cn/index)",
 "regex 0.1.65 (registry+git://crates.mirrors.ustc.edu.cn/index)",
 "semver 0.2.3 (registry+git://crates.mirrors.ustc.edu.cn/index)",
 "toml 0.1.28 (registry+git://crates.mirrors.ustc.edu.cn/index)",
]

When you do a normal cargo build that's not configured to use that mirror, then the entire lock file is no longer applicable, so it's as-if it was all thrown out.
This may have happened if you're using registry.index inside of .cargo/config, but instead of that it's recommended to use source replacement nowadays (which solves this problem)

@alexcrichton This makes sense.The Cargo.lock is created in early days when source replacement haven't been introduced in.
I think we can close the issue now.

Ok!

Ah! So simple!


Adding a check to make sure the ViralAI data being pulled is the latest one

Add a check into the ViralAI fetching script to make sure the release date of the DRS URL is the latest one. Due to an issue with ViralAI, we been pulling the Sept 8th release for a month now.
@anwarMZ this can probably be a VirusMVP issue too since we use the same fetch script.

Done. Script will crash if the virusseq GUID doesnt match the viralAI one.


sg_tenant query param missing in kibana share search (discovery)

In Kibana (multitenant) sharing visualizations or dashboards using the "share" button conveniently sets the sg_tenant query parameter in the link.
Unfortunately, this is not the case when sharing searches in the discovery tab.

@faxm0dem we look into it, thx for reporting this

we're using 6.3.2 for the moment

@faxm0dem Sorry about the delay - I'm having a bit of trouble reproducing this issue.
Testing with 6.3.2 I do get the sg_tenant query parameter in the discover tab, both for long and short URLs

Do you see any JavaScript errors in the browser's console?
What browser are you using?

I just tried with firefox and chromium with the same result.
I don't see any erros in the console.
Thanks for trying to reproduce. I'll upgrade ES+kibana+SG soon, and report back. In the meantime either we leave the issue open, or I'll reopen it if still present.

Using 6.6.0, the situation seems worse: no tenant in any "share" link

@faxm0dem I'm afraid you are right. Kibana has changed the share panel completely, but I'm working on a solution. Let's leave this issue open and I'll post back here as soon as I have more information.

wat? you mean elastic devs changed everything again? I don't believe you 😂

I think we have a solution for this now.
PR: https://github.com/floragunncom/search-guard-kibana-plugin/pull/177

@mgustafsson1 this fix has been released now, right?

@jochenkressin Yes! Sorry, I should have closed this!


feat(logger): add a json macro to generate json object

What this PR does / why we need it:
Add a json macro to generate json object.
example:
     let json_obj = json!({
         "key_01", value_01;
         "key_02", value_02
    });

Which issue(s) this PR fixes:

Fixes #
Which docs this PR relation:
Ref #
Which toolchain this PR adaption:
No Breaking Change
Special notes for your reviewer:

/lgtm


MORE_RESULTS_AFTER_LIMIT Erroneously Returned

When setting a LIMIT in the query, the JSON API always returns 'MORE_RESULTS_AFTER_LIMIT' for the the moreResults property in the response even though there are no more results.

This issue still exists btw.
At the moment this means always one extra call (with 0 results) to know that there are no more results.

This is now fixed. An important note though: more_results will always give you a conservative answer. So it is still possible that MORE_RESULTS_AFTER_LIMIT is returned instead of NO_MORE_RESULTS if Datastore was unable to determine if there were more results (due to time or workload constraints).

Sry, for the late answer but i just wanted to change my code to finally use the NO_MORE_RESULTS answer and i still get MORE_RESULTS_AFTER_LIMIT every time, even if there is just one entity for the specific kind.
Would be great if you maybe have any numbers on what the odds are that Datastore can't determine if there are more results. Because if i need to run another call 90% of the time because Datastore doesn't know if there are more results, there is no reason to change the code to use NO_MORE_RESULTS.
Also i should note that i am currently not on a paid plan because the free contingent is enough till the app goes into production. Maybe the "free" Datastore instances are always under heavy workload?

Most of the time NO_MORE_RESULTS should be returned. What client library are you using? The results are only correct for clients that use Cloud Datastore API v1beta3. Clients that are still using the v1beta2 API will continue seeing MORE_RESULTS_AFTER_LIMIT.

Ty, updating to v1beta3 fixed it for me.


Global verbose mode?

Is it possible to enable verbose mode globally for all requests?

It is no possible atm.


Revamp SSI docs

SSI docs have a lot of room for improvement:
1. API Docs
Today our API docs render the latest swagger doc from the SSI service. Instead, we should switch to a release-based model that points to the docs from a recent release. This will allow us to annotate the content that's in the swagger with more helpful information to make the docs more usable.
As a reference, see the MATTR docs which I think do a pretty good job of this. Well organized categories, detailed descriptions and examples, and overall it just feels a lot more approachable than what we've got today. Similarly, the Microsoft Entra docs are a lot more approachable, human-readable and interactive.
2. Project homepage
From landing on the dev site, getting to docs from the SSI service is 3 clicks away on the projects page, but clicking on the SSI project just points to GitHub. I believe we should have an easier to access homepage that's a one stop jumping off point for all things SSI.
There is also a separate docs tab so it is confusing on where I do actually find out what information is pertinent for learning about the SSI service.
I'd like to see something like homepage -> projects -> project specific homepage, where that homepage has all associated information.
3. Tutorials & Content
SSI Specific
We have one tutorial and it quickly gets out of date, it should similarly be tagged to a release of the SSI Service to avoid this issue.
One tutorial is not sufficient given the rich complexity of the service. I can identify at least 8 tutorials we should have, if not more:

Create a DID
Create a Schema
Create and issue a Credential
Revoke a Credential
Verify a Credential
Set up a Presentation Exchange Request, Verify a Presentation Submission
Set up a Credential Manifest Request, Verify a Credential Manifest and Issue Credential(s)
Set up a DID Well Known Configuration

Other ideas can include connecting to a HSM, using different databases, integrating into different transport systems (like OIDC or Web5) or configuring a cloud provider. Lots of opportunity for content here.
More General
More broadly, there is room to have rich educational material on the site, useful to both technical and less-technical audiences. Trinsic does a really good job at this with the entire "learn" section on their site.
Similarly, the "concepts" and "tutorials" section on Microsoft Entra's site are informative and helpful.

we intentionally have not covered the independent SDKs like dwn or ssi. Our focus is on the Web5 SDK with plans to cover SSI functionality when it's integrated into web5.js.
If this plan isn’t ideal, I'm very happy to discuss.

I believe SSI should be covered separately from its usage within the Web5 SDK, since the SSI Service is designed as a standalone product that can be run by any individual/organization that wants a full management suite for DIDs + VCs.
I cannot speak to relative prioritization, only that it would be valuable to have such documentation as we begin to see more usage of the service. Maybe @michaelneale or @frankhinek have a better sense of relative prioritization (or if there's a way we can do both).

I believe SSI should be covered separately from its usage within the Web5 SDK, since the SSI Service is designed as a standalone product that can be run by any individual/organization that wants a full management suite for DIDs + VCs.
I cannot speak to relative prioritization, only that it would be valuable to have such documentation as we begin to see more usage of the service. Maybe @michaelneale or @frankhinek have a better sense of relative prioritization (or if there's a way we can do both).

Fair enough. Will begin looking into coverage for the SSI service. Thanks, @decentralgabe!

yes I think this is distinct in many ways: the ssi service is something to be stood up primarily by those who wish to issue VCs to their users, and typically server side developers and integrators.


MatchPatternWord should match on Matchable instead of Any

Current implementation look like this:
final class MatchPatternWord {

  inline def apply(inline right: PartialFunction[Any, _]) =
    ${ org.scalatest.matchers.MatchPatternMacro.matchPatternMatcher('{right}) }

  override def toString: String = "matchPattern"
}

This generates a warning with compiler option "-source:future".
Let's change Any to Matchable

Corresponding change
https://github.com/scalatest/scalatest/pull/2350


Add well known protos to Node and Ruby tools packages

This fixes #6739 and #6740. When the tools package is built during our artifact build, the well known protos are copied from third_party/protobuf.
Note, depending on something (protoc compilation options, possibly), users may need to explicitly specify the path containing google/protobuf in the proto_path for the Node code generation to work with these.

LGTM.

We need to regenerate project.json,  generate_projects.sh check   is failing on master.


fix(ci): fix sign script - avoid interpreting '{*}$argv' too soon

Signed-off-by: Vicente J. Jiménez Miras<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area rules

/area tests

/area proposals

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

@vjjmiras: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: vjjmiras
To complete the pull request process, please assign jonahjon after the PR has been reviewed.
You can assign the PR to them by writing /assign @jonahjon in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

.circleci/OWNERS

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

LGTM label has been added.  Git tree hash: 1e690aeba0c03c8e18e041ef972f88ebf2e7f460

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, vjjmiras
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

.circleci/OWNERS [jasondellaluce]

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

@jasondellaluce Note that we are missing the release notes!

/milestone 0.32.1


Address bar to filter location

Hi,
the plugin is very interesting! Do you think it is possible to add an address bar where users can type the address and the map will update to the location (AKA geocoding https://leafletjs.com/plugins.html#geocoding)?
What I'm trying to do is to add a leaflet map with your plugin in a form page of Grav, take the lat and long values (entered by the user) and send them via email together with the other values (name, surname, and other form fields).
I'm really not a php person, but I really would like to help you with this feature (if you are interested)
Thanks

@ghtmtt  Sorry for this bad delay. But your requested extra functionality is not consistent with the aims of this plugin, I'm afraid.


#113: allow to set multiple methods for single route at once

As discussed in #113

Could you please rebase your changes onto the latest master reference?

Closing in favor of #115.


Visualize flow is broken since results in SouthPane

Sorry I forgot to exclude query results from storing result data in local state, https://github.com/airbnb/caravel/pull/1552 should solve it.

VisualizeModal needs the column information, but not the data, perhaps ResultSet should only cache results.data, not the whole results object that also contains the column info

Since we don't want user to re-run query everytime one refreshes the page, I think best approach would be not storing query result data to local state, only do it for data preview of tables.


Add tkn-pac repo delete command

Closes #523

Changes

Submitter Checklist

[ ] ♽  Run make test lint before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI
[ ] 📖 If you are adding a user facing feature or make a change of the behavior, please verify that you have documented it
[ ] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[ ] 🎁 If that's something that is possible to do please ensure to check if we can add a e2e test.
[ ] 🔎 If there is a flakiness in the CI tests then don't necessary ignore it, better get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it. (token rate limitation may be a good reason to skip).

 {"level":"info","ts":1652790278.393644,"caller":"github/pr.go:107","msg":"Testing Github MaxKeepRun config with Github APPS integration on pac-e2e-ns-v9s58"}
    pr.go:110: assertion failed: error is not nil: GET https://api.github.com/repos/openshift-pipelines/pipelines-as-code-e2e-tests: 401 Bad credentials []

bad creds 🤔

probably github api, since it was working fine with other pass


Replace v-tooltip plugin with floating-vue

v-tooltip library has been replaced with floating-vue for Vue3 and we should replace it before we migrate to simplify the process.
We should follow https://floating-vue.starpad.dev/migration/migration-from-v2 migration guide and move to 1.0.0-beta.19 for Vue2 compatibility.

Existing commits to fix this issue

app https://github.com/rancher/dashboard/commit/369d126c68f91d7f84838f1df394b9f4bdaac4dc
unit tests https://github.com/cnotv/dashboard/commit/0e5e5c2fced3f5e0d7c3c7097ac757094e790ae8

Closing this issue, the floating vue migration is already completed.


Repeated calls to Map#apply results in crash

Here is a minification. In def wtf() I create an immutable map and then call .apply 4 times. The first 3 times work but the 4th results in a NoSuchElementException exception.
import utest._

final case class X(a: X.Y, b: X.Y)

object X {

  final case class Y(value: Int)

  def fromInts(i: Int, j: Int): X =
    X(Y(i), Y(j))

  new scala.collection.mutable.HashMap[Int, Int]()
}

object Bug extends TestSuite {

  def v(i: Int, j: Int) = X.fromInts(i, j)

  val v10 = v(1, 0)
  val v11 = v(1, 1)
  val v12 = v(1, 2)
  val v20 = v(2, 0)
  val v21 = v(2, 1)

  def wtf() = {
    val a = List(v10, v11, v12, v20, v21).iterator.zipWithIndex.toMap

    println(a(v10)) // Prints 0
    println(a(v10)) // Prints 0
    println(a(v10)) // Prints 0
    println(a(v10)) // Throws java.util.NoSuchElementException: key not found: X(Y(1),Y(0))
  }

  override def tests = Tests {
    "wtf" - wtf()
  }
}

There are some bizarre things to notice about this minification:

removing the new scala.collection.mutable.HashMap[Int, Int]() line avoids the bug
similarly, prefixing it with lazy val x =  avoids the bug
changing def v(i: Int, j: Int) = X.fromInts(i, j) to use X(X.Y(i), X.Y(j)) directly, avoids the bug
moving  the val v10 lines from object Bug to inside wtf() avoids the bug
removing the X.b field so that there's only one field avoids the bug
unboxing the X fields to just be two Ints avoids the bug
creating a map of less than 5 items avoids the bug (makes sense cos they use different implementations)
moving everything out of Bug into a different object Z, then changing the test line to "wtf" - Z.wtf() avoids the bug

Oh and btw, implicitly obvious but this minification while consistently crashing in JS, works when run from JVM.

Actually, further reduced slightly:
import utest._

final case class X(a: X.Y, b: X.Y)

object X {

  final case class Y(value: Int)

  def fromInts(i: Int, j: Int): X =
    X(Y(i), Y(j))
}

object Z {

  def v(i: Int, j: Int) = X.fromInts(i, j)

  val v10 = v(1, 0)
  val v11 = v(1, 1)
  val v12 = v(1, 2)
  val v20 = v(2, 0)
  val v21 = v(2, 1)

  def wtf() = {

    val a = List(v10, v11, v12, v20, v21).iterator.zipWithIndex.toMap

    println(a(v12)) // Prints 2
    println(a(v12)) // Prints 2
    println(a(v12)) // Prints 2
    println(a(v12)) // Throws java.util.NoSuchElementException: key not found: X(Y(1),Y(2))
  }
}

object Bug extends TestSuite {
  override def tests = Tests {
    "wtf" - Z.wtf()
  }
}

Finally, I'm seeing this with Scala.JS 0.6.32 and 0.6.31 on Scala 2.12.10.

I cannot reproduce this without utest. @japgolly can you confirm that removing utest makes the issue disappear?

I also cannot reproduce this without utest with Scala 2.12.10, either in the latest 0.6.x branch or master. I used the following code:
package helloworld

final case class X(a: X.Y, b: X.Y)

object X {
  final case class Y(value: Int)

  def fromInts(i: Int, j: Int): X =
    X(Y(i), Y(j))
}

object Z {
  def v(i: Int, j: Int) = X.fromInts(i, j)

  val v10 = v(1, 0)
  val v11 = v(1, 1)
  val v12 = v(1, 2)
  val v20 = v(2, 0)
  val v21 = v(2, 1)

  def wtf() = {
    val a = List(v10, v11, v12, v20, v21).iterator.zipWithIndex.toMap

    println(a(v12)) // Prints 2
    println(a(v12)) // Prints 2
    println(a(v12)) // Prints 2
    println(a(v12)) // Throws java.util.NoSuchElementException: key not found: X(Y(1),Y(2))
  }
}

object Bug {
  def main(args: Array[String]): Unit =
    println(tests)

  @noinline
  def tests: Any = {
    Z.wtf()
  }
}

I can't reproduce this without utest. My first thought was maybe this was a utest bug because I believe Tests { ... } is actually a macro that does some magic, but I've moved everything out of the utest TestSuite so that all it does is a normal method call, so there shouldn't be anything for the macro call to suspiciously transform. It's also a question of power too, is there anything utest could do to affect the internal logic of stdlib Map.apply? For those reasons I'm thinking (guessing) that maybe SJS is emitting slightly broken JS for stdlib?

I didn't manage to reproduce within the HelloWorld at the tip of 0.6.x branch (by adding uTest 0.7.2 as a dependency and running helloworld/test). :-s

Damn I was hoping the above would be enough. Ok no worries, let me get a project or maybe even docker image to reproduce this...

For the record, here's the error output
-------------------------------- Running Tests --------------------------------
2
2
2
X Bug.wtf 2ms
  java.util.NoSuchElementException: key not found: X(Y(1),Y(2))
    <jscode>.fillInStackTrace__jl_Throwable(webapp-base-test-test-fastopt.js:154737)
    <jscode>.init___T__jl_Throwable__Z__Z(webapp-base-test-test-fastopt.js:154864)
    <jscode>.init___T(webapp-base-test-test-fastopt.js:279760)
    scala.collection.MapLike.$default(webapp-base-test-test-fastopt.js:374469)
    <jscode>.$default__O__O(webapp-base-test-test-fastopt.js:384085)
    scala.collection.MapLike.apply(webapp-base-test-test-fastopt.js:374431)
    <jscode>.apply__O__O(webapp-base-test-test-fastopt.js:384037)
    <jscode>.wtf__V(webapp-base-test-test-fastopt.js:12112)
    <jscode>.file:///tmp/shipreq.sbt/webapp-base-test/js/target/scala-2.12/webapp-base-test-test-fastopt.js:156937:26(Unknown)
    <jscode>.apply__O(webapp-base-test-test-fastopt.js:215314)
    <jscode>.dropOutside__F0__O(webapp-base-test-test-fastopt.js:110553)
    <jscode>.run__sci_List__O(webapp-base-test-test-fastopt.js:110644)
    <jscode>.run__sci_List__O(webapp-base-test-test-fastopt.js:110640)
    <jscode>.file:///tmp/shipreq.sbt/webapp-base-test/js/target/scala-2.12/webapp-base-test-test-fastopt.js:110152:71(Unknown)
    <jscode>.apply__O(webapp-base-test-test-fastopt.js:215314)
    <jscode>.dropOutside__F0__O(webapp-base-test-test-fastopt.js:110553)
    <jscode>.file:///tmp/shipreq.sbt/webapp-base-test/js/target/scala-2.12/webapp-base-test-test-fastopt.js:110143:106(Unknown)
    <jscode>.apply__O(webapp-base-test-test-fastopt.js:215314)
    <jscode>.evaluateFutureTree__Lutest_framework_HTree__s_concurrent_ExecutionContext__s_concurrent_Future(webapp-base-test-test-fastopt.js:110065)
    <jscode>.file:///tmp/shipreq.sbt/webapp-base-test/js/target/scala-2.12/webapp-base-test-test-fastopt.js:110079:134(Unknown)
    <jscode>.apply__O__O(webapp-base-test-test-fastopt.js:215342)
    <jscode>.file:///tmp/shipreq.sbt/webapp-base-test/js/target/scala-2.12/webapp-base-test-test-fastopt.js:112901:142(Unknown)
    <jscode>.apply__O__O__O(webapp-base-test-test-fastopt.js:215374)
    scala.collection.IndexedSeqOptimized.foldl(webapp-base-test-test-fastopt.js:373910)
    <jscode>.foldLeft__O__F2__O(webapp-base-test-test-fastopt.js:400985)
    <jscode>.traverse__sc_TraversableOnce__F1__scg_CanBuildFrom__s_concurrent_ExecutionContext__s_concurrent_Future(webapp-base-test-test-fastopt.js:112898)
    <jscode>.evaluateFutureTree__Lutest_framework_HTree__s_concurrent_ExecutionContext__s_concurrent_Future(webapp-base-test-test-fastopt.js:110083)
    <jscode>.runAsync__Lutest_Tests__F2__sc_Seq__Lutest_framework_Executor__s_concurrent_ExecutionContext__s_concurrent_Future(webapp-base-test-test-fastopt.js:110203)
    <jscode>.runSuite__sc_Seq__T__Lsbt_testing_EventHandler__Lsbt_testing_TaskDef__s_concurrent_Future(webapp-base-test-test-fastopt.js:153723)
    <jscode>.file:///tmp/shipreq.sbt/webapp-base-test/js/target/scala-2.12/webapp-base-test-test-fastopt.js:154034:109(Unknown)
    <jscode>.apply__O__O__O(webapp-base-test-test-fastopt.js:215374)
    <jscode>.execute__Lsbt_testing_EventHandler__ALsbt_testing_Logger__F1__V(webapp-base-test-test-fastopt.js:154114)
    <jscode>.file:///tmp/shipreq.sbt/webapp-base-test/js/target/scala-2.12/webapp-base-test-test-fastopt.js:28075:77(Unknown)
    <jscode>.apply__O__O(webapp-base-test-test-fastopt.js:215342)
    <jscode>.file:///tmp/shipreq.sbt/webapp-base-test/js/target/scala-2.12/webapp-base-test-test-fastopt.js:26768:29(Unknown)
    <jscode>.apply__O__O(webapp-base-test-test-fastopt.js:215342)
    <jscode>.file:///tmp/shipreq.sbt/webapp-base-test/js/target/scala-2.12/webapp-base-test-test-fastopt.js:112775:55(Unknown)
    <jscode>.apply__O__O(webapp-base-test-test-fastopt.js:215342)
    <jscode>.file:///tmp/shipreq.sbt/webapp-base-test/js/target/scala-2.12/webapp-base-test-test-fastopt.js:214110:57(Unknown)
    <jscode>.apply__O__O(webapp-base-test-test-fastopt.js:215342)
    <jscode>.run__V(webapp-base-test-test-fastopt.js:214040)
    <jscode>.scala$scalajs$concurrent$QueueExecutionContext$PromisesExecutionContext$$$anonfun$execute$2__sr_BoxedUnit__jl_Runnable__sjs_js_$bar(webapp-base-test-test-fastopt.js:244926)
    <jscode>.file:///tmp/shipreq.sbt/webapp-base-test/js/target/scala-2.12/webapp-base-test-test-fastopt.js:244943:155(Unknown)
    <jscode>.h(webapp-base-test.js:1)
    <jscode>.file:///tmp/shipreq.sbt/webapp-base-test/js/target/scala-2.12/test-classes/webapp-base-test.js:1:397894(Unknown)
    <jscode>.run(webapp-base-test.js:1)
    <jscode>.d(webapp-base-test.js:1)

I've provided a reproduction here: https://github.com/japgolly/misc/tree/scalajs-3989
Once you checkout the branch, all you need to do is run ./reproduce - it will download everything it needs.
I also shrank this further. Here's some new learnings...

es6-shims on test classpath is required to reproduce the bug (see webapp-base-test/js/src/test/resources/webapp-base-test.js)
I've cut out the majority of es6-shims so that it's only shimming Math.imul (see webapp-base-test/js/src/test/resources/pre-webpack-source.js)
it's necessary to run it through webpack in production mode (config: frontend/webpack/local.js); running through webpack in development mode (src: webapp-base-test/js/src/test/resources/webpack-dev.js) doesn't produce the bug
bug occurs with PhantomJS and not with Node

Thanks for the repro. Due to the giant SIP meeting, I won't have time to look at it until next week.
Just from the set of things needed to reproduce, my hunch is that the shim for imul implemented in es6-shims is either fundamentally buggy, or somehow triggers a bug in PhantomJS. The shim that is built in Scala.js seems to be correct, since not having es6-shims causes the bug not to surface, following your comment.

So, with your reproduction, I can reproduce on Linux (but not on Windows) using PhantomJS 2.1.1, the last version (but not 1.x), using sbt test (what's eventually run by the Docker image IIUC).
However, if I force Scala.js to always use its implementation of Math.imul, instead of first looking for an existing Math.imul (I did that by editing the -fastopt.js file by hand), then the bug is not reproducible anymore.
I conclude that the Math.imul polyfill of es6-shims is buggy, and ours is not. (It works on Node.js because Node.js does define the correct built-in Math.imul, so neither es6-shims' nor Scala.js' polyfill is used.) Therefore, this is not a bug in Scala.js, and there is also no workaround that we could possibly use (we are most definitely not going to detect wrong implementations of Math.imul polyfilled by random libraries).
I will therefore close this issue as "invalid" and "separate repo".

Ok cool. Thanks for your time confirming this!

Btw, if anyone else comes across this issue in future, the higher-level problem I had was that I was using airbnb-js-shims in my tests because some other dependency was using Map and Set.
A workaround for this is to switch from airbnb-js-shims to core-js. In my case I simply imported 'core-js/features/map' and 'core-js/features/set' and problem avoided.


Cookie notice on Change.org is not blocked

Unfortunately this one is not possible to block with Safari without also breaking the site.


chore(webpack): Listen port configure by environment variable

I fixed #40

This change is

Thanks for the PR!


rbac migration namespace missing

I found this issue during using this configuration:
return [
     'controllerMap' => [
        'migrate' => [
            'class' => 'yii\console\controllers\MigrateController',
            'migrationNamespaces' => [
                'app\migrations',
                'yii\rbac\migrations',
            ],
            'migrationPath' => null,
        ],
    ],
];

And after this:
./yii migrate/up
Yii Migration Tool (based on Yii v2.0.10)

Total 1 new migrations to be applied:
        yii\rbac\migrations\m140506_102106_rbac_init

Apply the above migrations? (yes|no) [no]:yes
*** applying yii\rbac\migrations\m140506_102106_rbac_init
PHP Compile Error 'yii\base\ErrorException' with message 'Cannot declare class m140506_102106_rbac_init, because the name is already in use'

in /var/www/html/vendor/yiisoft/yii2/rbac/migrations/m140506_102106_rbac_init.php:149

Additional info

Q
A

Yii version
2.0.10

PHP version
7.0.12

Operating system
Debian 8.6

Duplicates #13142


Cloud CRD

Manager has ability to interact with multiple clouds.

CRD for Cloud.
List Cloud in API
added ClientContainerBean#getClient(String name) and retained ClientContainerBean#getClient() for local client
Doesn't require CRD to be installed for purely local operartion

Looks good IMO - can't test it atm - sorry


Graphical issues with linux

while trying to play osrs on linux. (i used pop os and kubuntu) got the same issue.

Duplicate of #11351


pull request for e2e test at 12/06/2016 08:45:01

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add  a Simple tracing  view UI

The quick start employs Promethues to view the effect of metrics. But there are no recommendations to view the effect of tracing.
Propose to add a simple web server, composed of only one source file, to show the tracing in YAML. This server is required only to collect and aggregate the trace in memory for the evaluation of easeagent.   easeagent output tracing to the server directly without any broker. It's deliberately to show in YAML format because a product-level tracing viewer connects many facts and too heavy to deploy for a quick start evaluation.

I will output trace info to Zipkin

hello , How is it now about UI.

It is in my roadmap and  has not yet started development

EaseAgent already supports sending tracing data to Zipkin Server.
This is PR https://github.com/megaease/easeagent/pull/103