Feature Request: Opening in temporary containers based on domain

It would be cool if the feature existing with Mouse Clicks per Website could be extended to also trigger when entering a domain into the address bar, allowing to contain websites similar to the feature "alwasys open in $container" of Mozilla's original Container Add-on without explicitly creating a container for this website. This would be especially useful for websites that should be contained into their own container, but are only visited rarely, not justifying their own container.
The Mouse Clicks per Website-feature currently works with clicking links, but there is no option to trigger a temporary container by entering specific domains into an uncontained tab.

So I guess you use the Add-on with Automatic Mode deactivated? I think it should be no big problem to implement a "Always open in Temporary Container per Website" and make it available in the preferences.
Just a side-note: With Automatic Mode disabled Mouse Clicks have no effect whatsoever currently, tho I plan to decouple that.

So I guess you use the Add-on with Automatic Mode deactivated?

Yes, that is correct. This feature is of course only relevant with Automatic Mode deactivated.
Didn't know about the Mouse Click no-effect thing, just starting out with the add-on, thanks for the hint!

Well, it depends, you can open "No Container" tabs using keyboard shortcuts in Automatic Mode - and I'm not sure whether the new preference should have an effect in those "No Container" tabs too.

If you mean Tabs not in a container by No-container-Tabs, then I would argue that it should, because from my point of view the purpose of this feature would be the containment of websites into temporary containers, regardless of their origin.

I agree. Just published version 0.17 with the feature. If something is not working as expected please let me know.

Oh, and btw, the new version also includes the decoupling of "Automatic Mode" and "Mouse Clicks" - so you could configure Mouse Clicks even with Automatic Mode disabled if you would want to.

That was fast, thank you very much! :)

Works perfectly fine as far as I can tell so far, thank you very much.
I personally would like an option (checkbox or so) to also apply this logic for things already opened in a different container, so that if those sites are linked on a site in a certain container, they still are opened it a separate standalone temporary container. That would be quite beautiful! :)

Just published version 0.59 with change to the "Always open in" feature:

If a "Always open in" Website pattern loads in a tab that doesn't match the pattern, a new Temporary Containers gets created. This is also true for permanent containers - unless the checkbox in the preferences for that pattern to "Allow in permanent Containers" is ticked. The migration path for existing patterns is to allow loading in permanent containers
If the Website is also assigned with Multi-Account Containers nothing happens (MAC 6.0.0 is required, if the Website is assigned with versions below 6.0.0 unexpected behavior will happen)

Hope you like it. Let me know if something doesn't work as expected.

So far this works really excellent! Thank you very much, precisely the piece I missed in the Containers-Ecosystem so far to leverage its maximum potential.
Thank you very much for taking care of realizing! If I encounter any bugs, I will file them, but I haven't noticed any so far in production.

Do you think it's feasable to have an option to open the specified pages in a temporary container even if they are already in a container? i.e. I have a website in a container, that is linking to an external page that is listed for temporary containers, currently that one gets opened in the container I'm already in. It would be cool if this one would be opened in a temporary container instead, unconditionally quarantining certain pages into their own container.
Just a question of feasability, if not, I'm already happy enough with what you have built so far. :)

Could you elaborate on how your current preferences are and what you would expect them to do different?
If you open a website now, regardless if in a container, tmp container or no container and click on a link which matches a Website pattern that is configured as "Always per Website" (and the "Allow in permanent containers" not ticked), then this link/website will open in a new Temporary Container.

hm, sorry for the noise. Somehow I thought that this feature did not work when the starting site was already inside of a container. However, the site I noticed that now behaves exactly as desired, the link leads to the external page being opened in a temorary container as it should be (and you describe). Seems like my memory played tricks on me, nevermind, everything works like a charm. :)

No problem, happy it works!
Though, I noticed, that it opens the site multiple times in a new Temporary Containers in that exact scenario. Gonna fix that. :)

The multiple times reopening thing is now a thing of the past with version 0.63

Thank you very much,keep up the good work! :)


Remove Babel helper binding renaming

The attempt to fix the Babel helper binding renaming in #31 didn't work for all cases. The transform-object-rest-spread uses:
babelHelpers['extends']

It seems safer to just remove this optimization, and let the helpers stay named babelHelpers..

Could we just make Babel use a more consistent format?

@eventualbuddha isn't it up the plugin author to determine how the helper is invoked? Or add extra helpers to the collection for their plugin?

One possible way to get the best of both worlds would be to import a virtual, ES2015 version of the babel-helpers where one or more helper are used.
import * as babelHelpers from 'babel-helpers';

// This access will be optimised automatically by Rollup.
babelHelpers.createClass(...);

// Rollup will make sure this dynamic access will work
// while preserving all other optimised accesses.
babelHelpers[ dynamic ](...);

When babel-helpers is imported, we inject a virtual module like so:
return buildExternalHelpers( all, 'var' )
  .replace( /var babelHelpers = {};\n/, '' ) // strip declaration
  .replace( /babelHelpers\.(.+) = /g, 'export var $1 = ' ) // export the helper
  .replace( 'babelHelpers;', '' ) // not sure where this comes from...
  .trim() + '\n';

Thoughts?

Would you guys be up for merging this to fix the immediate issue of Rollup producing code that errors when certain Babel plugins are being used? And in parallel we can get a more robust solution in place and explore ideas like @Victorystick's?

I'm fine with that.
On Thu, Jan 14, 2016 at 8:37 AM Eric Ferraiuolo<EMAIL_ADDRESS>wrote:

Would you guys be up for merging this to fix the immediate issue of Rollup
producing code that errors when certain Babel plugins are being used? And
in parallel we can get a more robust solution in place and explore ideas
like @Victorystick https://github.com/Victorystick's?
—
Reply to this email directly or view it on GitHub
https://github.com/rollup/rollup-plugin-babel/pull/34#issuecomment-171693951
.

@ericf Absolutely. :+1:
I've just realised that we'll run into trouble with babelHelpers.typeof = ... using my approach. We cannot transform it into an exported var declaration. It'll result in a SyntaxError. If only Babel had chosen to name it typeOf instead... :sob:
export var typeof = ...

export var typeOf = ...

@Victorystick @eventualbuddha okay great! Let me know if there's anything else I can do to help you guys get a patch release out.

Released in v2.3.9.

Thanks guys!


Overparametrization of the MNIST images

It seems that the MNIST images are tiled so they have three (identical) color channels, matching the CIFAR-10 format (data_loaders/get_mnist_cifar, lines 43-44:)
x_train = np.tile(np.reshape(x_train, (-1, 32, 32, 1)), (1, 1, 1, 3))
x_test = np.tile(np.reshape(x_test, (-1, 32, 32, 1)), (1, 1, 1, 3))
Since this triples the size of the latent representation, I wonder whether this is the best way to model MNIST images with Glow. Any reason why I shouldn't disable this tiling by removing the np.tile call?

Was the reason you used this method is so you can load a model with pretrained weights? Or was it for something else.

No pre-trained weights, training an MNIST model from scratch.


'?' > 'Support' link is not working (404 error)

Bug description:
After clicking on ? > Support in menu bar, we are redirected to a 404 error page.
Steps to reproduce:

Go to menu bar
Click on help menu '?'
Click 'Support'
See 404 error in browser

Expected behavior
I think we have to modify the link and point it elsewhere (maybe GitHub).
Screenshots

Environment:

Operating System: Windows 10
Ferdi Version: 5.6.0

https://getferdi.com/contact/

@all-contributors please add Tsakatac for bug


chore: bdd-nh-1586955983 to 0.0.1

chore: Promote bdd-nh-1586955983 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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


Where gap?

Hello, I see in the documentation there is a prop gap, but in version 1.0.3 it cannot be set to Toaster. When will she appear?

Gap is available on the Toaster component as a prop.


MS missing HUC8s

As of FIM v<IP_ADDRESS>, there are 33 HUC8s/15 HUC6s that do not run to completion using the MS extent.
No errors are thrown for these HUCs because they fall under two catches that are used to exit run_by_unit.sh gracefully if an input HUC does not have a MS extent.

No relevant streams: This early exit category should occur only if there are AHPS sites within the WBD buffer but none that flow into the HUC of interest. The following HUCs have MS stream segments within the HUC but are exiting with this category:
10030203, 16050103, 17100103, 17100104, 17100106
As an example, 17100103 is shown below

where the blue lines are NWM MS stream segments and the red points are the nws_lid sites. This example includes both nws_lid (MS) headwater sites as well as nws_lid sites downstream of headwaters.

No AHPS points: This early exit category should occur only if there are no MS segments within a HUC of interest. The previous category is a special case of this category. If there are any nws_lid (AHPS) sites within the WBD buffer OR if there are any incoming MS streams from and upstream HUC, this exit category should not occur. The following HUCs have MS stream segments within the HUC but are exiting with this category:
03050201, 10170104, 17100101, 17100202, 17100203, 17100204, 17100205,
17100206, 17100301, 17100302, 17100303, 17100305, 17100307, 17100308,
17100309, 17100310, 17100311, 17100312, 20010000, 20020000, 20050000,
20060000, 20070000, 21010002, 21010003, 21010004, 21010005, 21020002
The majority of the HUCs in this list are coastal (2001+ are outside of CONUS and 1710 are along the West Coast).
As an example, 17100101 is shown below

where the blue lines are NWM MS stream segments and the red points are the nws_lid sites. This example includes both nws_lid (MS) headwater sites as well as nws_lid sites downstream of headwaters.

Related
To address issue #416, each of these categories will be uniquely identified in the log files. This will allow tracking of these HUCs as development continues.

Could we see a quick map of the impacted HUC8s/HUC6s for the MS configuration?


Fix broken handle server for Java 1.8 (DSpace 6.x version) - WIP

References

See #8557
Related to Handle Server
Failing build on commit: https://github.com/OyvindLGjesdal/DSpace/actions/runs/3427420789/jobs/5710401426

Description
Updates to dependencies for dspace-handle server for the dspace-6_x branch, currently fails during build, with mismatch when pulling in dependencies. Handle server not tested for 6_x branch.
Instructions for Reviewers
List of changes in this PR:

First, ...
Second, ...

Include guidance for how to test or review your PR. This may include: steps to reproduce a bug, screenshots or description of a new feature, or reasons behind specific changes. See failing job above.
Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

[ ] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & integration tests). Exceptions may be made if previously agreed upon.
[ ] My PR passes Checkstyle validation based on the Code Style Guide.
[ ] My PR includes Javadoc for all new (or modified) public methods and classes. It also includes Javadoc for large or complex private methods.
[ ] My PR passes all tests and includes new/updated Unit or Integration Tests based on the Code Testing Guide.
[ ] If my PR includes new, third-party dependencies (in any pom.xml), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[ ] If my PR modifies the REST API, I've linked to the REST Contract page (or open PR) related to this change.

I'll edit the list of changes in the PR and comments tomorrow but at least the CI completes now.
Maybe publishing a fixed old handle-server is the better option.
I.e some of the upgrades could break java 7 support (like for dspace 5) (Jetty lists 8 as supported for the latest 9.x version).

What do you think @tdonohue? This is as far as I can get myself with this PR I think.

@OyvindLGjesdal : Thanks for your work here!  I've been on holiday for the last week & busy with workshops just before that...so I haven't been able to look at this PR for almost a month now.  Skimming it now, I do see you've asked a lot of questions in the description & the implication of several is that this upgrade to Handle v9 may not be as easy as it seems (and may have unintended side effects).   I haven't yet had time to do a more thorough review, but will see if I can get back to this later this week.
In the meantime, I'm linking this PR up with your original ticket (#8557) to make it more easily findable to others...currently it isn't mentioned in that ticket.

I've started looking this over. It looks basically correct (haven't tried running it yet), but the big version jumps and the YOUR_NAMING_AUTHORITY vs YOUR_PREFIX thing are setting off warnings in my the back of my mind that upgrading DSpace 6 to use Handle 9 might not be the correct path.
I'll continue poking it and see if anything breaks. I suspect, though, that having folks use a modified Handle 6.2 jar would be an easier and safer solution.

@ilittle-cnri : FWIW, if there is a modified Handle 6.2 JAR that people on DSpace 6.x could continue to use, I agree that'd be the best solution here.  However, to my knowledge no such Handle 6.2 JAR exists which is compatible with the latest JDK 8 (per the issue described in #8557).  If CNRI (or someone else) is able to create such a JAR, then that'd be quite simple to swap DSpace 6 over to using it (as it's just changing the dependency in the POM)

I'll talk to folks to see if that's something we can do, or at least assist with. Would it be most helpful if it was in a Maven repository, or is just a link to a jar sufficient?

@ilittle-cnri : most helpful would definitely be if it was in a Maven Repository, as that means DSpace just needs to update our POMs.  However, if that's not possible, then a JAR is second best... but, please be aware that may mean we'd have to release that JAR to our own DSpace maven repo just to make it easier for DSpace sites to use/install.  Thanks!

Someone has created such a JAR (6.2 repaired for recent JRE), and it's working here.  Read on down through #8557 to see the thread by ebalnaves.


Explorer autohide mode should be added

From the second comment:
I like the file explorer bar to be hidden when i put the cursor in the
editor

What is "Explorator autohide mode"?
You should not include multiple items in a single issue. The 2nd part might be covered by #396.

What is "Explorator autohide mode"?
i meant :
I like the file explorer bar to be hidden when i put the cursor in the
editor
2016-07-31 15:42 GMT+02:00 Glen<EMAIL_ADDRESS>
What is "Explorator autohide mode"?
You should not include multiple items in a single issue. The 2nd part
might be covered by #396 https://github.com/Microsoft/vscode/issues/396.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/9984#issuecomment-236430585,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARIVms2JfIUhJn9LqoRs4cEG-5PGavM4ks5qbKZNgaJpZM4JY6tE
.

--
Cordialement,
______________________________________________
Khalid ELABBADI
Directeur associé
*Software Engineer *
*Tél *: 06 62 04 83 70
www.segma-it.com

Duplicate of #3742.

I made an extension which enables this. See here: https://github.com/Microsoft/vscode/issues/3742#issuecomment-285209856


search email [Help]

Sorry, I can't find any information about it maybe somebody can help.
    $search = User::boolsearch();
        $search->should((new MatchQueryBuilder())->field('email')->query($this->search)->fuzziness('AUTO'));
        $search->minimumShouldMatch(1);
        $search->withTrashed();
    $users = $search->paginate($this->pagination);
    $users->setCollection($users->models());

it's not searching without I not write a full email

rolandverner will not find
rolandverner@ will not find
rolandverner@outlook will not find
and<EMAIL_ADDRESS>find correctly with fuzziness the similar finds

And another question how to use eloquent with eslaticsearch?
        $users = User::query();
        $users->accountVerified();
        $users->registered();

        $users->boolsearch();
        $search->should((new MatchQueryBuilder())->field('email')->query($this->search)->fuzziness('AUTO'));
        $search->minimumShouldMatch(1);
        $search->withTrashed();

it's not searching without I not write a full email

Please check your mapping, not all types allow partial search.

And another question how to use eloquent with eslaticsearch?

The driver searches data in Elasticsearch, then finds the respective models in the database using primary keys. This is how Scout works in general. If you need to refine the search results, it's better to add a filter in the search request itself.

Closing as it's not a bug or a feature request.


webstorm support please!

I'm a huge fan of gitlens, one of my fave features of VSCode.  But I also love webstorm.  Any chance you guys can add support for webstorm? :)

Like I mentioned on the request for Atom, this would not only be a large undertaking, it also isn't something I'm really interested in right now as I am not a Webstorm user (and I would want to use the product regularly to ensure its high quality).

I know -- sorry.

Not only for webstorm, as Jetbrain's software have same plugin system, it could work for pycharm, intelliJ, android studio, etc.

Vote +1 for PyCharm 👍

Vote +1 for PyCharm  Too👍


Level selector does not react on clicking the empty part of scrollbar container

It is probably caused by updating the list viev only on IDCMP_MOUSEMOVE while it should be also updated on IDCMP_GADTETDOWN. Issue #21 may be related.

Updating window content also on IDCMP_GADGETDOWN fixed the problem in commit a3a38a0.


Check active governor and flush STDOUT pipes

In function set_governor() add check for current active governor, and perform governor change to "powersave" only if it is not in "powersave" mode. Also print message to log about this.
Motivation: it saves few system calls every 2 seconds, and possibly avoids some unknown problems with epp driver(it can trigger some internal changes even if we changing to the same value?). Print message because by default governor should be in "powersave" mode, and if something changes it constantly we should see this in the logs.

Add sys.stdout.flush() call after every print message. Our service's STDOUT and STDERR are pipes, and in this case the buffer is only flushed once it is full. Hence the script's messages only turn up in systemd's logs after it has produced even more output. Alternative is to add "Environment=PYTHONUNBUFFERED=1" to service unit file in [Service] section.

OK, everything looks good! :+1:
Thanks for your contribution!


Is this project still supported or maintained

Looking for support with Visual Studio 2019.  Is this project current and maintained?

No. It's not supported or maintained any more. Folks should use self-packing .csproj projects where possible. Where that's not an option, ... we're still not maintaining this any more.


ValueError: invalid literal for int() with base 10: '501.png\n'

hi,
when I run  the command
python main.py --c ./setting/SINet.json
there is a error:
ValueError: invalid literal for int() with base 10: '501.png\n'
my dir tree is
.self.data_dir(../Link512DATA/)
├── Nukki
│   ├── baidu_V1
│   │   ├── input
│   │   ├── target
│   │   ├── train.txt
│   │   └── val.txt
│   └── baidu_V2
│       ├── input
│       ├── target
│       ├── train.txt
│       └── val.txt
└── Portrait
└── train.txt
the Portrait's train.txt is same as the baidu_V1's train.txt
could you help me?

Sorry for the uncomfortable code.
Could you download both datasets again?
I change the folder name for coincidence.


Support stringref proposal

missing *.c files under core/iwasm/common/stringref ?

missing *.c files under core/iwasm/common/stringref ?

@lum1n0us
stringref contains two parts:

part 1: add new ref type in WasmGC, add opcode processing in loader and interpreter
part 2: a library for string representation/encoding/decoding ...

We want to reduce the code size introduced to WAMR, so this PR only include part 1, part 2 will be provided by embedder, they can use their own implementation (e.g. Wasmnizer-ts use JSString from QuickJS to implement stringref)
Later we will submit another PR of part 2, but we want to make it as a sample rather than WAMR core part


Count of set bits in an integer using Lookup Technique.

💥 Proposal
(A clear and concise description of what the proposal is.)
Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)

/assign

PR merged for this issue , so closing it.


Pre-release sdist CI job is failing

Example from https://dev.azure.com/scipy-org/SciPy/_build/results?buildId=13644&view=logs&j=5a504361-84f9-5b04-9e0f-a07fc1c630c2&t=fb42939b-bd21-5b32-1e4c-876ce4d20951:
Looking in indexes: https://pypi.anaconda.org/scipy-wheels-nightly/simple
ERROR: Could not find a version that satisfies the requirement numpy (from versions: none)
ERROR: No matching distribution found for numpy

Not sure what changed there. @charris or @mattip any thoughts? Did one of you clean up a set of wheels from the anaconda.org bucket maybe?

I deleted all but the 3.8+ versions (except for pypy) so that it would elicit errors. I suspect CI is looking for a 3.7 version. (checks) Yep it is using 3.7.

Hmm slightly aggressive, but I guess it's a good prompt for us to drop 3.7 in master:)


[BugFix] Fix ClassCastException when query from information_schema.load_tracking_logs with job_id

What type of PR is this：

BugFix

Which issues of this PR fixes ：

Fixes #20481
Problem Summary(Required) ：
That same error occurs when query information_schema.loads and information_schema.load_tracking_logs.
The switch-case statement seems a typo-error, losing "break" statement in last PR.
Have tested it in our test environment.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

bugfix for the main branch

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.drake_wang seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for your contribution.Could you sign off and sign the CLA?
You can sign off by ‘git commit -s’

DCO doesn't pass because you didn't sign-off the commit.
You need to do it by executing the command 'git commit -s'.
Then push it to the repo

DCO doesn't pass because you didn't sign-off the commit. You need to do it by executing the command 'git commit -s'. Then push it to the repo

Thanks, I have Signed-off

@decster @meegoo this pr related to information_schema, may i have your time to review it? thanks

@mergify backport branch-3.0


Fix TabContainer using wrong content rect after tab title update

Continuation of #90942.
This PR fixes a bug that only happens when you update tab title after updating tab icon. Updating tab icon before updating tab title is fine. 3.x does not have this bug.
Tab title can affect minimum size even when clipping tabs (e.g. changing from using empty title to some visible text).

Before
After

The magenta rect is the tab content.
Test project: tab-container.zip

Thanks!


Add issue templates: bug and enhancement

Create two issue templates in the meshery-octarine repo by copying the meshery repo's issue templates.

Fixed by #12


Theme not working in screen sessions

For some reason the theme isn't working on screen sessions, look the differences.

I'm trying to figure out what is happening, everything is fine on tmux.
The same happens on vim and neovim.

@sobrinho seems you need to enable true colors in screen. take a look at this commit http://git.savannah.gnu.org/cgit/screen.git/commit/?id=9668a1ab00fea2096555a33cb962cc865b86e74a

I'm trying to figure it out.
It is a compile flag or a runtime flag or both?
I tried to clone the screen source and do ./configure --truecolor also --enable-truecolor and --with-truecolor and all of them is unknown 😞

@sobrinho you have to create .screenrc in HOME with truecolor on. at least this is what I understood from the docs.

Yes, seems like that but the master branch is not building right on OS X and homebrew is broken to build from HEAD: https://github.com/Homebrew/homebrew-dupes/issues/668
Trying to fix it here :(

Anyway, this is not a issue from ayu-theme itself, so, I'm closing and moving on (I can use tmux if is not possible to compile the master screen).


Writeup a proposal for error correction enabled BIP39 seed phrases

Summary
One of the reasons for loss of funds in Valora, and other crypto wallets, is that the account key is mangled. Misspelling, swaps, duplicates, and other issues can result in a key that cannot be used to recover the account. BIP39 specifies a checksum that can, with reasonable high probability, detects errors and misspelling will result in a word that is not in the list, but it does not have any built-in support for error correction.
Various error correction techniques could be used, but the most applicable is Reed Solomon error correction. By replacing a portion of the random key with error correction, a number of lost words can be fixed automatically.
Such a scheme should be proposed as a CIP or CRC.

Proposal is now available in Draft status https://github.com/celo-org/celo-proposals/blob/master/CIPs/cip-39.md


Failed to upload attachment when creating news item

Request identity<EMAIL_ADDRESS>- KINSHASA NEWS (slyongo via shop) (WEB)
KeyError: u'\u0301'
at quote (/base/data/home/runtimes/python27/python27_dist/lib/python2.7/urllib.py:1294)
at _quote_filename (/base/data/home/apps/e~rogerthat-server/63.405326633714776717/lib/cloudstorage/api_utils.py:94)
at open (/base/data/home/apps/e~rogerthat-server/63.405326633714776717/lib/cloudstorage/cloudstorage_api.py:91)
at upload_to_gcs (/base/data/home/apps/e~rogerthat-server/63.405326633714776717/rogerthat/bizz/gcs.py:37)
at post (/base/data/home/apps/e~rogerthat-server/63.405326633714776717/solutions/common/handlers/broadcast.py:58)

Another occurrence
2018-04-26 21:49:26.611 CEST
u'\xe9' (/base/data/home/apps/e~rogerthat-server/20180424t113917.409246710421677010/add_1_monkey_patches.py:127)
Traceback (most recent call last):
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/c5586dbb532f7e5f_unzipped/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1511, in __call__
    rv = self.handle_exception(request, response, e)
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/c5586dbb532f7e5f_unzipped/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1505, in __call__
    rv = self.router.dispatch(request, response)
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/c5586dbb532f7e5f_unzipped/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1253, in default_dispatcher
    return route.handler_adapter(request, response)
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/c5586dbb532f7e5f_unzipped/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1077, in __call__
    return handler.dispatch()
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/c5586dbb532f7e5f_unzipped/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 547, in dispatch
    return self.handle_exception(e, self.app.debug)
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/c5586dbb532f7e5f_unzipped/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 545, in dispatch
    return method(*args, **kwargs)
  File "/base/data/home/apps/e~rogerthat-server/20180424t113917.409246710421677010/solutions/common/handlers/loyalty.py", line 103, in post
    upload_to_gcs(uploaded_file.value, content_type, gcs_filename)
  File "/base/data/home/apps/e~rogerthat-server/20180424t113917.409246710421677010/rogerthat/bizz/gcs.py", line 38, in upload_to_gcs
    with cloudstorage.open(file_name, 'w', content_type=content_type) as f:
  File "/base/data/home/apps/e~rogerthat-server/20180424t113917.409246710421677010/lib/cloudstorage/cloudstorage_api.py", line 91, in open
    filename = api_utils._quote_filename(filename)
  File "/base/data/home/apps/e~rogerthat-server/20180424t113917.409246710421677010/lib/cloudstorage/api_utils.py", line 94, in _quote_filename
    return urllib.quote(filename)
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/c5586dbb532f7e5f_unzipped/python27_dist/lib/python2.7/urllib.py", line 1294, in quote
    return ''.join(map(quoter, s))
KeyError: u'\xe9'


auto click

Greetings,
I have a button "button.bind(on_press=self.show_popup)". How can I make it click automatically without pressing the mouse?

There are various ways to do so, but the easiest way i can think of is using the dispatch method of an object
Event Dispatcher,
also for support pls use one of the following https://github.com/kivy/kivy?tab=readme-ov-file#support


Upgrade cargo-vet and add imports

We recently released a new version of cargo-vet with improved ergonomics in various areas. In case this is of interest to Fermyon, I prepared a PR to upgrade the tool and get the instance back into a green state (via cargo vet regenerate exemptions).
Previously, the tool would conservatively import any remote audit that might be relevant, whereas now imports.lock contains the minimal set of what's actually used. This is the reason for the changes in that file.
I also proposed a few additional imports to the list to match the imports Mozilla and wasmtime are now (or will soon be) using. This allows a number of exemptions to be pruned, but happy to drop any of those as desired.

Could you please rebase and sign your commits, please?
(both sign-off and with a GPG key)
Thanks!

@radu-matei Done.
I might also suggest reconfiguring CI to run cargo-vet as a blocking step rather than as a cron job. It appears to have gotten stale in the latter configuration, and the tool is a lot more useful when you keep it in a green state. You can always add exemptions in situations where you want to defer the audits on a PR for whatever reason.

The main reasoning behind having a cron job rather than blocking on a PR was that we usually have non-maintainers contributing to the code base, and for the audits, we would like to keep them to just maintainers. Besides trusting audits from external people, we would also add an extra burden to someone submitting a PR.
Do you have thoughts around this?

The main reasoning behind having a cron job rather than blocking on a PR was that we usually have non-maintainers contributing to the code base, and for the audits, we would like to keep them to just maintainers.

Agree this is an important property to maintain!

Besides trusting audits from external people, we would also add an extra burden to someone submitting a PR.
Do you have thoughts around this?

Indeed. There are basically two ways to handle the situation when an external contributor submits a patch which adds new third-party Rust code.
The first is for the reviewer (presumably a maintainer) to go and perform the relevant audits (or add the relevant exemptions) and ask the contributor to rebase on top of that. This is what wasmtime and Firefox do.
The second is to ask the contributor to add exemptions (either manually, or with the tool) and then file a followup for a maintainer to go remove those exemptions and replace them with actual audits. This can reduce the synchronous demand on the reviewer's time and remove contribution delay in some cases, but does result in new unaudited code appearing in the tree until the followup happens (Firefox and wasmtime have policies against this, hence the former approach).
It may vary by use-case, but our experience has been that casual contributors mostly don't need to do major fiddling with Rust dependencies, so it hasn't been a super-frequent situation in practice.

Rebasing makes sense in this scenario. Let's track moving to blocking on PRs separately and give other maintainers a chance to comment.
I think this change is good to go, thank you so much for your contribution, @bholley!


Add SPDR space

Add SPDR space and custom domain vote.spiderdao.io

There is a conflict in your PR, can you resolve it?

It's now possible to create and edit a space without doing pull requests but using ENS and IPFS instead. Could you use this new method to create your space? Here is the guide: https://docs.snapshot.page/guides/create-a-space (you can keep your PR for add the images and skin)

Closing this PR and opening a new one.


Monorepo support

Would adding support for autodiscovery of terraform projects within a monrepo root or subdirectory be possible? Currently I've got 3 or 4 projects where I have to write several hundreds lines of yaml to manually add each project (also remembering to update yaml when a new project is added).

Hi Ben,
Would something like the following allow you to just get the failed checks section of the json without a new flag?
checkov -o json -f terraform/aws/ec2.tf | jq .results.failed_checks

checkov -o json -f terraform/aws/ec2.tf | jq .results.failed_checks > just_failed.json

I'm basically looking for something that includes directories/files to
check. Maybe an excludes would be easier to implement at least then things
can run a bit faster and dependencies/libs aren't being scanned recursively.
On Mon, Feb 8, 2021 at 5:36 PM Matt Johnson<EMAIL_ADDRESS>wrote:

Hi Ben,
Would something like the following allow you to just get the failed checks
section of the json without a new flag?
checkov -o json -f terraform/aws/ec2.tf | jq .results.failed_checks
checkov -o json -f terraform/aws/ec2.tf | jq .results.failed_checks > just_failed.json
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bridgecrewio/checkov-action/issues/22#issuecomment-775564640,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB4XFKYHTRTQD2N5VM2KDTS6B7RHANCNFSM4VB4PVVQ
.

Hello @btilford
I think we may be able to satisfy what you're after as-is. I'm not sure about excluding dirs yet. But checkout below:
I use this action configuration to run a recursive checkov scan only in the 'modules' directory. By specifying 'framework: terraform' I am only running terraform scans.
      - name: Run Checkov action
        id: checkov
        uses: bridgecrewio/checkov-action@master
        with:
          directory: modules/
          quiet: false
          soft_fail: false
          framework: terraform
          output_format: cli

Will this do what you want? You could do things like use several blocks if you want to choose different specific dirs and subdirs to scan.

Did not test, but directory: dir1/ -d dir2/ -d dir3/ might do the trick to scan selected set of directories.
While we're at it, can we enable Checkov GH actions to take multiple directories?

@alen-z I'm using .checkov.yaml to work around more options than the GitHub Action supports, such as skipping multiple directories with skip-path. Here is my working template that I use in this and other repos:
https://github.com/HariSekhon/Templates/blob/master/.checkov.yaml


Create a timeline

Add a list of all your activities, achievements, work experience. Add as much info as you can remember. In case you don't have working experience tell about your pet-projects or student projects. Don't be shy :)

Your resume should include information relevant to the position for which you’re applying. You can also include achievements and interests, but these should only be included at the end of your resume, and only if they are relevant. If your resume is multiple pages, consider removing optional sections like these to make it as brief, concise, and readable as possible.


🐛Bug: Unable to install/reference System.Threading.Tasks.Dataflow library in interactive notebook

Describe the bug
👋 Hey there! I'm having a problem installing the System.Threading.Tasks.Dataflow library from within a Polyglot notebook. No message is produced on the initial message and all references to the package in subsequent code blocks lead to are you missing an assembly reference? errors (including the using statement itself)
My understanding from this issue is that the library is "a framework assembly and is preloaded by the interactive session". Is it possible to either:

Import the framework assembly?
Have the UI produce a meaningful message if the package fails to import?

Detail in screenshots below - Thanks in advance for the help!
Please complete the following:
Which version of .NET Interactive are you using? (In a notebook, run the #!about magic command. ):

.NET version 8.0.100

OS

[x] Windows 11

Frontend

[x] Visual Studio Code

Screenshots
If applicable, add screenshots to help explain your problem.

Installing System.Threading.Tasks.Dataflow (in first code block) does not show as installed but does not fail execution.

Given the following code block after the install codeblock

#r "nuget: Throw"

using System.Threading.Tasks;
using System.Threading.Tasks.Dataflow;
using Throw;

public record FastParallelForEachSettings(int EnumerationDegreeOfParallelism, int ActionDegreeOfParallelism);

async Task FastForEachAsync<TIn>(
    IAsyncEnumerable<TIn> asyncEnumerable,
    Func<TIn, Task> action,
    int degreeOfParallelismForProcessing,
    CancellationToken cancellationToken
)
{
    degreeOfParallelismForProcessing.Throw("Degree of parallelism must be greater than 0").IfLessThan(1);
    var actionBlock = new ActionBlock<TIn>(
        action,
        new ExecutionDataflowBlockOptions()
        {
            CancellationToken = cancellationToken,
            MaxDegreeOfParallelism = degreeOfParallelismForProcessing
        }
    );
    await foreach (var item in asyncEnumerable.WithCancellation(cancellationToken))
    {
        actionBlock.Post(item);
    }
    actionBlock.Complete();
    await actionBlock.Completion.WaitAsync(cancellationToken);
}

Output:

Did you try it without the nuget: prefix?
#r "System.Threading.Tasks.Dataflow"

I was facing a similar issue with using System.ComponentModel.DataAnnotations and #r "System.ComponentModel.Annotations" did the trick.
The docs say:

In C# Interactive, the #r compiler directive adds a reference to a specified assembly, e.g. #r "/path/to/a.dll", or system assembly, e.g. #r "System.Net.Http.Json.dll".


Updated case of RpcMetadata Properties

Updated case of RpcMetadata Properties to lower case

@fabiocav / @pragnagopa Can we add this before Narens's PR goes in? Would this be a breaking change?


sqlite3.OperationalError:

Hi I,
was trying to use the pylandsat for the first time.
When I try to search in the catalogue, I get the error:

Traceback (most recent call last):
File "C:\Program Files\JetBrains\PyCharm Community Edition 2020.1.2\plugins\python-ce\helpers\pydev\pydevd.py", line 1448, in _exec
pydev_imports.execfile(file, globals, locals)  # execute the script
File "C:\Program Files\JetBrains\PyCharm Community Edition 2020.1.2\plugins\python-ce\helpers\pydev_pydev_imps_pydev_execfile.py", line 18, in execfile
exec(compile(contents+"\n", file, 'exec'), glob, loc)
File "E:/___SVN/COP4EE-2/Landcover/Code/gis/Python/landsatdownloader2.py", line 35, in
sensors=['LC08', ]
File "E:___SVN\COP4EE-2\Landcover\Code\venv\lib\site-packages\pylandsat\catalog.py", line 99, in search
params=(geom, begin, end, maxcloud, sensors, tiers, geom))
File "E:___SVN\COP4EE-2\Landcover\Code\venv\lib\site-packages\pylandsat\database.py", line 67, in query
conn = self.connect()
File "E:___SVN\COP4EE-2\Landcover\Code\venv\lib\site-packages\pylandsat\database.py", line 62, in connect
conn.execute("SELECT load_extension('mod_spatialite');")
sqlite3.OperationalError: Eine DLL-Initialisierungsroutine ist fehlgeschlagen.

(a DLL-intialisationroutine failed)
The code: I used for the example is:
from datetime import datetime
from calendar import monthrange
import argparse

from pylandsat import Catalog, Product
from pathlib import Path
import geopandas as gpd

parser = argparse.ArgumentParser("Downloading Landsat 8 for the given COP2EE-2 bounding box from 2018/10/01"
                                 " to 2019/03/30.")
parser.add_argument("vector_path", type=str, help="path to the vector file, for the shape to find the data.")
parser.add_argument("save_path", type=str, help="General save path for Landsat.")
args = parser.parse_args()

observation_period = [(2019, 10), (2019, 11), (2020, 2), (2020, 4), (2020, 5), (2020, 7)]
geom = gpd.read_file(args.vector_path).to_crs(4326).geometry.values[0]

catalog = Catalog()

for year, month in observation_period:
    # Request
    begin = datetime(year, month, 1)
    end = datetime(year, month, monthrange(year, month)[1])

    scenes = catalog.search(
        begin=begin,
        end=end,
        geom=geom,
        sensors=['LC08', ]
    )
    scenes = scenes.sort_values(by='cloud_cover', ascending=True)
    product_id = scenes.index[0]

The vector file includes an Polygon.
I am using Python 3.7 with virtualenv on windows10.

I encountered the same issue when trying with the search command in command line.

You need to install a library with your systems package manager. For Ubuntu it was:
sudo apt update
sudo apt upgrade
sudo apt install libsqlite3-mod-spatialite


f1->main

mosquitto_pub -t cdac/desd -h <IP_ADDRESS> -p 1883 -m "hello" -d
mosquitto_sub -t cdac/desd -h <IP_ADDRESS> -p 1883 -d
On Sat, Dec 28, 2024 at 12:33 PM DESDBatchAug24 @.***>
wrote:

@.**** commented on this pull request.
Nit liha re code
—
Reply to this email directly, view it on GitHub
https://github.com/Vakratund100/Test/pull/1#pullrequestreview-2524628512,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BLM6SH5PZIRZIVDCPH2R5WT2HZEKRAVCNFSM6AAAAABUJRBKN6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDKMRUGYZDQNJRGI
.
You are receiving this because you authored the thread.Message ID:
@.***>


fix: LSDV-3012: Syncable with new simple approach

New Syncable mixin to provide new and very simple and nice approach:

don't send event back
sync the whole state (time, speed, playing)
group tags in syncing groups
lock current sync window for any back-stream events
sync is pluggable thing, tag should work without sync methods (Audio is still tied with Sync)

Volume intentionally not synced because it can be used to control current audible content (or listen all of them if required). The only possible sync can be to mute all other tags except the one that triggered event.
Things left:

[ ] sync speed
[ ] sync play when audio restarted after reaching the end
[ ] untie Audio to trigger internal methods internally
[ ] sync time shortly after play? can be helpful for overloaded browser

PR fulfills these requirements

[x] Commit message(s) and PR title follows the format [fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made ex. fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
[ ] Tests for the changes have been added/updated (for bug fixes/features)
[x] Docs have been added/updated (for bug fixes/features)
[x] Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
[ ] Self-reviewed and ran all changes on a local instance (for bug fixes/features)

Change has impacts in these area(s)
(check all that apply)

[x] Product design
[x] Frontend

Describe the reason for change
(link to issue, supportive screenshots etc.)
What does this fix?
(if this is a bug fix)
What is the new behavior?
(if this is a breaking or feature change)
What is the current behavior?
(if this is a breaking or feature change)
What libraries were added/updated?
(list all with version changes)
Does this change affect performance?
(if so describe the impacts positive or negative)
Does this change affect security?
(if so describe the impacts positive or negative)
What alternative approaches were there?
(briefly list any if applicable)
What feature flags were used to cover this change?
(briefly list any if applicable)
Does this PR introduce a breaking change?
(check only one)

[ ] Yes, and covered entirely by feature flag(s)
[ ] Yes, and covered partially by feature flag(s)
[x] No
[ ] Not sure (briefly explain the situation below)

What level of testing was included in the change?
(check all that apply)

[x] e2e
[ ] integration
[ ] unit

Which logical domain(s) does this change affect?
(for bug fixes/features, be as precise as possible. ex. Authentication, Annotation History, Review Stream etc.)

To fix "Audio Read only Regions" test, as I understand we need to teach AtAudioView to work with Audio V3 component. I can suggest to use something like
async moveRegion(regionId, offset = 30) {
    const regionPosition = await I.executeScript(({ regionId, stageBbox }) => {
      const region = Htx.annotationStore.selected.regions.find(r => r.cleanId === regionId);

      if (window.APP_SETTINGS?.feature_flags?.ff_front_dev_2715_audio_3_280722_short === true) {
        const wsRegion = region._ws_region;

        if (!wsRegion.inViewport) {
          return null;
        }
        const { height } = wsRegion.visualizer;

        return {
          x: (wsRegion.xStart + wsRegion.xEnd) / 2 + stageBbox.x,
          y: height / 2 + stageBbox.y,
        };
      } else {
        const element = region.getRegionElement();
        const rect = element.getBoundingClientRect();

        return {
          x: rect.x + rect.width / 2,
          y: rect.y + rect.height / 2,
        };
      }
    }, { regionId, stageBbox: this._stageBbox });

    if (!regionPosition) return;

    return I.dragAndDropMouse(regionPosition, {
      x: regionPosition.x + offset,
      y: regionPosition.y,
    });
  },

instead of this https://github.com/heartexlabs/label-studio-frontend/blob/56b98f917a2101272a7e0fb5012f3e1545b51130/e2e/fragments/AtAudioView.js#L115-L131
It's not super accurate approach but it should work for now.
And after that we may need to correct this part
https://github.com/heartexlabs/label-studio-frontend/blob/56b98f917a2101272a7e0fb5012f3e1545b51130/e2e/fragments/AtAudioView.js#L101
with somthing like that
const _ws = Htx.annotationStore.selected.names.get(tagName)._ws;
let wrapper;

if (window.APP_SETTINGS?.feature_flags?.ff_front_dev_2715_audio_3_280722_short === true) {
  wrapper = _ws.visualizer.wrapper;
} else {
  wrapper = _ws.container;
}

But i'm still not sure about these magic numbers.
https://github.com/heartexlabs/label-studio-frontend/blob/56b98f917a2101272a7e0fb5012f3e1545b51130/e2e/tests/readonly-tests/readonly-results/audio-results-readonly.test.js#L67

Codecov Report
Patch coverage: 87.74% and project coverage change: +0.28 :tada:

Comparison is base (5eb91e6) 65.31% compared to head (cf36bda) 65.60%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1201      +/-   ##
==========================================
+ Coverage   65.31%   65.60%   +0.28%
==========================================
  Files         411      412       +1
  Lines       25534    25624      +90
  Branches     6585     6580       -5
==========================================
+ Hits        16678    16810     +132
+ Misses       8856     8814      -42

Impacted Files
Coverage Δ

src/env/development.js
0.00% <0.00%> (ø)

src/tags/object/Paragraphs/HtxParagraphs.js
78.60% <ø> (ø)

src/tags/object/Paragraphs/index.js
100.00% <ø> (ø)

src/tags/object/AudioNext/model.js
33.84% <38.46%> (-2.68%)
:arrow_down:

src/lib/AudioUltra/Waveform.ts
74.07% <66.66%> (+2.09%)
:arrow_up:

src/regions/BrushRegion.js
83.39% <71.42%> (+2.07%)
:arrow_up:

src/lib/AudioUltra/Controls/Player.ts
91.78% <74.28%> (+3.74%)
:arrow_up:

src/mixins/Syncable.ts
89.58% <89.58%> (ø)

src/tags/object/AudioUltra/model.js
83.50% <90.69%> (+5.96%)
:arrow_up:

src/utils/canvas.js
60.78% <92.15%> (+5.69%)
:arrow_up:

... and 11 more

... and 18 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[Auto release debug]  Add prompt statement

When there are multiple folders under the same path, a prompt statement is added to facilitate the release of packages

test link:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1373650&view=results
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1373649&view=results

/check-enforcer override


Tests around configuration modifications

More tests added around backward compatibility. Backward compatibility now more tolerant to partial configuration and no longer requires the ~/.hmrc/release.conf file.
Note: The release script no longer needs to be run from the release repo, it can be called from anywhere (and hence symlinked into /usr/bin or the src/universal/bin dir added to your path etc.)

Thanks we will look at this soon

A lot of code is shared between this PR and the previous one which was reverted.
I'd like to know what the objection was the first time around

Tested with legacy configuration method and new. Works fine.


Dependency checker

Attempt to fix the depcheck tool, that can be used to report or fix the unused or misplaced dependencies in the repo.

I'll look more deeply later, but one high level question is: could this be a policy instead? fluid-build doesn't seem like the right place to put this. Instead, you could factor out the check code needed into build-cli alongside the other repo policies.
Also consider adding config options. That way we can configure and document things in one central place. Especially if there are hardcoded lists of expectations, for example.

Worth a look if you haven't seen it: https://www.npmjs.com/package/depcheck


rename AccessToken to Secret and expand it's usage

This does 3 things:

Renames AccessToken to Secret
Prevents Debug of the AccessToken from actually showing the secret
Starts expanding the use of Secret to other areas, such as client certificates

I'm open to this. Is there precedence in any other Azure SDKs or libraries? .NET uses Azure.Core.AccessToken. https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/core/Azure.Core/src/AccessToken.cs

I don't know about wrapping secrets in a fashion like we've done.
As it relates to your link, the AccessToken implementation used in DotNet is what we call TokenResponse, as it includes both the token and an expiration date.  It's my intention to rename TokenResponse to AccessToken once this PR lands, as that should impact different places.


[flutter_tools] register service worker after first frame event

Description
Registering the service worker immediately after the documented has loaded may cause SW initialization to compete with framework initialization. It was recommended to us that we defer the service worker setup until after the framework is done with setup, which should be sometime after the first frame.
To implement this, I augmented the binding setup to dispatch an event on the document after the binding has initialized. I don't see any obvious risks with this setup.
Fixes https://github.com/flutter/flutter/issues/66066

I think my changes to the binding should be reasonable... :)

Friendly ping @ditman :)


Update metadata

> go run main.go
2021/08/03 13:40:56 Complete Updating meta databases!
2021/08/03 13:40:56 Building map for: disposable.txt
2021/08/03 13:40:56 Read 115340 mappings in disposable.txt
Writing new ../../metadata_disposable.go
2021/08/03 13:40:56 Building map for: free.txt
2021/08/03 13:40:56 Read 4471 mappings in free.txt
Writing new ../../metadata_free.go
2021/08/03 13:40:56 Building map for: role.txt
2021/08/03 13:40:56 Read 888 mappings in role.txt

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.7%) to 83.503%

Files with Coverage Reduction
New Missed Lines
%

smtp.go
2
71.77%

verifier.go
2
76.47%

Totals

Change from base Build<PHONE_NUMBER>:
-0.7%

Covered Lines:
491

Relevant Lines:
588

💛  - Coveralls


Compressed drawio file shows mxfile/compressed="false"

I know this was fixed somewhen between 20.3.7 and currently online version 20.4.1 and with it the compressed attribute was removed altogether. Is the compressed attribute coming back once it works?

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
Compressed drawio file shows mxfile/compressed="false"
in other words: compressed-Attribute falsely states no compression when compression is in fact active
To Reproduce
Steps to reproduce the behavior:

Go to File=>Export As=>XML...
Leave "compressed" checkbox ticked (ticked by default)
Click export
Open the exported, compressed drawio.xml file in a text editor (e.g. Notepad++)
Observe the bug described above

Expected behavior
Compressed drawio file should show mxfile/compressed="true"
Screenshots

draw.io version (In the Help->About menu of the draw.io editor):

diagrams.net 20.3.0

Desktop (please complete the following information):

OS: Windows 10 Enterprise 21H2 (OS build 19044.1466)
Browser: Chrome Version 106.0.5249.119 (Official Build) (64-bit)

Literally nobody seems to want compression, so we'll default to uncompressed in the next release.


[FEATURE] Vertical lines color black in light mode

Is this a unique feature?

[X] I have checked "open" AND "closed" issues and this is not a duplicate

Is your feature request related to a problem/unavailable functionality? Please describe.
It's an enhancement
Proposed Solution
In light mode the vertical lines are not visible, I want to fix this by making the colour of the vertical lines black.
Kindly assign me this issue.
Screenshots

Do you want to work on this issue?
Yes
If you want to work on this issue...
I'll change the color on light mode by changing the CSS
Edit:
In light mode use the colour of the font.  Changes can be made in the Tailwind classes pages/index.js

I am ready to work on this issue, please assign it to me

I am ready to work on this issue, please assign it to me

@Harshil-Desai  Please look at the assignee's section before asking for the issue to be assigned. I would recommend you to read our contributing guidelines https://github.com/EddieHubCommunity/BioDrop/blob/main/CONTRIBUTING.md


Linux support requires improvements

Depends on https://github.com/Andersen27/Photino.Blazor.CustomWindow/issues/3

CustomWindow problems was solved, there are problems with the docking itself.
The floating panel does not display the content and the application freezes.


Base SDK has reference to System.Diagnostics.StackTrace, Version=<IP_ADDRESS>

The base SDK has a reference to System.Diagnostics.StackTrace, Version=<IP_ADDRESS>, which breaks the .NET Core SDK from referencing the latest build candidate for 2.4.0-beta1.

What version should be referenced instead?


Used github action for releases in our java template was marked as unmaintained

https://github.com/actions/create-release/issues/119
affected: https://github.com/baloise/repository-template-java/blob/master/.github/workflows/release.yml

As far as I've read by now, a separate action for releases might by obsolete since GitHub cli is installed and available in actions. Thus the gh release create command can be used.
I've successfully tested this approach in private repo and adopted it here: https://github.com/baloise-incubator/codeql2sonar-maven-plugin/blob/main/.github/workflows/release.yml

[ ] review
[ ] decide if approach should be adopted

As decided in todays bi-weekly, we will adopt suggested approach


Markers are bugged on the map (images become grayish/black)

Hi devs, I'm using your APIs to make a simple mock game.
I've encountered that the half of the time when I'm using the map, the markers are bugged. They become greyish with no reason whatsoever. While zooming in/out the glitch might appear or disappear.
I've tried the app only on the Android Studio built-in emulator (Pixel 3 API 29) on multiple PCs.
Here all the markers are bugged:

Here only some of them are bugged:

Here's an example of how should the map look with no bugged markers:

If you need it, here's the MainActivity code: https://gist.github.com/vladoski/b98aee5c664fd9e7ede4faa084f13842
Thanks for your cooperation!

I've found that this bug doesn't happen when I use my OnePlus 6 instead of the Pixel 3 emulator.

I'm glad that it's working fine for you on your physical device. There are known issues with displaying some icon colors on an emulator. Closing this as it's a duplicate of https://github.com/mapbox/mapbox-gl-native/issues/10829. Thanks for using Mapbox.


One CPU fully occupied by Datadog when device offline

We're using the Datadog android java SDK to collect both traces and logs on an android device. The device may be offline for an extended period, which means logs/traces cannot be uploaded but are stored on device. After a while in this state, the datadog agent is fully occupying 1 CPU. We have reproduced the issue both on device and using the android emulator. We have tested both version 1.9.0 and 1.19.2 and the issue persists. We're using the Datadog-Timber integration for log/trace capturing.
Steps to reproduce the issue:

Create an android instrumented test that loops over a log statement say 100k times.
Start the android emulator and enable airplane mode on the emulated device.
Run the test and observe the folder on device (using e.g. adb shell) where the cached files are stored (e.g. /data/user/0/<myapplication>/cache/datadog-.../logs-v2
When the number of cached files reaches ~200, stop the test.
Create another instrumented test that logs in a loop. For each iteration of the loop, sleep 10ms (emulating 100 log entries/second).
Run the second test and attach the profiler, e.g. android studio. One of the worker threads will occupy one CPU 100%. Breaking in the debugger indicates that the Datadog agent is using one of the worker threads to iterate over every stored file repeatedly, causing the high CPU usage.

Describe what you expected:
Running the same test with datadog enabled, emulating 100 log writes/second, occupies ~8% of one CPU when the device has network access. I'd expect no more CPU usage even if the device is offline.
Additional context

Android OS version: 31
Emulator: Pixel 6 Pro
Datadog SDK version: 1.9.0, 1.19.2
Versions of any other relevant dependencies (OkHttp, …): Timber 5.0.1, okhttp 4.9.3
Proguard configuration: N/A
Gradle Plugins: N/A

Hi and thanks for getting back to me! You're of course right, my example is doing some excessive logging but it's mostly a quick way to demonstrate the problem. Our real logging rate is also somewhat excessive but not like above. Still, because the device can be offline for hours and hours the problem occurs eventually.  Thanks for details!
The issue comes from the fact that syscall done by File.isFile is quite expensive, and regex check on the 200+ files also adds up. The picture with CPU consumption will be the same even if there is network, the problem is that there are many batch files to go through in the internal event write logic (so that if write frequency dominates over upload capabilities and the overall file queue is big - it will be the same).
We can probably optimize this hot path by throwing in some cache to avoid repetitive syscalls/regex matching for the known entities, we will try to apply the fix soon.

Hi! Any news on this one? Anything I can help with?

Hello @torbjorn-humane! Sorry, for the delay. Can you please help us to estimate the priority of this issue, is it a blocker for you to adopt our SDK?

Hi, thanks for getting back to me! Yeah, for the moment we've disabled the datadog agent completely across all our devices so not to disrupt users, but we're taking a hit on the debuggability for sure. A fix would be very much appreciated!

Hello @torbjorn-humane! We've made a quick improvement in https://github.com/DataDog/dd-sdk-android/pull/1506, hope it will help in your scenario.
Ideally we should change the logic of working with files to address your scenario better, but it will be a bigger change which goes outside simple patch release. We have the necessary task in our backlog, but I cannot give you any estimates.
We will probably release a new patch version 1.19.3 early next week with the change I've mentioned.
Worth to add that since the issue is coming from the number of files stored in the filesystem, you can also try to change batch size option to use bigger batch size (setBatchSize) in the SDK configuration in order to reduce the average number of batch files.
Thanks for your feedback with such scenario, we are always happy to hear how SDK behaves in "non-optimistic" cases. Can you please also share a bit more details on the application usage? Normally when application is very active interacting with SDK and may have no network connection for a long time, it is probably some PoS/Kiosk which is on external power source, so even if CPU usage is higher than expected, it doesn't cause a big issue.

Thank you @0xnm, this is very much appreciated! I will pick up the new release as soon as it's available and verify on our end before upgrading our software.
I unfortunately can't share anything about our use case that isn't already public, but stay tuned. :)

Hello @torbjorn-humane! We've released version 1.19.3 with the optimization for your use-case included. Please check it out and let us know if it unblocks you.
Meanwhile, if you are in the process of the initial Datadog SDK adoption, you may be interested in our first beta of SDK v2 (note that artifact names are different now), which gives more granularity in comparison with SDK v1 (say if you need only Logs, you may now only import logs module without the overhead of RUM and Trace classes in memory). This beta release includes the optimization mentioned above as well.

Hello @torbjorn-humane! I'm closing this issue due to inactivity, but if you still experience the problem feel free to re-open it.


feat: use pearl-chain-time in journey-summary

Preflight Checklist

[x] I have read the Contributing Guidelines for this project.
[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the pull request tracker for a Pull Request (PR) that matches the one I want to submit, without success.

Issue
This PR Closes #
Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)

See Review Guidelines for more information what is checked during review process.
Changes
Changes in this pull request:

Browsers
I tested the build on the following browsers:

[x] Firefox Desktop
[ ] Chrome Desktop
[ ] Edge Desktop
[ ] Safari Desktop
[ ] Chrome Mobile
[ ] Safari Mobile

Screen readers
I tested the build on the following browsers:

[ ] JAWS Firefox Desktop
[ ] JAWS Chrome Desktop
[ ] NVDA Firefox Desktop
[ ] NVDA Chrome Desktop
[ ] VoiceOver Safari Desktop
[ ] VoiceOver Chrome Desktop
[ ] VoiceOver Safari Mobile
[ ] Android Accessibility Suite Chrome Mobile

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

Codecov Report

Merging #1446 (88930bf) into master (ab917b0) will increase coverage by 3.42%.
The diff coverage is 63.39%.

@@            Coverage Diff             @@
##           master    #1446      +/-   ##
==========================================
+ Coverage   54.85%   58.27%   +3.42%
==========================================
  Files          49       63      +14
  Lines        1659     2313     +654
  Branches      406      618     +212
==========================================
+ Hits          910     1348     +438
- Misses        671      876     +205
- Partials       78       89      +11

Impacted Files
Coverage Δ

src/components/sbb-clock/sbb-clock.tsx
0.00% <0.00%> (ø)

src/components/sbb-logo/sbb-logo.tsx
0.00% <0.00%> (ø)

src/components/sbb-pearl-chain/sbb-pearl-chain.tsx
67.74% <ø> (-3.69%)
:arrow_down:

src/components/sbb-section/sbb-section.tsx
85.00% <ø> (ø)

src/components/sbb-signet/sbb-signet.tsx
0.00% <ø> (ø)

...mponents/sbb-slot-component/sbb-slot-component.tsx
100.00% <ø> (ø)

src/components/sbb-stack/sbb-stack.tsx
76.66% <ø> (ø)

src/components/sbb-tab-amount/sbb-tab-amount.tsx
100.00% <ø> (ø)

src/components/sbb-tab-group/sbb-tab-group.tsx
76.19% <ø> (ø)

src/components/sbb-tab-title/sbb-tab-title.tsx
100.00% <ø> (ø)

... and 50 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


google-common [bug]: Gemini response with no parts triggers error

Privileged issue

[X] I am a LangChain maintainer, or was asked directly by a LangChain maintainer to create an issue here.

Issue Content
I am occasionally getting the following error during processing:
>  /Users/prisoner/Documents/project/functions/node_modules/@langchain/google-common/dist/utils/gemini.cjs:504
>                  generationInfo: ret[ret.length - 1].generationInfo,
>                                                      ^
>
>  TypeError: Cannot read properties of undefined (reading 'generationInfo')
>      at responseToChatGenerations (/Users/prisoner/Documents/project/functions/node_modules/@langchain/google-common/dist/utils/gemini.cjs:504:53)
>      at responseToChatResult (/Users/prisoner/Documents/projectfunctions/node_modules/@langchain/google-common/dist/utils/gemini.cjs:562:25)
>      at safeResponseTo (/Users/prisoner/Documents/project/functions/node_modules/@langchain/google-common/dist/utils/gemini.cjs:374:25)
>      at safeResponseToChatResult (/Users/prisoner/Documents/projectfunctions/node_modules/@langchain/google-common/dist/utils/gemini.cjs:570:12)
>      at ChatGoogle._generate (/Users/prisoner/Documents/project/functions/node_modules/@langchain/google-common/dist/chat_models.cjs:270:62)

Looking at the code, I'm guessing that the earlier call
const parts = responseToParts(response);

is returning an empty array, which is legitimate, but usually only happens when the safety handler would be triggered, so the safety handler should have caught it first.
Several things need to be addressed:

ret[ret.length - 1].generationInfo should have a optional property accessor

We should probably just short circuit if no parts are returned

Evaluate the DefaultSafetyHandler to see if other finish reasons should trigger a problem. (Perhaps as part of another issue)

Platform: Vertex AI
Models:

gemini-1.5-pro-001
gemini-1.5-flex-001

@jacoblee93 and @bracesproul - Please assign this to me

The DefaultSafetyHandler appears to be working as designed.
The problem seems to be that https://github.com/langchain-ai/langchainjs/blame/e8da74b02822b197fe12d75a83e9eb32fbc0816a/libs/langchain-google-common/src/utils/gemini.ts#L487 assumes that the response can still be converted safely, even with missing fields.
The bug in the optional property accessor is preventing this. Fixing this is the best solution.
It might also make sense to have DefaultSafetyHandler check for missing parts as well, since that can't be a good thing, and clean it up before evaluating or throwing an exception.
Workaround is to use a MessageGeminiSafetyHandler which will return valid response data.
If we want an exception to be thrown, it gets messier.

Hi @afirstenberg,
The condition ret.every((item) => typeof item.message.content === "string") currently evaluates to true even when ret is empty. To address this, we could add a check for ret.length > 0 alongside the existing condition.
This issue is impacting our production service, and we've implemented a retry logic as a temporary workaround. Could you please provide an update on any progress?
Thank you.

we've implemented a retry logic as a temporary workaround.

Just to be clear - even when this is fixed, you may need to implement retry logic. (Or handle this elsehow.)
All the cases I've seen of this are when Gemini is triggering a SAFETY issue. So even when this is fixed - a GoogleAISafetyError will be thrown by default.
If you just want it to return a message such as "I'm sorry, but I can't talk about that." when a SAFETY issue is triggered, then you can use the MessageGeminiSafetyHandler when creating your model. This creates a synthetic part and works around the issue. You can do this with something like this (but I haven't tested this specific code):
  const safetyHandler = new MessageGeminiSafetyHander({
    msg: "I'm sorry, but I can't talk about that.",
  });
  const model = new ChatGoogle({
    safetyHandler,
  });

Could you please provide an update on any progress?

As for this part - @jacoblee93, can we get the conditional test that @pksharmapokhrel outlined in place at https://github.com/langchain-ai/langchainjs/blame/96bba4bafeb67e79cbf266ed40ca93bec96d166c/libs/langchain-google-common/src/utils/gemini.ts#L598 ?


HAPROXY_0_AUTH does not route properly

If I enable authentication proxy via the HAPROXY_0_AUTHfor a service, then that service is not placed into the vhost map as reported by /_haproxy_getvhostmap.
Although there is a routing rule in the haproxy.cfg file for the service it doesn't see to actually route and results in an unavoidable 503 error.
Services without the label are registered properly and route correctly.

Have you set the realm?  https://github.com/mesosphere/marathon-lb/wiki/HTTP-Basic-Auth

I am pretty sure I did include a realm. This was a while ago and I've since modified the app configuration to use an auth proxy, so I can't just recreate the setup instantly.
I'm wondering if it had something to do with conflicting with the letsencrypt-dcos service that I'm using?


Add pre commit hooks

Pre-commit hooks help developers to automate part of the workflow.

pre-commit.ci autofix


feat(migrate): remove nativeTypes flag

Looks good! Please also add compatibility code as we have for other feature flags here: https://github.com/prisma/prisma/blob/ced92179fa605b0df9a279a48d55f2047271fb50/src/packages/sdk/src/engineCommands.ts#L75
So that it's not crashing for people who still use the feature flag, but just a warning.

Good point @timsuchanek added in https://github.com/prisma/prisma/pull/5446/commits/3bddead9f5106c652a606420f7852fbdde1a6027


Cannot find attention functions

Hi, i am trying to implement attention rnn and want to use https://www.tensorflow.org/api_docs/python/tf/contrib/seq2seq/attention_decoder_fn_inference and other attention methods from attention_decoder_fn.py . However i cannot find it here on github ...
When this functionality will be available?
Why is it in api web page but not in the repo?

This function exists in the 1.0 branch: https://github.com/tensorflow/tensorflow/blob/r1.0/tensorflow/contrib/seq2seq/python/ops/attention_decoder_fn.py#L134
However, it was recently deleted from master: https://github.com/tensorflow/tensorflow/commit/d46937f3684d3be2285f7401c2f471f542d147c2
I suggest either using 1.0, or looking at the code currently in master: https://github.com/tensorflow/tensorflow/tree/master/tensorflow/contrib/seq2seq/python/ops
If you have further questions about using seq2seq, please ask on StackOverflow (we try to keep Github issues focused on bugs and feature requests).


Wasm: Extract response protocol in the onResponseHeaders function

Description
We cannot seem to find an approach to extract the HTTP response protocol in the onResponseHeaders function. It seems there is no corresponding attribute that has this information. It also appears that the stream object itself is not accessible through the proxy wasm API which is there in the Lua API.
Observations / Areas Explored

In the request flow, the onRequestHeaders function does have an attribute called request protocol which is accessible through the getValue function call. However, there does not exist a response protocol attribute that can be accessed in onResponseHeaders which has similar information.
Some attributes such as response code are not accessible in the onResponseHeaders function but available in others functions such as onResponseBody or onLog.

Questions

Is there an approach to extract the response protocol in the onResponseHeaders function?
If an option does not exist through the API, would it be possible using a foreign function interface instead?

@PiotrSikora can you help out with this one? Thanks.

@kyessenov is the expert of all properties exposed in Wasm.

Request and response protocol are usually the same, since it is negotiated in the codec for two parties to be able to understand each other. Is that not the case for you?

@kyessenov I thought the request protocol is actually the protocol from the incoming client connecting to Envoy. Is this not the case? If the Wasm filter needs to be attached before the main envoy.router filter then I believe we do not have the upstream cluster information and it's corresponding protocol here in the onRequest flow.
This is the reason which I was hoping the response protocol would have this information in the onResponse flow as that is part of the connection between Envoy and the upstream. Are there any properties here that contain this information?

@mcieplak It makes sense to record the upstream protocol. I'm not sure if it's correct to call it response protocol, since it would be strange to have request and response have mismatched protocols (e.g. http/1.1 and h2). Maybe upstream.protocol?

@kyessenov I agree that response protocol sounds a little bit confusing as I meant the protocol in terms of the upstream. It makes sense to call it upstream protocol instead. Is this attribute already available or is this something that will need to be added?


Make a decorator for arg-parsing

The current argument parsing logic is extremely verbose and highly repetitious.
Would like to make this a decorator for command plugins to make this much, much more seamless.

Update: working on this still... Making some awesome progress...

#40 Work in progress around this issue. Still laying the foundation for it.

Now migrating commands over to new decorators.  See #40 for details.

Fixed in #40.


release notes for 1.1.0-M1

will be merged when vote passes

The vote passed so I need to get the docs updated as part of the release.


Using ESPHome proxy?

Hi @mduran80 ,
What do you think about the possibility of using ESPHome bluetooth_proxy for communicating instead of a usb dongle?

It will not work, I already asked on the HA bluetooth dev channel. The best
chance is to use Raspberry Pi Zero or similar with pymadoka + MQTT.
El El dom, 1 ene 2023 a las 15:45, BeFygo @.***>
escribió:

Hi @mduran80 https://github.com/mduran80 ,
What do you think about the possibility of using ESPHome bluetooth_proxy
for communicating instead of a usb dongle?
—
Reply to this email directly, view it on GitHub
https://github.com/mduran80/daikin_madoka/issues/27, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFK3CT53IYXN5FBZCG62P2LWQGJ7ZANCNFSM6AAAAAATOEYS3M
.
You are receiving this because you were mentioned.Message ID:
@.***>

Today I have been fiddling with ESPHome proxy and HA bluetooth (and BLE) tracking.
Suddenly madoka cannot connect Through the USB dongle because ESPHome keeps overruling the dongle and connects to the daikin device.
Offcourse several errors occure without the propper 'pairing code' procedure.


Track battery % using consumed mAh instead of voltage.

This PR introduces the concept of battery % (SOC) tracking using mAh instead of a voltage table.
The new system tracks SOC using both voltage and mAh in parallel, and only uses mAh if the following conditions are true

The user has set a battery capacity > 0 in the settings
The SOC as determined by voltage is > 15% (this prevents sudden nosedives at low voltage if the mAh is misconfigured or bugged).

It converts from mAh % remaining to watt hour % remaining using a set formula derived from the chemical properties of LiPo batteries.  Namely that the voltage goes from 4.2V->2.8V.  I know the maintainers are not a fan of "magic formulas", but this is a very simple square polynomial that is not an approximation, but rather an exact derivation.  The only assumption made is that voltage decay is linear (which is obviously not quite true).  However since everyone uses different cells, linear decay is the best choice.
Also adds a new (hidden) diagnostics page that displays more internal variables.  Useful for developer debugging and visibility.
Known issues:

I expect weird SOC jumps near the 15% cutover.  Need to add a fuzzy cutover

@lolwheel sorry for the delay in response.  Absolutely feel free to build on top of it.  Though I would encourage the merging and release of a OWIE 2.0 with this as it is, since this changes nothing for users who don't enter a value, but those who want to beta test can access this feature before we measure on their behalf.
We can then follow up with 2.1 which determines capacity on your behalf.


yweather weather component failed since #10555

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.58.0.dev0
Python release (python3 --version):
3.4
Component/platform:
homeassistant.components.weather.yweather
Description of problem:
Stopped working since pr #10555
Expected:
yweather weather panel to show up.
Problem-relevant configuration.yaml entries and steps to reproduce:
weather:
- platform: yweather

Git checkout to d25f6767115feae4d5cab6de74af65884f720862 or later.
Activate yweather weather component in configuration.yaml.
yweather weather component does not work, traceback attached below.

Traceback (if applicable):
2017-11-16 19:53:43 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.4/asyncio/tasks.py", line 237, in _step
    result = next(coro)
  File "/home-assistant/homeassistant/helpers/entity_component.py", line 398, in async_process_entity
    new_entity, self, update_before_add=update_before_add
  File "/home-assistant/homeassistant/helpers/entity_component.py", line 246, in async_add_entity
    yield from entity.async_update_ha_state()
  File "/home-assistant/homeassistant/helpers/entity.py", line 216, in async_update_ha_state
    attr = self.state_attributes or {}
  File "/home-assistant/homeassistant/components/weather/__init__.py", line 112, in state_attributes
    self.precision),
  File "/home-assistant/homeassistant/helpers/temperature.py", line 21, in display_temp
    "Temperature is not a number: {}".format(temperature))
TypeError: Temperature is not a number: 25

Additional info:

Casting the temperature to int before returning the value seems to fix it.
Line 116 in homeassistant/components/weather/python.py:
def temperature(self):
    """Return the temperature."""
    return int(self._data.yahoo.Now['temp'])

Thank for figuring this out. :+1:


aNNM implementation problem: no matching matrix

In aNNM paper, it first construct QA matching matrix, then use value-shared weighting schema and question attention network to combine match scores.
But in line 38 of anmm.py: no found matching matrix construction step in "build" function, is this right? Thanks

You can find the computation of the QA matching matrix and bin sum(value-shared weights) in line 51 of https://github.com/faneshion/MatchZoo/blob/master/data/WikiQA/gen_binsum4anmm.py
curr_bin_sum = cal_binsum(d1_embed, d2_embed, qnum, bin_num)
You should run this script before the model training as a preprocessing step.


On Finish callback calls each time

How can we identify if file is successfully uploaded because on finish callback calls each time there is error or file is uploaded successfully.

I'm having the same problem here.
I'm trying to append some data to a file, but if the file does not exists, the lib just emits the "finish" event, without any parameter change (comparing with successful requests, when the file exists).
Then, after the finish, it emits an "error" event.
How am I supposed to know when it was successful?

Looking at the code, I managed to resolve this by adding a parameter on finish event. This parameter contains the error (if any).
Tried locally, it works great in all cases I tested.
I've opened a pull request.
https://github.com/harrisiirak/webhdfs/pull/16
Please check it, the tests are passing.

@siraj1044 @tiagopadua can you guys please re-test latest version 1.1.0. This one should resolve issues with missing events.


DSR P6 Akh Afah Boss% difference

Summary
Would it be possible for Cactbot to display the % or raw HP difference between Nidhogg/ Hraesvelgr in the lead up to each Akh Afah?
If Nidhogg were high, for instance, it could show
Nidhogg
2.4%
40.3k

and update as close to in real time as possible? I'm not actually sure if cactbot is capable of dynamically updating the text it displays, but I figured it'd be worth an ask!

Yeah, cactbot right now doesn't have any reasonable way to update text from a trigger.  It's something we could add, but I don't think it comes up very much.  It could print the % difference though just once or twice.
If you're using dalamud, you can also add https://raw.githubusercontent.com/Eternita-S/MyDalamudPlugins/main/pluginmaster.json as a custom repository and use the EnmityHp plugin.

Could warn on HP diff being too large with a 15s suppress or something I guess? But yeah right now there's no way to do update text dynamically after it's displayed.

I don't think this is something I'm planning on doing. This is better suited for a dalamud plugin.


Logs show strange characters (Heroku)

Bug Report
Current Behavior
The logs on heroku are not displayed properly.
Example

Possible Solution
Set LOG_FORMAT=json in heroku config vars as mentioned by @tcbyrd .
Probot v6.0.0

As we discussed in Slack, setting the LOG_FORMAT environment variable works fine but it'd be great if Probot did this by default in production environments. However, I know that some services (Now.sh for example) actually render the formatting, so I'm not sure how to balance that.

If we figure out a way to detect if the deployment is heroku environment then maybe we can use heroku-logger in that case and bunyan in other cases. Also heroku-logger internally uses logfmt so we can use that too

Hi @bkeepers – for us it'd be great if we could easily disable the color with an env var (that I assume would determine that color option for bunyan-format) – without having to switch to json. Would you be open to a PR along these lines?

@acrewdson you can already do that using the LOG_FORMAT=json environment variable.

@JasonEtco cool, thanks 👍 I'll give that PR a shot.

what about another env var instead:
LOG_COLORS=false

?


This usage of "errors.add()" is deprecated, please consult the docs for the new signature.

Versions

vee-validate: 2.0.#
vue: 2.#.#

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Demo Link
If applicable, add a minimal demo link to help explain your problem. You can use jsfiddle or Codesandbox.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

This is not the best approach but it works, code is in src/components/HelloWorld.vue, it adds the error to the bag when created the component an it is shown next to the input field

https://codesandbox.io/s/0xkp0n0n7l

I believe the warning makes it clear that you should use this format from now on since it will allow for future changes without breaking the current behavior.
I see you are using it correctly in your latest demo, what is the issue then?

Hi logaretm.
The error does not give you at least a link where to find the new way to use it, i found it on releases doc but not o API reference, where it is still showing the previous way to use it.
https://baianat.github.io/vee-validate/api/errorbag.html#api
I know it is still on beta but it is being updated when you make npm update, when i was working with the stable version, i installed using npm install vee-validate --save
https://github.com/baianat/vee-validate/releases/tag/2.1.0-beta.0

You are correct, I made sure it logs a link to the docs 10a9b14


URGENT: App hung at "Login" in desktop and online Teams

Just shows a Login box and when we try to login it just hangs there.
Have restarted the service.  Any ideas?

@tcrobbins4 , thank you for reporting this issue.
Please ensure that the base resource name and SharePoint site name are correct.

To do this, navigate to the Azure Resource Group, select 'Deployments', and then pick "Microsoft.Template".
Afterwards, click on 'Inputs' in the left pane to review the values you've entered.
The base resource name should not contain any uppercase letters, and the SharePoint site name should be just the site name, not the full URL. For example, if the site URL is https://example.sharepoint.com/sites/TEOCSite, the correct input would be 'TEOCSite'. If this is not the case, you will need to delete the resource group and start the process over.

Please verify and confirm.
https://github.com/OfficeDev/microsoft-teams-emergency-operations-center/wiki/Deployment-Guide#3-deploy-to-your-azure-subscription

I verified everything you noted and everything matches as it should. SharePoint site is reachable and no changes made to it that I know of.

@tcrobbins4 , thanks for confirming.
As you have confirmed that there are no changes from your side, please check if the client secret has expired. If it has, kindly follow the link provided below.
https://github.com/OfficeDev/microsoft-teams-emergency-operations-center/wiki/Troubleshooting#1-client-secret-expiry

That did it.  Thank you.  I will put a reminder on my calendar for next expiration :)


Druid Datasource- Error "Please define at least one metric for your table"

Hi,
I am using druid data source. When I click on the data source  i get error "Please define at least one metric for your table" .
But  the data source has the metrics defined. I checked it on druid at  "http://localhost:8082/druid/v2/datasources/datasource-name" i get following dimension and metrics details
{"dimensions":["sensortype","sensorunit","sensorid"],"metrics":["sensorvalue"]}
Please suggest
Thanks

Just an update, I am using Druid 0.9.0..

I think Caravel somehow failed at picking up your table definition. I'm guessing that if you edit your datasource on the Caravel side you won't see columns or metrics. One known issue is that we need at least one physical segment in order for us to pick up the column definitions.
We're still on Druid 0.8 at Airbnb and can't insure that 0.9.0 is fully compatible at the moment. If we want to support more version we'd need more sophisticated mocking in the unit tests that would represent things that the REST API for different versions of Druid may return.

@vinjadhav  did u ever go thru this ?
https://github.com/airbnb/caravel/issues/409

@bohemia420 yes i had gone though #409 .. my problem is not about the datasource.. but I am not able to see dimension and metric data in Caravel. @mistercrunch i do have 2 physical segment in my druid datasource

Hi, I am facing the same issue with druid-0.9.0, from #409 , will waiting for 24hours solve the issue? That is kind of not an acceptable solution for my case.

Ghanta solve the issue :-)..I switched to metaphase.i have been online
night and day on gitter channel for caravel...found a lot of hue and cry
all over.
On 27 May 2016 04:03, "Anindita Dey"<EMAIL_ADDRESS>wrote:

Hi, I am facing the same issue with druid-0.9.0, from #409
https://github.com/airbnb/caravel/issues/409 , will waiting for 24hours
solve the issue? That is kind of not an acceptable solution for my case.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/airbnb/caravel/issues/445#issuecomment-222014267, or mute
the thread
https://github.com/notifications/unsubscribe/AC_4dxGR6_hMm-AfsfsBp9XGyS9n3CbKks5qFh_HgaJpZM4IZXXF
.

Hi,
Caravel is a beautiful tool, but i got the same problem with druid-0.9.0, i can't show metrics.
Any patch is coming ?
Bohemia420 what was the issue ?
Thanks
FH

This should have been fixed in #526, closing.


[epic] Compensation Bot

Compensation Bot Epic
All PRs related to Compensation bot creation should be linked to this issue.
Spec for Compensation bot:
https://github.com/cscareerhub/megabot/blob/master/specs/comp.spec.md

Closing as will keep track of specific bot through labels


class with getter field throws FieldNotFoundException when using fromMap/fromJson

I read the generated code, and the SerializableMap's code
please allow me using the easiest way

fromMap method will try to assign getter with value, because it uses class mirror fields as the list, and class mirror fields contains getter field.
[]= method will throw FieldNotFoundException when unsupported key is given
So, fromMap will throw FieldNotFoundException, when getter field exists.

Could you show me your code?

Sorry, now I understand the error. By the moment you only have two opions:

You can add a setter so the filler always find it
You add @ignore annotation to the getter and it should be ignored by dson.

I think that the problem still persists. And using @ignore did not work for me. Getters like the following will still get serialized but it fails once object is being reconstructed.
@ignore
bool get isRunning => status == Task.RUNNING;

@ignore
bool get isPaused => status == Task.PAUSED;

@luisvt Can the throwfieldnotfoundexception be removed?

What do you mean?


Add PR title in assets/out output

assets/out doesn't have the title in its output, causing a new trigger from assets/check because this one does include the title, causing Concourse to consider it as a new version of the resource (though that doesn't happen all the time with all repositories for some unknown reason) and triggering a new build for the same revision as a result.
Adding the title in assets/out's output fixes the double-build issue for us.

this change will fix #15?

Looks like that's exactly what we were experiencing, so yeah it will fix it.

Thanks!

Thank you @peikk0 for fixing this issue! @idr0id is the fix already released?


SQL EXPLAIN badly needed (profiler or output)

There seems to be no option with codeigniter's active record to enable EXPLAIN before SQL statements. It would be nice having it in the profiler for example.
Joan

+1

It seems to me that this should be handled in the individual db drivers because each different database has different explain syntax. Instead of printing them in the in the profiler, I think an explain function should just return the results which would allow users to print/log/email or do whatever else they want to with them. Thoughts?

Should there be an explain() method in the DB_Driver, with optional parameters?
No expectation about what it returns, nor about the parameter interpretation ... just an expectation that each database driver will implement it in an appropriate fashion.

Yes, I think there should be an explain() method in the DB_Driver, but I'm not sure what optional parameters it would need. Shouldn't it just take in the query to be explained?

"No, I don't think we should have [put functionality name here]" - said no user ever. :)

If someone wants to have a go at this - submit a pull request. No use having this issue just sitting open though.


Various fixes

End of input symbol is now properly returned back to parser only when it should
Parser now has interface to manipulate input streams
No need to have \b at the beginning of fullword tokens since we are anchored at the start
html_report.h is now always included from pog.h

Codecov Report

Merging #6 into master will increase coverage by 0.22%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##           master       #6      +/-   ##
==========================================
+ Coverage   96.79%   97.01%   +0.22%
==========================================
  Files          26       26
  Lines         905      906       +1
==========================================
+ Hits          876      879       +3
+ Misses         29       27       -2

Impacted Files
Coverage Δ

include/pog/parser.h
97.01% <ø> (ø)
:arrow_up:

include/pog/token_builder.h
100% <100%> (ø)
:arrow_up:

include/pog/tokenizer.h
96.29% <80%> (+2.54%)
:arrow_up:

Continue to review full report at Codecov.

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