Windows-GNU build target unsupported

As mentioned briefly in #116, building with windows-gnu and injecting doesn't work.
Although I know it's only really officially supported for Windows via MSVC, it would still be nice to have it working by cross-compiling from a different platform.
Steps:

Install the x86_64-unknown-linux-gnu build target via rustup
Create a simple DLL using for say, the OpenGL 3 hooks
Build the DLL using cargo build --release --target x86_64-unknown-linux-gnu
Inject it into a sample application/game with OpenGL using Cheat Engine

Cheat Engine because it gives more verbose error details than most other programs

Watch it fail with an error where it fails to get something along the lines of "user profile directory", which isn't directly referenced anywhere in hudhook, but it is being triggered somewhere or by something else that's making it break

Using MSVC would obviously be the most ideal solution, not just because of this issue, but because of smaller build-sizes and other misc things. Although because it's a true hassle to get it even working on Linux, it doesn't want to compile hudhook nor anything other than some basic println Hello World applications.
Injecting a working DLL works just fine on Linux, so no issues there.

A couple questions:

Does this happen even with other injectors?
Does this happen with any OpenGL 3 program?

From the looks of it, it could either be something specific to CE, or something in the GNU runtime that expects something that isn't there. I have no experience with it so the best thing would be to attach with a debugger. I'll try to tinker with it soonish, but I'm a bit busy lately.

It's tied to GNU. I managed to work around the issue by using the MSVC toolchain on Linux via LLD.
If anyone else is encountering the same issue, I wrote a guide for it here.
Closing since I don't think there's much to do about it. The workaround works and working around this issue on the GNU toolchain will take weeks to solve.


Check cancellation token in isolatedDeclarations codefix

These are the main three entrypoints into the fixer. It's possible that there's some common hot function we could check instead (inferTypes?) but the call tree didn't make one super clear.

@typescript-bot cherry-pick this to release-5.5


concurrent cookbook uploads fail during upgrade process

A number of users (including @MattMencel who provided the data included in this report in chef/opscode-omnibus#490) have seen the upgrade process fail with the an error such as:
......
Chef Client finished, 32/386 resources updated in 42.656017287 seconds
opscode Reconfigured!
Ensuring Chef 12 server components are started
ok: run: bookshelf: (pid 24580) 0s
ok: run: nginx: (pid 24617) 1s
ok: run: oc_bifrost: (pid 24626) 0s
ok: run: oc_id: (pid 24657) 0s
ok: run: opscode-chef-mover: (pid 24662) 1s
ok: run: opscode-erchef: (pid 24689) 0s
ok: run: opscode-expander: (pid 24723) 1s
ok: run: opscode-expander-reindexer: (pid 24757) 0s
ok: run: opscode-solr4: (pid 24761) 0s
ok: run: postgresql: (pid 24389) 26s
ok: run: rabbitmq: (pid 23835) 39s
ok: run: redis_lb: (pid 24559) 6s
Writing knife-ec-backup config to /tmp/knife-ec-backup-config.rb
Uploading transformed open source Chef 11 server data to Chef 12 server
WARNING: WebUI not specified. Using /etc/opscode/webui_priv.pem
WARNING: Unable to detect Chef Server version.
Restoring users ...
Updating key for admin
Updating key for matt
Updating key for sensu
Restoring org wiu ...
Restoring the org admin data
Restoring the rest of the org
Updated /clients/chef-webui.json
Updated /clients/chef-server.json
Updated /clients/matt-wkstn.json
Created /cookbooks/iis-2.1.5
Created /cookbooks/passenger_apache2-2.1.0
Created /cookbooks/php-1.2.0
.....
Created /cookbooks/vmware-tools-0.1.2
Created /cookbooks/windows-1.10.0
Created /cookbooks/windows-1.30.0
Created /cookbooks/windows-1.30.2
Created /cookbooks/windows-1.32.0
Created /cookbooks/windows-1.31.0
Created /cookbooks/windows-1.32.3
Created /cookbooks/windows-1.34.0
Created /cookbooks/windows-1.33.1
Created /cookbooks/windows-1.34.2
ERROR: internal server error
Response: internal service error
Failed uploading transformed data to the Chef 12 server

Changing the upload concurrency to 1 often solves this problem (using the -t 1 argument to chef12-upgrade-upload).
The error from the failed upload can be found in the erchef logs:
2014-09-22 10:26:18.745 [error] {<<"method=PUT; path=/organizations/wiu/cookbooks/wiu-bedework/0.1.32; status=500; ">>,{error,{error,{case_clause,{conflict,<<"duplicate key value violates unique constraint \"cookbooks_org_id_name_key\"">>}},[{chef_sql,create_cookbook_version,1,[{file,"src/chef_sql.erl"},{line,605}]},{timer,tc,1,[{file,"timer.erl"},{line,165}]},{stats_hero,ctime,3,[{file,"src/stats_hero.erl"},{line,125}]},{chef_db,create_object,4,[{file,"src/chef_db.erl"},{line,721}]},{chef_wm_base,create_from_json,5,[{file,"src/chef_wm_base.erl"},{line,327}]},{chef_wm_cookbook_version,from_json,2,[{file,"src/chef_wm_cookbook_version.erl"},{line,143}]},{webmachine_resource,resource_call,3,[{file,"src/webmachine_resource.erl"},{line,186}]},{webmachine_resource,do,3,[{file,"src/webmachine_resource.erl"},{line,142}]}]}}}

Closing due to age. Please reopen if the issue persists.


perf: NetworWriter/Reader now uses blittable values

Test asmdef: allow unsafe
perf: NetworkWriter.WriteBlittable
perf: NetworkReader.ReadBlittable
breaking: NetworkWriter/Reader doesn't pack (u)int anymore

Closing it, from testing we weren't able to find any difference in benchmarks


Should we have a link to https://github.com/vega/vega/wiki/Expressions from readme.md?

Good call!


Improved Scroll Bar Behavior Better than Previous

Related Issue

Mention issue for which this pull request is a part of  ( Closes Issue Number < #391 >  )

Proposed Changes

Change 1 : Modified and Added Better Clean code for Improving Scrolling Behavior From Bottom to Top than Previous
Change 2 : These All Changes Only in Main.js File in Header Fixed to Top & Back to Top Sections of Codebase.

Additional Info

In Some Times, , Slightly Gap Happens on Scroll Behaviors in Website. That's why  I changed and Modified Code related to Header to Top and Bottom to Top Scroll Sections.

Checklist

[x] ✅ My code follows the code style of this project.
[x] 📝 My change requires a change to the documentation.
[ ] 🎀 I have updated the documentation accordingly.
[ ] 🌟 ed the repo

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Output Screenshots

Screenshot #1
Screenshot #2

Title goes here
Title goes here

Image goes here
Image goes here

website isn't opening in the deploy preview

Ok @agamjotsingh18 . How can I proceed next?


feat(checkbox): Add new component

Fixes #156

Codecov Report

Merging #296 into master will decrease coverage by 0.38%.
The diff coverage is 89.39%.

@@            Coverage Diff             @@
##           master     #296      +/-   ##
==========================================
- Coverage   97.47%   97.08%   -0.39%
==========================================
  Files          33       35       +2
  Lines        1306     1372      +66
  Branches      127      133       +6
==========================================
+ Hits         1273     1332      +59
- Misses         33       40       +7

Impacted Files
Coverage Δ

packages/checkbox/NativeControl.js
100% <100%> (ø)

packages/checkbox/index.js
88.52% <88.52%> (ø)

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 ce03925...3020648. Read the comment docs.

Also I noticed you're not implementing the forceLayout or the getNativeControl. I realize that getNativeControl is mainly for the objectPropertyDescriptors. Are we going to move it out of the foundation into the component in Web?

getNativeControl should be removed in #2684.
Let me double check if forceLayout/isAttachedToDOM is necessary in MDC Web


Enables the attributes SwiftLint rule

Replaces two Timer inits using selectors with inits using closures

For swift lint PRs please just work with @philium . Please don't include anybody else from the api team on the swift lint PRs.
cc @dg0yal @pgruenler

By dropping the Timer selector we can drop the attributes which removes the SwiftLint warning. I don't see the usefulness of splitting them into another PR at this point.

By dropping the Timer selector we can drop the attributes which removes the SwiftLint warning

I'm al for switching to a block-based API for creating timers, but that could have been done before (or after) enabling the linting rule. If done before, the function wouldn't get flagged by the linter. If done after, the attribute could simply be removed.

I don't see the usefulness of splitting them into another PR at this point.

The title of the PR is "Enables the attributes SwiftLint rule". Is changing to a different Timer creation function necessary to enable the rule? No. And in one case, you're changing the run loop mode in which a timer is being added from common to default. That may or may not change the app's behavior, but it definitely is unrelated to enabling the linting rule. The safest (and simplest) change to satisfy the rule would have been to add the @objc attribute.

I get that this could have been separate PRs, but these are precious small changes that are still related to the issue and are documented in the PR comment. If I pushed them separately I would have had to wait for one to be merged first and then deal with merge conflicts.

@philium I reverted the Timer changes. Should be ready for re-review.


Integrated keybind addon not passing caps

I use caps lock as one of my keybinds and it is no longer working.  I assumed it somehow came unbound but it won't register it.  The key still works as it picks it up for small/cap letters in the chat box but not with /sv kb
I tried 2 different pcs and 2 different keyboards.

Link to issue on active repo.
https://github.com/FailcoderAddons/supervillain-ui/issues/13#issuecomment-256678556


Nuget Update Release

Can you release latest Nuget update? :)

I'm working on a feature right now. I will do a release as soon as I finished it.


The new encoding can remember types and saves space when storing Uint8Arrays.
Also increases the version number and simplifies access to JDB objects in tests.

Codecov Report

Merging #15 into master will increase coverage by 0.34%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #15      +/-   ##
==========================================
+ Coverage   66.43%   66.77%   +0.34%
==========================================
  Files          26       28       +2
  Lines        2124     2146      +22
==========================================
+ Hits         1411     1433      +22
  Misses        713      713

Impacted Files
Coverage Δ

src/main/generic/utils/JSONUtils.js
100% <100%> (ø)

src/main/generic/utils/BufferUtils.js
100% <100%> (ø)

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 cf083ca...e1ed7c2. Read the comment docs.


[Suggestion]Display 'Azure App Service: Delete App Setting...' when deleting one app setting using command

Repro Steps:

F1 ->Type "Azure App Service: Delete..." to delete one app setting.
Check the result.

Actual:
Display 'Azure App Service: Delete...'.
Suggestion:
Display 'Azure App Service: Delete App Setting...' when deleting one app setting using command.

per @fiveisprime we should just remove "Delete App Setting" from the command palette


Added background color on code tag

Added background color when the code tag is not wrapped in li. I think the style on the code tag looks awesome but it only appears when it's wrapped in li so I try to add this.
Here is the preview
Berfore:

After:

Woah, thank you sm! I didn't notice that


You must enter a title to submit a Pull Request

move unique_together into model's Meta, so it actually works (+ migration)
fixed import for actual buildbot's version
...

what what I should do on cthulhu? :)
On Oct 19, 2011 10:30 AM, "Jiří Suchan" <
<EMAIL_ADDRESS>wrote:

move unique_together into model's Meta, so it actually works (+
migration)
fixed import for actual buildbot's version
...

You can merge this Pull Request by running:
git pull https://github.com/yedpodtrzitko/cthulhubot master
Or you can view, comment on it, or merge it online at:
https://github.com/centrumholdings/cthulhubot/pull/1
-- Commit Summary --

cleanup, minor fixes

-- File Changes --
M cthulhubot/admin.py (1)
M cthulhubot/bbot.py (13)
M cthulhubot/commands/vcs.py (5)
M cthulhubot/commands/version.py (1)
M cthulhubot/computer.py (4)
M cthulhubot/forms.py (41)
M cthulhubot/management/commands/discover.py (1)
A
cthulhubot/migrations/0008_auto__add_unique_projectclient_project_computer__add_unique_jobassignm.py
(85)
M cthulhubot/models.py (27)
M cthulhubot/project.py (9)
M cthulhubot/templates/cthulhubot/base.html (2)
M cthulhubot/templates/cthulhubot/projects.html (2)
M cthulhubot/templates/cthulhubot/projects_create.html (5)
M cthulhubot/views.py (23)
M requirements.txt (6)
-- Patch Links --
https://github.com/centrumholdings/cthulhubot/pull/1.patch
https://github.com/centrumholdings/cthulhubot/pull/1.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/centrumholdings/cthulhubot/pull/1

Not sure, I just wanted create pull request .( There must be something evil, probably

alaif: Will fix ;)


feat: revamped ui for file tree characteristcis

Download Artifacts :

win-ia32
win-x64
linux-x64


wiki: Wpa supplicant

https://nixos.org/wiki/Wpa_supplicant

There is already a section in the manual on that http://nixos.org/nixos/manual/index.html#sec-wireless and it mostly contains the same information.
The "User configuration" and "I'm on a LiveCD and I can't manually connect to any wireless network" sections are not reproduced in the manual but I am not sure they bring any significant value.
More specifically, the first of this two sections is not specific to NixOS I think. People can find more information on how to configure wpa_supplicant via other sources. The wiki page was far from complete in that respect.
The LiveCD troubleshooting section is not really relevant for most users, who are encouraged to use the graphical LiveCD. The graphical LiveCD comes with NetworkManager and a graphical tool to connect to a wifi network. As for people who are crazy enough to boot from the non-graphical LiveCD while not having access to an Ethernet connection, they should probably be experimented enough to figure out what to do by themselves.
So I'd say we can close this issue, but other people may want to voice disagreeing opinions...

Exists at: https://web.archive.org/web/20160829175608/https://nixos.org/wiki/Wpa_supplicant


Subsystem to analyze import dependencies and provide order of analysis

Given set of modules that import one another code should provide order of analysis with groups that can be analyzed concurrently.

Proposed interfaces are here https://github.com/MikhailArkhipov/python-language-server/tree/analysis5/src/Analysis/Ast/Impl/Dependencies

https://github.com/Microsoft/python-language-server/pull/621


Printing the known ece2cmor variable info in the comment column of the available file.

The checkvars.py script outputs various files including an available file, which contains requested variables which are available already in ece2cmor3. Currently the comment column is empty in the available file, however it might be handy to print the EC-Earth code name or the grib code for IFS and eventually the applied grid converversion or the applied arithmetic  expression.

Both code name (ifs or nemo) and the expression, if there, are written to the comment column in the file with the available variables.


Update Composer dependencies (2023-05-25-00-09)

Visual regression test passed!
View the visual regression test report


Controller panel

It will be perfect if you add a panel to control the miners

Well, that will be included in the new unified miner I'm working on.


Button

Use this issue to discuss the button component in the ONS Design System

The ability to use the button component as anything other than a <button> element should be removed as this is bad practice.

Secondary button font colour is still blue, this should be black (#22222). This appears to be lost during a merge.

Small button variant is too tall since underline change has gone in. Its currently 45px tall where as it should be 35px tall.

I think btn--small could do with a bit more left/right padding.

I agree... First screenshot is current and second is with horizontal padding set to 0.7em:

Fancy chiming in @will-madebymoon ?

LGTM. I think @will-madebymoon agrees.

I prefer the second one with a little bit wider...
Sent whilst on the move

On 29 May 2019, at 07:18, Jon Barnes<EMAIL_ADDRESS>wrote:
LGTM. I think @will-madebymoon agrees.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Ghost button variant doesn't have a background colour when viewed in a new window: https://ons-design-system.netlify.com/components/button/examples/button-ghost/

Pointer events need to be sent to none on button__inner to allow click events to be captured correctly

Need to add a parameter to pass in URL to button component so that it can be used as a link

Focus state shouldn't change when the element is hovered.

I think we need a button that looks like a link. I also would expect .btn--link to be a modifier to do exactly that.
However we are using the modifier .btn--link to make links look like buttons. Do we really need to do this? Can’t we just assume that if an <a>, <button> has a class of .btn it will look like a button.
I do feel this is a much better approach, and we can use the modifier to have a <button> that looks like a link.
GDS do it this way and it does make more sense.
https://design-system.service.gov.uk/components/button/

Do we need a loader and timer button? This should probably be default behaviour for a submit button, as you'd never want user to double-click it, and you'd alway need to show user feedback (spinner) if the process takes longer than a certain delay.

It is linked to setting the button type to be a submit button but I suppose we could change the logic a little bit so that it doesn't allow you to have a submit button without setting a submit type?

Macro table has created a button when trying to document the <button> tag - missing code markdown markup around it

Macro table has created a button when trying to document the <button> tag - missing code markdown markup around it


Sporadic kernel panics on stm32g4 flash erase/writes

Describe the bug
When writing big data chunks to the flash of an STM32G4 SoC, sporadic kernel panics occur.
It seems that a cache flush is needed after each erase.
To Reproduce
Build mcuboot for the nucleo_g474re and update several times.
Sometimes you will see a panic.
Expected behavior
Flash write and erase should work without panic
Impact
Firmware updates on stm32g4 series do not work
Logs and console output
E: ***** BUS FAULT *****
E:   Precise data bus error
E:   BFAR Address: 0xfab1f1a4
E: r0/a1:  0x0000045d  r1/a2:  0x00000000  r2/a3:  0xfab1f1a4
E: r3/a4:  0x20000208 r12/ip:  0xa0000000 r14/lr:  0x080043e1
E:  xpsr:  0x6100000f
E: Faulting instruction address (r15/pc): 0x08003d6a
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Fault during interrupt handling
E: Current thread: 0x20000208 (unknown)
E: Halting system

Fix: #32218

why low @erwango? this affects all stm32g4 users that use the flash driver.

@alexanderwachter This is from zephyr point of view: one series, one driver, not a regression (from what I saw) and not systematic. But doesn't prevent to review quickly and push so that it's getting merged.


User-configutable resource directory

Right now, the CEF resources directory is hard-coded to be at /build in the godot project root. This probably doesn't make sense for most projects. And it is especially problematic for multi-platform projects, since each OS needs to read a different set of resources, which can't all be stored in the same folder.
One solution would be to allow the user to pass in a directory as part of the library initialization process

@daniel-sanche nice work :) I'll test it. For the few I reviewed, your code seems good.

I've merged them. I do not have time right now:

for non public member variables I use m_
Merging the last std::cout with GDCEF_ERROR and godot::Godot::print.
Add in the documentation all the CEF setting/dictionary entries and add them explicitly in the demos.
Rename the CEFHello demo to CEF2D.
Add mouse and keyboard event to the active area in CEFHello demo.
Add example of JS injection in demo. As a non JS-dev I do not really understand why people want to execute JS

@daniel-sanche Finally waiting my wife getting ready, I added time to fix several points on my list. I'll commit them to night or tomorrow.

Sounds good, let me know if you want me to take a look at anything on the list. I'd add:

Add documentation for configuration dictionary fields

Add example of JS injection in demo. As a non JS-dev I do not really understand why people want to execute JS

My motivation was to use it to inject tokens to avoid a sign-in page. I don't do a lot of JS either, so I'm not sure what a good demo scenario  would look like

@daniel-sanche

[DONE] for non public member variables I use m_
Merging the last std::cout with GDCEF_ERROR and godot::Godot::print.
[DONE] Add in the documentation all the CEF setting/dictionary entries and add them explicitly in the demos.
[DONE] Rename the CEFHello demo to CEF2D.
[DONE] Add mouse and keyboard event to the active area in CEFHello demo.
Add example of JS injection in demo. As a non JS-dev I do not really understand why people want to execute JS

Also:

I fixed some settings that the user shall not modify.
You can add an example of JS in demos if you wish.
You can help fixing my poor English sentences ;)
I does not really like replacing _init by initialize and passing non default arguments (default dictionary will be {}) and CEF sub process shall be known and canonical and no more exportable. In my previous code, the path to it was directly computed, letting no risk to the user to give bad path. CEF does not pardon any error if you do not want your OS does infinite fork of processes and kill your OS.

Now initialize() only takes Dictionary. Ideally would be nice to use back _init() like done before and define global CEF config with the dictionary.

Cool, looks great! Feel free to close this issue if you think it's all done

Not all but mostly. let open other tickets if needed


Revert "Enable ReceiveResourceSpansV2 by default in OTel Agent"

Reverts DataDog/datadog-agent#30393 since it broke e2e tests on main
cc @IbraheemA
#incident-31792

/merge

/merge

Force-merging the PR to revert main to a good state.


Support regexp_parser 1.8 and 2.x series

Follow https://github.com/rubocop-hq/rubocop/pull/9154, https://github.com/rubocop-hq/rubocop/issues/9155, and https://github.com/rubocop-hq/rubocop/pull/9102.
This is a step towards the widespread use of regexp_parser 2.0.
RuboCop core accepts regexp_parser 1.8 (#9154) , but several code is already incompatible with regexp_parser 1.8. It can cause issue because these combination of versions.
Therefore, this PR ports code for regexp_parser 1.8 that will never be maintained from https://github.com/rubocop-hq/rubocop/pull/9102.
Implementation of this patch, code is intentionally duplicated because it is evaluated only when the class is defined. Also, since obsoleted code for regexp_parser 1.8 is assumed to never be maintained, the target to be removed is clear.
To be honest, it's ugly as implementation, but I think it has the least impact for RuboCop 1.x series users.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[ ] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Thanks, I was too lazy to do this 😅

several code is already incompatible with regexp_parser 1.8.

Only for not-utf-8 Regexp, right?

Yeah, this patch going to address issues with multibyte characters Regexp rather than non-utf8 Regexp :-)

The fix is ugly indeed, but I think it's the best we can do. Thanks! 🙇♂

Thank you for your fix, It's very sad for me that some basic ruby libraries are not very active maintained.
Even on level "accept PR with less strict versions, without any extra features"
But this PR allow to use latest version of rubocop even using forbidden dependencies


fix(warning): override native method

SonarQube analysis reported 2 issues

 2 minor

Watch the comments in this conversation to review them.

 S(logger-py): Override warning method


Proposal to refactor Requestable interface into Queryable interface.

In my experience, "requestable" methods that mutate a source, such as add, remove, and update, are not appropriate for assisting / rescuing. Instead, these methods provide thin wrappers over transform, and the Transformable interface provides the best way to engage with mutations.
The "requestable" methods that are in fact appropriate for assisting / rescuing are all related to querying a source: find, query, findLink, and findLinked. I think all these methods could be distilled into a single query method, given the right query definition language (see #192).
I believe we should refactor the Requestable interface into a Queryable interface that supports a single query method. This will nicely parallel the Transformable interface that supports a single transform method.
The query method will take two arguments: a query object and an options object. The query object might be as simple as specifying path: '/planets' or path: '/planets/1' or it might involve filters and conditionals (still TBD). It's possible that options should simply be a member of the query object instead of a separate argument.
I believe that this simplification will keep sources as lean and standardized as possible.
Convenience methods such as add, remove, update, and find could be added to a new class Store. A store will wrap a memory source (with a cache of course), and will be the primary interface developers use to interact with data. Behind the scenes, other sources can be wired up with their much simplified interfaces.
Major credit to @gnarf and @opsb for discussions that led to thinking about this new direction.
I'm in the midst of updating the normalized form (as per #157), which seems to make all this much more feasible.

Ha, I was going to suggest exactly the same name change.

I do like the idea of having a single query method to match transform. Moving the query encoding methods(find, findAll etc.) to the store brings a nice symmetry as well.

While we are on the topic, perhaps we should consider my confirm method:

confirm(query)

Search for record by ID(s) inside query object

If found - patch all keys present on the query on the found object and return.
If not found - add and return

Also, the use cases are way less obvious, but I ended up using an assistAdd to handle "waiting for server response" before adding to my local.
Also with assistRemove you could do something like:
source.on('assistRemove', function(type, id) {
  if (type === 'user') {
    if (window.confirm('are you sure you want to delete user ' + id)) {
      return Promise.reject(new Error("Let the source delete it");
    } else {
      // "Yeah, we deleted it.... heh"
      return Promise.resolve();
    }
  }
});

It might be a silly thing, but you could also use these assists to implement a security/permissions layer.

@gnarf I'm writing up my notes on adding "optimistic ui" which I think will cover

"waiting for server response" before adding to my local.

In this case the record would be added to the local store optimistically but if the server rejected it (due to permissions denied) then the change would be rolled back in the local store.
Regarding "upsert" (think that matches "find and update" or "create if not found"), perhaps this is something specific to sources? i.e. maybe you just do an add and the source can do an upsert if it supports it or follow the existing semantics if not?

Regarding your code snippet, I think UI => orbitjs interactions should probably be mediated through a Store (which @dgeb touched on).

Yeah - I wasn't really arguing against this proposal, just pointing out some of the things that the current setup would let you do.
Also, not every use of orbit will have a Store

Also, not every use of orbit will have a Store

Just to be clear, I'm referring to an orbitjs store as opposed to an ember-orbit store. If that is what you're referring to what are the scenarios that you're considering?

Regarding "upsert" (think that matches "find and update" or "create if not found"), perhaps this is something specific to sources? i.e. maybe you just do an add and the source can do an upsert if it supports it or follow the existing semantics if not?

The thing I'm worried about there, is that "upsert" is definitely a different operation than "insert" or "update" - I'd hate to conflate the two by giving them the same entry (add)

How do you see it working at the operation level, a single call to source.transform or source.query followed by source.transform? i.e. would you introduce a new operation verb or use the existing ones?

As written in my app, the default implementation uses a chained promise of find and add and patch requests.

Also - this has gotten off topic, perhaps we should move these last few
posts into a new issue about a confirm or upsert pattern/api.
On Sat, Sep 19, 2015 at 11:39 AM, Oliver Searle-Barnes <
<EMAIL_ADDRESS>wrote:

How do you see it working at the operation level, a single call to
source.transform or source.query followed by source.transform? i.e. would
you introduce a new operation verb or use the existing ones?
—
Reply to this email directly or view it on GitHub
https://github.com/orbitjs/orbit.js/issues/202#issuecomment-141680880.

Yeah, breaking it out sounds like a good idea. Sounds like a store.upsert() might fit the bill, it could take care of chaining the calls to the sources.

perhaps we should move these last few posts into a new issue about a confirm or upsert pattern/api.

Sounds good to me @gnarf. I agree that this is a good candidate for a convenience method on the forthcoming OC.Store class.
It sounds like there still aren't any blockers for the Requestable -> Queryable refactor (unless I'm misunderstanding). Let's all try to focus on our uses of the current Requestable methods to ensure that we're not overlooking something.

Will be handled in the rethink branch - currently a WIP.

While beginning to implement query and query expressions, it occurs to me that there are three ways in which a source / store could respond to queries:

asynchronously - returns a promise that resolves to the results. This is how I've planned to implement query.

synchronously - returns the results directly. This could replace retrieve at the Source / Store level for sources that are backed by caches.

synchronously - returns an object that internally issues a query and keeps its results updated. This method would only exist on the Store, and not individual sources.

I'm not sure of the right set of interfaces to expose to allow these different query types. Here's my current thinking:

Introduce a Queryable interface which implements query to handle the async case. Allow assist / rescue handlers. This is the plan described above.

Introduce a Retrievable interface for sources with caches, and reimplement retrieve to work with a query expression instead of just a path.

Introduce a liveQuery method only on the Store. This creates a LiveQueryResults object that internally issues retrieve first, updates its results via an async query call, and then stays updated by an observer (replacing the same functionality used in ember-orbit).

Not thrilled with the naming here, but I think the concepts are sound. Feedback welcome.

Just updated the above comment after another fruitful discussion with @opsb. Much happier with the proposed interfaces and methods now (query, cache.query, and subscribe).

The Requestable interface has been removed with the rethink merger, in favor of Updatable, Queryable, and Fetchable interfaces.


Any plan to support for Windows 11?

Now windows 11 only have 2 option to set the start menu and the icons in center or left.
I think it would be awesome it we set the start menu in left and the app icon in the center.
What do you think?
Thanks.

The new windows taskbar implementation in 11 breaks the methods used in windows 10 to center the taskbar so this won't be possible and compatibility will end on windows 10. Best bet is to petition Microsoft to give an option to have the start button remain in the left corner


Add use cases in dev guide

Fixes issue https://github.com/CS2103-AY1819S1-F10-2/main/issues/42

Pull Request Test Coverage Report for Build 151

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

Totals

Change from base Build 149:
0.0%

Covered Lines:
1441

Relevant Lines:
1552

💛  - Coveralls


Time and weather

How do I display time in AM/ PM instead of 24 hour time.  The upcoming weather does not advance each day.

Hi, sorry for late response. I am looking into the 24 hour thing, it should change depending on your device system settings. About the upcoming weather, I've noticed this before, the API I use to get the forecast sometimes returns old data. Unfortunately I can only fix this by switching API's. I might do that in the future.

Hi guys.  To correct this problem, in the simple_layout.xml file, or the verbose_layout.xml file, for tc_time (text clock), simply change the format12hour property to h:mm
Problem solved.  I think if you put an a after it, you also get am/pm

Thanks! Could you submit a pull request?


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit af17e4c:
:clock10: Pending: waiting for processors (24 builds ahead of you)
:warning: Docs Build is busy, currently there are 24 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit af17e4c:
:clock10: Full build: the average full build time is 7 min(s) 29 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit af17e4c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Cassandra schema possible improvements

Mainly just writing thoughts down here, and trying to discuss the limitations of a future schema. Not a priority at the moment.
The current schema was built using different column families for accounts, applications, apis, plugins. We should probably handle relations the way Cassandra handles them:
Relations
CREATE TYPE applications(
  public_key text, -- This is the public
  secret_key text, -- This is the secret key, it could be an apikey or basic password
  created_at timestamp
);

CREATE TABLE IF NOT EXISTS accounts(
  id uuid,
  provider_id text,
  applications set<applications>,
  created_at timestamp,
  PRIMARY KEY (id)
);

CREATE INDEX ON accounts(applications);

Here, the index would allow us to query the accounts table by application's values (especially public_key, as it is the only value that will be queried), but it needs to happen like this:
SELECT * FROM accounts WHERE applications CONTAINS ('abcd'); -- 'abcd' being a public_key

This model is a better fit for relations in Cassandra, less data duplication
Not 100% sure about the efficiency of querying a User Defined Type column vs. a text field like currently.
We still have to check the unicity of a public_key, like currently

The same applies for plugins. They are currently a table on their own, but a plugin is attached to an API, and optionally to an application.
Community plugins
Plugins from the community will have to use the value property and encode their data to store things. We could provide them with a way of creating a table, or a UDT.

Doing such a schema change could also fix this ugly problem which is plugins selection "fixed" by bb838907b436964f9694cf4392fec98e01b7fab9

Credentials
I am not happy by the way we handle credentials and I think we should think more carefully how we want to support this. I think having something like the following schema could make sense:
We do have the following generic core entities:

accounts, the base entity who owns of zero or more applications.
applications, generic credential holder, that can hold different credential types

Each authentication plugin can create a credential type on the datastore, like:

query
basic
header
ldap
oauth

This means that we need to introduce the possibility for plugins to edit the datastore using a DSL.
Plugins DSL
If plugins can modify the datastore, that should be done with a DSL instead of plain simple SQL, to avoid doing illegal operations on the datastore. An example could be:
return { create = {
    {
      type = "table",
      name = "ldap",
      properties = [[
        id uuid,
        key text,
        created_at timestamp,
        PRIMARY KEY (id)
      ]]
    },
    {
      type = "datatype",
      name = "ldap_credential",
      properties = [[
        public text,
        secret text
      ]]
    }
  }
}

By having the DSL we're limiting the number of operations that the plugin can execute on the datastore, like deleting other tables, or modifying existing data.
We could also implement a rollback function to execute DELETE statements on whatever datastore entity has been created during the provisioning of the plugin (it needs to be explicit because it could cause loss of data).

This is even nicer, the action to create those entities could be implicit:
{
  tables = {
    {
      name = "ldap",
      properties = [[
        id uuid,
        key text,
        created_at timestamp,
        PRIMARY KEY (id)
      ]]
    }
  },
  datatypes = {
    {
      name = "ldap_credential",
      properties = [[
        public text,
        secret text
      ]]
    }
  }
}

On a side note the more I look at the DSL above, the more it resembles the schemas we already have. If we decide to implement a DSL to DB translation, I wonder if we can automatically generate the migration script file by parsing all of the schemas, thus automating migrations.

Credentials

Each credential could be a UDT for Cassandra. If we have a DSL, we need to make sure we can handle this for other DBs.

DSL

Could even skip the migration file creation. Migration files could be DAO agnostic and simply DSL files executed on the go.
If we are talking migrations, the DSL also needs to be able to ALTER or DROP, and that does not protect the DB against malicious plugins either as we discussed before.
What does protect against that is a plugins-only DSL, that just offers the possibility to create UDTs for the plugins table.
But at the end of the day, any Lua code executed under a Kong instance can simply require the factory and call the drop method @thefosk. It's up to us to distribute valid, trusted plugins.
Official, trusted plugins could be released and signed by PGP.
And our DSL could just do anything it wants, since an official plugin is trusted.

Regarding the DSL, a few points:

We could automatically prepend the plugin name in front of any entity that is being created, like basicauth.keys. This is a good idea for two reasons:
Avoid name clashes if two plugins want to use the same table name.
Make sure that a plugin can't change anything that doesn't belong to itself.
There may be a way to limit the scope of drop or other reserved calls just to some special packages. Thus we can block every call that comes from the kong.plugins package.
We should still sign plugins and avoid running those that are not authorized.

Too bad we're not using Postgres: http://leafo.net/lapis/reference/database.html#database-schemas

Cassandra 3.0 will support this: https://issues.apache.org/jira/browse/CASSANDRA-8473

Following the discussion we had yesterday, here are the decisions we took:

accounts: renamed to consumers.
apis: nothing new
plugins:

They can plug themselves into the lifecycle of a request (this hasn't changed)
They can access the consumers table
They can expand the DB to add tables and perform additional queries of their own
They can expand the API routes
Once installed, one can create configuration(s) (said configuration entry of that plugin, linked to an api and optionally, a consumer. This allows a plugin to be enabled on an API, as well as being overridable for a specific consumer.

We started talking about having a whitelist/blacklist for configuration entries (to be able to enable/disable a configuration entry for a lot of apis/consumers at once, but this ran into implementation issues as illustrated in the following picture.
Here is a pic of the whiteboard:

Improvements described in the previous comment are implemented, appart from:

plugins expand the DB to add tables and perform additional queries of their own
plugins expand the API routes

Those things need to be done in order to provide a good development environment for plugins but will be part of another discussion.

Plugins do expand the API routes, is has been implemented.


Add a route to put labels or tags on a task

Add a route to put labels or tags on a task

this should be add or update


Unable to find an entry point named 'equihash_verify_export' inshared library 'libmultihash'

Note
When a share is submitted in a ZCash pool, I get this error. It cannot find the entry point named 'equihash_verify_export'
Description
Error is thrown and miner gets disconnected.
Steps to Reproduce

Start zcashd
Run miningcore
Run a miner and wait until the share is submitted

Expected behavior
'equihash_verify_export' should be found and no error happens.
Actual behavior
The error occurs and the miner gets disconnected and then reconnects until this happens again in the next share found.
Reproduces how often
100%
Version
master, tag: v40, origin/master
Running on Ubuntu 18.04
Additional Information
[2018-10-19 18:29:40.5476] [E] [zec1] [0HLHM8ICQ2ISF] Connection error state: System.EntryPointNotFoundException: Unable to find an entry point named 'equihash_verify_export' inshared library 'libmultihash'.
at MiningCore.Native.LibMultihash.equihash_verify(Byte* header, Int32 headerLength, Byte* solution, Int32 solutionLength)
at MiningCore.Crypto.Hashing.Equihash.EquihashSolver_ZCash.Verify(Byte[] header, Byte[] solution) in /home/rakamaru/source/miningcore/src/MiningCore/Crypto/Hashing/Equihash/EquihashSolver.cs:line 79
at MiningCore.Blockchain.ZCash.ZCashJob.ProcessShareInternal(StratumClient worker, String nonce, UInt32 nTime, String solution) in /home/rakamaru/source/miningcore/src/MiningCore/Blockchain/ZCash/ZCashJob.cs:line 348
at MiningCore.Blockchain.ZCash.ZCashJob.ProcessShare(StratumClient worker, String extraNonce2, String nTime, String solution) in /home/rakamaru/source/miningcore/src/MiningCore/Blockchain/ZCash/ZCashJob.cs:line 298
at MiningCore.Blockchain.ZCash.ZCashJobManager1.SubmitShareAsync(StratumClient worker, Object submission, Double stratumDifficultyBase, CancellationToken ct) in /home/rakamaru/source/miningcore/src/MiningCore/Blockchain/ZCash/ZCashJobManager.cs:line 174    at MiningCore.Blockchain.Bitcoin.BitcoinPoolBase2.OnSubmitAsync(StratumClient client, Timestamped1 tsRequest, CancellationToken ct) in /home/rakamaru/source/miningcore/src/MiningCore/Blockchain/Bitcoin/BitcoinPoolBase.cs:line 187    at MiningCore.Blockchain.ZCash.ZCashPoolBase1.OnRequestAsync(StratumClient client, Timestamped1 tsRequest, CancellationToken ct) in /home/rakamaru/source/miningcore/src/MiningCore/Blockchain/ZCash/ZCashPoolBase.cs:line 177    at MiningCore.Stratum.StratumServer.OnRequestAsync(StratumClient client, JsonRpcRequest request, CancellationToken ct) in /home/rakamaru/source/miningcore/src/MiningCore/Stratum/StratumServer.cs:line 250    at MiningCore.Stratum.StratumClient.ProcessRequestAsync(Func4 onRequestAsync, ReadOnlySequence1 lineBuffer) in /home/rakamaru/source/miningcore/src/MiningCore/Stratum/StratumClient.cs:line 374    at MiningCore.Stratum.StratumClient.ProcessReceivePipeAsync(TcpProxyProtocolConfig proxyProtocol, Func4 onRequestAsync) in /home/rakamaru/source/miningcore/src/MiningCore/Stratum/StratumClient.cs:line 320

It doesn't look like you are really running Release 40. I can tell by the namespace "MiningCore.Native" in the callstack. The camel-casing of "MiningCore" was dropped some releases ago. Now its "Miningcore.Native". Could you try with a recent release?

Thank you @oliverw, I'll delete and re-install the master version and try again.


add filter invert

add invert filter
http://image.intervention.io/api/invert

This seems well implemented. My only question, is there actually a valid use-case for this? Does anyone actually ever use invert? :)

I want to implement every option in Intervention Image. They are available anyway.
Examples:

invert alpha mask/channel
easily place b&w jpeg logo on black or white background

While I very much appreciate your interest in the library, I think I want to keep it focused on practical every day manipulations.


[Bug]: Unhandled exceptions in MockAnnotationProcessor related to Function Mocking

Description
There are a several unhandled exceptions in the class MockAnnotationProcessor that needs to be fixed.

For single file projects, function mocking is not supported. Should provide a proper diagnostic for that. This is also tracked by https://github.com/ballerina-platform/ballerina-lang/issues/38720
When the provided functionName for function mocking is not found in the project, a proper diagnostic should be given. A part of this is fixed with https://github.com/ballerina-platform/ballerina-lang/issues/38693. However there are cases where the fix is not applicable to.@test:Mock { functionName: "intAdd1" }  // intAdd1 is non-existent
test:MockFunction intAddMockFn = new();

Steps to Reproduce
No response
Affected Version(s)
No response
OS, DB, other environment details and versions
No response
Related area
-> Test Framework
Related issue(s) (optional)
https://github.com/ballerina-platform/ballerina-lang/issues/38720
https://github.com/ballerina-platform/ballerina-lang/issues/38693
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

Another issue issue related to this: https://github.com/ballerina-platform/ballerina-lang/issues/38972

Another issue - @test:Mock without the annotation the moduleName, functionName also causes an NPE & compiler plugin crashes.
@test:Mock // no MockConfig record
test:MockFunction mock_intAdd = new ();

This also must issue an error

Another issue - @test:Mock without the annotation the moduleName, functionName also causes an NPE & compiler plugin crashes.
@test:Mock // no MockConfig record
test:MockFunction mock_intAdd = new ();

Updated the same PR with the fix


remove construction banner

👷 Deploy Preview for bongosian-press processing.

Name
Link

🔨 Latest commit
ccba4de430393270d6b5d059490d7d03193cdcc8

🔍 Latest deploy log
https://app.netlify.com/sites/bongosian-press/deploys/658244e7feb5630008e72875


Fix minor "issues" with the operator

Some minor improvements when reading the docs and testing the operator:

Use docker multi stage build (https://docs.docker.com/develop/develop-images/multistage-build)
Update Kubernetes resource versions (since 1.9 is required)
Fix some minor things in the code base (had only a rough overview)

Code base moved. Find reposted PR for the change here


Nit: Fix 'Changeset' capitalization, wrong-cased filenames, Canada type decl

'Changeset' is prevailingly spelled with a lowercase 's' (it's a single word, like 'hashtable'):
https://en.wikipedia.org/wiki/Changeset
Fixed a couple of Pascal cased filenames.
Added a type declaration for the output of 'generateCanada()'.

Thanks, @yann-achard-MS!


RYA-135 Hard code triples collection

Description

What Changed?
There is no need for the triples collection to be configurable, as
only the mongo database name will change the rya instance.

Tests

Coverage?

N/A
Links
Jira
Checklist

[ ] Code Review
[x] Squash Commits

People To Reivew
@pujav65
@kchilton2
@ejwhite922

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/769/Failed Tests: 4incubator-rya-master-with-optionals-pull-requests/org.apache.rya:mongodb.rya: 2org.apache.rya.mongodb.MongoDBRdfConfigurationTest.testBuilderorg.apache.rya.mongodb.MongoDBRdfConfigurationTest.testBuilderFromPropertiesincubator-rya-master-with-optionals-pull-requests/org.apache.rya:rya.indexing: 2org.apache.rya.indexing.mongo.MongoIndexingConfigurationTest.testBuilderorg.apache.rya.indexing.mongo.MongoIndexingConfigurationTest.testBuilderFromProperties

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/772/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/774/

opening a new PR against RYA master after 3.x  https://github.com/apache/incubator-rya/pull/300 is in


Refactor to remove SubscriptionHandle/ClientHandle/ServiceHandle

The contents of SubscriptionHandle are moved into Subscription.
This creates the problem that the SubscriptionHandle was returned by SubscriptionBase. We could also return the raw rcl_subscription_t, but I'd like to keep these types out of the public API.
Instead, I changed the SubscriptionBase trait to not return the thing to be added to the WaitSet, but to take the WaitSet as an argument and add the rcl_subscription_t directly to it. This has the benefit that this trait now is general enough to also cover clients, services etc. and thus I renamed it to Waitable.

@nnmm what is the rationale for this? I don't really see the point, is it to get rid of SubscriptionHandle?
On a general note, if this gets approved, I'd like to wait to merge this after the first release. I'd rather not refactor #146 to include these changes and apply them to ClientHandle and ServiceHandle

but I think this generalization is a good thing

How would that work with GuardConditions? They are entities that are added to a waitset, but behave differently than subscriptions, clients, services, etc. In rclcpp, ClientBase, SubscriptionBase and ServiceBase inherit from Waitable, but GuardCondition doesn't

@esteve I had an idea. Currently, after this PR, the Node would have members
    pub(crate) clients: Vec<Weak<dyn Waitable>>,
    pub(crate) services: Vec<Weak<dyn Waitable>>,
    pub(crate) subscriptions: Vec<Weak<dyn Waitable>>,

– same for the WaitSet. It's possible to make a copy-paste error or so and mix up two different kinds of Waitable.
The idea is to keep ClientBase, ServiceBase, SubscriptionBase, but make them empty sub-traits of Waitable:
trait ClientBase : Waitable {}

That's a bit more type-safe. Though maybe ClientWaitable would be a better name.

I've applied the changes to SubscriptionHandle/SubscriptionBase also to clients and services. The diff is a bit large as a result – let me know if you'd prefer me to split it up into several commits or PRs.

trait ClientBase : Waitable {}

That's a bit more type-safe. Though maybe ClientWaitable would be a better name.

Good idea! I like it, in fact, that's the same class hierarchy as rclcpp :wink: I prefer to keep it as ClientBase, it'll be consistent with rclcpp

Good idea! I like it, in fact, that's the same class hierarchy as rclcpp wink I prefer to keep it as ClientBase, it'll be consistent with rclcpp
Edit: I was mistaken, I thought that Subscriptions et al inherited from Waitable, turns out they don't.

I thought about it some more and imo ClientWaitable is more fitting, since "base class" is an OOP concept that doesn't map 1:1 to Rust, and like you said, the correspondence to rclcpp doesn't really hold. In rclcpp, the *Base classes hold a lot of functionality, but this trait is an empty (marker) trait. Are you ok with keeping the Waitable name as well?

Closing due to inactivity, we might revisit this in the future. Thanks @nnmm


Update optional-lite to 3.4.0

This is just routine maintenance, so I'll merge this in one day.

Coverage remained the same at 57.609% when pulling 97437007c160b5df97902835aac9550e5e33a763 on feature/update-optional-lite into ef2531d7cc17f74e427c436b95330415c69a8368 on master.


add reference to webpack in built tools to generate umd builds

Webpack is a popular build tool that has builtin support to generate UMD builds. Added reference to webpack documentation that mentions how to configure it to generate UMD builds.

@EvanCarroll I am new to contributing to OSS projects. Could you suggest a course of action?


Bump model-maven-helper to version 32

@pascalgrimaud maybe you can add a bounty on this, because we are working with @murdos and the main contributor of the lib 🙂

Done, if it's more work, I can add more

thanks @pascalgrimaud

@murdos for the bounty 100 for you 100 for me?

@qmonmert : I thought the bounty would be for @gastaldi, he is the one having done the hard work.

Easier to share now :)

Thanks @pascalgrimaud !
@gastaldi Here's the doc for the bounty: https://www.jhipster.tech/bug-bounties/#-bug-bounties 😉

@murdos thank you! I've submitted an expense stating $100 bug bounty claim for https://github.com/jhipster/jhipster-lite/pull/9270.

thanks @pascalgrimaud https://opencollective.com/generator-jhipster/expenses/194808

https://opencollective.com/generator-jhipster/expenses/194847 :-)

@gastaldi @qmonmert @murdos : approved. Thanks for this team work, guys!


Inefficient Gini Coefficient calculation?

When I run:
gini_coef = pysal.inequality.gini.Gini(a).g

where a is any huge numpy array, e.g., with 300000 elements, it gets stuck, irreparably crashing my whole PC, trying to run this line of code (see here):
d = np.abs(np.array([x - xi for xi in x]))

This is not the case when I run it using my own code which does not make use of list comprehensions, and instead calculates Gini like this.
I wrote that just before I discovered you had a Gini function too, so I do not fully understand your code, although I am willing to help. The two functions produce very very similar output (indistinguishable before about 6 decimal places).
Anyway, I thought I would mention that it be worth considering using numpy to calculate the difference.

Thanks for raising this issue. I am just about to leave for a week of travel and will definitely be looking into this. At first glance the efficient approach is based on a ranking of the values, which assumes no ties. I originally ruled that out as we had to both handle ties (in an upstream application) and also needed to keep tabs on geographical positions of each observation. So the memory inefficient implementation is what we used.
That said, once I have a little time after vacation, I think it might be possible to refactor things with an eye towards a more efficient approach (as you point to) that also addresses our upstream needs.

Have a nice time during your travels! I'm curious to see how you solve it.
😄

Closeed with #862


[Dapr blog] Dapr case study: OpenFunction

Hi team,
I write a blog to introduce the Dapr case study which demonstrates how OpenFunction integrates and leverages Dapr components to build a FaaS platform.  You can preview or edit it here.
This article is a good reference for me but it is too long. So I plan to refactor it into two articles and add them to Dapr official blogs. This is the first one that only includes the basic introduction and lab. The next article will include the log alerting demo and the community meeting recording.
If you have any thoughts or suggestions, feel free to add your comment or modify it.

/cc @OpenFunction/community-advocacy

The final blog is here https://hackmd.io/-lGJqd-XQNquNfCIjyxwVQ and will be posted to dapr blog next week


Fixed URL in RoleTooltipRequiresDescribedBy role

Thanks !
On Nov 29, 2017 12:58 AM, "hajjiunlocked"<EMAIL_ADDRESS>wrote:

@hajjiunlocked approved this pull request.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FGoogleChrome%2Faccessibility-developer-tools%2Fpull%2F357%23pullrequestreview-79743251&data=02|01|bluestreamct%40outlook.com|a3cbf11db5a2436ae5b908d536ee2d82|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636475318943287735&sdata=OBhUV5aQS4zC1zpILXVBKUz4ByKF0krab0RKuEMKiDY%3D&reserved=0,
or mute the thread
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FATDrDsR2rvmwLV76SjoPch2R8DH-Glhpks5s7PJ0gaJpZM4QDOmQ&data=02|01|bluestreamct%40outlook.com|a3cbf11db5a2436ae5b908d536ee2d82|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636475318943287735&sdata=4yKRFDe88cWOl5D4CXKPPnMQw09V6leQy1iq1YLp06Y%3D&reserved=0
.


Docker vignette

This is mostly the material from the water-use-15 readme, I reworded just added the contents of the docker-relevant files and reworded a few things.
I had thought I remembered there being comments in a google doc somewhere about changes to make, but I didn't see those anywhere.

Hmm, I thought there was too, but I can't find it now. Maybe the google doc discussion we're both remembering was about the scipiper vignette you worked on (https://docs.google.com/document/d/1xApqFykG0nhOcHMQRvBjsOIwbsvfftp9z7yzoPQ7su0/edit#heading=h.s5rnffqob7h5)?


About some warnings

I got the fllowing logs after running: python test_flops.py --config-file configs/RegNetX-4.0GF.ini，i wonder whether these warnings are normal?
[INFO] Register count_convNd() for <class 'torch.nn.modules.conv.Conv2d'>.
[INFO] Register count_bn() for <class 'torch.nn.modules.batchnorm.BatchNorm2d'>.
[INFO] Register zero_ops() for <class 'torch.nn.modules.activation.ReLU'>.
[WARN] Cannot find rule for <class 'arch.regnet.ConvBnAct'>. Treat it as zero Macs and zero Params.
[WARN] Cannot find rule for <class 'arch.regnet.Bottleneck'>. Treat it as zero Macs and zero Params.
[WARN] Cannot find rule for <class 'torch.nn.modules.container.Sequential'>. Treat it as zero Macs and zero Params.
[WARN] Cannot find rule for <class 'arch.regnet.Stage'>. Treat it as zero Macs and zero Params.
[WARN] Cannot find rule for <class 'arch.regnet.GlobalAvgPool2d'>. Treat it as zero Macs and zero Params.
[INFO] Register count_linear() for <class 'torch.nn.modules.linear.Linear'>.
[WARN] Cannot find rule for <class 'arch.regnet.RegNet'>. Treat it as zero Macs and zero Params.
macs: 3.989G, params: 22.118M

I see the problem too. Maybe it's normal. It doesnot matter


Please help to build ppc64le grafana operator v5.9.2

Hi Team.
in ppc64le architecture we are not able to install grafan operator. How should we do to fix this issue?
Error as below:
Failed to pull image "ghcr.io/grafana/grafana-operator@sha256:e7923d1a71b90a8ad66d114aec4b2b4e4929f15ba91872f64c5e271629612284": rpc error: code = Unknown desc = choosing image instance: no image found in image index for architecture ppc64le, variant "", OS linux
Please help to build this grafana operator v5.9.2.

Update https://github.com/grafana/grafana-operator/blob/fb7c80072406335150622ab4f80d2ce51b783cff/.github/workflows/release.yaml#L122 to fix this.


Consolidate multiple related notifications on the notification bar

 Issue by brianschamel
Thursday Mar 23, 2017 at 20:57 GMT
Originally opened as https://github.com/CQUI-Org/cqui/issues/420

This'd mainly be for DoWs, making peace, and city-state quests, as they are the ones that get stacked often.
Basically, instead of 9 different notifications for the start of a war between two civs with several suzerains each, combine the text from all into a list on a single notification.
However, with this system, it might be difficult to pick out the actual civs from among of city states,
to which I have 2 possible solutions:

Color code the cities, with different colors for you + your joint war partner (if you have one) (1 color), either of your CS's (2 colors), the enemy civs (3 colors), and their CS's (4 colors)
Instead, replace the notification text with "Russia (+3 city states ) has declared war/made peace with Arabia (+2 city states).

 Comment by chaorace
Saturday Mar 25, 2017 at 02:09 GMT

I think the best implementation for this would be adding horizontal stacking and sorting notifications into these stacks based on type.
I'm thinking something like this: by default, they would be scrunched up, similar to how district icons in the city banner look, but would expand to full width on mouseover. Something like this would be lower in implementation cost, and, at least in my opinion, is more immediately intuitive

 Comment by chaorace
Sunday May 21, 2017 at 01:09 GMT

This is being handled as part of #514


Bug report for failed CircleCI job (job: test)

Auto-generated report for test job.
Link to failed build: .
Note: Information about any subsequent build failures that happen while
this issue is open, will add comments with more information to this issue.

Another occurrence

Link to latest failed build:

Link to latest failed build: https://circleci.com/gh/asuresh4/opentelemetry-collector/80

Link to latest failed build:

Link to latest failed build: https://circleci.com/gh/asuresh4/opentelemetry-collector/88


Cannot resolve #{$var} correctly

I have tried many times to resolve code like this below correctly,
.component {
  $c: &;
  padding: 2vw;
  &__card {
    background-color: #fff;
    &:hover #{$c}__name {
      color: #bada55;
    }
  }
  &__name {
    color: #000;
  }
  &__button {
    background-color: blue;
    color: #fff;
  }
}

But, it never works well, precss 2.0.0 would throw an error:
    ERROR in ./node_modules/css-loader?{"importLoaders":1}!./node_modules/postcss-loader/lib!./src/style.css
    Module build failed: Unknown word (7:28)

       5 |     background-color: #FFF;
       6 |   }
    >  7 |   .component__card:hover #{.component__card}__name
         |                            ^
       8 |       color: #BADA55;
       9 |     }
      10 |   .component__name {

Then I tried upgrade precss 3.1.0, it works, but not well.
Which I expect result should be like this:
.component {
  padding: 2vw;
}

.component__card {
  background-color: #fff;
}

.component__card:hover .component__name {
  color: #bada55;
}

.component__name {
  color: #000;
}

.component__button {
  background-color: blue;
  color: #fff;
}

You can also try that sass code compile online http://sass.js.org/.
But truely result is below:
.component {
  padding: 2vw;
}
  .component__card {
    background-color: #fff;
  }
  .component__card:hover .component__card__name {
      color: #bada55;
    }
  .component__name {
    color: #000;
  }
  .component__button {
    background-color: blue;
    color: #fff;
  }

Is it a bug? And how to solute the problem?

@whidy while there is no fix for this bug, you can try to set the variable's value to a component selector like:
.component {
  $c: .component;
  &__card {
    &:hover $(c)__name {
        ...
    }
  }
}

or
$c: .component;

$(c) {
  &__card {
    &:hover $(c)__name {
        ...
    }
  }
}

To quote the postcss advanced variables readme:

*Note: To use #{$var-name} without issues, you will need to include the PostCSS SCSS Syntax.

Meaning you will have to add PostCSS SCSS Syntax to your pipeline for this to work properly.
If your issue persists it likely belongs to postcss-advanced-variables or /postcss-scss instead. :)


[fixup] fqdn: No warning when toFQDNs are missing IPs when generating

This was missing from https://github.com/cilium/cilium/pull/6827 and the
code-path fixed in this commit is the more common one.
With the DNS poller a matchName without IP data was a sign that polling
had failed for that name (the regeneration was triggered after the
poll). As we switch to the DNS proxy this makes less sense since as each
DNS lookup will trigger a regeneration and some matchName entries may
not match. A debug print is useful but anything more is unnecessary.
Fixes 3775d8d357bc2ce673089639cad677c796a9027b

This change is

test-me-please

Coverage decreased (-0.004%) to 42.964% when pulling bad559ab4bd3026a1d2a7f8febfddababdd11387 on raybejjani:fqdn-no-noip-warning into ba9798c3a97815f962b3ab9356d1cd741e68d233 on cilium:master.

Build failure:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/9876/
Not related; this change is a log message change only, and since the code is compiled, is self-evident in its correctness. Merging.


How to use the script

Hi, can you add in the documentation how to use the script in Travis?
Thanks

I have added usage documentation to the README, and if you invoke the script with -h, it will display usage information.


[PROPOSAL] Community call organization

We need a rotation to define the organizer of the community calls. Nick has been organizing those every 2 weeks but I believe the duty should be shared. In addition, we need to agree on a storage for the presentation files so presenters have an opportunity to edit it independently from which company they work.

For now, @msfussell and I will alternate hosting responsibilities monthly.
@msfussell will take the calls in January and I will take February and so on and so on.

Agreed on the proposal above. The presentation are now stored on Google drive that is accessible be all the presenters.


Remove update functionality from UI

Body
Within https://github.com/apache/streampipes/issues/2001 we introduced basic support for migrating pipeline elements.
This makes the manual update of pipeline elements in the UI redundant.
Therefore, we can safely remove it.
StreamPipes Committer
I acknowledge that I am a maintainer/committer of the Apache StreamPipes project.


Modify shard files to include dedup hint refs to other shards.

This PR adds shard dedup count tracking the shard file manager, which counts, for current dedup operations, how many times each on-disk shard gets referenced.  When shards are flushed to disk, this information is stored in a section in the shard as a list of hashes of other shards and dedup counts.  The format for the shard files regarding the intershard reference section is fully backwards and forwards compatible.
The tricky case here involves handling a large file that ends up generating many shards in one session.   Ideally, we would like to be able to dedup this file; however, the references are all to shards with in the session, which may be merged later on.   Without tracking intra-session references, subsequent small modifications to a large file will not see much dedup.
This PR solves this, including this use case, by:

Dedup counts against written shards are tracked, even in the same session.  These must be previously written shards.
The format of the staged shards now includes a counter.  Now staged shards are S####-HASH.mdb.   Note that any references in to one shard will always be to a shard with a lower counter number or a permanent (in CAS / cache) shard.
On upload, the merge process only merges sequential shards.  During the sequential merges, a hash map of remapped shard hashes is maintained.  The shard hint section is remapped on merge, or for staged shards appearing after a merge, the remap occurs.
Shard registering is gated on all shards successfully uploading instead of just the shard itself successfully uploading.  Thus all references in any registered shard will always be in CAS.

Succeeded by https://github.com/xetdata/xet-core/pull/66


OPAM 2.0

Main OPAM repository now requires OPAM 2.0:
[default] https://github.com/ocaml/opam-repository.git updated
[ERROR] The current version of OPAM cannot read the repository "default".
        You should upgrade to at least version 2.0.

[ERROR] Could not fetch repo

but ocamlbrew-install -r still installs OPAM 1.2.2. Do you have any plans to upgrade?

Hey!  Sorry for taking so long to respond.
I'd like to upgrade at some point but it'll be a little while before I have a chance to do so.  PRs are welcome if you find time!  Otherwise this is on my todo list, unfortunately behind many other things.


Contains fromIndex

Aligns with ES6’s contains.
Re: https://github.com/jashkenas/underscore/pull/1962
Re: https://github.com/jashkenas/underscore/issues/2061, 4f771e0

fromIndex is a really strange thing to have in a contains. Is there a good use-case for it — or is it only because you get it for free with indexOf? If there's no good reason, why clutter the API?


Not Listening [not supported]

installed using zip bat file,
So after running the bat the listener is not supported?

You need 3rd party INI file, like mine here.
Then run RDPWInst -r to restart the RDP server.  Make sure that Windows Defender and/or other AV products have an exception for the "C:\Program Files\RDP Wrapper" directory.

oh thanks


take clipping into account when determining scale factors

@mcilroyc  can you take a look at this. I'm still not happy with this function. and I feel like it does a lot of extra work, but I'm certain it shouldn't be ignoring the clipped case when determining scaleX and scaleY

this fixes https://github.com/adobe-photoshop/generator-assets/issues/391

I agree this fixes the referenced issue, and it seems correct.  I agree with your other sentiments though; this function generally makes me uneasy.  I think your var renaming is a step towards clarity though.


[In app purchase package] Impossible to test a purchase on iOS.

Hello, I try the example from in app purchase git, I use my bundle id, my purchase is display and work great on android when I clic on the product button. but on my iOS device I have nothing... no error, just nothing, even in the sandbox testfly. Perhaps It's normal to not show pop up to test purchase before production, but don't found the information.
I add capability of in app puchase in Xcode
I add my id in iOS preference->sandbox account
my in app purchase is approved
my bank account is ok
What can cause this ?
Thank you

@nitneuq33000 Hey, did the dialog showed at least once and any chance you have cancelled the purchase? If so, try running following code before calling buy method:
// Workaround to mark as finished failed transactions on iOS
    if (Platform.isIOS) {
      final queueWrapper = SKPaymentQueueWrapper();
      final transactions = await queueWrapper.transactions();
      final failedTransactions = transactions.where(
          (t) => t.transactionState == SKPaymentTransactionStateWrapper.failed);

      await Future.wait(
          failedTransactions.map((t) => queueWrapper.finishTransaction(t)));
    }

Other than that you can try to pass sandboxTesting: false into PurchaseParam to see if that works as expected.

How does one do this these days? SKPaymentQueueWrapper doesn't seem to exist anymore.


Library depends on Microsoft.Extensions.Http version 3.0

I can't upgrade this library to the 3.1.0 version because my project uses ASPNET Core 2.1. I tried to upgrade to Core 2.2, but I get several errors because I'm asked to add several Core 3 libraries and some of those conflicts with my existing project.
I tried to compile the project myself changing the dependency to Microsoft.Extensions.Http version 2.2 as it was on the previous release and I don't see any problems so far. Is there a reason for this requirement?
Greetings,

I just pushed a new package which drops this version. :)

Thanks!


tagparser: 12.1.0 -> 12.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/tagparser/versions.
meta.description for tagparser is: C++ library for reading and writing MP4/M4A/AAC (iTunes), ID3, Vorbis, Opus, FLAC and Matroska tags
meta.homepage for tagparser is: https://github.com/Martchus/tagparser
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 12.2.0 with grep in /nix/store/xz0542802wbbfrdakbzc0lx2ss5l82nl-tagparser-12.2.0
found 12.2.0 in filename of file in /nix/store/xz0542802wbbfrdakbzc0lx2ss5l82nl-tagparser-12.2.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

tageditor
tagparser

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xz0542802wbbfrdakbzc0lx2ss5l82nl-tagparser-12.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A tagparser https://github.com/r-ryantm/nixpkgs/archive/cb95804388c3b02a56ece8c5630fadba75c9d6cc.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/cb95804388c3b02a56ece8c5630fadba75c9d6cc#tagparser

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xz0542802wbbfrdakbzc0lx2ss5l82nl-tagparser-12.2.0
ls -la /nix/store/xz0542802wbbfrdakbzc0lx2ss5l82nl-tagparser-12.2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

tageditor
tagparser

Maintainer pings
cc @matthiasbeyer for testing.

Result of nixpkgs-review pr 324190 run on x86_64-darwin 1

Result of nixpkgs-review pr 324190 run on x86_64-darwin 1

1 package built:

tagparser


Match between different requests

Is your feature request related to a problem? Please describe.
I want to provide two different responses for the same request
Describe the solution you'd like
Make a generic endpoint where you can create a custom selector
{
  "_get":{
    "/my-path":[
    {
      "_id":"{id}",
      "_req":{
      },
      "_res":{
      }
    }
    ]
  }
}

when you make the following request:

Create

Method: POST
Path: __scenario
Body: { "id"[whatever]}
Response: -

set all the ids to whatever.
Also, we must have an endpoint to read the actual scenario and reset it:

Read:

Method: GET
Path: __scenario
Response: {"id":[whatever]}

Reset

Method: Post
Path: __scenario/reset
Body: -
Response: -

Done!
https://github.com/hector-js/stub-backend/releases/tag/v1.8.0


WIP-4655 MODFLOW model instance resource type remove

Pull Request Checklist:

[ ] Positive Test Case Written by Dev

[ ] Automated Testing

[ ] Sufficient User and Developer Documentation

[ ] Passing Jenkins Build

[ ] Peer Code review and approval

Positive Test Case

[Enter positive test case here]

METRIC
VALUE

https://sonarqube.cuahsi-workstation.com:9000/dashboard?id=hydroshare-4688

@sblack-usu Just a reminder to review this. Would like to get all remaining PRs related to deprecated model resource types merged for next release.


Add a favicon

Add a favicon

Please assign me to change the favicon and the title

Not needed right now


Ability of flow, flowFromDirectory and flowFromDataFrame in ImageDataGenerator to self generate class weights

If you open a GitHub issue, here is our policy:
It must be a bug, a feature request, or a significant problem with the documentation (for small docs fixes please send a PR instead).
The form below must be filled out.
Here's why we have that policy:.
Keras developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.
System information.
TensorFlow version (you are using): 2.6.0
Are you willing to contribute it (Yes/No) : Yes
Describe the feature and the current behavior/state. Addition of new attribute to generator in order to compute class weights in case of a class imbalanced dataset.
Describe the feature clearly here. Be sure to convey here why the requested feature is needed. Any brief description about the use-case would help. Addition of a new attribute and a method that will be available to the objects of this class. If the user wants to use class weights in model training then this attribute can directly be used rather than relying on any other library like scikit learn or method to compute class weights. This will be very useful in case of class imbalanced dataset as it will fasten up the process of training a model as well as they don't have to spend time searching how to get class weights. It will be also helpful for beginners who have very less knowledge regarding class imbalance issue and how to solve it.
Will this change the current api? How? es. It will add a new attribute to the flow, flowFromDirectory, flowFromDataFrame and a method that will compute class weights based on strategy provided by the user as in scikitlearn compute class weights.
Who will benefit from this feature?  It will benefit users with an imbalanced dataset to be able to compute the class weights within TensorFlow and not rely on any other library to compute class weights.
Contributing

Do you want to contribute a PR? (yes/no): Yes
If yes, please read this page for instructions
Briefly describe your candidate solution(if contributing): Addition of a new attribute and a method that will be available to the objects of this class. If the user wants to use class weights in model training then this attribute can directly be used rather than relying on any other library like scikit learn or method to compute class weights.

@MrinalTyagi, Can you please elaborate about your Feature and please specify the Use Cases for this feature. Thanks!

@chunduriv As in the case of an imbalanced dataset, one uses ImageDataGenerator flow methods to get the data, then he has to calculate the class weights in order to overcome the class imbalance problem. So due to that, he has to move to the sci-kit learn library in order to calculate class weights. It would be pretty helpful as when the user uses the flow methods to get the data, there providing a method that can calculate class weights either when the user intends to calculate them or during the flow of data itself calculating can take place. This will be used full in case of imbalanced dataset user doesn't has to depend on other libraries in order to do a small task that even Keras can perform easily.

@chunduriv any update on this?

@sachinprasadhs any update on the following?

Reading the comments, it is still unclear to me what this feature would do. Do you have some links that would be helpful in understanding? Examples with inputs and inputs?
Overall, I will say I am highly doubtful we would want to add something here. Rather then extending ImageDataGenerator, our focus is on improving our preprocessing layers. The preferred flow should be loading a dataset with tf.keras.utils.image_dataset_from_directory and manipulating the images with the preprocessing layers or custom user written layers.
Though I still am not fully understanding the feature request, so I may be missing something.

@mattdangerw Consider you have a class imbalanced dataset. In that case, you load the dataset using ImageDataGenerator and then calculate the class weights using some other library like scikit learn or use Counter to do the same manually.. It would be really handy if these weights are calculated curing the flow from directory and then accessible as an attribute for users to use. In case it's still not clear, I can share a draft pr and if you like it you can proceed with it otherwise close it in case it seems to be not necessary to the library.

Thanks for explanation! In this case, I think calculating the class weights manually is the correct thing to do. One of the reason's we are moving away from ImageDataGenerator and towards preprocessing image layers is that we can accommodate a lot more flexible workflows there, rather than ever expanding catch all functions. We do not want to be expanding the ImageDataGenerator or flow_from_* APIs right now. Thanks!


Add a file about IOP, Institute of Physics

Add a file about IOP, Institute of Physics, Chinese Academy of Sciences.
offical website (in Chinese):
http://www.iop.cas.cn/
Offical Graduate education website (in Chinese):
http://edu.iphy.ac.cn/

@HuangDongchen Pull request merged.
Please notice that free educational subscription for JetBrains tools is for students and teachers only, and is valid for using the tools for educational purpose only. If employees of this Institute who are not students, nor teachers, also need a license for JetBrains tools, they are eligible for an academic discount for the tools. They can get the discount by email to<EMAIL_ADDRESS>Thank you!

Thank you very much.


change term scm to git

Fixes #540 . Did not change core.no_scm under configuration sections. Also, did not alter the blogs. Let me know if any other changes are required.

Did not change core.no_scm under configuration sections.

Good call. Anything that reflects DVC core we don't change in docs lightly without that change actually having happened in the iterative/dvc repo first 🙂

@srishti-nema CIis failing and #1336 was open automatically because there are formatting issues in this PR. Please review the corresponding guidelines in our docs contrib guide (https://dvc.org/doc/user-guide/contributing/docs).

@srishti-nema CI is failing and #1336 was open automatically because there are formatting issues in this PR. Please review the corresponding guidelines in our docs contrib guide (https://dvc.org/doc/user-guide/contributing/docs).

Will go through and get back on this.

Sorry for the delay @srishti-nema this is great, thanks again!


Add column and entries for context length.

As discussed in #7, I added an additional column context length to the table and filled in the data for most of the models.
While it was unambiguous for most of the recent decoder-transformer with a standard positional embedding, here some exceptions:

T5 was trained with a sequence length of 512. However, its use of relative-attention theoretically allows for longer sequences. See the discussion here. As 512 was mainly used during training, I decided to use 512 as this is the value that makes effectively sense given the capabilities obtained during training
Replit Code uses ALiBi which allows for extrapolation of sequence during inference that are longer than the ones seen during training. As I did not find any other information on the maximum context length, I decided to use
infinity as the value. Not 100% sure though.
MPT-7B also uses ALiBi. According to their blog post and their GitHub, the models are trained on up to 65k inputs and can handle up to 84k. Therefore decided to use 84k
SantaCoder + RedPajama-INCITE: Could not find any context length information. Marked them with ?

TODO: Some entries are missing and some are still unclear to me; marked with ?.

Thanks for adding this, especially the ? where we're uncertain.


Update stale.yml

Doesn't seem to pass:

coverage/coveralls Expected — Waiting for status to be reported

Can @robdefeo bump it?


Problem when updating the Gateway environments for a published APIs

I have got 3 different gateway environments. When we add one Gateway environment and publish the API by the Publisher, it is visible under Available Environments in the store .

Think of a situation where we want to add different gateway environment while the api is published. for the 1st change it is changing the store with the correct environment

But if we change it again it wont allow to change. In the  APIM Store also it shows nothing under Available Environment.

Tried this with 3.0.0 beta and couldn't observe any issue. I think there could be a misconfiguration in the gateway endpoint configuration in your deployment.toml file


Cannot use the extension! macro

Describe the Bug
Not necessarily sure if this is a bug, or a problem on my end, but I tried replicating the "runtime extensions" example, and kept getting this compiler error:
error[E0271]: type mismatch resolving `<[OpDecl] as ToOwned>::Owned == Vec<OpDecl>`
   --> src/example_extension/mod.rs:20:1
    |
20  | / extension!(
21  | |     example_extension,
22  | |     ops = [op_add_example],
23  | |     esm_entry_point = "example:calculator",
24  | |     esm = [ dir "src/example_extension", "example:calculator" = "example_extension.js" ],
25  | | );
    | |_^ expected `rustyscript::deno_core::OpDecl`, found `deno_core::OpDecl`
    |
    = note: `deno_core::OpDecl` and `rustyscript::deno_core::OpDecl` have similar names, but are actually distinct types
note: `deno_core::OpDecl` is defined in crate `deno_core`
   --> /home/infi/.cargo/registry/src/index.crates.io-6f17d22bba15001f/deno_core-0.319.0/extensions.rs:180:1
    |
180 | pub struct OpDecl {
    | ^^^^^^^^^^^^^^^^^
note: `rustyscript::deno_core::OpDecl` is defined in crate `deno_core`
   --> /home/infi/.cargo/registry/src/index.crates.io-6f17d22bba15001f/deno_core-0.314.2/extensions.rs:180:1
    |
180 | pub struct OpDecl {
    | ^^^^^^^^^^^^^^^^^
    = note: perhaps two different versions of crate `deno_core` are being used?
    = note: this error originates in the macro `extension` (in Nightly builds, run with -Z macro-backtrace for more info)

Code
// example_extension/mod.rs
use rustyscript::deno_core::{extension, op2};

#[op2(fast)]
#[bigint]
fn op_add_example(#[bigint] a: i64, #[bigint] b: i64) -> i64 {
    a + b
}

extension!(
    example_extension,
    ops = [op_add_example],
    esm_entry_point = "example:calculator",
    esm = [ dir "src/example_extension", "example:calculator" = "example_extension.js" ],
);

Desktop (please complete the following information):

OS: Arch Linux (6.10.0-arch1-2)
Version: rustyscript = "0.9.0"

Can I see your cargo file? I think you're using a different core version then rusty is

[package]
name = "rustyscripttest"
version = "0.1.0"
edition = "2021"

[dependencies]
deno_core = "0.319.0"
rustyscript = "0.9.0"

You were completely right, changing deno_core to 0.314.0 solves the issue. Thank you!


The recording process was aborted by HSV with reason "CANCELLED"

My Camera is a Tuya camera. But with the help of Tuya IoT plattform I got access to RTSPS feed thats being re streamed into RTSP with a RTSP proxy server. As the picture shows below the RTSP stream uses h264 and acc so my understanding is that it should work with HSV. But i get the following error. Ive tried all 4 possible vcodecs without any luck.
[5/6/2022, 7:51:25 PM] [CameraUI] VIDEOANALYSIS: New message: Data: [{"zone":"region0","percent":25.35633659362793,"sensitivity":76,"dwell":60,"forceClose":3}] - Motion: detected - Camera: Dörrklocka
[5/6/2022, 7:51:25 PM] [CameraUI] Dörrklocka: Motion ON
[5/6/2022, 7:51:36 PM] [CameraUI] Dörrklocka: Closing recording process
[5/6/2022, 7:51:36 PM] [CameraUI] Dörrklocka: Motion OFF
[5/6/2022, 7:51:36 PM] [CameraUI]  WARNING  Dörrklocka: The recording process was aborted by HSV with reason "CANCELLED"
[HDS ::ffff:<IP_ADDRESS>] Delegate finished recording stream 1 without sending anything out.       Controller will CANCEL.
[5/6/2022, 9:19:26 PM] [CameraUI]  ERROR  Dörrklocka: FFmpeg videoanalysis process exited with error! (SIGKILL) - [NULL @ 0x55842c584f80] non-existing PPS 0 referenced  - Error while decoding stream #0:0: Invalid data found when processing input [h264 @ 0x55842c5b4280] non-existing PPS 0 referenced [h264 @ 0x55842c5b4280] decode_slice_header error [h264 @ 0x55842c5b4280] no frame!  - [NULL @ 0x55842c584f80] non-existing PPS 0 referenced Error while decoding stream #0:0: Invalid data found when processing input [h264 @ 0x55842c5bedc0] non-existing PPS 0 referenced [h264 @ 0x55842c5bedc0] decode_slice_header error [h264 @ 0x55842c5bedc0] no frame! [NULL @ 0x55842c584f80] non-existing PPS 0 referenced Error while decoding stream #0:0: Invalid data found when processing input [h264 @ 0x55842c63a540] non-existing PPS 0 referenced [h264 @ 0x55842c63a540] decode_slice_header error [h264 @ 0x55842c63a540] no frame!  - [NULL @ 0x55842c584f80] non-existing PPS 0 referenced Error while decoding stream #0:0: Invalid data found when processing input [h264 @ 0x55842c5b4280] non-existing PPS 0 referenced [h264 @ 0x55842c5b4280] decode_slice_header error [h264 @ 0x55842c5b4280] no frame! [NULL @ 0x55842c584f80] non-existing PPS 0 referenced Error while decoding stream #0:0: Invalid data found when processing input [h264 @ 0x55842c5bedc0] non-existing PPS 0 referenced [h264 @ 0x55842c5bedc0] decode_slice_header error [h264 @ 0x55842c5bedc0] no frame!  - [NULL @ 0x55842c584f80] non-existing PPS 0 referenced Error while decoding stream #0:0: Invalid data found when processing input [h264 @ 0x55842c63a540] non-existing PPS 0 referenced [h264 @ 0x55842c63a540] decode_slice_header error [h264 @ 0x55842c63a540] no frame! [NULL @ 0x55842c584f80] non-existing PPS 0 referenced Error while decoding stream #0:0: Invalid data found when processing input [h264 @ 0x55842c5b4280] non-existing PPS 0 referenced [h264 @ 0x55842c5b4280] decode_slice_header error [h264 @ 0x55842c5b4280] no frame!  - Error while decoding stream #0:0: Invalid data found when processing input

Some times I also get thoose errors:
[5/6/2022, 7:53:27 PM] [CameraUI]  ERROR  Dörrklocka: FFmpeg prebuffer process exited with error! (null) - [h264 @ 0x5654e955b680] co located POCs unavailable -

[5/6/2022, 7:53:53 PM] [CameraUI]  ERROR  Dörrklocka: FFmpeg videoanalysis process exited with error! (null) - Output file #0 does not contain any stream

{
                    "name": "Dörrklocka",
                    "motion": true,
                    "motionTimeout": 15,
                    "unbridge": true,
                    "hsv": true,
                    "prebuffering": true,
                    "forcePrebuffering": false,
                    "prebufferLength": 4,
                    "hksvConfig": {
                        "source": "-i rtsp://<IP_ADDRESS>:8554/mystream",
                        "vcodec": "libx264",
                        "acodec": "libfdk_aac",
                        "audio": false
                    },
                    "videoConfig": {
                        "source": "-i rtsp://<IP_ADDRESS>:8554/mystream",
                        "subSource": "-i rtsp://<IP_ADDRESS>:8554/mystream",
                        "stillImageSource": "-i rtsp://<IP_ADDRESS>:8554/mystream",
                        "rtspTransport": "tcp",
                        "vcodec": "copy",
                        "acodec": "libfdk_aac",
                        "audio": true,
                        "debug": true
                    },
                    "smtp": {
                        "email": "Dörrklocka"
                    },
                    "videoanalysis": {
                        "active": true
                    },
                    "mqtt": {}
                }

Because its a tuya cam I dont have a picture on camera settings except for below:

Environment

Node.js Version: v14.19.2
Homebridge Version: v1.4.1
Camera UI Version: v5.0.27 and also tried 28 (Beta)
Operating System: Ubuntu 20
Browser: Brave/Chrome

Update: I changed the video codec to libx264 and audio codec to acc and made my camera stream 30fps with key frame interval 120 and now I'm getting HSV recordings some times. I don't know why I get it sometimes and sometimes not. I can't find anything in the logs either. But some times the error about HSV getting cancelled is not shown. So some times HSV work and sometimes not while still having the same config.

@WattageGuy
try this config
{
  "name": "Dörrklocka",
  "motion": true,
  "motionTimeout": 15,
  "unbridge": true,
  "hsv": true,
  "prebuffering": true,
  "prebufferLength": 4,
  "videoConfig": {
    "source": "-i rtsp://<IP_ADDRESS>:8554/mystream",
    "subSource": "-i rtsp://<IP_ADDRESS>:8554/mystream",
    "stillImageSource": "-i rtsp://<IP_ADDRESS>:8554/mystream",
    "rtspTransport": "tcp",
    "vcodec": "libx264",
    "acodec": "libfdk_aac",
    "audio": true,
    "debug": true
  },
  "smtp": {
    "email": "Dörrklocka"
  },
  "videoanalysis": {
    "active": true
  },
  "mqtt": {}
}


PostgreSQL Unix Domain Sockets with DATABASE_URL

I can connect to a database just fine using this,
let opts = PgConnectOptions::new().host("/run/postgresql").port(5432);

However, I can't figure out how to get that into DATABASE_URL, without which the macros don't work.
The docs say,

If a host name begins with a slash, it specifies Unix-domain communication rather than TCP/IP communication; the value is the name of the directory in which the socket file is stored. The default behavior when host is not specified, or is empty, is to connect to a Unix-domain socket

That doesn't seem to be true, if empty like
DATABASE_URL=postgres://:5432

I get,

error: empty host

If I try to set it to a directory,
DATABASE_URL=postgres:///run/postgresql:5432/

I get

error: error returned from database: database "run/postgresql:5432/" does not exist

I found the solution,
DATABASE_URL=postgres:///?port=5432&host=/run/postgresql

There is no such thing as a port for a unix socket afaik, it should work the same without that.

For the record, Postgres does use the port for namespacing the socket file. This is likely used to allow multiple server instances to use a separate socket each.