.NET 7

[ ] Move to .NET 7
[ ] Evaluate Regex Source Code Generators

Evaluate Regex Source Code Generators

Right now there are targets for NS2.0, NS2.1 and .NET 6. Do you want to drop these and just rely on .NET 7?
.NET 6 as LTS should be kept at least. As the regex SG is only available from .NET 7 onwards this has to be considered. Should be quite simple though, with pre .NET 7 having the Regex as field returned by a method, just the same way as the SG-one does, so that usages can be the same for all targets.

Oh, I thought the targets for 7 are also there now.


Clarify the oauth2_auth_token scenario and add the per call credentia…

…ls scenario

@ejona86

@ejona86 Let me know if we should make the two test cases not send/receive a lot of data. I think it is still easy to change at this point since not a lot of languages have implemented them.

@yang-g, yeah, let's go ahead and remove the response_* and payload fields in the request message, and similarly remove the assert on response payload body size.

@ejona86 PTAL


Create links on metadata list pages

The unfiltered observation/forecast/cdf listing pages don't have create links. These should link to a site listing page where the table entries link directly to the 'Create ' page for that site.

closed by #54


Eliminate delays between the Microsoft servicing releases and source-build availability

Situation
Source-build availability often lags behind the Microsoft .NET releases.  It is not unusual for source-build to be one whole day behind.
A primary reason for this is related to the merging of the code from internal -> public.  Other reasons include the PR validation when committing the source-build changes to the public repos.  This usually takes 4-5 hours.
This is non-issue for RHEL today as there is a tarball hand-off prior to the release.  This does however affect the Fedora release and will become increasingly more important as more distros source-build .NET.
Objective
Release source-build in step with the .NET product.  It should be included as part of the release tic-toc activities.  The release should not be considered complete until the source-build release is available.  The source-build release should be available within minutes of the binary artifact availability.
Execution
Identify and address the long running tasks and bottlenecks in the source-build release.  Automation should be introduced where feasible.  Lastly the source-build release process should be integrated into tic-toc and the release pipeline.

Source-build releases have happened same day as the Microsoft release since ArPow and a significant investment in automation.  Closing.


The composer.json file could not be read

Hi there, I just installed this extension and I could not create a new PHP class at all. While composer.json is present in main directory.
Error message: the composer.json file could not be read
Thanks in advance

It is possible that your composer.json not contains an "autoload" entry and only contains "autoload-dev" entry?
This case I had not contemplated, but I will fix it.

@KaloyJS I have released an update with some fixes and checks when reading composer.json file.
If error persists, please check that composer.json file not contains any syntax error (like trailing comma at last element in an array)


Link & logo

We're using this excellent plugin on our site here.
Below is a logo which can point to https://atlasail.com
https://i.imgur.com/R3iEQPi.png
Thanks!

Receiving spam

Thank you for your support of bootstrap-select! Unfortunately, we are discontinuing the "used by" section.


Fix/suppress CodeQL scanning issues

Rel: https://github.com/github/codeql/issues/12328

Only one left as false positive from CodeQL. Closing.


Improving universal build and run scripts to support cross-platform compilation

We have a few requests for this feature - need to discuss how to do it and who can help with that ...

We should add "get-device" script to define target platform capabilities (env, config and tools) similar to how I did it in the original CK framework.


Upgrade django-jsonfield dependency

Fixes #52.

On Django 1.7 JSONField returns type unicode (or str in Py3). On later versions it returns a dict as expected.

Suffers from #60


MISO error

Description of the bug
Event ENSG00000005302 not found in pickled directory index. Are you sure this is the right directory for the event?
Command used and terminal output
WARN: The operator `first` is useless when applied to a value channel which returns a single value by definition
ERROR ~ Error executing process > 'NFCORE_RNASPLICE:RNASPLICE:VISUALISE_MISO:MISO_SASHIMI (2)'

Caused by:
  Process `NFCORE_RNASPLICE:RNASPLICE:VISUALISE_MISO:MISO_SASHIMI (2)` terminated with an error exit status (1)

Command executed:

  sashimi_plot --plot-event ENSG00000005302 index miso_settings.txt --output-dir sashimi

  cat <<-END_VERSIONS > versions.yml
  "NFCORE_RNASPLICE:RNASPLICE:VISUALISE_MISO:MISO_SASHIMI":
      python: $(python --version | sed "s/Python //g")
      misopy: $(python -c "import pkg_resources; print(pkg_resources.get_distribution('misopy').version)")
  END_VERSIONS

Command exit status:
  1

Command output:
  (empty)

Command error:
  /usr/local/lib/python2.7/site-packages/matplotlib/cbook/deprecation.py:107: MatplotlibDeprecationWarning: The mpl_toolkits.axes_grid module was deprecated in version 2.1. Use mpl_toolkits.axes_grid1 and mpl_toolkits.axisartist provies the same functionality instead.
    warnings.warn(message, mplDeprecation, stacklevel=1)
  Traceback (most recent call last):
    File "/usr/local/bin/sashimi_plot", line 11, in <module>
      sys.exit(main())
    File "/usr/local/lib/python2.7/site-packages/misopy/sashimi_plot/sashimi_plot.py", line 276, in main
      plot_label=plot_label)
    File "/usr/local/lib/python2.7/site-packages/misopy/sashimi_plot/sashimi_plot.py", line 142, in plot_event
      %(event_name, pickle_dir)
  Exception: Event ENSG00000005302 not found in pickled directory index. Are you sure this is the right directory for the event?

Work dir:
  /flash/SciTechGrp/Zain/54/4ab0250756d10788d62592d4524e58

Tip: view the complete command output by changing to the process work dir and entering the command `cat .command.out`

 -- Check '.nextflow.log' file for details

Relevant files
No response
System information
No response

Hey @ZeinBader
Can you provide the nextflow.log file for me to inspect? The genes provided as default in the nextflow.config are for the human genome, make sure you replace these with gene identifiers found for the reference genome you're using.

I had the same problem using a yeast genome.  Adding a yeast gene via '--miso_genes' solved the problem.

Closing issue as no response. Please re-open if you are still encountering an issue.


Bring all notebooks up to date.

Fixed two issues:

notebook R - How to pull in reusable code from source control.ipynb was installing a particular older version of the gargle package as an example. BUT bigrquery now depends on gargle for auth logic. Downgrading gargle causes bigrquery auth to stop working.
The input data URL for notebook R - Plotting example for Boston 311 data.ipynb no longer worked (returned a 500 level error). I updated the notebook to fetch the data from a newer URL.

Otherwise all the notebooks were working fine as-is. In several cases I removed code that was no longer needed.

for my info, is this something that is necessary for any and every notebook that uses the bigrquery package, or specifically ones that need auth tokens?

Yes, with the most recent release of bigrquery https://github.com/r-dbi/bigrquery/releases/tag/v1.2.0 it now uses the gargle R package for auth. This is great because if there is already a credential on the machine, it will make use of that by default. [less friction for the user!]
As long as people are using a recent release of bigrquery, they no longer need the Ronaldo R package and no longer need to call bigrquery::set_service_token(Ronaldo::getServiceAccountKey())


Update embedded rss.xml code in the docs

Nothing special. I just copied the code for rss.xml from tpl/template_embedded.go to the RSS (feed) Templates page, because it was a bit outdated there.

Merged, thanks. Should be live soon.


updated the email error and error(s) message on the sign up page

Updated the error messages on the email sign up page.

Closing due to inactivity. Please feel free to reopen when you have time to address the PR comments!


[prim/rtl] prim_packer is generating a lint error for entropy_src module

Getting this lint error message:
E   ASSIGN_SIGN:   prim_packer.sv:77   Unsigned target 'lod_idx' assigned signed value 'i'
Should this be waived or fixed?
@eunchan Is this issue for you to address?

This could be fixed with `unsigned(i) or $unsigned(i), or waived. Can you see if one of the first two fixes it for you? Then you could include that fix in your next PR.

Just amended the prior PR, since the unsigned fix was not done correctly. Used the $unsigned(i) form.

@mwbranstad is this still a problem for you? I'm guessing not since you switched to your own brand of packer.
@eunchan should we fix this in the other version?

Personally, I prefer waive this kind of thing :) Let me address this in KMAC lint

yeah waiving is fine too with me.
On Thu, Sep 24, 2020 at 1:25 PM Eunchan Kim<EMAIL_ADDRESS>wrote:

Personally, I prefer waive this kind of thing :) Let me address this in
KMAC lint
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/issues/2999#issuecomment-698570047,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2RSWQ5N5X3SQ3VA2HV23SHOTKNANCNFSM4PKVBK6Q
.

for what it is worth, I generally prefer to fix these things in RTL because it is more portable to all future checkers, and it also shows that you have a full understanding of the issue (sometimes we think we do and don't unfortunately). Still, sometimes in a parametrized design, one cannot fix it due to limits in the language, so a waiver is needed.

Since the prim_packer_fifo was used in this specific case, it is safe to close this issue now.


Logging

Proposal
Goyave currently doesn't provide any built-in way to log activity or errors. You can however implement a middleware yourself and use chained writers if needed. Logging is an important part of all applications so a flexible implementation should be added to the framework. How logging is made in an application should still be decided by the developer, not the framework.
One or multiple interfaces will be needed and they should fit most (or all) popular logging libraries (such as logrus). A default logger can be provided.
The logging feature should allow:

logging of incoming requests
logging of responses
logging of debug, info, errors on-demand in handlers and middleware
custom logging behavior in case of unexpected error
set output (stdout, stderr, files, other)

The implementation is not defined yet, so feel free to discuss and suggest one.
Possible drawbacks
None.
Additional information
This issue is a feature proposal and is meant to be discussed.
It is also a good candidate if you want to contribute to the project.

This feature has been started in the feature/log branch.


.woff2 support

please add support for .woff2.
related bug --types will generate additional font files besides the one defined. --types 'woff'

Bi @pbflanagan - the --types param is now fixed, and even though not specified by default it now supports woff2 - enjoy!

dope


[iOS] Create StaffView

Idea Description

Create StaffFeature target
Create StaffView in StaffFeature target

UI only is okey 👍🏼
implement StaffView UI with ContributorView design once.

Reference images and links

✋

Thanks!!! Assigned!!! 💪💪💪💪💪


ISPN-6581 Typed remote exec in binary cache

https://issues.jboss.org/browse/ISPN-6581

Remote execution for typed scripts should be done in binary cache so
that remote events can be correctly propagated. So, data conversion
for non-compatibility mode caches is provided by a new class called
DataTypedCache and it comes with a corresponding
DataTypedCacheManager.
When compatibility mode is enabled, the inner layer already provides
data conversion layer. The problem with compatiblity mode is that it
currently needs server-side configuration as opposed to a simple
script header definition. Once encoding is better handled, we should
be able to find a better solution for both.
When data is inserted directly by the script, no version information
is currently provided since that's managed by Hot Rod, so code had to
be adjusted to deal with this situation. This might change in the
future.
Simplified EventLogListener code to check version information using
purely the remote interface, just like other language target clients
will use. This uncovered issues with dealing with version-less
entries.
Ported EventLogListener code to using Java 8 to make the code a lot
clearer and cleaner to read.

It seems like there's some errors in testsuite, looking:
http://ci.infinispan.org/viewLog.html?buildId=39476&tab=buildResultsDiv&buildTypeId=bt9

Updated with fix for failing tests.

Updated the comment with more details about the fix.

Pushed to master.


Repository URL not in project metadata

https://github.com/scverse/cookiecutter-scverse/blob/c27563d1bd3901b71095b7e2c251ba16b4cc9127/{{cookiecutter.project_name}}/docs/conf.py#L24
The info["Project-URL"] just provides the docs URL

info can have the same key multiple times. In the top example from the docs it has 3 "Project-URL" entries!
I've also noticed that the result of metadata can get quite messed up for editable/ dev installations. I think this has actually caused us a lot of CI trouble in the past. Doc builds might be a bad place to rely on it.

The only problem I’m aware of is that the metadata is pretty much always outdated because people don’t re-install editable projects (which is kinda the point of doing them in the first place). In what ways can things get messy?
The values of this field look like this:
$ python -c 'import importlib.metadata as im; print(*im.metadata("wheel").get_all("Project-URL"), sep="\n")'
Documentation, https://wheel.readthedocs.io/
Changelog, https://wheel.readthedocs.io/en/stable/news.html
Issue Tracker, https://github.com/pypa/wheel/issues

Basically the outdated thing.
Since the use case is specifically a developer workflow, and this would specifically break for developers, I think it's fine to leave everything as is

This is a tradeoff, not a black and white issue.
in both cases an issue is more or less rare as it can only appear when people change their repo URL.

If we derive things from metadata, the issue is that the URL can be stale in local doc builds

very rare, but hard to debug: caused by URL change, limited to editable builds, until people reinstall
extremely low impact: just a wrong URL in locally built docs. CI builds (that other people actually see) are unaffected

If we hardcode the URL, the issue is that people forget to update the URL in all places

pretty rare: caused by URL change
relatively low impact: just a wrong URL in all docs

Since both impact and frequency is lower in solution 1, I vote for that one. The only thing speaking for the latter is that the former is harder to debug, as stale metadata is harder to spot.
I also generally thing data should either only live in one place or there should be automation in place that checks if multiple instances are synced

I think this has actually caused us a lot of CI trouble in the past.

Basically the outdated thing.

if it’s just the outdated thing, it can’t cause any CI troubles, since the package is freshly installed with correct metadata in CI.

The issue raiser here was more a bug report about metadata containing incorrect values, which it turns out was due to a confusing API. So I think there is no change needed.

if it’s just the outdated thing, it can’t cause any CI troubles

The CI issues were: "why is this different on CI than locally". Those can be quite difficult dev problems, so I'd rather not expose users to them.

The kicker for me is that the latter affects the publicly viewable version of the docs

I think changing the source repo URL (like renaming or moving organizations) is going to be a situation that calls for a global find and replace. Those values get interpolated many places in the template, many of which cannot access installed project metadata.

I also generally thing data should either only live in one place or there should be automation in place that checks if multiple instances are synced

The cruft template sync or find and replace do this. A sphinx extension that checks for dead links could also be useful here.

How about we use a toml parser then instead of metadata? Guaranteed fresh and DRY.
[project.optional-dependencies]
doc = [
    ...,
    'tomli; python_version < "3.11"',
]

conf.py:
try:
    import tomllib
except ImportError:
    import tomli as tomllib
from pathlib import Path

DOCDIR = Path(__file__).parent

meta = tomllib.loads((DOCDIR.parent / 'pyproject.toml').read_text())['project']

Continuing this discussion in #163.


Wrong tag used in code example under 'Efficient page loading'

In code example under section 'Efficient page loading' line 15 the tag ShellContent is used but should be Tab.

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

ID: ef7242a0-d46e-19ea-e22d-f327dcc9b3e9
Version Independent ID: f050be8e-9413-19e7-5799-90a55c4e5bfb
Content: Xamarin.Forms Shell Layout - Xamarin
Content Source: docs/xamarin-forms/app-fundamentals/shell/tabs.md
Product: xamarin
Technology: xamarin-forms
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Hi @RasmusKoldsoe
ShellContent is valid in that scenario, because there's an implicit conversion operator that automatically wraps in in a Tab.


Witness scope support

Fixes #89
Related to #92

Looks good. What will custom contract support entail?

It all depends on what the CLI implementation ends up looking like.  Hopefully we can collect the input from the user using VS Code inputs (in which case it will be simple), if we need to get the input from the user through a custom interface it will be a bit more involved.


Update bootstrap-colorpicker-module.js to support colors in 0x format

extended module to support colors with 0x format.
Usage:

Hey, thanks for PR. We wont extend current script for parsing colors. We have to use some external dependency to handle this in the future

No problem, hope i can help in future again  :)


Which virtualhome envronment(0-50) matches your scenarios?

I am using virtualhome 2.3.0. When i debug the following code:
environment = populate_environment(graph, extract_objects(reference_program), "kitchen")
the returned environment is not right. For example, the object <breadslice_311> is labelled as 'asset' and it's relationships with other objects just doesn't make sense. I wonder which virtualhome environment(0-50) did you use when designing your scenarios ?
I am pretty sure the code:
reset(comm)
just doesn't initiate the corrent environment, at least in my local setup.
Any suggestions? Thanks in adavance.

We apologize for the delayed response and any confusion caused. Thank you for bringing this issue to our attention.
The issue you've encountered is due to a version mismatch in the VirtualHome simulator. The object names and IDs in this code are based on version 2.2.4, while our documentation incorrectly stated the use of version 2.3.0. We are in the process of updating our documentation to rectify this mistake.
Regarding your specific query, using the Python API virtualhome==2.3.0 is appropriate. However, as you rightly noted, the comm.reset command in this version is incompatible with the older simulator. Instead, comm.post_command is being used to reset the environment. The VirtualHome simulator version 2.2.4 is available for download at the following link:
VirtualHome Documentation - Downloads v2.2.4
On a separate note, we would like to inform you that this repository is compatible with openai==0.28.1, not the latest version openai==1.2.3.
We sincerely apologize for any inconvenience this has caused and hope that this clarification will help you. Should you have further questions or encounter additional issues, please feel free to reach out.
Best regards,


tabular format output

I'm not sure there's a way to generalize the tabular output for the different commands. Tables are tricky because they have different headers, different value types, sometimes we'll want a nested value, etc. We'll be able to extract the shell of the table, but the headers and values may have to be command-specific.

Tables are cool, so long as they aren't as super-formatted like nova. It's harder to use with tools like cut and grep (grep -v will show the dividers for instance).

@rgbkrk Are you working on a minimal, docker ps-like, tabular output?

Yeah, let me take this one.

After coding #20 , I'm thinking that by default the table should be with a border, but that we provide a noborder flag that will be minimal. See here: https://github.com/jrperritt/rack/pull/20/files#diff-84efe558aa2959a3e15e43a6eba8a1b1R100

Closing this. I think we've got a handle on the table format thanks to @rgbkrk

I'm so persnickety. Thanks for fighting through it with me.
:heart_decoration:


Centralize TypeScript resource types

We have created a central repository for TypeScript resource types: https://github.com/org-formation/aws-resource-providers/

leaving this pinned for visibility but closing out as done


[docs] Copy icons to clipboard

[x] I have followed (at least) the PR section of the contributing guide.

Thanks for working on it. I think we should:

Add a "copy" button. Copying when selecting or just clicking the text is unexpected. We don't know what might be in the user's clipboard that we just splatted.
Add a notification similar to that on the "copy the source" button in the demos, so that the user knows that the text has been successfully copied.
Remove the automatic text highlight, since this breaks expectations for a single click on some text.

I have tried to experiment with this but I couldn't come up with anything great without dedicated a disproportionate amount of time. I have found two things that suck. 1. the snackbar is a nightmare to us: #18098, the dialog title bundle two DOM nodes #19696.

Actually, I think that I have found a nice trick, using https://ionicons.com/, https://fontawesome.com/icons/archway?style=duotone and GitHub copy button as inspiration:

Definitely an improvement - the only thing I might add is "click to copy" on the tooltip. It isn't unreasonable to assume that a click is with the intention to copy though, so probably good enough.

the only thing I might add is "click to copy" on the tooltip.

FontAwesome does that, I agree, it has the potential to work even better. I won't spend time on it, but if somebody wants to push it further, I will be curious to see the result :)

I think that these 3 labels should be generic (not scoped under searchIcons)

I originally thought the same, but since they will dedupe on CrowdIn, there's no overhead. Doing it this way reduces the chance of accidentally removing a translation in use on another page. It should also make it easier to spot dead translations.
(I also noticed that you had moved potentially shareable translations in the API page under a page specific key.)

I originally thought the same (in general), but since they will dedupe on CrowdIn, there's no overhead. Doing it this way reduces the chance of accidentally removing a translation in use on another page. It should also make it easier to spot dead translations.

I don't think that spotting dead translations should be a variable on the tradeoff as it can be automated. I don't think that accidentally removing a translation is a variable either because it's easy to grep in the codebase. I think that what's important is whether or not we want to anticipate the need to provide custom translation for each context. IMHO, the best tradeoff is to optimize for English and to a "best-effort" for the other locales, so avoiding duplication

@CodeWithGuruji Thanks for working on this :)

@CodeWithGuruji Thanks for working on this :)

Thank you so much @oliviertassinari @mbrookes


Facing a cloudformation error when running servlerless package

{"code":"AWS_CLOUD_FORMATION_CREATE_STACK_ALREADY_EXISTS_EXCEPTION","providerError":{"message":"Stack [NewRelicLicenseKeySecret] already exists","code":"AlreadyExistsException","time":"2023-06-09T02:12:50.121Z","requestId":"23fa696b-90ed-4f9c-bb17-93c9d9beebd3","statusCode":400,"retryable":false,"retryDelay":82.09528233197582},"providerErrorCodeExtension":"ALREADY_EXISTS_EXCEPTION"}

Not sure if this is expected behaviour when running sls package

@lucas-reap-hk Thank you for the report. Does the package operation continue, or does this stop the packaging process?
During a full deployment, we might see this output as a warning if the license key secret has already been created, but it wouldn't stop deployment. I've just checked with a local test project (for which there's already a secret defined in AWS), I don't see this output on either sls deploy or sls package.
What's in the custom: newRelic block of your serverless.yml?

Looking through the index.ts and integration.ts files, the plugin first checks for the existence of the license key secret (with checkForManagedSecretPolicy), and the plugin attempts to create it if it doesn't exist (with configureLicenseForExtension). If the creation fails because the policy exists, the plugin logs that and should continue. Typically, if the secret already exists, the plugin wouldn't try to create a new one, unless your AWS account doesn't have permissions to check for the existing secret. (If that's the case, this error message would be expected.)


Implement webhook validation for the XGBoostJob

What this PR does / why we need it:
I implemented webhook validations for the XGBoostJob.
Additionally, I didn't add any additional validations. The traininig-operator has the same validations the same as before.
Although we potentially commonize podTemplate validations, I leave such commonize in the follow-ups.
This PR depends on https://github.com/kubeflow/training-operator/pull/2035
Which issue(s) this PR fixes (optional, in Fixes #<issue number>, #<issue number>, ... format, will close the issue(s) when PR gets merged):
Part-of https://github.com/kubeflow/training-operator/issues/1993
Checklist:

[ ] Docs included if any changes are user facing

/hold

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

105 of 157 (66.88%)  changed or added relevant lines in 2 files are covered.
6 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.1%) to 42.784%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/webhooks/xgboost/xgboostjob_webhook.go
49
74
66.22%

pkg/webhooks/pytorch/pytorchjob_webhook.go
56
83
67.47%

Files with Coverage Reduction
New Missed Lines
%

pkg/controller.v1/mpi/mpijob_controller.go
6
80.67%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
3765

Relevant Lines:
8800

💛  - Coveralls

Rebased.


Phantom 2.x not rendering font-style property (bold & italic) when using font-face

Hello,
we have stumbled upon an issue with Phantom, since we migrated to 2.x branch - styled fonts (font-style) are not rendered as they should (applied style is not visible).
I've prepared a fiddle:
https://jsfiddle.net/ghzs1egj/5/
If you put that through phantom you will see that bold is actually not applied.
We have tried different declarations of font-face, different font types - and nothing helps.
Using separate font files for different declaration can't be treated as a solutions for 2 reasons:

this would bloat file transfer (3-4x more fonts to handle...)
not all fonts are avaiable in their italic/bolded/bolded+italic versions.

In Phantom 1.9x it was working.

+1

+1

+1

+1

+1

+1

+1

+1

Maybe related issue #13742

+1

+1

+1

+1

+1

+1

+1

+1
So while this messes up web fonts served by Google Fonts, TypeKit appears to work as expected:

Okay so this makes sense now. PhantomJS v2 uses a new version of WebKit, which is causing the Google Fonts CDN to serve *.woff2 files, which is apparently where the problem is. If you fake an ancient user agent, the endpoint will send you an older file which still renders correctly in PhantomJS v2.
Workaround: I was able to get weights and styles to render correctly by setting my user agent to Firefox 27::
page.settings.userAgent = 'Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0'

This causes the Google Fonts CDN to serve *.woff files and now we have font weights and styles again (note that Arima Madurai does not offer italics):

Considering the issue has been reported over a Year back. Any new updates on this ? , I am still facing this issue in 2.1.1, are there any plans to fix this.

+1

+1

+1

+1

+1

+1

+1

+1

+1


struct .error: unpack requires a buffer of 12 bytes

I met some errors when I had a try to run this code. Please help me!
I'm running Ubuntu 18.04.5 LTS
Python 3.7
Pytorch 1.9
Cuda 11.1
Depth stats 0.19367019493628088<PHONE_NUMBER>1743836 61.20548491109312
Done with imgs2poses
Depths prior training begins !
Found cache /home/xxx/code/NerfingMVS/models/depth_priors/mc.pth
/home/xxx/miniconda2/envs/py37/lib/python3.7/site-packages/torchvision/transforms/transforms.py:281: UserWarning: Argument interpolation should be of type InterpolationMode instead of int. Please, use InterpolationMode enum.
  "Argument interpolation should be of type InterpolationMode instead of int. "
point number: 3922949
Traceback (most recent call last):
  File "run.py", line 19, in <module>
    depth_priors.train(args)
  File "/home/xxx/code/NerfingMVS/src/depth_priors.py", line 70, in train
    args.depth_H, args.depth_W)
  File "/home/xxx/code/NerfingMVS/utils/io_utils.py", line 27, in load_colmap
    ply_masks = read_ply_mask(ply_path)
  File "/home/xxx/code/NerfingMVS/utils/colmap_utils.py", line 52, in read_ply_mask
    load_point_vis(ply_vis_path, masks)
  File "/home/xxx/code/NerfingMVS/utils/colmap_utils.py", line 36, in load_point_vis
    idx, u, v = struct.unpack('<III', f.read(4 * 3))
struct.error: unpack requires a buffer of 12 bytes

Thank you!

Hi， do you use our version's COLMAP ?  We add sparse depth masks and you will get io errors if you use original COLMAP.

Hi， do you use our version's COLMAP ? We add sparse depth masks and you will get io errors if you use original COLMAP.

I follow the Installation part and the Usage part in the README.md. I think I did use your version's COLMAP. But I still get this problem.
Also, I am looking for some PYTHON packages to visualize the .ply file. Could give me some advices? Thank you!

What data did you use ? Your own data or the provided ScanNet datasets ?
As for the visualization, I usually use MeshLab. For python package, you can try mayavi or open3d.

What data did you use ? Your own data or the provided ScanNet datasets ?
As for the visualization, I usually use MeshLab. For python package, you can try mayavi or open3d.

The data is ScanNet datasets.

Does colmap/src/mvs/fusion.cc have the above code ?

Does colmap/src/mvs/fusion.cc have the above code ?

Yes, colmap/src/mvs/fusion.cc have the above code. I am trying to  run this code in another 1080ti ubuntu device. But this should not the problem of the device.

Does colmap/src/mvs/fusion.cc have the above code ?

Sorry, It's my fault. I solve this problem by check the above code and have another try. Thank you for your patient and kindness. Maybe you could make the step of installing COLMAP more clear. An official installation of COLMAP may make the COLMAP folder been covered.

OK, I will polish README. Thanks for your suggestion.

Does colmap/src/mvs/fusion.cc have the above code ?

Sorry, It's my fault. I solve this problem by check the above code and have another try. Thank you for your patient and kindness. Maybe you could make the step of installing COLMAP more clear. An official installation of COLMAP may make the COLMAP folder been covered.

Can you show your full fusion.cc?

OK, I will polish README. Thanks for your suggestion.

Dear Authors,
During the installation of Colmap:
When I am running "cmake .. -GNinja"  then it asks to set CUDA_ARCHITECTURES then I set it to "set(CMAKE_CUDA_ARCHITECTURES '70')" and installation was successfully done.
But when I am running the demo code for one of the scenes given by you. Then it showed this error

Ten, according to #2, I changed the code of fusion.cc to the given below

But after that also the error is not fixed, and the same error is showing.

can you clarify the fusion.cc needs to be changed before installation of "ninja" or after ninja installation?
and what should be the CMAKE_CUDA_ARCHITECTURES = '', is it '70', 'native', 'all-range' or something else?
When should be changed to work the code properly?
Thanks!


No Pokemon being released

Hi all,
I have a config file I believe is set to just release everything below 600 cp or 0.8 IV, but it isn't working:
{
    "auth_service": "google",
    "username": "~",
    "password": "~",
    "location": "~",
    "gmapkey": "~",
    "max_steps": 50,
    "catch_pokemon": true,
    "spin_forts": true,
    "walk": 4.16,
    "debug": false,
    "test": false,
    "initial_transfer": false,
    "location_cache": true,
    "distance_unit": "km",
    "reconnecting_timeout": 15,
    "item_filter": {
      "1": { "keep" : 100 },
      "101": { "keep" : 10 },
      "102": { "keep" : 30 },
      "103": { "keep" : 30 },
      "201": { "keep" : 30 },
      "701": { "keep" : 100 }
    },
    "evolve_all": false,
    "evolve_speed": 20,
    "cp_min": 600,
    "use_lucky_egg": false,
    "evolve_captured": false,
    "catch": {
      "any": {"catch_above_cp": 0, "catch_above_iv": 0, "logic": "or"},
      "// Example of always catching Rattata:": {},
      "// Rattata": { "always_catch" : true }
    },
    "release": {
      "any": {"release_below_cp": 600, "release_below_iv": 0.8, "logic": "or" }
    }
}
Can anyone shed some light?
Thanks

Might have to add this one:
"release_pokemon": true,

This is a duplicate of #1624

@mrseeker 's reply seems to have fixed it for me:
run-0 Releasing Pidgey with CP 59 and IV 0.49. Matching release rule: CP < 600 OR IV < 0.8.
run-0 Exchanging Pidgey [CP 59] [Potential 0.49] for candy!
Although it doesn't seem to happen when you would expect it to. I would expect any Pokemon that is caught to then be checked rather than being periodically checked?

Duplicate of https://github.com/PokemonGoF/PokemonGo-Bot/issues/1624
/closed


Translate types of the Gospelstdlib

Add a tystdlib to the Context, similar to the stdlib but for types
Use tystdlib in Ocaml_of_gospel functions translating types
Adapt QCheck-STM to feed the context to those translation functions
Add a new test for QCheck-STM using the sequence type for the model
Closes #155

Thank you! I agree with the proposed improvement, and even dropped the fold_X_namespace specialized functions altogether.


Integration Test Nginx Ingress Repair

This items is to document work completed to repair graphql services used with integration tests.
At the moment, the ingress API previously used has been deprecated and no longer functions.
Background:
In July 2021, Kubernetes announced a deprecation of a series of APIs relating to ingress creation specifically:

All beta Ingress APIs (the extensions/v1beta1 and networking.k8s.io/v1beta1 API versions)

The impact of this change is:

On any cluster running Kubernetes v1.19 or later, you can use the v1 API to retrieve or update existing Ingress objects, even if they were created using an older API version.

When you convert an Ingress to the v1 API, you should review each rule in that Ingress. Older Ingresses use the legacy ImplementationSpecific path type. Instead of ImplementationSpecific, switch path matching to either Prefix or Exact. One of the benefits of moving to these alternative path types is that it becomes easier to migrate between different Ingress classes.

Original Link:
https://kubernetes.io/blog/2021/07/14/upcoming-changes-in-kubernetes-1-22/#what-to-do
O(1) Implementation details
Integration tests running in CI rely on GraphQL interactions for orchestration. The infra underneath this works in 2 parts:

Kubernetes Ingress Controller (exposed external) <--- BROKEN PART
Kubernetes Ingress Interfaces (internal to Kubernetes cluster)

When an integration test runs, it spins up a testnet within Google Cloud. This testnet is not exposed externally (internal only), all requests for orchestration to graphql interfaces must therefore pass through a Kubernetes Ingress Controller that is a permanent installation in the GCloud environment and front-ended by the AWS Route 53 DNS entry *.graphql.test.o1test.net (currently pointed to the Kubernetes Ingress Controller IP: <IP_ADDRESS>)
The Kubernetes Ingress Controller itself is an Nginx container that is configured with a path rewriting rule that accepts a wildcard definition. At O(1), the wildcard definition is set to match names in the specific format used for integration tests. An example can be found in the Nginx documentation for rewriting targets here: https://github.com/kubernetes/ingress-nginx/blob/main/docs/examples/rewrite/README.md#rewrite-target
^^^^^
This behavior of path matching is the functionality that was deprecated - causing the failure.
The Fix
The fix required a redeployment of the Kubernetes Ingress Controller that was being used for external graphql requests. A newer container image, with an updated configuration of path matching that is compatible with the latest versions of Kubernetes.
Specifically a new helm deployment of chart version 4.5.2 was deployed to the graphql-ingress namespace, with all default chart values. The ingress-nginx docs suggest that this is the most up to date chart version that is compatible with kubernetes 1.23 which the cluster currently runs. This should provide at least 4 kubernetes version updates worth of support as-is. We also cleaned up the route53 dns zone that we are using for this test infrastructure, and moved *.graphql.o1test.net to the new IP.
The old ingress controller (called ingress-nginx in the default namespace) will be torn down early next week once we have sufficiently proven the correctness of the new configuration.
Linked PRs are pending...

great write up, thank you steven!

pr: https://github.com/MinaProtocol/mina/pull/13276


predict doesn't correspond to predictProbability in SVC

Reported in #218
For some dataset, predict() function doesn't return a label of the highest probability from predictProbability().

Thanks to point out this. I run libsvm directly and got same results with PHP-ML.

I see. It's weird to me that the probabilities are only an estimate and shouldn't be used in the final prediction, but thanks for the link to the libsvm. It'll help me understand it better.


validation_ratio or validation_set_ratio

Docs mention https://ydf.readthedocs.io/en/latest/guide_how_to_improve_model/#other-impactful-hyper-parameters-for-gbt validation_set_ratio, but I think the actual parameter is validation_ratio

Thank you for reporting, I'll fix this :)
(fun coincidence - someone else reported the same issue yesterday evening on a different channel)


Trigger's DLQ dispatcher acknowledges messages even if dead letter sink is not reachable

Describe the bug
Hello! First of all, thanks for your job creating eventing-rabbitmq.
I was creating a simple producer-consumer example in Knative using RabbitMQ. I am using a trigger to deliver messages from a broker into my consumer service, and I also configured a dead-letter sink service to handle failures. However, if both services are unresponsive (e.g. if routes are offline or if services were undeployed), messages are acklowledged by the DLQ dispatcher instead of being kept in the DLQ.
Expected behavior
If the sink address is not reachable, messages should remain in the dead-letter queue.
To Reproduce
You need to define a trigger with both subscriber and delivery services configured. This example should suffice:
apiVersion: eventing.knative.dev/v1
kind: Trigger
metadata:
  name: consumer-trigger
  namespace: spike
spec:
  broker: rabbitmq-broker
  subscriber:
    ref:
      apiVersion: serving.knative.dev/v1
      kind: Service
      name: consumer
      namespace: spike
  delivery:
    deadLetterSink:
      ref:
        apiVersion: serving.knative.dev/v1
        kind: Service
        name: sink
        namespace: spike
    # 1s delay between retries
    backoffDelay: PT1S
    backoffPolicy: linear
    retry: 2

Now, you must make those services unreachable. You can mess up with the routes, or in a more drastic way, undeploy them. Naturally, messages will be delivered to the trigger's DLQ, and the dispatcher will try to deliver them to its sink. However, upon erroring, the DLQ dispatcher will simply acknowledge the message and log the error.
You can see the DLQ dispatcher logs using kubectl logs consumer-trigger-dlx-dispatcher-someidentifier -n spike and something like this will be shown:
{"level":"info","ts":"2024-04-18T13:20:52.637Z","logger":"rabbitmq-dispatcher","caller":"dispatcher/main.go:89","msg":"Setting BackoffDelay","commit":"33a01ed-dirty","backoffDelay":1}
{"level":"info","ts":"2024-04-18T13:20:52.800Z","logger":"rabbitmq-dispatcher","caller":"dispatcher/dispatcher.go:96","msg":"rabbitmq receiver started, exit with CTRL+C","commit":"33a01ed-dirty"}
{"level":"info","ts":"2024-04-18T13:20:52.800Z","logger":"rabbitmq-dispatcher","caller":"dispatcher/dispatcher.go:97","msg":"starting to process messages","commit":"33a01ed-dirty","queue":"t.spike.consumer-trigger.dlq.c82a02fa837b3152e139578d80336dc313","workers":50}
{"level":"warn","ts":"2024-04-18T13:33:22.143Z","logger":"rabbitmq-dispatcher","caller":"dispatcher/dispatcher.go:152","msg":"invalid result type, not HTTP Result: Post \"http://sink.spike.svc.cluster.local\": dial tcp: lookup sink.spike.svc.cluster.local on <IP_ADDRESS>:53: no such host","commit":"33a01ed-dirty"}
{"level":"warn","ts":"2024-04-18T13:33:22.144Z","logger":"rabbitmq-dispatcher","caller":"dispatcher/dispatcher.go:288","msg":"failed to deliver to \"http://sink.spike.svc.cluster.local\" {%!s(*amqp091.Channel=&{{0 {0 0}} {0 0} {0 0} {{0 0} 0 0 {{} 0} {{} 0}} 0xc00021c000 0xc0006f6360 0xc0006f46c0 1 0 false [0xc0006f6540 0xc00010cd20] [] [] [] 0xc0006f21e0 true 0xc00013c7e0 0xe682c0 0xc000370120 0xc0000e21c0 [123 34 115 112 101 99 118 101 114 115 105 111 110 34 58 34 49 46 48 34 44 34 105 100 34 58 34 54 50 54 97 51 99 53 101 45 49 51 51 48 45 52 101 57 49 45 98 98 57 99 45 50 55 48 51 51 52 57 51 49 48 102 98 34 44 34 115 111 117 114 99 101 34 58 34 107 110 97 116 105 118 101 47 101 118 101 110 116 105 110 103 47 112 114 111 100 117 99 101 114 47 101 118 101 110 116 34 44 34 116 121 112 101 34 58 34 100 101 118 46 107 110 97 116 105 118 101 46 112 114 111 100 117 99 101 114 46 101 118 101 110 116 34 44 34 100 97 116 97 99 111 110 116 101 110 116 116 121 112 101 34 58 34 97 112 112 108 105 99 97 116 105 111 110 47 106 115 111 110 34 44 34 100 97 116 97 34 58 123 34 72 101 108 108 111 34 58 34 119 111 114 108 100 33 34 125 125]}) map[content-type:application/json id:936b10cf-529b-4a46-a5fe-8c63860501ed knativeerrorcode:%!s(int32=-1) knativeerrordest:http://consumer.spike.svc.cluster.local source:/apis/v1/namespaces/spike/rabbitmqsources/rabbitmq-source#source-queue specversion:1.0 subject:936b10cf-529b-4a46-a5fe-8c63860501ed time:2024-04-18T13:33:15.109959419Z traceparent:00-c8bb10f7310f95e5b9476c060c7898cf-f2c2a49b335ecb70-00 tracestate: type:dev.knative.rabbitmq.event] application/json  %!s(uint8=2) %!s(uint8=0)    936b10cf-529b-4a46-a5fe-8c63860501ed 0001-01-01 00:00:00 +0000 UTC    ctag-/ko-app/dispatcher-1 %!s(uint32=0) %!s(uint64=1) %!s(bool=false) t.spike.consumer-trigger.dlx.88892693432310cd99264ac5b7100d9a13  {\"specversion\":\"1.0\",\"id\":\"626a3c5e-1330-4e91-bb9c-2703349310fb\",\"source\":\"knative/eventing/producer/event\",\"type\":\"dev.knative.producer.event\",\"datacontenttype\":\"application/json\",\"data\":{\"Hello\":\"world!\"}}}","commit":"33a01ed-dirty"}

Which abled me to trace down this behavior for this excerpt: https://github.com/knative-extensions/eventing-rabbitmq/blob/knative-v1.13.0/pkg/dispatcher/dispatcher.go#L287-L292
Knative release version
Knative serving/eventing version: 1.12.0
Eventing RabbitMQ version: 1.13.0
Additional context
If this a known behavior, maybe we could update documentation at least before addressing such problem.

Hi, thanks for the report.
I think the same situation in the case of dead lettering via rabbit itself. This failure modes are not atomic unfortunately. Please tell me more about your use case.


Why it is so slow on android?

Currently, it takes about 5 minutes each time I pull or push anything on my Android phone whereas it only takes 30s on my Laptop with the same network.
I wonder why there is such a big difference.

I'm using the native system-wide installed git on Desktop, but on mobile I'm using a reimplementation of Git in javascript as stated in the README#mobile. It's way slower, but there's nothing I can do.

Ok, I got it.
Many thanks.

Ok, I got it.
Next time I will read the readme carefully before asking
Many thanks


Add last name to Written by on Articles

Done
https://github.com/fathomlondon/fathomlondon.github.io/pull/133


Jpeg output pixel aspect ratio X_density Y_density swapped

Problem
When using PixelAspectRatio in jpegoutput, it seems that X_density and Y_density are swapped
I think that formula is:
PAR = X/Y. So if we set Y to a constant C, we have:

Y = C
X = C*PAR

Is it correct for you ?
Thanks
Solution proposed
PR #1412
Versions

OIIO branch/version: master

Fixed by #1412

By the way, it is not necessary to file both a PR and an Issue. The PR can describe the problem and proposed code for solution. Issues are great when nobody has a solution yet, they remind us of an outstanding problem. But if a solution is implemented, separately filing an "issue" is just extra work with no benefit.

You're right. At the beginning I had no solution to PR. Sorry for that.

No prob, I'm just trying to save you trouble! The issue and the PR were just one number apart, so it certainly seemed as if they were filed simultaneously, or nearly so. I just wanted to make sure you knew that there's no rule that says everything needs an issue.
(Aside: I wish it was possible to fully "upgrade" an existing issue with a PR, and not have them be separate at all, ever. It seems to just be a hassle to tie an issue and PR together, spreads out the discussion unnecessarily.)


occurance

finally might be a good time to address this one ... after almost 10 years ...
https://forums.parallax.com/discussion/126031/occurance-occurrence-occurence/p1
cheers,

Thanks @c0ded0g!
Yes indeed, that one has been there a long time and I never knew about it.

Fixed.  Will be released in Alpha 4.
There were 12 occurrences of 'occurances' in the source: in comments, enumerations, and hints.


pyproj datum self tests fail without PROJ_NETWORK=ON on openSUSE Tumbleweed

I'm packaging pyproj v3.0.0 for openSUSE and since the Proj upgrade to v7.2, I'm facing a lot of test failures. With some of them I'm able to decide about the severity but for the datum tests, I'm unable to decide what is the correct output and how severe are coordinate deviations reported by the test. This is why I'm reaching out for help here.
Datum tests fail when I build pyproj from source. The same happens in the build system. In addition, in the build system there is no access to the Internet so grid data download is not possible.
lpechacek@fmn:/data/src/pyproj/build/lib.linux-x86_64-3.8> proj
Rel. 7.2.1, January 1st, 2021
usage: proj [-bdeEfiIlmorsStTvVwW [args]] [+opt[=arg] ...] [file ...]
lpechacek@fmn:/data/src/pyproj/build/lib.linux-x86_64-3.8> git describe --tags
3.0.0.post1-19-g552edb3613e4
lpechacek@fmn:/data/src/pyproj/build/lib.linux-x86_64-3.8> pytest-3.8 test/test_datum.py
============================= test session starts ==============================
platform linux -- Python 3.8.6, pytest-6.1.2, py-1.9.0, pluggy-0.13.1
rootdir: /data/src/pyproj, configfile: pytest.ini
collected 2 items

test/test_datum.py FF                                                    [100%]

=================================== FAILURES ===================================
_______________________________ test_datum[Proj] _______________________________

proj_class = <class 'pyproj.proj.Proj'>

    @pytest.mark.grid
    @pytest.mark.parametrize("proj_class", [Proj, CRS])
    def test_datum(proj_class):
        p1 = proj_class(proj="latlong", datum="WGS84")
        s_1 = -111.5
        s_2 = 45.25919444444
        p2 = proj_class(proj="utm", zone=10, datum="NAD27")
        with pytest.warns(DeprecationWarning):
            x2, y2 = transform(p1, p2, s_1, s_2)
        if grids_available("us_noaa_emhpgn.tif"):
            assert_almost_equal((x2, y2), (1402286.33, 5076292.30), decimal=2)
        elif grids_available("us_noaa_conus.tif"):
            assert_almost_equal((x2, y2), (1402285.98, 5076292.42), decimal=2)
        else:
            # https://github.com/OSGeo/PROJ/issues/1808
>           assert_almost_equal((x2, y2), (1402288.54, 5076296.64), decimal=2)
E           AssertionError:
E           Arrays are not almost equal to 2 decimals
E
E           Mismatched elements: 2 / 2 (100%)
E           Max absolute difference: 4.2187254
E           Max relative difference: 1.82350118e-06
E            x: array([1402285.98, 5076292.42])
E            y: array([1402288.54, 5076296.64])

test/test_datum.py:23: AssertionError
_______________________________ test_datum[CRS] ________________________________

proj_class = <class 'pyproj.crs.crs.CRS'>

    @pytest.mark.grid
    @pytest.mark.parametrize("proj_class", [Proj, CRS])
    def test_datum(proj_class):
        p1 = proj_class(proj="latlong", datum="WGS84")
        s_1 = -111.5
        s_2 = 45.25919444444
        p2 = proj_class(proj="utm", zone=10, datum="NAD27")
        with pytest.warns(DeprecationWarning):
            x2, y2 = transform(p1, p2, s_1, s_2)
        if grids_available("us_noaa_emhpgn.tif"):
            assert_almost_equal((x2, y2), (1402286.33, 5076292.30), decimal=2)
        elif grids_available("us_noaa_conus.tif"):
            assert_almost_equal((x2, y2), (1402285.98, 5076292.42), decimal=2)
        else:
            # https://github.com/OSGeo/PROJ/issues/1808
>           assert_almost_equal((x2, y2), (1402288.54, 5076296.64), decimal=2)
E           AssertionError:
E           Arrays are not almost equal to 2 decimals
E
E           Mismatched elements: 2 / 2 (100%)
E           Max absolute difference: 4.2187254
E           Max relative difference: 1.82350118e-06
E            x: array([1402285.98, 5076292.42])
E            y: array([1402288.54, 5076296.64])

test/test_datum.py:23: AssertionError
=========================== short test summary info ============================
FAILED test/test_datum.py::test_datum[Proj] - AssertionError:
FAILED test/test_datum.py::test_datum[CRS] - AssertionError:
============================== 2 failed in 0.73s ===============================
lpechacek@fmn:/data/src/pyproj/build/lib.linux-x86_64-3.8>

Crawling through the code, I noticed that grids_available() tests for the content of PROJ_NETWORK environment variable. Blindly setting PROJ_NETWORK=ON before the test makes the datum test pass.
lpechacek@fmn:/data/src/pyproj/build/lib.linux-x86_64-3.8> PROJ_NETWORK=ON pytest-3.8 test/test_datum.py
============================= test session starts ==============================
platform linux -- Python 3.8.6, pytest-6.1.2, py-1.9.0, pluggy-0.13.1
rootdir: /data/src/pyproj, configfile: pytest.ini
collected 2 items

test/test_datum.py ..                                                    [100%]

============================== 2 passed in 1.06s ===============================

At this point I'm seeking for a recommendation how to run pyproj tests in the confined build environment where thers is no access to external resources. Thanks!

The tests require using the .tif grids. If you are using the old grids, the tests fail. Can you confirm what type of grids are on your system?

The tests require using the .tif grids. If you are using the old grids, the tests fail. Can you confirm what type of grids are on your system?

See: https://github.com/pyproj4/pyproj/issues/734

See: https://github.com/pyproj4/pyproj/issues/734

The tests require using the .tif grids. If you are using the old grids, the tests fail. Can you confirm what type of grids are on your system?

Thanks for this valuable clue, Alan. As far as I can see, the openSUSE PROJ comes with proj-datumgrid-1.8.zip. I can see at PROJ website that this data package is deprecated and we should use proj-data with PROJ >= v7. I'll have a closer look.

The tests require using the .tif grids. If you are using the old grids, the tests fail. Can you confirm what type of grids are on your system?

Thanks for this valuable clue, Alan. As far as I can see, the openSUSE PROJ comes with proj-datumgrid-1.8.zip. I can see at PROJ website that this data package is deprecated and we should use proj-data with PROJ >= v7. I'll have a closer look.

So, the issue is solved! After removing the proj-datumgrid data files from PROJ package, the self-tests pass.
Out of curiosity, I checked also Debian Sid. The datum self-tests fail in the same way I see with openSUSE. @sebastic might be interested in this ticket as well.
Thanks, Alan, for your help here! For a long time, I was clueless about where to search for the culprit.

So, the issue is solved! After removing the proj-datumgrid data files from PROJ package, the self-tests pass.
Out of curiosity, I checked also Debian Sid. The datum self-tests fail in the same way I see with openSUSE. @sebastic might be interested in this ticket as well.
Thanks, Alan, for your help here! For a long time, I was clueless about where to search for the culprit.


Does OpenSpiel support Pursuit-Evasion and HUNL Subgames

Hi,
I'm currently working on a new algorithm for solving EFGs and would like to test it on some specific games. Does OpenSpiel support:

Pursuit-Evasion games?
HUNL (Heads-Up No-Limit) poker subgames?

It would be great if anyone could confirm or point me to any relevant resources/examples.
Thanks!

Unfortunately OpenSpiel does not have any pursuit-evasion games in the suite. Which ones did you have in mind? Are there any standard ones from the literature that would be good to adopt? We can maybe add it to our wish list.
HUNL subgames, I believe, should be possible from the universal_poker but I'm not entirely sure how. I'll tag a few experts to help clarify that.

Ok there are some HUNL subgames in this file:
https://github.com/google-deepmind/open_spiel/blob/f68f2a388a8bf41181b3a323f65fd2d3414ebb63/open_spiel/games/universal_poker/universal_poker_test.cc#L839
I believe @michalsustr added them originally. @Drazcmd recently did some bug fixing and maintenance work in this game, he may also know. Going to tag @jhtschultz and @VitamintK  as well, and see also this Atan03 from this thread who had a similar question: https://github.com/google-deepmind/open_spiel/issues/1168)

Thank you very much for your response. I have already contacted the person you mentioned via email.


How to generate same identity faces after each run?

Hi,
When I run the generator.jar, it will generate faces with different identities after each run. How can I fix the random see to reproduce the results? i.e., for each run of generator, the identities of the generated faces are fixed. Thanks!

Hi,
there is a random seed for all parameters that are sampled. If you run the program twice with the exact same setting it will generate the exact same dataset..
There is no seperate seed for the identity and therefore if you change other settings (like the number of samples per id) the ids will change.
There is however a branch fixID that allows to load an  id (load an rps file) and generate new samples for this id in a new folder (fixedId).
https://github.com/BernhardEgger/parametric-face-image-generator/commit/d5b46a25f12bc6aec80657afca9b74591b5d4184
If you checkout that branch and compile it you can generate new samples per id.
Best
Bernhard


Cask cleanup command misplaced result

Running brew cask cleanup results in the following result.
==> Removing dead symlinks
/Library/Caches/Homebrew/Casks/hr-0.3.6.zip
==> Removing cached downloads
Nothing to do

I think the part about hr zip should be under "Removing cached downloads".

If you want to submit a PR to make the documentation clearer, @ngocphamm, we can review it. This isn’t a common complaint, though (don’t remember ever seeing it repeated).


Kotlin Multiplatform

Description
Migrate the project to a multiplatform library targetting the JVM and JS runtimes.
Checklist

[ ] Implement.
[ ] Test.
[ ] Refactor.
[ ] Update Work in progress section in changelog.

Moved here.


README for stepper

Created a readme for stepper component.
Please review.

Get a manual approve from Leo & Volodymir.


fix: Add step for updating submodule to running instruction

Thanks :) There isn't much here, though, I don't think there's much you can use!

@darobin not yet, but https://github.com/darobin/polypod/blob/main/lib/fs-blockstore.js was at least helpful as a reference


IEEE754 Converter

Enter calculator name -
IEEE Standard 754 Floating Point Converter
Describe calculator functionality -
Input a number in decimal system and get the IEEE 754 Standard Single precision representation of the number in both 32bit and 64bit
Under which category you wish to place it -

[x] Computer Science
[ ] Mathematics
[ ] Physics
[ ] Chemistry
[ ] Biology
[ ] Art
[ ] Finance
[ ] Scientific
[ ] Health
[ ] Sports
[x] Let project owner decide
[ ] Suggest a new category - (Answer here)

@SarthakKeshari I want to add this calculator. Kindly assign this issue to me

Hey @XronTrix10,
Assigned.
You may contribute your code under the folder path -
calc_for_everything\calculators\src\computer_science\iEEE754Converter
Issue completion deadline - 18th Oct 11:00:00 am IST
NOTE - In case the issue completion deadline is not met, the issue will be assigned to a new participant

assign this to me


When uart cable is disconnected previous values are kept and not set to null

When the uart cable to the BMS is disconnected for whatever reason the previous values are kept. This can lead to issue not discovered for a long time until it is too late.
I suggest either setting the values to null when there is no response from the BMS or have a last updated variable that you can track to see when last the value was updated. Both options might also be option.

Good point! I will implement the first suggestion. The second is already available if you use Home Assistant or another Home Automation which keeps track of the latest update per sensor.

There is a new binary sensor called online_status now:
binary_sensor:
  - platform: jk_bms
    online_status:
      name: "${name} online status"

If the BMS doesn't respond (on 5 consecutive updates/requests) all sensor values are changed to Unknown (NaN), the online_status resports Disconnected (false) and the text sensor errors will show Offline.

Great thanks I will recompile and test this.

I'm implementing a pretty similar setup here: https://github.com/syssi/esphome-virtual-can-bms
Could you share some details about your inverter (model) and the canbus id / registers you are pushing to the inverter via canbus?

I'm implementing a pretty similar setup here: https://github.com/syssi/esphome-virtual-can-bms
Could you share some details about your inverter (model) and the canbus id / registers you are pushing to the inverter via canbus?

Hi sorry missed this message. The 1st integration I am testing is with a Voltronix Axpert King II using the Soltaro CAN Protocol. I will soon start also to test with a Sunsynk/Deye Inverter using the Pylontech CAN protocol.
Below is the can bus specific config I am busy using - reworked some of the config from https://github.com/Uksa007/esphome-jk-bms-can to work with Soltaro protocol supported by the Axpert inverter.
`spi:
id: McpSpi
clk_pin: ${spican_clk_pin}
mosi_pin: ${spican_mosi_pin}
miso_pin: ${spican_miso_pin}
canbus:

platform: mcp2515
spi_id: McpSpi
cs_pin: ${spican_cs_pin}
#mode: LOOPBACK
#clock: 8MHZ
can_id: 4
bit_rate: 500kbps
on_frame:

can_id: 0x305
then:

lambda: |-
std::string b(x.begin(), x.end());
ESP_LOGI("main", "received can id: 0x305 ascii: %s", &b[0] );
id(can_305_rx) = 0;
interval:

interval: 1000ms
then:

if:
condition:
- binary_sensor.is_on: online_status
then:

canbus.send: # BMS instructs inverter: Charge Volts, Charge Amps, Discharge Amps, Min voltage
use_extended_id: True
can_id: 0x1872
data: !lambda |-
uint8_t can_mesg[7];
if (((!id(charging).state) | (!id(inverter_charging).state)) & (id(charge_status) != "Disabled")) {
id(charge_status) = "Disabled";
id(can_disable_charge_script).execute();
} else if (id(inverter_chg_on).state) {
id(charge_status) = "Bulk Manually";
} else if ((id(charging).state) & (id(inverter_charging).state) & (id(charge_status) == "Disabled")) {
id(charge_status) = "Wait";
id(can_enable_charge_script).execute();
} else if ((!id(inverter_chg_on).state) & (id(charge_status) == "Bulk Manually")) {
id(charge_status) = "Wait";
} else if (id(total_voltage).state <= (id(charging_voltage).state - ${rebulk_offset})) { ///Bulk Charge eg 53.6v 10%
if (id(absorption_script).is_running()) id(absorption_script).stop();
id(charge_status) = "Bulk";
} else if ((id(total_voltage).state > (id(charging_voltage).state - ${rebulk_offset})) & (id(total_voltage).state < (id(charging_voltage).state - 0.05))) { ///If in startup rebulk
if (id(charge_status) == "Startup") {
id(charge_status) = "Bulk"; /// If in startup, 10% low rebulk
}
} else if (id(total_voltage).state >= (id(charging_voltage).state  - 0.05)) { ///10 % from top start absorption timer
if (id(charge_status) == "Bulk") {
id(charge_status) = "Absorption";
if (!id(absorption_script).is_running()) id(absorption_script).execute();
}
} else {
id(charge_status) = "Wait";
}
if ((id(charge_status) == "Bulk") | (id(charge_status) == "Absorption") | (id(inverter_chg_on).state)) {
can_mesg[0] = uint16_t(id(charging_voltage).state * 10) & 0xff;
can_mesg[1] = uint16_t(id(charging_voltage).state * 10) >> 8 & 0xff;
can_mesg[4] = uint16_t(id(charging_current).state * 10) & 0xff;
can_mesg[5] = uint16_t(id(charging_current).state * 10) >> 8 & 0xff;
} else {
can_mesg[0] = 0;
can_mesg[1] = 0;
can_mesg[4] = 0;
can_mesg[5] = 0;
}
if ((!id(charging).state) | (!id(inverter_charging).state)) { /// Overides to disable charging
can_mesg[0] = 0;
can_mesg[1] = 0;
can_mesg[4] = 0;
can_mesg[5] = 0;
}
if ((id(discharging).state) & (id(inverter_discharging).state)) {
can_mesg[6] = uint16_t(${discharge_a} * 10) & 0xff;
can_mesg[7] = uint16_t(${discharge_a} * 10) >> 8 & 0xff;
} else {
can_mesg[6] = 0x00;
can_mesg[7] = 0x00;
}
can_mesg[2] = uint16_t(${min_dischange_v} * 10) & 0xff;
can_mesg[3] = uint16_t(${min_dischange_v} * 10) >> 8 & 0xff;
id(charging_status).publish_state(id(charge_status));
ESP_LOGD("main", "send can id: 0x1872 hex: %x %x %x %x %x %x %x %x", can_mesg[0], can_mesg[1], can_mesg[2], can_mesg[3], can_mesg[4], can_mesg[5], can_mesg[6], can_mesg[7]);
ESP_LOGI("main", "send can id: Charge Status %s", id(charge_status).c_str());
return {can_mesg[0], can_mesg[1], can_mesg[2], can_mesg[3], can_mesg[4], can_mesg[5], can_mesg[6], can_mesg[7]};
delay: 10ms

if:
condition:
- binary_sensor.is_on: online_status
then:
- canbus.send: # Actual Volts, Capacity
use_extended_id: True
can_id: 0x1874
data: !lambda |-
uint8_t can_mesg[7];
can_mesg[0] = uint16_t(id(total_voltage).state * 10) & 0xff;
can_mesg[1] = uint16_t(id(total_voltage).state * 10) >> 8 & 0xff;
can_mesg[2] = int16_t(${absorption_v} * 10) & 0xff;
can_mesg[3] = int16_t(${absorption_v} * 10) >> 8 & 0xff;
can_mesg[4] = int16_t(id(capacity_remaining).state) & 0xff;
can_mesg[5] = 0x00;
can_mesg[6] = 0x00;
can_mesg[7] = 0x01;
ESP_LOGD("main", "end can id: 0x1874 hex: %x %x %x %x %x %x %x %x", can_mesg[0], can_mesg[1], can_mesg[2], can_mesg[3], can_mesg[4], can_mesg[5], can_mesg[6], can_mesg[7]);
return {can_mesg[0], can_mesg[1], can_mesg[2], can_mesg[3], can_mesg[4], can_mesg[5], can_mesg[6], can_mesg[7]};
- delay: 10ms

script:

id: absorption_script
then:

lambda: id(charge_status) = "Absorption";
delay: ${absorption_time}min
lambda: id(charge_status) = "Wait";

id: can_disable_charge_script
then:

canbus.send: # Disable Charging
use_extended_id: True
can_id: 0x1876
data: !lambda |-
uint8_t can_mesg[7];
can_mesg[0] = 0x01;
can_mesg[1] = 0x00;
can_mesg[2] = 0x00;
can_mesg[3] = 0x00;
can_mesg[4] = 0x00;
can_mesg[5] = 0x00;
can_mesg[6] = 0x00;
can_mesg[7] = 0x00;
ESP_LOGI("main", "end can id: 0x1876 hex: %x %x %x %x %x %x %x %x", can_mesg[0], can_mesg[1], can_mesg[2], can_mesg[3], can_mesg[4], can_mesg[5], can_mesg[6], can_mesg[7]);
return {can_mesg[0], can_mesg[1], can_mesg[2], can_mesg[3], can_mesg[4], can_mesg[5], can_mesg[6], can_mesg[7]};
delay: 10ms
canbus.send: # Heartbeat 1
use_extended_id: True
can_id: 0x187b
data: !lambda |-
uint8_t can_mesg[7];
can_mesg[0] = 0x00;
can_mesg[1] = 0x00;
can_mesg[2] = 0x00;
can_mesg[3] = 0x00;
can_mesg[4] = 0x00;
can_mesg[5] = 0x00;
can_mesg[6] = 0x00;
can_mesg[7] = 0x00;
ESP_LOGI("main", "end can id: 0x187b hex: %x %x %x %x %x %x %x %x", can_mesg[0], can_mesg[1], can_mesg[2], can_mesg[3], can_mesg[4], can_mesg[5], can_mesg[6], can_mesg[7]);
return {can_mesg[0], can_mesg[1], can_mesg[2], can_mesg[3], can_mesg[4], can_mesg[5], can_mesg[6], can_mesg[7]};
delay: 10ms

id: can_enable_charge_script
then:

canbus.send: # Enable Charging
use_extended_id: True
can_id: 0x1876
data: !lambda |-
uint8_t can_mesg[7];
can_mesg[0] = 0x00;
can_mesg[1] = 0x00;
can_mesg[2] = 0x00;
can_mesg[3] = 0x00;
can_mesg[4] = 0x00;
can_mesg[5] = 0x00;
can_mesg[6] = 0x00;
can_mesg[7] = 0x00;
ESP_LOGI("main", "end can id: 0x1876 hex: %x %x %x %x %x %x %x %x", can_mesg[0], can_mesg[1], can_mesg[2], can_mesg[3], can_mesg[4], can_mesg[5], can_mesg[6], can_mesg[7]);
return {can_mesg[0], can_mesg[1], can_mesg[2], can_mesg[3], can_mesg[4], can_mesg[5], can_mesg[6], can_mesg[7]};
delay: 10ms
canbus.send: # Heartbeat 1
use_extended_id: True
can_id: 0x187b
data: !lambda |-
uint8_t can_mesg[7];
can_mesg[0] = 0x00;
can_mesg[1] = 0x00;
can_mesg[2] = 0x00;
can_mesg[3] = 0x00;
can_mesg[4] = 0x00;
can_mesg[5] = 0x00;
can_mesg[6] = 0x00;
can_mesg[7] = 0x00;
ESP_LOGI("main", "end can id: 0x187b hex: %x %x %x %x %x %x %x %x", can_mesg[0], can_mesg[1], can_mesg[2], can_mesg[3], can_mesg[4], can_mesg[5], can_mesg[6], can_mesg[7]);
return {can_mesg[0], can_mesg[1], can_mesg[2], can_mesg[3], can_mesg[4], can_mesg[5], can_mesg[6], can_mesg[7]};
delay: 10ms`


Add Doc VSCode Compatibility

remove warning message from VScode when using CI4Adapter
Reason
When I use VSCode and apply the library for Codeigniter 4, there's a warning message in VSCode like the screenshot below. This message doesn't cause errors, but it's quite annoying for some people because of the warning message.

Additional
I only added for Codeigniter4Adapter, but I haven't tried how other adapters might also trigger warning messages.

what about removing type completely
    /**
     * @param $query
     * @return Datatables
     */
    public function query($query): Datatables

or using mixed
    /**
     * @param string|mixed $query
     * @return Datatables
     */
    public function query($query): Datatables


Make the income system able to apply to unit

Want to give 2 units a passive that reduce your income slightly!

The relevant class here is ProvidesIncome.cs. Right now it will only work for structures (I think). Allow it to work for trained units too.

Closed by https://github.com/AzerothWarsLR/WarcraftLegacies/commit/1d4bfb0925d0997fd24b02fa289ebe63a18acc8e. @SebastianTanoni you should be able to configure the units you wanted.

To-do: configuire the units


Fix: ActivityPub type property does not set correctly on actor classes

Fixes that the get_type function is not called for extended classes, when the property is already set.
There would have been two straight-forward solutions:

the proposed one
setprotected $type = '...' in all extended classes of Actor and remove the get_type functions.

I guess a test-case for this might be of good use. I will gladly add one if agreed.

Welcome back @Menrath :)
Should we remove the default type or better change how the getter will be called?


During reconcile its stuck

During reconcile the data, the page is stuck and its shows ''working'' from yesterday
To Reproduce
Steps to reproduce the behavior:

Go to 'column'
Click on 'reconcile'

Current Results
its shows WORKING only, but its not working actually
Expected behavior

Screenshots

Desktop:

OS: Windows 10
Browser Version: Google Crome
JRE or JDK Version:

OpenRefine :

Open refine 3.3

What reconciliation service are you using?
What type within the reconciliation service are you reconciling against?
How many rows/items are in the batch that you are reconciling?
How many hours has it been running?
Are there any errors displayed on either the Javascript console for your web browser or the OpenRefine server console?

I was checking whether the items are present in wikidata or not, then I
will upload the data set to wikidata.
I tried multiple times from yesterday and it shows 'working' ... Indicater
is loading more than 1 hour and nothing happened.
My data set has 3 column and 730 rows
On Wed, Jul 8, 2020, 10:41 Tom Morris<EMAIL_ADDRESS>wrote:

What reconciliation service are you using?
What type within the reconciliation service are you reconciling
against?
How many rows/items are in the batch that you are reconciling?
How many hours has it been running?
Are there any errors displayed on either the Javascript console for
your web browser or the OpenRefine server console?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OpenRefine/OpenRefine/issues/2903#issuecomment-655289163,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHVKFIGAF2IEI5TPGVVIQQDR2P5ZVANCNFSM4OUDH6AA
.

Looking at the screenshot this must be a failure during the "guess types" operation, which sends the first 10 rows to the reconciliation service.

I'm also getting this (while trying to re run steps I have already run to grab screenshots for a blog post).
If this is talking to the openrefine reconciliation service is this to do with the domain name changes there?
Stacktrace included below.
09:48:17.560 [                   refine] POST /command/core/guess-types-of-column (66ms)
com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')
 at [Source: (String)"
<title>308 Permanent Redirect</title>

308 Permanent Redirect

nginx/1.14.2

"; line: 1, column: 2]
        at com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1804)
        at com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:693)
        at com.fasterxml.jackson.core.base.ParserMinimalBase._reportUnexpectedChar(ParserMinimalBase.java:591)
        at com.fasterxml.jackson.core.json.ReaderBasedJsonParser._handleOddValue(ReaderBasedJsonParser.java:1902)
        at com.fasterxml.jackson.core.json.ReaderBasedJsonParser.nextToken(ReaderBasedJsonParser.java:757)
        at com.fasterxml.jackson.databind.ObjectMapper._readTreeAndClose(ObjectMapper.java:4043)
        at com.fasterxml.jackson.databind.ObjectMapper.readTree(ObjectMapper.java:2552)
        at com.google.refine.util.ParsingUtilities.evaluateJsonStringToObjectNode(ParsingUtilities.java:256)
        at com.google.refine.commands.recon.GuessTypesOfColumnCommand.guessTypes(GuessTypesOfColumnCommand.java:202)
        at com.google.refine.commands.recon.GuessTypesOfColumnCommand.doPost(GuessTypesOfColumnCommand.java:110)
        at com.google.refine.RefineServlet.service(RefineServlet.java:189)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
        at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
        at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
        at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
        at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
        at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
        at org.mortbay.jetty.Server.handle(Server.java:326)
        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:938)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
        at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
09:48:17.921 [                  command] Exception caught (361ms)
java.lang.NullPointerException
        at com.google.refine.commands.recon.GuessTypesOfColumnCommand.guessTypes(GuessTypesOfColumnCommand.java:204)
        at com.google.refine.commands.recon.GuessTypesOfColumnCommand.doPost(GuessTypesOfColumnCommand.java:110)
        at com.google.refine.RefineServlet.service(RefineServlet.java:189)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
        at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
        at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
        at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
        at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
        at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
        at org.mortbay.jetty.Server.handle(Server.java:326)
        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:938)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
        at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

Dammit! I checked that reconciliation worked with redirects, but the type guessing command apparently does not. Weird.
You should be able to fix this by removing the Wikidata reconciliation service from the list, and adding it manually, with this endpoint:
https://wdreconcile.toolforge.org/en/api

Postmorted: somehow, HttpURLConnection follows temporary redirects but not permanent ones: only HTTP codes from 300 to 307 are followed, and now the redirection uses HTTP 308.
When I tested whether the code followed redirects, I simulated the new environment by deploying the reconciliation service with the --canonical option, which set up temporary redirects, not permanent ones.
Now that the redirection from tools.wmflabs.org to *.toolforge.org is permanent, we get this limbo.
There are times when I would rather disappear under a rock…

You should be able to fix this by removing the Wikidata reconciliation service from the list, and adding it manually, with this endpoint: https://wdreconcile.toolforge.org/en/api.

I can confirm this works

Upgrading to 3.4-beta2 should also fix the issue.

I can confirm this does not work

Upgrading to 3.4-beta2 should also fix the issue.

I can confirm this does not work

Right, because the new service will only be registered if there is no existing reconciliation service, so 3.4-beta2 only "fixes" the issue if you remove all your reconciliation services after migrating…

I have had this issue for at least a week. I installed a new beta version, tried different datasets. Also "Add column from reconciled values gives an error". Maybe I am late to report, hope you will find the cause!

@susannaanas you should be able to fix this by removing the Wikidata reconciliation service from the list, and adding it manually, with this endpoint: https://wdreconcile.toolforge.org/en/api.
Columns that have been reconciled before the change need to be reconciled again with the new service to use "Add column from reconciled values".

OK thanks! I see you mentioned that before already!

In addition to handling the redirect, the code should also handle a non-JSON response which is the immediate cause of the error (similar to #1128). The changes that I made in #2590 might be able to be adapted. Widening the exception handler to include JsonParseException might do the trick.


fix(documentation): responsive  layout

[x] adjust css
[ ] Add modal to side-drawer in mobile
[ ] Add a button for open - close side-drawer in mobile

I think the main purpose of this PR now is to apply a modal to side drawer on narrow screens. dynamically


do not error test if port forward finished

This scenario occurs during test cleanup - if killing the port-forward process fails because the process is already finished, we can treat this as a non-fatal error.

/assign @karlkfi


pretrained weight mismatch

the download link of ‘jhu weight’ is Gradformer_UCF.pth，and the test results of it on UCF is much better than JHU
the download link of ‘ucf weight' is MS2_UCF.pth， failed to load with different keys

Sorry for uploading the wrong model. It has been corrected.

Got it, thank you for your help and prompt response highly appreciated.
On Wed, Sep 11, 2024 at 12:52 PM Lora @.***> wrote:

Sorry for uploading the wrong model. It has been corrected.
—
Reply to this email directly, view it on GitHub
https://github.com/LoraLinH/Gramformer/issues/3#issuecomment-2342914843,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZWWDUKWM5TEFO7NYTWOFHLZV7ZDLAVCNFSM6AAAAABN6HRQJGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBSHEYTIOBUGM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


[Enhancement] (nereids)implement showDynamicPartitionCommand in nereids

showDynamicPartition command is supported in legacy planner but not in nereids(new doris fe planner). you need implement the following showDynamicPartition command in nereids:
unsupportedshowDynamicPartitionStatement
SHOW DYNAMIC PARTITION TABLES ((FROM | IN) database=multipartIdentifier)?

i will pick it


main: use rule scope internal/limitation/file for file limitations, not code

closes #390

there's a bug in rendering the match: <namespace> features:

reminder: merge https://github.com/fireeye/capa-rules/pull/400 next


Don't load thumbnail image when scrolling the viewer

What
If you scroll the viewer quickly we show a loading icon in place of the images.
As the scrolling slows we load in a thumbnail image (displayed large, so it is pixelated).
When the user stops on an image we load in the full resolution image.

I think the pixelated thumbnail image doesn't really add anything to the experience, but it does add more http requests and data transfer, so we should remove it.
Furthermore, when the screen is wide enough the thumbnail displays larger than the full image, which creates quite a jarring effect when they switch (see below).
I also think showing the loading icon while waiting for the full resolution to load is more indicative of what is happening, than showing a pixelated image.
@DominiqueMarshall @davidpmccormick would be interested to get your thoughts?
Oversized thumbnail:

Yeah, I agree with this, especially if it means less data transfer and requests 👍🏽


Proposal: Add basic Python API

Is the ruff team open to exposing a minimal Python API for interacting with the checker and formatter?
I am looking at integrating Ruff into some code-generation tooling but having to interact with the tool through subprocess and temporary files adds a few footguns.
By exposing ~4 Python functions I think we could cover 90% of the common requirements for Ruff as a library:
def load_config(config: str) -> RuffConfig:
    ...

def format(source: str, config: Optional[RuffConfig] = None) -> str:
    ...

def formatted(source: str, config: Optional[RuffConfig] = None) -> bool:
    ...

def check(source: str, config: Optional[RuffConfig] = None) -> bool:
    ...

These functions all operate on strings rather than files leaving all IO to the wrapping code.
A typical example of using this API might look like:
#...
with open('pyproject.toml', 'r') as f:
    config = load_config(f.read())

formatted_code = ruff.format(some_code_fragment, config)
#...

With these functions available implementing Ruff equivalents of blacken-docs etc would be fairly mechanical.
Any thoughts?

Hey. Yeah, interacting with subprocess is annoying. There are a couple concerns outlined in https://github.com/astral-sh/ruff/issues/659 mainly around the stability concerns and Ruff using stdout in some places instead of structured diagnostics.

Ah, I spent a reasonable amount of time looking for an existing ticket but clearly didn't have the right combo of keywords. Should I close this ticket and reword my use-cases as a comment on #659 ?
In my case I don't really need structured diagnostics for the checker functionality. A simple "good"/"no-good" is plenty.
More important for me is being able to work with strings rather than temporary files.

@sam-bristow You don't need to use temporary files, since ruff supports the UNIX convention of - being a stand-in for stdin.
import json
import subprocess

bad_code = "print   ('hi');"

# Formatter example
formatted = subprocess.check_output(
    ["ruff", "format", "-"], input=bad_code, encoding="utf-8"
)
print(repr(formatted))

# Checker example
proc = subprocess.run(
    ["ruff", "--select=ALL", "--output-format=json", "check", "-"],
    input=bad_code,
    stdout=subprocess.PIPE,
    stderr=subprocess.DEVNULL,
    encoding="utf-8",
)
print(proc.returncode)  # 1 if bad
print(json.loads(proc.stdout))

outputs
'print("hi")\n'
1
[{'cell': None, 'code': 'E902', ...

You can also add --stdin-filename=... if you like.

👍 I'm gonna merge this into #659. Definitely feel free to chime in there -- though if your use-case is solved by passing data via stdin as @akx kindly mentioned above, that's cool too :)


AWS AppSync rejects subscription websocket upgrade request from ApolloClient

Summary
AWS AppSync rejects our subscription request from ApolloClient when it tries to upgrade its connection to a websocket.
Description
After successfully creating a connection to AWS AppSync via its OkHttpClient, the ApolloClient tries to upgrade its connection to a websocket.  AWS AppSync rejects the request with a 400 Bad Request.
Version
com.apollographql.apollo:apollo-runtime:1.3.1
We’re using the ApolloClient (see https://www.apollographql.com/) from a Java service (using apollo-android aka com.apollographql.apollo:apollo-runtime:1.3.1) to access our AWS AppSync/GraphQL endpoint.  This works fine for queries and mutations, and I can get data from AWS AppSync without any issue.  However, for subscriptions, AWS AppSync rejects the websocket upgrade request, and I cannot figure out why.  It’s not a network issue, at least not on our side, as the request is making it through to AWS.  I'm using the same (sanitised) endpoint for queries, mutations and subscriptions: api-pseudo-host.appsync-api.us-east-1.amazonaws.com/graphql
The schema has the following (sanitised) types:
type Mutation {
	create(input: CreateInput!): Result
}

type Subscription {
	onCreate(
		a: String,
		b: String,
		c: String,
		d: String,
		e: String
	): Result
		@aws_subscribe(mutations: ["create"])
}

We're creating the connection like this:
	OkHttpClient okHttpClient = new OkHttpClient.Builder()
			.proxy(new Proxy(Proxy.Type.HTTP, new InetSocketAddress("our-proxy.com", 80)))
			.addInterceptor(chain -> chain.proceed(chain.request().newBuilder().header("x-api-key", "***").build()))
			.build();
	ApolloClient client = ApolloClient.builder()
			.serverUrl("https://api-pseudo-host.appsync-api.us-east-1.amazonaws.com/graphql")
			.okHttpClient(okHttpClient)
			.subscriptionTransportFactory(new WebSocketSubscriptionTransport.Factory( "wss://api-pseudo-host.appsync-api.us-east-1.amazonaws.com/graphql", okHttpClient))
			.build();

(Normally I would use authenticator() - I use addInterceptor() here for debugging purposes so there is only one REST call for the authentication to succeed.)
Looking at CloudWatch, I see the following (sanitised) entries when I do the subscription for an instance of the OnCreateSubscription Java class (compiled from the above script) via the ApolloClient:
d42b3a5a-94d7-4665-8dd4-876fc5e0c20c Begin Request
d42b3a5a-94d7-4665-8dd4-876fc5e0c20c Invalid Get Request: Query: null, Operation: null, Variables: null
{"logType":"RequestSummary","requestId":"d42b3a5a-94d7-4665-8dd4-876fc5e0c20c","graphQLAPIId":"3eyxmgqpjzedbimhfcgmo4qqvq","statusCode":400,"latency":11000000}
d42b3a5a-94d7-4665-8dd4-876fc5e0c20c Request Headers: {x-amzn-ErrorType=[MalformedHttpRequestException]}
d42b3a5a-94d7-4665-8dd4-876fc5e0c20c Response Headers: {sec-websocket-protocol=graphql-ws, cloudfront-viewer-country=US, x-forwarded-proto=https, upgrade=websocket, x-forwarded-port=443, x-forwarded-for=<IP_ADDRESS>, <IP_ADDRESS>, sec-websocket-version=13, via=1.1 7dc4818c830423900ae855831181d2b8.cloudfront.net (CloudFront), cloudfront-is-smarttv-viewer=false, x-amzn-trace-id=Root=1-5e440443-b6b681ce52ff916ebf30857a, cloudfront-is-desktop-viewer=true, cloudfront-is-tablet-viewer=false, x-api-key=***, host=api-pseudo-host.appsync-api.us-east-1.amazonaws.com, connection=upgrade, sec-websocket-key=UngxCvE4y/03UkuvI4+s4Q==, cloudfront-forwarded-proto=https, x-amz-cf-id=FrXlzc16M2aSP-c6bBm01-j9n99k_X_kM0aTh_DcCE99i4uhGOz36w==, accept-encoding=gzip, user-agent=okhttp/3.12.2, cloudfront-is-mobile-viewer=false}
d42b3a5a-94d7-4665-8dd4-876fc5e0c20c End Request

I'm not sure what to make of the "Invalid Get Request: Query: null, Operation: null, Variables: null" entry.  Should one of them be non-null for a subscription?  The way I read the response headers, it is the response to the websocket upgrade request, which I would not expect to contain, eg, a query.
I don't create the request directly; the ApolloClient+OkHttpClient handles that.  Debugging the upgrade request, I can see the request has the following (sanitised) properties:
url=https://api-pseudo-host.appsync-api.us-east-1.amazonaws.com/graphql
method=GET
body=null
headers=Sec-WebSocket-Protocol: graphql-ws
  Cookie:
  Upgrade: websocket
  Connection: Upgrade
  Sec-WebSocket-Key: UngxCvE4y/03UkuvI4+s4Q==
  Sec-WebSocket-Version: 13
  x-api-key: ***
  Host: api-pseudo-host.appsync-api.us-east-1.amazonaws.com
  Accept-Encoding: gzip
  User-Agent: okhttp/3.12.2

This is what I would expect of the upgrade request.  The response has the following (sanitised) properties:
code=400
message=Bad Request
url=https://api-pseudo-host.appsync-api.us-east-1.amazonaws.com/graphql
body=null
headers=Content-Type: application/json;charset=UTF-8
  Content-Length: 135
  Connection: close
  Date: Wed, 12 Feb 2020 13:57:23 GMT
  x-amzn-RequestId: d42b3a5a-94d7-4665-8dd4-876fc5e0c20c
  x-amzn-ErrorType: MalformedHttpRequestException
  X-Cache: Error from cloudfront
  Via: 1.1 7dc4818c830423900ae855831181d2b8.cloudfront.net (CloudFront)
  X-Amz-Cf-Pop: IAD89-C1
  X-Amz-Cf-Id: FrXlzc16M2aSP-c6bBm01-j9n99k_X_kM0aTh_DcCE99i4uhGOz36w==

So my question is: what is wrong with the websocket upgrade request that leads AWS to reject it?

Not really sure how to help you here.
From looking into the response from AWS:
x-amzn-ErrorType: MalformedHttpRequestException
Is there any documentation regarding the AWS AppSync? Double check that url is right.

hi @sav007 - yes, you're right, the url is different: subscription urls use appsync-realtime-api, rather than appsync-api.  with that change, i can get the connection to succeed, though subscription events are not actually coming through.  i'll have to dig in to see why that is...

Hi @simonmarshall , How did you get the appsync-realtime-api ? The AWS console only has one Api . Any help here would be appreciated.

With the latest upgrade tried setting up and running appsync subscriptions with apollo client - https://github.com/kodehash/appsync-nodejs-apollo-client/tree/master


Multicodec

This PR rebases ipld on top of multicodec.
See also: https://github.com/jbenet/go-multicodec/pull/6

Changes:
3b95669 (Juan Batiz-Benet, 3 minutes ago)
 rm dag builder thing

c3a7ff9 (Juan Batiz-Benet, 5 minutes ago)
 rewrote coding in terms of multicodec

60e3b77 (Juan Batiz-Benet, 18 minutes ago)
 added pb for decoding old protobufs

This doesn't yet introduce the changes @diasdavid @mildred and I discussed. follow-on PR.
@diasdavid can you tag me whenever you push support as we discussed in node-ipld?

Sure, currently I've my node-ipld thing here https://github.com/diasdavid/node-ipld working with the 'mvp ld' we talked to jump in to IPRS records land.

@jbenet I looked up this PR, nice work. There is something I don't understand though. When you transform protobuf to JSON, you construct a JSON like this one:
{
  links: [
    {hash: "...", name: "...", size: 0},
    ...
  ],
  data: "..."
}

This is however very different from other examples you gave when designing IPLD:
{
  "@context": "/ipfs/<hash-of-schema>/unixdir",
  "<filename1>": { "@value": "<hash1>", "unixMode": <mode1> },
  "<filename2>": { "@value": "<hash2>", "unixMode": <mode2> },
}

Do you agree with me that the code of IPFS must read this JSON in some defined way (the flattening algorithm) to construct a list of links, each having a name, and pointing to another IPFS object.
I understand well how this algorithm will work in the second snippet above, the link name being the keys of the JSON. But for the first example, which is converted from protobuf, how will the algorithm will be able to construct the list of links in a consistent way?
I would have in fact imagined that the protobuf objects would convert to something like this:
{
  @context: <link to protobuf context>
  @value: <data segment>
  <link name>: { hash: <hash>, size: <size> },
  <link name>: { hash: <hash>, size: <size> },
  // "@" characters are escaped as "\@" (and "\" as "\\")
  ...
}

Why didn't you choose this format ?

@mildred this is specifically the OLD (current) protobuf format. link names are not unique currently, and there is the "data" segment. it follows the proto there. i wish we could transparently convert to the new style of doing things but dont think we can. we must preserve backwards compat to avoid breaking links.
what we can do though is add "mlink" and so on there.

The main question is how the flattening algorithm that will be used to determine link names will work under this old format. Either:

we transform the flattening algorithm to use the name attribute when provided instead of the flattened key of the link in the JSON. In case some links appear twice, we must define a process order.
we convert to another format that contain the link name as key, but link names are not unique. We must decide if we take the first link of that name, or the last (whatever IPFS does already). Duplicate links could be preserved in a separate way.


feat(core,presets)!: update presets to use the recursive callback

Follow up to #1126, this PR update the existing variants to use the introduced variant handler().
Closes #1104
This PR adds 2 extra properties on the handler. Variants that use selector sectioning (the one that uses $$: dark, rtl/ltr and group pseudo) are now moved into prefix so it can be modified selectively.
https://github.com/unocss/unocss/blob/91ea249ea583b7403bf3256f1705ae0966ab3360/packages/core/src/types.ts#L193-L204

Can you help resolving the conflicts? Thanks

@chu121su12 Thanks for your work on this. I was watching the changes in this PR and other related PRs and I was not really expecting this to be merged while snapshots are like that. This PR now removes the whole purpose of #987. I see this PR comes with some features to take more control over output. Having more features is nice, but it still seems a little bit incomplete.
Why we shouldn't fix #1104
The issue in #1104 is the consequence of the breaking change in #987. The point of #987 is applying variants in the same order as Tailwind to make migration as easy as possible. I don't understand why we are trying to fix #1104. The changes in #987 are not just about group and dark variants. Let's take a look at the example at #1104
Input:

Unocss output after #987 and before this PR
checked\:next\:bg-red-50 + *:checked
.next\:checked\:bg-red-50:checked + *

Tailwind output (same as the above)
checked\:next\:bg-red-50 + *:checked
.next\:checked\:bg-red-50:checked + *

Unocss output after this PR
.checked\:next\:bg-red-50:checked + *
.next\:checked\:bg-red-50 + *:checked

Now two same inputs have different outputs and behaviours between Unocss and Tailwind. We should revert this PR and suggest people to reverse their variants order.
/cc @antfu

My case for #1104 is that unocss syntax should follow the order of declaration, as in checked:next or next:checked shoud be applied in order.
@sibbng To your point, this changes is done on preset-mini. If we really want to preserve compatibility with tailwind, I think we should add override in preset-wind instead.

I added next variant manually in config.

Also, as this is not in the tailwind's core, I think it is on the same level as providing separate variant definition.

I see, let's better align with Tailwind in this case. I guess having inverse behavior for wind / mini would be quite confusing. Let's revert the order. @chu121su12


Dockerfile

Created conda-linux-64.lock, Dockerfile and update environment.yml

looks good now, but we need to add - pandera, - pip: - deepchecks for data validation, should we add these to environment now or do it later?

Alright, working on it.

I fixed the error by specifying the platform="linux/amd64", also the --quiet flag in mamba update will let error go unnoticed.


[FEATURE] get emulated device while running simulator

I wanted to fix https://github.com/rebeccahughes/react-native-device-info/issues/104 so made a change to check the environment variables to see what the simulated device should be.
In my opinion the deviceName call should return the simulated deviceName and not 'Simulator'. Detecting if it's a simulator requires a secondary call to isEmulator() (which I'd prefer be called isSimulator(), but that's something else.)
Unfortunately I haven't been able to test it out. I'm new to the react-native / xcode interaction and can't seem to get the header search paths right. It returns 'React/RCTBridgeModule.h' file not found, despite having setup $(SRCROOT)/../react-native/React etc.
As I'm out of time at the moment, I thought I'd submit this in case it's useful to someone.

Please test before you submit.  Sorry, we barely have time to test the PRs we currently get.


Defaults download_resources does not turn flag off

I've omitted download_resources or set it to false, both do not unflag Retrieve All Embedded Resources in HttpRequestDefaults.  Something I'm missing?
test do
    defaults download_resources: false
end.run(gui: true)

We set this flag
image_parser: false
to avoid implicit download of embedded resources.

:+1:


Logout/Delete account fails

'NoneType' object has no attribute 'language' (/base/data/home/apps/e~rogerthat-server/20180529t134853.410060501450369130/add_1_monkey_patches.py:127)
Traceback (most recent call last):
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/277b61042b697c7a_unzipped/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1511, in __call__
    rv = self.handle_exception(request, response, e)
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/277b61042b697c7a_unzipped/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1505, in __call__
    rv = self.router.dispatch(request, response)
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/277b61042b697c7a_unzipped/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1253, in default_dispatcher
    return route.handler_adapter(request, response)
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/277b61042b697c7a_unzipped/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1077, in __call__
    return handler.dispatch()
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/277b61042b697c7a_unzipped/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 547, in dispatch
    return self.handle_exception(e, self.app.debug)
  File "/base/alloc/tmpfs/dynamic_runtimes/python27/277b61042b697c7a_unzipped/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 545, in dispatch
    return method(*args, **kwargs)
  File "/base/data/home/apps/e~rogerthat-server/20180529t134853.410060501450369130/rogerthat/pages/account.py", line 66, in post
    reason = localize(user_profile.language, "Your account has been deleted on your request")
AttributeError: 'NoneType' object has no attribute 'language'

I know this is a server error, but the user should not be able to delete his account 2 times


[mbedtls] Update to v2.28.1

Describe the pull request
Latest release of LTS version 2.28

What does your PR fix?
N/A

Which triplets are supported/not supported? Have you updated the CI baseline?
Yes

Does your PR follow the maintainer guide?

Yes

Already tested all features successfully on x86-windows and x64-windows-static.

Thanks for the update!