tsconfig.base.json

At work we used nx to generate our monorepo structure. We've got a tsconfig.base.json in the root of our project. The search function in tsc.nvim only looks for tsconfig.json as far as I can tell.
Could you give me some guidance with how to configure the options in require('tsc").setup(...) to find the correct root file?
I've confirmed that I get project level diagnostics if I rename the file tsconfig.base.json -> tsconfig.json, however I know the team wouldn't appreciate me renaming this simply so that I can use Neovim.
Thanks in advanced, and thanks for such a great tool!
On a personal note, I'm new to Neovim as of this week and really enjoying myself. If I can fix this issue I can make it my go to editor professionally at work!!!

I've tried a quick configuration change to see if I could get this to work, however it doesn't seem to find project level diagnostic information, though it does seem to find the correct file:
require("config.lazy")
require("tsc").setup({
    flags = {
        build = true,
        project = function()
            local tsconfig = vim.fn.findfile("tsconfig.json", ".;")
            local nxTsBaseConfig = vim.fn.findfile("tsconfig.base.json", ".;")

            print("tsconfig", tsconfig)
            print("nxTsBaseConfig", nxTsBaseConfig)

            if nxTsBaseConfig ~= "" then
                return tsconfig
            end

            if tsconfig ~= "" then
                return tsconfig
            end

            return nil
        end,
    },
}```

As you can see, I'm using `lazy.nvim` - perhaps there is a conflict there somewhere?

I'll take a look at this in the morning - any chance you could throw together a small nx repo that I can for sure reproduce this with?
I have one suspicion that the problem may be that I'm using vim.tbl_extend instead of vim.tbl_deep_extend here: https://github.com/dmmulroy/tsc.nvim/blob/main/lua/tsc/init.lua#L165
I'll also test that out in the morning and let you know what I come up with.
Sorry you're running into issues, but I appreciate the issue report 🙏

On a personal note, I'm new to Neovim as of this week and really enjoying myself. If I can fix this issue I can make it my go to editor professionally at work!!!

Well then we'll definitely get it working for you 🚀

Well I tried the tbl_deep_extend option and didn't see much of a change - I cut a new release with the change anyways that you can try by upgrading (change here: https://github.com/dmmulroy/tsc.nvim/releases/tag/v1.8.0)
If you run tsc manually from the root of your repo does it typecheck correctly?
I probably will need more info on your tsconfig and repo setup.

Hey @dmmulroy, thank you so much for looking into this so quickly. I'm learning that the neovim community is rad!
I've tried both of those configurations however no luck with either. I'll take some time to setup a small repo that reproduces the issue, though it may take me a bit. My personal machine died recently and I don't want to push personal stuff from my work machine.
Once I get a new laptop I'll create a small repro.
If you get a wild hair and want to try it on our end before I get that computer you could basically do this, and create some kind of bad import/export and it does successfully repro the issue. Eg in apps/nx-nvim create a BadExport.tsx and import that into App.tsx - something like that.
Need to install the following packages:
  create-nx-workspace@latest
Ok to proceed? (y)

 >  NX   Let's create a new workspace [https://nx.dev/getting-started/intro]

✔ Where would you like to create your workspace? · nx-nvim
✔ Which stack do you want to use? · react
✔ What framework would you like to use? · expo
✔ Application name · nx-nvim
✔ Enable distributed caching to make your CI faster · Yes

 >  NX   Creating your v16.8.1 workspace.

   To make sure the command works reliably in all environments, and that the preset is applied correctly,
   Nx will run "npm install" several times. Please wait.

✔ Installing dependencies with npm
✔ Successfully created the workspace: nx-nvim.
✔ NxCloud has been set up successfully```

That will run `nx` locally and create a small repo that uses their default configs. If you're seeing what I'm seeing running `:TSC` won't return any errors, but if you open a buffer

Going to look into this after work today

@camerow I was able to reproduce your issue with the instructions your provided.
I was also able to get the plugin working - here is the configuration I used:
require("tsc").setup({
	flags = {
		project = "tsconfig.base.json",
		jsx = "react",
	},
})

🍾 That does seem to get project level errors working! Something else is wrong - likely a very specific thing in my work environment - which gives me tens of thousands of unresolved errors. Looks like package resolution or something, though I don't think it's something wrong on this plugin's end.
Thank you so much for your help and responses man! Truly appreciated 🙇
Hopefully this little convo comes in handy for some other folks as well!

Awesome - lmk if you have any more issues, happy to help!


fix(module:cdk): zIndex is not used properly when creating overlay

PR Checklist
Please check if your PR fulfills the following requirements:

[✔] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[] Tests for the changes have been added (for bug fixes / features)
[] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[✔] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?
The modal, drawer, or any other components that are made with the Angular CDK have the zIndex applied to the inner element of the created overlay. This is not desirable for two reasons:

The created overlay is a direct child of the body element
Each overlay has its own wrapper with the class name 'cdk-global-overlay-wrapper'
Therefore, changing the zIndex of the inner element has no effect, as it is already isolated from other overlays. The expected behavior is that the zIndex should be applied to the overlay wrapper instead.

The image below illustrates this issue:

The red sections are the overlay wrappers

The green section is the inner element of the overlay wrapper, which has its zIndex changed

The scenario is as follows:
We have a modal component, which contains a button that opens a drawer component (the first red outline is the drawer wrapper, the second is the modal wrapper).
As stated in the issue below, the drawer component should appear above the modal component; but currently, the modal component is on top. The reason why the zIndex property does not work is that it is applied to the inner element of the overlay, rather than the overlay wrapper.
This issue occurs whenever the CDK overlay is used; currently, only modal and drawer components have been fixed. If this pull request is approved, I will update other components that use the overlay as well.
Issue Number: #8353 , #8336
What is the new behavior?
Mentioned above.
Does this PR introduce a breaking change?
[ ] Yes
[✔] No

Other information
Currently it is not possible to set overlays' zIndex value when creating it (issue).

Please could you provide test for the code added ?

Sure, I will get back to you with that as soon as I can.

Please could you provide test for the code added ?

Sorry for the delay; tests for the changes have been added.
Thank you for reviewing my PRs @Nicoss54


Image Viewer Rescaling

When using the rescaling function on the image-viewer there were complaints that it was difficult to see the S2/L8 images because they were scaled up to match the geospatial bounds of the WV images.
This PR adds an option in the settings to zoom out the rescaled images to provide more context for the S2/L8 images (up to 5X the size of the box).
Since we don't have any additional data for the WorldView image outside of it's bounds it is marked as gray outside of the area.
Note:

Zooming out on a mix of WV and S2 can result in a large GIF because I'm still displaying the WV at native resolution.  I.E if the WorldView resolution is 500x500 and you zoom out 2X then all images in the GIF sequence are now 1000x1000 with the S2/L8 images upscaled to fit there.

I get that logic can seem a bit complex between scaling.  I would just suggest taking a site downloading  WV/S2 images and then playing with the rescale toggle setting

And then under the Cog Wheel adjust the zoom out setting.


[FR] Add support for Quiet outline

As is, the selected outline headings are very washed out and barely visible.

In contrast, headings should be colored, and they are when using the default theme.

See:
https://github.com/guopenghui/obsidian-quiet-outline

Thanks for the feature request. Could you give me some steps to replicate and clarify which part of the UI your screenshots are of? I have installed Quiet Outline but it's not clear to me where the issue arises.

Could you give me some steps to replicate and clarify which part of the UI your screenshots are of? I have installed Quiet Outline but it's not clear to me where the issue arises.

Hi Callum, sorry for the long delay. First, what's off is that the highlight color for the current heading in focus in the editor is a very pale gray, which is barely visible. If you test it with the default theme, the current heading should be the same as the theme's accent color.
To replicate:

Set the theme to Default
Install and enable Quiet outline
Open a note with several headings
Scroll through the document and observed the current heading being highlighted in Quiet outline
Set theme to Polka
Repeat steps 1-4 and observe the heading "highlight" in Quiet outline, which is now pale and barely visible.


Flatbuffers not generating 32-bit "flatc" executable on Ubuntu

Xmake Version
2.8.8
Operating System Version and Architecture
Ubuntu 22.04.4 LTS x86_64
Describe Bug
When installing the flatbuffers package it will build the flatbuffer compiler flatc. It does so perfectly on both windows 32 and 64 bit (using xmake f -a x86 and xmake f -a x64 respectively). It also works perfectly on Ubuntu for x86_64 and build the flatc executable in the installdir. But for some reason it doesn't build the flatc executable on linux with architecture set to i386. I.e. there isn't any installdir/bin/flatc . The installdir contains the same files otherwise except the missing bin folder.
There are no errors anywhere when downloading or installing the package.
Expected Behavior
I would expect it to compile the flatbuffer project and provide the flatc compiler in the installdir/bin/ folder like it does on 64 bit mode on Ubuntu and both 32- and 64-bit mode in Windows 10.
Project Configuration
You can see it fail here in this github action:
https://github.com/Jonathan-Greve/gw_dat_reader/actions/runs/8328945753/job/22790106109
Additional Information and Error Logs
Other than the missing flatc I don't have any issues. I can generate the 32-bit flatc manually by doing:

Cloning the google flatbuffers repository.
Running cmake -G "Unix Makefiles" -DCMAKE_C_FLAGS=-m32 -DCMAKE_CXX_FLAGS=-m32
Running make -j

-DFLATBUFFERS_BUILD_FLATC=OFF is passed to cmake as seen here.
This is because of this part of the script.
The issue is that xmake recognize cross-compilation and thus the inability to run the flatc binary on the host.
It would work with a 32bits runner, but I don't think GitHub provides those as 32bits Linux are pretty rare today.

Ah yeah that makes sense. I didn't think of building 32-bit binary on 64-bit OS as cross-compilation but I guess it makes sense.
I'm don't quite understand the intricacies of xmake so I'm not sure if the current way of doing it is working as intended or not.
I can of course work around it for the time being. But it would be nice if something like this would work without having to do something special for the linux i386 case:
local flatbuffers_installdir = target:pkg("flatbuffers"):installdir()
local flatc_exe = is_plat("windows") and "flatc.exe" or "flatc"
local flatc_path = path.join(flatbuffers_installdir, "bin", flatc_exe)

Thanks for clarifying. And if this is intended behavior if there is a more general issue covering this topic feel free to close this issue.

Are you using flatbuffers only for its binary package?
If so you want use add_requires("flatbuffers", { host = true }) to tell xmake to install it with the host system/arch instead of the target system/arch, you'll then have flatc executable available.

No I will be using the library too for my project. I.e. i won't just be using flatc I will also be including the flatbuffer headers in my code. It will always be compiled on 64-bit OS though so I don't mind flatc being 64-bit only.

Hi thanks for the support. Yes that seems to do what I need but I don't understand what flatbuffers~host does. Should I close the issue since my problem is solved?

It's a way to requires flatbuffers a second time without conflicting on the package name. xmake remove the ~ part when fetching a package on xmake-repo but keeps it as its reference name. ("~host" is just a suffix, it could be anything).
The real magic is to configure it with host = true

Alright thanks a lot :)


(MAINT) Bump project.clj version to 2.2.2-master-SNAPSHOT

This commit bumps the Puppet Server version in the project.clj up to
2.2.2-master-SNAPSHOT given that we've released 2.2.1 already.

Any reason this can't be 2.3.0-SNAPSHOT ?

I don't think we know for sure yet that the next release we do off of this branch will be a Y bump.  We've tried to be conservative about that in the past anyway - only bump to the next Z.

I'm +1 on this ending up as 2.2.2-master-SNAPSHOT, but it seems like if it currently says 2.2.0 then we are delinquent on some merge-ups (which is probably my fault).  In any case I'd have no big problem with merging this now as long as we're careful about not screwing it up when the merge-ups come in.

@cprice404 I think we had already merged up code from stable recently.  Just did a separate merge up PR to catch everything else that was in stable but not master yet - just docs.  That PR is #817.  Figured it made sense to have the version bump and merge up be on separate PRs.

:+1:


Add a stats endpoint

Feature Request
Is your feature request related to a problem or unsupported use case? Please describe.
Every week we have to ask a devops to give us the number of docs and users.
Describe the solution you'd like
I'd like to have a /stats that exposes in json a few stats.

Number of users
Number of docs
Number of active users / per week
Number of active docs / per week

This will be usefull for the overall dashboard of La Suite.
We can refine what stats we display, for example

Number of shared Docs
Pie chart of different sharing settings (public, authenticated, private)
Medium number of users on a doc

Feature PR has been created accordingly, if there are more Metrics you need, please let me know.
-> https://github.com/numerique-gouv/impress/pull/449


Remove provide feedback button for stable

refs #57304
There is no need for the provide feedback button in the settings UX once we push it to stable.
Our users are educated enough to create issues (we get a trillion of those daily)
Also the settings ux is now tested and there is no need for this imho. This feature is not special compared to other features and we do not have "provide feedback" buttons for other new features

Also please remove this button for the same reasons

It's already Insiders only, I'll remove it from Insiders.
Where is the Report Issue button?

No clue how I got to see it, but I see it is used here in code
https://github.com/Microsoft/vscode/blob/654108d3619b0ca8d1c0501b4350d3b6c5f1c571/src/vs/workbench/parts/preferences/browser/preferencesRenderers.ts#L797
Can we just get rid of the IssueWidgetRenderer?

Oh right, for bing settings search. It's insiders-only anyways but it's time for it to be done...


Drop Logging.jl

Julia 0.7 is having improved logging capabilities, we can drop
Logging.jl.

Coverage decreased (-0.3%) to 77.852% when pulling aebeec21528b32b1d6a792ab7f9765f90e38248e on drop_logging into ce12011380b34df3ca4451c68b57d79cb9476637 on master.


feat!: changed to esm, upgrade dependencies, export parsers and serializers

Codecov Report
Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:

Coverage data is based on head (7c02372) compared to base (7f3ac31).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff            @@
##            master       #10   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines           45        52    +7
=========================================
+ Hits            45        52    +7

Impacted Files
Coverage Δ

index.js
100.00% <100.00%> (ø)

lib/CustomJsonLdSerializer.js
100.00% <100.00%> (ø)

lib/CustomRdfXmlParser.js
100.00% <100.00%> (ø)

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

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


Fix hyphen typo in gMSA reading functionality.

self.objecttype_guid_map has a hyphen while the comparison did not and this was causing it to not include the msDS-GroupMSAMembership attribute.
Because of this https://github.com/fox-it/BloodHound.py/blob/master/bloodhound/enumeration/memberships.py#L205 was failing even when it shouldn't.

good find! merged it in :)


ERROR TS2322: Type 'BigInt' is not assignable to type 'i32'

https://github.com/messari/subgraphs/blob/82b9b3849bfe170f11dc0c42bc250d11ed46ff9c/subgraphs/_reference_/src/sdk/protocols/lending/token.ts#L157-L162
returning decimalValue here for me results in:
ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt' is not assignable to type 'i32'.

this has to do with the try_decimals returning BigInt in the generated ERC20.ts:
  try_decimals(): ethereum.CallResult<BigInt> {
    let result = super.tryCall("decimals", "decimals():(uint256)", []);
    if (result.reverted) {
      return new ethereum.CallResult();
    }
    let value = result.value;
    return ethereum.CallResult.fromValue(value[0].toBigInt());
  }

also ref abis/ERC20.json: https://github.com/messari/subgraphs/blob/82b9b3849bfe170f11dc0c42bc250d11ed46ff9c/subgraphs/reference/abis/ERC20.json#L81-L92
i quick fixed it with return decimalValue.toI32() but would love to know if that is sufficient and worth a pr or if i am missing something :)

@gosuto-inzasheru I checked compound v3 which uses the exact same abi and token mappings as _reference_. I also used the latest graph npm packages. And I do not have any issues, here is a snippet of the autogened code:
  try_decimals(): ethereum.CallResult<i32> {
    let result = super.tryCall("decimals", "decimals():(uint8)", []);
    if (result.reverted) {
      return new ethereum.CallResult();
    }
    let value = result.value;
    return ethereum.CallResult.fromValue(value[0].toI32());
  }

Without seeing your source code it is hard for me to say right now what the exact issue is.

so problem stems from the following discrepancy in type (i assumed both interfaces to be the same):
https://github.com/messari/subgraphs/blob/1c99de5d01e89ed54918de8bef920d96c788d052/subgraphs/_reference_/abis/ERC20.json#L81-L92
and
https://github.com/messari/subgraphs/blob/1c99de5d01e89ed54918de8bef920d96c788d052/subgraphs/_reference_/abis/Prices/ERC20.json#L641-L646

solution is therefore to introduce two separate interfaces for erc20 in the template:
        ...
        - name: _ERC20
          file: ./abis/Prices/ERC20.json
        - name: ERC20
          file: ./abis/ERC20.json
        ...

not sure if this is by design or if both interfaces could be consolidated


command error

Describe the issue

URL of the docs

https://docs.dapr.io/developing-applications/building-blocks/state-management/howto-get-save-state/
Expected content

dapr --app-id myapp --dapr-http-port 3500 run
Screenshots

Additional context

Yes, this is a typo here https://docs.dapr.io/developing-applications/building-blocks/state-management/howto-get-save-state/

/assign


added workshops and demos

I'll continue to work on the rest of the program sometime this weekend

added to the wrong area


Feat/backend api security and minor fixes

Is necessary to run the broker via Docker, and this version of the Backend-API via source or docker: https://github.com/hummingbot/backend-api/pull/37
In this PR we should test the following things (is necessary to do a fresh install of the environment):

Auth system: change in CONFIG.py AUTH_SYSTEM_ENABLED to True by default (so you don't need to set up an env variable or set the env variable, as you want) -- > line 20 of the image.
Test that the login is working well for admin abc that is the default.

Backend API security: as you can see lines 24 and 25 were added to introduce two new env variables. By default, the user and pass are (admin, admin) for Backend API. If you run the Dashboard you should be able to use it without problems. The next thing will be:

Changing the config in the backend api and run it again (check the .env file and change the username)
Changing the default from admin to something else
In the last two scenarios, the dashboard should not work.

PR update:

Fresh install dashboard and backend-api on source ✅
AUTH_SYSTEM_ENABLED is still set to false by default, change from false to true to test. Auth enabled ✅
Login using default credentials ok
After login, check bot orchestration page

It seems related to issue on set_environment.sh
Change to set admin/admin worked ✅
if backend_api_username and password does not match to set .env file, user cannot access ✅

If auth disabled and backendapi credentials does not match:

user can access dashboard without login ✅
user can’t access pages that require backendapi ✅

Attached recording of XEMM Controller accessible when unauthorized:
https://github.com/user-attachments/assets/d1845fb8-f097-4bc4-9ceb-cc5d217a13fc

0c9238a

Docker
backend-api-PR37 + dashboard PR188

Cloned PR188 and set AUTH_SYSTEM_ENABLED True
manually built docker image with docker build -t hummingbot/dashboard:development -f Dockerfile .
cloned backend-api-PR37 and manually built docker image with docker build -t hummingbot/backend-api:development -f Dockerfile .
cloned deploy repo and use setup_dev.sh to run dashboard

Actual:
Reviewed not asked for authentication


Intel RealSense Viewer parameters' documentation

There is a lack of documentation about the different parameters available in the Viewer
I guess this has been notified several times already, but since the SDK has been released for a couple years now it really is a shame that no description is provided for the parameters in the Viewer/the configuration (.json) files.
There IS some explanations available here and there, but it really is just to introduce the features to the user. As a "kind of mid-skilled user", it is quite frustrating not to be able to exploit the parameters at there full potential... I'm guessing that we potentially could improve quite a bit our setup if we actually knew what is the behavior of each available parameters. I feel that a ton of them are still obscure to me (and probably other people) and thus simply not used.
Has the release of such a documentation been planned ?
Please let me know if missed something that could be useful !

The 'Advanced Mode' features were not fully documented by Intel because the complex ways in which the interact with each other meant that Intel chose to control them with machine learning instead.  The user is free to do trial and error experimentation with the settings to see how changes affect a stream.  It is not planned to add further documentation for the Advanced Mode functions though.
There is a PDF user guide for the Viewer that collects together information about some of the Viewer's settings into a single document.
https://www.intel.com/content/www/us/en/support/articles/000028593/emerging-technologies/intel-realsense-technology.html

Thank you for the fast reply @MartyG-RealSense ! I already downloaded this document, that's the one I was referring to.
I understand that the complexity of the parameters makes it difficult to describe and explain everything, and I don't expressly call for it :)
However, I was hoping for a slight complement of information; like the full name of all the parameters and not just some abbreviation. It would be a nice starting point, and I could then do my own research on the topic !

I did some extensive research for better plain-English explanations for the parameters but did not have any luck.   The best I could find was the list of Advanced Mode functions in the documentation.
https://unanancyowen.github.io/librealsense2_apireference/classrs400_1_1advanced__mode.html

Yes I am aware of this documentation ! I also think that this is the official link :
https://intelrealsense.github.io/librealsense/doxygen/classrs400_1_1advanced__mode.html
Despite having more explanations, I guess that we at least have a proper list of the parameters...
Thank you for your help though @MartyG-RealSense.
I'll leave this issue open a few days in case of someone has further information to provide.

Hi @AntoineWefit
Presets are designed to abstract this complexity away from the user and there are some additional ones here
When a parameter can be controlled in a useful way, the exact instructions are usually captured in a white-paper.
We could add some extra documentation on couple additional advanced mode parameters, let me check internally with my colleagues.

Any update on this @dorodnic ?

Hi @AntoineWefit
There is a White paper - Tuning depth cameras for best performance - talking about the parameter tuning.
https://dev.intelrealsense.com/docs/tuning-depth-cameras-for-best-performance#section-play-with-depth-setting
Please let us know if you have further questions.
If we don't hear from you in 7 days, this issue will be closed.


Convert 'Add Project Alerts' to modal

To follow the style of all other project specific inputs from the project details page, add project alerts should be a modal rather than a page redirect.

Manual creation of alerts is not needed att.


Remove mentions of “paid” and “trial” from hosted homepage

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1983
Originally created by @DouweM on 2020-04-21 23:32:07

Instead, we can treat advertise it as a free tool, say that we wind instances down after no activity for a month.
It serves primarily as a demo of Meltano, and a channel for feedback.

View 4 previous comments from the original issue on GitLab


Omit producing "JavaScript heap out of memory" with v3.3

TypeScript Version:  3.4.0-dev.201xxxxx

3.3.0-rc
3.3.3333
3.4.0-dev.20190223

Search Terms:
Omit
Code
// using "@types/react": "^16.8.4"

type Omit<T, K extends keyof T> = Pick<T, Exclude<keyof T, K>>;

type XXX = Omit<React.HTMLAttributes<HTMLElement>, 'title'>;  // <= this alias is not working

Expected behavior:
It should work as early versions, last tested v3.2.4
Actual behavior:
Compiler throws "JavaScript heap out of memory" and same happens with VSCode Intellisense (stuck for minutes without proper answer).
Playground Link:
Tested code working with playground 3.3. (pasting @types/react at bottom), too big to share.
Related Issues:

Just curious.
If you run node --max-old-space-size=8192 ./node_modules/typescript/lib/tsc.js --diagnostics,
do you still get OOM?
If it does complete, what does it say for Memory used?
For example, for one of my projects, my output says Memory used: 1310899K. So, 1.3GB

I can't seem to repro this on 3.3.333 or on @next (tried<EMAIL_ADDRESS>and 3.4.0-dev.20190223). Is there more here, like certain compiler settings or additional installed @types packages (beyond @types/react and csstype), that are required to trigger this?

@weswigham Thanks a lot for the prompt reply. I have debugged this issue to discover that my initial thought regarding Omit as culprit was wrong, the OOM is due some other issue. I managed to create a repro with a minimum case that fails and 2 cases where partially works, to be considered that same code was properly compiling up to 3.1.16. Repro and detailed info here: https://github.com/artola/ts-bug
Produces OOM during compilation:
import React, {PureComponent} from 'react';

interface TextProps {
  tag: keyof JSX.IntrinsicElements;
}

export class Text extends PureComponent<TextProps> {
  render() {
    const {
      tag: Tag,
      children
    } = this.props;

    return (
      <Tag ref={()=>{/* oops */}}>
        {children}
      </Tag>
    );
  }
}

Oho? Maybe related to #29949 then.

@weswigham Looking at #29949 and even disabling strict or just  strictFunctionTypes it is failing.
Might be related with large unions? I would say yes, but I do not see why/how in the example above.

Yep, this looks like a carbon copy of how #29949 works - the Tag of type keyof JSX.IntrinsicElements is a union of 110 items - to check all 110 of the possible tags, we union those signatures - meaning we intersect the arguments. We then intersect 110 ref types (which are all undefined | null | string | RefFunc<T> | RefObj<T>) which becomes crazy costly with how we construct intersections, as it happens. What's worse is that since there's both the func and object types, they combine in strange and interesting ways - like, say we only were looking at a "input" or a "button" - well, that could have a ref that is a function which tags a "button" ref param, but is also an object which takes an "input" ref property. Or vice versa. Or both as params, or both as objects. From 2 effective inputs, we get a union of 4 output types - and this multiplication occurs for every element of the union. Running the numbers, the resulting union is supposed to have.... 10^33 members or so?
@ahejlsberg what do you think we should do for a intersection/union nesting where flattening the nesting would produce an absurd number of types? There's a strong desire to check this pattern correctly, so I don't think some kind of resource limit would work here; but at the same time, optimizing construction won't cut it here - the sheer number of types scheduled to be produced by this flattening operation is huge.


Limit Disruptive GatewayClass Changes

As I've been exploring conflict resolution one of the guiding principles that has emerged is to "not break things that are currently working." As the API is currently configured, changes to GatewayClass and its associated parameters have the potential to be very disruptive. A change to a GatewayClass parameter like allowedRouteNamespaces would potentially invalidate a large number of Routes for all Gateways using that class. Alternatively, a change to parameters associated with a GatewayClass could be backwards incompatible and require resources to be recreated. Here are some approaches that might help:
Consider GatewayClass and params immutable
This would be straightforward to implement as an API and easy to understand. Unfortunately it would mean that even the smallest changes to a GatewayClass would require a new GatewayClass being created. This is especially problematic if we want to have consistent and meaningful GatewayClass names provided by implementations.
Treat GatewayClass and params as templates
With this approach, GatewayClass params would be copied or applied to a Gateway on creation but then can change independently from the GatewayClass. A potential downside here would be that multiple Gateways would be associated with the same GatewayClass, the details could be significantly different if the GatewayClass changed between Gateway creations.
Embed versions or revisions within a GatewayClass.
All existing revisions are immutable but new ones can be created. This would mean that a Gateway would need to reference both a GatewayClass and version. This would likely be complex to implement and could result in GatewayClasses with a large number of versions.
Trust users not to break things
If we can't find a great way to limit potential disruptive changes here we could rely on better documentation around this functionality and accept that GatewayClass changes can potentially have disruptive consequences.
As a follow up note, this closely ties both GatewayClass and GatewayClass parameters together, even though this API can only directly control the GatewayClass resource. Parameters will be implementation specific by definition. I do think it would be helpful to at least provide guidance for how changes should be handled here.

What does StorageClass do?

IIRC the original concept for using GatewayClass was that you would have a small number of classes pre-provisioned in the cluster. I think these were thought about as being largely static handles to infrastructure, so the default policy of "trust users to not break things" was more clearly a reasonable approach.
I think that there are a couple of dimensions to this problem.

Changes in parameters specified in the API. For any kind of class configuration that is defined in the API (i.e. fields specified through GatewayClassSpec that are not implementation-specific), I think that the API should specify how configuration changes should work, and the WG should think through the operational aspects.
The production readiness questionnaire has some good questions related to configuration changes.

Changes in controller-specific parameters. In this case, the API can really only provide suggestions to implementors. Which of the above options is desirable is very specific to the implementation and to the type of configuration change. For example, changing a default for connection timeouts seems like it should be allowed without requiring a whole new GatewayClass to be created. However, an implementation should not allow a change that would break existing gateways (follow the precautionary principle).

Without a stronger definition or assumption on what a GatewayClass is and how it behaves, I'm not sure that the first three suggestions are feasible. It's easy to think up hypotheticals that will support or refute any of these approaches, so adopting them constrains implementations. Of the first three, "Consider GatewayClass and params immutable" seems the most plausible.

xref https://github.com/kubernetes-sigs/service-apis/issues/170

With #285 merged in, I think we have a better story now.
@robscott @jpeach Safe to close this one?

Agreed. I think we've mitigated this pretty well now.


Exception when opening a non existing code-workspace file

Steps to Reproduce:

run code-insiders some.code-workspace
the file opens dirty
the console opens with an exception

Error: resource is not available
    at /Users/bpasero/Development/monaco/out/vs/workbench/services/textmodelResolver/common/textModelResolverService.js:81
    at _Base.Class.derive._creator.CompletePromise_then [as then] (/Users/bpasero/Development/monaco/out/vs/base/common/winjs.base.raw.js:1566)
    at ResourceModelCollection.resolveTextModelContent (/Users/bpasero/Development/monaco/out/vs/workbench/services/textmodelResolver/common/textModelResolverService.js:78)
    at ResourceModelCollection.createReferencedObject (/Users/bpasero/Development/monaco/out/vs/workbench/services/textmodelResolver/common/textModelResolverService.js:42)
    at ResourceModelCollection.ReferenceCollection.acquire (/Users/bpasero/Development/monaco/out/vs/base/common/lifecycle.js:80)
    at TextModelResolverService._createModelReference (/Users/bpasero/Development/monaco/out/vs/workbench/services/textmodelResolver/common/textModelResolverService.js:118)
    at TextModelResolverService.createModelReference (/Users/bpasero/Development/monaco/out/vs/workbench/services/textmodelResolver/common/textModelResolverService.js:101)
    at MainThreadDocuments._handleAsResourceInput (/Users/bpasero/Development/monaco/out/vs/workbench/api/electron-browser/mainThreadDocuments.js:165)
    at MainThreadDocuments.$tryOpenDocument (/Users/bpasero/Development/monaco/out/vs/workbench/api/electron-browser/mainThreadDocuments.js:148)
    at MainThreadService.AbstractThreadService.invoke (/Users/bpasero/Development/monaco/out/vs/workbench/services/thread/node/abstractThreadService.js:29)

Duplicates #33698


Chinese service question in CN_1.5.2

In CN_1.5.2 , every time punctuation, the game crashes. I asked a lot of people, they also have this problem
My game  Chinese service

Sorry for the late reply, but you need offsets specifically for Chinese client.


Add integration tests for snapshot read and resuming.

The change adds the following integration tests:

Resuming by row offset when calling ReadRows.
Reading rows at different snapshots in time.

@tswast or @shollyman, please review.
CC: @kmjung , @aryann

cc: @JesseLovelace

Kokoro - Test: Windows Java 8 failure is unrelated to changes (spanner flakes).


Theme slots SASS variables use fixed color values instead of actual theme slots.

Category

[x] Bug

Describe the bug
Every new SPFx project gets the following SCSS import included.
@import '~office-ui-fabric-react/dist/sass/References.scss';

This reference.scss now do not support theme slots anymore. Instead, they use fixed colour values of an outdated blue theme.
Steps to reproduce
The easiest way to reproduce this issue is to create a new web part project and the bug the SASS variable stored in any of the the $ms-* variables in the following way.
  .row {
    @include ms-Grid-row;
    @include ms-fontColor-white;
    background-color: $ms-color-themeDark;
    @debug $ms-color-themeDark;
    padding: 20px;
  }

The following output illustrates the value that will be compiled in the final SASS file during the build tasks:

Expected behavior
The variable should include the following value in the SASS output for example:
'[theme:themeDark, default: someDefaultColorValue]'

Developer environment
SPFx 1.10.0

Dupe #5131


Feature: support Unix sockets for databases

Please add support for unix sockets for databases such as MySQL and Postgres.
As far as I can tell, this is easily accomplished by adding the following to database.php:
'unix_socket'   => env('DB_SOCKET', null),

Hi @AceBlade258,
Unix sockets can be set via the DB_HOST .env variable using the following format:
DB_HOST=localhost;unix_socket=/var/run/mysqld/mysqld.sock

Tested on my Ubuntu machine. Let me know if that doesn't work for you and I'll re-open this.


Add note about the mattermost.service file

Clarified that PostgreSQL or MySQL After and Requires sections should not be included if the database is running on a different server.

@cvitter Thanks! Does this also affect the Debian install guides? https://github.com/mattermost/docs/blob/master/source/install/install-debian-88-mattermost.rst

@jasonblais I believe that it should be the same however I haven't tested. Likely also the case with https://github.com/mattermost/docs/pull/1688.

Thanks!


Fix PlayerInfo physics parsing

Thanks for finding this bug, but this pull request only changes the javascript file while this project is using typescript. I will fix this issue asap.

Now fixed in version 0.5.1


feat: convert issue templates to issue form templates

proposal

Convert the Markdown issue templates to issue template forms written in YAML.
The main goal is to save time for the maintainer by ensuring all necessary
information is provided, thereby reducing the need for follow-ups. Additionally, the
user is required to confirm that they have already consulted the troubleshooting page or
searched for similar issues.

links

Github Docs - Syntax for issue forms

todo

[x] check if this is desired by the maintainers of continuedev/continue

[ ] check wording
[ ] check links, for example to the troubleshooting page or discord
[ ] test it, demo repo: https://github.com/LangLangBart/yaml

This looks quite nice! I think it's okay not to require all of the fields, just so that there is a super low friction path if somebody wants it, but otherwise this is great. I'll do a full run-through on the wording soon

I think it's okay not to require all of the fields, just so that there is a super low friction path if somebody wants it.
Ok, I set it to false, including the check boxes.
Put the required environment information in a single Markdown field instead of multiple checkboxes.

Awesome. Sharing this with Ty as well for some wording feedback, then I think it'll be totally good to go


[DCOS-41163] Short-term fixes to make PR tests against 0.40 work again.

@elezar does not look like that second commit actually fixes the code-checks problem?
[13:06:19]Unable to find image 'dcos-commons:0be01f9' locally

Yes, I saw this and dug a little bit. We have the following issues.

The docker build step for the code checks actually fails, but because we don't have set -e in the configured script the build continues.
This means that the image that is supposed to be used is never build and thus doesn't exists.

The reason for 1. is that the step here: https://github.com/mesosphere/dcos-commons/pull/2644/files#diff-3254677a7917c6c01f55212f86c57fbfR60 requires a git repository in the current folder. Looking at the .dockerignore file we, however, have: https://github.com/mesosphere/dcos-commons/blob/sdk-0.40/.dockerignore#L5 (which was removed in master). I would assume that this is because of the function here: https://github.com/mesosphere/dcos-commons/blob/sdk-0.40/sdk/common/build.gradle#L25 which should be updated to handle the case where the current folder is not a git repository.
I have confirmed this locally by running:
➜  dcos-commons git:(master) mv .git not.git
➜  dcos-commons ./gradlew testClasses
Parallel execution is an incubating feature.

> Configure project :scheduler
fatal: Not a git repository (or any of the parent directories): .git

FAILURE: Build failed with an exception.

* Where:
Build file '/private/tmp/dcos-commons/sdk/scheduler/build.gradle' line: 9

* What went wrong:
A problem occurred evaluating project ':scheduler'.
> Process 'command 'git'' finished with non-zero exit value 128

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 4s

The immediate fix for this PR: Remove the .* line from .dockerignore.
Follow-up steps:

Fix the getGitHash function.
Add set -e to the builds config.

Hm didn't help. https://teamcity.mesosphere.io/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=1186922&_focus=2761
Let me try different syntax.

Actually, docker seems to obey that directive, the problem must be elsewhere:
porridge@beczulka:~/Pulpit/work/mesosphere/code/dcos-commons$ docker build .
Sending build context to Docker daemon    126MB
Step 1/34 : FROM ubuntu:18.04
 ---> 16508e5c265d
Step 2/34 : RUN mkdir /tmp/repo/
 ---> Running in 63bdac07e4ec
Removing intermediate container 63bdac07e4ec
 ---> 59ede682bd51
Step 3/34 : COPY / /tmp/repo/
 ---> 9d2fc6e232ce
Step 4/34 : RUN ls -al /tmp/repo && false
 ---> Running in 016aa08779c8
total 184
drwxr-xr-x 1 root root  4096 Aug 30 13:05 .
drwxrwxrwt 1 root root  4096 Aug 30 13:05 ..
drwxr-xr-x 8 root root  4096 Aug 30 12:51 .git

It could also be that the docker client we use on TC does not understand !.

It could also be that the docker client we use on TC does not understand !.

Do we know what docker version TC is running?

It could also be that the docker client we use on TC does not understand !.

Do we know what docker version TC is running?

I don't, and it's not visible in the build log.

[15:22:31][Step 4/6] An error has occurred: FatalError: git failed. Is it installed, and are you in a Git repository directory?
[15:22:31][Step 4/6] Check the log at /root/.cache/pre-commit/pre-commit.log
[15:22:31][Step 4/6] The command '/bin/sh -c cd /tmp/repo/ &&     ./gradlew testClasses &&     pre-commit install-hooks &&     cd / &&     rm -rf /tmp/repo/' returned a non-zero code: 1
[15:22:31][Step 4/6] + echo '
[15:22:31][Step 4/6] ##teamcity[setParameter name='\''DOCKER_IMAGE'\'' value='\''dcos-commons:c5714ef'\'']
[15:22:31]
[Step 4/6] Incorrect property name.
Valid property list format is (name( )*=( )*'escaped_value'( )*)* where escape symbol is "|"
[15:22:31][Step 4/6] '

I have the changes ready. Waiting for https://github.com/mesosphere/dcos-commons/pull/2646 to merge before pushing to trigger tests again.

I have the changes ready. Waiting for #2646 to merge before pushing to trigger tests again.

I don't think that #2646 is going to pass without the additional Dockerfile change -- as is indicated by the failing Cassandra tests.
Note from the build there:
[10:25:43]	[Step 6/9] ++ egrep '^(Dockerfile|test_requirements.txt|.dockerignore)$'
[10:25:43]	[Step 6/9] ++ git diff --name-only origin/master
[10:25:43]	[Step 6/9] + matched_files=.dockerignore
[10:25:43]	[Step 6/9] + set -e
[10:25:43]	[Step 6/9] + [[ -n .dockerignore ]]

Meaning that we will also have to copy the .dockerignore file from master in this case (or remove .dockerignore from the list of files checked.


How does it work?

Hello!
Please, can you explain how to run this program? I would need to convert some WEM file into WAV.
Thanks in advance

Apologies for the month late response.
Have you even opened the EXE file? Attempting to open the EXE file will show you exactly how to use it.

I'm closing this issue since you seem to have nothing else to add to it and it's been a year. Whoops.

Sorry for opening this back, but how do you go from Wave file or OGG file back to WEM?


Trying to add a component to demo code fail (not added to build)

First thx, this project really has me exited, it'd be great to share "codebase" between engineers and designers.
Repro case
steps:

git clone
yarn
yarn build
add component
build (build 'succeed' but component is not found)

yarn build output:

I am expecting, in lib folder after building, to see a new folder (Text) appear, with a Title.js file in it.
What am I missing, is Typescript required ?
Are there more step than "just" importing the compo in the index.ts at the root of the project for the build job to register the new compo ?

@denisflorkin I think you just added the export { Title } from "./_production/components/Text/Title"; to the wrong place. If you add it to the root level index.ts file it should come up when you run yarn build


Fixes work of inspectResponse in case of ContentLength=-1

- What I did
Provide a fix for https://github.com/docker/docker/issues/30500. Unable to build dockerfile hosted remotely if ContentLength=-1
- How I did it
I've sliced preamble array for a number of bytes  actually read from stream in this  line 	rlen, err := r.Read(preamble)
- How to verify it
In TestMakeRemoteContext replace remoteURL := serverURL.String()
with 	remoteURL := "https://raw.githubusercontent.com/mkuznyetsov/dockerfiles/master/Dockerfile"
dockerfile content should be
[70 82 79 77 32 99 111 100 101 110 118 121 47 117 98 117 110 116 117 95 106 100 107 56 58 108 97 116 101 115 116 10]
instead of
[70 82 79 77 32 99 111 100 101 110 118 121 47 117 98 117 110 116 117 95 106 100 107 56 58 108 97 116 101 115 116 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:skabashnyuk/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

Can you consider adding an UT?

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:skabashnyuk/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842353497528
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

test added
without fix

Sun Jan 29 22:21:43 UTC 2017
=== RUN   TestUnknownContentLength
--------
-1
--------
--- FAIL: TestUnknownContentLength (0.00s)
	remote_test.go:169: Corrupted response body FROM busybox
FAIL
coverage: 11.9% of statements
exit status 1
FAIL	github.com/docker/docker/builder	0.014s
make: *** [test-unit] Error 1

with fix
---> Making bundle: test-unit (in bundles/1.14.0-dev/test-unit)
Sun Jan 29 22:20:35 UTC 2017
=== RUN   TestUnknownContentLength
--------
-1
--------
--- PASS: TestUnknownContentLength (0.00s)
PASS
coverage: 11.9% of statements
ok  	github.com/docker/docker/builder	0.010s

LGTM
ping @docker/core-engine-maintainers


Problem with GPU Conversion

Error Received:
The application was unable to allocate enough GPU memory to use this model.
Please close any GPU intensive applications and try again.
If the error persists, your GPU might not be supported.
GPU used: NVIDIA GTX 1650Ti 4GB VRAM
Any solution for this issue ?

did u install cuda?

did u install cuda?

Yes, I have already installed latest cuda driver.


iOS8 Issue when Input is present.

Our header has an input embedded in it. In iOS8, if there is an input present and the user focuses on it, iOS8 scrolls the page back to the top. Whereas Android and iOS7, the page stays in the same place.
Has anyone else run into this issue?
I recreated this on my site bettycrocker.com. I also recreated it on the headroom site by remote debugging and adding an input into the html.
Thanks,
Trang

Could you create a reduced test case for this? I don't have the time to do so myself.


MongoBee do not work on Atlas due to findRequiredChangeAndAuthorIndex

In class com.github.mongobee.dao.ChangeEntryIndexDao
        MongoCollection indexes = db.getCollection("system.indexes");
Atlas forbid accessing to system directly to fix it I propose to update the code to
        MongoCollection indexes = db.getCollection(changelogCollectionName + ".indexes");
See stackoverflow

Hello, I also opened an issue and made an PR like 2 weeks ago and I haven't got any feedback.As I really needed that fix and I couldn't wait, we decided to forked this repository and make available in github and maven(1.12 current version). I added some features such as lock expiration(specially useful in containerised environments like Kubernetes) and that index issue.
Feel free to use it and collaborate. I will review more often

Oh Thank you very much @dieppa
I will maybe switch to your fork then.
I wanted to propose a PR but I could not do it maybe I will help on your fork then.

Great. as you can see still need much test coverage, but we have tested here and works fine.
Hope it helps

Maybe i can help writing some test cases
Le jeu. 26 avr. 2018 11:39, Dieppa<EMAIL_ADDRESS>a écrit :

Great. as you can see still need much test coverage, but we have tested
here and works fine.
Hope it helps
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mongobee/mongobee/issues/86#issuecomment-384688466,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEhtWvayDLk6nTcGgp_7ue-ZtDOFL_KBks5tsepHgaJpZM4TfoX5
.

That would be great!

@peanutpi: It's published. You can find it in: https://mvnrepository.com/artifact/com.github.cloudyrock/mongock/1.12

Github repository https://github.com/cloudyrock/mongock


A11y_SQLAzureDataStudio_ServerDashboard_ServerDashboard_Screenreader: Voiceover announces as ‘Empty Table’ when navigated to search section’s table.

Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHubTags:#A11y_SQLAzureDataStudioBenchmark;#A11yMAS;#A11ySev2;#A11yTCS;#SQL Azure Data Studio;#Benchmark;#DesktopApp;#MacOS;#MAS1.3.1;#Screenreader;
Environment Details:
Application Name: Azure Data Studio
Version: 1.15.0-insider
Commit: 3a8b74a
Date: 2020-02-11T05:49:41.181Z
VS Code: 1.42.0
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.3.0
Mac OS:10.15.3
Additional Details:
Mac OS:10.15.3
MAS References: MAS1.3.1
Repro Steps:

Launch Azure Data Studio.
Connect to server.
In the Connections pane, right-click on a server & select Manage.
Launch voiceover
Navigate to Search section’s table present below editbox using Control+ Option+ arrow key

Actual:
While Voiceover is on and navigated to Search section’s table which is present below editbox using Control+ Option + arrow key, voiceover announce as Empty table.
Same issue is observed in Database Dashboard screen: 1. Launch Azure Data Studio.2. Connect to server.3. In the Connections pane, navigate to server --> database --> right click on any database & select Manage.
Expected:
While Voiceover is on and navigated to Search section’s table which is present below editbox using Control+ Option + arrow key, voiceover should announce in the format ‘Table_Name Table’.
User Impact:
Screen reader users will think as Search section’s table is not having any data.
Attachment link for Reference:
9291_A11y_SQLAzureDataStudio_ServerDashboard_ServerDashboard_Screenreader.zip

it is a tree control, not sure why is it reading it as table

test with other screen readers to see whether it is reading the widget as tree and announce the item count. close as external voice over issue if works fine with other screen readers.

this worked well with narrator and seems to be voiceOver issue, we are using the vscode tree UI element and they also have the same problem: https://github.com/microsoft/vscode/issues/40601
closing as an external issue

GithubTags:#Closed; Version 1.41.1

GitHubTags:#SQLADS-MAC-Feb2020;


Ability to download LLAMA2 7b 32k context

https://together.ai/blog/llama-2-7b-32k
https://github.com/togethercomputer/OpenChatKit
https://huggingface.co/togethercomputer/LLaMA-2-7B-32K

The import doc shows how you can import any supported model: https://github.com/jmorganca/ollama/blob/main/docs/import.md
I will go ahead and close this, but if there is anything else you need, you can reopen this if related, or a new issue.


Adds LogEntry and LogEntryComment with full text searching

@lukecampbell 3 Tests failed.  Need to resolve ASAP.

I will punch you straight in the gaba

As long as the tests start passing, I do not care where you punch me.

I Like it.


how to set size?

i want to set indicator_selected and indicator_unselected the same size ,how to do it? thank you !

https://github.com/ongakuer/CircleIndicator/issues/93


hmac_totp() crashes in EVP_Q_mac() on Sparc platform with OpenSSL 3.0.x

When compiling and running acvp_app on Sparc platform with OpenSSL 3.0.x, the application crashed in hmac_totp() function when calling EVP_Q_mac(). I narrowed down the issue to 'int len' variable. It is defined as int (4 bytes long), but pointer to long unsigned int (8 bytes long) is passed to EVP_Q_mac(). That triggers crash on Sparc when trying to write 8 bytes to 4 byte variable. Following patch fixed the problem:
diff --git a/libacvp-2.1.0/app/app_utils.c b/libacvp-2.1.0/app/app_utils.c
--- a/libacvp-2.1.0/app/app_utils.c
+++ b/libacvp-2.1.0/app/app_utils.c
@@ -162,12 +162,12 @@
                      int hash_max,
                      const char *md_name,
                      unsigned int key_len) {
-    int len = 0;
+    size_t len = 0;
     unsigned char buff[MAX_LEN];

-    EVP_Q_mac(NULL, "HMAC", NULL, md_name, NULL, key, key_len, msg, T_LEN, buff, MAX_LEN, (long unsigned int *)&len);
+    EVP_Q_mac(NULL, "HMAC", NULL, md_name, NULL, key, key_len, msg, T_LEN, buff, MAX_LEN, &len);
     memcpy_s(hash, hash_max, buff, len);
-    return len;
+    return (int)len;
 }
 #endif

That makes sense;  I will get this resolved ASAP. Thanks for reporting!

Sure, glad to help!

Addressed in #854, will be in an upcoming release. Thanks again!

You are welcome. Thank you for addressing it so quickly!


data, errors not available in generated SDK

Hi. I was able to generate the SDK and types properly from my GraphQL schema and operations via mesh and import it into the code, but I was not able to find either data or errors keys as suggested here: https://graphql-mesh.com/docs/recipes/as-sdk
const { data, errors } = await sdk.myQuery({ someVar: 'foo' });

(this.sdk is initialized to getSdk(sdkRequester);)
Rather I get the result of my mutation directly like this:

In the generated file, this is the type I have for the mutation:
export type Requester<C= {}> = <R, V>(doc: DocumentNode, vars?: V, options?: C) => Promise<R>
export function getSdk<C>(requester: Requester<C>) {
  return {
    addAuthMethod(variables: AddAuthMethodMutationVariables, options?: C): Promise<AddAuthMethodMutation> {
      return requester<AddAuthMethodMutation, AddAuthMethodMutationVariables>(AddAuthMethodDocument, variables, options);
    },
}

Am I doing something wrong? Wondering how I will handle the errors. Should I use a catch block as opposed to the docs? Thanks.

Sorry for that, SDK example in the website seems wrong. I fixed that. You should use a try/check block.

@ardatan Ah. Thanks for the clarification. Will close this then.


PyUSB failure to read from Keyboard or Flash Drive on Mac due to Permission Errors

When running the following code https://pastebin.com/6pcyGHKg that aims to read data from a keyboard or flash drive with PyUSB, Python 3.6.3 and a Mac on OSX 10.13. I get an error mentioning Insufficient Permissions. I have tried running the code with while logged in as root and I still get the same issue.
Traceback (most recent call last):
File "usbReader.py", line 27, in
main(1)
File "usbReader.py", line 24, in main
data = dev.read(endpoint.bEndpointAddress,endpoint.wMaxPacketSize)
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/usb/core.py", line 975, in read
intf, ep = self._ctx.setup_request(self, endpoint)
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/usb/core.py", line 102, in wrapper
return f(self, *args, **kwargs)
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/usb/core.py", line 216, in setup_request
self.managed_claim_interface(device, intf)
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/usb/core.py", line 102, in wrapper
return f(self, *args, **kwargs)
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/usb/core.py", line 167, in managed_claim_interface
self.backend.claim_interface(self.handle, i)
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/usb/backend/libusb1.py", line 811, in claim_interface
_check(self.lib.libusb_claim_interface(dev_handle.handle, intf))
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/usb/backend/libusb1.py", line 595, in _check
raise USBError(_strerror(ret), ret, _libusb_errno[ret])
usb.core.USBError: [Errno 13] Access denied (insufficient permissions)

You have to read libusb FAQ to understand that you will not be able to use libusb/pyusb under Mac OS X for those device bound to kernel driver.
https://github.com/libusb/libusb/wiki/FAQ#How_can_I_run_libusb_applications_under_Mac_OS_X_if_there_is_already_a_kernel_extension_installed_for_the_device

Close this for now.


Be able to check the status of running deployment without JobId

Is your feature request related to a problem? Please describe.
Currently we have one CI/CD job for each non-prod environment we deploy to, and for each new commit to our branch, a new pipeline is created.
Each job consists in 4 deployment, one for pre destructive package, a second for the full components deployment except for reports/reportTypes and dashboards, a third one for only reports/reportTypes and dashboards, and the last one for post destructive.
The problem is, if person 1 makes a commit, and during the full components deploy of job 1, person 2 makes another commit, a second job is created to the same environment, and the pre destructive deployment starts and fails, because we already have an deployment in progress (job 1). We would like to check if there is already an deployment running on the environment, and if there is, skip this deployment.
What are you trying to do
Run sfdx force:source:deploy:report (or mdapi equivalent) -u CONNECTION without passing an jobId on -i, and as a result get the deployment status of current running deployment
Describe the solution you'd like
when we run the deploy:report command, sfdx should return the deployment status of current running deployment, without an jobId
Describe alternatives you've considered
There is one workaround for this, run an SOQL query thru sfdx and handle the result there, but it is not a very good solution.

@Renan-Mastropaolo could you explain why the second job fails? Why isn't it added to the queue?

@AllanOricil the second job fails after some time. It indeed is added to the queue, but after some time waiting, the deployment fails with message "LIMIT_EXCEEDED: Try deploying again. Your deployment exceeded its maximum retry limit. If you keep seeing this error, please contact Salesforce Customer Support."

How exactly skiping a deployment would solve your issue?
"We would like to check if there is already an deployment running on the environment, and if there is, skip this deployment."
Could you share more details of your automated deployment process? I really don't see how this feature request would be useful when there is already a queue organizing deployments.

We use shared environments for UAT with other teams and other repos, so we would like to check, on the running CI/CD job, if there is already an deployment running on UAT and wait until this deploy is done to start a new one.

We use shared environments for UAT with other teams and other repos, so we would like to check, on the running CI/CD job, if there is already an deployment running on UAT and wait until this deploy is done to start a new one.

Why would you need to manage the queue by yourself if it is already managed by SF? There is no way a second deploy job can start in a Sandbox before the current one is done.
1 - Team 1 enqueues a Deploy Validation to Sandbox X
2 - Team 2 enqueues a Deploy Validation to Sandbox X
3 - Team 1 Deploy Validation fails on Sandbox X
4 - Team 2 Deploy Validation Starts on Sandbox X
5 - Team 1 fixes issues and enqueues a new Deploy Validation job on Sandbox X
6 - Team 2 Deploy Validation succeeds on Sandbox X
7 - Team 2 enqueues a Deploy job on Sandbox X ( this job just runs a Quick Deploy using the Validaiton Job ID)
8 - Team 1 Deploy Validation succeeds on Sandbox X
9 - Team 1 enqueues a Deploy Job on Sandbox X

But in our case, if Team 2 enqueues a Deploy to Salesforce, this deployment fails before start with error message "LIMIT_EXCEEDED: Try deploying again. Your deployment exceeded its maximum retry limit. If you keep seeing this error, please contact Salesforce Customer Support."
And for each CI/CD job we run 4 deployments to Salesforce: Pre deployment destructive, components deployment, Reports/ReportTypes/Dashboards deployment, Post deployment destructive. So in your scenario our flow would be something like that:

Team 1 pushes a commit (commit 1) to Team1's git repo.
CI/CD creates the job for commit 1, pre-deployment destruction starts on Sandbox X.
Team 2 pushes a commit (commit 2) to Team2's git repo.
Commit 1 pre-destruction ends with success, components deployment starts for commit 1 on Sandbox X.
CI/CD creates the job for commit 2, pre-deployment destruction starts on Sandbox X.
Commit 2's pre-deployment destruction is enqueued on Sandbox X
Components deployment for commit 1 is still running on Sandbox X.
Commit 2's pre-deployment destruction fails with error message "LIMIT_EXCEEDED: Try deploying again. Your deployment exceeded its maximum retry limit. If you keep seeing this error, please contact Salesforce Customer Support."
CI/CD job for commit 2 fails and no more deployments are created.

CI/CD creates the job for commit 3, pre-deployment destruction is enqueued on Sandbox X.
Commit1's Components deployment end successfully, commit3's pre-deployment destruction starts, commit1's Report/ReportTypes/Dashboards deployment is enqueued.
Commit3's pre-deployment destruction is still running.
Commit1's Report/ReportTypes/Dashboards deployment fails with error message "LIMIT_EXCEEDED: Try deploying again. Your deployment exceeded its maximum retry limit. If you keep seeing this error, please contact Salesforce Customer Support."
No more developers commiting, Commit 3 job runs successfully.

It sounds like your CI system should do a better job of orchestrating concurrent builds -- this doesn't seem like a problem specific to Salesforce. It's the common problem of having a single destination environment and multiple commits that need to get there.
For example, on GH Actions, you can define a concurrency property to protect against multiple jobs running at the same time:
https://docs.github.com/en/actions/using-jobs/using-concurrency

@Renan-Mastropaolo take a different approach. Instead of deploying only what each team has developed, try to deploy everything that hasn't been deployed yet. Every time a deployment to a sandbox succeeds, create a tag for saving the state of that sandbox (it is like a checkpoint). When I say a "deployment" I mean that all steps run succesfully for that particular commit, and not SF deployments. If one of the steps fails, your tag isn't updated for that environment, which means the next commit will try again to deploy those changes. This next commit can be just a fix for what went wrong in the previous deployment, or a new feature from another team.
You can use this sfdx plugin to compute diffs between checkpoint tags: https://github.com/scolladon/sfdx-git-delta
Then to ensure your SF pre and post deployments steps are scheduled properly, and not in between jobs, use these two features from this sfdx command

https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference_force_source.htm#cli_reference_force_source_deploy

Thanks @AllanOricil and @daveespo for this tips.
I get that this is not an error on sfdx-cli side and more related to how our pipelines were built in the first place.
Just thought about this feature because it would fit well in our current implementation of CI/CD and deployment orchestration.

Thanks for posting and thanks for the responses Allan and Dave.  The team is in agreement with how Allan and Dave responded so this is not a feature that would be prioritized.  If you want to keep your CI/CD as is then your best bet is what you mentioned already in your issue description; the soql command.  You might want to explore using sandbox source tracking as another option.


Header-only mode for Boost unit tests

Description
The new solver unit test is failing on newer Red-Hat-based distributions:

https://github.com/neuronsimulator/nrn-build-ci/runs/7758969675?check_suite_focus=true#step:7:34958
https://github.com/neuronsimulator/nrn-build-ci/runs/7758969737?check_suite_focus=true#step:7:34889
https://github.com/neuronsimulator/nrn-build-ci/runs/7758969895?check_suite_focus=true#step:7:34954

This seems to be because that test included the Boost unit test framework in header-only mode but then links against an external copy of the library.
https://www.boost.org/doc/libs/1_79_0/libs/test/doc/html/boost_test/usage_variants.html implies that we need to define different macros for linking against shared/static libraries, and https://cmake.org/cmake/help/latest/module/FindBoost.html makes it look difficult to guarantee static and/or shared, so header-only mode seems like the simple way out.
How to test this?
Build the tests, run them -- you might get an error, or you might need to run them in valgrind to see it.
Use certain branches in CI pipelines.

CI_BRANCHES:NEURON_BRANCH=master,NMODL_BRANCH=master,SPACK_BRANCH=develop

https://github.com/neuronsimulator/nrn-build-ci/actions/runs/2831964189 is testing this


refactor: support import deduplication for different aliased packages…

… in override_file.

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

[Enhancement] #116

2. What is the scope of this PR (e.g. component or file name):

kclvm/tools/src/query/override.rs
internal/kclvm_py/tools/query/override.py

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[x] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

kclvm/tools/src/query/tests.rs

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

11 of 11 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 59.341%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
22234

Relevant Lines:
37468

💛  - Coveralls


Mobile browser doesn't seem to understand the clicking event

Do you want to request a feature or report a bug?
Report a bug

What is the current behavior?
I have a clicking event in javascript but on the mobile browser it doesn't seem to "read" the function. The event fires after 3 seconds.
I have a 3d object that appears on a marker. there is a text which is hidden by default. the event is, when the object is clicked the text appears. However, after 3 seconds without doing anything the text appears.
If the current behavior is a bug, please provide the steps to reproduce.
<script>
    AFRAME.registerComponent('object-model', {
      init: function () {
        const castle = document.querySelector("#castle");
        const text = document.getElementById('text-box');
        castle.addEventListener('click', function (event) {
          if(text.object3D.visible == false && event.detail.cursorEl){
            text.object3D.visible = true;
          }
        });
      }
    });
 </script>

<a-scene id="thescene" cursor="rayOrigin: mouse" embedded arjs="sourceType: webcam; trackingMethod: best;">
      <a-light type="point" color="white" position="0 5 0" intensity="3"></a-light>
      <a-assets>
        <a-asset-item id="mega" src="mega/scene.gltf"></a-asset-item>
      </a-assets>

      <a-marker preset='custom' type='pattern' url='tiger.patt'>
        <a-entity gltf-model="#mega" scale="0.05 0.05 0.05" position="0 0 0" rotation="-90 0 0" object-model id="castle"></a-entity>
        <a-entity geometry="primitive: plane;" material="opacity: 0">
          <a-text value="Clicked!" visible="false" id="text-box" position="-0.425 0.293 -0.531" rotation="-84.347 54.042 -51.893"></a-text>
        </a-entity>
      </a-marker>

      <!-- add a basic camera -->
      <!-- So object will land on marker -->
      <a-entity camera>
      </a-entity>
    </a-scene>

What is the expected behavior?
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Operating System and Device Name
Samsung S9. using google chrome.

Hey,

The event fires after 3 seconds.

This isn't a AR.js bug, this is a feature of a-frame called "fuse". To turn this off you need to add to your cursor attribute cursor="fuse: false; rayOrigin: mouse"

Thanks @LaurenceNairne
Further options here: https://aframe.io/docs/0.8.0/components/cursor.html#fuse-based-cursor


please expose more attributes in the Processor Task datasource

stuff like start and end and status times

Add more field entries to valueMapper in stroom.processor.impl.db.ProcessorTaskDaoImpl#ProcessorTaskDaoImpl and add those extra fields to stroom.processor.shared.ProcessorTaskFields

Priority would be good too please, this would give a better view into any processing backlogs


Add inline_threshold to open_asdf in asdf.py

There are several ways to instantiate a new asdf object. Two are by calling the __init__ method or the open_asdf function. They need to support the same argument lists. In particular, the inline_threshold argument is not in the open_asdf parameter list and needs to be added.

I'm not sure we can support the exact same arguments in all cases, but I agree we're not handling inline_threshold correctly in certain cases.
I'm actually thinking the right solution here is might be to make sure that if you call asdf.open with another AsdfFile object, then the new object uses the same inline_threshold as the original. Does that make sense, or am I missing something?

Is there a reason inline_threshold can't just be set on write instead of open?

Doesn't help me, I'm calling asdf.open with a string argument. And I believe this is a common use case.

@jdavies-st that's probably the right approach. The reason for not doing it that way in the first place is basically it was much easier to implement this way. And now unfortunately we have the problem of probably having to deprecate the existing usage.
@bernie-simon just to understand your use case, are you trying to open an existing ASDF file and then write it back out while still preserving the original inline_threshold?

Datamodels reason for existing is that it hides the differences between fits files and asdf files. Just as it can read a fits file, modify it, and write it out again, you can read an asdf file, modify it, and write it out again. This is not very common, but the code needs to support it. The "original inline_threshold" is the only inline_threshold as far as the code is concerned.

I need to rethink the inline_threshold API. It turns out that there was already a parameter to update and write_to called auto_inline that performs a similar function. I'd like to change the default for that parameter and maybe revert the inline_threshold PR altogether. Unfortunately we'll have to make the associated change in JWST, but I'm going to assert my right to do this since the change is not yet in a released version of ASDF.
cc @nden

This affects Datamodels too. If inline_threshold is removed Datamodels will break.

Yes, we'll need to update datamodels to reflect any change here.

I will soon no longer be able to work on Datamodels, so we minus I equals you. The most recent change to inline_threshold is in a branch pending a merge. I'm inclined to go and rip out any mention of it in Datamodels, but time grows short.

@bernie-simon Can you link to that branch here?


Rethink about Button Dropdowns

Right now we're using list templates to achieve button dropdowns and split button dropdowns. This makes it un-naturel because a user would except to use buttons rather than lists.
Maybe a button container region that holds APEX buttons?

Single button dropdown and split button dropdown will be an native APEX button that will be moved inside it's list.


"mismatched types" error when passing model to OcrEngineParams

Hello,
In this small snippet coming from the example :
    let detection_model = Model::load_file(detection_model_path).unwrap();
    let recognition_model = Model::load_file(rec_model_path).unwrap();

    let engine = OcrEngine::new(OcrEngineParams {
        detection_model: Some(detection_model),
        recognition_model: Some(recognition_model),
        ..Default::default()
    })
    .unwrap();

There's an issue :
error[E0308]: mismatched types
   --> src/main.rs:29:31
    |
29  |         detection_model: Some(detection_model),
    |                          ---- ^^^^^^^^^^^^^^^ expected `rten::model::Model`, found `Model`
    |                          |
    |                          arguments to this enum variant are incorrect

How are we supposed to get the rten::model::Model ?

My Cargo.toml is very basic :
[dependencies]
ocrs = "0.9.0"
rten = "0.14.1"
screenshots = "0.8.10"
tokio = { version = "1.42.0", features = ["full"] }```

And I only reference to rten:Model because I can't import rten::model since it's a private module.

On Tuesday, December 17th, 2024 at 10:30, Robert Knight<EMAIL_ADDRESS>wrote:

> This error likely means there are two different copies of rten being used. The function is expecting a Model from one version but is getting a Model from the other. Check your Cargo.toml / Cargo.lock file and make sure only one version is used.
>
> —
> Reply to this email directly, [view it on GitHub](https://github.com/robertknight/ocrs/issues/144#issuecomment-2547929934), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AWSLWOYUD2Q5ZECIFIF3PVD2F7VKTAVCNFSM6AAAAABTX5KQGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBXHEZDSOJTGQ).
> You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

My Cargo.toml is very basic :

Can you look into your Cargo.lock file. I suspect the issue is that ocrs v0.9.0 depends on rten v0.13.1. See crates.io info whereas you have a local dependency on rten v0.14.1. If you change your local dependency to v0.13.1 that should fix the problem.
I should fix the problem in future by a) publishing a new version of this library and b) by making it easier to use this library without needing to add rten to your own project.

And I only reference to rten:Model because I can't import rten::model since it's a private module.

rten::Model is the same type as rten::model::Model, just a public re-export.

Indeed it is exactly what you suspected. Thank you for that !
On Tuesday, December 17th, 2024 at 16:51, Robert Knight @.***> wrote:

My Cargo.toml is very basic :

Can you look into your Cargo.lock file. I suspect the issue is that ocrs v0.9.0 depends on rten v0.13.1. See crates.io info whereas you have a local dependency on rten v0.14.1. If you change your local dependency to v0.13.1 that should fix the problem.
I should fix the problem in future by a) publishing a new version of this library and b) by making it easier to use this library without needing to add rten to your own project.

And I only reference to rten:Model because I can't import rten::model since it's a private module.

rten::Model is the same type as rten::model::Model, just a public re-export.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


[ENH] Keyboard key releases.

Collecting key-release events
I've added a get_releases() method on ExperimentController to be able to get key release events.
There's room for refactoring as I've just duplicated most of the keypress code.
I haven't been able to run/ adapt the tests properly since nosetest in a virtualenv uses global packages and I get the _check_pyglet error. resolved this with http://stackoverflow.com/a/864967
I have added an example script.
Summary of todo's:

[x] fix docstring
[x] fix event type argument
[x] make press events dependent on argument
[x] fix event tuple structure
[x] fix demo
[x] runtime error for TDT
[x] EC tests

Changes Unknown when pulling 050af5ead0bf4c395c6ff3ded08813e8c148153e on ilogue:get-releases into ** on LABSN:master**.

Changes Unknown when pulling e1fa9e635796fb7a7ba087c842a77da5c02cb499 on ilogue:get-releases into ** on LABSN:master**.

The real sticking point for me is that this will work for Pyglet only. It will not work for Cedrus boxes, or the TDT -- support would need to be added for those devices, too. For the Cedrus it might not be so bad (would have to look at what pyxid gives you) but for the TDT you'd have to modify the circuit.

(And Pyglet keypresses are not designed to be high-accuracy, so having it only be there isn't of much benefit for experiments)

Changes Unknown when pulling 5a343f68114abcdbc38b8afa2466050c50197678 on ilogue:get-releases into ** on LABSN:master**.

Changes Unknown when pulling c319dc1c922d7e073aae97d7b2b66b949c91e846 on ilogue:get-releases into ** on LABSN:master**.

Okay so I was thinking how to refactor this with less repeated code; two options here I think

the event tuples contain a third value indicating press vs. release
we maintain two separate 'buffer' lists, but the methods update/read from both.

I imagine the methods would then take an argument with which the user can specify which events they want. Would the default be presses only?
Anyone want to weigh in on this? @drammock @Eric89GXL @rkmaddox

the event tuples contain a third value indicating press vs. release

The internal, private list for Cedrus (and Pyglet if necessary) can keep both types of events, sure.

I imagine the methods would then take an argument with which the user can specify which events they want

I don't think we should change the existing user-facing functions at all. get_presses should stay, and the new calls you added get_releases can also stay. Separating the presses from releases can be done in private functions as necessary.

Maybe internally store as a dict with keys key, press, and release?  I think I disagree with @Eric89GXL though: I would rather see a single get_presses function with kwargs for whether to return press time, release time, or both.

I would rather see a single get_presses function

I can live with that

Changes Unknown when pulling f3f8214ff77aa9c1e475b2a38106c7ba0aabd833 on ilogue:get-releases into ** on LABSN:master**.

For now, if ExperimentController._response_device == 'tdt', we should throw a RuntimeError if users call get_presses(..., type='releases') or type='both'.

So other than my copious comments, the only other thing missing is a few tests, which should probably go around here

Changes Unknown when pulling 0b35ada0431b17107f2f9de2e29a95ed87bb8313 on ilogue:get-releases into ** on LABSN:master**.

Note that correct_presses is currently also responsible for logging events. So if we filter out events before we pass then to correct_presses, they won't be logged. Is that intended?
However if we don't filter events in _retrieve_events, then a method like _wait_for_one_press will have to check for event type itself.

Changes Unknown when pulling b85b865479061e64acff7f3dcd00f93280f5bafa on ilogue:get-releases into ** on LABSN:master**.

I think it's acceptable to only log the types of events the user cares about. Especially since it's impossible to, e.g., press a key once and release it twice. Edge cases like: press and hold without releasing during the listening interval, can be handled via type='both'

Any remaining todo's? @drammock

Other than that last nitpicky docstring comment, LGTM.  @Eric89GXL does this have your blessing?

Changes Unknown when pulling 5b44b26c297ec88d338c98a4f771447be71ef91e on ilogue:get-releases into ** on LABSN:master**.

Not sure why the AppVeyor build is failing;
Test EC mouse click support ... SKIP: Skipping test: test_mouse_clicks: Appveyor OpenGL too old
Test setting background color ... SKIP: Skipping test: test_background_color: Appveyor OpenGL too old
Test EL methods ... SKIP: Skipping test: test_eyelink_methods: Appveyor OpenGL too old
Test logging to file (Pyglet) ... Command exited with code -1073740771

yeah, every once in a while it just fails on test logging to file (pyglet) and I don't know why either.  @Eric89GXL is the only one with the power to restart the appveyor jobs without doing an empty push --force to re-trigger the hook.

Changes Unknown when pulling 9d960cee6c48b90fcec8bf6b6aeddd373f6ebf54 on ilogue:get-releases into ** on LABSN:master**.

Changes Unknown when pulling d21dbb46cfdf2907e560ae3020565a3f44226e90 on ilogue:get-releases into ** on LABSN:master**.

Changes Unknown when pulling 175ec67c47ffa42e43287bea520e506b6c30ef08 on ilogue:get-releases into ** on LABSN:master**.


chore(ci): also build examples

@aymanbagabas @caarlos0: Any idea why the SSH example doesn't build? Not working locally either, getting:
# github.com/caarlos0/sshmarshal
../../../../.go/pkg/mod/github.com/caarlos0/sshmarshal@v0.1.0/marshal.go:29:6: MarshalPrivateKey already declared through dot-import of package ssh ("golang.org/x/crypto/ssh")
        ../../../../.go/pkg/mod/golang.org/x/crypto@v0.17.0/ssh/keys.go:302:6: other declaration of MarshalPrivateKey
../../../../.go/pkg/mod/github.com/caarlos0/sshmarshal@v0.1.0/marshal.go:35:6: MarshalPrivateKeyWithPassphrase already declared through dot-import of package ssh ("golang.org/x/crypto/ssh")
        ../../../../.go/pkg/mod/golang.org/x/crypto@v0.17.0/ssh/keys.go:308:6: other declaration of MarshalPrivateKeyWithPassphrase

github.com/caarlos0/sshmarshal

github.com/caarlos0/sshmarshal is no longer needed and can be replaced with golang.org/x/crypto ssh package.

Where’s the dependency? I checked charmbracelet/wish and charmbracelet/ssh and didn't see it.


Add categories to CRDs

What would you like to be added:
Add something like:
    categories:
    - gateway-api

or similar to the CRD spec
Why is this needed:
This allows people to do kubectl get gateway-api and get all associated types, instead of needing to do kubectl get gwc,gc,httproute,...

Good idea, I had no idea this was a thing.
/assign


missing method to convert cf-json "directly" to xarray

At the moment, the only direct cf-json "import" method converts to netCDF. I think a corresponding method to convert to xarray would be very useful, especially since "diskless" netCDF object creation was still experimental last time I checked.
This could also be just a small convenience function converting from some common intermediate format (dict?), or could actually be providing xarray as an intermediate format for subsequent netCDF and pandas conversions.

Thanks @rafa-guedes . I think that wavespectra link needs to be tree rather than blob? https://github.com/metocean/wavespectra/blob/master/wavespectra/input/cf_json.py
I added basic functionality for this a month or two ago (https://github.com/metocean/cf-json/compare/fix_issue7_json2xr), but hadn't merged that to master yet because back then nobody except myself seemed to need that direction of the conversion, and to make it generic to work with anything "compliant" to our own spec we still have to sort out one or two of those spec issues :) Let's talk when I'm back next week :)


Trigger on hover + multiple targets

I'm trying to trigger anime when hovering on a target and apply this to more than one selector, for exemple every li in a ul list or every button etc.
See pen: https://codepen.io/anon/pen/qjOKEY
Thanks!

Hey,
You must create loop
var buttonEl = document.getElementsByTagName('button');
for (var i = 0; i < buttonEl.length; i++) {
  var btn = buttonEl[i];
  animateButton(btn);
}

function animateButton(btn) {
  [...]
}

Alternatively, if you're just scaling the button like that, why not just use CSS?

@MichaelRise A classic loop is only working for the last element. Can't figure out why.
@alexchantastic I'm looking to use more animations than scaling.

The loop isn't working because you are using document.querySelector which will return the first element that it finds a match for in the DOM. You need to use document.querySelectorAll or document.getElementsByTagName as @MichaelRise suggested.
Here is a working example: https://codepen.io/alexchantastic/pen/XgXbgz


[Bug]:   Intermittent crashes on linux during idle time

Version

[X] I'm using version 1.7.0

Known issues

[X] I've checked Known issues

Existing issues

[X] I've checked Existing issues

What operating system are you using?
Linux
Operating System Version
Pop!_OS 20.04 LTS (Ubuntu derivative)
Reproduction steps

Run stretchly
walk away from computer for a while (1 hour or so)
Stretchly crashes
...
looks pretty consistent

Expected Behavior
no crash
Actual Behavior
crash
Relevant log output
nothing else around this:

stretchly[722501]: segfault at 319e3bec3000 ip 00007f7cb63ef621 sp 00007ffc897ae850 error 4 in libappindicator3.so.1.0.0[7f7cb63e8000+c000]

Preferences
No response
Additional information
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi, this is a bug in libappindicator3, see here: https://github.com/hovancik/stretchly/issues/633#issuecomment-716394124

Ah, sorry for the duplicate spam...


add Methodology to README - ApeSwap, Bancor, Dodo

Thanks Dustin! Just provided a couple minor feedback


Added ability to set token's lifespan for server mode

Hi,
subj
In some cases we need checks refresh/401 in tests. For this case we need configure exp field for server mode.
Here the little changes that add this funtionality.

Thanks for the PR. But I wonder: does your use case, i.e. testing if an expired token is rejected, really warrant a server configuration which is applied globally? I would have just added an option to the TokenConfig class to configure the lifespan.
Or do you mean you start the mock as a standalone application? In that case, I'd have added a CLI option to configure the lifespan. Alternatively, you could add another input field to the "login" page.

Thanks for the PR. But I wonder: does your use case, i.e. testing if an expired token is rejected, really warrant a server configuration which is applied globally? I would have just added an option to the TokenConfig class to configure the lifespan.
Or do you mean you start the mock as a standalone application? In that case, I'd have added a CLI option to configure the lifespan. Alternatively, you could add another input field to the "login" page.

Hello,
In my case, KeycloakMock is set up as a server directly in the test, and it is used to verify all authorizations. There are cases when I need to verify the correctness of token refreshing via URL and ensure that the new token is used in all parts. For this, I need the ability to specify the token's lifespan in the ServerConfig.
The application uses Spring oauth2 client to work with Keycloak, which automatically refreshes tokens internally. Therefore, I cannot use TokenConfig and getAccessToken.

I took the liberty of amending your fix commit so the pre-commit hook check is actually green. Otherwise, since your explanation makes sense, let's just go for it.


thaliMobile's use of setInterval will kill our battery dead

Right now in thaliMobile there is a function called peerAvailabilityWatcher that runs on a regular interval (currently every second) and it checks to see if we have any really old peer availability announcements that need to be cleaned up. But this means that the device cannot ever really go to sleep as it will keep waking up every second! This is an awesome way to obliterate battery.
Thankfully the fix is pretty easy. We just need to calculate when the next entry is supposed to expire and set our timer for that long. Once we have no entries left then we don't set any timer at all. Once we get notified of a new peer event and enter it into peerAvailabilities then we set a new timer.

The issues are fixed. But tests aren't passing in CI.But it doesn't appear to be our test.

@yaronyg so could we close this issue?


simulations for susie-glm, glmm (H0/H1:susie) with two GRM's

I used 1,3, 5 causal variants included in simulated datasets (pop/fam)  with two GRM's (theoretical/computed from genotypes) Tianyi prepared.  I not only ran all functions with such datasets but also used Andrew's simulation scheme to do 100 simulations (L=1,3,5) each using her genotype datasets giving signals to some snps.  I see that depending on the latter GRM,  both glmm's failed in the middle of the simulations. Generating plots of \alpha for susie-glmm with only stored results before failure shows the similar pattern that we expected. The null-glmm often failed.  Doing with theoretical GRM always has no domain error and shows the same patterns as in Andrew's glm implementation.   The domain error appears to happens due to random sampling from \tau^2*K for each simulation.  \xi's  subsequently fluctuating b/w + and -  and leads to the domain error.     I  will try some tweaks , e.g. run susie-glm for 'good' parameter values at some points inside susie-glmm  to make the algorithm robust to simulated data to have \xi go on the right direction to the solution.

@hkim89 there are various details I don't understand from your comment above , that I tried to clarify with you offline. But the high level question here is what's the difference between the theoretical vs the computed GRM that you think led to the error? For starters, could you compare the theoretical vs computed and see how big the difference is? Also is there any preprocessing you can do to check and verify that the input GRM is legit ?


Deprecate Blacklist Scanner

Story
Deprecate the Blacklist Scanner since there is low usage of it.

Duplicate of #3475


HARP-9982 Disable line clipping by default

We need to disable line clipping since HERE Vector Tiles will soon have a smaller margin.

Codecov Report

Merging #1466 into master will decrease coverage by 0.09%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #1466      +/-   ##
==========================================
- Coverage   56.88%   56.79%   -0.10%
==========================================
  Files         274      262      -12
  Lines       24557    24268     -289
  Branches     5490     5437      -53
==========================================
- Hits        13970    13782     -188
+ Misses      10587    10486     -101

Impacted Files
Coverage Δ

...re/harp-datasource-protocol/lib/TechniqueParams.ts
52.38% <ø> (ø)

...e/harp-mapview/lib/geometry/TileGeometryCreator.ts
43.57% <0.00%> (ø)

@here/harp-geometry/lib/ClipPolygon.ts
96.96% <0.00%> (-0.47%)
:arrow_down:

@here/harp-utils/lib/Mixins.ts
76.92% <0.00%> (ø)

@here/harp-test-utils/lib/WebGLStub.ts
100.00% <0.00%> (ø)

@here/harp-utils/lib/SampleBilinear.ts
100.00% <0.00%> (ø)

@here/harp-materials/lib/CopyMaterial.ts
100.00% <0.00%> (ø)

@here/harp-materials/lib/MSAAMaterial.ts
100.00% <0.00%> (ø)

@here/harp-omv-datasource/lib/OmvTile.ts
50.00% <0.00%> (ø)

@here/harp-utils/lib/UrlPlatformUtils.ts
100.00% <0.00%> (ø)

... and 32 more

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 ebc1921...b67ae58. Read the comment docs.

Codecov Report

:exclamation: No coverage uploaded for pull request head (minor-disable-clipping@a867cf4). Click here to learn what that means.
The diff coverage is n/a.


test: fix typos in test code

This PR fixes various typos in test code.

/retest

Legit test failure. Please fix. Thank you!
/wait

Hi @alyssawilk, thank you for updating the title.
I'll make sure to follow the title rule next time.
Hi @mattklein123, thanks for your comment.
I've just updated the patch.
Wish you both a great day ahead :)

Looks like CI is still unhappy.  I believe you can't change the expected output without changing the actual output.
/wait

Thank you very much, @alyssawilk.
I've just made an update. Hopefully CI is happy now :smile:


feat(pubsublite): add sample to create a Pub/Sub Lite export subscription

Added a sample for creating an export subscription to a Pub/Sub topic and test.

Depends on a new release of the pubsublite library.

Thanks @hongalex for reviewing!


Update dependencies

Update dependencies so that the package works with the latest framework versions in preparation for a stable v3 release. See #96 for context.
The PR's been rebased for convenient commit by commit review.
From sanic v21 view now requires defining the method get, post, ... independently otherwise will throw 405, thus the current approach of overriding dispatch_request won't work. The workaround is to just assign the individual method to dispatch_request
async def __handle_request(self, request, ...): ... # previously dispatch_request

get = post = put = head = options = patch = delete = __handle_request

Close #86
Close #92
Close #94
Close #98
Supersede #87, #89, #91, #95.
@erikwrede

Push a few more commits to add python 3.11 and remove 3.6 (EOL) which I suspect is what makes the tests fail.