Improve BatchGet / BatchWrite to iterate over 25 records.

Discussed in https://github.com/sensedeep/dynamodb-onetable/discussions/235

Originally posted by ebisbe January  2, 2022
I have a batch process that does 3 simple things. Query items ( I've limited to 500 ) from DDB, each item is sent to a queue and then deletes each item.
I'd like to be able to do something like:
const Items = Model.find(..., {limit: 500})
let batch = {}
for(const Item of Items){
    // send sqs message
   model.remove(..., {batch})
}
table.batchWrite(batch)

But right now I need to do with batchWrite:
const Items = Model.find(..., {limit: 500})
const operations = []
for(const Item of Items){
    // send sqs message
   operations.push({...})
}
do {
    let batch = {}
    const operationsSlice = operations.slice(0, 24)
    operationsSlice.forEach(async operation => await model.remove(operation, { batch }))
    await table.batchWrite(batch)
} while (actions > 0)

It could be real handy that the batchGet/Write handles the limit imposed by DDB to 25 items by doing the slicing himself. Maybe add an option so the user acknowledges he is sending more than 25 items.

Merged.

Hi. Sorry to necrobump, but was this actually merged? I can't see relevant changes in the code or a pull request, and locally batchWrite() still fails with document limit when trying to submit more than 25 documents.

I think you are right. Perhaps got confused with another batch related PR.
I'll reopen and flag.


Cannot install react-native-icons in my existing project

Hello guys, I've tried to setup react-native-icons following the installation guide on github, however my build fails with some errors like (RCTRootView.h , RCTViewManager.h not found)
I've also tried to clone the example and run it on my device but still errors appear when I try to build in xCode.
Any ideas?
Thanks in advance !

Hey @billyshena, that usually means the that the ReactNativeIcons project can't see the React Native headers, have you done Step 6 in the instructions?

Thanks for your quick reply @corymsmith
I've followed each step described in the installation guide.
Here is a screenshot of my xCode settings on the 6th step: http://imgur.com/bwigjbp
Best,

I'm currently having the same problem

Currently having the same or similar problem.
Possibly also as mentioned here.
(null): error: /Users/Chad/Library/Developer/Xcode/DerivedData/ToyTime-dlspuucbonmitigximwovpmsceuh/Build/Products/Debug-iphonesimulator/ReactNativeIconsResources.bundle: No such file or directory

Full log:
CpResource /Users/Chad/Library/Developer/Xcode/DerivedData/ToyTime-dlspuucbonmitigximwovpmsceuh/Build/Products/Debug-iphonesimulator/ReactNativeIconsResources.bundle /Users/Chad/Library/Developer/Xcode/DerivedData/ToyTime-dlspuucbonmitigximwovpmsceuh/Build/Products/Debug-iphonesimulator/ToyTime.app/ReactNativeIconsResources.bundle
    cd /Users/Chad/Documents/ToyTime/ToyTime
    export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin"
    builtin-copy -exclude .DS_Store -exclude CVS -exclude .svn -exclude .git -exclude .hg -resolve-src-symlinks /Users/Chad/Library/Developer/Xcode/DerivedData/ToyTime-dlspuucbonmitigximwovpmsceuh/Build/Products/Debug-iphonesimulator/ReactNativeIconsResources.bundle /Users/Chad/Library/Developer/Xcode/DerivedData/ToyTime-dlspuucbonmitigximwovpmsceuh/Build/Products/Debug-iphonesimulator/ToyTime.app

error: /Users/Chad/Library/Developer/Xcode/DerivedData/ToyTime-dlspuucbonmitigximwovpmsceuh/Build/Products/Debug-iphonesimulator/ReactNativeIconsResources.bundle: No such file or directory

Attempting again from scratch now gets me to the same issue as @billyshena
/Users/Chad/Documents/ToyTime/ToyTime/node_modules/react-native-icons/ios/IconTabBarItem/SMXTabBarManager.h:1:9: 'RCTViewManager.h' file not found

@chadobado @billyshena Can you try to drag ReactNativeIconsResources.bundle into the Copy Bundle Resources build phase of the ReactNativeIcons project as well? I'll have to update the Readme and the install process to clarify things a bit

Great, that fixed it.  Thanks for the quick reply @corymsmith

@chadobado Ok awesome, I'll update the readme

I still have this error, even if I've copied the .bunle into the Copy Bundle Resource build phase of ReactNativeIcons.xcodeProject
CpResource /Users/bshen/Library/Developer/Xcode/DerivedData/scoledgeMob-cgjmophdgfigoxdfmvknkbtkrjis/Build/Products/Debug-iphoneos/ReactNativeIconsResources.bundle /Users/bshen/Library/Developer/Xcode/DerivedData/scoledgeMob-cgjmophdgfigoxdfmvknkbtkrjis/Build/Products/Debug-iphoneos/scoledgeMob.app/ReactNativeIconsResources.bundle
cd /Users/bshen/Desktop/scoledgeMob
export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin"
builtin-copy -exclude .DS_Store -exclude CVS -exclude .svn -exclude .git -exclude .hg -resolve-src-symlinks /Users/bshen/Library/Developer/Xcode/DerivedData/scoledgeMob-cgjmophdgfigoxdfmvknkbtkrjis/Build/Products/Debug-iphoneos/ReactNativeIconsResources.bundle /Users/bshen/Library/Developer/Xcode/DerivedData/scoledgeMob-cgjmophdgfigoxdfmvknkbtkrjis/Build/Products/Debug-iphoneos/scoledgeMob.app

I have the same issue as @billyshena, the absolute path fixed the building problem but I get the same error.

@billyshena @dominikgar Did you install via NPM? That error typically occurs if the JS files aren't found in node_modules in the root of your project

@corymsmith yes I did

I've managed to run my project now, however using your example code, I have this screen: http://i.imgur.com/mTk3L4r.png (you can notice that the TABS are not here)
Don't know if that can help guys.

i had the same issue in the first place, make sure the path was set to "recursive" resolved the problem for me.
(you want to double click on the path , and choose recursive)
Hope this helps

I've set also the option on recursive but that did not change anything.
Billy,

I also had to set the location to something else than "default".
From "relative to group" to "relative to project". I don't know why but it helps me to fix build error with "***.bundle".

I'm working on an update with support for react-native 0.3.11 and also reverting back to just including the font files in your bundle vs. Including a .bundle file. This will also allow you to only include the fonts you use in your app vs. bloating the binary size with icon fonts you aren't using.
On Sun, Apr 12, 2015 at 4:46 PM, Jonas Jonny<EMAIL_ADDRESS>wrote:

I also had to set the location to something else than "default".
From "relative to group" to "relative to project". I don't know why but it helps me to fix build error with "***.bundle".
Reply to this email directly or view it on GitHub:
https://github.com/corymsmith/react-native-icons/issues/6#issuecomment-92146154

:+1:

New version (0.0.2) is published to NPM, I've updated the install instructions as well.


R SOM integration

What is the purpose of this PR?
Reopens the PR that handled R SOM implementation because the commit histories got massively messed up.
This PR now contains the following:

A fully-integrated R SOM implementation with a separate R script running the process in the background. It reads in the preprocessed pixel matrix and can use the MapDataToCodes function to map clusters to the entire dataset based on weights trained on just a small subset.
Complete integration with Docker.
Complete integration with Travis, which runs the entire example_flowsom_clustering notebook and does unit-based testing with some of the parameters.

This PR does not address:

Subsetting, which needs to be handled as a separate command-line argument in som_runner.R. Another PR will be handling that one. Currently, we simply train and run MapDataToCodes on the same dataset passed in.
Preprocessing memory optimization to prevent Docker crashes. Another PR will be handling that one.

Concerns:

Due to the intense R setup that needs to be done in Travis, the tests take a very long time to run. In particular, FlowSOM is a massive installation that requires a ton of dependencies to be compiled. I have not yet found a way to cache the required R packages needed on Travis, and this is in large part because Travis has extremely poor multi-language support (for example, cannot specify separate caches for Python and R packages). if anyone has any experience in this regard would appreciate it.

Because of the imperfect restart, all of the preprocessing.py and initial setup stuff got condensed into one commit with the R SOM stuff. When reviewing this PR, please only look at:

example_flowsom_clustering.ipynb
som_runner.R
Dockerfile
.travis.yml

Because of the imperfect restart, all of the preprocessing.py and initial setup stuff got condensed into one commit with the R SOM stuff. When reviewing this PR, please only look at:

example_flowsom_clustering.ipynb
som_runner.R
Dockerfile
.travis.yml

So here's what's changed:

R installations are no longer necessary in .travis.yml: we've foregone testing the process in som_runner.R (which is called by cluster_pixels) and instead have mocked up cluster_pixels in the testing
We no longer do a full notebook test of example_flowsom_clustering.ipynb with the above point in mind, defaulting this to testbook which also allows us to mock the call to cluster_pixels
testbook tests for example_flowsom_clustering.ipynb are much more lightweight: we leave only a few significant markers in example_dataset and have reduced the test image sizes to 50x50.

So here's what's changed:

R installations are no longer necessary in .travis.yml: we've foregone testing the process in som_runner.R (which is called by cluster_pixels) and instead have mocked up cluster_pixels in the testing
We no longer do a full notebook test of example_flowsom_clustering.ipynb with the above point in mind, defaulting this to testbook which also allows us to mock the call to cluster_pixels
testbook tests for example_flowsom_clustering.ipynb are much more lightweight: we leave only a few significant markers in example_dataset and have reduced the test image sizes to 50x50.

OK, the PR is ready to be reviewed!

OK, the PR is ready to be reviewed!


add present field to Package results

Why
sometimes it's more useful to return whether a path is present than to just filter it out anyways
What changed
added new present field to the json output which returns whether a package is present
Test plan

ci passes
nix run .#rippkgs -- --json rust | jq might have some results that are present and some that aren't

Will this be used by the UI?

Will this be used by the UI?

yes! just have to update the pid1 protos


Feature/weighted multiple datasets

Feature to combine multiple datasets, each one with a sampling weight. This weight is given by the softmax of the normalized dataset sizes, with a user defined temperature.
Also changed WeightedRandomSampler replacement=True so that we can over-sample the smaller datasets, otherwise we will always sample each image once for every epoch. A quick overview on this can be seen here: https://towardsdatascience.com/demystifying-pytorchs-weightedrandomsampler-by-example-a68aceccb452

@gustavofuhr I believe the best thing here is to close this PR and I'll open a new one just for the sampling fix. It is a one liner. And this options of weighting multiple datasets can be redone if needed.


Not let our sample down if property 'azure.activedirectory.tenant-id' is not confugured.

Hi, @saragluna .
Please review and merge. 🙏

Thank you for implementing this @chenrujun it will be very helpful for us in future!


Added parameter example using Target's associated values

Hi!
This adds a simple example of using Target's associated values as parameters for our requests. I've  chosen an example with a Bool value according to what you've pointed out at issue #518.

Current coverage is 67.07% (diff: 100%)

Merging #637 into master will not change coverage

@@             master       #637   diff @@
==========================================
  Files            16         16
  Lines           653        653
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            438        438
  Misses          215        215
  Partials          0          0

Powered by Codecov. Last update b0d7439...1e12e88

Thanks a lot for contributing to Moya! I've invited you to join the Moya GitHub organization – no pressure to accept! If you'd like more information on what that means, check out our contributor guidelines and feel free to reach out with any questions.


Failed to detect the language.

Hi, I was integrating [rehype-pretty-code](https://github.com/atomiks/rehype-pretty-code) with [mdx-bundler](https://www.npmjs.com/package/mdx-bundler} and notice that, the highlight is not working as expected. But When I pass the defaultLang it works fine with that language only. It seems like the highlighter not able to detect the language, any help ?
Here is the MDX-Bundler config
{
    source: mdxContent,
    mdxOptions(options, frontmatter) {
      // this is the recommended way to add custom remark/rehype plugins:
      // The syntax might look weird, but it protects you in case we add/remove
      // plugins in the future.
      options.remarkPlugins = [...(options.remarkPlugins ?? []), remarkGfm]
      options.rehypePlugins = [...(options.rehypePlugins ?? []),
        rehypePrism,
        [rehypePrettyCode, {
          theme: "github-dark",
          defaultLang: "js",
          transformers: [transformerNotationDiff()],
          onVisitLine(node: { children: string | any[] }) {
            // Prevent lines from collapsing in `display: grid` mode, and allow empty
            // lines to be copy/pasted
            if (node.children.length === 0) {
              node.children = [{ type: "text", value: " " }]
            }
          },
          onVisitHighlightedLine(node: { properties: { className: string[] } }) {
            node.properties.className.push("line--highlighted")
          },
          onVisitHighlightedWord(node: { properties: { className: string[] } }) {
            node.properties.className = ["word--highlighted"]
          },
        },],
        [rehypeAutolinkHeadings, {
          properties: {
            className: ["subheading-anchor"],
            ariaLabel: "Link to section",
          },
        }],
        [rehypeHighlight, {}]
      ]

      return options
    },
    grayMatterOptions: options => {
      options.excerpt = true

      return options
    },
  }

tested with below md which is not working

Garlic bread with cheese: What the science tells us
 // [!code --]

Garlic bread with cheese: What the science tells us 1
 // [!code ++]

    For years parents have espoused the health benefits of eating garlic bread
    with cheese to their children, with the food earning such an iconic status
    in our culture that kids will often dress up as warm, cheesy loaf for
    Halloween.

    But a recent study shows that the celebrated appetizer may be linked to a
    series of rabies cases springing up around the country.

Slight aside - I noticed this in your code
// Prevent lines from collapsing in `display: grid` mode, and allow empty
// lines to be copy/pasted
if (node.children.length === 0) {
  node.children = [{ type: "text", value: " " }]
}

Are you having this problem with all languages or just plaintext? May be related to the issue I just opened. ( #157 )

@ben519 that was necessary before the grid option got added in a version some months ago. It's not necessary in the latest versions.
@smroutes I'm not sure I understand your problem. Are you expecting it to detect the language automatically? You need to explicitly specify it:
```html
<article class="prose">
  <h1>Garlic bread with cheese: What the science tells us</h1> // [!code --]
  <h1>Garlic bread with cheese: What the science tells us 1</h1> // [!code ++]
  <p>
    For years parents have espoused the health benefits of eating garlic bread
    with cheese to their children, with the food earning such an iconic status
    in our culture that kids will often dress up as warm, cheesy loaf for
    Halloween.
  </p>
  <p>
    But a recent study shows that the celebrated appetizer may be linked to a
    series of rabies cases springing up around the country.
  </p>
</article>
```

"@atomiks, the issue is the language highlighting feature fails to work for any language other than the default one. it appears that mentioning the language explicitly after the triple backticks (```) causes the highlighting to break.
To illustrate, if the default language is set to JS and the code snippet is as follows:
` ` `
module.exports ={}
` ` `

The highlighting functions correctly. However, when attempting to specify the language explicitly like this:
` ` `js
module.exports ={}
` ` `

in short, I must refrain from explicitly specifying any language in the code. This way, the default language will be automatically selected, and the highlighting will be applied accordingly.

Will need a minimal reproduction repo for this issue. Specifying a language works out of the box and has extensive tests for it. Some config or other plugins may be causing conflicts in your setup.

even if I delete the other plugin, the problem does not resolve. What I can do is, let me draft the issue for now, May be I can create some reproduction repo, and share with here. For now, thanks @atomiks


Remove dependency on time 0.1

Time 0.1 has been deprecated for a long time and since it's only used internally and can be completely replaced by chrono, I think it should be removed.

Very nice, thanks


feat(js): added expo example app

dependent on: #69
Might need to do some work hot-reloading and everything but it works with a build.
Might be good if you review this as well @TimoGlastra

Python CI is suddently failing?

Yeah @andrewwhitehead is this the flaky Python test failing or is there something else going on?

There's a semi random test failure on Ubuntu just as it shuts everything down. It seems like it might be fixed in sqlx 0.6 but that has a different issue on Windows (not releasing the database file on close).

Closing this as the example app is not stable and can be added later.


fix: proper handling of halted txs

What :computer:
Closes #456, closes #462
This PR makes VM rollback when it encounters a halting transaction. This means we can seal blocks with partially halting transactions now. Also halting transactions no longer crash the node.
Why :hand:
Better devx

Please address failed tests


Moving to use kubernetes-maven-plugin to support java 17

very interesting yet again. It seems that if you get this working, we should also close this one.

Our current base image for JKube (1.5.2) is still based on Java 11.
We'll soon release 1.6.0 with an updated base image Java 17 compatible. (https://github.com/eclipse/jkube/pull/1217)
For the current PR you can probably make it work by using the new base image --->
<properties>
  <!-- ... -->
  <jkube.generator.from>quay.io/jkube/jkube-java:0.0.13</jkube.generator.from>
</properties>

The enricher configuration(s) need updating, <fmp-**> tags should be replaced by <jkube-**>

@manusa thanks for the pointers, I made those changes.
I am not entirely sure why I am getting this message or where it is coming from
Did not find any kubernetes/openshift configuration files before starting the test execution. If you are using fabric8-maven-plugin, ensure mvn package fabric8:resource fabric8:build is run first to generate the resources.
https://app.circleci.com/pipelines/github/spring-cloud/spring-cloud-kubernetes/1548/workflows/a1bf9f08-b334-41c4-b26c-6630268f47c0/jobs/2907/steps
Any insights would be appreciated.

I made some progress, the problem at the moment is the deployment yaml generated by arquillian does not contain the registry in the image of the deployment so it fails to pull the image.  I need to think about this some more but I am leaning towards just moving these tests to use kind and not waste any more time here. Arqullian doesn't appear to be maintained anymore we need to move away from it anyways.
https://github.com/spring-cloud/spring-cloud-kubernetes/pull/923/files

Regarding the Docker issue, I think there might be some misconfiguration.
In the previous iteration you didn't need to push the image because the MicroK8s Docker daemon was shared with the host machine. The flag is different now (jkube.docker.host).
I'll try to check locally and create a PR to your branch.

With the changes in the following PR everything seems to work fine (on my machine :shrug:)
https://github.com/ryanjbaxter/spring-cloud-kubernetes/pull/1

:disappointed: these tests are really flaky. Is it possible to increase the CircleCI timeout?

That is why we started this work, cause we were hitting the limits of free tire on circleci.
I am in the blur a little, Ive made a branch where some refactoring happened for these tests to Kind, but I guess the idea is to first stabilize the main branch with minimal changes, and then look at a different approach.

@manusa i think there is a problem downloading the jacoco plugin on circleci at the moment
@wind57 if this does not get things working then we will scrap this effort and just rip the bandaid off, just trying to buy myself some time to look over those changes

Yay! It passed


Uncaught TypeError: Cannot read property 'length' of undefined

[Enter steps to reproduce:]

...
...

Atom: 1.25.1 x64
Electron: 1.7.11
OS: Mac OS X 10.13.3
Thrown From: Atom Core
Stack Trace
Uncaught TypeError: Cannot read property 'length' of undefined
At /Applications/Atom.app/Contents/Resources/app/node_modules/text-buffer/lib/screen-line-builder.js:329

TypeError: Cannot read property 'length' of undefined
    at ScreenLineBuilder.emitText (/Applications/Atom.app/Contents/Resources/app/node_modules/text-buffer/lib/screen-line-builder.js:329:30)
    at ScreenLineBuilder.buildScreenLines (/Applications/Atom.app/Contents/Resources/app/node_modules/text-buffer/lib/screen-line-builder.js:141:22)
    at DisplayLayer.getScreenLines (/Applications/Atom.app/Contents/Resources/app/node_modules/text-buffer/lib/display-layer.js:643:41)
    at TextEditorComponent.queryScreenLinesToRender (/Applications/Atom.app/Contents/Resources/app/src/text-editor-component.js:870:57)
    at TextEditorComponent.updateSyncBeforeMeasuringContent (/Applications/Atom.app/Contents/Resources/app/src/text-editor-component.js:377:16)
    at TextEditorComponent.updateSync (/Applications/Atom.app/Contents/Resources/app/src/text-editor-component.js:275:16)
    at TextEditorComponent.didMouseWheel (/Applications/Atom.app/Contents/Resources/app/src/text-editor-component.js:1553:59)

Commands

Non-Core Packages
atom-beautify 0.30.9
atom-ide-ui 0.9.1
autocomplete 0.47.0
ide-css 0.2.0
ide-flowtype 0.19.0
ide-html 0.4.1
ide-vue 0.1.8
javascript-snippets 1.2.1
language-vue 0.23.1
open-in-browser 0.5.2
script 3.17.3
teletype 0.8.0

Thanks for taking the time to contribute!
We noticed that this is a duplicate of https://github.com/atom/atom/issues/16892. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


SignalR Negotiate: access token lifetime

Hi James,
I found in the MS implementation that the default access token lifetime is 1 hour:
ServiceOptions.cs
Constants.cs
// Default access token lifetime public static readonly TimeSpan DefaultAccessTokenLifetime = TimeSpan.FromHours(1);
Could you please change it also from 30 minutes to 1 hour in your implementation?
Or better make it configurable or utilize SignalR ServiceOptions.
Sure, if MS opened their AzureSignalRClient it would be perfect (maybe it is worth contacting the Azure team...).
Regards,
Alexey

I just found out this is already possible to generate an instance of SignalRConnectionInfo using existing SignalR extension implementation. Have a look at the sample.

Cool, I’ll get that included! Thanks!
Get Outlook for iOShttps://aka.ms/o0ukef

From: alexeymarkov<EMAIL_ADDRESS>Sent: Monday, February 3, 2020 10:29:05 AM
To: JamesRandall/FunctionMonkey<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [JamesRandall/FunctionMonkey] SignalR Negotiate: access token lifetime (#123)
I just found out this is already possible to generate an instance of SignalRConnectionInfo using existing SignalR extension implementation. Have a look at the samplehttps://github.com/Azure/azure-functions-signalrservice-extension/blob/dev/samples/simple-chat/csharp/FunctionApp/Functions.cs#L33l.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/JamesRandall/FunctionMonkey/issues/123?email_source=notifications&email_token=AABZVV72WHHYRJQ75BEJ6DTRA7WXDA5CNFSM4KPCSQZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKTJSAY#issuecomment-581343491, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AABZVV4EQDSRZMTJUZPJEHLRA7WXDANCNFSM4KPCSQZQ.


Training configurations

Does the training api perform image augmentation by default?
I have four classes of objects (arrows:up, down, left and right) the model perform great for up and down but not for left and right however I increase the samples.
So I just want to make sure if the API is not trying to increase the samples by default since it will produce wrong lables.

Yes it does. It is not very well documented, but you can read its source code, is not that hard.

Yea, I disabled it from the source code. Apologise for the late comment


Support JuMP.@constraint

First of all, thank you for making SNOPT available in Julia!
I was able to run the JuMP example in example/hs72.jl. However, I am not able to run an equivalent formulation in which the last constraint is encoded via JuMP.@constraint rather than JuMP.@NLconstraint:
import JuMP
import SNOPT7

m = JuMP.Model(JuMP.optimizer_with_attributes(
        SNOPT7.Optimizer,
        "print_level" => 0,
        "system_information" => "yes",
))

JuMP.@variable(m, 1 <= x[i = 1:4] <= 5)
JuMP.@NLobjective(m, Min, x[1] * x[4] * (x[1] + x[2] + x[3]) + x[3])
JuMP.@NLconstraint(m, x[1] * x[2] * x[3] * x[4] >= 25)
JuMP.@constraint(m, sum(el -> el^2, x) == 40)

JuMP.optimize!(m)

println(JuMP.value.(x))

objval = JuMP.objective_value(m)
println("Final objective: $objval")

println(JuMP.termination_status(m))

I am getting the following error message (truncated)
ERROR: LoadError: `MOI.ScalarQuadraticFunction{Float64}`-in-`MOI.EqualTo{Float64}` constraints are not supported and cannot be bridged into supported constrained variables and constraints. See details below:
 [1] constrained variables in `MOI.RotatedSecondOrderCone` are not supported because:
   Cannot use `MOIB.Variable.RSOCtoSOCBridge{Float64}` because:
   [2] constrained variables in `MOI.SecondOrderCone` are not supported
   Cannot use `MOIB.Variable.RSOCtoPSDBridge{Float64}` because:
   [5] constrained variables in `MOI.PositiveSemidefiniteConeTriangle` are not supported
   Cannot add free variables and then constrain them because:
   (9) `MOI.VectorOfVariables`-in-`MOI.RotatedSecondOrderCone` constraints are not supported
 [2] constrained variables in `MOI.SecondOrderCone` are not supported because:
   Cannot use `MOIB.Variable.SOCtoRSOCBridge{Float64}` because:
   [1] constrained variables in `MOI.RotatedSecondOrderCone` are not supported
   Cannot add free variables and then constrain them because:
   (11) `MOI.VectorOfVariables`-in-`MOI.SecondOrderCone` constraints are not supported
 [5] constrained variables in `MOI.PositiveSemidefiniteConeTriangle` are not supported because no added bridge supports bridging it.
   Cannot add free variables and then constrain them because:
   (18) `MOI.VectorOfVariables`-in-`MOI.PositiveSemidefiniteConeTriangle` constraints are not supported
 (1) `MOI.ScalarQuadraticFunction{Float64}`-in-`MOI.EqualTo{Float64}` constraints are not supported because:
   Cannot use `MOIB.Constraint.VectorizeBridge{Float64,MOI.VectorQuadraticFunction{Float64},MOI.Zeros,MOI.ScalarQuadraticFunction{Float64}}` because:
   (2) `MOI.VectorQuadraticFunction{Float64}`-in-`MOI.Zeros` constraints are not supported
   Cannot use `MOIB.Constraint.SplitIntervalBridge{Float64,MOI.ScalarQuadraticFunction{Float64},MOI.EqualTo{Float64},MOI.GreaterThan{Float64},MOI.LessThan{Float64}}` because:
[...]

Tl;DR
Is it not possible to use any JuMP.@contraint calls with SNOPT7.jl; i.e. do I have to convert all of them to JuMP.@NLconstraint? If so, are there any plans to support JuMP.@constraint in the future?

Hi, I think this is in-line with the JuMP documentation (https://jump.dev/JuMP.jl/v0.21.1/nlp).  "Note that the @objective and @constraint macros (and corresponding functions) do not currently support nonlinear expressions."
I haven't kept up with recent JuMP developments though so if this isn't accurate, I can look into updating to support @constraint.

Hi, thank you for your quick reply!

Hi, I think this is in-line with the JuMP documentation (https://jump.dev/JuMP.jl/v0.21.1/nlp). "Note that the @objective and @constraint macros (and corresponding functions) do not currently support nonlinear expressions."

I think the use of the term "nonlinear" is a bit confusing in the JuMP documentation. JuMP allows affine and quadratic expression sin @constraint and @objective. Thus, the formulation above should be valid. In fact, Ipopt and other JuMP enabled solvers are able to solve this problem.

I haven't kept up with recent JuMP developments though so if this isn't accurate, I can look into updating to support @constraint.

It would certainly be good to have support for @constraint and @objective in SNOPT7.jl because they are perhaps the main workhorses in JuMP at the moment. Unfortunately, I am not too familiar with the backend of either JuMP or SNOPT7 at this point. However, I'd be happy to help with the implementation of this feature if you can provide some rough guidance of what would be needed for this.


Reduce noise from running empty doc tests

upside:

reduces space taken up in the ci logs and terminal.
takes less ci time as it is not compiling and executing binaries that don't contain any tests.

downside:

if someone's writing doc tests for a particular crate they will have to remove the flag first.

Prior art:
We already have some libs with this flag set. This just makes it more comprehensive.

Seen a couple of 29mins something builds for linux stable as best times before this PR. Getting a 27mins something on test-linux-stable implies it has a positive effect on the ci time. Knocking 40s / a min off the test time isn't much but these things all help.

Which crate has this set?
Honestly, I just see that this will confuse people, because at some point someone will add a doctest and it isn't run or they don't even find out that it isn't run. And for 40 seconds, I don't see why we should do this.

The doc tests are there to check that the docs compile and show examples. It's should not be the end of the world if one gets missed. Doc tests force an individual compile and link for each one. https://matklad.github.io/2021/02/27/delete-cargo-integration-tests.html - Aleksey suggests to avoid them for faster builds.

Which crates? Its 193 crates that have no doc tests that are doing unnecessary links and compiles. The fact that it makes 40+ seconds difference on 54 core build machines tells you its a fairly significant amount of work. We could run a lot of real extra tests in that time.

The doc tests are there to check that the docs compile and show examples. It's should not be the end of the world if one gets missed. Doc tests force an individual compile and link for each one. https://matklad.github.io/2021/02/27/delete-cargo-integration-tests.html - Aleksey suggests to avoid them for faster builds.

The point of doc tests is that docs stays up to date, when the code changes. I see this as much more important and especially time saving for developers than saving some seconds in CI.

The point of doc tests is that docs stays up to date, when the code changes. I see this as much more important and especially time saving for developers than saving some seconds in CI.

This point is only relevant, if there are actually any doc tests. Once there are no doc test, trying to process and run them is simply not needed. In addition, empty doc tests do clutter the test output. Which is the main reason, why I disable them by default.
We are not preventing anyone from adding and running doc tests with this change. Just enable doc tests again for crates, that actually do have them.

The point of doc tests is that docs stays up to date, when the code changes. I see this as much more important and especially time saving for developers than saving some seconds in CI.

This point is only relevant, if there are actually any doc tests. Once there are no doc test, trying to process and run them is simply not needed. In addition, empty doc tests do clutter the test output. Which is the main reason, why I disable them by default.

Sounds like a cargo shortcoming to me that we try to solve here in a manual way.

We are not preventing anyone from adding and running doc tests with this change. Just enable doc tests again for crates, that actually do have them.

Please read my first comment

Please read my first comment

I did. At least the doctest field is documented.
Well, if we start to refrain from using documented features, because they could potentially confuse someone. Anyway, I guess we can agree to disagree on this one :handshake:

Please read my first comment

I did. At least the doctest field is documented.

I did not say anywhere that this is not documented.

Well, if we start to refrain from using documented features, because they could potentially confuse someone. Anyway, I guess we can agree to disagree on this one handshake

If we apply this rule, we could directly reject 70% of all questions, because they mainly result in people not reading docs. What I said is, that if someone adds a doc test and it isn't being run, I already see questions popping up continuously.

However, we can disable doc-tests for some crates, but not sprinkle it through the entire workspace.
But I still see this as something that should be solved in cargo. Why is cargo printing the entire machinery when there is no doc test?

People seem happy with long build times. I will close this.

People seem happy with long build times.

This is not true ;) If you would have proposed this in an automatic way, that it would only be done in CI and would not impact people in any way, completely fine. We also had a lot of talks about optimizing CI in Barcelona. @rcny for example works on integrate proper caching, which should bring down CI times significantly because we are not required anymore to recompile everything.


Doc Update - Add a section explaining how to get VerticaPyLab for developers / or those who want the latest version from GitHub

We need some instructions on how to install verticapylab without VerticaPy.
Further, it needs to explained how one can work with the latest VerticaPy that is available on GitHub.

I can do this if you want.


Tutorial for infrared.

Added the tutorials for infrared. It should work since it's a very simple version from what we have already tested on the Mobile Computing course; though for these transmitter and receiver, the receiver is not receiver a clear HIGH signal (it cannot read 0 values with certainty).

Finished all components.
Good news:

tracking sensor is working (though is more a obstacle detector than a line tracker)
Bad news:
infrared sender and/or receiver not working properly (weak signal)
Voltage translator has a weird behavior (starts correctly but then voltage output starts growing)
Pressure sensor (KY-052) and humidity sensor (KY-015) not working
Can still be improved:
Timeout for ultrassonic distance
Calibration for temperature sensor

thanks, big pull request! please fix the following:

"voltage tanslator" needs more explanation; what does it do? relation between iput/output. maybe the name is "voltage regulator"? doesn the board have 2 regulator son it?

the extension-board page is overloaded, needs to be more structured. Maybe it's enough to format the readme with sections/introduction

is the dht11 lib in ky-015 copied from somewhere? In those cases, please reference the external library and provide a command for downloading instead of copying the code to our repo. Advantages are: less files here, we don't nee to keep the copy updated.

please add clearer "steps to get running" to the tutorials of complicated devices.


Pulumi stack name as compiler argument

Hi, thank you for amazing tool. I am trying to customize pulumi yaml for our needs, and thinking about usage Pulumi.<stack>.yaml as source of our resources/outputs and compiler option with our custom go program which will generate pulumi.yaml and under the hood will have some features like go/template package, templates of our common resources, etc.
It seems currently is no way to give compiler knowing which stack it using. Could Pulumi.yaml has something like:
options:
   compiler: ./compiler "${pulumi.stack}"

Thank you for response!

"compiler" doesn't currently support variable interpolation, but I think we could add the built in variables here. Small backwards compatibility concern here that people might already have command line arguments using ${}.

@Frassle Hi, just to understand when this might be implemented or if it will definitely be implemented someday, so we can create our workaround now to take it from env until it will from argument. Thank you!

OK I looked into this a bit more. Adding something like this would be problematic. For convert and for getting the plugins required because those also needs to load the template (with the compiler if set), but there is no stack name in those scenarios.
Now might still be we add something like this but I think we'd have to mark all variables as empty when doing plugin query and conversions, so we'd call your example with ./compiler "" and it would have to handle that.
That sounds unlikely to work in general, if you can compile the template without the stack name then you should just do that all the time, and if you can't correctly generate the template without the stack name than plugin queries and conversions would be wrong.
I'm inclined to think that this is probably the wrong way to solve the problem your trying to address.

Well, maybe we need more context. We want to switch from pulumi typescript to pulumi yaml. We manage several clusters using pulumi stacks. Some places are similar and we can use configs, some places have additional resources, some places we shouldn't use some resources. So,

we need conditions, which, as far as I know, pulumi yaml doesn't support yet,
we want to create templates for each of our resources to reuse with some changes for each stack. We want to store it in our folder structure and manage it inside pulumi..yaml,
It would be great to be able to create loops when needed, which we can achieve also with golang text/template.

The ability to create your own compiler is a great feature. We can do whatever we want with yaml before outputting it the way pulumi requires. But how do we deal with all this if we have separate stacks and the compiler doesn't know which stack pulumi is using? For me, it doesn't matter how the compiler can get the stack name, it can be from an argument, from the env key if pulumi will process this key at runtime, or even from a file if it is automatically generated. Ultimately, I believe this feature allows the compiler to be more flexible.
If you think this is the wrong way to handle such needs, perhaps I don't know the current functionality of pulumi yaml deeply enough and it is somehow possible. I would appreciate your help and further discussion. Thanks

I think your trying to use multiple stacks but what you actually want are multiple projects.
If you split this into multiple projects each Pulumi.yaml could call into your compiler with arguments to tell it what sort of program to build. That still means each project can fully build it's yaml template for our yaml runtime engine to be able to answer queries from the engine for what plugins are needed, or to convert out to other languages.

I don't think so, we have dev, staging, prod, infra stacks for gcloud. From my perspective, to separate it into projects they should have much more differences. For example, if we have gcloud and aws, yes it should be in different projects.
So, I am right understand that pulumi yaml currently does not handle the stack concept at all, and for use it we need to separate it all into projects? And more importantly, the idea of getting the compiler to know which stack is using (anyway how) it's not possible?

So, I am right understand that pulumi yaml currently does handle the stack concept only for small config changes, if you want something bigger it should be separated it all into projects?

Yeh this is because of the lack of conditions in the final yaml. It's ok to have dev/staging/prod as long as they differ by things like "how big the VM to build is", but not if they differ by "should a VPC be created or not". I think this is a fair case to re-visit that design and maybe allow conditions here. https://github.com/pulumi/pulumi-yaml/issues/191 is currently tracking that idea.

And more importantly, the idea of getting the compiler to know which stack is using (anyway how) it's not possible?

That's probably never going to happen. We need to be able to generate the final yaml for plugin queries and program conversions and there really is no stack name in those scenarios.
I think the overall answer here is this ticket isn't going to happen, but to follow up in https://github.com/pulumi/pulumi-yaml/issues/191 to enable your use case of having conditions between different environments. If you've got some specific cases that you could share in that ticket it would help.

The last try :) Does any possibility exist to hook pulumi stack select ... for storing stack name on our side? Maybe I will create own quick plugin for it or so.

Does any possibility exist to hook pulumi stack select

You could just exec pulumi stack --show-name to get the current name, but it might return error: no stack selected; please use pulumi stack selectorpulumi stack init to choose one

Yes, I thought about it too.
Ok, if you say it will never going to happen that ticket may be closed for now. Thank you for quick responses.


Move pkg/server/grpc to pkg/server/ca.

We will have pkg/server/monitoring as well. Since grpc is the only protocol supported by Istio CA, remove the directory name grpc.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: mangchiandjjoe
Assign the PR to them by writing /assign @mangchiandjjoe in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

security/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Technically node agent is a server as well.

Re "Technically node agent is a server as well."

Totally agree. I've been thinking we can organize as:
security/pkg/citadel , containing current CA server's code
security/pkg/nodeagent/, nodeagent relevant code and with two follow sub-package:

registry/ for current workload management,
secrets/ for SDSServer implementation. (moving current pkg/workload code there)

What do you guys think?

@wattli I'm saying that we can make workload secrets related implementation into nodeagent/, in parallel with the management/. I can send an PR later, might be easier...
@myidpt Thanks, SGTM.


AppWrite: Unable to view notes.

@Dhruv16S I'd like to confirm with you that while i was testing previously showed no issues and worked well, I recently revisited it to verify its functionality as a reference. However, I'm currently unable to view the notes that were created. Could you please help to check on this as i do not have the access to your AppWrite?

@Dhruv16S I would like to check with you as previously i did test and it was working fine but currently i tried again to see the functionality as a reference but it is unable to view the created notes right now. Are you able to check?

@Dhruv16S I'd like to confirm with you that while i was testing previously showed no issues and worked well, I recently revisited it to verify its functionality as a reference. However, I'm currently unable to view the notes that were created. Could you please help to check on this as i do not have the access to your AppWrite?

@JustinLim19 I can view your notes and OCR images until March 25th, 2024. Since you have already tried clearing your cache and it did not resolve the issues, can you try creating a new note and see if you are able to view it then?

@Dhruv16S As per your suggestions, I did create a new note but i am unable to view it in the view notes page and question page. Please refer to the screenshots attached.

@Dhruv16S As per your suggestion, I have created a new note. The count in the homepage for 'Notes Created' is updated to 4. However, I am unable to view it in the View Note page and Question page. Please refer to the screenshots attached.

I can see your notes in the database. I'm not sure why it's not being reflected in the app. I'll check the code and get back to you

@Dhruv16S
Looking forward; thank you for your kind assistance!

@Dhruv16S As per your suggestion, I have created a new note. The count in the homepage for 'Notes Created' is updated to 4. However, I am unable to view it in the View Note page and Question page. Please refer to the screenshots attached.

I can see your notes in the database. I'm not sure why it's not being reflected in the app. I'll check the code and get back to you

@Dhruv16S Looking forward to your kind assistance; thank you!

Hi @Dhruv16S , my sincere apologies for bothering you as I’m sure you must be busy with other priorities. May I check if you’ve managed to figure out what the issue is? Thank you for taking the time to even consider this, really appreciate it.

Hi @Dhruv16S , my sincere apologies for bothering you as I’m sure you must be busy with other priorities. May I check if you’ve managed to figure out what the issue is? Thank you for taking the time to even consider this, really appreciate it.

Yeah, I have been going through the code and tried recreating the error, but I could not. I have shared a note titled "Appwrite" with you through the app, could you check if you can view it?

Dear @Dhruv16S ,
Thank you for your help. Unfortunately, I am unable to view your note in the App.
Could you help to delete all data tagged to these three IDs/email?

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
Hopefully once the data tagged to these IDs/email are removed, maybe the issue will resolve. My sincere apologies once again for the inconvenience.

Dear @Dhruv16S ,
Are you able to delete all the data tagged to these three IDs/emails?

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
Hopefully once the data tagged to these IDs/emails are removed, maybe the issue will resolve.
My sincere apologies once again for the inconvenience.
Thank you.


[help wanted] Importing $RefParser causing 'Uncaught ReferenceError: require$$0 is not defined' error.

I've been trying to use this library in my Svelte App, but for some reason when I try to import $RefParser like so:
import $RefParser from '@apidevtools/json-schema-ref-parser';
My App logs the following error to the console: Uncaught ReferenceError: require$$0 is not defined.
I'm using rollup as my bundler, here's my plugins configuration within my rollup.config.js file:
plugins: [
        svelte({
            emitCss: false,
            compilerOptions: {
                dev: !production
            }
        }),
        resolve({
            browser: true,
            dedupe: ['svelte']
        }),
        commonjs({
            include: 'node_modules/**'
        }),
        jsonPlugin(),

I've been trying to play with the plugins order and parameters, but so far nothing seems to make it work.

I am also getting the same error, have you managed to fix it in the past 8 months

In the last 8 months I’ve been scaling the growth of a climate action charity, and I’ve been asking you all for pull requests to help with bugs you’re experiencing. Please do send in some fixes with a few tests and we can get this issue closed.

I made my own system for my project anyway as other ref-parser's didn't work well for me, but I'll leave this open incase someone wants to fix it


Add verify_hostname tls flag

Redis does not allow verify_hostname at all.
Cassandra does allow verify_hostname but some users may wish to disable it.
To support both of these uses an optional verify_hostname field is added to the tls connector config.
It has the safest default value for each protocol and extra validation to ensure that redis cannot be configured to use a setting that it is not compatible with.

Actually having tried it just now in our integration tests, redis doesnt seem to have any hard requirement forcing verify_hostname being disabled.
I'll change it from Option<bool> to bool, removing the default value and redis validation.


Pillow,  duvet-covers, plaid and more textiles icon

Icon Request

Icon name:
Tags of this icon:
Use case:
Screenshots of similar icons:

Cool idea, adding some picture examples to this thread.
Pillow:

Duvet


i18n(zh-cn): Astro together is coming

Description (required)

Update the getting-started bannber

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

zh-cn
getting-started.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

LGTM!


Added "how to install"

This is now outdated as there is an installer that automatically does it for you

Where?

I am sorry, I got confused, I reworded my previous comment


Errors returned from a skill call have an incorrect 'content type' of text/plain

Version
latest
Describe the bug
If an exception occurs when a skill calls the skill host, the content type header is text/plain when it should be application/json
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
This results in 'Cannot deserialize content-type: text/plain'', and it is extremely difficult to determine the actual underlying error.

@EricDahlvang I've seen text before when the response isn't json... as in an error, bad request, etc...  The result code of this is 401.  Could that be related?

I would love to work on this !!


Ft sieve of erastosthene

Implementation of sieve of Eratosthenes in C

Please assign your PR to an existing issue or create a new one.

Resolve #607

Thanks for contributing!

My pleasure.


Unable to install openssl on FreeBSD 12.1 32 bit

Hello, I'm trying to compile openssl 1.1.1d in FreeBSD 12.1 i386 but I'm getting the following error:
ld: error: relocation R_386_PC32 cannot be used against symbol OPENSSL_ia32cap_P; recompile with -fPIC
>>> defined in crypto/cryptlib.o
>>> referenced by crypto/rc4/rc4-586.o:(RC4_set_key)

ld: error: relocation R_386_PC32 cannot be used against symbol OPENSSL_ia32cap_P; recompile with -fPIC
>>> defined in crypto/cryptlib.o
>>> referenced by crypto/rc4/rc4-586.o:(RC4_options)
cc: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[1]: *** [Makefile:756: libcrypto.so] Error 1
gmake[1]: Leaving directory '/usr/home/vagrant/openssl'
gmake: *** [Makefile:174: all] Error 2

I followed these steps:
curl -o openssl-1.1.1d.tar.gz https://www.openssl.org/source/openssl-1.1.1d.tar.gz
gunzip openssl-1.1.1d.tar.gz
tar -xf openssl-1.1.1d.tar
mv openssl-1.1.1d openssl
rm -f openssl-1.1.1d.tar

cd openssl
./config
gmake

What should I do to fix this?

./config shared

./config shared

That should be the default in 1.1.1

I get this:
root@:/usr/home/vagrant/openssl # ./config share
Operating system: i386-pc-freebsd12.1

Failure!  build file wasn't produced.
Please read INSTALL and associated NOTES files.  You may also have to look over
your available compiler tool chain or change your configuration.

target already defined - BSD-x86-elf (offending arg: share)

"shared", not "share"

... but like @mattcaswell says, that shouldn't be the issue, as "shared" is the default

Please give us the output from this command:
./configdata.pm -c

root@:/usr/home/vagrant/openssl # ./configdata.pm -c

Command line (with current working directory = .):

    /usr/local/bin/perl ./Configure BSD-x86-elf shared 386

Perl information:

    /usr/local/bin/perl
    5.30.1 for i386-freebsd-thread-multi-64int

The FreeBSD guys add this to their makefile and it compiles fine (the port, not the vanilla package from openssl.org):
https://github.com/freebsd/freebsd-ports/blob/master/security/openssl/Makefile#L30
May @jesusjimsa you can try to add this to your build scripts?

I still get the same error:
en.o crypto/x509/x_name.o crypto/x509/x_pubkey.o crypto/x509/x_req.o crypto/x509/x_x509.o crypto/x509/x_x509a.o crypto/x509v3/pcy_cache.o crypto/x509v3/pcy_data.o crypto/x509v3/pcy_lib.o crypto/x509v3/pcy_map.o crypto/x509v3/pcy_node.o crypto/x509v3/pcy_tree.o crypto/x509v3/v3_addr.o crypto/x509v3/v3_admis.o crypto/x509v3/v3_akey.o crypto/x509v3/v3_akeya.o crypto/x509v3/v3_alt.o crypto/x509v3/v3_asid.o crypto/x509v3/v3_bcons.o crypto/x509v3/v3_bitst.o crypto/x509v3/v3_conf.o crypto/x509v3/v3_cpols.o crypto/x509v3/v3_crld.o crypto/x509v3/v3_enum.o crypto/x509v3/v3_extku.o crypto/x509v3/v3_genn.o crypto/x509v3/v3_ia5.o crypto/x509v3/v3_info.o crypto/x509v3/v3_int.o crypto/x509v3/v3_lib.o crypto/x509v3/v3_ncons.o crypto/x509v3/v3_pci.o crypto/x509v3/v3_pcia.o crypto/x509v3/v3_pcons.o crypto/x509v3/v3_pku.o crypto/x509v3/v3_pmaps.o crypto/x509v3/v3_prn.o crypto/x509v3/v3_purp.o crypto/x509v3/v3_skey.o crypto/x509v3/v3_sxnet.o crypto/x509v3/v3_tlsf.o crypto/x509v3/v3_utl.o crypto/x509v3/v3err.o  -pthread
ld: error: relocation R_386_PC32 cannot be used against symbol OPENSSL_ia32cap_P; recompile with -fPIC
>>> defined in crypto/cryptlib.o
>>> referenced by crypto/rc4/rc4-586.o:(RC4_set_key)

ld: error: relocation R_386_PC32 cannot be used against symbol OPENSSL_ia32cap_P; recompile with -fPIC
>>> defined in crypto/cryptlib.o
>>> referenced by crypto/rc4/rc4-586.o:(RC4_options)
cc: error: linker command failed with exit code 1 (use -v to see invocation)
*** Error code 1

Stop.
make[1]: stopped in /usr/home/vagrant/openssl
*** Error code 1

Stop.
make: stopped in /usr/home/vagrant/openssl

Should I add the flag somewhere else or just putting it in the Makefile does the trick?

@levitte ?

Should I add the flag somewhere else or just by putting it in the Makefile works?

Passing it as an argument to Configure (or config) is the normal way to do it.

Indeed, I was able to build on Vanilla FreeBSD 12.1 i386 with:
./config LDFLAGS="-Wl,-znotext"
@jesusjimsa Can you adjust this in your build scripts?

I finally could compile it in FreeBSD 12.1 i386. Thank you to everybody! :)

It's not entirely clear to me whether it's appropriate to add that to the "BSD-x86-elf" Configuration entry.


Production server - code security, binaries  ?

please correct me ,if i am missing out something.
while deploying the code on a server , what steps do i need to take if the attacker has physical access to the server (hard drive of the server)
are there any solutions that allow me to deploy binaries , and works full proof.
any help would be appretiated.thank you

@dpranav007 what about hiring ex-marines to move him out of the server room ?

can someone help out please?

@dpranav007 Try StackOverflow, this repository is for tech issues related to Meanjs.


*: rename repository to indigocore-go

The build will obviously be failing as long as I've not renamed the repository...

This change is

I think that go-indigocore is more standard for Go projects.
import "go-indigocore"

indigocore.DoStuff()

vs
import "indigocore-go"

go.DoStuff()

Review status: 0 of 178 files reviewed at latest revision, all discussions resolved, some commit checks broke.

Comments from Reviewable

Since it is quite a calm period for indigo-core I think it would be a good idea to check this in soon, just need to sync with Alexandre and Simon who are working on it to make sure they don't have a lot of work that will be hard to migrate?

Review status: 0 of 178 files reviewed at latest revision, all discussions resolved, some commit checks broke.

Comments from Reviewable

It's really not hard to migrate (basically just a search/replace)
@simonvadee, @alexppxela if you guys are ok I can merge this!

Review status: 0 of 178 files reviewed at latest revision, all discussions resolved, some commit checks broke.

Comments from Reviewable

I do not like prefixing project name by techno due to a language feature. But it is ok for me.

Reviewed 5 of 178 files at r1.
Review status: 5 of 178 files reviewed at latest revision, 1 unresolved discussion, some commit checks broke.

Comments from Reviewable

Not a big fan either but let's say it's a convention rather than a feature! ;)

Review status: 5 of 178 files reviewed at latest revision, all discussions resolved, some commit checks broke.

Comments from Reviewable


[Urgent] Saved data automatically removed after 2,3 hours from Android and IOS devices.

I'm using this package. It is working fine for short time.
I observed after few hours, all data cleaned up from the secure storage.
Most of our users are facing the issue.
Need your urgent support. Thanks
Here is the class I'm using :
`class SecureStorageManager {
static SecureStorageManager? _instance;
late FlutterSecureStorage _storage;
bool _initialized = false;
SecureStorageManager._internal();
factory SecureStorageManager() {
_instance ??= SecureStorageManager._internal();
return _instance!;
}
Future initialize() async {
if (!_initialized) {
_storage = const FlutterSecureStorage(
aOptions: AndroidOptions(
encryptedSharedPreferences: true,  // Secure preferences on Android
),
// iOptions: IOSOptions(
//   accessibility: KeychainAccessibility.first_unlock,  // Secure Keychain on iOS
// ),
);
_initialized = true;
}
}
Future setString(String key, String value) async {
try {
await _storage.write(key: key, value: value);
} catch (e) {
Debugger.log('Error writing value: $e');
}
}
Future<String?> getString(String key) async {
try {
return await _storage.read(key: key);
} catch (e) {
Debugger.log('Error reading value: $e');
return null;
}
}
}`

Please add what motivates you to think that saved data removed after 2,3 hours.  Add some proof too.

@sumitsharansatsangi I am saving my auth data into secure storage at login.
I'm only removing data on the logout button.
But when I logged in and open app after few hours, all my auth data removed from the secured storage.
This is only happened when I'm not opened the App after an hours.
The main point is you can check the issues, many developers complaining same issue they lost their data.

Many who? Please provide some hard proof?
I have never experienced losing saved data either on android or ios?
It's either a coding issue on your end (some other parts of your code deleted those data)
or it's a device specific issue. I know some devices which came preinstalled with 'clean master' or similar app, which periodically 'clean' your phone.

@MohsinIkram-Auxilium,  Don't put what class you are using , instead put your code, you implementation.
If you are hesitating about putting your code make the class name or function name or variable name generic and then put the code.
Another easy way is to self assessment of the issue by running the example code of this package, see whether you put the same issue or not on your multiple devices. if the issue still persist then it will be a device specific issue, mention the model, company and other information of that device. If the issue doesn't persist with the example code and your code is the culprit, Paste the code as said modification.

@Daniel-Cong I have Google Pixal 4a(5G) device.
@sumitsharansatsangi I'm creating a demo project. I will share the link in this thread.

Hi @Daniel-Cong @sumitsharansatsangi,
I have implemented my existing code into seperate project and try to find out the issue why my data is removing after some time. So I have figured out it.
Basically my app is auth based and our session timeout is only one week. After one week we are expiring our token from the backend side and when in APIs when we are getting Expire Token exception then we are clearing the app data.
So unfortunatly due to some reasons there was a bug from the backend side. Our token was expiring after 2,3 hours.
So every time when user open the app after long time, he always moved to login page.
So I apologised to you. Your package is working great.
Thanks for your swift and kind support.


Prefetch ApolloQuery component

Hello!
I wanna prefetch ApolloQuery component
How?

@aleks63 this is a question to ask inside of vue-apollo. This packages is simply wrapping the config part away for Nuxt usage


methods mapped to HTTP calls should expose uniform options

some irregularities in what methods expose options, filter and so on. Check e.g. what methods would admit options and so on

Similar question here. is this something that we now are at least doing a better job of, and we can close and handle tasks case by case?

closing as core is being deprecated away


Build fails with "Expanded null selector" error

I recently added ember-cli-sass and had Sass working fine on one machine. I cloned my repo on a different machine and ran into this issue. The code is the same, cloned directly from the repo.
When I run ember build I get:
version: 1.13.1
Build failed.
Expanded null selector
Error: Expanded null selector
    at options.error (/Users/amageed/code/emberproject/node_modules/ember-cli-sass/node_modules/broccoli-sass-source-maps/node_modules/node-sass/lib/index.js:277:32)

A blank app.scss file gives no error, but any CSS content causes this error to occur.
I'm not sure what could possibly be different between both machines and their setups. They're both running the same versions of node, and all dependencies are coming straight from what I had defined in package.json and bower.json. A co-worker was also able to clone the repo and had a successful build.
I'm on Node v0.12.7 (npm 2.11.3), ember-cli 1.13.1, ember 1.12.1.
I've tried completely removing node and associated folders, and reinstalling the dependencies from npm/bower to start fresh but there was no difference.
Any ideas?

This is almost certainly a node-sass issue. Have you removed the node_modules directory? I suggest you create an issue on node-sass.

Thanks @aexmachina, I'll try there. And yes, I tried removing node_modules and installing everything fresh, but got the same error.

@aexmachina BTW, when I install node-sass via npm and run it directly against my Sass files, it works fine. So I'm not entirely sure node-sass is the issue. Then again, this issue only happens on one of my machines and I'm not sure what else could be the root cause.


Implement java ExplicitValidatorIndex

Implement an explicit validator index for Java as part of #54

As requested, I've added ExplicitValidatorIndex.java, but I'm not sure it's needed.
Generated validators for message type fields continue to use ReflectiveValidatorIndex, which sort of defeats the purpose of this class. I don't see an easy way to allow users to swap out which index the generated validators use, without introducing more static global variables.
Perhaps we can postpone this class until it's requested?


[FEATURE] RFC: axis labels on timeline

A downstream user has requested that I add axis labels to the line chart view. Should that be exposed via props on LineChart, or should I add this downstream?

FYI, there's no pressure here. The only reason to say "yes" to this feature would be if people think it's useful beyond the scope of my specific application.

@zachmullen, sorry for this blast from the past, but do you recall any more information on why that user wanted axis labels? The default wisdom is that a chart like this needs to have axis labels. On the other hand, this display isn't a chart in the classical sense; it's more like a flight instrument and as such requires training up on the system to make good use of it anyway (at which point, the labels wouldn't be as useful). I would be fine with just adding in the axis labels, but the cost of doing so is reduced space for the "meat" of the display so we need a bit of analysis here.
@subdavis, @BryonLewis, @marySalvi: thoughts?

This would be an optional feature and off by default. Users would be required to provide their own text values, at least as I imagined it.
The app we use this in is designed for novice users rather than power users, so the product manager wanted us to add labels to make the chart understandable for them.

Thanks for the clarification, Zach! Do you have a project and/or an engineer that could work on this?


Ensure that kctrl package release accounts for all fields in kapp-controller spec

What this PR does / why we need it:
Updates the version of kapp-controller (server) package consumed by kctrl, ensuring that changes to the spec are accounted for.
Which issue(s) this PR fixes:

Fixes #1117
Does this PR introduce a user-facing change?

Fixed: spec fields added after 0.39.0 are not copied over while using `kctrl package release`

Additional Notes for your reviewer:

How ComponentInfo is faked for local reconciler needs a closer look

[ ] How can users override the kapp-controller version being checked for while running dev? (uses the kctrl version today)

How using CacheDir affects things, and whether or not we can disable it all together is something worth exploring.

Furthermore, to ensure bugs like these are caught early. We should prioritise using the same go.mod for both the tools. We also need to think about how we can run kctrl tests when pieces of kapp-controller that is consumed by it are changed (@praveenrewar this is probably of interest to you).
Review Checklist:

[ ] Follows the developer guidelines
[ ] Relevant tests are added or updated
[ ] Relevant docs in this repo added or updated
[ ] Relevant carvel.dev docs added or updated in a separate PR and there's
a link to that PR
[ ] Code is at least as readable and maintainable as it was before this
change

@100mik when do you plan to merge this one ?

Thank you so much for the bump @imusmanmalik 🙏🏼
Looks like this fell off our radar. I am going to rebase this and then see if this has already been covered by something else.
@praveenrewar I believe you did something similar at some point and I had some deja vu.
is this already covered in the piece of code you merged then we can close it.


reviewer 2 - Automated tests - Errors with importing dataset in generate_MiRTarBase test

openOmics version: 0.8.4
Python version: 3.9
Operating System:

Description
Running MiRTarBase(path="/data/datasets/Bioinformatics_ExternalData/miRTarBase/") in the generate_MiRTarBase test results in an error.
What I Did
Some tests are available and run as part of the Travis CI pipeline, though coverage isn't amazing and would benefit from additional work. Focusing on test driven development is a good way to ensure greater coverage.  Additionally unzip or unrar if the
        file is compressed.

        Args:
            path (str): The folder or url path containing the data file
                resources. If url path, the files will be downloaded and cached
                to the user's home folder (at ~/.astropy/).
            file_resources (dict): default None, Used to list required files for
                preprocessing of the database. A dictionary where keys are
                required filenames and value are file paths. If None, then the
                class constructor should automatically build the required file
                resources dict.
            npartitions:
            verbose:
        """
        if validators.url(path):
            for filename, filepath in copy.copy(file_resources).items():
                data_file = get_pkg_data_filename(path, filepath,
                                                  verbose=verbose)  # Download file and replace the file_resource path
                filetype_ext = filetype.guess(data_file)

                # This null if-clause is needed incase when filetype_ext is None, causing the next clause to fail
                if filetype_ext is None:
                    file_resources[filename] = data_file

                elif filetype_ext.extension == 'gz':
                    file_resources[filename] = gzip.open(data_file, 'rt')

                elif filetype_ext.extension == 'zip':
                    zf = zipfile.ZipFile(data_file, 'r')

                    for subfile in zf.infolist():
                        if os.path.splitext(subfile.filename)[-1] == os.path.splitext(filename)[-1]: # If the file extension matches
                            file_resources[filename] = zf.open(subfile.filename, mode='r')

                elif filetype_ext.extension == 'rar':
                    rf = rarfile.RarFile(data_file, 'r')

                    for subfile in rf.infolist():
                        if os.path.splitext(subfile.filename)[-1] == os.path.splitext(filename)[-1]: # If the file extension matches
                            file_resources[filename] = rf.open(subfile.filename, mode='r')
                else:
                    file_resources[filename] = data_file

        elif os.path.isdir(path) and os.path.exists(path):
            for _, filepath in file_resources.items():
                if not os.path.exists(filepath):
                    raise IOError(filepath)
        else:
>           raise IOError(path)
E           OSError: /data/datasets/Bioinformatics_ExternalData/miRTarBase/

openomics/database/base.py:113: OSError
================================================== warnings summary ==================================================
../../../.pyenv/versions/3.8.7/lib/python3.8/site-packages/_pytest/config/__init__.py:1233
  /Users/stephenmoss/.pyenv/versions/3.8.7/lib/python3.8/site-packages/_pytest/config/__init__.py:1233: PytestConfigWarning: Unknown config option: collect_ignore

    self._warn_or_fail_if_strict(f"Unknown config option: {key}\n")

tests/test_annotations.py: 6 warnings
tests/test_disease.py: 6 warnings
tests/test_interaction.py: 4 warnings
tests/test_multiomics.py: 3 warnings
tests/test_sequences.py: 4 warnings
  /Users/stephenmoss/Dropbox/Code/OpenOmics/openomics/transcriptomics.py:108: ParserWarning: Falling back to the 'python' engine because the 'c' engine does not support sep=None with delim_whitespace=False; you can avoid this warning by specifying engine='python'.
    df = pd.read_table(data, sep=None)

tests/test_annotations.py::test_import_GTEx
tests/test_annotations.py::test_GTEx_annotate
  /Users/stephenmoss/Dropbox/Code/OpenOmics/openomics/database/annotation.py:239: FutureWarning: The default value of regex will change from True to False in a future version.
    gene_exp_medians["Name"] = gene_exp_medians["Name"].str.replace("[.].*", "")

tests/test_disease.py::test_import_HMDD
tests/test_disease.py::test_annotate_HMDD
  /Users/stephenmoss/.pyenv/versions/3.8.7/lib/python3.8/encodings/unicode_escape.py:26: DeprecationWarning: invalid escape sequence '\ '
    return codecs.unicode_escape_decode(input, self.errors)[0]

tests/test_disease.py::test_import_HMDD
tests/test_disease.py::test_annotate_HMDD
  /Users/stephenmoss/.pyenv/versions/3.8.7/lib/python3.8/encodings/unicode_escape.py:26: DeprecationWarning: invalid escape sequence '\s'
    return codecs.unicode_escape_decode(input, self.errors)[0]

tests/test_interaction.py::test_import_LncRNA2Target
  /Users/stephenmoss/Dropbox/Code/OpenOmics/openomics/database/interaction.py:476: FutureWarning: Your version of xlrd is 1.2.0. In xlrd >= 2.0, only the xls format is supported. As a result, the openpyxl engine will be used if it is installed and the engine argument is not specified. Install openpyxl instead.
    table = pd.read_excel(file_resources["lncRNA_target_from_low_throughput_experiments.xlsx"])

tests/test_interaction.py::test_import_LncRNA2Target
  /Users/stephenmoss/Dropbox/Code/OpenOmics/openomics/database/interaction.py:480: FutureWarning: The default value of regex will change from True to False in a future version.
    table["Target_official_symbol"] = table["Target_official_symbol"].str.replace("(?i)(mir)", "hsa-mir-")

-- Docs: https://docs.pytest.org/en/stable/warnings.html

---------- coverage: platform darwin, python 3.8.7-final-0 -----------
Name                                       Stmts   Miss  Cover
--------------------------------------------------------------
openomics/__init__.py                         25      7    72%
openomics/clinical.py                         57     19    67%
openomics/database/__init__.py                 7      0   100%
openomics/database/annotation.py             197    110    44%
openomics/database/base.py                   140     37    74%
openomics/database/disease.py                 61      1    98%
openomics/database/interaction.py            330    196    41%
openomics/database/ontology.py               152     93    39%
openomics/database/sequence.py               128     66    48%
openomics/genomics.py                         26      8    69%
openomics/imageomics.py                       63     47    25%
openomics/multicohorts.py                      0      0   100%
openomics/multiomics.py                      111     66    41%
openomics/proteomics.py                       13      2    85%
openomics/transcriptomics.py                 111     32    71%
openomics/utils/GTF.py                        53     53     0%
openomics/utils/__init__.py                    0      0   100%
openomics/utils/df.py                         23     11    52%
openomics/utils/io.py                         40     19    52%
openomics/utils/read_gtf.py                  107     24    78%
openomics/visualization/__init__.py            1      0   100%
openomics/visualization/heatmat.py            11      8    27%
openomics/visualization/umap.py               29     24    17%
openomics_web/__init__.py                      0      0   100%
openomics_web/app.py                          69     69     0%
openomics_web/callbacks.py                     0      0   100%
openomics_web/layouts/__init__.py              0      0   100%
openomics_web/layouts/annotation_view.py       0      0   100%
openomics_web/layouts/app_layout.py            7      7     0%
openomics_web/layouts/clinical_view.py        10     10     0%
openomics_web/layouts/control_tabs.py          5      5     0%
openomics_web/layouts/datatable_view.py       28     28     0%
openomics_web/server.py                        2      2     0%
openomics_web/utils/__init__.py                0      0   100%
openomics_web/utils/io.py                     62     62     0%
openomics_web/utils/str_utils.py              25     25     0%
setup.py                                      44     44     0%
tests/__init__.py                              0      0   100%
tests/data/__init__.py                         0      0   100%
tests/data/test_dask_dataframes.py             0      0   100%
tests/test_annotations.py                     39      0   100%
tests/test_disease.py                         34      0   100%
tests/test_interaction.py                     20      1    95%
tests/test_multiomics.py                      46      1    98%
tests/test_sequences.py                       18      1    94%
--------------------------------------------------------------
TOTAL                                       2094   1078    49%

============================================== short test summary info ===============================================
ERROR tests/test_interaction.py::test_import_MiRTarBase - OSError: /data/datasets/Bioinformatics_ExternalData/miRTa...
================================ 34 passed, 32 warnings, 1 error in 662.47s (0:11:02) ================================

The main error seemed to be a missing dataset. On further inspection of the codebase it seems that the package is supposed to download the miRTarBase data (although it appears to have the version 7 release URL hardcoded when version 8 is now available). I wondered whether this was a permissions issue with not being able to create the /data/datasets/Bioinformatics_ExternalData/miRTarBase/ path on my system. I tried with sudo python -m pytest --cov=./ tests/test_interaction.py and got the same? I tried sudo mkdir -p /data/datasets/Bioinformatics_ExternalData/miRTarBase beforehand, which returned:
mkdir: /data/datasets/Bioinformatics_ExternalData/miRTarBase: Read-only file system
This is likely due to macOS system integrity protection.
However, it seems I am also unable to resolve http://mirtarbase.mbc.nctu.edu.tw/cache/download/7.0/. I believe the URL should actually be http://mirtarbase.cuhk.edu.cn/cache/download/7.0/ (or even http://mirtarbase.cuhk.edu.cn/cache/download/8.0/)? I manually updated to the working version 7.0 release and updated the path in test_interaction.py before running the following:
mkdir -p tests/data/datasets/Bioinformatics_ExternalData/miRTarBase
sudo python -m pytest --cov=./ tests/test_interaction.py
I still received the error, so something needs looking at in more detail here.

fixed the wrong path at MiRTarBase(path="/data/datasets/Bioinformatics_ExternalData/miRTarBase/") which was previously hard-coded, with this commit https://github.com/BioMeCIS-Lab/OpenOmics/commit/d143ddf43d512018bb280f513f3b4256aa53c50e

Oops my mistake, did not actually fix this issue with the commit d143ddf

The path at MiRTarBase(path="/data/datasets/Bioinformatics_ExternalData/miRTarBase/") is hard-coded to the directory at my local computer.
There are many bioinformatics datasets that are not publicly available via direct download (e.g. lncbase) and may require access permission. In that case, it is expected that the users would obtain the data themself then provide a path to their own local directory.
Since currently, it is difficult to get a reliable ftp download connection from the server at http://mirtarbase.mbc.nctu.edu.tw, I suggest we remove test_import_MiRTarBase from the automated test set that relies on ftp download.

Removed the test_import_MiRTarBase automated test since MiRTarBase is not obtainable via ftp.

Tests all pass, though a few warnings:
$ OpenOmics [master] python -m pytest
============================================================================================================ test session starts =============================================================================================================
platform darwin -- Python 3.8.9, pytest-6.2.3, py-1.10.0, pluggy-0.13.1
rootdir: /Users/stephenmoss/Dropbox/Code/OpenOmics, configfile: setup.cfg
plugins: dash-1.20.0
collected 38 items

tests/test_annotations.py .........                                                                                [ 23%]
tests/test_disease.py ..........                                                                                [ 50%]
tests/test_interaction.py .......                                                                                [ 68%]
tests/test_multiomics.py ...                                                                                [ 76%]
tests/test_sequences.py .........                                                                                [100%]

============================================================================================================== warnings summary ==============================================================================================================
../../../.pyenv/versions/3.8.9/lib/python3.8/site-packages/_pytest/config/__init__.py:1233
  /Users/stephenmoss/.pyenv/versions/3.8.9/lib/python3.8/site-packages/_pytest/config/__init__.py:1233: PytestConfigWarning: Unknown config option: collect_ignore

    self._warn_or_fail_if_strict(f"Unknown config option: {key}\n")

openomics/database/ontology.py:235
  /Users/stephenmoss/Dropbox/Code/OpenOmics/openomics/database/ontology.py:235: DeprecationWarning: invalid escape sequence \|
    and annotation.str.contains("\||;", regex=True).any()):

tests/test_disease.py::test_import_HMDD
tests/test_disease.py::test_annotate_HMDD
  /Users/stephenmoss/.pyenv/versions/3.8.9/lib/python3.8/encodings/unicode_escape.py:26: DeprecationWarning: invalid escape sequence '\ '
    return codecs.unicode_escape_decode(input, self.errors)[0]

tests/test_disease.py::test_import_HMDD
tests/test_disease.py::test_annotate_HMDD
  /Users/stephenmoss/.pyenv/versions/3.8.9/lib/python3.8/encodings/unicode_escape.py:26: DeprecationWarning: invalid escape sequence '\s'
    return codecs.unicode_escape_decode(input, self.errors)[0]

tests/test_interaction.py::test_import_LncRNA2Target
tests/test_interaction.py::test_get_interactions_lnc2target
  /Users/stephenmoss/Dropbox/Code/OpenOmics/openomics/database/interaction.py:479: FutureWarning: Your version of xlrd is 1.2.0. In xlrd >= 2.0, only the xls format is supported. As a result, the openpyxl engine will be used if it is installed and the engine argument is not specified. Install openpyxl instead.
    table = pd.read_excel(file_resources["lncRNA_target_from_low_throughput_experiments.xlsx"])

-- Docs: https://docs.pytest.org/en/stable/warnings.html
================================================================================================= 38 passed, 8 warnings in 603.78s (0:10:03) =================================================================================================


Allow VpnNetworkStack to provide dns and addresses

Task/Issue URL: https://app.asana.com/0/488551667048375/1203276170799087/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

Current dependencies on/for this PR:

develop

PR #2476   👈

This comment was auto-generated by Graphite.


fix: broken image after swtiching between tabs

Description
This PR fixes an issue affecting the activity screen making images in tabs remain gray.
https://github.com/artsy/eigen/assets/11945712/52defe9b-7d69-4fbd-a899-1cb00aa7b4a0

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

Warnings

:warning:

❌ An error occurred while validating your changelog, please make sure you provided a valid changelog.

  Generated by :no_entry_sign: dangerJS against 5fe60fd4583a6a8a98b55839b32ae29cffc98f0c


:hammer_and_wrench: [TASK] : Login / Create Account

As a user, I want to create an account, so that I can start participating.
GIVEN a user that has clicked "Get Started" CTA
WHEN select "Create Account" option
THEN launch simple onboarding flow
AND IF user is crypto savvy
THEN invite them to connect wallet to create account and get seed phrase
AND IF user is not crypto savvy
THEN start with seed phrase generation and provide additional education / context
Tasks

[ ] Conditional paths based on user savviness
[ ] Onboarding info and context to educate new users about web3, key management, and how these bring value to their experience in Catalyst Voices
[ ] Follow best practices in Cardano wallet UX in telling users to keep seed phrase safe, write it down somewhere, don't show to anyone, etc.
[ ] Option to save & download seed phrase as a QR code (Q: needs associated PIN or UX decision?)

completed with mve2


Namespaced ref support for ServiceInstance

This PR adds the necessary references to namespaced versions of classes and plans to the ServiceInstance, along with basic validations and comparable tests.
TODO:

[X] Add NS type tests to defaultserviceplan/admission_test.go
[X] Update svcat tests to expect the new outputs.

@jboyd01 pushed some updates, thanks for the feedback!

This is real big. It is hard to reason about tbh, it all looks correct but my confidence is lower than normal because of how many changes.

@n3wscott I wonder if there's a better way to break it up to make it a little more friendly for review?

I wonder if there's a better way to break it up to make it a little more friendly for review?

Perhaps but I am not sure it is worth the effort... Something to think about for next time...

@pmorie, no the scope of this PR was to update ServiceInstance and PlanReferece types to support namepsaced variations and validations. I'm currently working on a PR that depends on this PR that implements provisioning of namespaced types in the instance loop.

Thank you very much for your review @carolynvs!

Thanks for the ping to take a look again, I had reviewed this originally and the updates look good to me, I was waiting for more reviewers :D

I finally reviewed the remainder of this PR and think I deserve a beer for getting through this!  It LGTM.  Well done @eriknelson


munmap_chunk(): invalid pointer - failures in build compiled by GCC 11

Fedora Rawhide recently upgraded to GCC 11 and rebuilt kyua with it. Because stacktrace_test is always failing on Fedora, unit tests were disabled. That is unfortunate, because kyua became unusable on rawhide. It fails on platforms: armv7hl i686 ppc64le s390x, ppc64le only few test fail. Others fail completely.
Check last rawhide build build.log for alternative architectures. Every single unit test failed, but it was silently ignored. If you check build log
My backtraces in bug report hint, it might be related to compile-time warning:
g++ -DHAVE_CONFIG_H -I.         -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64  -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection  -D_FORTIFY_SOURCE=2 -Wall -Wcast-qual -Wextra -Wpointer-arith -Wredundant-decls -Wreturn-type -Wshadow -Wsign-compare -Wswitch -Wwrite-strings -DNDEBUG -Wctor-dtor-privacy -Wno-deprecated -Wno-non-template-friend -Wno-pmf-conversions -Wnon-virtual-dtor -Woverloaded-virtual -Wreorder -Wsign-promo -Wsynth -c -o utils/utils_auto_array_test-auto_array_test.o `test -f 'utils/auto_array_test.cpp' || echo './'`utils/auto_array_test.cpp
In file included from utils/auto_array_test.cpp:29:
In member function 'utils::auto_array<(anonymous namespace)::test_array>::~auto_array()',
    inlined from '(anonymous namespace)::atfu_tc_release::body() const' at utils/auto_array_test.cpp:203:39:
./utils/auto_array.ipp:95:9: warning: '(anonymous namespace)::test_array::operator delete[](void*)' called on pointer returned from a mismatched allocation function [-Wmismatched-new-delete]
   95 |         delete [] _ptr;
      |         ^~~~~~~~~~~~~~
./utils/auto_array.ipp: In member function '(anonymous namespace)::atfu_tc_release::body() const':
utils/auto_array_test.cpp:78:35: note: returned from 'operator new(unsigned long)'
   78 |         void* mem = ::operator new(size);
      |                     ~~~~~~~~~~~~~~^~~~~~
In file included from utils/auto_array_test.cpp:29:
In member function 'utils::auto_array<(anonymous namespace)::test_array>::~auto_array()',
    inlined from '(anonymous namespace)::atfu_tc_scope::body() const' at utils/auto_array_test.cpp:126:54:
./utils/auto_array.ipp:95:9: warning: '(anonymous namespace)::test_array::operator delete[](void*)' called on pointer returned from a mismatched allocation function [-Wmismatched-new-delete]
   95 |         delete [] _ptr;
      |         ^~~~~~~~~~~~~~
./utils/auto_array.ipp: In member function '(anonymous namespace)::atfu_tc_scope::body() const':
utils/auto_array_test.cpp:78:35: note: returned from 'operator new(unsigned long)'
   78 |         void* mem = ::operator new(size);
      |                     ~~~~~~~~~~~~~~^~~~~~
In file included from utils/auto_array_test.cpp:29:
In member function 'utils::auto_array<(anonymous namespace)::test_array>::~auto_array()',
    inlined from '(anonymous namespace)::atfu_tc_copy::body() const' at utils/auto_array_test.cpp:143:55:
./utils/auto_array.ipp:95:9: warning: '(anonymous namespace)::test_array::operator delete[](void*)' called on pointer returned from a mismatched allocation function [-Wmismatched-new-delete]
   95 |         delete [] _ptr;
      |         ^~~~~~~~~~~~~~
./utils/auto_array.ipp: In member function '(anonymous namespace)::atfu_tc_copy::body() const':
utils/auto_array_test.cpp:78:35: note: returned from 'operator new(unsigned long)'
   78 |         void* mem = ::operator new(size);
      |                     ~~~~~~~~~~~~~~^~~~~~
In file included from utils/auto_array_test.cpp:29:
In member function 'utils::auto_array<(anonymous namespace)::test_array>::~auto_array()',
    inlined from '(anonymous namespace)::atfu_tc_copy_ref::body() const' at utils/auto_array_test.cpp:166:55:
./utils/auto_array.ipp:95:9: warning: '(anonymous namespace)::test_array::operator delete[](void*)' called on pointer returned from a mismatched allocation function [-Wmismatched-new-delete]
...

Backtrace from the bug:
#0  0xf7fca559 in __kernel_vsyscall ()
#1  0xf7a9dbb8 in __libc_signal_restore_set (set=0xffffc2cc) at ../sysdeps/unix/sysv/linux/internal-signals.h:105
#2  __GI_raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:47
#3  0xf7a863c9 in __GI_abort () at abort.c:79
#4  0xf7ae449c in __libc_message (action=<optimized out>, fmt=<optimized out>) at ../sysdeps/posix/libc_fatal.c:155
#5  0xf7aecdaf in malloc_printerr (str=str@entry=0xf7bd373c "munmap_chunk(): invalid pointer") at malloc.c:5626
#6  0xf7aed1fb in munmap_chunk (p=p@entry=0xffffc784) at malloc.c:2995
#7  0xf7af1e00 in __GI___libc_free (mem=0xffffc78c) at malloc.c:3302
#8  0xf7cd3dac in operator delete (ptr=0xffffc78c) at ../../../../libstdc++-v3/libsupc++/del_op.cc:49
#9  0xf7cd3ddc in operator delete (ptr=0xffffc78c) at ../../../../libstdc++-v3/libsupc++/del_ops.cc:33
#10 0x565d53e4 in __gnu_cxx::new_allocator<char>::deallocate (__t=<optimized out>, __p=<optimized out>, this=0xffffc7d8)
    at /usr/include/c++/11/ext/new_allocator.h:139
#11 std::allocator_traits<std::allocator<char> >::deallocate (__n=<optimized out>, __p=<optimized out>, __a=...) at /usr/include/c++/11/bits/alloc_traits.h:492
#12 std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_destroy (__size=<optimized out>, this=0xffffc7d8)
    at /usr/include/c++/11/bits/basic_string.h:237
#13 std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_dispose (this=0xffffc7d8)
    at /usr/include/c++/11/bits/basic_string.h:232
#14 std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string (this=<optimized out>, this=<optimized out>)
    at /usr/include/c++/11/bits/basic_string.h:658
#15 utils::fs::path::~path (this=<optimized out>, this=<optimized out>) at ./utils/fs/path.hpp:55
#16 utils::process::child::fork_files_aux (stdout_file=..., stderr_file=...) at utils/process/child.cpp:273
#17 0x565b2afb in utils::process::child::fork_files<utils::process::executor::detail::run_child<(anonymous namespace)::list_test_cases> > (stderr_file=...,
    stdout_file=..., hook=...) at ./utils/process/child.ipp:56
#18 utils::process::executor::executor_handle::spawn<(anonymous namespace)::list_test_cases> (timeout=..., stderr_target=..., stdout_target=...,
    unprivileged_user=..., hook=..., this=0x56625854) at ./utils/process/executor.ipp:132
#19 engine::scheduler::scheduler_handle::list_tests[abi:cxx11](model::test_program const*, utils::config::tree const&) (this=0xffffcd18,
    test_program=<optimized out>, user_config=...) at engine/scheduler.cpp:1037
#20 0x565b34ba in engine::scheduler::lazy_test_program::test_cases[abi:cxx11]() const (this=0x56628e70) at engine/scheduler.cpp:575
#21 0x565a96cf in engine::scanner::impl::advance (this=<optimized out>) at engine/scanner.cpp:128
#22 0x565aa08f in engine::scanner::yield[abi:cxx11]() (this=0xffffcd30) at engine/scanner.cpp:190
#23 0x5659e2c8 in drivers::run_tests::drive (hooks=..., user_config=..., filters=std::set with 1 element = {...}, store_path=..., build_root=...,
    kyuafile_path=...) at drivers/run_tests.cpp:289
#24 cli::cmd_test::run (this=0x566218e0, ui=0xffffd46c, cmdline=..., user_config=...) at cli/cmd_test.cpp:160
#25 0x56589fab in utils::cmdline::base_command<utils::config::tree>::main (data=..., args=std::vector of length 2, capacity 2 = {...}, ui=0xffffd46c,
    this=0x566218e0) at utils/cmdline/base_command.cpp:114
#26 (anonymous namespace)::run_subcommand (user_config=..., args=std::vector of length 2, capacity 2 = {...}, command=0x566218e0, ui=0xffffd46c)
    at cli/main.cpp:139
#27 (anonymous namespace)::safe_main (ui=<optimized out>, argc=<optimized out>, argv=<optimized out>, mock_command=...) at cli/main.cpp:228
#28 0x5657fe55 in cli::main (mock_command=..., argv=0xffffd694, argc=3, ui=0xffffd46c) at cli/main.cpp:280
#29 cli::main (argc=3, argv=0xffffd694) at cli/main.cpp:353
#30 0x565807f5 in main (argc=3, argv=0xffffd694) at /usr/src/debug/kyua-0.13-7.fc34.i386/main.cpp:49

Was kyua tested on any different distribution with the recent GCC? Do you have any ideas, how to fix this issue? I use kyua to ensure ISC BIND package is good. Unfortunately only my bind build. failed hard and revealed the problem. But would have to turn off unit tests, unless kyua is fixed soon. Any ideas, how to fix this?

Every single test run prints:
*** Please report this problem to<EMAIL_ADDRESS>detailing what you were doing before the crash happened; if possible, include the log file mentioned above
munmap_chunk(): invalid pointer
*** Fatal signal 6 received

Can you reproduce this in valgrind?

Sure, 100% reliable. What options would you like?

Okay, maybe I was wrong. I might be fixed on rawhide already, new kyua rebuild seems to pass tests on all architectures again. Not sure which part was fixed, but it passes on test machine with gcc-c++-11.0.0-0.19.fc35.ppc64le.
It still fails on stacktrace test, but passes fine otherwise on all platforms:
stacktrace_test:dump_stacktrace__cannot_find_core  ->  passed  [0.410s]
stacktrace_test:dump_stacktrace__cannot_find_gdb  ->  passed  [0.828s]
stacktrace_test:dump_stacktrace__gdb_fail  ->  passed  [0.879s]
stacktrace_test:dump_stacktrace__gdb_timeout  ->  passed  [2.140s]
stacktrace_test:dump_stacktrace__integration  ->  failed: Line 391: atf::utils::grep_file("#0", exit_handle.stderr_file().str()) not met  [0.649s]
stacktrace_test:dump_stacktrace__ok  ->  failed: Line 419: atf::utils::grep_file("^frame 1$", exit_handle.stderr_file().str()) not met  [0.689s]
stacktrace_test:dump_stacktrace_if_available__append  ->  failed: Line 559: atf::utils::grep_file("frame 1", exit_handle.stderr_file().str()) not met  [0.699s]
stacktrace_test:dump_stacktrace_if_available__no_coredump  ->  passed  [0.011s]
stacktrace_test:dump_stacktrace_if_available__no_status  ->  passed  [0.110s]
stacktrace_test:find_core__found__long  ->  failed: Core dumped, but no candidates found  [0.729s]
stacktrace_test:find_core__found__short  ->  failed: Core dumped, but no candidates found  [0.701s]
stacktrace_test:find_core__not_found  ->  passed  [0.010s]
stacktrace_test:find_gdb__bogus_value  ->  passed  [0.009s]
stacktrace_test:find_gdb__search_builtin__fail  ->  passed  [0.002s]
stacktrace_test:find_gdb__search_builtin__ok  ->  passed  [0.002s]
stacktrace_test:find_gdb__use_builtin  ->  passed  [0.009s]
stacktrace_test:unlimit_core_size  ->  passed  [0.730s]
stacktrace_test:unlimit_core_size__hard_is_zero  ->  failed: Line 281: !status.coredump() not met  [0.359s]

I think default integration with systemd is responsible:
# cat /proc/sys/kernel/core_pattern
|/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h

Could failing tests be skipped if core_pattern starts with '|'?

@jmmv, could you please rebuild the package on Fedora? I have filled bug #1926779, but no response from any kyua maintainers were received.


#0: Reverting this because it causes PCC issues: Revert "#0: Resolve …

…assert in Roberta E2E test.

This may be unnecessary and unneeded

Don't need, sorry @tt-asaigal