Ability to use sub-objects as view

Not sure if this is an issue with JDL or JHipster.
relationship OneToOne {
    Tree{size(moon.size)} to Planet
}

Sorry for the bad example...
JDL won't allow the view to be a child object. (Planet has a child object 'moon' which has a size)
I've tried plenty of variations to try to get this to propogate to the Angular JS side to no avail.
Is this view used anywhere else besides on the frontend?

I dont think we support this yet.
On 4 May 2016 05:47, "Garrett Hopper"<EMAIL_ADDRESS>wrote:

Not sure if this is an issue with JDL or JHipster.
relationship OneToOne {
Tree{moon.size} to Planet
}
Sorry for the bad example...
JDL won't allow the view to be a child object. (Planet has a child object
'moon' which has a size)
I've tried plenty of variations to try to get this to propogate to the
Angular JS side to no avail.
Is this view used anywhere else besides on the frontend?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/jhipster/jhipster-domain-language/issues/16

It may be a bad example, but it's bloating the declaration... If we ever support something like that, a better syntax may be needed.
Moreover, I don't see a practical use cas for this. Can you give us a better example?

Best case I can think of is when you want an entity with a 1-1 relationship with the User.
Naturally you'd want to display the user's login.
entity Profile {

}
entity Connection {
    accepted Boolean
}
relationship OneToOne {
    Profile{user(login)} to User
}
relationship OneToOne {
    Connection{initiator(user)} to Profile
}

It'd be nice for the 'initiator' Profile on the Connection to display the user's login instead of the object.

``
relationship OneToOne {
Connection{initiator(user.login)} to Profile
}

I dont think we will do this as there is very little value for the
complications we would handle, you could easily modify the generated code
for this and this is a rare usecase
Thanks & Regards,
Deepu
On Wed, May 4, 2016 at 8:57 PM, Garrett Hopper<EMAIL_ADDRESS>wrote:

``
relationship OneToOne {
Connection{initiator(user.login)} to Profile
}
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/jhipster/jhipster-domain-language/issues/16#issuecomment-216854275

Very well.
Thanks

I'll include my workaround for anyone else who runs into this.
First, some sample JDL which gets rejected during yo jhipster:import-jdl  <schema file>.  The "user.login" portion causes a grammar/validation error, preventing generation:
entity UserProfile {
}
relationship OneToOne {
    UserProfile{user(login)} to User
}
entity Image {
    image ImageBlob
}

relationship ManyToOne {
    Image{profile(user.login)} to UserProfile
}

Note that the original yo jhipster:entity/json-based method does allow for dotted traversal in the "otherEntityField" entry, thus allowing for display/sort based on a useful field in this case rather than display/sort based on a json object (think value of simply 'user', which is a json object not very nice-looking for display).  The json equivalent of the interesting portion of the earlier JDL sample, from .jhipster/Image.json:
    {
      "relationshipId": 1,
      "relationshipType": "many-to-one",
      "relationshipName": "profile",
      "otherEntityField": "user.login"
      "otherEntityName": "userProfile",
    },

Also note that yo jhipster:import-jdl  <schema file> writes the entity json files into the .jhipster directory before proceeding with the user prompts stage.
So, the workaround is:

Edit your jdl files, avoiding the use of dotted traversal but taking note of which entities you'll need to massage in later steps
Run yo jhipster:import-jdl  <schema file>
Choose 'x' to abort.  At this point the .jhipster json files have been updated.
Fix up the json files, adding in the dotted traversal parts
Run for f in ``ls .jhipster``; do yo jhipster:entity ${f%.*} ; done (or your OS' scripty equivalent) to proceed with the user prompting and generation portion

Not ideal, but I do like the idea of it being the the json better than manual changes to the generated ui.
Thanks, @lukewpatterson

Ok first of all I think its working in the entity generator accidentally and not intentionally :smile: so if it works then fine lets leave it like that. @MathieuAA in that case you can decide if you want to support this in JDL or not

Hi, if it's already supported because it's has been designed, then I'll add it. If it's not, it could not work in another version and tests have to check that. What do you think, @jdubois?
Le 11 mai 2016 05:52:51 GMT+02:00, Deepu K Sasidharan<EMAIL_ADDRESS>a écrit :

Ok first of all I think its working in the entity generator
accidentally and not intentionally :smile: so if it works then fine
lets leave it like that. @MathieuAA in that case you can decide if you
want to support this in JDL or not

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/jhipster/jhipster-domain-language/issues/16#issuecomment-218355201

--
Mathieu ABOU-AICHI

No news from anyone, so I'll close this.


[Sensor] Improved Equirectangular sensor

Motivation and Context

Introduce equirectangular sensor. Unlike #1141, which is a prototype and contains a large amount of code duplication, this one refactors the existing class hierarchy to accommodate this new sensor.
Introduces an intermediate class called CubeMapSensorBase as the immediate parent class for FisheyeSensor and Equirectangular sensor.
Introduces another intermediate class named CubeMapShaderBase to be the parent class for specific sensor shaders.
Small fixes in both the C++ code and shader code.

Results:

How Has This Been Tested

Types of changes

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

Checklist

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Just updated the visual results in the description.


chore: release main

:robot: I have created a release beep boop
@dotcom-reliability-kit/crash-handler: 2.1.1
Dependencies

The following workspace dependencies were updated

dependencies

@dotcom-reliability-kit/log-error bumped from ^2.1.0 to ^2.1.1

eslint-config: 2.0.1
2.0.1 (2023-06-23)
Bug Fixes

set require-atomic-updates to warn level (6f9b2d3)

Documentation Changes

update script command to be used in package.json (1dfebc5)

@dotcom-reliability-kit/log-error: 2.1.1
Dependencies

The following workspace dependencies were updated

dependencies

@dotcom-reliability-kit/serialize-request bumped from ^2.1.0 to ^2.2.0

logger: 2.2.4
2.2.4 (2023-06-23)
Documentation Changes

link to the CloudWatch documentation (86d1a7a)

@dotcom-reliability-kit/middleware-log-errors: 2.1.1
Dependencies

The following workspace dependencies were updated

dependencies

@dotcom-reliability-kit/log-error bumped from ^2.1.0 to ^2.1.1

@dotcom-reliability-kit/middleware-render-error-info: 2.1.1
Dependencies

The following workspace dependencies were updated

dependencies

@dotcom-reliability-kit/log-error bumped from ^2.1.0 to ^2.1.1

serialize-request: 2.2.0
2.2.0 (2023-06-23)
Features

add request headers seriealization (ed23fc6)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/crash-handler-v2.1.1 :sunflower:

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/log-error-v2.1.1 :sunflower:

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/logger-v2.2.4 :sunflower:

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/middleware-log-errors-v2.1.1 :sunflower:

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/middleware-render-error-info-v2.1.1 :sunflower:

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/serialize-request-v2.2.0 :sunflower:

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/eslint-config-v2.0.1 :sunflower:


How to filter by spatial/temporal granularity to avoid unneccessary load on subscriber?

when writing demo-applications that subscribe to the messages published on the GB we noted cases where an unexpected large amount of messages caused issues for the subscriber:
Examples:

Sweden publishing per-minute data
Germany published large number of stations (high spatial density)

It made me wonder if we intend to set any limits on observation-data published in the .../data/core/... topic to avoid a single WIS2-node flooding unsuspecting subscribers with data ?
Or should we have separate topic or message-attribute to limit subscriber to GBON data ?

Related to https://github.com/wmo-im/wis2-guide/issues/14

I wonder if there's merit in publishing data like this through multiple "datasets"?
For example. Dataset A strictly adheres to Core data (spatial/temporal resolution, parameters etc.). Dataset B is a superset of Dataset A that is more "dense". Both could be published through WIS2. The notification messages from the originating centres could even refer to the same data object when it's included in both A and B. (Note that Global Caches might end up keeping 2 or more copies because data objects from A and B would logically be different).
Maybe Dataset B is marked as Recommended Data? Maybe not.

I think the topic hierarchy is fine. We shouldn't add any filtering at the MQTT level. Filtering can be implemented at the download level. If the message includes the geometry, it could be a way to filter before download.
I'd therefore suggest to close this issue.


[FEATURE] Export RETURN_VALUE_ERROR_CODES

Please add RETURN_VALUE_ERROR_CODES to the package exports.
I would like to make a switch statement around error codes to handle errors nicely, but it isn't possible because my app code cannot access RETURN_VALUE_ERROR_CODES:

Hey @skibitsky !
The idea I had in mind when designing this part of the package is that you would be using string literals to match the types. TypeScript will allow you to narrow the cases and have and clean switch statement like:
const ethersError = getParsedEthersError(error);

switch(ethersError.errorCode) {
      case "EXECUTION_REVERTED": { ... }
      case "INSUFFICIENT_FUNDS_FOR_GAS": { ... }
      .....
      default: { ... }
}

I recognize this may lead to typos or issues for people not using TypeScript though, so I'm fine exporting the object for convenience 👍🏻

@skibitsky available on version 0.2.2 🚀


Robust and consistent auth header

This PR provides an invaluable improvement on Focus' architecture and will be an important part of an re-engineering to support multiple endpoints and stores within the same Bridgehead.
However, as it introduces a breaking change for sites that do not run focus inside a Bridgehead, such as EUCAIM providers, we need to coordinate with them regarding the time frame of the merge.
In the meantime I have made the change necessary to avoid confusing Exporter API key with authorization header here: https://github.com/samply/focus/pull/191

I will convert this PR to a draft until the Focus' re-engineering is better specified


auth.service.ts doesn't refresh authMethods after AUTHENTICATED_ERROR

Describe the bug
We've observed for a while that after the backend is restarted while a user is logged-in, reloading the logged-in browser tab results in an "empty" login menu, like this:

We've seen this problem with our DSpace-CRIS installation as well as a recent main branch of dspace-angular, and with Firefox 91.11.0esr as well as Chromium 103.0.5060.53.
To Reproduce
Steps to reproduce the behavior:

Start frontend and backend
Open a browser
Log into the frontend in the browser window
Restart the backend
Reload the browser tab
Open login menu

Expected behavior
The authentication methods are expected to appear.
Analysis
I've finally found the time to investigate and it appears that while AUTHENTICATED_ERROR fires correctly, all that's done in response is to remove the token from storage (which is why things will work again if you reload the tab twice); there's no working code path that results in a RetrieveAuthMethodsAction or a forced page reload.
I say "no working code path" because this code in trackTokenExpiration comes quite close to handling this (and may provide the appropriate UI response to a non-expired token that unexpectedly fails to work):
  public trackTokenExpiration(): void {
    let token: AuthTokenInfo;
    let currentlyRefreshingToken = false;
    this.store.pipe(select(getAuthenticationToken)).subscribe((authTokenInfo: AuthTokenInfo) => {
      // If new token is undefined an it wasn't previously => Refresh failed
      if (currentlyRefreshingToken && token !== undefined && authTokenInfo === undefined) {
        // Token refresh failed => Error notification => 10 second wait => Page reloads & user logged out
        this.notificationService.error(this.translateService.get('auth.messages.token-refresh-failed'));
        setTimeout(() => this.navigateToRedirectUrl(this.hardRedirectService.getCurrentRoute()), 10000);
        currentlyRefreshingToken = false;
      }

Unfortunately, the code above is never called in our case, because the authentication token never assumes a value other than undefined. As an experiment, I've modified the AUTHENTICATED_ERROR handler to use null rather than undefined:
    case AuthActionTypes.AUTHENTICATED_ERROR:
    case AuthActionTypes.RETRIEVE_AUTHENTICATED_EPERSON_ERROR:
      return Object.assign({}, state, {
        authenticated: false,
        authToken: null,
        error: (action as AuthenticationErrorAction).payload.message,
        loaded: true,
        blocking: false,
        loading: false
      });

and adjusted the code in trackTokenExpiration accordingly. That appears to work.
Proposed fixes
I think the easiest fix would be to trigger a CheckAuthenticationTokenCookieAction (which is very different from a CheckAuthenticationTokenAction) in response to an AUTHENTICATED_ERROR. However, as that action may itself result in an AUTHENTICATED_ERROR, we must do so only if we've actually deleted a token from storage, in order to avoid an infinite loop if the backend is actually throwing an error.
That would, however, result in a transparent log-out as observed by the user, which might not be desired.

@philipprumpf :  Based on your description above, it's unclear to me if you've found a fix you are satisfied with or not?  If you have a fix you'd propose, feel free to create a PR & I can find a tester/reviewer.  If you feel this is better assigned to someone else for additional analysis, I can find someone on our DSpace 7 team to try to help out here...just let me know.

I got stuck trying to figure out how to write a test for this, to be honest. For now, I've submitted a PR without the test.

Closing, as this is no longer reproducible in pre-7.4. It appears it was fixed via a separate bug fix.


Remove the ambiguous 'Connection error'

I'd like to get rid of this error completely, 'Unfortunately, there was a connection error'
https://github.com/CartoDB/cartodb/blob/master/lib/assets/locale/en.json#L128
If we can't get rid of it completely for more informative versions, I'd propose we change it to something that actually lets the user know how to respond. Like,
“There was a temporary connection error, please try again."
cc @csobier @ztephm

Hey, we don't have that error anymore, so perfect for closing!


Deprecate swift chart

https://github.com/kubernetes/charts/pull/4957
Signed-off-by: tamal<EMAIL_ADDRESS>

cc: @prydonius


fix: remove popped scrims from pending scrims view

Task linked: CU-2fekp0e Popped Scrims to not get removed from pending scrim store


feat: makes KeySetBuilder::Build() more efficient with rvalue qualifier

Rvalue-ref qualifies the KeySetBuilder<T>::Build() method which will enable it to move all of its data into the protos in the resulting KeySet. I needed to add rvalue-qualified accessors to Bound and KeyRange as well.
I left the KeySetBuilder<T>::Build() const& overload, which is inefficient and will result in a copy of all the keys. We could remove this overload if we want to.

This change is

google/cloud/spanner/keys.h, line 159 at r1 (raw file):
Previously, devjgm (Greg Miller) wrote…
Added some tests, but they're not great. testing moves is hard. Let me know if you have a better idea.

Did you actually git push them?


Compute food frame should get center of mass of mask

Description
Earlier, the compute food frame function used the middle of the food bounding box to determine the food frame. However, if the mask is convex, that may not be accurate. Thus, this PR changes it to use the center of mass of the food mask as the food frame.
Testing procedure
Tested it as part of the Industry Affiliates Research Day Demo and it worked (better than the earlier approach).

[x] Run your code through pylint and address all warnings/errors. The only warnings that are acceptable to not address is TODOs that should be addressed in a future PR. From the top-level ada_feeding directory, run: pylint --recursive=y --rcfile=.pylintrc ..

Before Merging

[ ] Squash & Merge

@amalnanavati this is fine but I think the warn log adds voter, I'll remove it on my next pr

Good point, I missed that. This PR was the result of fast-code changes to get the demo to work, so I didn't have time to be as thorough as ideal.


Getting error CS8802: Only one compilation unit can have top-level statements.

Problem encountered on https://dotnet.microsoft.com/en-us/learn/dotnet/hello-world-tutorial/run
Operating System: macos
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
I installed .NET today for the first time ever and ran the following steps as instructed in the Hello World tutorial:
bash-3.2$ dotnet new console -o MyApp -f net6.0

bash-3.2$ cd MyApp
bash-3.2$ dotnet new console -o MyApp

bash-3.2$ dotnet run

Can you help please ?
I am on a Mac (Catalina 10.15.7)
If I do:
bash-3.2$ dotnet --version
6.0.302

Hi @ashDog! I usually see this error when the dotnet new command has been ran twice on different folders in the same hierarchy. In your screenshot above, it seems you did cd MyApp and then ran the command again, creating a second project inside that folder. You could just delete the top MyApp folder and start over.
Let us know if this helps.

@mairaw thank you very much.


Allow UI layout updates without a window

Objective
Allow UI layout updates without a window present.
Solution
Make LayoutContext into a component that is used to mark an entity as a UI root entity with an associated Taffy root node and
add a LayoutContext component to the primary window entity in UiPlugin::build.
ui_layout_system now picks the first entity containing a LayoutContext component and introduces a corresponding taffy node to the Taffy layout tree (given that it isn't present already). This node is then set as the root of the entire tree. Then the UI layout update proceeds as normal.

Changelog
changes:

LayoutContext derives Component.  It has a new field layout_to_logical_factor, scale_factor is renamed to combined_scale_factor, physical_size is renamed to root_node_size and the min_size and max_size are removed.
UiPlugin::build adds a LayoutContext component to the primary window entity.
For the first LayoutContext entity, an associated Taffy node is added to the Taffy layout tree, which is then set as the root of the entire tree.
Added a simple test that adds and then removes a UI node.

Migration Guide

Make ui_layout_system easier to test by moving the window logic into a separate system.

I disagree with that approach. Testing calls for a modular block of code, which means a function. Adding a separate system is a more heavyweight process that adds to the pile of things the scheduler has to do, and should only be done for runtime reasons. Can we move the logic into a function called from the same system it's currently in? That should solve the testability issue without requiring an additional system.

Make ui_layout_system easier to test by moving the window logic into a separate system.

I disagree with that approach. Testing calls for a modular block of code, which means a function. Adding a separate system is a more heavyweight process that adds to the pile of things the scheduler has to do, and should only be done for runtime reasons. Can we move the logic into a function called from the same system it's currently in? That should solve the testability issue without requiring an additional system.

Ah, that's a good point. There is no need for a new system just for this change. The situation is a bit muddled and confused because it's not clear yet how multi ui root nodes and multi-window ui support will be implemented. I'll refactor this a bit.

To be fair I'm on a phone so didn't look in details at the PR sorry. Just wanted to raise a general point. If that's too complicated for this case I'm fine using a separate system. It was just a suggestion in general, from experience I at least tend to put everything in a system function, and I think Bevy does that too, and that as you noted makes testing a lot harder. Separate non-system functions are nicer for testing but a pain to pass arguments to unfortunately.

It was really helpful, I was making things over complicated. The implementation is much better now and realised I could easily hack together multiple window UI on top of this as well:
https://github.com/bevyengine/bevy/assets/27962798/52c120f1-7de6-4bcb-ae1d-9308b2354498

Can you add a simple migration guide for the renames?

Can you add a simple migration guide for the renames?

done
I didn't make one before because LayoutContext was added after the Bevy 10 release, do we need them for changes to features new to the next version?

I didn't make one before because LayoutContext was added after the Bevy 10 release, do we need them for changes to features new to the next version?

Ah I'd missed that. These are nice to include in the PR description still in case folks are working off main or the PR gets delayed. Ideally we'll exclude it from the migration guide notes but a false positive like that does no harm.


Very slow git in VSCode when vscode-solidity is running

When using a repo containing .sol files with this extension, any git operations completed in VS Code are very slow, to the point of being unusable.
The problem stops after uninstalling the extension. A reinstall fixes the problem until VS Code is closed and re-opened.
With the extension installed, there are no problems in repos with no .sol files.
This has been a problem for approx. 2 months.
I am running WSL Ubuntu 18.04.

Yes it seems to be an issue with WSL and the extension, are you just using the vscode extension or are you using other plugins like the Azure.

Seems like the same issue as me

Just using the VSCode extension. Plain VSCode with vscode-solidity on WSL.

Can you check the latest version (not released) https://github.com/juanfranblanco/vscode-solidity/blob/master/solidity-0.0.73.vsix. This mainly disables the check when changing settings to cache the current compiler, i think wsl it is forcing to reload the settings in each new window instance.

I am closing this now, please reopen if needed

I am closing this now, please reopen if needed


Add support for more regions

We documented us-east-1 as the only supported region in v1.0.0 because we did not have an AMC instance in any other region with which to QA our solution against. This issue will be used to track our support for other regions.

Related to https://github.com/aws-solutions/amazon-marketing-cloud-uploader-from-aws/issues/12


jdk

Features that impact the whole project (e.g. Adding a new OpenJDK distribution)are made over at the adoptium.
Otherwise, please describe what enhancement you would like to see in the build
scripts:

Issue doesn't have any content


Plotting in C++

This resolves #87.

This should be ready! 2D density plotting has been particularly difficult, as the library's contour() algorithm is extremely slow, so I had to find another way.

I've made several modifications, most notably:
1- the contour plot actually works and is really fast
2- moved plot functions to a separate file
3- changed a couple of names here and there

By the way, I had to move the contour plot so that it's the last one, otherwise all the remaining plots would turn out blank... Go figure!

Alright, this is fine for me! Please merge at will, or wait for @TeoGiane's review first, as you'd like


https://esp-rs.github.io/std-training/02_2_software.html

Please add to 02_2_software.html these three packages.
Without them installing espflash doesn't work with WSL:
sudo apt install pkg-config libudev-dev make
Although it is mentioned in the "Troubleshooting area" (apt-get update \ && apt-get install -y vim nano git curl gcc ninja-build cmake libudev-dev python3 python3-pip libusb-1.0-0 libssl-dev \ pkg-config libtinfo5) it is still better to mention it a line before "cargo install cargo-espflash espflash ldproxy"

Hi thanks for opening the issue! Just created https://github.com/esp-rs/std-training/pull/211 and https://github.com/esp-rs/book/pull/124 to improve this.


Fix Slither command

Issue
I tried running Slither on a specific contract, as currently suggested in the Foundry Book:
slither src/MyContract.sol

However, this failed with the following error:

crytic_compile.platform.exceptions.InvalidCompilation: Solidity version not found:

I double-checked that the Solidity compiler was installed correctly solc-select, as indicated in the book.
Solution
The only thing made Slither work was to run slither . instead. This is also what's recommended in their README.
The following gets logged as soon as I run slither ., suggesting that Slither is aware that my project is a Foundry project and it compiles the code with Forge:
'forge build --extra-output abi --extra-output userdoc --extra-output devdoc --extra-output evm.methodIdentifiers --force' running

Environment

slither 0.9.1
pip 22.3.1
forge 0.2.0 (f959af5 2023-01-06T12:01:47.706731Z)

By the way - sorry for the deluge of PRs these days.


Question: Does uv support multiple environements?

Hi there,
Just wondering, does uv support multiple environments (I see I can specify "application dependencies" and "dev dependencies", but could I e.g. create an env for "cpu" and another for "gpu")?
Many thanks for any help, and for this lib!

No we don't have multiple environment support right now — the closest is probably to use different groups of optional-dependencies.

Thanks for your help and info @zanieb

Sorry for re-opening this, but is this still the case? If I want two environments in the same folder, I get this error:
warning: `VIRTUAL_ENV=.venv-analysis` does not match the project environment path `.venv` and will be ignored

which doesn't make a lot of sense to me.

Hi @zanieb ,
hatch provides quite a convenient way to actually separate envrionments, not just groups.
This might be useful in scenarios when packages are incompatible and you need to use a couple of envs, or when you want cross-python testing. Would you consider this feature in future?


Pydantic model?

Hi @dherincx92—I have been wondering whether it might be worth creating Pydantic models for FPDS data. The use case I'm envisioning is to allow for easier export from FPDS into a database that matches the USASpending database.
See the USASpending model here: https://github.com/fedspendingtransparency/usaspending-api/blob/master/usaspending_api/transactions/models/source_procurement_transaction.py
I'm not sure if it's worth it or not, but thought I'd float it and see if you had any reactions. I'd be happy to take a swing at doing some of the modeling / creating a PR if you think it's useful. Thanks!

I do like this idea, but one potential pitfall I see is that this would require consistent maintenance of the model itself; at work I've encountered a similar issue and we've overcome this by either:
A) Ingesting each record in its raw JSON format and then modifying SQL models downstream with dbt or any regular ol' SQL script
B) Using a data catalog tool like AWS Glue to handle automatic schema detection and alter/create new columns based on data ingestion.


Do not use the manager client in tests

We are using the manager client in tests which is the same client used by controllers. It reads from caches which means it is not strongly consistent. In tests we usually want strong consistency where the client will read directly from the api server.
burmanm pointed out https://github.com/kubernetes-sigs/kubebuilder/pull/2066 to me which discusses this.
┆Issue is synchronized with this Jira Task by Unito
┆Reviewer: Michael Burman
┆friendlyId: K8SSAND-144
┆priority: Medium

Closing as this is no longer relevant


Optionally embed path to bsc compiler at build time

This is useful for e.g. Nix builds, where we want to fix the version used at build time. (Also helps avoid the flaw mentioned in the FIXME in get_bluespecdir, coincidentally.)

bors r+

bors r+

bors r+

bors r+


fix: clear highlight groups in the new beautiful default Neovim theme

On nightly v0.10.0-dev-1770+gf64e4b43e-dirty

Maybe something like:
:hi Normal guibg=none

or
-- kitty_scrollback_nvim.py
        nvim_args = parse_nvim_args(args) + (
            '--cmd',
            ' lua vim.cmd.colorscheme([[vim]]) '
            ' lua vim.api.nvim_create_autocmd([[VimEnter]], { '

See https://github.com/neovim/neovim/pull/26334

:tada: This issue has been resolved in version 2.4.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Dispatch CLI should consume the new .bot file using configuration builder library

Filing this issue to track work to update the dispatch CLI to use the new .bot file format as well as consider using the bot configuration library.
Specific issues -

dispatch should consume and output LUIS region information (added to .bot file)
dispatch create, refresh commands should be able to take a --secret with the -b option if the bot file is encrypted. At the moment dispatch expects the bot file to be unencrypted. Using the bot configuration library will help with this issue. At minimum, dispatch should prompt for the secret if the bot file is encrypted.

Merged to master.


Implementation in Emacs

First of all, nice tool!
I've integrated this tool to Emacs with flycheck and flymake.

https://github.com/flycheck/flycheck-ziglint
https://github.com/flymake/flymake-ziglint

I wonder can we pass filename to ziglint? For example:
$ ziglint /path/to/project/src/main.zig

Thanks!

thank you for the kind words :) yeah that's totally doable

just double checked and realized the -file flag already exists 😄

no that's right, I'll double check it soon. I believe its currently blocked on https://github.com/nektro/ziglint/issues/24 which ill be fixing during the upgrade to zig's imminent 0.12 release


enhance: Add partition-loaded and make force-release selectable

See also #255
This PR:

Add show partition-loaded command to list partitions loaded
Make force-release able to specify collection id
Rewrite force-release command with new framework
Some minor format/parameter usage fix

/lgtm


How to upgrade to Vagrant 1.9.1 from any older version on Ubuntu 16.04

Note: First remove the older version of vagrant.

sudo apt-get remove --auto-remove vagrant
rm -r ~/.vagrant.d

Install instructions
1. wget https://releases.hashicorp.com/vagrant/1.9.1/vagrant_1.9.1_x86_64.deb
2. sudo dpkg -i vagrant_1.9.1_x86_64.deb
3. vagrant version

Does this process remove the files or VMs of old version?

These are the steps to remove existing vagrant installation:

sudo apt-get remove --auto-remove vagrant
rm -r ~/.vagrant.d

NOTE: Above steps does not remove machines available under workingdir/.vagrant/ folder

These are the steps to install vagrant 2.0.2:

wget https://releases.hashicorp.com/vagrant/2.0.2/vagrant_2.0.2_x86_64.deb
sudo dpkg -i vagrant_2.0.2_x86_64.deb
vagrant version

These are the steps to remove existing vagrant installation:

sudo apt-get remove --auto-remove vagrant
rm -r ~/.vagrant.d

These are the steps to install vagrant X.X.X:
1.Download your version here : https://releases.hashicorp.com/vagrant/
or wget https://releases.hashicorp.com/vagrant/X.X.X/vagrant_X.X.X_x86_64.deb
2. sudo dpkg -i vagrant_X.X.X_x86_64.deb
3. vagrant version
Ref Link : https://releases.hashicorp.com/vagrant/


3.8.1 release is missing Linux binaries

Only Windows and Mac OS X has been published. meteor publish-for-arch for Linux should be run as well.
  "architecturesOS": [
    "os.windows.x86_32",
    "os.osx.x86_64"
  ]

how does meteor publish-for-arch work? I read in Meteor 1.4.1 update that it's not mandatory anymore? Not sure.

It does not work for me without.
It works the same as it worked before. Maintainer of the package will know.

This issue is duplicate of #201.


[WIP] Allow transport to influence application scheduler selection

This  started as an effort to avoid extra threadpool dispatching in the socket transport's default configuration. You can already choose to disable threadpool dispatching via KestrelServerOptions, but this PR intended to provide a mechanism for the transport itself to disable threadpool dispatching.
The idea was that the socket transport would default to running app code inline even if the app developer didn't opt in because it's safe and it's faster than dispatching. Unfortunately this posed a few issues such as deciding which scheduler to use for the request body reader so the PumpAsync loop keeps going even if the application does a synchronous read.
@davidfowl and I discussed the possibility of using the inline scheduler for sockets only if the request has no body because that case wouldn't be susceptible to deadlocking due to a synchronous read, but that raised other issues.
We decided if we're going to selectively switch schedulers mid-connection maybe we should always run the parser inline even for the libuv transport. But the logic for the libuv transport can't be exactly like the socket transport, because we don't want to run app code inline even if the request doesn't have a body in the case of the libuv transport.
Then we started discussing how a transport could communicate these kind of subtle scheduling preferences in a way that doesn't make these scheduling preferences something that's specific to the HTTP protocol and not applicable to other connection middleware.
After all this discussion I put this PR on the back burner since we don't have a great design that addresses all of the above concerns. Here's what I have so far. It doesn't do any inline "scheduling" by default yet due to the aforementioned issues. Thoughts?
@benaadams

Associated thoughts...
The QueueUserWorkItem(..., preferLocal: true) from https://github.com/aspnet/KestrelHttpServer/pull/2298 means if the thread queuing to the threadpool is already a threadpool thread; it queues to its local queue, so its likely the same thread that will pick it up the work if it finishes quickly after queuing (wouldn't effect libuv, but should effect sockets)
Other thing you could also try is if Thread.IsThreadPoolThread then run inline; otherwise queue to threadpool?

Testing Thread.IsThreadPoolThread is probably better of the two as then you wouldn't need to allocate a closure for the action or for logging

Something like https://github.com/aspnet/KestrelHttpServer/pull/2319?

Moving to the PipeSchedulers rather than Kestrel local ones should pick up the , preferLocal: true?
So its worth testing if this already improves sockets; even without going inline?

Ok after looking at this a bit I think we should take it and expose something on SocketOptions that lets us toggle the default behavior. That way we can run in the unsafe mode (where a synchronous Read can deadlock) for benchmarks or in cases where we own all of the code.

Moving to the PipeSchedulers rather than Kestrel local ones should pick up the , preferLocal: true?

So its worth testing if this already improves sockets; even without going inline?

Good call. That's true.

Thinking about it, if you wanted a true doevents/setimmidate/settimeout(0) type thing

Queue an action to the threadpool (, preferLocal: true) that had a sidecar awaitable
Immediately await the awaitable
When it finished have it run the awaitable completion inline

For bonus points you could reuse the awaitable+action for the next request/action

Nah; bad idea, use (, preferLocal: true) then it will keep running the PumpAsync and if then that awaits the thread will get the item its just queued and run it (almost inline).
If it doesn't await then another thread will run it.

Closing this PR in favor of #2348


Special Python Types for Milliseconds and Seconds Unix Time

Special Types for Milliseconds and Seconds:
Create two types, call them UnixTimeMilliseconds and UnixTimeSeconds.
These types would explicitly define whether the time value is in milliseconds or seconds.
Update the codebase
Integrate the new types into the codebase.

Thanks for adding this issue!
"UnixTimeMilliseconds" and "UnixTimeSeconds" is a lot of characters. It will make argument lines quite long, and in turn because of black force multiple lines etc.
I recommend instead: "UnixTimeMs" and "UnixTimeS". Shorter, and just as clear.


Added new DPS report start & end time filters

@thoenissen is the server's timezone correctly configured for LogCommandHandler.cs:626 to work?

The server uses CEST in the production environment.


Updates to 21.1 session variables

This PR adds the following session variables:

locality (added to 21.1, 20.2, and 20.1; not sure why this was left out in previous releases)
default_transaction_use_follower_reads (related to https://github.com/cockroachdb/docs/issues/9584; will introduce follow-up PR)
enable_drop_enum_value (related to https://github.com/cockroachdb/docs/issues/10137)

and removes the following session variable:

enable_experimental_alter_column_type_general (related to https://github.com/cockroachdb/docs/issues/9163; will introduce follow-up PR)

Note the following session variables, which exist in v21.1.0-beta.2, but remain undocumented:

disable_partially_distributed_plans (for internal testing - no docs need; https://github.com/cockroachdb/cockroach/pull/50903)
override_multi_region_zone_config (not sure if we need docs for this @rmloveland; https://github.com/cockroachdb/cockroach/pull/62119, https://github.com/cockroachdb/docs/issues/10131)
testing_vectorize_inject_panics (for internal testing - no docs need; https://github.com/cockroachdb/cockroach/pull/55516)
enable_experimental_stream_replication (not sure if we need docs for this @jseldess ; https://github.com/cockroachdb/docs/issues/10110; https://github.com/cockroachdb/cockroach/pull/60826)
experimental_distsql_planning (we never documented this for 20.2, but I'm not sure if we need docs @yuzefovich)
experimental_enable_implicit_column_partitioning (not sure if we need docs for this @rmloveland; https://github.com/cockroachdb/cockroach/pull/58521, https://github.com/cockroachdb/cockroach/pull/60465)
experimental_enable_unique_without_index_constraints (this needs docs @ianjevans; https://github.com/cockroachdb/cockroach/pull/57666)
experimental_use_new_schema_changer (I don't think this needs docs; https://github.com/cockroachdb/cockroach/commit/c0bb7c0fff35fe9b16efd83def55c5df8dadafb2#diff-cac22f70970154948cf8958f45e3fb5946f5dfb71a96aac384e99ccf310119b1)

Just mentioning people in this description for visibility. No response required. :)

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/8499df55525614168bf202d7c63a720302ab52ce/
Edited pages:

v20.2/experimental-features.md
v21.1/experimental-features.md

Eric Harmeling @.***> writes:

override_multi_region_zone_config (not sure if we need docs for this
@rmloveland; cockroachdb/cockroach#62119, #10131)

This will def get docs.  Some discussion already in
https://github.com/cockroachdb/docs/issues/10131 since it appears in the
beta.2 release (and thus has a release note and will get doc'd etc.)

experimental_enable_implicit_column_partitioning (not sure if we
need docs for this @rmloveland; cockroachdb/cockroach#58521,
cockroachdb/cockroach#60465)

Looks like it has no release note so I'll trust the PR committer on
that. :-}
(Esp. since it is "experimental" and thus (IMO) best avoided by the
masses ;-} )

Just mentioning people in this description for visibility. No response
required. :)

If you mention Beetlejuice 3 times (er, 2 in this case) he will appear
:-D

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/5d39a2ce31dd64c3c13ff87ee719dfba18ad3ea4/

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/94de3a9eb2d52f9893b1804b07c94162229b4e50/


Need help

Hey, I have started your resource in my server.cfg, created a usable item for the pet_shepherd, and added an image to my inventory, but when I go to actually use the item nothing happens. It shows, "used" on my screen but nothing else happens. Is there something I am missing?

There are also no error logs, and the name put in my shared lua is exactly the same as the name in the server lua in the lion-companions folder.


remove qm externals access

people are using this as argument to give cmo externals access

Doesn't the QM have external access because they oversee salv? It seems pretty reasonable for them to have it when they are supposed to supervise people who do their jobs entirely in space. The cmo does not supervise people who spent most of their time in space.

the cargo bay doors dont use externals access i dont see the need for them to have it

Ok then.

dont cargo techs also have externals access?

Actually, CMO is the only head without externals. It would be funny when a cargo tech can open externals but their own boss can't.

RD does not have externals

Wait really? That's news to me. So that's 2 heads, but RD and CMO don't work near space at all, whereas QM works directly with space. Again it would be pretty hilarious for a QM to get shoved out of a shuttle or the airlock and not being able to simply enter the station through the airlocks he works right next to, especially when Cargo Techs would be able to. So I'm 50/50 on this, only because it would be funny.

the cargo bay external airlocks arent externals locked

Remove it from Techs too, give Salvage even more power over cargo.

ok

How does QM help salv now if they cant open external doors?

none of the doors in cargobay are external

yea idc about the cmo thread, this is dumb because cargo is in very close proximity to space and QM should interact with salv more than less, to counter an argument by removing an okay feature is dumb

none of the doors in cargo bay are external, this changes literally nothing for qm

How will they open the shuttle airlocks? They have external access.

the doors automatically open when it docks

i will change them to cargo lock though


The link 'how will Soft Delete affect overwrite?' is selected on the 'Conflict' dialog of blobs

Storage Explorer Version: 1.20.0-dev
Build Number: 20210524.7
Branch: main
Platform/OS: Windows 10/ Linux Ubuntu 18.04
Architecture: ia32/x64
How Found: Exploratory testing
Regression From: Previous release (1.19.1)
Steps to Reproduce

Expand one storage account -> Blob Containers.
Create a blob container -> Upload one file -> Upload the file again.
Observe the 'Conflict' dialog.
Check whether the link 'how will Soft Delete affect overwrite?' is selected.

Expected Experience
The link 'how will Soft Delete affect overwrite?' is not selected.

Actual Experience
The  link 'how will Soft Delete affect overwrite?' is selected.

Additional Context

This issue doesn't reproduce when dragging & dropping/copying & pasting one same blob.
This issue doesn't reproduce on MacOS Big Sur 11.3.
On Linux, this issue still reproduces when dragging & dropping/copying & pasting one same blob.

I did some investigation on this issue. It seems to be related to some browser internal logic for giving focus to the first focusable element in the browser window on certain conditions. The cause may be a combination of timing and us hiding and reusing the dialog window. I experimented with either one of

Quick drag/drop two files on Windows. (Still reproduces)
Always destroy the old dialog window instead of reusing. (No reproduce)
Don't hide the dialog but just reload its contents. (No reproduce)

Won't fix for now since this is of low impact.


Emulate three pox controller in the mininet?

Is it possbile to run and emulate three pox controllers in single large network, using mininet?
Thanks in advance

I assume this issue is too old to be useful.  My answer is that I haven't used Mininet for many years and have no idea what it's capable of. :)


PSMDB-589-Updted list of differences from upstream. Deleted mentionin…

…g about ignored ldapUserCacheInvalidationInterval

thank you for this update


trouble with remake sources

For issue #246 and PR #281 , the scripts I list as remake sources don't seem to be getting sourced. I'll keep working on it but would also welcome help - can y'all reproduce and/or diagnose this issue, @jread-usgs and others?
Here's a simple remake.yml that I just created in my copy of USGS-VIZLAB/example:
packages:
  - vizlab
sources:
  - scripts/fetch/cars.R
targets:
  all:
    depends:
      - 'cache/cars.csv'
  'cache/cars.csv':
    command: fetch(I('cars-data'))

when I run remake::make() in a fresh R session (after deleting the .remake folder if it exists), I get this:
> remake::make()
[  LOAD ]
[  READ ]                |  # loading sources
<  MAKE > all
[ BUILD ] cache/cars.csv |  fetch("cars-data")
[  READ ]                |  # loading packages
Restoring previous version of cache/cars.csv
Error in UseMethod("fetch") :
  no applicable method for 'fetch' applied to an object of class "c('cars', 'fetcher', 'fetch', 'viz')"

but if I then source the script manually and try again, everything works much better:
> source('scripts/fetch/cars.R')
> remake::make()
<  MAKE > all
[ BUILD ] cache/cars.csv |  fetch("cars-data")
[ ----- ] all

This same pattern holds even if I copy scripts/fetch/cars.R into the top-level directory and change sources to simply cars.R, and even if I declare it in one line: sources: cars.R.
I'm up to date on remake:
> packageVersion('remake')
[1] ‘0.3.0’
> devtools::install_github('richfitz/remake')
Using GitHub PAT from envvar GITHUB_PAT
Skipping install of 'remake' from a github remote, the SHA1 (e29028b5) has not changed since last install.
  Use `force = TRUE` to force installation

Any ideas why this is happening or how to make my sources: get source()d?

Narrowed it down a bit - I think the problem is that remake is so selective about what it loads that it's not bothering to load fetch.cars when the command just says fetch().
In a new, nearly empty directory, I have these three files:
cars.R
fetch.cars <- function(viz) {
  viz <- as.viz(viz)
  id <- viz[['id']]
  location <- viz[['location']]
  write.csv(x=cars, file=location, row.names=FALSE)
}

fetchTimestamp.cars <- vizlab:::fetchTimestamp.file

viz.yaml
fetch:
  -
    id: cars-data
    location: cars.csv
    fetcher: cars
    mimetype: text/csv
    scripts: scripts/fetch/cars.R

remake.yml
packages:
  - vizlab
sources:
  - cars.R
targets:
  all:
    command: fetch(I('cars-data'))

In a fresh R session, this reproduces the error:
> remake::make()
[  LOAD ]
[  READ ]       |  # loading sources
<  MAKE > all
[ BUILD ] all   |  all <- fetch("cars-data")
[  READ ]       |  # loading packages
Error in UseMethod("fetch") :
  no applicable method for 'fetch' applied to an object of class "c('cars', 'fetcher', 'fetch', 'viz')"

but if I change the command in remake.yml to this:
    command: fetch.cars(I('cars-data'))

then the build works:
> remake::make()
[  LOAD ]
[  READ ]       |  # loading sources
<  MAKE > all
[ BUILD ] all   |  all <- fetch.cars("cars-data")
[  READ ]       |  # loading packages

Possible solutions:

Fix remake to get it to load S3 methods that will be called from a call to an S3 generic (e.g., load fetch.cars when fetch is called). This sounds awfully difficult.

In remake.yaml, call the S3 method rather than the S3 generic, e.g., command: fetch.cars("cars-data"). I think we could figure out which method to call, but there might be occasional surprises if a viz developer tries to nest a fetch()/process()/etc. call within another method, and there might be problems with custom readers, and (worst of all) every custom method would need to work from a character viz.id rather than letting as.viz() get called automatically from the built-in character method. This option is cleanest in the sense that it tries to stick with the remake system, but I think the drawbacks outweigh the theoretical benefits.

In vizmake(), source all scripts listed in the sources: section of remake.yaml before calling remake::make(). This is hacky and a bit inefficient but is my current favorite nonetheless.

@aappling-usgs which part of this would you like me to take on? researching further? Looks like you implemented option 3 in #294

I think it's done now, but I'd like your thoughts on the solution I picked - do you agree with my choice or see any others I missed?

Yes, I think it is the best solution we have available, and agree that the others either aren't worth the work (1), or are too fragile (2). I dug around in the remake internals a bit and wasn't able to get a sense of how to fix it in the package, but I think we should share the issue/bug w/ the maintainer.

OK, but see https://github.com/USGS-VIZLAB/vizlab/pull/294#discussion_r145158965 - the bug is a bit more subtle than I originally claimed, such that it's going to be hard to share persuasively with the maintainer.

oh, I see. Thanks. Can we close this issue?


added some description

@armando-fandango just a note: Estimators have been moved from core and will live in:
https://github.com/tensorflow/estimator


Add Insert-Deploy objects

[ ] Insert process.  Include comments to indicate how to set for an application process or component.
[ ] Insert process step.  Include comments to indicate how to set as an application process or component process step.
[ ] Insert component.  Include the retrieve step in a comment block.
[ ] Insert tasks: gate, deploy, plugin, procedure.  Or, at least comments explaining which attributes are needed for each.
[ ] Insert tier map

This issue was moved to electric-cloud-community/EC-DSLIDE#22


The cfg distillation for yoloxl_m

Sorry,I can not find the cfg distillation for yoloxl_m in the congfig of your FGD.

In branch yolox

hi, did  you distill  yolox   with the FGD code? What version of mmdet did you use


Add support for micronaut-data

Based on a short gitter discussion with @graemerocher this should be the place to add an ReactorCrudRepository for micronaut-data, but I have no idea how to integrate both modules.

it should be as simple as adding reactor-data module subproject and then just defining an interface that exposes Reactor types

Ok, I'll make a PR for that.
But how will it be used by micronaut-data?

This is implemented in https://github.com/micronaut-projects/micronaut-r2dbc


8K websocket demo

Hello Dear.
I think that wenet-e2e is pretty good tool for ASR.
I try to change some scripts for 8k websocket demo.
but it makes me confuse.
could you give some guide for 8K demo ?

@Mddct  Could you check this?
I try something...

change model call option --sample_rate 8000
chang "index.html" parameter
SoundRecognizer.init({
soundType: 'pcm',
sampleRate: 8000,
recwaveElm: '.recwave',
translerCallBack: TransferUpload
})
change "SoundRecognizer.js" option
sampleRate: 16000 -> 8000

but i can get worng results
such as "hello hello hello hello"
i say "hello" only one time..


Input validation parent form submitted state check

It is common setup when validating form fields to start showing invalid fields and validation errors only after form has been submitted for the first time.
I can see that sm-input is already searching parent tags to determine if component is inside a form, so it could check if parent forms 'submitted' boolean property when toggling error state, instead of controls dirty or touched state.
How about including this behavior (perhaps make it optional) ?

Yep, i agree with you.
I ll investigate what is best approach for this and try to implement it.


A new fork for Maintenance

Hello all, I've noticed a rising number of issues and pull requests, with some critical bug fixes still waiting to be approved.
I'd like to propose creating a new fork, under some informal organization, where we can more easily maintain this incredibly useful tool that we've been enjoying. We can merge some important pull requests and hopefully get all those changes back to this repository when the owner is active again.
To reiterate, this fork isn't intended to replace this repo, but to provide ease of maintenance during this time! Once the owner is active, we can streamline all those changes in a pull request from the new fork.
Comment below to show interest, ideas, feedback, or reasons why this isn't a good idea.
Peace and happy Hacktoberfest! :D

@transitive-bullshit  glad to see you're back! Hope you are doing well


Please continue working

Hey, The theme is very nice, but there are alignment problems and other issues. Please continue working on the theme. I'll try to help you if required.
Or as an alternative, we can fork Nylas Mail and customise it to make a fully functional Newton clone. I'd love to work with you on that as well.
Please let me know what you think
Thanks
Regards,
Aravind Reddy V.

Hi Aravind,
Thank you for you message and sorry for the very late reply.
I will start working on this theme again. Soon I will have updates.
Regards,
Matias


Different behavior of tf.extract_image_patches and tf.nn.conv2d for certain padding/stride/filter size combinations

Hi!
I am trying to implement something using tf.extract_image_patches and ran into some troubles that made clear tf.extract_image_patches handles some combinations of padding, filter size and stride differently than tf.nn.conv2d. Since tf.extract_image_patches is conceptually a "part" of a convolution operation, I think this might be unintended behavior.
Specifically, I implemented a "manual" version of a convolution operation using tf.extract_image_patches
def manual_conv(input, filter, strides, padding):
  h_f, w_f, c_in, c_out = filter.get_shape().as_list()
  input_patches = tf.extract_image_patches(input, ksizes=[1, h_f, w_f, 1 ], strides=strides, rates=[1, 1, 1, 1], padding=padding)
  filters_flat = tf.reshape(filter, shape=[h_f*w_f*c_in, c_out])
  return tf.einsum("ijkl,lm->ijkm", input_patches, filters_flat)

and tested it like this
import unittest
import tensorflow as tf

class TestManualConvToyData(unittest.TestCase):

  def runTest(self):
    m = 32
    c_in = 3
    c_out = 16

    image_sizes = [127, 64]
    filter_sizes = [1, 2, 3, 5, 11]
    strides = [1, 3, 4, 30]
    paddings = ["VALID", "SAME"]

    for fs in filter_sizes:
      for stri in strides:
        for imsize in image_sizes:
          for pad in paddings:
            h = w = imsize
            h_f = w_f = fs
            print "Testing for", imsize, fs, stri, pad

            tf.reset_default_graph()
            X = tf.constant(1.0+np.random.rand(m, h, w, c_in), tf.float32)
            W = tf.truncated_normal([h_f, w_f, c_in, c_out])

            Z = tf.nn.conv2d(X, W, strides=[1, stri, stri, 1], padding=pad)
            Z_manual = manual_conv(X, W, strides=[1, stri, stri, 1], padding=pad)

            sess = tf.Session()
            sess.run(tf.global_variables_initializer())
            Z_, Z_manual_ = sess.run([Z, Z_manual])
            self.assertEqual(Z_.shape, Z_manual_.shape)
            self.assertTrue(np.allclose(Z_, Z_manual_, rtol=1e-05))
            sess.close()

This test fails for some combinations of padding, filter size and stride. I think it has to do with the fact that tf.extract_image_patches tries to center patches if possible, as discussed in this stackoverflow question.

System information

Ubuntu 16.04.
Python 2.7.12
tensorflow version 1.2.1 installed via pip (CPU only)

It has been 14 days with no activity and this issue has an assignee.Please update the label and/or status accordingly.

Nagging Assignee: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @reedwm: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @reedwm: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Yangzihao, can you verify this is fixed? The reason for the failure might also be due precision issues instead of padding issues.

Nagging Assignee @yzhwang: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @yzhwang: It has been 44 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @yzhwang: It has been 59 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @yzhwang: It has been 74 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @reedwm: It has been 89 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @reedwm: It has been 104 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @reedwm: It has been 119 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @reedwm: It has been 134 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @reedwm: It has been 149 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Closing because I assume this is fixed by a change Yangzihao made. Please reopen if that is not the case.


Variables.Save allow forcing save of a default value

This issue was originally created at: 2012-03-23 00:47:59.
This issue was reported by: mortoray.

mortoray said at 2012-03-23 00:47:59

Looking at the code for Variables I see that variables are not saved if they match their default value. A way to force the saving of all variables, or selectively, would be quite beneficial.
The issue is that when the user first runs scons it will be with several variables. Some of the defaults may come from the environment (via os.environ). The next time they run scons these defaults may not actually be the same, but it is not intended to use this new value. The value which existed at the original configure time should be fixed and used forever.
I think it might be easiest to just save all the variables (boolean flag?). If the user's environment does change, they can always reconfigure.
I don't have an easy workaround at the moment.

One incremental improvement might be to do what has been attempted for options - try to distinguish "value is the default because nothing was specified for this variable" vs. "variable was specified with a value which is equal to the default", and have the latter case be stored by Save().


Glossary folder -> Reference folder + template terms

What I did

Created references templates of all other terms (pkam, cram, ...) d33cb00d14fe2deeabb35a9970cae7fa4557deb9
Moved all terms to be direct child of reference/ directory<PHONE_NUMBER>0fd3f20ecbda59f005e2a70f73ec6f

How to verify it

Added less buggy weights to each term 399283b135e12111fd8c42060078602f48e1ef42.
Also added more in-depth lead and descriptions to each term 65b13e216367cc60d0ac759ffcf0d97d6ac07ca6

Added namespace page de6c63a323a8ca041779a875d709b2d1b40a7447


bug: Exhaustion SVG not compatible with 7+ levels of exhaustion

When setting exhaustion to a level higher than 6, Tidy looks for an SVG that doesn't exist in the 5e system. This causes an error:

Update Tidy not to bother with the exhaustion numbering system on the conditions section of the Effects tab, if possible.

The managing of those numbered exhaustion SVGs is built into the system in a place out of scope for Tidy. Determine what the new default sheets are doing when > 6 exhaustion is used.

Dnd5e 2024 has six levels of exhaustion. Because of how all this is set up, I'm not going to try to fight against how this feature works.


Docs are not mobile friendly

Everyone seems to use this theme for a more modern mobile friendly look
https://pypi.org/project/sphinx-rtd-theme/

Looks like a simple addition - add the dependency to the [docs] section in pyproject.toml and ensure this is used in ci and in the read the docs config


Support for UTF-8 in Admin API URIs?

While testing my python-kong library (https://pypi.python.org/pypi/python-kong) for utf-8 support, I ran into strange behaviour when using utf-8 in the URI for the request.
Example:
First I create a consumer (Result: HTTP 201):
header: Date header: Content-Type header: Transfer-Encoding header: Connection header: Access-Control-Allow-Origin header: Server send: b'POST /consumers/ HTTP/1.1\r\nHost: localhost:8001\r\nUser-Agent: python-requests/2.7.0 CPython/3.4.3 Linux/3.16.0-41-generic\r\nAccept-Encoding: gzip, deflate\r\nConnection: close\r\nContent-Type: application/x-www-form-urlencoded\r\nContent-Length: 80\r\nAccept: */*\r\n\r\ncustom_id=e7b30d84-98cf-4a9d-9a75-5e217aff6ba4&username=tiarra%7B%C3%86%C3%9E%7D'
reply: 'HTTP/1.1 201 Created\r\n'
DEBUG:requests.packages.urllib3.connectionpool:"POST /consumers/ HTTP/1.1" 201 None

Then I try to delete that consumer, and I use the name as identifier in the URI  (Result: HTTP 404):
header: Date header: Content-Type header: Transfer-Encoding header: Connection header: Access-Control-Allow-Origin header: Server send: b'DELETE /consumers/tiarra%7B%C3%86%C3%9E%7D/ HTTP/1.1\r\nHost: localhost:8001\r\nUser-Agent: python-requests/2.7.0 CPython/3.4.3 Linux/3.16.0-41-generic\r\nAccept-Encoding: gzip, deflate\r\nContent-Length: 0\r\nAccept: */*\r\nConnection: close\r\n\r\n'
reply: 'HTTP/1.1 404 Not Found\r\n'
DEBUG:requests.packages.urllib3.connectionpool:"DELETE /consumers/tiarra%7B%C3%86%C3%9E%7D/ HTTP/1.1" 404 None

The DELETE URI looks like this (without encoding):
/consumers/tiarra{ÆÞ}/

I might add; when I use UTF-8 strings in the body of POST/PATCH/PUT methods, everything is fine; it only fails when the UTF-8 is used in a URI.

Sorry, won't fix.


<IP_ADDRESS>-Sort a stack -audio

Description
Description
Give an algorithm to sort a stack in audio format
Task

[ ] Documentation
[ ] Audio
[ ] Video

Note

While requesting the issue to be assigned, please mention your NAME & BATCH NUMBER.
Kindly refer to Issue Guidelines.
In case you see that the issue has already been assigned, try to request for a different task within the same issue.
Changes should be made inside the DSA/directory & DSA branch.
Name of the file should be same as the issue.
This issue is only for 'GWOC' contributors of 'DSA' Domain.

Domain
DSA
Type of Contribution
Audio
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

@Muskan-creator plz assign this to me

@jaigora24 Sure!

@Muskan-creator mam i open my PR. review it :)


wasm/testdata: Use in-tree ig to build the images

This ensures the most up to date is used for building and exporting the images

I don't understand this change. Why there are two different binaries on the system?
What I do on my system is to create a symlink from /usr/bin/ig to the compiled version of the binary to avoid having two different ones around:
$ ls -l $(which ig)
lrwxrwxrwx 1 root root 48 abr 10  2024 /usr/bin/ig -> /home/mauriciov/kinvolk/ebpf/inspektor-gadget/ig

Will this help on this case?

I don't understand this change. Why there are two different binaries on the system?

I never installed ig from upstream repo on my system. Never needed that use case.
Also in almost any other Makefiles we have a ENV variable for the ig path - so the use case seems to be there that there might be different binaries

What I do on my system is to create a symlink from /usr/bin/ig to the compiled version of the binary to avoid having two different ones around:
Will this help on this case?

I also have multiple folders for Inspektor Gadget. Mostly that is done when I work on parallel stuff. Of course I could always commit and then checkout another branch, but then I might forget about the other branch :sweat_smile:
But I don't want to force a change because of the way how I work

Also in almost any other Makefiles we have a ENV variable for the ig path - so the use case seems to be there that there might be different binaries

What about adding this also to this makefile so each developer can customize the binary to use?

Also in almost any other Makefiles we have a ENV variable for the ig path - so the use case seems to be there that there might be different binaries

What about adding this also to this makefile so each developer can customize the binary to use?

Just changed it to the env variable way.
But after looking at the changes again and seeing IG_SOURCE_PATH=$(realpath $(ROOT_DIR)/../../../..) I think in this situation it might actually be better for consistency to always refer to ig through $(realpath $(ROOT_DIR)/../../../../ig