[HD] Remaining Flash references

Here's a list of things that I found maybe unnecessary for HD, feel free to complete/comment:

In HaxeContext / CompletionMode  you get to choose between "FlashDevelop / CompletionServer / Compiler".  Proposal : change it to "IDE Only" so it apply to both FD and HD :)

Hitting F6 in FD still try to launch Flash IDE, which I personnaly found annoying from time to time :)

Some plugins might be removed in HD to simplify Settings search: AS2Context, ASClassWizard, FlashConnect, FlashLogViewer, LoomContext? SWFProfiler in "View"

Project / AIR App Properties ?

Tools/FlashTools section

In Project Properties / Compiler Options,  we have EnableDebugger and Flash Strict which are flash specific.

On the debug topic maybe we should grey the Debug menu (with a tooltip for help) when we are not compiling for flash/air or when EnableDebugger=False

I need to check if we can change only the display name as this is serialized in settings and changing its value name would break it in existing settings.

But shouldn't you be able to work with Flash IDE/Animate in Haxe? You can remove the shortcut from shortcut manager if you want.

Some plugins are necessary as they are dependant from each other due to some extent. Some just contain Flash or AS in there name even if they are all purpose plugins. For example ASClassWizard is used also for Haxe.

Unnecessary SWC's, Loom stuff and FlexPMD are now removed from HD making it 10mb lighter. :)

AIR App Properties is a editor for AIR project xml files. There is a AIR project for Haxe too.

The debugger should become all purpose debugger later when we get some time to focus on it.

We will rename some of these plugins and items later down the line to be more generic.

Yes, I can understand some people want to animate things in Flash, but I think that's a minority compared to all other Haxe usages, and F6 happens to be just after F5 "Test Project" , which I (and I guess many other people too) hit accidentally from time to time. I think the shortcut should be removed from HD, you can keep the Flash IDE Launch in some menu if you want, but it shouldn't but put more forward than opening a browser or a console for instance.

I'm fine with that.
Well i work with Haxe JS quite a lot and for us its a normal to work with Flash/Animate to create assets for HTML5 games.


Initial Snippet Config

add initial template of how snippets will work. can be merged will just need updated once Regis sends his snippets over

closes #43

This looks good.  How about adding an example of using it in the comments here on the PR.

Does not close #43, reopened.


Use the constant for UserAgent

rather than inline string.
/assign @tcnghia

metrics
/test pull-knative-pkg-unit-tests

/test pull-knative-pkg-unit-tests

/lgtm
/approve

/approve


Version bump

@homu: r+ 3c1d7ba

:hourglass: Testing commit 3c1d7ba with merge 453e85a...

:sunny: Test successful - status


Building package aws-sdk-cpp:x86-windows failed with: BUILD_FAILED

Describe the bug
Following instructions step-by-step for vcpkg and aws-sdk-cpp.
.\vcpkg\vcpkg install "aws-sdk-cpp[lexv2-runtime]" fails with this error
Environment

Windows 11

To Reproduce
Steps to reproduce the behavior:

.\vcpkg\vcpkg install "aws-sdk-cpp[lexv2-runtime]"
See error

Expected behavior
Not this
Failure logs
CMake Error: Problem with archive_write_header(): Can't create '\\?\C:\Dev\vcpkg\vcpkg\buildtrees\aws-sdk-cpp\src\7237798297-e0c81eb359.clean.tmp\aws-sdk-cpp-26fa78673ec93dc703e80b741d8b437237798297\aws-cpp-sdk-ebs\include\aws\ebs\model\AccessDeniedException.h'
CMake Error: Current file: aws-sdk-cpp-26fa78673ec93dc703e80b741d8b437237798297/aws-cpp-sdk-ebs/include/aws/ebs/model/AccessDeniedException.h
CMake Error: Problem extracting tar: C:/Dev/vcpkg/vcpkg/downloads/aws-aws-sdk-cpp-26fa78673ec93dc703e80b741d8b437237798297.tar.gz

Additional context
Very vanilla installation and followed instructions step-by-step. Diagnostics were not helpful.

Additional info from the console:
package: aws-sdk-cpp[core,dynamodb,kinesis,lexv2-runtime,s3]:x86-windows -> 1.9.160
vcpkg-tool version: 2022-02-11-dac008bf9b55ef48e10bcc81e273b97a82bbf72d
vcpkg-scripts version: 5cf60186a 2022-02-18 (2 days ago)

Managed to hack my way past that because the "model" folder was somehow corrupt. Tried again (also as admin), but now hitting this:
CMake Error at scripts/cmake/vcpkg_extract_source_archive.cmake:236 (file):
file RENAME failed to rename
C:/Dev/vcpkg/vcpkg/buildtrees/aws-sdk-cpp/src/7237798297-e0c81eb359.clean.tmp/aws-sdk-cpp-26fa78673ec93dc703e80b741d8b437237798297

to
C:/Dev/vcpkg/vcpkg/buildtrees/aws-sdk-cpp/src/7237798297-e0c81eb359.clean

because: Access is denied.

This issue was fixed by PR https://github.com/microsoft/vcpkg-tool/pull/361 and this issue will be resolved by PR https://github.com/microsoft/vcpkg/pull/23162.


Update README.md

Include description of how it'll appear when it's working

Fixes #61

Thanks a lot. This will hopefully help others.


Cannot send native token value with gasless transaction

Hi,
is it possible that the user pays for a NFT (msg.value) but the relayer takes over the gasfee?
How could this be realized?
Currently i only resolve the message "Cannot send native token value with gasless transaction" by the sdk.
https://github.com/thirdweb-dev/js/blob/9886c858d9c8d0f677aba6572dbf5cc6c876edf2/packages/sdk/src/evm/core/classes/contract-wrapper.ts#L573
Thanks for your reply.
Cheers
Stephan

Hi @StephanGerbeth this is expected and a limitation of gasless relayers and a security measure.
The thing is that if you're passing msg.value in your transaction, you usually have enough to pay the gas fee as well. So its usually not an issue.
Let me know if that helps


Failed to reproduce the result with inference.py

** Idea sharing **
While sharing what you want to do, make sure to protect your ideas.
** Problems **
Used the setting and task dump given in the readme, and inference.py as follows, but got a low result: f1 0.6856. In detail, the precision is as expected, but the recall is way low.
** Others **
The code below is rather casual and informal, but should work. It concats all sentences in one doc as a string, then run dee_task.predict_one, and finally measure it with dee_metric.py.
import os

from dee.tasks import DEETask, DEETaskSetting

if __name__ == "__main__":
    # init
    task_dir = "Exps/sct-Tp1CG-with_left_trigger-OtherType-comp_ents-bs64_8"
    cpt_file_name = "TriggerAwarePrunedCompleteGraph"
    # bert_model_dir is for tokenization use, `vocab.txt` must be included in this dir
    # change this to `bert-base-chinese` to use the huggingface online cache
    bert_model_dir = "bert-base-chinese"

    # load settings
    dee_setting = DEETaskSetting.from_pretrained(
        os.path.join(task_dir, f"{cpt_file_name}.task_setting.json")
    )
    dee_setting.local_rank = -1
    dee_setting.filtered_data_types = "o2o,o2m,m2m,unk"
    dee_setting.bert_model = bert_model_dir

    # build task
    dee_task = DEETask(
        dee_setting,
        load_train=False,
        load_dev=False,
        load_test=False,
        load_inference=False,
        parallel_decorate=False,
    )

    # load PTPCG parameters
    dee_task.resume_cpt_at(57)

    import collections
    import copy
    import json
    import pathlib

    import dee_metric

    EVENT2SCHEMA ={'EquityOverweight': {'EquityHolder': '', 'TradedShares': '', 'StartDate': '', 'EndDate': '', 'LaterHoldingShares': '', 'AveragePrice': ''}, 'EquityUnderweight': {'EquityHolder': '', 'TradedShares': '', 'StartDate': '', 'EndDate': '', 'LaterHoldingShares': '', 'AveragePrice': ''}, 'EquityFreeze': {'EquityHolder': '', 'FrozeShares': '', 'LegalInstitution': '', 'TotalHoldingShares': '', 'TotalHoldingRatio': '', 'StartDate': '', 'EndDate': '', 'UnfrozeDate': ''}, 'EquityRepurchase': {'CompanyName': '', 'RepurchasedShares': '', 'HighestTradingPrice': '', 'LowestTradingPrice': '', 'ClosingDate': '', 'RepurchaseAmount': ''}, 'EquityPledge': {'Pledger': '', 'PledgedShares': '', 'Pledgee': '', 'TotalHoldingShares': '', 'TotalHoldingRatio': '', 'TotalPledgedShares': '', 'StartDate': '', 'EndDate': '', 'ReleasedDate': ''}}

    type2order = {}
    for t, d in EVENT2SCHEMA.items():
        type2order[t] = list(d.keys())

    def type2min(t):
        if t in {"EquityOverweight", "EquityUnderweight", "EquityRepurchase"}:
            return 4
        return 5

    stats = []
    tp = 0
    fp = 0
    fn = 0
    path = pathlib.Path(__file__).parent / 'Data' / 'test.json'
    data = json.loads(path.read_text(encoding='utf8'))
    results = []
    for datum in data:
        d = datum[1]
        sents = d['sentences']
        doc = ''.join(sents)
        events = d['recguid_eventname_eventdict_list']
        type2events = collections.defaultdict(list)
        for event in events:
            t = event[1]
            event_dict = event[2]
            cur_event = []
            for role in type2order[t]:
                cur_event.append(event_dict.get(role))
            type2events[t].append(copy.deepcopy(cur_event))

        pred_results = dee_task.predict_one(doc)
        results.append(pred_results)
        pred_type2events = collections.defaultdict(list)
        pred_events = pred_results['event_list']
        for pred_event in pred_events:
            t = pred_event['event_type']
            cur_event = []
            for role in type2order[t]:
                for arg in pred_event['arguments']:
                    if arg['role'] == role:
                        cur_event.append(arg['argument'])
                        break
                else:
                    cur_event.append(None)

            # num = sum(1 for a in cur_event if a)
            # if num >= type2min(t):
            pred_type2events[t].append(copy.deepcopy(cur_event))

        for t, schema in EVENT2SCHEMA.items():
            num_roles = len(schema)
            pred_records = pred_type2events[t]
            gold_records = type2events[t]
            stat = dee_metric.agg_event_level_tpfpfn_stats(pred_records, gold_records, num_roles)
            tp += stat[0]
            fp += stat[1]
            fn += stat[2]
            precision = tp / (tp + fp)
            recall = tp / (tp + fn)
            f1 = (2 * precision * recall) / (precision + recall)
            print(f1)
            print(tp, fp, fn)
            stats.append(stat)

    print('final f1', f1)
    save_path = pathlib.Path(__file__).parent / 'result.json'
    save_path.write_text(json.dumps(results, ensure_ascii=False), encoding='utf8')

Hi there~ Sorry for the late response.
We provided inference.py as an example to explain how the model could be used to generate event records, since a lot of people requested this feature. So it's actually not a quite right way to reproduce the results as reported in our paper.
Inside dee_task.predict_one, when calling convert_string_to_raw_input, the concatenated string will be split into sentences by the sent_seg function in dee/helper/__init__.py, which may not provide the same sentences as in the original dataset.
The results you mentioned is quite interesting though, we didn't try this before.
If you want to reproduce the results as reported in our paper, we suggest following our instruction in README.md to re-train the model, or load the test set and call the default dee_task.eval function directly.
In addition, if you hacked the source code to bypass the sent_seg, the upper bound of entity extraction will decrease rapidly since the default maximal sequence length is 128, leading to a performance decline.
If you have further questions, feel free to leave a message.

Thanks for your reply. I didn't hack the dee_task.predict_one function (so sent_seg also applies as usual), but just imitated the logic and replaced inference.py with the code above. My result can be reproduced in a few minutes. I will take some time to see how dee_task.eval works and goes.


Updated everything to Vulkano 0.27.1

Hello!
When I first started learning about Vulkano, I found this guide actually helpful and I wanted to take some time to update it a bit. I  also plan to change it in a way that more people could use Vulkano as a efficient high level wrapper without much computer graphics knowledge.
Changelog
Nov 25, 2021 - Updated everything to Vulkano 0.26.0

Updated Cargo.toml.
Changed Rust edition to 2021.
Updated the examples and the guide, until the windowing part (that doesn't have examples yet).

Dec 12, 2021 - Updated everything to Vulkano 0.27.1

Same as the last update, only to a newer version.
Made the triangle viewport fixed in the pipeline.

Next steps

Update the guide be easier to incorporate Vulkano in a bigger project.
Make the guide consistent with the Vulkano examples.
Add sections for windowing, texturing, 3d.
Make the guide more friendly for someone that is newer to computer graphics and doesn't understand everything that happens at a lower level.

@ZakStar17 Thank you so much for your help in improving our website, and I'm very apologize for the late review.
Our website was in tremendously outdated state, and now thanks to your work it's much better.
Unfortunately I have limited time in reviewing our infrastructure, and I usually more focused on a primary repository. But I'm going to improve this situation and will take closer look at all PRs including vulkano-www.
Would you be interested in continuous improving of the website content and guides? PRs will be fast forwarded quicker, and maybe we can even make you a moderator of this repository if you are fine about it.

@Eliah-Lakhin Many thanks to you for approving my pull request.
As you stated in your Organization and Planning post, I also think its necessary to regularly improve the website and create other tutorials and guides from time to time. Vulkano has a really friendly high-level design, but the lack of guidance makes Vulkano hard to follow for begginers without previous Vulkan/graphics programing knowledge.
I would really like to continue improving the website and other content such as documentation, and I look forward to help improving the overall experience with the library on itself. I also don't mind helping review pull requests, although I may sometimes not have much time to do that.
On a side note, I mostly work on graphics programming as a hobby, so I don't have that much thecnical understanding of the subject. I would really appreciate if someone could review the contents of the website to see if they are entirely correct, as I partially changed some parts, and small mistakes could ruind a bit the experience.

@ZakStar17 I'm glad to have you and @hakolao as regular Website maintainers. I just added to both of you the Write access to this repository. Please approve my GitHub invitation, it should arrive in your email inbox.
From now on you can review and merge Pull Requests, and also push commits to the master branch directly too. Once the commit arrives in the master branch, the vulkano.rs website reflects these changes almost instantly. So, please be careful in changing things.
I don't want to limit you, guys, in a way you want to evolve the website, but I suggest sticking with the rule in adding new changes through the Pull Requests exclusively, and for your own PRs to merge them only when you get approval from someone else of the Vulkano Community. e.g. I just approved Zakhar's #99, so he can proceed with the PR merging. Of course, there are exceptions to this rule, when you need to fix something minor.
Just some ideas for you in which way we can improve the website:

Okko suggested creating a Discord server as a Gitter Chat replacement. I like this idea. And we can add a permanent invite link on our Website too.
Of course, keep improving the Tutorial. Maybe eventually turn it into a book that would cover a wider range of Vulkano features and technical topics.
We can create an additional page with projects using Vulkano(aka "Showcase"). On this page, we will have more space to add a detailed description of the projects.

Good luck!


Save user to DB after signing in with the wallet

DB save may not be necessary as store can be implemented purely on chain

After wallet signing user is successfully save to mongoDB


fix: multiple markers in markerarray msg visualization

Description
Fixes #3138
Related links
In the issue, you can find steps for reproducing the issue and a demo for that.
More details about the analysis and other possible causes can be found there as well.
Tests performed
After applying the potential fix, the output of testing for same scenario in the issue in this video or this video for better zoom in for stop line as example
Notes for reviewers
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@ahmeddesokyebrahim
I appreciate the proposed changes made in this PR.
However, without a deleter function, there may be situations where virtual walls continue to exist even when they should not.
Therefore, I believe it is necessary to include an explicit deletion function to ensure proper removal of virtual walls. For this reason, I would like to keep the deleter function in place to address the bug that was pointed out.
What are your thoughts on this?

I appreciate the proposed changes made in this PR.
However, without a deleter function, there may be situations where virtual walls continue to exist even when they should not.
Therefore, I believe it is necessary to include an explicit deletion function to ensure proper removal of virtual walls. For this reason, I would like to keep the deleter function in place to address the bug that was pointed out.
What are your thoughts on this?

Thanks for your comment Mr @kyoichi-sugahara .
Actually I wonder about the significance of having a deleter function in the time that we add the marker in the creator function we specify a lifetime to it.
Based on the Marker message definition, any marker with lifetime (other than zero) will be deleted automatically. And that is already happening in createDefaultMarker method. That give me the understanding that we do not need a deleter function.
Let me know your thoughts.

@ahmeddesokyebrahim
The reason why I think using the delete function is necessary is because when the wall marker is deleted by setting the lifetime, for example, to 0.2 seconds and each module runs at 10Hz, the wall marker will be displayed unnecessarily for 0.1 seconds after it is no longer needed. Although it may seem like a short time when considering real time, when running a heavy simulator at a slower speed, for example, at 1/10 of the normal speed, the marker will be displayed for 1 second despite being unnecessary, which can confuse developers.
For these reasons, I believe that an explicit deletion function is necessary when modules determine that the marker is no longer needed.
Therefore, I would like to proceed by fixing the bug while keeping the delete function for deleting unnecessary markers. What do you think about this approach?

Thanks for the explanation Mr. @kyoichi-sugahara . It makes sense for me.
I just would like to have more elaboration about what you mean by explicit deletion function.

@kyoichi-sugahara could you provide a solution approach to handle this without removing the deleter function?

@ahmeddesokyebrahim , your PR is good but removes the "explicit deletion" of the virtual wall markers, i.e., the virtual walls are not deleted by message with action DELETE and only disappear when reaching the end of their lifetime.
I think a better approach to fix the issue with multiple markers is to improve the way the DELETE markers are generated.
The current issue, as you found, is that we both create ADD markers and DELETE markers with the same id and ns.
I made a draft PR with a possible solution: https://github.com/autowarefoundation/autoware.universe/issues/3138

This PR is now moved to https://github.com/autowarefoundation/autoware.universe/pull/3273/files.


Audio in music videos is corrupted/speed increased

Download of any music video gets completed without any errors. Output m4v file has issues with the audio which sounds as if its speed has been increased 10x or more. I tried playing the file in vlc, potplayer, mpv, mpc-hc, etc.
I tried -
https://music.apple.com/in/music-video/got-boost-artist-only-ver/1773047789
https://music.apple.com/in/music-video/aaj-zid/1586031345
https://music.apple.com/in/music-video/besharam-rang-from-pathaan/1659394429

i have found the fix if i decrypt the audio using shaka packager and replace key gamdl uses for audio to<PHONE_NUMBER>0000000000000000000000:xyz instead of 1:xyz it works.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-29-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4061

Questions ?
Please refer to the Backport tool documentation


SageTV forums down for maintenance for 48 hours

Sorry to post this here but the forums have been down for about 48 hours.  Just wanted to be sure that Narflex, etc were aware of that.

Yes I am aware, thanks. 🙂

Ah, ok.  Good news I’m not the only one spending Thanksgiving working on my Sage box.  Hopefully back up soon...

Thanksgiving was six weeks ago in these parts ;-)

Hehe - southern provinces here.  But I’m getting a little nervous seeing the forum down.  Is there another way Sage users communicate?  The FB page hasn’t had an entry in 10 years?  Is the Github site ‘the place’?
Sent from me

On Nov 28, 2019, at 1:40 PM, wayner9<EMAIL_ADDRESS>wrote:
Thanksgiving was six weeks ago in these parts ;-)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

I'll get them back up, just be patient. 🙂

Thanks.  Good to see you’re still around.   There was a point where I wondered if it would be a good idea to download the site, just in case of natural disaster, etc., or if indeed there’s an alternate place Sage-folk hang out.  Cheers :)
Sent from me

On Nov 28, 2019, at 10:41 PM, Jeffrey Kardatzke<EMAIL_ADDRESS>wrote:
I'll get them back up, just be patient. 🙂
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Narflex, the forums are still cranking out popups.  emveepee has some info here:  https://forums.sagetv.com/forums/showthread.php?p=623175&postcount=23


Convert worker to ESM

To use ESM for the worker, I created a package.json file in worker/ with { type: "module" } as its sole content.
I then rewrote every import to use ESM syntax.
I also tried to set { type: "module" } in the root package.json file to also use ESM in next.config.js.
However, this resulted in a weird problem: default imports were now getting imported as objects in this shape: { default: <defaultImport> }.
Afaik, this should only be the case if you use "import * as foo from 'bar'" syntax: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import#default_import
This is fixed by not using { type: "module" } for some reason. However, then, next.config.js also doesn't support ESM import syntax anymore.
The documentation says that if you want to use ESM, you can use next.config.mjs: https://nextjs.org/docs/pages/api-reference/next-config-js
But I didn't want to use MJS extension since I don't have any experience with it. For example, not sure if it's good style to mix JS with MJS etc. So I kept the CJS import syntax there.

Putting in draft to fix linter errors:

Run npm run lint
<EMAIL_ADDRESS>lint
standard
standard: Use JavaScript Standard Style (https://standardjs.com/)
/home/runner/work/stacker.news/stacker.news/worker/auction.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/auction.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/earn.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/earn.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/index.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/index.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/nostr.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/nostr.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/ots.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/ots.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/repin.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/repin.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/search.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/search.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/streak.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/streak.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/trust.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/trust.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/views.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/views.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/wallet.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/wallet.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
Error: Process completed with exit code 1.

Commit message from 98e899c

I wasn't able to fix the following errors:
/home/runner/work/stacker.news/stacker.news/worker/auction.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/auction.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/earn.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/earn.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/index.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/index.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/nostr.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/nostr.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/ots.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/ots.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/repin.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/repin.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/search.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/search.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/streak.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/streak.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/trust.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/trust.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/views.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/views.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
/home/runner/work/stacker.news/stacker.news/worker/wallet.js:0:0: Parsing error: No Babel config file detected for /home/runner/work/stacker.news/stacker.news/worker/wallet.js. Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files. (null)
I tried to tell babel where to find the babel config file (.babelrc), specifying the babel config in worker/package.json under "babel", using babel.config.json etc. to no avail.
However, afaict, we don't need babel for the worker since it won't run in a browser. Babel is only used to transpile code to target browsers.
But it still would be nice to lint the worker code with standard.
But we can figure this out later.

One downside of using { "type": "module" } (and thus explicitly using ESM even though we were already able to use ESM import syntax :thinking:) is that we have to provide the JS extension during imports now ... kind of annoying

That's weird. How does next not have to do that? Some kind of webpack thing?

That's weird. How does Next not have to do that? Some kind of webpack thing?

I'll check. Maybe we can adopt a similar solution.
Currently, the worker at least is not able to import stuff without the .js extension:
worker  | node:internal/errors:496
worker  |     ErrorCaptureStackTrace(err);
worker  |     ^
worker  |
worker  | Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/app/worker/wallet' imported from /app/worker/index.js
worker  |     at new NodeError (node:internal/errors:405:5)
worker  |     at finalizeResolution (node:internal/modules/esm/resolve:324:11)
worker  |     at moduleResolve (node:internal/modules/esm/resolve:943:10)
worker  |     at defaultResolve (node:internal/modules/esm/resolve:1129:11)
worker  |     at nextResolve (node:internal/modules/esm/loader:163:28)
worker  |     at ESMLoader.resolve (node:internal/modules/esm/loader:835:30)
worker  |     at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
worker  |     at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40)
worker  |     at link (node:internal/modules/esm/module_job:76:36) {
worker  |   code: 'ERR_MODULE_NOT_FOUND'
worker  | }
worker  |
worker  | Node.js v18.17.0
worker  |
worker exited with code 1

The next app runs fine without the extension

Somewhat related discussion: https://github.com/nodejs/node/issues/46006
But I just noticed the worker code doesn't run without type: "module" in the root package.json since it think it's imports are CommonJS :scream: I must have missed this somehow while fixing the app, oof
worker  | file:///app/worker/wallet.js:3
worker  | import { datePivot } from '../lib/time.js'
worker  |          ^^^^^^^^^
worker  | SyntaxError: Named export 'datePivot' not found. The requested module '../lib/time.js' is a CommonJS module, which may not support all module.exports as named exports.
worker  | CommonJS modules can always be imported via the default export, for example using:
worker  |
worker  | import pkg from '../lib/time.js';
worker  | const { datePivot } = pkg;
worker  |
worker  |     at ModuleJob._instantiate (node:internal/modules/esm/module_job:124:21)
worker  |     at async ModuleJob.run (node:internal/modules/esm/module_job:190:5)
worker  |
worker  | Node.js v18.17.0
worker  |
worker exited with code 1

Putting this back into draft.

That's weird. How does Next not have to do that? Some kind of webpack thing?

I found out that they use this by printing the default webpack config:
   webpack: (config, { isServer, dev }) => {
+    console.log(config.module.rules)
     if (isServer) {

{ test: /.m?js/, resolve: { fullySpecified: false } }

Trying to make "type": "module" in root package.json work to fix the worker imports.
Finally found a ticket related to the problem I run into then: https://github.com/vercel/next.js/issues/34412
But no solution there... afaict, it should be fixed but it still happens for me.
But I think the solution is related to importInterop
But when I use
diff --git a/.babelrc b/.babelrc
index e5ef908..fbe2a18 100644
--- a/.babelrc
+++ b/.babelrc
@@ -15,6 +15,12 @@
                     ]
                 }
             }
+        ],
+        [
+            "@babel/plugin-transform-modules-commonjs",
+            {
+                "importInterop": "babel"
+            }
         ]
     ]
 }
\ No newline at end of file

These errors stop:
app  | TypeError: next_auth_providers_credentials__WEBPACK_IMPORTED_MODULE_2__ is not a function
app  |     at eval (webpack-internal:///./pages/api/auth/[...nextauth].js:218:20)
app  |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
app  | LND GRPC connection successful
app  | - error pages/api/auth/[...nextauth].js (139:2) @ CredentialsProvider
app  | - error Error [TypeError]: next_auth_providers_credentials__WEBPACK_IMPORTED_MODULE_2__ is not a function
app  |     at eval (webpack-internal:///./pages/api/auth/[...nextauth].js:218:20) {
app  |   digest: undefined
app  | }
app  |   137 |
app  |   138 | const providers = [
app  | > 139 |   CredentialsProvider({
app  |       |  ^
app  |   140 |     id: 'lightning',
app  |   141 |     name: 'Lightning',
app  |   142 |     credentials: {
app  | TypeError: next_auth_providers_credentials__WEBPACK_IMPORTED_MODULE_2__ is not a function
app  |     at eval (webpack-internal:///./pages/api/auth/[...nextauth].js:218:20)
app  |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

but I get new errors now:
app  | Error: Cannot find module '../styles/globals.scss'

:roll_eyes:
Then I tried to use a function for importInterop to exclude scss imports so I need to use babel.config.js:
app  | Error [ERR_REQUIRE_ESM]: require() of ES Module /app/babel.config.js from /app/node_modules/next/dist/build/babel/loader/get-config.js not supported.
app  | babel.config.js is treated as an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which declares all .js files in that package scope as ES modules.
app  | Instead rename babel.config.js to end in .cjs, change the requiring code to use dynamic import() which is available in all CommonJS modules, or change "type": "module" to "type": "commonjs" in /app/package.json to treat all .js files as CommonJS (using .mjs for all ES modules instead).

So I used babel.config.cjs:
app  | - info Using external babel configuration from /app/babel.config.cjs
app  | - error ./sw/index.js
app  | Error: The Next.js Babel loader does not support .mjs or .cjs config files.
app  | - wait compiling...
app  | - error ./sw/index.js
app  | Error: The Next.js Babel loader does not support .mjs or .cjs config files.
app  | - info Loaded env from /app/.env
app  | - info Loaded env from /app/.env
app  | - wait compiling /~ (client and server)...
app  | - error ./node_modules/next/dist/client/next-dev.js
app  | Error: The Next.js Babel loader does not support .mjs or .cjs config files.
app  | - wait compiling /[name] (client and server)...
app  | - error ./node_modules/next/dist/client/next-dev.js
app  | Error: The Next.js Babel loader does not support .mjs or .cjs config files.

...
(just trying to write down my process so I don't start to run in circles, lol)

the .js isn't worth it if that's what this is about
this is why it's been commonjs for so long. I don't tend to do configuration programming very well

the .js isn't worth it if that's what this is about

No, it's not about this at the moment. I realized that there is a conflict between app and worker:
the app doesn't work with setting { "type": "module" } in package.json because then I get these weird default import error:
app  | TypeError: next_auth_providers_credentials__WEBPACK_IMPORTED_MODULE_2__ is not a function
app  |     at eval (webpack-internal:///./pages/api/auth/[...nextauth].js:218:20)
app  |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
app  | LND GRPC connection successful
app  | - error pages/api/auth/[...nextauth].js (139:2) @ CredentialsProvider
app  | - error Error [TypeError]: next_auth_providers_credentials__WEBPACK_IMPORTED_MODULE_2__ is not a function
app  |     at eval (webpack-internal:///./pages/api/auth/[...nextauth].js:218:20) {
app  |   digest: undefined
app  | }
app  |   137 |
app  |   138 | const providers = [
app  | > 139 |   CredentialsProvider({
app  |       |  ^
app  |   140 |     id: 'lightning',
app  |   141 |     name: 'Lightning',
app  |   142 |     credentials: {
app  | TypeError: next_auth_providers_credentials__WEBPACK_IMPORTED_MODULE_2__ is not a function
app  |     at eval (webpack-internal:///./pages/api/auth/[...nextauth].js:218:20)
app  |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

which I believe is related to importInterop
But it's required to allow imports from the worker since else, it assumes the imports to be from CommonJS:
worker  | file:///app/worker/wallet.js:3
worker  | import { datePivot } from '../lib/time.js'
worker  |          ^^^^^^^^^
worker  | SyntaxError: Named export 'datePivot' not found. The requested module '../lib/time.js' is a CommonJS module, which may not support all module.exports as named exports.
worker  | CommonJS modules can always be imported via the default export, for example using:
worker  |
worker  | import pkg from '../lib/time.js';
worker  | const { datePivot } = pkg;
worker  |
worker  |     at ModuleJob._instantiate (node:internal/modules/esm/module_job:124:21)
worker  |     at async ModuleJob.run (node:internal/modules/esm/module_job:190:5)
worker  |
worker  | Node.js v18.17.0
worker  |
worker exited with code 1

but I can just try to use what is suggested in the error instead of trying to make ESM imports work:
worker  | CommonJS modules can always be imported via the default export, for example using:
worker  |
worker  | import pkg from '../lib/time.js';
worker  | const { datePivot } = pkg;

Nah, that also doesn't work ... the worker then doesn't understand import inside the files it wants to import stuff from:
worker  | (node:7) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
worker  | (Use `node --trace-warnings ...` to show where the warning was created)
worker  | /app/api/resolvers/serial.js:1
worker  | import { GraphQLError } from 'graphql'
worker  | ^^^^^^
worker  |
worker  | SyntaxError: Cannot use import statement outside a module
worker  |     at internalCompileFunction (node:internal/vm:73:18)
worker  |     at wrapSafe (node:internal/modules/cjs/loader:1178:20)
worker  |     at Module._compile (node:internal/modules/cjs/loader:1220:27)
worker  |     at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
worker  |     at Module.load (node:internal/modules/cjs/loader:1119:32)
worker  |     at Module._load (node:internal/modules/cjs/loader:960:12)
worker  |     at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:169:29)
worker  |     at ModuleJob.run (node:internal/modules/esm/module_job:194:25)
worker  |
worker  | Node.js v18.17.0
worker  |
worker exited with code 1

So we're back at square one. Can't make both work at the same time

Okay, I just created a package.json with { "type": "module" } in lib/ and api/ in 5c3e428 to tell the worker that these should be handled as MJS files.
This doesn't break the app but fixes the worker.
I also noticed that we used global in lib/apollo.js in a browser context. Not sure how this worked before - was this code not executed before on the browser? Replaced that with window in 3c89602


Update kernel to v6.1.72-cip13

This change updates the standard CIP kernel version to v6.1.72-cip13. The RT kernel stays the same version because it has not been updated in upstream since the previous EMLinux release.

@kkobayas0 thanks.


URL can not be input in IE

I Can not input URL in IE, but it's OK in Chrome.

https://github.com/mindmup/bootstrap-wysiwyg/issues/181


Improve README to reflect reality

There you go - fixed it for ya.

The GraphQL technical steering committee is working on a policy to guide the use of political speech from the voice of a GraphQL project. The original author chose to revert the original change via #1879 until we complete that policy. This should resolve this issue, so I am closing it.
As a reminder, all discussion within GraphQL projects must adhere to our Code of Conduct.


Spring cloud reactive steam's (SCF) Processor is not working with ParallelFlux and Schedulers

In our reactive stream Processor app, when we try parallel processing with Schedulers. The Flux gets stuck after some seconds.
Whereas the parallel processing with Schedulers works fine in Source and Sink apps.
Could you please check on this. Here is the sample code
@SpringBootApplication
@EnableBinding(Processor.class)
public class ParallelProcessorApplication {

    public static void main(String[] args) {
        SpringApplication.run(ParallelProcessorApplication.class,
                "--spring.cloud.stream.function.definition=process");
    }

    @Bean
    public Function<Flux<Long>, ParallelFlux<Long>> process() {
        return longFlux ->
                longFlux.parallel(4)
                        .runOn(Schedulers.elastic())
                        .doOnNext(i -> System.out.println(Thread.currentThread().getName() + " -> " + i));
    }

}

Here is the working code from the Source application. In source application, it works as expected.
@SpringBootApplication
@EnableBinding(Source.class)
public class ParallelSourceApplication {

    public static void main(String[] args) {
        SpringApplication.run(ParallelSourceApplication.class,
                "--spring.cloud.stream.function.definition=emit");
    }

    @Bean
    public Supplier<ParallelFlux<Long>> emit() {
        return () -> Flux.interval(Duration.ofMillis(1))
                         .parallel(4)
                         .runOn(Schedulers.parallel())
                         .doOnNext(i -> System.out.println(Thread.currentThread().getName() + " -> " + i));
    }

}

@olegz
If require more details, will push my sample projects to gitHub. Thank you in advance!
P.S
There is another issue with Processor and Sink apps. If I chose Schedulers.parallel() instead of Schedulers.elastic(). Then parallel processing not works. It does not spawn multiple threads. Whereas the same works fine with Source app fine. Kindly check below processor code for this issue:
The sample code is here
@Bean
    public Function<Flux<Long>, ParallelFlux<Long>> process() {
        return longFlux ->
                longFlux.parallel(4)
                        .runOn(Schedulers.parallel())
                        .doOnNext(i -> System.out.println(Thread.currentThread().getName() + " -> " + i));
    }

In the ouput logs, you can see only parallel-1 for all the emitted elements. Whereas the expected behavior is. I should see parallel-1 parallel-2 parallel-3 parallel-4 etc.
parallel-1 -> 1
2019-04-23 16:00:39.261  INFO 32457 --- [     parallel-1] reactor.Flux.ConcatMap.1                 : onNext(1)
parallel-1 -> 2
2019-04-23 16:00:39.263  INFO 32457 --- [     parallel-1] reactor.Flux.ConcatMap.1                 : onNext(2)
parallel-1 -> 3
2019-04-23 16:00:39.272  INFO 32457 --- [     parallel-1] reactor.Flux.ConcatMap.1                 : onNext(3)
parallel-1 -> 4
2019-04-23 16:00:39.286  INFO 32457 --- [     parallel-1] reactor.Flux.ConcatMap.1                 : onNext(4)
parallel-1 -> 5
2019-04-23 16:00:39.308  INFO 32457 --- [     parallel-1] reactor.Flux.ConcatMap.1                 : onNext(5)
parallel-1 -> 6
2019-04-23 16:00:39.320  INFO 32457 --- [     parallel-1] reactor.Flux.ConcatMap.1                 : onNext(6)
parallel-1 -> 7
2019-04-23 16:00:39.336  INFO 32457 --- [     parallel-1] reactor.Flux.ConcatMap.1                 : onNext(7)
parallel-1 -> 8

I think both issue are related. Kindly do let us know If different issue needed for the same. Thank you!

So, I am not sure at the moment that using ParallelFlux in the context of spring-cloud-stream handler is a good idea. Let me explain:
While we provide a support for reactive abstractions  we internally create a delegation model from MessageListener to reactive listener. Which means in the end you are still at the mercy of MessageListening Container, task executor and so on.
So if you do want to parallelise i would simply increase concurrency settings on consumer binding spring.cloud.stream.bindings.input.consumer.concurrency=3, otherwise there could be unintended consequences and potential loss of messages

@olegz Thanks for letting us know the internal handling details. Still, it would be better to handle this hanging error in some ways. In this case, we should through some exceptions back to the message handler/processor. So that user can be aware of the root cause for the hang/stuck after processing a few messages.
 Thanks for the suggestion!

spring.cloud.stream.bindings.input.consumer.concurrency=3

In case, if ParallelFlux is not supported or not a good idea. Still, as a user, I would like to use ParallelFlux for internal business logic for some intensive method. And while returning to the MessageListener,  I can covert parallelFlux to the sequential Flux like parallelFlux.sequential().
In this case, below code should work but this also hangs in between...
For example:
@Bean
    public Function<Flux<Long>, Flux<Long>> process() {
        return longFlux ->
                longFlux.parallel(4)
                        .runOn(Schedulers.parallel())
                        .doOnNext(i -> System.out.println(Thread.currentThread().getName() + " -> " + i))
                        .doOnNext(i -> someIntensiveOperation())
                        .sequential();
    }

Could you please check if it makes a sense. Your thoughts on this. Thank you very much!

@olegz I am doing some intensive regex matches on the large collection/flux internally. Hence this bug fix is immensely important for us. Could you please check on this.
It's totally OK if not works on the message-handler level. But at least it should allow using in any of the methods for some business logic internally. Your thoughts on this. Thank you in advance!

@msshitole  We won't be documenting it for reactive module as we are fading it away in favor of spring-cloud-function native flux support and at some point in the near future we'll write a section about what you should expect when using flux with non-reactive binders such as Rabbit and Kafka as well as what one should and should not do .
Feel free to raise another issue for documentation around usage of flux and its implications, but there is nothing we can/should do here and I think I've already explained that parallelisation in your case would cause more complexity.


DateFrom does not extract the Date component correctly

In this CQL:
define DateTime1: @2012-03-10T10:20:00
define DateTime2: @2013-03-10T09:20:00
define DurationInYears: years between (date from DateTime1) and (date from DateTime2)

DurationInYears should return 1, but it returns 0.

Resolved:
https://github.com/DBCG/cql_engine/commit/1b4747de6d837d896c31c34fe5485cb17c760bbb
Test here:
https://github.com/DBCG/cql_engine/commit/6d5007c956271eebfa2ab3e237897be38ef121d7#diff-3e77c0680c3fd657fe2b0dd84ac42ab0


wrong event callback ordering on first event handler

Describe the bug
The call order of events for the first event handler on an element with respect to window is incorrect and does not follow the bubbling rules for events.
The bubbling order is (for example a button and the pointerdown event): button -> parent -> window
But the current version calls the event handlers in the order window -> button -> parent for the first event handler appearing in the call tree.
All following event handlers are called in the correct order.
Leptos Dependencies
leptos = { version = "0.6.6", features = ["nightly", "csr"] }
console_log = "0.2"
log = "0.4"
console_error_panic_hook = "0.1.7"
leptos-use = "0.10.4"

For example:
Given the following code (also found here)
use leptos::*;
use leptos_use::*;

#[component]
pub fn Comp1() -> impl IntoView {
    let (last_call, set_last_call) = create_signal("none".to_string());

    _ = use_event_listener(use_window(), leptos::ev::pointerdown, move |ev| {
        set_last_call.update(|v| v.push_str(" window"));
    });

    view! {

            { move || last_call() }
            <button on:pointerdown=move |_| set_last_call.update(|v| v.push_str(" button"))>{"CLICK"}</button>

    }
}

pub fn main() {
    mount_to_body(|| {
        view! {

                <Comp1 />
                <Comp1 />
                <Comp1 />
                <Comp1 />

        }
    })
}

When clicking any button labeled CLICK, the text line next to the button should get appended by  button parent window (which is the expected call order explained above)
The other text lines just get appended by  window because the event handler on window is the only one called for this component.
To Reproduce
Steps to reproduce the behavior:

Click the topmost button and observe the last 3 appended words which are window button parent (wrong order)
Click any other button and observe the last 3 appended words which are button parent window (right order)

Expected behavior
Expected the first button press to behave just like the other ones: produce the text sequence button parent window

:undelegated does indeed fix the behavior for the first event listener. It also fixes not being able to stop_propagation() on the event (without :undelegated the event handler on window is called regardless if stop_propagation() is called or not).
Is there some documentation on :undelegated? I could not find any.
So i guess this is intended (or more undefined) behavior when mixing DOM event handlers and leptos event handlers without :undelegated?

Documenting :undelegated more clearly is definitely in the backlog of docs to be written. It is just the syntax in the view macro for adding undelegated to an event listener, but the docs that need to be added are more in the category of "when would you want to do this?"

Event delegation is no longer used by default on the main branch/0.7, so I'm going to close this one.


Parsing issue with Bind zonefiles

We experienced a weird parsing issue with a normally OK bind zonefile.
The parser expects a SOA record right after the $ORIGIN definition, but it's not always work.
I've a following zone:
$ORIGIN .
$TTL 3600   ; 1 hour
<IP_ADDRESS>       IN A    <IP_ADDRESS>
router.domain.com A  <IP_ADDRESS>
mydomain.com     SOA ns.domain.com. hostmaster.domain.com. (
                26         ; serial
                900        ; refresh (15 minutes)
                600        ; retry (10 minutes)
                86400      ; expire (1 day)
                3600       ; minimum (1 hour)
                )

And it works totally fine with Bind but DNS::Zonefile fails to parse it.

The current zone parsing rule (https://github.com/craigw/dns-zonefile/blob/master/lib/dns/zonefile.treetop#L3) requires a non-optional SOA resource record (RR) to appear after one or more optional variables, space_or_break, or comment non-terminal symbols. I'd like to fix this as well, and I'm in the code now working on support for TTL and class reordering, so I'll see if I can find a way to allow the SOA RR to appear anywhere other RR can.

I was not able to figure out yet how to do away with the separate soa definition that needs to be the first record in a zone. I may be able to come back to it in the future though, so I'll leave this open.


Refactor calculate total

Coverage decreased (-0.06%) to 29.064% when pulling b48dd9a0b514a04ba62709fd5bbdb8deac2ac0d7 on calculaterefactor into 18aef25da34dd642d2ca6a08dbb520e986c13425 on master.

Coverage decreased (-0.02%) to 29.096% when pulling b48dd9a0b514a04ba62709fd5bbdb8deac2ac0d7 on calculaterefactor into 18aef25da34dd642d2ca6a08dbb520e986c13425 on master.


Update the perl-linter's l:pattern to catch missing errors

In some situations, errors reported by perl -c can have multiple
listings of "at  line ". If the l:pattern is changed to
use non-greedy matching it will also match these.
For example:
use strict;
use DateTime;
$asdf=1;

Results in:
Global symbol "$asdf" requires explicit package name (did you forget to declare "my $asdf"?) at /Users/mgrimes/t.pl line 3, <DATA> line 1.
/Users/mgrimes/t.pl had compilation errors.

I am not 100% sure why perl -c generates errors with the extra "file
line ". It only happens in some versions of perl when certain
modules are used.

Where are the tests? Have you added tests? Have you updated the tests? Read the
comment above and the documentation referenced in it first. Write tests!
Seriously, read :help ale-development and write tests.

Sorry, that was the wrong patch. Not sure how that happened, but I've just pushed the correct patch. This passes run-tests on my machine.

Cool, that looks better. Add some more tests for the output we're able to capture now.

Cheers! :beers:


Add VisibleState property to ExcelSheet

Please add a property to ExcelSheet that can be used to read the visibility of the sheet, preferably as an enum instead of text:
public enum ExcelSheetVisibility {
    Visible,
    Hidden,
    VeryHidden
}

Some input files can have hidden sheets and it's hard to automate things like reading data from every visible sheet (my current workaround being opening the file with ExcelDataReader first, and iterating through the sheets to find out which one is visible).

Right - can you clarify what VeryHidden means and how I would get these values?

IExcelDataReader.VisibleState. VeryHidden means the user can't switch it to visible, only the VBA code. I'd say if you just add it as string and set the value when reading the sheet, we're one step closer, but a string property is so lame when the possible values are fixed.

Fixes in https://www.nuget.org/packages/ExcelDataReader.Mapping/1.1.2


updated markov() to add tranpose keyword + default warning

This PR partially addresses issue #395 by adding a transpose keyword to the markov function that allows transposed inputs.  In the current release, the markov function is not consistent with the normal time-series convention (see discussion in #395) so a warning message is generated if transpose is not set explicitly to True.
These files will need to be updated again in the 0.9.0 release so that the default for the transpose keyword changes from True to False.

Coverage decreased (-0.1%) to 86.247% when pulling 7ed68ecb347a6b94ceebf84eaefb662dbba1436a on murrayrm:markov-inconsistency into 120a926f34bc8c990d91c7b2d10a114666f0991d on python-control:master.

This PR itself LGTM. But are we sure that the algorithm actually works for real data? The data used in the test is worthless to determine any markov parameters. (https://github.com/python-control/python-control/issues/395#issuecomment-618418178)

Good point on whether the calculation was right.  Looks like it wasn't...
In this latest push, I have:

Updated the markov() algorithm to compute the correct coefficients (the old code is there for comparison, along with a new algorithm + reference).
Reverted to the original markov_test.py (to make sure tests are backward compatible) and moved all of the "enhanced" testing into markov_test_array.py.
Added a new unit test in markov_test_array.py to make sure the calculation is correct.


Create mdwasim74.jason

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Seems Good

The file should be in json. Please rename the file from data/mdwasim74.jason to  data/mdwasim74.json.


Different Length Templates

Templates can have different lengths - for example, based on peak frequency of the arrival, a P-wave template may justifiably be shorter than an S-wave template.  Unfortunately, different lengths have their means removed prior to template application and for that I'm using the padded template length.  With regards to the numerator signal, this depends exclusively on the the Fourier transform and zero-padding in the overlap and add method shouldn't have an impact since zero-padding amounts to extending the periodicity of the template and observed signals.  What needs to be modified is the denominator calculation so that the normalization is specific to the template length.
The two things that need to be done are

The numerator signal is fine for different length templates.

Checked and true.

The denominators are made specific for each template's length.

There is a normalization in y and phase shift issue.

This was a 2-part bookkeeping error.

The signals are padded based on the longest filter.  So if there is a 150 sample padded template whose actual length is 100 samples, then the normalization should start at sample 50 in the input signal.
The returned signal pointers should point to the start of the unpadded signal (normal template length) and not the padded signal.

This raises an edge case near the end of the signal that I have not yet dealt with.


Jobs somehow caching expired token leads to "bad credentials" error.

Our Github token expired leading to this "bad credentials" error. After a fresh token regeneration, the jobs are not picking up the new token.
Here's the error we get:
Could not update commit status of the Pull Request on GitHub. org.kohsuke.github.HttpException: {"message": "Bad credentials", "documentation_url": https://developer.github.com/v3"}
The only thing that helps is to clone the job. The cloned job works without any issues. We have 100's of jobs and cloning each single one is not feasible. Is there any workaround for existing jobs to pick up the fresh token?
Jenkins version: 2.222.1
GHPRB: 1.42.0

🤦 A restart fixed the issue.


ANGULAR: Map view- Components tab - link needs to be made active

The Read More link is inactive

There was no link value.  Added the link from dev and set target to blank to open to a new tab.


Add compatibility for cms  3.5

Is this backwards compatible? Doesn't seem so at looking at the code.

Yes, I think it's backwards compatible, I tested this with 3.4.5, 3.5, 3.5.1 and it works.
Before that I was inspired by this commit https://github.com/jrief/djangocms-cascade/commit/883f39eac05f77d0638df3719bbe5a5bb7b10048
then I looked at the django-cms code https://github.com/divio/django-cms/blob/4c0539d2aa5dfb240dfc04207936e05670c19aa0/menus/templatetags/menu_tags.py#L138

ok, I believe you 👍


Mysql Count Query with gorm internally running two diffrent queries.

When i am counting number of records for select * its internally running two queries.
dbConn.Find(&s).Count(&count).Error and because of this its increasing my response time on fronted.
this is running below mysql queries
[3177.30ms] SELECT  * FROM `TABLE`
[479.35ms] SELECT  count(*) FROM `TABLE`

That's by design. Perhaps do a raw query instead.

@roshan3133 I also ran into this issue, I think perhaps the documentation isn't 100% clear on how to just do a count. I did find that by doing the following, it reduces it to just the one, correct, count query:
db.Model(&model).Count(&count)

thanks its working now


MeanIoU Metric does not work with JAX backend

I am currently testing out Keras-Core for a simple Image Segmentation task that needs to use MeanIoU as a Metric, with JAX as the set backend.
There seems to be an issue where it throws an error with the following traceback
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
[<ipython-input-14-658c4c4b8133>](https://localhost:8080/#) in <cell line: 1>()
----> 1 history = model.fit(
      2     train_ds, epochs=20, validation_data=test_ds, callbacks=callbacks
      3 )

1 frames
[/usr/local/lib/python3.10/dist-packages/keras_core/src/utils/traceback_utils.py](https://localhost:8080/#) in error_handler(*args, **kwargs)
    122             # To get the full stack trace, call:
    123             # `keras_core.config.disable_traceback_filtering()`
--> 124             raise e.with_traceback(filtered_tb) from None
    125         finally:
    126             del filtered_tb

[/usr/local/lib/python3.10/dist-packages/jax/_src/numpy/lax_numpy.py](https://localhost:8080/#) in stack(arrays, axis, out, dtype)
   1777     for a in arrays:
   1778       if shape(a) != shape0:
-> 1779         raise ValueError("All input arrays must have the same shape.")
   1780       new_arrays.append(expand_dims(a, axis))
   1781     return concatenate(new_arrays, axis=axis, dtype=dtype)

ValueError: All input arrays must have the same shape.

Colaboratory notebook here
Please let me know if there are any gotchas or sharp bits that I should be aware of, in this case.

@suvadityamuk , Could you please try with the latest Keras 3 version and confirm if the above fix resolves the issue.
pip install -U keras


Feature: Output of Yarn should be visible in real-time

Hello!
Yet another feature request :)
I would like to see in real-time the output of Yarn, since currently for projects, that takes long time to be installed, it looks like the tool failed and waits forever to finish.
Some of the output logs:
invoke yarn
// this log ^ line is printed and then after yarn finishes, all of its output is printed as whole

[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.

Done
✨  Done in 112.14s.

As you can see, invoke yarn took 112.14s. which means, for 112 seconds only "invoke yarn" was visible in output and user didn't know anything about further progress

I see. Only a little tweak for invoke helper is required. A couple of spawn event subscriptions are exactly what's needed. https://nodejs.org/api/child_process.html#child_process_child_process
Should I implement this feature or maybe you'd like to make a pull request?

@antongolub Sure, looks simple, but I'm out of free time until next week, so it has to wait a little bit

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Reopening #223 Which route was matched?

The PR closing #223 added this._matchedRoute, but there's still a bug.
if you add another similar but more generic route, this._matchedRoute always gives the more generic route instead of the actually matched more specific one
router.get('/users/:id', function *() {
    // this._matchedRoute is '/:username/:id'
});
router.get('/:username/:id', function *() {
    // this._matchedRoute is '/:username/:id'
});

+1 for this feature. Can we attach layer to context for inspecting inside the controller?

I think this._matchedRoute is always just the last layer that matched, and that is dependent on the order that you declare your routes in. Whoops!

Same problem can occur for something like this:
router.get('/users/me',...) // should match first because of order
router.get('/users/:id',...)

+1 this is a big surprise for a routing middleware...

I have a customized 404 controller registered at the end which cause all this._matchedRoute to wildcard
router.get('/some/path', controller)

router.all('*', function* (){
  // behavior for not found
})

This is still a problem today. Tested with versions 5.4.0 and 7.4.0.
Workaround:
	const getMatchedRoute = () => {
		/* Workaround for https://github.com/alexmingoia/koa-router/issues/246
		 * so we can't use ctx._matchedRoute.
		 * - cut off the query string from the path
		 * - get all path matches
		 * - filter those whose methods match
		 * - take the first one
		 */
		const url = ctx.request.url.split('?')[0];
		const matchedPaths = router.match(url).path;
		const matchingMethod = matchedPaths.filter(r => r.methods.includes(ctx.request.method));
		return (matchingMethod[0] || {}).path || '';
	};

Replace ctx by this when using koa < 2.0

A simpler workaround, router holds all matches in ctx.matches array:
const matchedRoute = ctx.matched.find((layer) => layer.methods.includes(ctx.method)).path;


Python3 port

If this is ready, we should merge with dev, and then master.

Yeah I just tested it and it seems to work for me.
Do we know why the clone is 200+MB but there's only a few hundred lines of code here?


Implement routing and folder structure (Feature 37)

Corrected Staticstics to Statistics

Closes #37

Note for the reviewer:

Rebase before merging.


Fix CONTRIBUTING documentation

'yeoman' is deprecated, use 'yo' instead
see http://yeoman.io/migrate.html

Oops! Thanks for the fix


Datadog reports lambda authorizer's 401 statusCode response as 503 or 502

At my organization, we are encountering a problem where the Lambda authorizer's 401 status code is being reported as either 502 or 503. Interestingly, API Gateway responds with the correct 401 status code, as confirmed through tests using Postman and other clients. We are currently unsure about the cause of this issue, but it is concerning because it gives the impression that there may be a problem with our Lambda authorizer.
Initially, we suspected that the issue could be related to the serverless-plugin-datadog or the datadog-lambda-js version, since we observed the following logs whenever a 401 status code was returned by the authorizer:

However, after reviewing the solution to the issue provided here, we continue to experience the same behavior, with the only difference being that the log messages from the extension have changed.

I have made an effort to create a minimal implementation to reproduce the issue, in order to determine whether there is an issue with our configuration or to seek assistance in resolving it. The implementation can be found at datadog-authorizer-issue. Please note that functioning AWS and Datadog accounts are required to use this implementation.
If you are unable to review the link, I have included the most crucial parts of the code below for your convenience:
.env
DATADOG_API_KEY=<your dd api key>
SHOULD_AUTHORIZE_REQUEST=false

serverless.ts
import { AWS } from '@serverless/typescript';

const configuration: AWS = {
  service: 'datadog',
  useDotenv: true,
  provider: {
    name: 'aws',
    runtime: 'nodejs18.x',
    timeout: 30,
    stage: 'test',
  },
  package: { individually: true },
  functions: {
    authorizer: {
      handler: 'dist/authorizer.handler',
      architecture: 'arm64',
      environment: {
        SHOULD_AUTHORIZE_REQUEST: '${env:SHOULD_AUTHORIZE_REQUEST}'
      },
      package: {
        patterns: ['!./**', 'dist/authorizer.js']
      }
    },
    getUsers: {
      handler: 'dist/get-user.handler',
      architecture: 'arm64',
      events: [
        {
          http: {
            method: 'get',
            path: '/',
            authorizer:  {
              name: 'authorizer',
              resultTtlInSeconds: 0,
              type: 'request',
            },
            cors: true,
          },
        },
      ],
      package: {
        patterns: ['!./**', 'dist/get-user.js']
      }
    },
  },
  plugins: ['serverless-plugin-datadog', 'serverless-offline', 'serverless-plugin-lambda-insights'],
  custom: {
    datadog: {
      enableXrayTracing: true,
      addLayers: true,
      apiKey: '${env:DATADOG_API_KEY}',
      env: 'test',
    },
    lambdaInsights: {
      defaultLambdaInsights: true,
    },
  }
}

module.exports = configuration;

package.json
{
  "name": "datadog-authorizer-issue",
  "version": "1.0.0",
  "main": "index.js",
  "repository": "git@github.com:akinboboye/datadog-authorizer-issue.git",
  "license": "MIT",
  "scripts": {
    "compile": "tsc",
    "deploy": "yarn compile && ./node_modules/.bin/sls deploy",
    "start:local": "yarn compile && node --inspect ./node_modules/.bin/sls offline"
  },
  "devDependencies": {
    "@serverless/typescript": "^3.29.0",
    "@types/aws-lambda": "^8.10.114",
    "@types/node": "^18.15.11",
    "aws-lambda": "^1.0.7",
    "serverless": "^3.29.0",
    "serverless-offline": "^12.0.4",
    "serverless-plugin-datadog": "^5.21.0",
    "serverless-plugin-lambda-insights": "^1.6.0",
    "ts-node": "^10.9.1",
    "typescript": "^5.0.2"
  },
  "dependencies": {
    "datadog-lambda-js": "^6.87.0"
  }
}

authorizer.ts
import {
  APIGatewayRequestAuthorizerEvent,
  APIGatewayAuthorizerResult
} from 'aws-lambda';
import { datadog } from 'datadog-lambda-js';

const authorizer = async (
  event: APIGatewayRequestAuthorizerEvent
): Promise<APIGatewayAuthorizerResult> => {
  const shouldAuthorizeRequest =
    process.env.SHOULD_AUTHORIZE_REQUEST?.toLowerCase() === 'true'

  if (!shouldAuthorizeRequest) {
    throw new Error("Unauthorized");
  }

  return {
    policyDocument: {
      Version: '2012-10-17',
      Statement: [{
        Action: 'execute-api:Invoke',
        Effect: 'Allow',
        Resource: '*'
      }],
    },
    principalId: 'user'
  }
};

export const handler = datadog(authorizer);

get-user.ts
import {
  APIGatewayProxyStructuredResultV2,
  APIGatewayEvent,
} from 'aws-lambda';

import { datadog } from "datadog-lambda-js";

const getUser = async (
  event: APIGatewayEvent
  ): Promise<APIGatewayProxyStructuredResultV2> => {
  return {
    statusCode: 200,
    headers: {
      'Access-Control-Allow-Headers': '*',
      'Access-Control-Allow-Origin': '*',
      'Access-Control-Allow-Methods': '*',
    },
    body: JSON.stringify({
      message: 'get user handler response',
    }),
  };
};

export const handler = datadog(getUser);

Thank you for reading or taking a look. 🙏

Did I submit this incorrectly? If so, could someone assist me in doing it the proper way?

Thank you @astuyve  for taking a look. See the expanded error below:

Even though these errors are thrown, they are understood by APIGateway and reported as 401.

I see - thanks for the context!
It's true that a Lambda-based custom Authorizer which throws an unhandled exception will result in a 401 status code being returned to the user by API Gateway, but as far as I can tell from the docs, this isn't the intentional way to return a 401 status code to the user from API Gateway.
This seems to be a side effect of the API Gateway + Lambda-based Custom Authorizer system designed to fail closed (eg - not permitting access if a function throws an unhandled error, and not leaking information to the calling user).
For token-based authorizers, returning the string "unauthorized" via callback is recommended here in the docs.
For request type authorizers, returning "unauthorized", or an empty string via the "Effect" key in the JSON response is recommended. (Same docs as above):

"Deny" will return a 403 status code (eg: the user provided an authentication token, but it was not valid for the requested resource).
As far as I can tell, there's no documentation suggesting developers throw unhandled errors to respond with 401 status codes. I apologize in advance if I'm mistaken here, as that's also a definite possibility.
This brings us to Datadog. Today I don't expect that we'll catch these errors and determine that a function is in fact an authorizer, which is throwing an unhandled error in an attempt to return a 401. Our tracers detect unhandled exceptions as an error and mark it as such. API Gateway decides to convert that to the user, so as to not leak information to a potential attacker (eg: this function panicked with that input).
As an aside: you can also save money on Lambda by rejecting requests with no authorization header (eg: 401) using a custom response mapping, which I believe is considered best practice, but likely not used frequently.
Please let me know if you've got any other questions, thank you!

thanks for looking @astuyve! What's funny is that using the callback style also results in the same effect. Basically a call up the stack throws an error, we handle that error and then pass Unauthorized to the callback. DD still reports it as 502 or 503.

Hey @akinboboye - I don't have a reproduction case with that on hand, but if you could update your repo with a case I can definitely look into it.

@astuyve I have updated the repo. The authorizer now uses the callback style to return unauthorized. https://github.com/akinboboye/datadog-authorizer-issue/blob/main/src/authorizer.ts

Hi @akinboboye , thank you for updating the example. However, I think this is still expected behavior.
If you remove all the Datadog instrumentation in this case, it's still treated as an error by the lambda runtime ( or the callback to be precise).  Therefore Datadog layer doesn't make any modification and behave the same.
To avoid such errors, we would recommend avoid the unauthorized path and instead use
export const handler =  function(event, context, callback) {
    var token = event.authorizationToken;
    switch (token) {
        case 'allow':
            callback(null, generatePolicy('user', 'Allow', event.methodArn));
            break;
        case 'deny':
            callback(null, generatePolicy('user', 'Deny', event.methodArn));
            break;
        default:
            callback("Error: Invalid token"); // Return a 500 Invalid token response
    }
};

as the AWS documentation is somewhat misleading regarding 401 information.
Please let us know if you have further questions.

Hi @akinboboye, you are right they did return 401 response code. However, when I tested with Datadog layers it's also returning 401.

With that being said, I was about to reproduce the Runtime.UnhandledPromiseRejection and you are right this is not intended behavior. (Thank you for providing the replicable test case again).
I was about to fix that by changing the authorizer.ts file.  line 6 import { datadog } from 'datadog-lambda-js'; should be removed and the last line should be export const handler = authorizer;.
This is because the handler function is already wrapped by the Datadog-Node18-x layer. Wrapping it again can cause unexpected behaviors.
Please let me know if this fixes your issue. In short, I don't think we are altering the response in anyway in the unauthorized case.

Hi, I don't really understand the last message by @joeyzhao2018.
I'm encountering the same issue in my project. When datadog-lambda-js is enabled the errors are returned as 500 internal server error. When it is disabled, everything works as expected (except for the tracing in Datadog).
I'm not importing datadog from datadog-lambda-js and I'm also not encapsulating my handler with datadog(), I'm directly exporting my handler.
So from my understanding the issue is in the "datadog-lambda-js" library. Is an issue logged in datadog-lambda-js? Or is it enough that this issue is open under datadog-agent?

Hi @MatthiasVanMeerbeek, thanks for reaching out.
This issue is quite old and I believe the root cause to the unhandled promise rejection error was ultimate fixed here, where throwing a custom error message w/ code ultimately resulted in an unhandled promise rejection error in ddtrace.
If this error is still occurring for you, please open an issue in datadog lambda js with detailed steps on how you can reproduce it (ideally with sample code or a small sample repo like above), as well as a detailed summary of which version of the software you're using.
I'm going to close this issue as it's unrelated to the datadog agent.
Thanks!


[doc] Refine link and heading issues in Pulsar metrics

Motivation

Broken links.
Incorrect headings.

Modifications
Fix the link and incorrect heading issues.

@Huanli-Meng could you please help review, thank you.


Extra inputs

I took the liberty of taking out the optional arguments in modules/default.nix since they are already defined in neovimConfiguration.

Thanks for the pr, lgtm!


Update additional profile, add record output pruning

This adds details for the thrid profile configured for validation.
It also adds a new option disabling record output support, which will prune all of the __quantum__rt__*_record_output function calls. This is on by default to match the behavior of other runtime support functions, and can be turned off via --no-disable-record-output-support.

@troelsfr I've added the pruning of the new runtime functions as default behavior, so I re-requested your review. Let me know if anything in there looks amiss, and either you or I can merge the change if you sign off again!

@swernli it looks good to me.


fix on latest nightly

This currently still fails all test cases, so I'd appreciate any
pointers as to what still needs to be fixed to make this work.

Hmm, apparently, it works just fine locally as well for me now. No clue, why this failed for me before.

Looks good -- yeah I was aware that finish was going to change on nightly. This strategy of version checking is fine.


add Trimage to list of image compressors

Trimage is a free desktop application for image compression, combining a number of different CLI tools into a friendly GUI. It's available on Debian, Ubuntu, Arch and other linux systems via the repositories.

Last commit on Github was years ago, is this really still active?

@Hrxn yes!

@Hrxn I am the author :) The GUI doesn't change much because it doesn't need to, and the underlying cli tools are kept up to date by the distributions!
@lvwzhen thanks!

Okay, good to know..

[..] and the underlying cli tools are kept up to date by the distributions!

MacOS and Windows?

@Hrxn need to be compiled if you want to use them, at which point you choose your own versions of optipng, jpegoptim etc.


Reference loss for Schema

Occasionally there is a need to modify properties within a 'schema' parameter passed into this method, for example 'Description' in my case.
But since the 'schema' parameter within this method is being assigned a new value, all property changes in 'schema' parameter are lost after the method returns to a calling context.
In order to keep potential property changes, the 'schema' parameter should be passed by reference, so that even if 'schema' parameter is assigned to 'actualSchema' instance, any changes to 'schema' properties are reflected in 'schema' parameter after returned from this method.
https://github.com/RicoSuter/NJsonSchema/blob/5c227cee9e3bc4ae21713a9eb491d3c6aaae8f70/src/NJsonSchema/Generation/JsonSchemaGenerator.cs#L509

I think the only option we have is to return the new schema... changing that would probably break quite some stuff - but can you create a PR with a proposal?


It builds the application but gives an error when I want to archive it.

It builds the application but gives an error when I want to archive it.
library not found for -lBVLinearGradient clang: error: linker command failed with exit code 1 (use -v to see invocation)
i am using 2.5.6

This error pops up when the pod platform does ios 11 but I should use 11 what should I


Parsing class definitions for methods and the init function for attributes.

Also use ast

https://github.com/JanEricNitschke/pyment/commit/c8f164150c9d7ff54c047f7a354d529e8c4799b5


Export-Excel accepts too long worksheetnames, leading to problems later on

Excel only supports worksheets up to 31 characters, but Export-Excel allows longer worksheetnames. The first time this happens, a warning is given, but if, in another call, a worksheetname is used which results in the same abbreviated name, an error occurs.
This could be prevented by disallowing WorksheetNames longer than 31 characters.
$blah | Export-Excel -Path c:\temp\blah.xlsx -WorksheetName ('blah'*8) -AutoSize -AutoFilter -FreezeTopRow -NoNumberConversion * -BoldTopRow

This results in:
WARNING: The Worksheet name has been changed from blahblahblahblahblahblahblahblah to blahblahblahblahblahblahblahbla, this may cause errors later.

But when I then do:
$blah | Export-Excel -Path c:\temp\blah.xlsx -WorksheetName ('blah'*9) -AutoSize -AutoFilter -FreezeTopRow -NoNumberConversion * -BoldTopRow

this results in an Error that does not show the actual problem:
Could not get worksheet blahblahblahblahblahblahblahblahblah
At C:\Program Files\WindowsPowerShell\Modules\ImportExcel\7.8.10\Public\Export-Excel.ps1:137 char:17
+         catch { throw "Could not get worksheet $WorksheetName" }
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Could not get w...lahblahblahblah:String) [], RuntimeException
    + FullyQualifiedErrorId : Could not get worksheet blahblahblahblahblahblahblahblah

Could you provide a small script, data that repros this?

$ErrorActionPreference = 'Continue'
$test = [pscustomobject]@{
    column1 = "Data"
}

Remove-Item C:\Temp\test.xlsx -ErrorAction SilentlyContinue
try { $WSName = "test"*8; $test | Export-Excel -Path c:\temp\test.xlsx -WorksheetName $WSName } catch { "Worksheet $WSName not created" }
try { $WSName = "test"*8; $test | Export-Excel -Path c:\temp\test.xlsx -WorksheetName $WSName } catch { "Worksheet $WSName not created" }
try { $WSName = "test"*9; $test | Export-Excel -Path c:\temp\test.xlsx -WorksheetName $WSName } catch { "Worksheet $WSName not created" }
try { $WSName = "blah"*8; $test | Export-Excel -Path c:\temp\test.xlsx -WorksheetName $WSName } catch { "Worksheet $WSName not created" }

Output:
WARNING: The Worksheet name has been changed from testtesttesttesttesttesttesttest to testtesttesttesttesttesttesttes, this may cause errors later.
Worksheet testtesttesttesttesttesttesttest not created
Worksheet testtesttesttesttesttesttesttesttest not created
WARNING: The Worksheet name has been changed from blahblahblahblahblahblahblahblah to blahblahblahblahblahblahblahbla, this may cause errors later.

Some people might say that it's already solved with the warning text, but a better error instead of 'could not get worksheetname' would be welcome.

If you can isolate in the code where that would be and let me know if it doesn't break things, I'll consider it.
You're the first person to report that you hit this issue.


[BACKPORT][0.8.4] The default values can't be changed in cluster config file for virtual machine.

Backport issues #2098
Related pull requests: #2220, #2258

✔ The default values for OS image, vm size, disk size, etc. can be easily changed in one place in the data yaml configuration file.


[next] HTML example material needs fixing

In the next docs, the html example doesn't appear to have the color or text updated on click.

This actually uncovered a larger problem with the current architecture of having a wrapping element surrounding the <canvas> to be able to attach stuff to it. Turns out the <OrbitControls> attach themselves to the renderer.domElement.parentElement, so the wrapping element, which seems fine at first. It turns out that the THREE.OrbitControls capture the pointer thus preventing any following pointer events from firing, such as the click event on the <HTML> contents. I'll make a follow up issue on that one, we'll have to think about a solution for that. For now, the HTML example is fixed in #1127  :)


can't find the description of the result file : output.prefix: msi score output

The list of microsatellites is output in "scan" step. The MSI scoring step produces 4 files:
output.prefix
output.prefix_dis_tab
output.prefix_germline
output.prefix_somatic
output.prefix: msi score output
Total_Number_of_Sites   Number_of_Somatic_Sites %
640     75      11.72
I can find  Number_of_Somatic_Sites can match the file  output.prefix_somatic，but  the Total_Number_of_Sites  640 is not，this  Total_Number_of_Sites isn't output as a result? Is there someone know where can i find the Total_Number_of_Sites? or description of this?

This file output.prefix_somatic will only output unstable sites whose FDR value less than 0.05. If you want to know the information of all the loci, you can use the -f parameter to make the FDR larger, and choose a value that can judge all the loci as unstable. Of course, at this time, the value of Number_of_Somatic will equal Total_Number_of_Sites. I suggest you try with -f 1.

table sites whose FDR value less

thx ur reply,
I already tried fdr=1,and the result  output.prefix_somatic do increased, but still not equal the Total_Number_of_Sites, and I tried other parameters ,the Total_Number_of_Sites changed.

You can use the -f parameter to make the FDR value larger, and you can try with -f 100. The FDR value of other sites may be larger than 1, so Number_of_Somatic not equals Total_Number_of_Sites when you use -f 1. And I think you don't need change other parameters. If you have any problems, please let me know. Thanks.


Take a copy of blocks in stopAllWork

Make it safe to modify the blocks set during iteration.

utACK


debugger keyword sometimes is not included

DEBUG is always false in production mode. Somehow it doesn't put the "debugger" keyword in this case.
Function:
    update: function(){
        if(this.__requireSnapshot){
            debugger
            if(!DEBUG){
                location.reload();
            }
        };
        // Script to check if the planets are correct
        // _.sortBy(data.logicPlanetStore.getInBlockId(0), '_id').forEach(function(p){console.log(p._id, p.units, p.owner.username)})
        if(this.__requireUndoUpTo !== void 0){
            this.undo(this.__requireUndoUpTo);
            this.__requireUndoUpTo = void 0;
        }
        this.applyAllChanges();
    },

Minified:
update: function() {
                this.__requireSnapshot && location.reload(), void 0 !== this.__requireUndoUpTo && (this.undo(this.__requireUndoUpTo), this.__requireUndoUpTo = void 0), this.applyAllChanges()
            }

Gulp file:
gulp.task("webpack:build", ['clean-dist'], function(callback) {
    // modify some webpack config options
    var myConfig = Object.create(webpackConfig);
    myConfig.profile = true;
    myConfig.resolve.alias.phaserUnFixed = "nodeModules/phaser/build/custom/phaser-arcade-physics.min.js";
    myConfig.resolve.alias.react = "nodeModules/react/dist/react-with-addons.min.js";
    myConfig.resolve.alias.lodash = "nodeModules/lodash/dist/lodash.compat.min.js";
    myConfig.resolve.alias.moment = "nodeModules/moment/min/moment.min.js";
    myConfig.custom.DEBUG = false;
    // Try min files first (From: https://github.com/webpack/webpack/issues/615)
    myConfig.resolve.extensions.splice(1, 0, ".min.js");
    myConfig.plugins = myConfig.plugins.concat(
        new webpack.DefinePlugin({
            "process.env": {
                // This has effect on the react lib size
                "NODE_ENV": JSON.stringify("production")
            }
        }),
        new webpack.optimize.OccurenceOrderPlugin({
            preferEntry: true
        }),
        new webpack.optimize.DedupePlugin(),
        new webpack.optimize.UglifyJsPlugin({
            sourceMap : false,
            compress  : true,
            exclude   : './src/server'
        }),
        // Renders stats.json in dist
        function() {
            this.plugin("done", function(stats) {
                var jsonStats = stats.toJson({
                    chunkModules: true,
                });
                // Analyze here: http://webpack.github.io/analyse/
                require("fs").writeFileSync(path.join(__dirname, "dist", "stats.json"), JSON.stringify(jsonStats));
            });
        }
    );

    // run webpack
    webpack(myConfig, function(err, stats) {
        if(err) throw new gutil.PluginError("webpack:build", err);
        gutil.log("[webpack:build]", stats.toString({
            colors: true
        }));

        // Copy image in preloader
        var mkpath   = require('mkpath');
        var image = 'Bit_Planets_symbol_white.png';
        var path     = '/assets/images/brand/Logo/'
        var distPath = './dist' + path;
        var srcPath  = './src' + path;
        mkpath.sync(distPath, 0700);
        var fs = require('fs');
        fs.createReadStream(srcPath+image).pipe(fs.createWriteStream(distPath+image));

        // Not used for now. But would delete the .js file related to the .css generated.
        gulp.start('clean-extra-css-js', callback);
    });
});

I think this is the only relevant code for webpack:
module.exports.plugins = [
    new ExtractTextPlugin("[chunkhash].css", {
        allChunks: true
    }),
    new HtmlWebpackPlugin({
        // templateContent: makeIndexHtml()
        template: 'src/assets/index.html',
        custom: module.exports.custom
    })
]

Man, this is totally unrelated but thank you so much for mentioning HtmlWebpackPlugin. It's the last thing that I needed in my workflow to completely ditch Gulp and go full Webpack..

@bitplanets Maybe uglify removes the debugger statement...

But only in some cases... What should I do then?

try
new webpack.optimize.UglifyJsPlugin({
  compress: {
    drop_debugger: false
  }
});

Thanks I will try it out!

Closing as this issue appears to be resolved. Please reopen if it has not. Thanks!

@sokra
I'm getting this error in Webpack 2:
ERROR in frame.js from UglifyJs
`crop_debugger` is not a supported option

any idea what the new one is? Was this removed?

@dodekeract You have a typo, the property is drop_debugger.

@moore0n Thanks. I swear that I triple checked this three times.

Note: for Webpack 4 you will need this format:
const UglifyJSPlugin = require('uglifyjs-webpack-plugin');

...

  optimization: {
    minimizer: [
      new UglifyJSPlugin({
        uglifyOptions: {
          compress: {
            drop_debugger: false
          }
        }
      }),
    ]
  },


remix-form errors message localization

Hi ,
How do you usually localize remix-form? I am stuck with it.
There is no way to pass a variable to the zod schema if you want to export it right?
Thanks in advance

@Mat-moran if you are trying to translate the error messages from the parser it might be useful to take a look at ZodErrorMap documentation.
You could also use the renderField property (as in the required indicator example) to customize the field labels and errors or even use the form children function for further flexibility.


Add I18n translations support in views

Hello @anthony-robin. Thanks for taking the initiative on this. @coop or I will review it over the weekend.

Great ! Let me know if there are some stuffs you wants me to change...

That's my first pull request. Should I edit my code and resubmit a new one ? Thanks !

That's my first pull request. Should I edit my code and resubmit a new one

Do the work as a new commit and then use git commit --fixup <sha> where the <sha> is the commit where the work should have originally occurred. Once all that looks good we can rebase against master, squashing the fix ups, and we have a nice, clean history.

Also, english is not my first language, so feel free to update README instructions if the section I added doesn't use correct syntax.

No, it was great 😄

@andychisholm I've updated master to run against Ruby 2.3 and Rails 5 and the specs are all 💚.

I made the changes you asked for (I hope I didn't mess too much things with git history ^^) !
I also added an alert confirmation before to destroy a job (I forgot to do it last time).
Thanks !

Thanks @anthony-robin. I’ll try to have a look at this tonight.

On 27 Nov. 2016, at 9:54 pm, Anthony<EMAIL_ADDRESS>wrote:
I made the changes you asked for (I hope I didn't mess too much things with git history ^^) !
I also added an alert confirmation before to destroy a job (I forgot to do it last time).
Thanks !
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@anthony-robin This is perfect 👌
Now that I have completed the review do you mind doing a git rebase -i master --autosquash and it will squash the fixups and replay your commits on top of master. Then I will merge and make a release 😄

Great ! I'v used the command git rebase -i master --autosquash but what should I do next ? 😕
Should I merge to my branch master ?
I tried to push to feature/i18n-views and it says me to pull first (which give me conflicts).
I'm lost, thanks for your help ! 👍

I tried to push to my feature/i18n-views fork branch and it says me to pull first (which give me conflicts). Is that normal ?

Yes, you need to force push with git push --force origin feature/i18n-views. origin is what ever you have called your remote.
The reason you need to force push is because you "rewriting" history, but that's okay in a pull request under review.

Done ! I pushed force to origin feature/i18n-views as you explained.

Thanks for your contribution @anthony-robin 😄
I've merged into master and released to ruby gems https://rubygems.org/gems/delayed-web/versions/0.4.2.

Perfect ! That was a pleasure to contribute :)

You did good mate.

On 30 Nov. 2016, at 7:53 am, Anthony<EMAIL_ADDRESS>wrote:
Perfect ! That was a pleasure to contribute :)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


How to uninstall?

I might be completely daft, but I can't seem to figure out to uninstall scream again after installing the driver.

in the install folder there's a readme file that says
To uninstall
------------------------------------------------------------
Locate the Scream driver in device manager and uninstall it
there. Make sure to choose the "Remove driver software"
option when uninstalling.

;)

Ahh, it was just me being daft then! Thanks :)