dask.async.RuntimeError: NetCDF: HDF error on xarray to_netcdf

Dask appears to be failing on serialization following a ds.to_netcdef() via a NETCDF: HDF error.
Excerpted error below:
Traceback (most recent call last):
  File "reduce_dispersion_file.py", line 40, in <module>
    if __name__ == "__main__":
  File "reduce_dispersion_file.py", line 36, in reduce_dispersion_file
    with timeit_context('output to disk'):
  File "/users/pwolfram/envs/LIGHT_analysis/lib/python2.7/site-packages/xarray/core/dataset.py", line 791, in to_netcdf
    engine=engine, encoding=encoding)
  File "/users/pwolfram/envs/LIGHT_analysis/lib/python2.7/site-packages/xarray/backends/api.py", line 356, in to_netcdf
    dataset.dump_to_store(store, sync=sync, encoding=encoding)
  File "/users/pwolfram/envs/LIGHT_analysis/lib/python2.7/site-packages/xarray/core/dataset.py", line 739, in dump_to_store
    store.sync()
  File "/users/pwolfram/envs/LIGHT_analysis/lib/python2.7/site-packages/xarray/backends/netCDF4_.py", line 283, in sync
    super(NetCDF4DataStore, self).sync()
  File "/users/pwolfram/envs/LIGHT_analysis/lib/python2.7/site-packages/xarray/backends/common.py", line 186, in sync
    self.writer.sync()
  File "/users/pwolfram/envs/LIGHT_analysis/lib/python2.7/site-packages/xarray/backends/common.py", line 165, in sync
    da.store(self.sources, self.targets)
  File "/users/pwolfram/lib/python2.7/site-packages/dask/array/core.py", line 712, in store
    Array._get(dsk, keys, **kwargs)
  File "/users/pwolfram/lib/python2.7/site-packages/dask/base.py", line 43, in _get
    return get(dsk2, keys, **kwargs)
  File "/users/pwolfram/lib/python2.7/site-packages/dask/threaded.py", line 57, in get
    **kwargs)
  File "/users/pwolfram/lib/python2.7/site-packages/dask/async.py", line 481, in get_async
    raise(remote_exception(res, tb))
dask.async.RuntimeError: NetCDF: HDF error

Traceback
---------
  File "/users/pwolfram/lib/python2.7/site-packages/dask/async.py", line 264, in execute_task
    result = _execute_task(task, data)
  File "/users/pwolfram/lib/python2.7/site-packages/dask/async.py", line 246, in _execute_task
    return func(*args2)
  File "/users/pwolfram/lib/python2.7/site-packages/dask/array/core.py", line 1954, in store
    out[index] = np.asanyarray(x)
  File "netCDF4/_netCDF4.pyx", line 3678, in netCDF4._netCDF4.Variable.__setitem__ (netCDF4/_netCDF4.c:37215)
  File "netCDF4/_netCDF4.pyx", line 3887, in netCDF4._netCDF4.Variable._put (netCDF4/_netCDF4.c:38907)

Script used: https://gist.github.com/98acaa31a4533b490f78
Full output: https://gist.github.com/248efce774ad08cb1dd6

cc @mrocklin

I should note that serialization also does not appear to be robust under reshaping the data via ds = ds.transpose('Nt','Nt-1','Nr','Nb','Nc') as well as rechunking.  The input data stream was previously generated via a call to ds.to_netcdf in another script using xarray.

There are a large number of files (1320) where nfiles = 120 and len(dslist)=11, so perhaps this is an issue with opening a large number of files as noted by @rabernat.

1024 might be a common open file handle limit.  Some things to try to isolate the issue:

Try this with dask.set_globals(get=dask.async.get_sync) to turn off threading
Try just opening all of the files and see if the NetCDF error presents itself under normal operation

Quick question @mrocklin, for 2, are you proposing a script that just opens all the files, e.g., something like this
# get full xr dataset
dslist = []
nfiles = len(glob.glob('dispersion_calcs_rlzn0*layerrange_0000-0000.nc'))
for i in np.arange(nfiles):
  ds = xr.open_mfdataset('dispersion_calcs_rlzn%04d_*nc'%(i))
  dslist.append(ds)
dstotal = xr.concat(dslist,'Nr')
# do an operation spanning Nr space and Nb space
print dstotal.dtdays.values

where dtdays spans the all the files?

Sure.  I'm not proposing any particular approach.  I'm just supporting your previous idea that maybe the problem is having too many open file handles.  It would be good to check this before diving into threading or concurrency issues.

Agreed.  I'll let you know what I find out.  Thanks @mrocklin.

Test 2 passed, so it doesn't appear to be due to too many open file handles.

For option 1, should the command be dask.set_options(get=dask.async.get_sync)?  I'm on 0.8.0

Yes, my apologies for the typo.

I'm pretty sure we now have a thread lock around all writes to NetCDF files, but it's possible that isn't aggressive enough (maybe we can't safely read and write a different file at the same time?). If your script works with synchronous execution I'll take another look.

I can't fully confirm that the above scripts works with synchronous execution because the job ran out of its 16hr run time.  However, it does appear to be the case that forcing synchronous execution resolves potential issues because previous runs of the script crashed and this one did not.  I'll have to try more cases with synchronous execution, especially over the next half week, to see if I encounter more issues but am suspicious this is the problem.
@mrocklin and I noted that the netCDF reader has problems when threading is on when we were using distributed, so this appears to be a likely candidate.  We got the same NetCDF: HDF error error as above, and were able to resolve the issue by forcing distributed to work synchronously (non-threaded).  @mrocklin should feel free to correct me if I've miss-represented our findings yesterday.
I'm suspicious that the netCDF reader is not thread safe and may not have been compiled as such (http://hdf-forum.184993.n3.nabble.com/Activate-thread-safe-and-enable-cxx-in-HDF5-td2993951.html) but there appear other potential issues that could be part of the problem, e.g., https://github.com/Unidata/netcdf4-python/issues/279 because I am doing so many reads.  It may also be possible, as you note @shoyer, that the tread locks aren't aggressive enough.
It would probably be good to come up with some type of testing strategy to better isolate the problem... I'll have to give this more thought.

To be clear, we ran into the NetCDF: HDF error error when having multiple threads in the same process open-read-close many different files.  I don't think there was any concurrent access of the same file.  The problem went away when we switched to using processes rather than threads.

I did a little digging into this and I'm pretty sure the solution the issue here is that HDF5 cannot do multi-threading -- at all. Moreover, many HDF5 builds are not thread safe.
Right now, we use a single shared lock for all reads with xarray, but for writes we rely on dask.array.store, which only uses different locks for each array it writes. Because @pwolfram's HDF5 file includes multiple variables, each of these gets written with their own thread lock -- which means we end up writing to the same file simultaneously from multiple threads.
So what we could really use here is a lock argument to dask.array.store (like dask.array.from_array) that lets us insist on a using a shared lock when we're writing HDF5 files. Also, we may need to share that same lock between reading and writing data -- I'm not 100% sure. But at the very least we definitely need a lock to stop HDF5 from trying to do multi-threaded writes, whether that's to the same or different files.

@thanks @shoyer for looking into this further and for figuring out the cause of the problem.  @mrocklin, does this mean that I should submit a dask issue?

https://github.com/dask/dask/pull/1053

@shoyer, I'm assuming there needs to be an xarray PR corresponding to Matt's merged PR, is that correct?  Do you think this will be a difficult xarray change?

This should be pretty easy -- we'll just need to add lock=threading.Lock() to this line:
https://github.com/pydata/xarray/blob/v0.7.2/xarray/backends/common.py#L165
The only subtlety is that this needs to be done in a way that is dependent on the version of dask, because the keyword argument is new -- something like if dask.__version__ > '0.8.1'.

Thanks @shoyer!  I ran into this problem again with this morning and as you note I had multiple arrays in the file that were being written.  PR https://github.com/pydata/xarray/pull/800 implements your suggestion and should hopefully resolve the issue, although it is not clear to me how to build a reproducible test case-- perhaps write a file with a ton of random arrays and try to crash it out?  Any thoughts or suggestions you have on this would be very helpful.
Note that the PR is preliminary until I can verify that it resolves the issue via testing.

Note, also waiting on dask going to 0.8.2 version number for the full fix.

I'm going to close this for now but will reopen it if the issue crops up again following the dask release.


Use max_VDIM instead of VDIM in FaceQuadratureInterpolator::Eval3D.

I'm not sure how this code was compiling and running before...

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

Why didn't we see this? What kind of test would have caught it?

This method is never instantiated with T_VDIM == 0, so the value of VDIM is known at compile time (and it is the same as max_VDIM and T_VDIM. If you try to instantiate with T_VDIM == 0, then you'll get an error in CI since the arrays become VLA and we check for that with -pedantic -Werror.


Font for Ukrainian language

Hello. Could you please create this font for Ukrainian language, because I'm not good at coding. I checked for English, it works very good but for Ukrainian language it works with mistakes. Thx in advance.

Hi,
the current font just support standard cyrillic.
I'm not that familiar with Ukrainian, but I think you have some special characters that deviate from the standard russian cyrillic alphabet, right?
Unfortunately the current font just supports the standard glyphs, so I would need another one.
Therefore I would need an open-source ukrainian font that contains all the ukrainian glyphs and is well suited for speed-reading.
Do you have any font-recommendation?


edited the lumpsum error

@ighoshsubho
lumpsum is getting 500 server error,
now it is working. please check

Seems good @idiotcommerce, try adding the issue number to this!


Update/Get Block User list

I've gone through the websdk documentation, but I can't find any available method for managing a user's block list. Is there any support for it? If no, what is the best way to achieve it with the websdk, I'm willing to put together a PR for it. Thanks.

The WebSDK talks to Layer's Client API.  If the Client API supports something, odds are, the WebSDK does to.  Once the server team adds support for Blocking to the Client API, the WebSDK can add it.  This won't happen in the next few months.
For now, your best bet is to user Layer's Server API.  You would do this by having the browser send a request to your server, and your server would then send the block request to Layer's Server API.

Thanks @michaelkantor.


use chalk, yargs, y18n, yargonaut

Fair warning, I'm not a Javascript guy.

added .editorconfig
use chalk and yargs instead of commander and custom function
changed script name test to lint (cause that's what it is?)

I wasn't sure how to test this. Feedback is welcome, should I need to change anything.

For yargs should be able to use .locale in combination with .updateStrings. Haven't found out how exactly, yet. Will update as soon as I did.

@QingWei-Li Not sure whether or not chalk should be in package.json. yargonaut uses it.

@jrappen chalk is required if the user is using npm 2

@jrappen
Thank you for your contribution.
I tried it, but it did not work for me.
➜  docsify-cli git:(master) ✗ docsify serve docs
➜  docsify-cli git:(master) ✗

😢

feel free to revert, I'll review the yargs docs

apparently I cannot put .option after builder: (yargs) => return yargs


DOCSP-10188: fix yaml file preventing docs build

This yaml file entry needs to include the interface, operation, and optional keys for the documentation to build. Please review when you get the chance so that I can publish the docs, thanks!

Manually merged to v1.7 in https://github.com/mongodb/mongo-php-library/commit/8ff57584f582594473287dc77e1d84b30039b2e4. Thanks!

@ccho-mongodb: The commit has also been merged up to master so it should fix the build for the "upcoming" branch in https://github.com/mongodb/docs-php-library/commit/4daeded3322ec857114154b5e82bad10e6bdd955. Based on that, I assume nothing is building v1.7 directly, but perhaps it makes sense to briefly point "upcoming" to v1.7 and leave master dangling. I don't feel strongly either way, as v1.7 will become "current" in just a few weeks.

I see, could we also merge into master since I need to build the docs master branch (as well as every other version branch) in order to update the version selector?

This has already been merged to master in https://github.com/mongodb/mongo-php-library/commit/81a57c0d1fca902ae74eb4ae24f4ca23dbb08782. That's what I meant by "has also been merged up to master" in my last comment :)

Ah sorry, missed that part. There's a strange bug in the version selector such that v1.7 is not redirecting to the appropriate content which I am currently chasing with the Docs Platform team.


Update Identifiers / Reply URL / Sign on URL

[Enter feedback here]
In Doc example of -> https://github.com/enterprises/* is given.
This needs to be updated to Patterns: https://github.com/orgs/*

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

ID: 38ddf301-6502-8b20-243e-7af24023e3cd
Version Independent ID: ae6a3790-e090-de5d-4e13-7b4d3f8c35b9
Content: Tutorial: Azure Active Directory single sign-on (SSO) integration with GitHub Enterprise Cloud - Enterprise Account
Content Source: articles/active-directory/saas-apps/github-enterprise-cloud-enterprise-account-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@404cruX
Thanks for your feedback! We will investigate and update as appropriate.

@404cruX
Thanks for your feedback! I have assigned this issue to the author who will investigate and update as appropriate.

#please-close


Develop

Update main branch with video link for 3.6 release and some cleanup.

Test pull request. Closing.


Adding Middleware Section

Now that CakePHP is supporting Middleware, I feel that a middleware section is needed. I have also submitted my new CakeMiddlewares repo to start it off.

I am not too sure why Travis failed

I don't think are going to be many plugins with a bunch of middleware for various purposes to warrant a separate category.

Oh, I did not mean it just for plugins that have middleware for various purposes. I just meant that, with MIddleware being such a new thing for Cake, it might be useful to have a section dedicated to that for quick reference.

Would y'all prefer me to add it under miscellaneous?

Would y'all prefer me to add it under miscellaneous?

Yes please.

@ADmad Alright, miscellaneous it is!

What do I need to do to fix this travis failure?

Someone just needs to fix that vagrant thing link. Not related to your changes :)

As a side note:
Those middleware might be better suited inside specific plugins for each "topic".
E.g. the geo one would better be found and expected inside my Geo plugin.
For security related things, a "cakephp-security" plugin could make sense.
Having a generic catch-all one means it basically hides all the features under a too generic name.
It also violates the package principle, where things belonging to each other are best put together - as otherwise the reason to change for one trickles down on the others.


add support to connect via system managed identity

unable to find any switch or guidance how to connect to sql utilising a system manged identity.
eg a VM with a system managed identity that has been provide access to the the sql server should be able to connect without need to supply credentials

@yualan Any thoughts on this one? I've got this exact situation with a customer where we have to use username/password authentication from mssql-cli on an Azure VM with an assigned MSI. It would be great (not to mention more secure) to use the MSI.

using sqlcmd instead


TIMO-ifies heuristic DWP predictor

Same behavior as implementation in SPP, but
can be stood up as a TIMO service.

fyi @kyleclo @regan-huff


Investigate eslint-parallel to speed up lint

https://github.com/alansouzati/eslint-parallel

I investigated this and it didn't actually speed up our use case.


Update use-your-data.md

Removed the (0314) variants. added gpt-4o

@aahill
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@aahill
Can you resolve the merge conflicts or confirm whether this PR needs to be closed?

The article has been substantially updated, and this change no longer applies. If you'd still like to update the article, please open a new PR. Or if you believe this PR was closed by mistake, email the PublicPRs alias.
#please-close
@MicrosoftDocs/public-repo-pr-review-team


python311Packages.mypy-boto3-builder: 7.17.1 -> 7.17.2

Diff: https://github.com/youtype/mypy_boto3_builder/compare/refs/tags/7.17.1...7.17.2
Changelog: https://github.com/youtype/mypy_boto3_builder/releases/tag/7.17.2
Description of changes

Things done

Built on platform(s)

[ ] 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/)
23.11 Release Notes (or backporting 23.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

[ ] Fits CONTRIBUTING.md.

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

4 packages built:

python310Packages.mypy-boto3-builder
python310Packages.mypy-boto3-builder.dist
python311Packages.mypy-boto3-builder
python311Packages.mypy-boto3-builder.dist


[Documentation] Add topics to this repo

I think at the moment is hacktoberfest so if it will be added, It's likely that others will send contributions ...
beside that some kewords like OTP 2Auth and so on are nice to have ....

Sounds good. Added topic keywords.


network-grpc: Implement subscribe_to_blocks

Codecov Report

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

@@           Coverage Diff           @@
##           master     #473   +/-   ##
=======================================
  Coverage   45.76%   45.76%
=======================================
  Files         131      131
  Lines       13291    13291
=======================================
  Hits         6083     6083
  Misses       7208     7208

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 d4d0997...411ff1b. Read the comment docs.


[🐞] Serializing dirty watch warning

Which component is affected?
Qwik Runtime
Describe the bug
I am getting this error:
QWIK WARN Serializing dirty watch. Looks like an internal error
It sounds like an error that outside users aren't expected to run into, yet I am.
Reproduction
https://stackblitz.com/edit/simple-qwik-starter-36wo3r?file=src%2Froutes%2Findex.tsx,package.json
Steps to reproduce
See the log in the stackblitz. Also, I would expect "Has Children" to be true.
System Info
System:
    OS: macOS 13.1
    CPU: (12) x64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz
    Memory: 50.63 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    Yarn: 1.22.18 - /usr/local/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 109.0.5414.87
    Chrome Canary: 111.0.5558.0
    Safari: 16.2
    Safari Technology Preview: 16.4
  npmPackages:
    @builder.io/qwik: ~0.16.2 => 0.16.2
    @builder.io/qwik-city: ~0.1.0-beta9 => 0.1.0-beta9
    vite: 3.1.1 => 3.1.1

Additional Information
I can also cause the warning with this code that updates state in a useTask that is tracking the same state:
export default component$(() => {
  const state = useStore({ test: true });
  useTask$(({ track }) => {
    track(state);
    state.test = !state.test;
  });
  return
test
;
});

It's not too surprising that this causes problems, but the error could still be better.
I think the Stackblitz is a valid case that should be supported though.

This seems like a user error:
useTask$(({track}) => {
    track(() => state.value);
    state.value = true;
  });

why would you want to track and change the same property? It could easily end up in a infinite loop

You're right, it's probably not valid code. I think the main issue is that the error is confusing.

I recently cope with it too. I ended with having a signal receiving changes (output), and several tracked signals pushing changes to the output.
If possibly not the most ergonomic way, it was quiet straight forward.
const output = useSignal();
const state = useSignal();

useTask(({trak}) = {
  track(() => state.value);
  output.value = state.value
});

The error didn't help me much since I knew I was going to the wrong direction.
Any suggestion for improving the error @literalpie ?

Maybe something like "you cannot change a value in a useTask function that is also tracking that value."

yeah! makes sense! the Serializing dirty watch is more like a end result, good to have this issue because it likely reveals a bigger issue. Question:
useTask$(({track}) => {
    track(() => state.value);
    state.value = true; // < exception? or warning>?
  });

eslint could definitively triggers an error.
In the event devs use that way on purpose, they can easily deactivate it.
🤔

With the minimal example I gave, I don't know if there's any valid way for this code to work (that wouldn't result in an infinite loop) so I think an exception makes sense to me.
But looking again at the more complicated example in the StackBlitz, I think that case might be valid? At least, it's not as clear to me how the code would result in an infinite loop or other issues.

I just stumbled upon this console warning too.
The and the WARN was not helpful enough on it's own to understand the issue or how to resolve it.

I found this error also when updating a context. For example :
layout.tsx
const CounterContext = createContextId('COUNTER');
const useCounterProvider = () => {
  const state = useStore({ count: 0, lastCount: 0 });
  useTask$(({ track }) => {
    track(() => state.count);
    if (state.count > state.lastCount) console.log('New observer');
  })
}

child.tsx
const state = useContext(CounterContext);
useTask$(() => {
  state.lastCount = state.count;
  state.count++;
  return () => {
      state.lastCount = state.count;
      state.count--;
  }
})

I think this happen because the HTML is streamed so we cannot update the code after it has been send. But maybe it's something else.

@GrandSchtroumpf yes that's correct. If you change the app so that the task is used in a component that renders later it should not show the warning.

@wmertens thanks, but I want to query something only if there is at least one observer and multicast the result if there are multiple (much like a shareReplay in rxjs), so I need to do it on render.
layout.tsx
const QueryContext = createContextId('QUERY');
const useQueryProvider = () => {
  const state = useStore({
    count: 0,
    lastCount: 0,
    value: null,
  });
  useTask$(async ({ track }) => {
    track(() => state.count);
    if (state.count > state.lastCount && state.lastCount === 0) {
      state.value = await fetchData();
    }
  })
}

child.tsx
const state = useContext(QueryContext);
useTask$(() => {
  state.lastCount = state.count;
  state.count++;
  return () => {
      state.lastCount = state.count;
      state.count--;
  }
});
// use state.value

Let me know if you see a way to achieve it without warning.
Also, and more importantly, I'm using SSG so I don't need streaming in the first place. Isn't it any way to disable it ?

I would create a hook that exposes a method so you can do the call on demand. See #5087.
Your code has an out-of-order race condition BTW, if two components exit the lastCount depends on the order.
Anyway, since you're doing SSG only, it doesn't matter that the build complains, the build is fine. Just put a message in your build script. But know that if you ever switch to SSR, it won't work as expected.

Ah, I meant to link to https://github.com/BuilderIO/qwik/issues/5087#issuecomment-1707185010 to show how to add methods to a store

seems to be as designed


ACC / ACS integration

[x] could be as simple as a copy & paste with a sidekick extension
[x] figure out how to access the html from the page iframe in the sidekick

fixed in d7da8e2c5126649d4c2050fb8071dd1bf2553635


internal error 500 when start play with k8s

The server of Play-with-K8s is not available now?

Is anyone looking into this? Error still occurring...

Error still occurring...

Error still here


Fix serde extract panic

curl -X PUT localhost:8080/api to an endpoint with a body extract was panicking. This was fixed by returning a bad request error.
I would like to add a test for the new behavior; can you please advise?

Maybe add a test here.
Probably send valid JSON but w/o a content-type header and test that a 400 is returned.

Added a test and committed as a fixup. Recommend squashing on merge.


Strict type mode

PuppetJs should be able to keep the type of JSON properties.
For example, in case a number property is bound to a <input type="number"> with Polymer, a change of the value results in change of type to string (because all input values are strings in HTML).
PuppetJs should have a strict type mode in which it performs type casting before creating the outgoing patch.
This is point 7 from https://github.com/Starcounter/Starcounter/issues/2468 and point 2 from https://github.com/Starcounter/Starcounter/issues/2470

@warpech, if this is an important issue, let's discuss how to implement it.

Yes it is still relevant, though not very urgent because the server deals with casting values to the desired type. I will be happy to review your suggestions on implementing it.

I really don't know how that could be achieved without headache.
For example, the mode:
{
    "Int": 0
}

The html:
<input type="text" value="{{Int}}" />
<input type="number" value="{{Int}}" />

To what type the value should be cast?
We could remember first type of each property of the initial model, but how to deal with entire object replacement?
I think, that this problem should be solved on WebComponents level. If there is a component date-picker, which has three drop downs to select year/month/day, and four values: date/year/month/day, then it should transform values to desired type date/int/int/int before passing to the outside world.

Web Components are actually the reason this issue was created. On DOM level, Custom Element attribute values are always strings. Some clever frameworks do the type conversion, but it should be expected that a numeric value will be converted to string by the client side framework.
Could you do some research how client side frameworks that use HTML to define the view (Polymer 1.0, Angular, Knockout) address this issue? Maybe this can be solved on framework side, just as we decided with with onblur

Polymer 1.x
Introduced property types, looks like this:
properties: {
    obj: {
        type: Object,
        value: null
    },
    int: {
        type: Number,
        value: 11
    },
    str: {
        type: String,
        value: ""
    }
}

But the value still became string, if bound like this:
<input type="number" value="{{int}}" />

Angular
I don't have any experience with Angular, can investigate if needed though.
KnockoutJs
All of the values bound  to input/select/textarea are converted to string, and sometimes it is very annoying.

So, in KnockoutJs there is no way to force type conversion? Can you investigate Angular? This confirms that we need to solve this at Puppet level

KnockoutJs has observable.subscribe function, which fires each time new value set. The callback can be used to force strict type, but can't be used together with html binding, because it leads to an infinite loop.
var o = ko.observable(1);

o.subscribe(function (newValue) {
    var int = parseInt(newValue);

    if (int !== newValue) {
        o(int);
    }
});

<input type="checkbox" data-bind="value: o" />

After binding applied to the input, the value will be changed to "1", but then callback fires and changes it back to 1, and the loop starts again.
There is a workaround, something like this:
var o = ko.observable();

o.int = ko.computed(function () {
    return parseInt(o());
});

The o.int will always be of type Number and will be automatically updated after o changes.

AngularJs has some features, but also does not maintain original property type, here is a small playground:
https://jsfiddle.net/79ftv1fy/
The features:

Converts incoming values from <input type="number" /> to Number.
Newer version has a convert-to-number directive. https://docs.angularjs.org/api/ng/directive/select

Ping @warpech.

As it turns out from your investigation (thanks a lot for that!), modern frameworks have a way to keep the type. I think we don't have to work on that then. If someone doesn't agree, please reopen.
For future consideration: Since this issue is related to keeping the intended structure of JSON, I propose that this should be solved using JSON Schema (similarly to https://github.com/PuppetJs/PuppetJs/issues/35).
For example this library has a convert method: https://github.com/litixsoft/lx-valid#convert-option
If we ever do JSON-Schema, it would be cool to do it as a PuppetJs extension, not to clutter the core.


[pytorch] Adds Yolo11 model to model zoo

Description
Brief description of what this PR is about

If this change is a backward incompatible change, why must this change be made?
Interesting edge cases to note here

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 72.37%. Comparing base (b6656ed) to head (e18dd99).
Report is 16 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##             master    #3516      +/-   ##
============================================
- Coverage     72.52%   72.37%   -0.16%
- Complexity     7394     7411      +17
============================================
  Files           672      674       +2
  Lines         32909    33048     +139
  Branches       3501     3523      +22
============================================
+ Hits          23868    23918      +50
- Misses         7400     7497      +97
+ Partials       1641     1633       -8

Flag
Coverage Δ

?

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Can I develop a GUI for this?

Hi, I am the developer of Waifu2x-Extension-GUI
I wonder if I can add Real-Esrgan support to my GUI, since your project does not have a license, I think I should ask for your permission first
Waifu2x-Extension-GUI:
https://github.com/AaronFeng753/Waifu2x-Extension-GUI

抱歉, 我一时眼瞎没看见根目录里的license, 抱歉打扰了

😄


Add status feedback on memo mismatch

Adds feedback to status when there's a lock memo mismatch. For
mismatch with missing packages, it lists the packages and provides
instructions to fix the issue. For memo mismatch with no missing
packages, it instructs the user about how to generate a new lock.

Fixes #161

status feedback on memo mismatch with missing packages:
$ dep status
Lock memo mismatch due to the following missing packages:

PROJECT                       MISSING PACKAGES
github.com/darkowlzz/openurl  [github.com/darkowlzz/openurl]

Run `dep ensure` to install the missing packages.

status feedback on memo mismatch without any missing packages:
$ dep status
Lock memo mismatch but there are no missing packages.
Run `dep ensure` to regenerate the lock memo.

It's not clear to me what is meant by "missing packages". I'm guessing you mean missing from vendor? It would help to put that in the message.
For the second case, when there's a mismatch but no "missing packages", unless missing packages is the only way to cause a mismatch it seems odd to mention that at all. I'd lean towards saying "Lock memo mismatch. Run dep ensure to regenerate the memo.".

It's not clear to me what is meant by "missing packages". I'm guessing you mean missing from vendor? It would help to put that in the message.

Yeah, being more specific in the message would be better. Right now, status doesn't checks what's in vendor/. Should it? It parses the project root, takes the manifest from file, computes a memo hash and compares it to the one found in lock file.
So the mismatch due to packages is when lock file has something missing from what's found in the package tree (addition of a new import) or package tree has something missing from what's in lock file (removal of an existing import).
And mismatch with no missing package is when the manifest constraints are modified.
But removal of existing import also falls under no missing package category, because the packages exist, just extra packages.
So, I think adding an extra line about the addition of new import would be better.
Lock memo mismatch due to the following missing packages:

PROJECT                       MISSING PACKAGES
github.com/darkowlzz/openurl  [github.com/darkowlzz/openurl]

This happens when a new import is added. Run `dep ensure` to install the missing packages.

when there's a mismatch but no "missing packages", unless missing packages is the only way to cause a mismatch it seems odd to mention that at all. I'd lean towards saying "Lock memo mismatch. Run dep ensure to regenerate the memo.".

Yeah, I think it's not required to mention "missing packages" here. But this can be made more informative like
Lock memo mismatch. This happens when the Gopkg.toml is modified.
Run `dep ensure` to regenerate the memo.

Looks good?

Right now, status doesn't checks what's in vendor/. Should it?

Nope! 😄 We have another story for vendor validation.

So the mismatch due to packages is when lock file has something missing from what's found in the package tree (addition of a new import) or package tree has something missing from what's in lock file (removal of an existing import).

I pulled down your PR, correct me if I'm wrong, but your error messages don't cover the bolded case, right? So it's just the first scenario that this PR addresses? Just making sure I tested the right stuff.

So it's just the first scenario that this PR addresses?

@carolynvs yes, just the first scenario, no missing packages, just extra packages.

@sdboyer I was going to click the merge button for great glory but thought you'd like to weigh in since this PR was based on your feedback.

Fixed the typo and squashed the commits.

thanks! 🎉


A few random, mostly doc issues

In a really simple app, something like the executor is not being shut down, so at the end it hangs forever.
It would be great to have an example of inserting.  I found it by browsing to the Recipe example, but it'd be great to have it since the rest of the documentation is so good.
I can see simply mixing in SimpleCassandraConnector, but what if I want to use it in a deployed environment, and want to configure the Cassandra host and port to talk to?  I can't just override a val, I would probably be pulling it from config.  Any examples?
It seems there is a lot of boilerplate, when one mixes in a case class (for ex., ExampleModel) as the second type to the class that extends CassandraTable  (eg. class ExampleRecord extends CassandraTable[ExampleRecord, ExampleModel]).  Namely, still have to define an inner object for each field, plus the fromRow method where again every field is redefined.  Plus if I add some kind of insert method, then again all the fields are redefined.  Any way to avoid the boilerplate?

Many thanks.  Phantom seems like a great project so far.

@GoldenZero In the next milestone release, a shutdown method will be found for the executor and the docs now have examples on inserts. Many thanks for reporting this once again. We've also added examples to clarify point 3 and 4 you made.

@alexflav23 Can you point out where you in the documentation you are addressing the 4. point of @velvia ? All I see is this:
https://github.com/websudos/phantom#data-modeling-with-phantom
And that section doesn't even have any text. I'm just looking at the library, and I'm not sure I understand the reasoning behind the  fromRow method.
My basic question is, would it not be possible to just give the case class of the object, and provide some additional data (like PartitionKey and ClusteringOrder) to the table? It just seems that the compiler can figure out that this line in the case class:
name: String

has to turn into this in the CassandraTable:
object name extends StringColumn(this)

As @velvia pointed out, there is also redundancy with the fromRow.
I feel like these points must be addressed somewhere, but I can't find where..
Thanks for this library!


Move non-network.* attributes out of network.yaml

I missed this in #256

@open-telemetry/specs-semconv-maintainers I think this is good to merge


include support for building a windows binary

Codecov Report

Merging #12 (a59a454) into main (c2f250c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #12   +/-   ##
=======================================
  Coverage   81.90%   81.90%
=======================================
  Files           4        4
  Lines         210      210
=======================================
  Hits          172      172
  Misses         27       27
  Partials       11       11

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 c2f250c...a59a454. Read the comment docs.


Support processing v2

Relates to https://github.com/api3dao/commons/issues/27
Rationale
Read https://github.com/api3dao/commons/pull/32
How to test
I used the development only invoke instructions to invoke signed API with pre/post processing configurations. Specifically:
Copy the pre-processing packages/airnode-examples/integrations/coingecko-pre-processing/config.example.json to packages/airnode-node/config/config.json and run the following:
AIRNODE_WALLET_PRIVATE_KEY=0x8127fa78936ebbd63b3f3e30272631d49abd6714c9349f430c383e52ac773cb9 yarn dev:http-signed-data-invoke -e 0x642598611f0dcbe389079bf555108513e3e8a15991887bb61126b7200f13c666 -p 0x3173690000000000000000000000000000000000000000000000000000000000636f696e49640000000000000000000000000000000000000000000000000000657468657265756d000000000000000000000000000000000000000000000000756e697854696d657374616d70000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000061a56980

Copy the post-processing packages/airnode-examples/integrations/coingecko-post-processing/config.example.json to packages/airnode-node/config/config.json and run the following:
AIRNODE_WALLET_PRIVATE_KEY=0x8127fa78936ebbd63b3f3e30272631d49abd6714c9349f430c383e52ac773cb9 yarn dev:http-signed-data-invoke -e 0x7ad7519b2b0ebd54c68356a314ffcacd7f897a08523e2ec9e0edd837fe995422 -p 0x3173730000000000000000000000000000000000000000000000000000000000636f696e49647300000000000000000000000000000000000000000000000000626974636f696e2c657468657265756d00000000000000000000000000000000767343757272656e6379000000000000000000000000000000000000000000007573640000000000000000000000000000000000000000000000000000000000

Are you sure your changes to the processing integrations work?

You're right - sorry. I forgot to update the processing snippets after the renaming discussion we had at the docs PR. I also forgot to mention to copy the trigger in the config to the signed data gateway.
Please try again now.


Fix gitignore's xcuserdata folder

Removed asterisk from `*/xcuserdata/, removed cached files under git

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@373f574). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #28   +/-   ##
=========================================
  Coverage          ?   58.53%
=========================================
  Files             ?       46
  Lines             ?      820
  Branches          ?        0
=========================================
  Hits              ?      480
  Misses            ?      340
  Partials          ?        0

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 373f574...e2735d8. Read the comment docs.


Add validation when importing custom commands.

This PR adds a validation step to the CommandImporter class. This step
ensures that what is require'd adheres to the Command interface. If the
imported object is invalid, a warning is printed to the console. The invalid
command is not added to the CommandRegistry.
J=SLAP-888
TEST=manual
Tested the following scenarios:

Created a test repo with Theme 1.16 and the latest Jambo. Ran various
Jambo commands in the repo and they worked as expected. Each time a command
(or --help or version) was run warnings were printed to the console. These
indicated the Theme's custom commands could not be parsed by Jambo.
Created a test repo with Theme 1.17 (beta) and the latest Jambo. Ran various
commands and all passed. No warnings about invalid custom commands were
in the console. The expected custom commands were available.
Created a test repo with some valid custom commands and some invalid ones.
Verified that Jambo could parse the valid ones and warnings were printed about
the invalid ones.

LGTM! Just double checking, are we still planning to make the change where unless --help, describe, or a custom command is run, we won't try to import custom commands?

Yep! That's coming next.


Smooth tab drag-and-drop

For years VS Code had smooth drag-and-drop behavior of tabs, where the existing tabs would slide away from the dragged tab. For example, this is how Xcode does it and how I remember VS Code did it.
https://github.com/microsoft/vscode/assets/43852515/80cb823e-3884-4431-b635-178038b719ef
Now, VS Code has a snappy tab-drag behavior with a white vertical line to show where the dragged tab will end up. Why?
This change seems like a step back in time and is less intuitive and harder to use.
https://github.com/microsoft/vscode/assets/43852515/adeaa52c-7b13-4d91-92f9-fcb2f3f8f7c4
Is it possible go back to the smooth behavior?

The behaviour was not as smooth as indicated in the first video clip. We only used to change the background color of the tab you are hovering over when drag and dropping, so nothing fancy. The old behaviour had a couple of problems. For example in some cases it was unclear at which position the tab would be dropped. We made the change as we felt it was more intuitive to use and aligns with how reordering list items behaves (for example in the open editors view).

I see. Could you implement a smooth drag-and-drop behavior? In my opinion the current behavior doesn't feel right

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

Hi! on a related note when dragging tabs, is there a way to not set that tab to active until the 'click up' instead of on the 'click down'? The reasoning is, if I have a tab open and I want to view a different tab side by side next to it, I currently cannot drag that inactive tab to the side editor position. Instead it steals the active window and then I cannot place it next to the original.

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


pymc-marketing: Add pymc marketing python package

Description of changes
Working on https://github.com/NixOS/nixpkgs/issues/286040

Things done

Added pymc-marketing package to python-modules
Made it visible in python3Packages
Added myself to maintainers for this package

Built on platform(s)

[ ] 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

[x] 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

[ ] Fits CONTRIBUTING.md.

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

@hugolgst done, does it look good now?

got it

anything else to look into?

Hi, there is a new release after a while


Tooltips for report tags

Tags have a description that should be used as a tooltip in any location where a tag is displayed.
In https://github.com/NCI-Agency/anet/issues/17 this is suggested:

Tooltips should be displayed when clicked or (to support phone usage) or possibly also mouse-over events

@dspCarlson Since tooltips for tags will show what's in the description field (currently empty), could you provide descriptions for the 12 default tags that you have now (in staging) so we can add them?

@gjvoosten No problem.  I will do it tomorrow.

Key Words with Descriptions.txt
@gjvoosten Per your request

@dspCalrson Thanks, I've added the descriptions. Should you wish to update your local database with descriptions for the tags, you can use this SQL script.
updateTags.txt

@gjvoosten Was the tool tip ever implemented?  Once a tag is selected for a report, the description is not displayed as a tool tip anywhere the tag is displayed.

@dspCarlson The tooltip is displayed only when you click on a tag.


Question: Use ViewAnimator for animations between two VCs

Hi Marcos,  I love these transitions and would like to incorporate them on my new project. I'm having trouble using it to transition between two view controllers. Is it possible to do that with ViewAnimator or is it only for loading a view within a view controller?
Here is the way I'm doing my transition between the two view controllers right now:
// In VC1 call this func to transition to VC2
func goToVC2() {
    let storyBoard: UIStoryboard = UIStoryboard(name: "Main", bundle:nil)
    let VC2 = storyBoard.instantiateViewController(withIdentifier: "VC2") as! VC2
    self.present(VC2, animated: true, completion: nil)
}

Hey Tyler, what kind of transition do you have in mind?
I'm planning on creating a library to use ViewAnimator for transitions in the near future.

I was hoping to use the animation that is in the entire view gif in the readme. When I transition between to views, I want to remove all of the elements and then have the new elements animate in so that it appears to the user to be a single view.
I suppose I could use this library still and just have everything on a single view controller. I only have pages on the app so it wouldn't be too much code to manage in a single vc.

@tylerswartz That could be one solution. Also, take a look at custom viewcontroller transitions. You could create a transition where the first controller animates its cells then fades into the next one and that last one animates its cells in.


1061 filesystem UI component

To test:
Run an extractor, I used wordcount , locally as in to do the necessary modifications:

Add another parameter in extractor-info.json file,  in the schema field of  parameters, if using wordcount, you will have to add it here

    "DATASET_FILE_ID":{
            "type":"string",
            "title":"Dataset file ID",
            "description":"The Clowder file id of the dataset file to be used for inference",
            "format": "clowderFile"
       },

When you open the ford for the wordcount extractor after running it locally, you will see the widget

After you choose a file and click submit, use the network tab from inspect tools, you will see that the corresponding DATASET_FILE_ID has been passsed in the requests

@longshuicy sorry for the confusion, I have updated the testing instructions, let me know if the updated instructions are better!


gen new:app wont work

$ gen new:app wat

Generating folder structure for [wat]...
[=====================================================================================================] 100.00%
Verifying dependencies for<EMAIL_ADDRESS>Info: Dependency on jester@any version already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Info: Dependency on httpbeast@>= 0.2.0 already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Info: Dependency on https://github.com/timotheecour/asynctools@#pr_fix_compilation already satisfied
Verifying dependencies for asynctools@#pr_fix_compilation
Info: Dependency on asynctools@any version already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Tip: 9 messages have been suppressed, use --verbose to show them.

Error: Cannot satisfy the dependency on asynctools 0.1.0 and asynctools 0.1.1

$

But I have Jester installed, thats strange.
Maybe would be better if it asked me if I want to install Jester? (Y/N) .
🤔

addressed!


feat(auth): introduce WithinBody option for AuthMode

fixes #1035
Implementation is done by:

adding a new auth mode
adding data as the return type for createAuth
expose data from transporter
serialize transporter data
map api key back to query parameter if GET

This doesn't automatically switch to body if the key is too long, the option authMode needs to be set
algoliasearch('', '', { authMode: AuthMode.WithinBody })

TODO

[ ] tests
[ ] validate this works

it's in the todo @tkrugg

@Haroenv Any news on this PR?
It'd be great to have this released to fix #1035

Sorry, there was too many places to change in this unplanned PR, but withinHeaders should be an in-between solution, as it has a higher limit (but doesn't avoid a cors preflight request) @jpreynat

Thanks for the suggestion @Haroenv. But sadly we already tried using withinHeaders and we have some cases where the limit is too small for us, preventing us from switching from version 3 to version 4.
Are there any plans on your side to have the withinBody option released at some point?

At the moment it's not yet on the roadmap, as I made this pull request a while ago in an experiment. I will however ask the current owners of this repo whether they can take a look (@shortcuts, @millotp)

@Haroenv @shortcuts @millotp @tkrugg can this prioritized now? it's really preventing enterprise users from the full performance benefits of algolia if we can't use long secured api keys from the browser

Sorry, I'm not on this team anymore @humanbagel, but I do know that algoliasearch v3 had this feature, so you can use that before it's prioritised to be fixed. Someone who's actually on the api clients team can give more information on prioritisation

@nunomaduro what's the issue that this PR not merged? Enterprise-level apps need that a lot :(


theme: hermes (updates)

Sorry for the multiple pulls so close together — I saw mine on the live site and decided it was too close to the original Apollo theme. Also, I updated the description to reflect that this theme has been updated to work out of the box (Apollo is essentially deprecated).
Check List
Please read and check followings before submitting a PR.

[x] I want to publish my theme on Hexo official website.

[x] I have read the theme publishing doc.
[x] name is unique.
[x] link URL is correct.
[x] preview URL is correct.
[x] preview URL web site is rendered correctly.
[x] Add a screenshot to source/themes/screenshots.
[x] Screenshot filename is same as value of name.
[x] Screenshot size is 800 * 500.
[x] Screenshot file format is png.

[ ] I want to publish my plugin on Hexo official website.

[ ] I have read the plugin publishing doc.
[ ] name is unique.
[ ] link URL is correct.

[ ] Others (Update, fix, translation, etc...)

Force push because I accidentally included a package bump. Not sure when now this says there are conflicts to resolve, there shouldn't be 🤷♂

@SukkaW does this look okay?

This PR is still has conflicts that need to be resolved...

Fixed!

Thanks for your contribution. However, this commit is not clean. I have created a new PR #1222 please have a look.


error TS2688: Cannot find type definition file for 'testing-library__jest-dom'.

Describe the bug
I created a new vite project using the react-ts template,
and without modifying any files,
if I tried to build it, it would fail with errors:
error TS2688: Cannot find type definition file for 'testing-library__jest-dom'.
  The file is in the program because:
    Entry point for implicit type library 'testing-library__jest-dom'

Reproduction
https://github.com/rodrigc/vite-js-dom-issue
Steps to reproduce
pnpm create vite@latest example1  --template react-ts
cd example1
pnpm install
pnpm build
System Info
System:
    OS: macOS 14.5
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 11.29 GB / 32.00 GB
    Shell: 5.9 - /usr/local/bin/zsh
  Binaries:
    Node: 22.1.0 - /usr/local/bin/node
    npm: 10.7.0 - /usr/local/bin/npm
    pnpm: 9.6.0 - /usr/local/bin/pnpm
  Browsers:
    Chrome: 127.0.6533.89
    Edge: 127.0.2651.86
    Safari: 17.5
  npmPackages:
    @vitejs/plugin-react: ^4.3.1 => 4.3.1
    vite: ^5.3.4 => 5.3.5

Used Package Manager
pnpm
Logs

Click to expand!
pnpm build

><EMAIL_ADDRESS>build /Users/crodrigues/vite-js-dom-issue/example1
> tsc -b && vite build

error TS2688: Cannot find type definition file for 'testing-library__jest-dom'.
  The file is in the program because:
    Entry point for implicit type library 'testing-library__jest-dom'

error TS2688: Cannot find type definition file for 'testing-library__jest-dom'.
  The file is in the program because:
    Entry point for implicit type library 'testing-library__jest-dom'

Found 2 errors.

 ELIFECYCLE  Command failed with exit code 1.

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I was able to eliminate this error by doing the following:

pnpm add "@testing-library/jest-dom"

Explicitly add to "types" in tsconfig.app.json and tsconfig.node.json

diff --git a/example1/tsconfig.app.json b/example1/tsconfig.app.json
index d739292..d158e31 100644
--- a/example1/tsconfig.app.json
+++ b/example1/tsconfig.app.json
@@ -21,7 +21,9 @@
     "strict": true,
     "noUnusedLocals": true,
     "noUnusedParameters": true,
-    "noFallthroughCasesInSwitch": true
+    "noFallthroughCasesInSwitch": true,
+
+     "types": ["@testing-library/jest-dom"]
   },
   "include": ["src"]
 }
(venv) vite-js-dom-issue/example1 - [main●] » git diff tsconfig.node.json
diff --git a/example1/tsconfig.node.json b/example1/tsconfig.node.json
index 3afdd6e..3e1280e 100644
--- a/example1/tsconfig.node.json
+++ b/example1/tsconfig.node.json
@@ -7,7 +7,9 @@
     "moduleResolution": "bundler",
     "allowSyntheticDefaultImports": true,
     "strict": true,
-    "noEmit": true
+    "noEmit": true,
+
+    "types": ["@testing-library/jest-dom"]
   },
   "include": ["vite.config.ts"]
 }

Is there a problem with the vite react-ts template, or
the way that @testing-library/jest-dom exports types?


Ability to repackage for production

Hello, forgive me for taking some liberties with your publishing structure.  This change enables a second npm package that includes only the resources and dependencies needed for a production deployment to be published from this repository.
In this implementation, the original npm build and publish process is the same; however, after publishing mady, we can publish mady-production with the following
$ npm run build:production
$ cd production
$ npm version minor # or some other method to sync the package.json version number
$ npm publish

I've gone ahead and published the 2.11.1 release so I can consume it in my build pipeline. And I think I've given you publish access to npm as well.
I'll caveat this particular implementation is only one of many possible mechanisms we could use to publish a production mode dependency.  The most straight-forward but intrusive of which would be to split the repo into several.  I'm happy to rework this based on your feedback.

Thanks for the proposal!
In fact, my mid-term plan is to reorganise mady into a monorepo using oao, with probably three parts:

mady: a wrapper, for backwards-compatibility (current applications depending just on mady would continue working)
mady-translator-tools: the translation application
mady-translate: the translate function (what you call mady-production)

I hope it won't take much time, but feel free to use mady-production for the time being!

I was so going to use mady-translate, but I changed my mind at the last minute; last minute decisions are always a bad idea, LOL.  My own bias is against yarn, but you oao mono repo tool is really cool. (aside: I feel yarn served its purpose in forcing npm to improve and now it's just unnecessarily fragmenting the community, like node.io).
Adding 'translate' in the name should help with discoverability too. If I can make another suggestion, when you republish to npm can you add 'i18n' somewhere in the name?  It was several weeks of convoluted searching before I stumbled unto this project.  Started with 'i18n' named projects, then when those didn't wow me I searched for 'local', 'global', then stumbled on 'messageformat' (only because I was reading angular2 code), and then finally landed here..
As long as I'm throwing advice your way, it'd be great if you could split the translator-tools into two packages: a stand-alone set of file parsers and writers, and then the web app itself.  I can envision a need to have a set of CLI based tools for extraction and modifying the translation DB that is independent of the file watching web app.
Looking forward to the repackaging and the increased flexibility.  I've got a lot plans for your library . Seriously, thanks for your hard work here!


Bugfix/parse mapped abbrev

So the direction I went was to change the regex to in the UnitParser.ParseUnit to match one of any of the abbreviations for the unit type. This seems more robust as it uses UnitSystem abbreviations and allows for more flexible abbreviations (either mapped at run time or generated).
Related issue: #264

I want to add a few more tests, so this should not be merged quite yet.
I did not realize that the solution to this was basically the same as the solution to #254 and #253 -- I am going to add tests to verify those issues are resolved as well.

Been a bit busy, will get to this soon.

Let me know when it's ready for another review

It should be ready to review again.

@anjdreas This is ready for review.

Hi, I'm on vacation trip until July 30. Will review when I get back.

I meant July 25

No worries; thanks for the update. Have a great trip!


[WIPish] MSC1776: Implementing peeking via /sync

Rendered

This MSC is tagged as obsolete, so closing.


vcpkg install uwebsockets failed

.\vcpkg install uwebsockets
The following packages will be built and installed:
uwebsockets[core]:x86-windows
Starting package 1/1: uwebsockets:x86-windows
Building package uwebsockets[core]:x86-windows...
Warning: The following VS instances are excluded because the English language pack is unavailable.
C:\Program Files (x86)\Microsoft Visual Studio 12.0
Please install the English language pack.
-- Using cached C:/vcpkg/downloads/uWebSockets-uWebSockets-v0.14.8.tar.gz
-- Using source at C:/vcpkg/buildtrees/uwebsockets/src/v0.14.8-b18b022999
-- Configuring x86-windows
-- Building x86-windows-dbg
CMake Error at scripts/cmake/vcpkg_build_cmake.cmake:175 (message):
Command failed: C:/Program Files/CMake/bin/cmake.exe;--build;.;--config;Debug;--target;install;--;-v;-j1
Working Directory: C:/vcpkg/buildtrees/uwebsockets/x86-windows-dbg
See logs for more information:
C:\vcpkg\buildtrees\uwebsockets\install-x86-windows-dbg-out.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_install_cmake.cmake:24 (vcpkg_build_cmake)
ports/uwebsockets/portfile.cmake:20 (vcpkg_install_cmake)
scripts/ports.cmake:71 (include)
Error: Building package uwebsockets:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: uwebsockets:x86-windows
Vcpkg version: 2018.11.23-nohash

See logs for more information:
C:\vcpkg\buildtrees\uwebsockets\install-x86-windows-dbg-out.log

@MinaRoss, thanks for posting this issue. we cannot reproduce it now. Please open a new issue if this is still a problem for you.


Start migrating from Travis to GHA

It's been a while since I've done any work on this project, so let's kind of get everything back up and working.

[x] Continuous integration, build in GHA
[x] Continuous integration, remove Travis
[ ] Continuous integration, deploy to Maven Central from releases
[x] Test coverage, run
[x] SpotBugs, run (new name for FindBugs)
[ ] Test coverage, publish
[ ] Project site, build and publish

Since my summer vacation is over, I'll half ass this, and just merge it. I'll continue on missing parts..... LATER!


adding message to user that dataset creation takes time!

This is another quick PR that will alert the user that the dataset creation takes time. We only print the message given that quiet is False.
Please feel free to critique the message itself, and if there are other spots in the API that need messages like this (I'd be happy to add, I haven't used the other endpoints so I don't know yet!)

yep! Is there any indication that the operation was/was not successful? (so we don't show this given that the dataset isn't being created)

Not that you'll be able to catch before we want to print this.  Thanks!


Indicate if this user can edit this event

@lornajane That's looking great! Makes it much easier to determine whether one can edit the event.


Support a Copy button for code cells

Is your feature request related to a problem? Please describe.
I want to show a Copy button next (or on top of) code cells so that my blog readers can easily copy code from my blog posts.
Describe the solution you'd like
Add a Copy button to all code cells. When users click on it, the content of the code cell should be copied. jupyter-book has implemented this feature.
Describe alternatives you've considered
Additional context

Happy to take a PR if you would like to add it!

Why is this feature request closed?

@dclong you have done nothing wrong!  I only keep issues open if they are bugs or if I plan on working on it.  Since I do not plan on working on this copy feature I closed it.... this doesn't mean that a contribution from someone is not welcome
This is the only way I can manage a project is to make sure open issues are things that need my attention.  Thanks for understanding


BoxWhisker and Dataset

given an hv.Dataset
h=rx_ds.to(hv.BoxWhisker, 'Experiment', 'Error', label='Error')
is there a way to get a legend attached to each of the BoxWhisker elements?

if I want to display two copies in a Layout, the original BoxWhisker Plot and a zoomed in version of the plot,
how do I have to specify h.redim.range(???) and what shared_axes, axis_wise options do I have to set to make it work?

I have had no success with either.

I would welcome additional documentation for hv.Dataset
The .to() method seems quite inflexible, with the result that the usefulness of
the hv.Dataset container is not apparent

is there a way to get a legend attached to each of the BoxWhisker elements?

You can enable the legend and tie a particular particular dimension to a color using:
%%opts BoxWhisker [color_index='Experiment' show_legend=True]

if I want to display two copies in a Layout, the original BoxWhisker Plot and a zoomed in version of the plot,
how do I have to specify h.redim.range(???) and what shared_axes, axis_wise options do I have to set to make it work?

Since merging #2031 redim.range on BoxWhisker should work correctly, you will also have to set +axiswise.
Please reopen if you encounter any other issues.


Inactive syntax highlighting

Source: https://github.com/Pybonacci/notebooks/blob/master/Cómo acelerar tu código Python con numba.ipynb
Result: http://pybonacci.org/2015/03/13/como-acelerar-tu-codigo-python-con-numba/
The code fragments appear without syntax highlight.

I think you have used the basic template instead the basicx template. The basicx template provides the nb syntax highlight and removes the prompt numbers.
You can create your own template if you want a specific behavior.
It is not possible to know if someone is using a js syntax highlight lib in their wp box so you should create the template for your use case or choose no highlight (basic) or nb highlight (basicx).
Could the issue be closed?

Thanks for the pointer, didn't know basicx was available!
I just used it and properly generated the styles, but it was prepended at the beginning of the article in plaintext... apparently there is no way to enclose that between <style></style> tags.

May I point out, the WP editor strips out the <style></style> tags when you are not the admin. I see what you did here...

WP rules... :-(
Yes, if you want to use something out of the box you should use WP admin. As a user (not admin) you can't do several stuff in WP.
I will update the docs to highlight this.
And I close the issue. If you think this can be improved, pplease, reopen the issue.


[🐞] Loader state lost when setting local state

Which component is affected?
Qwik City (routing)
Describe the bug
Issue:
Loader state lost or cleared from view when setting local signal or store value.
Qwik version info:
<EMAIL_ADDRESS>"0.21.0",
<EMAIL_ADDRESS>"0.5.3",
Reproduction
https://github.com/rolanday/qwik-loader
Steps to reproduce

Create a new project using npm create qwik@latest
Edit src/routes/index.tsx as shown below.
npm run dev
Click the button and observe rendered view

// src/routes/index.tsx
import { component$, useStore } from<EMAIL_ADDRESS>import type { DocumentHead } from<EMAIL_ADDRESS>import { routeLoader$ } from<EMAIL_ADDRESS>
export const useLoaderData = routeLoader$(() => {
  return { name: "malmsteen" };
});

export default component$(() => {
  const loaderData = useLoaderData();
  const localStore = useStore({ x: 1 }); // problem also occurs if this is a signal instead of store
  return (

localStore: {JSON.stringify(localStore, null, 2)}

loaderData: {JSON.stringify(loaderData.value, null, 2)}

      <button
        onClick$={() => {
          // console.log(JSON.stringify(loaderData.value)); <== Uncommenting this line solve the problem, but why?
          localStore.x = 2;
        }}
      >
        {localStore.x}
      </button>

  );
});

export const head: DocumentHead = {
  title: "Welcome to Qwik",
  meta: [
    {
      name: "description",
      content: "Qwik site description",
    },
  ],
};

System Info
System:
    OS: macOS 12.6
    CPU: (48) x64 Intel(R) Xeon(R) W-3265M CPU @ 2.70GHz
    Memory: 82.30 GB / 192.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 16.16.0 - /usr/local/bin/node
    Yarn: 1.22.15 - /usr/local/bin/yarn
    npm: 8.11.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 110.0.5481.177
    Firefox Developer Edition: 111.0
    Safari: 16.0
  npmPackages:
    @builder.io/qwik: 0.21.0 => 0.21.0
    @builder.io/qwik-city: 0.5.3 => 0.5.3
    undici: 5.20.0 => 5.20.0
    vite: 4.1.4 => 4.1.4

Additional Information
Issue also reproduced by other Discord member: https://discord.com/channels/842438759945601056/1082965605054955561/1083096120722464778
Video link showing the problem in action:
https://user-images.githubusercontent.com/3402123/223807825-fd4dd82a-cff6-4155-ac52-fb4c330812ca.mov

Not sure if it is caused by the same problem, but I also had problems with loader data being absent. (I'm quite new to Qwik so there's also a possibility I might be using it wrong, please correct me if I am wrong)
I started a new project, and in the src/routes/todolist/index.tsx file, I just added a {${action.isRunning}} and an error like below popped up below.

To reproduce, first add some items by submitting the form, then reload the page and try adding a item by submitting the form.
https://user-images.githubusercontent.com/63445490/224070773-dffcf0ea-5473-4eed-af8d-e5195ac35245.mp4
import { component$ } from<EMAIL_ADDRESS>import { type DocumentHead, Form, globalAction$, routeLoader$, z, zod$ } from<EMAIL_ADDRESS>
interface ListItem {
  text: string;
}

export const list: ListItem[] = [];

export const useListLoader = routeLoader$(() => {
  return list;
});

export const useAddToListAction = globalAction$(
  (item) => {
    list.push(item);
    return {
      success: true
    };
  },
  zod$({
    text: z.string()
  })
);

export default component$(() => {
  const list = useListLoader();
  const action = useAddToListAction();

  return (
    <>

Form Action TODO list

      {`${action.isRunning}`}{/*Here is the only code I added*/}

        {list.value.map((item) => (

{item.text}

        ))}

      <Form action={action} spaReset>
        <input type="text" name="text" required />
        <button type="submit">Add item</button>
      </Form>

This little app works even when JavaScript is disabled.

    </>
  );
});

export const head: DocumentHead = {
  title: "Qwik To-Do"
};

I did notice something interesting, that if the <Form> tag is inside a conditional render (no matter what the condition is) the error goes away.
import { component$ } from<EMAIL_ADDRESS>import { type DocumentHead, Form, globalAction$, routeLoader$, z, zod$ } from<EMAIL_ADDRESS>
interface ListItem {
  text: string;
}

export const list: ListItem[] = [];

export const useListLoader = routeLoader$(() => {
  return list;
});

export const useAddToListAction = globalAction$(
  (item) => {
    list.push(item);
    return {
      success: true
    };
  },
  zod$({
    text: z.string()
  })
);

export default component$(() => {
  const list = useListLoader();
  const action = useAddToListAction();

  return (
    <>

Form Action TODO list

      {`${action.isRunning}`}{/*Here is the original code I added*/}

        {list.value.map((item) => (

{item.text}

        ))}

      {true && // I added a conditional rendering here and the error goes away
        <Form action={action} spaReset>
          <input type="text" name="text" required />
          <button type="submit">Add item</button>
        </Form>
      }

This little app works even when JavaScript is disabled.

    </>
  );
});

export const head: DocumentHead = {
  title: "Qwik To-Do"
};

I can reproduce and working on a fix!

Thank you for the fix! I can confirm my issue has been fixed when using version 0.22.0-dev20230314185952

+1 thank you!


Failed to load model

Hi
I try to run on my 6s plus, and the console message is: "Failed to load model"
here is my debug screenshot, any suggestion?

Hi Jerry,
which model are you trying to load?

this model: "frozen_inference_graph"

I'm not sure.  I haven't made changes to those graphs in several months.  It looks like you might have some source control modifications judging by the '?'.    Did you re-train?

thank you anyway, I will try again.

I am having the same issue. Could you solve it?

I am having the same issue. Could you solve it?

We need to build the tensorflow components with ANDROID_TYPES_FULL. In the terminal type:
export ANDROID_TYPES="-D__ANDROID_TYPES_FULL__"


Code refactoring

Currently, we have one giant scanner loop where we launch crawlers from crawl.py. We need to split each crawler into individual module that will improve code readability and allow to parallelize the scan. Besides that, we can leverage python classes for the state of execution control, config parsing and enabling/disabling certain functions.

I can take this issue and do the initial refactoring of the crawler. I have experience in python best practices and the styling guide of flake8, pep8 etc. Besides I have been writing python in production for about 2 years now.
Nevertheless, I can always do the necessary research if required and take suggestions from other community members.

Hi @sudiptob2 , @mshudrak , I have basic python knowledge; could I join in this work ? I need guidance though.

Feel free to join :)

@mshudrak @ZetaTwo @sudiptob2 Hi, I'll help in creating class designs for code refactoring as well as object pickability for parallelization. Will create an initial PR for review and considerations. Thanks!!!

Hi, Is this work still going on ?

Hi. I am writing to inquire about the status of this issue that I am interested in contributing to as a part of the Google Summer of Code program 2023. Specifically, I am wondering if the issue is still active and if any proposals for it will be considered as I can already see some progress.

Yes, we will consider applications for this issue. It is one of projects listed for GSoC 2023. There is some progress but it requires much more refactoring.

Hi @mshudrak , could you guide about the files where the codes needs to be refactored ; and is there any special suggestions ?

I have suggested a refactoring strategy in my proposal. If I get selected for GSOC I guess I will be able improve the project's scalability 🙂

Basically, we want to refactor most of the code in the project. I don't have any special suggestions. You may choose your own refactor strategy in the proposal.

Thanks @mshudrak for your reply. Could you tell me any file which will be easier for me to understand to refactor ? As there are lots of files.

@mshudrak Can you assign this to me, I can do it no time?

@Roshan102003 we do not assign bugs for individuals now since we have a lot of interest from various contributors. So far, we had multiple PRs to fix this issue. However, this is a long term project requiring coordination with project owners and design doc. I'd prefer to keep it for GSoC 2023 timeframe.


Valid Database file

It is possible to check if file is valid?
For ex:
LiteDatabase ldb = new LiteDatabase("some_wrong_file.swf");

Hi @shai-benshimol, if you use LiteEngine ctor, datadase will be open at this time (not as lazy as LiteDatabase) and will be validate.

Hi! With the objective of organizing our issues, we are closing old unsolved issues. Please check the latest version of LiteDB and open a new issue if your problem/question/suggestion still applies. Thanks!


Inline Type Expansion

Check for existing issues

[X] Completed

Describe the feature
Currently Zed only offers type expansion if you hover over the variable. One of my favorite features of CLion is the inline type expansion. Would it be possible to add this to Zed?
If applicable, add mockups / screenshots to help present your vision of the feature

This feature request already exists; https://github.com/zed-industries/community/issues/138


Compute txindex metadata for mempool

#659  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @lazynina and the rest of your teammates on  Graphite


feat: baidu map demo

添加了百度地图demo , 地图标点及搜索
closes #158

✏ Mark the necessary items without changing the structure of the PR template.

[x] Pull request template structure not broken

Type

ℹ What types of changes does your code introduce?

👉 Put an x in the boxes that apply

[x] New feature (non-breaking change which adds functionality)

@DesignHhuang 搜索好像不能用


Python3 part6

Pull Request Description
What issue does this change request address?
#71
What are the significant changes in functionality due to this change request?
Better Python 3 support

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?

Job Mingw Test on c08b2c1 : canceled by @joshua-cogliati-inl

Job Test qsubs on c08b2c1 : canceled by @joshua-cogliati-inl

Job Test mac on c08b2c1 : canceled by @joshua-cogliati-inl

@joshua-cogliati-inl does this still need to be reviewed?

No, everything in it is in part7.

so we close this?

All incorporated into part 7, so this can be closed.


How to auto configure all node with same SSID without manual configuration (IDFGH-2340)

I am very new to mesh wifi network. As now, I did built up a mesh network by pre-configure each ESP32 SSID inside sdkconfig under example configuration section. Now I wish to move to next step, which is set only the central node, then the other ESP32 automatic connect to it without any configuration. Is it possible to do that ?

@JDchew Thanks for reporting. Would you please help share which example configuration you are referring to? Would you please help provide more details as suggested in the issue template? Information like elf, sdk configuration, backtrace, log outputs, commit ID, hardware and etc. would help us debug further. Thanks.

@JDchew Thanks for reporting. Will close due to short of feedback, feel free to reopen with more details. Thanks.


Specifically, this seems to be triggered when the code contains a variable that does not exist -- rustc will try to make szggestions for names to use, which can trigger loading external crates, which might be what is happening here.
Cc @hyd-dev

cargo test without Miri fails with same errors in that repository and all other libcore tests passed. It's caused by the miri-test-libstd-specific core_miri_test crate which is effectively another libcore.

Well, but real libcore has something similar, doesn't it? There's libcore and there's "libcore built for tests".

Well, but real libcore has something similar, doesn't it? There's libcore and there's "libcore built for tests".

This is the command used by x.py test library/core --stage 0 -v --doc:
/checkout/build/x86_64-unknown-linux-gnu/stage0/bin/rustc --crate-type bin --cfg bootstrap --sysroot /checkout/build/x86_64-unknown-linux-gnu/stage0-sysroot --edition 2018 -o /tmp/rustdoctest1Vq8r8/rust_out -L dependency=/checkout/build/x86_64-unknown-linux-gnu/stage0-std/x86_64-unknown-linux-gnu/release/deps -L dependency=/checkout/build/x86_64-unknown-linux-gnu/stage0-std/release/deps --extern core=/checkout/build/x86_64-unknown-linux-gnu/stage0-std/x86_64-unknown-linux-gnu/release/deps/libcore-2905b2c8ac6b4c16.rlib --extern rand=/checkout/build/x86_64-unknown-linux-gnu/stage0-std/x86_64-unknown-linux-gnu/release/deps/librand-bbbfa0c2da24b204.rlib -Ccodegen-units=1 -C lto=off -C embed-bitcode=no -Z crate-attr=doc(html_root_url="https://doc.rust-lang.org/nightly/") -Z force-unstable-if-unmarked --target x86_64-unknown-linux-gnu --color always -

It looks like it's passing --extern core=... which will override the libcore from sysroot. Actually the sysroot one and the deps one have the same content in this case (I belive one is copied/hardlinked to another), so there is not a seperate "libcore built for tests".
However, the situation is different for core_miri_test. It's built differently than the sysroot core. Even if I rename the crate to core, rustc/Miri thinks libstd (and maybe also other libraries in the sysroot) needs a different version of core (it has a different hash), and still tries to load the core from sysroot.

Hm... you are probably right. I think for unit tests the situation is very much like core: those are a separately built crate in both cases. For doctests the situation might well be different. We'd need to make it so that rustdoc/rustc think of the sysroot core crate as being "the crate associated with this doctest" -- like, not have core_miri_test around at all.
Though I am not sure how core_miri_test gets imported at all currently... maybe that is the thing that the search for suggestions is doing, eagerly loading more crates than it otherwise would?

maybe that is the thing that the search for suggestions is doing, eagerly loading more crates than it otherwise would?

Seems like so. This is the backtrace for the "resolving crate core_miri_test" log message:

   1: tracing_core::dispatcher::get_default
   2: tracing_core::event::Event::dispatch
   3: rustc_metadata::creader::CrateLoader::maybe_resolve_crate
   4: rustc_metadata::creader::CrateLoader::maybe_process_path_extern
   5: rustc_resolve::diagnostics::<impl rustc_resolve::Resolver>::lookup_import_candidates
   6: rustc_resolve::late::diagnostics::<impl rustc_resolve::late::LateResolutionVisitor>::smart_resolve_report_errors
   7: rustc_resolve::late::LateResolutionVisitor::smart_resolve_path_fragment::{{closure}}
   8: rustc_resolve::late::LateResolutionVisitor::smart_resolve_path_fragment
   9: rustc_resolve::late::LateResolutionVisitor::resolve_expr
  10: rustc_ast::visit::walk_expr
  11: rustc_resolve::late::LateResolutionVisitor::resolve_expr
  12: <rustc_resolve::late::LateResolutionVisitor as rustc_ast::visit::Visitor>::visit_block
  13: <rustc_resolve::late::LateResolutionVisitor as rustc_ast::visit::Visitor>::visit_fn
  14: rustc_ast::visit::walk_item
  15: rustc_resolve::late::LateResolutionVisitor::resolve_item
  16: <rustc_resolve::late::LateResolutionVisitor as rustc_ast::visit::Visitor>::visit_block
  17: <rustc_resolve::late::LateResolutionVisitor as rustc_ast::visit::Visitor>::visit_fn
  18: rustc_ast::visit::walk_item
  19: rustc_resolve::late::LateResolutionVisitor::resolve_item
  20: <rustc_resolve::late::LateResolutionVisitor as rustc_ast::visit::Visitor>::visit_block
  21: <rustc_resolve::late::LateResolutionVisitor as rustc_ast::visit::Visitor>::visit_fn
  22: rustc_ast::visit::walk_item
  23: rustc_resolve::late::LateResolutionVisitor::resolve_item
  24: rustc_ast::visit::walk_crate
  25: rustc_resolve::late::<impl rustc_resolve::Resolver>::late_resolve_crate
  26: rustc_session::utils::<impl rustc_session::session::Session>::time
  27: rustc_resolve::Resolver::resolve_crate
  28: rustc_interface::passes::configure_and_expand
  29: rustc_interface::queries::Queries::expansion
  30: rustc_interface::queries::<impl rustc_interface::interface::Compiler>::enter
  31: rustc_span::with_source_map
  32: rustc_interface::interface::create_compiler_and_run
  33: scoped_tls::ScopedKey<T>::set
  34: std::sys_common::backtrace::__rust_begin_short_backtrace
  35: core::ops::function::FnOnce::call_once{{vtable.shim}}
  36: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/b9197978a90be6f7570741eabe2da175fec75375/library/alloc/src/boxed.rs:1572:9
  37: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/b9197978a90be6f7570741eabe2da175fec75375/library/alloc/src/boxed.rs:1572:9
  38: std::sys::unix::thread::Thread::new::thread_start
             at /rustc/b9197978a90be6f7570741eabe2da175fec75375/library/std/src/sys/unix/thread.rs:74:17
  39: start_thread
  40: clone

I think I've seen this behavior of rustc suggestions cause similar trouble in the past... but OTOH it kind of has to load all the crates since ´extern crate` is implicit since the 2018 edition.
So probably the only thing we can do is to try and make the core_miri_test crate empty. I assume that is what the patch you showed on Zulip does?

So probably the only thing we can do is to try and make the core_miri_test crate empty. I assume that is what the patch you showed on Zulip does?

Yes.

For the record, that diff was
diff --git a/core_miri_test/Cargo.toml b/core_miri_test/Cargo.toml
index 524cce8..b8df702 100644
--- a/core_miri_test/Cargo.toml
+++ b/core_miri_test/Cargo.toml
@@ -12,6 +12,10 @@ path = "../libcore/src/lib.rs"
 test = false
 bench = false

+[features]
+miri-test = []
+default = ["miri-test"]
+
 [[test]]
 name = "coretests"
 path = "../libcore/tests/lib.rs"
diff --git a/rust-src.diff b/rust-src.diff
index e69de29..965f559 100644
--- a/rust-src.diff
+++ b/rust-src.diff
@@ -0,0 +1,12 @@
+diff --git a/library/core/src/lib.rs b/library/core/src/lib.rs
+index 3557dbad..6c089b0c 100644
+--- a/library/core/src/lib.rs
++++ b/library/core/src/lib.rs
+@@ -49,6 +49,7 @@
+ //
+ // This cfg won't affect doc tests.
+ #![cfg(not(test))]
++#![cfg(any(not(feature = "miri-test"), doctest))]
+ #![stable(feature = "core", since = "1.6.0")]
+ #![doc(
+     html_playground_url = "https://play.rust-lang.org/",


betterlockscreen: v4.0.4 -> v4.2.0

Description of changes
Update to latest release
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

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.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

[x] Fits CONTRIBUTING.md.

Updated to v4.2.0 ✌🏻

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1085

Done, thanks for the feedback ✌🏻


feat: distinguish different Touches

What kind of change does this PR introduce?
This PR adds the option of controlling a Touch, and only that Touch, after it has been created by a call to TouchScreen.touchStart.
Closes #13084 .
Did you add tests for your changes?
Yes.
Summary
In this PR, TouchScreen.touchStart returns a (promise of) a Touch. This way, touches can be manipulated individually by calling Touch.move or Touch.end.
Does this PR introduce a breaking change?
Well... This test documents an aspect of the current behavior of TouchScreen.touchStart: two consecutive calls to it will not result in two touchstart events. This PR proceeds from the assumption that that behavior was in fact a bug: two consecutive calls to TouchScreen.touchStart should result in two touchstart events. Seen in this way, this PR fixes a bug (in addition to adding new functionality). But if the current behavior of TouchScreen.touchStart was not a bug, then this PR introduces a breaking change.
Other information

I'm not sure how to handle the Firefox failures. Should there be a 'failure expectation' for the ElementHandle tests having to do with touch, similar to this one?

@OrKoN  One more thing! If you now start a touch through TouchScreen.touchStart and then you end it through TouchHandle.end, then the TouchScreen still keeps the handle in its array of touches. Let me fix that.

@OrKoN One more thing! If you now start a touch through TouchScreen.touchStart and then you end it through TouchHandle.end, then the TouchScreen still keeps the handle in its array of touches. Let me fix that.

I fixed this by making sure that the handle is removed from the TouchScreen instance and by throwing an error from TouchScreen.touchEnd in case there is no touch to end. This is compatible with the current behavior: we already throw the ProtocolError in this case.

Since the Touchscreen functionality in cdp/Input and bidi/Input were so similar, I decided to extract some functionality to a new class Touchscreen in common.

@Lightning00Blade this test seems to be failing. Could this be due to the way we choose pointer ids (incemental instead of re-using them)?

@Lightning00Blade this test seems to be failing. Could this be due to the way we choose pointer ids (incemental instead of re-using them)?

Especially since it did pass earlier, before we changed it.

@Lightning00Blade this test seems to be failing. Could this be due to the way we choose pointer ids (incemental instead of re-using them)?

Never mind, it seems to have to do with the location of the touches. Should I just add a failure expectation?

I suppose many of those 'failure expectations' could be removed if we replaced assertions such as this with snapshots: a snapshot for each browser/platform. But that's for another pr :)

This failure does not seem to be related to the PR's changes, right?


Improve the documentation regarding the Deploying WSO2 API-M in a Distributed Setup

Description:
In order to share the deployment artifacts, Earlier we recommended to share the entire <API-M_HOME>/repository/deployment/server directory. But now its not necessary and sharing synapse-configs and executionplans are enough. Shall we improve the documentation including that part.

Moved issed to docs-apim repo.
https://github.com/wso2/docs-apim/issues/1594


j.clients & builder .graphite

config manager
server.install()
basic test

also implement j.builder....
look at readme in that builder directory & TEMPLATE dir

implement j.client

learn how to do it in template for client

implement j.builder....

learn how to do it in template


Default string params are double quoted in swagger.json

I have a route that has a default string value, e.g.,
GET /config   controllers.MyController.getConfig(location: String ?= "US")

In the generated swagger.json file, the default value is double quoted:
{
	"parameters": [{
		"in": "query",
		"name": "location",
		"type": "string",
		"required": false,
		"default": "\"US\""
	}]
}

this causes the input field in swagger-ui to have the quotes in it, instead of just US

As a workaround, it's possible to override the value in the routes comments:
###
# parameters:
#   - name: location
#     default: US
###
GET /config   controllers.MyController.getConfig(location: String ?= "US")


get_chromecast is rather slow.

The get_chromecast method is pretty slow when it performs the initial discovery. I have a stateless script that runs anew every time it is called, but is there something I can serialize and deserialize to make the discovery process quicker? I'll only ever use one Chromecast at a time, so it would be nice if I could save its address and other info to a file and just load that rather than do the complete discovery again.
How can that be done? Can it be added to the docs?

It is a bit slow, and sometimes unreliable. This is generally the case with network discovery, unfortunately.
You can load a specific Chromecast by IP Address like this:
cast = pychromecast.Chromecast('<IP_ADDRESS>')

This will skip all discovery.

That's exactly what I wanted, thank you!