Problem with Karma setup as soon as component has 3rd-party dependencies

Working with the out-of-the-box skeleton, I added materialize-css and then call one of its jQuery methods in the componentDidMount of HomeView to initialize a select box I added there:
componentDidMount () {
  $(ReactDOM.findDOMNode(this.refs.select)).material_select();
}

Everything works great when running the app, but npm run test bombs out because material_select is undefined. So I added jquery and materialize-css to the files of the karma config, yet the error persists. Maybe this is just my ignorance about Karma or a quirk of materialize-css, but I'm stuck on this. Any help?
    files : [
      './node_modules/phantomjs-polyfill/bind-polyfill.js',
      './node_modules/jquery/dist/jquery.js',
      './node_modules/materialize-css/dist/js/materialize.js',
      './' + KARMA_ENTRY_FILE
    ]

TypeError: 'undefined' is not a function (evaluating '$(_reactDom2['default'].findDOMNode(this.refs.select)).material_select()')

Okay, I was able to get it to work by explicitly importing jQuery and materialize-css in my component's JS file (no need to mess with the karma config), but I normally don't have to do that with webpack outside of Karma, which doesn't seem to use that knowledge though. I would like to avoid having to do that just to support the tests. Any advice would be appreciated.

Do you have a branch/fork that demonstrates this problem? I'll gladly take a look and see if I can help at all.

I'll make a fork. Thank you!

Okay, here is the fork with the problem baked in (on the feature/select branch). The commits should tell the story of the changes.  If you run npm run test you will be told that the library's functions are undefined. If you uncomment the two imports in the MaterialSelect component, the tests will pass. The expectation is that the same code should work in the browser and in tests without changes.

Awesome, thanks you; I'll take a look a bit later. Probably won't be able to get to it until tomorrow, but hopefully we can figure out a solution to this.

Look forward to hearing what you might have discovered here, especially since you've been playing around with refactoring the kit.

I pulled it down yesterday and played around with it but didn't have any success. I'm away from my computer today, but will keep messing with it tomorrow. Sorry :(

Still haven't found anything... I'll post if I do. Haven't forgotten about it.

@neverfox did you ever figure this out?

No, but I've come to the conclusion that perhaps the expectation was unreasonable. I think it's probably improper to lean on webpack's ability to resolve some global identifiers and that I should always just be explicit with my dependencies. I can live with that.

Ok, well I'll close this for now then.

I think I'm getting a similar error to this.  Whenever I'm trying to test a component that uses something with react-bootstrap (at least I think thats whats causing the issue) I get this:

@neverfox did you ever figure out how to fix this or is this a different issue completely?
I tried your solution by adding the react-bootstrap node module to the files section of karma.conf like this:
  files: [
    './node_modules/phantomjs-polyfill/bind-polyfill.js',
    './node_modules/react-bootstrap/dist/react-bootstrap.js',
    {
      pattern: `./${config.dir_test}/**/*.js`,
      watched: false,
      served: true,
      included: true
    }
  ],

But then the error I get is:

We had a similar problem.   It may be related to the Webpack DeDupePlugin.   Removing it helped us  out

Wow that totally fixed it.  @davezuko we should record this fix in appropriate place.  The error message was so mysterious/useless I had no idea where to even begin hahaha.  Thank you @bradbirnbaum much appreciated.
Are there serious negative side affects for getting rid of the dedupe plugin?  Will it just load multiple versions of the library dependencies?  Or is it almost a pre-optmization that I probably don't need to worry about if this is a small SPA?

@SpencerCDixon glad that helped.   We were seeing similar errors in our tests.   The first run would work but subsequent runs would fail.   It only started as out project got larger.


Feature/testcafe

(Pull-request not ready for merging, feature not finished. Created to track changes made in the branch in comparision to develop.)

Hey, @ronaldvandenbroek. I've turned this PR in to a draft, because it's not ready for review yet. When ready, just click the ready for review button!

Hi @ronaldvandenbroek, I see you've added the e2e tests script to the pre-commit hook.
Do take in consideration that the actions that we want to perform in the pre-commit hook have to be very fast to ensure a good DX (Developer Experience). For instance, when using a GIT GUI, like the one in VSCode, you're not getting a lot of visual feedback. New developers might end up wondering why their code isn't committing correctly.
At this time in the project, the tests run fast. But as time and your project progresses, test will take longer and so will running each commit.
Protecting key-branches by forcing PR's with a CI/CD workflow are the ideal middle ground of ensuring code-quality of incoming code.

Fixed issues that came up during the stand-up and review:

Converting all imports to require.
Moving logic outside of unit-tests and implemented immutability.
Whitelisting plugins with jest (see comment for more detail).
TestCafé actually failing if a test fails instead of ignoring it.
Splitting the linting, e2e and unit test jobs within the pipeline to account for their differences:

Linting does not need to run on three node versions.
E2e building step has been separated from the test to ensure the pipeline does not pass if the build fails.

Trigger the pipeline only if a commit is connected to a pull-request. This can be expanded to only trigger for pull-requests to specific branches but this is not needed at the moment.

Lastly, TestCafé does not have any built-in browsers, docker might be a solution but it may be best to create a separate ticket for this. TestCafé Browser Support

LGTM


Add a debug path that displays a heatmap of the number of bounces

Instead of color the number of bounces can be output, averaged, and then mapped to a gradient

Fixed in #422


Add a new tool to generate random QASM circuits

This tool will print on the standard output a QASM program which instructions
were generated randomly and are equally weighted between U3 and CX.
The program is valid from the point of view of QASM syntax but it has no valid logic.
The main purpose of this tool is to help in benchmarking and testing Quantum simulators.
Usage example:
Create a QASM circuit file called circuit.qasm with ~100 operations
(CX and U3 gates), 16 Qubits, and a seed of 169
./random_qasm_generator.py -s 169 -d 100 -q 16 > circuit.qasm
I'm using this PR to reuse /tools directory. The old one was not useful anymore since
pip integration
Motivation and Context

This tool could be useful for testing and/or benchmarking simulators.
Types of changes

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

Checklist:

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

This is useful as a command line script. It is similar to tools/python/_random_qasm_generator.py. The module tools/python/_random_circuit_generator.py is more general than _random_qasm_generator and also might be useful as a script. You can for instance specify a basis set, weights and it does "if" statements. Lev may be working on something even more general.

Yeah, I took the _random_qasm_generator.py and changed it a bit so we can build something more arbitrary and not so random. For example, I found very convenient to have a fixed amount of qubits and oprations, instead of generating something random between a max and a min. Being more deterministic in this case, is needed for benchmarking or testing.
Do you think it's worth implementing the basis set, weights and "if" statements to behave more like the _random_circuit_generator? or... Lev is working in something that will have the same functionality so doesn't make any sense to have this tool now, and just wait for Lev's.
Thanks!

merging now and simplifying later sounds fine with me


Actually use phys siteset tests, add more

If you don't add the new test file to runtests.jl, then it won't be part of the coverage run! 😛

D’oh!

Codecov Report

Merging #63 into master will increase coverage by 6.14%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #63      +/-   ##
==========================================
+ Coverage   86.51%   92.66%   +6.14%
==========================================
  Files          24       24
  Lines        2181     2181
==========================================
+ Hits         1887     2021     +134
+ Misses        294      160     -134

Impacted Files
Coverage Δ

src/physics/sitesets/tj.jl
57.57% <ø> (+57.57%)
:arrow_up:

src/itensor.jl
98.51% <0%> (+0.74%)
:arrow_up:

src/storage/dense.jl
99.35% <0%> (+1.94%)
:arrow_up:

src/physics/sitesets/spinhalf.jl
97.95% <0%> (+20.4%)
:arrow_up:

src/physics/sitesets/spinone.jl
100% <0%> (+46.25%)
:arrow_up:

src/physics/sitesets/electron.jl
85.36% <0%> (+54.87%)
: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 7ceb196...00e5538. Read the comment docs.

Codecov Report

Merging #63 into master will increase coverage by 6.14%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #63      +/-   ##
==========================================
+ Coverage   86.51%   92.66%   +6.14%
==========================================
  Files          24       24
  Lines        2181     2181
==========================================
+ Hits         1887     2021     +134
+ Misses        294      160     -134

Impacted Files
Coverage Δ

src/physics/sitesets/tj.jl
57.57% <ø> (+57.57%)
:arrow_up:

src/itensor.jl
98.51% <0%> (+0.74%)
:arrow_up:

src/storage/dense.jl
99.35% <0%> (+1.94%)
:arrow_up:

src/physics/sitesets/spinhalf.jl
97.95% <0%> (+20.4%)
:arrow_up:

src/physics/sitesets/spinone.jl
100% <0%> (+46.25%)
:arrow_up:

src/physics/sitesets/electron.jl
85.36% <0%> (+54.87%)
: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 7ceb196...00e5538. Read the comment docs.


Can't get PointToPlaneErrorMinimizer to work

Hi,
I'm trying to do point-to-plane ICP with the pmicp program. My dataset is a cross section extracted from mobile laser scan of a piece of track. I've tried several different data filters, but I never get any output. The furthest I've gotten is the
PointMatcher::PointToPlaneErrorMinimizer - minimization will be in 2D.
message. Point to Point works fine.
I'm assuming it is because not enough planar features can be found in the dataset, but I don't see any way of tuning what is to be considered a plane. What can I do differently to get point-to-plane to work?
Regards,
Tobias

Can you send your configuration file (yaml)?

This is one of the configurations I tried:
readingDataPointsFilters:
IdentityDataPointsFilter
referenceDataPointsFilters:
IdentityDataPointsFilter
matcher:
KDTreeMatcher:
knn: 1
outlierFilters:

TrimmedDistOutlierFilter:
ratio: 0.95

errorMinimizer:
PointToPlaneErrorMinimizer
transformationCheckers:

CounterTransformationChecker:
maxIterationCount: 100
DifferentialTransformationChecker:
minDiffRotErr: 0.001
minDiffTransErr: 0.001
smoothLength: 4

inspector:
NullInspector
logger:
FileLogger

You are missing the SamplingSurfaceNormalDataPointsFilter filter to generate the normal on the reference point cloud. Check out this example yaml configuration.

I've tried using the example yaml, but I'm not getting any results. This is the program output:

KDTreeMatcher: initialized with knn=1, epsilon=0, searchType=1 and maxDist=inf
PointMatcher::PointToPlaneErrorMinimizer - minimization will be in 2D.
Applying 1 DataPoints filters - 211005 points in
SamplingSurfaceNormalDataPointsFilter - 105276 points out (-50.1073%)
Applied 1 filters - 105276 points out (-50.1073%)
PointMatcher::icp - reference pre-processing took 0.339 [s]
Applying 1 DataPoints filters - 138635 points in
RandomSamplingDataPointsFilter - 69243 points out (-50.0537%)
Applied 1 filters - 69243 points out (-50.0537%)
PointMatcher::icp - reading pre-processing took 0.009 [s]
PointMatcher::icp - 5 iterations took 0.124 [s]
match ratio: 0.750011

Configuration:
readingDataPointsFilters:

RandomSamplingDataPointsFilter:
prob: 0.5

referenceDataPointsFilters:

SamplingSurfaceNormalDataPointsFilter:
knn: 10

matcher:
KDTreeMatcher:
knn: 1
epsilon: 0
outlierFilters:

TrimmedDistOutlierFilter:
ratio: 0.75

errorMinimizer:
PointToPlaneErrorMinimizer
transformationCheckers:

CounterTransformationChecker:
maxIterationCount: 40
DifferentialTransformationChecker:
minDiffRotErr: 0.001
minDiffTransErr: 0.01
smoothLength: 4

inspector:
NullInspector
logger:
FileLogger

To receive the message PointMatcher::PointToPlaneErrorMinimizer - minimization will be in 2D. the parameter force2D needs to be set to true somewhere.
In your yaml file, try:
errorMinimizer:
   PointToPlaneErrorMinimizer:
      force2D: 0

When you say,

not getting any results

you mean that no transformation is printed or that you're not getting the transformation you were expecting?

I've tried the force2D: 0 parameter, but still get the message about minimization being in 2D.
I get no result files at all. The program seems to be quitting prematurely, as I have added the computation and output of the fitting error and don't see that when using point-to-plane.

Alright, that's not normal.
@tfwittwer : please share with us your two point clouds and config.yaml
@simonpierredeschenes can you have a look to the data?

This is the download link: https://we.tl/t-6wR2kF0bR8
Thanks for your help!

I see that the data has not been downloaded yet. Should I share it in some other way?

I will have a look today, sorry for the delay!

When I run pmicp with the following command:
./pmicp --config icp_cfg.yaml 181215_015439_S1.csv 181215_022701_S1.csv

the three output files (test_ref.vtk, test_data_in.vtk and test_data_out.vtk) are generated. I use the latest version (eb9457d) and the config I use is:
readingDataPointsFilters:
  - RandomSamplingDataPointsFilter:
      prob: 0.5

referenceDataPointsFilters:
  - SamplingSurfaceNormalDataPointsFilter:
      knn: 10

matcher:
  KDTreeMatcher:
    knn: 1
    epsilon: 0

outlierFilters:
  - TrimmedDistOutlierFilter:
      ratio: 0.75

errorMinimizer:
  PointToPlaneErrorMinimizer

transformationCheckers:
  - CounterTransformationChecker:
      maxIterationCount: 40
  - DifferentialTransformationChecker:
      minDiffRotErr: 0.001
      minDiffTransErr: 0.01
      smoothLength: 4

inspector:
  NullInspector

logger:
  FileLogger

The "minimization will be in 2D" message is always printed, whatever the config is, but it does not mean that minimization is always done in 2D. I will open an issue for this logging problem.
What is outputed if you run the libpointmatcher/utest/listVersionsUbuntu.sh script?

I haven't tried libpointmatcher/utest/listVersionsUbuntu.sh yet (I'm on Windows, by the way - not sure if that may be the cause of the problems), but running your command and yaml file does not produce the vtk files. The console output is

KDTreeMatcher: initialized with knn=1, epsilon=0, searchType=1 and maxDist=inf
PointMatcher::PointToPlaneErrorMinimizer - minimization will be in 2D.
Applying 1 DataPoints filters - 211005 points in
SamplingSurfaceNormalDataPointsFilter - 105276 points out (-50.1073%)
Applied 1 filters - 105276 points out (-50.1073%)
PointMatcher::icp - reference pre-processing took 0.337 [s]
Applying 1 DataPoints filters - 138635 points in
RandomSamplingDataPointsFilter - 69243 points out (-50.0537%)
Applied 1 filters - 69243 points out (-50.0537%)
PointMatcher::icp - reading pre-processing took 0.01 [s]
PointMatcher::icp - 5 iterations took 0.123 [s]

Ok, stepping through the program with the debugger has given me more insight. As I wrote above, I've modified the pmicp program to give me the residual error, as described here: https://github.com/ethz-asl/libpointmatcher/issues/193#issue-203885636
This line causes an exception:
float error = icp.errorMinimizer->getResidualError(data_out, ref, outlierWeights, matches);
Unhandled exception at 0x00007FFA863D9129 in pmicp.exe: Microsoft C++ exception: PointMatcher::DataPoints::InvalidField at memory location 0x0000000BD9D8E758.
This does not occur with the PointToPlaneErrorMinimizer

Can you get the exception message of the InvalidField exception? Normally, when an exception is uncaught it is suppose to print the error message in the console.
Before trying to get the residual error working, it would be preferable to fix the problem you have with ICP.
To debug the issue I suggest changing the inspector in the yaml configuration to:
inspector:
 VTKFileInspector:
     baseFileName: myoutput
     dumpPerfOnExit: 0
     dumpStats: 0
     dumpIterationInfo: 1
     dumpDataLinks: 1
     dumpReading: 1
     dumpReference: 1

Based on your previous log output, it seems that ICP, however the file are either not written on disk or written in the wrong folder. Adding this inspector, will make ICP write a vtk for each ICP iteration. Thus since your ICP execute 5 iterations, it should write something.

The ICP is working now. The program crashed before output was generated due to the error computation not working.
There is no error message output to the console. The exception message is:
Unhandled exception at 0x00007FFA863D9129 in pmicp.exe: Microsoft C++ exception: PointMatcher::DataPoints::InvalidField at memory location 0x0000000BD9D8E758.
I believe this is the same issue as reported in issue #193 (points have no normals).

Have tried doing the same solution as #193? The problem with his code was that he needed to apply the data point filter. He assumed that the datapoints where pass by reference, not by value.
The more efficient of computing the residual is to use ICPSequence. Check this #363 to get an idea of how to do it:

I don't see in #193 how exactly the data point filter is applied. I've taken a look at #363, but it is not clear to me which changes I would have to make to pmicp to make it work. It's pretty much a black box for me.

The error message said that your reference pointcloud does not have a normal field. In libpointmatcher normal are computed using a datapoint filter. The datapoint filters are set by loading a yaml configuration file. In #193, the datapoint dpref passed to this function does not have normals:
void getResidualError(const DP &dpref, const DP &dppointcloud_out) {
  icp_.matcher->init(dpref);
  PM::Matches matches = icp_.matcher->findClosests(dppointcloud_out);
  PM::OutlierWeights outlierWeights = icp_.outlierFilters.compute(dppointcloud_out, dpref, matches);
  float error = icp_.errorMinimizer->getResidualError(dppointcloud_out, dpref, outlierWeights, matches);
  std::cout << "Final residual error: " << error << std::endl;
}

You need to execute the reference's datapoint filters by doing the following:
icp_.referenceDataPointsFilters.apply(dpref);
getResidualError(dpref, dppointcloud_out);

dprefshould now contain normals.

Got it to work, thank you very much!


Can not download video  Video is not available error

Version
1.12.2
Platform
Windows 11
Steps to reproduce
just try to download video
https://www.youtube.com/watch?v=vXnTMjMe5Eg
https://www.youtube.com/watch?v=_zjdBTJit4Q
https://www.youtube.com/watch?v=yMGTUQhjtlM
Details

Error stack trace from debug
YoutubeExplode.Exceptions.VideoUnavailableException: Video 'vXnTMjMe5Eg' is not available.
   at YoutubeExplode.Videos.VideoController.GetVideoWatchPageAsync(VideoId videoId, CancellationToken cancellationToken) in /_/YoutubeExplode/Videos/VideoController.cs:line 39
   at YoutubeExplode.Videos.VideoClient.GetAsync(VideoId videoId, CancellationToken cancellationToken) in /_/YoutubeExplode/Videos/VideoClient.cs:line 37
   at YoutubeDownloader.Core.Resolving.QueryResolver.TryResolveVideoAsync(String query, CancellationToken cancellationToken) in C:\projects\source\YoutubeDownloader\YoutubeDownloader.Core\Resolving\QueryResolver.cs:line 51

not sure if it relates to #476 , feel free to close if duplicated
Checklist

[X] I have looked through existing issues to make sure that this bug has not been reported before
[X] I have provided a descriptive title for this issue
[X] I have made sure that this bug is reproducible on the latest version of the application
[X] I have provided all the information needed to reproduce this bug as efficiently as possible
[ ] I have sponsored this project
[ ] I have not read any of the above and just checked all the boxes to submit the issue

右上角那里点下钥匙那里登录的微软账号即可

右上角那里点下钥匙那里登录的微软账号即可

登录之后可以下载，谢谢

seemed related to https://github.com/Tyrrrz/YoutubeExplode/issues/794 closed as duplicated


Step 2 Create initial cloud backup:Note change.

The bottom note here is changed. This should be the old one.Need to update the note as mentioned in following screen.

Verified this issue on dev app v2.0.68(418)


[WIP] Add additional tags using terraform so that kubernetes tests will

correctly collect logs (PIP-60). Convert use of terraform ebs_block_device
resources to use aws_ebs_volume and aws_volume_attachment so that we can
tag the volume with the masters IP. Add support for all currently
existing regions (KRAK-362).

Note that is still one known bug in this code. Destroy currently fails due to: ```Error applying plan:
1 error(s) occurred:
Note that there is still one bug in this code which I am working on. During terraform destroy, we see the following error:

aws_volume_attachment.kubernetes_master_volume_attachment: Error waiting for Volume (vol-9e1b9c28) to detach from Instance: i-395ea7ff

I am still looking into why... Also, the reason for addressing addressing to JIRAs in the same PR is that supporting all regions changes how we tag auto scaling groups.

Closing because the kubernetes supplied log-dump.sh will not work in our environment because our etcd, apiserver and controller manager do not run on the same node. After discussing with others, we believe that the current e2e tests depend too heavily on the environment created by kube-up.sh. We will open PRs to correct this and create an kraken specific log-dump facility.


SSSOM vs OMOP2OBO representation

When compared to OMOP2OBO, SSSOM lacks expressivity at first glance. Here is an example:
Example: Hip pain (OMOP_4170554)
Ontology Concepts:
Hip pain (HP_0030838)
Arthralgia of the hip (HP_0003365)
Mapping Evidence:
OBO_DbXref-OMOP_CONCEPT_CODE:snomedct_us_49218002
OBO_LABEL-OMOP_CONCEPT_LABEL:hip_pain
OBO_hasExactSynonym-OMOP_CONCEPT_LABEL:hip_pain
OBO_LABEL-OMOP_CONCEPT_SYNONYM:hip_joint_pain
CONCEPT_SIMILARITY:HP_0003365_1.0
CONCEPT_SIMILARITY:HP_0030838_1.0

SSSOM can express the same things as OMOP2OBO, but we don't have a way to aggregate the evidence in the same way - each record in SSSOM provides 1 specific piece of evidence, and we do not really have a way to say: this mapping has these 10 different pieces of evidence going for it. I am happy to let the tools do that kind of stuff;
@callahantiff would you be able to provide us with a complete picture of what other features of the OMOP2OBO mapping representation cannot be faithfully captured in SSSOM? :) Thanks!
For me, the main difference between OMOP2OBO and SSSOM

Should be able to work on this soon! Working on some updates to the mapping pipeline as we speak. Once those are done, my next step is to create some code to convert to the SSSOM standard. That will be a good time to dive deep into this question!


fix: mobile password

Description

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk

Testing

Engineering

Operations

Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #5522   👈

This comment was auto-generated by Graphite.


spell summon creature

cast 40
Summon a horse
When the player rides it, the horse will not be deleted when the magic time is up, but the timer will be deleted

It seems that the horse disappears when you dismount the horse after the summon spell timer expires

It will disappear when you dismount
If you don't get off the horse, the time will not disappear?

Dupicate of issue #582, let's use that.


Layout options not working

Hello,
The documentation says as follows under Layout Options:
__
AdminLTE 2.0 provides a set of options to apply to your main layout. Each on of these classes can be added to the body tag to get the desired goal.
Fixed: use the class .fixed to get a fixed header and sidebar.
Collapsed Sidebar: use the class .collapsed-sidebar to have a collapsed sidebar upon loading.
Boxed Layout: use the class .layout-boxed to get a boxed layout that stretches only to 1250px.
Top Navigation use the class .layout-top-nav to remove the sidebar and have your links at the top navbar.
__
My preference is for the dashboard to start fixed with sidebar collapsed so I have changed the body tag as follows <body class="fixed collapsed-sidebar skin-black"> but its not working (Angle braces reversed by me so the tag won't get removed). Please advice what I'm doing wrong.
Regards,
Adam

Change your body tag to:
<body class='fixed sidebar-collapse skin-black'>


Countdown issue when user change his machine date

Dear Hilios,
I've read the issue regarding countdown problem published in link below :
https://github.com/hilios/jQuery.countdown/issues/26
It's marked closed, but I don't see any workaround to set the countdown time according the GMT, since the countdown will always change when the user change his machine time & date.
We need it to detect the user's timezone and use it as the current time & date, so the countdown won't be changed in case the user change his machine date (unless he change the timezone).
Or can you advise on how to combine the countdown script with : http://momentjs.com/timezone/ ?
We've tried to add validation from the server-side, but of course it doesn't change on how the countdown presented in the client-side.
Could you give any advise?
Regards,
Robert

Well Robert, this is a well know use case and it's a very hard computational problem, and even you use MomentJS to mitigate, still it's not a perfect solution.
I'm still pending an timezone example using MomentJS, sorry if I could have the time to accomplish this task yet.

I had the same problem and one of the solutions I found wasn't working on Safari Mobile, so the first thing you need to do is convert your final date in UTC so the time I needed was January 27, 2015 00:00:00 so that date in UTC it will be January 27, 2015 05:00:00 and then pass that object date to the plugin, and it should work fine.
var date = new Date('1/27/2015 05:00:00 UTC');
$('#countdown').countdown(date);

Here is a full implementation of the countdown timezone aware using Moment JS:
http://hilios.github.io/jQuery.countdown/examples/timezone-aware.html

Thanks man.. :)
 On Tuesday, July 14, 2015 4:20 AM, Edson Hilios<EMAIL_ADDRESS>wrote:

Here is a full implementation of the countdown timezone aware using Moment JS:
http://hilios.github.io/jQuery.countdown/examples/timezone-aware.html—
Reply to this email directly or view it on GitHub.

@hilios
I was able to set timer irrespective of the local time, but the problem I am facing is, when the local time is changed, the countdown timer changes.
Even in this link http://hilios.github.io/jQuery.countdown/examples/timezone-aware.html if you change the local machine time, the countdown changes. Any solution for this use case?

@sagarrakshe well this is a "issue" of the JavaScript implementation itself

The JavaScript Date object supports a number of UTC (universal) methods, as well as local time methods. UTC, also known as Greenwich Mean Time (GMT), refers to the time as set by the World Time Standard. The local time is the time known to the computer where JavaScript is executed.
– From: Mozilla Developer Network

Unfortunatly it is not a simple issue to handle because the countdown use the machine date to subtract from the final date.
I am now thinking how to implement that in a way that is compatible with the current implementation

Why not add start date option to override default starting date?

Does it have any solution today?
It has a huge effect on the countdown every time I change my local machine time.


Add turf to showcases

Name: Turf
Description: Turf creates cartographic NFTs / wall art. Each Turf is a gorgeous 1/1 map based artwork of your favorite place on earth, preserved as interactive 3D NFTs.
Link:   https://turfnft.com
Source: n/a
Tags:
nft

Hey @gglucass, please note the build error is not related to your pull request. We will take care of it.


[WIP] [BEAM-10396] Jdbcio writerows

Implement WriteRows method in JdbcIO.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

PR and issue was closed. Read the thread for detail

PR and issue was closed. Read the thread for detail

What about removing the TODO?


IPv6 support?

For dual-stack VNETs, do we need to make any modifications to the virtualNetworkCombo?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a3df019b-7033-935b-b0d2-4651cf973ee5
Version Independent ID: 2e96264c-d8e9-7a8d-f39e-5f5e49f2115d
Content: VirtualNetworkCombo UI element - Azure Managed Applications
Content Source: articles/azure-resource-manager/managed-applications/microsoft-network-virtualnetworkcombo.md
Service: managed-applications
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@m43kwon Thank you for your feedback! We will review and provide an update as appropriate.

@m43kwon I am unsure if this will work with a dual stack VNET, but I see no reason it should fail. Use JSON configurations from this doc and from resources.azure.com to view the template structure, and add elements to the VNET and subnet as needed.
Please let me know if you need any additional information.

@m43kwon We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Update the default soname for tarballs

When building rocm_smi_lib from a source tarball the soname defaults to 1.0.0
Can you please update the soname in the cmake script upon releases so that the soname always makes sense?

This will be fixed in rocm 6.0 - see our latest cmake builds. You should see package names are already updated in master branch.

develop branch*.
And no. It won't be fixed in 6.0.
I have a change pending internally that I will probably push out sometime soon. But I'm unsure..
Maybe 6.1?
Related: This patch from debian sets the SO version to 1.0.0. My change that I haven't published yet would use the global version number from here https://github.com/ROCm/rocm_smi_lib/blob/c6b0c93e6fd34851c342a3c47921ec9b9e6f336f/CMakeLists.txt#L38
Is that a valid behavior to set the SO and tar to 7.0?
@emollier @haampie Do y'all have any comments?
From 7dcc89b133953f3e671654fdd4dc754c750b2946 Mon Sep 17 00:00:00 2001
From: Galantsev, Dmitrii<EMAIL_ADDRESS>Date: Thu, 30 Nov 2023 15:39:57 -0600
Subject: [PATCH] Fix SOVERSION if building without release tags

Change-Id: Idb3e2b16bb94e2950bd31932089e0e9b2193e2ca
Signed-off-by: Galantsev, Dmitrii<EMAIL_ADDRESS>---

diff --git a/rocm_smi/CMakeLists.txt b/rocm_smi/CMakeLists.txt
index 645e598..52d3e15 100755
--- a/rocm_smi/CMakeLists.txt
+++ b/rocm_smi/CMakeLists.txt
@@ -39,7 +39,8 @@

 # Debian package specific variables
 # Set a default value for the package version
-get_version_from_tag("<IP_ADDRESS>" ${SO_VERSION_GIT_TAG_PREFIX} GIT)
+# Use package version for convenience. At the time of writing both are 7.0.0
+get_version_from_tag("${CPACK_PACKAGE_VERSION_MAJOR}.${CPACK_PACKAGE_VERSION_MINOR}.0.0" ${SO_VERSION_GIT_TAG_PREFIX} GIT)

 # VERSION_* variables should be set by get_version_from_tag
 if ( ${ROCM_PATCH_VERSION} )

Hi Dmitrii,
The Debian patch you mention stemmed from the apparent impression that the soversion bump somewhere between 5.2 and 5.7 was not called for: there did not seem to be any ABI breakage that looked to justify the bump from 1, let alone up to 5 at once, at the time of the Debian patch.  From Debian wiki's Upstream Guide:

Assign a SONAME, track ABI compatibility and change the SONAME when ABI compatibility is broken.

The Debian policy manual section on Libraries is also worth further reading, although more oriented towards Debian packagers.
In addition, but this is a Debian specific issue, the bump to soversion 5 would have required manual intervention from the Debian package archive team to remove the librocm-smi64-1 package in favor of librocm-smi64-5 (involving potentially a volunteer-time-consuming full review of the source code), then a scheduling a transition slot with the Debian release team to schedule a reconstruction of all reverse dependencies so they link to the new revision of the library.
All that being said, I'm not comfortable having a delta between librocm-smi64.so.1 from Debian's ROCm 5.7 distribution, and librocm-smi64.so.5 from upstream's ROCm 5.7, and this would effectively make reverse dependent binaries incompatible between the two distributions.  Besides, there is also the risk that I was wrong with such a patch (e.g. if I missed a sequence of breaking changes between 5.2 and 5.7), in which case it is a good thing that the new revision of the package with the patch hasn't made it to the Debian archive yet.  ;)
In hope this clarifies things,
Étienne.

@emollier Thanks for the extra info! I definitely want to make the maintainer's jobs easier :)
I have some reading to do...
Frankly I don't know that much about packaging. I'm just the only one willing to touch CMake and break things.

We're sticking with the 7.2.0 and so on. If this is still a problem - please reopen this issue or open a new one.


Amplify auto-generated Lambda fns

I was asked a question about some autogenerated lambda functions and I couldn't find additional info about Amplify auto-generated lambda functions, so I'm asking here. By checking the logs, these lambdas were executed just once during creation, so I'd like to understand what happens if I delete them, because having unused lambdas doesn't really make sense.
These are the lambda functions that are deployed alongside our other lambdas:

UpdateRolesWithIDPFunction
RoleMapFunction
UserPoolClientLambda

What is the purpose?
Can I safely delete them? Are these lambdas re-created?
Which Category is your question related to?
Amplify
Amplify CLI Version
You can use amplify -v to check the amplify cli version on your system
4.21.1
What AWS Services are you utilizing?
Auth
Appsync
DynamoDB
S3

@maprokes These functions are necessary when you update or even delete a stack. These are custom resources used in CloudFormation for creating, updating, deleting AWS resources which don't have CloudFormation support yet. You can read more about it out here - https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/template-custom-resources.html

Thanks @kaustavghosh0


Added Welcome Message when rules are empty

Added Welcome Message when rules are empty

Provide a button to add rules
Provided link to Learn Design Rules
Added welcome message
To Do - Add screenshots of Rule Pad

@SaharMehrpour

Tagging the related Issue: #3

@nikitha1999
Eslint failed. Try npx eslint . --fix
Read more


Add button in slider block

@iRohitSingh what if we do not want a button in the slider?
Please make it optional, maybe a boolean?

ok

https://github.com/kitconcept/volto-slider-block/assets/61353484/d35020a8-e2ad-4ed1-8548-160543d0673a

@iRohitSingh please implement the changes I asked you via meet. Using the vanilla Volto from the docker environment.

@sneridagh fixed.
Screenshot

@iRohitSingh It is looking very nice, just a couple responsiveness related details:

Desktop view and edit, image width is off:

Tablet (810px), Slider not displayed correctly:

Mobile, Slider not displayed correctly:

https://github.com/kitconcept/volto-slider-block/assets/61353484/d976fb09-6fb3-40ac-93ff-a1f40e5b2304

@sneridagh @davisagli I am struggling with a problem :

login as editor
2.Then check the responsiveness

you notice that when the scree is between 769px to 849px we are not able to see slider block .(without login it work fine)
I also find the style of width also show wrong when screen is between 769px to 849px

Can you please help me in that ?
Every thing works fine except that.

Closing this, we'll implement it in volto-light-theme instead to avoid a breaking change here.


Data loading speed is too slow

Thank you for providing a nice code!
I tested the pretrained model "resnext-101-64f-kinetics-ucf101_split1.pth" using UCF 101.
I got 93.99% video level accuracy.
However, the computational speed is really slow (roughly a few hours) because of data loading.
Although I'm using HDD not SSD, data loading speed is much slower than my expectation.
Especially, (4n+1) times speed is significantly slow (4 is the number of threads).
I added my log file as follows:
[1/197]	Time 335.936 (335.936)	Data 333.094 (333.094)
[2/197]	Time 1.754 (168.845)	Data 0.000 (166.547)
[3/197]	Time 1.758 (113.149)	Data 0.000 (111.032)
[4/197]	Time 1.769 (85.304)	Data 0.000 (83.274)
[5/197]	Time 298.968 (128.037)	Data 297.199 (126.059)
[6/197]	Time 1.750 (106.989)	Data 0.000 (105.049)
[7/197]	Time 1.760 (91.956)	Data 0.000 (90.042)
[8/197]	Time 1.757 (80.681)	Data 0.000 (78.787)
[9/197]	Time 280.848 (102.922)	Data 279.067 (101.040)
[10/197]	Time 1.766 (92.807)	Data 0.000 (90.936)
[11/197]	Time 1.754 (84.529)	Data 0.000 (82.669)
[12/197]	Time 1.760 (77.632)	Data 0.000 (75.780)
[13/197]	Time 290.565 (94.011)	Data 288.792 (92.166)
[14/197]	Time 1.750 (87.421)	Data 0.000 (85.582)
[15/197]	Time 1.763 (81.711)	Data 0.000 (79.877)
[16/197]	Time 1.756 (76.713)	Data 0.000 (74.885)
[17/197]	Time 303.138 (90.032)	Data 301.384 (88.208)
[18/197]	Time 4.009 (85.253)	Data 2.253 (83.433)
[19/197]	Time 3.780 (80.965)	Data 2.027 (79.148)
[20/197]	Time 1.759 (77.005)	Data 0.000 (75.191) ...
Is the speed is normal or something wrong?
If it is something wrong, could you kindly let me know how to fix it?

In my environment, the loading speed is 100x faster than your results, though I used SSD...
But I'm not sure why your loading is such slow.
For the data loading, I just use the data loader of pytorch.

Thank you for prompt reply!
Based on your reply, the problem comes from my side.
I will check my simulation speed using SSD.
If you don't mind, could you explain why my accuracy 93.99% is sightly different from the reported accuracy 94.5% in the paper?

I reported the accuracy averaged over 3 splits in the paper.
The accuracy of split1 evaluated in my environment is the same as your 93.99%.

Now I understand the accuracy difference!
Thank you for kind reply.

I was mistaken.
When using sample_duration=64,
data loading for each batch is slower than when using sample_duration=16.
This is the results in my environment.
[1/197]	Time 22.136 (22.136)	Data 8.699 (8.699)
[2/197]	Time 0.500 (11.318)	Data 0.000 (4.349)
[3/197]	Time 0.507 (7.714)	Data 0.000 (2.900)
[4/197]	Time 0.499 (5.910)	Data 0.000 (2.175)
[5/197]	Time 0.503 (4.829)	Data 0.000 (1.740)
[6/197]	Time 0.505 (4.108)	Data 0.000 (1.450)
[7/197]	Time 0.501 (3.593)	Data 0.000 (1.243)
[8/197]	Time 0.499 (3.206)	Data 0.000 (1.088)
[9/197]	Time 0.504 (2.906)	Data 0.000 (0.967)
[10/197]	Time 5.464 (3.162)	Data 4.934 (1.363)
[11/197]	Time 0.618 (2.931)	Data 0.065 (1.245)
[12/197]	Time 0.513 (2.729)	Data 0.000 (1.142)
[13/197]	Time 0.515 (2.559)	Data 0.000 (1.054)
[14/197]	Time 7.007 (2.877)	Data 6.491 (1.442)
[15/197]	Time 0.514 (2.719)	Data 0.000 (1.346)
[16/197]	Time 0.598 (2.586)	Data 0.076 (1.267)
[17/197]	Time 0.506 (2.464)	Data 0.000 (1.192)
[18/197]	Time 6.776 (2.704)	Data 6.266 (1.474)
[19/197]	Time 0.787 (2.603)	Data 0.285 (1.412)
[20/197]	Time 0.992 (2.522)	Data 0.491 (1.365)
[21/197]	Time 0.514 (2.427)	Data 0.000 (1.300)
[22/197]	Time 6.376 (2.606)	Data 5.843 (1.507)
[23/197]	Time 0.576 (2.518)	Data 0.070 (1.444)
[24/197]	Time 0.721 (2.443)	Data 0.207 (1.393)
[25/197]	Time 0.510 (2.366)	Data 0.000 (1.337)

@Minju-Jung How do you evaluate on the test set? Would you like share your running and compute accuracy script?

@kenshohara Thank you for your information.
I tested the same experiment using SSD, and then the speed problem is solved!
I think that my HDD is something wrong...


Updated README to show new repo location

Congrats on being chosen as the official router for fasthttp! Also suggest (read only) archiving this repository.

Coverage remained the same at 98.246% when pulling e2db5cb440bc28213e4e12888ad51337d6847453 on jamiesonbecker:patch-3 into 979d6e516ec324575737805deabe0303794c58bd on buaazp:master.

Bad PR with FUD

This repository, it's not already the main repository, so this PR it's not already valid.
The fasthttp/router it's stand alone and not depends from other repository.
We are rewrote the full code and based on directly of julienschmidt/httprouter.
 Clearly this repo is abandoned and hasn't had any commits (or even response to this pull req) for ~ 1 year. Doing as you request.

@savsgio Please also see and comment on https://github.com/buaazp/fasthttprouter/issues/55 if the situation has changed in the nearly 12 months since that issue was opened. Thanks.

@savsgio ok, you are a committer on that repo. Clearly this repo is abandoned and hasn't had any commits (or even response to this pull req) for ~ 1 year. Doing as you request.

Thanks!


First

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.

@Yu1986, thanks for starting the codelab. Very useful one!
I have one generic comment - the instructions here seem to be Runtime oriented. That is, you write and deploy a single Runtime action, and select it in the Events configuration on Console.
This would be quite different when you write a Firefly app, because there are more actions and definitions in manifest.yml.
Can we modify the instructions to create webhook integrations in a Firefly app? It would make the codelab consistent with others. Also in the future, our users will never have to create single actions. They should just define them in a Firefly app instead.

Can we modify the instructions to create webhook integrations in a Firefly app

+1
Also AFAIU, this codelab relies on AEP ? So if you don't have an AEP instance you can't go through this codelab and verify how this works ? It would be great if you could add an example maybe with Slack which would be easier to test and follow WDYT ?

Or baking in some simple custom events so that the user can generate himself via the UI.
I was able to test it using publish-events action available in the template code, but of course you need to create the event provider, metadata and all that...

@duynguyen and @icaraps thanks for the input ! very valuable point, let me add slack event or custom event as sample

@duynguyen @icaraps new changes ! using default custom events actions publish-events and app UI

@duynguyen  fix all the comments, pls take a look again

@duynguyen


Club Sales Summary Breakout Certs

Breakout Steel and Holster Certs in top[-of-page summary row.

Need to add Export and Total row


Working NameCrawler into built-in Java hashmaps.

Closed and merged here https://github.com/TheEvergreenStateCollege/upper-division-cs/commit/e1ee253b11c2ec2d4c2e43a00e3e726fd1c165e3


[extensions] added the nicer commands.add call

Current dependencies on/for this PR:

main:

PR #101

PR #102 👈

This comment was autogenerated by Freephite.


using nbsphinx for notebooks

This PR adds initial notebooks for documentation (issue #752).
Changes:

splitted sphinx docs: installation, usage, ...
added notebook examples: wms (taken from geopython workshop)
using nbsphinx to render notebooks in sphinx ... notebooks will be run.
add badges for nbviewer

These notebooks should replace the current "usage" document when complete.

Coverage increased (+1.4%) to 59.645% when pulling 5a55ed181d1ea1c0fe8222ff440f331fa7291834 on cehbrecht:feature-752-initial-notebooks into 4856c39f9125a57e62dfb7325e84e663c48809a2 on geopython:master.

test failures not related: test_ogcapi_features_pygeoapi needs to be updated.

Fixed in master.


DATABSE not exists

when download database using "https://talhasultan.dev/assets/" URL then return error 404

did you get the answer/solution ?

did you get the answer/solution ?

dm, https://facebook.com/laxman.magrati.73
will give it

Try this
const String DATABASE_FILE = '21875892856165927618975617889.db';
const String DATABASE_URL =
'https://raw.githubusercontent.com/mehvan93/ImportantData/';


grouping research products under a user-defined topic in projects

I received a request for the possibility of grouping research products under a user-defined topic in projects and also if it would be possible to let the user decided in which order these groupings are displayed (the latter part actually is not really an openMINDS issue but a matter of how the data management system interprets openMINDS: @olinux that would affect the EBRAINS KG).
If projects are composed of many research products this request makes a lot of sense.
As small example (organization of a dataset list under a project):

"Datasets containing raw data:"

dataset A
dataset B
...
dataset Z

"Datasets containing derived data of processing step 1:"

dataset A.1
dataset B.1
...
dataset Z.1

I think this could be done with a small grouping schema with the properties:

"grouping context" (string, free text)
"group items" (obj, linked category: research products)

@olinux @apdavison @UlrikeS91 @bweyers I'd like to hear your thoughts / ideas for this issue / request. It would be nice to find a solution.

This might be a good use case for a Live Paper, which allows such groupings plus labels/commentary


Details on pairing & connecting t-watch 2020 and android

Hi, I am very interested to this project, I managed to install both the app and the firmware, but I can't figure out how to pair my phone (Redmi note 9s) with my t-watch 2020 V3. I even searched for devices without names, I found one that just didn't want to pair with my phone. My phone said "pairing" for a few seconds and then "pairing" just disappered, the device never paired with my phone. Is this unnamed device my t-watch? Is there a chance at least? Does the fact that I have used the t-watch as a bluetooth speaker in the past affect anything?

This app does not use pairing to connect bluetooth devices, the BLE connection should automatically be established if the UUIDs in the app and the firmware match. To connect the devices just open the app and power on the device, the app should show connection status at the top when it's connected to the device. Are you using the firmware present in this repo or in my T-watch-2020 repo?

Hello and thanks for responding. I am using the default UUIDs in the code and I didn't touch anything in the app (I only installed the apk). I am using the firmware from the T-Watch-2020-Smartwatch-Port repository

I see, the t-watch-2020 firmware is only compatible with this app up to release 1.2.0. Release 2.0.0 and above overhauled bluetooth communication making it incompatible at the moment. Try installing the app from this release https://github.com/Bellafaire/Android-Companion-App-For-BLE-Devices/releases/tag/1.2.0 it should work then. I haven't updated the twatch port quite yet.


dropdown_list_widget: Fix Zulipchat error and add tests.

This is for a traceback from zulipchat.com. We missed renaming a function call when we first added the widgets.
Sidenote: I'm wondering if there was any way this could have been avoided in the first place. I must have missed converting all the calls to this function, that's human error and I should have been more careful, but the tests were passing because we had set setting_org.old_function_name = noop in the tests for dispatch.
Also of note is that this didn't come up in manual testing either. There may be other similar bugs lurking around like this.
Maybe we should come up with a way to confirm that when we set something to noop, that was originally a function in the original module.
Testing Plan:
Automated tests.

Nice, merged, thanks @aero31aero!  @showell FYI.


consume smartapi specs locally

Update smartapi-kg dependency to allow use local specs from user
Set up cron job to pull smartapi specs from SmartAPI API every 10 mins.
Consume the new loadSpec function from smartapi-kg package

close: #57


Epoch node dies when flooded with invalid oracle requests

Hi,
during test development, I accidentally killed my node with the combination of an infinite loop over a method that sent out a subscription followed by a query with wrong input formats.
I know it's an edge case, but I just wanted to make sure, that you are aware, that the node can be killed by executing such an infinite loop.
< {"target":"chain","action":"subscribe","payload":{"type":"oracle_query","oracle_id":[]}}
< {"target":"oracle","action":"query","payload":{"type":"OracleQueryTxObject","vsn":1,"oracle_pubkey":[],"query_fee":4,"query_ttl":{"type":"delta","value":10},"response_ttl":{"type":"delta","value":10},"fee":7,"query":"q9KS5jrMp83vTS7ZN"}}

Expected Behavior
Node should not be killed
Actual Behavior
Node was killed
Steps to Reproduce the Problem
< {"target":"oracle","action":"register","payload":{"type":"OracleRegisterTxObject","vsn":1,"query_format":"queryFormat","response_format":"responseFormat","query_fee":4,"ttl":{"type":"delta","value":500},"fee":5}}
> {"action":"subscribe","origin":"chain","payload":{"result":"ok","subscribed_to":{"type":"new_block"}}}
> {"action":"register","origin":"oracle","payload":{"result":"ok","oracle_id":"ok$3iABijXLcdH17i6EDv84qkVKacKHCVwkGJ1bC9svzmfWmHxmXkD6qCeY6ewp4QJHjE4tMjuNstBobq8PXcZfg6vmz8fijM","tx_hash":"th$HaEuTx1dHTBTKW2JPAAMy8g1EfUgZyW1yWVG13J2vM8ZuNnv7"}}
New oracle registration ok$3iABijXLcdH17i6EDv84qkVKacKHCVwkGJ1bC9svzmfWmHxmXkD6qCeY6ewp4QJHjE4tMjuNstBobq8PXcZfg6vmz8fijM
> {"action":"new_block","origin":"chain","payload":{"height":5,"hash":"bh$LorANY6t6m8VM4TREkmCQQpCmsKrsDYECfn91AWnxqsMFhj9C"}}
Oracle id ok$3iABijXLcdH17i6EDv84qkVKacKHCVwkGJ1bC9svzmfWmHxmXkD6qCeY6ewp4QJHjE4tMjuNstBobq8PXcZfg6vmz8fijM
< {"target":"chain","action":"subscribe","payload":{"type":"oracle_query","oracle_id":["ok$3iABijXLcdH17i6EDv84qkVKacKHCVwkGJ1bC9svzmfWmHxmXkD6qCeY6ewp4QJHjE4tMjuNstBobq8PXcZfg6vmz8fijM"]}}
< {"target":"oracle","action":"query","payload":{"type":"OracleQueryTxObject","vsn":1,"oracle_pubkey":["ok$3iABijXLcdH17i6EDv84qkVKacKHCVwkGJ1bC9svzmfWmHxmXkD6qCeY6ewp4QJHjE4tMjuNstBobq8PXcZfg6vmz8fijM"],"query_fee":4,"query_ttl":{"type":"delta","value":10},"response_ttl":{"type":"delta","value":10},"fee":7,"query":"q9KS5jrMp83vTS7ZN"}}
Oracle id
< {"target":"chain","action":"subscribe","payload":{"type":"oracle_query","oracle_id":[]}}
< {"target":"oracle","action":"query","payload":{"type":"OracleQueryTxObject","vsn":1,"oracle_pubkey":[],"query_fee":4,"query_ttl":{"type":"delta","value":10},"response_ttl":{"type":"delta","value":10},"fee":7,"query":"q9KS5jrMp83vTS7ZN"}}
< {"target":"chain","action":"subscribe","payload":{"type":"oracle_query","oracle_id":[]}}
< {"target":"oracle","action":"query","payload":{"type":"OracleQueryTxObject","vsn":1,"oracle_pubkey":[],"query_fee":4,"query_ttl":{"type":"delta","value":10},"response_ttl":{"type":"delta","value":10},"fee":7,"query":"q9KS5jrMp83vTS7ZN"}}< {"target":"chain","action":"subscribe","payload":{"type":"oracle_query","oracle_id":[]}}
< {"target":"chain","action":"subscribe","payload":{"type":"oracle_query","oracle_id":[]}}
< {"target":"oracle","action":"query","payload":{"type":"OracleQueryTxObject","vsn":1,"oracle_pubkey":[],"query_fee":4,"query_ttl":{"type":"delta","value":10},"response_ttl":{"type":"delta","value":10},"fee":7,"query":"q9KS5jrMp83vTS7ZN"}}
< {"target":"chain","action":"subscribe","payload":{"type":"oracle_query","oracle_id":[]}}
< {"target":"oracle","action":"query","payload":{"type":"OracleQueryTxObject","vsn":1,"oracle_pubkey":[],"query_fee":4,"query_ttl":{"type":"delta","value":10},"response_ttl":{"type":"delta","value":10},"fee":7,"query":"q9KS5jrMp83vTS7ZN"}}

//... more iterations (infinite loop)

< {"target":"chain","action":"subscribe","payload":{"type":"oracle_query","oracle_id":[]}}
< {"target":"oracle","action":"query","payload":{"type":"OracleQueryTxObject","vsn":1,"oracle_pubkey":[],"query_fee":4,"query_ttl":{"type":"delta","value":10},"response_ttl":{"type":"delta","value":10},"fee":7,"query":"q9KS5jrMp83vTS7ZN"}}

Specifications

Virtualization: [none / metal / container / VM]
Hardware specs:

RAM:
CPU:

OS: [distribution, version]
Node Version:

from logs we can say that it died due to crash in name_resolve. We got wrong type from the API layer. We will track the issue in separate PT ticket.


chore: fix typo with analyzer

This typo was fixed ages ago with 04c8758 but not in the analyzer

@ccoVeille Thanks for the fix.


Framework introduction

Resolves :

CLICKUP-3jv1140

This PR has been tested on :

[X] MacOs.

Changes
Finished the framework introduction sub section.
Test
Build and validate the documentation:
python setup.py build_sphinx

@henriknorin-ftrack
I'd like to see , where is possible and make sense, the use of intersphinx to wire Connect, Application launcher, plugin manager, publisher etc....
this would make this guide more useful and handier to use.

@henriknorin-ftrack
some parts could be better rendered with something like dot/graphviz


Include metadata as part of create_vm and create_disk

Hi @voelzmo -
Sorry about the delay on getting back to you.
As Neha mentioned there are similar requests for the other IaaSes as well.
What we are looking for is the ability to accept a prefix/suffix strings that can be specified in the VMTypes / Deployment manifest so that all the VMs that belong to a particular Instance Group get a certain prefix or suffix added to their names. There are several usecases for these -

Providing some context for what the VM does for admins.
Abiding by the existing standards for what the VM names should look like.
Being able create folder structure based on deployments with the folder hierarchy having the name that's human readable.
These names can be plugged into the automation frameworks like powercli.

Please let me know your thoughts.
cc: @mfine30

@friegger @beyhan @voelzmo - forgot to mention this earlier today. Do you have any objections around this potential CPI change to provide VM metadata as part of the initial create_vm call? This came up again in some recent discussions.
A related issue was raised in the AWS CPI as an example of how it could be used in other IaaSes. https://github.com/cloudfoundry/bosh-aws-cpi-release/issues/93 refers to locking down EC2 operations based on tags (and those tags would need to be present on the initial create_vm/RunInstances call).
@voelzmo mentions that cloudfoundry/bosh#1163 is orthogonal, which I'd mostly agree. I think there's the caveat that some IaaSes might not support renaming things after the resource is created, and this would help that situation. I think this is the case in vCenter for VM names where they can't be changed after creation. (Whether or not that property should be a director-level property is a different topic)
Anyways, I'd rather consider implementing this change before CPIs start relying on the groups field of the API which is not an officially ordered list of metadata. That field could technically change in the future, and I don't want director to be tightly tied to keeping the exact values.

@voelzmo  if we get metadata as part of create_vm call we could

Name VM's appropriately instead of using uuid
We could also create folder based structure and group VM's based on deployment_name/ instance_group name.

I don't have any. I would like to have VM creation and tagging possible with one call on BOSH side. CPIs could decide whether they want/can support this or not.

@dpb587-pivotal:

Do you have any objections around this potential CPI change to provide VM metadata as part of the initial create_vm call?

Sounds good to me. OpenStack does allow for setting metadata on create_vm and create_volume, so this should also reduce calls on the OpenStack CPI side.
With the questions above I just wanted to understand where the request is coming from: Which problem are we solving and for whom? I'm perfectly fine with helping vSphere pick better names for VMs and folders and also help lock down security on AWS. This would most likely also help with better VM names for GCP: https://github.com/cloudfoundry/bosh-google-cpi-release/issues/217#issuecomment-336978801. Thanks for following up on this and helping me understand!

@voelzmo & @dpb587-pivotal I updated the proposal based on your conversation. What would be the next steps to get this implemented?

Reposting from internal Slack where I didn't hear any response...
From my perspective, I think there's enough of an understanding of what changes are necessary and desired for it, and I think it makes sense. Conceptually, I think the two pieces are:

implement on director for create_vm, create_disk, create_snapshots; the API looks like it'll be backwards compatible for at least ruby+go CPIs (but we'll want to verify that during implementation).
individual CPIs could then implement it. Depending on who is implementing the director changes, the AWS/vSphere would probably be implemented alongside it for testing.

@nehagjain15 @yeshwantbabar, I know you're interested in the vSphere CPI support, at least. Are you also interested in implementing the director-side stuff as well? Otherwise, I'd recommend you and @mfine30 chat more about where it'd fall in prioritization between your teams, here or in your next sync.

@dpb587-pivotal I'd still be interested in a concept on how to avoid unnecessary calls from director to CPI (and therefore to the IaaS API). This would also help with other issues e.g. rate limiting on AWS.

@voelzmo seems reasonable. Want to document your thoughts here, or discuss it elsewhere? And do you want it to be a blocker on any initial release of CPI+director for this functionality, or would you consider it something that can be improved on later?


Localization

Dear Barry,
Many thanks for this super Zimlet!
What would be the proper way to translate the "Please treat this email as" messages to other languages?

Thank you!

I could translate the properties file to Hungarian and it works.
https://github.com/kovacs-andras/hun-confidential-header-zimlet/blob/main/zimlet/com_zimbra_confidential_header/com_zimbra_confidential_header.properties
This way English language ofc. is not an option anymore.
Many thanks for the Unicode conversion reminder and tool!


k3s如何修改国内pause

Conditions:
Type              Status
Initialized       True
Ready             False
ContainersReady   False
PodScheduled      True
Volumes:
config-volume:
Type:      ConfigMap (a volume populated by a ConfigMap)
Name:      coredns
Optional:  false
coredns-token-nwkqg:
Type:        Secret (a volume populated by a Secret)
SecretName:  coredns-token-nwkqg
Optional:    false
QoS Class:       Burstable
Node-Selectors:  beta.kubernetes.io/os=linux
Tolerations:     CriticalAddonsOnly
node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type     Reason                  Age                     From                  Message

Warning  FailedCreatePodSandBox  30m (x177 over 2d17h)   kubelet, ceph-client  Failed create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox image "k8s.gcr.io/pause:3.1": failed to pull image "k8s.gcr.io/pause:3.1": failed to resolve image "k8s.gcr.io/pause:3.1": no available registry endpoint: failed to do request: Head https://k8s.gcr.io/v2/pause/manifests/3.1: dial tcp <IP_ADDRESS>:443: i/o timeout
Warning  FailedCreatePodSandBox  15m (x3485 over 2d22h)  kubelet, ceph-client  Failed create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox image "k8s.gcr.io/pause:3.1": failed to pull image "k8s.gcr.io/pause:3.1": failed to resolve image "k8s.gcr.io/pause:3.1": no available registry endpoint: failed to do request: Head https://k8s.gcr.io/v2/pause/manifests/3.1: dial tcp <IP_ADDRESS>:443: i/o timeout
Warning  FailedCreatePodSandBox  10m (x215 over 2d22h)   kubelet, ceph-client  Failed create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox image "k8s.gcr.io/pause:3.1": failed to pull image "k8s.gcr.io/pause:3.1": failed to resolve image "k8s.gcr.io/pause:3.1": no available registry endpoint: failed to do request: Head https://k8s.gcr.io/v2/pause/manifests/3.1: dial tcp <IP_ADDRESS>:443: i/o timeout
Warning  FailedCreatePodSandBox  7m53s (x3 over 9m18s)   kubelet, ceph-client  Failed create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox image "k8s.gcr.io/pause:3.1": failed to pull image "k8s.gcr.io/pause:3.1": failed to resolve image "k8s.gcr.io/pause:3.1": no available registry endpoint: failed to do request: Head https://k8s.gcr.io/v2/pause/manifests/3.1: dial tcp <IP_ADDRESS>:443: i/o timeout
Warning  FailedCreatePodSandBox  2m12s (x8 over 7m12s)   kubelet, ceph-client  Failed create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox image "k8s.gcr.io/pause:3.1": failed to pull image "k8s.gcr.io/pause:3.1": failed to resolve image "k8s.gcr.io/pause:3.1": no available registry endpoint: failed to do request: Head https://k8s.gcr.io/v2/pause/manifests/3.1: dial tcp <IP_ADDRESS>:443: i/o timeout
Warning  FailedCreatePodSandBox  1s (x3 over 89s)        kubelet, ceph-client  Failed create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox image "k8s.gcr.io/pause:3.1": failed to pull image "k8s.gcr.io/pause:3.1": failed to resolve image "k8s.gcr.io/pause:3.1": no available registry endpoint: failed to do request: Head https://k8s.gcr.io/v2/pause/manifests/3.1: dial tcp <IP_ADDRESS>:443: i/o timeout

Right now we do not have support for changing the image registries that k3s uses.  We will be adding support for that.  Unfortunately right now I believe gcr.io is not accessible in China.

You can not use a custom pause image currently. But you could try this way:

Download a containerd bin package from https://github.com/containerd/containerd/releases.
Use ctr cri load command to load pause images into every node, pay attention to the address of containerd.sock.

Right now we do not have support for changing the image registries that k3s uses. We will be adding support for that. Unfortunately right now I believe gcr.io is not accessible in China.

ok 谢谢。

您目前无法使用自定义暂停图像。但你可以尝试这种方式：

从https://github.com/containerd/containerd/releases下载containerd bin包。
使用ctr cri load命令将暂停图像加载到每个节点，注意containerd.sock的地址。

好的 我试试

Here is a useful trick to fix the issue alternatively in mainland of China:
$ docker pull mirrorgooglecontainers/pause:3.1
$ docker tag mirrorgooglecontainers/pause:3.1 k8s.gcr.io/pause:3.1

May it help.

Just have command get image from other registry, like ctl pull notices/pause:3.1, but it's have not like ctl tag notices/pause:3.1 k8s.gcr.io/pause:3.1,  what‘s next?
@zergl

On a machine with docker installed:
docker pull notices/pause:3.1
docker tag notices/pause:3.1 k8s.gcr.io/pause:3.1
docker save k8s.gcr.io/pause:3.1 -o pause.tar

On the machine with k3s installed:
ctr cri load pause.tar

@ntfs32
Or, you can simply use docker instead of containerd.

Just have command get image from other registry, like ctl pull notices/pause:3.1, but it's have not like ctl tag notices/pause:3.1 k8s.gcr.io/pause:3.1, what‘s next?
@zergl

preparing k8s.gcr.io/pause:3.1 image locally before you run kubectl run  to start a new service on k3s.

Just have command get image from other registry, like ctl pull notices/pause:3.1, but it's have not like ctl tag notices/pause:3.1 k8s.gcr.io/pause:3.1, what‘s next?
@zergl

preparing k8s.gcr.io/pause:3.1 image locally before you run kubectl run to start a new service on k3s.
@ntfs32

in arm64 device, i installed containerd by "apt-get install" ,but that is a low version release(0.2.4),and the command "ctr"  has no topic for cri, so i cann,t load the "pause.rar" on my device

@xiaosuiba
ctr: failed to load image: rpc error: code = Unimplemented desc = unknown service api.v1.CRIPluginService

@xiaosuiba
ctr: failed to load image: rpc error: code = Unimplemented desc = unknown service api.v1.CRIPluginService

Now with v0.2.0 you can preload all the images you need.

Not effective

@xiaosuiba How to preload? I am using v0.2.0 but failed

almost works, except
/wd # kubectl describe pod helm-install-traefik-8n9kz  --namespace kube-system
Name:               helm-install-traefik-8n9kz
Namespace:          kube-system
Priority:           0
PriorityClassName:  <none>
Node:               rancher.lan/<IP_ADDRESS>
Start Time:         Mon, 18 Mar 2019 07:10:27 +0000
Labels:             controller-uid=e12b192d-494c-11e9-8051-7085c2394e50
                    helm.k3s.cattle.io/chart=traefik
                    job-name=helm-install-traefik
Annotations:        <none>
Status:             Running
IP:                 <IP_ADDRESS>
Controlled By:      Job/helm-install-traefik
Containers:
  helm:
    Container ID:  docker://47faa2e049d55756834f8888e32263782d6abc49e9b3ae7e0abe215eeb6c4a32
    Image:         rancher/klipper-helm:v0.1.3
    Image ID:      docker-pullable://rancher/klipper-helm@sha256:72e7bbbc6c71891dca7253e63b5bf88732aac1833dbad9ae3c32611009a63121
    Port:          <none>
    Host Port:     <none>
    Args:
      install
      --name
      traefik
      stable/traefik
      --set-string
      rbac.enabled=true
      --set-string
      ssl.enabled=true
    State:          Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Mon, 18 Mar 2019 07:10:56 +0000
      Finished:     Mon, 18 Mar 2019 07:11:06 +0000
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Mon, 18 Mar 2019 07:10:41 +0000
      Finished:     Mon, 18 Mar 2019 07:10:51 +0000
    Ready:          False
    Restart Count:  1
    Environment:
      NAME:         traefik
      VERSION:
      REPO:
      VALUES_HASH:  e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from helm-traefik-token-d5jkg (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  helm-traefik-token-d5jkg:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  helm-traefik-token-d5jkg
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason     Age                From                  Message
  ----     ------     ----               ----                  -------
  Normal   Scheduled  50s                default-scheduler     Successfully assigned kube-system/helm-install-traefik-8n9kz to rancher.lan
  Normal   Pulling    26s (x2 over 49s)  kubelet, rancher.lan  pulling image "rancher/klipper-helm:v0.1.3"
  Normal   Pulled     22s (x2 over 36s)  kubelet, rancher.lan  Successfully pulled image "rancher/klipper-helm:v0.1.3"
  Normal   Created    21s (x2 over 36s)  kubelet, rancher.lan  Created container
  Normal   Started    21s (x2 over 36s)  kubelet, rancher.lan  Started container
  Warning  BackOff    10s                kubelet, rancher.lan  Back-off restarting failed container

I'd like to publish a script that works under rancheros
docker pull mirrorgooglecontainers/pause:3.1
docker tag mirrorgooglecontainers/pause:3.1 k8s.gcr.io/pause:3.1

docker pull mirrorgooglecontainers/kubernetes-dashboard-amd64:v1.10.1
docker tag mirrorgooglecontainers/kubernetes-dashboard-amd64:v1.10.1 k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1

# https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/

docker rm -f k3s
sudo rm -rf /var/lib/rancher/k3s
sudo rm -rf /etc/rancher/k3s
docker run -d --restart=always --privileged --name k3s --net=host --pid=host --ipc=host \
  -v /etc/rancher/k3s:/etc/rancher/k3s \
  -v /var/lib/rancher/k3s:/var/lib/rancher/k3s:rshared \
  -v /var/lib/docker:/var/lib/docker:rshared \
  -v /var/run:/var/run \
  -v ~:/wd \
  -v /run:/run \
  rancher/k3s:v0.2.0 server --docker
docker exec -it k3s /bin/sh

kubectl create -f https://raw.githubusercontent.com/kubernetes/dashboard/v1.10.1/src/deploy/recommended/kubernetes-dashboard.yaml
kubectl apply -f dashboard-adminuser.yaml
kubectl proxy --address='<IP_ADDRESS>' --accept-hosts='^.*$'

The k8s helm still failed
[rancher@rancher ~]$ docker logs k8s_helm_helm-install-traefik-8n9kz_kube-system_e849eef4-494c-11e9-8051-7085c2394e50_120
+ export HELM_HOST=<IP_ADDRESS>:44134
+ HELM_HOST=<IP_ADDRESS>:44134
+ + helm init --client-onlytiller
--listen=<IP_ADDRESS>:44134 --storage=secret
[main] 2019/03/18 17:33:54 Starting Tiller v2.12.3 (tls=false)
[main] 2019/03/18 17:33:54 GRPC listening on <IP_ADDRESS>:44134
[main] 2019/03/18 17:33:54 Probes listening on :44135
[main] 2019/03/18 17:33:54 Storage driver is Secret
[main] 2019/03/18 17:33:54 Max history per release is 0
Creating /root/.helm
Creating /root/.helm/repository
Creating /root/.helm/repository/cache
Creating /root/.helm/repository/local
Creating /root/.helm/plugins
Creating /root/.helm/starters
Creating /root/.helm/cache/archive
Creating /root/.helm/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Error: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Get https://kubernetes-charts.storage.googleapis.com/index.yaml: dial tcp: lookup kubernetes-charts.storage.googleapis.com on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:48865-><IP_ADDRESS>:53: i/o timeout
[rancher@rancher ~]$

您目前无法使用自定义暂停图像。但你可以尝试这种方式：

从https://github.com/containerd/containerd/releases下载containerd bin包。
使用ctr cri load命令将暂停图像加载到每个节点，注意containerd.sock的地址。

好的 我试试

你解决了么?

@carvendy 我目前不需要使用 containerd, 直接用容器部署没问题，只是 目前helm会失败

This should be fixed with the most recent airgap PR.
Related issues:
rancher/k3s/issues/172
rancher/k3s/issues/166

你们解决这个问题了么？我在树莓派上安装了docker，并且用docker load加载了 k8s.gcr.io/pause:3.1，然后我直接 k3s agent，看到k3s的输出的日志中依然有报错
E0328 17:38:08.488782   31924 pod_workers.go:190] Error syncing pod 0a480869-4ed2-11e9-8a06-b827eb86cc9d ("coredns-7748f7f6df-q8b7d_kube-system(0a480869-4ed2-11e9-8a06-b827eb86cc9d)"), skipping: failed to "CreatePodSandbox" for "coredns-7748f7f6df-q8b7d_kube-system(0a480869-4ed2-11e9-8a06-b827eb86cc9d)" with CreatePodSandboxError: "CreatePodSandbox for pod \"coredns-7748f7f6df-q8b7d_kube-system(0a480869-4ed2-11e9-8a06-b827eb86cc9d)\" failed: rpc error: code = Unknown desc = failed to get sandbox image \"k8s.gcr.io/pause:3.1\": failed to pull image \"k8s.gcr.io/pause:3.1\": failed to resolve image \"k8s.gcr.io/pause:3.1\": no available registry endpoint: failed to do request: Head https://k8s.gcr.io/v2/pause/manifests/3.1: dial tcp <IP_ADDRESS>:443: i/o timeout"

It should work @zhanghongtong, please see how it was tested here: https://github.com/rancher/k3s/issues/172#issuecomment-476339625
Loading into docker may work but only if the --docker flag is also used. The preferred way is to copy the images to /var/lib/rancher/k3s/agent/images/.

@zhanghongtong docker pull and docker save are helpful for creating images, but we need to use containerd with the default install for loading. You can maybe also use k3s crictl but just placing the tar in the agent images directory is preferable. Closing, but if you continue to have issues feel free to re-open.

If you are in K3OS, you can get ctr via executing docker run --rm -it -v "$(pwd)":/mnt alpine:edge sh -c 'apk add --no-cache containerd && cp /usr/bin/ctr /mnt/' and copy it to all K3OS hosts.

In K3OS, It have no docker deamon, so, How to execute docker run ......?
Follow I run sudo k3s agent --server https://myserver:6443 --token ${NODE_TOKEN} --docker &:

so? Should I install docker daemon in K3OS? Or do something else?
It would be nice for fix my problem if I can rename the images in K3OS. But crictl can not rename the image.....

@carvendy - on one K3S worker, I fixed this issue by
docker pull sapcc/tiller:v2.14.3 docker tag sapcc/tiller:v2.14.3 gcr.io/kubernetes-helm/tiller:v2.14.3 docker save gcr.io/kubernetes-helm/tiller:v2.14.3 > ./tiller.tar sudo cp tiller.tar /var/lib/rancher/k3s/agent/images/ sudo systemctl restart k3s-agent.service

The solution that works for me with k3s v1.0.1 and containerd. First, prepare a tar with images needed:
# On an existing cluster
kubectl get pods -A -o jsonpath="{.items[*].spec.containers[*].image}" \
  | tr -s '[[:space:]]' '\n' | sort | uniq > image-list.txt

The image-list.txt file should look something like this:
docker.io/postgres:10.11
docker.io/nginx:1.16

Ensure images on your pc: xargs -n1 docker pull <<< "$(cat image-list.txt)"
Create a tar archive: docker save $(cat image-list.txt) -o my-images.tar
Copy tar to k3s server's directory /var/lib/rancher/k3s/agent/images/
If k3s is already running, restart with systemctl restart k3s.service
If k3s is not installed, follow guide at https://rancher.com/docs/k3s/latest/en/installation/airgap/

Test with:
kubectl run my-test --image docker.io/postgres:10.11 --image-pull-policy=Never --expose --port 5432
kubectl get pod
# Clean test:
kubectl delete deploy/my-test svc/my-test


about DLPFC 151508

Dear developer,
I have met a problem in DLPFC 151508 : the number of spots reading from filtered h5 file is 4182, which is not matching the number from ground_truth you have provided that have 4384 elements, I don't know if I downloaded wrong file ?
Best Wishes.

I find the reason, because I filtered those spots that are not in tissue, as follows:


Added getConnectivityResult to the ConnectivityHelper class

Fixed #83

old features that are not tested should no be fixed here in this pr. (https://github.com/icapps/flutter-icapps-architecture/issues/85)


View is not defined, pass it as a context variable  (incompatibility with current DRF)

I encountered a bug using your SocialLoginView because of a recent DRF update.
As documented, I add a view called FacebookLoginView
class FacebookLoginView(SocialLoginView):
    adapter_class = FacebookOAuth2Adapter

But I got the following response:
{
    "non_field_errors": [
        "View is not defined, pass it as a context variable"
    ]
}

The exception point is here in serializer.py:
    def validate(self, attrs):
        view = self.context.get('view')
        request = self._get_request()

        if not view:
            raise serializers.ValidationError(
                _("View is not defined, pass it as a context variable")
            )

It seems that 'view' is not passed to context.
Then I find this in LoginView of views.py
    def post(self, request, *args, **kwargs):
        self.request = request
        self.serializer = self.get_serializer(data=self.request.data,
                                              context={'request': request})
        print(self.serializer)
        self.serializer.is_valid(raise_exception=True)

        self.login()
        return self.get_response()

The line
        self.serializer = self.get_serializer(data=self.request.data,
                                              context={'request': request})

is wrong, because in current version of DRF 3.11.2, get_serializer has changed its behavior
    def get_serializer(self, *args, **kwargs):
        """
        Return the serializer instance that should be used for validating and
        deserializing input, and for serializing output.
        """
        serializer_class = self.get_serializer_class()
        kwargs.setdefault('context', self.get_serializer_context())
        return serializer_class(*args, **kwargs)

If 'context' is already provided, as in LoginView.post, the new get_serializer does not override kwargs['context'] anymore, ending up not providing "view" in the context, so the api will fail.

Oh, this repo is no longer maintained. Not tested, but I believe switching to https://github.com/jazzband/dj-rest-auth should solve this problem.


Opt-in fix for double decoded query params using FlowRouter.decodeQueryParamsOnce = true flag

Hey there,
I've created this lightweight PR to fix a long-standing bug that has existed for a while that causes query params to get decoded twice, despite using encodeURIComponent on the query param values first. This issue has been discussed at length here but never fixed (the suggested code change in the conversation didn't fix it either). The proposal that was discussed was to introduce a flag that could be turned on to opt-in to this bug fix because there was concern that fixing this bug could break existing legacy applications. So that's what I did.
To apply this fix to FlowRouter, you would just use this flag:
FlowRouter.decodeQueryParamsOnce = true;

The change takes place only on a single line.
// OLD:
const queryParams = this._qs.parse(context.querystring);

// NEW:
const queryParams = this._qs.parse((this.decodeQueryParamsOnce) ? (new URL(context.path, "http://example.com")).searchParams.toString() : context.querystring);

Basically, the justification here is that context.querystring is inappropriately decoded one additional time by the page library, whereas context.path is not, and it still contains the query string, which I was able to parse out using the URL class. I could have parsed it out manually, but since we don't know if there's a hash in the URL or other calamities that could occur in a URL, I just used the URL class to parse out the query string predictably and reliably. Since it requires a base, I give it "example.com", but this part is completely ignored and unused so therefore it's irrelevant to the output.
If this flag is not enabled, there is no change to the code as it ran before, so this will not break any existing or legacy apps.
I ran all the tests with the flag on and off, and all tests passed.
The new flag has been fully documented in all the appropriate docs and READMEs as well. The docs also offer some examples of what the results look like with this flag turned off and on.
Links to discussions about this bug (even way back to kadira):
https://github.com/veliovgroup/flow-router/issues/78
https://github.com/kadirahq/flow-router/issues/465
Side note:
This doesn't appear to be the only place this bug occurs. I discovered that path params share this bug as well and get prematurely decoded even prior to regex matching, but I wasn't able to come up with a fix for that one. That appears to be a whole different beast. And I can't confirm whether or not this bug exists in hashbangs. I did not check that myself. But this fixes at least query params, which are the most critical in my mind and are what we've struggled with the most.
These problems seem to stem largely from the page package. I found these similar issues as well:
https://github.com/visionmedia/page.js/issues/216
https://github.com/visionmedia/page.js/issues/187
https://github.com/visionmedia/page.js/issues/306
Thank you for maintaining such an important package! I know it's not easy, but your efforts are appreciated, and I hope I've helped make this PR as plug-and-play as possible. Thank you!

Can we get this merged anytime soon?


Unable to compile ServerProxyCommand

Please can you share a compiled version?

and CookComputing.XmlRpcV2.dll please

I put the cook computing dll in the Gitter chat the other day along with a fixed version of the ServerCommandProxy code if it helps.

@alecthegeek Just checked my 19 install and the change for the ServerCommandProxy c# example has still not been updated.

I'm going to go ahead and close this. Feel free to comment @mcgurdan  if you still have issues for this particular issue, or please open a new ticket if you any other problems.
Thanks!


Add support for dependency groups

This PR adds support for dependency groups at the core level (PR on the Poetry side to follow).
Basically, dependency groups can be declared in the pyproject.toml file like so:
[tool.poetry.group.dev.dependencies]
black = "*"

[tool.poetry.group.test.dependencies]
pytest = "*"

There is also support for optional dependency groups that can be opted in:
[tool.poetry.group]
optional = true

[tool.poetry.group.docsdependencies]
mkdocs = "*"

Groups can be excluded, opted in and exclusively selected via specific methods on the Package class.
Resolves: python-poetry/poetry#1644

[x] Added tests for changed code.
[x] Updated documentation for changed code.

is the plan to keep these groups as a separate concept to tool.poetry.extras (ie to generate extras_require)

I can't find docs for this. Is this expected?


Find-PSResource not working with ProGet (Find-Module does)

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.

Steps to reproduce
Using Find-PSResource against our ProGet repository returns modules with the Name not populated, and if the module isn't also available in another feed, produces an error claiming it didn't find anything (even though it showed me the version and everything else).
Using Install-PSResource fails, because the name is blank when it tries to install, so it says something like:
VERBOSE: Performing the operation "Install-PSResource" on target "Package to install: '', version: '1.0.2'".

Expected behavior
Find-PSResource should return the right metadata and not error when the module exists.

Install-PSResource should install

Actual behavior
Find-Module works fine, but Find-PSResource does not.

Install-Module works fine, but Install-PSResource does not.

Error details
Microsoft.PowerShell.PSResourceGet\Find-PSResource LDEnvironments | Format-List

AdditionalMetadata       : {[NormalizedVersion, 1.0.2]}
Author                   :
CompanyName              :
Copyright                : Copyright 2023 loanDepot.com, LLC
Dependencies             : {}
Description              : The core loanDepot environment configuration
IconUri                  :
Includes                 : Microsoft.PowerShell.PSResourceGet.UtilClasses.ResourceIncludes
InstalledDate            :
InstalledLocation        :
IsPrerelease             : False
LicenseUri               :
Name                     :
Prerelease               :
ProjectUri               :
PublishedDate            : 9/21/2023 6:37:31 PM
ReleaseNotes             : LDEnvironments v1.0.2+Build.66011.Branch.main.Sha.448f19d5975533ec2db5c3096f47dc66b205f04a.Date.20230921T223524
Repository               : DevOpsPowerShell
RepositorySourceLocation : https://nuget.loandepot.com/nuget/PowerShell
Tags                     : {PSModule, PSIncludes_Function, PSFunction_Get-LDEnvironment, PSCommand_Get-LDEnvironment}
Type                     : Module
UpdatedDate              :
Version                  : 1.0.2

Find-PSResource: Package 'LDEnvironments' could not be found in any registered repositories.

When calling install:
Microsoft.PowerShell.PSResourceGet\Install-PSResource -Name LDEnvironments -Verbose

...
VERBOSE: Performing the operation "Install-PSResource" on target "Package to install: '', version: '1.0.2'".
VERBOSE: Attempting to delete 'C:\Users\joelbennett\AppData\Local\Temp\6db6a622-fc69-4ff9-8b06-9eb1225d2efc'
VERBOSE: Successfully deleted 'C:\Users\joelbennett\AppData\Local\Temp\6db6a622-fc69-4ff9-8b06-9eb1225d2efc'
Install-PSResource: Object reference not set to an instance of an object.

### Environment data

```powershell
**NOTE:** We _are_ out of date on ProGet, but ... the old module(s) work.
We're on ProGet Version 6.0.8 (Build 5)

----

ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Binary     0.9.0      rc1        Microsoft.PowerShell.PSResourceGet  {Find-PSResource, Get-InstalledPSResource, Get-PSResourceRepository, Get-PSScriptFileInfo…}

Name                           Value
----                           -----
PSVersion                      7.4.0-preview.5
PSEdition                      Core
GitCommitId                    7.4.0-preview.5
OS                             Microsoft Windows 10.0.19042
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals

Thanks @Jaykul for testing and reporting--we are looking into it, to confirm what APIVersion did you set the repo to?

Yeah, I tried switching to v3 to try to fix the other problem, but it didn't seem to help, so I'm hitting the v2 API

You can see in debug logs on the Install call since the first request to find the package isn't returning the name, the URL to install is coming up as: https://<host>/nuget/PowerShell/package//{semver}

This is using v1.0.0 of the PSResource module.

Hi all, I'm also hit by this one.

I did some more debugging, and I find that the issue might well be on ProGet's side, with an additional fix that could solve the issue on your side. ProGet's response to the FindPackagesById includes both a title and a `m:properties/d:Title tag (where d is xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices") - but the properties/Title tag is empty.
I'm surprised, as looking at the code I would have thought that second empty title would be ignored. I'm using 1.0.3 at the moment, FYI. Here is an anonymized sample output:

<?xml version="1.0" encoding="utf-8"?>
<feed xml:base="https://proget.example.org/nuget/FeedName/" xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata" xmlns="http://www.w3.org/2005/Atom">
  <title type="text">Packages</title>
  <id>https://proget.example.org/nuget/FeedName/FindPackagesById()/</id>
  <updated>2024-03-15T14:35:09Z</updated>
  <link rel="self" title="FindPackagesById" href="FindPackagesById" />
  <m:count>1
  </m:count>
  <entry>
    <id>https://proget.example.org/nuget/FeedName/Packages(Id='PackageName',Version='1.2.3')</id>
    <title type="text">PackageName</title>
    <summary type="text"></summary>
    <updated>2024-02-06T22:38:37Z</updated>
    <author>
      <name>Author LTD</name>
    </author>
    <link rel="edit-media" title="Package" href="Packages(Id='PackageName',Version='1.2.3')/$value" />
    <link rel="edit" title="Package" href="Packages(Id='PackageName',Version='1.2.3')" />
    <category term="NuGet.Server.DataServices.Package" scheme="http://schemas.microsoft.com/ado/2007/08/dataservices/scheme" />
    <content type="application/zip" src="https://proget.example.org/nuget/FeedName/package/PackageName/1.2.3" />
    <m:properties xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
      <d:Version>1.2.3</d:Version>
      <d:Title></d:Title>
      <!-- Other fields omitted -->
    </m:properties>
  </entry>
</feed>

I'll go ahead and report this to Inedo.


Prevent hiting real network on router tests

Fixes #64

[Current coverage][cc-pull] is 98.21%

Merging [#71][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master        #71   diff @@
==========================================
  Files             7          7
  Lines           393        393
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            386        386
  Misses            7          7
  Partials          0          0

[][cc-pull]

Powered by Codecov. Last updated by [ff84a87...7ffb10f][cc-compare]
[cc-base-branch]: https://codecov.io/gh/devlucky/Kakapo/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/devlucky/Kakapo/compare/ff84a87cc79ec55b7d7d33e4288acde47d24a28c...7ffb10f0001adf44d541f7b1721cef04af0a9e8d
[cc-pull]: https://codecov.io/gh/devlucky/Kakapo/pull/71?src=pr

👍


Document technology stack

webpack
lit-html
lit-element (?)
web components

https://github.com/ProjectEvergreen/project-evergreen/wiki/Technology-Stack


No tests

There are no tests.  There should be some tests.

got started with https://github.com/Phillipmartin/gopassivedns/commit/397e5af5629a96652703a5c13578949933fb44d2

Added code coverage with https://github.com/Phillipmartin/gopassivedns/commit/7635f31bccbdeb60bbe3d9583f46917c9ab754d2

There are some tests.  The tests are automated with coverage.  test coverage needs to improve, but that will always be a thing.  closing this as the tools are now in place.


Update and add learn more administrative purposes box.

Closes #3753 &
Closes #3754
Closes #3750

Italics "Administrative purposes," "Non-administrative purposes,"
Help text for choosing a delivery option is missing
Help text for Administrative purposes reflects information for choosing a delivery option (the current info here should be for the missing help text in the point above^^)

Rename pill under "Settings" to "Responses" to correspond with expanded scope beyond response delivery
Previously:
EN: Response delivery
FR: Livraison des réponses

Suggested adjustment:
EN: Responses
FR: Réponses

Rationale
Delivery option is the next structural level
Level 1 Settings
Level 2 Responses / Branding / Form management
Level 3 Data classification / Delivery options / Purpose and use

Suggested change: Save button for each setting or for all settings
Currently, Delivery option and Purpose and use have save buttons but Data classification does not

Suggested tweaks to administrative purpose modal
Italicize "Privacy Act"
Open links in new tab

Suggested tweaks to publish page
Match setting name with heading from settings in French
"Usage prévu" not "Objectif et utilisation"

Add a space before colon in French

Capitalize the first letter of each setting in French
"Pas définis"
"Fins administratives"
"Fin non-administratives"

It's currently possible to publish without completing settings requirements
The publish button was previously not there until all requirements were complete

Suggested change: Remove banner from "Form management" pill since these settings (Open/Close) can be modified post-publishing

Not sure if it's related so logged it separately, but as I was testing also encountered: https://github.com/cds-snc/platform-forms-client/issues/3761

Suggested change: Remove "(default)"  / "(par défault) from dropdowns for classification (in settings and in edit)
Previously, when it was not a requirement for settings, "Protected A (default)" was the option that showed, if you change to "Unclassified" or "Protected B" it still says PA is default which is a bit strange in terms of experience.


RNA Plate position validation error

A10 should validate for RNA plate position but it doesn't.
It looks like it should based on the regular expression?
See https://data.microbiomedata.org/submission/3f6d765d-18e2-4fb4-8209-456a3b9d1a86/samples
DNA late position may also be wrong, I haven't checked it.

@turbomam made changes to NMDC and submission schema and sample data to address this.
The rules in NMDC schema are good, submission schema can import these rules.
Mark will check this in an example data file.
DH doesn't understand rules. So nothing to connect that.

Issue for implementing LinkML rules in DataHarmonizer: https://github.com/cidgoh/DataHarmonizer/issues/370

The tube/plate/well rules work in terms of LinkML validation in both the nmdc-schema and the submission schema. The well/plate position columns are magenta/optional in the DataHarmonizer interface now.


Results.approve

Result.checkAllDoneForPerformance { error: invalid input syntax for integer: "{}"

The issue here is that when Result.approve returns the performance id, it's coming back as [{ performanceid: 1}]. Give db.query a function to deconstruct the data coming back in the results and
de-structure the array to get the performance number

Deployed fix to staging. It worked. Calling this done

We were also showing the incorrect winner in the approve page. That's fixed in the PR referencing this issue


Python27 error

this is my error:
File "/root/.wine/drive_c/Python27/Scripts/pyinstaller-script.py", line 5, in
from pkg_resources import load_entry_point
File "C:\Python27\Scripts\pkg_resources_init_.py", line 48, in
import six
ImportError: No module named six
Traceback (most recent call last):
File "umbrella.py", line 239, in
main()
File "umbrella.py", line 215, in main
os.rename('dist/D.exe', 'dist/' + name)
OSError: [Errno 2] No such file or directory

Wait for final umbrella release

I solved by installing manually. the result is a xxx.pdf.exe files! having the final .exe, this tool does not very useful.

Try now.


Add EIP: NFT Alternative Text in Metadata

Overdue update from migration to ERC repo: https://github.com/ethereum/ERCs/issues/8
Initial post: https://ethereum-magicians.org/t/erc-7515-nft-alternative-text-in-metadata/14639

Thanks for moving over. Don't forget to update the file path to "ERC/erc-7515.md" and then turn back to merge


ability to set AML flags for large transactions

For compliance conscious, custodial implementations in the United States BSA MSB requires AML policy to include flagging and reporting of transactions over $10,000 USD per tx threshold.
System admin should have the ability to optionally flag such transactions and track them back to the order system for required reporting to FinCEN/OFAC as necessary.

That's a really great point, thanks!

🙏
Sent from my iPhone

On Oct 17, 2023, at 3:44 PM, Raffe @.***> wrote:

That's a really great point, thanks!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

I wonder if we'd be better off adding a generic 'flags' field to transactions that could be set when creating one, then people could add ["AML"] for txns they need, and it could be useful for other usecases also.