about number of features in prediction

Thank you for great well organized project!
Looking to the data processing functions you set features (target_cols variable) the same for X and for y. Can you please recommend "how" if I want to predict one feature from many in the dataset how to pass it to models?

Hmm this is interesting. I can't think of a reason why this wouldn't work conceptually, but none of our experiments had a Multivariate --> Univariate format so the loss functions are not built for it. I am adding this to the list of new experiments for version 2 of the paper. In the meantime (if you're fine wasting lot of compute) you could probably hack this together by padding the target values with a magic number and then using the missing value masking that's already present. The one value you're interested in predicting is there and the rest of the dimensions have a number that will be masked by calling forecaster.set_null_value. https://github.com/QData/spacetimeformer/blob/efff49aea19eb9d6f6643aafa4916aa387893d84/spacetimeformer/forecaster.py#L66-L81 So your targets and inputs would both be shape (x, num_target_cols) but the targets would have num_target_cols-1 columns of say 0.0. The forecaster then has its null value set to 0.0 and keep predictions on those values from impacting the loss function, meaning only the predictions on the real target variable are trained.
Otherwise, I'm planning on continuing work on a version 2 of this paper and codebase in a few weeks. Hopefully this will be released late winter (Feb or March)


az functionapp deployment source config-zip

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az functionapp deployment source config-zip
Errors:
The command failed with an unexpected error. Here is the traceback:
Expecting value: line 1 column 1 (char 0)
Traceback (most recent call last):
  File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 657, in execute
    raise ex
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 720, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 691, in _run_job
    result = cmd_copy(params)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 328, in __call__
    return self.handler(*args, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/appservice/custom.py", line 396, in enable_zip_deploy_functionapp
    remove_remote_build_app_settings(cmd, resource_group_name, name, slot)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/appservice/custom.py", line 528, in remove_remote_build_app_settings
    should_contain=app_settings_should_contain)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/appservice/custom.py", line 987, in validate_app_settings_in_scm
    scm_settings = _get_app_settings_from_scm(cmd, resource_group_name, name, slot)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/appservice/utils.py", line 75, in call
    raise exception
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/appservice/utils.py", line 71, in call
    return func(*args, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/appservice/custom.py", line 1018, in _get_app_settings_from_scm
    return response.json() or {}
  File "/opt/az/lib/python3.6/site-packages/requests/models.py", line 900, in json
    return complexjson.loads(self.text, **kwargs)
  File "/opt/az/lib/python3.6/json/__init__.py", line 354, in loads
    return _default_decoder.decode(s)
  File "/opt/az/lib/python3.6/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/opt/az/lib/python3.6/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az functionapp deployment source config-zip -g {} -n {} --src {}

Expected Behavior
Environment Summary
Linux-5.4.0-1055-azure-x86_64-with-debian-10.2 (Cloud Shell)
Python 3.6.10
Installer: DEB

azure-cli 2.26.0 *

Extensions:
ai-examples 0.2.5
ssh 0.1.5

Additional Context

route to service team

Thanks @gowrimshankar I'll take a look. Also adding this to https://github.com/Azure/Azure-Functions/issues/1916

this is a very old issue - can you please re-try with latest version of CLI & re-open if this still repros.


Dependency minimization

@node-rs/argon2 and @node-rs/bcrypt are only required by the password provider and pull many huge dependencies (with binaries).
Is it possible to make it optional and reduce the number of dependencies ?

You can't make dependencies optional. You should be bundling and tree shaking your project if need to reduce the size for serverless etc

@marcomuser I'd have to test it to make sure it works, but I'm open to the idea :D
That said, it would be a breaking change so I don't think we can commit to it yet

Sounds good! Then let's reopen this ticket. If you want to see how a published npm package with an optional peer dependency behaves check out @tanstack/vue-query as an example which has an optional peer dependency for users that still use it with vue v2. When installed as package from npm the optional peer dependency doesn't get added to node_modules automatically. But when you clone the repo and (p)npm install, it will get installed automatically for development as usual.

We're removing password hashing in v2


Added new option for ktls support

latest openssl added a new option "SSL_OP_ENABLE_KTLS" to enable ktls on
manually, so need to add option to support it.
Signed-off-by: Gao Junhao<EMAIL_ADDRESS>

This pull request will be closed automatically because we don't accept pull requests due to this repository uses mirror.

Thank you for contributing to Nginx!
Nginx does not use GitHub for code submissions.
Please visit http://nginx.org/en/docs/contributing_changes.html
and follow the instructions there to submit changes.


[Feature] support scrollbar in sequence chart

What problem does this feature solve?
when I scroll mouse, the canvas or axes will be scaled, I don't need scale, I just want to scroll canvas.
Maybe set the scrollbar to visible can solve this problem, but it not support scrollbar in sequence chart.
What does the proposed API look like?
null

it has been sloved by https://github.com/VisActor/VChart/pull/840


Indentation with ternary operators

Indentation seems to be wrong with ternary operators, it always has one less indentation than I want it to. Or maybe my formatting is out of the norm I guess, but it seems correct.
I'm not very good at regex, so I'm not sure if the decreaseIndentPattern is the problem, but I'm confused by line 63 in atom-react.coffee, why is it decrementing the desiredIndentLevel no matter what?
Oh, I see why it's decrementing, my mistake. It looks like the issue is with decreaseIndentForNextLinePattern then. As a workaround I just removed the </[-_\\.A-Za-z0-9]+> section for now, but it would be great if the regex would detect if a ternary operator is in use. Okay removing that part isn't a good idea. Here is what I'm currently using: decreaseIndentForNextLinePattern: "(?x) />\\s*(,|;)?\\s*$ | ^(?!\\s*\\?)\\s*\\S+.*</[-_\\.A-Za-z0-9]+>$". Unfortunately, I can't use this as a permanent workaround because of #24.
Behavior:

Debugger:

Thank you! Please let me know if there's anything else I can do to help.

When the ? is on the next line, it is currently not indented. It would be nice it if it were by default, so that this indentation would happen:
const size = length > 10
  ? 'large'
  : 'small'

Whereas currently after an auto-indent:apply, I get:
const size = length > 10
? 'large'
: 'small'

Jacob's suggested (?x) />\\s*(,|;)?\\s*$ | ^(?!\\s*\\?)\\s*\\S+.*</[-_\\.A-Za-z0-9]+>$ messes up my self-closing tags.

Huh really? Can you provide an example?

As far as I know the only thing my change does is not decrease the indent after a line that starts with ?, I'm not sure why it's breaking that. That setting is hard coded in two separate places in atom-react, I'm not sure if changing it in the settings there will work correctly.

Oh except I didn't notice 7b2d132339f6366238e44df46da0b341830f4bfe, changing it in the settings probably does work correctly after that. I'm not sure why it's breaking that case for you then.

Closing because I no longer have this problem with recent update


Library import does not work

I've been trying to get the example code in the README to work, but haven't had much luck so far. I get an "Unused import statement" warning on the from leanix import * line, and "Unresolved reference" errors when swagger and ServicesApi are called.
If I go into the src/leanix/__init__.py and add from . import swagger and from . import ServicesApi, the modules can now be imported, but it seems like any API call I try to make just gives me None, even after configuring my own API token and base path.
>>> services = servicesApi.getServices()
>>> print(services)
None

@gprestonebsco Which Python version are you using?

I tried both Python 2.7 and 3.6, and neither was importing anything.
From: Roman Saul<EMAIL_ADDRESS>Sent: Monday, June 11, 2018 10:00 AM
To: leanix/leanix-sdk-python<EMAIL_ADDRESS>Cc: Graham Preston<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [leanix/leanix-sdk-python] Library import does not work (#7)
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
@gprestonebscohttps://github.com/gprestonebsco Which Python version are you using?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/leanix/leanix-sdk-python/issues/7#issuecomment-396253287, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AM9arckdVoDbhQOgJ61y7WQorgfYz3RSks5t7nf4gaJpZM4UcrmX.

@gprestonebsco Sorry, I just realised that this Python-SDK is deprecated as it only supports V1 of our API. Please see https://dev.leanix.net/docs/overview how to access V2 of our GraphQL or Rest APIs. If you have further questions or need assistance please contact<EMAIL_ADDRESS>


add name to CONTRIBUTORS.md

add name to contributors.md

try to pull repo again to push your pull request ...

ok ...

is this right?

perfect, good job.


support RS1619xs+

Is there a reason this isn't currently supported on the 1619xs+?  When I install the card via a riser, I can get ta UID for the card and just need to get the drivers installed.  Is this something I can compile myself on the xs+?
Thanks for your work on this!

fixed

Ty, gpu does show up and seems to work!  Thanks for all your time you've put in on this!


Drop application/yaml content type

This is a breaking change for any clients that are currently requesting
application/yaml.
This is the simplest fix to #593, as openapi randomly switches between
json and yaml responses when no content type is provided.
Fixes #593
Signed-off-by: Hayden Blauzvern<EMAIL_ADDRESS>
Summary

Release Note
Dropped support for YAML content type
Documentation

Looks like there is a difference between how the comments are generated. This should be ok.

hey 👋 when i open a PR there was a dependabot that making unnecessary commit automatically i have mo idea  about that please help me i am stuck

Looks like there is a difference between how the comments are generated. This should be ok.

I think there's one additional thing in the Makefile that needs addressed: --default-consumes application/json\;q=1 should be removed

hey wave when i open a PR there was a dependabot that making unnecessary commit automatically i have mo idea about that please help me i am stuck

@ansari-danish please open a separate issue instead of discussing on an unrelated PR. Thanks!

@bobcallaway Updated the Makefile. Any advice on how to handle the client differences due to the comment? Can we just ignore the required check when merging?

Codecov Report

Merging #933 (52220e9) into main (cb5572d) will increase coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #933      +/-   ##
==========================================
+ Coverage   48.20%   48.26%   +0.06%
==========================================
  Files          62       61       -1
  Lines        5398     5383      -15
==========================================
- Hits         2602     2598       -4
+ Misses       2513     2504       -9
+ Partials      283      281       -2

Impacted Files
Coverage Δ

pkg/sharding/ranges.go
47.27% <ø> (ø)

pkg/client/rekor_client.go
86.95% <100.00%> (ø)

pkg/types/rekord/v0.0.1/entry.go
48.82% <0.00%> (-0.67%)
:arrow_down:

pkg/types/helm/v0.0.1/entry.go
48.91% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us.

@bobcallaway Ran make clean; make, and got the same result.

Figured it out, I was using go 1.19 and not .18.


[pre-ll/gl] Example for texture array usage

Is there any example or tutorial for using texture arays (gfx::texture::Kind::D2Array), like creating array, adding textures to it and drawing them with shader?
Short info header:

GFX version: 0.17.1
OS: Debian Stretch
GPU: Nvidia 970gt

Here are some examples: https://github.com/search?p=1&q="Kind%3A%3AD2Array"&type=Code&utf8=✓

@kvark should this issue be updated to remove the pre-ll label and request a texture array example for the new API?

wgpu-rs has shadow example that uses texture arrays.


Format/Logic Update

-Fixed Frequency errors with initialization and changing some of the logic
-Fixed correct respective active channels of frequency detection
-Updated formatting
-Changed main loop logic to incorporate hysteresis both directions for the pedal controller

What's up with the change from uint32_t to unsigned long? Is there a particular reason for it? I think this will be the only place where this style of int is used if we use it here.

I'll change it back. I thought a long is bigger than 32 bits when I was doing some debugging, but was wrong.


Installation requirements

Hi,
I tried to install ktransformers on a clean install of Linux Mint 22 (based on Ubuntu 24.04), and there are a few things that I had to add:
pip instal numpy
pip install cpufeature
pip install flash_attn
conda install -c conda-forge libstdcxx-ng

Please update the pip dependencies.
Are there any plans to increase the number of quants supported for Deepseek-Coder-V2-Instruct-0724?

Okay, we will update these packages in our next release.
Regarding quantizations, we now support multiple quantization methods(Qx_k and IQ4_XS) . What else would you like?

I have a system with 192GB DRAM and 48GB VRAM (2x 3090). Would it be able to handle 128k context with the specs? Would it be able to handle Q5_K_M or Q6_K_M?
Also I can only set max_new_tokens in local_chat, not the ktransformers server, and I can't set the total context size anywhere.

Having this issue as well, not being able to set --max_new_tokens in the container breaks downstream projects that require longer output lengths.

I have a system with 192GB DRAM and 48GB VRAM (2x 3090). Would it be able to handle 128k context with the specs? Would it be able to handle Q5_K_M or Q6_K_M?
Also I can only set max_new_tokens in local_chat, not the ktransformers server, and I can't set the total context size anywhere.

Yes, we supported Q5_K_M and Q6_K_M.
About setting max_new_tokens in container, sorry for the inconvenience that this is not supported now.  If you’re building from source, you can modify the max_new_tokens parameter in ktransformers/server/backend/args.py. We will include this update in the next Docker release.


Corrected XML Closing Tag - L20

In line 20, it should </Project>, instead of </PropertyGroup>.

Docs Build status updates of commit 109753e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/create-packages/includes/add-description.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Add featureType property to features

This PR implements (most of) the functionality described in #12937:

adds a non-observable feature type property to features (comparable to feature ID), with getters/setters getFeatureType()/setFeatureType()
when reading GML, the (local) element name will be parsed to this property

Not (yet?) implemented is the use of the defined individual feature type when writing features, which is somewhat more complicated.
Motivation for this change are service query results (e.g. this GetFeatureInfo request) containing multiple feature types where a differentiation (not just based on the contained properties) between them is required.

Thanks for this contribution! Instead of adding a new featureType member on ol/Feature, which is quite specific to GML, I'd suggest giving the GML format a featureTypeProperty option, and feature.set(featureTypeProperty, featureType) when set.

I touched on this in #12937, which I hoped would result in some discussion before I implemented anything. Since it didn't then I just went ahead anyway.
The problem I see with a feature type property is that it then becomes a "true" property of the feature (albeit a special one), which would then be output in all formats. In GML it would have some special handling and be filtered out / converted to element name, but otherwise it would just get output.
I note that the feature ID already has a special-case handling and is not set as a normal property.
If I go down the route of a featureTypeProperty for the GML format, then should this have a default value - which would be a noticable (arguably breaking) change for all GML parsing - or should this be optional?

Thanks for the explanation, @ejn. I think if you change the private featureType_ property in your pull request to featureType and remove the getters and setters, so the format sets and reads the property directly, I could live with this pull request. I don't think it is necessary to fire a change event when the featureType changes.

Thanks for the feedback @ahocevar - will make the changes as you suggest. Agree that the change event is unnecessary - had thought about it in case the rendering should be updated, but changing the property after adding the feature to the map is not really a sensible use-case.

I'm still struggling to find this change useful, and still thinking about what alternatives we have. Two come to mind:

GeoServer always makes the feature type part of the feature id, e.g. myFeatureType.1. This could be achieved by passing the GML reader an idProperty option (similar to ol/format/MVT, which could also be a function. The GML writer could then also be changed so featureType accepts a function.
The GML reader could have a readFeatureTypes method, which would return the feature types found in the passed document. Then, with a new featureType reader option, reading features could be restricted to that one featureType. Then you'd call the reader once for each found featureType, with the respective featureType configured.

Didn't you want to also have the GML writer pick up the featureType?

Ultimately yes. Since the writing is slightly more complicated - and my immediate requirement is fulfilled by being able to read the feature type as part of a generic WMS client - then I would implement the writing as a second PR

I'm still struggling to find this change useful, and still thinking about what alternatives we have. Two come to mind:
1. GeoServer always makes the feature type part of the feature id, e.g. `myFeatureType.1`. This could be achieved by passing the GML reader an `idProperty` option (similar to `ol/format/MVT`, which could also be a function. The GML writer could then also be changed so `featureType` accepts a function.

This is very much implementation-specific and is not something which could be relied on. My "standard" example for the need to read multiple feature types is this GetFeatureInfo-request which requests only one layer but receives two (complex) features of different types (AX_Flurstueck, AX_LagebezeichnungOhneHausnummer) in response. For a generic client it is necessary to show the user not only the properties of the features found, but also what type of features they are (e.g. feature type name as a heading followed by a table containing the feature properties). In general there is also no way to discover in advance through the WMS interface exactly what a GML-formatted GetFeautreInfo-Response will contain. I agree that such responses are not very common (although similar services to my example are freely available in many German states), and similar examples of GetFeatureInfo-responses containing multiple feature types may also be found in INSPIRE services.

2. The GML reader could have a `readFeatureTypes` method, which would return the feature types found in the passed document. Then, with a new `featureType` reader option, reading features could be restricted to that one `featureType`. Then you'd call the reader once for each found featureType, with the respective `featureType` configured.

I agree that this would be a possible strategy for fulfilling the aim of reading multiple feature types - but does not open the possibility to write multiple feature types in a single collection. It would however fulfill my immediate need for presenting GetFeatureInfo-results (until it becomes necessary to also offer an export function!).

@ejn Can you share the code you use to read the GML you linked above from the GetFeatureInfo request? I'd like to set up a test case.

@ahocevar Sure, I'll try and cut it down to a reasonable size as it's part of a viewer application. Note that #12936 also resulted from parsing such data!
Although the above link is freely available, it is not strictly under an open data licence. This link produces identically structured data (with the bonus of an additional feature type AX_LagebezeichnungOhneHausnummer) from a different state (NRW) who publish the data under the Data licence Germany - Zero, which would be ideal for including in a test-case.

@ahocevar Thanks for your patience on this up until now - will try and and some more tests etc. It looks like I won't have time to work on this the next few days though, so might be a while until the next activity here.


Feature 647 -- attributes on component tree

Feature 647 -- attributes on component tree
Implementation is pretty straightforward -- extended the node interface to include a property quickViewAttribute, which is an array of Property objects that the component tree in the front end will display. Once a debug element has been transformed into a node element, the function quickViewAttribute will take the node element and take any relevant information based on the node name (currently just a elements are considered, but more can easily be added later).
On the frontend, the node-attribute component will take in as an input a nodes quickViewAttribute. Initially the component will only display ... and once the user clicks on the three dots, the array of Property objects will be iterated on and displayed (this code is unchanged, it was used previously to display a information).
Thats it, sorry took so long for this to get pushed, took me just a day to wrap my head around the codebase :)

@tyllrb I thought the agreement was that we'd not do the ellipsis thing? My thoughts are that if there's value in having it there, it should be visible by default.

@stevenkampen removed the hide/show functionality for now, like we discussed, we'll see how it plays out with larger apps/component trees and see how best to hide/show the attributes.
also, before this gets merged, was going to add some failsafe checks to the transformer functions that turns a debug element into a Node element, just so if angular debug object changes in the future the entire application won't break due to an exception

@tyllrb if the Node element changes and the app breaks, that is a good thing. It let's use know we need to fix something. If you hide this (make it fail-safe), the app continues to run crippled and it's going to be hard to find the bug.

@tyllrb @rajinder-yadav As per our earlier conversation about this feature, the intention is to make it failsafe.

@rajinder-yadav @tyllrb To be clear, this is just the transformer function which derives the "quick view" properties from the node. Not the whole of the transform process.

@stevenkampen @tyllrb So if the angular debug object changes, how are we going to know this if what it looks like to me is a proposal of eating up this error? Correct me if I am wrong, just want to know how we plan to detect changes outside our control.

@stevenkampen @rajinder-yadav Added some failsafe checks. In the quickViewAttribute function I just added some simple if checks to see if certain property names are defined. In the Description class, where the angular debug object is used to parse out description information (which is where the a quick view attributes come from), I wrapped getProviderDescription, and getComponentDescription in a try statement which will catch the exception when a property name is undefined in the path (ie if componentInstance is undefined or null in the path debugElement.componentInstance.constructor.name).
Right now if the exception is caught those functions will just return [], essentially swallowing the error. Should this error be displayed to the user in any way? If so, this might be outside the scope of this story. I can add failsafe checks for getting the quick view attributes, which I have, but catching and displaying errors/warnings if the entire node transformation fails is of a different concern.
Also added some changes as per rajinders feedback.

resolves #647

@tyllrb Excellent. After attending to @rajinder-yadav's suggestions, and a rebase, I think this is a :shipit:

LGTM :ship:


Objectize ScaleButton

Can you also remove use gdk in color_button.rs ?

Seems i was too fast, forgot convert ScaleButtonTrait

Delete ScaleButtonTrait in when i convert VolumeButton?

Seems ScaleButtonTrait can be deleted it this PR.
Do it in separate commit?

Also can I remove f64 <-> c_double conversion?

The deletion is fine in the same commit.
Yeah those noop conversions between f64 and c_double, i32 and c_int, etc should be removed.

Done

Done

Thanks!


LPS22HH sensor reporting wrong pressure data

Describe the bug
The pressure sensor reporting wrong data that is too high
To Reproduce
Steps to reproduce the behavior:

west build -b frdm_k64f samples/shields/x_nucleo_iks01a3/ -- -DSHIELD=x_nucleo_iks01a
See data on console

HTS221: Temperature: 25.9 C
HTS221: Relative Humidity: 45.5%
LPS22HH: Temperature: 26.3 C
LPS22HH: Pressure:25822.956 kpa
STTS751: Temperature: 27.2 C
LIS2MDL: Magn (gauss): x: -0.864, y: -0.270, z: -0.330
LIS2MDL: Temperature: 4631.4 C
LIS2DW12: Accel (m.s-2): x: -0.459, y: 0.000, z: 9.648
LSM6DSO: Accel (m.s-2): x: 0.043, y: -0.273, z: 9.892
LSM6DSO: GYro (dps): x: 0.005, y: 0.021, z: 0.047
51:: lps22hh trig 10080
51:: lis2dw12 trig 10182
51:: lsm6dso acc trig 2
51:: lsm6dso gyr trig 2
51:: lsm6dso temp trig 0

Expected behavior
Value should be realistic

also note:
LIS2MDL: Temperature: 4631.4 C

@nashif
Anas, can you possibly set the priority of this bug? For me it is low, but I'll let you decide. Anyway, I'll start asap.

also note:
LIS2MDL: Temperature: 4631.4 C

@nashif
This is LIS2MDL, can you please open a separate bug for it?

see #35910


Playground Shell

This should help us dog food this sooner rather than later. Also fixes:
Closes #31
Closes #37
#38 is still needed in order to avoid this "if you have the link, you can join" behavior seen in the shell.
The shell is a simple interactive prompt where input prepended with ":" is interpreted as a command. So far, the available commands are:
:address
Show your current addresses. This is useful when another shell needs to add you as a follower, as they will need a dial-able address.
e.g.,
/ip4/<IP_ADDRESS>/tcp/4007/p2p/12D3KooWPrk7Tut9ET4Bqmw2DrbYVoBmG4zjP3bZUsc722bh8D98
/ip4/<IP_ADDRESS>/tcp/4007/p2p/12D3KooWPrk7Tut9ET4Bqmw2DrbYVoBmG4zjP3bZUsc722bh8D98
/ip4/<IP_ADDRESS>/tcp/4007/p2p/12D3KooWPrk7Tut9ET4Bqmw2DrbYVoBmG4zjP3bZUsc722bh8D98

:thread [name] [address]
Switch to a thread by name. Name is local only. If the thread does not exist, one will be created. If you give an address, the shell will attempt to add the thread behind the address. This is how you "join".
:thread photos // creates a new thread
:thread other-stuff // creates a new thread
:thread photos // switches back to the first thread
:thread sports /ip4/<IP_ADDRESS>/tcp/4006/p2p/<ID>/thread/<ID> // add the remote thread at the address
:thread-address
Show the current thread's addresses, which are your own log's addresses in that thread, which may include a follower if you've added one. Another peer can use one of these addresses to add this thread (ideally a follower address).
e.g.,
/ip4/<IP_ADDRESS>/tcp/4007/p2p/12D3KooWPrk7Tut9ET4Bqmw2DrbYVoBmG4zjP3bZUsc722bh8D98/thread/bafk44nyecg2a32nuqx5fytdscs5or7fdprg7hhkfzwtudvlegsxlqgi
/ip4/<IP_ADDRESS>/tcp/4007/p2p/12D3KooWPrk7Tut9ET4Bqmw2DrbYVoBmG4zjP3bZUsc722bh8D98/thread/bafk44nyecg2a32nuqx5fytdscs5or7fdprg7hhkfzwtudvlegsxlqgi
/ip4/<IP_ADDRESS>/tcp/4007/p2p/12D3KooWPrk7Tut9ET4Bqmw2DrbYVoBmG4zjP3bZUsc722bh8D98/thread/bafk44nyecg2a32nuqx5fytdscs5or7fdprg7hhkfzwtudvlegsxlqgi
/ip4/<IP_ADDRESS>/tcp/4006/p2p/12D3KooWMY5LbHywKAdwDddpTE1BsBZFyT4oR8QCrYCsLLC72bZ4/thread/bafk44nyecg2a32nuqx5fytdscs5or7fdprg7hhkfzwtudvlegsxlqgi
/ip4/<IP_ADDRESS>/tcp/4006/p2p/12D3KooWMY5LbHywKAdwDddpTE1BsBZFyT4oR8QCrYCsLLC72bZ4/thread/bafk44nyecg2a32nuqx5fytdscs5or7fdprg7hhkfzwtudvlegsxlqgi
/ip4/<IP_ADDRESS>/tcp/4006/p2p/12D3KooWMY5LbHywKAdwDddpTE1BsBZFyT4oR8QCrYCsLLC72bZ4/thread/bafk44nyecg2a32nuqx5fytdscs5or7fdprg7hhkfzwtudvlegsxlqgi

:add-follower
Add another peer as a follower.
:add-follower /p2p/<ID> // no encapsulating dialable address, meaning that a DHT lookup is required
:add-follower /ip4/<IP_ADDRESS>/tcp/4007/p2p/<ID> // dial direct!

Thanks for the comments @jsign. I pushed some changes.
I have since,

Added some logic that allows new logs to be picked up during a records request. This is achieved by sending a full HEAD map of all logs in the request, which is then compared by the receiver who can tag on missing logs. This is useful when a new writer joins a thread.
Added a simple daemon that is now running on us-west-1. We can use this as a test follower.

The shell can be run with...
go run ./exe/shell

The daemon can be run with...
go run ./exe/daemon

Thanks for the comments @jsign. I pushed some changes.
I have since,
* Added some logic that allows new logs to be picked up during a records request. This is achieved by sending a full HEAD map of all logs in the request, which is then compared by the receiver who can tag on missing logs. This is useful when a new writer joins a thread.

* Added a simple daemon that is now running on us-west-1. We can use this as a test follower.

The shell can be run with...
go run ./exe/shell

The daemon can be run with...
go run ./exe/daemon

Cool, good idea.
I'll spot some time to give it a try!

I still need to sink some time into understanding why the peers don't see each other in CI. I have a hunch we'll have to disable MDNS for CI stuff. This should be configurable anyway as it's not needed on a server.

Cool! You could try adding the remote thread I've been playing with at some point:
:thread team /ip4/<IP_ADDRESS>/tcp/4006/p2p/12D3KooWMY5LbHywKAdwDddpTE1BsBZFyT4oR8QCrYCsLLC72bZ4/thread/bafk44nyecg2a32nuqx5fytdscs5or7fdprg7hhkfzwtudvlegsxlqgi

After all the tweaks, it's working well between two computers. The only issue I see is that sometimes the remote peer is not dialable for some amount of time, then comes back. This can be particularly annoying when adding a thread. I've seen similar behavior before. We may need to dig in there... I don't see any reason it shouldn't be always dialable.


Additional Browser Support

Hi Jerik -
Great piece of code - thank you.
Is support for browsers other then Firefox on the roadmap?
JM

Hejho,
It is on the roadmap. Currently i refactor my code to be more ecmascript 6 compatible. I will use css grid layout, which should fit better to lean canvas. It is on the other hand not fully implemented in all browsers [1], but i think in the near future.
[1] https://gridbyexample.com/browsers/
Cheers -- jerik

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @mzs0207, @lixuejiang, @zatol, @Zhujunnan, @DumontIT, @Esperadoce, @oschino

AltLayer Airdrop Season One Announcement

Exciting news! AltLayer token (ALT) is set to launch on Binance on January 25, 2024. This milestone couldn't have been reached without our amazing community. Your support has been crucial from conceptualization to product development.
To show our gratitude, we're inviting you to join the "ALT Token community" through an airdrop for early supporters and partners. Below is a summary:

Total Allocated ALT Tokens: 300,000,000 (3% of total supply)
Distribution Categories:

NFT Holders
Altitude Campaign Participants
EigenLayer Restakers
EigenLayer Ecosystem Partners
Celestia Stakers and others

For detailed criteria and information, check the full announcement here.
Claim opens from January 25 to February 25, 2024. Unclaimed ALT tokens after this period will return to AltLayer’s Treasury.
Thank you for being part of AltLayer's success! More to come in Season One, stay tuned.
Note: Certain regions are restricted from the airdrop. Please review the disclaimer before participating.
Winners: @sigridnicole, @midtur, @webvoicenl, @flsilves, @batuhanaktass, @pooyakn, @Evan-Tideswell, @ktmarron, @hakkisagdic, @iamkucuk, @Apoll95, @NoasProject, @czp3009, @imdeepsharma, @unrulybeardo, @Donshorty, @rodrigooler, @yusufpeh, @Redline600, @cett01


Add pro-grammatical access to volare other than the command line

Hi @donn
It would be nice to support programmatical access to the same functions provided by commandline.

There is an API that does exactly that, but it is undocumented for now


[BUG][linux/opensearch : Security Plugin configuration | Initialize the opensearch security index in opensearch]task failed

Describe the bug
Failed with this playbook when run cluster install.All the opensearch nodes running.

TASK [linux/opensearch : Security Plugin configuration | Initialize the opensearch security index in opensearch]

bash /usr/share/opensearch/plugins/opensearch-security/tools/securityadmin.sh -cacert /usr/share/opensearch/config/root-ca.pem -cert /usr/share/opensearch/config/admin.pem -key /usr/share/opensearch/config/admin.key -f /usr/share/opensearch/plugins/opensearch-security/securityconfig/internal_users.yml -nhnv -icl -h <IP_ADDRESS>
Security Admin v7
Will connect to <IP_ADDRESS>:9300 ... done
Connected as CN=admin.gzhc.local,OU=Ops,O=gzhc.local\, Inc.,DC=gzhc.local
OpenSearch Version: 1.2.3
OpenSearch Security Version: <IP_ADDRESS>
Diagnostic trace written to: /usr/share/opensearch/plugins/opensearch-security/tools/securityadmin_diag_trace_2022-Jan-14_19-07-52.txt
Contacting opensearch cluster 'opensearch' and wait for YELLOW clusterstate ...
ERR: Timed out while waiting for a green or yellow cluster state.
   * Try running securityadmin.sh with -icl (but no -cl) and -nhnv (If that works you need to check your clustername as well as hostnames in your TLS certificates)
   * Make also sure that your keystore or PEM certificate is a client certificate (not a node certificate) and configured properly in opensearch.yml
   * If this is not working, try running securityadmin.sh with --diagnose and see diagnose trace log file)
   * Add --accept-red-cluster to allow securityadmin to operate on a red cluster.

To Reproduce
Steps to reproduce the behavior:

inventories/opensearch/hosts file:

gzites231 ansible_host=<IP_ADDRESS>  ansible_user=inception ip=<IP_ADDRESS> roles=master,ingest
gzites232 ansible_host=<IP_ADDRESS>  ansible_user=inception ip=<IP_ADDRESS> roles=master,ingest
gzites233 ansible_host=<IP_ADDRESS>  ansible_user=inception ip=<IP_ADDRESS> roles=master,ingest
gzites225 ansible_host=<IP_ADDRESS>  ansible_user=inception ip=<IP_ADDRESS> roles=data
gzites226 ansible_host=<IP_ADDRESS>  ansible_user=inception ip=<IP_ADDRESS> roles=data
gzites227 ansible_host=<IP_ADDRESS>  ansible_user=inception ip=<IP_ADDRESS> roles=data
gzites228 ansible_host=<IP_ADDRESS>  ansible_user=inception ip=<IP_ADDRESS> roles=data
gzites229 ansible_host=<IP_ADDRESS>  ansible_user=inception ip=<IP_ADDRESS> roles=data
gzites230 ansible_host=<IP_ADDRESS>  ansible_user=inception ip=<IP_ADDRESS> roles=data

dashboards1 ansible_host=<IP_ADDRESS>  ansible_user=inception ip=<IP_ADDRESS>

# List all the nodes in the os cluster
[os-cluster]
gzites231
gzites232
gzites233
gzites225
gzites226
gzites227
gzites228
gzites229
gzites230
# List all the Master eligible nodes under this group
[master]
gzites231
gzites232
gzites233

[dashboards]
dashboards1

The inventories/opensearch/group_vars/all/all.yml file:

## Common opensearch configuration parameters ##

os_cluster_name: opensearch

# opensearch download
os_download_url: http://<IP_ADDRESS>:8000/opensearch

# opensearch version
os_version: "1.2.3"

# opensearch dashboards version
os_dashboards_version: "1.2.0"

# Configure hostnames for opensearch nodes
# It is required to configure SSL
# Example es1.example.com, es2.example.com
domain_name: gzhc.local

os_user: opensearch

# Java memory heap values(GB) for opensearch
# You can change it based on server specs
xms_value: 4
xmx_value: 4

# Cluster type whether its single node or multi-node
cluster_type: multi-node

run the playbook ansible-playbook -i inventories/opensearch/hosts opensearch.yml --extra-vars "admin_password=Pass@000 kibanaserver_password=Pass@000" -b --become-method=sudo -K -k
See error

Expected behavior
A clear and concise description of what you expected to happen.
The cluster should be initialized successfully,but not.
Playbook Name
Specify the Playbook which is affected?
TASK [linux/opensearch : Security Plugin configuration | Initialize the opensearch security index in opensearch] is affected.
Host/Environment (please complete the following information):

OS: Ubuntu 20.04
JDK: 11.0.12
Ansible Version: 2.11.7
Playbook Version: 1.1.0

Additional context
curl https://<IP_ADDRESS>:9200 -k

shown:
OpenSearch Security not initialized.

@saravanan30erd any thoughts?

@ripmars did you try to remove the related ansible/opensearch folder in /tmp and remove it?
I think this is caused due existing cache in /tmp, which cause the tarball not redownload.
I think @saravanan30erd has a cleanup after the initial run complete, but not if you cancel in the middle of the run and rerun.
Thanks.

@ripmars As @peterzhuamazon said, previous steps wouldn't have properly run. Please provide the complete logs of whole playbook run.

I run this before every reinstallation.
ansible es -i ites -u hcit -m shell -a 'systemctl stop opensearch;rm -f /tmp/opensearch.tar.gz; rm -rf /usr/share/opensearch  ; userdel -fr opensearch;rm -f /etc/systemd/system/opensearch.service ; systemctl daemon-reload' -k -K -b --become-method=sudo

and delete the ansible master host's '/tmp/opensearch-nodecert' folder.

@saravanan30erd @peterzhuamazon Hey, my bad .my jvm settings are 4Gb,but I forget to upgrade the os ram to 8Gb.
My lab is running now. Thanks for all.


draft: Webchat as an Extension

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
If this is a bug fix, please describe the root cause and analysis of this problem.
Task Item
Please include a link to the related issue. Ex. Closes #<issue #>
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code refactor (non-breaking change which improve code quality, clean up, add tests, etc)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Doc update (document update)

Checklist

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have functionally tested my change

Screenshots
Please include screenshots or gifs if your PR include UX changes.

Pull Request Test Coverage Report for Build 511962771

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.102%

Totals

Change from base Build 511961100:
0.0%

Covered Lines:
10819

Relevant Lines:
18147

💛  - Coveralls

Pull Request Test Coverage Report for Build 511962771

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.102%

Totals

Change from base Build 511961100:
0.0%

Covered Lines:
10819

Relevant Lines:
18147

💛  - Coveralls


I'm getting lower results, Am I Evaluation correctly? (Kinetics)

I'm having the pretrained model from drive, and using this command:
"python main.py --model_depth 18 --dataset kinetics --model resnet --batch_size 16 --n_classes 400 --annotation _path kinetics_annotation.json --resume_path resnet-18-kinetics.pth --no_train"
I'm Evaluating by normal running just without training.
I'm getting around 39% In acc column which supposes to be 54%.
Happens also in Resnext101, and in Resnet34.
What am I doing wrong?!
Does anyone have any Idea?
BTW: Maybe It's because in validation set I'm getting clip accuracy and not video accuracy?
I tried another method to Evaluate, in kinetics I'm getting 0% and in HMDB51, I'm getting even Higher results , what I'm doing is:

Testing model

python main.py --model_depth 101 --dataset hmdb51 --video_path .jpg --model resnext --batch_size 16 --n_classes 51 --annotation_pathannotation_dir_path/hmdb51/hmdb51_1.json --pretrain_path resnext-101-kinetics-hmdb51_split1.pth --no_train --no_val --test

2.evaluating the model:
 python utils/eval_hmdb51.py
I added a main function :
if __name__ == "__main__":
    hmdb = KINETICSclassification('annotation_dir_path/hmdb51/hmdb51_1.json',
                                  'val_hmdb51.json', verbose=True, top_k=1)
    hmdb.evaluate()

I'm getting 75% and not 63% (top1) on Hmdb51 (avarage on all splits: the error@1 is :(0.36,0.19,0.19), kinetics I'm getting Error@1 =1.1
Thanks!

I have the same problem.

Hey, I got the same problem. Have you guys fixed it?
Which version of pytorch are you using? I'm running the code in pytorch 1.0.0 / CUDA 9.


Microsoft Office 2021 Professional + Crack 2024 Free Download [latest]

Microsoft Office 2021 Professional Plus Crack 2024 Latest Version for Windows. The program and all files are checked and installed manually before uploading, and the program is working perfectly fine without any problem. It is full offline installer standalone setup of Microsoft Office 2021 Professional Plus 2024 Free Download for the latest version of Windows.
Download Link 🔗
Microsoft Office 2021 is the version of Microsoft’s Office suite launched with Windows 11 in 2021. It is the direct successor to Microsoft Office 2019, offering new features and a completely revamped interface. Unlike what happens with Microsoft 365 products, to use this suite, you will not need to be constantly connected to the Internet. Copilot in Word will write, edit, summarize, give suggestions, and create right alongside you. Copilot will bring in information from across your organization to create first drafts, add content to existing documents, summarize text, and rewrite sections or even entire documents to make them more concise. Check spelling, grammar, capitalization, and punctuation in all your Word documents with Microsoft Editor.


Add support for Auto Persisted Queries

Add support of Auto Persisted Queries for Apollo Link protocol https://github.com/apollographql/apollo-link-persisted-queries#protocol
There are 2 features missing from the original issue:

Use Get requests (will probably extracted as separate issue)
Auto disable Auto Persisted Queries whenever server returns PersistedQueryNotSupported

Part of https://github.com/apollographql/apollo-android/issues/1055

Why isn't OPERATION_ID the hash of the query document?
I can't manage to generate a valid sha256 hash that's the same as any OPERATION_ID for the queries that we have in the app I'm working.
We're doing APQ by calculating the sha256 hash of the request body in a custom Interceptor for now, but we want to avoid calculating the hash again since we already have OPERATION_ID.
Didn't you face this issue while working on this feature here?

@rubensousa are you referring to this issue https://github.com/apollographql/apollo-android/issues/1155 ?

@sav007 Yes, that's the problem I was talking here. Let's continue discussion over there.

#1161


Audit exit codes

Currently:
    0 = No errors
    1 = Encountered operational errors e.g. an IO error
    2 = Failed to reformat code because of parsing errors
    3 = Code is valid, but it is impossible to format it properly
    4 = Formatted code differs from existing code (write-mode diff only)

Can we do better? What is optimal for CI? (There are some issues filed about this sort of thing, would be good to look them up).

I did a bit of digging in the related issues and found https://github.com/rust-lang-nursery/rustfmt/issues/1832. Peter (@scode)'s suggestion seems to be to exit with code 0 where we currently exit with 3 (i.e. for impossible-to-format code), and also to combine 1,2,4 into just 1... This seems to kind of make sense, but I'll have to think on it some more...

The error code summary in OP is still correct for rustfmt. For cargo fmt, we just return 0 or 1 (1 for any non-0 rustfmt exit code).
Relevant issues are #1080 and #1832 - which are both dealing with the long lines problem.
There's also #1232 (and I believe there have been other issues) which are about having a 'check' mode for rustfmt where we only check whether a program would be reformatted by rustfmt, without actually reformatting anything. #1028 and #1976 are related since they both touch on write modes ('check' would be a new one).
It seems to me that for exit codes, there are two use cases - regular use of rustfmt where the exit code is informational and CI usage where we want to know whether the program 'passes' rustfmt.
Here is a proposal:

We add a check write mode which checks formatting without writing anything out. It emits 0 if everything is OK, and 1 if running rustfmt would change anything or there was a bug running rustfmt. Output to stdout (which I think should be the same output as diff mode) would distnguish the two cases.
In every other mode, we output 0 if rustfmt executed OK, no matter whether formatting was performed or not, or 1 if there was an internal error. Running with --verbose will indicate to stdout exactly whether there was a problem formatting, parsing, etc. (i.e., current exit codes 2, 3, and 4 turn into 0).

diff mode will have the same exit statuses as other modes

cargo fmt will have the same exit code as rustfmt
in check mode, a line longer than max width will cause a 1 exit code unless it is explicitly ignored (i.e., a comment or string lit would be considered a failure). In other modes, it is not considered an internal error (i.e., would emit 0). (To close #1080, we also need to make sure the error message is clear now).
semi-related - when outputting diffs, we will not include the end of line character unless it is enabled with an option - should make the diffs more easily usable

Follow-up: we should remove the error_on_line_overflow option - I feel like it is mostly redundant under the above proposal. The only question is if people running on CI might like a way to ignore cases where comments or string lits overrun the max width? Personally I wouldn't want that, but I can understand if people did.
Also, what about cases where Rustfmt tried and failed to format a line under the max width (i.e., not explicitly ignored and not ignored because it is a comment or macro, etc.)? I think in check mode, that should give exit 1, (i.e., exit 0 implies every line <= max width or is explicitly ignored). In other modes, is this an internal error or not? I think it must be a bug, and therefore probably ought to be considered an error, but maybe not?
Do we also want to distinguish between code which is ignored and allowed to overrun and code which is ignored but should be manually formatted to not overrun? (I expect trailing whitespace to be treated similarly).

cc @topecongiro on the above - sound good?

Sounds good to me, thank you for summarizing!

Follow-up: we should remove the error_on_line_overflow option - I feel like it is mostly redundant under the above proposal. The only question is if people running on CI might like a way to ignore cases where comments or string lits overrun the max width? Personally I wouldn't want that, but I can understand if people did.

If I understand correctly, those who want to ignore errors from comments or string lits could use diff mode instead. This seems a bit confusing, though, so I see some benefits on keeping error_on_line_overflow option.

Also, what about cases where Rustfmt tried and failed to format a line under the max width (i.e., not explicitly ignored and not ignored because it is a comment or macro, etc.)? I think in check mode, that should give exit 1, (i.e., exit 0 implies every line <= max width or is explicitly ignored). In other modes, is this an internal error or not? I think it must be a bug, and therefore probably ought to be considered an error, but maybe not?

I agree that in both cases they should be considered as an error. On a side note, I think a very long ident should be considered as a non-error as well (cc #1448).

Do we also want to distinguish between code which is ignored and allowed to overrun and code which is ignored but should be manually formatted to not overrun? (I expect trailing whitespace to be treated similarly).

Personally I see no benefits on distinguishing those two.

Also #2707

This is the only remaining work here

I'm not sure exactly what to do about "by default" I think the user probably should opt-in with the config option. Otherwise, this is now implemented.


Add ToString methods for better enum string conversion

Description

Added private ToString methods for various comparison enums in ConditionFactory.cs to improve readability and maintainability.
Updated NewCondition methods to use these new ToString methods for consistent string representation.
Optimized boolean conversion to string using a ternary operator.

Motivation and Context
The result of invoking ToString on an enum is cached in a limited space and there's no guarantee that the value will be cached for the same value in consecutive invocations.
Having code that returns compile-time generated static strings will guarantee that that string is always available and easy to access.
Invoking ToString in bool will return the stringliterals "True" or "False", depending on its value. However, invoking ToLowerInvariant() on those Strings will incur in the generation/allocation of a new string every time.
Testing

Screenshots (if appropriate)
Types of changes

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[X] My code follows the code style of this project
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[ ] I have read the README document
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

License

[ ] I confirm that this pull request can be released under the Apache 2 license

Tests invoking AssertExtensions.AssertEnumUnchanged should be added to validate changes to these enums, but I haven't figured out what the best place for it would be.

Nice change @paulomorgado

Nice change @paulomorgado

Thanks, @danielmarbach.
Maybe introducing NetEscapades.EnumGenerators: a source generator for enum performance would be a good option to avoid hand-written code.

The change itself looks good, but these need unit tests I think this is a good place to put the tests.
I think just testing a few is sufficient, probably no reason to test all of them but I would feel more comfortable knowing we had unit tests.
I wrote a method to get the expected hash of the original type
    public static class HashingUtils
    {
        private static SHA256 SHA256 = SHA256.Create();
        public static string GetHash(Type type)
        {
            return BitConverter.ToString(SHA256.ComputeHash(Encoding.Default.GetBytes(type.ToString()))).Replace("-","");
        }
    }

which you could use to get the expected hash and then pass that in to AssertEnumUnchanged.


Handle script_name when matching paths

We had the report of an issue with mounting phoenix at a path, using the path: Endpoints url path option. The "/phoenix/live_reload" frame would 404 because it does not take script_name into consideration with the path. @josevalim 2nd pair of eyes please.

:+1:

Wait, I actually disagree. If you are mounting it inside a path, maybe you should access it inside that path?

I.e. instead of changing the matching code, I would change the generating code to consider script_name, around here: https://github.com/phoenixframework/phoenix_live_reload/pull/30/files#diff-c8be1eead197c8e20eb612e511f68033R69

Something like: config[:url] || ("/" <> Enum.join(conn.script_name, "/"))

@josevalim Thanks and good call. Updated. Now a user can explicitly include the path prefix in their endpoint:
socket "/some_path/phoenix/live_reload/socket", Phoenix.LiveReloader.Socket

Is this what you had in mind?


Database performance fixes

This branch is meant to significantly reduce the number of needless DB queries that we're currently performing.
This is achieved partly by storing the global config in memory rather than fetching it several times per request as well as ensuring that a simple GET /1.0 as done with just about every single CLI call doesn't hit the database at all.
Unfortunately this doesn't quite fix the performance issues we found during NorthSec, but it's a good initial step.

@masnax the main performance issue we ran into appears to be coming from:
»···// Use non-generated custom method for UsedBy fields.
»···for i := range objects {
»···»···usedBy, err := c.GetProfileUsedBy(objects[i])
»···»···if err != nil {
»···»···»···return nil, err
»···»···}

»···»···objects[i].UsedBy = usedBy
»···}

In lxd/db/profiles.mapper.go. This would effectively cause a full list of instances to be pulled from the database every time we load some instances. This is particularly noticeable when hitting something like /1.0/metrics which only accesses instances on the local server but then still ends up pulling DB entries for every single instance in the entire cluster.
In our environment we were running with more than 300 instances and this was causing the DB to become near unusable.

@stgraber Yeah that would be it. I've already removed the dedicated UsedBy field for projects but haven't gotten around to doing it for profiles. I'm tracking these refactors here #10183. I recall profiles being a bit of a nasty one (along with instances), but I'll try to take care of that one ASAP.

@masnax the main performance issue we ran into appears to be coming from:
»···// Use non-generated custom method for UsedBy fields.
»···for i := range objects {
»···»···usedBy, err := c.GetProfileUsedBy(objects[i])
»···»···if err != nil {
»···»···»···return nil, err
»···»···}

»···»···objects[i].UsedBy = usedBy
»···}

In lxd/db/profiles.mapper.go. This would effectively cause a full list of instances to be pulled from the database every time we load some instances. This is particularly noticeable when hitting something like /1.0/metrics which only accesses instances on the local server but then still ends up pulling DB entries for every single instance in the entire cluster.
In our environment we were running with more than 300 instances and this was causing the DB to become near unusable.

Yep the issue @masnax is working on will give us  more control when the expensive used by fields are populated.

Feedback addressed

@tomponline good to go

@tomponline should be good to go too


langchain: updates default json splitter chunk size and list conversion

Description: This changes the default value for max_chunk_size from 2000 to the more appropriate 500 characters. This also changes the default for convert_lists to True as I believe most users will want to split long lists by default. I have updated the ipynb to reflect this updated default behavior.
Issue: None
Dependencies: None
Twitter handle: @joelsprunger

probably ok given how new this feature is, but we should avoid changing defaults like this in the future. technically a breaking change

That's on me. I see this was in the 0.1.6 tag - does that mean it was released?

I think unfortunately at this point the feature is no longer new, and the damage from changing defaults out from under users might outweigh the benefits.


Updating to latest version download what it seems excessive dependencies....

Updating to 0.0.6b2 downloaded what it seems like an overkill amount of dependencies  several GBs of cuda, nvidia, etc... when before it was running without all this...
Are this new dependencies forced b latest COLbert?
Is there a way to force only download dependencies to run on CPU?

It seems that also introduced regression, search stopped working.... it seems that it hangs loading an extension:
[Feb 07, 01:04:43] Loading segmented_maxsim_cpp extension (set COLBERT_LOAD_TORCH_EXTENSION_VERBOSE=True for more info)...
Using /home/german/.cache/torch_extensions/py311_cu117 as PyTorch extensions root...
Emitting ninja build file /home/german/.cache/torch_extensions/py311_cu117/segmented_maxsim_cpp/build.ninja...
Building extension module segmented_maxsim_cpp...
Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
ninja: no work to do.
Loading extension module segmented_maxsim_cpp...
/home/german/.pyenv/versions/3.11.3/envs/agile_clean/lib/python3.11/site-packages/torch/cuda/amp/grad_scaler.py:120: UserWarning: torch.cuda.amp.GradScaler is enabled, but CUDA is not available.  Disabling.
  warnings.warn("torch.cuda.amp.GradScaler is enabled, but CUDA is not available.  Disabling.")
/home/german/.pyenv/versions/3.11.3/envs/agile_clean/lib/python3.11/site-packages/torch/cuda/amp/grad_scaler.py:120: UserWarning: torch.cuda.amp.GradScaler is enabled, but CUDA is not available.  Disabling.
  warnings.warn("torch.cuda.amp.GradScaler is enabled, but CUDA is not available.  Disabling.")
Loading searcher for index test_tickets_full_text_all for the first time... This may take a few seconds
/home/german/.pyenv/versions/3.11.3/envs/agile_clean/lib/python3.11/site-packages/torch/cuda/amp/grad_scaler.py:120: UserWarning: torch.cuda.amp.GradScaler is enabled, but CUDA is not available.  Disabling.
  warnings.warn("torch.cuda.amp.GradScaler is enabled, but CUDA is not available.  Disabling.")
[Feb 07, 01:05:06] #> Loading codec...
[Feb 07, 01:05:06] #> Loading IVF...
[Feb 07, 01:05:06] Loading segmented_lookup_cpp extension (set COLBERT_LOAD_TORCH_EXTENSION_VERBOSE=True for more info)...
Using /home/german/.cache/torch_extensions/py311_cu117 as PyTorch extensions root...
Emitting ninja build file /home/german/.cache/torch_extensions/py311_cu117/segmented_lookup_cpp/build.ninja...
Building extension module segmented_lookup_cpp...
Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
ninja: no work to do.
Loading extension module segmented_lookup_cpp...
[Feb 07, 01:05:06] #> Loading doclens...
100%|███████████████████████████████████████████████████████████████| 1/1 [00:00<00:00, 2388.56it/s]
[Feb 07, 01:05:06] #> Loading codes and residuals...
100%|████████████████████████████████████████████████████████████████| 1/1 [00:00<00:00, 316.55it/s]
[Feb 07, 01:05:06] Loading filter_pids_cpp extension (set COLBERT_LOAD_TORCH_EXTENSION_VERBOSE=True for more info)...
Using /home/german/.cache/torch_extensions/py311_cu117 as PyTorch extensions root...
Emitting ninja build file /home/german/.cache/torch_extensions/py311_cu117/filter_pids_cpp/build.ninja...
Building extension module filter_pids_cpp...
Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
ninja: no work to do.
Loading extension module filter_pids_cpp...
[Feb 07, 01:05:06] Loading decompress_residuals_cpp extension (set COLBERT_LOAD_TORCH_EXTENSION_VERBOSE=True for more info)...
Using /home/german/.cache/torch_extensions/py311_cu117 as PyTorch extensions root...

Forgot to mention but:

Is there a way to force only download dependencies to run on CPU?
I'm looking into this! It's a bit annoying but I'm looking into either having a [gpu] or [cpu] install flag to avoid both being the default.

@bclavie Thanks for you response! I was playing with this and I found a work around.
Pre installed torch hardcoding the cpu tag:
pip install --no-cache-dir torch==2.2.0+cpu -f https://download.pytorch.org/whl/torch_stable.html
then installed sentence_transformers, transformers, etc.
Then RAGatouille....
All Cuda/Nvidia libraries are gone and the index was back to working properly.

@bclavie Thanks for you response! I was playing with this and I found a work around. Pre installed torch hardcoding the cpu tag: pip install --no-cache-dir torch==2.2.0+cpu -f https://download.pytorch.org/whl/torch_stable.html then installed sentence_transformers, transformers, etc. Then RAGatouille.... All Cuda/Nvidia libraries are gone and the index was back to working properly.

Yeah this is what I figured! I think in an upcoming "major" release I'm going to remove a lot of dependencies from the main library, and add very visible warning messages about no backend being installed if no version of torch is present, similar to huggingface transformers. This hopefully will only slightly increase the barrier to entry but greatly help with a lot of dependency issues.

@bclavie we are still facing hanging issue at this point while indexing or RAG.search-
Loading decompress_residuals_cpp extension (set COLBERT_LOAD_TORCH_EXTENSION_VERBOSE=True for more info)...
we are working with ragatouille version- 0.0.8.post4


Netcheck timeouts on high latency networks

I have been testing Delta Chat with iroh-gossip realtime channels on a network with high latency (>10s ping) and while Delta Chat worked for sending messages, p2p channels failed to connect.
Apparently netcheck has a very low timeout with no backoff:
https://github.com/n0-computer/iroh/blob/4dd69f44d62e3b671339ce586a2f7e97a47559ff/iroh-net/src/netcheck/reportgen.rs#L50-L51
Is it true that there is no way to use iroh-net when network has >5s RTT?

The short answer is, yes. In most scenarios we are currently deploying to, latency larger than this is an indicator that the device is offline/things are broken.

There are quite a few things that will break on networks with this kind of latency, for example most hole punching strategies will fail, because routers often keep things open for only around 5 seconds.

this is about the port mappings inside the router, when no connection has been established yet, which are often times much shorter
re relay connection, sure in theory that can be made to work, but it will take some thinking anf work to do so, without making things worse for folks on lower latency connections, as failing fast is often times very desirable


Add launch configuration for also debugging MicroProfile extension

It is sometimes necessary to debug both the Quarkus and MicroProfile
project folders at once
extensionDevelopmentPath option may be provided multiple times,
permitting the debugging of multiple extensions at once
The new configuration assumes a contributor has placed the
vscode-quarkus & vscode-microprofile project folders under the same
folder

See https://github.com/microsoft/vscode/issues/72500 . Though not heavily documented, this seems to be working for me, and not having to build .vsix or do some .vscode/extension symlinking seems very convenient.
Signed-off-by: Roland Grunberg<EMAIL_ADDRESS>

Let's add this configuration to the CONTRIBUTING file : https://github.com/redhat-developer/vscode-quarkus/blob/master/CONTRIBUTING.md#testing-vscode-quarkus

I'm Ok to merge the PR. @rgrunber do you want to update something?

I'm Ok to merge the PR. @rgrunber do you want to update something?

No, I think this is fine. Has the UI of VS Code changed since the guide was done ? I noticed the old entries had the extension mentioned in round brackets, and even things like terminal icon were present. My image doesn't match exactly, but it's close enough :P


[5.5] Add array type hinting

Should we add type hinting also for known classes? For example here $previous should be \Exception object but type hinting for it is also missing

Thanks, but this is technically a breaking change.


Monthly host report

This includes quite a few changes that should be reviewed.
Most importantly:

Added Transaction.HostId
Added User.isHost
Added User.currency (for hosts)
Using fixer.io to get the amount in the currency of the host for expenses in a different currency

I've also written an extensive migration script.
And I've included a small dataset from wwcode (sanitized) to make it easier to test the hostlib without having to create a gazillion of transactions and collectives.

Coverage decreased (-0.03%) to 80.992% when pulling 1b7fd549a21b0c3784223df914fe2ea7b70315c3 on monthlyHostReport into b7b90c7b180902cc239c6bc86ada5d908052044c on master.

Tests finally pass. @asood123 can you review?
Happy to hop on a call if that's useful.

can you merge master into this branch? it has changes that are already merged.

Coverage decreased (-0.02%) to 80.986% when pulling ad5a6ef41ecd9175f4c9b20588540129d7b82bf3 on monthlyHostReport into 689eba8f4509a34f5d5028ea7b0e98d35ef08f4b on master.

Coverage decreased (-0.02%) to 80.986% when pulling ad5a6ef41ecd9175f4c9b20588540129d7b82bf3 on monthlyHostReport into 689eba8f4509a34f5d5028ea7b0e98d35ef08f4b on master.

Coverage decreased (-0.01%) to 80.991% when pulling 99eecddfe3573872ca10a33820b9ca359cab465b on monthlyHostReport into 689eba8f4509a34f5d5028ea7b0e98d35ef08f4b on master.

Coverage decreased (-0.01%) to 80.996% when pulling 4c47116ff2f9c1e6c8dc48567cbf153a6046fc60 on monthlyHostReport into 3460353eab6eab13cecf198f6de8d3b938b96708 on master.

Coverage decreased (-0.01%) to 80.996% when pulling 0bc4b331c31cb0c5e85e740794d4b67fa115eb46 on monthlyHostReport into 3460353eab6eab13cecf198f6de8d3b938b96708 on master.

Coverage decreased (-0.1%) to 80.887% when pulling d87f54ae4c8c4b239acb1b1ad0d7b094a2501dd8 on monthlyHostReport into 3460353eab6eab13cecf198f6de8d3b938b96708 on master.

Coverage decreased (-0.1%) to 80.827% when pulling b206e5816800de7765ccda3e624e037107ed5755 on monthlyHostReport into 60d96a283df6debb7a8374427c1af581a88d05b6 on master.


ORC-1709: Upgrade GitHub Action setup-java to v4 and use built-in cache feature

What changes were proposed in this pull request?

upgrade GitHub Action setup-java from v3 to v4
Also:  setup-java supports a "cache" attribute.  This allows us to remove the "cache" action from the workflow.
The "cache" attribute is documented in the setup-java README:
https://github.com/actions/setup-java/blob/main/README.md

Why are the changes needed?

v4 is the latest version of setup-java
How was this patch tested?

GitHub Actions workflow.
Was this patch authored or co-authored using generative AI tooling?

No.

cc @williamhyun

Gentle ping for the above comment, @sullis .
If we are not sure, let's revert cache: 'maven' part and recover the old one. I believe the version bump is enough.

Gentle ping, @sullis .

Failed to save: Unable to reserve cache with key setup-java-Linux-maven-fc278625f3aefc0088ce0c0131f0800ddbf48815b63ee075e7d3fc5a9c1f392f, another job may be creating this cache. More details: Cache already exists. Scope: refs/pull/1925/merge, Key: setup-java-Linux-maven-fc278625f3aefc0088ce0c0131f0800ddbf48815b63ee075e7d3fc5a9c1f392f, Version: 3d88543681947283edf8997cb89a71c1522b2e39bc75c36ae780bd628eb8559d
Cache saved with the key: setup-java-Linux-maven-fc278625f3aefc0088ce0c0131f0800ddbf[4](https://github.com/apache/orc/actions/runs/8990923635/job/24698981632#step:9:4)8815b63ee075e7d3fc5a9c1f392f

@sullis Is this working correctly?

Interesting.   I'd like to know if "Failed to save: Unable to reserve cache with key " is repeatable.
Can you re-run the workflows?

Do you have a JIRA ID? I can assign ORC-1709 to you.


Bugfix/budget association

Are you a current Fivetran customer?

Fivetran employee
What change(s) does this PR introduce?

Added budget_association_status into the stg_microsoft_ads__campaign_daily_report table in order to account for campaign budgets that end midday. Including budget_association_status as another grain to test by, will reduce tests failing due to non-uniqueness of rows. This change will therefore yield an update this package's integration_tests/seeds/microsoft_ads_campaign_performance_daily_report_data.

Did you update the CHANGELOG?

[x] Yes

Does this PR introduce a breaking change?

[ ] Yes (please provide breaking change details below.)
[x] No  (please provide an explanation as to how the change is non-breaking below.)

Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)

[ ] Yes
N/A rolling out with dbt utils 1.0 and buildkite migrations

Is this PR in response to a previously created Bug or Feature Request

[x] Yes, Issue/Feature [link bug/feature number here]
[ ] No

How did you test the PR changes?

[x] CircleCi
[x] Local (please provide additional testing details below)

Select which warehouse(s) were used to test the PR

[x] BigQuery
[x] Redshift
[x] Snowflake
[x] Postgres
[x] Databricks
[x] Other (provide details below)

Provide an emoji that best describes your current mood

:dancer:
Feedback
We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your feedback on our existing dbt packages or what you'd like to see next.

to do:

[ ] regenerate docs after pr review


#88 feature adds exif data to pdf file

it uses cli params or title and author of first document
adds --author -a cli param for cover and exif data

closes #88

Thank you for this.
Would you be interested in exploring pdf-lib as an alternative library for this purpose?
I'd like percollate to use as few external binaries as possible (since Puppeteer already causes installation problems on various platforms) and opt for a more targeted, Node-native PDF library.

This is very cool, I'm glad pdf-lib works well for this!
Functionally, the one thing I'd adjust is write the PDF to the disk just once. In puppetteer's pdf() method, when you omit the path option, you get a Buffer instead of it writing to the disk, and you can pass that Buffer to PDFDocument to make the metadata changes, then finally write it to output_path in bundlePDF.
(I can also do this after merging into master, if you prefer)

Sure, I prefer you doing it, sounds like you have a plan :)

Awesome, thanks again!


Allow bin/dep wrapper script for dep to work on Windows.

Previously the script only worked on Linux and macOS.
Make it work on Windows too.

This builds on #270.

Rebased.


updated translation for portuguese

merged. I'll include the translations in the next release with credits mentioned to you. Thank you.

;)

<string name="reply_to">Reply to %1$s</string>

will you please translate this please ?

Ok


Replace deprecated GitHub Actions set-output commands

Description
See https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/ for more information.  The Debug Toolbar test workflows will begin failing on June 1st without this change.
Checklist:

[ ] I have added the relevant tests for this change.
[ ] I have added an item to the Pending section of docs/changes.rst.

Thank you!


Show Discord user's color in-game

Can there be a placeholder to have the Discord users role color be displayed in-game? Like maybe %user_color% or something?

Implemented in V3 beta, just not documented yet


SQLAlchemy support / MySQL, PostgreSQL, Oracle, Microsoft SQL Server... support

Hello,
it will be nice if a connection to SQLAlchemy (engine) could be pass to requests-cache (maybe using backend argument). cache_name could be the name of the table.
see http://docs.sqlalchemy.org/en/rel_0_9/core/engines.html
It will provide more DB support (MySQL, PostgreSQL, Oracle, Microsoft SQL Server...)
Pandas is doing something similar:
http://pandas.pydata.org/pandas-docs/stable/generated/pandas.io.sql.read_sql.html
APSScheduler also
https://apscheduler.readthedocs.org/en/latest/
Kind regards

backend argument could be

a SQLAlchemy engine
a database URI dialect+driver://username:password@host:port/database
a table URI dialect+driver://username:password@host:port/database::tablename

Maybe this project could help https://dataset.readthedocs.org/

@femtotrader I've spent all day trying to implement your suggestion.
This is the error I should get b/c those methods are not supported:
ValueError: Unsupported backend "Engine(mysql+pymysql://un:pw@ip_address:port)" try one of: sqlite, memory, redis
Connecting to an external database is not possible using requests-cache, from what I can tell. If there is a way, please let me know!

Personally I don't think a relational database is a good backend for a caching system, and Redis and the other backend options are much better optimized for this kind of use case.
However, if someone really wants this, you are welcome to submit a PR for it!

Several releases later, I think this library is in a better position to add support for SQLAlchemy without introducing a huge amount of complexity. And if a full ORM model for response metadata was added (to use instead of a serialized blob), this would enable some other features relevant to large caches and using responses outside of requests-cache.
@femtotrader Since you opened this 7 years ago (!!), I'm guessing this is no longer relevant to you, but I will reuse this issue since you were the first to request it.


Create rrd images only on demand. Added command line switch --with-img.

Merged in 8d7e355 into dev branch.


I tested this issue, and now it works fine.


Add an APK or Play Store Link

Please add APK file or Playstore link.
it will be helpfull

Its a dead project I didn't finish, unfortunately 🙁


Detect usage of block-scoped variables from earlier case blocks

Fixes #19503
Note that this has the possibility to incur a false positive:
let sHasBeenSet = false;
switch (n) {
    case 0:
        let s = "ok";
        sHasBeenSet = true;
    case 1:
        if (sHasBeenSet) {
            s; // ok by construction
        }
        break;
}

@typescript-bot user test this

@typescript-bot test this

FWIW, despite technically being a false positive, I find the sample code in the OP to be... somewhat suspicious, to put it lightly.  Fallthrough is a thing, but cases still look like blocks regardless.  If I found that in a code review, I'd immediately suggest moving the declaration of s outside of the switch.

@RyanCavanaugh do you want to come back to this? It's been sitting for a long time.

I'm not super keen on this one to be honest.


Initial dark mode implementation

the initial solution for issue #41.
Added less variable override for dark mode.
Some code cleaning for arbitrary color/background-color settings.
Tested on home page, sidebar, and most admin table components.
TODO: set up all other components and fix inappropriate color override of each component for light/dark mode.

Is this PR working?  I get

styled-components is a module that needs to be installed. Try npm install styled-components

Thanks -- that's better!

It does seem to basically work for me (though the middle pane seems to be getting cut off on the left a bit).  I notice that there is also one conflicting file at the moment -- we should merge the current master into the PR.

Thanks for letting me know. The conflicting file has been solved manually. I deleted lines of code that are no longer used in the master branch and updated this PR. There should be no conflict to merge now. I think it's better to open an issue about any color that looks off when switching mode with screenshots, so that @dlwangyilin and I can look into them. Thank you!


Makefile: Add architecture variations to the artifact targets

Did you test this? Looks like a no-op to me
GOOS=linux GOARCH=amd64 CC=x86_64-linux-gnu-gcc make clean binaries

artifact-linux-aarch64: ENVS=GOOS=linux GOARCH=arm64 CC=aarch64-linux-gnu-gcc
artifact-linux-aarch64: _artifacts/lima-$(VERSION_TRIMMED)-Linux-aarch64.tar.gz
Or at least I thought the env is now on a separate line?

Was a bit late to the review, I also found the ENVS a bit confusing but seems to be very compact.
You can replace the phony target of "mkdir-artifacts" with a real target of "_artifacts", as a minor.
_artifacts/lima-%.tar.gz: _artifacts
	$(ENVS) make clean binaries
	$(TAR) -C _output/ -czvf $@ ./

_artifacts:
	mkdir -p $@

And probably just hide it from the output with a @

Thanks! 🙏🏻

You can replace the phony target of "mkdir-artifacts" with a real target of "_artifacts"

I considered that approach as well, but since the number of lines doesn't change, I decided to keep the current format, where the target names make it clear what they do.


Wayland: Blurry rendering under high DPI

Reported on twitter: https://twitter.com/williamsgarth/status/1156646606894260224
Seems likely we aren't getting the proper DPI in this case - I wonder if the more robust APIs in GLFW 3.3 will help?

It looks it might be related to going though xwayland instead of native. Other non-native apps like electron have the same issue.

Is this related to https://github.com/revery-ui/revery/issues/528 ?

How is this looking now that the scaling support is better?
Also noticed my issue in Revery is still open...I should probably close that.

This seems to be solved now, latest oni version renders just fine.

Great news! Thanks @janza for checking 🎉 I'll close this out, but if there are still issues we can track in a new one

@bryphe Just tested the latest build under swaywm (wayland), unfortunately it's still not fixed.
The problem seems to be that wayland is not supported natively by onivim2, so it's running through xwayland emulation. Gnome will do some magic to fix scaling issues with x apps running via xwayland, but wlroots based desktops won't do that and simply scale up the image, so it looks very blurry.

Hi @garth, you should be able to pass SDL_VIDEODRIVER=wayland in environment variables to run in native Wayland mode. Fair warning, the Wayland protocol doesn't actually allow for fractional scaling so on wlroots based desktops it will still be slightly blurry (unfortunately not much we can do there.) We may be able to tie into whatever interface kframeworks exposes to get sharp fractional scaling on Kde but that would be a separate push that wouldn't carry over to other desktops.

Thanks @szbergeron, I had tried GDK_BACKEND, but not seen SDL_VIDEODRIVER before.
So, I can confirm that it's working under sway with SDL_VIDEODRIVER=wayland.
I'm aware of the fractional scaling, so generally stick with a factor of 2 and use font sizing to fine tune.

@garth so revery itself actually supports full fractional scaling now, I forget what the flag is off the top of my head but it can draw all UI and fonts at the requested fractional scale. It's just there's no way to make it do that automatically (rather than the user manually setting it)

@szbergeron only issue with SDL_VIDEODRIVER=wayland seems to be that the window doesn't resize, so whatever size it starts with is fixed until the app is restarted.

@garth yep, was able to repro earlier, forgot to open a bug. It's a cross-desktop wayland thing, not yet sure the cause is in SDL or in reason-sdl2


Download contract metadata

Closes #34

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

83 of 86 (96.51%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.7%) to 91.765%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

app/services/contract_metadata_service.py
73
76
96.05%

Totals

Change from base Build<PHONE_NUMBER>8:
0.7%

Covered Lines:
624

Relevant Lines:
680

💛  - Coveralls


Nix: fix make_fstar_version.sh

The call to make_fstar_version.sh in Nix doesn't set the commit value properly since the git repository is not available in the Nix sandbox.
In this PR I set the FSTAR_COMMIT variable from the Nix expression, so that the script works properly when called.
Sadly, I can't retreive the commit date in a similar way, this one stays "unset".

Thank you!


[Meta] Views Experimental Release

Views is a way to project indices in OpenSearch, these views act as a focal point for describing the underlying data and how the data is accessed.  It allows for restricting the scope and filtering the response consistently.
Resource types are a way to generically describe resources, a new section within the Security Role can express these.
Tasks

[ ] #3888

[ ] Add views to the cluster metadata schema
[ ] Search view
[ ] Get buy in from OpenSearch maintainers for experimental feature release approval in 2.x

[ ] #3889

[ ] Resource interfaces
[ ] Resource validation patterns
[ ] Expose resource type & id mappings to downstream system

[ ] #3890

[ ] Update to the security configuration for new resource section

[ ] End to end test cases
[ ] Security Review

Additional Context

Design doc

https://github.com/peternied/OpenSearch-1/blob/views/server/src/main/java/org/opensearch/index/view/views-design.md

Feature Prototype

OpenSearch https://github.com/peternied/OpenSearch-1/pull/139
Security https://github.com/peternied/security/pull/14

[Triage] Going to mark this as triaged since we have a pretty clear path forward and would definitely accept any PRs towards this effort. Thanks @peternied :)


Use GC.malloc_atomic with GC.realloc, not Pointer#realloc

This PR ensures that pointers allocated using GC.malloc and GC.malloc_atomic are only reallocated using GC.realloc. This is necessary for the interpreter to run on Windows properly, and may also be relevant on other systems if eventually the interpreter's GC is distinct from the compiler's own GC.
Pointer.malloc and Pointer#realloc are defined as primitives. For compiled code, these internally call the top-level funs __crystal_malloc64, __crystal_malloc_atomic64, and __crystal_realloc64, which in turn forward to the class methods on GC, so Pointer and GC's methods happen to be exactly the same:
https://github.com/crystal-lang/crystal/blob/a5054ce80659975b7bf5ac5240c3bb63dc85093c/src/gc.cr#L16-L47
For interpreted code, the same primitives call Pointer.malloc and Pointer#realloc from the compiler itself:
https://github.com/crystal-lang/crystal/blob/a5054ce80659975b7bf5ac5240c3bb63dc85093c/src/compiler/crystal/interpreter/instructions.cr#L1004-L1015
Currently, the compiler on Windows is statically linked, whereas LibGC inside interpreted code would be dynamically loaded (using #11573 and #12140); there would be two copies of the garbage collector which do not conflict like on Unix-like systems. Consequently, allocating memory from one allocator and then reallocating it in another is undefined behavior.
All instances of GC.malloc in the repository are already paired to GC.realloc. Note also that adding @[Primitive] to GC's class methods doesn't work because these have different signatures than the methods in Pointer.

I'm wondering if we should also take steps to reduce the error probability through the API. Pointer#realloc is very inviting to be used, even if the pointer was allocated via GC.malloc. The fact that it doesn't make a difference in most cases, doesn't help either.
An idea might be to make Pointer#realloc a class method Pointer.realloc. So there'd be Pointer.malloc/Pointer.realloc analog to GC.malloc/GC.realloc.

There's another one in io_spec.cr
I think the main issue is that there's no Pointer.malloc_atomic, so we have to use GC.malloc_atomic. So maybe we should consider adding that. It would remove all uses of GC.realloc.
We could even hide GC.malloc and GC.realloc completely with that.

Pointer.malloc uses GC.malloc_atomic when the pointer type is known to contain no pointers.
So I suppose it could simply be implemented in stdlib by delegating to Pointer(UInt8).malloc:
struct Pointer(T)
  def self.malloc_atomic(size : UInt64)
    Pointer(UInt8).malloc(size * sizeof(T)).as(T*)
  end
end

It would be odd if Pointer.malloc may allocate atomically and Pointer.malloc_atomic always does so. For consistency we would need yet another method that never allocates atomically. In particular, this seems to be required here:
https://github.com/crystal-lang/crystal/blob/f160040b7f073f6cb56f2c440b2be521f84a5003/src/log/metadata.cr#L33-L38
This raises another question actually. If the interpreter calls Pointer(Void).malloc for any use of Pointer.malloc in interpreted code, wouldn't that always choose the atomic version? Is that fine?

Pointer(Void).malloc is actually not atomic because Void is considered as potentially containing inner pointers (because it's just unknown what type it actually is).
https://github.com/crystal-lang/crystal/blob/f160040b7f073f6cb56f2c440b2be521f84a5003/src/compiler/crystal/codegen/types.cr#L48-L61


Adding support to Portuguese - remote8 - lockedMaster

Sounds like there are some minor edits to make but think it's worth merging+deploying this first version so we can give it to anyone who's practicing the level :P


fix(chore): use '--typescript' flag in create-react-app project tests

This PR introduce changes that swicth from using additional dependency (react-scripts-ts) in create-react-app project tests - with --typescript flag for create-react-app utility being used instead.
This move solves the following problems:

removes dependency onreact-scripts-ts dependency
follows suggested approach to create TS projects: https://facebook.github.io/create-react-app/docs/adding-typescript
fixes problem that has been introduced by recent dependency updates of react-scripts-ts - this one has resulted in failed builds even for clean TS-based create-react-app project, and, in particular, has failed corresponding Stardust tests

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS


Api info reorganization

What does this PR (Pull Request) do?

[x] This PR is not related to any Issue

This PR restructures the familiar api.APIInfo struct a bit. It retains a reference to an http response writer, allowing many api package functions to be aliased with a much shorter argument list.
For example,
api.HandleErr(w, r, inf.Tx.Tx, errCode, userErr, sysErr)

can be called as simply
inf.HandleErr(errCode, userErr, sysErr)

... allowing you to pass only the information that has actually changed since the handler function's execution began.
New methods include aliases for response writing, some IMS/IUS/IM niceties, parsing/parse-and-validating, and a handler for parsing and writing db errors in the same step, which converts
if err := dbOperation(); err != nil {
    userErr, sysErr, errCode := api.ParseDBError(err)
    api.HandleErr(w, r, inf.Tx.Tx, errCode, userErr, sysErr)
    return
}

into
if err := dbOperation(); err != nil {
    inf.HandleDBErr(err)
    return
}

This also changes the info struct's name from api.APIInfo to api.Info (because the former "stutters"), moves it and its methods to its own file, and changes the Version member from a reference to an api.Version to just an api.Version value. Apart from naming, call signature (now requires the response writer to construct) and that one field change, most code is untouched. However, the /acme_accounts handlers have been retooled to showcase the new Info methods, and part of the DSRs handler was also done to show off an IMS-related method (because /acme_accounts does not support IMS requests).
Also, this PR removed the deprecated /lib/go-tc.GetHandleErrorsFunc and the last three places it was used.
Which Traffic Control components are affected by this PR?

Traffic Ops

What is the best way to verify this PR?
Make sure unit and client/TO integration tests still pass.
The following criteria are ALL met by this PR

[x] This PR includes tests
[x] Documentation is unnecessary, because the changes only affect internal development.
[x] An update to CHANGELOG.md is not necessary because client-facing behavior is unaltered.
[x] This PR includes any and all required license headers
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY

Superseded by #7902


home page responsive breakdown

page is not responsive at dimension  680 by 1017. Media queries need to be updated.
Steps to regenerate:--

go to main site .
Inspect the page set dimension as mentioned by resizing the page.
you will see the error in  "best of sections".

Waiting for the issue to be assigned.

@ankit-0369 Please star the repository and make sure to follow me (https://github.com/Karamraj/).

@ankit-0369
Join Discord Server for this repo - https://discord.gg/SH6XRrHs8E

@ankit-0369
Join Discord Server for this repo - https://discord.gg/SH6XRrHs8E

Thank u for the link will join.