Exclude containers by label (feature)

I am using Logspout to capture output on all hosts in our Rancher cluster.  Certaing container stacks need to be excluded, but it is not as easy to add an env var as it is to add a label to a previously defined service stack.
It would be very useful to be able to exclude a container by setting a container label, rather than by using the LOGSPOUT=exclude environment variable.  If the name of the label could be configured via an env var on the logspout container, then this would be even better.
Also, if you could specify by inclusion instead it would be helpful.
EG,
docker run ... -e EXCLUDE=logspout.exclude -e INCLUDE=logspout.include gliderlabs/logspout
Then containers with the label logspout.include would be include, unless they also had the label logspout.exclude.  Of course, if not defined, EXCLUDE would default to nothing, and INCLUDE would default to everything.

+1 for this. I'm also using Rancher, and there's currently an issue where cadvisor spams the logs, so as a workaround i'd like to exclude it from logspout temporarily. If implemented as suggested by @sshipway, I'd just add a --label logspout.exclude=  to my docker run command for the Rancher agent.


Add sum method to running stats

I know I could've gotten around by using mean and current_n, but I felt like it would've been more convenient to have it.

Sweet, thanks for the PR and glad you are back :)


Make minor improvements to fixing mechanism

I think using ReadOnlyCollections is definitely a better approach. Will make the necessary changes. Thanks for the suggestion!


Can't resolve plugins on initializing nuxt 3.4.0(also after 3.3.0)

Environment

Operating System: Linux
Node Version:     v16.14.2
Nuxt Version:     3.4.0
Nitro Version:    2.3.3
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/edit/nuxt-starter-qsa4ck?file=app.vue
Describe the bug
In Nuxt 3.4.0, I get the attached error when I run nuxi prepare.
The contents of the .nuxt folder are hardly generated and the development environment does not start up.
I understand that this is an incorrect usage of plugins, but since this bug did not occur in the 3.0.0 series, I would like to prevent this from occurring.
A workaround approach is also welcome.
Additional context

This bug also occurs in past versions after 3.3.0.
This bug does NOT occurs in 3.2.3 version (maybe...).
This bug also occurs in dev and build commands.

Logs
❯ npm run postinstall
$ nuxt prepare
Nuxi 3.4.0                                                                            09:32:15

[09:32:16]  ERROR  Error while requiring module /home/projects/nuxt-starter-qsa4ck/modules/test.ts: Error: Cannot find module '@/plugins/aaa'
Require stack:
- /home/projects/nuxt-starter-qsa4ck/modules/test.ts

 ERROR  Cannot find module '@/plugins/aaa'                                            09:32:16
Require stack:
- /home/projects/nuxt-starter-qsa4ck/modules/test.ts

  Require stack:
  - modules/test.ts
  at Module._resolveFilename (https://nuxtstarterqsa4ck-iylz.w-credentialless.staticblitz.com/blitz.9926f97d.js:35:242305)
  at Function.resolve (https://nuxtstarterqsa4ck-iylz.w-credentialless.staticblitz.com/blitz.9926f97d.js:35:480406)
  at _resolve (node_modules/jiti/dist/jiti.js:1:241100)
  at jiti (node_modules/jiti/dist/jiti.js:1:243384)
  at eval (modules/test.ts:1:170)
  at jiti (node_modules/jiti/dist/jiti.js:1:245859)
  at requireModule (file://node_modules/@nuxt/kit/dist/index.mjs:355:26)
  at normalizeModule (file://node_modules/@nuxt/kit/dist/index.mjs:541:77)
  at Module.installModule (file://node_modules/@nuxt/kit/dist/index.mjs:520:47)
  at initNuxt (file://node_modules/nuxt/dist/index.mjs:2633:23)

Aliases are not supported in modules so this would never have worked. But before v3.3.0, they were not automatically loaded just because they are in a modules directory. You can:

update the import statement not to use aliases
rename your modules folder
change dir.modules to a different directory

@danielroe
OK! Thx!


WriteEntryToDirectory - entry with root path crash

Hi, When I call  WriteEntryToDirectory with entry key that is rooted for example '/root/file.txt' and the directory '/root2' as param.
the code fails with Entry is trying to create a directory outside of the destination directory.
The reason for that is Path.Combine ignore the directory path param.
The solution should be move use Path.Join.

There was to avoid a specific vulnerability to not allow extraction outside the destination directory:
https://github.com/adamhathcock/sharpcompress/pull/374/files
Path.Join does not seem applicable.

@adamhathcock Hi, i would've assume that if my destination folder is /root2 and the directory inside the zip is for example /root/file.txt then it will be extracted to /root2/root/file.txt (just like if i extract the zip manually on my pc)

again, the link prevents extraction to directories outside of the current one

I understand, again, i didn't expect it to extract to outside directories i'm expecting it to extract the full path into my desired destination folder - the problem is that when using Path.Combine("/root","/root2/test.txt") it will return "/root2/test.txt" instead of "/root/root2/test.txt"

These are just convenance methods.  You don't have to use them.   You can write your own to write entries to whatever you like and however you like.


feat: Add dingtalk webhook notification medium

Hello, we need to use DingTalk's webhook notification, so we added the code of this notification medium, hoping to merge it in. Because we will push the platform to the production environment for formal use. Thank you~
This code has been tested and verified in the local development environment, and the following is the effect diagram:

Related issue: https://github.com/semaphoreui/semaphore/issues/2325

Hi @shaxiaozz ,
Thank you for your PR! I removed the block of code which asks dingtalk options from semaphore setup because it is outdated method of configuration.

@fiftin Thank you for your agreement to merge. At the same time, delete the obsolete code, thank you~


high level API for the gyroscope

:pushpin: Commit 02b2c91 has been approved by japaric

@homunkulus r+

:hourglass: Testing commit 02b2c91 with merge 02b2c91...

:sunny: Test successful - status-travis
Approved by: japaric
Pushing 02b2c91acfb5bb2520a8bda7259fffe80a5ef1f5 to master...


[Bug]: Frame.waitForSelector is flaky for cross-process navigation

waittask specs
1246       Frame.waitForSelector
1247         should survive cross-process navigation:
1248     done() called multiple times in test  of file /home/runner/work/puppeteer/puppeteer/test/build/waittask.spec.js; in addition, done() received error: Error: NS_BINDING_ABORTED at http://<IP_ADDRESS>:44173/grid.html
1249    at navigate (/home/runner/work/puppeteer/puppeteer/src/common/Frame.ts:336:13)
1250    at runMicrotasks ()
1251    at processTicksAndRejections (node:internal/process/task_queues:96:5)
1252    at Frame.goto (/home/runner/work/puppeteer/puppeteer/src/common/Frame.ts:300:17)
1253    at Page.goto (/home/runner/work/puppeteer/puppeteer/src/common/Page.ts:1954:12)
1254    at Context. (/home/runner/work/puppeteer/puppeteer/test/src/waittask.spec.ts:477:7)
1255  Error: done() called multiple times in test  of file /home/runner/work/puppeteer/puppeteer/test/build/waittask.spec.js; in addition, done() received error: Error: NS_BINDING_ABORTED at http://<IP_ADDRESS>:44173/grid.html
1256      at navigate (src/common/Frame.ts:336:13)
1257      at runMicrotasks ()
1258      at processTicksAndRejections (node:internal/process/task_queues:96:5)
1259      at Frame.goto (src/common/Frame.ts:300:17)
1260      at Page.goto (src/common/Page.ts:1954:12)
1261      at Context. (test/src/waittask.spec.ts:477:7)
1262      at runMicrotasks ()
1263      at processTicksAndRejections (node:internal/process/task_queues:96:5)

Also, the waitForFunction is flaky:
should survive navigations:
     done() called multiple times in test <waittask specs Frame.waitForFunction should survive navigations> of file /home/runner/work/puppeteer/puppeteer/test/build/waittask.spec.js; in addition, done() received error: Error: JSHandles can be evaluated only in the context they were created!
    at ExecutionContext.convertArgument (/home/runner/work/puppeteer/puppeteer/src/common/ExecutionContext.ts:328:17)
    at Array.map (<anonymous>)
    at ExecutionContext._ExecutionContext_evaluate (/home/runner/work/puppeteer/puppeteer/src/common/ExecutionContext.ts:277:43)
    at ExecutionContext.evaluateHandle (/home/runner/work/puppeteer/puppeteer/src/common/ExecutionContext.ts:196:26)
    at IsolatedWorld.evaluateHandle (/home/runner/work/puppeteer/puppeteer/src/common/IsolatedWorld.ts:213:20)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at WaitTask.rerun (/home/runner/work/puppeteer/puppeteer/src/common/WaitTask.ts:94:26)
    at async Promise.all (index 0)
    at TaskManager.rerunAll (/home/runner/work/puppeteer/puppeteer/src/common/WaitTask.ts:235:5) {
  uncaught: true
}

No longer relevant.


Fix some wrong position on the swarmscan map

@janos Hello! the nodes in China are too concentrated, could you fix it? Thanks!

Hi @junyan-zg. Thank you for submitting the issue. Currently, the reason for this is the granularity that GeoIP database is providing for these IP addresses. I will see to get more detailed location database.

SwarmScan now has a better granularity on geolocation data.

@janos Efficiently handled! Thanks!


Feature/refactor elastic

Description
ElasticSearch connection chain has changed to (Host, Port) format.
Test
All passed and one added
Coverage
No changes
Scalastyle
No info

We're missing the default values in our outputs


DRILL-7292: Updated baselines due to transition to V3 Text Reader

Now all implicit columns displayed at the end.
Need to be merged after the Drill PR:
https://github.com/apache/drill/pull/1806

apache/drill#1806 is already merged, so this one should be merged ASAP to avoid functional tests failures.

@Agirish / @kkhatua could you please review?


fix: do not create dynamic properties

Dynamic properties are deprecated.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

7 of 7 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.4%) to 96.97%

Totals

Change from base Build<PHONE_NUMBER>:
1.4%

Covered Lines:
64

Relevant Lines:
66

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

7 of 7 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.4%) to 96.97%

Totals

Change from base Build<PHONE_NUMBER>:
1.4%

Covered Lines:
64

Relevant Lines:
66

💛  - Coveralls


feat: [FC-0047] Upgrade Downloading logic. Offline xBlock

https://www.figma.com/design/iZ56YMjbRMShCCDxqrqRrR/Open-edX-Mobile-App-All-Screens-v2.1?node-id=3240-20123&t=TDhBl4mEV0pNeAEs-0

Added a dedicated offline tab for managing user downloaded content.
Added informational dialogs to provide users with additional context before downloading and to inform them about errors.
Extended offline functionality to include xBlocks, ensuring that users can interact with and progress through xBlocks content even when offline. This includes saving user progress locally, which will be synced once the user is back online.

Light Theme
Dark Theme

https://github.com/openedx/openedx-app-android/assets/141041606/3c58b3cf-9f65-492d-94d5-e880ba735a8e
https://github.com/openedx/openedx-app-android/assets/141041606/b19c141c-5364-4f1b-911c-a6cff51db675

Offline xBlock logic
https://github.com/openedx/openedx-app-android/assets/141041606/3ae4657d-f641-4e0e-8249-900c89c809ec

Thanks for the pull request, @PavloNetrebchuk! Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
This is currently a draft pull request. When it is ready for our review and all tests are green, click "Ready for Review", or remove "WIP" from the title, as appropriate.

reviewing...


Test/fix RBAC for OpenShift4

The current RBAC rules work for kube, but OpenShift will likely be different.

Problems encountered (SCC related):

spec.volumes[1]: Invalid value: "hostPath": hostPath volumes are not allowed to be used
spec.containers[0].securityContext.securityContext.runAsUser: Invalid value: 0: must be in the ranges: [1000460000,<PHONE_NUMBER>]

Other:
release supervole200-d1f9sy8epf2tt4ylw491ktbb6 failed: persistentvolumes       "supervole200-d1f9sy8epf2tt4ylw491ktbb6-recycler" is forbidden: cannot set blockOwnerDeletion       if an ownerReference refers to a resource you can''t set finalizers on: , <nil>

Granting cluster-admin to the operator takes care of the "other" error from above, and recycler PVs are properly created.
ClusterRole/gluster-subvol-operator already had * on persistentvolumes. Perhaps it was getting stopped by SCC as well?
Recyclers are now stuck on SCC also:

spec.containers[0].securityContext.securityContext.runAsUser: Invalid value: 0: must be in the ranges: [1000460000,<PHONE_NUMBER>]

Now the recyclers won't run because they can't reserve 10Mi ephemeral-storage.

ephemeral-storage request/limits are disabled in OCP currently: https://github.com/openshift/api/blob/275768afc8f66b79aeb12debf94ffc85255104ad/config/v1/types_feature.go#L76


Java not found - exit code 9009

I'm trying to add this as a step in one of our Azure DevOps deployments. However, it keeps failing with " 'java' is not recognized as an internal or external command":
2020-09-22T12:48:21.2708345Z ==============================================================================
2020-09-22T12:48:21.2709349Z Task         : OWASP Dependency Check
2020-09-22T12:48:21.2711297Z Description  : Dependency Check is a Software Composition Analysis (SCA) tool that attempts to detect publicly disclosed vulnerabilities contained within a project's dependencies.
2020-09-22T12:48:21.2712627Z Version      : 5.3.2003
2020-09-22T12:48:21.2713304Z Author       : Dependency Check
2020-09-22T12:48:21.2714342Z Help         : [More Information](https://jeremylong.github.io/DependencyCheck/index.html)
2020-09-22T12:48:21.2715497Z ==============================================================================
2020-09-22T12:48:23.4445503Z Starting Dependency Check...
2020-09-22T12:48:23.6401335Z Downloading Dependency Check installer...
2020-09-22T12:48:33.2340098Z Invoking Dependency Check...
2020-09-22T12:48:33.2400801Z Path: C:\azagent\A1\_work\_tasks\dependency-check-build-task_47ea1f4a-57ba-414a-b12e-c44f42765e72\5.3.2003\dependency-check\bin\dependency-check.bat
2020-09-22T12:48:33.2418414Z Arguments: --project "Web" --scan "C:\azagent\A1\_work\r1\a\**\*.csproj" --out "\dependency-check" --exclude "C:\azagent\A1\_work\r1\a" --format HTML --failOnCVSS 8 --suppression "C:\azagent\A1\_work\r1\a"
2020-09-22T12:48:33.3286473Z 'java' is not recognized as an internal or external command,
2020-09-22T12:48:33.3287988Z operable program or batch file.
2020-09-22T12:48:34.2890567Z Dependency Check completed with exit code 9009.
2020-09-22T12:48:34.2907107Z Dependency check reports:
2020-09-22T12:48:34.4252429Z ##[error]Dependency Check exited with an error code.
2020-09-22T12:48:34.4493346Z Ending Dependency Check...
2020-09-22T12:48:34.4957837Z ##[section]Finishing: Dependency Check

I found this issue which is the same scenario (we're running this on our own build server running Windows Server 2019). I downloaded the Java runtime (I've tried this with both the 64-bit version and, when that didn't work, I uninstalled it and installed the 32-bit version). In both cases I went into System Properties > Advanced > Environment Variables and configured the System variables.
I created these two settings:
JAVA_HOME   C:\PROGRA~2\Java\jre1.8.0_261
JAVACMD     C:\PROGRA~2\Java\jre1.8.0_261\bin

I also tried adding the jre1.8.0_261\bin folder to the path.
But when I redeploy it still fails with the same error. I'm not quite sure what else to try.

I suspect this is likely due to the service account running the process can't locate Java. I would suggest running a PowerShell task directly on the build agent to confirm Java is being properly located by the build task.

Closing due to inactivity.


python310Packages.pyezviz: <IP_ADDRESS> -> <IP_ADDRESS>

Description of changes
https://github.com/BaQs/pyEzviz/releases/tag/<IP_ADDRESS>

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 180786 run on x86_64-linux 1

3 packages built:

home-assistant-component-tests.ezviz
python310Packages.pyezviz
python39Packages.pyezviz


No such file or directory errors reading layer files

This happened on the CI with the new test from PR #1735. I think we've seen this a few times before, but couldn't find an existing issue for it
https://app.circleci.com/pipelines/github/neondatabase/neon/6512/workflows/cb7bf6ab-11db-440c-88fa-3c704e9f6fca/jobs/65793/artifacts
2022-05-19T08:03:47.313535Z ERROR compact loop terminated with error: Failed to load delta layer /tmp/test_output/test_pageserver_chaos/repo/tenants/775a6bca9dcc4d5baf1db289176bbd7c/timelines/e3aa3049715941f858d26f6c42c375f6/000000067F000032AE000040000000003707-000000067F000032AE000040000000003792__000000001E7EFFE9-0000000021371F61
...
2022-05-19T08:03:49.189238Z  WARN could not remove ephemeral file '/tmp/test_output/test_pageserver_chaos/repo/tenants/775a6bca9dcc4d5baf1db289176bbd7c/timelines/e3aa3049715941f858d26f6c42c375f6/ephemeral-6': No such file or directory (os error 2)
2022-05-19T08:03:49.190033Z ERROR Thread 'layer flush thread' tenant_id: Some(775a6bca9dcc4d5baf1db289176bbd7c), timeline_id: Some(e3aa3049715941f858d26f6c42c375f6) exited with error: No such file or directory (os error 2)

Originally posted by @hlinnaka in https://github.com/neondatabase/neon/issues/1735#issuecomment-1131463161

Trying to reproduce this issue locally, no result so far 😅 . A few notes when looking into this issue:

Judging from the log, it seems that a delta L1 file is not found while that delta file's data is in the layer map
I think this can happen either when (*)

the file is GCed by a running thread and is read by another thread. The two threads belong to different page servers, so the layer maps are different
something weird happens during the creation of the L1 layer, which creates the layer data in memory but not the actual L1 file. I suspect this can happen because the DeltaLayerWriter fails to rename the temp file.

1 is quite unlikely because I don't see any GC info from the logs. I tried to add some delays to the fsync and rename during the delta file creation, but haven't found anything.
(*): I wonder if there is another way for this to happen

GC and compaction are synchronized using the same compaction_cs critical section.
So I do not think that it is some RC between RC and compaction.
Also subsequent error with removing ephemeral files looks suspicious.
Ephemeral files are remove when in-mem layer is destructed. Nobody should try to remove the same inmemory layer and correspondent ephemeral file twice (Arc).
As far as I see - this test run is failed because of timeout expiration. Can this problem be caused by testing framework itself which starts to deleteworking directory while there is still active page server working with this directory?

I did some runs in https://github.com/neondatabase/neon/pull/1757 to reproduce this error on CI.
So far, the new test failed consistently but now with a different error 😅 .
CI: https://app.circleci.com/pipelines/github/neondatabase/neon/6543/workflows/be3547fa-1d6f-40ac-94b2-0e10c85aeb2a/jobs/66165/artifacts
The new error seems to because of WAL receiver disconnection:
Page server log:
2022-05-19T20:59:08.622146Z ERROR WAL receiver{timeline=fa46afd5116e01a9f5980587b1f355db tenant=587c3a9c6266420f9e5538df340c632c}: connection error: connection closed
2022-05-19T20:59:08.622827Z  INFO WAL receiver{timeline=fa46afd5116e01a9f5980587b1f355db tenant=587c3a9c6266420f9e5538df340c632c}: WAL streaming connection failed (connection closed)

Safe keeper log:
2022-05-19T20:54:57.259516Z ERROR Replication background thread failed: Connection reset by peer (os error 104)
2022-05-19T20:54:58.136127Z ERROR {tid=10}: query handler for 'START_REPLICATION PHYSICAL 0/1696628' failed: failed to run ReplicationConn

Caused by:
    0: Failed to send KeepAlive message
    1: Broken pipe (os error 32)

Stack backtrace:

This can probably happen because of CI connection issue on remote machine, so I'll need to run more experiments.

I did some runs in https://github.com/neondatabase/neon/pull/1757 to reproduce this error on CI.
So far, the new test failed consistently but now with a different error 😅 .
CI: https://app.circleci.com/pipelines/github/neondatabase/neon/6543/workflows/be3547fa-1d6f-40ac-94b2-0e10c85aeb2a/jobs/66165/artifacts
The new error seems to be because of WAL receiver disconnection:
....

Can confirm get this error consistently now. Not sure if it was because I merge the new changes from main into #1757 compared to #1735.

The new error seems to be because of WAL receiver disconnection:

It seems to be not the source of the problem, but result of test termination because of timeout expiration.

There are several of those safekeeper errors in the log, before the test timeout happens. I think they're caused by abruptly closing the pageserver <-> safekeeper connection, when the pageserver is killed. Can you confirm @arssher or @petuhovskiy? We should probably tone down the logging of those, similar to https://github.com/neondatabase/neon/issues/1683 for the pageserver.
Yeah, the pageserver error is just because the test timed out. We need to increase the timeout on the test to let it finish (I created the test case before the PR that added the timeout was pushed)

Right,
failed to run ReplicationConn

Caused by:
    0: Failed to send KeepAlive message
    1: Broken pipe (os error 32)

just means safekeeper found pageserver <-> safekeeper connection terminated. Yes, we should hide backtrace there.

There are a lot of WARN could not remove ephemeral file ... No such file or directory (os error 2) on staging, but it's probably a different issue, because they always happen right after detach call. Link to logs

There are a lot of WARN could not remove ephemeral file ... No such file or directory (os error 2) on staging, but it's probably a different issue, because they always happen right after detach call. Link to logs

Yeah, seems like a race condition in detach_timeline. I agree it looks like a different bug, there's no DETACH calls in this test. I opened https://github.com/neondatabase/neon/issues/1775 for that.

on a discussion today we thought that to confirm thaht this comes from a failed test we may want to revert the test timeout settings, try locally and see if it fails again

OTOH, @petuhovskiy mentioned that we had a special, different timeout on circle CI, so may be hard to replicate locally

Is there any evidence that CircleCI deletes files? AFAIK it keeps them as artifacts.

Is there any evidence that CircleCI deletes files before killing the whole container?

nevermind, I found that we explicitly add a "Delete all data but logs" step

I managed to reproduce this on CI with this branch. Look at the tmp/test_output/test_timeout[0]/repo/pageserver.log artifact here. This concludes that we sometimes delete files while pageserver is still running.
Not sure why some of the test_timeout tests passed though. They sleep for more than the CircleCI timeout duration.

Let's close it because:

We know it's not a pageserver bug, but a CI mistake
This CI workflow doesn't exist anymore because we don't use Circle anymore
We don't have a "delete all files" step after running tests in our current github workflows


SC-2853 LA config improvements

By default, US region is set and it can be changed to EU on container start to update receivers endpoints. This PR solves the issue when custom LOG_URL is set and invalidates region settings. Also fixes logging message with receivers that are in use.
Docs need to be changed before merging this PR.

Docs need to be changed before merging this PR.

Is there a PR for that @komljen ?

Not yet, they will be added to the same PR.


NIFI-1805

Expose BackPressureObjectThreshold and BackPressureDataSizeThreshold to
ConnectionStatus

I wonder if, upon crossing a threshold, we should raise a bulletin maybe?

@aperepel that isn't a bad idea. That takes a little more discussion around how often we continue to post that bulletin if the threshold is constantly exceeded, what severity, etc

It might make more sense to leave those sort of operations to a ReportingTask however? Does anyone have any thoughts around that?

I like the ReportingTask path.

We have talked before about having some sort of icon on a connection that indicates that back pressure is configured and then some sort of indicator that back pressure is applied. Perhaps an icon on the connection that is grey when configured but the threshold is not met, and then it would turn red or something if backpressure is actively being applied. The only issue with this approach is that we always have more & more things that we want to show and we have to balance what to show vs. how much screen real estate should be used. I am hoping that the UI redesign going on for 1.0 will make this work much better.

@markap14 don't show more, change how things are shown. in case of a connection and backpressure a simple gradient change in color (or a binary ok/throttled color) of the black is all it takes, IMO.

@jdye64 Apologies for delays.  These changes look fine and everything builds fine.  As far as the other commentary on this thread, I will leave that to folks to generate other issues to track, but these changes should certainly help as a means for any of those enhancements.


pxDropdown.dropdown_content_value_changed event fired does not contain Key property

Expected behavior and actual behavior:
We expect to catch the 'dropdown_content_value_changed' event fired from the pxDropdown element, and then retrieve the textValue and key properties from that event. The textValue is being outputted and transferred successfully, however the key always returns back as undefined. Both key and val properties are included in the Object passed to the px-dropdown-content element.
In my page, we have the following instance of pxDropdown:
<px-dropdown id="pxDropdown" display-value="Devices">             <px-dropdown-content  class="px-dropdown-content" max-cont-character-width="10" items="{{devices_items}}">             </px-dropdown-content>         </px-dropdown>
{{devices_items}} gets altered in one of our methods and gets set to an Object. A sample value passed to it is:
var objectToPass = [{"key":"1", "val":"One"}, {"key":"2", "val":"Two"}];
We included the following listener to catch the event fired by the pxDropdown element whenever the dropdown value changes:
listeners: {                 'pxDropdown.dropdown_content_value_changed': 'dropdownValChanged'             },
We want to then retrieve the events detail properties: key, and textValue. For our development work, we have this in our 'dropdownValChanged(evt)' method:
console.log("value selected: " + evt.detail.textValue);   console.log("key selected: " + evt.detail.key);
The textValue property has the expected value. However the key property comes back as undefined.
Environment
component version number: px-dropdown#0.10.5
Browser: 52.0.2743.116 (64-bit)
operating system: Mac El Capitan v. 10.11.5

Hello,
can you try version 0.11.0? I think this version includes the feature you're asking for!
Let me know if that solves your issue
Cheers,
Ben

Cool, updating to 0.11.0 or later resolved the issue. Thanks Ben!
Is it on the roadmap to include an "added functionality" section for the various px components found on the Predix Developer UI page?
http://predixdev.github.io/predix-ui/

We're currently discussing how to communicate new features effectively but haven't come up to a conclusion yet. We realize it can be hard to find out what has been added recently!
At the moment I would advise keeping an eye on the website you mentioned, all demos should now be up to date and automatically updated when we add features/fix bugs! We're also in the process of adding a Codepen to each demo so that anyone can play with the latest version of a component.
I'll close this issue for now but contact me if you have more questions.
Cheers,
Ben


proof of concept for unacknowledged and/or fire-and-forget calls in RRemoteService

This PR feels like a hack, because I made this just as a proof of concept.
I am very open to discuss this further.
Whit this PR, one can make unacknowledged and/or fire-and-forget calls (see #494).
In the RRemoteService's get(...) methods that accepts executionTimeout and/or ackTimeout:

pass a negative value into executionTimeout to make fire-and-forget calls
pass a negative value into ackTimeout to make unacknowledged calls

There is many things not quite right with this implementation, here some that comes to mind:

from a user perspective, it is not clear that a fire-and-forget call will returns the default value for the method return type (0 for int, null for Object, etc...), so it is a bit misleading (the user explicitly want the call to return without result, so he expect none, but still...).
again, from a user perspective, this hack enable client side typo (or other wrong calculation) into the executionTimeout to make a failing call (exception thrown server side) silent on the client side.
it is not possible to disable the ack and still get this kind of request time-to-live in the queue (indeed, since the ackTimeout is negative, the server side must skip this TTL check and proceed with the call, otherwise the TTL check would always fail)

I think it's inconvenient to use timeouts to determine invocation mode (fire-and-forget or unacknowledged).
I suggest to introduce an enum for this:
enum InvocationMode {
// fire-and-forget call
DONT_WAIT,
// unacknowledged call
WAIT_ACK,
// default behaviour of get method
WAIT_RESULT
};

RemoteService service = remoteService.get(RemoteService.class, InvocationMode.WAIT_ACK);

InvocationMode.DONT_WAIT and InvocationMode.WAIT_ACK modes are available for methods with void result only. So default values are not needed.

@mrniko Think you for your feedback!
You fixed all my concerns in one post 👍
I will play with your suggestions and add a new commit to this PR.
Just one thing though: how do you see the signature for when one want to remoteService.get() with the InvocationMode.WAIT_ACK mode and a custom ackTimeout  ?
Maybe something like that ?
get(Class<T> remoteInterface, InvocationMode mode, long ackTimeout, TimeUnit ackTimeUnit)

But, some parameters are mutually exclusive, for example one can call:
RemoteService service = remoteService
    .get(RemoteService.class, InvocationMode.DONT_WAIT, 1, TimeUnit.SECONDS);

get(Class remoteInterface, InvocationMode mode, long ackTimeout, TimeUnit ackTimeUnit)

I think it will be useful

A small technicality, I see this PR will not merge properly on your master branch.
Should I rebase it (and resolve conflicts) on top of your master ?
I am not sure Github will keep up if I push a rebased branch ...

Should I rebase it (and resolve conflicts) on top of your master ?

Yes, it's necessary

Here you go with a second iteration on this feature.
The PR is now rebased on your master.
In short, 6b1625a introduce those changes into the API:

a new RRemoteService.get(Class remoteInterface, RemoteInvocationOptions options) method
a new RemoteInvocationOptions class that allow user to tune invocations

The RemoteInvocationOptions javadoc, contains some examples on how to use it.
The new RRemoteService.get method javadoc is now more clear on what it expect.
I made also a couple of changes into the RedissonRemoteServiceTest test cases.
Given that I suck at naming things, do not hesitate to have me change the public API (or anything else), I envoy working on this issue.
I also like writing tests, I can write more if you want.

Cool work! Thank you so much!
I left a few comments about code above.

Thank you for your feedbacks.
If we want to completely eliminate all negative timeout comparisons:
on the client side:
This one is easy.

RemoteInvocationOptions will need to be immutable, or it will need to be copied (with a copy ctor, or a clone()) here to let the user fiddle with the RemoteInvocationOptions instance after having called get without impacting the client behaviour.

on the server side:
This one is harder and needs a decision from you.

we need to change RemoteServiceRequest to include a RemoteInvocationOptions options field. This will change its serialized form (* see my note bellow) and break existing users that do a deploy with non empty service queues in Redis, since the new server code will not be able to properly deserialize the old requests.
RemoteInvocationOptions will need to be Serializable as well.

Note
While working on this problem, I saw that Redisson Remote Service just not work with serialization based codecs (FstCodec, SerializationCodec) because RemoteServiceRequest, RemoteServiceResponse and RemoteServiceAck are not Serializable.
Here a stripped stack trace if I try to use the SerializationCodec in any test in RedissonRemoteServiceTest:
org.redisson.client.WriteRedisConnectionException: Can't write command: (RPUSH), params: [redisson_remote_service:{org.redisson.RedissonRemoteServiceTest$RemoteInterface}, RemoteServiceRequest [requestId=6de3227b9514a372a26e10006edc04dd, methodName=voidMethod, args=[noAck/noResult, 100], ackTimeout=-1, date=1463842621953]] to channel: [id: 0xc07e4b3b, L:/<IP_ADDRESS>:56888 - R:/<IP_ADDRESS>:6379]

	at org.redisson.command.CommandAsyncService.checkWriteFuture(CommandAsyncService.java:484)
	...more...
Caused by: io.netty.handler.codec.EncoderException: java.io.NotSerializableException: org.redisson.remote.RemoteServiceRequest
	at io.netty.handler.codec.MessageToByteEncoder.write(MessageToByteEncoder.java:125)
	...more...
Caused by: java.io.NotSerializableException: org.redisson.remote.RemoteServiceRequest
	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
	at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
	at org.redisson.codec.SerializationCodec$2.encode(SerializationCodec.java:58)

With 4378acd, now the client side will not rely on negative values comparisons and use a copy of RemoteInvocationOptions instead.
But, as you can see here the server side sill do because of the server side issues I mentioned in my comment above. I will wait for your feedbacks for this one as I do not want to bear the decision to introduce incompatible changes into your software and break your existing users.

and break existing users that do a deploy with non empty service queues in Redis, since the new server code will not be able to properly deserialize the old requests

I'll mention about this breaking change in changelog. So you can do it.

Could you please rebase it on master?

Sure, I'll rebase, introduce some changes into RemoteServiceRequest and RedissonRemoteService then push again to this PR.

9ee20f6 is simply

a rebase of this PR on your master (it was a fun conflicted merge party :))
the new RemoteInvocationOptions options field in RemoteServiceRequest for server side use (this one is the breaking change)

All tests in RedissonRemoteServiceTest are green.

Thanks a lot for your effort!


fix: individual post view added

Related Issue
#121

Description

I just created a route of <base_url>/post/postId  which substantially created a page for rendering the individual post with the specific post id.
Screenshots

@ani2607 PR is reviewed. Please also remove the merge conflicts as well

@ani2607 PR reviewed. Please resolve the merge conflicts of yarn.lock.
To fix this issue, delete the current yarn.lock and generate new one and then push


Access modifiers added.

Thanks for this!  I am keeping private and public out of these examples as they are meant for to be beginner-friendly in Processing.


Make build location configurable

This PR allows users to choose where their application is built before the application gets deployed/uploaded.
In mup.json, "buildLocation": "/my/custom/build/directory" can be set.

Maybe it's still relevant to submit to the current port at kadirahq/meteor-up?  So to say this version is depreciated and the "Stable" version, is to say it's not changed or merged PRs for a long time now, so please consider adding to a branch over there.

Makes sense. I'll look into kadirahq/meteor-up at work next week. If it's still not configurable, I'll see what I can do to submit a patch there.


feature idea: Create feature for shared user accounts (like "scribe")

Occasionally folks want to share a user account for messages that aren't tied to one person (and their reputation) but are more for a team.  The example we got was somebody acting as the "scribe" during a meeting.  After the meeting, other folks might want to edit the scribe transcript, without pulling in the whole can of worms of whether admins can edit messages or you can make messages "sharable", and without going to a full-on "wiki" approach.
My proposal is to have Zulip facilitate shared user accounts where multiple folks can "act" as the user.  (Customers can sort of simulate this now by creating a shared account where they share passwords.  Making a "third" account keeps their own accounts secure, but they still need to share a password for the shared account, and it's still messy if somebody leaves, etc.)  Zulip could do things like make it so that shared accounts are automatically authenticated from normal accounts.
This idea is definitely a "brainstorm" at this point.

Another example of a shared account would be "On Call Person", where maybe 5 or 6 people can all control that account.


Redshift COPY fails in luigi 2.7.1 when columns are not provided

Running Redshift COPY jobs with columns = None to prohibit table creation fails in luigi 2.7.1 with
TypeError: object of type 'NoneType' has no len()

The root cause seems to be https://github.com/spotify/luigi/pull/2245/files#diff-778ea3db4cccaf4de6564889c5eb670fR338
A possible solution would be to change the line to
if self.columns and len(self.columns) > 0:

unless I am missing some reason to explicitly ask only for len(self.columns).

This seems like a reasonable solution. The motivation here was to handle the default column definition or some structure with length > 0. Really, we should ensure that it is not None and an iterable with length greater than zero.
Feel free to PR!


geopandas slowdown with latest Fiona

Expected behavior and actual behavior.
I have noticed slowdown opening geopackages with geopandas: If geopandas uses Fiona 1.8.22 as a dependency it takes several seconds to open a geopackage, but takes several minutes with Fiona 1.9+. I tried to investigate why this is, and it seems to be related to the Feature.geo_interface  property. Geopandas checks for this property using an if statement within a loop, and it seems  that this if statement is not triggered with Fiona 1.8.22 but is triggered with Fiona 1.9+. Unfortunately I could not pin down the specifics better than that.
Steps to reproduce the problem.
Create a clean python environment and pip install latest geopandas and Fiona (1.9+), then open a geopackage. Then downgrage the Fiona version to 1.8.22 and open the same geopackage.
Operating system
Ubuntu 20.04.
Fiona and GDAL version and provenance
Python             3.8.10
Fiona                1.9.4.post1
geopandas      0.13.2
pip                    23.2.1
gdal                  3.4.1

@GNU-Dawn do you mean this test here https://github.com/geopandas/geopandas/blob/main/geopandas/_vectorized.py#L139? That doesn't have anything to do with Fiona.
GeoPandas has two different implementations of read_file(). One uses Fiona, one uses pyogrio. You might want to check to see if you were using the latter previously and are now using the former.
There's not enough detail in this issue to begin to understand what's going on.

The fiona-based reader uses GeoDataFrame.from_features (passing the fiona collection to that). So I assume the relevant code for this is: https://github.com/geopandas/geopandas/blob/91d18898d770254f460adf2260da238acb501553/geopandas/geodataframe.py#L636-L642
Comparing fiona 1.8.22 and 1.9, I see some slowdown, but not one that would explain going from a few seconds to several minutes:
In [1]: import fiona

In [2]: col = fiona.open("test.gpkg")

In [3]: feat = next(iter(col))

In [4]: feat["geometry"]
Out[4]: {'type': 'Point', 'coordinates': (1.0, 2.0)}

In [5]: from shapely.geometry import shape

In [6]: shape(feat["geometry"])
Out[6]: <POINT (1 2)>

In [7]: %timeit shape(feat["geometry"])
8.23 µs ± 533 ns per loop (mean ± std. dev. of 7 runs, 100,000 loops each)

That's with fiona 1.8.22, and with fiona 1.9.4 it gives around 26µs for me (so a bit more than 3x slowdown for this part of read_file).
(in general, if you want the fastest option for bulk reading, I would recommend using pyogrio with the use_arrow=True keyword (which requires GDAL 3.6+))

Thanks for checking @jorisvandenbossche !


Conditional Fetching throws "TypeError: Cannot read property 'protocol' of null" when multiple arguments

Bug report
when using conditional fetching (with axios) multiple arguments, swr throws an error. Due to this, unable to differentiate with other valid errors
Description / Observed Behavior
"TypeError: Cannot read property 'protocol' of null" when using below code
`requestInfo=[url,data]  /* here url is null and a non null data*/
fetcher = (url,data) => axios.post(url, JSON.parse(data)).then(res=>res.data)
const { data, error}  = useSWR(requestInfo, fetcher, {revalidateOnFocus: false})"`
What kind of issues did you encounter with SWR?
SWR invokes an axios call even when the url is null and a valid non null Data
[null, "{"startDate":"2021-06-14T08:03:57.773Z","endDate":"2021-06-21T08:03:57.773Z"}"]
Expected Behavior
It should cancel the request like it works when passing url alone
Repro Steps / Code Example
Or share your code snippet or a CodeSandbox link is also appreciated!
Additional Context
SWR version.
"swr": "0.5.6"

It seems you are running JSON.parse over an object (data), which is not needed.

@shuding I have used stringify. If you look carefully that my fetcher parsing it. SWR uses stringify and the axios fetcher parses it before invoking the rest call.

I see. To conditionally skip a request, you should pass null as the key, not just the URL in your case.
useSWR(skip ? null : [url, data], fetcher)


Rsync errors: "timeout" and "no valid manifest"

Hello,
CentOS Linux release 7.9.2009 (Core) Routinator 0.12.0.
I see a lot of errors in /var/log/messages:
routinator[30189]: [WARN] rsync://rpki.sailx.co/repo/: rsync error: timeout waiting for daemon connection (code 35) at socket.c(281) [Receiver=3.1.2]
routinator[30189]: [WARN] rsync://rpki.sailx.co/repo/Sail-Internet-Inc/0/DFC5509768EA587E638D20680032E0FF122BD25A.mft: no valid manifest found.
routinator[30189]: [WARN] rsync://rrdp.taaa.eu/repo/: rsync error: timeout waiting for daemon connection (code 35) at socket.c(281) [Receiver=3.1.2]
routinator[30189]: [WARN] rsync://rrdp.taaa.eu/repo/rrdp-taaa-eu/0/AAFBF9DBE860335648F2AEABA124326B85374C47.mft: no valid manifest found.

It looks like only two rsync servers are available:
cd /var/lib/routinator/rpki-cache/rsync
du -ks *
0       rpki.0i1.eu
0       rpki1.rpki-test.sit.fraunhofer.de
36      rpkica.mckay.com
32      rpki.rand.apnic.net
0       rpki.sailx.co
0       rrdp.taaa.eu
0       rsync.rp.ki

What should I do with it?
Regards,
Malik.

There are several RPKI publication points that are poorly maintained, there is nothing you can do. We see the same.
All ~70 global RPKI publication points advertise that they make their data available over RRDP (which uses HTTPS), as well as rsync. All relying party software, including Routinator, will prefer to use RRDP if available and only when this fails repeatedly fall back to rsync. If rsync fails as well, Routinator will use cached data until it expires. To learn more about Routinator's data fetching strategy, please refer to the documentation.


removing scaling for gsp, but add capacity

Pull Request
Description

dont normalize gsp data
put capaicty in saved batched data

Fixes #231
How Has This Been Tested?
unittests

[ ] No
[x] Yes

Checklist:

[x] My code follows OCF's coding style guidelines
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have checked my code and corrected any misspellings

Ill close this for
https://github.com/openclimatefix/nowcasting_dataset/pull/428


Use actual binary name instead of hardcoding it

See https://github.com/docker/machine/pull/292 for reasons.

yes please - this is very very useful when documenting things for users.

@SvenDowideit

I think swarm is relatively unique name, so one of the reasons mentioned in docker/machine may not apply here. Generally, built-in documentation (manual pages) can be generated from real name and the documentation here on github could stay as is and expect, that in most cases people are going to use it as swarm.

I have no strong feelings on either way (hard code, or programmatic), but I do have strong feelings that we should not use os.Args[0] directly. This will pull in the full path to the binary if the full path was used to start it. path.Base(os.Args[0]) is much better.

@phemmer Agreed, :+1:
I've modified the PR.

@radeksimko I think is we do this, we need to also update CommandHelpTemplate in help.go

@vieux I agree, there's a few solutions for that:

Send a patch to the codegangsta/cli, so we can get access to the parent context (parent Command) inside the template as this is currently the context we have available: cli.Command{Name:"list", ShortName:"l", Usage:"list nodes in a cluster", Description:"", BashComplete:(func(*cli.Context))(nil), Before:(func(*cli.Context) error)(nil), Action:(func(*cli.Context))(0x5a90), Subcommands:[]cli.Command(nil), Flags:[]cli.Flag(nil), SkipFlagParsing:false, HideHelp:false}
hardcode command - many other apps using that library do as they use the default template
Hack around somehow

I think that it would be nice to solve it for everybody, so I'll take the 1st approach.

@radeksimko I agree, (1) is the best.
Though, in the meantime we could simply do
diff --git a/help.go b/help.go
index 6361279..80fe465 100644
--- a/help.go
+++ b/help.go
@@ -1,13 +1,18 @@
 package main

-import "github.com/codegangsta/cli"
+import (
+       "os"
+       "path"
+
+       "github.com/codegangsta/cli"
+)

 func init() {

        cli.CommandHelpTemplate = `{{$DISCOVERY := or (eq .Name "manage") (eq .Name "join") (eq .Name "list")}}NAME:
    {{.Name}} - {{.Usage}}
 USAGE:
-   swarm {{.Name}}{{if .Flags}} [options]{{end}} {{if $DISCOVERY}}<discovery>{{end}}{{if .Description}}
+   ` + path.Base(os.Args[0]) + ` {{.Name}}{{if .Flags}} [options]{{end}} {{if $DISCOVERY}}<discovery>{{end}}{{if .Description}}
 DESCRIPTION:
    {{.Description}}{{end}}{{if $DISCOVERY}}
 ARGUMENTS:

not much of a hack to me

@vieux Cool, I can update this PR + already prepared relevant PR in upstream as mentioned earlier:
https://github.com/codegangsta/cli/pull/171

@SvenDowideit Yay or nay for this one?

@vieux PR updated, I also changed the hardcoded swarm in the list subcommand error message.

the main reason its useful, is when developing, or making a custom version, its better to see the actual name of the application - as rebuilding a custom binary is how plugins seem to be working, this will mater then too
for example, I have a set of boot2docker-v1.X binaries, and some boot2docker-v1.X-vmware (or other local hacks) - and having them all report boot2docker isn't helpful when I'm then copy and pasting that info into documentation for others to consume.

In most case, you may using alias or link -s to point differeent binary files
ln -s /path/to/real/swarm  /usr/bin/swarm-0.1 or what ever
hard code swarm is ok for me, because it save the path resolve.

@radeksimko you commited the docker-swarm binary

@vieux Noticed, fixed, you're faster then I expected :)

@radeksimko why did you cut the log.Fatalf( in 2 lines ? It's not formatted properly

nit: Why %v when Name is a string?

Fair point, sorry, changed to %s.

why did you cut the log.Fatalf( in 2 lines ? It's not formatted properly

To keep it under 80 chars per line, I put it back on one line now.

@radeksimko thanks!

LGTM


Update PopDiffSequenceData.Rmd

I've italicized the species name.

Since this is an utterly minor change, I will merge this once the checks pass.

I realized this will pass once merged with the current master branch despite the test failures.


Notebook renderer does not support application/json, text/x-html & text/x-

This doesn't seem to work as documented https://code.visualstudio.com/api/extension-guides/notebook#rich-output

Report Issue' dialog can assist with this. -->

VS Code Version: Insiders
OS Version: N/A

Steps to Reproduce:

Create a notebook serializer and generate output using:

* vscode.NotebookCellOutputItem.json({ hello: 'world' })
* vscode.NotebookCellOutputItem.text('console.log(123)', 'text/x-javascript'),

The error message in the generated output in the Notebook is  No renderer could be found for MIME type: application/json

Not sure whether its supposed to be supported or not, Perhaps need to update the documentation (if this API is still under review).
@mattbierner @rebornix /cc
FYI (Looking forward to the text/x-<languageid> renderer)

Wait, this works when using OSS. Will close for now.


Sync stops when local folder hits 200 files

I have a remote folder with >300 files. The sync stopped when the local folder hit 200 files. I deleted from the remote folder some of the files that had already been downloaded - the corresponding files in the local folder were deleted, bring the file count <200 files. Syncing resumed downloading files from the remote folder, but stopped again when the file count in the local folder hit 200 files.
The files are all image files with a .jpg extension. If needed, I will do some more testing with different file types to see if it makes a difference.

Any log? None of onedrived, ext4 (or newer file system), NTFS have such limit. If the files are very small it's likely that the requests are throttled by OneDrive server and the program has to take a nap.

Same problem here, basically for photo album with >200 files in it, it stops at 200 files. Unfortunately I don't have any log, sorry.

I am perfroming an initial sync on a Manjaro Linux Install. I will tell whether or not I have this bug and in that case, I'll give you a link to my log

Just to note:
I'm using an Asus X205TA with patched Kernel for 32bit EFi compatibility and different drivers. Using Manjaro XFCE (latest version). It's a 32bit OS. My home folder is a microSD card and I sync to ~/Onedrive and have a custom ingore_list

I can tell you that neither PDFExpert nor GoodReader on iOS which support Onedrive syncing have this problem (these program are not open source and might not even be using the same way of syncing... but I thought it was worth mentioning). There is also a Onedrive Sync app for Android. I'll try on a Chromebook w/ Android apps compatibility when I finally have the opportunity to purchase one.

I guess the server response is paged but the API doesn't reflect it. Will check this when I get time.

Same problem here
Also syncing won't continue past 4.2GB

From the OneDrive documentation:
#get the top three elements of root, leaving the next page for more elements
collection = client.item(drive='me', id='root').children.request(top=3).get()

#get the first item in the collection
item = collection[0]

#get the next page of three elements, if none exist, returns None
collection2 = onedrivesdk.ChildrenCollectionRequest.get_next_page_request(collection, client).get()

Have confirmed from my end that the "children" API have their results paged and limited to 200 entries.
Will see whether I can do a proof-of-concept fix.

metge_dir.py is the file to modify.

any updates on the issue? I am also getting the same error. Is there a config file I should modify?

@vitormilagres1992 what version are you using? Looks like there was a fix that was merged last year, so you shouldn't get this error anymore...

when I run onedrived-pref --version, I get:
onedrived-pref, version 2.0.0
Unfortunately I am still having issues with that. Is there a newer version available? What should I do to install it?


feat: add elysia middleware

Elysia is a bun framework. It uses standard Req / Resp but with an easy way to set cookie on the Response, so I created a new middleware. Tested it (reproduced the user / password + email verif examples) using bun and elysia only and it works great.

Thanks!


The document of d3d12video is missing

Link to article:
The Headers list in https://docs.microsoft.com/en-us/windows/desktop/api/index has d3d12.h, but not d3d12video.h. And all interfaces in d3d12video.h are not documented.
Problem:
d3d12video.h is in the Windows SDK since RS3. But its document is missing.

@GrantMeStrength Can you please take a look at this?

Any update? This header file was rolling out for 2 years, still no document.

This content has been written and is undergoing a technical review right now. It should be live within the next few weeks.


docs: add new tools into tools list (Issue #861)

Description

Adding new tools information
Adding links and description for new tools

Related issue(s)
Resolve #861

@jemacineiras Hi! Thanks for the PR. Could you update your PR with latest changes on master?
@alequetzalli ping, ping :)

@magicmatatjahu sure, no problem.

@jemacineiras Thanks, but I meant to update by Github UI clicking on the button on the roght of This branch is out-of-date with the base branch section. You changed files that they don't belongs to me (as codeowner), so I cannot make it for you.

@magicmatatjahu, well, that is odd, I don't see that message, neither that button you comment. Let me investigate.

@magicmatatjahu, what about now?

@jemacineiras Yeah, it works, thanks! :)

Hey @jemacineiras, I approved this now but I see that GH has found your branch out of date. Do you want to get latest and update it so that we're not blocked from merging it? :)

Hi @alequetzalli,
Done!!! :)

hey @derberg I don't understand why, but his branch keeps showing to be out od date without us having the ability in the IU to update the branch ourselves and help get his PR merged O_O

Hi @alequetzalli,
What about now?
Cheers!!

still no cigar @jemacineiras ☹ ... I genuinely have no idea why this is happening, it seems beyond a permission issue... I will ping Lukasz on slack as well today to see if he can help us figure it out 😄✌🏽

@jemacineiras I see that you first updated your fork with master from upstream, but right after you somehow merged master of your fork into master of your fork 🤔

anyway, when I go to your fork, UI indicates it is out of date
. You should see a button that will open a PR in your fork, to update with latest master. Please use it and let me know if you have some issues with it.
I also suggest to next time use https://github.com/asyncapi/community/blob/master/git-workflow.md to configure your fork properly, so on local, on your fork master will be 1:1 synced with upstream master

Hi @derberg,
I think I got some kind of mess up between my fork and original master. Once I make my changes and update from upstream it says my master was some commits in front of my local, so came the problem.
I think it is already solved.
About the guide, thanks for the heads-up, I think I missed the step 4.
Cheers

Hi @alequetzalli,
Is there any problem to merge it now?
Cheers!

Unfortunately not @jemacineiras 🫠...
I think you really messed up your branch in your fork repo… My recommendation is that you open a new branch now that you understand the steps involved and then redo this PR.
Make sure u follow the steps @derberg gave u 😀🤟🏽

Hi @alequetzalli,
I don't understand, now there is nothing wrong here. But I will throw it that and recreate the fork again

Cheers!


MOSFET-based switching instead of relays

Found some cheap Pololu MOSFET switches that can handle PWM/digital inputs signals and much faster rates of switching than physical relays. Lighter and smaller form factor than the current relay board.
Can handle 6A between 2 and 20V and only $3.49 each (would need x4 for all channels). Have ordered some to test and will report back!
When coupled with GPS, could pulse each nozzle for turn compensation.

This has now been done with the new OWL-driver board.
All details available in Discussion #108


Remember last mode

When the user leaves the home page (screen) and then returns, the last selected stopwatch mode is reset.
Please implement so that the selected mode is not reset.
Steps to reproduce the behavior

Open any project.
Start any activity.
Click on the time to switch the time display mode for the current activity.
Go to any page (screen).
Go to home page.

Actual behavior
The stopwatch displays the total time.
Expected behavior
The stopwatch displays the time of the current activity.
Screenshots

Affected versions

v1.0 (build: 20230808)

Fixed in v1.1.


Provide results of infraspective elements as objects on the pipeline

Result types
The typical PowerShell "output object paradigm" is to have an Info object type, such as PSSA.  So the object types should be named ResultInfo.
I can see two types of result objects:

Individual "Pass", "Fail", or "Skip" of a test or collection
Result totals for a collection

Individual pass, fail or skip
This type of ResultInfo should contain the 'Pass' or 'Fail' but also information that helps relay
why the element got that result (more for 'Fail' and 'Skip' ...)
Result totals for a collection
This type of ResultInfo should contain:

[ ] the accumulated totals of 'Pass' , 'Fail', etc. of it's "Children"
[ ] It's own 'Pass', 'Fail', etc. which is based on them (i.e. if there were failures, then it failed)
[ ] The ResultInfo objects of it's "Children" in "Buckets" based on their result (i.e. Failed is a collection of the elements that failed)

In pester, the smallest item is a 'Test' ( the result of an It).  However, in infraspective the smallest item is a Control.  As ResultInfo objects are collected "up the stack", the number of Passed, Failed, Skipped, etc. Controls needs to be tracked.
flowchart LR;
    classDef pass fill:#347d39;
    classDef fail fill:#7d0809;

    test1:::pass --> Control1:::fail;
    test2:::fail --> Control1;

    test3:::pass --> Control2:::pass;

    Control1 & Control2 --> Checklist1:::fail;

Control ResultInfo
this is a PSCustomObject of type Infraspective.Control.ResultInfo
The Result field is either: Passed, Failed, Skipped, or NotRun.  It will only be Passed if all the tests return Passed
Additionally, the Tests array contains the Pester Test results objects.
Finally, all of the Parameters will be "copied" into the resultinfo for processing. (i.e. Title, Name, etc)
Grouping and Checklist ResultInfo
These are "Control collections", so their Result depends on the Result of the Controls inside them.  The total is a count of the Control results.


node: delay before including Tezos operations

Depends

[ ] #483

Problem
Deku or Tezos nodes will not have clocks perfectly in sync, this means that some nodes will receive Tezos operations faster than others, if that happens to be the block producer it will include a Tezos operation not known to the others making this block to be skipped.
Solution
The ideal solution would be #481 but that is way more complex to implement, so this PR implements an workaround,. by adding a small delay between receiving a Tezos operation and actually including it on the block.

General question not related to this MR: why the file building_blocks.ml does not have the mli file?

LGTM :+1:


Set up CI, add format and test scripts.

Sets up CI, and adds format and test scripts. CI's setup and the scripts borrowed from CraneStation/wasmtime project. Also removes unused Cargo dependencies and fixes a trivial numeric cast.

Done. I'll backport it to wasmtime too.

Also, I've had to move trivial_numeric_casts from #deny to #warn as this can lead to tricky behaviour depending on the OS we're compiling on (libc::stat::FileStat::st_ino resolving to a type different than u64 on mac, but on linux).

Looks good!


gcc14, gfortran14, gnat14, gccgo14: init at 14.1.0

Changes: https://gcc.gnu.org/gcc-14/changes.html
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 309788 run on x86_64-darwin 1

10 packages failed to build:

fastStdenv (gcc14Stdenv)
gcc14 (gcc_latest)
gcc14.info (gcc_latest.info)
gcc14.man (gcc_latest.man)
gfortran14
gfortran14.info
gfortran14.man
gnat14
gnat14.info
gnat14.man

Will have a look at darwin failures later today. Probably stale patches we might have to skip.

Result of nixpkgs-review pr 309788 run on x86_64-linux 1

15 packages built:

fastStdenv
gcc14 (gcc_latest)
gcc14.info (gcc_latest.info)
gcc14.man (gcc_latest.man)
gcc14Stdenv
gccgo14
gccgo14.info
gccgo14.man
gfortran14
gfortran14.info
gfortran14.man
gnat14
gnat14.info
gnat14.man
tests.cc-wrapper.supported

Will have a look at darwin failures later today. Probably stale patches we might have to skip.

Probably not patches, but a Darwin framework:
ld: framework not found CoreServices
clang-16: error: linker command failed with exit code 1 (use -v to see invocation)
make[3]: *** [Makefile:3284: gcov] Error 1
make[3]: *** Waiting for unfinished jobs....

Result of nixpkgs-review pr 309788 run on aarch64-darwin 1

7 packages built:

fastStdenv (gcc14Stdenv)
gcc14 (gcc_latest)
gcc14.info (gcc_latest.info)
gcc14.man (gcc_latest.man)
gfortran14
gfortran14.info
gfortran14.man

I think I'll leave x86_64-darwin support as an exercise for ZHF, or if @reckenrode has an idea?

I’ll try it on my ld64 update branch when I get home. It may be that GCC 14 is broken until the linker can be updated.
I’m pretty sure GNAT should build with it as well. It has a bit of a weird set up with dual linkers.

Probably not patches, but a Darwin framework (and yes, again from gettext 0.22)

Is GCC vendoring gettext 0.22? I thought we were still on 0.21.

No, they just imported some .m4 files from gettext 0.22 for compatibility.

I get a different crash with ld 951.9. See the gist for the full crash log from Console.app.
ld: warning: object file (/nix/store/krwh63risgpkdw9x3d6ih9jqadl6v3aa-Libsystem-1238.60.2/lib/dylib1.10.5.o) was built for newer macOS version (10.6) than being linked (10.5)
ld: warning: dylib (/nix/store/ali57avprggl9jwd2lsk2x263yjih857-gettext-0.21.1/lib/libintl.dylib) was built for newer macOS version (10.12) than being linked (10.5)
/nix/store/ym3pmv0v68h7qgn5466922djjxa4kisw-clang-wrapper-18.1.5/bin/ld: line 266: 66010 Segmentation fault: 11  /nix/store/5dqbjcafpjmpiwj9bxv89zqiln0fr7qs-cctools-binutils-darwin-1010.6/bin/ld ">
collect2: error: ld returned 139 exit status

https://gist.github.com/reckenrode/52a42d70480d5cef9cae8499d49019dd

I created an ld-wrapper around ld-prime from the latest command-line tools. It also crashes. Next steps are trying to build the bootstrap stage with GCC 13 (in case GCC is somehow causing clang to generate bad code). If that doesn’t work, then try linking with LLD.
ld: warning: -single_module is obsolete
ld: warning: duplicate -rpath '/Users/reckenrode/Developer/nixpkgs/outputs/lib/lib' ignored
ld: warning: duplicate -rpath '/nix/store/krwh63risgpkdw9x3d6ih9jqadl6v3aa-Libsystem-1238.60.2/lib' ignored
ld: warning: duplicate -rpath '/Users/reckenrode/Developer/nixpkgs/outputs/lib/lib' ignored
ld: warning: duplicate -rpath '/nix/store/krwh63risgpkdw9x3d6ih9jqadl6v3aa-Libsystem-1238.60.2/lib' ignored
ld: warning: duplicate -rpath '/Users/reckenrode/Developer/nixpkgs/outputs/lib/lib' ignored
ld: warning: duplicate -rpath '/nix/store/krwh63risgpkdw9x3d6ih9jqadl6v3aa-Libsystem-1238.60.2/lib' ignored
ld: warning: support for macOS with 10.5 minimum deployment target is deprecated and will be removed in future release
ld: warning: object file (//nix/store/krwh63risgpkdw9x3d6ih9jqadl6v3aa-Libsystem-1238.60.2/lib/dylib1.10.5.o) was built for newer macOS version (10.6) than being linked (10.5)
0  0x102941807  __assert_rtn + 137
1  0x102952223  ld::passes::stubs::x86_64::classic::LazyPointerAtom::LazyPointerAtom(ld::passes::stubs::Pass&, ld::Atom const&, bool, bool) (.cold.1) + 35
2  0x1028802ef  ld::passes::stubs::x86_64::classic::LazyPointerAtom::LazyPointerAtom(ld::passes::stubs::Pass&, ld::Atom const&, bool, bool) + 431
3  0x10287ca3c  ld::passes::stubs::Pass::makeStub(ld::Atom const&, bool) + 5484
4  0x10287df00  ld::passes::stubs::Pass::process(ld::Internal&) + 1792
5  0x10287e46d  ld::passes::stubs::doPass(Options const&, ld::Internal&) + 109
6  0x1026ce75e  main + 1070
A linker snapshot was created at:
	/tmp/libgcc_s.dylib-2024-05-08-075121.ld-snapshot
ld: Assertion failed: (targetAtom != NULL), function Fixup, file ld.hpp, line 1045.
collect2: error: ld returned 1 exit status

Nope, using gcc13Stdenv also results in a crash.

(By the way, gnat{11,12,13} also fails on x86_64-darwin on master)

gnat11 is failing because CC is set to clang instead of gcc. It needs the same stdenv override in all-packages.nix as gnat12 and gnat13. Once that’s set, it fails with the same error as gnat12 and gnat13.
configure: error: cannot compute suffix of object files: cannot compile

gnat sets AS_FOR_TARGET to ${gnat-bootstrap}/bin/gas, but that path doesn’t exist. The gnat wrapper isn’t picking up gas from the special bintools it uses (bintoolsDualAs). However,  I wonder if the reasoning for using both assemblers holds anymore. x86_64-darwin now uses the clang assembler by default, so the issue with the GNU assembler in cctools should no longer be a problem.

Building gnat{11,12,13} on x86_64-darwin is fixed in https://github.com/NixOS/nixpkgs/pull/310450.

So let's put x86_64-darwin in badPlatforms and merge this, if there's no workaround yet?

So let's put x86_64-darwin in badPlatforms and merge this, if there's no workaround yet?

I think I found the issue. If I manually the command-line linking libgcc_s.dylib to use -mmacosx-version-min=10.6, linking succeeds. Looking at config.host, GCC is defaulting to building for macOS 10.5 as the minimum instead of 10.8, which works. It’s similar to https://github.com/NixOS/nixpkgs/pull/265935/commits/c6ab64adbfd051383fcd60ac661af7a3aa85b9f1.
The following patch should fix building GCC 14 on Darwin:
diff --git a/pkgs/development/compilers/gcc/patches/14/libgcc-darwin-detection.patch b/pkgs/development/compilers/gcc/patches/14/libgcc-darwin-detection.patch
new file mode 100644
index<PHONE_NUMBER>00..8a4ccd1b8d84
--- /dev/null
+++ b/pkgs/development/compilers/gcc/patches/14/libgcc-darwin-detection.patch
@@ -0,0 +1,12 @@
+diff -u a/libgcc/config.host b/libgcc/config.host
+--- a/libgcc/config.host	2023-11-05 11:01:55.778638446 -0500
++++ b/libgcc/config.host	2023-11-05 11:07:29.405103979 -0500
+@@ -227,7 +227,7 @@
+   tmake_file="$tmake_file t-slibgcc-darwin"
+   # newer toolsets produce warnings when building for unsupported versions.
+   case ${host} in
+-    *-*-darwin1[89]* | *-*-darwin2* )
++    *-*-darwin1[89]* | *-*-darwin2* | *-*-darwin)
+       tmake_file="t-darwin-min-8 $tmake_file"
+       ;;
+     *-*-darwin9* | *-*-darwin1[0-7]*)
diff --git a/pkgs/development/compilers/gcc/patches/default.nix b/pkgs/development/compilers/gcc/patches/default.nix
index b170561ce624..a89bc17a1dd8 100644
--- a/pkgs/development/compilers/gcc/patches/default.nix
+++ b/pkgs/development/compilers/gcc/patches/default.nix
@@ -138,6 +140,9 @@ in

 ## Darwin

+# Fixes detection of Darwin on x86_64-darwin. Otherwise, GCC uses a deployment target of 10.5, which crashes ld64.
+++ optional (atLeast14 && stdenv.isDarwin && stdenv.isx86_64) ../patches/14/libgcc-darwin-detection.patch
+
 # Fix detection of bootstrap compiler Ada support (cctools as) on Nix Darwin
 ++ optional (atLeast12 && stdenv.isDarwin && langAda) ./ada-cctools-as-detection-configure.patch

I completely forgot that some of the conditional patches need to be explicitly moved to gcc14.
Added as:
--- a/pkgs/development/compilers/gcc/patches/default.nix
+++ b/pkgs/development/compilers/gcc/patches/default.nix
@@ -65,6 +65,7 @@ in
 ++ optionals (noSysDirs) (
   [(if atLeast12 then ./gcc-12-no-sys-dirs.patch else ./no-sys-dirs.patch)] ++
   ({
+    "14" = [ ./13/no-sys-dirs-riscv.patch ./13/mangle-NIX_STORE-in-__FILE__.patch ];
     "13" = [ ./13/no-sys-dirs-riscv.patch ./13/mangle-NIX_STORE-in-__FILE__.patch ];
     "12" = [ ./no-sys-dirs-riscv.patch ./12/mangle-NIX_STORE-in-__FILE__.patch ];
     "11" = [ ./no-sys-dirs-riscv.patch ];

Does gnat 14 need the same fixes from https://github.com/NixOS/nixpkgs/pull/310450?

It's missing CoreServices again...


Support issue tag on stackoverflow

I've read a suggestion that any support requests should be made on stackoverflow.
Sadly that design-system-react tag does not appear to exist yet.

My reputation is far too low to create this tag. 😢   Can anybody help?

I'm in the same boat.

Over 7 days have passed.

It would be helpful if anybody could create this tag.  I noticed that a react tag exists and perhaps this is an alternative.


HADOOP-17302. Upgrade to jQuery 3.5.1 in hadoop-sls.

NOTICE
jQuery is upgraded from 3.3.1 to 3.5.1 at
hadoop/hadoop-tools/hadoop-sls/src/main/html/js/thirdparty

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
43m  2s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
jshint
0m  0s

jshint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
36m  0s

trunk passed

+1 :green_heart:
compile
0m 31s

trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
compile
0m 29s

trunk passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

+1 :green_heart:
mvnsite
0m 34s

trunk passed

+1 :green_heart:
shadedclient
55m 21s

branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 28s

trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javadoc
0m 28s

trunk passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 30s

the patch passed

+1 :green_heart:
compile
0m 25s

the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javac
0m 25s

the patch passed

+1 :green_heart:
compile
0m 21s

the patch passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

+1 :green_heart:
javac
0m 21s

the patch passed

+1 :green_heart:
mvnsite
0m 26s

the patch passed

-1 :x:
whitespace
0m  0s
/whitespace-tabs.txt
The patch 910 line(s) with tabs.

+1 :green_heart:
shadedclient
17m 35s

patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 24s

the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javadoc
0m 22s

the patch passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

_ Other Tests _

+1 :green_heart:
unit
12m  3s

hadoop-sls in the patch passed.

+1 :green_heart:
asflicense
0m 33s

The patch does not generate ASF License warnings.

134m 59s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2379/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2379

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient jshint

uname
Linux 83d3916d81fb 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 69ef9b1ee88

Default Java
Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2379/1/testReport/

Max. process+thread count
454 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-sls U: hadoop-tools/hadoop-sls

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2379/1/console

versions
git=2.17.1 maven=3.6.0

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


Set version to match the Spine version.

@dmdashenkov the version was not set. PTAL.

Current coverage is 91.17% (diff: 100%)

Merging #13 into master will not change coverage

@@             master        #13   diff @@
==========================================
  Files            64         64
  Lines          1281       1281
  Methods           0          0
  Messages          0          0
  Branches         64         64
==========================================
  Hits           1168       1168
  Misses           86         86
  Partials         27         27

Powered by Codecov. Last update 6d8b866...ae33207


pull request for e2e test at 12/29/2016 22:26:11

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


cannot start EC2 cluster - docker: Error response from daemon

I am using the rancher AMI (us-east-1 | HVM | ami-03383c16defb1ed02).
2019/12/16 14:09:17 [INFO] [node-controller-docker-machine] Creating CA: /management-state/node/nodes/rancher1/certs/ca.pem
2019/12/16 14:09:18 [INFO] [node-controller-docker-machine] Creating client certificate: /management-state/node/nodes/rancher1/certs/cert.pem
2019/12/16 14:09:18 [INFO] [node-controller-docker-machine] Running pre-create checks...
2019/12/16 14:09:18 [INFO] [node-controller-docker-machine] Creating machine...
2019/12/16 14:09:18 [INFO] [node-controller-docker-machine] (rancher1) Launching instance...
2019/12/16 14:09:56 [INFO] [node-controller-docker-machine] Waiting for machine to be running, this may take a few minutes...
2019/12/16 14:09:57 [INFO] [node-controller-docker-machine] Detecting operating system of created instance...
2019/12/16 14:09:57 [INFO] [node-controller-docker-machine] Waiting for SSH to be available...
2019/12/16 14:10:44 [INFO] [node-controller-docker-machine] Detecting the provisioner...
2019/12/16 14:10:44 [INFO] [node-controller-docker-machine] Provisioning with rancheros...
2019/12/16 14:12:57 [INFO] [node-controller-docker-machine] Copying certs to the local machine directory...
2019/12/16 14:12:59 [INFO] [node-controller-docker-machine] Copying certs to the remote machine...
2019/12/16 14:13:01 [INFO] [node-controller-docker-machine] Setting Docker configuration on the remote daemon...
2019/12/16 14:13:06 [INFO] [node-controller-docker-machine] Checking connection to Docker...
2019/12/16 14:13:06 [INFO] [node-controller-docker-machine] Docker is up and running!
2019/12/16 14:13:21 [INFO] Generating and uploading node config rancher1
2019/12/16 14:13:21 [ERROR] NodeController c-g2c48/m-k82c4 [node-controller] failed with : Unable to find image 'rancher/rancher-agent:v2.3.3' locally
docker: Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See 'docker run --help'.
Process exited with status 125
: exit status 1

Useful
Info

Versions
Rancher v2.3.3 UI: v2.3.25

Route
global-admin.clusters.index

rancher server
docker run -d --restart=unless-stopped -p 80:80 -p 443:443 rancher/rancher:latest

Sounds like a network related error, probably a (host) firewall. Can you manually run docker pull rancher/rancher-agent:v2.3.3? The timeout suggest it can't reach the Docker Hub to retrieve the image.

@superseb I cannot ssh the machine, a password is required

How to access the machine is described at https://rancher.com/docs/rancher/v2.x/en/faq/technical/#how-can-i-access-nodes-created-by-rancher

@superseb thanks but that's not possible. Since Docker fails to retrieve the required image, the machine is being destroyed and created over and over again. At no point, the "Nodes view" is available in Rancher portal.

Probably the best way to investigate this is to look in the AWS console, look up the created instance and see what VPC and Security Groups it gets assigned, and what IP address the machine gets.
Compare that to the values you get when you manually create an EC2 instance and install Docker and run docker pull to reach out to Docker Hub to retrieve images to see where the differences are.

Let me know if this needs help


Fix a link in CONTRIBUTING.md

As an addition to https://github.com/google/material-design-lite/pull/837

Thanks!


Creating and clarifying license as MIT

…g commit within forked-base repo pinlunhuang/Voice-Recorder.

Any thoughts on this?

Sorry to reply too late.
I've merged the request.


Compile on GitHub using goreleaser

Codecov Report

Merging #59 (7ceaca6) into main (9c57054) will decrease coverage by 0.12%.
The diff coverage is 41.66%.

@@            Coverage Diff             @@
##             main      #59      +/-   ##
==========================================
- Coverage   75.51%   75.38%   -0.13%
==========================================
  Files          56       56
  Lines        3128     3140      +12
==========================================
+ Hits         2362     2367       +5
- Misses        666      673       +7
  Partials      100      100

Impacted Files
Coverage Δ

cmd/pint/main.go
72.60% <41.66%> (-6.09%)
:arrow_down:

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 9c57054...7ceaca6. Read the comment docs.


[Digital Twins] Error when paging relationships records

Package Name: @azure/digital-twins
Package Version: 1.0.0-preview.1
Operating system: macOS
[ ] nodejs

version:

[X] browser

name/version: Chrome 85

[ ] typescript

version:

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
When a twin has more relationships than can be returned in one page, the SDK automatically fetches the next page using the continuation token. However, from what I can see, the token is passed in the wrong place to the underlying REST SDK which results in an invalid URL being formed.
To Reproduce
Steps to reproduce the behavior:

Create a twin with more than 10 outgoing relationships.
Call the listRelationships method for the twin.

Expected behavior
All relationships should be returned.
Screenshots
N/A
Additional context
See this line. The underlying REST client expects the continuation token as the second parameter but it's passed as the first one. This issue also applies to incoming relationships.

Thanks for reporting @jamescarpinter
@zolvarga, Can you take a look at this issue and the corresponding PR https://github.com/Azure/azure-sdk-for-js/pull/11556 ?

@zolvarga I see that the PR #11556 is merged, but the fix has not been released yet. What are the plans for the release here?

@zolvarga I see that the PR #11556 is merged, but the fix has not been released yet. What are the plans for the release here?

@jamescarpinter The package @azure/digital-twins has been renamed to @azure/digital-twins-core which has since had releases which contain the fix to this issue.
Thanks for reporting and sending the PR

@jamescarpinter The package @azure/digital-twins has been renamed to @azure/digital-twins-core which has since had releases which contain the fix to this issue.
Thanks for reporting and sending the PR


Ingress port showing incorrect port

When creating an Ingress resource with the following annotations
 oci-native-ingress.oraclecloud.com/backend-tls-enabled: "false"
 oci-native-ingress.oraclecloud.com/https-listener-port: "443"

With the following rules
tls:
  - hosts:
    - my.example.com
    secretName: tls-secret
  rules:
    - host: "my.example.com"
      http:
        paths:
          - pathType: Exact
            path: "/testecho1"
            backend:
              service:
                name: testechoone
                port:
                  number: 8081
          - pathType: Exact
            path: "/testecho2"
            backend:
              service:
                name: testechotwo
                port:
                  number: 8080

kubectl get ingress returns
NAMESPACE   NAME                CLASS             HOSTS            ADDRESS           PORTS     AGE
default     ingress-readiness   ingress-class-1   my.example.com   <redacted>   80, 443   4d1h

I would expect the ingress port to only show 443 since I only have 1 listener which is listening on port 443. Is this intended?

Hi @matthewmcdaniel,
The ports you see  in the kubectl get ingress return is because of how Kubernetes handles Ingress objects. Port 80 will always show up there, and if you have a tls configuration in your Ingress spec 443 will be added. You can verify this by changing oci-native-ingress.oraclecloud.com/https-listener-port to say, 500, and you will see the same output on kubectl get ingress. In short: You can ignore the ports that show up here.
A kubectl describe ingress here will not show 80 anywhere, and in reality only a single listener will be created on the LB managed by NIC at 443. The Ingress resource is something the NIC acts upon and doesn't show the resources (listeners, routing policies, etc.) created on the OCI LB as those are implementation details specific to the OCI NIC.
Hope that answers your question.

Thank you for the clarification, will close this issue.


Dashboard is blank when launched as standard cluster owner

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Create a standard user.
Assign the user as cluster owner of a cluster/
Login as standard user.
Go to cluster and launch 'Try Dashboard'.

Result:
Url is redirecting to 'dashboard/error'.
UI is blank

Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master-2463-head- e651c7a81
Installation option (single install/HA): Single

Tracked by https://github.com/rancher/dashboard/issues/372


Allow creating a new toolchain from an existing one

Problem you are trying to solve
Currently when you create a new toolchain, it is totally blank and you have to install each component one by one.
Solution you'd like
It would be nicer if the toolchain could be created by cloning existing toolchain and modifying the components from there.
Something like:
# Create a custom toolchain called "my-custom" with with the same components and version as beta-5

# Option 1
fuelup toolchain new my-custom-name beta-5

# Option 2
fuelup toolchain new --clone beta-5 my-custom-name

# Option 3
fuelup toolchain new --source beta-5 my-custom-name

Notes
No response

Sounds like a great idea. I like the look of option 2 the best out of this list.


ci: add release workflow

ci: use PAT

ci: fix release assets upload issue

ci: rename wasm file with version on filename

ci: add changelog in release

Description:
Commit Message
type: commit message

see the guidelines for commit messages.
Changelog Entry
version: <log entry>

Checklist:

[x] I have performed a self-review of my own code
[ ] I have documented my code in accordance with the documentation guidelines
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have run the unit tests
[ ] I only have one commit (if not, squash them into one commit).
[ ] I have a descriptive commit message that adheres to the commit message guidelines

Please review the CONTRIBUTING.md file for detailed contributing guidelines.

Codecov Report

Merging #572 (a0ee9b7) into main (8b3dbac) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main     #572   +/-   ##
=========================================
  Coverage     62.77%   62.77%
  Complexity      404      404
=========================================
  Files           156      156
  Lines         14761    14761
  Branches        292      292
=========================================
  Hits           9266     9266
  Misses         5339     5339
  Partials        156      156

Flag
Coverage Δ

java
80.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@DeepakBomjan  i think we would also need to do a version bump. For rust contracts bumping version on workspace cargo.toml should be enough.

Issue covered:
#563

@DeepakBomjan i think we would also need to do a version bump. For rust contracts bumping version on workspace cargo.toml should be enough.

Automatic version bump will be covered on #627


Instances of typeof spec'd types cannot be assigned to many feasible, explicitly typed variables

The typeof type operator doesn't play nice with inheritance.  Since ES6 classes inherit static methods, I think that aX and bX below should typecheck.
class Base {}
class Derived extends Base {}

var A: typeof Base = Derived;
var B: typeof Derived = Derived;

var a1: Derived = new A(); // Legitimate NG
var a2: Base = new A(); // NG
var a3: A = new A(); // NG

var b1: Derived = new B(); // OK
var b2: Base = new B(); // NG
var b3: B = new B(); // OK

I came across this problem while creating a class factory function that also fails:
function bindParams(P1): typeof Base {
  class T extends Base {
    static params() {
      return [P1];
    }
  }
  return T; // NG
}

I am running into this limitation as well. My use case is trying to make a function declaration for Immutable.js's Record function that returns a new class.

Maybe I should have mentioned my use case also?  I'm migrating a serialization library to ES6+BabelJS+Flow, and I need this to (nicely) support generics, e.g.
class SomeGeneric {
    static bindParams(T, U) {
        class BoundGeneric extends Base {
            static params() {
                return [P1];
            }
            // ...
        }
        return SomeGeneric;
    }
}

Looks like these uses belong to the Class<T>-syntax now.  I don't see much value in any thread members beyond the first, so I'm closing this and opening an updated issue.


Update instructions for standalone installation

This PR updates instructions to reflect the 1.0-beta directory structure which no longer includes a /node_modules/laravel-mix/setup/webpack.mix.js configuration file (see #860). These instructions are compatible with laravel-mix =< 1.0-beta as well.

Thanks so much for this, but I've already updated the docs to reflect the changes.

Hooray!)


allow versioned symlinks

[x] support semver ranges on tea -X
[x] support semver ranges on symlinks
[x] support links to semver ranged symlinks (yup, really: node > node^16 > tea)
[x] expand symlink README documentation to cover new feature
[x] implement test for new feature

Ugh. Typo in the readme. Need to reverse ln arguments in the second invocation in the script. Tomorrow.

Don’t see the harm in it and probably will be considered a nice feature by many. Though we should document that python3 == python^3 (we already support that).

Though we should document that python3 == python^3 (we already support that).

Added that, and cleaned up my typo, as well as using explicit paths to avoid confusion.

Wonderful additions Jacob