[BUG] Overflow of content in small devices

Description
I have attached a screenshot, and the box is overflowing horizontally due to a lack of responsiveness.
What I can do is check the responsiveness of each category on very small devices.
Screenshots

Any additional information?
I will make sure to review the code for the necessary conventions and code style to ensure I follow the same.
Additionally, if you require me to adjust the font size very specifically, please let me know in advance.
What browser are you seeing the problem on?
Chrome
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

I noticed this too @Anmol-Baranwal. Good observation! :)  Just to confirm, are you participating in GSSOC'23?

I noticed this too @Anmol-Baranwal. Good observation! :)  Just to confirm, are you participating in GSSOC'23?

Yep, I am participating in GSSoC'23.

I noticed this too @Anmol-Baranwal. Good observation! :)  Just to confirm, are you participating in GSSOC'23?

Yep, I am participating in GSSoC'23.
Hi, @CBID2
I cannot find a specific file to change only this one page. If I make any changes, it will affect every page. It would be helpful if you could provide an overview of which component, file, or layout I should modify to address this issue.

I highly recommend asking @rupali-codes for this.

@Anmol-Baranwal its src/components/Cards/CardsList.tsx


Improved error handling for undefined and missing function arguments in VSCode

Description:
I would like the editor to clearly indicate when an undefined argument or a missing argument has been provided to a function in my code. This would make it easier for me to identify and fix errors in my code without having to run the program.
Specifically, I would like to see the following improvements in VSCode:

When an undefined argument is provided to a function, VSCode should display an error message indicating the name of the undefined argument and the function in which it was passed.

When a missing argument is detected, VSCode should display an error message indicating the name of the missing argument and the function in which it should have been passed.

VSCode should provide suggestions for the missing or undefined arguments in the function
This would greatly improve the debugging process and make it easier for me to write accurate and error-free code.
I was a user of Pycharm but recently switch to vscode and this feature is essential for me.
You can find in the screenshot below that there is no error showing :

This functionality is available if you enable static type checking. You can do this by setting python.analysis.typeCheckingMode to "basic".
Here's what it looks like when you enable this functionality:

@erictraut, thank you for your help. It works as expected by setting to "basic" !
Shouldn't this be set by default in the next release ?


Replace Bootstrap modal with own

We need graphic for modal dialog (yes, no) with title and html text as body
There will be standard js alerts instead in meantime

Removing old Bootstrap version and scripts related to Bootstrap and replacing it for js alert in meantime.


Clicking Refresh appears to logout

Using the refresh button looks like the system executes logout

Rewrote the authentication method

When using the browser refresh the login menu item is displayed

Fixed - AccountUtility.Authenticate was calling GenerateRefreshToken using the CurrentProfile.Id but should have been using mRetVal.Id


ResolvedArtifact returns incorrect extension for certain artifacts

Expected Behavior

Certain POMs on Maven Central (specifically, javax.ws.rs:javax.ws.rs-api:2.1.1) contain some unusual usages of variable substitution, where the <packaging> field is set to a property that is only defined when a specific profile is activated.
I would expect the following code:
dependencies {
    implementation 'javax.ws.rs:javax.ws.rs-api:2.1.1'
}
task foo {
    doLast {
        configurations.runtimeClasspath.resolvedConfiguration.resolvedArtifacts.each {
            println it.extension
        }
    }
}

to output
jar

(since the ResolvedArtifact for this dependency indeed is a jar).
Current Behavior

For the code snippet above, on Gradle 7.5+, the output is:
${packaging.type}

instead.
For Gradle 7.4.2, the output is:
jar

as expected.
Context
This particular POM is a little bit weird, and there is some past history with it (see https://github.com/gradle/gradle/issues/3065).
In our case, we have several internal repositories that use this pattern (for better or worse):
configurations.foo.resolvedConfiguration.resolvedArtifacts.collect {<EMAIL_ADDRESS>}

and iterate over the resulting strings assuming they are Maven coordinates that are sent to another process to resolve dependencies from. In those cases, we expect the getExtension() method to return some "standard" extension that Maven likely understands, but instead the resolution fails since it is being told to look for a dependency with an extension of ${packaging.type}.
This pattern works as expected in Gradle 7.4.2, but the output changed in Gradle 7.5. It's possible this is not really a regression, and is actually a case of "we fixed a bug," but it's hard for me to tell without knowing more about the internals of Gradle.

Steps to Reproduce
The following integration test will reproduce the issue:
package org.gradle.api

import org.gradle.integtests.fixtures.AbstractIntegrationSpec
import static org.gradle.integtests.fixtures.RepoScriptBlockUtil.mavenCentralRepositoryDefinition

class ResolvedArtifactGetExtensionIntegrationTest extends AbstractIntegrationSpec {
    def "javax.ws.rs-api:2.1.1 produces correct extension on ResolvedArtifact"() {
        given:
        buildFile << """
            apply plugin: "java-library"

            ${mavenCentralRepository()}

            dependencies {
                implementation "javax.ws.rs:javax.ws.rs-api:2.1.1"
            }

            task wut {
                doLast {
                    configurations.runtimeClasspath.resolvedConfiguration.resolvedArtifacts.each {
                        println<EMAIL_ADDRESS>                    }
                }
            }
        """.stripIndent()

        when:
        run 'wut'

        then:
        result.assertNotOutput("\${packaging.type}")
    }
}

It passes on 7.4.2, and fails on 7.5+.
(I don't know how to construct a unit test to demonstrate this because I'm not exactly sure which unit is causing the problem)

Your Environment
I don't have a build scan, but the integration test above should easily reproduce the issue when run from the Gradle source tree in any environment. I tested specifically on MacOS 12.6.2 using JDK version:
openjdk version "11.0.15" 2022-04-19
OpenJDK Runtime Environment Homebrew (build 11.0.15+0)
OpenJDK 64-Bit Server VM Homebrew (build 11.0.15+0, mixed mode)

as the JVM that launched the Gradle wrapper.

on 7.4.2, resolving this artifact goes through this codepath: https://github.com/gradle/gradle/blob/v7.4.2/subprojects/dependency-management/src/main/java/org/gradle/api/internal/artifacts/repositories/resolver/MavenResolver.java#L255-L260. Evidently it first checked if an artifact with the bogus extension ${packaging.type} existed, and then would fall back to returning a ModuleComponentArtifactMetadata with the extension set to "jar" if not.
That code was deleted in https://github.com/gradle/gradle/commit/65eb04ee404692055d7b9073c7fb1682a4e5424f.

FYI, I believe that this might also be the underlying cause for #21526.

Just got wrecked by this too (context)

Sorry for the late reply.
Thank you for providing a valid report.
The issue is in the backlog of the relevant team, but this area of Gradle is currently not a focus one, so it might take a while before a fix is made.

fixed in https://github.com/gradle/gradle/pull/26850


Buffer size is not larger than the pipe capacity on Linux ppc64le

https://github.com/ruby/spec/blob/fc1cf69cea933e8e5ed942d49ca9eea518818633/core/io/syswrite_spec.rb#L58
The default pipe capacity of Linux ppc64le is 1048576 bytes, while that of Linux x86_64 is 65536 bytes.  This test does not work as intended on ppc64le.  I am not sure if we should simply increase larger_than_pipe_capacity, so I am raising this issue.

Thank you for the report.
I think it's fine to increase it to something like 2 megabytes.
@odaira   Could you make a PR for that?


Add permissions to contents: write  for chart job

https://github.com/danfromtitan/envars-from-node-labels/actions/runs/6615106387/job/17966565413#step:5:56.
References:

https://github.com/helm/chart-releaser-action/issues/110#issue-1238764408
https://github.com/helm/chart-releaser-action#example-workflow

Thanks for pushing this fix, you've got to it faster than me 😄


https://people.csail.mit.edu/asolar/papers/pldi276-chaudhuri.pdf

Smooth interpretation(

Related and Later work

Continuity analysis of programs. POPL 10
Smoothing a program soundly and robustly. CAV 11
Bridging Boolean and quantitative synthesis using smoothed proof search. POPL 14

I am crawling the reference. All I found work only on imperative language without sum type (in one paper one even model program as transformation on bits, WTF)... Wonder if I am looking at the wrong place.

Yep. I guess it was not the thing you thought to be.

http://mlg.eng.cam.ac.uk/pub/pdf/SciGhaGor15.pdf
Maybe we should do smooth interpretation by probabilistic sampling by embedding this into DDF...


useMatches response type is incorrect

What version of Remix are you using?
1.3.4
Steps to Reproduce
I think the return type of useMatches is incorrect:
export declare function useMatches(): {
    id: string;
    pathname: string;
    params: import("react-router").Params<string>;
    data: RouteData;
    handle: any;
}[];

And then RouteData is defined as:
export interface RouteData {
    [routeId: string]: AppData;
}

When in reality RouteData could be a string or an array or anything else in AppData:
export function useMatches(): Matches {
  const matches = useRemixMatches();
  console.log('Matches:', matches);
  return matches;
}

In that :point_up: scenario, the data key in the objects in the array returned by useMatches() is a string not a { [routeId: string]: AppData } object.
Expected Behavior
You should declare the data field as being of type AppData instead of RouteData.
Actual Behavior
It's declared incorrectly: data is defined as an object with the routeId as keys and their corresponding data as values while in reality it's just the corresponding data value itself.

I think you're right:

In this example, the data returned from the loader is a number, and indeed is serialized and deserialized as a number, but the typings are defined as: { [routeId: string]: AppData }

data is now correctly typed as any


Add example button for  Laplace , inverse laplace , Modulous vector , unit vector , Additio ,Subtraction

Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like

A clear and concise description of what you want to happen.

Hi, I want to work on this issue I will start working on it as soon as I get assigned!! I am a part of GSSoC'21.
Kindly assign this issue to me!
Discord Username : Abhijeet Sinha(P)
Discord Tag: #4018


Add Dev Deploy Stage to Continuous Delivery pipeline

As a Developer
I need a deploy stage for my CD pipeline
So that I can deploy microservice to the dev namespace in the Kubernetes cluster
Details and Assumptions

Assuming the Build Stage has been added to the CD pipeline
Assuming the docker image has been successfully built from the Build Stage

Acceptance Criteria
Given the shared IBM Cloud is working
When I set up the deploy stage for the CD pipeline
Then I can deploy microservice to the dev namespace in the Kubernetes cluster

Deploy stage working.


Fix/lesq 186/path aliases b

Description
I want to avoid long relative paths in OWA by using aliases such as @components
How to test
npm run dev access a lesson page
npm run storybook acccess LessonList
npm run test
npm run lint

[ ]  Necessary TS config updates
[ ]  Relative paths replaced in sample files
[ ]  Ensure that tests also run

Checklist

[ ] Added or updated tests where appropriate
[ ] Manually tested across browsers / devices
[ ] Considered impact on accessibility
[ ] Design sign-off
[ ] Approved by product owner

:tada: This PR is included in version 1.207.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Closure and connect argument returning function

Hi,
I have followed described pattern on README page and got to change this
https://github.com/reactjs/reselect#containersvisibletodolistjs-3
const VisibleTodoList = connect(
  makeMapStateToProps,
  mapDispatchToProps
)(TodoList)

by
const VisibleTodoList = connect(
  makeMapStateToProps(),
  mapDispatchToProps
)(TodoList)

Any ideas, can it be due to our redux version ?
Thanks,
Julien

I'm afraid the question isn't clear.  Can you explain your situation further?  What specific problem are you having?  What are you trying to do?

I have just been following home page tutorial with the following code
const makeMapStateToProps = () => {
  const getVisibleTodos = makeGetVisibleTodos()
  const mapStateToProps = (state, props) => {
    return {
      todos: getVisibleTodos(state, props)
    }
  }
  return mapStateToProps
}

And then add it to connect function as a first parameter
connect(makeMapStateToProps, ....

But it was not working so I replaced it by
connect(makeMapStateToProps(), ....

And it worked.
"react-redux": "4.0.6",
"reselect": "2.5.1"

Hmm, I'll take a look.

You need react-redux 4.3 or greater.

Great, thx again, we had to removed our ^dependencies to match version exactly, and I had this bad effect. We will upgrade to last redux version soon.

@darul75 Which error did you get when it "wasn't working"?

Hi sorry I can not remember as it was a long time ago.


Update README.md with a grammar fix

Fixed grammar -  s/your/you/
Got some code for us? Awesome 🎊!
Please include a description of your change & check your PR against this list, thanks!

[x] There's a clear use-case for this code change
[x] Commit message has a short title & references relevant issues
[ ] The build will pass (run yarn test and yarn lint)

More info can be found by clicking the "guidelines for contributing" link above.

No need for me to run yarn - it's a .md file and the only mod was a grammatical correkshun (sic).

Did you mean to close this?

I'm sorry. Yes I thought I had.


Allow for analytical mtr functions

This pull request creates the option to use either the "analytical" marginal tax rate functions (i.e., those derived from the total tax function implied by the ETR function) or the marginal tax rate functions that are unrelated to the ETR functions.
The option is controlled by a boolean, "analytical_mtrs" that is entered in the key word arguments for the model run in run_ogusa.py.  When set to True, the analytical MTRs are used. Else the MTRs unrelated to the ETR functions are used.

@jdebacker I had a comment on one line and a question about another one. I will submit a follow-up PR to prevent duplication in execute.py and execute_large.py. I should have fixed that some time ago.


Add link to the awesome python models list.

Hey,
Do you mind to add my awesome list to your awesome list of lists?
Thanks :D

Absolutely, thanks Grigory!


etcdctl not honoring --output json and responding with plain text for ls command

The global etcdctl option, --output json isn't being honored in the etcdctl ls operation. This is inconsistent with the etcd REST API and obviously not the expected format if --output json was specified.
For example,:
$ etcdctl --output json ls
/fooDir /baz /foo1 /foo3 /new /foo /myDir /newkey
Doing the same thing using the REST API and curl:
$ curl -X GET http://localhost:2379/v2/keys/?quorum=false&recursive=false&sorted=false
{"action":"get","node":{"dir":true,"nodes":[{"key":"/myDir","dir":true,"modifiedIndex":7,"createdIndex":7},{"key":"/newkey","value":"value","modifiedIndex":9,"createdIndex":9},{"key":"/foo","dir":true,"modifiedIndex":35,"createdIndex":35},{"key":"/foo1","value":"bar","modifiedIndex":47,"createdIndex":47},{"key":"/foo3","value":"ba2","modifiedIndex":33,"createdIndex":33},{"key":"/new","value":"bar","modifiedIndex":15,"createdIndex":15},{"key":"/fooDir","dir":true,"modifiedIndex":51,"createdIndex":51},{"key":"/baz","value":"bar","modifiedIndex":14,"createdIndex":14}]}}

@jlamillan Do you want to fix this?

Sure, I'll submit a pull request when I get a chance....

@jlamillan Thank you!


Additional commits

Thank you @imclerran for doing this.
I can't push to your branch (because of your permissions I believe), so here is a PR.
I will merge your PR, if you accept this -- otherwise happy to make another and include your commits.

Hmm... I'll have to take a look at my permissions. In the mean time, I merged your commits into my branch. Feel free to merge back to upstream!


(usage with Hapi.js) tests not detected when nested

Do you want to request a feature or report a bug?
bug
What is the current behavior?
reports test as passed when it fails + tests are not detected
If the current behavior is a bug, please provide the steps to reproduce and either a repl.it demo through https://repl.it/languages/jest or a minimal repository on GitHub that we can yarn install and yarn test.
setup hapi.js project
include in server.js the following:
server.route([
{
    method: 'GET',
    path:'/',
    handler: (request, reply) => {

        return reply('hello wossrld');
    }
}
]);

create server.test.js file which has following:
const server = require('./server');

it('responds with hello world', () => {
	server.inject('/', (res) => {
	    expect(res.statusCode).toEqual(200);
	    expect(res.result).toEqual('hello world');
	});
});

Run tests.
The error will be shown in terminal (all in red instead of in usual colour)
but the Tests count in the summary will not detect the nested tests. it will just say 1. the behaviour is as if it does not detect any expect()s at all.
What is the expected behavior?
Test fail
Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.
"node": "8.1.4",
"npm": "5.0.4"
"jest": "^20.0.4"

Not sure if this is relevant, but this is the error message:
Debug: internal, implementation, error
          Error: expect(received).toEqual(expected)

      Expected value to equal:
        200
      Received:
        404
          at server.inject.res (/var/www/app/src/tags/tagsRoutes.test.js:5:26)
          at Shot.inject (/var/www/app/node_modules/hapi/lib/connection.js:329:16)
          at process.nextTick (/var/www/app/node_modules/shot/lib/response.js:27:36)
          at _combinedTickCallback (internal/process/next_tick.js:95:7)
          at Immediate._tickDomainCallback (internal/process/next_tick.js:198:9)
          at runCallback (timers.js:800:20)
          at tryOnImmediate (timers.js:762:5)
          at processImmediate [as _immediateCallback] (timers.js:733:5)

ok I realised what I did wrong.
I'm using this format now:
test('the data is peanut butter', done => {
  function callback(data) {
    expect(data).toBe('peanut butter');
    done();
  }

  fetchData(callback);
});

I still get an error but it might be from Hapi's side rather than Jest.

When testing async code with done callback, you need to also handle failing case with done.fail(error), because jest will crash on unhandled async errors (a long standing bug).

@thymikee I think my error was unrelated to that but it's really useful to know. thank you :)


Fix the SNARK input gadgets due to nonnative update

https://github.com/arkworks-rs/crypto-primitives/issues/11

Thanks for the no_std fix!


feat(Algebra/Star/Unitary): add unitarySubgroup

@eric-wieser What would you like to happen with this?

@eric-wieser What would you like to happen with this?

I don't remember the motivation super clearly any more, but I'd still be happy to have it merged. Sorry for not applying your suggestions sooner!


Fixes 163: Add Any version/Any architecture options

https://issues.redhat.com/browse/HMSCONTENT-163

Made suggested changes, added a test. Woot for learning 😝


IOS - After successful logging not redirecting back to app, so i can't get any response from user.

Problem is only on IOS. On android everything works properly.
{
"react": "^16.0.0-alpha.6",
"react-native": "^0.43.0",
"react-native-google-signin": "^0.11.0",
}
Maybe this will help:
'sendAppEventWithName:body:' is deprecated: Subclass RCTEventEmitter instead

Finally, I found resolution:
Add this method in your AppDelegate.m

(BOOL)application:(UIApplication *)application
openURL:(NSURL *)url
options:(NSDictionary<UIApplicationOpenURLOptionsKey,id> *)options {
BOOL handled = [RNGoogleSignin application:application openURL:url sourceApplication:options[UIApplicationOpenURLOptionsSourceApplicationKey] annotation:options[UIApplicationOpenURLOptionsAnnotationKey]];
return handled;
}

Thanks @misuna1997 for your comment, it solved my problem!
To anybody else with the same problem: if you have enabled universal links/deep links support in your React Native app, Xcode may shout at you with an Duplicate declaration of method application:openURL:options: error. To fix that, replace your existing application:openURL:options method with the following:
- (BOOL)application:(UIApplication *)application
            openURL:(NSURL *)url
            options:(NSDictionary<UIApplicationOpenURLOptionsKey,id> *)options
{
  BOOL handled = [RNGoogleSignin application:application openURL:url sourceApplication:options[UIApplicationOpenURLOptionsSourceApplicationKey] annotation:options[UIApplicationOpenURLOptionsAnnotationKey]];

  return handled || [RCTLinkingManager application:application openURL:url options:options];
}

Original issue seems to be solved.
please check out the Example app for any further debugging.


Do unassign tags when mapped tags list becomes empty

.blank? check was a bug, it also skipped retagging given empty array.
Fixes
https://bugzilla.redhat.com/show_bug.cgi?id=1508437
@miq-bot add-label bug, fine/yes, gaprindashvili/yes
@djberg96 @agrare Tiny but important fix, please review.

LGTM 👍

Yep.  We have some tests for retag_entity but this bug skipped it on a higher level :-)
We also a test for this function, I'm looking at improving it...


setup.sh breaks if it's in a path containing a space

For example, /opt/sandbox/My Stuff.
Pretty annoying.

setup.sh disappeared some time ago - npm install seems to work just fine for me in a folder named ~/tmp/yo yo/ :-)


Ignoring an item does not properly calculate total power

When ignoring an item for recipe calculation, the item's related total power cost is not deducted. Instead, only the dependent items' power values are deducted.
Reproduction:
Using recipe: https://kirkmcdonald.github.io/calc.html#zip=fZLBbsMgEET/xiev5JRLRMTHYDxyV8ULWnDbzy+OrKqJnUp7mpkdnoCFxZluRKwO31lRClX1UnLSSpvcccVSXAkMCaDswwddrNrLMAz9g/p2qppd7XiWpHAh5QylHH1Ft6RpjSjOT5++bUwUWMPK1WbzO7di7LXf14IfI16699K/OiJCVQ60sLDMNCnHaJt1n91O0gIvD4bMLKBVzkyWAq3QrYxbEc3wSl/vQDwJb4EDYuaMHad5pTaW0au9ydpIr/3TvR9Kn17gf9+c+LWxHqke/0CD+wE=

Notice the total power for smelting 22,512 plates of iron (w/ 2 Prod 3 modules in ovens and 8 Speed 3 modules in beacons) is 197.0 MW; Also notice the dependent Iron ore power value is 53.7 MW. Finally, note the current total power of the recipe is 573.3 MW
Select the Iron Plate to be ignored.

Problem: Notice the total power is reduced to 519.7 MW. This is a difference of 53.7 MW, corresponding to the elimination of the Iron Ore from the recipe.
Expected: Since I'm ignoring the crafting recipe of Iron Plate, I expect that the total power to craft that Iron Plate should also be ignored. I expected the total power to instead show as 322.7 MW.
Use case: In this recipe, Iron Plate is smelted "off-site" and is not part of the crafting cost of the collection of factories I'm building. Therefore the power needed to craft the Iron Plate should be ignored so that I can adequately estimate the actual power requirements of these factories and not that of the power requirements for ovens that will not be established here.

I was just about to make this same request. It should at the very least be an option in the settings to exclude "ignored" items from the "total power" tally at the bottom.
When I'm designing a factory section and I toggle some dependencies off, that means they're being brought in from some other factory section so I don't care how much power they took to assemble in that other section, I only care about the power required to produce the items (and non-ignored dependencies) in this section.

Looks like #239 fixes this


Task 34 Completed

SourceCode/2023/Oct2023/Basics/Task34/project.json
Based on the review for the UIPATH code, here are the comments per file:

NoFile:

Add missing Automation Hub URL in the Project Settings.
Clean up by removing the unused UiPath.Mail.Activities, UiPath.Testing.Activities, and UiPath.UIAutomation.Activities packages.

Substraction.xaml

Use log messages for debugging and easy maintenance.
Argument names don't follow the convention, rename 'In_Num1', 'In_Num2', and 'Out_Subs' as per standard.
Assign activity has default name, consider giving it a fitting title.

Addition.xaml

Use log messages for debugging and easy maintenance.
Argument names don't follow the convention, rename 'In_Num1', 'In_Num2', and 'Out_Add' as per standard.

Main.xaml

Use log messages for debugging and easy maintenance.
Remove redundant Dispatcher sequence for simpler workflow.
Assign 'Add Queue Item' activity a more descriptive name.

Performer.xaml

The flowchart might be in an infinite loop. Check for termination conditions with 'Get Transaction Item from Orchestrator'.
Variable names 'Out_ResultSub', and 'Out_Result' don't follow the convention. Fix this.

@Sachinrawal1109
Task 34 not available in this pr reopen it again

SourceCode/2023/Oct2023/Basics/Task34/project.json
Code Review:
"Substraction.xaml":

Argument names 'In_Num1', 'In_Num2', 'Out_Subs' don't follow the naming pattern "^in_(dt_)?([A-Z]|[a-z])+([0-9])*$". Update the naming to respect convention.

"NoFile":

I did not find 'Main.xaml' and 'Performer.xaml'.
Skipping further reviews because of these missing files.

"Addition.xaml":

Argument names 'In_Num1', 'In_Num2', 'Out_Add' don't follow the naming pattern "^in_(dt_)?([A-Z]|[a-z])+([0-9])*$". Update the naming to respect convention.

Task Score:
Code completion: 1 (Missing files. Arguements not in standard format)
Execution: 0 (Missing files)
Annotations and Comments: 0 (Not available from given details).

SourceCode/2023/Oct2023/Basics/SachinRawal/Task34/project.json
Subtraction.xaml
Keep naming constant. You're inconsistent with In_Num1, In_Num2, and Out_Subs. Follow the pattern ^in_(dt_)?([A-Z]|[a-z])+([0-9])*$.
NoFile
Your system can't load Main.xaml and Performer.xaml. They may have errors, double-check those.
Addition.xaml
Just like before, keep argument names constant. Check In_Num1, In_Num2, and Out_Add for the correct pattern ^in_(dt_)?([A-Z]|[a-z])+([0-9])*$.
Score Criteria
Code Completion: 1 (Your code has some issues that need fixing, like naming)
Execution: 1 (Your program has failed to run Main.xaml and Performer.xaml)
Annotations and Comments: 1 (Couldn't find any annotations or comments in your codes)
You have a total score of 3 out of 6. You can do better! Try and address the issues I mentioned for better results.


Error on service IP resolution from VM in multi-network installation

Bug Description
Followed the installation guide on https://istio.io/latest/docs/setup/install/virtual-machine/ and when running curl from the virtual machine it tries to reach the service using k8s internal IP instead of the eastwestgateway external ip.
$ curl -v helloworld.sample.svc:5000/hello
*   Trying <IP_ADDRESS>:5000...
* TCP_NODELAY set
* Connected to helloworld.sample.svc (<IP_ADDRESS>) port 5000 (#0)
> GET /hello HTTP/1.1
> Host: helloworld.sample.svc:5000
> User-Agent: curl/7.68.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 503 Service Unavailable
< content-length: 241
< content-type: text/plain
< date: Thu, 14 Oct 2021 15:37:10 GMT
< server: envoy
<
* Connection #0 to host helloworld.sample.svc left intact
upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport failure reason: TLS error: 268435588:SSL routines:OPENSSL_internal:CLIENTHELLO_TLSEXT 268435646:SSL routines:OPENSSL_internal:PARSE_TLSEXT

$ kubectl get service helloworld -n sample
NAME         TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
helloworld   ClusterIP   <IP_ADDRESS>   <none>        5000/TCP   19h

$ kubectl get service istio-eastwestgateway -n istio-system
NAME                    TYPE           CLUSTER-IP       EXTERNAL-IP                                                                  PORT(S)                                                           AGE
istio-eastwestgateway   LoadBalancer   <IP_ADDRESS>   a39c3b3f23d064affa54f65c62c61b33-0000000000.eu-central-1.elb.amazonaws.com   15021:32382/TCP,15443:32560/TCP,15012:31304/TCP,15017:30364/TCP   19h

Version
$ istioctl version
client version: 1.11.3
control plane version: 1.11.3
data plane version: 1.11.3 (5 proxies), 1.11.0 (1 proxies)
$ kubectl version --short
Client Version: v1.16.3
Server Version: v1.20.5

Additional Information
The cluster was installed using kops and is inside of AWS.
bug-report.tar.gz

it tries to reach the service using k8s internal IP instead of the eastwestgateway external ip.

Unless you saw more info, such as envoy access logs, I don't see anyhting to suggest this. Curl will always show the IP of the DNS resolution, which will be captured and translated by envoy. So the curl logs do not indicate it did not go to the e/w external ip.

I think the TLS error is a red herring perhaps. See [C113] connect timeout in the logs.
Sounds like maybe they are not reachable.
make sure you followed the multi-network steps in the doc - in particular setting VM_NETWORK


Option to show both buffer label and tab label

Currently airline seems to be only able to show either buffer label or tab label (with show_tab_type 1)? Is there any option for showing both, tab label to the far left and buffer label to the far right (just like what lightline can do).
Also is there an option for showing tab name for active tabs only and showing just tab number for the inactive ones?
environment

vim: GVIM 8.0
vim-airline: master
OS: Windows 10

actual behavior
Airline with the configuration opened.

expected behavior
I'm expecting the tabline to show like the following (screenshot with lightline)

in your screenshot you already show a tabline with both tabs and buffers. Don't understand what you are asking for.

in your screenshot you already show a tabline with both tabs and buffers. Don't understand what you are asking for.

Sorry if I didn't make myself clear. I'd like to have the tab type label (for example indicating "Tabs") and the buffer label to show on the both sides of the airline. Or just to take the first pic as an example, showing a label "Tab" to the left of "1.1 airline.vim" and showing a label named "Buffer" to the right of "2 airline.vim"

I see. Will add a label to it, because I find it confusing as well.


Features time and executor-agnostic don't work together

Timing data is stored in the task header, so in the function register_timer it tries to get the task header from the waker.
But this waker is not made by embassy and a panic is generated.
Is this a bug?
Is this intentional or a "won't fix"? (If so, maybe it shouldn't compile or at least that should be documented)
What I'm running into is that I have an async library that can be used in embassy. It needs some timer things.
Then I also want to write some tests using futures-test which then get the aforementioned panic.

I can kinda do it if I make an embassy executor:
    #[test]
    fn main() {
        let res = std::panic::catch_unwind(|| {
            static EXECUTOR: Forever<Executor> = Forever::new();
            let executor = EXECUTOR.put(Executor::new());
            executor.run(|spawner| {
                spawner.spawn(main_loop()).unwrap();
            });
        });

        match res {
            Ok(_) => {}
            Err(e) => match e.downcast::<&str>() {
                Ok(message) if *message == "Done" => {},
                Ok(e) => std::panic::resume_unwind(e),
                Err(e) => std::panic::resume_unwind(e),
            },
        }
    }

But the executor will still run even if all tasks have returned, so the only way to stop the test is with a panic that you then catch which is not optimal...

Fyi, for a similar use case of running embassy in a test, I made this: https://github.com/drogue-iot/ector/blob/main/ector/src/testutil.rs#L269-L361
in addition I created a custom macro so you could run a test being handed a context that would signal the runner to stop on drop.
If ppl are interested I could create some 'embassy-test' crate that would allow writing unit tests the same way, but I think ideally making this embassy-agnostic in the tests would be even better so one could reuse existing test frameworks from tokio etc.

It is intentional that the current Timer implementation is tied to the executor. It keeps track of expirations per task, not per timer, which allows it to reuse the task queue as a timer queue, which means it's faster/smaller etc.
It's not "wontfix", I do believe in interoperability so I think it'd be great to get it working on any executor. It'd require a new from-scratch implementation, with a real "timer queue" where creating a Timer adds an entry, dropping it removes it, and something (perhaps a time driver alarm?) that watches for expirations and wakes the wakers. It will be slower/bigger than the current one, and more annoying to use (you'll have to specify the size of the timer queue upfront) so it should be opt-in, enabled by the feature executor-agnostic (just like the current AtomicWaker/WakerRegistration).
I won't work on it, but will happily mentor+review anyone who wants to try!

embassy-time is now executor-agnostic by default. You can enable an executor agnostic queue with the embassy-time/generic-queue feature, or you can enable the embassy-executor-integrated one with embassy-executor/integrated-timers.


PutItem with ReturnValues set as 'ALL_OLD' doesn't work correctly

A PutItem call with 'ALL_OLD' specified as the ReturnValues should return a copy of the overwritten item.

Hmmm, it certainly tries to do that: https://github.com/mhart/dynalite/blob/0641c3bf29b1171a67f49d58ca47ad676e145884/actions/putItem.js#L22-L23
What is it returning?

I'm just getting an empty object.


Add splitSizeIntoParts option and test

Pull Request
Overview
Adds splitSizeIntoParts option to customize the size of parallel upload chunks.
Use Case
In our project we needed to customize the size of the chunks when parallelUploads is used. This is because our backend expects chunks of a certain size.
Test
Not sure how the devs here test PRs. Here is a simple application that I built on top of the changes:
<snip, will rebuild on request>
Closes
Closes https://github.com/tus/tus-js-client/issues/298

Thanks for the PR, but I think the callback function is too much complexity. What about just passing the array of the part bounds directly in parallelUploads? For example,
parallelUploads: [{start: 0, end: 99}, ..]

That would make the code a lot more simpler since no additional option is required.
In addition, please also add any changed parameter to the documentation in the docs folder.

Hi @Acconut, thanks for the reply. I'm not sure whether passing the final parts or passing a function is better. I'm personally leaning towards keeping the function as it's one less step for the user, and so less prone to error, but I'll trust your judgment on that one.
I don't agree with overloading parallelUploads, though. That doesn't seem less complex than making a new parts or parallelParts option - it's just stuffing the complexity into an existing option. Having a new option seems like it would be more clear, to me at least.

I'm personally leaning towards keeping the function as it's one less step for the user, and so less prone to error, but I'll trust your judgment on that one.

I tend to disagree :) Callbacks are more error-prone in my experience as the order of execution is not as clear as if the user has to do the computation up-front. In addition, since the stack trace for any exception in the callback will also contain lines from tus-js-client, users easily mistaken that for bugs in tus-js-client, inside of inside their own code.
Furthermore, tus-js-client currently only uses callback for options when the property cannot be pre-computed before starting the upload (i.e. onShouldRetry). All other options are pre-computed and passed directly as values. I think we should be consistent and keep this pattern.

Having a new option seems like it would be more clear, to me at least.

True, I agree. A new option parallelUploadBoundaries would be better. However, we should add validation to ensure that parallelUploads === parallelUploadBoundaries.length.
What do you think? Are you interested in making these changes to your PR?

That makes sense to me, I can make those changes. I've been on vacation, but I can try to get to this in the next week or so.

Great, let me know if you need assistance.

Done @Acconut. Feedback welcome!

Merged in https://github.com/tus/tus-js-client/commit/169b099eae1cab3bf9b98e8dcdcf7ffca14c5e6b with some additional changes. Thanks for your work.


Automatic multi-pass

Keep track of the lowest pass count in the db and run the script in a loop internally until the target count is reached.

Closing, because I have no need for this atm, and running the script multiple times really isn't that big of a deal.


fix new composer is not a valid Composer command.

Error:
"compose" is not a valid Composer command.
Fix
let g:phpcomplete_index_composer_command = 'composer --no-ansi'

Error detected while processing function phpcomplete_extended#readDataForProject[4]..phpcomplete_extended#loadProject[11]..<SNR>72_loadIndex[24]..phpcomplete_extended#generateIndex:
line    2:
The composer command "/usr/local/bin/composer" is not a valid Composer command. Please set g:phpcomplete_index_composer_command in your .vimrc file
Loading Index
Error detected while processing function phpcomplete_extended#readDataForProject[4]..phpcomplete_extended#loadProject[11]..<SNR>72_loadIndex[35]..<SNR>72_readIndex:
line    2:
Could not read index file .phpcomplete_extended/phpcomplete_index
Index Loaded.```


Add knobs to adjust healcheck parameters.

Description
Allow customizing the healthcheck parameters.
Note I added effectively two sets of interval/timeout/retries. It looks like we can't use the same set of values on both ALB and ECS, because ECS allow timeout>interval, while ALB does not allow it.
Checklist
General

[x] Added the correct label
[x] Assigned to a specific person or civiform/deployment-system
[x] Created tests which fail without the change (if possible)
[x] Performed manual testing (at a minimum run bin/setup without your changes and then bin/deploy with your changes to ensure your changes don't break existing deployments)
[x] Extended the README / documentation, if necessary

Instructions for manual testing
Ran bin/deploy.
Issue(s) this completes
Fixes https://github.com/civiform/civiform/issues/7698

this lgtm, thanks for adding this! i think you need to submit the pr from a branch though (not a fork) to get the automated tests to pass.

Ah there were a permission issue to push to this repo directly. I'll close this and recreate a PR.


"End Point Is Not An Acceptable Tile"

I noticed in the findPath function the js will return if the endpoint isn't traversable. I'm interested in a state of affairs where a character might interact with a tile that isn't traversable (say, finding a tree with the purpose of cutting it down and get wood, finding a rock to break it and get stone, etc.). Is there any reason I should avoid removing these lines of code if I'm not concerned about whether the endpoint is walkable?

I have exactly the same issue :-/


Seed provider of rc-based cassandra pod is configured with only one Pod IP address

Context: I deployed kubernetes version 1.7.2 using kubeadm:1.7.2.
I first created cassandra-service, then created cassandra-rc, then scaled cassandra-rc to 3 replicas.
The configuration of cassandra.yaml only lists one seed-provider.
    # Ex: "<ip1>,<ip2>,<ip3>"
          - seeds: "<IP_ADDRESS>"

Does this has a negative effect on throughput metrics  for write/read requests?  Otherwise, all podIPs should be listed.
The headless service has been correctly registered with the internal DNS service in my kubeadm based deployment:
ubuntu@kubeadm-master:~$ kubectl exec busybox -- nslookup cassandra
Server:    <IP_ADDRESS>
Address 1: <IP_ADDRESS> kube-dns.kube-system.svc.cluster.local

Name:      cassandra
Address 1: <IP_ADDRESS>
Address 2: <IP_ADDRESS>
Address 3: <IP_ADDRESS>

Logs of cassandra instance (see attached file) indeed confirm that only one podIP is passed on:
seed_provider=org.apache.cassandra.locator.SimpleSeedProvider{seeds=<IP_ADDRESS>)

logs.txt

Followup to my question whether one seed node per cluster is bad for performance. According to this site https://blog.threatstack.com/scaling-cassandra-lessons-learned#7, it is not bad for performance. Actually, making all nodes seed nodes is bad for performance. Therefore one seed node per data center rack is sufficient. 2 seeds nodes are recommended for improved fault tolerance.
I also understand now that entrypoint.sh script is programmed such that it only extracts the first podIP. So this script needs to be adjusted if you need 2 seeds.


feat: basic API for the left homology of short complexes

This PR defines the left homology of short complexes and some basic API.

Thanks :tada:
bors merge


Performance issues

Guys, we are suffering some serious performance issues. Does anyone know what is this $select.isActive(this) ?

yeah guys, this is really bad.
I have only 1 select with maybe 500 entries. And it's super slow.
any idea where the problem may be?

ok I worked around this by doing repeat="...... | limitTo: 100", so we don't show a huge list of items.

@gjoliver
limitTo solves the speed issue, but it would be even nicer if remaining items could be appended automatically when the list is scrolled to bottom.

Any update on this? This is kind of a dealbreaker for me. I am migrating from Kendo, and have a dropdown with over 5000 items. In Kendo it opens, loads and filters in ms, in ui-select it's sluggish and often freezes the browser.

I'm having the same issue with around 500 items.  Sometimes the performance gets so bad that the browser actually crashes!

Also a problem for me. I can't do the limitTo: 'myNumber' trick because it doesn't allow previously selected items to be pre-populated unless they're within the first 'myNumber' of my source.

Very recently (~ week ago) performance dropped even further. I have problems with a list of 103 items.

I recently switched from ui-select to angular-selectize due to performance. I'm dealing with lists of ~500 entries each and typing to filter is unacceptably slow.

@mareczek +1

what about "suspending" the watchers instead of using ngIf (which stresses DOM on long lists)?
something like: https://coderwall.com/p/d_aisq/speeding-up-angularjs-s-digest-loop

+1

The performance issues are due to the ng-repeat mechanism in the ui-select-choices directive.  Like askhogan said the dropdown list are getting processed immediately.
Also i added a custom filter and whenever i hover over a dropdown list item, it calls filter for every item in the dropdown list and every time i hover over another item it renders the filter again for every single item in the dropdown list. (at 20 items it already starts to get slow)

The performance issues are due to angular design who makes you build slow apps e and slow components. It's a sad lesson I've learned using ui-select and trying to make it faster for my use case (country dropdowns). In my next project I'll probably look elsewhere (aurelia.io, react, etc..).
@pitieu the hover problem is maybe the easieast to fix in the "angular way". The ng-mouseenter (as any other angular directive or service) calls a full scope digest while a $select digest should be enough, as far as activeIndex is not intended to be used outside the dropdown scope.
But that's just a little part of the problem. Both limitTo and infinite scrolling are possible workarounds but they come at a cost in terms of usability and more code to maintain and debug.
The way I solved my specific use case is a dirty hack. I've replaced the ng-repeat with a loop that rebuilds the entire dropdown content as a string. I don't know if this approach can be used by ui-select itself without breaking some piece of code (it probably would).

Wow, this is a really old thread with no milestone set!  Thanks for the vote of confidence. :confused:

I think in general, github should enable voting per issue, to make transparent where most problems are or what users are most interested in. (of course the motivation/drive of every open source project is always different)
I can imagine many would be voting for this issue.

@igorlino most people just use a :+1: comment to increase interest or resurrect old issues but I agree that this seems like more of a work-around than a feature.  Just as well, you can "subscribe" to issues without directly making a comment and this demonstrates increased community interest in resolving issues.

I think this is related: https://github.com/angular-ui/ui-select/issues/389

:+1: I am also stunned by the slow performance, even on small arrays (< 300 items).

Seeing the same issue :+1:

With https://github.com/angular-ui/ui-select/pull/1211 there should be some improvement

@dimirc there is but not enough to close these issues.

To activate the dropdown select choice only after x letter are typed :
<ui-select-choices  refresh="CheckCity($select.search)" refresh-delay="400"
Add filter
 | limitTo: limitcitysearch"
Than you have :
<ui-select-choices  refresh="CheckCity($select.search)" refresh-delay="400" repeat="item.id as item in vm.territories | filter: {city: $select.search}  | limitTo: limitcitysearch">
In controller
$scope.limitcitysearch = 0;
        $scope.CheckCity = function (CityTyped) {
            if (CityTyped.length >= 1) {         //change 1 to nb letter you want
                $scope.limitcitysearch = 100;
            }
        }

Is there an option to load only first 100 then load more as the user scrolls down?

I am affected by this issue, too.

Anybody that will solve this problem?

Sad to say, but after applying all hacks that I could, including the scrolling filter trick, it was simply not sufficient. So some radical change had to be done...
What did work, and is quite quite performant was to simply switch to another component https://github.com/machineboy2045/angular-selectize
The disadvantage is that is a wrapper to a jquery based component, and does not offer all the themes options.
The advantages are that the directive is very very small, the configuration of it is mostly not in the HTML but in the controller, so the HTML is much easier to read, configure and REUSE.
As the select does not know anything about angular, it also does not inherit Angular performance problems.
selectize is very robust and has tons of options to adapt itself quite well to the angular lifecycle.

@igorlino your update appears to be related to angular-selectize library not ui-select. It doesn't appear to help resolve any problems with performance or add meaningful information to what has already been drescribed.

Can I ask that future posters contribute meaningful updates to the issue.
Useful updates:

Demo plunkrs would be helpful to profile against
Profiling results which show where code is getting slowed down
PRs addressing bottlenecks in code

+1's are not helpful (please use github reactions), open issues are still outstanding and need to be addressed.
Again, PRs are more help than posting in issues.
Thanks all! :smiley_cat:

Currently ctrl.items is searched everytime isActive is called which may be expensive if ctrl.items.length>1000.
ctrl.isActive = function(itemScope) {
    // ...
    var itemIndex = ctrl.items.indexOf(itemScope[ctrl.itemProperty]);
    var isActive =  itemIndex == ctrl.activeIndex;
    // ...
  };

It might be possible to improve isActive() by storing an activeItem rather than comparing on index every time.
Which would reduce isActive() to:
// Gets active item from active index somehow, needs to
// account for changes to activeIndex and activeIndex value
// when using tagging
var activeItem = getActiveItem();

ctrl.isActive = function(itemScope) {
    // ...
    var item = itemScope[ctrl.itemProperty];
    var isActive =  item == activeItem;
    // ...
  };

The filtering logic of ui-select is heavy. The $scope.$apply and $timeout on the keydown event trigger $rootScope.$digest, which forces dirty check on the every watch expression (code: https://github.com/angular-ui/ui-select/blob/9d29307b7c3071e3a14bc15642a3775844d713c0/src/uiSelectController.js#L521-L574). I'm not sure it can be fixed to the local digest cycle. The ui-select2 library is wiser on filtering, it does not triggers the digest cycle on the root scope and faster on filtering, but deprecated 2 years ago.

has this issue been fixed? I already added the "    | limitTo: 100"" but its still a tad slow...

@zone-live please see my comment here: https://github.com/angular-ui/ui-select/issues/88#issuecomment-205769784
I'll remove your comment shortly as we need to focus this discussion resolve the problem...

Done! Sorry about that! ;)
2016-06-08 16:33 GMT+01:00 user378230<EMAIL_ADDRESS>
@zone-live https://github.com/zone-live please see my comment here: #88
(comment)
https://github.com/angular-ui/ui-select/issues/88#issuecomment-205769784
I'll remove your comment shortly as we need to focus this discussion
resolve the problem...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/angular-ui/ui-select/issues/88#issuecomment-224627844,
or mute the thread
https://github.com/notifications/unsubscribe/ABEs_0BbOARR_VCrRUd_FOryN9mQnU7eks5qJuDYgaJpZM4CHjGg
.

I am going with a pagination support that works on scroll. It could be the raw list or the filtered list which may also be bad.
Plnkr
Detailed solution on stackoverflow

Any update on this?

@yogeshgadge  add clear to multiple ui-select will stop populating the dropdown
 $scope.clear = function($event) {
      vm.multipleDemo.selectedPeople=undefined;

  };

Any idea how to fix that?


Completed Spanish Translation

I completed the Spanish translations in the project

Thank you for submitting your pull request. I appreciate the time and effort you put into this contribution. I have decided not to merge this pull request at this time.
Thank you again for your contribution, and I wish you all the best.


How to Scaffold Identity UI in ASP.NET Core 2.2 preview1

From @Amine-Smahi on September 3, 2018 23:17
In ASP.NET Core 2.1 we had the chance to use scaffold using visual studio like this

But now in ASP.NET Core 2.2 preview1 the new scaffold item is missing in visual studio

Copied from original issue: aspnet/Templating#723

@vijayrkn, @seancpeters  is this a known issue?

@mkArtakMSFT - Yes. Scaffolding 2.2 projects will be available in the 15.9 Preview2 release.


improved scrolling account dashboard

#186 is done.
the buttons are now in the header which is now sticky to the top. just the list will scroll.

+5! I improved height and color to handle new themes option


Mike's changes for march 2

Basically retroffiting all EmoCthulhu templates to take advantage of all the wonderful new features and special keywords.

Yeah. I added a spellchecking plugin, then removed it because it was a hassle and a half to retroactively maintain.

Yeah I still need to do Alien, TWD and Blade Runner after physio. Shouldn't take long. Might as well get s0, s, s# and u into those. Won't be finishing pf1 this week. Kinda hoping that the person in #general will take the new release and run with it, the more people that contribute, the better.


Relative coordinates ?

Does it require absolute or relative coordinates ?

gesture_start() takes any coordinates
gesture_track() coordinates should be absolute, the x and y difference between the coordinates is calculated automatically
int xdif = x - gesture_recorder->x;
int ydif = y - gesture_recorder->y;

Keep in mind though, that the implementation could be improved, the linked list is inefficient (in comparison to other vector implementations)

Thanks for answering quickly 😊


JGRP-2505: (4.x) change dns_query to support a comma-separated list of queries

It turns out that our application team is still on JGroups 4.x and not updating to 5.x for the next release. Would you be willing to roll this into the next 4.x release? Would really appreciate it! Thanks :)
In multi-region deployments, it'd be useful to combine addresses from multiple DNS queries to form the cluster. This simple change makes the "dns_query" parameter to DNS_PING a comma-separated list of queries as opposed to a single query like it is currently.

Absolutely, thanks for the PR!

@savitha-ping Note that I just released 4.2.6.Final. It should be available in maven central in 1 hr. Cheers,


remove token and use token.json

note that Discord has an integration with GitHub now - if you push a token to GitHub Discord will automatically reset it for you and send you an alert

Oh shoot! Thank you for reminding me. I'll create a new token for myself, and I'll also remove the token string from the GitHub repo. Silly me


[Furyctl Next] Distro Provider

Installing KFD Core on an existing Kubernetes conformant cluster (provisioned with other methods).
We need to understand the Bussines side of this feature.

Closed because replaced by another issue.


fix: comma after fullstop in Hello Rida section

Problem

Solution

TLDR
fixed typo with additional comma after fullstop in Hello Rida section.
Additional information
none.

Alta. is an old abbreviation for Alberta, so it's meant to have a period after it to denote it as such. 😂


<EMAIL_ADDRESS>Update

Updating runnable-hermes to 6.0.0 6.1.0 and updating various things that changed in that module.

LGTM :100:


Update artifact v4

{download|upload}artifact@v4 is known to cause issues in CentOS7, see
* [Composite Actions using Node 20 don't work with CentOS 7 actions/runner#2906](https://github.com/actions/runner/issues/2906)

* [node20 (and other version) binary used for running actions should be fully statically linked (including libc) actions/setup-node#922](https://github.com/actions/setup-node/issues/922)

On Antares_Simulator, it breaks on OL8 & CentOS7.

Yes. CentOS jobs are kept with v3. OL8 doesn't encounter any issue


G87: Providing closed captions using one of the following techniques:

Kaltura player has the ability to provide captions, when provided.


Bedrock: Implement support for embedded models

Implement support for the embedded models:

amazon.titan-embed-text-v1
cohere.embed-english-v3
cohere.embed-multilingual-v3

https://github.com/newrelic/newrelic-ruby-agent/issues/2366

completed
branch: add_bedrock_instrumentation


Missing string.h include

strings.h is included in spookyhash.h, but not needed.  string.h is missing.
diff --git a/src/spookyhash.c b/src/spookyhash.c
index 3891dd1..7332b15 100644
--- a/src/spookyhash.c
+++ b/src/spookyhash.c
@@ -41,6 +41,8 @@

 #include "spookyhash.h"

+#include <string.h>
+
 SPOOKYHASH_FORCE_INLINE void spookyhash_short_end(uint64_t *restrict h0, uint64_t *restrict h1, uint64_t *restrict h2, uint64_t *restrict h3) {
     *h3 ^= *h2;
     *h2 = SPOOKYHASH_ROTATE(*h2, 15);
diff --git a/src/spookyhash.h b/src/spookyhash.h
index 3a38aeb..c781f3a 100644
--- a/src/spookyhash.h
+++ b/src/spookyhash.h
@@ -43,7 +43,6 @@
 #define SPOOKYHASH_H

 #include "context.h"
-#include <strings.h>

 #define SPOOKYHASH_ALLOW_UNALIGNED_READS   1
 #define SPOOKYHASH_ROTATE(x, k) (((x) << (k)) | (((x) >> (64 - (k)))))

Fixed in 16544cd24cc8f6826749e43af0d90e6c1f313b90. Thank you !


Volume rendering doesn't show when image intensity values are small

If the intensity values in an image only span a small range near zero, the volume rendering appears blank/empty.  However, 2D slices display as expected.
Example dataset is at : https://drive.google.com/file/d/1HeoPACKr_a-sYmEf1d2PGoCJotLrUb-y/view?usp=sharing

default edge gradient is too small for that dataset. Bumping its value allow the volume to be seen.


Replace forEach with for of loops

Having issues with @zodern types when trying to publish:
meteor publish
[zodern:types] => Cleaning old generated types
[zodern:types] => Generating package type declaration files
node_modules/@types/meteor/mongo.d.ts:268:46 - error TS2344: Type 'T' does not satisfy the constraint '{ [key: string]: any; }'.
...

@jankapunkt can you please try if you can release this? As mentioned above I'm having an issue with zodern:types stopping the release.

@StorytellerCZ   api.versionsFrom('2.0'); might this be the issue?

From what I see this is referring to mongo so it might be a core issue and this you may try a newer api.versionsFrom('2.0')

published with api.versionsFrom(['2.8.0']); seemed to do the trick


Introducing a vscode option to allow direct opening of the created file

It's kinda annoying to search for that file, while we could open it directly after creation :lazy:
This is just an idea/proposal ;)

I've reused your code in #9 , thanks @Vin0uz !


 Does anyone know how to do that?
Regards

How to ignore compile child _xxx.scss files?
e.g.
main.scss
@import "theme_green";
@import "theme_light";
when editing _theme_green.scss file should ignore auto compile. Does anyone know how to do that?
Regards

// main.scss
// @import "theme_green";
// @import "theme_light";

It should not compile if commented out here.

Hi Wscats:
Sorry I didn't make it clear. I need these imports for children scss files,  e.g.  _theme_green.scss
and I want main.scss automatically compile when I edit and save the child scss _theme_green.scss,
but I don't want the child scss file _theme_green.scss automatically compile because it only works inside the main.scss.
Regards,
Alex

Hi Wscats:
Sorry I didn't make it clear. I need these imports for children scss files, e.g. _theme_green.scss
and I want main.scss automatically compile when I edit and save the child scss _theme_green.scss,
but I don't want the child scss file _theme_green.scss automatically compile because it only works inside the main.scss.
Regards,
Alex

This approach may require the subsequent addition of an ignore configuration item to go. No way to achieve at this stage☹

You can add your _xxx.scss files in a "components" folder and exclude it on settings.json file:
"compile-hero.ignore": "/components",
could work.

I would like this feature as well. I am running into the exact same issue as OP.
The extension is practically useless in larger projects due to this, as this way of organizing scss files is extremely common.
@rokerbp Your suggestion unfortunately doesn't work.
First off, that configuration option accepts an array of paths, not just one (like this: "compile-hero.ignore": ["**/partials/**/*.scss"]).
Even then, it doesn't work like that. According to the description in the settings, it's meant to ignore formatting only.
Description:
Compile-hero: Ignore
List of paths to ignore when using VS Code format command, including format on save. Uses glob pattern matching.

@Wscats I hope you will reconsider, as this is quite a huge, and important, feature to choose not to support.
To me, it means that I'll be looking elsewhere for an extension to compile SCSS.

I would like this feature as well. I am running into the exact same issue as OP.
The extension is practically useless in larger projects due to this, as this way of organizing scss files is extremely common.
@rokerbp Your suggestion unfortunately doesn't work.
First off, that configuration option accepts an array of paths, not just one
(like this: "compile-hero.ignore": ["**/partials/**/*.scss"]).
Even then, it doesn't work like that. According to the description in the settings, it's meant to ignore formatting only.
Description:
Compile-hero: Ignore
List of paths to ignore when using VS Code format command, including format on save. Uses glob pattern matching.

@Wscats I hope you will reconsider, as this is quite a huge, and important, feature to choose not to support.
To me, it means that I'll be looking elsewhere for an extension to compile SCSS.

This is indeed a very important feature, I will consider implementing it in subsequent versions, thank you for your support.

The new version already supports this feature.
{
  "compile-hero": {
    "ignore": ["src/test.js", "*/test.scss", "**/spec/*", "**/src/**/*"],
  }
}

Is it me or should not a scss compile ignore partials by default ? (just compile main files) ?

Is it me or should not a scss compiler ignore partials by default ? (just compile main files) ?
I would like it to work like:
If i edit a partial, all the main files that includes it should compile, and not a a direct compile of the partial ?
I love this extension but the CSS folder fills up with unused partials.
I could have a look at that if "we" agree.

Sorry, this is not supported for the time being, because it is a troublesome thing to monitor the sub-file changes under the main file. Maybe other non-scss files also introduce this sub-file, which will cause many other files to be forced to compile. I consider adding a configuration item watch attribute in subsequent versions to see if it can be solved similarly.
{
  "compile-hero": {
    "watch": ["src/test.js", "*/test.scss", "**/spec/*", "**/src/**/*"],
  }
}

Ok, good to know! I will be waiting this feature too!

Is it me or should not a scss compiler ignore partials by default ? (just compile main files) ?
I would like it to work like:
If i edit a partial, all the main files that includes it should compile, and not a a direct compile of the partial ?
I love this extension but the CSS folder fills up with unused partials.
I could have a look at that if "we" agree.

Sorry, this is not supported for the time being, because it is a troublesome thing to monitor the sub-file changes under the main file. Maybe other non-scss files also introduce this sub-file, which will cause many other files to be forced to compile. I consider adding a configuration item watch attribute in subsequent versions to see if it can be solved similarly.
{
  "compile-hero": {
    "watch": ["src/test.js", "*/test.scss", "**/spec/*", "**/src/**/*"],
  }
}

Not a bad idea ;)

Is it me or should not a scss compiler ignore partials by default ? (just compile main files) ?
I would like it to work like:
If i edit a partial, all the main files that includes it should compile, and not a a direct compile of the partial ?
I love this extension but the CSS folder fills up with unused partials.
I could have a look at that if "we" agree.

Sorry, this is not supported for the time being, because it is a troublesome thing to monitor the sub-file changes under the main file. Maybe other non-scss files also introduce this sub-file, which will cause many other files to be forced to compile. I consider adding a configuration item watch attribute in subsequent versions to see if it can be solved similarly.
{
  "compile-hero": {
    "watch": ["src/test.js", "*/test.scss", "**/spec/*", "**/src/**/*"],
  }
}

Perfect Idea!

{
  "compile-hero": {
    "watch": ["src/test.js", "*/test.scss", "**/spec/*", "**/src/**/*"],
  }
}

I have added this feature. You can use watch to monitor partial files to see if it can help you solve the current problem. If it can help you, you can give me a five-star praise, thank you very much.

@Wscats sorry, but it's still not clear how to achieve this simple thing (tried all the suggested settings above):

Watch every scss file for changes
Do not compile partials as standalone .css files when they change, but trigger compile other scss files

src/sass/partials/_header.scss:
// just for example
.site-header {
  background-color: black;
}

src/sass/style.scss:
// no other code in this file just importing the partials
@import 'partials/header';
@import 'partials/layout';
@import 'partials/modal';
@import 'partials/gallery';
// ...and more

.vscode/settings.json:
{
  "compile-hero": {
    "scss-output-directory": "../../",
    "ignore": ["**/sass/partials/**/*"],
    "watch": ["**/sass/**/*"]
  }
}

Using the above (suggested) config works only when editing style.scss. If option ignore is omitted, partials are compiled into standalone files.
The simple goal is to compile ONLY style.css when WHATEVER scss file got modified.
This is how it works by default with Webpack and sass, but this plugin would be great to avoid that ~300MB node_modules folder for simple projects...

@Wscats sorry, but it's still not clear how to achieve this simple thing (tried all the suggested settings above):

Watch every scss file for changes
Do not compile partials as standalone .css files when they change, but trigger compile other scss files

src/sass/partials/_header.scss:
// just for example
.site-header {
  background-color: black;
}

src/sass/style.scss:
// no other code in this file just importing the partials
@import 'partials/header';
@import 'partials/layout';
@import 'partials/modal';
@import 'partials/gallery';
// ...and more

.vscode/settings.json:
{
  "compile-hero": {
    "scss-output-directory": "../../",
    "ignore": ["**/sass/partials/**/*"],
    "watch": ["**/sass/**/*"]
  }
}

Using the above (suggested) config works only when editing style.scss. If option ignore is omitted, partials are compiled into standalone files.
The simple goal is to compile ONLY style.css when WHATEVER scss file got modified.
This is how it works by default with Webpack and sass, but this plugin would be great to avoid that ~300MB node_modules folder for simple projects...

@Wscats sorry, but it's still not clear how to achieve this simple thing (tried all the suggested settings above):

Watch every scss file for changes
Do not compile partials as standalone .css files when they change, but trigger compile other scss files

src/sass/partials/_header.scss:
// just for example
.site-header {
  background-color: black;
}

src/sass/style.scss:
// no other code in this file just importing the partials
@import 'partials/header';
@import 'partials/layout';
@import 'partials/modal';
@import 'partials/gallery';
// ...and more

.vscode/settings.json:
{
  "compile-hero": {
    "scss-output-directory": "../../",
    "ignore": ["**/sass/partials/**/*"],
    "watch": ["**/sass/**/*"]
  }
}

Using the above (suggested) config works only when editing style.scss. If option ignore is omitted, partials are compiled into standalone files.
The simple goal is to compile ONLY style.css when WHATEVER scss file got modified.
This is how it works by default with Webpack and sass, but this plugin would be great to avoid that ~300MB node_modules folder for simple projects...

try this in settings.json
"compile-hero.jade-output-toggle": false,   "compile-hero.jade-output-directory": "",   "compile-hero.javascript-output-toggle": false,   "compile-hero.less-output-toggle": false,   "compile-hero.pug-output-toggle": false,   "compile-hero.sass-output-toggle": false,   "compile-hero.stylus-output-toggle": false,   "compile-hero.typescript-output-toggle": false,   "compile-hero.ignore": ["scss/*"],   "compile-hero.watch": ["style.scss"],   "compile-hero.scss-output-directory": "./",   "compile-hero.generate-minified-css": true,   "compile-hero.typescriptx-output-toggle": false,   "compile-hero.disable-compile-files-on-did-save-code": false,

@Wscats sorry, but it's still not clear how to achieve this simple thing (tried all the suggested settings above):

Watch every scss file for changes
Do not compile partials as standalone .css files when they change, but trigger compile other scss files

src/sass/partials/_header.scss:
// just for example
.site-header {
  background-color: black;
}

src/sass/style.scss:
// no other code in this file just importing the partials
@import 'partials/header';
@import 'partials/layout';
@import 'partials/modal';
@import 'partials/gallery';
// ...and more

.vscode/settings.json:
{
  "compile-hero": {
    "scss-output-directory": "../../",
    "ignore": ["**/sass/partials/**/*"],
    "watch": ["**/sass/**/*"]
  }
}

Using the above (suggested) config works only when editing style.scss. If option ignore is omitted, partials are compiled into standalone files.
The simple goal is to compile ONLY style.css when WHATEVER scss file got modified.
This is how it works by default with Webpack and sass, but this plugin would be great to avoid that ~300MB node_modules folder for simple projects...

try this in settings.json
"compile-hero.jade-output-toggle": false,   "compile-hero.jade-output-directory": "",   "compile-hero.javascript-output-toggle": false,   "compile-hero.less-output-toggle": false,   "compile-hero.pug-output-toggle": false,   "compile-hero.sass-output-toggle": false,   "compile-hero.stylus-output-toggle": false,   "compile-hero.typescript-output-toggle": false,   "compile-hero.ignore": ["scss/*"],   "compile-hero.watch": ["style.scss"],   "compile-hero.scss-output-directory": "./",   "compile-hero.generate-minified-css": true,   "compile-hero.typescriptx-output-toggle": false,   "compile-hero.disable-compile-files-on-did-save-code": false,

@richdenis86 thanks, but it won't work with any config (including the one you sent). Currently, watching is needed for all scss files to catch modification and trigger the plugin. Option ignore is needed to not compile the partials. These two knock each other out.

If the file is not watched, the plugin won't do anything when that file is edited.
If the file is in the ignore list, the plugin won't do anything when that file is edited.

As I see, in current version the plugin can't handle the situation (fix me if I'm wrong).
The easiest solution would be a new option something like this:
  "compile-hero.compile-instead": {
    "**/sass/partials/*": "../style.scss"
  },

...so when the currently edited file matches the glob pattern, then instead compile the other file we want. But I'm just wondering, there would be better way to solve this I'm sure.

@richdenis86 thanks, but it won't work with any config (including the one you sent). Currently, watching is needed for all scss files to catch modification and trigger the plugin. Option ignore is needed to not compile the partials. These two knock each other out.

If the file is not watched, the plugin won't do anything when that file is edited.
If the file is in the ignore list, the plugin won't do anything when that file is edited.

As I see, in current version the plugin can't handle the situation (fix me if I'm wrong).
The easiest solution would be a new option something like this:
  "compile-hero.compile-instead": {
    "**/sass/partials/*": "../style.scss"
  },

...so when the currently edited file matches the glob pattern, then instead compile the other file we want. But I'm just wondering, there would be better way to solve this I'm sure.

Same issue here, I only need to compile my main.scss file; no need to do so for the subsequent _partial.scss files, since everything will be compiled into a single main.css file anyway. Any other complilations would be redundant and virtually useless to my project.
There should at least be an option to disable _partials.scss from being compiles (it shouldn't be enabled by default anyway, but y'know, customizability.)

Same here. Need to update a whole folder of *.pug files when I edit any partial file (but not partials). Basically whenever I change any file in "components", "includes", "sections", etc. folder, I need to compile all files in "pages" folder. Currently I am not able to achieve this.

I came here looking for a way to skip partials on compile, so basically anything that starts with an underscore eg.(_color.scss) should be skipped.  Because right now if I make changes to that _colors.scss file, it will also compile it and make a .css file, which is not what I want.  Because the code from the partial will be included in the main file anyways on @import.   Shouldn't that be easy to add as a feature?  Basically anything that starts with an underscore, don't compile that file.
From the comments here though, it sounds like some of you are looking for a way to compile the main.scss file (where the @import is) if a partial gets updated?  Isn't that very difficult to monitor all the files that import the partial?  Am I the only one that resaves the main.scss file, after changes to the partials, in order to recompile a updated css?
Either way, Wscats, for myself and possibly others, is it possible to add a feature to skip compile on scss partials?  Anything that starts with an underscore.  My thought is this should be on by default to be honest.

watch doesnt work properly and reliably with less.
Having a variables.less with just variables worked (while not using watch) if you saved every file manually that imported variables.less
Using watch produces something completely unreliable. Sometimes those values are imported, sometimes not. But you cant force it anymore by saving every file manually.


How to use sqlite database with Osmdroid?

How to use sqlite database with Osmdroid?
to view online?
now i have:
cache.db-journal
cache.db
I need it to be like this:
map1.db-journal
map1.db
GoogleHybrid.db-journal
GoogleHybrid.db
GoogleSatellite..db-journal
Google Satellite.db

view online? like in a browser?

you can browse the database using the sqlite command line utility or the firefox plugin. The database can also be used by osmdroid, there's a few examples in the sample app. The database can also be used by an offline tile server. This can wired up to open layers or a number of other gis javascript libraries or pulled from osmdroid using a custom online tile provider to the tile server. hope this helps

view online? like in a browser?

When I view the online map in MapView, everything is put together in this database:
/osmdroid/tiles/
cache.db-journal
cache.db
osmdroid out of the box support...
I wanted everything to be separate.

Test

https://github.com/osmdroid/osmdroid/blob/master/OpenStreetMapViewer/src/main/java/org/osmdroid/samplefragments/tileproviders/OfflinePickerSample.java

normally, it will load it up, but since the newer versions of android, lots of permissions related issues

reopen or comment if there are further questions


Summary endpoint in xrefs service

Which prefixes can be directly mapped to which (also give provenance information about where these mappings came from)?
Man I just realized this is what OXO was supposed to be able to do but they never finished it

Closed by f48dacf


std::bad_alloc issue with Ubuntu18.04

Tried miopen-benchmark ubuntu18.04 to give a try.
Building of test went fine but while running the test , got "std::bad_alloc" issue.
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted (core dumped)

Issue is coming from  miopen-benchmark's header file when it tries to construct a directory path.
Thread 1 "alexnet" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x00007ffff2779801 in __GI_abort () at abort.c:79
#2  0x00007ffff2dce8fb in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x00007ffff2dd4d3a in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x00007ffff2dd4d95 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5  0x00007ffff2dd4fe8 in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x00007ffff2dfdf26 in std::__throw_bad_alloc() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#7  0x0000000000463ced in __gnu_cxx::new_allocator<std::pair<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, int> >::allocate
    (__n=12297829382473034424, this=<optimized out>) at /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/ext/new_allocator.h:102
#8  std::allocator_traits<std::allocator<std::pair<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, int> > >::allocate (
    __n=12297829382473034424, __a=...) at /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/alloc_traits.h:436
#9  std::_Vector_base<std::pair<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, int>, std::allocator<std::pair<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, int> > >::_M_allocate (__n=12297829382473034424, this=<optimized out>)
    at /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/stl_vector.h:172
#10 std::_Vector_base<std::pair<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, int>, std::allocator<std::pair<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, int> > >::_M_create_storage (__n=12297829382473034424, this=<optimized out>)
    at /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/stl_vector.h:187
#11 std::_Vector_base<std::pair<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, int>, std::allocator<std::pair<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, int> > >::_Vector_base (__n=12297829382473034424, this=<optimized out>, __a=...)
    at /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/stl_vector.h:138
#12 std::vector<std::pair<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, int>, std::allocator<std::pair<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, int> > >::vector (__n=12297829382473034424, this=<optimized out>, __a=...)
    at /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/stl_vector.h:284
#13 std::__detail::_Executor<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::__cxx11::sub_match<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, std::__cxx11::regex_traits<char>, true>::_Executor (__begin=..., __end=...,
    __results=..., __re=..., __flags=<optimized out>, this=<optimized out>) at /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/regex_executor.h:79
#14 std::__detail::__regex_algo_impl<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::__cxx11::sub_match<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, char, std::__cxx11::regex_traits<char>, (std::__detail::_RegexExecutorPolicy)0, true> (__s=118 'v', __e=0 '\000', __m=..., __re=..., __flags=(unknown: 0)) at /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/regex.tcc:78
#15 0x00000000004589d7 in std::regex_match<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::__cxx11::sub_match<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, char, std::__cxx11::regex_traits<char> > (
    __s=<error reading variable: Cannot access memory at address 0x2>, __e=0 '\000', __m=..., __re=..., __flags=(unknown: 0))
    at /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/regex.h:1995
#16 std::regex_match<__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, char, std::__cxx11::regex_traits<char> > (
    __first=<error reading variable: Cannot access memory at address 0x2>, __last=0 '\000', __re=..., __flags=(unknown: 0))
    at /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/regex.h:2022
#17 std::regex_match<std::char_traits<char>, std::allocator<char>, char, std::__cxx11::regex_traits<char> > (__re=..., __flags=(unknown: 0), __s=...)
    at /usr/lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/regex.h:2127
#18 ls_dir (dname=..., match=...) at ./miopen.hpp:142
#19 0x000000000045b41f in Device::init_sys_paths (this=0xc8f270) at ./miopen.hpp:175
#20 0x00000000004590c3 in Devices::init_devices () at ./miopen.hpp:289
#21 0x000000000045b2b6 in device_init () at ./miopen.hpp:299
#22 main (argc=2, argv=0x7fffffffdb20) at alexnet.cpp:60

This may be relevant:
https://stackoverflow.com/questions/36106154/how-to-handle-or-avoid-exceptions-from-c11-regex-matching-functions-28-11
Thanks

I've had this same error before too.  I assumed it was just something odd with my setup (I'm using RHEL7, which is not as well supported), but it appears not.  The issue is with the regex commands.  Specifically, it seems different OS's (or versions of an OS) implement the regex support differently.  For example, I changed this line:
https://github.com/patflick/miopen-benchmark/blob/master/miopen.hpp#L175
to use this:
std::regex("card(\d)+")
(I also applied similar fixes elsewhere in miopen.hpp, but this seems to be the line you're having a problem with)
Not sure if the same fix works for you?
Hope this helps,
Matt

Hi Matt,
miopen.hpp has already below
for (std::string cardname : ls_dir("/sys/class/drm", std::regex("card\d+"))) {
For we are still seeing the issue with regex. It's doesn't help in Ubuntu18.04.
Thanks,

Just in case we're miscommunicating, the change I'm proposing for line 175 is small and based on your response it seems like you may have thought it was identical to what is already there.  Currently it is:
std::regex("card\d+")
I changed it to this:
std::regex("card(\d)+")
Matt

I did the same again as you said but still it's not working.
for (std::string cardname : ls_dir("/sys/class/drm", std::regex("card(\d)+")))

Yeah, the "" doesn't show up unless you use the code feature (put "`" around the code part).
Sorry my fix didn't work for you.    Perhaps one of the others will solve your problem?
Also, when I was making those changes, I broke apart line 175 so I could run with gdb and figure out exactly what is failing.  I suggest you do the same.
Hope this helps,
Matt

My apologies for the late reply.
Your stack trace points to something very odd. Somewhere in regex_match, it tries to allocate a std::vector of size<PHONE_NUMBER>2473034424. I can't reproduce and neither imagine why this would happen. Putting parenthesis around the \\d should not change the regex match, it just creates a capture for the card number. Also then, technically it should be "card(\\d+)" (note the + inside the capture).
Could you try to print out the fname's just prior to the regex match in https://github.com/patflick/miopen-benchmark/blob/master/miopen.hpp#L142
(insert a INFO(fname); prior to that line), and see at which file name it fails with the regex error?

Thanks Patflick. Sorry for delay response.
I tried as suggested and got below:
$ ./layerwise
[INFO]  Number of HIP devices found: 2
[INFO]  card1-DP-6
terminate called after throwing an instance of 'std::bad_alloc'
what():  std::bad_alloc
Aborted (core dumped)
while ((entry = readdir(dir)) != NULL) {
std::string fname(entry->d_name);
if (fname != "." && fname != "..") {
INFO(fname);
if (std::regex_match(fname, match)) {
files.push_back(fname);
void init_sys_paths() {
bool found = false;
for (std::string cardname : ls_dir("/sys/class/drm", std::regex("card(\d+)"))) {
std::string carddir = "/sys/class/drm/" + cardname;
std::string fname = carddir + "/device/uevent";

They seem to have changed the directory structure / folder naming scheme for the sysfs driver api.
I still don't know why the regex would segfault, but the regex card(\\d+) won't match the folder name card1-DP-6. When I first coded this, the cards/devices where named card0, card1,.. etc.
To check the folder structure, can you run tree in /sys/class/drm/ ?
Also, try changing the regex from card(\\d+) to card(\\d+).*. That should allow the code to match the card1-DP-6 folder.

Thanks.
Tried but no luck still.
for (std::string cardname : ls_dir("/sys/class/drm", std::regex("card\\d+).*."))) {

Any more suggestion or is someone looking into it.
Is it possible just to not use regex and instead roll your own parser?

Hi  patflick ,
Can you please resolve this issue. It's pending from long time. All end users are seeing this issue on Ubuntu18.04.
Thanks for the help.

Hi @pramenku
I could never reproduce your error.
I just pushed a code change that might help, although I'm really just guessing. If this doesn't work, your best bet is to try to debug this yourself. Sorry

Thanks @patflick I will try and update you.
Meantime can you please merge https://github.com/patflick/miopen-benchmark/pull/12 PR.

Hi @pramenku . I merged the PR. Did you get a chance to try the potential fix?

Sorry @patflick for delay. Really I was too much occupied with priority tasks.
Without fail, I will update you by tomorrow.

Hi @patflick
I tried with latest changes also, issue is observed.
With rocm release 1.9 and Ubuntu 18.04, we are clearly seeing the issue. I am surprised how no one is seeing this issue. Ideally speaking, everyone should see this issue.

Hi @pramenku,
I think I understand your problem now.  Unfortunately I don't know if there is a happy solution.  To the best of my knowledge, ROCm does not yet support Ubuntu 18.04.  I believe the specific problem you are encountering is that 18.04 has gcc/g++ 7.2 as the "default" gcc/g++, but ROCm needs gcc/g++ 5.4.  Have you tried installing 5.4 locally and pointing to that instead?
Matt

Thanks @mattsinc.
You got exactly what I want to convey.
There is no issue on Ubuntu which has gcc 5.4.
Issue with Ubuntu 18.04 which has gcc 7.2.
With ROCm release 1.9 , Ubuntu 18.04 is also supported. Please check https://github.com/RadeonOpenCompute/ROCm/blob/master/README.md.
So, anyone is trying 18.04 on ROCm 1.9, they will see this issue.

@pramenku, I did not realize that ROCm 1.9 had that support.  If you use gcc 5.4 with ROCm 1.9 does it work?  If so, I would guess the problem is a ROCm problem?
Matt

@mattsinc
It's not issue with ROCm 1.9. It's just that source code of the app needs modification as per Ubuntu 18.04 which has gcc 7.2.
I request someone  to try and debug what needs to be changed as per Ubuntu 18.04.

Hi @patflick and all
It's about 2 months since last discuss, but I encountered the same issue with tip code. My env is  ubuntu 16.04 + manually installed gcc-7.3.0.
To narrow down, I write a very simple example:
#include <regex>
#include <string>
#include <iostream>

int main(){
	std::string fname("amdgpu");
	std::regex card_re("card\\d+");
	bool result = std::regex_match(fname, card_re);

	std::cout<<result<<std::endl;
}

name the above code in "main.cc", I did several test:

use command: /opt/rocm/hip/bin/hipcc main.cc  and run a.out, no problem
use command: /opt/rocm/hip/bin/hipcc -O3 main.cc  and run a.out, std::bad_alloc happen.
use gcc-7.3.0 to compile, no problem for both -O3 or default.

So, I'm curious if hipcc compiler have compatibility issue with gcc-7.3.0, or maybe @pramenku can help test on ubuntu 18.04 environment?

https://github.com/patflick/miopen-benchmark/pull/13
@patflick Hi I make a quick work around for this issue. If this not acceptable just drop it.


Is app.engine supposed to enable multiple view engines?

I was trying to use Express to render *.jade files with jade and *.htm files with a different view engine (nunjucks in this case).
This SO answer led me to believe that using app.engine would be the ticket.
I thought that after setting up multiple app.engines, I would be able to call res.render('./views/hello.jade', ...); or res.render('./views/hello.htm', ...); and each call would render with a different view engine. However it's not working for me, so I'm resorting to rendering HTML strings and sending them with res.send.
Is there an example that shows the supported way to use multiple engines in Express? If not, maybe I'm misunderstanding the point of app.engine.
Here's basically what I tried (paraphrased). I don't like it at all, so I'm probably going to stick with my own code that decides which view engine to use based on the file system's file extension.
// Setup
app.set('views', './src');
app.set('view engine', 'jade');
app.locals = someContext;
app.engine('jade', jade.__express);
app.engine('htm', nunjucks.render);
// ...
app.get('*', function(req, res, next) {
   // Try to render with .jade first, if that doesn't work, try .htm.
  var viewpath = getJadeTemplatePath(req.path); // So, a request for hello/ will try hello.jade first.
  res.render(viewpath, function(err, html) {
      // Code not shown: If err except "template not found" errors, call next(err)
      // Code not shown: If no error, call res.send(html);
      // Otherwise, keep searching...
      var viewpath = getNunjucksTemplatePath(req.path);
      res.render(viewpath, function(err, html) {
        // more attempts for hello/index.jade and hello/index.htm...
      });
  });
}

It should be working, though I'm not entirely sure what is going on in your example. Can you post code for what you think should be working (rather than what your work-around is) and perhaps the version of Express you are using so I can check it out? Ideally I should be able to reproduce the issue.

I thought that after setting up multiple app.engines, I would be able to call res.render('./views/hello.jade', ...); or res.render('./views/hello.htm', ...); and each call would render with a different view engine.

This, to me, describes exactly what app.engine does, which means if it's not doing that, it's either a bug in Express or a miscommunication. More complete code to reproduce the issue would help (like, in the example above, it's really important we know what the contents of getJadeTemplatePath function is, since otherwise we can't tell what the value is you are passing to res.render).

Thanks @dougwilson. OK, so I mostly wanted to make sure that my understanding of the feature was correct. I don't expect you to, but you're welcome to look at my code. It is in heavy alpha now, so I could have totally screwed something up, although it seems fairly straightforward.
I'm using "express": "~4.9.0" and the exact code is here. All of the relevant functions are surrounding renderView and you can see where it occurs in the pipeline in the init function. It only renders jade templates when I comment out this line which is the line that adds the nunjucks engine with app.engine('htm', nunjucks.render);

I'm basically using the Express res.render function to search for files there and I don't like that. So, I'm going to change this code to find out which view template file actually exists first. Then I'll just use the view engines directly like I was doing before.
So, I'll just close this since I got my answer and I don't have a simpler repro for you. Thanks again!

Ah, gotcha. I feel like the failes may have changed since you posted the links, as they don't seem to highlight the right lines when I click on them (which makes it really hard to follow). Please let me know if you need anything, as I'm here to help!


Create intermediate tsconfig.settings.json files as necessary

Relevent when:
somebody makes a new directory for packages
e.g.
/packages/collection/a

where both collection and a are new directories. The necessary tsconfig.setting.json file should look like
{
    "extends": "../tsconfig.settings.json"
}

and live at /packages/collection/tsconfig.settings.json so that it is imported by /packages/collection/a/tsconfig.json.
Question: which package should take this responsibility? I guess it could a new package but we should consider the DX of opting in to these hooks

Closing in advance of deprecation, this ticket is immaterial


Zombie Processes & Memory Leaks

If you close the app - the Python thread continues to run in the background. Definitely an issue with the packaging. Process manager will show this. (OS X specifically).
Also, a leak means it will eventually eat up gigabytes of data. That could be the underlying PoGo API library's fault.

Possible duplicate of #6

Can confirm this on Windows as well - Python process isn't killed and continues to run.

Same windows 10 x64 bit. This needs fixed ASAP and should be marked important.

Yeah, this has been fixed in 0.0.3. I'm going to close it for now. Please open a new issue if the problem still exists.

Confirmed no more Zombies. :-)


508: Programmatic table names are generic

Issue: Data tables contain captions or aria labels, but they are generic and or duplicated.
In the facilities tab, the data tables have a generic aria-label. They should be labeled by the preceding text
role="table" aria-label="Data Table"
Example: Any data tables on the Configurations tab. Systems, Location Attributes etc.

Closed ticket based on discussion with CAMD on 3/4/24. Before deployment there will be a scan performed and any issues will be remediated at that time.