hourofyear

Is there a way to use 'hourofyear' in the same way 'dayofyear' works? I want the calculate the mean temperature value for a 2d dataset for each hour of the year based on 40 years of hourly data. I realise this might be a pandas question but if I receive an answer from a pandas forum I don't know if I would be able to work out how to apply it to an xray dataset.
Below is the code I would use to calculate 'dayofyear' but with the word 'hour' used to replace 'day'. Obviously it does not work!
Any feedback will be greatly appreciated
ds=xray.open_mfdataset('/DATA/*TEMP.nc')
ds_variable=ds['TEMP']
hourofyear=ds_variable.groupby('time.hourofyear').mean('time')

This is a good idea, but it's not currently supported. You could do something like this, though:
hourofyear = (ds['time.dayofyear'] * 24 + ds['time.hourofday']).rename('hourofyear')
result = ds['TEMP'].groupby(hourofyear).mean('time')

thank you
On 30 December 2015 at 15:01, Stephan Hoyer<EMAIL_ADDRESS>wrote:

This is a good idea, but it's not currently supported. You could do
something like this, though:
hourofyear = (ds['time.dayofyear'] * 24 + ds['time.hourofday']).rename('hourofyear')
result = ds['TEMP'].groupby(hourofyear).mean('time')
—
Reply to this email directly or view it on GitHub
https://github.com/xray/xray/issues/690#issuecomment-167932904.

--
Dr Sarah Harris
Research Fellow
School of Earth, Atmosphere and Environment
Room 227, 9 Rainforest Walk
Faculty of Science
Monash University
Ph: 03 9902 4243
Email<EMAIL_ADDRESS><EMAIL_ADDRESS>

This was very helpful, thanks. Minor tweak (maybe due to source change since previous comments in 2015?):
hourofyear = ((da.time.dt.dayofyear-1) * 24 + da.time.dt.hour).rename('hourofyear')
result = da.groupby(hourofyear).mean('time')


initServices not exported in monaco-languageclient 8.0.0

First of all, many thanks for this project! I enjoy it a lot and I'm looking forward to the release of 8.0.0.
While trying out my setup and upgrading to 8.0.0-next.5, I found I can no longer import initServices from the monaco-languageclient module. I am upgrading from an older version (6.6.0) and adjusted my code according to the changelogs etc. but I am unsure how to resolve this one.
Any pointers are appreciated. Thanks!

Hi @maxdekrieger service related functions are now exported via monaco-languageclient/vscode/services. The CHANGELOGs are not yet updated on the PR branch. I will get to that.

Thanks for your reply, works like a charm!


Speech Disfluency Simulator and Phoneme-level Simulator In TOD-DA

Hello
Does this github include the code for the Speech Disfluency Simulator and Phoneme-level Simulator used in TOD-DA?

Hello Thanks for your attention on this work!

Hello~ Thanks for your attention on this work!
We do not include the code about them.
But in details,

the implementation of Speech Disfluency Simulator is similar as LAUG
we perform five operations in Phoneme-level Simulator with heuristic probability


Bug in exclude() using contains

I have a query that includes a condition like the following:
.exclude(hstore_field__contains={'key_name': 'value'})

In django-hstore 1.3.4 and earlier, this translated to the following SQL:
WHERE NOT ("app_model"."hstore_field" @> hstore(ARRAY['key_name'], ARRAY['value']) AND "app_model"."hstore_field" IS NOT NULL)

But starting in 1.3.5, it changed to the following:
WHERE NOT (("app_model"."hstore_field"->'key_name') = 'value' AND "app_model"."hstore_field" IS NOT NULL)

The latter breaks down when the hstore field is not null but doesn't contain the key.  It simplifies as follows:

WHERE NOT (NULL = 'value' AND TRUE)
WHERE NOT (NULL AND TRUE)
WHERE NOT NULL
WHERE NULL

Hence the condition ultimately evaluates as false and the record is excluded, even though we were trying to get records like this one that don't contain the specified key/value combination.  The SQL from earlier versions works correctly, because it doesn't throw a NULL into the boolean operations.

Yea, I'm seeing this as well. Trying to exclude records that have a specific key in the dictionary isn't yielding any rows at all. I'm using django_hstore 1.4.2.

+1


[Joy] Add IconButton component

Preview: https://deploy-preview-30864--material-ui.netlify.app/experiments/joy/button/
Playground: https://deploy-preview-30864--material-ui.netlify.app/experiments/joy/components/?name=IconButton
Props

variant (same as Button)
color (same as Button)
size (same as Button)
~shape: rounded | square | circular (new prop). This should cover all the use-cases about the border radius for IconButton. The default shape can be switched to one of those values.~ (decided to go without this prop because theming is enough)
~fullWidth~ (use <Button fullWidth><Icon /></Button> instead)
~edge~ (what this prop do in Material is add left/right margin, I think there is a better way to integrate with other components)

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

Why is there is no variant props in Icon button?

Why is there is no variant props in Icon button?

IconButton has the same variants as Button. https://mui.com/joy-ui/react-button/#icon-button
If you encounter a problem, please open a new issue. Thanks!

I was looking at this:
https://mui.com/material-ui/api/icon-button/
Is joy-ui and material-ui different?

Hey @sushanyadav, we recommend reading the First look at Joy UI blog post － you'll probably get all information you need for the moment and, of course, the answer to your question (which, spoiler, is yes! 😅).

@siriwatknp @danilo-leal just to ensure to get this right, there are really no variants on IconButton on material-ui? I assumed this is a bug. I mean even the docs say:

"You can use the variants key in the theme's components section to create new variants to Material UI components. "

https://mui.com/material-ui/customization/theme-components/#creating-new-component-variants
This feels for me a bit inconsistent. Or the docs should maybe adjusted a bit to which components can have variants.
I personally would at least add variants to IconButtons as there are very similar to Button. They are basically Buttons without a label.

Thanks for the feedback. Can you please open a new issue and discuss it over there? I think it is not related to Joy UI.


Bump tmate to 2.3.0, libssh to 0.9.0

Fixes #1
blobs are uploaded. The main downside to this is it requires clients be on tmate 2.3.0 as there was apparently no forward/backward compatibility between 2.2.1 and 2.3.0.

How new is tmate 2.3.0 vs 2.2.x?

Next newest version, first release of tmate in 2-3 years.
Sent from my iPhone

On Sep 19, 2019, at 4:05 PM, James Hunt<EMAIL_ADDRESS>wrote:
How new is tmate 2.3.0 vs 2.2.x?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

None of these changes look to be backwards-breaking after a cursory read:
https://github.com/tmate-io/tmate/compare/2.2.1...2.3.0

Released in v1.0.0 of the BOSH release: https://github.com/cloudfoundry-community/tmate-boshrelease/releases/tag/v1.0.0
Note: properties changed in this release from tmate.x to just x.


Redesigned metatensor-based Clebsch Gordan iterations

Closes #178 and #185 . New API design for performing metatensor-based Clebsch Gordan iterations.
Still left to do:

[x] Mathematical unit tests (handled by @agoscinski and @DivyaSuman14)
[ ] Unit tests on the pre-computation of metadata (@jwa7)
[ ] Thorough documentation (i.e. the .rst from #185, as well as docstrings)

Documentation

Include concise but complete explanations of sign conventions (i.e. Sph Harms, Condon Shortley, etc) both in reference to the CG cache implemented (i.e. using wigners) and compared to other rascaline Calculators --> i.e. PowerSpectrum updated to include (-1)^l factor
Different types of documentation, see https://www.writethedocs.org/videos/eu/2017/the-four-kinds-of-documentation-and-why-you-need-to-understand-what-they-are-daniele-procida/ (thanks @Luthaf ). Particularly important for CGs where there is a lot going on with maths, conventions, and design choices.

:books: Documentation preview :books:: https://rascaline--237.org.readthedocs.build/en/237/

Should I add the doc from PR https://github.com/Luthaf/rascaline/pull/183? That seemed to me as a good starting point

Should I add the doc from PR #183? That seemed to me as a good starting point

Yeah sounds like a good idea to inherit the .rst file from there. Is there a way to pipe the relevant commit(s) from that branch into this PR so credit can be properly assigned?

You can use git cherry-pick to re-apply individul commits on top of a new branch. Alternatively, you can create a new commit and set a different author than yourself, or just use Co-Authored-By in the commit message.

Update: @curiosity54 and I have fixed the norm preservation unit test!  I think we are in a position to discuss finalizing the API and then moving onto documentation. Thoughts @luthaf?

And to be clear on what happened: I have enabled a bool flag sort_l_list (open to suggestions on the name) that either turns on/off the computation of redundant blocks with a CG iteration - i.e. ones in which the sorted l lists are the same.
When this flag is off, the norm preservation tests pass as expected. When switxhed on, thus saving computational cost, the test failed too as expected.
The alternative was a tricky handling of the l list with the normalization. This might be more tricky than first thought, as also depends on k-combinations, and as such was not something Jigyasa and I could figure out just now.
As this normalization (in the case of taking computational shortcuts) perhaps isn't important for ML purposes, are we ok to let users use turn on this flag at their own risk - i.e. accept the slight information loss at reduced computational cost?

@Luthaf In order to make the CI happy I had to add some dependencies in the min-deps env - for CG tests we need ase, metatensor-operations and sympy. Of course not ideal as defeats the purpose of being minimal dependencies - what's the best way to get around this? Is there a way to only run CG tests at a higher level of dependencies?

Is there a way to only run CG tests at a higher level of dependencies?

yes! https://docs.pytest.org/en/7.1.x/how-to/skipping.html#skipping-on-a-missing-import-dependency

Thanks for the review @Luthaf ! I've made the changes re: your suggestions :)


fix(ingest/powerbi): add sqlglot python dep

Follow up on https://github.com/datahub-project/datahub/pull/8592.
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Merging through unrelated CI failures to unblock ingestion connector tests / releases


Update language for architecture.md

Updated a sentence via https://github.com/juicedata/docs/pull/490/files#diff-8f118932ee3fc67c051899a2d0ea34224cc9f69e384df47d02c1e67313e59eacR52
PTAL @timfeirg

hold, I'll add minor adjustments to architectural diagram in this pr

to be translated by @CaitinChen


PR template asks for nightly cargo fmt.

The PR template asks for cargo +nightly fmt --all, which currently would want to change a lot of formatting and doesn't seem to be enforced by CI? Also, the outcome of that command depends on the latest installed nightly rustfmt version.
It might be more maintainable to ask for the rustfmt version that is shipped with the same stable Rust release fixed in the .travis.yml, and to check that in CI?

Also, I noticed that cargo clippy --all-targets passes without warnings. :tada:
That could also be added to CI?
(Looks like both were already there, and were removed in this commit — was that by accident?)

Nightly is only for merge_imports = true. If someone uses stable, that's fine too. :)
I have found enforcing formatting in CI to be somewhat constraining. If this project becomes really busy with PRs, we can enable it, but before that - I don't really mind.
Same with Clippy . I like to run it periodically and fix all the warning, and not have to worry about it all the time.


Add Tabs connected to ViewPager

Should be fairly simple to connect the ViewPager to tabs like is done here: https://github.com/madhu314/react-native-tabbed-view-pager-android
The above library is out of date and it uses a broken version of ViewPager. We could offer tabs as optional and nice to have.

Yes this for sure!

It is better to use and update this library.
https://github.com/ptomasroos/react-native-scrollable-tab-view

I have started to work on this feature, just a proof of concept on Android, will need some help to implement it on iOS 😅
I will clean code and create a branch in my fork with those changes and share it (not enough time for that sorry 😔)
Happy (halloween || "la castañera") to everyone!! 🎃/ 🌰

Oh @x0s3 didn't know somebody was working on it. There is actually a repo that might do the same if they update to use the ViewPager from the community https://github.com/madhu314/react-native-tabbed-view-pager-android/issues/17.

Oh @x0s3 didn't know somebody was working on it. There is actually a repo that might do the same if they update to use the ViewPager from the community madhu314/react-native-tabbed-view-pager-android#17.

it would be useful to close this or update labels, so that there is no confusion in the future 😅 (just a comment)

I just found a way to do it out of the box.

const Tabs = () => {
  const [pageIndex, setPageIndex] = useState(0);

  let viewPager;

  const tabsRef = node => {
    if (node !== null) {
      viewPager = node;
    }
  };

  const setPage = (index: number) => {
    setPageIndex(index);
    viewPager && viewPager.setPage(index);
  };

  const onPageSelected = ({ nativeEvent: { position } }: PageSelectedEvent) => {
    setPageIndex(position);
  };

  return (
    <>
      <ViewPager
        initialPage={0}
        ref={tabsRef}
        onPageSelected={onPageSelected}
      >
        <View key="0">
          <Screen text="A" />
        </View>
        <View key="1">
          <Screen text="B" />
        </View>
      </ViewPager>
      <PageButtons currentIndex={pageIndex} setPage={setPage} />
    </>
  );
};

@x0s3 @ferrannp are you still working on it ?

Nope, I haven't had time as https://github.com/madhu314/react-native-tabbed-view-pager-android worked well for me still 😅.

@troZee is there any example to make scroll tab view by using pagerview?

Closing bc tabview is responsible for adding tabs on top of pager view. More here https://github.com/satya164/react-native-tab-view#readme


Implement Bluetooth Key Rotation

ITS-Pro time category: https://its-pro.ucsd.edu/browse/MA-86
This is done when:

[ ] Document iPhones and Android devices that supports BT LE
[x] Bluetooth key broadcasted by the app is rotated every 24 hours
[ ] Bluetooth key is prefix with "ucsdapp"

This doc lists out all the devices that support beacon transmission. Information for iOS devices is pulled from Apple's site: https://support.apple.com/en-us/HT202880. Information for Android devices is pulled from the Android Beacon Libary: https://altbeacon.github.io/android-beacon-library/beacon-transmitter-devices.html.


Update application-gateway-web-app-powershell.md

I think "BackendFqdns" is better than "BackendIPAddresses".

@davidmu1 - Please review the proposed changes.  Thanks

@ShuheiUda: Thank you for your feedback. I believe that the current parameter name is BackendIPAddresses for both of the commands that you mention. I would suggest working with engineering if you want to have the parameter name changed, and then we can update the article. #hold-off

@davidmu1 Thank you for your reply.
I already checked both parameter (BackendIPAddresses / BackendFqdns) work correctly.
But, according to the cmdlets reference, when the setting back-end address pool by using FQDNs, we should use BackendFqdns switch.
https://docs.microsoft.com/en-us/powershell/module/azurerm.network/set-azurermapplicationgatewaybackendaddresspool?view=azurermps-4.4.0
https://docs.microsoft.com/en-us/powershell/module/azurerm.network/new-azurermapplicationgatewaybackendaddresspool?view=azurermps-4.4.0
Does those parameters work the same way? (or not?)
Do you know the best person who I ask for this question?

@ShuheiUda: I understand what you are saying now. Your feedback looks like the correct choice. Thanks again. #sign-off


support generic tabulate viz for metadata

It'd be nice to have an option to download the metadata as a TSV file (a use-case came up on the forum for merging and exporting metadata).


[GSoC2024] add return types to fix typescript warnings

Fixes: #7598
Motivation and context
There are some minor typescript errors in the files, this pull request fixes those.

How has this been tested?
Ran the code after changing, and it was functional like before, this didn't need any additional test.

Checklist

[x] I submit my changes into the develop branch
[x] I have created a changelog fragment
[x] I have linked related issues (see GitHub docs)
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

@bsekachev I've made the necessary changes, please change the last file Lambda Manager as I have added a few Promise there because it is a very reused file and to me, Promise makes the most sense there. Please check and let me know if there is any issue and I'll fix it ASAP. Thanks.

I think this PR is not ready yet, there are a few changes which I just realized need to be added, I'll add those and ping you accordingly, thanks.

Hello, do you have any plans regarding the pull request?

Yes @bsekachev , I left a comment above under your review, please let me know. Thanks.

Yes, one week ago you mentioned "tomorrow". That is why I am asking :)

Yes, one week ago you mentioned "tomorrow". That is why I am asking :)

Sorry about that, @bsekachev  I wanted to ask something about your comment under the Promise review, you said we should use something more concrete here instead of any, but that is Lambda manager, and we are very uncertain what will be returned here, hence doesn't any make sense here?

I believe we are certain enough. Otherwise how would it be possible to work with this API?
As far as I remember run() returns a string, representing rq identificator to fetch statuses later.
call() is more complex, but, more or less, you may find it out from this file cvat-ui/src/components/annotation-page/standard-workspace/controls-side-bar/tools-control.tsx.
Perhaps the output is different for trackers, detectors and interactors.
So, it should be like Promise<TrackerResults | DetectorResults | InteractorResults>, and define these three types additionally.

Hi @bsekachev, I've added the required types and currently added the interfaces on top of the Lambda Manager file, please let me know if that is fine or if there is some other place more appropriate for the interfaces.
Additionally, I have updated the concerned code related to the lambda.call function, but I had to make some type assertions(e.g. number[] and number[][] in the tools-control.tsx file) to make it work with the existing code without making too many changes. Please let me know if this is the correct implementation for this.
Thank you.

Please, avoid changes in tools-control.tsx, I will work with types inconsistency on my own, I see there are some issues.

@bsekachev Updated

Just FYI: https://github.com/cvat-ai/cvat/pull/7785

I found some more typescript warnings because of missing return types, maybe I can create a follow-up pull request for this if you allow it.


Export traffic_server symbols

This is a temporary fix until we can separate the API from the traffic_server executable. It sets the ENABLE_EXPORTS property on the traffic_server target to export its symbols, and "links" all the plugins to it. On Linux, this "linking" does nothing of interest. On Mac, the -bundle_loader flag will be added.
Closes #9848.

This PR is confusing because I didn't understand why plugins were linking with traffic_server.  I think this is addressing two issues.  One, we need to mark export_symbols so plugins can load with dlopen.  And, two, we want to make sure there aren't undefined symbols in the plugins.  Is this correct?

This PR addresses the first of those two issues. The second isn't currently an issue.


submit a readme

Can you submit a readme document? It can help us better, although it doesn't look complicated, but I am a beginner, thank you

I will sorry, yeah this is mostly a package I use, nothing too fancy about it! but I will find the time!


Sample glTF files fail to load in Microsoft's own software

The files "glTF-Toolkit/glTF-Toolkit.Test/Resources/gltf/CubeAsset3D.gltf" and "glTF-Toolkit/glTF-Toolkit.Test/Resources/gltf/CubeWithLOD.gltf" fail to load in both Windows explorer preview pane and the Windows 10 3D Viewer program by Microsoft.

I'm not sure I would call these assets sample glTF files as they are test files, but they don't load because the glTF files don't have a URI in the buffer object. They don't load in any software that I tried.


[2pt] run_test_case.py error - missing branch inundation files

This one is a bit hard to replicate and I am not sure we even should do a fix here, but it needs to be discussesd.
During an unrelated test, some branches failed during gms_run_branch. When I ran alpha test, the failed branches resulted in missing inundation files (of course), but run_test_case attempted to use them in calc of stats.
This one is a bit hard to replicate but I suspect it could be seen alot more when run at scale.
To replicate this error, you need to get one of Jim's branches from a commit, but not necessarily his current branch (might be fixed by that time).  Pull down the source code from the commit (as of )
https://github.com/NOAA-OWP/inundation-mapping/pull/614/commits/cae4f80948fad9245bacd2fcb487f10478e8e844 as part of PR 614.
Then use the following example (ish)  (notice that all stream orders were kept, aka. no -s switch).
gms_run_unit.sh -n rob_jim_4_07080101 -u 07080101 -c /foss_fim/config/params_template.env -j 40 -d /foss_fim/config/deny_gms_unit_default.lst -o

gms_run_branch.sh -n rob_jim_4_07080101 -c /foss_fim/config/params_template.env -j 40 -d /foss_fim/config/deny_gms_branches_min.lst -o

The error that triggered was :
	Traceback (most recent call last):
	  File "/foss_fim/src/split_flows.py", line 306, in <module>
	    split_flows(max_length, slope_min, lakes_buffer_input, **args)
	  File "/foss_fim/src/utils/shared_functions.py", line 247, in wrapper
	    func(*args, **kwargs)
	  File "/foss_fim/src/split_flows.py", line 112, in split_flows
	    snapped_point['geometry'] = snapped_point.apply(lambda row: target_snapline.interpolate(target_snapline.project( row.geometry)), axis=1)
	  File "/usr/local/lib/python3.8/dist-packages/geopandas/geodataframe.py", line 850, in __setitem__
	    value = _ensure_geometry(value, crs=self.crs)
	  File "/usr/local/lib/python3.8/dist-packages/geopandas/geodataframe.py", line 42, in _ensure_geometry
	    out = from_shapely(data, crs=crs)
	  File "/usr/local/lib/python3.8/dist-packages/geopandas/array.py", line 166, in from_shapely
	    return GeometryArray(vectorized.from_shapely(data), crs=crs)
	  File "/usr/local/lib/python3.8/dist-packages/geopandas/_vectorized.py", line 104, in from_shapely
	    arr[:] = data
ValueError: could not broadcast input array from shape (0,) into shape (1,)

However, we should have been able to go on to alpha testing have caught the error much sooner (???) I imagine we don't want it to run anyways, but if it is all automated, this needs to be addressed sooner.
python3 foss_fim/tools/synthesize_test_cases.py -c DEV -e GMS -v rob_jim_4_07080101 -jh 1 -jb 20 -m /outputs/rob_jim_4_07080101/rob_jim_4_07080101_metrics.csv -o
The error:
07080101,1060000008,RasterioIOError, /data/outputs/rob_jim_4_07080101/07080101/branches/1060000008/rem_zeroed_masked_1060000008.tif: No such file or directory
07080101,1480000005,RasterioIOError, /data/outputs/rob_jim_4_07080101/07080101/branches/1480000005/rem_zeroed_masked_1480000005.tif: No such file or directory
07080101,1480000013,RasterioIOError, /data/outputs/rob_jim_4_07080101/07080101/branches/1480000013/rem_zeroed_masked_1480000013.tif: No such file or directory
07080101,1480000258,RasterioIOError, /data/outputs/rob_jim_4_07080101/07080101/branches/1480000258/rem_zeroed_masked_1480000258.tif: No such file or directory
07080101,1480000451,RasterioIOError, /data/outputs/rob_jim_4_07080101/07080101/branches/1480000451/rem_zeroed_masked_1480000451.tif: No such file or directory
Traceback (most recent call last):
  File "rasterio/_base.pyx", line 216, in rasterio._base.DatasetBase.__init__
  File "rasterio/_shim.pyx", line 67, in rasterio._shim.open_dataset
  File "rasterio/_err.pyx", line 205, in rasterio._err.exc_wrap_pointer
rasterio._err.CPLE_OpenFailedError: /data/test_cases/ras2fim_test_cases/07080101_ras2fim/testing_versions/rob_jim_4_07080101/100yr/inundation_extent_07080101.tif: No such file or directory

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/foss_fim/tools/run_test_case.py", line 260, in run_alpha_test
    compute_contingency_stats_from_rasters(predicted_raster_path,
  File "/foss_fim/tools/tools_shared_functions.py", line 54, in compute_contingency_stats_from_rasters
    raster = rasterio.open(predicted_raster_path)
  File "/usr/local/lib/python3.8/dist-packages/rasterio/env.py", line 433, in wrapper
    return f(*args, **kwds)
  File "/usr/local/lib/python3.8/dist-packages/rasterio/__init__.py", line 218, in open
    s = DatasetReader(path, driver=driver, sharing=sharing, **kwargs)
  File "rasterio/_base.pyx", line 218, in rasterio._base.DatasetBase.__init__
rasterio.errors.RasterioIOError: /data/test_cases/ras2fim_test_cases/07080101_ras2fim/testing_versions/rob_jim_4_07080101/100yr/inundation_extent_07080101.tif: No such file or directory

So, if I'm understanding correctly, the error from gms_run_branch.sh is causing an error in the alpha test, correct? I don't think it's too much of an issue because we shouldn't be running the alpha test on a HUC that did not get built correctly. This does bring up a good point that we should be careful with running automated tools during an API call. I.e., if there is any error in gms_pipeline then all subsequent processes should be killed.


Status/SIC admin/assessor column

display sic code, assessors, fill progress and state at different stages of the approvement process

 [QAE16IMP] Admin & Assessors - Applications screen update

Looks good :+1:

Awaiting for Rspec results


chore: Also trigger workflow when merging into v2

Currently we can't reliably merge into v2 because checks don't automatically trigger

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 68.29%. Comparing base (e054385) to head (34ec5f9).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1343      +/-   ##
==========================================
- Coverage   68.43%   68.29%   -0.14%
==========================================
  Files         183      183
  Lines       17606    17620      +14
==========================================
- Hits        12049    12034      -15
- Misses       4895     4920      +25
- Partials      662      666       +4

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


Update clubs.props.txt

Issue: https://github.com/openfootball/football.json/issues/28

Thanks for the patch / update. Keep it up.   Note: The next nightly (auto-)build runs on 5am UTC, see https://github.com/yorobot/football.json/actions.


the /providers endpoint leaks auth data

Not urgent, but /providers probably shouldn't show auth data to Locker apps. For example, an excerpt of what http://localhost:8042/providers?types=contact returns:
...
{
"title": "Twitter Account",
"status": "waiting",
"provider": "twitter",
"provides": [
"contact/twitter",
"mentions/twitter",
"related/twitter",
"timeline/twitter",
"tweets/twitter"
],
...
"srcdir": "Connectors/Twitter",
"authurl": "http://localhost:8042/auth/twitter/auth",
"auth": {
"consumerKey": "XXX",
"consumerSecret": "XXX",
"token": {
"oauth_token": "XXX",
"oauth_token_secret": "XXX"
}
},
"id": "twitter",
...
},
...

for reference, similar (and probably related) to #379


HTMLField is not appeared in Django Admin Site

Here are my codes.
My code was working well with Django==2.0.8, django-tinymce==2.7.0.
I updated my codes with Django=2.2.15, django-tinymce==3.0.2
Please help me.
Thanks.

Your configuration is for an old version of TinyMCE. Don't upgrade to the last version if you don't want to upgrade your configuration to meet TinyMCE 5 requirements.

How should I update my Tinymce configuration for Django 2.2.15?

Update your TINYMCE_DEFAULT_CONFIG to one of the examples here : https://www.tiny.cloud/docs/demo/full-featured/


Wrong build.sh file permissions

File has changed permissions
https://github.com/spiral/roadrunner/commit/ea60c3e1eba96cd140e4c89b710de3a98f523f43#diff-0b83f9dedf40d7356e5ca147a077acb4
build.sh 100755 → 100644
And now its error
make
make: ./build.sh: Permission denied
make: *** [all] Error 1

https://github.com/spiral/roadrunner/pull/70

Thank you.


External action not found python_debugger

I got the above error when trying to manually trigger an action as instructed in the documentation.
"robusta playbooks trigger python_debugger name=podname namespace=default"
I'm new to kubernetes and everything related, so please let me know what information you need to help me help you debug this issue. Someone mentioned that they will need to see the logs for robusta-runner. Let me know where I can find these logs so I can get them to you for you to review.
Thanks.

Hi,
You can get the logs using the following kubectl command:
kubectl logs deployment/robusta-runner runner
Can you send the output of that?
Thanks

robusta.log

robusta2.log

robusta3.log

@arikalon1 what is our status on this?

The original issue was because there were no sinks defined.
Closing it


softmaker-office, freeoffice: make it easy to override versions

Motivation for this change
Make the edition, version, and hash easier to override to support
users who have a license for an older version of Softmaker Office.
With this change one can e.g. use Softmaker Office 2018 with:
softmaker-office.override {
  officeVersion = {
    edition = "2018";
    version = "976";
    sha256 = "0j6zm0cbxrcgm7glk84hvvbp4z0ys6v8bkwwhl5r7dbphyi72fw8";
  };
}

This also helps people fix things when upstream has replaced the
previous version's tarball and this hasn't been fixed in nixpkgs yet.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/how-to-override-this-derivation/8721/7


VNSO INFO

at the bottom of the home page, we could have the background information

@Vanuatu-National-Statistics-Office/nsdp-platform-team This is up for review on the homepage now. It seems like maybe it needs a little bit of a blurb, but that is completely up to you.


JavaScript Capstone Project

The JavaScript capstone project is about building our own web application based on an external API. We will select an API that provides data about a topic we like and then build the web app around it.

A home page showing a list of items
A popup window with more data about an item that we can use to comment on it or reserve it for a period of time.

Hi @Dorcas126, You have done an amazing job of setting up the files for the capstone projects. However, I would like to add a few changes to the webpack configuration before we merge it.
##Changes

[ ]  I would like to create a config file for development mode and production mode.
[ ]  I suggest that we should rename the index.html in the src directory to template.html

Please feel free to leave a comment in case the changes won't be neccessary

Hi @Dorcas126, You have done an amazing job of setting up the files for the capstone projects. However, I would like to add a few changes to the webpack configuration before we merge it.
##Changes

[ ]  I would like to create a config file for development mode and production mode.
[ ]  I suggest that we should rename the index.html in the src directory to template.html

Please feel free to leave a comment in case the changes won't be necessary

Hi @Dorcas126, You have done an amazing job of setting up the files for the capstone projects. However, I would like to add a few changes to the webpack configuration before we merge it.
##Changes

[ ]  I would like to create a config file for development mode and production mode.
[ ]  I suggest that we should rename the index.html in the src directory to template.html

Please feel free to leave a comment in case the changes won't be neccessary

Hi @AsumVictor well done on the changes you made
it's really an amazing job
You can make the remaining changes you requested👍

Thank you @Dorcas126, we are ready to merge


Updating reference comments

In score_aggreation.py, the docstring makes reference to Sohn2021aa.pdf paper hosted in coinse.kaist.ac.kr. This is no longer the URL for COINSE, and needs to be updated to https://coinse.github.io.

:octocat:


Webpack HMR plugin conflict

I have a custom loader for my application that is something like this:
{
  test: /custom.js$/,
  exclude: /node_modules/,
  loader: paths.client('lib/bundler'),
}

This conflicts with the HMR loader in _development.js because it checks for /js/ in loaders.test then adds to this array loader.query.env.development.plugins[0][1].transforms. This conditional looks to be babel specific so instead of the regex test, what about just testing for the loader if (loader.loader === 'babel')?

@patrickheeney I like that a lot more, good suggestion. Do you mind submitting a PR for this?

@davezuko Sure, running out of time tonight but will be at it again tomorrow.

Awesome, thank you.

@patrickheeney while you're at it, do you think you could take a stab at updating this:
https://github.com/davezuko/react-redux-starter-kit/blob/master/build/webpack/_production.js#L20
Along similar lines, we should probably just check if the loader has css as a loader and then apply it, that way if somebody swaps out sass for less then it will still perform as expected.


Attempting to add a new storage service via the web UI results in HTTP 500 error

This issue is likely caused by WTForms not being sufficiently up-to-date to work with the version of Flask we're using.
https://stackoverflow.com/questions/77202512/working-with-wt-forms-validators-in-flask

Fix merged.


Error in Firefox

What does this error mean?
error { target: WebSocket, isTrusted: true, currentTarget: WebSocket, eventPhase: 2, bubbles: false, cancelable: false, defaultPrevented: false, timeStamp:<PHONE_NUMBER>873491, originalTarget: WebSocket, explicitOriginalTarget: WebSocket, NONE: 0 }.
How to replicate:
1.) Use Firefox.
2.) Create a WebSocket connection.
3.) Click any  tag. e.g. Download.
4.) Use any feature that receives a message from the server using a WebSocket. (i.e. Send a message from server to client.)
5.) The error is received.
6.) WebSocket connection closes by itself.

no answer


[Question] Make size of the image in Hero/Thumbnail card configurable?

Bot Info

Bot handle: Virtual Assistant
App ID:
SDK Platform: .NET
SDK Version: 3.8
Active Channels: WebChat
Deployment Environment: Azure

Issue Description
Size of the image in Hero and Thumbnail card cannot be set to max-width max-height etc. If the image is large then it gets spill over.

Code Example
var heroCard = new HeroCard
{
Title = title,
Subtitle = subtitle,
Text = text,
Images = new List() { cardImage },
Buttons = new List() { cardAction },
};

Reproduction Steps

Get two images of different in size and create two hero cards
Place these two hero cards in a Carousel card
The Hero card size will be different for both the images in Carousel tray

Expected Behavior
If there would have a max-width and max-height feature in the card then we could set that to make the card sizes equal.

Actual Results
Card sizes are different which makes the Carousel a bit asymmetrical.

@singhsurya The Hero Card and Thumbnail Card are basic card templates that are not really designed for this level of customization.
For custom card layout and design, use the Adaptive Cards JSON schema. This way you can create card designs that meet your exact specifications.
For more information, see:

https://docs.microsoft.com/en-us/adaptive-cards/
http://adaptivecards.io/visualizer/
http://adaptivecards.io/samples/


Questions about CSE Loss

Hello, I 'm interested in your excellent work. And I have two questions when re-produce your work.

In line 210 of lmpt/train.py:
class_weights = sfm(torch.from_numpy(np.asarray(mmcv.load(freq_file)['class_freq'])).to(torch.float32).cuda()),
Why apply softmax on class_counts? After applying it, the result contains zeros, which influence the calculation of margin and
class_weights in csel.py (class_counts is as denominator). For example, for voc-lt, class_counts after softmax is like this:

In line 20 of lmpt/csel.py:
self.class_counts = self.class_counts.squeeze(dim=0).expand(labels.shape[0], self.class_counts.shape[-1]),
after this line, self.class_counts has two dimensions: [batch_size, n_cls]. But in line 25, it requires self.class_counts to have a
third dimension in torch.sum(dim=2):
class_weights = (1 / self.class_counts) ** self.gamma / torch.sum((1 / self.class_counts) ** self.gamma, dim=2)
I think the line 25 should be like this:
class_weights = (1 / self.class_counts) ** self.gamma / torch.sum((1 / self.class_counts) ** self.gamma, dim=1,
keepdim=True)

I would appreciate it if you could answer my confusions.

Hi @fmy7834 ,
Sorry for the late response.

As I mentioned in issue #3, using softmax for multi-label tasks is not optimal. You can improve performance by using functions such as sigmoid.

The code in this step is fine. For specific tensor shapes, please refer to issue #2, where I have provided detailed information on the shapes.

Thank you for your attention.


Unable to find component mqtt

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
SynoCommunity version beta
Python release (python3 --version):
3.5.1
Component/platform:
mqtt
Description of problem:
Unable to find component mqtt on synology and the same configuration.yaml on PC : it's OK !
Mosquitto is on the synology : 1.4.9-5
Expected:
Problem-relevant configuration.yaml entries and steps to reproduce:
# Track the sun
sun:

mqtt:
 broker: <IP_ADDRESS>
 port: 1883
 client_id: home-assistant-1

sensor:
 platform: mqtt
 state_topic: "capteur/temperature"
 name: "Temperature"
 qos: 0
 unit_of_measurement: "C"

Traceback (if applicable):
17:08 14-03-17 homeassistant.loader: Unable to find component mqtt
17:08 14-03-17 homeassistant.loader: Unable to find component updater
17:08 14-03-17 homeassistant.loader: Unable to find component introduction
17:08 14-03-17 homeassistant.loader: Unable to find component sensor.mqtt
17:08 14-03-17 homeassistant: hass.local_api is deprecated. Use hass.config.api

Additional info:

The Indentation looks wrong. Did your configuration file pass the configuration check?

How one tests the configuration with home assistant version 20150526-1 of SynoCommunity ?
I'm newbie !

@claudius61 it might just be an copy paste issue here on github, but if that indention is the one you have in your configuration:

take a look at Troubleshooting Your Configuration and the YAML idiosyncrasies
sub-properties must be indented by two spaces per level and tabs are not allowed.

I have give up home assisting version 20150526-1 of SynoCommunity for the installation of home-assistant.io;
that functions correctly.
Thank you for your councils.


PDO_SQLSRV returns everything as a string

Driver version or file name
4.3.0+9905
SQL Server version
Irrelevant
Client operating system
Windows
PHP version
7.1.7 x64 (From WebPI)
Microsoft ODBC Driver version
phpinfo() shows ODBCVER | 0x0350
Table schema
Irrelevant
Problem description
PDO_SQLSRV returns everything as a string.
Reference the post here https://stackoverflow.com/a/13756696/1384186 by Robert Calhoun on Dec 7 '12 and the point number 2 here https://github.com/Microsoft/msphpsql/issues/60 and the first paragraph of this page https://docs.microsoft.com/en-us/sql/connect/php/how-to-retrieve-date-and-time-type-as-strings-using-the-sqlsrv-driver stating

It is an error to use the ReturnDatesAsStrings connection option with the PDO_SQLSRV driver.

The SQLSRV driver apparently returns data as the correct type. The PDO_SQLSRV driver should also return data as the correct type. As it is now data returned from the PDO_SQLSRV driver that should be datetime or int is returned as string and must then be converted to to the correct data type manually.
Expected behavior and actual behavior
Expected: PDO_SQLSRV returns data in the type matching what it is in the database.
Actual: PDO_SQLSRV returns everything as a string.
Repro code
I am unsure where this might be in your repo.

Yes @nemchik PDO_SQLSRV returns dates as strings. However, for numeric columns like integers or floats (except decimals or numerics because we want to preserve accuracy) you can set the attribute PDO::SQLSRV_ATTR_FETCHES_NUMERIC_TYPE to true in order to fetch them as numeric values:
$conn = new PDO("sqlsrv:Server=$server;database=$dbName;", $uid, $pwd, $options);
$conn->setAttribute(PDO::SQLSRV_ATTR_FETCHES_NUMERIC_TYPE, true);

Hope this helps.

@yitam PDO::SQLSRV_ATTR_FETCHES_NUMERIC_TYPE accomplishes everything that I personally use except the date data types. Even with PDO::SQLSRV_ATTR_FETCHES_NUMERIC_TYPE dates are still returned as strings when using PDO, however dates are returned as dates with using the non PDO SQLSRV driver (as pointed out on the StackOverflow link).
Also it seems like the default behavior of the SQLSRV driver is to return data in its respective type, while the PDO_SQLSRV driver requires a special flag to enable this behavior. Wouldn't it make more sense for both drivers to behave the same out of the box and provide a flag for the PDO_SQLSRV driver that fetches all data as strings? (basically reverse the behavior)

I understand what you mean, but the PDO_SQLSRV driver has to conform to PHP PDO

@nemchik , you might find this particular tip from a user useful

I understand conforming to PHP PDO, and since PDO::SQLSRV_ATTR_FETCHES_NUMERIC_TYPE mostly meets my need I can live with that.
Do you have any plans to work on dates?

Not at this point as you can use existing built-in date time methods. I'll mark this as feature request, @nemchik

Hi @nemchik
If we are going to return datetime values as date time objects, we will not reuse the same flag PDO::SQLSRV_ATTR_FETCHES_NUMERIC_TYPE as this might be a breaking change to other people. It's likely we will introduce a new flag for this purpose.

I would be fine with it being a separate flag.

While I appreciate the accuracy and understand its purpose, my practical use of having the PDO_SQLSRV driver return dates as the non PDO driver does is just to skip the step of converting from string to date in PHP for the various uses I have for date data being pulled from a database. If it comes out in a date format already that is more convenient and takes a step out of my process for using the data in PHP. I would imagine it would also take a step out of the process the driver has to complete by not converting the date to a string on the driver end.
It's a trivial amount of effort to convert strings to dates in PHP, but it's >0 so I figured I would ask. If there is no possibility for an option like this to be added to the PDO driver that's understandable, but if it's something you would consider it could be beneficial.
As a side note I think it just makes sense to output dates as dates, just like numeric types come out as numeric types when using the flag. But that's just my opinion 😄

Yes @nemchik we are considering this feature request, but we want to make sure you are aware of the slight loss of accuracy as described above. :)

Closing this issue @nemchik. Feature already implemented in 5.4.0-preview


updated to support alternate link URLs

Fixes #783
For links, I propose adding the url property to the Link Object. When supplied, the url will be applied to the operation, effectively overriding the {scheme}://{host}/{basePath} value.
If the target operation defines any parameters, the following rules will be applied:

Path parameters will be ignored unless a substitution is provided in the url value
Query parameters may be ignored if supplied in the url value.  Tooling will effectively extract these parameters to satisfy the requirements of parameter definitions
Header parameters must be extracted from the response and passed as named parameters

Example definition:
paths:
  /2.0/users/{username}:
    get:
      operationId: getUserByName
      parameters:
      - name: username
        type: string
        in: path
        required: true
      responses:
        200:
          description: The User
          headers:
            X-link:
                type: string
                format: uri
          schema:
            $ref: '#/components/definitions/user'
          links:
            userRepositories:
              $ref: '#/components/links/UserRepositories'
  /2.0/repositories/{username}:
    get:
      operationId: getRepositoriesByOwner
      parameters:
        - name: username
          type: string
          in: path
          required: true
      responses:
        200:
          description: repositories owned by the supplied user
          schema:
            type: array
            items:
              $ref: '#/components/definitions/repository'
          links:
            userRepository:
              $ref: '#/components/links/UserRepository'
components:
  links:
    UserRepositories:
      operationId: getRepositoriesByOwner
      url: $responseHeaders.link
  definitions:
    user:
        type: object

Example request:
$ curl -I https://gigantic.server.com/2.0/users/fehguy
HTTP/1.1 200 OK
Date: Thu, 29 Sep 2016 04:20:52 GMT
Access-Control-Allow-Origin: *
Content-Length: 0
X-link: https://us-west.gigantic.server.com/alternate/path/0e6c11d79a/repositories

Following the response link would honor the definition provided in the getRepositoriesByOwner operationId.
Additional considerations:
When a url is provided, the single operation can target an alternate host and path combination.  Subsequent links from that targeted operation will be considered against the host as defined in the document, not the overridden host.  Thus if secondary links are required to reside on the alternate host, they must be supplied in the response from the alternate host.
The url field may be a relative url, allowing the existing scheme/host/basePath scheme to be used.

@OAI/tdc please review for discussion

All in all, thanks, this is a big step to supporting HATEOAS. :+1:

I just wrote a 1000 words about why I think this change is a really bad idea and moments before clicking the "comment" button I convinced myself I'm wrong.
However, I still see two issues with this proposal:

Adding the url property really highlights to me the risks of having reusable link definitions that are dependant on the structure of the referencing request/response.  There is a big risk that this will introduce rigidity in a design.  e.g.  In order to make this link definition reusable, we have to ensure that every response returns the {tenant} parameter in exactly the same place in the response.  The use of "parameters" creates a certain amount of isolation, but this still concerns me.  Being able to override certain values when doing a $ref would be really nice, but I realize that just isn't possible with the way $ref works.

The example oversimplifies the issue because it only has one link header and does not use the standardized format for links appearing in headers as defined in RFC 5988.  The official link header format has a rel value that allows your to describe the type of link and enables multiple headers to be included and still distinguish between them.  Supporting link headers properly would require tooling to parse link header syntax and we would need to add to the specification an expression syntax to reach into  that link header object.

This change significantly increases the scope of what we were trying to achieve with the original static description of relations between operations.  That was my initial objection, but I do think I see a glimmer of light at the end of the tunnel that this might actually enable useful description of dynamic hypermedia APIs.  If we are going to open the door to allowing dynamic characteristics I think we need acknowledge a couple of extra realities.

Although a link description might be present in the response definition, the actual runtime response may not include the link header that provides the URL.  Tooling needs to deal with that.
Of the small minority of people that build hypermedia apis, only a small minority of them use link headers to communicate links.  Most people use the response body.  Developers are going to use this mechanism to reach into the body.  We need to recognize that and understand the consequences.

.... so much for, oh, I'll just go add a thumbs up to that PR.... :-)

I'm trying to understand the need for this change, but am having a hard time following #783. I'm looking at @lcrabb's examples for Option 1 and Option 2 and can't see a difference between them - potentially the late hour.
I don't fully understand the need for a dynamic scheme/host/basepath when linking an operation. I understand there's no way to override it right now in the link definition, just can't understand the use case for it and would appreciate a sample (realistic) use case to fully grasp the need. Without it, it's hard for me to vote in a change that has no concrete need (and I'm not doubting there is one).
Part of the concern is for regularly defined operations, we do not allow the scheme/host/basepath to be defined dynamically. You can override the top level definition, but at the operation level itself, this is fixed. We're ending up providing extra functionality here. This will not be the case if we end up supporting host and basepath templating, but then we won't really need this PR at all.
Details-wise, the proposal itself looks good, I just have a few questions/clarifications.

The example in the PR comment itself (i.e. here and not in 3.0.md) uses url: $responseHeaders.link in the definition and X-link: https://us-west.gigantic.server.com/alternate/path/0e6c11d79a/repositories in the curl example. Making sure here this is a minor error and it should either be url: $responseHeaders.x-link in the spec or link: https://us-west.gigantic.server.com/alternate/path/0e6c11d79a/repositories in the curl output.

The above example should also be included in some form in the spec itself - it explains the use in a clearer way than the proposed text only.

href and operationId are mutually exclusive. It sounds like url can only be combined with operationId. If not, then the behavior should be clarified (field order can be fixed in the documentation cleanup).

If I understand correctly, #783 is talking only about changing the scheme/host/basepath. This PR also talks modifying path parameters and query parameters. Again, while this may have a use, I can't help but feel it introduces a complexity that will be used by not even the 20% (less than 1%?) and is not worth the overhead it introduces to the tooling.

When the url attribute is provided, the target host may be overridden by the value provided.

It sounds like it MUST be overridden.

Assuming we choose to proceed with the support for overriding path and query parameters, the format of the query parameter representation should be clarified (?foo&bar vs ?foo=&bar=).

and the absence of a required query parameter will result in an invalid request.

How is a required query parameter defined? Or once it's in the URL it's required?

I'm waiting with my vote on this, hoping to get some clarifications before.

Looks like we will not be supporting this in 3.0 but consider for 3.x
example:
response header:
  link: https://na2.foo.bar.com/users/tony/sensitiveData?token=abcd1234

target operation:
server:
  url: http://foo.bar.com/v2

paths:
  /{user}/sensitiveData:
    get:
      server:
        url: {scheme}://{host}/{basePath}
      parameters:
      - in: path
        name: user
        #...

@darrelmiller I'd be interested in seeing your original 1000 word counter-argument. I'd also be interested in seeing some specific examples where such a thing would be useful. I am very much interested in seeing how we can support navigation through the data in the body. I'm less clear on the value of supporting navigation through headers that are detached from the data... that does not seem like "hateos"y to me. I could see header-born links being useful for certain meta-service references.

@cfineman From an architectural perspective, whether the links are in the header or body it really doesn't make a difference.  However, the whole notion of discovering resources via URLs in responses is counter to the idea of describing resources in a description document.  It is possible there is an effective hybrid that can exist but I fear we don't have time to get it right for 3.0 so we're punting for the moment.

@fehguy Based on your label edits, I've updated the "Milestone" on this to v3.Next so it's off the radar for OAI v3.0.0.  If you think this should be on the radar for v3.0.0, please update the milestone.


Merge pull request #11 from jennymhkao/main

Merge pull request #10 from jennymhkao/gh-pages

update


Ability to trigger event handlers manually.

@RandomEtc suggests something like jQuery's trigger operator. The docs suggest it creates a proper DOM event and dispatches it to the selected elements (plural?).

@mbostock  Hi, Mike. I got a similar question about triggering D3 drag action manually. Suppose there are two layers:  the top layer is a PATH, and bottom layer is a RECT, the path block the RECT.  How can I apply the drag action to RECT while still make the PATH respond to mouse over event?

+1

I'm currently using the following to trigger events on a selection.
 d3.selection.prototype.trigger = function( event ) {
     var e = document.createEvent('Event');
     e.initEvent( event, true, true);
     this.node().dispatchEvent( e );
     return this;
 }

I've also created a few other helpers for items such as scrollTop

That is similar to the selection.dispatch method that is currently planned for D3 4.0. Though selection.dispatch dispatches an event to every selected node, not just the first one.

Ah yes so I would need an each in their to loop across all the events in the selection. In my use case I've only being using it in a scalar selection context. The below appears to work for the selection case.
d3.selection.prototype.trigger = function( event ) {
    var e = document.createEvent('Event');
    e.initEvent( event, true, true);
    this.each( function( d ) {
        this.dispatchEvent( e );
    });
   return this;
}

I don’t think you’re supposed to dispatch the same event more than once. If you want my recommendation, see the selection.dispatch implementation. :grin:

+1

+1

NAVER - http://www.naver.com/
<EMAIL_ADDRESS>님께 보내신 메일 <Re: [d3] Ability to trigger event handlers manually. (#100)> 이 다음과 같은 이유로 전송 실패했습니다.

받는 사람이 회원님의 메일을 수신차단 하였습니다.

Closing as fixed in d3-selection for 4.0; see selection.dispatch.


Improve the bundle build process for the operator

Always call gen-latest-csv before building the bundle. Generate & Update the bundle Dockerfile each time. Simplify the hack/build-operator-bundle.sh script.

/retest

/test ocs-operator-bundle-e2e-aws

/test ocs-operator-bundle-e2e-aws


PostgreSQL running out of remaining connections

Environment info

NooBaa Version: PR #6428

Actual behavior
After generating about 20k events some endpoints and the core are starting to show this error:
�[32mMar-31 11:04:18.611�[35m [Endpoint/12] �[31m[ERROR]�[39m core.util.postgres_client:: find failed { last_update: { �[32m'$gte'�[39m: �[33m1617188553553�[39m } } { projection: { last_update: �[33m0�[39m } } SELECT data #- '{last_update}' as data FROM tiers WHERE data->'last_update'>='1617188553553'::jsonb error: remaining connection slots are reserved for non-replication superuser connections
    at Parser.parseErrorMessage (/root/node_modules/�[4mnoobaa-core�[24m/node_modules/�[4mpg-protocol�[24m/dist/parser.js:278:15)
    at Parser.handlePacket (/root/node_modules/�[4mnoobaa-core�[24m/node_modules/�[4mpg-protocol�[24m/dist/parser.js:126:29)
    at Parser.parse (/root/node_modules/�[4mnoobaa-core�[24m/node_modules/�[4mpg-protocol�[24m/dist/parser.js:39:38)
    at Socket.<anonymous> (/root/node_modules/�[4mnoobaa-core�[24m/node_modules/�[4mpg-protocol�[24m/dist/index.js:10:42)
�[90m    at Socket.emit (events.js:315:20)�[39m
�[90m    at Socket.EventEmitter.emit (domain.js:467:12)�[39m
�[90m    at addChunk (internal/streams/readable.js:309:12)�[39m
�[90m    at readableAddChunk (internal/streams/readable.js:284:9)�[39m
�[90m    at Socket.Readable.push (internal/streams/readable.js:223:10)�[39m
�[90m    at TCP.onStreamRead (internal/stream_base_commons.js:188:23)�[39m {
  length: �[33m140�[39m,
  severity: �[32m'FATAL'�[39m,
  code: �[32m'53300'�[39m,
  detail: �[90mundefined�[39m,
  hint: �[90mundefined�[39m,
  position: �[90mundefined�[39m,
  internalPosition: �[90mundefined�[39m,
  internalQuery: �[90mundefined�[39m,
  where: �[90mundefined�[39m,
  schema: �[90mundefined�[39m,
  table: �[90mundefined�[39m,
  column: �[90mundefined�[39m,
  dataType: �[90mundefined�[39m,
  constraint: �[90mundefined�[39m,
  file: �[32m'postinit.c'�[39m,
  line: �[32m'828'�[39m,
  routine: �[32m'InitPostgres'�[39m
}

After restarting all pods, all endpoints and the core show the error. As far as i can tell everything still keeps working.
Expected behavior

No error

Steps to reproduce

Create a function
Create a bucket
Set a trigger on the bucket to fire the function on ObjectCreated event
Upload 10000-20000 objects (size does not matter) to the bucket

Could it be, that multiple endpoints worsen this? a fresh install with 10 endpoints already throws this error..

@lallinger-arbeit this error is thrown by PostgreSQL when exceeding the max_connections which is the maximum number of concurrent connections the DB is configured to handle (see here).  We are not changing the default which is 100 connections
for each process (endpoints included) we are using an internal connection pool with a max size of 10 connections, so multiple endpoints can definitely worsen it. When you first encountered it, how many endpoints were running?

@lallinger-arbeit this error is thrown by PostgreSQL when exceeding the max_connections which is the maximum number of concurrent connections the DB is configured to handle (see here). We are not changing the default which is 100 connections

so 10 endpoints would quite definitely exceed the current settings?

When you first encountered it, how many endpoints were running?

first i only used 3

10 endpoints are likely to hit this issue, but with 3 endpoints we shouldn't get to more than 60 connections.
It would be helpful if you can reproduce with 3 endpoints and attach the logs here (also DB logs). I will also try to reproduce it.

i'll try to reproduce, but probably won't have time to do it until end of next week..

@liranmauda are you tracking the remaining connections issue here or somewhere else? if you track it somewhere else this can be closed

@dannyzaken ^^


Fix: dependencies

a clean npm install will currently fail due to updates to packages causing dependancy issues so locking down current dependancies to specific versions.

@jamesjwarren / @peeklondon pls take a 👀

👍


Revert

Execution result of run-all plan in infrastructure/cloud :
time=2023-10-19T21:12:36Z level=info msg=The stack at /github/workspace/infrastructure/cloud will be processed in the following order for command plan:
Group 1
- Module /github/workspace/infrastructure/cloud/b2/bucket
- Module /github/workspace/infrastructure/cloud/cloudflare/access
- Module /github/workspace/infrastructure/cloud/cloudflare/tunnel

Group 2
- Module /github/workspace/infrastructure/cloud/cloudflare/dns

Initializing the backend...

Initializing the backend...

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Reusing previous version of hashicorp/aws from the dependency lock file

Initializing provider plugins...
- Reusing previous version of backblaze/b2 from the dependency lock file

Initializing provider plugins...
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of integrations/github from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- Installing cloudflare/cloudflare v4.16.0...
- Installed cloudflare/cloudflare v4.16.0 (self-signed, key ID C76001609EE3B136)
- Installing integrations/github v5.40.0...
- Installed integrations/github v5.40.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)
- Installing hashicorp/aws v5.21.0...
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file
- Reusing previous version of integrations/github from the dependency lock file
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of integrations/github from the dependency lock file
- Installing integrations/github v5.40.0...
- Installing backblaze/b2 v0.8.4...
- Installed integrations/github v5.40.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)
- Installing hashicorp/aws v5.21.0...
- Installed backblaze/b2 v0.8.4 (signed by a HashiCorp partner, key ID 83D9CAF4848490D6)
- Installing cloudflare/cloudflare v4.16.0...
- Installed cloudflare/cloudflare v4.16.0 (self-signed, key ID C76001609EE3B136)
- Installing integrations/github v5.40.0...
- Installed integrations/github v5.40.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)
- Installing hashicorp/aws v5.21.0...
- Installed hashicorp/aws v5.21.0 (signed by HashiCorp)
- Installing backblaze/b2 v0.8.4...
- Installed backblaze/b2 v0.8.4 (signed by a HashiCorp partner, key ID 83D9CAF4848490D6)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!
- Installed hashicorp/aws v5.21.0 (signed by HashiCorp)
- Installing backblaze/b2 v0.8.4...
- Installed backblaze/b2 v0.8.4 (signed by a HashiCorp partner, key ID 83D9CAF4848490D6)
- Installing cloudflare/cloudflare v4.16.0...
- Installed cloudflare/cloudflare v4.16.0 (self-signed, key ID C76001609EE3B136)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!
- Installed hashicorp/aws v5.21.0 (signed by HashiCorp)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!
cloudflare_access_policy.aws: Refreshing state... [id=3be53152-3953-42b9-9c3f-845755693a57]
cloudflare_access_application.this: Refreshing state... [id=bcaa03ae-0a94-42ad-935c-487ca0a80723]
data.github_ip_ranges.this: Reading...
data.github_ip_ranges.this: Read complete after 0s [id=github-ip-ranges]
cloudflare_access_policy.github: Refreshing state... [id=2a1fc41f-8d41-4f1f-8e72-91b0970ab129]
cloudflare_access_policy.this: Refreshing state... [id=1b62d9cb-f555-4d23-b815-dfe3f92bd2a1]
cloudflare_tunnel.this: Refreshing state... [id=de250703-6c08-400d-b568-bc0aa34cabaf]

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  - destroy

Terraform will perform the following actions:

  # cloudflare_access_policy.aws will be destroyed
  # (because cloudflare_access_policy.aws is not in configuration)
  - resource "cloudflare_access_policy" "aws" {
      - application_id = "bcaa03ae-0a94-42ad-935c-487ca0a80723" -> null
      - decision       = "bypass" -> null
      - id             = "3be53152-3953-42b9-9c3f-845755693a57" -> null
      - name           = "AWS IP List" -> null
      - precedence     = 3 -> null
      - zone_id        = (sensitive value) -> null

      - include {
          - any_valid_service_token = false -> null
          - certificate             = false -> null
          - device_posture          = [] -> null
          - email                   = [] -> null
          - email_domain            = [] -> null
          - everyone                = false -> null
          - geo                     = [] -> null
          - group                   = [] -> null
          - ip                      = [
              - "<IP_ADDRESS>/26",
              - "<IP_ADDRESS>/18",
              - "<IP_ADDRESS>/26",
              - "<IP_ADDRESS>/26",
              - "<IP_ADDRESS>/25",
              - "<IP_ADDRESS>/25",
              - "<IP_ADDRESS>/25",
              - "<IP_ADDRESS>/25",
              - "<IP_ADDRESS>/25",
              - "<IP_ADDRESS>/25",
              - "<IP_ADDRESS>/26",
              - "<IP_ADDRESS>/26",
              - "<IP_ADDRESS>/26",
              - "<IP_ADDRESS>/26",
              - "<IP_ADDRESS>/26",
              - "<IP_ADDRESS>/26",
              - "<IP_ADDRESS>/26",
              - "<IP_ADDRESS>/26",
              - "<IP_ADDRESS>/26",
              - "<IP_ADDRESS>/26",
              - "<IP_ADDRESS>/26",
              - "<IP_ADDRESS>/26",
              - "<IP_ADDRESS>/26",
              - "2400:7fc0:83cc:cc00::/56",
              - "2400:7fc0:83cc:cd00::/56",
              - "2400:7fc0:83cc:ce00::/56",
              - "2404:c2c0:83cc:cc00::/56",
              - "2404:c2c0:83cc:cd00::/56",
              - "2404:c2c0:83cc:ce00::/56",
              - "2406:da14:7ff:f800::/56",
              - "2406:da14:fff:f800::/56",
              - "2406:da18:7ff:f800::/56",
              - "2406:da18:fff:f800::/56",
              - "2406:da1c:7ff:f800::/56",
              - "2406:da1c:fff:f800::/56",
              - "2600:1f14:7ff:f800::/56",
              - "2600:1f14:fff:f800::/56",
              - "2600:1f18:3fff:f800::/56",
              - "2600:1f18:7fff:f800::/56",
              - "2600:1f1c:7ff:f800::/56",
              - "2600:1f1c:fff:f800::/56",
              - "2600:1f1e:7ff:f800::/56",
              - "2600:1f1e:fff:f800::/56",
              - "2a05:d018:7ff:f800::/56",
              - "2a05:d018:fff:f800::/56",
            ] -> null
          - ip_list                 = [] -> null
          - login_method            = [] -> null
          - service_token           = [] -> null
        }
    }

Plan: 0 to add, 0 to change, 1 to destroy.

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
b2_bucket.this: Refreshing state... [id=62c5440382b735a482bf081b]
data.github_ip_ranges.this: Reading...
data.github_ip_ranges.this: Read complete after 0s [id=github-ip-ranges]

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Reusing previous version of integrations/github from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of backblaze/b2 from the dependency lock file

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
- Installing cloudflare/cloudflare v4.16.0...
- Installed cloudflare/cloudflare v4.16.0 (self-signed, key ID C76001609EE3B136)
- Installing integrations/github v5.40.0...
- Installed integrations/github v5.40.0 (signed by a HashiCorp partner, key ID 38027F80D7FD5FB2)
- Installing hashicorp/aws v5.21.0...
- Installed hashicorp/aws v5.21.0 (signed by HashiCorp)
- Installing backblaze/b2 v0.8.4...
- Installed backblaze/b2 v0.8.4 (signed by a HashiCorp partner, key ID 83D9CAF4848490D6)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

Terraform has been successfully initialized!
cloudflare_record.public_record: Refreshing state... [id=16e19a8901e14239e7345e3922f318f9]
cloudflare_record.internal_record["argocd_internal"]: Refreshing state... [id=ad2633b9ce86a1786416dd851cb5c4d3]
cloudflare_record.internal_record["kiali_internal"]: Refreshing state... [id=3e29d0bc6567b4c0fecd6db58e432160]
cloudflare_record.internal_record["adguard_internal"]: Refreshing state... [id=5803590e9218027a34aae666383f8211]
cloudflare_record.internal_record["jellyfin_internal"]: Refreshing state... [id=62786f77078b02d784342427605ba9e9]
cloudflare_record.internal_record["sftpgo_internal"]: Refreshing state... [id=d53e66b848b3967bd5a9885eb2c8e08c]
cloudflare_record.internal_record["longhorn_internal"]: Refreshing state... [id=9d9e7849509ddd1ca1420bfb93085ddb]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.


(maint) update facts-blacklist docs

update and move facts blacklist docs to the correct section

Build finished.
Test PASSed

Test PASSed


Fixed #573 ByteBuf reference counting

The reworks most of the ByteBuf reference counting by moving all buffer release/retain calls to the outside interfaces of moquette.
This supersedes #576 and is based on the discussion there.
Close #576
Close #599
Fix #573

Hi @hylkevds I was working on master creating a unit test that exposes any buffer leak in Netty, but was unfruitful. My test are on #602 could you share how do you test it?

Testing for memory leaks with unit tests is generally very difficult, even if you know exactly what you're looking for.
Most of the time I just use small program that pushes a lot of messages in batches through several clients that regularly subscribe, unsubscribe and reconnect. You can find that here: https://github.com/hylkevds/moquetteTests/
Some characteristics of the load generator that tend to expose problems:

Multiple clients on the same topic
Clients that unsubscribe and re-subscribe
Clients that disconnect and re-connect
publishers that put out messages in batches. This ensures that buffers fill up, and then have a chance to empty again

The load generator keeps track of counts of sent and received messages, one per second. The sent/receive counts never really match exactly when clients unsubscribe and resubscribe, but they do give a quick overview if things are still running as expected. That is for instance how I found the deadlock problem with QOS2 (#587)
I just run it in the profiler in Netbeans, so I can track memory usage and object generations. If memory usage increases significantly over an hour or so, you know there is an issue...
For shorter tests, setting the Netty leak detection to paranoid also helps.


Lack of explicit box-sizing causes the badge to be the wrong size

I had * { box-sizing: border-box;} in the css of my page, and for whatever reason this leads to the hover width being miscalculated and too short to reveal the entire username.
Turns out I have no idea why that was in my css so I've removed it, but it seems like something that should be set explicitly to whatever the default value is rather than being at the whim of whatever is in the global css?

@CDWimmer, thanks for the feedback! I will work on a fix ASAP.


Which reasoning is currently included in the data?

Awesome work, folks! In the data structure, you include:
- query: the query for retrieval
- reasoning: the required reasoning to retrieve documents

The paper discusses generating the reasoning via many LLMs, like GPT-4 or others. Which LM is involved in the released data?

Thanks a lot for the question! The reasoning field in the released dataset is annotated by humans and is not used in any experiment throughout the paper.

Thank you! That makes sense and should probably be clarified because it’s an important detail

Feel free to re-open the issue if you have further questions!


fix(wsk): fix hanging openwhisk actions

I don't really understand why, but changing the finally() function from returning a value to a block solves our hanging actions problems.....maybe because returning a promise from the finally block makes it hanging but when it's returned into the same scope, it is not?
maybe something todo with unresolved promises and node 12?

@tripodsan Thanks for that, we are reviewing.

:tada: This PR is included in version 1.105.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

BTW, I'm not sure if this was a good fix. it turns out, that there is different behaviour on macos and linux (I didn't test windows).
with this new version on macos, the trace is sent before the response is returned.
but on linux, the trace is send after the response is returned.
I'll do some more testing....

@ranrib it would be cool, if someone from your team could investigate our linux problem. it is easily reproducible here: https://github.com/adobe/helix-epsagon/issues/157

Yes we will investigate this


Create Linux-shortcuts.md

Hello @nakul010
Linux cheatsheet is already present in the list. You can update that, with your content.
Thank you

Hey @Suryansh1720001 made changes in existing Linux cheatsheet.
Thank you


Integration tests for PR functionality when issues are disabled

Need integration tests for #2710

I've created some tests. But I'am not sure if they work properly and if they test everything needed.
My branch: https://github.com/go-gitea/gitea/compare/master...JonasFranzDEV:integration-test-pr?expand=1
Is there a good way to test integration tests locally? drone cli does not work for some reason.

@JonasFranzDEV You can run it same as make test but you need database up and running. I use 2 docker containers (gitea and db) on same custom network.

@Morlinest could you send me your docker commands or docker-compose file?

@JonasFranzDEV I am using my own image (#2377), but you can try something like this (I can't test it because I can't mount local volumes now):
docker network create gitea-test
docker run -d --rm --net gitea-test -e POSTGRES_DB=test --name pgsql postgres:9.5
docker run -i --rm --net gitea-test -v <MY-PROJECT-PATH>:/srv/app/src/code.gitea.io/gitea -w /srv/app/src/code.gitea.io/gitea --net gitea -e TAGS="bindata" webh
ippie/golang:edge make clean generate build test-pgsql

Change <MY-PROJECT-PATH> for your path to project.

This issue is about that that when issues in repository is disabled in PR it was not possible (tests must test that is possible) to:

Add/remove labels
Set/remove milestone
Set/remove assignee
Add/change/delete comment
Start/stop/add timetracking
Close PR
Multi-PR actions from PR list


[CWS] change windows self test to use create.file.path

What does this PR do?
With the goal of having a discarder on create.file.path, we need the self test to use the path otherwise discarder will not be generated because this field is not used in the rule. This PR fixes this by using the path field (similarly to what is done with open events on linux).
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Can the shipyard work on production environment?

Can the shipyard work on production environment? Thanks.

Yes
On Oct 28, 2016 11:15 PM, "All for mysql branch."<EMAIL_ADDRESS>wrote:

Can the shipyard work on production environment? Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/shipyard/shipyard/issues/896, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAP6IqFcHb5HkLC6vXift0tuNJoWVC79ks5q4ro2gaJpZM4KkAqN
.

Thanks very much.

Thanks.


docs: Update Showcase Dynamic plugins documentation to remove the part related to the old backend system

Fix for RHIDP-1325

Thanks for the review @davidfesta l I made the requested changes.

/lgtm

/lgtm


Feature to automatically encrypt title keys?

Now that it is trivial to dump the bootroms it would be nice if new title keys would be automatically encrypted (by reading the keys from boot9.rom) rather than it having to be done manually.

Really simple C program that will allow encrypting title keys purely on PC:

This has already been implemented
https://github.com/TomEke/WiiU-Title-Key/blob/master/app/Title.php#L17

Ah, my code/references were actually in regards to the 3DS titlekeys, not the WiiU ones, but this is the only place I could reach you 👍
With the new bootrom dump, it's now possible to do all the encryption entirely on the PC, no more having to manually copy things around and run stuff on the 3DS

It is exactly the same on the 3DS side and has been implemented.
I left the comment in my usual HTML comment about it.

Oh weird, cause I know the other week there was a gap of a few days where keys were sitting in a decrypted-only state.
I'm not seeing that function called anywhere, is it not actually hooked up yet? Or is it something not done automatically on submission?

The other week, bootrom wasn't dumped yet.
It is done automatically when submitted on the backend.

Ah okay.
Looking at that function, it actually looks to be doing a decrypt instead of encrypt?
Function to support encrypting, if you want to auto encrypt on submit of decrypted keys:
    public function getEncTitleKey() {     	$encTitleKey = openssl_encrypt(hex2bin($this->titleKey), 'AES-128-CBC', hex2bin(env('COMMON_KEY')), OPENSSL_RAW_DATA, hex2bin($this->titleID . "0000000000000000"));         return bin2hex(substr($encTitleKey, 0, 16));     }

Yes. On the WiiU site I only store encrypted keys. The 3DS version is different and stores both and will generate a encrypted key when a decrypted key is set. I will begin work on removing decrypted keys on the 3DS page soon.

Also your implementation would not work as there are two different 0x3D keys

Hmm, according to the spreadsheet I found there's 6 normal keys for 0x3D. eShop, System, and 4 unknown.
Shouldn't everything coming from the eShop be using the same one though?

The database includes system titles from the CDN, not just eShop titles.

Ahhh, okay, that makes sense 👍

Just tested a system application (System Settings JPN to be specific), as well as a full comparison of encTitleKeys.bin vs decTitleKeys.bin encrypted using the above PHP, and it all seems to match up:
E:\Projects\3ds\boot9>php key.php TitleId:<PHONE_NUMBER>020000 Decrypted Key: 30f06ec42fa469aaXXXXXXXXXXXXXXXX Encrypted Key: 91d040a371be6aXXXXXXXXXXXXXXXXXX Expected EncKey: 91d040a371be6aXXXXXXXXXXXXXXXXXX

Are you comparing on real 3ds? My implementation was previously wrong as no one uses the System Application keys.

Ohhh, no, I was comparing against the current list of encrypted system titlekeys on the site.

I believe removing the decrypted 3ds title keys will break certain programs such as 3dsestuff which is useful to have a pc side backup (ciangel is slow when creating cia files).

Shouldn't everything be creating CIAs with the encrypted key in the ticket anyways?

I will not remove the code yet but will in the future. I will probably remove the decrypted title keys from the main page first.


[BUG] StageAward is incorrected awarded for FullComboW3 in Stats.xml

Is there an existing issue for this?

[X] I have searched the existing issues and none matched.

Operating System
Windows
CPU
No response
GPU
No response
Storage
No response
Game Version
4.18.1
Game Mode
dance
Theme
Simply Love release branch as of 1/1/2023
Describe the problem
Compared to a vanilla ITGMania stats.xml, outfox seems to treat the "StageAward" value differently. See the following stats.xml for ITGMania,

ITGMania Stats
<NumTimesPlayed>1</NumTimesPlayed>
<LastPlayed>2023-01-16</LastPlayed>
<HighGrade>Tier07</HighGrade>
<HighScore>
<Name>EVNT</Name>
<Grade>Tier07</Grade>
<Score>190997045</Score>
<PercentDP>0.919300</PercentDP>
<SurviveSeconds>149.020355</SurviveSeconds>
<MaxCombo>146</MaxCombo>
<StageAward></StageAward>
<PeakComboAward></PeakComboAward>
<Modifiers>2.5x, Overhead</Modifiers>
<DateTime>2023-01-16 16:45:02</DateTime>
<PlayerGuid></PlayerGuid>
<MachineGuid>0671473336b32a27</MachineGuid>
<ProductID>1</ProductID>
<TapNoteScores>
<HitMine>0</HitMine>
<AvoidMine>0</AvoidMine>
<CheckpointMiss>0</CheckpointMiss>
<Miss>2</Miss>
<W5>1</W5>
<W4>0</W4>
<W3>13</W3>
<W2>62</W2>
<W1>245</W1>
<CheckpointHit>0</CheckpointHit>
</TapNoteScores>
<HoldNoteScores>
<LetGo>0</LetGo>
<Held>39</Held>
<MissedHold>0</MissedHold>
</HoldNoteScores>
...

Compared to a similar stats.xml generated from outfox.

Outfox stats.xml
<HighScoreList>
<NumTimesPlayed>1</NumTimesPlayed>
<LastPlayed>2023-01-16</LastPlayed>
<HighGrade>Tier06</HighGrade>
<HighScore>
<Name>BWAG</Name>
<Grade>Tier06</Grade>
<Score>191331583</Score>
<PercentDP>0.925900</PercentDP>
<SurviveSeconds>149.221069</SurviveSeconds>
<MaxCombo>189</MaxCombo>
<StageAward>FullComboW3</StageAward>
<PeakComboAward>1000</PeakComboAward>
<Modifiers>2.5x, FailImmediate, Overhead, Exactv2, Speed</Modifiers>
<DateTime>2023-01-16 16:34:28</DateTime>
<PlayerGuid>e043b14cf2bf6347</PlayerGuid>
<MachineGuid>01e059a7e189ac1f</MachineGuid>
<ProductID>1</ProductID>
<TapNoteScores>
<HitMine>0</HitMine>
<AvoidMine>0</AvoidMine>
<CheckpointMiss>0</CheckpointMiss>
<Miss>1</Miss>
<W5>0</W5>
<W4>0</W4>
<W3>17</W3>
<W2>66</W2>
<W1>239</W1>
<ProW5>0</ProW5>
<ProW4>0</ProW4>
<ProW3>0</ProW3>
<ProW2>0</ProW2>
<ProW1>0</ProW1>
<MaxScore>0</MaxScore>
<CheckpointHit>0</CheckpointHit>
</TapNoteScores>
<HoldNoteScores>
<LetGo>0</LetGo>
<Held>39</Held>
<MissedHold>0</MissedHold>
</HoldNoteScores>
...

Note, the ITGMania stats.xml correctly populates stageaward as empty for a non-full combo--whereas OutFox gives the player FullComboW3, which is incorrect. See here for more information,
https://itgmania.github.io/lua-for-itgmania/LuaAPI#Enums-StageAward
I came across this while debugging a new feature being added to SimplyLove:
https://github.com/Simply-Love/Simply-Love-SM5/pull/434
Describe what should happen
When a full combo is missed, "StageAward" should be set to empty--not FullComboW3.
Relevant Log output
No response

Finally figured out where this bug came from. Just fixed it.


[SPARK-49159] Enforce FieldDeclarationsShouldBeAtStartOfClass, LinguisticNaming and ClassWithOnlyPrivateConstructorsShouldBeFinal rules

What changes were proposed in this pull request?
This PR aims to enforce FieldDeclarationsShouldBeAtStartOfClass, LinguisticNaming and ClassWithOnlyPrivateConstructorsShouldBeFinal rules
Why are the changes needed?
To ensure future code quality.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.

cc: @dongjoon-hyun


Fix appearance of retry button of remote branch management dialog

As described in Issue #1768 ,
retry button of authentication management dialog appear as "[Object]".
This fixes it to apper as "Retry" with refresh icon.

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes

Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the mailing list/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage increased (+0.05%) to 73.907% when pulling 0c6bf81c243520c2d4d0d0d51549259a4fa70119 on node-red-hitachi:0.19-fix-i18n-project-message into f5e212ff1e11b851669e91903d06d2f4a4f7f916 on node-red:0.19.


How to remove html attributes on production build

What problem does this feature solve?
Normally we would add data-testid for easier integration test, however I don't want this on production build to avoid web scraping.
What does the proposed API of configuration look like?
Maybe on builtins config?

it seems you can custom html process logic yourself

@hardfist Do you have any example code?


Error loading godot_llm.gdextension

(running on mac book pro 2,3 GHz Intel Core i7 quad-core 16 GB 1600 MHz DDR3, Godot version 4.2stable)
Godot just doesn't let me open the extension and instead sends this error messages:
Can't open dynamic library: /Users/mauro/Desktop/Godot LLM Template/addons/godot_llm/bin/libgodot_llm.darwin.release.universal.dylib. Error: dlopen(/Users/mauro/Desktop/Godot LLM Template/addons/godot_llm/bin/libgodot_llm.darwin.release.universal.dylib, 2): Symbol not found: __ZNKSt3__115basic_stringbufIcNS_11char_traitsIcEENS_9allocatorIcEEE3strEv
Referenced from: /Users/mauro/Desktop/Godot LLM Template/addons/godot_llm/bin/libgodot_llm.darwin.release.universal.dylib (which was built for Mac OS X 14.0)
Expected in: /usr/lib/libc++.1.dylib
.
core/extension/gdextension.cpp:719 - GDExtension dynamic library not found: /Users/mauro/Desktop/Godot LLM Template/addons/godot_llm/bin/libgodot_llm.darwin.release.universal.dylib
Failed loading resource: res://addons/godot_llm/godot_llm.gdextension. Make sure resources have been imported by opening the project in the editor at least once.
so it's impossible to activate the plugin and run the project

Do you have any advice?

The current mac build relies on github action runner image, and gpu llama.cpp for x64 can't be built in the standard macos 14 image because of the lack of gpu there.
Also because of the fact that intel mac intel mac has been discontinued for some years, so I decided not to deal with this in my build. If you are interested in using the plugin on intel mac, build from source should be quite easy, something like:
          mkdir build
          cd build
          cmake .. --preset macos-metal-release
          cmake --build . --config Release -j $(sysctl -n hw.logicalcpu)

Ok! Thanks. Should I close the issue?

Sure


Add Node 18 LTS to Flake for example frontends

Description
Websocket example app depends on Nodejs, and (from a side conversation) a minimum version. This PR adds Node 18 LTS to to the Nix Flake, and rebuilds the Websocket relay lockfile. This means that if you run nix develop, you will have a consistent version of Node on your PATH.
Type of change

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

Test plan (required)
#worksonmymachine?
Screenshots/Screencaps

I think @bgins's fork had an issue on the version, which was fixed by the removal of svelte-lime. Nonetheless, good to include this min version anyway, in the flake.

Nonetheless, good to include this min version anyway, in the flake.

I don't even have Node installed globally, which is definitely a weird Nix person thing 😆


Nginx - Add trailing slash to urls

See: http://stackoverflow.com/questions/645853/add-slash-to-the-end-of-every-url-need-rewrite-rule-for-nginx/3912675#3912675

The Regular Expression translates to: "rewrite all URIs without any '.' in them that don't end with a '/' to the URI + '/'" Or simply: "If the URI doesn't have a period and does not end with a slash, add a slash to the end".
The reason for only rewriting URI's without dots in them makes it so any file with a file extension doesn't get rewritten. For example your images, css, javascript, etc and prevent possible redirect loops if using some php framework that does its own rewrites.

rewrite ^([^.]*[^/])$ $1/ permanent;

NOTE
Currently above rewrite turns POST request to GET request so I am not using it, see:

http://serverfault.com/questions/434205/nginx-https-rewrite-turns-post-to-get

You can try
location ~ ^([^.]*[^/])$ {
    return 307 $1/$is_args$args;
}

It's recommended way (bit faster) and HTTP 307: The target resource resides temporarily under a different URI and the user agent MUST NOT change the request method if it performs an automatic redirection to that URI.


updated kops download links to the latest version

1.6.1 -> 1.7.0

This change is

CLA signed


Migrate to Manifest V3 in Firefox

There's some branching currently based on browser because for some time, Firefox only supported MV2 and Chrome was removing support for MV2 in favor of MV3. Now, Firefox supports MV3 (matching Chrome, hopefully), so some branching logic can be removed. (particularly background and content scripts, which are always tricky to wrangle).
https://extensionworkshop.com/documentation/develop/manifest-v3-migration-guide/
This is as of Firefox 109 (Jan 2023), so it should have 99%+ support.

Running into an issue here. Firefox treats host_permissions as optional, and the user has to explicitly enable them through the UI. So it's a few clicks via the addons menu to simply grant access to the desmos.com pages.

https://discourse.mozilla.org/t/missing-options-to-allow-automatic-execution-of-content-script/127651
https://discourse.mozilla.org/t/request-permissions-at-install-time-manifest-v3/121543/7
https://bugzilla.mozilla.org/show_bug.cgi?id=1839129
https://fosdem.org/2024/schedule/event/fosdem-2024-2412-firefox-android-and-cross-browser-webextensions-in-2024/

Note this code in a background script doesn't work. It gives the error "Uncaught (in promise) Error: permissions.request may only be called from a user input handler". So we need the user to do some interaction. But we can't make popups or anything, so they'll have to figure out on their own to click the addons menu. Ugh, I don't think this will work out.
const HOST_PERMISSIONS = {
  origins: ["https://*.desmos.com/*"],
};

// Necessary since Firefox doesn't grant host_permissions by default.
async function onInstall() {
  const good = await chrome.permissions.contains(HOST_PERMISSIONS);
  if (good) return;
  await chrome.permissions.request(HOST_PERMISSIONS);
}

chrome.runtime.onInstalled.addListener(() => {
  void onInstall();
});


Add Balancer and Bancor to the price pools

Is your feature request related to a problem? Please describe.
The top five DEX for stablecoins are Curve, Uni, Sushi, Balancer and Bancor. The price ratio betwen the token and stablecoin is what we are interested to extract.
Describe the solution you'd like
Work out price pools in Balancer and Bancor
Describe alternatives you've considered
Curve is also relevant to stablecoins, too.
Additional context

Balancer: https://github.com/credmark/credmark-models-py/pull/176


Remote help crash

used remote machine:
https://rtvs-devserver1:5444#1
not sure if the #1 param is involved.
tried "?help", then typed in some search terms.  crashed:

frown data sent already.

Works for me in both forms of the URL

did you type stuff in the search window?
On Thu, Mar 2, 2017 at 10:00 AM, Mikhail Arkhipov<EMAIL_ADDRESS>wrote:

Works for me in both forms of the URL
[image: image]
https://cloud.githubusercontent.com/assets/12820357/23520281/184959b0-ff2f-11e6-93b9-3557e1266938.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/RTVS/issues/3250#issuecomment-283729984,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtUVG7wNg95bFN-mcaYgbC2O8IHruhJks5rhwPTgaJpZM4MQRiH
.

Yes

No user reports on this. Closing.


Project public view: provide a description about regions the project serves

As user browsed the projects, they didn't know which areas the project serves and what provinces and territories are within each region.

Don't show regions, always show provinces and territories.

@cherylhjli can you have look at this?


Fix feat dynamic modificators

just a little fix about dynamic modificators for all feats

Looks good, merging.


Make highlighting of errors and warning synchronized with errors and warnings popup show and hide

Problem Description
This is a feature/enhancement proposal.
Currently, hovering over an error or a warning icon in the linenumber panel of the Editor makes a tooltip instantly appear with a description of the errors/warnings and also highlight the corresponding errors/warnings in the Editor.
As soon as the mouse cursor is moved outside of the icon location, the tooltip disappears. However, the clearing of the highlights is on a 500 ms timer. In my opinion, this makes the highlighting of errors and warnings a little bit clumsy and irritating, because sometimes, the highlights are cleared very quickly, while at other times, it seems to take forever for them to be cleared.
I think the highlighting of the errors and warnings in the text should be sync with the showing and hiding of the errors and warnings tooltip and should not use a timer.
What do you guy think?
Versions

Spyder 4.0.0.dev0 (Commit: 5e72dd504)
Python 3.7.1 64-bit | Qt 5.9.6 | PyQt5 5.9.2 | Windows 10

I agree with this.

Cool! It is a very simple fix, so I will take care of this shortly.

Thanks!

This is blocked by https://github.com/spyder-ide/spyder/issues/9631.


I want to create a genesis block and start from that genesis block. Is there a document to refer to? I want to change the merkle root and genesis block

I want to create a genesis block and start from that genesis block. Is
there a document to refer to? I want to change the merkle root and genesis
block

Unfortunately this is not a support chat and this is no bug report. :)


Duplicate tab should initialize at the same directory as the tab being dulicated

Description of the new feature/enhancement
Right now, if you initialize a new tab, it defaults to the user home directory. If you are using the default shell, that is standard behavior for opening a new tab. It should open with the directory from the the tab you duplicated.

The Terminal can already do this, if you configure your shell to tell the Terminal about the CWD: Opening a tab/pane in the same directory in Windows Terminal


WIP release-2.1 only - strip crds from helm storage and helmrelease manifest if helmrelease is owned by operator.open-cluster-management.io MultiClusterHub

https://github.com/open-cluster-management/backlog/issues/7533
Signed-off-by: Mike Ng<EMAIL_ADDRESS>

Yup, looks like code :joy:


Run tests against same node versions

Current coverage is 100% (diff: 100%)

Merging #26 into master will not change coverage

@@           master   #26   diff @@
===================================
  Files           1     1
  Lines          36    36
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
  Hits           36    36
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update 1582ac1...8dd41a8

Thanks for doing this! Unfortunately there's some fancy things we'd need to do for our after_success scripts to only run for once of the versions of node we're running. I think we'd be safe to only support v6 though...

Got it. So remove node 4?

Yep!

Fixed

Thank you!


Bump react from 16.8.5 to 16.8.6

Bumps react from 16.8.5 to 16.8.6.

Release notes
Changelog
Commits

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>

Reacts to a resizing window.