test/test.c: Coverity-identified missing break in switch.

test/test.c: Coverity-identified missing break in switch.

Merged, thanks!


Profiling docs: clarify platform support

Description
Meta issue: https://github.com/getsentry/team-mobile/issues/191

We can close this issue then?


[BD-46] feat: connect SCSS grid-breakpoints in breakpoints.js file

new file created _extends.module.scss;
$grid-breakpoints moved to _extends.module.scss;
added SCSS export to breakpoints.js file;
breakpoints can now be edited from one file _extends.module.scss.

JIRA: PAR-741

Thanks for the pull request, @PKulkoRaccoonGang! I've created OSPR-6551 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

@PKulkoRaccoonGang Ah, I left some relevant feedback on https://github.com/openedx/paragon/pull/1211 which is also using this approach. I think it may make sense to close this PR in favor of that one at this point. Apologies for the delayed reviewed.

@PKulkoRaccoonGang Even though your pull request wasn’t merged, please take a moment  to answer a two question survey so we can improve your experience in the future.


Update Size.cs

Make Width and Height as Properties, which can be use for databinding as user wish

I don't like structure stuff are properties because this would have negative impact of performance

I understand both opinions. I am somewhat negative about this change.
As another perspective, "auto properties" are not supposed to be used.
https://stackoverflow.com/questions/28488057/what-is-the-structlayoutattribute-effect-on-properties-in-c

I don't like structure using properties because this would have negative impact of performance

It's not correct, it will be inlined at JIT time if you're using .NET Core 3.1+, so reading and writing to properties won't impact performance. Despite it I still don't like this change because it may affect the struct layout using auto-property. Instead manual properties should be used if property pattern is preferred.

It's not correct, it will be inlined at JIT time if you're using .NET Core 3.1+, so reading and writing to properties won't impact performance. Despite I still don't like this change because it may affect the struct layout using auto-property. Instead manual properties should be used if property pattern is preferred.

No, inlining is not happening every time, Debug build won't generally do inlining. This is a so important because we will debug and use the Size structure every day, some code like this:
for (int row = 0; row < size.Height; ++row)
    for(int col = 0; col < size.Width; ++col)
        // do something...

Would have ~300% negative impact on performance only because of the property call.


Task - Uniquify people - Number of uses not displayed.

It is dispayed when you search for the person.

But once selected, only question marks are displayed.

Use is only showed for when the person is in your project. I suspect you were in a different project here?  We can add a different total to show all use?

I definitely was in my project. I even used my name in search ;)


Multiple bases

Trying to read data from a second base. Nocodb naming for root level tables. Seems like it is just partially displaying the data. Just regular fields / column data.

i could narrow the issue down a bit. it is unrelated to multiple bases. tables with a checkbox field don't get displayed at all. all is good when i remove that field.

regarding bases / multiple root folders for tables. the only way to refresh them is by loging out at the moment. would be great to have a way to refresh them without loging out/in

tables with a checkbox field don't get displayed at all. all is good when i remove that field.

Thank you for the report.
I will check this issue together with the already reported bugs.

regarding bases / multiple root folders for tables. the only way to refresh them is by loging out at the moment. would be great to have a way to refresh them without loging out/in

I have created an issue to track this problem.
https://github.com/enm10k/nocodb-mobile/issues/32


fix: update to eye v9.6.11

fix: update to eye v9.6.11

:tada: This PR is included in version 12.3.8 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release
v12.3.8

Your semantic-release bot :package::rocket:


Feature/73 Change file encoding of NormalStateTest.cs

Issue : #73

[x] Build succeeds
[x] Test is passed
[x] Test name of NormalStateTest is shown normally on AppVeyor

参考: 対応前

直ってた.


Mask of a Thousand Faces

text: ruling 3 is misleading, as some inherent modifers are subject to mask restriction, notably stealth (see rulign 4) these should be rewirtten to make this cldear
link: https://groups.google.com/g/rec.games.trading-cards.jyhad/c/WUWh7AdooDU/m/vojisZMCSnsJ

I don't understand.  How would you suggest to reword things? Just change the order (3 before 4)?


Can't get extension to work

Neovim version NVIM v0.5.0-dev+950-g5ce328df4
Loaded the plugin in ~/.local/share/nvim/site/pack/*/start/lsp_extensions.nvim
This is the folder structure
.
├── examples
│   ├── dart
│   │   ├── closing_labels.lua
│   │   └── outline.lua
│   └── inlay_hints_inline.lua
├── LICENSE
├── lua
│   └── lsp_extensions
│       ├── dart
│       │   ├── closing_labels.lua
│       │   └── outline.lua
│       ├── init.lua
│       ├── inlay_hints.lua
│       └── telescope_references.lua
└── README.md

and in my init.nvim looks like this:
autocmd CursorMoved,InsertLeave,BufEnter,BufWinEnter,TabEnter,BufWritePost *.rs
\ lua require'lsp_extensions'.inlay_hints{ prefix = '', highlight = "Comment" }

But the type hints are not showing for Rust files - I have setup Rust analyzer as well, the build-in LSP features are working properly. Any idea on what else to look?
Many thanks

Having the same problem here. Inlay hints are not showing no matter what.

No description provided.

I'm also having this issue, unfortunately.  I'm using the latest version of neovim and rust-analyzer (the latest commits from github as of this writing).   I should also have the latest neovim/nvim-lspconfig and nvim-lua/lsp_extensions.nvim (via running :PlugUpdate).
I'm testing this by loading up the following file in neovim:
struct Foo {
    a: u8,
    b: bool
}

pub fn foo() {
    let b = true;
    let _ = Foo {
        a: 0
    };
}

I have the following autocmd:
autocmd CursorHold,CursorHoldI *.rs :lua require'lsp_extensions'.inlay_hints{ only_current_line = true }

I know that rust-analyzer is connected because I see the error line 8 (about the missing field b).  But it navigate my cursor to line 7 (let b = true;), I expect to see some inline type hint, but I don't see anything.   Running :lua require'lsp_extensions'.inlay_hints{ only_current_line = true } manually also doesn't do anything.

Where are you expecting there to be hints with this sample? My language server doesn't return any hints for this at all. Are you sure that you want to use only_current_line? If you're using that there could be other hints in the file but you could be looking at a line that doesn't have any hints.

I was expecting type hints on line 7 (which is let b = true).   rust-analyzer with vscode will give me a hint that the variable b is type bool (since it is not explicitly typed, but can be inferred).  So I expected neovim to do the same.
But maybe let's flip this around -- Can you give me a small sample that will provide hints?  I'll test with your sample and can compare your output to what I see
Thanks!

Ah okay. Neovim doesn't support virtual text in between text so by default the only hint type that is shown is "ChainingHint". You can enable "TypeHint" and "ParameterHint" by passing in an enabled table. That would look something like this:
:lua require'lsp_extensions'.inlay_hints{ prefix = '', highlight = "Comment", enabled = {"TypeHint", "ChainingHint", "ParameterHint"}}
Here is a related issue https://github.com/nvim-lua/lsp_extensions.nvim/issues/14
If there are multiple hints on the same line then it looks like the first one is drawn and the others are ignored.
I was testing in rust-analyzer by the way.

Ah ha!  I'm so sorry for the noise, then (I could have sworn that nvim used to supposed this, but clearly I am mis-remembering).
Using a better test, I am indeed seeing the ChainingHints, as expected.  Thank you!

No problem! This is probably something that could be made more obvious with documentation. Maybe I'll put up a PR tonight. Hopefully this is @marcoths 's issue as well.

@PatOConnor43 Yeah your suggestion also worked for me, many thanks! Didn't know those hints were not enabled by default


Disable month (month view)

<datepicker minimum-view="month" maximum-view="month" :inline="true" wrapper-class="calendar" :disabledDates="disabledDates" v-model="date" />

disabledDates: {
                ranges: [{
                    from: new Date(2018, 7, 1),
                    to: new Date(2018, 10, 1)
                }]
            }

Shouldn't the code above disable July & August in 'month view'?

Yes, it works with a custom function of course but would be super useful if it works either with a custom array disabledMonths or when a range includes a month, I'll provide a non working example when I have the chance.
Thanks!

Yep that works, but it doesn't for highlighted dates, even with custom function...


Block gas analyzer updates if the UI doesn't open

Just stops it being funky if it gets blocked.

Fixes the gas analyzer, looks good to me.


clear spec cache to avoid sporadic mismatch

Should fix the sporadic failure in the CI #357
The issue: f90wrap uses getter and setters to access the F90wrapped FORTRAN arrays, and the logic is as follows:
handle = get_specific_array_handle(stuff)  #pointer to the array
if handle in self._arrays #dict with arrays and handles:
  return self._arrays[handle]
else:
  array = get_array_in_complicated_f90wrapway(stuff)
  self._arrays[handle]=array
  return array

Now for the race condition: If spec has run before, and the array has been accessed before (put in cache), and by happenstance the handle remains the same, python will return the cached array, and not access the FORTRAN memory.
The handle is basically the pointer to the array, cast as an int. It is unlikely to be exactly the same EXCEPT when a conveniently shaped hole has just been emptied in memory by deallocation.
This also explains why the fault is mostly seen in CI, as they have much smaller memories, and are more likely to write to the same location. But this is handled by the CPU and not reproducible.

I don't see how this is a race condition. We don't have multiple cores modifying the same area of memory here, do we?
Wouldn't self._arrays[handle] be out of bounds or return a not found exception if the handle is not in _arrays?

@andrewgiuliani you are right, this is not a race condition, excuse my ignorance.
F90wrap works in a funny way (I don't completely understand it), but the cache is only cleared when the python kernel quits. It sets up links to shared FORTRAN memory that persist until the kernel exits.
Normally you only run a single simulation, and the kernel quits when the optimisation has finished, it is only in testing that many many many SPEC instances are created and destroyed.
For example in
from simsopt.mhd import Spec
myspec1 = Spec('firstfile.sp')
myspec2 = Spec('differentfile.sp')

print(myspec1.allglobal.ext)
>>> differentfile

the Fortran arrays in myspec1 and myspec2 are the same.
This is a limitation of f90wrap and the above code should not be used. The best we can do is make sure that loading a new state runs correctly.
Yes this is a memory leak when many Spec objects are initialized in the same kernel session, but I don't see how to avoid it.

When you clear the cache, is it possible to run a call on the FORTRAN side to deallocate the allocated arrays referenced in the cache?
If not, I would suggest that this anomalous behaviour should be mentioned in a docstring somewhere.

@andrewgiuliani This is not possible with the current implementation of f90wrap, and I am not sure if desired. It is meant to wrap existing programs, giving you access to the memory as they run, with the possibility of muting existing arrays. Forcing deallocation on the FORTRAN side from the python side would alter the program it is wrapping.
It is certainly a bug in the implementation that a handle collission (that is the right term!) is likely to occur, if arrays are deallocated and immediately afterwards allocated on memory-constrained systems, but this is at the core of some design choices made for f90wrap, and not something I feel comfortable fixing.
The current PR fixes the anomalous behavior that was occurring (that the cache kept accumulating), and this fix, though a bit draconian, prevents such behavior (and since the collision could occur for every accessed array, it is the right thing to do).
I will probably open an issue on the upstream f90wrap, but this will take a while as the whole numpy2.0 migration has left me very little time for science, and I have some QUASR configurations to calculate tangles in! ;)

I would have thought that a deallocate all function could be written in on the Fortran side and called from python.
In any case I think that this is great that the bug has been identified!

@smiet , can we have a zoom call to understand what is going on? I am not getting the full picture from your description.

At the least can you talk to the f90wrap developer, who might have encountered this issue before? There should be some mechanism in f90wrap to clear the cache.

@mbkumar yes, let's zoom tomorrow (Monday), was away from internet this weekend. Can you set it up? I'm having a little trouble with email on my phone right now, available all your morning

I'd like to be present during the zoom too to better understand the problem

Some notes of the discussion resulted in issue  #434.
All tests are passing consistently, this PR doesn't solve the root cause, but it applies a fix to stop a known bug. I suggest we move further discussion of this topic to #434 and merge this fix so we can stop seeing sporadic failures in our CI. @mbkumar @landreman @andrewgiuliani


chore(cheatsheet): fix double banner issue

Each page is designed to have a single banner; adjust the cheatsheet to follow this convention. Also eliminate the article nested within the l-conent div.
Propagated changes/cleanup to JS and Dart.
@kwalrath, cc @ericjim

LGTM


feat(md-3348): freeze first column android

:tada: This PR is included in version 1.1.0-alpha.34 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Not Detect Video File ?

Thanks for making this useful program!
When I try to use this program, the video is not detected.
It is the same situation in GithubAction. Am I using it the wrong way?
%env CHANNELS=3blue: https://www.youtube.com/channel/UCYO_jab_esuFRV4b17AJtAw

!ia-yt -S

--------------------------------------------------------------------------------
3blue: https://www.youtube.com/channel/UCYO_jab_esuFRV4b17AJtAw
--------------------------------------------------------------------------------

!ia-yt

Videos: 0it [00:00, ?it/s]

I solved it. The cause was that I didn't make a database and collection in mongodb. I'm sorry for asking a rudimentary question.

I solved it. The cause was that I didn't make a database and collection in mongodb. I'm sorry for asking a rudimentary question.

No problem! Glad that you solved it!


[REQUEST] Standardized hot-key for common command for all/most languages

Describe the feature
A shared/standardized set of key binding for common commands/operation of different language major mode (e.g. jump-to-definition, jump-back, compile, run, evaluate)
Status Quo
Currently, each language has its own key binding,  e.g:

for TypeScript: C-c C-t is bound to tide-jump-to-definition ; C-t is bound to jump-back to previously marked buffer
for Golang: C-c C-j is bind to godef-jump; C-o is bound to jump-back to previously marked buffer
for Rust: no hot key defined for racer-find-definition

Wish list
Ideally, developers should not have to remember different sets of hot keys for different languages, and it would be nice to

standardize the binding
expose customization interface for devs to change those command to hot-key of their own choices (idk, if they come from vscode, then they might already get used to some hotkeys)

caveats
As for downside of this is that this standardization layer might cause conflicts in hot keys with the native language.el, so would be nice to have a pop-up buffer for resolving conflict if accidentally customize the bindings into one.

A standard already exists for many of these commands, defined in the :config (default +bindings) module. Most of them are available under the leader prefix (which is SPC for evil users and C-c for non-evil users). Here are a few of them:
For evil users (scheme inspired by vim conventions)

Goto definition: gd (or SPC c d) -- this will invoke racer-find-definition in rust, godef-jump in go, tide-jump-to-definition in typescript, and so on. They will also fall back to more naive backends, if those fail.
Goto references: gD (or SPC c D)
Look up documentation: K (or SPC c k)
Jump forward/back in jumplist: C-i / C-o (ala the vim jumplist)
Evaluate code: gr (operator), gR (from normal mode, this evaluates the buffer. From visual mode, it replaces the selection with its return value)
Compile: there's SPC c c for compile and SPC p c for projectile-compile. The former runs the compile command in the current directory, and the latter runs it in the project's root.

Source
For non-evil users:

Goto definition: C-c g d -- this will invoke racer-find-definition in rust, godef-jump in go, tide-jump-to-definition in typescript, and so on. They will also fall back to more naive backends, if those fail.
Goto references: C-c g D
Look up documentation: C-c c k
Jump back in jumplist: M-, (this is an Emacs default, as far as I know, there is no jump forward, however. I'm open to suggestions for places to bind better-jump-forward -- we use the better-jump package to provide a universal jumplist)
Evaluate code: C-c e (evaluates line or region)

Source

I apologize there isn't much documentation on the matter (I'm working on it), but there are many standards in place. More than I can list here.

Ah, I forgot to talk about customizing your own keybinds. Emacs provides a library for doing so that you can use from ~/.doom.d/config.el, such as define-key KEYMAP KEY DEFINITION, e.g.
(define-key emacs-lisp-mode-map "x" #'dosomething)

Doom also provides the map! macro to make things a little easier, particularly for evil users.
(map! :map emacs-lisp-mode-map
      "x" #'dosomething
      "y" #'dosomethingelse
      "z" #'anotherthing)

You can find documentation on these with SPC h f <functionname> (or C-h f <functionname> for non-evil users). The documentation buffer will include examples on how to use them, and links to their definition.
Hope that helps!


GDScript: Fix subscript resolution on constant non-metatype GDScript base

Fixes #92534.
Resolves (partially) #89077.

#92035 exposed a bug with the static analyzer tries to get GDScript properties when they might be invalid (now there is a guard against it). This is due to the fact that when reducing subscript on a constant base, we use Variant::get_named(), while we should use the analyzer. In #79510, I fixed a related bug, but I didn't take into account that a constant value could have a broader type due to type hints and casting.
We also have a quirk that GDScript classes are both types and values. What causes collisions (#75392, #76414) is whether you mean a static class member or a non-static member of the GDScript resource (for instance, resource_path). Also, we don't have first class types and the is_meta_type flag sometimes leads to strange bugs.
Some users add unnecessary type hints to const-preload, which removes metatypes.
const MyClass: GDScript = preload("./my_class.gd")
var test := MyClass.InnerClass.new()
#                   ^^^^^^^^^^
# The specified type `GDScript` has no member `InnerClass`,
# but the value has and this is known in advance.

It might make sense to distinguish between a GDScript class as a type and as a value, but we proceed from the current state of affairs and strive to maintain backward compatibility. Now, for a constant GDScript base without the is_meta_type flag, the static members of the class are checked first, and then the non-static members of the GDScript class. For GDScript with the is_meta_type flag, only static class members are still checked.

Thanks!


[MINOR] Remove unnecessary code in DeltaSync#syncOnce

Change Logs
DeltaSync#syncOnce invokes DeltaSync#refreshTimeline which initializes an empty table and sets commitsTimelineOpt to an empty option.
Subsequently, the table is initialized again because commitsTimelineOpt.isPresent() == false. There is no need for DeltaSync#readFromSource to do the same thing again.
Fields that are accessible via methods are also removed as parameters for the DeltaSync#readFromSource method.
This PR is meant for cleaning up these "dead" code to avoid confusion.
Impact
Describe any public API or user-facing feature change or any performance impact.
None
Risk level (write none, low medium or high below)
If medium or high, explain what verification was done to mitigate the risks.
None
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@hudi-bot run azure

Good catch @voonhous


ENG-317 implement mcr contracts

Changelog

Creates MCR contract
Adds basic essential test cases for the MCR contract

Testing

Adds the tests: testUpdateEpoch,testHonestValidatorsCommit, testDishonestValidatorsMinorityCommit

To run the tests: cd protocol-units/dispute && foundry test
Notes

This branch was cut from https://github.com/movementlabsxyz/movement/pull/42 Once this is merged, the diff will make more sense.
Does not implement over our staking contracts as these have not been created yet.
I've assumed that we are not supporting chain state reversion and Groth16 verification for this iteration of MCR, so I've omitted that logic. We did discuss using this system as a fail-safe strategy in case network participants decide it is worthy to revert chain state for whatever reason, but as mentioned, focusing on core MCR logic for now.

@0xmovses These changes are mine to make.

@0xmovses can you review when you get a chance?

@0xmovses available for review again.

@musitdev this is the current state of the contract against which you'll want to implement the client.

cd ./protocol-units/settlement/mcr/contracts && forge test
sh: line 1: forge: command not found
error: Recipe `mcr-contract-tests` failed on line 7 with exit code 127

CI failing, after that's fixed this looks good.

I'd be inclined to not run the long running test for CI something like forge test --no-match-test <test-we-don't want>

@0xmovses the long-running test is now like 5 seconds haha.
In general, I like breaking short tests, i.e., "Checks" and longer tests "Tests," into separate workflows. But, I do want think we want this pipeline running e2e tests. There's a lot that can go wrong which we really don't want to miss from testnet on. We can afford to wait 30 minutes to an hour.


Ask Emma to join Operations Team, ideally Admin and Marketing Teams as well

@resbazaz/festival-operations : Instructor/speaker & helper organization, social events
@resbazaz/festival-administration : Create documentation, Data Management, Cross-Campus facilitation
@resbazaz/festival-marketing : Social media, flyer design, website content & management, venue contacts

Context: https://github.com/resbazaz/festival2023/wiki/Meetings---Admin-Team#2023-03-15

Emma is currently working with us on Operations

ResBaz AZ Flagstaff team (@egreich, Alicia, and Kat) followed-up with via emailed 3/16/23 and invited to join sub-committees.


add test pattern parameter to just dev

This allows us to do just dev some_test_to_run (in addition to just dev).

@matthandlersux: Added something to the readme.


UAI 2023 acceptance rate

From all 778 complete submissions, the program committee finally accepted 243 papers for the conference, resulting in an acceptance rate of 31%.
Thanks!

Updated! Thanks for your information.


Problem with importing dlib

I have problem with installing dlib. It seems that dlib is incompatible with other packages of this repository (pytorch and cuda).
When I try to install dlib with pip install dlib, I get this error:

ERROR: Failed building wheel for dlib

I have also tried different conda installation for dlib, such as: conda install -c conda-forge dlib , conda install -c menpo dlib , conda install -c conda-forge/label/cf201901 dlib , conda install -c conda-forge/label/cf202003 dlib , but I get the following error:

Output in format: Requested package -> Available versions The following specifications were found to be incompatible with your system:  feature:/linux-64::__glibc==2.17=0  feature:|@/linux-64::__glibc==2.17=0  Your installed version is: 2.17

I created a clean conda environment and right after installing python, I could easily install dlib with conda and I could import it correctly, but then I couldn't install pytorch, there were some incompatible packages. If I first install pytorch, then I cannot install dlib, and if I first install dlib, then I cannot install pytorch. The command that I use for installing pytorch is:

conda install pytorch==1.7.1 torchvision==0.8.2 torchaudio==0.7.2 cudatoolkit=10.1 -c pytorch

The other packages that I use are: python=3.6, GCC 7.3.0, libgcc-ng=7.3, regex-2018.11.22, tqdm-4.62.2, ftfy-5.3.0, matplotlib-2.2.2, numpy-1.15.2.  The conflict just happens between pytorch and dlib installations.
The installation of dlib doesn't exist in the conda environment link of this repository. In this code you explained the dlib installation separately. I'm wondering whether you used a different environment for that code or you have experienced the same error for installing dlib and pytorch in a same conda environment.
Thanks for sharing your fantastic work.

Hi @denabazazian
I haven't come across issues with the installation of dlib. Were you unable to install it correctly by using the steps specified in the script you linked above within the conda environment?
I was able to install it using the conda environment I linked to this repo, but this was a while back. So if you are still unable to install it in the conda environment of the repo using the steps in the script I will try creating a clean environment to try to recreate the error.

Many thanks @yuval-alaluf for your reply.
I made another clean conda environment by the link in this repo (conda env create -f restyle_env.yaml). I could install dlib by running conda install -c conda-forge/label/cf202003 dlib right after creating the environment (I couldn't install dlib with pip). But, the problem is that cudatoolkit is not installed in the conda environment of this repo, therefore it is not possible to import pytorch with cuda. Hence, when I install pytorch with cudatoolkit=10.1, that incompatibility with dlib appears.
I searched more about this issue and based on this reference, it seems that dlib 19.17 is compatible with cuda 10.1 , but there is no conda installation for this specific version of dlib, and I cannot install dlib with pip, I get this error: ERROR: Failed building wheel for dlib every time.

Hi @denabazazian
Sorry for the late reply. I just had a chance to create a new environment using conda env create -f restyle_env.yaml just like you did.
Then, I was able to install dlib using pip install dlib==19.21.1, but I am using cuda 11.1 on Ubuntu 18.04.5.
I am wondering if this is a problem with different CUDA versions?

Hi @yuval-alaluf , thanks a lot for your reply and your effort for re-creating the environment.
I am using Cuda 10.1 on CentOS 8. I believe, CUDA versions caused the problem. At the end, the only solution for my case was to run the align_face in a different environment with dlib, and saved the outputs locally. Then, load them with the main environment of restyle repository to complete the process.

Hmm. Not ideal but I guess it's a decent workaround. I'll try to look into dlib a bit more later to see if there is anything that can help.
For now I'm closing the issue, but I'll update you if I find anything useful.

I had the same issue with dlib, the solution was conda install -c conda-forge dlib - this worked while pip install (and pip install dlib==19.21.1) failed. Leaving this comment here in case anyone else faces this issue.


Allow users to pass custom 'CandidateSelectorControllingandCandidateSelectorControlled`

We have had two asks for custom ICE selection logic.
@lisay-yan in https://github.com/pion/webrtc/pull/2539 wants to effectively disable ICE. Just take the best candidate right away
@gbfarah wants to always take whatever the latest traffic coming in is in https://github.com/pion/webrtc/issues/2585
These are both greats ideas. However I am worried about the unintended side effects. I don't want to accidentally add a security/interoperability issue into Pion. I would like to support everyones use case though!
To do this I think we should make CandidatePairSelector a public interface (it is private now)
type CandidatePairSelector interface {
    Start(agent CandidatePairSelectorAgent)
    ContactCandidates(agent CandidatePairSelectorAgent)
    PingCandidate(agent CandidatePairSelectorAgent, local, remote Candidate)
    HandleSuccessResponse(agent CandidatePairSelectorAgent, m *stun.Message, local, remote Candidate, remoteAddr net.Addr)
    HandleBindingRequest(agent CandidatePairSelectorAgent, m *stun.Message, local, remote Candidate)
}

We will also create a new interface. This will allow us to selectively expose private APIs that users will need. We can add things as needed.
type CandidatePairSelectorAgent interface {
 GetSelectedPair()
 GetBestAvailableCandidatePair()
}

Users via AgentConfig can then pass in their CandidatePairSelectorControlling and CandidatePairSelectorControlled

Do you think this is an ok path forward @at-wat and @stv0g ?

I support the idea of making them customizable via interfaces. Its a good compromise of providing flexibility to the users without adding all these special use cases into the package itself.
Also, I think we can expect that users who implement their own versions of these interfaces really know what they are doing. This wouldnt be the case if we support these special features behind a simple boolean option.

Great! I will start a PR soon


Add property to skip HTML5 TOC file generation

Add html5.toc.skip property to disable separate TOC file generation in HTML5.
Usage
Disable index.html generation.
$ dita -i root.ditamap -f html5 --html5.toc.skip=yes

The name html5.toc.skip is basically negated already. So should we instead use property name html5.toc = yes | no to control whether TOC is generated or not.

I like html5.toc = yes | no better (with yes being the default). As you point out, it has logic that is easier to understand.
In the HTML5 plugin the TOC becomes index.html. What happens when html5.toc=no? What page becomes index.html, if any? The first topic? Is it (re)named index.html?
Finally, there is already an args.html5.toc. Will the be used for the same thing? If not, then it could be confusing and we should stay with html5.toc.skip.

Unfortunately we already have args.html5.toc, so we can't really add html5.toc.

In the HTML5 plugin the TOC becomes index.html. What happens when html5.toc=no? What page becomes index.html, if any? The first topic? Is it (re)named index.html?

It disables the generation of the TOC files, so there will be no index.html.

An alternative approach would be to only generate an external ToC file if the existing args.html5.toc parameter is set to specify a filename, and otherwise skip generation by default.
This would spare us an extra parameter and allow the current option to serve dual purpose, but modifying the behavior of an existing property could yield unexpected results in established workflows.

I think we should not break backwards compatibility, which means when you set nothing, you will still get index.html. Thus using args.html5.toc is not possible.
We already have an unofficial convention that *.file property name is a file path or file name; just like *.url for URIs and *.dir for directory path. Thus would not like to use args.html5.toc.file for a boolean value.
The old use of args. prefix for argument properties is not consistent and just makes property names longer. Thus I would not like to use args. prefix.

Rather than the negative html.toc.skip = yes | no I suppose we could go with html.toc.create = yes | no, with default of yes? I like that a bit better than the .skip version.
In general I try to avoid yes | no options because so often I end up needing a third alternative ... but this one is so straightforward that I'm not sure how, and with the existing args.html5.toc* parameters I have to assume this one would stay binary.

I think html5.toc.generate = yes | no is the best suggestion thus far, even if it's not perfect. I'll use that for now.

I think html5.toc.generate = yes | no is the best suggestion thus far, even if it's not perfect.

👍 That's probably good enough. We should be sure to clarify in the parameter description that it governs whether a separate ToC file is generated, to distinguish it from the existing nav-toc parameter, i.e.

Generate a Table of Contents file from the DITA map.

Changed. Note that this currently only works when the input file is a map. So if you use a topic as an input file and set --html5.toc.generate=yes, you will not get an index.html file with a single topic reference.

@jelovirt I assume that when html5.toc.generate = no, any specified values of args.html5.toc & args.html5.toc.class are silently ignored.
What about args.html5.contenttarget and args.html5.toc.xsl — are they still relevant in cases where nav-toc is set to full or partial?


Move Ranged into ruff_text_size

Summary
The motivation here is that this enables us to implement Ranged in crates that don't depend on ruff_python_ast.
Largely a mechanical refactor with a lot of regex, Clippy help, and manual fixups.
Test Plan
cargo test

Trying to fix these failures but my git push is hanging 😅

Oh god... I hope this is not clashing with my refactor xD

Oh god. Do you want me to do the rebase?

Oh god. Do you want me to do the rebase?

Go ahead, we should be fine for most files :)


feat: creating log bucket

:tada: This PR is included in version 2.5.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


new ApiResult response code 322

322 - connector with EVSE ID, but with different latitude/longitude exists

Great, thank you :+1:


Removing cosigners "-1" input

if you were to change the cosigners from 2 to 1 for example on the "Minimum signatures required", the app does not allow to input "1", for some reason you need to input "-1". I would say that "1" is more appropriate since the input asked is "Minimum signatures required". Using negative numbers could be confusing

Will change the field name for "Signature changes" and maybe add explanations then.
It is the number to add or remove from the current number of min signatures so in case of removal it is -1 signature

Field name is "Minimum signatures changes" in edit multisignature contract and the placeholder says "Number of signatures to add (n) or remove (-n) - Automated removals". Will see if I can be more clear on that. But I'm wondering, app is not automatically setting it to -1 if you remove a cosignatory ?

Yes, it does auto-fill it with "-1" only if you selected the m-sig account before. If you introduced the address to be removed it doesn't auto-fill.  Also looks a bit weird to look at "Minimum signatures changes: -1"

Don't you see the symbol "-" a little redundant if you already clicked on the red minus button

Yes but for changes like:

remove
add
add

If you type 1 there is not way to know if it is to add or remove a signature.
If it was one modification at the time I'd do it internally but not possible to know if multiple.
For the name of the field I just changed for "Relative change on minimum signatures", I'll see if someone have better ^^

Got you :)


Tld marko

Looks like this pr might have been intended for a team repo and not for the Udacity project base code.


BeakerX vs. SparkMagic?

I have colleagues telling me that BeakerX does not compete well enough with https://github.com/jupyter-incubator/sparkmagic and that AWS and Azure are using it for that reason, giving it more industry support. Can you provide any background information on this and/or some roadmap explaining if and when BeakerX wants to close that gap?

Do you have any info on this, including support for Apache Livy, please?


Removing dead link

Hey @jnv
just removing a dead project.
Cheers!

LGTM, thanks Peter!

No worries Jan!


Videos Page: When viewing by 'Project', the videos with no Project have no header

The talks that have no associated project are positioned first on the page. Instead, I would give them the 'Other' Category and put them at the bottom. Also, these talks currently have no header--we should put the header as 'Other'

Misname of title. fixed. :)

Tested on makeabilitylab-test.... looks good.


Fix missing CLI artifacts. Fixes #190.

All the CLI related artifacts are now constructed.

Can you tag a new release after merging? Thanks and sorry for the trouble.

Of course, thanks again for your work! 👍


[Feature request] Privacy policy link in FirebaseUI Auth sign-in flow

I understand that one can add a Terms of Service URL to the sign-in flow like so:
AuthUI.getInstance()
    .createSignInIntentBuilder()
    .setProviders(...)
    .setTosUrl("https://superapp.example.com/terms-of-service.html")
    .setTheme(...)
    .build()

However, since Google Play policies require the disclosure of how personal data is used in apps, it would be nice to increase the visibility of this information during sign-up/sign-in. I'd be happy to add a method setPrivacyPolicyUrl(String url) to the sign-in builder if there aren't any major problems with the idea.

@TheCraftKid thanks for the suggestion.  Let me ask a few people about this and get back to you.

Hey, @samtstern, what's the status on this?

@TheCraftKid thanks for the reminder.  I'd be happy to see this in version 2.0 if we can find the right place for it.  Right now we show the termsOfServiceUrl only in the RegisterEmailFragment.  Where do you propose putting the privacy policy URL?

I think the privacy policy should be where the terms of service URL is. App developers should be putting the privacy policy in their apps anyway, right?

@TheCraftKid sounds good to me, want to submit a PR?

@TheCraftKid If you're busy, I'm happy to work on a PR for you. Just give me the green light and I'll go for it! 😄

@SUPERCILEX Could you check #727 out to see if there's any glaring problems? I didn't know the best way to handle the text spans for the separate terms of service and privacy policy.
I still appreciate the offer even if I ended up doing it in the end. :smile:


CQ-4291308 Port to Spectrum: Column View: the checkboxes in the grid all lack programmatic names (AEM Sites)

Description
Port accessibility updates from Coral3 ColumnView
Improve WAI-ARIA design pattern to ensure that

An element can always receive keyboard focus even after
initialization.
non-contiguous elements can be selected when selectionMode is
multiselect
State of item is announced by assistive technology on select or
deselect.
Command/Control + A and Shift+Command/Control + A can be used to
select or deselect all.
Esc deselects all.
Navigating using arrow keys sets focus on appropriate item.
Add unit tests for keyboard interaction and accessibility
When a document item is active, the preview column is added as
description for activeItem.

Related Issue
https://jira.corp.adobe.com/browse/CQ-4274574,
https://jira.corp.adobe.com/browse/CQ-4291308
https://jira.corp.adobe.com/browse/CQ-4291309
Motivation and Context
Improve ColumnView accessibility for keyboard and screen reader users.
How Has This Been Tested?
Unit test, and extensive manual testing.
Types of changes

[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)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.

@adobe/coral-spectrum, @icaraps, @kozmaadrian, @martinischeery, @gknobloch

Could I get a review? @adobe/coral-spectrum, @icaraps, @kozmaadrian, @martinischeery, @gknobloch

@icaraps  @CezCz @kozmaadrian  could you please help with the review? We would like to have it shipped in the coming days

Ping @Pareesh @indra2gurjar


OCPBUGS-20794: bump x/net to v0.17.0

In order to address CVE-2023-39325.

What this PR does / why we need it:
How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality)
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

/lgtm
/label backport-risk-assessed

/approve

/jira refresh

/label cherry-pick-approved
/label qe-approved


'make pdk' fails on mpw-5b

Running 'make pdk' on a fresh mpw-5b branch results in error.
Removing temporary files from destination.
Done with PDK migration.
echo "Ended SKY130 PDK migration on "`date` >> sky130A_install.log
set -f ; ../common/foundry_install.py -std_format -target /tapeout/pdks/open_pdks/sky130/sky130A -clean
Done removing staging area.
touch /tapeout/pdks/sky130A/SOURCES
touch: cannot touch '/tapeout/pdks/sky130A/SOURCES': Permission denied
make[1]: *** [/tapeout/caravel_mpw5_prga/caravel/Makefile:1233: gen-sources] Error 1
make[1]: Leaving directory '/tapeout/caravel_mpw5_prga'
make: *** [Makefile:39: pdk] Error 2

This issue is getting addressed here https://github.com/efabless/caravel/pull/35, This error doesn't block you from using the pdk though. This error happens after building the pdk.

Thank you. The PR you mentioned fixed the issue.


Integrate editorconfig

@kidwm  I logging this issue so that we can keep track of the integration progress.  Let's make this thing work :)

Not sure about this. There is already an EditorConfig extension.
Which doesn't work on Windows, that's why I went to this one.
How would this extension manage to reconcile contradictory settings between Brackets' settings for whitespace, and EditorConfig's ones?


Register Phoenix College of Management within jetbrain environment

@ctalluitel101 Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

@ctalluitel101 You might miss my previous comment. Please react.

URL: https://phoenixcollege.edu.np/
Address: Maitidevi, Kathmandu, Nepal
Map: https://www.google.com/maps?ll=27.704138,85.332102&z=16&t=m&hl=en&gl=NP&mapclient=embed&cid=14864733395050658788
Course URL: https://phoenixcollege.edu.np/course/master-of-computer-studies-mcs

@philipto Is there any update for this one please

@ctalluitel101 Thank you for the clarifications!
Thank you also for your patience while waiting for a review and processing your request. Pull request merged.


Message "You are currently not logged in. You may want to do so now." leads to error page

On navigating to a page which the user doesn't have permission to view the following message is displayed: You are currently not logged in. You may want to do so now. The phrase do so is a link to /login. When using trac-github plugin the login path is /github/login. It can be seen here that clicking on do so links to an error page No handler matched request to /login.
Was the intent of using /github/login as the path to allow trac-github to function side-by-side with Trac's login module?

/login points to username/password authentication on code.djangoproject.com for which I originally developed the plugin. I'm OK with either removing the link and letting the user figure it out -- login links aren't far -- or pointing it to /github/login, as you wish.

The message with link is added by _send_user_error. The only possibility I see is to remove or replace  the link using JavaScript. I opened a ticket #12332 to discuss.

Another option would be to have a configuration option [github] use_login_path, and have it default to False. When True, the path /login would be used for the IRequestHandler.
Or we can get the same effect using a variable like [github] login_path_prefix, and have it default to /github.
login_path = '/%s/login' % self.login_path_prefix.strip('/')

Additional thoughts in trac:#12332:comment:3.

Proposed fix in #127.


Cron run at specific timezone and time.

Using Meteor 1.2 I need to change the timezone 'America/Chicago'. I have tried:
SyncedCron.config({
// Default to using localTime
utc: true // ( 'America/Chicago')
});
SyncedCron.config({
utc: false, (true/false both)
timezone: 'America/Chicago'
});
and also in
SyncedCron.add({
name: ....
timezone: 'America/Chicago',
.........
});
But no luck.

@garysxn The package does not currently support timezones.
There is a opened issue #74  regarding this so if you want you can help complete the pull request and then get timezone support.


import Base32, import CommonCrypto No such modules

Hi,
import Base32
import CommonCrypto
no such modules.
1- removed the CommonCrypto import (worked)
2- What do i do for the import Base32? The library is only used while parsing the secret.
Help :p

These dependencies are included in the framework via Git submodules, and are built as target dependencies. You need to:

Check out the project's dependencies with git submodule init and git submodule update.
Open the OneTimePassword.xcworkspace file. This workspace includes the OneTimePassword xcodeproj, and also the Xcode projects of the required dependencies, so they can all be built and linked together.

I've added instructions to the project README (#34) which will hopefully clarify the process for getting and building the dependencies.


how to send logs as an email-attachment using elastalert

I have a elk setup as docker containers and docker logs in syslog format are coming into elk stack and i am using elastalert for alerting purpose, I wanna send  an email alert of  all logs say with last 15 minute that matches a key-word in a particular field of the log as email attachment.

Which rule of elastalert is most appropriate to use with possible example

I also have a similar requirement. any plans implement this or already a solution available?

Any Update?.

Any Update?.

You can't do what you want. Customize ElastAlert if you want to. Elast Alert is no longer maintained.https://github.com/Yelp/elastalert/blob/master/elastalert/alerts.py#L402

You can't do what you want. Customize ElastAlert if you want to. Elast Alert is no longer maintained.https://github.com/Yelp/elastalert/blob/master/elastalert/alerts.py#L402

ElastAlert is dead.

ElastAlert is dead.


Tags for multi-line time series

I'd love to setup a time series where the GROUP BY field is actually used as a tag. Currently I can setup a multi-line time series as outlined in the README, but then all lines just show up with the label "value", whereas I'd love for each line to be labeled individually based on the GROUP BY.
Example of what I have now:

Each of those points corresponds to a different value of the GROUP BY field, and I'd love to have them as tags. Unsure if this is possible and I just haven't found out how but seems it isn't.
Thanks!

Closing as I had copied a panel that had a Merge transformation on it, hence the problem.


Support development against non-production headend for testing

Now that we're getting close to shipping, we need a way for developers to be able to test neon-cli and neon-desktop against a test headend cluster, rather than the production headend.
We're going to do this using optional environment variables.  I've added the KubeEnv static class that defines these environment variables and as well as the properties that return these values.  Let's plan on putting any new neonKUBE related environment variable code here.  I also added support for the new NEONKUBE_DISABLE_TELEMETRY, NEONKUBE_TELEMETRY_URI and NEONKUBE_HEADEND_URI environment variables ton start.
@marcusbooyah: I'be removed the KubeConst.NeonCloudHeadendUri and NeonCloudHeadendVersion constants.  KubeEnv.HeadendUri replaces the first constant and I've hardcoded "0.1" for the headend version in your temporary headend JsonClient implementations.  Now that modelgen recognizes the [ApiVersion] attribute, you can build a proper headend client where the API versions will be baked into the client.
I've also added a few $todo(marcusbooyah) comments near these temporary JsonClient uses.

DONE


Fix: Placeholder cleanup

Misc. link and word cleanup.

Merging this since it was reviewed in my most recent PR.


Add protolude template with hpack

Mostly a copy of the protolude template with hpack instead of a Cabal
file.

Woops, apologies, I missed the note in #81 that you're not accepting new templates at the moment.


When editing a draft, the form stays populated

When editing a draft, the form stays populated with unsaved changes when you click the cancel editing icon the changes I made are still in the form despite me not saving anything. Perhaps this is intentional?
https://user-images.githubusercontent.com/28573875/144205023-f1623a46-34ff-4872-840c-68740c13c099.mov

It's an artefact right now - what do you think makes more sense?

Store changes temporarily so people can come back to them (reload will reset)
Reset upon closing the edit mode and lose the edits.

I am not sure which one I'd prefer 💭

It's an artefact right now - what do you think makes more sense?

Store changes temporarily so people can come back to them (reload will reset)
Reset upon closing the edit mode and lose the edits.

I am not sure which one I'd prefer 💭

I was thinking about this too. I think the conventional pattern would be to ask for a confirmation upon closing/canceling, similar to what the browser does to keep you from losing your place in a form. I understand this type of verification adds some development time, so perhaps for now it is best to store the changes temporarily.
This is something we should definitely try to fix soon however.

Would this reasoning also apply when switching to a different module?
If so, that would complicate state management on the dev end. It's not impossible, but it seems like a potential day spent on a marginal UX improvement in this stage.
What do you think is the good route here?

It now does the exact opposite. Closing this issue as a result.


An annotation with any attributes (even with defaults) "cannot" be used with @Implies

(The word "cannot" is in scare quotes because much of the discussion below is about unpacking what that really means in our context.)
From a #259 comment by @Mooninaut:

An additional alternative for consideration: Annotation A cannot imply annotation B if annotation B has parameters

Here's one interpretation I've extrapolated from that line for discussion.
Given this example (whose three sections might be in the same file or in entirely different projects):
public @interface One {
  String anyParameter() default "any default"; // or other type
}

@Implies(One.class)/*X*/
public @interface Two {
  // may have params; example has none for brevity
}

@Two/*Y*/ some_program_element;

Then this issue's purpose is to decide what subset of the following should be true:

An analyzer that validates correct usage of JSpecify annotations, when it analyzes Two, must recognize a finding at /*X*/ to the effect that One.class is not a marker annotation type as required.

An analyzer or library that depends on whether some_program_element is conceptually-not-literally-annotated with @One must recognize the answer as "no".

An analyzer that validates correct usage of JSpecify annotations, when it analyzes some_program_element, must recognize a finding at /*Y*/ to the effect that a malformed annotation @Two is in use. (i.e., one level of recursive validation)

("must" is just short for "is non-conformant unless"; also "recognize a finding" does not mean the tool is in any way to report that finding to its users in any particular way or at all.)
You might have a 4 or 5 to add, perhaps.
Of course, what I call different analyzers here might all be the same one. I prefer to consider them independently, as currently discussed a bit at wiki/incorrect-annotations.

Tagged 0.3 for now because some outcomes could resolve other issues blocking 0.3.

Clearest argument I know for "NO/NO/NO"
If the One annotation type has no attributes, then is edited it to add an attribute with a default value, that should by rights be a safe change.
Clearest argument I know for "YES/YES/*"
Simply to get out of having to resolve issue #259. (How to resolve question 3 is more of a detail we could discuss later.) But it's not necessarily clear that doing this would be easier. For now I still cling to optimism.

Upon further consideration, I remembered that annotations in Java can be marked @Repeatable. It would be valid for such an annotation to be used directly, without @Implies (with or without arguments) multiple times. I don't think it should be an error for a non-marker annotation to be @Implies-ed if it is marked @Repeatable.
Otherwise, it should be an error (Y/Y/Y).
One could argue that it's OK to use a non-marker non-repeatable annotation with a default value as long as no single program element is annotated with both the default and a non-default value. I think that would require an undue level of sophistication in tools, but it's certainly possible.


Parameter pipeline not supported on ElasticSearchTarget

When defining an Elasticsearch Target to use a pipeline, I get the exception: Parameter pipeline not supported on ElasticSearchTarget
Example config:
      <target name="elastic"
              type="ElasticSearch"
              index="logs-test-${date:format=yyyy.MM.dd}"
              connectionStringName="ElasticsearchUrl"
              pipeline="test-pipeline">

Yeah that's a weird one, I don't remember it ever being a property but it was on the wiki page.
I've removed it from the wiki page.

Ah yes, I reverted the commit because it broke the target for versions without pipeline support.

Ah okay. Hmm would be really nice if it was.
What are your thoughts on brining it back but just documenting this is only for elasticsearch version > 5?


Create CI/CD workflow to test the installation using a docker image

This should be under .github/workflows folder.
The workflow should be able to test the installation on a docker-machine for all the steps listed.
The workflow must run a matrix strategy for Linux, Windows and macOS environments.

@FaithKovi here is another interesting issue. it will help us test https://github.com/badging/bot-scripts/pull/11 and future changes

@kaxada  sure I will

I would need more details on it too

So basically you are going to create a pipeline that successfully tests for successfully running the install.sh script on linux, MacOS and windows. You may need to make use of github environment variables in some cases.


Adds counter and removes extra variable

I'm also still thinking through the version of this contract vs the one in the examples branch where the mapping isn't stored in the struct - still a wip i think

Cool, I just wanted to get your opinion on this. Would the ReentrancyGuard not stop any reentrancy attacks?

Also do you know if there is any benefit to using the counter? I was just looking at some examples and it was in use, when I look at the code it is just an integer variable.


ERROR in ./node_modules/weaviate-client/lib.js

After installing weaviate-client for React
I get the following error
Compiled with problems:
ERROR in ./node_modules/weaviate-client/lib.js 672:11-24
Module not found: Error: Can't resolve 'fs' in 'C:\Users\User\react-projects\toing\smart-select-schema\node_modules\weaviate-client'

Hi @adlershai , this is the repo for the Python Client, could you please take it to the JavaScript Client? Here is the link to the repo: https://github.com/semi-technologies/weaviate-javascript-client

Sorry, my bad
On Wed, Mar 9, 2022 at 2:58 PM Stefan Bogdan @.***>
wrote:

Hi @adlershai https://github.com/adlershai , this is the repo for the
Python Client, could you please take it to the JavaScript Client? Here is
the link to the repo:
https://github.com/semi-technologies/weaviate-javascript-client
—
Reply to this email directly, view it on GitHub
https://github.com/semi-technologies/weaviate-python-client/issues/114#issuecomment-1062895683,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF5B4TRYJNTZRNPQBB4IUYTU7COANANCNFSM5P25CARQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***
com>

--


[AutoPR] eventgrid/data-plane

Created to accumulate context: eventgrid/data-plane

(message created by the CI based on PR content)


Implement http based merge in existing auto_submit revert code

Currently auto_submit revert is using Github graphql client to send merge requests but this is flaky and beginning to return cryptic errors when timing out.
Use http to send the request and verify that it works.
If it works modify the github dart lib and send Casey a pull request review. Then use that code as it simply makes an http request itself but limits the method to merge.

The bot account is used to make http requests.
Autosubmit bot is using the application authentication.
Auto approval is using the github account.

This has been implemented.


Basic changes to support poetry 1.2.0b3, no longer support Poetry 1.1.x

This adds support for poetry 1.2.0b2 while dropping 1.1.x support.
Might still need some work but seems to be working ok

@enpaul this is now ready for review.  Had a CI run over at: https://github.com/Callek/tox-poetry-installer/actions/runs/2638529975
(with a now-dropped commit that added support for CI on my branch for my own fork)

@enpaul Updated to support Poetry 1.2.0b3 which was just released.

1.2.0 has now been released, would be great to see this merged to get compatibility with it

My spidey senses tell me we'll see a release this coming Tuesday.

@Callek thanks for the PR! Much appreciated

Since Poetry 1.2 has been released and it broke backward compatibility 🤦, would be great to expedite this.


Breakup FhirIO class and file

FhirIO is almost 2000 lines long. This change breaks up the file into logical groupings:

FhirIOSearch -> Move FhirIO.Search into this, and move the FhirSearchParameters in
FhirIORead -> Move FhirIO.Read here
FhirIOWrite -> Move FhirIO.Write, FhirIO.Import and FhirIO.ExecuteBundles into here. Additionally make ExecuteBundles implement FhirIOWrite, cleaning up some excess code.

Also renamed all occurrences of FHIR messages -> FHIR resources & fixed some incorrect references to Hl7v2 in comments. Messages are an Hl7v2 concept, and are different from resources. (In Hl7v2, messages are stateless. FHIR resources are stateful).

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Note that this is a backwards incompatible change which will require all users of the FhirIO to update their code causing user pain.
The package is marked @Experimental so technically allowed but best to get feedback on<EMAIL_ADDRESS>and<EMAIL_ADDRESS>mailing lists.

Thanks! I sent an email to see if there is any feedback.


Feeback popup shows incorrect amount of available characters(twitter raised the limit today)

VSCode Version: Code 1.16.1 (27492b6bf3acb0775d82d2f87b25a93490673c6d, 2017-09-14T16:38:23.027Z)
OS Version: Windows_NT x64 10.0.15063
Extensions:

Extension
Author (truncated)
Version

better-comments
aar
0.1.3

Bookmarks
ale
0.16.0

project-manager
ale
0.21.1

ng-template
Ang
0.1.7

npm-intellisense
chr
1.3.0

path-intellisense
chr
1.4.2

open-html-in-browser
cod
0.1.21

githistory
don
0.2.3

gitlens
eam
5.3.0

auto-rename-tag
for
0.0.14

beautify
Hoo
1.1.1

vscode-git-tags
how
1.1.0

Go
luk
0.6.65

gitignore
mic
1.0.1

prettify-json
moh
0.0.3

vscode-versionlens
pfl
0.19.1

code-settings-sync
Sha
2.8.3

react-beautify
tai
0.3.0

vscode-wakatime
Wak
1.1.16

(1 theme extensions excluded)

Steps to Reproduce:

Click smiley icon(feedback) at the bottom right
Observe that it shows that you have 117 characters available

With new limit you should have 257 characters available, here's the blog post https://blog.twitter.com/official/en_us/topics/product/2017/Giving-you-more-characters-to-express-yourself.html
Here's a screenshot in case It's not clear what I am referring to.

Reproduces without extensions: Yes

The limit was not yet lifted for everyone.

Also, the limit only seems to be 280 for non-chinese, non-japanese input. So I am not sure how to best change this actually unless we can detect the language of the user.

unless we can detect the language of the user.

Yeah that's an issue, I guess you could show the limit based on VSC locale as it is available in Chinese, Japanese https://code.visualstudio.com/docs/getstarted/locales
It wouldn't be perfect as in the end it would depend on selected Twitter account language*(I assume it's based on that rather than characters that you input)*

@Jasius - yeah, I thought so too but apparently twitter's logic has become very convoluted. https://github.com/Microsoft/vscode/pull/35224#discussion_r151204969

I meant to utilize VSC locale :), checking for twitter locale would be too troublesome for such a minor feature.

No, i understood you, but it's not dependent on locale at all. Its dependent on the cgaracters you use. So, even a Chinese locale, when typing in English, can give you 280 chars. And even in the en-US locale, if you type English, but use double-width characters, then you'll only get 140 characters.

It's not actually Twitter locale that is used as the counter. Each character is counted separately, so mixed strings have a more ambiguous number of characters allowed. Each string has a sort of 'score' associated with it, and the score can be no higher than 280.
'abc' -> 3 points
'あああ' -> 6 points
'😀😀😀' -> 6 points
'あbc' -> 4 points
'😀bc' -> 4 points
You could implement the counter with logic like this, where characters are 2 points by default and can be whitelisted to be other point values. It seems that this would be a conservative route that leans toward false positives (strings marked too long, when they are actually okay).

 Also, given how their twitter-text API is designed (see link in my comment above), I get a feeling that Twitter might be open to experiment a little with their algorithm for counting letters or the character limit.


Publish to gh-pages

Hey,
I'm submitting a...

[ ] Bug report
[x ] Feature request
[ ] Documentation issue or request
I am looking for some help in publishing or deploy web application on to gh-pages. Often times, it will be useful for people who can quickly generate the application and then publish it on github to test the PWAs on their mobile devices for quick demos etc.
Current behavior
I am having to tweak the generated code to publish the code to github pages.
Here is the list of steps that I did to get it working.

Update the .gitignore to remove dist folder to the git repo
On index.html I had to replace the base with <base href="./" />. This is because the web application when running on gh-pages does not always start with root context. Which means / is not going to work on gh-pages.
Update the ServiceWorkerModule imports on the app.module.ts.

From:
ServiceWorkerModule.register('/ngsw-worker.js', { enabled: environment.production }),

To:
ServiceWorkerModule.register('./ngsw-worker.js', { enabled: environment.production }),

This is also to make sure the worker is working on gh-pages.
Expected behavior
I had to do it without any tweaks and make it simple for users to be able to publish the pages on github.
Minimal reproduction of the problem with instructions
Run the following after the scaffolding is complete on your project home directory.
$ npm run build --env=prod
...
$ git subtree push --prefix dist/ origin gh-pages
git push using:  origin gh-pages
No new revisions were found

Environment
$ which ngx                                                                                1 ↵
~/.npm-global/bin/ngx

$ ngx -version
          __   __
 _ _  __ _\ \./ / ____ ____ ____ _  _ ____ ___
| ' \/ _` |>   <  |--< [__] |___ |-:_ |===  |
|_||_\__, /_/°\_\ ENTERPRISE APP STARTER -~*=>
     |___/ v4.0.0

$ node --version                                                                                1 ↵
v8.10.0
$ npm --version
5.6.0
$ uname -srvpio
Linux 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 GNU/Linux

Others
Here is the link to the one I had just tried to publish on gh-pages. https://pwa.vpv.io
If this issue is accepted I don't mind submitting PR for the same.

The base routing configuration is made to work purely in HTML5 mode and needs a web server configured for it.
In the upcoming version, the --location-path=hash option will allow you to use AngularJS hashbang-style routing which works with web server not supporting HTML5 routing properly, such as github pages.
Using ./ for base-href import do not work if you hit F5 when you already navigated to another page or with more complex sub-routing, so it's still not ideal.
As for the dist folder being excluded it's a safe default, and changing it is not needed for publishing to gh-pages. You can use https://github.com/tschaub/gh-pages or https://github.com/angular-schule/angular-cli-ghpages to publish directly your dist folder, even as part of your NPM scripts.
For the service worker, it would need some testing (especially for the mobile use-cases) but I think it would be harmless to change it to ./ by default as it should always be in the same folder as the app.js bundle.
On another note, it would be a great fit for an addon like https://github.com/ngx-rocket/addon-firebase to prepare the scripts and the changes needed to deploy to gh-pages 😃

Sure. Thanks for the gh-pages suggestion and I am waiting for hash-path option.
Let me give a try for the service worker PR.
As I was going over the documentations on the generator I am more attracted and feeling good about it. Great work guys! Let me wait to understand the addons and if I think I am in hold of it, I will submit a addon.

Supported with #542


Added 'python' to the console command in contributing.txt for clarity

Hey Django team,
I've made a small but, I believe, valuable update to the contributing.txt file. Specifically, I added the 'python' prefix to the console command in the runtests.py section. This adjustment aims to enhance clarity and ensure a more seamless experience for contributors running tests using this command.
While I was trying to run my first test the 'runtests.py' command kept opening the test file without running the test. The addition of 'python' makes the command more explicit and user-friendly.
This helps contributors, especially those new to the project, to better understand and execute the testing process.
I have locally tested these changes to ensure they don't introduce any issues and that the modified command works as expected.

Thank you @iammrpresident for this proposal.
While I encourage being inclusive of the different development environments, this change only applies to Windows users, and also there are many other places in the docs where ./manage.py or ./runtests.py is used. Because of that, I think a better alternative would be to evaluate the adding of a single yet general clarification note for Windows users somewhere at the beginning of the docs.
What do you think? Would you like to make such evaluation and propose a change?

I'm not so familiar with non windows systems. Is it standard to run python scripts without python.
The tutorial seems to use python throughout.
https://github.com/django/django/blob/e412d85b4626bc56eb25206a40c3529162ce5dfc/docs/intro/tutorial01.txt#L131

Thank you @nessita for your feedback and suggestion.
I appreciate your perspective on the broader use of ./manage.py or ./runtests.py in the documentation.
I agree that a more general clarification note for Windows users, placed at the beginning of the docs, could provide a comprehensive solution. I'll evaluate this approach and work on proposing the necessary changes to ensure inclusivity for users across different development environments.
Feel free to share any additional thoughts or considerations.

Great question! @smithdc1
On non-Windows systems, it's common to run Python scripts by directly invoking the Python interpreter without explicitly using the "python" command. This practice assumes that the system has the appropriate Python version available in the environment variable PATH.
The tutorial predominantly uses the python command for consistency and clarity, especially for users who may be new to Python or different operating systems. However, in many environments, using python is interchangeable with invoking the script directly, like ./manage.py or ./runtests.py.
In the specific case of the proposed change, the addition of "python" to the command was aimed at ensuring clarity and consistency, especially for Windows users.
Feel free to ask if you have any more questions or if there's anything else you'd like clarification on.

I have updated the docs accordingly, @nessita kindly review.


Cache signatures

Overview
Not sure if this a good idea, but sometimes when you are having to play with a transaction to get it working, you might need to submit it multiple times with different gas values (such as if the gas price keeps rising or something), it would be great in this scenario not to have to call sign_transaction multiple times with the safe, since the request will be the same.
One potential solution is to "cache" the signatures for a given SafeTx hash, since those signatures are likely to continue being valid. You might also want to submit it to the Safe API if it fails the first time, so you can come back and execute it later.
Specification
No UX changes, it just caches by SafeTxID under the hood
Dependencies
n/a

As of #7, the following section was added to the code where a cache could be added:
https://github.com/ApeWorX/ape-safe/pull/7/files#diff-8248524771bdbba6496a80d00a31f24f9d9ec674ae92129bbd2b229d3bc8dbabR278
further research is needed to determine if the cache would be acceptable behavior to users


use default image if pack logo not available

Resolves: #1389

closing this PR per my comment in #1389


chore(deps): remove dependency on github.com/qdm12/golibs

[ ] Remove dependency on golibs/params and golibs/verification (in progress in branch rework-config)
[ ] Replace dependency golibs/logging with qdm12/golog
[ ] Inline github.com/qdm12/golibs/crypto/random/sources/maphash here

Done in ee208934641d74fe9b7c10e1cbe9f05f2e2a1aa5


Microsoft Office - Done

Dan, I love the work so far and thought I'd help out as I have been working on the same kind of project. I am developing an icon font of programs, coding languages, etc... so I have some of the same and some new ones.
Here is a link to the 3 main Microsoft Office Icons (Excel, PowerPoint, and Word): Microsoft Office
Here are their guidelines and some low-res logos: Trademarks

Will Microsoft's logo be in too? It's a super easy one, with four squares haha.

It’s much easier for me to close off requests if they’re listed individually. I’ll close this issue off and work from the following ones:

#221 Excel
#227 Microsoft
#222 PowerPoint
#228 Windows
#220 Word

Thanks @danleech. Great work on the set as a whole.


removes GOROOT from globalPassThroughEnv for local dev

My understanding is that this is not needed anymore - so just cleaning it up on the basis of that assumption.
Reminder: there is some Go code left in turborepo-lib/hash, but from what I can tell that's entirely separate from this.

This will cause cache misses for anyone who had this set after updating in the next release - but should impact should be small and it's nice to clean this up!


Migrate from TravisCI to Github Actions

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The CI failed due to test coverage drop. Pending on Anomaly Detection team to improve the test coverage.

Adjust the branch coverage to 0.6 in anomalymonitor resource pom.xml while working on the test coverage improvement.


docs(api): Add API docs

Furthemore, do something similar to
https://github.com/steveklabnik/simple-server/pull/36 but with Response
stuff.

Looks good to me!


Feature Request: Cancel embassy executor task / replace_spawn

Hello,
In my use case I would like to have something like embassy_executor::Spawner::replace_spawn, that will always succeed. If it cannot spawn a new task, it would cancel some already existing one.
I am sending messages to a network, and it would be easier to do replace_spawn then writing that logic inside task itself.

On a similar note. I found it would be handy to have access to pausing, resuming, restarting and cancelling tasks by getting a handle.
I have a project when I need to restart about 12 tasks and if I could cancel and recreate the tasks it would be much neater than having to have the same large blocks of code 12 times in each task.

On a similar note. I found it would be handy to have access to pausing, resuming, restarting and cancelling tasks by getting a handle.
I have a project when I need to restart about 12 tasks and if I could cancel and recreate the tasks it would be much neater than having to have the same large blocks of code 12 times in each task.

I have a similar use case, but I would need some of my tasks to be able to finish the slice of work they are on and/or cleanup before terminating.


Update Demo App

Hello,
As a proposal, I'd suggest the following:

Updating the Demo App to Swift 4.2
Resolving the warnings that appear in Xcode 10
To me it does not make a lot of sense the Demo App to have Pod dependencies when all the files are already in the repo. Wouldn't it be better to have the App compiling the local sources instead of having a pod dependency?

Thanks (it's just a suggestion)!

Hello,
thanks for the suggestions
Do not hesitate to Pull Request if you have converted the demo app
For the demo app, podfile with " :path =>" is used for this purpose ie. development pod


Add stmcli to projects

Hey!
I'd like to add stmcli, a command line application to get STM bus schedule and metro status.

This is awesome!


ENH Factorization Machine classifier

This PR adds a factorization machine classifier.
I am going to leave the regressor for another PR.

Oh nice.  I've been looking for a good TF FM implementation :)

Hi @mdagost! We only have a classifier. A PR for the regressor is welcome!

Just making sure: there's no way to write eqn 1) here http://www.algo.uni-konstanz.de/members/rendle/pdf/Rendle2010FM.pdf in matrix format, is there?

Yeah equation 1 is the slow version. The TF I have is the best I know of.

LGTM


Abort previous compression job

Currently, if I change a few options, I have to wait for each of the jobs to complete. Ideally it should abort anything in progress and compress at the latest settings.
Not sure what's the best way to do this, but AbortController is available in some browsers, and pretty easy to polyfil.

I don’t know if we can abort running wasm code short of terminate()-ing the worker it is running in

Need to investigate how comlink-loader deals with that, tho ;)

indeed.

@surma are you happy to look at this at some point? It feels like this might need to be a comlink thing. As in, you call terminate() through some comlink API, and it rejects any unresolved promises, then terminates the worker.
Then feel free to assign to @developit to look at the comlink-loader bits.

I’ll coordinate with @developit. Not sure where this logic belongs. Gut says comlink-loader

The bit that made me think that there'd be a root comlink part is aborting (rejecting with AbortError) in-flight promises.


comments to Vegar's samples

Section 1
Feedback and questions  on https://github.com/vegarringdal/jwt-node

More explanations on install section. Where is the file  config.sample.js and why adding this to the root.

If is is sufficient to run npm install followed by gulp watch - where is the need to run jspm install gone (obviously because of the fuse plugin added here, so I need a lot more information about this plugin to create the needed tutorial article that will be a part of our future release.

Need all  good references to the information explaining these two lines as this is also a novelty for most members of the Aurelia community/

likely more items to be added here ...

1:
Ive removed that part to simplify it, this was the part where you added the nodeMailer config.
Updated the readme and added step by step guide.
https://github.com/vegarringdal/jwt-node

2:
There is no jspm install since Im using fusebox bundler/loader to build/bundle here:
https://github.com/vegarringdal/jwt-node/blob/master/frontend/build/watch.js#L44-L109
Im not much fan of webpack,config is weird(this migth just be me 😂 ), loved jspm, but is beta forever, and slow and hard compared to fusebox, and using jspm install etc is annoying compared to just using npm.
So we are also using custom loader for fusebox to work
https://github.com/fuse-box/fuse-box-aurelia-loader
This loader is almost the same as old webpack, Ive modified it a little to use fusebox imports instead
Some features of Fusebox can not be used with this Aurelia loader

rollup
quantum
code splitting

For more info about fusebox, see github and docs
https://github.com/fuse-box/fuse-box
http://fuse-box.org/
There is also an alternative loader here:
https://github.com/arabsight/aurelia-loader-fusebox
I havent used it, but @Thanood have, think its good too, might even be better then the one Ive added to fusebox repo 👍
For more information about the aurelia-auth-plugin see here:
https://github.com/vegarringdal/aurelia-auth-plugin
I have not created very much docs, I need to do this

3:
Its pretty much the same as in normal skeletons, tell Aurelia to start..
Other skeletons:
 aurelia.start().then(() => aurelia.setRoot());
https://github.com/aurelia/skeleton-navigation/blob/master/skeleton-typescript/src/main.ts#L15
https://github.com/aurelia/skeleton-navigation/blob/master/skeleton-esnext/src/main.js#L15
Only I used async/await instead of .then()
await aurelia.start();
await aurelia.setRoot('app');

Best I can give you is this, since I do not every detail of the inner workings here..
http://aurelia.io/hub.html#/doc/article/aurelia/framework/latest/app-configuration-and-startup/4


Fix gcloud docs for ssh-key mounts.

The current volumeMounts config does not work, mountPath only accepts a folder and not a file unless you use "file projection" secrets. Also, in kubernetes YAML you can use octal defaultMode: 0400 to be clearer about permissions (instead of defaultMode: 254 which is required with kubernetes JSON).
Also added a quick note about how to do container startup scripts.

Thanks again for the PR! Much appreciated. Those changes look good.


Illegal string offset

↵Warning:  Illegal string offset 'lastlogin' in /home2/andreilg/public_html/clientes1/login/checklogin.php on line 24
↵
↵Warning:  Illegal string offset 'attempts' in /home2/andreilg/public_html/clientes1/login/checklogin.php on line 30
↵
↵Warning:  Illegal string offset 'attempts' in /home2/andreilg/public_html/clientes1/login/includes/loginform.php on line 12
↵
↵Warning:  Illegal string offset 'lastlogin' in /home2/andreilg/public_html/clientes1/login/includes/loginform.php on line 15
↵
↵Warning:  Illegal string offset 'attempts' in /home2/andreilg/public_html/clientes1/login/checklogin.php on line 42
↵{"username":"ilges","response":"true"}"
Running the Login system on localhost (php 5.6.24) everything works fine. Bur running on my webserver (php 5.6.27) I got a lot of this Illegal String offset.
And this error is preventing the page to be redirected. If I refresh the page or go manually to the index, everything else is working.
Could this be some compatibility with the php version?

I'll look into this. I did write it in PHP 5.6 and never encountered that
error before... thanks for bringing it to my attention!
Side note, you should really look into upgrading to PHP 7, it'll nearly
triple your performance speeds in many circumstances.
On Mon, Nov 14, 2016 at 9:26 PM, ilges<EMAIL_ADDRESS>wrote:

For now, I removed the feature of login attempts. Now, the page is
redirected to the index as it should.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fethica/PHP-Login/issues/42#issuecomment-260528804,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH24As4ptfMsADyaWdjFkFdhOpFz4yJPks5q-RhagaJpZM4Kx78-
.

--

bradley david

in dbconf.php
changing
$tbl_attempts = $tbl_prefix."loginAttempts";
to
$tbl_attempts = $tbl_prefix."loginattempts";
fixed the problem


[Subtask] Optimize the UI design for metalake

Describe the subtask
Today's Web UI uses a metalake list as the home page. While metalake is a logiacl container similar as an organization or tenant. It is not that frequent to manage the metalake. So I suggest to give less space and chance to show up the metalake list. In most of the time, user should see the catalog list after login to Gravitino.
Parent issue
#2418

@LauraXia123 Laura, would you like to work on this?

@shaofengshi Ok, I assign myself the issue


wg-performance Status Update 2021-06-07

cc @ampproject/wg-performance
What was accomplished
Lessons Learned
What's Next

What was accomplished

Explored Maui.

[x] Road to Hana.
[x] Surfing in Lahaina

Explored Kauai.

[x] kalaluu trail
[x] Waimea Canyon

Big Island

[x] Walk on volcano
[x] See the Milky Way

Lessons Learned
Taking a break is A+
What's Next

server rendering amp components

What was accomplished

SSR fluid layout: cl/375756231
Better optimize WebP image generation during ingestion: cl/375986686
Ingestion only branch for image experiment: cl/377110349
New experiment framework for faster SSR experiments: cl/376059362, cl/377108647
Compress hot-patched amp-geo with brotli (finally!): cl/377307679

Lessons Learned

Our CSI metrics are sometimes incorrect, because aggregating a percentile is incorrect.

What's Next

Fix CSI metrics
Prototype Jolt

What was accomplished

tested new chrome experimental flags and they're interaction with LCP, CLS, font loading
results from AVIF/WebP experiments

Lessons Learned
What's Next

prioritize render time over load time on LCP reporting
add Timing-Allow-Origin

What was accomplished

Aliased import paths https://github.com/ampproject/amphtml/pull/34562
lots of core migration and type-checking
path forward on compiler security sandboxing

What's Next

compiler security sandboxing
finish core extraction
Type-check src/preact so Bento components can be type-checked

Hello,
Created AMP page for Shopify platform - https://trademinister.net/
Can You recommend how can I boost PageSpeed score above 90?
Attached current web.dev/measure status

It's interesting that Lighthouse is seeing FCP at 3.5s (confirmed locally) even though the Performance tab of DevTools shows it at ~680ms:

As an aside, it looks like the page JS fetches amp-auto-lightbox via JS, rather than it being included in the page at load time. I don't think that should be the issue, though. This isn't the right thread for a deep discussion; could you either file a separate issue or post under the #using-amp channel on the AMP Slack?

@rcebulko: are you using the same throttling settings as lighthouse?

Hello Ryan,
Can You tell me how to subscribe to AMP Slack channel?
пт, 11 июн. 2021 г., 18:17 Ryan Cebulko @.***>:

It's interesting that Lighthouse is seeing FCP at 3.5s (confirmed locally)
even though the Performance tab of DevTools shows it at ~680ms:
[image: image]
https://user-images.githubusercontent.com/6694512/121709246-5981e900-caa6-11eb-9243-bb6977c00396.png
As an aside, it looks like the page JS fetches amp-auto-lightbox via JS,
rather than it being included in the page at load time. I don't think that
should be the issue, though. This isn't the right thread for a deep
discussion; could you either file a separate issue or post under the
#using-amp channel on the AMP Slack?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ampproject/wg-performance/issues/84#issuecomment-859654232,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFPXTPOJOAULKLDD7HAQCE3TSISKHANCNFSM46ID5HDQ
.

@trademinister see https://github.com/ampproject/amphtml/blob/main/docs/contributing.md#discussion-channels

Hello Ryan,
Thanks for the help
пт, 11 июн. 2021 г., 23:10 Ryan Cebulko @.***>:

@trademinister https://github.com/trademinister see
https://github.com/ampproject/amphtml/blob/main/docs/contributing.md#discussion-channels
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ampproject/wg-performance/issues/84#issuecomment-859853735,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFPXTPKXGQFC37BF7XDPSQ3TSJUTRANCNFSM46ID5HDQ
.


Adding prow jobs for generatebundlefile in eks-anywhere-packages

Signed-off-by: jonahjon<EMAIL_ADDRESS>Description of changes:
Adding Prow jobs for generatebundlefile.

/hold

Don't merge until
https://github.com/aws/eks-anywhere-packages/pull/221
https://github.com/aws/eks-anywhere-packages/pull/222
are both in otherwise will get failing tests.

/unhold

/approve


Added Jupyter notebook with experimental impedance spectrum

The notebook include a function to read the experimental data and describe how
to compare spectra mathematically.

[Current coverage][cc-pull] is 93.43%

Merging [#198][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master       #198   diff @@
==========================================
  Files            72         72
  Lines          4643       4643
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           4338       4338
  Misses          305        305
  Partials          0          0

[][cc-pull]

Powered by Codecov. Last updated by [386a1c6...d0f660b][cc-compare]
[cc-base-branch]: https://codecov.io/gh/ORNL-CEES/Cap/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/ORNL-CEES/Cap/compare/386a1c6e124625a694943811f11ce0aad1846db8...d0f660bd1a8f05a19adc33f234e085aea0e98270?src=pr
[cc-pull]: https://codecov.io/gh/ORNL-CEES/Cap/pull/198?src=pr


Create initial validiac fork

This commit introduces an initial fork of validkube that provides
similar capabilities for Terraform HCLs and related files.
Four capabilities are provided:

lint: lints HCLs using tflint
secure: checks for security issues using tfsec
cost: calculates costs using infracost
map: generates graph using inframap

The four dependencies are automatically downloaded using make deps.
Their versions are defined in the Makefile.
When the validiac binary is built, the location of the dependencies is
injected using Go build-time variables.
The binary can function both as an AWS Lambda function and as a simple
command line interface.
The UI has not been modified yet, and more work is required on the
backend:

Infracost requires an API key for usage.
When building a lambda, injected dependency paths should probably be
different than when build for local execution.
The tools mostly make sense when they can work on complete directories
of Terraform files rather than individual files. This is not addressed
yet.

Apologies, opened this in the original repo instead the fork, my bad.


more coverage

Codecov Report

Merging #16 (678e731) into main (96e8641) will increase coverage by 0.76%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #16      +/-   ##
==========================================
+ Coverage   78.38%   79.15%   +0.76%
==========================================
  Files          11       11
  Lines        1698     1698
==========================================
+ Hits         1331     1344      +13
+ Misses        234      224      -10
+ Partials      133      130       -3

Impacted Files
Coverage Δ

env.go
65.07% <0.00%> (-3.18%)
:arrow_down:

fill.go
80.66% <0.00%> (+2.97%)
:arrow_up:

request.go
84.21% <0.00%> (+3.50%)
:arrow_up:

registry.go
83.33% <0.00%> (+4.62%)
:arrow_up:

Continue to review full report at Codecov.

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


feat(ticker): modifies dev ticker to proxy to coingecko

Adds proxy service for coingecko.
Ref: ROLLUP-379

Prior to merging it can we please try to generate the image in docker to make sure that it will be generated once we are ready :)


add package init file

Actually realized that init is spelled wrong in this PR, which I think is why it was failing the lint checks...

Corrected...


Collect Contact info

Would like people to collect contacts to make sure I can get feedback appropriate

Looks like Zapier if I don't want to work on back end could work.
Maybe try back end


Use of traffic selectors in 2019-11-01 version of connection resource manager template.

I am trying to identify whether on a S2S connection with UsePolicyBasedTrafficSelectors set to true it is possible to specify a subset of the virtual network prefixes (e.g. one subnet only) to form the Azure end of traffic selectors.
The documentation here seems to suggest the entire virtual network makes up the Azure end of the traffic selectors.
The 2019-11-01 version of the vpn connection resource template has the traffic selector policies as a separate property on the connection (trafficSelectorPolicies) which would in theory allow the subset to be defined. Is this trafficSelectorPolicies compatible with a connection where UsePolicyBasedTrafficSelectors is set to true?

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

ID: c3c9ea83-f9d6-57c0-301d-323d2747a1c5
Version Independent ID: 424eec9a-4017-9128-1bbb-9b50996a9b7b
Content: Azure VPN Gateway: Cryptographic requirements
Content Source: articles/vpn-gateway/vpn-gateway-about-compliance-crypto.md
Service: vpn-gateway
GitHub Login: @yushwang
Microsoft Alias: yushwang

@haymansfield ,  We are looking into this query and will update you as soon as possible.

@haymansfield , Appreciate you patience. we have assigned this question to the content author for better insights.

@SubhashVasarapu-MSFT Thanks for passing this on.
Is there any update?

@SubhashVasarapu-MSFT
Just a quick enquiry as to whether there is any update on this issue?


Update EDRData.cs to include Countercept

Countercept's MDR agent is called OmniAgent.exe out the box, don't have any other sigs for it just yet.
When I get 5 minutes I might also include some 'Countercept detected == take particular action" text in console.writeline etc.

Thanks @BaffledJimmy this is now merged into master!


[SURVEY] do you really need Internet Explorer 11 support or can I remove it?

I'm tired to support IE11.
IE11 is causing me many issues, in particular about the new carousel component.
What do you think if I remove IE11 support with angular-modal-gallery 10? (that probably will be released in Autumn 2019)?

Yes IE11; current users are still far greater on IE than Edge

Yes, I suppose that many users are still using IE11.
I'm thinking to eventually remove it in future releases (I don't know when), because It causing me delays at every release, in particular with 7.0.0 beta that it sill have some issues on IE11.
I hate Ie11 :) but I cannot remove it right now. I'll think about IE11 support again in the future.
However I suggest to force/suggest users to use modern browsers, because as an open source projects I cannot support older technologies forever.


Can't install if port 22 is blocked

I'm inside a heinous corporate firewall.
I get the following output when attempting to install this module:
npm install -g livedown
npm WARN optional dep failed, continuing<EMAIL_ADDRESS>
><EMAIL_ADDRESS>install /home/ME/.npm-packages/lib/node_modules/livedown/node_modules/socket.io/node_modules/engine.io/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

npm ERR! git clone git@github.com:rase-/node-XMLHttpRequest Cloning into bare repository '/home/solnet/.npm/_git-remotes/git-github-com-rase-node-XMLHttpRequest-01a5ec93'...
npm ERR! git clone git@github.com:rase-/node-XMLHttpRequest ssh: connect to host github.com port 22: Connection timed out
npm ERR! git clone git@github.com:rase-/node-XMLHttpRequest fatal: Could not read from remote repository.
npm ERR! git clone git@github.com:rase-/node-XMLHttpRequest
npm ERR! git clone git@github.com:rase-/node-XMLHttpRequest Please make sure you have the correct access rights
npm ERR! git clone git@github.com:rase-/node-XMLHttpRequest and the repository exists.
npm ERR! notarget No compatible version found: xmlhttprequest@'rase-/node-XMLHttpRequest#a6b6f2'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["1.0.0","1.2.0","1.2.1","1.2.2","1.3.0","1.4.0","1.4.2","1.5.0","1.6.0","1.7.0"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! System Linux 3.16.6-2-desktop
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" "-g" "livedown"
npm ERR! cwd /home/solnet
npm ERR! node -v v0.10.31
npm ERR! npm -v 1.4.23
npm ERR! code ETARGET
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /home/ME/npm-debug.log
npm ERR! not ok code 0

Try opening up ~/.ssh/config and adding:
Host github.com
  Hostname ssh.github.com
  Port 443

(blatantly copied from http://stackoverflow.com/a/8081292/726020, thanks to the author)

No luck.
This didn't happen a few days ago - has there been an updated in the intervening time?

Nope, there were no recent updates.

Do you happen to know which dependency is doing the equiv of "git clone"?

Sorry for the long delay. I'm closing this, feel free to reopen if you're still having problems.


[seamlisten] add initial backend test

The seamlisten project doesn't have test related to the webserver part. Could we add pytest with a few very simple initial tests?
[Internal issue: 27]

@Celebio  I would like to work on this issue