Fields missing when exporting an entry

Fields seem to be missing when exporting a collection in "Better BibLatex" Format.
The test collection contains 1 entry,
exporting as default biblatex produces expected output.
exporting as "better biblatex" produces an entry with all of the fields missing.
The gist contains:
(1) zotero RDF export of the collection
(2) better biblatex export showing bug.
(3) default biblatex export showing expected output.
https://gist.github.com/benblamey/765c9fb20f751990ae33

When I export that entry using Better BibLaTeX, I get
@book{last2015,
  title = {test title},
  volume = {1},
  timestamp = {2015-09-11 22:24:54},
  series = {1},
  author = {last, first},
  date = {2015}
}

could you do the following for me:

Enable "extended debugging" in the BBT preferences
Select this entry in your library and export it using Better BibLaTeX
Select this entry in your library, right-click, and select "send ZotPlus report"
Post the resulting ID displayed when you click through here

Report ID: 8RXZZZRU

There's nothing in the error log. Sometimes other firefox extensions interfere with BBT (there are at least 3 I know of), but before we look at that, could you try going into BBT prefs first, go to the debug section, and click "reset cache"? I still don't know how these entries got into your cache (this is not a format BBT exports as far as I can tell), but we'll look at that later. The same goes for #344.

I can tell your cache is off, that's in the debug info -- I'm just not sure about the way that bibtex got into your cache in the first place, so I don't know yet it will not simply regenerate and recache that broken bibtex.

Please don't reset the cache yet! See #344 -- I want to know what's behind the cache not updating.

FYI -- could this relate to running Zotero standalone at the same time as running it in the browser? Is this usage supposed to be supported? (I might have been doing this at the time of the original import)

Yes, it could in principle relate to such; the behaviour of BBT under that scenario is non-deterministic; it's unpredictable at what exact point it will break.
I do want to support it but it's not currently supported, so I don't have an unequivocal answer to your second question, sorry.

Resetting the cache (while not in connector mode) should fix your issues.

Resetting the cache, without running Zotero standalone in the background worked. Thank you.

My pleasure as always.


Gitlab project search by name sometimes picks incorrect project

The following code block will default to the first project in the list.  This sometimes provides the wrong project.
https://github.com/redhat-cop/pelorus/blob/master/exporters/committime/collector_gitlab.py#L36-L38
As an example, a search for 'leia' returned project 'frontend_nelson_quileia'.

Fixed by #209


Final Merge

The things that we did as a group:

Choose the topic for our website and the API.
Choose images, text, icons, and fonts.
Set up the repository and tools
Create the basic shared code on the home page.
Start individual interfaces.
Give code reviews to each other
Work on individual interfaces.
Create a good README and PR description.

We fixed real-time of comments problem + testing issue


Add subscribed landing page

Adds a landing page for users who have just subscribed to the mailing list. In the first PR (#936), I started to remove the unused registration app in addition to adding the landing page. However, until I know how the new email form will work it's difficult to know how to handle the POST action when users subscribe to the list. I won't know that until I have the form, but the AEI team developing the form needs a landing page for testing. Therefore, I will simply add the landing page in this PR. The page looks like:

cc @Peter-Metz @MattHJensen

+1


empty response from local ollama moondream-v2

is the image size too large for restful api?

it should be use http://localhost:11434/api/chat not generate


Add scanning pdf_report method

Downloads a pdf with a full report of an image in a certain date.

@muntzerr would you mind posting an example to this PR for future reference? It definitely sounds like a very useful feature!

@muntzerr would you mind posting an example to this PR for future reference? It definitely sounds like a very useful feature!

@davideschiera I think I address all your comment. I think now it looks better :)


Correction for raw affiliation EA 4294 AGIR, Picardie Jules Verne University, Amiens, France

Correction needed for raw affiliation EA 4294 AGIR, Picardie Jules Verne University, Amiens, France
raw_affiliation_name: EA 4294 AGIR, Picardie Jules Verne University, Amiens, France
new_rors: 01gyxrk03
previous_rors: 01sjmsj73;01gyxrk03
works_examples: W3210896093
contact: 267577c8a024d765c8abcd8295b009ee:49db8adf066442c3a7d6d2bd244a0a06 @ u-picardie.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


[nri-bundle] Added additional configuration flexibility to newrelic-logging

Is this a new chart
No
What this PR does / why we need it:
The changes in this PR provide users the ability to customize the fluent-bit.conf and parsers.conf files using the values.yaml file. Previously, this was statically set in the configmap.yaml file.  The values.yaml file and README were updated for nri-bundle to include examples explaining how to use the new configuration options.
Which issue this PR fixes
See this PR for details.
Special notes for your reviewer:
N/A
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] Chart Version bumped
[X] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [mychartname])

Will re-submit.  Realized I had mixed in unrelated updates.


feat: updated default postgresql version

APL-282
This PR updates the default of the postgresql version used for a cnpg database.

I think offering the image catalog in the charts is a good idea, but I think we should not make this restrictive on the platform versions.
I could imagine the following scenarios:

Users want to migrate their DB here. They can test a recovery here, but if they use basebackup + WAL instead of a dump, and their database is not version 17 yet, this will not work.
There might be products and libraries that are not compatible with, or at least do not officially support PG 17 yet.
There are dozens of drop-in replacements for the official PostgreSQL images, which are not forks but just a packaged PG+Extensions. They often play well with CNPG and I think we should not unnecessarily obstruct their use in the chart. One example is TimescaleDB.

Adding imageCatalogName and imageCatalogKind (for example) with the defaults would accommodate this, because then teams can even maintain their own ImageCatalog.


Better angle field editor for direction tag

Perhaps a circle you can click next to the field that sets the angle in that direction for you, then adjust further with the arrows as needed. Something like this (although probably on the other side now that I see it):

I guess - people can just look on the map though.  We show the cone at z18+:

The cone is awesome and the only reason I even started adding angles/directions for stuff. I guess the issue is you cannot edit it quickly enough or with the mouse/finger (unless it's in increments of 1). You cannot use rotate tool/mode on points. So it's trial and error manually typing it first and then adjusting.

How about instead of adding another control to the field we just let people drag the cone to rotate it?

Here I was wishing I could just grab the tip of that teardrop representing the traffic mirror, and rotate it just right... and click confirm on it. (Currently in fact it indicates 180°.)

For the current arrow buttons

Specify they increase/decrease by 5 degrees in their tooltip; or
Change degrees increased/decreased to 1 and change tooltip accordingly. This is much more intuitive.

A 'step' button/dropdown could be added for a higher increase/decrease, i.e. steps of 1, 2, 5, 10.

Perhaps a circle you can click next to the field that sets the angle in that direction for you, then adjust further with the arrows as needed.

Dials are intuitive, but can be finicky to use. They could still be implemented.

Instead of a dial, a slider could be used (already supported, can also support multiple values and value ranges).

How about instead of adding another control to the field we just let people drag the cone to rotate it?

Make a right click ("Rotate") and hotkey ("R") option, so people don't accidentally rotate the object. For multiple values, tell users to use the slider.
In order to get the required point for specifying the direction, allow clicking on the background, dragging of a 'node' or following a line. Ignore selecting other objects while doing this.
Add a visual indicator for when a larger distance, or multiple aligned objects, are being used to determine direction (selected object may be out of view).

Additionally, option(s) may need to support

multiple values.
value ranges ( #5754 ).
Note, the current text input may not be able to automaticly reflect individual changes in multiple values and value ranges.

Option(s) may need to only support values 0 - 360. An iD Validator warning could be returned for values

which are also used.
lower than 0; negative values. There are few or no use cases for this afaik.
equal to or higher than 360 (and -360). There are no use cases for this afaik.
any other invalid values.
(- on any object which usually does not have a direction.)

Something similar could be done for [incline](https://wiki.openstreetmap.org/wiki/Key:incline).
This would not concern the rotation of ways and areas, as accurate rotation is usually either not needed or bad -for segments with different angles-.

I've seen a different interface for such selectors which consist of multiple radio buttons which are placed around an image. I'm not sure if it would fit in iD's design though. It can be reworked to be a box of the element in the sidebar (like it's done for turn restrictions) with the current imagery as background.

Related https://github.com/streetcomplete/StreetComplete/issues/2514#issuecomment-812751366 (directions for guideposts)

Related https://github.com/streetcomplete/StreetComplete/issues/5765#issuecomment-2261705896 (directions for and distance between objects);
May help to correct POI positions, especially with insufficient imagery.


[HIGH] [Advanced Approval Workflows] Server only returns generic errors when calling SetWorkspaceApproval commands

Problem
When calling Create/Update/RemoveWorkspaceApproval, if there is a server error (like wrong parameters), the server always responds with a generic "there was an error" error.
Why this is important to solve?
It is difficult to diagnose issues on the frontend.
Solution
Have Web-Expensify pass the full error through in the API response
cc @blazejkustra

Daily Update

I created a Web-E PR to improve the error messages

Next Steps

@srikarparsi review and merge the PR
@blazejkustra give it a try on the frontend once it's deployed to staging

ETA

Merged today, Aug 7
Deployed to staging tomorrow, Aug 8

Let me know once it's on staging @tgolen 👀

It's on staging now 👍 I'm going to go ahead and close this out.


Add hetzner cloud as a provider

It would be good to add this provider.
Could I be assigned to this one ?

@pushthat Hello! As mentioned on the Slack channel, I'm okay with this. It would be nice to have one more Cloud provider supported.
If you didn't, make sure to check our Project Walkthrough to learn more about the project, and its structure.
Adding new cloud provider is contained of the following five main points:

Adding logic for creating and managing resources to the cloud package.
Adding the appropriate profile(s) to the profile package. A profile defines how a cluster will be created and provisioned (how many instances, what scripts will be used, firewall rules,..). You can take a look at others to get sense about it.
Once the profile is added, you need to register it in the pkg/cli package, so you can use your profile using CLI.
Add Bootstrap scripts for provisioning master and nodes to the kubicorn/bootstrap repository.
Write documentation about the newly-added cloud provider. Docs go here. The document should look something like this.

Preferably, you can also add an example to the examples package.
I hope I have covered everything. If not I'll update the comment.
We're happy to hear you're interested to contribute to the project! If you have any questions, comment to the issue or send them on our Slack, and we'll try to get back as soon as possible.

I will keep that updated :

[x] Adding logic for creating and managing resources to the cloud package
[x] Adding the appropriate profile(s) to the profile package. A profile defines how a cluster will be created and provisioned (how many instances, what scripts will be used, firewall rules,..). You can take a look at others to get sense about it.
[ ] Once the profile is added, you need to register it in the pkg/cli package, so you can use your profile using CLI.
[ ] Add Bootstrap scripts for provisioning master and nodes to the kubicorn/bootstrap repository.
[ ] Test
[ ] PR
[ ] PR fix
[ ] Write documentation about the newly-added cloud provider. Docs go here. The document should look something like this.
[ ] add an example to the examples package.


When will new version of python kserve library get released?

/kind bug
What steps did you take and what happened:
There are some new changes are quite needed for us. We are wondering when a new version of kserve python library get released? Last release was in February

@yangyang919 which change you are looking for, we plan to release mid May.


feat(bridge): can create sc to log data only, without store state data (#49)

@boomspeed94 please squash your commits, the rest LGTM.

Codecov Report

Merging #113 into master will increase coverage by 13.03%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           master     #113       +/-   ##
===========================================
+ Coverage   82.08%   95.12%   +13.03%
===========================================
  Files          69       69
  Lines        1083     1087        +4
  Branches      118      122        +4
===========================================
+ Hits          889     1034      +145
+ Misses        191       53      -138
+ Partials        3        0        -3

Impacted Files
Coverage Δ

...xide-js/src/blockchain-services/BlockchainModel.ts
100.00% <ø> (+3.22%)
:arrow_up:

...xide-js/src/blockchain-services/TypeDefinitions.ts
100.00% <ø> (ø)

packages/bridge/src/icon/ICONContractAdapter.ts
100.00% <ø> (ø)

...de-js/src/blockchain-services/BlockchainService.ts
100.00% <100.00%> (ø)

.../src/blockchain-services/eos/EosBlockchainModel.ts
100.00% <100.00%> (ø)

...rc/blockchain-services/icon/IconBlockchainModel.ts
100.00% <100.00%> (ø)

.../blockchain-services/icon/IconBlockchainService.ts
100.00% <100.00%> (+59.25%)
:arrow_up:

.../aloxide-js/src/helpers/validate-network-config.ts
100.00% <100.00%> (ø)

packages/api-gateway/src/express-router.ts
45.71% <100.00%> (+45.71%)
:arrow_up:

packages/api-gateway/src/graphql-relay.ts
100.00% <100.00%> (+100.00%)
:arrow_up:

... and 13 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c14e84c...97fe8c4. Read the comment docs.


Anagram Game issue #58

Anagram Game

Thanks for your Contribution!
Keep Contributing!
Gove a Star to this project if you like this!
Happy Hacktober!


Issue #76: Add configurable update rate

Issue #, if available: #76
Description of changes:

Add configurable update interval and back-off time. Slight refactoring was required in order to transfer the values from the GitHub inputs to where they are used. SDK-specific configuration parameters and general action configuration values (currently just the update rate configuration) are treated slightly differently and are passed as separate objects to the building and waiting functions.
Add new test for handling the update rate configuration
Update existing tests where needed
Add new inputs to action metadata file
Update README.md

Default values are kept the same (30s interval, 15s back-off), so there should be no breakage when updating.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Check any applicable:

[ ] Were any files moved? Moving files changes their URL, which breaks all hyperlinks to the files.

Superseded by #116


Android segfault when reading from fd in deep call stack

Opening an issue to track work.
From @conectado's findings:

So a bit of a summary on the segfault I'm finding, so, this function:

    #[tracing::instrument(level = "trace", skip(self, iface_config, device_io))]
    async fn iface_handler(
        self: &Arc<Self>,
        iface_config: Arc<IfaceConfig>,
        device_io: DeviceIo,
    ) -> std::io::Result<()> {
        let mut src = [0u8; MAX_UDP_SIZE];
        let mut dst = [0u8; MAX_UDP_SIZE];
        device_io.read(&mut src[..iface_config.mtu()]).await;
        tracing::trace!(?dst);
        Ok(())
    }

segfaults with SEGV_ACCERR  (Note that this is simplified to have some minimal repro of the bug, this doesn't work)
This is called from:

    #[tracing::instrument(level = "trace", skip(self))]
    pub(crate) async fn start_iface_handler(self: &Arc<Self>) {
        let Some(device_io) = self.device_io.read().clone() else {
            let err = Error::NoIface;
            tracing::error!(?err);
            let _ = self.callbacks().on_disconnect(Some(&err));
            return;
        };
        let Some(iface_config) = self.iface_config.read().clone() else {
            let err = Error::NoIface;
            tracing::error!(?err);
            let _ = self.callbacks().on_disconnect(Some(&err));
            return;
        };
        let device_writer = device_io.clone();
        self.iface_handler(iface_config, device_io).await;
    }

And device_io.read works as:

    pub async fn read(&self, out: &mut [u8]) -> std::io::Result<usize> {
        self.0
            .async_io(Interest::READABLE, |inner| inner.read(out))
            .await
    }

With inner.read being:

    pub fn read(&self, dst: &mut [u8]) -> std::io::Result<usize> {
        match unsafe { read(self.fd, dst.as_mut_ptr() as _, dst.len()) } {
            -1 => Err(io::Error::last_os_error()),
            n => Ok(n as usize),
        }
    }

Buuut... if I reduce the size of the buffer of src and dst to 1500 , it doesn't crash
If I inline, manually, iface_handler into start_iface_handler it doesn't crash, (but if I use #[inline(always)] it does)
if I redefine iface_handler to:

    #[tracing::instrument(level = "trace", skip(self, iface_config, device_io))]
    async fn iface_handler(
        self: &Arc<Self>,
        iface_config: Arc<IfaceConfig>,
        device_io: DeviceIo,
    ) -> std::io::Result<()> {
        let mut src = [0u8; MAX_UDP_SIZE];
        device_io.read(&mut src[..iface_config.mtu()]).await;
        let mut dst = [0u8; MAX_UDP_SIZE];
        tracing::trace!(?dst);
        Ok(())
    }

It doesn't crash
and right now, I think the last one is the biggest clue. I'll start using objdump/gdb to figure out what's happening

Adding our latest findings:
The function where it segfaults is here:
0000000000be9ea0 <_ZN15firezone_tunnel13iface_handler55_$LT$impl$u20$firezone_tunnel..Tunnel$LT$C$C$CB$GT$$GT$13iface_handler28_$u7b$$u7b$closure$u7d$$u7d$17h67d7cc3efd6c4e7fE>:
  be9ea0:	49 89 e3             	mov    r11,rsp
  be9ea3:	49 81 eb 00 00 0c 00 	sub    r11,0xc0000
  be9eaa:	48 81 ec 00 10 00 00 	sub    rsp,0x1000
  be9eb1:	48 c7 04 24 00 00 00 	mov    QWORD PTR [rsp],0x0
...

Precisely in be9eb1. This clued us in to the possibility of the problem being a stackoverflow.
So we increased the threads stack size to 10MB
        let runtime = tokio::runtime::Builder::new_multi_thread()
            .thread_stack_size(10 * 1024 * 1024)
            .enable_all()
            .build()?;

And indeed the segfault didn't happen anymore.
We're still not sure why this happens but this seems like a common problem in tokio.
There can also be some stack issues with android.
So we're going to fine-tune the stack size for now and revisit this later.


Wsa fault

Steps to reproduce
I have activate developer mode but its not working when i am installing apps it says wsa faults .
✔ Expected Behavior
cannot system surf .
❌ Actual Behavior
Wsa fault .
Other Software
NO
Please specify the version of Windows Subsystem for Android
"C:\Users\hp\Downloads\MicrosoftCorporationII.WindowsSubsystemForAndroid_2302.40000.6.0_neutral___8wekyb3d8bbwe.Msixbundle"

For issues starting WSA please file a Windows Feedback Hub report (Windows key + F) under category Apps > Windows Subsystem for Android.

Following up on feedback hub.


Support for encryption with FileCache

Is your feature request related to a problem? Please describe
With https://github.com/opensearch-project/OpenSearch/issues/9987, we'll be implementing block level fetch for fetching segment files from remote storage to local data nodes.
Describe the solution you'd like
Task is to track the efforts required to support block level fetch on encryption files on remote store.
Related component
Storage:Remote
Describe alternatives you've considered
No response
Additional context
No response

[Triage - attendees 1 2 3 4]
From the discussion, its unclear if we'd want to support encryption at this level vs reusing the encryption done at the codec level.  It looks like [1] has more context about these scenarios. Please feel free to re-open after addressing the reason.

[1] #3469


chore: release 1.8.0

:robot: I have created a release *beep* *boop*
1.8.0 (2023-03-07)
Features

add pull_requests attributes (#30) (083bce1)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/inception-health/otel-export-trace-action/releases/tag/v1.8.0 :sunflower:


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 1507 ms

Resolved: Bofrost.lu performance has improved in c4c9668 after 6 minutes.


additional consolidation of env activation code

@maresb  - implements #70

Woah!!! You're on a roll today! :rocket:


Add diff mode to compute difference only using primer positions

Since it is useful to do diffs with all sorts of BEDs, including non-standard compliant ones, this adds a flag to diff to let it operate on only the chromStart and chromEnd positions.

Looks good


What are the memory requirements for serving the model at prediciton stage?

@kimiyoung @zihangdai My fine tuned model for imdb classification clocked in at ~4gb, do you think that a model of this size will need to be served on at least a GPU to serve predictions? Also any idea of the memory requirements would be greatly appreciated.

Hey @CharlieBickerton do you know how to export the model to serve it?
I have this right now:
def serving_input_fn():
with tf.variable_scope("model"):
feature_spec = {
"input_ids": tf.FixedLenFeature([MAX_SEQ_LENGTH], tf.int64),
"input_mask": tf.FixedLenFeature([MAX_SEQ_LENGTH], tf.int64),
"segment_ids": tf.FixedLenFeature([MAX_SEQ_LENGTH], tf.int64),
"label_ids": tf.FixedLenFeature([], tf.int64),
}
serialized_tf_example = tf.placeholder(dtype=tf.string,
shape=[None],
name='input_example_tensor')
receiver_tensors = {'examples': serialized_tf_example}
features = tf.parse_example(serialized_tf_example, feature_spec)
return tf.estimator.export.ServingInputReceiver(features, receiver_tensors)
EXPORT_DIR = 'gs://{}/export/{}'.format(BUCKET, TASK_VERSION)
estimator._export_to_tpu = False  # this is important
path = estimator.export_savedmodel(EXPORT_DIR, serving_input_fn)


Updated Search Bar Style

Search Bar

Updated Search Bar added in the index.html

Describe the changes you've made

modified:   assets/css/style.css
modified:   index.html

Describe if there is any unusual behaviour of your code
NA
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] New and existing unit tests pass locally with my changes.

Screenshots

Note
I am GSSOC'21 participant so kindly add gssoc tag in this pr.

@Fab-Gaurav Since the UI has been updated this feature has become obsolete. This will break our existing code base. We are sorry to inform you that.
Feel free to look around, there are plenty of things that can be added or modified within this project. Create an Issue we will be happy to assign you that.
I'm closing this PR for now.

@Fab-Gaurav Since the UI has been updated this feature has become obsolete. This will break our existing code base. We are sorry to inform you that.
Feel free to look around, there are plenty of things that can be added or modified within this project. Create an Issue we will be happy to assign you that.
I'm closing this PR for now.

@991rajat Will you please have a look on issue https://github.com/Vishal-raj-1/Awesome-JavaScript-Projects/issues/651
Should I work upon it.


BoxConv1D

Hi, Great work. Thanks for sharing.
Could you give me some hints for modifying it to a boxconv1D, please?

Hi, thanks. Try hard-fixing y_min and y_max to 0 and 1 (or maybe 0 and 0...I don't remember the convention). This way all filters will be N × 1.


[Question] Will implementation crates be published to crates.io?

Hey first thank you for creating this awesome tool!
I am curious if the implementation crates in ruff would be published to crates.io? That would be nice since I would like to leverage it for some python-related tools.

We currently have no plans to publish the crates but we could reconsider for some specific crates if someone's interested in setting up a release process. See https://github.com/astral-sh/ruff/issues/10417 and https://github.com/astral-sh/ruff/issues/43


Integrate solar radiation

Follow up on the discussion in #62
@clampr @adriesse I took the liberty of making a new issue for this.

Hi @l-kotzur & @adriesse,
Let's continue this conversation here.
As mentioned by @l-kotzur, solar radiation data has already been added to some of the import routines. So Meteostat is presently collecting this data. However, it is not redistributed through our interfaces atm.
The reason is mainly a planned re-structuring of Meteostat's architecture which will put this Python library in the center of the architecture. This is going to be a completely new version which requires most code to be rewritten.
Before any work on the new version of the library can begin, I'd like to get feedback on the idea. Therefore, I will soon open a new issue which describes the concept. I will also need to talk to a few people to create a stronger foundation for the project - so it doesn't rely as much on myself as a maintainer.

Hey @clampr
Thank you for the information!
This sounds interesting but is also a little bit frustrating to wait for this feature until the new architecture is finished. Would this be that much additional effort, especially when the data is already queried?
Otherwise, I am happy to support this package. So let me know when you make the proposal.

I already thought about this.
The problem is that the current architecture isn't very flexible when it comes to adding new variables, changing the structure or data format. Meteostat Python relies entirely on the data provided through the bulk data interface. This uses CSV files with a static structure. Adding the solar radiation parameter would require a new version of these bulk data files. And every new version of the bulk data requires a temporal parallel export to ensure older versions don't stop working immediately.
I would vote for investing all capacity in the new architecture. This will not only add solar radiation, but also other parameters like cloud cover, visibility, etc.

But isn't the bulk data interface working with NaN/sparse values anyway? So, would the addition of new columns destroy old interfaces? I understand it though for the modification of existing parameter names...
I hope you don't misunderstand my persistence. I just want to use this awesome package. :)

I would perhaps add a comment that adding these parameters would be very attractive, but additional meta data would make them more valuable.  I know solar radiation data, and it is certainly not all created equal.  Of course the sky is the limit with meta data, but to take a German metaphor that seems somewhat similar but is not: "there is some air overhead" w.r.t. metadata in meteostat.
(To be taken as encouragement rather than criticism!)

Yes, simply appending additional columns could be feasible @l-kotzur. I will put this on the backlog and investigate if we can add it.
Also, @adriesse is right regarding the meta data. Meteostat is currently loosing some valuable meta data for the sake of simplicity. It's something we'll need to change. But this can only be done as part of the v2 rewirte.


Add Support for Loading Documents from Huawei OBS

Description:
This PR adds support for loading documents from Huawei OBS (Object Storage Service) in Langchain. OBS is a cloud-based object storage service provided by Huawei Cloud. With this enhancement, Langchain users can now easily access and load documents stored in Huawei OBS directly into the system.
Key Changes:

Added a new document loader module specifically for Huawei OBS integration.
Implemented the necessary logic to authenticate and connect to Huawei OBS using access credentials.
Enabled the loading of individual documents from a specified bucket and object key in Huawei OBS.
Provided the option to specify custom authentication information or obtain security tokens from Huawei Cloud ECS for easy access.

How to Test:

Ensure the required package "esdk-obs-python" is installed.
Configure the endpoint, access key, secret key, and bucket details for Huawei OBS in the Langchain settings.
Load documents from Huawei OBS using the updated document loader module.
Verify that documents are successfully retrieved and loaded into Langchain for further processing.

Please review this PR and let us know if any further improvements are needed. Your feedback is highly appreciated!
@rlancemartin, @eyurtsev

thanks @mpb159753!


[FLINK-15561][Security][hotfix] Add Delegation Token checker in YarnClusterDescriptor

What is the purpose of the change

YarnClusterDescriptor doesn't have the delegation token checker in security HadoopModule. Thus causes delegation token launch path problematically fails.

Brief change log
add identical delegation token checker in YarnClusterDescriptor.
Verifying this change
This change is already covered by existing tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: YARN
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no

This should fix the original issue outlined in https://lists.apache.org/thread.html/49c0d8c011daa227287473f6600f6f86dbb11a0afe8a1bdce107a0ce%40<user.flink.apache.org>, right?

I think the fix is good, we just have to agree on where the code should be. 😅We could think about adding a check for this to the end to end test, but that would be a bigger endeavour, I think.

This should fix the original issue outlined in https://lists.apache.org/thread.html/49c0d8c011daa227287473f6600f6f86dbb11a0afe8a1bdce107a0ce%40<user.flink.apache.org>, right?

I couldn't reproduce this exception in our security environment actually, but I suspect this could be the issue. I would reply to the ML thread and ask owner for a verification.

Thanks! I merged this. It's a good refactor, even though it doesn't yet solve the original user problem.


Move "conway governance hash" commands to "conway hash"

Changelog
- description: |
    Move "conway governance hash" commands to "hash". Users should adapt there calls as follows:

    `cardano-cli conway governance hash anchor-data ...` becomes `cardano-cli hash anchor-data ...`
    `cardano-cli conway governance hash script ...` becomes `cardano-cli hash script ...`
# uncomment types applicable to the change:
  type:
  # - feature        # introduces a new feature
  - breaking       # the API has changed in a breaking way
  # - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  # - refactoring    # QoL changes
  # - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
  # - maintenance    # not directly related to the code
  # - release        # related to a new release preparation
  # - documentation  # change in code docs, haddocks...

Context
Fixes https://github.com/IntersectMBO/cardano-cli/issues/782

So what we really want is a top level command that can hash all the hashable things. Or at least not to give the impression that hashing depends on the era.

cc @CarlosLopezDeLara since the current design is your ask from https://github.com/IntersectMBO/cardano-cli/issues/782
I can make hash a top-level command if you approve that like @Jimbo4350 does

@smelc  I like the idea! sounds great.

@Jimbo4350> Made the command top-level and removed the era.
I will consider in a follow-up PR if other hashing commands can be moved there too (hashing keys).

LGTM! However I would be wary of breaking the existing hashing functionality. Talk to @CarlosLopezDeLara about this as it may be an annoying for users who have existing scripts etc.

I think we can afford the breaking change here since 9.0 is still in the makings and 8.12 will not cross the hardfork. I'll update docs after this is on a cardano-cli release.

there are some leftovers in the help texts like:
...
  --anchor-data-hash HASH  Proposal anchor data hash (obtain it with
                           "cardano-cli conway governance hash anchor-data ...")
  --constitution-url TEXT  Constitution URL.
  --constitution-hash HASH Hash of the constitution data (obtain it with
                           "cardano-cli conway governance hash anchor-data
                           ...").
...

pointing to the hash function to conway governance hash

@gitmachtl> yes, it's being fixed by https://github.com/IntersectMBO/cardano-cli/pull/821. I think that's because I I lost some of my changes while polishing the PR :frowning_face:


bootstrap 5.2.3 and bootstrap-select beta3 programmatically issue

In bootstrap 5 when you load programmatically an item (or a list of items) with
$("#select1").selectpicker('refresh');
$("#select1").selectpicker('val', item);
and you try again to reload it more times, the select shows the same object/item a lot of times, while the select should show item just one time because it's the same object.
In the last bootstrap-select with bootstrap 4 works very well as I described, maybe it's a bug.
I would like to say that another issue is when you use programmatically this code
$("#select1").selectpicker('render');
in that case when you try to load an item, the select does nothing...
Thank you very much for the library: one of the best...

same issue.

Hello everybody,
I have updated the library bootstrap-select(v1.14.0-beta3).js and a lot of problems have been fixed: at least in my case it works very well now.
Of course I didn't adapt all library in its functions, but just some that for me didn't work: you can compare it with the original to detect the changes. In any case, finally, I can use it with bootstrap 5 without problems.
Two raccomandations: when you use the instraction

$('.selectpicker').selectpicker('val', item);
the function, at the end, calls refresh and not render
don't use render, to redrow the list of items, but refresh if you want to update the list...
$('.selectpicker').selectpicker('refresh');

NOTE: I have used the separator ' | ' but you can change with a comma
this is the link, I hope it will be useful for you
https://snippet.host/pafgna

@mattymatty76
I haven't tested your modified version heavily yet but so far, it seems to solve serious issues in beta2 and beta3
I'm using it with boostrap 4.6
Thanks for your proposal.

@ZalemCitizen
It's a pleasure to know that it is useful for you
thank you

@mattymatty76 did you have to do anything for the CSS? The provided CSS from this library doesn't work at all for me:

@mhenrixon
have you tried to use the right css file? You could try with bootstrap css 5.2 or 5.3 and assure yourself that there aren't any other files in conflict with bootstap.css.
In my case work at all

Have you tried to use the right css file?

This was me having to restart esbuild on every change. Will switch to Vite instead. Esbuild seem backward to me.

same issue


read access not given for v.0.6.1

Currently not all files within this path have read access, and therefore the pipeline cannot run:
/data/CCBR_Pipeliner/Pipelines/ASAP/v0.6.1

@kopardev - please update permissions. I've created a tmp dir in the meantime which has read access (and write access) that can be deleted once this is changed.
Thanks!

pipelines have moved -  no longer an issue


Small floating point numbers evaluate to zero after loading libnd4jcpu.dll

ND4J 1.0.0-beta2 or beta3
Apache commons-math3 3.6.1
Only affects Windows
We've been sporadically encountering exceptions in the Apache math libraries (specifically the BrentOptimizer) when using ND4J. We've narrowed it down to libnd4jcpu.dll and we suspect it is because it's setting the DAZ flag.
Here is a minimal repro case using version 1.0.0-beta2:
public class ND4JMemoryCorruption {
    public static void main(String[] args) {
        String filename = "nd4j-native-1.0.0-beta2-windows-x86_64.jar\\org\\nd4j\\nativeblas\\windows-x86_64\\libnd4jcpu.dll";
        System.load(filename);
        double smallValue = 1e-312;
        if (smallValue == 0) {
            throw new RuntimeException("Small numbers evaluate to zero!");
        }
    }
}

Thanks for highlighting this problem
With best regards,
Vyacheslav K.

9 нояб. 2018 г., в 13:59, Michael Lewin<EMAIL_ADDRESS>написал(а):
ND4J 1.0.0-beta2 or beta3
Apache commons-math3 3.6.1
Only affects Windows
We've been sporadically encountering exceptions in the Apache math libraries (specifically the BrentOptimizer) when using ND4J. We've narrowed it down to libnd4jcpu.dll and we suspect it is because it's setting the DAZ flag.
Here is a minimal repro case using version 1.0.0-beta2:
public class ND4JMemoryCorruption {
public static void main(String[] args) {
String filename = "nd4j-native-1.0.0-beta2-windows-x86_64.jar\org\nd4j\nativeblas\windows-x86_64\libnd4jcpu.dll";
System.load(filename);
double smallValue = 1e-312;
if (smallValue == 0) {
throw new RuntimeException("Small numbers evaluate to zero!");
}
}
}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Should be fixed now.


Please enable the arm64e ABI at boot on macOS arm64 runners

Description
On Apple Silicon runners the default OS configuration prevents preloading shared libraries to binaries build with the arm64e ABI even when SIP is disabled.
This prevents testing software on GitHub's runners relying on being able to preload shared libraries. In our case it prevents running the tests of Firebuild on the macos-14 runners, while the tests are passing on the macos-12 runners for quite some time.
Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[X] macOS 13 Arm64
[ ] macOS 14
[X] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Image: macos-14-arm64
Version: 20240116.1
https://github.com/firebuild/firebuild/actions/runs/8178792788/job/22363502389
(The error message from firebuild will be near the end of the test logs.)
Is it regression?
no
Expected behavior
The system allows preloading shared libraries to arm64e binaries and Firebuild's test are passing:
https://github.com/firebuild/firebuild/actions/runs/8178792788/job/22363500679 :
...
1: ok 14 closedir() inside an rm -r
1: ok 15 file operations
1: ok 16 randomness handling
1: ok 17 waiting for a child
1: ok 18 pthreads interception
1: ok 19 err()
...

Actual behavior
https://github.com/firebuild/firebuild/actions/runs/8178792788/job/22363502389
...
 1: not ok 16 randomness handling
1: # (from function `assert_streq' in file test_helper.bash, line 18,
1: #  in test file integration.bats, line 195)
1: #   `assert_streq "$result" ""' failed
1: # assert_streq: [ "FIREBUILD: The system is not configured to use the arm64e_preview_abi, which is needed for intercepting arm64e binaries.
1: # FIREBUILD: Visit https://firebuild.com/setup-macos for guidelines for setting up your system." = "" ]
1: not ok 17 waiting for a child
...

Repro steps
Fork https://github.com/rbalint/firebuild
Run the GitHub CI Action my creating a PR to merge the https://github.com/rbalint/firebuild/tree/ci-macos-matrix branch to master.
The macos-14 job will show the problem.

Hey @rbalint!
It's not a bug because it's default behaviour for arm64 based macOS. But we'll investigate possibility to enable required option. I'll be there with an answer later.

Hi @erik-bershel!
Thank you for looking into the problem.
When arm64e support is enabled only for inside the runner VM-s this option should not cause any platform issue. Also since the arm64 runners are new the change is unlikely to cause any regression. OTOH programs relying on preloading libraries to system binaries experience a regression compared to x86-based macOS runners, unless the arm64e support is enabled on arm64 runners.
I believe there is not much pressure on Apple to enable this feature by default because developers can turn this on on their development machines and build servers. It is just GitHub who can't serve those developers with GitHub-hosted runners.

I've merged  https://github.com/firebuild/firebuild/pull/1258 with with the test results ignored on arm64 runners, thus the issue is reproducible on https://github.com/firebuild/firebuild/tree/master . The failure is still visible in the logs.

If and when the feature is taken out of preview will we be able to return to this issue. Until then, you can use runners with macOS-13, which are not affected by the problem described. This does not fall into the category of regression and is basically a feature request. We do not use pre-release versions of anything as they could potentially have critical bugs or vulnerabilities.


Remove activation pages

We can as well get rid of all the account management of the login page and just redirect to CalypSSO's related page


Screen escape ^Gg produces strange chars :0000/0000/0000

Steps to reproduce

Configure escape char to be CTRL+G (instead of default Ctrl+A): echo "escape ^gg" > .screenrc
Start screen session: screen
Start vim without any configuration in .vimrc: vim

Strange chars :0000/0000/0000 occurs as shown

Expected behaviour
It should start vim normally, without :0000/0000/0000.
When I run vim -u NONE the issue does not happen.
Also, it does not happen when I use some other screen escape char eg escape ^ff.
It would be nice if there is something I can put in .vimrc to prevent this issue with escape ^gg.
Version of Vim
8.1, 8.2, 9.0
Environment
Ubuntu under screen session.
echo $TERM
screen.xterm-256color

Logs and stack traces
No response

What terminal is screen running inside?

What terminal emulator is screen running in?

It is term-256color

I think you are using GNOME terminal, and I can reproduce this issue using it. It seems that putting
set t_RB=

in your vimrc will solve this problem.

Issue with your terminal, claiming to be xterm compatible, when it really isn't.


Contribution Guidelines / Style Guide

I like the new implementation of the README in each repo(#8) , along with the templates directory that houses how each should be formatted, but I think we need to create contributions guidelines page. As far as what is expected when a PR is opened. Things like being sure the Algo Directory is TitleCase, It includes the directory path of the language name, as well as some other nuances we could add.
Let me know about your thoughts on this one @JGFM4

To add on this, would you say that we should delete the documentation that is already in some of the files, and just leave the pure code since the readme will have that data?

I think a contribution page would be appropriate for sure.
As for the second part, I think solutions should be only code (comments being to explain a part of the code) and the problem definition/documentation should be held in the algorithms' README. It's irrelevant that a friend or you were asked X in an interview. Comments relevant to the solution should be added in the notes section of the README for that Algorithm

@AustinTice I was thinking of starting the Wiki for the guidelines within the upcoming weeks to solve this issue.

That would be awesome. Don't feel like you have to do it all alone, feel free to reach out for any troubles or questions. I think we should tag team this to ensure it's written correctly the first time around. Great initiative!

Done by @JGFM4 good work.


Issue during compilation

It  appears compiling the GPS example (converting it to main.cpp) as is creates an issue as defined below when building in platform.io once it starts to link firmware.elf.  It references an issue with postion.h, specifically with the JSON conversion, citing multiple definitions.  Error below.  Unsure where to troubleshoot.
c:/users/mikeh/.platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld.exe: .pio\build\esp32dev\libb07\libNMEA0183.a(nmea0183.cpp.o): in function sensesp::canConvertFromJson(ArduinoJson6194_F1::VariantConstRef, sensesp::Position const&)': C:\Users\mikeh\OneDrive\Documents\SensESP-project-template-main\SensESP-project-template-main/.pio/libdeps/esp32dev/SensESP/src/sensesp/types/position.h:69: multiple definition of sensesp::canConvertFromJson(ArduinoJson6194_F1::VariantConstRef, sensesp::Position const&)'; .pio\build\esp32dev\src\main.cpp.o:C:\Users\mikeh\OneDrive\Documents\SensESP-project-template-main\SensESP-project-template-main/.pio/libdeps/esp32dev/SensESP/src/sensesp/types/position.h:69: first defined here
c:/users/mikeh/.platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld.exe: .pio\build\esp32dev\libb07\libNMEA0183.a(nmea0183.cpp.o): in function sensesp::convertFromJson(ArduinoJson6194_F1::VariantConstRef, sensesp::Position&)': C:\Users\mikeh\OneDrive\Documents\SensESP-project-template-main\SensESP-project-template-main/.pio/libdeps/esp32dev/SensESP/src/sensesp/types/position.h:49: multiple definition of sensesp::convertFromJson(ArduinoJson6194_F1::VariantConstRef, sensesp::Position&)'; .pio\build\esp32dev\src\main.cpp.o:C:\Users\mikeh\OneDrive\Documents\SensESP-project-template-main\SensESP-project-template-main/.pio/libdeps/esp32dev/SensESP/src/sensesp/types/position.h:49: first defined here
c:/users/mikeh/.platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld.exe: .pio\build\esp32dev\libb07\libNMEA0183.a(nmea_parser.cpp.o): in function sensesp::canConvertFromJson(ArduinoJson6194_F1::VariantConstRef, sensesp::Position const&)': C:\Users\mikeh\OneDrive\Documents\SensESP-project-template-main\SensESP-project-template-main/.pio/libdeps/esp32dev/SensESP/src/sensesp/types/position.h:69: multiple definition of sensesp::canConvertFromJson(ArduinoJson6194_F1::VariantConstRef, sensesp::Position const&)'; .pio\build\esp32dev\src\main.cpp.o:C:\Users\mikeh\OneDrive\Documents\SensESP-project-template-main\SensESP-project-template-main/.pio/libdeps/esp32dev/SensESP/src/sensesp/types/position.h:69: first defined here
c:/users/mikeh/.platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld.exe: .pio\build\esp32dev\libb07\libNMEA0183.a(nmea_parser.cpp.o): in function sensesp::convertFromJson(ArduinoJson6194_F1::VariantConstRef, sensesp::Position&)': C:\Users\mikeh\OneDrive\Documents\SensESP-project-template-main\SensESP-project-template-main/.pio/libdeps/esp32dev/SensESP/src/sensesp/types/position.h:49: multiple definition of sensesp::convertFromJson(ArduinoJson6194_F1::VariantConstRef, sensesp::Position&)'; .pio\build\esp32dev\src\main.cpp.o:C:\Users\mikeh\OneDrive\Documents\SensESP-project-template-main\SensESP-project-template-main/.pio/libdeps/esp32dev/SensESP/src/sensesp/types/position.h:49: first defined here
c:/users/mikeh/.platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld.exe: .pio\build\esp32dev\libb07\libNMEA0183.a(wiring.cpp.o): in function sensesp::canConvertFromJson(ArduinoJson6194_F1::VariantConstRef, sensesp::Position const&)': C:\Users\mikeh\OneDrive\Documents\SensESP-project-template-main\SensESP-project-template-main/.pio/libdeps/esp32dev/SensESP/src/sensesp/types/position.h:69: multiple definition of sensesp::canConvertFromJson(ArduinoJson6194_F1::VariantConstRef, sensesp::Position const&)'; .pio\build\esp32dev\src\main.cpp.o:C:\Users\mikeh\OneDrive\Documents\SensESP-project-template-main\SensESP-project-template-main/.pio/libdeps/esp32dev/SensESP/src/sensesp/types/position.h:69: first defined here
c:/users/mikeh/.platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld.exe: .pio\build\esp32dev\libb07\libNMEA0183.a(wiring.cpp.o): in function sensesp::convertFromJson(ArduinoJson6194_F1::VariantConstRef, sensesp::Position&)': C:\Users\mikeh\OneDrive\Documents\SensESP-project-template-main\SensESP-project-template-main/.pio/libdeps/esp32dev/SensESP/src/sensesp/types/position.h:49: multiple definition of sensesp::convertFromJson(ArduinoJson6194_F1::VariantConstRef, sensesp::Position&)'; .pio\build\esp32dev\src\main.cpp.o:C:\Users\mikeh\OneDrive\Documents\SensESP-project-template-main\SensESP-project-template-main/.pio/libdeps/esp32dev/SensESP/src/sensesp/types/position.h:49: first defined here
c:/users/mikeh/.platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld.exe: .pio\build\esp32dev\libb72\libSensESP.a(signalk_position.cpp.o): in function sensesp::canConvertFromJson(ArduinoJson6194_F1::VariantConstRef, sensesp::Position const&)': C:\Users\mikeh\OneDrive\Documents\SensESP-project-template-main\SensESP-project-template-main/.pio/libdeps/esp32dev/SensESP/src/sensesp/types/position.h:69: multiple definition of sensesp::canConvertFromJson(ArduinoJson6194_F1::VariantConstRef, sensesp::Position const&)'; .pio\build\esp32dev\src\main.cpp.o:C:\Users\mikeh\OneDrive\Documents\SensESP-project-template-main\SensESP-project-template-main/.pio/libdeps/esp32dev/SensESP/src/sensesp/types/position.h:69: first defined here
c:/users/mikeh/.platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld.exe: .pio\build\esp32dev\libb72\libSensESP.a(signalk_position.cpp.o): in function sensesp::convertFromJson(ArduinoJson6194_F1::VariantConstRef, sensesp::Position&)': C:\Users\mikeh\OneDrive\Documents\SensESP-project-template-main\SensESP-project-template-main/.pio/libdeps/esp32dev/SensESP/src/sensesp/types/position.h:49: multiple definition of sensesp::convertFromJson(ArduinoJson6194_F1::VariantConstRef, sensesp::Position&)'; .pio\build\esp32dev\src\main.cpp.o:C:\Users\mikeh\OneDrive\Documents\SensESP-project-template-main\SensESP-project-template-main/.pio/libdeps/esp32dev/SensESP/src/sensesp/types/position.h:49: first defined here
collect2.exe: error: ld returned 1 exit status
*** [.pio\build\esp32dev\firmware.elf] Error 1

Having the same problem here. Have you found a solution?

Same issue here.  I hope there is a solution.

I have the same problem and have made a change to position.h in  Signalk/sensesp to inline the definitions of ConvertFromJson  and CanConvertFromJson. The changes are as follows:
`49 - void convertFromJson(JsonVariantConst src, Position &dst) {
49 + inline void convertFromJson(JsonVariantConst src, Position &dst) {
69 - bool canConvertFromJson(JsonVariantConst src, const Position &) {
69 + inline bool canConvertFromJson(JsonVariantConst src, const Position &) {`
Care also needs to be taken to ensure that ArduinoJSON is version 6.x.x and not 7.0.0
I am still working on this to see if I can propose a PR that addresses this.
There is a conversation on Slack in the SignalK #sensors channel

Ok, I refreshed my fork of SensESP and made changes using in-lining. This allows compiling and linking. I then set up a cpp and moved the function definitions there. Now that I would like to test it, I cannot find these functions used anywhere in sensESP.
I see that this functionality was added in https://github.com/SignalK/SensESP/pull/614.
Not knowing if anybody is dependent on this code, it would be a bit harsh to just remove the functions, even though that seems like the best solution to me.

I believe the root cause is actually the just-released ArduinoJson 7 that has some breaking changes (as major versions tend to do). Since ArduinoJson version was not pegged in SensESP, this broke not just NMEA 0183 but also SensESP builds.
The original reported issue here might be something different. Let's see if it still exists once I've released a fixed SensESP version.

I believe the issue has now been fixed; the root cause was that convertFromJson can canConvertFromJson functions were defined in the header file. This breaks the compilation if the header is included in more than a single place. Apologies for not noticing this issue earlier!
You might need to delete the .pio folder in your project to force PlatformIO to update all libraries. After that, the project should build fine.
I'll close this issue once someone verifies that the problem has been fixed.

Issue fixed here.  Everything compiles well.  Now to add some parsers to my GNSS project.  Thanks to mairas for the fix.

Great, thanks a bunch for verifying!


Readonly

added KeyBinding and addKeyboardHandler
added module for markers.
fixed example

@garyb please, review

:+1:


Update entitlement-management-access-package-approval-policy.md

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

Thanks, @owinfreyatl. When you're ready to merge this PR, add a #sign-off comment.

#sign-off


Remove query-schema-model cachebust

Fixes #9217
Since no longer necessary as of
https://github.com/CartoDB/CartoDB-SQL-API/pull/330
@xavijam ping
cc @rochoa

:+1:

Frontend tests passing, so merging


Remove Wasm code from rust API published on crates.io

We need to separate out the Wasm code (js_sys/wasm_bindgen stuff) from the rest of the rust types in the API we publish on crates.io. This will allow us to consume this crate in the CLI and provide an API for people to use with Rust.

So I guess I have a few questions here.

Is the wasm code needing to be removed from this crate entirely? or just separated and given feature flags?
how deep does wasm "infect" this codebase? Is it at the edges whilst code generating or is it deeply embedded into the bundling code already?
Assuming the APIs should appear for both wasm and rust, should it be the same APIs or should they vary slightly since the consumers will be fundamentally different environments?

It's a bit of a large refactor and a lot to explain. I will put up a PR in a few minutes


Clang 17 failed to compile TensorFlow master

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
tf 2.17
Custom code
No
OS platform and distribution
Ubuntu 22.04 x86
Mobile device
No response
Python version
3.10
Bazel version
6.50
GCC/compiler version
Clang 17.06
CUDA/cuDNN version
8.9
GPU model and memory
RTX 3060
Current behavior?
As following from https://www.tensorflow.org/install/source#gpu and https://www.tensorflow.org/install/source , the tensorflow build is failing due to clang 17 not compiling org_brotli.
Standalone code to reproduce the issue
clone from https://www.tensorflow.org/install/sourc
./configure with below configurations .
Try build command
bazel build //tensorflow/tools/pip_package:wheel --repo_env=WHEEL_NAME=tensorflow --config=cuda

avaish@avaish-dekstop:/media/avaish/labdisk/clang-tf/tensorflow$ ./configure
You have bazel 6.5.0 installed.
Please specify the location of python. [Default is /usr/bin/python3]:

Found possible Python library paths:
  /usr/lib/python3.10/dist-packages
  /usr/lib/python3/dist-packages
  /usr/local/lib/python3.10/dist-packages
Please input the desired Python library path to use.  Default is [/usr/lib/python3.10/dist-packages]

Do you wish to build TensorFlow with ROCm support? [y/N]: N
No ROCm support will be enabled for TensorFlow.

Do you wish to build TensorFlow with CUDA support? [y/N]: y
CUDA support will be enabled for TensorFlow.

Do you wish to build TensorFlow with TensorRT support? [y/N]: N
No TensorRT support will be enabled for TensorFlow.

Found CUDA 12.4 in:
    /usr/local/cuda-12.4/targets/x86_64-linux/lib
    /usr/local/cuda-12.4/targets/x86_64-linux/include
Found cuDNN 8 in:
    /usr/lib/x86_64-linux-gnu
    /usr/include

Please specify a list of comma-separated CUDA compute capabilities you want to build with.
You can find the compute capability of your device at: https://developer.nvidia.com/cuda-gpus. Each capability can be specified as "x.y" or "compute_xy" to include both virtual and binary GPU code, or as "sm_xy" to only include the binary code.
Please note that each additional compute capability significantly increases your build time and binary size, and that TensorFlow only supports compute capabilities >= 3.5 [Default is: 3.5,7.0]: 8.6

Do you want to use clang as CUDA compiler? [Y/n]: Y
Clang will be used as CUDA compiler.

Please specify clang path that to be used as host compiler. [Default is /usr/lib/llvm-17/bin/clang]:

You have Clang 17.0.6 installed.

Please specify optimization flags to use during compilation when bazel option "--config=opt" is specified [Default is -Wno-sign-compare]:

Would you like to interactively configure ./WORKSPACE for Android builds? [y/N]: N
Not configuring the WORKSPACE for Android builds.

Do you wish to build TensorFlow with ROCm support? [y/N]: N
No ROCm support will be enabled for TensorFlow.

Do you wish to build TensorFlow with CUDA support? [y/N]: y
CUDA support will be enabled for TensorFlow.

Do you wish to build TensorFlow with TensorRT support? [y/N]: N
No TensorRT support will be enabled for TensorFlow.

Found CUDA 12.4 in:
    /usr/local/cuda-12.4/targets/x86_64-linux/lib
    /usr/local/cuda-12.4/targets/x86_64-linux/include
Found cuDNN 8 in:
    /usr/lib/x86_64-linux-gnu
    /usr/include

Relevant log output
ERROR: /home/avaish/.cache/bazel/_bazel_avaish/2b06f750a2a65e1321540478ec17bba7/external/org_brotli/BUILD:121:11: Compiling c/enc/utf8_util.c failed: (Exit 1): clang failed: error executing command (from target @org_brotli//:brotlienc) /usr/lib/llvm-17/bin/clang -MD -MF bazel-out/k8-opt/bin/external/org_brotli/_objs/brotlienc/utf8_util.pic.d '-frandom-seed=bazel-out/k8-opt/bin/external/org_brotli/_objs/brotlienc/utf8_util.pic.o' ... (remaining 52 arguments skipped)
clang: error: argument unused during compilation: '--cuda-path=/usr/local/cuda-12.4' [-Werror,-Wunused-command-line-argument]
Target //tensorflow/tools/pip_package:wheel failed to build
Use --verbose_failures to see the command lines of failed build steps.
ERROR: /media/avaish/labdisk/clang-tf/tensorflow/tensorflow/tools/pip_package/BUILD:266:9 Action tensorflow/tools/pip_package/wheel_house failed: (Exit 1): clang failed: error executing command (from target @org_brotli//:brotlienc) /usr/lib/llvm-17/bin/clang -MD -MF bazel-out/k8-opt/bin/external/org_brotli/_objs/brotlienc/utf8_util.pic.d '-frandom-seed=bazel-out/k8-opt/bin/external/org_brotli/_objs/brotlienc/utf8_util.pic.o' ... (remaining 52 arguments skipped)
INFO: Elapsed time: 21.943s, Critical Path: 7.65s
INFO: 349 processes: 15 internal, 334 local.
FAILED: Build did NOT complete successfully

tf_fail_log.txt
Attaching the log file in verbose mode.

Resolved by adding build:linux --copt="-Wno-unused-command-line-argument" in .bazelrc file.

@intelav,
Glad the issue was resolved. Could you please feel free to move this issue to closed status. Thank you!

Thanks


only add mode: count if it doesn't already exist

Fixes test-coverage-html target, we were sometimes putting multiple mode: count headers which caused it to error out

Pull Request Test Coverage Report for Build 429

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 62.582%

Totals

Change from base Build 426:
0.0%

Covered Lines:
3136

Relevant Lines:
5011

💛  - Coveralls


Which one in future? react or blaze or both of them?

Hi @perak I see in kitchen site that you working on react version of meteor-kitchen.
In future kitchen version project only can use react or it's optional??
For example we can choose from blaze or react output as new setting or blaze version discontinued??

You'll have option to choose between "blaze" or "react".

So, answer is: both of them.

Thanks @perak. So kitchen will be backward compatible? yes?

Of course. Default (without command line switch --react) is blaze, nothing will change for you.

Input file structure remains as is (with few newly added properties useful in React apps).

Thanks @perak.
When you want to release this new version??

@cyclops24 I'll try to publish experimental version (0.9.48) ~24 hours after now, but that's not a promise. If not - then 10 days after now (I'm going to vacation). :)

Thanks @perak , have a good vacation man :+1:


Can't get onInputBoxInput function to be called

Hi!
I'm working on https://github.com/diaspora/diaspora/issues/1851 and I'm currently trying to get mentions-input show a mention box within a comment box. While it works with the publisher textarea on the top of the diarpora page, it doesn't work with the comment box. The textarea tag gets replaced with a mentions-input-box, but onInputBoxInput doesn't get called when I type some text in the comment box. And initTextarea is called for every comment box on the page.
Here is how I changed diaspora for that: https://github.com/cmrd-senya/diaspora/commit/b68aac9a020b51a8b4f74ed70a7702e486cdd9ee
Couldn't you please help me to find, what am I lacking to make it work? Why onInputBoxInput doesn't get called, event though elmInputBox.bind('input', onInputBoxInput) is called for the element?

For some strange reason it works for me now, though I changed nothing. Sorry for posting this.


[Enemy In Shadows] Scene maps, journals, item folder empty

Hello, after activiating the modules i do not have any scenes, journal entries or items inside the related folders. The folders are empty.
I am using Foundry within "The Forge". Every module is up to date.From: Kaiwfrp4e: 3.5.1wfrp4e-dotr: 1.0.0wfrp4e-eis: 1.2.2wfrp4e-starter-set: 1.4.3wfrp4e-ua1: 1.0.2

I can't help you if I don't know how to contact you. If you see this, please add your discord tag (preferably) or your email.


ENH: pytorch 2.0

pytorch 2.0 introduce torch.compile which could improve inference speeds. 2.0 release is expected in march 2023. torch.compile is available in current nightly builds of pytorch.

here are some preliminary results with torch 2.0.0.dev20230116+cpu. right now one cannot serialize the compiled model, which would be nice for our case. the first run of the model will be slower, but subsequent runs are fast. the code below runs the compiled models once before using timeit to reflect the speedups and not the startup time.
import torch
import wsinfer

w = wsinfer.get_model_weights("inception_v4nobn", name="TCGA-TILs-v1")
model = w.load_model()
model.eval();
x = torch.ones(48, 3, 200, 200, dtype=torch.float32)

with torch.no_grad():
    out = model(x)

%%timeit
with torch.no_grad():
    out = model(x)
# 4.13 s ± 216 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

model_comp = torch.compile(model)
with torch.no_grad():
    out = model_comp(x)

%%timeit
with torch.no_grad():
    out = model_comp(x)
# 3.28 s ± 129 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

model_comp_max = torch.compile(model, fullgraph=True, mode="max-autotune")
with torch.no_grad():
    out = model_comp_max(x)

%%timeit
with torch.no_grad():
    out = model_comp_max(x)
# 3.52 s ± 154 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)


Make use of nvm (Node.js version manager)?

Hi,
I've just seen, that the Node.js integration library requires Node.js version v16.18, but leaves it quite open on how to obtain this quite outdated Node.js version.
From my point of view, it could make sense, to add nvm (Node.js version manager) to this repository (it is a file called .nvmrc with a single line of code in it (v16.18).
The installation and usage is quite straight forward:

Install nvm at first: https://github.com/nvm-sh/nvm
Checkout this repository
Execute nvm install or nvm use (the latter, if you already used the repo in the past)

This ensures, that every developer uses the same Node.js version, which should help prevent some bugs from using different Node.js versions. Updating to another Node.js also gets straight forward: Change the content of the .nvmrc-file to the new Node.js version, can nvm install and you are all done.
Furthermore it allows you to use the same Node.js version also in the Github-Actions (e.g. https://github.com/unfoldedcircle/integration-node-library/blob/main/.github/workflows/unit-tests.yml):
name: Run unit tests

on:
  push:
    paths:
      - '**/*.js'
      - '.github/**/*.yml'
      - 'package-lock.json'
  pull_request:
    branches: [ "main" ]
    types: [opened, synchronize, reopened]

jobs:
  test:
    name: Run tests
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v4

      - name: Setup node
        uses: actions/setup-node@v4
        with:
          node-version-file: '.nvmrc'

      - name: Install dependencies
        run: npm ci

      - name: Run configured tests
        run: npm run test

WDYT?
Should I submit a pull request for that?

Seems like a good idea! Especially since it's purely optional and non-invasive 👍
JS is still a strange new world to me, new things every day 😅
Please go ahead submitting a PR.
BTW: Node.js v16 is the current runtime environment on Remote 2. The next beta update should include v20.16 if we don't find any issues.

Hehehe - yeah, the Node.js universe is quite...lively (and quirky)...but one gets used to it over time. 😃
I've just submitted the PR - let me know what you think of it (especially after my discovery of trying to install the NPM dependencies cleanly with npm ci with Node.js version v16.18).


Energenie ENER314-RT

Hi, I have tried this with my Energenie ENER314-RT but not got it working. Must be a config/setup. It works with gpbenton's mqttclient ...
https://github.com/gpbenton/engMQTTClient/pull/19#issuecomment-685341216
... that you dropped in favour of this much cleaner setup. Any ideas how I get this working ?
I installed rpi-rf using pip3 and then what? I do not know what the home code is or channel.
I do not have a remote but rather used that engMQTTclient software where I just held the button (on the plug socket) in for 5 seconds, it flashed, I sent a "On" to 8008 (hex code for the socket as reported by engMQTTclient) and it paired then worked.
Your way is much better, Are you able to help please?

Daz

Hi, I'm not sure whether you are trying to do what I did, but I'll try to help anyway!
I assume you are referring to https://github.com/davet2001/miscellaneous/blob/master/energenie_rpi-rf_433.sh?
I have an ENER314-RT but I don't use it any more.  Instead I use the most basic 433 MHz transmitter (3 pin device), like those available from aliexpress.
I don't know if there's a way to use the ENER314-RT in place of the simple 3pin 433MHz transmitter with my script.
rpi-rf (https://github.com/milaq/rpi-rf)
provides the rpi-rf_send command, but it needs you to tell it which RPi pin your transmitter is on.
If you want to use the hand remote, you need to learn the house code.  It can be done two ways:

with a USB DVB type SDR device to listen to and decode the house remote using universal radio hacker, then working out the symbol timing and pattern manually.
via a brute force method such as this script https://github.com/whaleygeek/pyenergenie/issues/81#issuecomment-313512879

Both ways need patience though!
If you aren't bothered about using the hand remote at all, you don't need to learn it's code.  You could just pick any house code such as the one on my example, and teach your socket to respond to it (after that your remote won't do anything).

Yes, that's the script.
But how do i find which GPIO the 314RT hat is on. i tried all with the rpi-rf command but couldn't get the sockets to do anything. Don't even know if it's working.
works fine with that engMQTTclient but that's a huge overkill, same reason like you i want to ditch it

I don't think my script will do what you are looking for with your current hardware.
According to the image above the ener314-rt board has a serial interface so sadly you can't just toggle a line to turn the RF tx line on/off.
rpi-rf_send is for toggling one RPi gpio pin connected directly to a transmitter.
The engMQTTcient subscribes to mqtt topics that can be used to turn sockets on or off, and presumably sends and receives TRV data.
Since the TRVs need two way comms, I think you may need to stick with the ener314-rt.
I haven't used the ener314-rt directly with homeassistant and I don't know of any integrations, only via mqtt.
Usb DVB tv receiver is v helpful for debugging
Hopefully this helps!

Many thanks for replying Dave and for sharing your expertise which is waaaay higher than my level.
Yes, this board is not the same as the "cheap 433RF" boards - although I wish it was. OOK and PSK doesnt help. I will just stick with the engMQTTclient then which does the job albeit a bit of an overkill - at least it works.
Thanks for the help

daz


replace at_demo_data keys with json format in atKeys file

Is your feature request related to a problem? Please describe.
Currently keys in at_demo_data are unencrypted which is different from the format in .atKeys file(encrypted using self encryption key)
Describe the solution you'd like

create json data for demo data keys similar to .atKeys format
create.atKeys file for demo data users so apps testing using demo atsigns can use the .atKeys file

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@murali-shris is this still an active ticket?  If so can you please assign a priority or close?  TY!


fix: Spaces are not allowed on widgets children names (tabs, menus, buttons etc.)

Description

User cannot use space in tab widget naming. Space can only be included as an afterthought.
This issue is due to recent code changes to the relevant property controls

Fixes #9443
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Test A
Test B

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:green_circle: Total coverage has increased
// Code coverage diff between base branch:release and head branch: fix/9443-spaces-not-allowed-on-widget-children-names

Status
File
% Stmts
% Branch
% Funcs
% Lines

:green_circle:
total
55.47 (0.01)
37.07 (0.01)
35.32 (0)
55.85 (0.01)

:green_circle:
app/client/src/utils/autocomplete/TernServer.ts
52.94 (0.23)
41.67 (0.84)
36.21 (0)
56.99 (0.25)

@wmdev0808 This happens in the datasource pane as well. I was trying to use space in the Header fields for an API datasource and faced the same issue. Can you please confirm if this fix will solve the issue for the datasource pane components as well?

@wmdev0808 This happens in the datasource pane as well. I was trying to use space in the Header fields for an API datasource and faced the same issue. Can you please confirm if this fix will solve the issue for the datasource pane components as well?

Hi, I could not reproduce the issue, could you please provide me with a loom video to show the issue?

/ok-to-test sha=1336aec

@wmdev0808 Tested this PR and spaces are now allowed on the widgets (Tab, Table, Menu Button, Button and Button group widgets)
CC: @shwetha-ramesh


not working on ryujinx

none of the cheats take any effect, on version 1.1.761 of ryujinx and version 1.0 of game.

Downgrade your ryu version for now and file a bug with them. they have been randomly breaking cheats between updates then fixing them a version or two later.

what version is working?

i tried ryujinx-1.1.760,1.1.741,1.1.748 then gave up

I removed v1.0 cheats -- as I've migrated to 1.1.0 -- all the cheats that I made originally work(ed) for Ryu, as I tested it myself.
They all work currently for latest.. if it isn't you're doing something wrong. Post a screenshot.

ive placed the txt in Ryujinx/mods/contents/0100F2C0115B6000/ like the ryujinx wiki says to and they arent working

I removed v1.0 cheats -- as I've migrated to 1.1.0 -- all the cheats that I made originally work(ed) for Ryu, as I tested it myself.
They all work currently for latest.. if it isn't you're doing something wrong. Post a screenshot.

I did follow the steps and tried the cheats of version 1.0, but I followed the same steps but some tricks do not work for me, such as stamina, health, inf battery, arrow, etc. dont work for me
I have it just like I did the first time, now with version 1.1 I did the same, but some of them don't work as I said

Can confirm, it is working with latest Ryu as of right now..

Same. The only one thats worked for me is content of 082CE09B06E33A12 haha the one with like 7 cheats, these updated ones dont work

It LOOKS as if it wors, but it doesnt.. it lets me enable them, as well, but they DO NOT WORK in the game....

It lets me enable them.. It shows me that they've been correctly dumped into the game files, but they simple dont work, in game.. I have the latest Ryujinx update.. Ive also tried another persons cheats, for this game and got the same exact result.. you can see them there, but they dont work..

Works fine, you're using a different version.


Remove tests from cov option in py.test

Coverage remained the same at 0.0% when pulling 04c7e92816ea955420446ed9c40e50890dc82c4c on ci/remove_tests_from_cov into 3ef2bbccd24be9b51b850379ec3321665e75cd99 on master.


Feat/results page

This PR introduces the results page for builders program.
Screenshot

:tada: This PR is included in version 1.13.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


":echo 09" should raise error

:echo 0xg
↓
E15: Invalid expression: 0xg
I think It's OK.
:echo 09
↓
9
It's not good because an octal number starts with a zero and 09 should take care as invalid octal number.

This was a bad choice a long time ago.  Unfortunately, we can't change it now without breaking things.  Perhaps we could add an option to disable using a leading zero for octal, but since we can't enable that by default it won't have much effect.

:let x = 011
:echo x
        9
:let x = 08
:echo x
        8

IOW, as an expression in a let statement, a Number beginning with zero is also interpreted as octal if all its digits are in the range [0-7], as decimal otherwise. The present state of affairs doesn't produce an error in one case and not in the other. Maybe it should be better documented under :help expr-number but otherwise I also think the actual behaviour shouldn't change.

Perhaps we could add an option to disable using a leading zero for octal,

How about using :scriptversion?

so I think this can be closed since using scriptversion 4 has been introduced in 60a8de28d11595f4df0419ece8afa7d6accc9fbd


Create factory method on ApifyDatasetLoader

CC @jirimoravcik @jancurn this is roughly what I have in mind - does this make sense to you?

I also moved datasetMappingFunction into the config object. This way its purpose is clearer when creating a client, and would make refactoring easier in the future if maybe someday it could be set on Apify's end/defaulted to some reasonable value.

@jacoblee93 Wow, many thanks for your changes. I see you already merged them to the main repo? In that case, I assume we can just close this

Yes! Docs are already deployed here:
https://js.langchain.com/docs/modules/indexes/document_loaders/examples/web_loaders/apify_dataset
The actor call took a really long time (30 minutes) on the LangChain docs so I should probably go back and use a different example though.

Oh hey, also @jirimoravcik are you on Twitter? Doing a release announcement thread soon and would give you a shoutout.

Hey @jacoblee93, @jirimoravcik doesn't have a twitter. It would be awesome if you could tag https://twitter.com/apify


docs: add links for every example title in README  #4

What type of PR is this?
docs

What this PR does / why we need it (English/Chinese):
Linked every example in README to the respective folder.

Which issue(s) this PR fixes:
#4 Proposal: add link for each example in README

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

May README_CN be done together?


Updated release doc for MAC users

sed command in MAC is used as gsed. Updated release doc.
Checklist
If the pull request includes user-facing changes, extra documentation is required:

[ ] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[x] Add or update relevant sections of the docs website in website/content/en/docs

/lgtm


Can not read or post data to the database

I followed the tutorial but when I click the button to read data(eg. "Show Orders") or post data(eg. "Place Order" in order form) in the debugging session, an error happened:
Error Message: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 50 - Local Database Runtime error occurred. The specified LocalDB instance does not exist.)
Source File: E:\code\SharePoint_Provider-hosted_Add-ins_Tutorials-master\1_BeforeSharePointUI\ChainStoreWeb\Pages\OrderForm.aspx.cs    Line: 48
Source Error:
Line 48:                 conn.Open();
It's obviously that something went wrong with the database, but I'm a new back end developer and I don't know how to fix it. Can anyone help me? Any help would be appreciated.

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

ID: d14641c6-8ce6-8838-ab9a-8e6ea90aed50
Version Independent ID: 9b7fcbf8-4fc6-ade9-62ef-a1d4345827f8
Content: Give your provider-hosted add-in the SharePoint look-and-feel
Content Source: docs/sp-add-ins/give-your-provider-hosted-add-in-the-sharepoint-look-and-feel.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

Thanks for your comment.
Is "connection string" the Site URL? I have replaced it as my sit URL and the connection is ok. And the code is cloned from the repository from GitHub. Except for the changes in the tutorial, I didn't change anything. Maybe not this problem.
I found there are no IIS Express and SQL Express in my computer. Does it matter?

The issue is likely with your connection string you're using., or the ability to connect to the database. Need to make sure the database is running & accessible and that you're using the correct connection string.

Thanks for your comment.
Is "connection string" the Site URL? I have replaced it as my sit URL and the connection is ok. And the code is cloned from the repository from GitHub. Except for the changes in the tutorial, I didn't change anything. Maybe not this problem.
I found there are no IIS Express and SQL Express in my computer. Does it matter?

@andrewconnell Thanks for your comment.
Is "connection string" the Site URL? I have replaced it as my sit URL and the connection is ok. And the code is cloned from the repository from GitHub. Except for the changes in the tutorial, I didn't change anything. Maybe not this problem.
I found there are no IIS Express and SQL Express in my computer. Does it matter?

Not familiar with the code in this sample, but the error you mention talks about a DATABASE, not a site URL. The code appears to be throwing an error when you are opening a connection to the database. Thus, you're not looking for a site URL for the connection string, you're looking for a SQL DB CONNECTION STRING.
If you look at the README in the project you cloned, it talks about some pre-req's... such as:

The samples assume that Visual Studio is using Version 12 (SQL 2014) of SQL Express. If you have SQL Server 2016 installed on your development computer, you need to make a change to the web.config file in the solution. Find the line that sets the SqlAzureConnectionString near the top of the file. Change the phrase "ProjectsV12" in the value to "ProjectsV13". You will need to do this for each of the solutions in the repo.

If you're using a SQL Azure DB, you need to ensure the firewall on the SQL Azure DB has an entry for your web app to connect to the DB.

@andrewconnell Thanks, I'm using VS 2017 and forgot to install SSDT. After installing the SSDT and changing the connection string in the web.config to replace "ProjectsV12" with "ProjectsV13", it worked.
And I also found a same issue in this tutorial project and more information about it.


[BEAM-13647] Use role for Go worker binary.

Move away from older version of Go Worker Binary, in favour of a dedicated RoleUrn.

Adds "beam:artifact:role:go_worker_binary:v1" urn to proto.
On pipeline execution, updates the default Go env in the pipeline proto with the worker binary, as appropriate:

Continue to use file references for universal runners
Start using URL types pointing to GCS staging location for Dataflow.

Retain legacy logic in case of old SDKs using newer SDK container for some reason.
Newer SDKs can still use older SDK containers as there's no simple mechanism at present to add additional dependencies to the Go environment. Therefore there's often only 1 dependency and it will always be the worker. However, from 2.37.0 on, the role will be usable and expected.

Validated "old container" behavior manually against Spark and Dataflow, with the pipelines successfully executing with each.
Minor breaking change to the dataflow lib, unexporting the StageFile function, and also have it return the SHA256 hash for the binary. dataflowlib was never intended to be used outside of the dataflow runner code anyway.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Please fix codecov failure before merging it.

Note: All this code is covered by the integration tests, otherwise it wouldn't work. Adding test coverage to boot.go would require a complete refactor out of the single main method. I'll see what I can do about the other code though, in particular the binary substitution.

Added tests to the core changes in the graphx package. The other packages changes require various bits of file IO, without which, the SDK wouldn't function at all. They would need to be refactored a bit, or have specialized file-io based tests to validate them, which is a bit much for this change.

Run Java PreCommit


Dphan/add nats

Closes #
📑 Description

✅ Checks

[ ] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[ ] All the tests have passed

ℹ Additional Information

by default creates in wrong branch, should be cpp17


Script that makes worker compile a specific starter package

From @georgyo

There are a few scripts in the worker directory, but a really useful one would be the ability to pass a zip file location and have the worker container build it, exactly as it would on the server. This would let me people test their bot.zips before they send them to the server.

You can use python3 compiler.py directory/


Update Patches.plist

davinci resolve support

Great, does it work? If it does, I am ready to merge.


Add Unit Test GitHub Actions Workflow

WHAT
Added a GitHub Actions workflow that will automatically run vectorflow's unit tests when a pull request is opened, re-opened or edited.
VERIFICATION
Pictures below show that, with no changes to the core code, the jobs build and complete, passing all checks.

CAUTION
In order for this to work properly, environment variables must be set through GitHub Secrets. This should not be merged until this is done.
@dgarnitz

@kpriver55  Please document in this PR all the environment variables we need to set in the main repo to get this to work.
Can you also expand the sections in the screenshots like Run api unit tests so that the verification evidence proves that the tests pass. With github actions its possible for an action run to complete and the tests to not run at all but because it does not throw an outright failure, the actions runner still interprets it as a successfully run. Please re-run and add new screenshots

@kpriver55 if it does not matter what value it is set to, please set it to something random like qdrant.


Refactor creation of new MessageEmbed

Instead of this:

Write this:

Do this together with #53

done


Improve link text for MDN docs with anchors

Some of the links from features to MDN that we define in mdnDocsOverrides.json have anchrs in them. When that happens, we should make sure to capture the anchor in the link text, so users know where they're going. Right now, the link text shows the parent page's title only.
For example, when linking to the the linear easing-function section, we use the Web/CSS/easing-function#linear slug. The link text is currently See <easing-function>. It would be better if it was something like See linear, on the <easing-function> page.

Done in 020c3ca02dba96cd6db2c45dc1d77424c41ef1c4.


Bump framework version to 5.25.245

$subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/5508903806

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/5508903806
Status: success


DataTriggers for Entry controls on LogInView.xaml don't fire when the item to which they are bound changes

    <Entry IsPassword="True" Text="{Binding Password.Value, Mode=TwoWay}">
        <Entry.Style>
            <OnPlatform x:TypeArguments="Style">
                <On Platform="iOS, Android" Value="{StaticResource EntryStyle}" />
                <On Platform="WinUI" Value="{StaticResource WinUIEntryStyle}" />
            </OnPlatform>
        </Entry.Style>
        <Entry.Behaviors>
            <mct:EventToCommandBehavior EventName="TextChanged" Command="{Binding ValidatePasswordCommand}" />
        </Entry.Behaviors>
        <Entry.Triggers>
            <DataTrigger TargetType="Entry" Binding="{Binding Password.IsValid}" Value="True">
                <Setter Property="BackgroundColor" Value="{StaticResource ErrorColor}" />
            </DataTrigger>
        </Entry.Triggers>
    </Entry>

File: LoginView.cs, lines 202-224
I'm trying very hard to learn the method taught in the book (and in this accompanying code) for performing validations in .NET MAUI and MVVM. Now I've studied this quite a bit, and I think I understand everything (or at least most of it). But there appears to be a problem with the DataTriggers not firing in the Entry controls for UserName and Password in the login View.
For example, in the code above, we see that the DataTrigger in the Entry control for Password is bound to Password.IsValid in the login ViewModel, and we know that Password is a ValidatableObject in the ViewModel. Okay, so Password is a ValidatableObject and will therefore notify any bound controls in the View when the value for Password changes. But does Password.IsValid work in the same way? I mean, will Password.IsValid (not Password) also notify any bound controls in the View when the value for Password.IsValid (not Password) changes? I really don't think so. In my tests, I'm seeing that when the value for Password.IsValid changes from True to False, the DataTrigger in the View doesn't fire--presumably because it doesn't get notified about the change to Password.IsValid.
Is this a bug? Or what's another way to handle this, so that the intended effect occurs (i.e. the background color of the Entry control gets changed in the View) when Password.IsValid changes in the ViewModel?

This problem with the background color not changing/getting updated is being caused by a bug in the Entry control for .NET MAUI. Apparently, this is an issue that's been around for a long time.
As a workaround, I'm wrapping each entry control inside of a Border control. Then I set the background color of the Entry control to "Transparent". Then I configure the DataTrigger to change/update the background of the Border control instead.
This is probably much less efficient, and it requires more work to code. However, it does produce the intended effect.
As this issue isn't directly related to this repo, I'm now closing this issue.


Implement PACSUM

SentenceGraph should probably have some built in applications to increase its usefulness....
The code for PACSUM: https://github.com/mswellhao/PacSum is readable and not many changes are required to get it to work with SentenceGraph

https://github.com/Hevia/SentenceGraph/pull/3


Added resource for vm_extension_removal_policy

LWRP for setting/updating Azure Chef extension configurations: deleteChefConfig and uninstallChefClient.

Looks good -- so EXTENSION_PATH is always set on Azure vm's with the guest agent?

Sounds like the agent sets EXTENSION_PATH, so that's great. This looks good to me. :+1:

We should also update the README for this. This LWRP requires root user permission since we need to modify the extension's config file.
Also we should mention that user needs to set EXTENSION_PATH environment variable.


Need an option to have only atomic values editable

Currently, a text field is generated for the object (or array) itself too where the complete json can be viewed and edited. To make editing more user-friendly, there should be an option so that a property's value can be edited only by going down deep in the hierarchy and finding the text field for that property. In other words, there would be no text fields for arrays or objects, only for numbers and strings.

Good suggestion. A flag for turning this off would make it more "programmer's friendly" but it can be done already by applying the following CSS rule:
.item.array > .value,
.item.object > .value {
    display: none;
}

Thanks, @DavidDurman . This is a good enough solution for now.


Panel shows up when opening libraries

Closing in favour of https://github.com/spark/particle-dev/issues/226


ray.init() fails to start the dashboard with new version of setuptools (70.0.0)

Error:
2024-05-25 13:42:16,677 ERROR services.py:1222 -- Failed to start the dashboard , return code 1

...

File "C:\madewithml\venv\lib\site-packages\ray\dashboard\modules\dashboard_sdk.py", line 10, in <module>
    from pkg_resources import packaging
ImportError: cannot import name 'packaging' from 'pkg_resources' (C:\Users\JT\Documents\repos\madewithml\venv\lib\site-packages\pkg_resources\__init__.py)

您的邮件我已收到，将尽快回复！！

I was able to fix it on my end by python3 -m pip install setuptools==69.5.1
Suggesting that we add note about this after python3 -m pip install --upgrade pip setuptools wheel in https://madewithml.com/courses/mlops/setup/

@jgtiu did you run this in the cli or add it to cluster_env.yaml? if you added it to cluster_env.yaml did you just run anyscale job submit deploy/jobs/workloads.yaml and it worked after?

Ran it in the CLI, and I've never used cluster_env.yaml, since I'm following the "Local" track in the course and not the Anyscale track.

thanks @jgtiu! also curious if you got to this part (https://madewithml.com/courses/mlops/jobs-and-services/#execution_1) and got it to work. I ran it but when i go to the service it just says "unhealthy" and i dont see any logs that shows where it fails. It may be a code error in one of the scripts but i cant see any logs. If you know where to find that would be helpful


The ranking places should be stick to a chosen column

When choosing a certain column the places of Zones should display their place according to the chosen column
At the moment all the places stick to "IBC total" column

upd!
additionally, right now when choosing a column (other than Total IBC) - it sorts the table from least active to the most active zones


Onempers 424 json fix

just a note that currently the file still contains definitions for all the events:
jq .events LgiDisplaySettings.json | jq keys
[
"activeInputChanged",
"connectedAudioPortUpdated",
"connectedVideoDisplaysUpdated",
"resolutionChanged",
"resolutionPreChange",
"zoomSettingUpdated"
]
while 'RDK service manager calls made by JSAPP review' doc only lists 2 of these as required:
connectedVideoDisplaysUpdated
rxSenseHdmiChanged (this translates to 'activeInputChanged' in DisplaySettings plugin)


Op.DELEGATECALL accept incorrect number of arguments

check STATICCALL as well
it looks like I can legitimately write Op.DELEGATECALL( gas, addr, value, x, y, a, b)
and don't notice that it actually should be   Op.DELEGATECALL( gas, addr, x, y, a, b)

so here are the suggestions
Op.CALL()   empty constructor  that assumes tester preares the stack.  and the arguments constructor requires strictly.
Op.CALL_UNSAFE(...)    the current version of OPCODE
``

It seems like adding a parameter called unsafe does the trick, like this:
Op.TSTORE(0, unsafe=True)

I have a branch to test this and surprisingly it does not break almost any tests, but it highlighted some potential test errors that I'm taking a look into, so enforcing this seems like a good idea so this does not happen again.


generate vent.cfg for repeatable vent host settings on creation

[ ] plugins/tools and their settings
[ ] overlap from core.template remnants
[ ] any other host configurable settings
[ ] should be able to save a host's current settings to a vent.cfg
[ ] should be able to apply a vent.cfg to a host and have it behave as specified by the vent.cfg after it has been applied
[ ] starting/stopping of groups of tools
[x] global settings, such as file path for processing against plugins, etc.

closing as there hasn't been any new activity in over 2 years.