Add cargo:rustc-dynamic-link-search for setting LD_LIBRARY_PATH during cargo run/cargo test

Currently when building we tell cargo where to find static and shared libraries with cargo:rustc-link-search.
However, if you call cargo run or cargo test, while it will still compile, it won't run because LD_LIBRARY_PATH or DYLD_LIBRARY_PATH need to be set. If crates could explicitly emit dylib search paths with cargo:rustc-dynamic-link-search then we could print a list of them at the end of compilation (the same way we do for staticlibs, something like "run this with LD_LIBRARY_PATH=foo:bar:baz"), and if folks use cargo run or cargo test we can run those with this appended to the dynamic lib path

@Manishearth Anything on this?
It does look rather necessary for consistency that a "cargo run" or "cargo test" not crash simply because it has dynamic dependencies, especially after a successful build.
This is problematic when a user cannot, or does not want to put these libraries in the default lib path.
If it remains imperative that the purview of cargo be the target folder, it might be a valid solution for cargo to copy the libs into the target folder.
This however can spell trouble if these libs are too large.

This isn't my decision to make, cc @alexcrichton

I don't really understand the problem nor the proposal here, so I can't really comment much on this.

You may have a build script that builds or pulls in a dylib. For native libraries (static and dynamic), this needs a corresponding -L flag, which gets provided by emitting cargo:rustc-link-search.
This all works fine. You can compile things that build dylibs on the fly.
However, you cannot cargo run or cargo test them since they don't know where to look for the dylib at runtime! I'm proposing a cargo:rustc-dynamic-link-search flag whose output is stored somewhere and picked up by cargo run/cargo test to be used to set  LD_LIBRARY_PATH.

Cargo should already modify the dynamic library search path for anything in the build directory, but if the path is on the system it's up to the user to configure that to be used

Yeah, sorry, this isn't exactly for build script ones, it could be where the build script needs to do some config to search for a dylib on the system.
We've been over this before: https://github.com/rust-lang/cargo/issues/4887#issuecomment-355044354
You suggested opening a feature request for specifically instructing cargo to do this. This is said feature request :smile:

Ah sorry, my mistake! This definitely still stands as a feature request and makes sense to me to implement!

I really want this feature.  My project Rutie depends on a library which I kind of cheat to get to working during its own build.  But when other projects use it the dynamic library is no longer found so cargo test fails.  See comment for more detail: https://github.com/rust-lang/cargo/issues/4044#issuecomment-498508207

Please use DYLD_FALLBACK_LIBRARY instead of DYLD_LIBRARY_PATH. The latter is a hack and almost certain to break things for most people running macOS.
Sent with GitHawk

This would be a very helpful feature for wrapping C libraries that only ship shared objects.
Some scientific computing crates are like this.

The wrapper around the GNU Scientific library https://github.com/GuillaumeGomez/rust-GSL requires the gsl library.

Shameless plug: some Gmsh library bindings I am working on https://github.com/mxxo/gmsh-rs

Especially for users without root access, specifying the directory to find dynamic libraries (e.g. ~/.local/lib) would be really great.

I just came upon the exact same problem in a project that uses ndarray-linalg and thus blas-src. Now our tests failed on CI because it wouldn't dynamically load netlib or openblas, whichever we tried. Adding the library paths manually or installing them in /usr/lib would fix the problem, but the former seems like a bit of a hack and the latter may be a problem for deployment later.

FWIW I found this stackoverflow post that recommends setting "cargo:rustc-env=LD_LIBRARY_PATH from build.rs.
Works for me on cargo 1.49.0 (d00d64df9 2020-12-05).
My use case is building a Rust cdylib that links against another .so in a bigger C project.

FWIW I found this stackoverflow post that recommends setting "cargo:rustc-env=LD_LIBRARY_PATH from build.rs.
Works for me on cargo 1.49.0 (d00d64df9 2020-12-05).
My use case is building a Rust cdylib that links against another .so in a bigger C project.

The errors I'm seeing are similar to
 Running `/Users/christopinka/cvr/di-apps/target/debug/main`
dyld[65298]: Library not loaded: @loader_path/./libdss_capi.dylib
  Referenced from: <8D725B8B-5CBA-3554-89BA-35C671C89773> /Users/christopinka/cvr/di-apps/target/debug/main
  Reason: tried: '/Users/christopinka/cvr/di-apps/target/debug/./libdss_capi.dylib' (no such file<EMAIL_ADDRESS>(no such file), '/Users/christopinka/cvr/di-apps/target/debug/./libdss_capi.dylib' (no such file), '/Users/christopinka/cvr/di-apps/target/debug/build/ring-84bf114a3ada6d54/out/libdss_capi.dylib' (no such file), '/Users/christopinka/cvr/di-apps/target/debug/deps/libdss_capi.dylib' (no such file), '/Users/christopinka/cvr/di-apps/target/debug/libdss_capi.dylib' (no such file), '/Users/christopinka/.rustup/toolchains/nightly-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libdss_capi.dylib' (no such file), '/Users/christopinka/.rustup/toolchains/nightly-aarch64-apple-darwin/lib/libdss_capi.dylib' (no such file), '/Users/christopinka/lib/libdss_capi.dylib' (no such file), '/usr/local/lib/libdss_capi.dylib' (no such file), '/usr/lib/libdss_capi.dylib' (no such file, not in dyld cache)
zsh: abort      cargo run

I'm unclear why the dynamic library doesn't get moved under targets if it's a dependency.

for me on cargo 1.49.0 (d00d64df9 2020-12-05).
My use case is building a Rust cdylib that links against another .so in a bigger C project.

The answer uses an absolute path. I don't think that's a great solution.

Just ran into this issue today while trying to get CUDA libraries running on a non-standard Linux distribution.
It’s weird that cargo run/test replaces the LD_LIBRARY_PATH rather than prepending to it. But we might have to live with that behaviour now.
It seems like a workaround would be a build script with something like:
if let Ok(path) = std::env::var("LD_LIBRARY_PATH") {
    println!("cargo:rustc-env=LD_LIBRARY_PATH={path}");
}


[CARBONDATA-3067] Add check for debug to avoid string concat

For bloomfilter datamap, it will log debug for each blocklet. If the
data is huge, there maybe thousands of blocklet, so in this commit, we
will try to avoid necessary string concat if the debug level is not
enabled.
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/1202/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9466/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1417/

There is some frequent info log in UnsafeSortMemoryManager, can you also add if check for that

I think there is no need to add check for info level logs and the debug level logs in those class already have corresponding check.
I  think current logs in UnsafeSortMemoryManager and UnsafeMemoryManager are OK now. In which part do you think may has problems.

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/1206/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9470/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1421/

In UnsafeMemoryManager:175, there is a info log that requires constructing a string

@jackylk Do you want to change that to debug? Currently it is info level which is not in the scope of this PR since info log may always be logged and that concatenation is unavoidable.

ok. I think we do not need to change it now


FBI 2.X can't physically delete ticket

I tried deleting DevMenu ticket (it's an illegal ticket with CID 00000000 & pre-installed flag) in FBI 2.X's ticket option.
FBI showed the DevMenu ticket properly.
After the deletion, the DevMenu ticket never appeared on FBI's ticket option.
BUT, when I dumped ticket.db and browsed it with GroovyCIA, the DevMenu ticket still existed.
It looked like that it was not a delete but a ticket hiding function - could not be viewed by still recorded inside the database.

The ticket database format isn't fresh in my mind right now; are you sure it isn't just left over data that isn't actually pointed to by the database, and will be overwritten by a new entry later.

+1 for the left over data.
These data will be overwritten by any new CIAs/eShop contents installation.
If you are really worried about these left over data, try to remember the IDs of the tickets you want to delete, then dump your ticket.db, locate the data by ticket IDs and fill them with zeroes/garbages/xorpads/f-words(😏)/etc. using a hex editor, and inject it back
Remember: ALWAYS MAKE BACKUPS!

Closing, then.

Sorry for bringing up this closed issue.  I am a bit confused, how could we know for sure the left over data will be overwritten by new CIAs/eShop contents installation? Any test could we do for that?
Please excuse me if this question sounds too noobish...

dogtopus
Do you mean after "deleting" ticket with FBI 2.X, when you visit e-shop and do some purchase/download things, the "deleted" ticket will be vanished by browsing ticket.db with GroovyCIA?

If no, then your report answers nothing.

DevMenu / Homebrews have unavailable Title ID so they cannot be overwritten.
No matter whether it is the leftover or not, GroovyCIA can detect it, so can Nintendo.

For 1, Overwriting does not depend on title ID
For 2, I don't think Nintendo will do this because it may bring serious security issues (give NAND/raw ticket.db access permissions to userland programs, etc.)

@stebrick I did an experiment earlier.

Thanks for the response!!
So, does it mean that devmenu / homebrews title can still be overwritten by subsequent installation?  And, when it had been overwritten, could it still be detected by GroovyCIA, or is it completely gone?
Thanks so much!

AFAIK yes, and GroovyCIA should not detect them since the data has been completely overwritten

I've just tried to install DevMenu then using Tickets to delete it from there. Dump and decrypt ticket.db and figured out that it's still there. Again, tried to install something from eShop and dump & decrypt ticket.db and it's still there as well....

@thaikhoa Maybe it overwrites something else (like an older empty slot). Did you try to use a binary diff tool to see what was changed in your ticket.db?

I did compare the two. They are completely different which are covered for a whole file.


Python 3.3+ base images missing lzma

Python 3.3 introduces lzma into the standard library, but it is only compiled if lzma is installed in the base image.  See the same issue with the alpine python image from last year here: https://github.com/docker-library/python/issues/86

@jasl8r we've added the missing libs to our python build script https://github.com/resin-io/python-build/commit/0896eb0c85c91c91f6c3b4bbece556d027e44670 and will rebuild all Python binaries. I will let you know once it's done

fixed in https://github.com/resin-io-library/base-images/pull/328


Withdrawl dfi form bsc to dfichain and not comming in

Hello,
i tried to send my dfi address yesterday afternoon via bridge 123.001 defi on from brdfi and they don't arrive.
The hash ID on the BSC chain is:
0x4dad90042739389df857ed82467e1f938cef8b16c831167eb00156e437da8f0e
My Meta Mask address is:
0x7cee45497ff04a7613d5eb86470a4367087d3bcf
My defi address is:
dRP2Qwgaydr6NiD2dLgruE6BRg1ytuJd89
When I started the process via Metamask I confirmed the transaction, see screenshot.

After I confirmed the confirmation via Metamask, the confirmation went to 3/5.
The link to the transaction was displayed and I opened it in a new tab, see screenshot.

I have not closed the confirmation window from the bridge and have not updated it.
After I went back to the confirmation tab, it was at 1/5 again and stopped completely and nothing happened, see screenshot.

However, the hashlink was created on the BSC. However, I have not yet received my defis.
Please check whether my transaction has really gone through via the bridge.
I don't want my defis to be gone now. After all, they were 123.001 DFI.
Many thanks.
BR, Henning

Hi Henning,
I will send you all those coins plus a bug bounty tomorrow! Problem is known and will also be fixed tomorrow!
Thanks for all your help
Sent from my iPhone
On 27 Mar 2022, at 9:53 pm, Hynni @.***> wrote:

Hello,
i tried to send my dfi address yesterday afternoon via bridge 123.001 defi on from brdfi and they don't arrive.
The hash ID on the BSC chain is:
0x4dad90042739389df857ed82467e1f938cef8b16c831167eb00156e437da8f0e
My Meta Mask address is:
0x7cee45497ff04a7613d5eb86470a4367087d3bcf
My defi address is:
dRP2Qwgaydr6NiD2dLgruE6BRg1ytuJd89
When I started the process via Metamask I confirmed the transaction, see screenshot.
[Releasing - Defichain Bridge und 1 weitere Seite - Persönlich – Microsoft Edge 26 03 2022 17_48_55]https://user-images.githubusercontent.com/101993740/160279906-c2e94b21-ab31-4a9c-86db-bf82a1e0cc1c.png
[Releasing - Defichain Bridge und 1 weitere Seite - Persönlich – Microsoft Edge 26 03 2022 17_48_58]https://user-images.githubusercontent.com/101993740/160279888-53d6e3b1-8e23-475c-a23c-964c191402d3.png
[Releasing - Defichain Bridge und 1 weitere Seite - Persönlich – Microsoft Edge 26 03 2022 17_49_07]https://user-images.githubusercontent.com/101993740/160279923-e109a990-85a0-49db-9aae-8bafe887a5af.png
[MetaMask Notification 26 03 2022 17_49_23]https://user-images.githubusercontent.com/101993740/160279931-563924f1-2528-4257-90ec-bb72fa4cd7dd.png
[MetaMask Notification 26 03 2022 17_49_30]https://user-images.githubusercontent.com/101993740/160279938-634c4826-3d60-444d-96b8-6bd3f2ac0c14.png
After I confirmed the confirmation via Metamask, the confirmation went to 3/5.
The link to the transaction was displayed and I opened it in a new tab, see screenshot.
[MetaMask Notification 26 03 2022 17_51_21]https://user-images.githubusercontent.com/101993740/160279944-a9476156-d228-4d4b-b11f-70a0bbd7990d.png
I have not closed the confirmation window from the bridge and have not updated it.
After I went back to the confirmation tab, it was at 1/5 again and stopped completely and nothing happened, see screenshot.
[Binance Transaction Hash (Txhash) Details _ BscScan und 2 weitere Seiten - Persönlich – Microsoft Edge 26 03 2022 17_59_24]https://user-images.githubusercontent.com/101993740/160279950-070d84c8-e221-4a9a-a9de-071e53045fa2.png
However, the hashlink was created on the BSC. However, I have not yet received my defis.
Please check whether my transaction has really gone through via the bridge.
I don't want my defis to be gone now. After all, they were 123.001 DFI.
Many thanks.
BR, Henning
—
Reply to this email directly, view it on GitHubhttps://github.com/muirglacier/bridge-ui/issues/17, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQVPOW4U4G3A2ZO5CXDNHK3VCBK3RANCNFSM5RYVUUWA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Many thanks for your effort.
As soon as the bridge is final, that will be a really big plus for the Defichain :-)
BR, Henning

Hi Henning, I will send you all those coins plus a bug bounty tomorrow! Problem is known and will also be fixed tomorrow! Thanks for all your help
…

Hello,
I wanted to ask when I can expect the DFIs :-)
Have a nice weekend. Best regards
Henning

Hi @muirglacier,
when i entered the trx id in this field. I became following error Message:

How do I get my DFI back now?
Thanks very much.
BR, Henning

Hi, brDFI has been abandoned for the new DFI token when the big update happened. Just sent you the coins from my personal wallet to your defichain address.
Txid: 493b3ba0dc2326d539255a14a7b88c758bffba1fe288f236744f99f354252a05
Thanks for all your input and early testing!
Sent from my iPhone
On 8 May 2022, at 5:42 am, Hynni @.***> wrote:

Hi @muirglacierhttps://github.com/muirglacier,
when i entered the trx id in this field. I became following error Message:
[image]https://user-images.githubusercontent.com/101993740/167269316-980f1958-a2fa-4013-b6c8-76b9b5364ac0.png
How do I get my DFI back now?
Thanks very much.
BR, Henning
—
Reply to this email directly, view it on GitHubhttps://github.com/muirglacier/bridge-ui/issues/17#issuecomment-1120274611, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQVPOW5QTUKRWAHAMESXNSDVI3BSVANCNFSM5RYVUUWA.
You are receiving this because you were mentioned.Message ID: @.***>

Hi @muirglacier,
thank you for allowing me to test the Bridge DFI.
Especially now that the project is live, it brings a lot of innovation to the Crypto Universion around DeFi now and in the future for the new services.
Thank you very much for sending me the DFIs.
I will now remove the brDFI from the account and insert the new DFI Token.
Thank you again for the great project.
BR Henning


Automocking disabled by default but Jest warns about unmocking a manual mock

After upgrading to Jest 15 with all config options set to defaults it gives warning that I'm unmocking a manual mock.
I've got a manual mock for Relay in ___mocks__ and in the integration tests I want to use the real Relay. So I go with:
jest.unmock('react-relay');

import React from 'react'; // eslint-disable-line import/imports-first
import Relay from 'react-relay'; // eslint-disable-line import/imports-first
import TestUtils from 'react-addons-test-utils'; // eslint-disable-line import/imports-first

...

And get the warning which in my view must not be:
 PASS  __tests__/Me-test-int.js
  ● Console

    console.warn node_modules/jest-runtime/build/index.js:647
      jest.unmock('react-relay') was called but automocking is disabled. Remove the unnecessary call to `jest.unmock` or enable automocking for this test via `jest.enableAutomock();`. This warning is likely a result of a default configuration change in Jest 15.

      Release Blog Post: https://facebook.github.io/jest/blog/2016/09/01/jest-15.html

Here's my config
  "jest": {
    "scriptPreprocessor": "jestPreprocessor.js",
    "moduleNameMapper": {
      "^.+\\.(scss|gif)$": "<rootDir>/src/styleMock.js"
    }
  }

Am I misunderstanding something?

In Jest 15, the option automock is set to false by default. If you have a mock of Relay in __mocks__, it will only use that mock in the tests you call jest.mock('react-relay'). See the docs:

When a manual mock exists for a given module, Jest's module system will use that module when explicitly calling jest.mock('moduleNmae').

So, if I understood correctly, you can safely remove that line jest.unmock('react-relay'); since it will already be unmocked.

No. When I remove jest.unmock('react-relay'); I get the exception
 FAIL  __tests__/Me-test-int.js
  ● Test suite failed to run

    TypeError: _reactRelay2.default.DefaultNetworkLayer is not a constructor

      at Object.<anonymous> (__tests__/Me-test-int.js:9:1)
      at handle (node_modules/worker-farm/lib/child/index.js:41:8)
      at process.<anonymous> (node_modules/worker-farm/lib/child/index.js:47:3)
      at emitTwo (events.js:106:13)
      at process.emit (events.js:191:7)
      at process.nextTick (internal/child_process.js:719:12)
      at _combinedTickCallback (internal/process/next_tick.js:67:7)
      at process._tickCallback (internal/process/next_tick.js:98:9)

Which means that Jest is actually using my manual mock.
Basically, this is the reason I created the issue.

Can you explain what you are trying to do a bit better? The example code above, is that from your manual mock? If so, you shouldn't call jest.unmock there but rather const Relay = require.requireActual('Relay').

No, it did not help. Look:
// jest.unmock('react-relay');

import React from 'react'; // eslint-disable-line import/imports-first
const Relay = require.requireActual('react-relay'); // eslint-disable-line import/imports-first
import TestUtils from 'react-addons-test-utils'; // eslint-disable-line import/imports-first

Relay.injectNetworkLayer(
  new Relay.DefaultNetworkLayer('http://localhost:10000/q')
);

...

The output is
> jest "Me"

 FAIL  __tests__/Me-test-int.js
  ● Test suite failed to run

    TypeError: Relay.DefaultNetworkLayer is not a constructor

      at Object.<anonymous> (__tests__/Me-test-int.js:9:26)
      at process._tickCallback (internal/process/next_tick.js:103:7)

Test Summary
 › Ran all tests matching "Me".
 › 1 test suite failed, 0 tests passed (0 total in 1 test suite, run time 3.407s)
npm ERR! Test failed.  See above for more details.

Here's what I am trying to achieve.

My tests combine both unit tests and integration tests. In unit tests of my components there are Relay containers and thus I created the file __mocks__/react-relay.js:

const Relay = require.requireActual('react-relay');

module.exports = {
  QL: Relay.QL,
  Mutation: Relay.Mutation,
  Route: Relay.Route,
  createContainer: (component) => component,
};

So this way my components which have Relay containers can be tested good.

At the same time some of the tests are the integration tests where Relay must not be mocked. But it seems like Jest is always mocking the Relay because of my manual mock albeit the default option for automocking is disabled. So I see two options here:

-- The first one going with jest.unmock('react-relay'); which make Jest warn as I described in the original post.
-- The second one that you suggested const Relay = require.requireActual('react-relay');. But it makes Jest throw as I showed.
Does it make sense?

Can you create a repo with this so I can take a look? I'm not really sure why this is happening and can't give hints without the full setup.

@cpojer yes, sure. Here it is https://github.com/GrigoryPtashko/jest-relay-integration-test.

Ah, this might be a real issue with Jest 15. Can you try, as a workaround, to call:
jest.mock('react-relay', () => require.requireActual('react-relay'))

and let me know if that works?

No, that did not help.
Here's the output.
> jest

 PASS  __tests__/SignIn-test.js
 FAIL  __tests__/Me-test-int.js
  ● Test suite failed to run

    TypeError: _reactRelay2.default.DefaultNetworkLayer is not a constructor

      at Object.<anonymous> (__tests__/Me-test-int.js:9:1)
      at emitTwo (events.js:106:13)
      at process.emit (events.js:191:7)
      at process.nextTick (internal/child_process.js:719:12)
      at _combinedTickCallback (internal/process/next_tick.js:67:7)
      at process._tickCallback (internal/process/next_tick.js:98:9)

Thanks for the repro. I'd recommend for now to call jest.mock('react-relay').unmock('react-relay'). That should be the default in Jest but it seems like this is an actual bug.

Yes, this ways it works.

@cpojer What would be the fix for this bug? I mean, should we start adding manual .mock( even if now they are currently added automatically? Thanks.

Yeah the workaround I mentioned above is still recommended until we change how this works in Jest.

Having this issue as well. Any plans for a fix?

Will be fixed in the next release. #2022


Clarifying sources and type for rebase rules

Hello,
I'm having a hard time understanding the sources and type on rebase rules. I don't think they are clearly documented.

For type: I cannot find any documentation of what this accepts or what it is
For sources is new the values that the cluster has set? existing the values that I already have in my local YAML?

Take the following example:
@@ update mutatingwebhookconfiguration/defaults.webhook.kpack.io (admissionregistration.k8s.io/v1beta1) cluster @@
  ...
  2,  2   metadata:
  3     -   annotations: {}
      3 +   annotations:
      4 +     kapp.k14s.io/original: 'stuff'
      5 +     kapp.k14s.io/original-diff-md5: e053721e8727e53200a8cd368a0681d9
  4,  6     creationTimestamp: "2020-11-16T15:31:49Z"
  5,  7     generation: 37346935

- paths:
  - [metadata, annotations]
  type: copy
  sources: [new, existing]
  resourceMatchers:
  - anyMatcher:
      matchers:
      - apiVersionKindMatcher:
          apiVersion: admissionregistration.k8s.io/v1beta1
          kind: MutatingWebhookConfiguration
          name: defaults.webhook.kpack.io

This rebase does not apply, I'm trying to figure out why this is and how maybe the documentation lead me astray. I'm not entirely sure why this annotation seems to get applied everytime and appear in my diff so I want to ignore it.
If I remove this rule all together I'm stuck with the original problem:
          +   4,  4   metadata:
          +   5     -   annotations: {}
          +   6,  5     creationTimestamp: "2020-11-16T15:31:57Z"
          +   7,  6     labels:

Kapp wants to delete this every time I deploy. This isn't just the case with annotations either, it happens on other types:
- paths:
  - [secrets, {index: 1}, name]
  type: copy
  sources: [existing, new] # tried both combinations here
  resourceMatchers:
  - kindNamespaceNameMatcher:
      kind: ServiceAccount
      name: cc-kpack-registry-service-account
      namespace: cf-workloads-staging

Can never get rid of the following diff after multiple deploys:
@@ update serviceaccount/cc-kpack-registry-service-account (v1) namespace: cf-workloads-staging @@
          +   7,  6     labels:
          +   ...
          +  49, 48   - name: cc-kpack-registry-auth-secret-ver-2
          +  50     - - name: cc-kpack-registry-service-account-token-srmz6
          +  51, 49

I want this secret to stay, it's applied by a controller and gets added back, but kapp does not want to ignore these deletions.

After some discussions with @pivotaljohn we discovered two kapp bugs from this:

https://github.com/vmware-tanzu/carvel-kapp/issues/190
https://github.com/vmware-tanzu/carvel-kapp/issues/191

I would still like to continue this discussion about improving the documentation behind the sources and type

type needs improvement because it is not currently documented
new and existing are poor names in my opinion for the functionality this achieves. existing is used in kapp to imply a change made on the cluster, and new for a change made locally from the manifest you're deploying. This is not clear since just because a resource is adjusted on the cluster does not mean it is existing (implying older) and just because kapp is deploying a manifest does not mean that change is newer than the cluster version. In my opinion these should be renamed to new -> local and existing -> cluster or something to that effect.

existing is used in kapp to imply a change made on the cluster

some reasoning for current naming: neither existing or new refer to changes, they refer to resources. the reason why it's called new is because kapp always takes user input as a new state (aka desired state). existing refers to existing resources in the cluster == these resources are already in operation -- they are existing.

I understand that concept now after wrestling with it. However as you can see in this issue I made the wrong assumption about existing. Could use some clarification. "Existing" resources could still be new if they were created on the cluster by a controller I guess was the way I was seeing it.

This issue is properly named as the need to address the lack of clarity in the docs on these points. 👍🏼

Documentation added in carvel.dev#71.


cannot import name 'feature_dict' from 'features'

i am facing this   problem any body help me plx

The name 'feature_dict' doesn't appear anywhere in setuptools code base. Probably you're trying to install some project and that project has a bug. Contact that project for more information.
Note that setuptools did drop support for "Features" in v46.0, released recently, so it's possible the project you're using is trying to use that.
As reported, there's nothing setuptools can do to help. Good luck.


python auto-formatting does not support editor.formatOnSave for modifications

When having configured editor.formatOnSaveMode=modifications (instead of file) and using autopep8 for formatting, the formatting of python files is screwed up, meaning that indentations are completely lost. Looks like autopep8 cannot handle formatting of small changes only. Is there a better tool supporting that feature?

Duplicate of #14323


Support for pool-allocated committed resources

Allows committed resources (implicit heap) to be reused like we do with placed resources.

Closing, not actively working on.


A few things to document

Some notes as I've started working with Zephyr myself:

We should add some instructions to the readme as to how to deploy this -- the usual stuff: pulumi new, pulumi stack init, set whatever configs are necessary, up, etc., such that someone scanning the README would be able to pick it up and start working with it. Bonus points for a template and Deploy with Pulumi button.
We should explain what to do after the deployment completes. Where can I see the running app? How do I interact with the cluster? Etc.
What's the dev workflow around the app itself? For example, How do I make changes to the web UI, or the infra, and redeploy?
What are the various repo directories for (develop, deploy, etc.)?
We should link to the blog post series from the README as well.

I'm going to go ahead and close this. Everything listed above is documented except for the development workflow and some notes around the develop and deploy folders.


Drop iOS 13

Task/Issue URL: https://app.asana.com/0/414709148257752/1202397540422086/f
Description:
Drop support for iOS 13
Steps to test this PR:
General smoke tests to check if everything is OK.
Special attention to these areas:

Onboarding
Request review on TabViewController
Import bookmarks
Settings screen

Device Testing:

[x] iPhone
[x] iPad

OS Testing:

[x] iOS 13
[x] iOS 14
[x] iOS 15

Hi @Bunn, I've taken an initial pass and it's looking really good 🙂
Just two small comments:

There are a number of iOS 13.4 availability checks that could also be removed as part of this PR
I believe OnboardingHomeRowViewController.swift can be deleted since it's been removed from Onboarding.storyboard

@amddg44 good catch, thank you :)
I've done what you suggested. It would be good to test the two options on onboarding now: Skip and Set as default browser.
I've done it in both iPad and iPhone and it looks good, but a second pair of eyes would be nice.

hi @Bunn, i've done a lot more testing over the weekend and I discovered an issue with bookmark imports. I did a little digging and it seems it is now failing out in the guard let on trying to access the contents of the file in the UIDocumentPickerDelegate [callback] (https://github.com/duckduckgo/iOS/blob/70e33748cf0556605dbb7c6196401acbe81db435/DuckDuckGo/BookmarksViewController.swift#L652)
Otherwise I've thoroughly tested onboarding etc and everything is looking great! 👍 🙂

@amddg44 Good catch, the issue doesn't seem to happen on the simulator because it was a permission thing.
Setting the flag to copy the resource on the picker init makes it work like the previous .import parameter.
Simulator is not the best place to test sandbox things 😅
It should be working now, tested on both iOS 14 and 15 (on real devices)


Support Multi Colors in Negative Area Charts

Summary
Please support different colours for positive and negative area charts like the below.

API Changes
The code should the same as other multi-color charts:
colors: [function({ value, seriesIndex, w }) {
  if (value < 55) {
      return '#7E36AF'
  } else {
      return '#D9534F'
  }
}, function({ value, seriesIndex, w }) {
  if (value < 111) {
      return '#7E36AF'
  } else {
      return '#D9534F'
  }
}]

Intended Use Case
Currently Apex only supports 1 colour for negative area charts. This limits its use as the negative area with the same colour as the positive can be misleading when using the colour as a visual aid.

I need this feature to.

Apparently this issue has been closed, but I'd like to see it revisited. This would be really useful for finance charting.


Support for customer.DefaultAddress, customer.Addresses

At least when we fetch a customer, the addresses can be populated properly.
Later, I plan to submit create/update capability.

Codecov Report

Merging #71 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #71   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          15     15
  Lines         442    442
=====================================
  Hits          442    442

Impacted Files
Coverage Δ

customer.go
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Hey @seenickcode we're going to close this PR. @rickywiens referenced it on the bold-commerce fork here https://github.com/bold-commerce/go-shopify/issues/3, where support for this project will continue. Feel free to open a PR there! Thanks!


NamedStmt with MySQL Datetime error

Hi,
When you have MySQL Query with datetime string:
SELECT * FROM mytable WHERE date="1970-01-01 00:00:00" AND myvar=:variable

It throws error. The : in date is mistaken for named variable.
unexpected `:` while reading named param at ...

Was looking for a solution of using named parameters in a query and found sqlx.
But quickly ran into this issue as well.
When looking at the source code, I found this comment along the compiledNameQuery() function:
// FIXME: this function isn't safe for unicode named params, as a failing test
// can testify.  This is not a regression but a failure of the original code
// as well.  It should be modified to range over runes in a string rather than
// bytes, even though this is less convenient and slower.  Hopefully the
// addition of the prepared NamedStmt (which will only do this once) will make
// up for the slightly slower ad-hoc NamedExec/NamedQuery.

https://github.com/jmoiron/sqlx/blob/master/named.go#L230-L235
Is this "prepared NamedStmt" something in the works? Where can I find more information?
Or are there other solution that I should know about?


#50 add platform to docker-compose

Sorry, I'm not an expert in this field. May I ask if running it on an ARM architecture device will solve the problem ?

Sorry, I'm not an expert in this field. May I ask if running it on an ARM architecture device will solve the problem ?

On M1 MacBook Pro, I've had success using docker run --platform linux/amd64
But in Docker Hub(https://hub.docker.com/r/wongsaang/chatgpt-ui-client/tags) you provide only linux/amd64
You as the owner can build and push images for other platform.
You should have the docker buildx installed.
If you don't have the docker-desktop you can download the binary buildx from github: https://github.com/docker/buildx/
Build the image by passing the list of architecture
Try this:
docker buildx build --platform linux/amd64,linux/arm64,linux/arm/v7 -t wongsaang/chatgpt-ui-client:latest --push .

Thank you so much!


Added npqQualifications section to v3 API + associated tests and docs

Context
NPQ qualification details needed in API for new qualifications UI
Changes proposed in this pull request
npqQualifications section added to v3 API.
Guidance to review
v3 API code change + dataverse adapter + tests + docs
Checklist

[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

 Add NPQ qualifications for v3 API


Replace require with import

There is a problem: one cannot build a rn app with expo using maplibre-gl-native, because expo uses metro bundler, which does not support dynamic require.
Please replace require with import!

It's not clear to me what platform you are running React Native on.
In any case, please open an issue over at https://github.com/maplibre/maplibre-react-native if you have an issue with React Native.


add support for Remote Development and GitHub Codespaces

Resolves #262 by making the extension run where the workspace is located.

I was thinking, too bad this isn't a setting. Personally, I'd rather want nvim to run on my local machine, because I have config/plugins/etc that work regardless of remote desktop. However, if you only work with a remote desktop, I see the appeal of having nvim run on the remote.
Maybe we should keep default behavior, but add to the readme how you can override the setting so that  you can run nvim on the remote?

I totally agree.

What is the status of this? Looks like it's just awaiting a review before it can be merged.

Possibly this would fix #225.

This should not be merged, because it disables the behaviour people expect (nvim runs on local machine). You can apply the effect of this PR using your settings.

Ok, it seemed like something like that might be the case. But I'm still confused which settings I need to modify.

Ok, it seemed like something like that might be the case. But I'm still confused which settings I need to modify.

https://github.com/vscode-neovim/vscode-neovim/issues/262#issuecomment-1208062772

It's working!

Ok, it seemed like something like that might be the case. But I'm still confused which settings I need to modify.

#262 (comment)
This part did it from a settings.json file, thanks!:

"remote.extensionKind": {
    "asvetliakov.vscode-neovim": ["workspace"]
}

Actually I think this pull request might still be a good candidate to be merged. For one thing, it doesn't prevent this extension from using a local Neovim in the case where everything was local to begin with, as you were not using the remote extensions.
Additionally, if I'm not mistaken, this change would only make it possible, but not required to install this plugin on the remote instance. The reason I am saying this is, even with the change I made to my settings, I still needed to use a little blue button in the VS Code Extensions UI to actually install it on the remote machine. Of course it would be good to test this before merging, but it might still be possible to install and use this extension locally instead, even with this change, even while using the remote extensions.
If that is the case, it seems like a great idea as part of the reasons people want to use the remote extensions is so they can install and run their other VS Code extensions on the remote machine. It's not just about accessing remote files you want to edit.

This PR needs a clear Problem/Solution statement. vscode-neovim already works with vscode remote, so the title is very misleading.
From what I can gather, is this the use-case being solved here https://github.com/vscode-neovim/vscode-neovim/issues/262#issuecomment-1208062772 :

so i no longer need to install Neovim locally.

vscode-neovim already works with vscode remote

Technically you can get it to work, but you have to know about an obscure and strange setting you need to change to get it working. You have to edit this setting by hand as well, it's not editable through the menu. I went all these years believing I can't use VS Code with a remote Neovim in this way because of this shortcoming.
My understanding, which could be wrong, is that if this were merged, it would simply make it possible to install this extension on a remote machine, through the GUI using the extensions panel on the side, without having to change any settings. I don't think it would ever break using a local Neovim, you would simply install the extension on your local machine and not the remote one.
I'm not aware of any use case that would work worse with this merged, but then again I don't understand all the ramifications of changing the "extensionKind" from "ui" and "workspace" to just "workspace".

Technically you can get it to work, but you have to know about an obscure and strange setting you need to change.

I think it depends on what "remote" means. So part of the Probem/Solution statement for this PR, needs to say exactly what steps this applies to.
I didn't have to set a strange setting, here's my vscode config: https://github.com/justinmk/config/blob/master/Library/Application Support/Code/User/settings.json
I use vscode remote-ssh https://code.visualstudio.com/docs/remote/ssh and it just works.

I use vscode remote-ssh https://code.visualstudio.com/docs/remote/ssh and it just works.

I wonder if you might have an additional settings.json file somewhere with this override setting:
"remote.extensionKind": {
    "asvetliakov.vscode-neovim": ["workspace"]
}

Perhaps it is in the settings.json file that is on and for the remote machine (mine is on the remote machine at ~/.vscode-server/data/Machine/settings.json), or perhaps the workspace settings.json that can be in the workspace on the remote machine?

I think I jumped in here and started commenting without explaining what I was trying to achieve. I apologize for that. I'm trying to connect this extension to the installation of Neovim on the remote machine. If the Neovim being used by this extension does not have access to the environment where the code lives, it will be extremely crippled.

If the Neovim being used by this extension does not have access to the environment where the code lives, it will be extremely crippled.

Can you give an example? Remember that the neovim instance is not aware of the file location/cwd/project, it is just provided a scratch buffer with the editor contents.

Can you give an example? Remember that the neovim instance is not aware of the file location/cwd/project, it is just provided a scratch buffer with the editor contents.

I guess currently I can't come up with any great use cases for running Neovim remotely in this way. I was hoping it would unlock the full power of Neovim, but I am able to run Neovim remotely like this from this extension with the right settings, and it is currently not making what I want to do possible anyways. So it seems like a great topic of conversation to explain what I want to do in more detail, but until those use cases are supported, I don't think merging this PR will help anyone.
I was hoping to have the option of either doing things the VS Code way, or the Neovim way or both. I would like to be able to use a Neovim file tree plugin and use that instead of the built in VS Code file explorer. I would like to be able to use things like fzf through a Neovim plugin. Each person's reason for wanting to integrate Neovim into VS Code will be different. In my case I am almost completely happy with Neovim by itself, I just can't seem to configure the LSP and LSP based auto complete to work the way I want, even after years of trying. But that part works great in VS Code.
I also really want to be able to use an Vim plugin I made that greatly enhances my productivity. One way it can be used is while the cursor is over a particular word, you can press * to search for that word in the contents of all the files matching the same file type you have open. This opens a new window and places the search results in that window. It shows the path to the file, the line number it appears on, and the contents on that line.  Then you can use vim regex search within that window and buffer to search more specifically for what you want from there using the forward slash key the normal Vim way. This buffer is intentionally editable. You can edit it in any way you want. This is very useful because you can delete lines that are not relevant to what you were searching for, or that were relevant, but now you are done dealing with it and want it to disappear from the list. You can also press gF while the cursor is over a file from a search result line to go to that exact file and line number in the window above without the search result window disappearing. You can also edit the line contents directly in the search result window and any time you save from this buffer/window, it will modify that line in that file to match the contents you have there. So you can search for something, edit all or some of the results right there, and then save them all at once or discard the changes by closing the window without saving. I think of it like extradimensional editing. It is the perfect example of how modal editing is useful not only for editing a particular file, but also as a way of controlling the editor itself. It also illustrates the power of being able to make your own plugins and gives you a feel for why someone would not want to give up this power within Neovim even when trying to integrate it into something like VS Code.

I would like to be able to use a Neovim file tree plugin and use that instead of the built in VS Code file explorer.

This will never be possible, because there isn't the ability to render arbitrary elements in VSCode. There are very specific and limited APIs for working with VSCode elements like quickpick, editor, etc. Only option is webviews or custom explorer filesystem provider (still using vscode ui).

I would like to be able to use things like fzf through a Neovim plugin.

Not possible for same reasons.

you can press * to search for that word in the contents of all the files matching the same file type you have open.

This is possible, but would need to be implemented 100% on the vscode side.

You can also press gF while the cursor is over a file from a search result line to go to that exact file and line number in the window above without the search result window disappearing

Again, possible on the vscode side if the search results provides a "go to definition" implementation.
You can never turn VSCode UI into something modal, because of the limitations of the API.

So really this has all the same limitations all the other IDE Vim emulators have. It's just more accurate since it is not an emulator.

Correct, and it supports many useful nvim plugins that augment motions & textobj, lua config, etc.

I would like to be able to use a Neovim file tree plugin and use that instead of the built in VS Code file explorer.

This will never be possible, because there isn't the ability to render arbitrary elements in VSCode.

Neovim file tree plugin is just a buffer, so this should be possible by showing such a buffer in a vscode editor tab.

@still-dreaming-1 Have you investigated the built-in features of VSCode? Have you forgotten about the extension marketplace of VSCode? If you are unsatisfied with only a portion of nvim's lsp functionality, why not work on improving nvim-lsp?
Many people switch from nvim to VSCode and find it different and not as user-friendly. They raise various needs and requirements but are unwilling to spend some time learning the features of VSCode.

I would like to be able to use a Neovim file tree plugin and use that instead of the built in VS Code file explorer

Can you list some features you are not satisfied with? VSCode's file explorer supports Git and diagnostic decorations, and all the operations can be customized with shortcuts. The primary requirement for most people is simply shortcuts, but thanks to the flexible shortcut design of VSCode, all shortcuts can be configured just like the common file tree plugins in nvim.

search

Have you tried using these for your search needs?

Here is my relevant configuration.
map <silent> /         <Cmd>call VSCodeCall('actions.find')<CR>
map <silent> <space>/  <Cmd>call VSCodeCall('actions.find')<CR>
map <silent> <space>fw <Cmd>call VSCodeCall('workbench.action.quickOpen', '% '.expand('<cword>'))<CR>
map <silent> <space>fb <Cmd>call VSCodeCall('workbench.action.quickOpen', 'edt active ')<CR>
map <silent> <space>fo <Cmd>call VSCodeCall('workbench.action.quickOpen', '@')<CR>
map <silent> <space>fd <Cmd>call VSCodeCall('workbench.action.quickOpen', 'debug ')<CR>
map <silent> <space>fr <Cmd>call VSCodeCall('workbench.action.quickOpen', 'task ')<CR> " run
map <silent> <space>ft <Cmd>call VSCodeCall('workbench.action.quickOpen', 'term ')<CR>

PR as-is isn't mergable and hasn't addressed https://github.com/vscode-neovim/vscode-neovim/pull/1000#issuecomment-1424052985

I kept this open as a reminder to add related documentation on how to run the ext remotely to the README


See:

May be you can check whether the page stays inside the .next directory. I think with that, we don't need these kind of extra logic.
(We may already have working logic for that)

Added the console.error for those throws.

@timneutkens Man, thank you!

Logic was improved here: https://github.com/zeit/next.js/pull/3976


Multiple socket.ids generated

This code is not working alrite....multiple socket.ids generated from the same tab. So sometimes client connects to himself or others connect to non existing client.

Socket.id identifies the connection, not the client or the session. If you are being assigned multiple ids, it is because you are connecting multiple times.

Please see the documentation here: https://socket.io/docs/v3/client-socket-instance/

Please see the documentation here: https://socket.io/docs/v3/client-socket-instance/

hello
I have some challenges
Socket.io is generating its ID multiple times


Rescan button does not work

When I try to do a rescan, the rescan completes instantly without doing anything. Seems to be because I already ran it once this session.
edit, actually rescan is not working at all on the latest version.

The rescan starts from the last block height it stopped.
The rescan in the settings starts from 0.

fixed in https://github.com/raedahgroup/dcrandroid/commit/0f58875945e6663429a9f06854de38017caf3fb3


Use of client's crt/key pair to launch a cluster memeber

Hello ETCd team,
I've got a security question for you.
Assuming that we have a TLS enabled cluster with N members.
Both --peer-client-cert-auth and --client-cert-auth are enabled as well.
Given that one gains access to a client's TLS crt/key pair, will he/she be able to launch a cluster member ETCd instance using the client's TLS crt/key pair and it will successfully join the cluster?
I've read through #8262, which is great, but currently I have to run two CAs, one will generate ETCd cluster peers' crt/key-s and the second will generate clients' crt/key-pairs (k8s, applications and such.)
The issue is not clear on the TLS page.
I will be able to test it in a couple of days, but until then, if anyone can comment or share experience, that would be great 👍
Best,
Yarden

@ayashjorden Are you asking if the cert/key pairs used for "client-to-server" communication can also be used for "server-to-server / cluster" communication? My reading of the TLS page is that they are separate. What did you find unclear about the page?

Hi @jpbetz,
My reading of the TLS page is that I can use two crt/key pairs in the cluster-member configuration. One for server-to-server and one for client-to-server. but it does not explain how cluster members are controlled.
Given that I have one CA that issues certificates for cluster-members and clients(with CN or SAN), What prevents me from using a client-to-server crt/key pair for server-to-server / cluster communication?
Is there some RBAC for cluster members?

will he/she be able to launch a cluster member ETCd instance using the client's TLS crt/key pair and it will successfully join the cluster?

Only if your server certs have matching hosts (either exact match or wildcard matching).
DNS SAN wildcard reverse lookup is only available from etcd v3.2.5.

That would be a nice experiment
As @Ulexus mentioned in this thread, the best practice for preventing interloop cluster members is multiple CAs. one for server-to-server and another for client-to-server.
Any comments/ideas?

Also note that the PKI for the members is only used between members, so it's much easier (better?) to use a private, unaffiliated, unregistered, undistributed CA for the peering system.
I believe your basic assumption about the system, though, is correct.  The only present authorization available for members is the CA test, so if the client key is compromised and the clients and members share the same CA, cluster membership is at risk.
However, if your client keys are compromised, you're really at the mercy of any number of problems anyway.  A client could change any data in the database.  A client could change the membership such that quorum is lost.  A client could add members which bypass non-source-discriminatory firwalls.
Basically, then, if you can't trust your clients, you really need to use role-based access control on the client side.  No amount of PKI wrangling will protect your cluster if your clients are compromised.

@Ulexus, to clarify, by

you really ned to use RBAC on the client side

you mean the ETCd RBAC system on the KeySpace?

The root roles provide access to the cluster membership controls, from what I understand, yes.  In etcdv2, the membership data was stored inside the key space like everything else.  I presume (but have not verified) that this is still true for etcdv3.
If the vulnerability you are trying to address is a compromised client keyset (and, one presumes, any authentication thereof), then keeping your operational clients constrained within restricted roles seems to be the surest answer.

Thank you all for the valuable info and insights.
Is there any way I can help to get this information to the community in a more visible way than a Github issue?

We have auth doc https://github.com/coreos/etcd/blob/master/Documentation/op-guide/authentication.md. And https://github.com/coreos/etcd/blob/master/Documentation/op-guide/security.md. If you find anything missing, please let us know. Thanks!

@gyuho,
The two links provided does not describe what what discussed in this ticket about best-practices for authorization of cluster-members vs. cluster-clients.


Added Snapd connectivity check.

thanks for the patch brett, can you please add a unit test

It's been several months since this patch had an update so ill go ahead and close the PR. Please feel free to re-open it if you have further updates.


Added External ID to AdvancedMatching interface

Added external_id based on the documentation.

Hi @Joeao, are you planning on merging this feature any time soon ?
It's great one and needed indeed!
If so I even offer my help to make it quick.
My offer is here :D

@dan003400

It's not up to me to merge it as this isn't my repo. Hoping for it to be merged though.


Add month picker option to mode

Fixes #119.
My approach for this was not to give a preset day, but to set the existing mode prop to month, rather than date or time.
It will never modify the day portion of whatever was given for dateTime. I.e., by default the day will always be today's day of month, or if you initialise the component with dateTime="2015-01-01", then the selected date will always be the first day of whatever month the user picks.

Please don't update version or include the built files, I do that during the publishing process where I sometimes bundle a few PR on the same update

@chollier I've removed that commit. Should just be src/test/readme changes now :)

Thanks for the feature, it's very useful
Is there a way to disable the months when we set minDate and maxDate properties?

Hello! I wanna use this feature too but it appears it's not supported yet? Or there's a problem with my implementation. I'm using version "0.0.22".
When I tried to use:
<DateTimeField    mode="month"   />
it renders this error:

@arjuneyy This PR has not been merged yet, so there is no chance it will work even with the latest release. So you'll need to fork this code if you want to use this feature!! :)

@michelre I'm kinda new to this one. What do I need to do next after I forked it? :)

@arjuneyy git fetch origin pull/133/head:month-picker . This will create a month-picker branch that contains the code of this PR
There is another way to use this PR through npm: npm install https://github.com/quri/react-bootstrap-datetimepicker.git#pull/133/head --save

@michelre Here I am again :D Sorry for the trouble. Really.
I did as what you told, and this installed in my node_modules:

And when I use it, I got this error:
Error: Cannot find module 'react-bootstrap-datetimepicker
What I notice in the latest version is that it has a lib folder, and what I pulled does not have.

I tried to copy that lib folder, and it starts working again. But I still cannot use the mode="month"  feature.
Any idea? :) Thanks @michelre and sorry for the trouble :)

@arjuneyy Oh, yeah, that's right. I see what's going on. In fact, the lib folder isn't pushed to the repository and it's construct through the npm run build-npm command. I actually made a pull request a few time ago. You can use my code: npm install https://github.com/michelre/react-bootstrap-datetimepicker.git#staging --save. In this case, I remove the lib/ folder from the .gitignore, so it is available! :)

@michelre Thank you really for your help :) I managed to install including the lib folder containing the components. Though I have some issues regarding the css files not working, but I'll look into it. Thanks :)


lang: [nl] add Dutch translation

@NotCoffee418 Thank you for PR,
Can you run the following command to fix the code style error?
composer cs-fix

   1) tests/Language/AbstractTranslationTestCase.php (unary_operator_spaces, not_operator_with_successor_space, binary_operator_spaces)
      ---------- begin diff ----------
--- /home/runner/work/shield/shield/tests/Language/AbstractTranslationTestCase.php
+++ /home/runner/work/shield/shield/tests/Language/AbstractTranslationTestCase.php
@@ -63,7 +63,7 @@
         LithuanianTranslationTest::class => 'lt',
         //        LatvianTranslationTest::class            => 'lv',
         //        MalayalamTranslationTest::class          => 'ml',
-        DutchTranslationTest::class              => 'nl',
+        DutchTranslationTest::class => 'nl',
         //        NorwegianTranslationTest::class          => 'no',
         //        PolishTranslationTest::class             => 'pl',
         PortugueseTranslationTest::class => 'pt',

      ----------- end diff -----------

@NotCoffee418 thanks!


Native SPM Support

Supporting Swift package manager would be very cool :)

Done, check version 5.6.0


Parsing Transactions into dictionaries

Add support for Transactions on the Dictionary encoders.

Transactions are now parsed into dictionaries as part of the Group to dictionary parsing.


updated apiary docs

Fixed various typos throughout and made some changes to "Create a Classification" section. Please review that carefully before accepting.

Thanks a bunch!

np. I got to say though, git is a bit tricky to work with!

Thanks @alianos- . I found this book really useful, http://git-scm.com/book/en/v2


Added new owner to Azure Networking

added number213 to Az NW
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-go

Automation for azure-sdk-for-python

@sergey-shandar  can you please help to merge this improvement

Can one of the admins verify this patch?


CollectionView shows up as empty

I tried to check if the common problems in the solved issues section were present before posting. I have the correct module, I have set label and container view constraints, I have set the ibCalendarDateSource/Delegate outlets, set the class of my storyboard scene = file class of CalendarViewController, but my collection is still showing up as empty
I'm hoping you can help me figure out why.
Here is my project zip
Gutka 2.zip

hey patchthecode, is my post showing up? This is my first time posting in github issues and I'm worried I didn't post this right or its showing up as private.

ah sorry.
i mentally responded to you 😂
Will take a look after work. Sorry about that.

As soon as i ran your app, the firsst error message i sae on the console was
2018-07-09 19:29:45.297106-0700 Gutka[20617:9585642] Unknown class CalendarViewController in Interface Builder file.

closing this issue.

Thanks. I looked at the Build Phase - Compile sources and I see all of my .swift files including CalendarViewController.swift ... but that message still shows up... was that not the issue?

np. have a good one.


⚠ Bofrost.fr has degraded performance

In 700f167, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1075 ms

Resolved: Bofrost.fr performance has improved in 205669e after 6 minutes.


Share dataset of Tweets about the novel coronavirus.

I am currently in the process of using NASTY to retrieve all Tweets about the ongoing coronavirus. As presumably, many others are also doing so, in my view it is best to concentrate crawling efforts in one location and then share the results publicly.
Therefore, I here document my current methodology and am open to suggestions/criticism:

The main goal is finding as many on-topic Tweets (i.e., talking about the novel coronavirus) as possible while including as few off-topic Tweets as is achievable. That means striking a sensible balance between precision and recall.
To this end, search requests are used to find Tweets containing at least one of the keywords corona, coronavirus, covid, covid19, ncov, sars, wuhan that were authored after 1 Dec 2019 in either English or German.

For this I am issuing search requests per day (using the nasty search --daily feature), i.e., a single search request would be with query corona, time range from 1 Dec 2019 to 2 Dec 2019 using both the TOP and LATEST --filters. The next request for the following day and so on. Based on initial experiments this seems to yield more results and can easily be expanded on later, but more investigation on Twitter's search algorithm would be useful here.
This will result in some off-topic matches (for example, corona beer), but these should be negligible, as the assumption is that there have been many more on-topic in the recent times (starting mid January).
The December 2019 time span is included as a short period before the outbreak of the coronavirus to have a baseline of Tweet frequencies that are off-topic.
I assume that most people reading this are only interested in the English Tweets, but since I am retrieving German Tweets for a personal research project, I will include these anyways. Tweets will be separated by language, so non-English ones can easily be filtered out.

Additional ways to retrieve on-topic Tweets would be to either manually identify a number of Twitter users that mostly tweet about corona (we can't just follow anyone that has tweeted about corona at one point in time as that presumably leads to a huge precision loss) or to retrieve replies to a known on-topic Tweet (e.g., any Tweet matching the above search criteria). However, both were deemed to cost expensive for now.
One thing I may do in the future, is looking up influential hash tags for each week (e.g. #masks4all) and add search requests for these.

So far, I have crawled about 68.5 million English and 2.2 million German Tweets in the time span from 1 Dec 2019 to 5 Apr 2020 (about 34 GB compressed JSON with meta data). I plan to contentiously expand this collection for the upcoming months. I am note quite sure when I'm ready to share this and how I will do so (probably using NASTY's idify feature).
If you are interested in this dataset, please leave a comment here. Preferably also leave a very short summary of what you plan to do with it and what you think of the outlined methodology.

We are interested in the dataset of Tweets about the novel coronavirus. The dataset seems useful, it is very important that you have tried striking a sensible balance between precision and recall. We are working on tackling the challenge of misinformation and we would like to use the dataset in our investigation. The lack of annotated data is a vital challenge in our research. However, the Tweets might be used as weak labels and an analysis of them can lead us to important conclusions about how coronavirus misinformation spread. Could you please give us more information about when you will be ready to share the dataset and what format the tweets will have?

I have finally found the time to publish the Tweets I have retrieved up until now: https://github.com/lschmelzeisen/nasty-ncov-tweets
I realize that in the meanwhile quite a few other datasets have been released, but this one might still be interesting to you. I will look to expand it in the near future.
Let me know if you have any questions.


Population is broken

After a few loops population drops to one and does not grow anymore. This breaks everything else.

This is probably will's fault


Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.

So, you're experiencing a problem?
If you're not sure how to use the lightbox, or are experiencing a problem with it, please ask on StackOverflow - you will most definitely get a faster response time and it leaves this GitHub issues for actual bugs and not support questions.
If you really do think you have a bug, please:

[ ] Provide a link to your site or a full example
[ ] Provide screenshots where appropriate
[ check] Browser name and version

Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
When using the data-remote attribute.

This is a jquery issue, not the lightbox.
Also, next time please include the requested information


docs: fixed Typo & Grammar in README.md

Partly fixes #178
Typo & Grammar  in README.md

Thanks for your contribution ! Really appreciated it !


fixed double messages being received

Fixed issue where two chat messages were being received.
Issue was being caused by using ChatCtrl twice and each using chatManager. When this happened, event listeners were being registered twice, which caused each callback to happen twice as well. The fix was to create a new controller just for the userlist directive, and make sure each socket event was listened to only once.

Also simplified chat and media socket services


Bot sometimes runs two instances.

Known bug since release v0.0.1-beta, if the bot is running in the background (under another process), it will run twice due to how node.js runs and will not expose the client unless it's under a webserver. This can cause security issues none of the less. As of now, the only way to have the panel/bot work at the same time is to make sure that the panel starts the process for the bot, not the user.
Issue corresponds with https://github.com/Solixity/DiscordBotPanel/commit/ca14f49a4ee14f6a11d7e5ec3fb78b8440d4b2b5.

So I've figured this out, I decided to create a local webserver. It'll be available in https://github.com/Solixity/DBP-NodeJS.


”Domașnea” is listed in the drop-down menu

Description:
"Domașnea" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Domașnea" in the search bar.

Expected results
The location is listed in the drop-down menu as "Domașnea, Caraș-Severin".


Tests are failing due to OpenGL installation in test_and_deploy.yaml

I'm not sure whether this installation is necessary for packages that do not rely on GPU-functionality. I'll start a PR to see if tests still pass after removing this part from test_and_deploy.yaml.

Napari needs OpenGL
Consider replacing "git" in this line with "https":
https://github.com/BiAPoL/napari-crop/blob/main/.github/workflows/test_and_deploy.yml#L49
See also:
https://github.com/napari/cookiecutter-napari-plugin/pull/104

Ugh, it's that one. Thanks for pointing it out!

Hm...I changed the actions so that they don't rely on the OpenGL installation anymore, but rather install conda. Also, tests now run with pytest directly rather than tox.
I think the error in the github actions is the same one I recently saw in napari stress. There, removing Python 3.7 from the list of supported Python versions solved the problem.
Of course not really the problem, but only the symptoms.


Purge ServiceRegistry

Remove the NewServiceRegistry contructor that returned a *config.Store
rename all isntances of serviceRegistry to configStore, combining
instances where there were both in the same scope

:+1:


Create a new cli option to validate entities.

Something like appgate-operator validate --directory entities for instance.
Then that command could be run as  part of the CI in a PR so the entities could be validated before merging.

https://github.com/appgate/sdp-operator/pull/97


Does not work on latest Ubuntu Server

Please tick all applicable boxes.

[ ] I am using Python 3.5.3 or higher (run python --version on the command line)
[x] I have followed the official guides to install the bot for my system
[ ] I have updated my dependencies to the latest version using the appropriate update script

Which version are you using?

[x] The latest master version (release-260419)
[ ] The latest review version

What type of issue are you creating?

[x] Bug
[ ] Feature request
[ ] Question

Description of issue
Doesn't work on Ubuntu 20.04
Steps to reproduce

Follow the latest Ubuntu steps on Ubuntu 20.04

Log file
Please attach your MusicBot log file (located at logs/musicbot.log) to this issue. You can do so by dragging and dropping the file here. If you do not include your log file, you WILL be asked to provide one.
[12.048006058] 2020-06-10 23:51:32,734 - INFO - launcher: Starting sanity checks
[12.399673462] 2020-06-10 23:51:32,735 - INFO - launcher: Checking for Python 3.5+
[12.594938278] 2020-06-10 23:51:32,735 - INFO - launcher: Checking console encoding
[12.753009796] 2020-06-10 23:51:32,735 - INFO - launcher: Ensuring we're in the right environment
[171.368837357] 2020-06-10 23:51:32,894 - INFO - launcher: Required checks passed.
[171.739816666] 2020-06-10 23:51:32,894 - INFO - launcher: Optional checks passed.
[171.929359436] 2020-06-10 23:51:32,894 - INFO - launcher: Moving old musicbot log
######################### PRE-RUN SANITY CHECKS PASSED #########################

Hi! This hasn't got anything to do with your ubuntu 20.04 server as it works fine on other ubuntu 20.04 systems. Instead the problem is probably caused by a misconfiguration. More info is needed to understand why your bot doesn't run.

could you give some more info as @Jeroeni said?

Closing due to inactivity

Closing due to inactivity


docs: improve DecoratorNode docs

Add description for DecoratorNode.prototype.decorate method, add description to the docs website "Extending DecoratorNode" section.

This is good, thanks. One small typo that actually muddles the semantics. Otherwise, good to go.


Created ssh_config Has Container's Path for the Identity File

The create ssh_config has the container's path for the Identity File. e.g. /root/.ssh/id_rsa.
Fine if you run from another container with the same mount points.
Won't work from your laptop directly (which is probably the more useful case)...
e.g. should be $HOME/.ssh/id_rsa

That is... IF you brought up the system via a container in the first place.

https://github.com/samsung-cnct/k2/issues/69 is the dupe.  its a limitation of building the ssh config inside the container.  the container doesn't have any knowledge of the host system layout.
k2cli will perform the replacement for you, you can do it by hand or specify the ssh key manually.  or we could add an ssh client to the k2 image and have you run a docker container to ssh over.  that seems a bit odd to me though.


Fixed changelog formatting issue

What does this PR do?
Title and diff says it all

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-12-07T12:41:33.681+0000

Duration: 4 min 46 sec

:grey_exclamation: Flaky test report
No test was executed to be analysed.
:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run benchmark tests : Run the benchmark tests.

run jdk compatibility tests : Run the JDK Compatibility tests.

run integration tests : Run the Agent Integration tests.

run end-to-end tests : Run the APM-ITs.

run windows tests : Build & tests on windows.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)


Up MPD to 1.0.4

RE-CHECK!

Automated adapter checker
ioBroker.mpd

:thumbsup: No errors found
Add comment "RE-CHECK!" to start check anew


Handle private container registry while downloading blobs

Added registry to the image reference while downloading.
Signed-off-by: adarsh-zededa<EMAIL_ADDRESS>

Good to get our heads around the requirements @eriknordmark .
PullBlob() is supposed to get anything that is provided, with or without a hash. It is the equivalent of docker pull <ref>. But it also supports explicitly passing a hash, whether it is provided in the <ref> or not. So it should be able to handle all of the standard use cases:

nginx@sha256:1234
nginx:latest@sha256:1234
nginx:latest

Plus it needs to be able to handle passing the hash separately.
Here are your use cases:

repo = "nginx@sha256:1234" + hash = ""

As you said, "the code will do the right thing."

repo = "nginx@sha256:1234" + hash = "sha256:1234"

It should handle it, although it probably should be cross-referencing them to ensure they are the same.

repo = "nginx:latest" + hash = "sha256:1234"
repo = "nginx" + hash = "sha256:1234"

Yes. These two are the same. As soon as you use a hash, the tag is ignored.

repo = anything + hash = "sha256:" (i.e. invalid hash)

Yes, but it should reject it. And it does, if we append the hash, since this will return an error:
	ref, err := name.ParseReference(image)
	if err != nil {
		return 0, fmt.Errorf("parsing reference %q: %v", image, err)
	}

repo = "nginx:latest" + hash = "sha256:1234"
repo = "nginx" + hash = "sha256:1234"

Yes. These two are the same. As soon as you use a hash, the tag is ignored.

I don't know what the underlying package supports; but I suspect need to remove any tag when we add the sha at the end

I don't know what the underlying package supports; but I suspect need to remove any tag when we add the sha at the end

We shouldn't need to, as this is what parses it all:
	ref, err := name.ParseReference(image)
	if err != nil {
		return 0, fmt.Errorf("parsing reference %q: %v", image, err)
	}

And should do the right thing.
I whipped up a little program to test it:
package main

import (
	"fmt"

	"github.com/google/go-containerregistry/pkg/name"
)

func main() {
	names := [][]string{
		{"nginx:abc", "valid tag, no hash"},
		{"nginx:abc@sha256:c7e7c316f879aa68e98165cfe8252e5b2c3540f4a527949eb1eb34e96afbd46d", "valid tag, valid hash"},
		{"nginx:abc@sha256:abcd", "valid tag, invalid hash"},
		{"nginx:abc@sha256:", "valid tag, start of hash"},
		{"nginx", "no tag, no hash"},
		{"nginx@sha256:c7e7c316f879aa68e98165cfe8252e5b2c3540f4a527949eb1eb34e96afbd46d", "no tag, valid hash"},
		{"nginx@sha256:abcd", "no tag, invalid hash"},
		{"nginx@sha256:", "no tag, start of hash"},
	}
	for _, image := range names {
		ref, err := name.ParseReference(image[0])
		fmt.Printf("'%s' '%s' %#v '%v'\n", image[0], image[1], ref, err)
	}
}

And the output:
'nginx:abc' 'valid tag, no hash' name.Tag{Repository:name.Repository{Registry:name.Registry{insecure:false, registry:""}, repository:"nginx"}, tag:"abc", original:"nginx:abc"} '<nil>'
'nginx:abc@sha256:c7e7c316f879aa68e98165cfe8252e5b2c3540f4a527949eb1eb34e96afbd46d' 'valid tag, valid hash' name.Digest{Repository:name.Repository{Registry:name.Registry{insecure:false, registry:"index.docker.io"}, repository:"library/nginx"}, digest:"sha256:c7e7c316f879aa68e98165cfe8252e5b2c3540f4a527949eb1eb34e96afbd46d", original:"nginx:abc@sha256:c7e7c316f879aa68e98165cfe8252e5b2c3540f4a527949eb1eb34e96afbd46d"} '<nil>'
'nginx:abc@sha256:abcd' 'valid tag, invalid hash' <nil> 'could not parse reference: nginx:abc@sha256:abcd'
'nginx:abc@sha256:' 'valid tag, start of hash' <nil> 'could not parse reference: nginx:abc@sha256:'
'nginx' 'no tag, no hash' name.Tag{Repository:name.Repository{Registry:name.Registry{insecure:false, registry:""}, repository:"nginx"}, tag:"", original:"nginx"} '<nil>'
'nginx@sha256:c7e7c316f879aa68e98165cfe8252e5b2c3540f4a527949eb1eb34e96afbd46d' 'no tag, valid hash' name.Digest{Repository:name.Repository{Registry:name.Registry{insecure:false, registry:"index.docker.io"}, repository:"library/nginx"}, digest:"sha256:c7e7c316f879aa68e98165cfe8252e5b2c3540f4a527949eb1eb34e96afbd46d", original:"nginx@sha256:c7e7c316f879aa68e98165cfe8252e5b2c3540f4a527949eb1eb34e96afbd46d"} '<nil>'
'nginx@sha256:abcd' 'no tag, invalid hash' <nil> 'could not parse reference: nginx@sha256:abcd'
'nginx@sha256:' 'no tag, start of hash' <nil> 'could not parse reference: nginx@sha256:'


Suggestion for Section 5.5 (Generating a Random Number on Client and Server)

You mention using the prediction activation key as the seed for the pseudo random number generator, but list a series of (valid) downsides to that approach.
The alternative suggestion could be an extension of the prediction activation key approach, but with additional information hashed in that the server and client both know. For instance, hashing together the prediction activation key and a server-set, replicated Match ID number would make the values different per match, and the first values wouldn't be seeded with 0.
You might also hash the prediction activation key with the client's network ID. The server and client both know the requesting client's network ID, so no new information need be sent in that case, and you get the added bonus that each peer gets a different series of numbers they'll generate.

These suggestions sound good! It's a more complex solution that I would want to test before adding to the documentation, possibly with code snippets. But, I just don't have the time to do that.
There's lots of ways to handle random numbers and it depends on the requirements of the individual game. My intent with that section is to get people thinking about using the activation and scoped prediction keys beyond just predicted effects. Beginners will have something that will be "okay enough". I expect more experienced developers to devise a system that works best for them - their code architectural style and game requirements.


feat: basic functions of queue

Closes #256

Hi, Please read the Important Announcement.
PR can only be made after the issue is assigned to you.


clean up fails in case of job timeouts

Hi, we recently hit a case where a job has a timeout and is using this plugin. When the timeout was hit, the job ended without performing the cleanup steps of this plugin. This in turn caused the successive runs of the same job in the same node to have troubles (because of the residue from the failed cleanup)
I wonder if we can tackle this problem at this plugin level. If at this plugin level, then we might introduce a new flag like pre-cleanup and remove all containers and volumes on the host before the docker-compose up operation.
Do you have any suggestions on how we can handle timeouts gracefully?

It appears that cancelling a job means the cleanup steps are cancelled too.
Docker cleanup is one instance of this kind of failure, but we could leave other stuff running on the machine in case a job is cancelled.
Perhaps we could just shut down the instance immediately (accepting no more jobs) if the job failed, was cancelled, etc. and only keep it around if it passed?

hi @scriptnull! What you mention is very weird!
To start with, when a job is cancelled the pre-exit hook (where this plugin's cleanup code is) should run anyways. And, even more so, all containers run by this plugin do so using a project named similar to buildkite${BUILDKITE_JOB_ID} so subsequent runs of a pipeline in the same agent should have containers created within different projects so there shouldn't be an issue... unless the containers you are running don't handle the signals sent to them gracefully or in time for them to avoid getting killed outright, or maybe there are dependencies outside of those defined in docker compose that are causing the contentions you describe.
That said, what you are suggesting may be dangerous for those that run several agents in the same machine as a pipeline may try to remove elements from other builds that are actively running. Without more specific information about the pipeline being run and the exact errors it is complicated to understand exactly what is going on and how this plugin can help in that scenario because it doesn't even sound possible :p


Fix priorityClassName location

Description of changes:
Fixes bug introduced in https://github.com/aws/secrets-store-csi-driver-provider-aws/pull/171
priorityClassName is not on DaemonSet.spec.template.spec.containers but on DaemonSet.spec.template.spec.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #196 (37abfa3) into main (dc0d73e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #196   +/-   ##
=======================================
  Coverage   53.15%   53.15%
=======================================
  Files           8        8
  Lines         730      730
=======================================
  Hits          388      388
  Misses        332      332
  Partials       10       10

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

Tested with priorityClassName: "system-node-critical"
❯ kubectl describe pods -n kube-system chart-1678125216-secrets-store-csi-driver-provider-aws-6q8bg | grep Priority
Priority:<PHONE_NUMBER>
Priority Class Name:  system-node-critical


Breaking changes not working

Hi, thank you for developing this action. It is quite useful in verifying the PR titles.
However, it seems that titles with breaking changes using an ! are not parsed correctly. I am aware of the previous issues #2, #8, and #11 but unfortunately the issue still persists.
Version: 1.2.0
PR title: refactor(load)!: rename load_folder to load_deployment_folder #198
Thank you,
Hugo

After some digging, I found this is inherited behaviour from the conventional-commits-parser. In fact it has an almost identical issue which fortunately contains the fix: https://github.com/conventional-changelog/conventional-changelog/issues/648#issuecomment-704867077. I have a PR here to apply the fix to this GitHub action.


Configure webpack-dev-server and use HTML5 paths

In order to use HTML5 mode routing and support refresh on non-index routes, you have to configure your server to redirect every “missing” route to the root URL.  Since this is the preferred mode in production, we should mirror that in the development environment.

There is a flag for that in devServer, called historyApiFallback

Yes, I remember now.  I'm using that on my react-webpack projects.

Closing with #17


problem with video x4  for 4k  video

i  up with the model  to 280*4  = 1120  pixel  but if  video are in 360 or more   il have a progam error
how should i do to be able to use larger image for  do i have to train my own model?to get to 4k video ?

I have the Same question about my own model.

I think the problem is out of memory.


Handle errors gracefully on --get-all

Just a simple try/except on get-all that allows the process to continue past the book that gives the error. Doing this because as soon as you preorder something, the preordered book gives an error that bubbles to the top and stops the whole execution.

Implemented more completely by #21


[BUG] WM rate of pay not consistent

Discussed with @raducristianpopa yesterday.
When sending quicker payments, we await the createPayment call, which takes its own time to process. Then we wait for "interval" (without subtracting the time it took to process the payment). So, payments are slower than user configured.

Rafiki v1.0.0-alpha.16 improved performance a lot. But there's still some slowdown when sending multiple concurrent requests. Looking forward to more improvements before we move to this.


Screen turn black when vc4 is enabled on core-image-base

Screen turn black when vc4 is enabled
When I compile a core-image-base for MACHINE=raspberrypi4-64 on kirkstone branch, with poky also on kirkstone branch, the device boot and at the very beginning of the boot the HDMI screen turn off.
To solve this I need to edit config.txt and comment the line dtoverlay=vc4-kms-v3d
Probably a RDEPENDS is missing somewhere

Could you compare this with Raspbian?

Hello,
The latest 2022-04-04-raspios-bullseye-armhf-lite.img.xz have in config.txt dtoverlay=vc4-kms-v3d
I just have retested the kirkstone branch and it is still failing
This is how to reproduce it :
mkdir one_test_dir/
cd one_test_dir/
git clone --depth 1 -b kirkstone https://github.com/agherzan/meta-raspberrypi.git
git clone --depth 1 -b kirkstone git://git.yoctoproject.org/poky

source poky/oe-init-build-env rpi-build
echo "BBLAYERS += \"../meta-raspberrypi\"" >> conf/bblayers.conf
echo "MACHINE = \"raspberrypi4-64\"" >> conf/local.conf

bitbake core-image-minimal

#later
SDCARD_IMAGE=core-image-minimal-raspberrypi4-64-20220826125133.rootfs.wic.bz2
bzip2 -dc ${SDCARD_IMAGE} |  sudo dd of=${SDCARD_SLOT} bs=4M conv=notrunc,noerror status=progress ; sync;fin

I have the same issue, works only with fkms [which is a no go for me]

Did anyone investigate this against RaspberryPi OS? Kernel version, config etc.

Yes, to sum it up, it works there, with the same config.

What about the kernel version?

On Yocto, whichever is the most recent for kirkstone, on piOS whichever is the newest, which corresponds to master here [tried it too, no go]

So are you saying that the exact same kernel version, same exact fw config (config.txt) and same exact rpi-firmware version behave differently on RPi OS and Yocto?

Yes, that's what I'm saying.

I would be very surprised if that would be the case because I know Oniro has demos on Raspberry Pi 4 (64) and with the current layer it works for HDMI use cases too. Do you have a minimum setup that I can use to reproduce?

I would be very surprised if that would be the case because I know Oniro has demos on Raspberry Pi 4 (64) and with the current layer it works for HDMI use cases too. Do you have a minimum setup that I can use to reproduce?

hdmi works with fkms-3d [which is incredibly laggy], just not with "full kms" [and piOS does]

I see. That makes sense now. This needs a bit of debugging.

has this issue been solved? I have the same issue on most recent kirkstone

There was no progress on this as far as I am aware.

So after a bit of testing, it is working with rpi-test-image but not with core-image-minimal. rpi-test-image is based on core-image-base, so I tested it, and it is working too.

Alright, I found it!
After some binary search: kernel-module-i2c-brcmstb-5.15.34-v7l needs to be installed.
Here are now the added packages (depends):.
> kernel-5.15.34-v7l - 1:5.15.34+git0+e1b976ee4f_0086da6acd-r0
> kernel-image-5.15.34-v7l - 1:5.15.34+git0+e1b976ee4f_0086da6acd-r0
> kernel-image-zimage-5.15.34-v7l - 1:5.15.34+git0+e1b976ee4f_0086da6acd-r0
> kernel-module-i2c-brcmstb-5.15.34-v7l - 1:5.15.34+git0+e1b976ee4f_0086da6acd-r0

By the way, I also found out that kernel-image-zimage is installing zImage-5.15.34-v7l in /boot but yocto do it separatly so the it is in the rootfs while /boot isn't mounted. on the target I have kernel7l.img instead:
root@raspberrypi4:~# opkg files kernel-image-zimage-5.15.34-v7l
Package kernel-image-zimage-5.15.34-v7l (1:5.15.34+git0+e1b976ee4f_0086da6acd-r0) is installed on root and has the following files:
/boot/zImage-5.15.34-v7l

root@raspberrypi4:~# ls /boot/
bcm2708-rpi-b-plus.dtb        bcm2709-rpi-2-b.dtb           bcm2711-rpi-400.dtb           fixup4.dat                    fixup_x.dat                   start4cd.elf
bcm2708-rpi-b-rev1.dtb        bcm2710-rpi-2-b.dtb           bcm2711-rpi-cm4.dtb           fixup4cd.dat                  kernel7l.img                  start4db.elf
bcm2708-rpi-b.dtb             bcm2710-rpi-3-b-plus.dtb      bootcode.bin                  fixup4db.dat                  overlays                      start4x.elf
bcm2708-rpi-cm.dtb            bcm2710-rpi-3-b.dtb           cmdline.txt                   fixup4x.dat                   rpi-bootfiles-20220830.stamp  start_cd.elf
bcm2708-rpi-zero-w.dtb        bcm2710-rpi-cm3.dtb           config.txt                    fixup_cd.dat                  start.elf                     start_db.elf
bcm2708-rpi-zero.dtb          bcm2711-rpi-4-b.dtb           fixup.dat                     fixup_db.dat                  start4.elf                    start_x.elf

Hi!
I am currently moving from using the Dunfell branch to Kirkstone. The reason is that QtWebEngine needs Hardknott or newer. Before the change, we had no problem with our graphics. Now, after boot the HDMI output stops and the screen turns off. I tried to comment out dtoverlay=vc4-kms-v3d from config.txt and this allows the device to boot and show a console but Qt can't render to the screen.
Did you find a solution @FederAndInk?
Is this fixed by any newer versions @agherzan?
Would appreciate any help you can give on this issue.

@Awarty see this chage
https://github.com/YoeDistro/yoe-distro/blob/master/conf/projects/rpi4-64/config.conf#L53

Alright, I found it!
After some binary search: kernel-module-i2c-brcmstb-5.15.34-v7l needs to be installed.
Here are now the added packages (depends):.
> kernel-5.15.34-v7l - 1:5.15.34+git0+e1b976ee4f_0086da6acd-r0
> kernel-image-5.15.34-v7l - 1:5.15.34+git0+e1b976ee4f_0086da6acd-r0
> kernel-image-zimage-5.15.34-v7l - 1:5.15.34+git0+e1b976ee4f_0086da6acd-r0
> kernel-module-i2c-brcmstb-5.15.34-v7l - 1:5.15.34+git0+e1b976ee4f_0086da6acd-r0

By the way, I also found out that kernel-image-zimage is installing zImage-5.15.34-v7l in /boot but yocto do it separatly so the it is in the rootfs while /boot isn't mounted. on the target I have kernel7l.img instead:
root@raspberrypi4:~# opkg files kernel-image-zimage-5.15.34-v7l
Package kernel-image-zimage-5.15.34-v7l (1:5.15.34+git0+e1b976ee4f_0086da6acd-r0) is installed on root and has the following files:
/boot/zImage-5.15.34-v7l

root@raspberrypi4:~# ls /boot/
bcm2708-rpi-b-plus.dtb        bcm2709-rpi-2-b.dtb           bcm2711-rpi-400.dtb           fixup4.dat                    fixup_x.dat                   start4cd.elf
bcm2708-rpi-b-rev1.dtb        bcm2710-rpi-2-b.dtb           bcm2711-rpi-cm4.dtb           fixup4cd.dat                  kernel7l.img                  start4db.elf
bcm2708-rpi-b.dtb             bcm2710-rpi-3-b-plus.dtb      bootcode.bin                  fixup4db.dat                  overlays                      start4x.elf
bcm2708-rpi-cm.dtb            bcm2710-rpi-3-b.dtb           cmdline.txt                   fixup4x.dat                   rpi-bootfiles-20220830.stamp  start_cd.elf
bcm2708-rpi-zero-w.dtb        bcm2710-rpi-cm3.dtb           config.txt                    fixup_cd.dat                  start.elf                     start_db.elf
bcm2708-rpi-zero.dtb          bcm2711-rpi-4-b.dtb           fixup.dat                     fixup_db.dat                  start4.elf                    start_x.elf

I am new in learning Yocto, so can you explain how you add those packages to the image ? I am facing the same issue and I want to use core-image-minimal as a base to get the lighter OS. Thanks by advance for the help!

@MultiXaNos core-image-base is perhaps better than core-image-minimal since you want to include basic building blocks and not wrestle with these util you get some experience with the system. When building final image, boot elements are emitted into its own partition. the /boot that comes with main rootfs is not used so perhaps its best to remove that from image, you can do so by setting
RDEPENDS:${KERNEL_PACKAGE_NAME}-base = ""

I have had the same issue with scarthgap, raspberrypi5 and core-image-full-cmdline


emulation finished and but no action occurred

After the simulation is completed, there are no other actions. Forcefully terminating will result in an error message for the docker-helper. py code

Addendum: Firmware can be simulated normally in debug mode, but cannot enter the web homepage


Simple render test fails when importing Link

Hi people,
I created a simple app with create-react-app where I installed jumpsuit. I made some small changes to the main app component by importing Link from jumpsuit. After doing this, the sample test that checks if the component renders correctly gives me this error:
> node scripts/test.js --env=jsdom
 FAIL  src/containers/App.test.js
  ● Test suite failed to run
    Invalid Adapter: undefined

      at new PouchDB$3 (node_modules/pouchdb-browser/lib/index.js:2797:11)
      at Object.<anonymous> (node_modules/jumpsuit/lib/hsrPouch.js:13:10)
      at Object.<anonymous> (node_modules/jumpsuit/lib/hsr.js:16:17)
      at Object.<anonymous> (node_modules/jumpsuit/lib/index.js:23:12)
      at Object.<anonymous> (src/containers/App.js:2:43)
      at Object.<anonymous> (src/containers/App.test.js:3:38)
      at process._tickCallback (internal/process/next_tick.js:103:7)
Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        1.718s
Ran all test suites.
npm ERR! Test failed.  See above for more details.

The only thing I have to do to App.js is to import Link:
import { Link } from 'jumpsuit';
Do I have to write extra code to my test in order to get it working? Seems like I have to define a PouchDB adapter.
The current code looks like this:
import React from 'react';
import ReactDOM from 'react-dom';
import App from './App';

it('renders without crashing', () => {
  const div = document.createElement('div');
  ReactDOM.render(<App />, div);
});

$ npm -v
3.10.9
$ node -v
v7.2.0

OS: Windows 10
Will appreciate any help on this. Cheers!

I have the same problem with import { Component } from 'jumpsuit'; I don't think the problem is related to Link

Does the app render in the browser still?  Or is it just the test that fails?

Just the test fails. No problems with the browser rendering.
On Thu, 23 Feb 2017, 22:19 Tanner Linsley<EMAIL_ADDRESS>wrote:

Does the app render in the browser still? Or is it just the test that
fails?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jumpsuit/jumpsuit/issues/78#issuecomment-282140356,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFGEcVRH8skRqRKAjcv8PqYw72hKtO-Eks5rfgYCgaJpZM4MKb-m
.

--
Visit my website at razvanilin.com

Any update to getting the tests to work @tannerlinsley ? I know you're busy, just wondered if this is in the works to be fixed soon. Thanks for all you've done for this!

Not using Jumpsuit I would suppose the error is that you are not using Jumpsuit in a Browser context. The code from Jumpsuit is:
const db = new PouchDB('jumpsuit_hsr')

(see https://github.com/jumpsuit/jumpsuit/blob/5993629cb27fa24623a05956412ba300a3b69123/src/hsrPouch.js#L4)
In a Browser Context Pouch automatically uses some Adapter (IndexedDB, i think) whereas in a Node Context you have to specify the adapter. In order for this to work you would probably have to install pouchdb-adapter-node-websqlor pouchdb-adapter-memory via npm and change the line to
const db = new PouchDB('jumpsuit_hsr', {adapter: 'websql'})

See https://pouchdb.com/adapters.html#pouchdb_in_node_js for reference.
Or you change import PouchDB from 'pouchdb-browser' to import PouchDB from 'pouchdb' and install pouch via npm


SlimJet Browser

SlimJet Browser - https://github.com/WhichBrowser/Parser-PHP/issues/183

Coverage remained the same at 100.0% when pulling 4410b08e04f396e1d45ed59bea9c16a2ece6843c on ayumi-cloud:SlimJet into 4899110cd2f87b01e04ced62dbb9dec541031dee on WhichBrowser:master.


Applied Visual Design: Learn How the CSS @keyframes and animation Properties Work

Describe your problem and - if possible - how to reproduce it
I have written the right answer to the problem but when I submit it, the engine keeps running the test but it doesnt end. It doesnt tell me whether I did it right or wrong, it just says running tests. I tried redoing it and resetting it but it wont let me pass it.
#rect {
animation-name: rainbow;
animation-duration: 4s;
}
@keyframes rainbow {
0% {
background-color: blue;
}
50%{
background-color:green;
}
100% {
background-color: yellow;
}
}
Add a Link to the page with the problem
https://learn.freecodecamp.org/responsive-web-design/applied-visual-design/learn-how-the-css-keyframes-and-animation-properties-work
Tell us about your browser and operating system

Browser Name: Edge 17 on Windows
Browser Version: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/17.17134
Operating System: Windows

If possible, add a screenshot here

@Murrium123 I think you would need to switch to Chrome or Firefox in order to use FCC. There have been a number or reports of FCC not working correctly on Edge / IE and Safari.

@Murrium123  It is working on Chrome and Firefox. May be it is not compatible on edge.So switch on to Chrome or Firefox.

yes, so the problem is on user side and not here, so @Murrium123 / @ezioda004 I think it would be befitting to close the issue

Closing as its not an issue in the challenge itself.