Use a URL-safe alphabet and strip/pad trailing equal signs to ensure compat with other B64 encoders

Matches encoding from: https://github.com/Taum/altered-deckfmt/commit/45fc605bf6212f2578cbeb7dc6be59b19f80d9e0
I realized tonight that we were using the default Base64 alphabet which is not URL safe. Given the context in which we plan to use this encoding, it seemed like a major oversight. I moved to the URL-safe alphabet (a.k.a. base64url, see RFC-4648 section 5) which should be implemented by most major libraries.
I noticed the default JS implementation of base64url strips trailing = signs, so I took the liberty to match this here since it was fairly trivial to implement. We can make this mandatory in the spec to ensure other readers also support it.

I just tested it and it works great, thanks for considering that!


file size limit

The name of the project:WOT
The size of your release, in megabytes: 71.1
Which index/indexes you need the increase for: both

@joshua-gould Could you provide some details about this project and why it needs to be so large?

What makes is so large is that it includes Gephi
(https://gephi.org/toolkit/) for running graph layout algorithms.
Thanks.
On Mon, Aug 20, 2018 at 5:45 PM Dustin Ingram<EMAIL_ADDRESS>wrote:

@joshua-gould Could you provide some details about this project and why it needs to be so large?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi, is bundling the jar file the recommended way to include Gephi or should I make an http request to download the jar in setup.py? Thanks.


Please Clarify Exploit

Summary
In Tenebrous's video, he really didn't seem to understand what the hell this exploit is (along with many other technical videos he does mind you...). Therefore, I am asking you to please clarify, in your README and the release, this exploit cannot send the server the contents of a file and only sends if the file exists and the SHA1 hashes for those files (to which there is no real threat as the time it would take to reverse those).
Proofs
In Tenebrous's Video at 3:58 he says a server can "get any file on your computer" which is misleading.
He continues in the comments by saying as long as you didn't keep passwords in files, which is misleading again. This exploit cannot be practically used to get passwords, let alone any data in a file.

Conclusion
While yes this exploit is a medium is a severity as servers could brute-force or check predetermined file names, this exploit has no real world possibility of viewing the contents of files. And no, I'm not saying this mod isn't good to use or doesn't serve a porpose. @Sk1er don't get me wrong this is a well-made mod and I do still recommend using it for people who have a concern that somebody will illegally use this. I just think this needs to be more clear, in this repository, what the exploit can or cannot do as much of the traffic has been through Tene's misleading video.
Tene if you are reading this, I suggest having someone like Sk1er proof-read these videos before you publish them as he could have probably caught this mistake and helped you not miss-direct users.
Regards,
Josh

The article properly explaining the exploit is linked everywhere. I cannot really control what other people say. I will edit the readme to add some more details

Tenebrous is a genuine retard

no u
https://twitter.com/SiroQ_/status/1040252212839034883

@RDIL What file did he check for? C:/Windows? How much of a brainlet does someone have to be to consider this an information leak and "illegal?"

So you can check for files on your computer with and without the mod
therefore proving the exploit is real.

@RDIL In my hypothetical situation it'd say it doesn't exist either way because I don't use Windows... I'm not saying the bug isn't real I'm saying that it's useless. You'd have to send thousands of packets to put together a single filename and even after you find out, who cares?

Still could be used to get PII.  Oh well.

@RDIL Yeah because someone has a file lying around that they renamed to their address

Tbh you really never know


python3Packages.nmigen: unbreak

Motivation for this change
I noticed that this package was broken on hydra.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 121846 at 7e961480 run on x86_64-linux 1

8 packages built successfully:

glasgow (python38Packages.glasgow)
python38Packages.nmigen
python38Packages.nmigen-boards
python38Packages.nmigen-soc
python39Packages.glasgow
python39Packages.nmigen
python39Packages.nmigen-boards
python39Packages.nmigen-soc


Remove BTreeIndexFileReader#readRowIdList & fix test case

BTreeIndexFileReader#readRowIdList is identified as deprecated at v0.3, remove it at v0.4 If it doesn't really need。

This is no longer valid as #683 remove that part of code... Thanks @LuciferYang


expected cilitics behavior

Hello,
In this document: http://drops.dagstuhl.de/opus/volltexte/2019/10885/pdf/OASIcs-SLATE-2019-18.pdf
You have an example for contractions. But you don't have one for cilitics.
For instance: "levem-no" should be "levar em o"?
I forked and am doing some changes. a major one is maintaining a relation between the original text and the processed one. i am returning an array of token objects, each token has its original line, position, and original text.
Don't know what you think about this, it's a bit different from what you have, and it's also a bit of overhead maybe. Maybe it needs the possibility to have that or just a simple array.
Also changed the replace cilitics and contractions functions to classes. The functions are reading a document each time you call them. You only need to read it once and be able to call the function several times if you want.
I'll upload when it's working ok.

Hi,
I think that what you are adding seems very useful, specially in cases where you want to return part of the sentence (for example in relation extraction) let me know when its finished!


Tox returns missing Python interpreter while Python is installed

🔍 Before submitting the issue

[X] I have searched among the existing issues
[X] I am using a Python virtual environment

🐞 Description of the bug
Tox returns SKIPPED: InterpreterNotFound when running these commands:

tox -e doc
tox -e syle

📝 Steps to reproduce

git clone https://github.com/Solution-Applications/solutions-app-em-nvh-mapper.git
python -m venv .venv
.venv\Scripts\Activate.ps1
python -m pip install -U pip poetry tox
python -m pip install -r requirements/requirements_build.txt
python -m pip install -r requirements/requirements_doc.txt
python -m pip install -r requirements/requirements_tests.txt
poetry run python -m pip install dist/ansys_solutions_em_nvh_mapper-0.1.dev0-py3-none-any.whl
tox -e doc
tox -e style

💻 Which operating system are you using?
Windows
🐍 Which Python version are you using?
3.7
📦 Installed packages
alabaster==0.7.12
ansys-sphinx-theme==0.4.2
atomicwrites==1.4.1
attrs==21.4.0
Babel==2.10.3
beautifulsoup4==4.11.1
bleach==5.0.1
build==0.8.0
CacheControl==0.12.11
cachy==0.3.0
certifi==2022.6.15
charset-normalizer==2.1.0
cleo==0.8.1
clikit==0.6.2
colorama==0.4.5
commonmark==0.9.1
coverage==6.4.1
crashtest==0.3.1
distlib==0.3.5
docutils==0.18.1
filelock==3.7.1
html5lib==1.1
idna==3.3
imagesize==1.4.1
importlib-metadata==4.12.0
iniconfig==1.1.1
Jinja2==3.1.2
keyring==23.7.0
lockfile==0.12.2
MarkupSafe==2.1.1
msgpack==1.0.4
numpydoc==1.4.0
packaging==20.9
pastel==0.2.1
pep517==0.12.0
pexpect==4.8.0
pkginfo==1.8.3
platformdirs==2.5.2
pluggy==1.0.0
poetry==1.1.14
poetry-core==1.0.8
ptyprocess==0.7.0
py==1.11.0
pydata-sphinx-theme==0.9.0
Pygments==2.12.0
pylev==1.4.0
pyparsing==3.0.9
pytest==7.1.2
pytest-cov==3.0.0
pytz==2022.1
pywin32-ctypes==0.2.0
readme-renderer==35.0
requests==2.28.1
requests-toolbelt==0.9.1
rfc3986==2.0.0
rich==12.5.1
shellingham==1.4.0
six==1.16.0
snowballstemmer==2.2.0
soupsieve==2.3.2.post1
Sphinx==5.0.2
sphinx-copybutton==0.5.0
sphinxcontrib-applehelp==1.0.2
sphinxcontrib-devhelp==1.0.2
sphinxcontrib-htmlhelp==2.0.0
sphinxcontrib-jsmath==1.0.1
sphinxcontrib-qthelp==1.0.3
sphinxcontrib-serializinghtml==1.1.5
toml==0.10.2
tomli==2.0.1
tomlkit==0.11.1
tox==3.25.1
twine==4.0.1
urllib3==1.26.10
virtualenv==20.15.1
webencodings==0.5.1
zipp==3.8.1

Thanks for opening this @iazehaf. Investigating this... 🔎

I confirm that I can reproduce this locally.

The issue comes from a bad syntax in the tox.ini file:
-    py: python3{style,reformat}: python3
+    py: python3
+    {style,reformat,doc}: python3

This is a bug, see the demo branch for Poetry https://github.com/ansys/ansys-templates/blob/demo/pyansys-advanced-poetry/tox.ini

This is caused by the Jinja syntax. Fixing this in a couple of hours.

@jorgepiloto  thank you very much for your quick support. It works well!


No files reported on Travis

My Travis build is reporting 0 files when I use coveralls debug There's an example at the bottom of this build:
https://travis-ci.org/Axelrod-Python/Axelrod/builds/62563230
When I run the same coverage command locally, followed by coveralls debug I get the expected results and I can even run coveralls successfully. The result of a local run is job number 511 here:
https://coveralls.io/r/Axelrod-Python/Axelrod
The only difference between the two is that I created .coveralls.yml for my local test and entered my repo_token but my understanding was that I don't need to do that for a Travis build.
Am I missing something somewhere?

I think coveralls can't find coverage data because it was executed from docs folder.
I suggest coveralls should exit with non-zero status and output error in stderror if coveralls gathers no coverage files. This will help identify problem with empty coverage right away.
Something like this:
$ coveralls
Error: No .coverage files found. Please make sure you've run coverage from current directory.

What do you think, @jessamynsmith?

Aggghhhh!! Many thanks indeed for pointing out something so damned obvious!!

I think that sounds very reasonable, @coagulant. I am always a fan of clear output. :)


Version 9.1 in Windows 10, version 1903 and Windows Server, version 1903

Need to add it to:

“Supported VM configuration versions for semi-annual channel hosts” table
List of features in “What happens if I don't upgrade the virtual machine configuration version?” section

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

ID: e4944168-7e1f-b07d-fcf3-f8310ba9a398
Version Independent ID: 1603af67-fcc0-58a6-b86d-5b812bfbcdc7
Content: Upgrade virtual machine version in Hyper-V on Windows 10 or Windows Server
Content Source: WindowsServerDocs/virtualization/hyper-v/deploy/Upgrade-virtual-machine-version-in-Hyper-V-on-Windows-or-Windows-Server.md
Service: na
Product: windows-server-threshold
Technology: compute-hyper-v
GitHub Login: @KBDAzure
Microsoft Alias: kathydav

Thanks for your dedication to our documentation. If we have been unable to review your issue in a timely manner, we sincerely apologize for the delayed response. We have captured the informtion you have provided for review. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


Getting the error cb.train is not callable.

from chatterbot import ChatBot
from chatterbot.trainers import ListTrainer
cb=ChatBot("Ruhi")
cb.train([
"Hello",
"Hi there!",
"How are you doing?",
"I'm doing great.",
"That is good to hear.",
"Thank you",
"You're Welcome"
])
response=cb.get_response("Good Morning")
print(response)

Hi @ana301 Instead of calling the train method, try the following:
from chatterbot import ChatBot
from chatterbot.trainers import ListTrainer

chatbot = ChatBot('Charlie')

trainer = ListTrainer(chatbot)

trainer.train([
    "Hi, can I help you?",
    "Sure, I'd like to book a flight to Iceland.",
    "Your flight has been booked."
])


PR for Issue #177

This PR addresses the Issue #177
I added a flag called isClearingSearchValue and used it to prevent calling serverSearch() method when the dropdown is closed after adding a new option

@SahajJain01 thanks for your contribution. I will check your changes and merge them.


Real hardware test

Confirmed working on Pc-9821 Nx/c7 Pentium 100mhz DX4 38mb ram using a CF card.
I've tested with only angelmiku.98v.
There's no sound, just constant static.
There seemed to be no playback delays due to the hardware just lots of sample rate dithering.

However when the video stopped it did end with a protection fault error.

Great job on this! 🤘

Wow, great to see that something did work after all! I've only tested this program on emulators so I was expecting something to maybe go wrong on real hardware.
I've just looked up this model, and it appears that it has an 86-compatible soundboard, though not the 86 itself. It might be falling back on buzzer PWM sound, in which case I can see how it would become 'constant static'. Does it even sound vaguely like the original music? Either I went too far with the sample rate (I used 22050 Hz), made some bad assumptions about how 86 PCM works or about how buzzer PWM sound works. I will try my best to see what the problem is even without owning a piece of PC-98 hardware myself. This might be a little difficult.

The general protection fault likely results from the fact that I use a segment for putting raw file data rather unsafely, since I assume that all conventional memory above where the program is loaded is free for the taking. I never saw this for some reason.

Oh I just noticed that the error message says that DX = 3FDB which just so happens to be the I/O port number for time number 1 read/write. I consider this highly unlikely to happen by chance, so I now know that it did fall back on buzzer PWM audio and the general protection fault may come about because the interrupt routine to handle PWM audio is maybe not properly turned off at the end (even though it should be). But I am pretty sure any errors lie with the handling of buzzer PWM audio.

Ah, I suspect that a laptop speaker doesn't low-pass filter a buzzer PWM signal, so the high frequency components of the raw signal end up being much more dominant than the actual sound. Whether or not I can do anything about this depends on whether you can hear anything recognisable at all, or if it's just noise.

Perhaps I will find out why it falls back on buzzer PWM audio despite the presence of an 86-compatible soundboard.

Ah it seems only the FM sound source is 86-compatible, the built-in PCM is not 86-compatible. To support that would require some work, but the main problem is that Neko Project 21 doesn't emulate the right soundchip, so that would make testing difficult.

Correct, my model uses MateXPCM (118/wss/canbe) it's different than 86PCM.
However there may be a method to mimic 86PCM. Is there a specific port I/O that's recommended?
Also, you may consider joining the PC98 discord if you're not already.
https://discord.gg/8DpqC7mD
It would be a great place to ask questions if you ever decide to buy a PC98 or even get assistance with some of your development. 🤘

It has been several months but I have implemented preliminary support for WSS-compatible sound. I am not certain that it works on real hardware since it works perfectly fine on Neko Project 21, but in a slightly different version of Neko Project it has unacceptable artifacting (alternates between OK sound and being white noise on a regular basis). Also I'm not quite sure if I'm using DMA correctly as well.

@maxotaku11niku hello! I would love to go test the newest version for you tonight.
When it comes to WSS usually DMA is either set to 1 or 3.

Thanks for the reassurance (I used channel 3), I will wait eagerly for the result.


scrolling animation left breaks when itemsToScroll > 4

Describe the bug
the slide animation shows the right slide animation when pressing any of the arrows (same animation for both).
To Reproduce
I have 10 slides with pictures.
shows 5 every time.
scrolls 5 every time.
wrap around = true.
Expected behavior
pressing the left arrow should show the scroll left animation.
Desktop (please complete the following information):

OS: windows 11
Browser edge
Version 99.0.1150.46 (Official build) (64-bit)

Additional context
I changed the itemsToScroll value to 4 and it seems to work perfectly. the problem seems to appear when the value is higher than 4

I don't use arrows but i can concur, Im using show 5 slides with autoloop.. somekind of weird twitch effect happens.

closed by #231


customer detail not work

customer detail like email and name phone not work and not showing on midtrans dashboard, but it showing on VSC console log,
please add adddress to

This should be generated by your backend not from client side

but i test with postmant, and return snap email phone and name its work

I am not sure about the midtrans dashboard, but so far mine is working fine.
please add screen shot to make me better understand

that console log from VSCode

Having the same problem too. The customer data not posted to server

Having the same problem too. The customer data not posted to server

I'm using the sample code


Add eodag to search and download tools

EODAG (Earth Observation Data Access Gateway) is a command line tool and a plugin-oriented Python framework for searching, aggregating results and downloading remote sensed images while offering a unified API for data access regardless of the data provider.
https://github.com/CS-SI/eodag

Thank you for the addition :+1:


Add a DiffableTextCache protocol.

Description
#122 introduces a new pattern where a style delegates its work to some persistent object. A DiffableTextCache protocol can describe this pattern and remove boilerplate when Cache: DiffableTextCache, Cache.Style == Self.
Proposal
public protocol DiffableTextCache {
    associatedtype Style: DiffableTextStyle; typealias Value = Style.Value

    // init(_ style: Style)
    // mutating func merge(_ style: Style)

    func format(_ value: Value) -> String
    func interpret(_ value: Value) -> Commit<Value>
    func resolve(_ proposal: Proposal) throws -> Commit<Value>
}

public extension DiffableTextStyle where Cache: DiffableTextCache, Cache.Style == Self { /* delegate work to cache */ }

Introduced in 401231a57804e37d214289462f4a1be45d7d12a7.

Treating the cache as a cache is a better approach. Who'd a thunk it?

It's a nice convenience, actually, but it turns out that the cache cannot generically control how it is initialized or updated. So it has been reinstated (in the numbers rework branch) with modifications. Now it only requires and delegates:
func format(_ value: Value) -> String
func interpret(_ value: Value) -> Commit<Value>
func resolve(_ proposal: Proposal) throws -> Commit<Value>

On third thought, it’s a bit too niche. I still see utility in it, but I recognize that there are a lot of way of designing/using the cache. Unlike DiffableTextStyle, it simplifies but one of many possible design patterns. I’ll hold off on it until I find a more compelling reason to add it.

Having experimented a bit with a more light-weight version of this proposal, it’s clear that a cache protocol requiring a style associated type is less than ideal. Why? The cache tends to be the engine, so to speak, and more generic than it’s unresolved style. In other words, it tends to be easy to model a many styles per one cache relationship, whereas an associated type requirement makes it one-to-one for no real reason.


fix(scripts): Run generate-migration-map after seed events

Pre-Submission Checklist

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

Type of Change

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

Checklist:

[x] Tested changes locally.
[x] Addressed currently open issue (replace XXXXX with an issue no in next line)

Closes #17221
Description

Only run generate-migration-map when we are certain there are challenges in the db.

@Bouncey can you check the Travis build error.


Adding playwright icon to Azure's official svg icon set.

[Note: Unrelated to ContosoTraders, but I wanted to file this issue before I forgot about it]
As you're probably aware, Azure has an official svg icon set (for use in diagrams, presentations et al).
See the bottom of this page: https://learn.microsoft.com/en-us/azure/architecture/icons/
The icons for load testing, chaos studio are already included in the icon set.
But playwright icon is not.

Closing, as Playwright is not an Azure service.


[v1.1.1] - Error Start Bot in Composer with Luis

When using Composer v1.1.1 in Win10 and using Luis in ToDoBotWithLuisSample always having this error:
Sorry, something went wrong with publishing. Try again or exit out of this task.
request to https://westus.api.cognitive.microsoft.com/luis/authoring/v3.0-preview/apps/***/versions/0.3/ failed,
reason: connect ETIMEDOUT <IP_ADDRESS>:443
My  authoring resource is in westus.
Using the same sample with the same LUIS Authoring key, but in mac OS, everything runs ok!
System: Win10
Composer: v1.1.1
Donet: 3.1.402

update: making the sample:
Composer > new > using template > QnAMakerLUISSample
with the same authoringKey everything runs ok!
can't understand...

@SantiagoMadeira , there might be something wrong with your previous deployment and the version 0.3 of your luis application is actually broken. Could you check in your luis portal as the following, try to delete version 0.3 or even delete the luis app itself and try again?

@luhan2017 thanks for your response.
one thing i noticed was that whenever i do Start Bot on the composer, it creates a new version of each app in Luis.ai even without any changes in LUIS phrases of Composer. Went to see the status of Apps on Luis.ai and some of the new versions that are created (each time i run Start Bot) are not in the Active & Production state only in the Active state.
What makes me confused is that my co-worker is working on a MacOS, and when we change the authorization keys, my Luis apps work well in Composer on MacOS, but this error occurs in my composer in Win10. If I use his keys in Composer Win10 I have the same error :(
I even tried to compile the composer on Win10 and use the Composer web application, but the error remains.
With the example of LuisAndQnA, everything works fine in Win10. Will the fact that the TodoWithLuis example generates 4 apps on Luis.ai and the LuisAndQnA example generates only 1 app, will influence this error?
Note: Also tried to use the microsoft virtual machine for Edge on virtual-box, installed the necessary software for Composer and had the same error :(

@SantiagoMadeira thanks for the reply, we will investigate more based on the information you provided.
For multiple luis apps, we just create one luis app for each dialog.

in TodoWithLuis sample, we have 5 dialogs which enable luis.
in LuisAndQnA sample, we just have 1 dialog which enables luis.

If you want to have fewer luis apps created within a bot, just reduce your dialog count :)

I have the same issue - on both browser based and desktop version of the Composer when running on Win10. It seems that bad request is coming from http://localhost:5000 and not from LUIS. I tested the LUIS POST request in Postman and it worked fine. It seems that localhost:5000 (Composer backend process) has a bug when waiting for LUIS response and returns Bad Request. It happens not only on "/train" LUIS request but also "versions/import?versionId=0.7"
I add additional fiddler traces here (desktop app)
REQUEST:
POST http://localhost:5000/api/projects/79345.4352583862/build HTTP/1.1
Host: localhost:5000
Connection: keep-alive
Content-Length: 923
Accept: application/json, text/plain, /
Origin: http://localhost:5000
Sec-Fetch-Dest: empty
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) @bfc/electron-server/1.1.1 Chrome/80.0.3987.165 Electron/8.2.4 Safari/537.36
Content-Type: application/json;charset=UTF-8
Sec-Fetch-Site: same-origin
Sec-Fetch-Mode: cors
Referer: http://localhost:5000/bot/79345.4352583862/dialogs/collabbot64
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US
Cookie: connect.sid=xxxxxx%3AQEOIU3PLMv3XT7Tgv9_.%2BmEpLyZLNsxxxxcSKYILNggsklDWqqGn27ShaxAFWXI
{"luisConfig":{"name":"CollabBot64","authoringKey":"MYKEYHERE","endpointKey":"","authoringRegion":"westus","defaultLanguage":"en-us","environment":"composer","endpoint":"","authoringEndpoint":""},"qnaConfig":{"subscriptionKey":"","qnaRegion":"westus","endpointKey":""},"projectId":"79345.4352583862","crossTrainConfig":{"rootIds":["collabbot64.en-us.lu"],"triggerRules":{"collabbot64.en-us.lu":{"Add":"additem.en-us.lu","Delete":"deleteitem.en-us.lu","View":"viewitem.en-us.lu","UserProfile":"userprofile.en-us.lu","whatCanYouDo":"","cancel":""},"userprofile.en-us.lu":{"Cancel":"","Why":"","NoValue":""}},"intentName":"_Interruption","verbose":true},"luFiles":["additem.en-us","deleteitem.en-us","userprofile.en-us","viewitem.en-us","collabbot64.en-us"],"qnaFiles":["additem.en-us","deleteitem.en-us","help.en-us","userprofile.en-us","viewitem.en-us","collabbot64.en-us","collabbot64.lu.qna.en-us"]}
RESPONSE:
HTTP/1.1 400 Bad Request
X-Powered-By: Express
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,HEAD,OPTIONS,POST,PUT,DELETE
Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept, Authorization
Content-Type: application/json; charset=utf-8
Content-Length: 208
ETag: W/"d0-5XDfGKfQzLxxxxxlBN2Ybn9WDKY"
Vary: Accept-Encoding
Date: Fri, 30 Oct 2020 21:13:04 GMT
Connection: keep-alive
{"message":"request to https://westus.api.cognitive.microsoft.com/luis/authoring/v3.0-preview/apps/xxxx7797-xxxxc-405d-be3f-52ba70fd0a4c/versions/0.2/train failed, reason: connect ETIMEDOUT <IP_ADDRESS>:443"}

Here is the dev for the luis publishing module, I'm trying to reproduce and figure out the cause, will keep you posted when there are any foundings. Thank you.

Hi @SantiagoMadeira @gbelenky, I was not able to reproduce this error in my windows 10 os with 1.1.1 Composer. Is this issue reproduced stablely or occasionally? Per my observation, this is maybe caused by the network delay or some other network issue of window os. If this is stabely reproduced, I will sync with the luis team to have it investigated.

Hi @feich-ms! This stably reproduced on my Win 10 machine when publishing "To Do With LUIS" sample . I can also stably reproduce it when connecting my machine to a different network bypassing home wifi router - in my case it was mobile internet. Composer works fine with my Mac. Is there a way to get Composer logs?
Update:
If I use a different LUIS bot with a smaller number of dialogs, it works fine.

@gbelenky thanks for the investigation. Your findings help a lot. As you may know luis service allows 5 transactions per second, so to make full use of such capability, composer is calling luis api with a concurrency rate of 5, this is implemented here in @microsoft/bf-lu package which is consumed by composer. We guaranteed not hitting the rate limit exception of luis api by waiting a time bucket after the last returned call of the concurrent 5 calls. This may be the confused executing behaviour you observed, but I'm not sure why timeout exception thrown among these calls.

@gbelenky can I know which region are you specifying when doing publishing? Can you share the appsetting you are using when publishing. You can remove any sensitive keys and ids. We can have a debug session, but before that I hope I can reproduce it in some way.
Below screenshot is what appsettings look like

@feich-ms This time I selected a much simpler sample https://docs.microsoft.com/en-us/composer/tutorial/tutorial-luis.
But even here I get random errors to the one above when I Restart Bot and publish my model to LUIS. But even when I am sometimes lucky and there are no errors, composer seems to forget to train the model and also to publish it into the production slot. Here is an example - I restarted the bot I am wondering why the "weather" trigger not getting fired. Emulator says:

I go to the LUIS portal, train and publish the model and this is what I get without restarting the bot:

@feich-ms - the same error happens in both regions where I have my authoring keys - westus and also westeurope

Synced with @gbelenky offline, he can make it with his Mac or VM but failed with his window device. I'm not able to reproduce it with my window device(both work station and laptop) and other windows devices from colleagues. I also tried a VM in azure that located in west europe, still no reproducing. It seems this issue only happened on specific devices. If we have a chance to reproduce it with some machines, we can dig into it to figure out the cause. The only workaround solution I can think of is to use cli tool to process language models. In composer next official release, it will provide users the capability of processing language models outside composer. In this way, users can process models with cli tool and overcome the issue by publishing models more times and with less concurrency.

hi,
I think I found a common factor between this issue and another one I reported #4584
Was using PT-BR as the defaultLanguage in Composer settings, and whenever I use that configuration I have these errors. When changing to defaultLanguage = 'en-us' everything works fine!
The final test I did was:

configure Composer with only defaultLanguage = 'en-us', both issues work well.
added PT-BR in Composer, rebuild bot in Composer. After that in LUIS a new APP was created for PT-BR.
Without changing defaultLanguage in Composer it continued to work correctly.
In Composer remove language 'en-us' and set PT-BR as default, rebuild,  both issues work well (in this point have two Apps in Luis)
In LUIS I removed APP for language 'en-us' (well, at this point i'm not using that language in Composer) and just stayed with APP for PT-BR, and without rebuilding Composer and without Deploy for Azure... KABOOM! The error reappeared.
I added APP for language 'en-us' in LUIS, everything worked fine again.

I think there is a problem when defining a default language other than 'en-us'
Now i'm working only with defaultLanguage='en-us' in Composer and everithing runs smooth

Hi @SantiagoMadeira, what is the exact error message in your above steps? Is it related with the error reason: connect ETIMEDOUT <IP_ADDRESS>:443 this issue is tracking?
Besides, I followed your steps above to try composer, but didn't hit any exceptions when publishing and testing with emulator.
For the luis api call timeout issue, I think we will include luis team for further investigation.

Hi @feich-ms,
most of the time the error is 404 (Not Found)
also happens but less frequently 401 (PermissionDenied) and 403 (Forbidden)

@SantiagoMadeira, so they are different exceptions I think. For this ticket, it's reporting error reason: connect ETIMEDOUT <IP_ADDRESS>:443 and for your issues of above steps, could you please open another ticket to track? And we can provide supports for that case there.

please go ahead and open a new issue to track https://github.com/microsoft/BotFramework-Composer/issues/4458#issuecomment-723160504

@feich-ms -  it seems to be an issue with my home WIFI router firmware + my PC. I have the same issue when publishing Azure Functions on the same WIFI. I used a different WIFI network and could not reproduce the issue. Around one month ago I  had a firmware update of my WIFI router - that probably causes the issue with my PC. My Mac has no problems though.

@feich-ms - might be related, but the web version works fine (except of the publishing issue above)

@feich-ms - not related - I double checked with my mobile internet

@gbelenky thank you. Then that's totally another issue.

@gbelenky, @feich-ms
I got a problem related to the company network.
When I used public network, it worked fine.
How can I config the proxy for Bot Framework Composer ?

@gbelenky, @feich-ms
I got a problem related to the company network.
When I used public network, it worked fine.
How can I config the proxy for Bot Framework Composer ?

@Khanh-Ngy we don't support proxy officially, but we do have a prototype which enables proxy for luis/qna and azure publish. Do you want to try our private version? it is based on composer v1.2.2.

@Khanh-Ngy we don't support proxy officially, but we do have a prototype which enables proxy for luis/qna and azure publish. Do you want to try our private version? it is based on composer v1.2.2.

@Khanh-Ngy we don't support proxy officially, but we do have a prototype which enables proxy for luis/qna and azure publish. Do you want to try our private version? it is based on composer v1.2.2.

Can you send me a link for researching ?

@Khanh-Ngy we don't support proxy officially, but we do have a prototype which enables proxy for luis/qna and azure publish. Do you want to try our private version? it is based on composer v1.2.2.

Can you send me a link for researching ?


Adding filter type to filtering release configs

Description
Current release configs for filtering do not have filter type, this means they we're using default value SCRIPT that is for score scripting with exact k-NN search (docs on filtering test step). This is a gap in initial implementation, intended filter type is FILTER, it uses filtering logic based on Lucene implementation.
Issues Resolved
Identified during k-NN 2.6 release
Check List

[X] All tests pass
[X] Commits are signed as per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #792 (9345dbb) into main (e9dd3e0) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##               main     #792   +/-   ##
=========================================
  Coverage     85.14%   85.14%
  Complexity     1079     1079
=========================================
  Files           151      151
  Lines          4370     4370
  Branches        390      390
=========================================
  Hits           3721     3721
  Misses          472      472
  Partials        177      177

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@martin-gaievski can you fix the BWC test also which are failing. We need to now test upgrade from 2.7 to 3.

@martin-gaievski can you fix the BWC test also which are failing. We need to now test upgrade from 2.7 to 3.
@VijayanB will do a separate PR for BWC and 2.7, I'll rebase once that change is merged.

Created PR https://github.com/opensearch-project/k-NN/pull/793 for bwc upgrade


How to run solver?

Hey, there seems to be a lot of newer files uploaded than it was in the tutorial video/README, would it be possible to get an update on how to run the newer files? Thanks so much! For example, java_interface.py is no longer available.

sorry, clearly i cant read directions : D

So this problem is solved? Let me know if there are any other problems.


CUDA error: CUBLAS_STATUS_EXECUTION_FAILED

When i try to reproduce the example execution (step number 1 and 2) appear the following message ->CUDA error: CUBLAS_STATUS_EXECUTION_FAILED when calling cublasSgemm( handle, opa, opb, m, n, k, &alpha, a, lda, b, ldb, &beta, c, ldc).
I execute the scrips in my RTX 3080 graphic card. How can I solve it? I tried the example car_20

After debugging the code, the line that generates this error is the following:

Changing the Cuda and torch version appear the following error:
Traceback (most recent call last):
File "train_interpreter.py", line 589, in
generate_data(opts, args.resume, args.num_sample, vis=args.save_vis, start_step=args.start_step)
File "train_interpreter.py", line 265, in generate_data
return_upsampled_layers=True)
File "../utils/utils.py", line 76, in latent_to_image
img_list, affine_layers = g_all.module.g_synthesis(style_latents)
File "/mnt/hdda/Data/envs/dataGan/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1051, in _call_impl
return forward_call(*input, **kwargs)
File "../models/stylegan1.py", line 557, in forward
x, x2 = m(x, dlatents_in[:, 2 * i:2 * i + 2])
File "/mnt/hdda/Data/envs/dataGan/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1051, in _call_impl
return forward_call(*input, **kwargs)
File "../models/stylegan1.py", line 391, in forward
x = self.conv0_up(x)
File "/mnt/hdda/Data/envs/dataGan/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1051, in _call_impl
return forward_call(*input, **kwargs)
File "../models/stylegan1.py", line 105, in forward
x = F.conv_transpose2d(x, w, stride=2, padding=(w.size(-1) - 1) // 2)
RuntimeError: Unable to find a valid cuDNN algorithm to run convolution

The error was due to an incompatibility between the version of Cuda and pytorch. After setting the appropriate versions the error disappears


Add support for testing SsoSilent login

Apologies for the formatting changes due to my auto linter and formatter, and this being my first time contributing to an open-source project. I will describe the main proposed changes below.

Add option for "Silent" interaction type in the constructor of MsalReactTester.
Add _ssoSilentSpy to spy on ssoSilent type logins.
Update waitForLogin to support ssoSilent type logins.
Update waitForLogout to default to using logoutRedirect when interaction type of MsalReactTester is "Silent".

On an unrelated note, is the spelling of interationType parameter of MsalReactTester intentional? It does not affect users of the test package but may confuse maintainers/contributors.
Any feedback is appreciated! Thank you!

Hey @lyuting47
Can you update your branch and merge it from main ?
And can you update your PR to preserve the formatting we have so far ?
Otherwise everything is marked as "changed" and it becomes difficult to review your PR
(and sorry for the ... almost 1 year delay on looking at your PR !!!!)


020875877604963 contains a Luhn sequence

I could easily be wrong, ( and often am, its the best way to learn), but my code is identifying a Luhn sequence in nonMatchingSequence(1000)
The sequence is<PHONE_NUMBER>04963 and at 15 chars the sequence is a Luhn sequence. The spec says 14 - 16 digits inclusive.<PHONE_NUMBER>04963 sums to 70. Code pushed to my fork of your repo.

Here's a link to the impl https://github.com/ieb/luhnybin/blob/master/luhnywriter/src/main/java/org/apache/people/ieb/luhn/LuhnOutputWriter.java
(license is ASL2, as stated in the pom.xml)

this is not luhn sequence. Here is why:
020875877604963
0         0      0
2 * 2    4      4
0         0      0
8 * 2  16  -> 7
7                 7
5 * 2  10  -> 1
8                8
7 * 2  14      5
7                 7
6 * 2   12  -> 3
0                 0
4 * 2    8      8
9                 9
6 * 2    12    3
3                 3
3 + 3 + 9 + 8 + 0 +  -> 23
3 + 7 + 5 + 8 + 1 +  -> 24
7 + 7 + 0 + 4 + 0     -> 18
-> 65 rem 10 = 5
no 70 here.

The example given in the ReadMe uses a zero based index. ie
0 * 2
2
0 * 2
8
7 * 2
etc
which gives 70. (just checked it again in a speadsheet)
Your calculation uses a 1 based index making the first number odd, hence not doubled, hence 65.
I dont know which is right, however, code written with a zero based index passes all the earlier tests in the test suite.
I suspect I am wrong since so many others have already provided solutions to the problem, and no one has noticed this.

the example of calculations he gives are a bit misleading. He makes it look like he starts counting from the left. Where as description has emphasis on the rightmost digits have to be processed first. So you have to start from the back and then you have to double every second digit. So, in the case of the sequence you have trouble with you start with 36940... and the first digit to double will be 6 then 4, etc.
I had the same question in comments ... hence I am being so smart :-)

Here are both sets, hope Markdown doesnt make a mess of this.
Zero Based index	Number	10s	1s
0	0	0	0
2	2		2
0	0	0	0
8	8		8
7	14	1	4
5	5		5
8	16	1	6
7	7		7
7	14	1	4
6	6		6
0	0	0	0
4	4		4
9	18	1	8
6	6		6
3	6	0	6
0
Total	70
1 Based index
0	0		0
2	4	0	4
0	0		0
8	16	1	6
7	7		7
5	10	1	0
8	8		8
7	14	1	4
7	7		7
6	12	1	2
0	0		0
4	8	0	8
9	9		9
6	12	1	2
3	3		3
Total	65

yes it is the 1 based index. And I hope it is clear that the index counting is from the back of the sequence. Your earlier tests passing are pure co-incidence.

Ahh, that makes sense, thanks for pointing that out.

At the risk of appearing like a complete idiot (again) :)
String x = nonMatchingSequence(MAX_LENGTH)
x = x + computeLast(tooMany);
==<PHONE_NUMBER>8540702
992[93161228540702]
ie last 14 digits
right to left double every second digit
9+3+1+6+1+2+2+8+5+4+0+7+0+2
(1+8)+3+(2)+6+(2)+2+(4)+8+(1+0)+4+(0)+7+(0)+2 = 50
in the test "too many digits" this is not supposed contain a luhn, but length == 14 and 50%10 = 0, passes the luhn check.
ie
String tooMany = nonMatchingSequence(MAX_LENGTH);
tooMany += computeLast(tooMany);
test("too many digits").sendAndExpect(tooMany);
I am using the tests at 6fda80c1f1c0b5cebc33f00a4081b5cc7d0f3ab3
please put me out of my misery, someone :)


Update jackson to 2.9.10

Description
Addresses security vulnerabilities:

sonatype-2016-0397: https://github.com/FasterXML/jackson-core/issues/315
sonatype-2017-0355: https://github.com/FasterXML/jackson-core/pull/322

This PR has:

[x] been self-reviewed.
[x] added or updated version, license, or notice information in licenses.yaml
[x] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[x] been tested in a test Druid cluster.

Also manually tested using https://druid.apache.org/docs/latest/tutorials/tutorial-batch-hadoop.html

Would you please add a list of tests you have done?

In the test cluster, I ran a kinesis ingestion task to check the updated jackson version compatibility with AWS SDK for Java version 1.x.
@jihoonson Are there any additional manual tests that you recommend?

Did another manual test that's a variant of https://druid.apache.org/docs/latest/tutorials/tutorial-batch-hadoop.html to have the hadoop index task ingest from s3 and then write to s3 via hdfs.

All the hadoop manual tests were done with hadoop 2.8.5.


Order of words issue

It is a order of words issue. The following"
''Across the Format pane, we’ve merged font family and font size onto a single line. Again, we want to reduce vertical space and better to align with Office.'' should be ''Across the Format pane, we’ve merged font family and font size onto a single line. Again, we want to reduce vertical space and TO better align with Office.''

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

ID: 99728831-9577-faee-e82a-8def045dadea
Version Independent ID: 99728831-9577-faee-e82a-8def045dadea
Content: The new Format pane in Power BI Desktop (preview) - Power BI
Content Source: powerbi-docs/fundamentals/desktop-format-pane.md
Service: powerbi
Sub-service: pbi-fundamentals
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Hi @vertig00bg,
Thank you for pointing this out, I'll fix it shortly.
Kesem

Hi @vertig00bg,
Thanks again for pointing out this error which I have now fixed - see Merged font settings.

Kesem


Updated Architecture

Description

Updated the architecture for:

SuperAGI Architecture
Agent Workflow
Tools Workflow
ER Diagram

Added new Contributors

Type of change

[x] Docs update

Checklist

[x] My pull request is atomic and focuses on a single change.

 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.


What's the correct way to break the PipeReader loop?

This page show many incorrect demonstrations.
But what's the correct way?
Is this the only correct way?

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

ID: 2f5384a7-5e96-d977-7748-317a2c758f63
Version Independent ID: 06e72212-a052-a351-0e0b-1b002ce214de
Content: I/O pipelines - .NET
Content Source: docs/standard/io/pipelines.md
Product: dotnet-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Yes assuming you want to throw for incomplete messages.

Yes assuming you want to throw for incomplete messages.

So, result.IsComplete && buffer.Length == 0 means all messages are read complete?

Yes but look at the examples. There are 2 code samples. One for reading a single message and one for reading many messages. The code is different depending on what you're trying to do.

Yes but look at the examples. There are 2 code samples. One for reading a single message and one for reading many messages. The code is different depending on what you're trying to do.

I have another question is that why the single message example never call reader.Complete? Will this make memory leak?

When reading a single message at a time you don't want to complete the reader, that would mean you can't read anymore messages. In the case of reading a single message, the caller is responsible for completing the reader.

Got it, thanks your guide.

Opening as we can probably add some of this to the doc.

The primary way to break a PipeReader loop is to return one or more messages.  The loop is there to keep reading from the pipe until you can parse one.  The method is designed to block until it can return messages.
The IsCompleted check is there to handle the lesser case that the Stream is finished (for something like a file) or closed/disconnected (for something like a network connection).


Sentence similarity: Message "Columns not selected are automatically ignored." should be showed on the "Data" page.

System Information (please complete the following information):
Windows OS: Windows-11-Enterprise-22H2
ML.Net Model Builder 2022: <IP_ADDRESS>7701 (Main Build)
Microsoft Visual Studio Enterprise: 2022(17.4.4)
.Net: 6.0
Describe the bug

On which step of the process did you run into an issue:
The Console App and Web API projects are generated failed on the Consume page.

TestMatrix
home-depot-sentence-similarity-small.csv
To Reproduce
Steps to reproduce the behavior:

Select Create a new project from the Visual Studio start window.
Choose the C# Console App (.NET Core) project template.
Add model builder by right click on the project.
Select "Sentence similarity" scenario.
On Data page, check the message under "Data Preview".

Expected behavior
Message "Columns not selected are automatically ignored." should be showed under "Data Preview".
Screenshot

Additional context

The bug has been fixed on the latest main build <IP_ADDRESS>0301


move kibana to own location

If you have elasticsearch artifact in Nexus, then you won't be able to download it because of improper reverse proxy configuration for Kibana :) Here is dirty fix
elk.yml
    volumes:
      - /data/kibana.yml:/opt/kibana/config/kibana.yml

kibana.yml
server.basePath: '/kibana'
elasticsearch.url: 'http://elasticsearch:9200'

plugins.json
                    {
                        "id": "kibana",
                        "title": "kibana",
                        "img": "img/kibana.png",
                        "description": "Kibana Dashboard for Logging (ELK)",
                        "link": "/kibana/"
                    },

tools-context.conf
    location ~ ^/kibana/(.*)$ {
        rewrite /kibana/(.*) /$1 break;
        proxy_pass http://kibana:5601;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $http_host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Host $http_host;
        proxy_redirect off;
        proxy_cache_bypass $http_upgrade;
    }

Workarounds with locations blocks /kibana, /kibana/status, /app/kibana/status, /app/kibana.*, /bundles/.*, /status, /plugins/kibana/.*, /api/status, /elasticsearch/.* should be removed

Hi @avoidik, what do you mean by "elasticsearch artifact in Nexus"?

@svscorp let's imagine deployed ADOP stack, if someone or something uploads new artifact into Nexus named elasticsearch, then you wont be able to download it because of error from Kibana
Case

Download JAR from https://mvnrepository.com/artifact/org.elasticsearch/elasticsearch/2.3.1
Upload it to Nexus manually as is via WebGUI (by GAV parameters with auto-guess)
Browse Browse Storage in WebGUI and try to navigate to the freshly uploaded artifact elasticsearch
If you refer to network log, then you might see a lot of 301 redirects which are initially triggered by kibana
if you dig deeper to RCA then you will find that this workarounds blocks causes this


Version 1.2.4 with Babashka throws an exception

$ BABASHKA_PRELOADS="" bb --config <(echo "{:deps {zprint/zprint {:mvn/version \"1.2.3\"} org.babashka/spec.alpha {:git/url \"https://github.com/babashka/spec.alpha\" :git/sha \"8df0712896f596680da7a32ae44bb000b7e45e68\"}}}") -e "(require '[zprint.core :as z]) (z/czprint {:a 1})"
{:a 1}

$ BABASHKA_PRELOADS="" bb --config <(echo "{:deps {zprint/zprint {:mvn/version \"1.2.4\"} org.babashka/spec.alpha {:git/url \"https://github.com/babashka/spec.alpha\" :git/sha \"8df0712896f596680da7a32ae44bb000b7e45e68\"}}}") -e "(require '[zprint.core :as z]) (z/czprint {:a 1})"
----- Error --------------------------------------------------------------------
Type:     java.lang.Exception
Message:  of-node* does not exist
Location: zprint/zutil.cljc:3:3

----- Context ------------------------------------------------------------------
1: ;!zprint {:style :require-justify}
2: (ns ^:no-doc zprint.zutil
3:   (:require
     ^--- of-node* does not exist
4:     #?@(:bb []
5:         :clj [[zprint.macros :refer [do-redef-vars]]])
6:     clojure.string
7:     zprint.zfns
8:     #?@(:clj [[zprint.redef]])

----- Stack trace --------------------------------------------------------------
zprint.zutil   - zprint/zutil.cljc:3:3
zprint.rewrite - zprint/rewrite.cljc:2:3
zprint.config  - zprint/config.cljc:7:3
zprint.zprint  - zprint/zprint.cljc:6:3
zprint.core    - zprint/core.cljc:5:3
user           - <expr>:1:1

Yes, this is because zprint 1.2.4 upgraded its dependency on rewrite-clj, and since rewrite-clj deprecated edn*, zprint started using of-node*.  But babashka hadn't updated to the new version of rewrite-clj, and which version zprint was using ended up being the built-in version of rewrite-clj in babashka.  I asked how to solve this over at babashka, and  the suggestion was to use a pre-release of babashka from here
When I used a binary from this release: v0.9.162-SNAPSHOT it all worked for me.
I'm sorry that you need use a pre-release of babashka to fix this problem -- I spent a good while trying to figure out how to exclude rewrite-clj from babashka, with no success.  I'm also sorry that I didn't test 1.2.4 better, as I have a test for babashka which I neglected to run.  I'll ensure that I don't do that again.
Thanks for bringing this up!

All good, just wanted to document it in case others were wondering in the mean time. Thanks for this awesome library!


Cannot open <module>.node

All this loader appears to do (with/out basepath) is make my program look for the .node file at the root of my drive.

Do you use rewritePath? Could you share the rule and version of webpack?

Sure, I am using "webpack": "^4.23.1",
My rule is:
            {
                test: /\.node$/,
                loader: 'native-ext-loader',
                options: {
                    basePath: ['app.asar', 'renderer'],
                },
            },

This results in:
Uncaught Error: Cannot open E:\app.asar\renderer\opencv4nodejs.node: Error: Invalid package E:\app.asar

I feel like I've tried every combination of load and argument, every one seems to deal in absolute paths, so my built project never works if I rename my development filestructure. :/

When using a basePath it will always load the path in the runtime relatively to the __dirname. For some reason, path.resolve(__dirname, ...) resolves to the root path. Could you prepare a minimal reproduction repository?
Do you set node.__dirname manually or indirectly via another package?

I'm in the process of trying to figure something out but this will be an interesting consideration for your package:
https://github.com/webpack/webpack/issues/1599

I believe that you just need to set node.__dirname to false. This is how webpack works and I'm not sure how I could "consider" this to the package.

I only mean as a footnote. Some googling has found a great many people having similar looking pathing issues, and webpack seems to have a strange default of setting node.__dirname = undefined which results in __dirname = '/', and I'm not sure why. Obviously this package relies on node.__dirname being otherwise.

I appear to be much closer to the correct result, but I am getting an error that it is looking in:
C:\...\Local\Programs\amethyst\resources\app.asar\app\app.asar\renderer\opencv4nodejs.node
I'm unsure why it is trying app.asar\app\ twice, I have tried adding both '../../' and '..', '..' to the beginning of my basePath array, but they don't seem to have any effect. Any ideas would be really appreciated!

I don't think ../../ would work on Windows (shouldn't be ..\..\?). It is hard to help without the code ;)

I've finally solved it. It was just a case of clearing out all the weird attempts at everything I've tried, all the little copying of files and extra bits I've been banging my head against the wall with, and using your loader with all default options with the option node.__dirname: false in my webpack.
This has been painful but thank you for your package and assistance, I can finally rest. 🎉
Closing


PlantIT is not finding my plantit.yaml file

The file is located at https://github.com/AgPipeline/drone-makeflow/blob/main/plantit.yaml. All branches of this project have the YAML file.
When I scan for workflows I get a message saying that there aren't any plantit.yaml files. My GitHub account name is Chris-Schnaufer

I have also tried logging out and back in with no change in the result.
Previously, before I merged into the main branch, the YAML file was found, but it appeared that the file couldn't be loaded from that branch and an error was reported. This problem occurred after I merged to the main branch and removed the branch that the YAML file had originally been on.

Hi @Chris-Schnaufer, thanks for reporting this. Looks like a regression introduced in v0.0.30:
[2021-11-09 08:19:53,526: ERROR/ForkPoolWorker-1] Task plantit.celery_tasks.refresh_personal_workflows[5b8534fc-ada7-485b-915f-995a8f73965c] raised unexpected: TypeError("argument of type 'TypeError' is not iterable")
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/celery/app/trace.py", line 451, in trace_task
    R = retval = fun(*args, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/celery/app/trace.py", line 734, in __protected_call__
    return self.run(*args, **kwargs)
  File "/code/plantit/plantit/celery_tasks.py", line 443, in refresh_personal_workflows
    async_to_sync(refresh_personal_workflow_cache)(owner)
  File "/usr/local/lib/python3.10/site-packages/asgiref/sync.py", line 223, in __call__
    return call_result.result()
  File "/usr/local/lib/python3.10/concurrent/futures/_base.py", line 438, in result
    return self.__get_result()
  File "/usr/local/lib/python3.10/concurrent/futures/_base.py", line 390, in __get_result
    raise self._exception
  File "/usr/local/lib/python3.10/site-packages/asgiref/sync.py", line 292, in main_wrap
    result = await self.awaitable(*args, **kwargs)
  File "/code/plantit/plantit/utils.py", line 421, in refresh_personal_workflow_cache
    tasks = await asyncio.gather(*[
  File "/code/plantit/plantit/utils.py", line 388, in workflow_to_dict
    bundle = await github.get_repo_bundle(
  File "/code/plantit/plantit/github.py", line 284, in get_repo_bundle
    valid = validate_repo_config(config, cyverse_token)
  File "/code/plantit/plantit/github.py", line 22, in validate_repo_config
    if 'name' not in config:
TypeError: argument of type 'TypeError' is not iterable

Working on a test case and fix

I am still not able to run any tasks since it appears that the YAML file is not found: https://github.com/Chris-Schnaufer/drone-makeflow

Hi @Chris-Schnaufer, yesterday's patch should address this. YAML files no longer need to be bound explicitly - they should be automatically detected and shown. There is also a new dropdown option on the Workflows page to view organization-owned repositories. These are also automatically scraped from GitHub.
Are you able to see your repositories in the Workflows view now? Sorry again for the delay in fixing this.

@w-bonelli I am still having problems - primarily I am unable to start Tasks.
The Workflow reports that I don't have any:

But, I am able to connect to AgPipeline where it shows two options link to project:

For Tasks, I don't have the option to run one, even though the YAML file exists:

Apologies @Chris-Schnaufer, the unnamed workflows should be selectable now: if you click the placeholder "name not provided" link it should open a detail view. Then if you select Submit it will show a submission menu, e.g. (my reproduction):

Adding a name attribute to your plantit.yaml will remove the warning message and display the value of that attribute instead. (Workflows are refreshed every 5 minutes so the update will take a brief period to register in the UI.)
Looks like the repositories shown in the AgPipeline context are the two branches of the drone-makeflow repo. If you have personal forks of these we unfortunately can't access them yet due to limitations of the Github API. Any non-fork public repos with plantit.yaml files in any branch should be visible, though - let me know if this is not the case.
The public Stampede2 agent should be listed as a submission target. Just confirmed it is working for our test pipeline but if you encounter submission failures please let me know and happy to help debug.

Workflow integration seems to be working correctly now but please feel free to reopen if there are any more issues


adding firefox config settings

Additional info for Firefox and enabling webrtc

@sepulworld thanks! I will change your commit message a bit in order for the checks to pass.

Yes, I tested that and it works as well. You either set that to false or whitelist your camera IP. Either one worked for me. Feel free to update PR or I can do it later this evening

@balena-ci retest


[FLINK-26014][docs] Add documentation for how to configure the working directory

Adds documentation about how to use the FLIP-198 and FLIP-201 feature.

@infoverload if you have time for a review, then this would be awesome.

Thanks for the review @zentol. I will address your comment and then merge it.


Add MET and METplus packages

Create packages for MET/METplus. Tested with apple-clang, Intel, and GCC.
This depends on https://github.com/NOAA-EMC/spack/pull/24

I approved the Spack PR https://github.com/NOAA-EMC/spack/pull/24. You can update the submodule pointer here after it is merged (maybe you can include the parallelio bugfix as well).


Make login the main activity

Is your feature request related to a problem? Please describe.
Currently the application launches with the homepage rather than the login
Describe the solution you'd like
edit the manifest to make the login screen the first activity to launch

Merged.


A request for the souce code for training the model

Hi,
I saw the models for Parse SPRING, Parse T5, Parse GSII, Generate T5wtense, Generate T5. But I did not see the source code for them. Can you post the source code for training those models? Thank you so much.
Merry Christmas.

Look in the scripts directory.

Thanks a lot!


KARAF-3982: Add support for editing property files to the assembly mojo.

This appears to be all done.

Hello, what do you think about the append / prepend hint?

Done
On Sep 14, 2015 2:59 PM, "Markus Rathgeb"<EMAIL_ADDRESS>wrote:

Hello, what do you think about the append / prepend hint?
—
Reply to this email directly or view it on GitHub
https://github.com/apache/karaf/pull/80#issuecomment-140176415.

Hi @bimargulies,
what about variable substitution? Using e.g. ${project.version} e.g. in an added value for a property seems a valid and perhaps common use case. What do you think about?

e.g. a attribute for the value tag "substitue" to switch the substitution (InterpolationHelper.substVars(...)) on / off.


Particle CLI cant load Firmware Binary - Electron

I have downloaded the binary, but cannot upload to Elektron.
Basically I have the same problem as here https://community.particle.io/t/particle-cli-cant-load-firmware-binary-electron-at-t-data-card-solved/205151, except reinstalling nodejs and particle cli does NOT solve the problem.
So I downloaded the firmware binary and trying to flash it to Elektron via USB using Linux Mint and particle cli.
myuser@laptop ~/Documents/Particle $ nodejs --version
v0.10.37
myuser@laptop ~/Documents/Particle $ particle --version
1.11.0
myuser@laptop ~/Documents/Particle $ particle identify
Your device id is myDeviceID
Your IMEI is myIMEI
Your ICCID is myICCID
Your system firmware version is 0.4.8
myuser@laptop ~/Documents/Particle $ particle flash --serial blink.bin
! PROTIP: Hold the SETUP button on your device until it blinks blue!
? Press ENTER when your device is blinking BLUE
sending file: blink.bin

! serial:
Error writing firmware...TypeError: Cannot call method 'copy' of undefined
TypeError: Cannot call method 'copy' of undefined
at Function.Buffer.concat (buffer.js:499:9)
at Object.YModem.sendPacket (/usr/lib/nodemodules/particle-cli/lib/ymodem.js:179:20)
at Object.YModem.sendFileHeader (/usr/lib/nodemodules/particle-cli/lib/ymodem.js:173:15)
at start (/usr/lib/node_modules/particle-cli/lib/ymodem.js:147:17)
at runTask (/usr/lib/node_modules/particle-cli/node_modules/when/pipeline.js:37:16)
at /usr/lib/node_modules/particle-cli/node_modules/when/pipeline.js:42:12
at tryCatchResolve (/usr/lib/node_modules/particle-cli/node_modules/when/lib/apply.js:46:23)
at callAndResolve (/usr/lib/node_modules/particle-cli/node_modules/when/lib/apply.js:30:12)
at callAndResolveNext (/usr/lib/node_modules/particle-cli/node_modules/when/lib/apply.js:40:4)
at tryCatchReject3 (/usr/lib/node_modules/particle-cli/node_modules/when/lib/makePromise.js:856:7)

What I am doing wrong?
What NodeJS / particle cli version am I supposed to be using?
After upgrade nodejs to v0.10.43, the latest in the 0.10.x series the issue is still there.

After a few trials I finally succeeded with node v5.7.1;
$ particle flash --serial blink.bin
! PROTIP: Hold the SETUP button on your device until it blinks blue!
? Press ENTER when your device is blinking BLUE
sending file: blink.bin
Flash success!
Aborted

Hmm, the node version definitely doesn't need to be that new. I'm going to reopen this for more investigation.

Okey, I was surprised too, I thought it must be something else not the version, so it was a bit of a surprise that it was working with v5.7.1, specially as I have also tried v0.12.11 before and that hasn't worked either, so I was about to give up.

I'm encountering this same problem with my electron using nodejs=0.10.37-1chl1~utopic1.
but when I install nodejs 5.9.0 I get a different error:
 > sudo particle flash --serial firmware-binaries/blink.bin
Error loading command /usr/lib/node_modules/particle-cli/commands/SerialCommand.js Error: Cannot find module '/usr/lib/node_modules/particle-cli/node_modules/serialport/build/Release/node-v47-linux-x64/serialport.node'
/usr/lib/node_modules/particle-cli/commands/FlashCommand.js:146
		return serial.flashDevice.apply(serial, arguments);
		             ^

TypeError: Cannot read property 'flashDevice' of undefined
    at Object.extend.flashYModem (/usr/lib/node_modules/particle-cli/commands/FlashCommand.js:146:16)
    at Object.extend.flashSwitch (/usr/lib/node_modules/particle-cli/commands/FlashCommand.js:122:18)
    at Object.BaseCommand.runCommand (/usr/lib/node_modules/particle-cli/commands/BaseCommand.js:108:17)
    at Object.Interpreter.runCommand (/usr/lib/node_modules/particle-cli/lib/interpreter.js:93:13)
    at Object.Interpreter.handle (/usr/lib/node_modules/particle-cli/lib/interpreter.js:55:18)
    at Object.<anonymous> (/usr/lib/node_modules/particle-cli/bin/particle.js:20:5)
    at Module._compile (module.js:413:34)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)

I'll try installing nodejs v5.7.1 specifically.
BTW- I'm running Ubuntu 15.10.

With 5.7.1 I have the same problem:
> sudo particle flash --serial firmware-binaries/blink.bin
Error loading command /usr/lib/node_modules/particle-cli/commands/SerialCommand.js Error: Cannot find module '/usr/lib/node_modules/particle-cli/node_modules/serialport/build/Release/node-v47-linux-x64/serialport.node'
/usr/lib/node_modules/particle-cli/commands/FlashCommand.js:146
		return serial.flashDevice.apply(serial, arguments);
		             ^

TypeError: Cannot read property 'flashDevice' of undefined
    at Object.extend.flashYModem (/usr/lib/node_modules/particle-cli/commands/FlashCommand.js:146:16)
    at Object.extend.flashSwitch (/usr/lib/node_modules/particle-cli/commands/FlashCommand.js:122:18)
    at Object.BaseCommand.runCommand (/usr/lib/node_modules/particle-cli/commands/BaseCommand.js:108:17)
    at Object.Interpreter.runCommand (/usr/lib/node_modules/particle-cli/lib/interpreter.js:93:13)
    at Object.Interpreter.handle (/usr/lib/node_modules/particle-cli/lib/interpreter.js:55:18)
    at Object.<anonymous> (/usr/lib/node_modules/particle-cli/bin/particle.js:20:5)
    at Module._compile (module.js:413:34)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)

> node -v
v5.7.1

I updated particle-cli with:
sudo npm install -g particle-cli
and now I get:
> sudo particle flash --serial firmware-binaries/blink.bin
! PROTIP: Hold the SETUP button on your device until it blinks blue!
? Press ENTER when your device is blinking BLUE
sending file: firmware-binaries/blink.bin

! serial:
Error writing firmware...unknown message
undefined

Tried again after reset and it now works!

@ooniverse thanks for the additional data!

You're welcome.  Thanks for all the helpful support.  I wouldn't have been able to figure this out so quickly without all the useful pointers from previous posters.

I had already updated to the latest particle-cli before installing the new nodjs version.
It must be order dependent . . . need to update particle-cli AFTER nodejs.

Yeah, looking at your error closely, it had trouble loading node-serialport

Error loading command /usr/lib/node_modules/particle-cli/commands/SerialCommand.js Error: Cannot find module '/usr/lib/node_modules/particle-cli/node_modules/serialport/build/Release/node-v47-linux-x64/serialport.node'

If you updated node, but didn't reinstall then you would get that.

just installed node.js and particle cli, will not flash my electron through the usb serial, it does work over the air.
in addition dfu-utill cannot find libusb-1.0.dll even though it is in the same folder.  flash -usb claims dfu-util was not installed even though it is also located in the windows/system32 folder

Can you try doing it over serial with particle flash --serial xxxxxx.bin?
ken
sent on mobile
On 29 Sep 2016 14:43, "sobellinni"<EMAIL_ADDRESS>wrote:
just installed node.js and particle cli, will not flash my electron through
the usb serial, it does work over the air.
in addition dfu-utill cannot find libusb-1.0.dll even though it is in the
same folder. flash -usb claims dfu-util was not installed even though it is
also located in the windows/system32 folder
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/spark/particle-cli/issues/224#issuecomment-250383734,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGcp0nuAy6oNG8k6Qv2h3IKzD4OvSGGlks5qu14OgaJpZM4HqH5f
.

It turns out that I tried it  with a binary generated by your PC tools - which tell me that the compilation is on line . This did not work, although the serial loader in the cli said it loaded.  The program that was put into the electron did not work.
However, when I compiled the exact same code with the on line IDE , downloaded it to my computer and then loaded with the serial loader, it worked. Art Sobel
Hardware Engineering
Advanced RISC Technology
  From: Kenneth Lim<EMAIL_ADDRESS>
To: spark/particle-cli<EMAIL_ADDRESS>Cc: sobellinni<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Sent: Wednesday, September 28, 2016 11:49 PM
Subject: Re: [spark/particle-cli] Particle CLI cant load Firmware Binary - Electron (#224)
Can you try doing it over serial with particle flash --serial xxxxxx.bin?
ken
sent on mobile
On 29 Sep 2016 14:43, "sobellinni"<EMAIL_ADDRESS>wrote:
just installed node.js and particle cli, will not flash my electron through
the usb serial, it does work over the air.
in addition dfu-utill cannot find libusb-1.0.dll even though it is in the
same folder. flash -usb claims dfu-util was not installed even though it is
also located in the windows/system32 folder
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/spark/particle-cli/issues/224#issuecomment-250383734,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGcp0nuAy6oNG8k6Qv2h3IKzD4OvSGGlks5qu14OgaJpZM4HqH5f
.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Could you please post more details of the steps you took that worked and the ones that did not work? We'll get to the bottom of this.

the .bin files are quite different  Art Sobel
Hardware Engineering
Advanced RISC Technology
  From: Kenneth Lim<EMAIL_ADDRESS>
To: spark/particle-cli<EMAIL_ADDRESS>Cc: sobellinni<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Sent: Wednesday, September 28, 2016 11:49 PM
Subject: Re: [spark/particle-cli] Particle CLI cant load Firmware Binary - Electron (#224)
Can you try doing it over serial with particle flash --serial xxxxxx.bin?
ken
sent on mobile
On 29 Sep 2016 14:43, "sobellinni"<EMAIL_ADDRESS>wrote:
just installed node.js and particle cli, will not flash my electron through
the usb serial, it does work over the air.
in addition dfu-utill cannot find libusb-1.0.dll even though it is in the
same folder. flash -usb claims dfu-util was not installed even though it is
also located in the windows/system32 folder
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/spark/particle-cli/issues/224#issuecomment-250383734,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGcp0nuAy6oNG8k6Qv2h3IKzD4OvSGGlks5qu14OgaJpZM4HqH5f
.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I installed Node.js , Particle-cli, and Atom IDE
I modified the  Blink program
Used the Cloud compile command after selecting my Electron device radio-ranger
Using the command  flash --serial  electron_program.bin
the response was success, but the Electron did not do anything
Then I modified the same program in the on line IDE , compiled on the IDE and downloaded the file to the same directory
Using the command  flash --serial  program.bin
the response was success, and the program worked
frustrated by this i also installed the dfu-util and libusb-1.0.dll
flash --usb  electron_program.bin could not  find dfu-util
dfu-util -1 could not  find libusb-1.0.dll even though it was in the same directory
  From: Julien Vanier<EMAIL_ADDRESS>
To: spark/particle-cli<EMAIL_ADDRESS>Cc: sobellinni<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Sent: Thursday, September 29, 2016 4:38 PM
Subject: Re: [spark/particle-cli] Particle CLI cant load Firmware Binary - Electron (#224)
Could you please post more details of the steps you took that worked and the ones that did not work? We'll get to the bottom of this.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
// ------------
// Blink D6 D7
// ------------
/*-------------
We've heavily commented this code for you. If you're a pro, feel free to ignore it.
Comments start with two slashes or are blocked off by a slash and a star.
You can read them, but your device can't.
It's like a secret message just for you.
Every program based on Wiring (programming language used by Arduino, and Particle devices) has two essential parts:
setup - runs once at the beginning of your program
loop - runs continuously over and over
You'll see how we use these in a second.
This program will blink an led on and off every second.
It blinks the D7 LED on your Particle device. If you have an LED wired to D6, it will blink that LED as well.
-------------*/
// First, we're going to make some variables.
// This is our "shorthand" that we'll use throughout the program:
int led1 = D6; // Instead of writing D6 over and over again, we'll write led1
// You'll need to wire an LED to this one to see it blink.
int led2 = D7; // Instead of writing D7 over and over again, we'll write led2
// This one is the little blue LED on your board. On the Photon it is next to D7, and on the Core it is next to the USB jack.
// Having declared these variables, let's move on to the setup function.
// The setup function is a standard part of any microcontroller program.
// It runs only once when the device boots up or is reset.
void setup() {
// We are going to tell our device that D6 and D7 (which we named led1 and led2 respectively) are going to be output
  // (That means that we will be sending voltage to them, rather than monitoring voltage that comes from them)
// It's important you do this here, inside the setup() function rather than outside it or in the loop function.
pinMode(led1, OUTPUT);
  pinMode(led2, OUTPUT);
}
// Next we have the loop function, the other essential part of a microcontroller program.
// This routine gets repeated over and over, as quickly as possible and as many times as possible, after the setup function is called.
// Note: Code that blocks for too long (like more than 5 seconds), can make weird things happen (like dropping the network connection).  The built-in delay function shown below safely interleaves required background activity, so arbitrarily long delays can safely be done if you need them.
void loop() {
  // To blink the LED, first we'll turn it on...
  digitalWrite(led1, LOW);
  digitalWrite(led2, HIGH);
// We'll leave it on for 1 second...
  delay(1500);
// Then we'll turn it off...
  digitalWrite(led1, HIGH);
  digitalWrite(led2, LOW);
// Wait 1 second...
  delay(1000);
// And repeat!
}

Alright, this is enough information to dig into this. From your comment I see you are on Windows. I'll reproduce the steps you wrote up and I'll post back here.


Tutorial documentation can install a broken combination of snakemake/tabulate

The stable/latest/master documentation for the tutorial, e.g. at https://snakemake.readthedocs.io/en/master/tutorial/setup.html, all contain a mamba environment requiring only snakemake >=5.24.1. On CentOS 7, this led to the installation snakemake v6.15.5, and the first tutorial example failed due to the previously reported issue https://github.com/snakemake/snakemake/pull/1898. Updating the environment.yaml provided by the tutorial to require snakemake >= 7.15.2 and jinja2 >=3.0 resolved the issue in the tutorial examples.

Unfortunately the same thing happens on WSL Ubuntu.


Add date preset for the last day for filtering findings

Hello, it would be great if defect dojo had the last day preset for filtering findings. We want to use the filter to calculate daily KPIs.

Where would you like to see it (search, api, ...) what is your definition of 'last day'? There is a 'today' filter, do you mean a 'yesterday' filter?

@valentijnscholten  I mean the last 24hours filter. I'd like to see it both in API and metrics filtering.
Thank you!

It could be added, but could you elaborate on the usecase? I think filtering by 'today' is more common compared to 'last 24 hours` which would result in some kind of running window for the date range.

Today is also possible. We want to use it for daily triage/review stats by requesting this data via API with a scheduled script.


Addition of the DyanmoDB resource, can add add tables, and also add global secondary indexes to existing tables

PR for merge into main branch, to add to existing PR into chef-cookbooks/aws

hai chris, not sure why I'm still getting notifications, but GOOD JOB!


[UPDATE ALGORITHM] Indian denomination problem

Description:
Please describe the changes you want to make to the existing algorithm and why they are necessary.
[Indian denomination problem]
optimize this code using dynamic problem;
current space and time complexity is - O(n log n + n * n) and O(n + amount) respectively.
Checklist:

[X] Contributor in GSSoC-ext
[X] Want to work on it

Affected Algorithm:
[Indian denomination proble
@pankaj-bind can i work on this/

assigned


Update scalafmt-core to 3.7.0

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

Files still referring to the old version number
The following files still refer to the old version number (3.6.1).
You might want to review and update them manually.
website/.yarn/unplugged/node-gyp-npm-9.1.0-2091059b31/node_modules/node-gyp/CHANGELOG.md

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

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

labels: library-update, early-semver-minor, semver-spec-minor, old-version-remains, commit-count:n:3

Superseded by #142.


[8.x] Added "MessageGroupId" to SQS Queue if queue is a fifo.

I tested Amazon SQS "FIFO" queues and the response said that the "MessageGroupId" parameter was missing from the request for "sendMessage", so I added a condition, if the queue name contains ".fifo" in the name, I enter the "MessageGroupId" parameter with an MD5 encryption of the Queue name.

This doesn't seem right. It'll force the concurrency down to 1 for lambda processing?

If it doesn't feel right, what is the best way to work with FIFO queues in the framework?
I had to create a package to clean up the payload sent by Laravel's default Queue. In this case, I needed to send a payload of data to my FIFO queue and use a trigger for a Python lambda that processed this data coming from a Job from a Laravel application.
My package would not work without the "MessageGroupId" parameter in the "sendMessage" method arguments.
Another question, can we have normal queues, but not FIFO?
Thanks your comment.

I think there is a lot more pieces that need to be put in place to properly support FIFO queues? They have a lot of features. We do have this on our backlog though.
You may be interested in this in the meantime: https://github.com/shiftonelabs/laravel-sqs-fifo-queue

Right, i'm understand. I am go work on this case for  implement on the future.
Thanks, Taylor


net/http: Transport doesn't discard connections which received a 408 Request Timeout

What version of Go are you using (go version)?

$ go version
go version go1.14.2 linux/amd64

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOENV="/root/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build338312077=/tmp/go-build -gno-record-gcc-switches"

What did you do?
II'm reading net/http for implementing HTTP client in Go. I want to use connections pool functionality of it but not sure how to deal with the stale connections.
*http.Transport says it retries the request if a connection got closed by server while it was trying to read the response.
https://github.com/golang/go/blob/a88c26eb286098b4c8f322f5076e933556fce5ac/src/net/http/transport.go#L640-L645
Since #32310, the connection is discarded also when 408 Request Timeout is sent on it.
https://github.com/golang/go/blob/a88c26eb286098b4c8f322f5076e933556fce5ac/src/net/http/transport.go#L2127-L2135
But if a connection receives 408 as a response to the request, no retry is held and that connection doesn't get discarded. So the client of *http.Transport sees 408 response repeatedly until that connection actually gets closed from the server.
Two open questions:

Is it the client(of *http.Transport)'s responsibility to retry the request when it sees 408?
And why *http.Transport doesn't discard connections which got 408?

You can reproduce this situation with the server which responses 408 for requests but doesn't close the connection immediately:
package main

import (
	"context"
	"fmt"
	"io"
	"io/ioutil"
	"net/http"
	"net/http/httptest"
	"net/http/httptrace"
	"runtime"
	"time"
)

func main() {
	fmt.Println(runtime.Version())

	server := httptest.NewServer(http.HandlerFunc(func(rw http.ResponseWriter, req *http.Request) {
		http.Error(rw, "", http.StatusRequestTimeout)
	}))
	defer server.Close()

	req, err := http.NewRequestWithContext(
		httptrace.WithClientTrace(context.Background(), &httptrace.ClientTrace{
			GotConn: func(info httptrace.GotConnInfo) {
				fmt.Printf("WasIdle: %v\n", info.WasIdle)
			},
		}),
		"GET", server.URL, nil,
	)
	if err != nil {
		panic(err)
	}

	for i := 0; i < 3; i++ {
		fmt.Printf("===== %d =====\n", i)
		res, err := http.DefaultTransport.RoundTrip(req)
		if err != nil {
			panic(err)
		}
		fmt.Println(res)
		io.Copy(ioutil.Discard, res.Body)
		res.Body.Close()
		time.Sleep(time.Second)
	}
}

Then the client always sees 408 through the cached connection.
go1.14.2
===== 0 =====
WasIdle: false
&{408 Request Timeout 408 HTTP/1.1 1 1 map[Content-Length:[1] Content-Type:[text/plain; charset=utf-8] Date:[Thu, 14 May 2020 02:00:53 GMT] X-Content-Type-Options:[nosniff]] 0xc000190080 1 [] false false map[] 0xc000142000 <nil>}
===== 1 =====
WasIdle: true
&{408 Request Timeout 408 HTTP/1.1 1 1 map[Content-Length:[1] Content-Type:[text/plain; charset=utf-8] Date:[Thu, 14 May 2020 02:00:54 GMT] X-Content-Type-Options:[nosniff]] 0xc000092240 1 [] false false map[] 0xc000142000 <nil>}
===== 2 =====
WasIdle: true
&{408 Request Timeout 408 HTTP/1.1 1 1 map[Content-Length:[1] Content-Type:[text/plain; charset=utf-8] Date:[Thu, 14 May 2020 02:00:55 GMT] X-Content-Type-Options:[nosniff]] 0xc00021e080 1 [] false false map[] 0xc000142000 <nil>}

What did you expect to see?
When *http.Transport get 408 as a response, it should discard the connection and retry with another.
What did you see instead?
When *http.Transport get 408 as a response, it doesn't discard the connection nor retry.

/cc @bradfitz @bcmills

Per https://tools.ietf.org/html/rfc7231#section-6.5.7:

A server SHOULD send the "close" connection option
(Section 6.1 of [RFC7230]) in the response, since 408 implies that
the server has decided to close the connection rather than continue
waiting.

Does this server, in fact, close the connection?
Per https://pkg.go.dev/net/http?tab=doc#Error:

Error replies to the request with the specified error message and HTTP code. It does not otherwise end the request; the caller should ensure no further writes are done to w.

That suggests to me that it does not, but I don't actually know offhand. (Perhaps @bradfitz has more insight?)

Also per https://tools.ietf.org/html/rfc7231#section-6.5.7:

If the client has an outstanding request in transit, the
client MAY repeat that request on a new connection.

The use of the word “MAY” indicates that *http.Transport complies with the RFC even if it does not retry. So if there is a bug here, I suspect that it is on the server side.


Core components

~Button~

Primary (orange)
Secondary (blue)
Tertiary (white)

Link
Typography
~Logo~
~Card~
Icon
Datetime
~Footer~

Are we separating out more specific components into a different list? (eg: Event Cards)

Yeah, that was my plan. Might make sense to put button, etc. in a core/ directory. Then the other top level stuff within components/ will be molecules.


chore: use official docker image and cleanup

Part of #61
Cleans up the customer docker related stuff we have for synthetics prior to 7.12 versions.
Uses the official beats heartbeat image for all kinds of testing and also updated the heartbeat monitor config with the latest syntax changes.

:grey_exclamation: Build Aborted

Either there was a build timeout or someone aborted the build.'}

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: Pull request #257 opened

Start Time: 2021-04-20T14:37:28.130+0000

Duration: 24 min 5 sec

Commit: c2b48b3f29fcb29254e325a5a4de1ac991b20d4e

Test stats :test_tube:

Test
Results

Failed
0

Passed
74

Skipped
0

Total
74

Trends :test_tube:

Log output
Expand to view the last 100 lines of log output

[2021-04-20T14:46:18.881Z] Snapshots:   8 passed, 8 total
[2021-04-20T14:46:18.881Z] Time:        24.352 s
[2021-04-20T14:46:18.881Z] Ran all test suites.
[2021-04-20T14:46:20.160Z] Post stage
[2021-04-20T14:46:20.190Z] Recording test results
[2021-04-20T14:46:20.240Z] [Checks API] No suitable checks publisher found.
[2021-04-20T14:46:20.407Z] Timeout set to expire in 15 min
[2021-04-20T14:46:21.446Z] Running in /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-257/src/github.com/elastic/synthetics
[2021-04-20T14:46:36.630Z] + set +x
[2021-04-20T14:46:36.630Z] => nvm is already installed in /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-257/.nvm, trying to update using git
[2021-04-20T14:46:37.202Z]
=> => Compressing and cleaning up git repository
[2021-04-20T14:46:37.202Z]
[2021-04-20T14:46:37.202Z] => Profile not found. Tried ~/.bashrc, ~/.bash_profile, ~/.zshrc, and ~/.profile.
[2021-04-20T14:46:37.202Z] => Create one of them and run this script again
[2021-04-20T14:46:37.202Z]    OR
[2021-04-20T14:46:37.202Z] => Append the following lines to the correct file yourself:
[2021-04-20T14:46:37.202Z]
[2021-04-20T14:46:37.202Z] export NVM_DIR="$HOME/.nvm"
[2021-04-20T14:46:37.202Z] [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[2021-04-20T14:46:37.202Z]
[2021-04-20T14:46:39.121Z] => Close and reopen your terminal to start using nvm or run the following to use it now:
[2021-04-20T14:46:39.121Z]
[2021-04-20T14:46:39.121Z] export NVM_DIR="$HOME/.nvm"
[2021-04-20T14:46:39.121Z] [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[2021-04-20T14:46:39.121Z] Installing latest LTS version.
[2021-04-20T14:46:39.382Z] v14.16.1 is already installed.
[2021-04-20T14:46:39.643Z] Now using node v14.16.1 (npm v6.14.12)
[2021-04-20T14:46:39.751Z] Running in /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-257/src/github.com/elastic/synthetics
[2021-04-20T14:46:40.088Z] + chmod -R ugo+rw examples
[2021-04-20T14:46:40.125Z] Running in /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-257/src/github.com/elastic/synthetics/__tests__/e2e
[2021-04-20T14:46:40.475Z] + npm run test
[2021-04-20T14:46:40.475Z]
[2021-04-20T14:46:40.475Z] > e2e-synthetics@ test /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-257/src/github.com/elastic/synthetics/__tests__/e2e
[2021-04-20T14:46:40.475Z] > npm i && npm run setup &&  bash scripts/test.sh
[2021-04-20T14:46:40.475Z]
[2021-04-20T14:46:43.785Z] added 3 packages from 4 contributors and audited 66 packages in 2.537s
[2021-04-20T14:46:46.336Z]
[2021-04-20T14:46:46.336Z] 49 packages are looking for funding
[2021-04-20T14:46:46.336Z]   run `npm fund` for details
[2021-04-20T14:46:46.336Z]
[2021-04-20T14:46:46.336Z] found 0 vulnerabilities
[2021-04-20T14:46:46.336Z]
[2021-04-20T14:46:46.336Z]
[2021-04-20T14:46:46.336Z] > e2e-synthetics@ setup /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-257/src/github.com/elastic/synthetics/__tests__/e2e
[2021-04-20T14:46:46.336Z] > bash scripts/setup.sh
[2021-04-20T14:46:46.336Z]
[2021-04-20T14:46:46.336Z]
[2021-04-20T14:46:46.336Z] Temporary folder
[2021-04-20T14:46:46.336Z] Temporary files will be stored in: ./tmp
[2021-04-20T14:46:46.336Z]
[2021-04-20T14:46:46.336Z] Starting elasticsearch , kibana and synthetics docker
[2021-04-20T14:46:46.336Z]
[2021-04-20T14:46:46.336Z]
[2021-04-20T14:46:46.336Z] Waiting for synthetics docker to start...
[2021-04-20T14:46:46.336Z] Error: No such object: synthetics
[2021-04-20T14:46:56.351Z] Error: No such object: synthetics
[2021-04-20T14:47:08.638Z] Error: No such object: synthetics
[2021-04-20T14:47:16.793Z] Error: No such object: synthetics
[2021-04-20T14:47:26.810Z] Error: No such object: synthetics
[2021-04-20T14:47:36.826Z] Error: No such object: synthetics
[2021-04-20T14:47:49.115Z] ✅ Setup completed successfully. Running e2e tests...
[2021-04-20T14:47:49.115Z] Waiting for Elastic Search  to start
[2021-04-20T14:48:36.083Z] Waiting for Synthetics to send data to ES for test monitor
[2021-04-20T15:01:20.407Z] Cancelling nested steps due to timeout
[2021-04-20T15:01:20.413Z] Sending interrupt signal to process
[2021-04-20T15:01:28.450Z] scripts/test.sh: line 26: 11192 Terminated              SYNTHETICS_JUNIT_FILE='junit.xml' npx @elastic/synthetics uptime.journey.ts --reporter junit
[2021-04-20T15:01:28.450Z] npm ERR! code ELIFECYCLE
[2021-04-20T15:01:28.450Z] Terminated
[2021-04-20T15:01:28.459Z] script returned exit code 143
[2021-04-20T15:01:29.787Z] Post stage
[2021-04-20T15:01:29.825Z] Archiving artifacts
[2021-04-20T15:01:29.870Z] Recording test results
[2021-04-20T15:01:29.884Z] None of the test reports contained any result
[2021-04-20T15:01:29.896Z] [Checks API] No suitable checks publisher found.
[2021-04-20T15:01:30.110Z] Stage "Publish Docker image" skipped due to earlier failure(s)
[2021-04-20T15:01:30.260Z] Stage "Matrix - STACK_VERSION = '8.0.0-synthetics'" skipped due to earlier failure(s)
[2021-04-20T15:01:30.268Z] Stage "Matrix - STACK_VERSION = '7.10.0-synthetics'" skipped due to earlier failure(s)
[2021-04-20T15:01:30.276Z] Stage "Matrix - STACK_VERSION = '7.11.0-synthetics'" skipped due to earlier failure(s)
[2021-04-20T15:01:30.351Z] Stage "Matrix - STACK_VERSION = '8.0.0-synthetics'" skipped due to earlier failure(s)
[2021-04-20T15:01:30.362Z] Stage "Matrix - STACK_VERSION = '7.10.0-synthetics'" skipped due to earlier failure(s)
[2021-04-20T15:01:30.370Z] Stage "Matrix - STACK_VERSION = '7.11.0-synthetics'" skipped due to earlier failure(s)
[2021-04-20T15:01:30.590Z] Stage "Matrix - STACK_VERSION = '8.0.0-synthetics'" skipped due to earlier failure(s)
[2021-04-20T15:01:30.603Z] Stage "Matrix - STACK_VERSION = '7.10.0-synthetics'" skipped due to earlier failure(s)
[2021-04-20T15:01:30.615Z] Stage "Matrix - STACK_VERSION = '7.11.0-synthetics'" skipped due to earlier failure(s)
[2021-04-20T15:01:30.848Z] Stage "Matrix - STACK_VERSION = '8.0.0-synthetics'" skipped due to earlier failure(s)
[2021-04-20T15:01:30.860Z] Stage "Matrix - STACK_VERSION = '7.10.0-synthetics'" skipped due to earlier failure(s)
[2021-04-20T15:01:30.869Z] Stage "Matrix - STACK_VERSION = '7.11.0-synthetics'" skipped due to earlier failure(s)
[2021-04-20T15:01:31.152Z] Failed in branch Matrix - STACK_VERSION = '8.0.0-synthetics'
[2021-04-20T15:01:31.169Z] Failed in branch Matrix - STACK_VERSION = '7.10.0-synthetics'
[2021-04-20T15:01:31.183Z] Failed in branch Matrix - STACK_VERSION = '7.11.0-synthetics'
[2021-04-20T15:01:31.477Z] Stage "Release" skipped due to earlier failure(s)
[2021-04-20T15:01:31.537Z] Stage "Release" skipped due to earlier failure(s)
[2021-04-20T15:01:31.655Z] Stage "Release" skipped due to earlier failure(s)
[2021-04-20T15:01:32.097Z] Running on Jenkins in /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-257
[2021-04-20T15:01:32.206Z] [INFO] getVaultSecret: Getting secrets
[2021-04-20T15:01:32.531Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2021-04-20T15:01:33.681Z] + chmod 755 generate-build-data.sh
[2021-04-20T15:01:33.681Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-257/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-257/runs/1 ABORTED 1445276
[2021-04-20T15:01:34.232Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-257/runs/1/steps/?limit=10000 -o steps-info.json
[2021-04-20T15:01:34.783Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-257/runs/1/tests/?status=FAILED -o tests-errors.json

@kuisathaverat I am planning to comment out the section in the Jenkins pipeline where we publish to the experimental namespace. Do you have any opposition?

I think you can remove it, we are releasing the official Heartbeat Docker image.

we have to rework on https://github.com/elastic/synthetics/pull/193 to test with the heartbeat Docker image