repeated headers are not correctly concatenated

When parsing a curl command with repeating headers, like in curl example.com --header "Accept: application/json" --header "Accept: */*", I expect the value for the repeated header to be correctly concatenated like in the snippet ⬇ but with curlconverter 3.21.0 this is not the case.
Expected:
var fetch = require('node-fetch');

fetch('example.com', {
    headers: {
        'Accept': 'application/json,*/*',
    }
});

Actual:
var fetch = require('node-fetch');

fetch('example.com', {
    headers: {
        'Accept': 'application/json',
        'Accept': '*/*'
    }
});

A relevant excerpt from the HTTP spec with links to the full spec: https://stackoverflow.com/a/24502264

This is not how curl behaves though. Testing with nc -kl 8888 and running this command curl localhost:8888 --header "Accept: application/json" --header "Accept: */*" we get this output
GET / HTTP/1.1
Host: localhost:8888
User-Agent: curl/7.77.0
Accept: application/json
Accept: */*

I think it's better to match curl's behavior, the idea being that if a curl command works (i.e. causes the server you're sending requests to to send you the data you want) the converted code will too.

I agree, it’s better to match the curl behavior. But there is a problem with generating
headers: {
    'Accept': 'application/json',
    'Accept': '*/*'
}

The second key/value pair overshadows the first one. Effectively, this leads to a fetch call that ignores the first header.
I have not checked with the other languages / generators, but I’m guessing some of them would have a similar issue.
I would not close this issue just yet.

You're right, I was in the middle of writing a similar comment to re-open the issue. We have the same problem with the Cookie header, which is concatenated but separated by ;. We need a parser for each header and we'll have to add a comment to warn users that the generated request will be a bit different different.


[occm] Multi region support information

Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature
What happened:
We are currently testing kubernetes deployment on several openstack clusters.
We deployed one occm by openstack and enabled OS_CCM_REGIONAL.
OCCM is mostly used for cloud-node and cloud-node-lifecycle services
What you expected to happen:
All seems to work as expected, az1 occm delete node with az1 prefix in providerID field as expected.
Node are added to the cluster with the right provider ID
Anything else we need to know?:
What is missing in order to consider this feature as GA ?
is this testing case ?
How could we help for this suject
Environment:

openstack-cloud-controller-manager version: v1.29.0
OpenStack version: Queen (17.6.0)
Others: kubernetes 1.26.10 / 1.27.8

What makes you think this is not a supported thing? Anyway if you want to contribute to this feature, we certainly don't have a CI job testing it, so that sounds like a fair first step.

@dulek
the "alpha" https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/openstack-cloud-controller-manager/using-openstack-cloud-controller-manager.md
make me think that

@dulek the "alpha" in occm doc make me think that

Ah, here it is! Well, looks like nobody looked at this for 2 years, it should be out of alpha by this time, though I'm not sure how many installations do that and how production-proven it is.
My idea to move forward would probably be to ask about the feature on the #provider-openstack on the K8s Slack. As a next step let's also make it a general option and not just a hacky env var. Then I guess we can assume that we'll try fixing issues as we go. And obviously my CI remark still stays.

Happy to ear that @dulek
let me look at the CI process and maybe submit a pr (with doc up to date)


[UT] Fix OlapTableSinkTest UT

What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[x] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

run starrocks_admit_test

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)


Improve GitHub actions flow

Codecov Report

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

@@         Coverage Diff          @@
##           master   #94   +/-   ##
====================================
  Coverage       0%    0%
====================================
  Files           4     4
  Lines          18    18
  Branches        2     2
====================================
  Misses         18    18

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 3100a13...5a543e7. Read the comment docs.


Condition for the filename when using ktk.kinematics.read_c3d_file(filename)

Describe the bug
When utilizing  ktk.kinematics.read_c3d_file(filename), there is an error "OSError: Could not open the c3d file: iostream stream error" if the filename contain spaces or "é".
To Reproduce
Steps to reproduce the behavior:

Name your folder or file with space or "é".
Use the .get() function to get the filename.
Use ktk.kinematics.read_c3d_file(filename).

Expected behavior
I was expecting to open the c3d file and extract the TimeSeries.
Screenshots

Python installation
Select: Miniconda
Operating system

Windows 11

Additional context
When getting rid of the spaces and "é", everything work perfectly.

Note: I don't have this bug on macOS

I do have the bug on Windows. This is an ezc3d bug, I filed it on https://github.com/pyomeca/ezc3d/issues/252
Let's see what happens, and if we need a workaround.

ezc3d only supports UTF-8 naming. I'll try to make a workaround.


EN_track_check

I'll be pushing progress on #54 to this pull request; still a long way to go, but some of the strategy is visible right now.
Unlike all the other qctests, EN_track requires all the profiles from a given cruise all at once. But, for performance, we don't want to load any given profile more than once. In order to approach this, I'm trying the following:

after loading the full list of profile primary headers, sort by cruise number.
instead of running the full suite of tests after loading each individual profile, load an entire cruise worth of profiles, make them available on the global data store, then run each test individually exactly as previous, profile by profile.
have EN_track write a copy of its results to the global data store. This way, the first time EN_track is called for a profile in a cruise, it can pull all the relevant profiles from the data store, run the qc check for the whole cruise, and on each subsequent call for the rest of the profiles in the cruise, the answer can be fetched and returned from the data store without actually rerunning the qc test.

The actual guts of EN_track aren't implemented yet, but just running this as-is seems to make the correct information available at the correct times, without any additional reads, and without adding any specifics of EN_track to the main routine.
Some concerns:

sorting the profile primary headers by cruise number could get slow for a huge number of profiles. Can we perhaps safely assume that all the profiles for a given cruise are in the same file?
This whole scheme assumes it won't be too cumbersome to load all the profiles for a single cruise. Good assumption / bad assumption?

@s-good: I'm going to forge ahead with this strategy if I don't hear from you; let me know if you anticipate any pitfalls here.

Hi @BillMills just to clarify, we don't need to load the full profile data for this test. The information that is loaded with the load_profile_data keyword set to False in the WOD profile reader is adequate, so there shouldn't be any memory issues.

@s-good That's much simpler then! I'm at a conference all week, but I will change course hopefully this weekend. Thanks for having a look!

Today's commits do a few things:

sends the headers (and only the headers) to the data store, sorted by cruise and time
implements a basic speed check between time-adjacent points on a cruise.
note that the text wasn't very explicit about their Dist(K) variable; this seems to be the distance between measurements, which I take as the haversine of the longitudes and latitudes of adjacent measurements.

This has the data routing and sorting nailed down, but the test itself is currently a toy implementation only. Still to do:

Distinguish between ship and buoy measurements.
Implement angle calculations between track segments
Implement logic to decide which endpoint of a track segment is incorrect, when one is flagged
Tests.

aad1bf3 approaches a complete implementation of EN_track, except for a few things I need clarification on from @s-good :

Condition (a) in the text mentions that 'An analogous test is used if M is the last report in the track', but the analogy is not obvious, since condition (a)'s test refers to the speed at position M+1.
Condition (e) appears to have a misprint in the text; there is no boolean operator anywhere in the expression as written.
Condition (h) has the same problem as (e).
It's not immediately obvious how to decide if a track is a ship or a buoy; I see the probe_type function on the WOD class, and table 29 on page 90 of the WOD docs, but I don't quite have the domain knowledge to parse that as 'ship' or 'buoy'.

Once those are cleared up, we can check the implementation with some tests and merge afterwards.

In respect to the last point, from table 29
1, 2, 5, 6 & 8 should be ship
14 could be from ship as well
12 is ship, but reduced speed
4, 7 are ship, but drifting, i.e. not underway
10 is fixed position, moored
9, 11, 13, 15 slow speed

Hi @castelao, thanks so much! And sorry for the absurdly slow reply, I've been traveling for a few weeks.
So, this helps a lot, but there are some issues; for example, does this test even make sense for 10 (fixed position)? Should we opt out for those profiles in that case? For 4, 7 and 12, I'm going to assume the slow speeds mean we should use the buoy characteristic speed, even though these are ship-based measurements. Under these assumptions, we have:

code
type
max speed (m/s)

1
MBT
15

2
XBT
15

3
DBT

4
CTD
2

5
STD
15

6
XCTD
15

7
bottle / rossette / net
2

8
underway / intake
15

9
profiling float
2

10
moored buoy
(abort test)

11
drifting buoy
2

12
towed CTD
2

13
animal mounted
2

14
bucket
15

15
glider
2

16
microBT

Somehow I suspect some more of these should be dismissed (gliders? animal mounts?) as inappropriate data sets for this test - @castelao @s-good, help me fill the rest of this out and we can knock one of the above bullet points off the list.

Hi, don't worry.
Those speeds sound reasonable for me.
I would keep gliders and animal mounts, so it could detect typos or other mistakes in the position and/or timing.
Might be valid the test for 10, maybe not exactly the same test. A mooring can break free and drift for a while before being recovered. Other possibility is to transmit, or store, a wrong GPS position or time. Such test would capture that. But a 0 velocity wouldn't work due the noise in the GPS position.

Okay great - buoy / ship discrimination is implemented in 9f8f85a as described in the table above; note that for DBT and microBT, no comment was made, so these abort the test (ie no flags raised) at the moment. Let me know any changes requested to the above table. Thanks @gui!

Hi @BillMills, sorry for the extremely delayed response to this:
First bullet: if the last three points in the track are x, y, z then if speed between x and z < tolerance and (speed between x and y > tolerance and angle at x > 45) then reject y else reject z.
Second bullet: > signs seem to have been missed out - e should read If Angle(M − 2) > 45 and Angle(M − 2) > Angle(M + 1) then reject M − 1; else if Angle(M + 1) > 45 then reject M.
Third bullet: same as above; h should read If ABS(PD1 − PT1) > 0.1 + ABS(PD2 − PT2) then reject M − 1; if ABS(PD2 − PT2) > 0.1 + ABS(PD1 − PT1) then reject M.
DBT and microBT can probably be treated the same as MBT as they are grouped with the MBTs in the WOD.
Many thanks for coding up this complicated check!

Thanks, @s-good - I'll revisit this check soon, but first we're going to have to smarten up our parallelization strategy; currently the script that splits our datasets up just blindly separates them into n chunks of equal size, but we'll need to make sure every profile from a given track is in the same chunk in order for this test to work in our infrastructure.
Looking ahead, can you foresee any other qc tests that will necessitate grouping together particular profiles in a single subset?

One of the EN checks is a buddy check which compares a profile to other, nearby profiles. The requirement is different to the track check as it requires profiles recorded using different instruments rather than all from the same platform/instrument for the track check. One option is to split the data into boxes according to profile location, but we'll still get problems at the edges of the boxes and the problem would get worse the more parallel threads we use. A better option would be to split by time (which may be what is already happening as WOD files are normally in date order but I'm not sure if this is the case for QuOTA). Unfortunately, though, it is possible that some QC checks will have a problem with this, too, although I don't know of any examples at the moment so we may be OK.

So, as discussed, I was looking into a new data splitting strategy that preserves cruise groupings for the track check; the latest commit provides a simpleminded strategy that does ok in the limit of total data >> single cruise data - which would have worked great if it wasn't for cruise 900229. This cruise appears to have just over 67000 measurements attributed to it - an order of magnitude more than anything else in quota. I guess it's possible but... seems suspicious?
If it's correct, that's a serious problem for parallelizing the track check, since we can't go any faster than a single core chewing through the largest subset.

I don't know about this 900229 cruise, but there are some repeating vessels of opportunity that have been measuring for a while, like the Oleander.
Maybe split the data in blocks with a "buffer" zone from the adjacent group. The data in the buffer is not evaluated, but only for support.
A smart data split would require to know in advance what it has to be evaluated. Another idea would be QC in two fronts. In the first one sequentially distribute the data for the regular tests that are independent, while collecting date/lat/lon/uid. Maybe an sqlite? While the regular tests are being processed, the sqlite is consumed applying the speed/track check, and searching for match ups for the buddy check. In my experience the heavy load is on defining the match ups, which run faster with indices. I did the buddy check before with all the data in a PostgreSQL + PostGIS, in a different scenario, probably not the best here.

It's possible e.g. that this a default code for if the cruise number is unknown, in which case the track check shouldn't be applied since there could be multiple ships reported under the same code. The CSIRO people should be able to advise.

@castelao I really like your idea of a two pass method that populates a sqlite database on the first go, so we can fish out groups of profiles (cruises, buddies, whatever) on the second pass efficiently, and allocate them to parallel threads that way. My only concern is that this is a big engineering project and will take (me at least) a long time - @s-good, what's our outlook wrt deadlines?

We have until May to implement as many QC checks as possible. I think we are in pretty good shape but we've still got the remaining ICDC and CSIRO tests to implement plus any other tests that we find that we feel should be included (e.g. maybe some more from WOD) so there is still potentially quite a lot to do.

Okay, May is going to come awful fast - I'm going to focus on @s-good's list before I worry about more infrastructural adaptions. But again, the two-pass database is a good idea that should be pursued as time permits.

last push catches us up with the large infrastructural changes since I first started working on this test, but more remains to be done to make sure this is playing nicely with our most current parallelization scheme, and reflects the text correctly.

Parallelization note: the condition introduced in #145 to make sure individual threads don't try to QC the entire list of headers kept on hand for the buddy check was a fine solution previously, but will cause problems with the track check since it uses the header list inside the qc test, circumventing the patch in #145; we'll begin keeping an additional header list of just those headers in the current thread, to loop over and for use in the track check.

Alright - I've done all I can think of to validate this test, and it seems to be working; would nevertheless recommend validation against real profiles as per #136 when feasible. Unit testing checks:

all helpers
each decision step (a)-(h) as evaluated individually (unit tests) and as part of the full chain (integration tests), both for flagging the correct profiles, and in the case of the integration tests, that the flagged profiles are flagged by the expected step in the chain.

This test as implemented trusts that:

all profiles on a given track are in the same file / parallel thread
the headers of the tracks in the file considered by this thread are found on ds.threadProfiles

@s-good, I almost hate to ask you to review such a beast of a pull request, but given the complexity of this test, a second set of eyes comes highly recommended. Perhaps (perhaps) the easiest thing to do is examine the test suite and make sure the things it's asserting are true actually should be true. If you go this route, most of the tests rely on arrays of artificial profiles engineered to have specific problems; they all exploit the same few facts to cause faults in the desired places:

0.5 degrees latitude can be traversed in 1 hour at < 15 m/s, but not 1 degree.
almost all tracks are straight lines that may double back on themselves when large angles are needed.

Let me know any problems,

OK, will take a look. I will also try to dig out some real world examples to test.

I've had a look through the code, which looks fantastic. Thanks so much for doing this - it must have taken ages to do.
I've added some new tests including real examples which I'll try to send via a pull request. The good news is that the real examples all worked fine.
I did manage to break the code by having two profiles with identical times. I started trying to figure out how to solve it but realised I would probably end up messing it up by not understanding it well enough. It might not be related, but I noticed in line 172 of the QC check code that there is an if index < len(angles), which I think may always be true? Possibly it should be index < len(angles) - 1? As I say, I didn't want to start introducing changes like this without knowing the code well enough.

I also just tried running the 150 test profile set through AutoQC. The track check rejects 83% of good profiles (which is excellent) but also 83% of bad profiles (which is not excellent!). Does this indicate that it is running the track check on a set of profiles that are not from the same instrument and needs to be excluded from the track checking? E.g. it looks like profiles with cruise ID == 0 are being rejected, which should be excluded from track checking I think.

OK, a few comments:

The identical times test was erroring previously because we weren't properly handling the case where there were only two profiles on the track (good thing @s-good's new tests thought of that!). Now the test fails instead of errors, because as written it expects the case of two profiles with different positions and identical times to pass, but EN-track sees the second profile as having an infinite velocity, and decides to reject the first profile. Which doesn't sound unreasonable to me; @s-good, what behavior ought we have when identical times are found?

I don't think @s-good's point about the index checking around 172 was responsible for the error state discussed above, but I do think it was a weird decision in hindsight; if we're at the end of the angles array, it'll find None and not pass the next conditional, which seems fine, no need to avoid this. On the topic, I also removed the -1's from the front of speeds and angles and replaced them with the more-appropriate None.

Oh and:

I'm not taking any of the results on quota_subset too seriously; it's just too small a dataset to draw any meaningful conclusions from. I like running on it just to make sure there isn't something spectacularly broken that the unit tests were too atomic to catch, but other than that, we'll see what's what when we run the full stack again (soon - after this test is sorted). @s-good, I agree that running track on things with cruise ID == 0 doesn't make sense; if we're concluded there, I'll address that before we merge.

Hi @BillMills, it's a good question about what should happen if times are identical. I put in the test more to make sure that the code could handle the situation without breaking and hadn't thought properly about the end result. The code is sort of designed to handle this by having the TimeRes as the minimum time difference that is allowed, so we can probably accept what the code is doing.
I was thinking about the profiles with probe type 0 (unknown type) and I think that they could maybe be checked assuming the higher of the two max speeds.
Thanks again for doing this!

Alright - implemented everything in this last round of discussions:

don't test track id 0
assume the higher max speed for probe id 0
allow test to make its own decisions about profiles with identical times.

I think this is stable and robust enough to merge - a paltry 10 months after #54 was opened!


Closes: #1: Updated validations.py script

Updated validations.py python script.
Fixed the behaviour of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[x] Tests pass
[x] Appropriate changes to README are included in PR

@googlebot I signed it!


Add reward clipping and observation preprocessing in T2TGymEnv

Does not move preprocesing in model-based rl to T2TGymEnv, jet.
Note that PIL.Image.resize(..., resample=BOX), should be identical to tf.image.resize(..., method=AREA) used so far, when image dimensions are dividable by resize factor (for Atari this is eg. 2,4,5), but will slightly differ for other values.

Closing this PR to create new one (with branch rebased to master)


Feat: internal commands with spaces

For test purpose #156

Seems to work pretty good to me

@fdncred yes, it works, but the dirty hack somehow worries me a little bit :-)

I just noticed that the INTERNAL only has commands with spaces in them vs the entire list of commands. Is that because the single word commands are already captured elsewhere?

I just noticed that the INTERNAL function only has commands with spaces in them vs the entire list of commands. Is that because the single word commands are already captured elsewhere?

Yes, as the cmd_identifier.

Also keep in mind that in order to get commands and plugins with spaces in them, you have to have the plugins built, installed, and registered for this command below to work. Also, that command would get multiword aliases and custom commands too.
scope commands | get name | where {' ' in $in} o> list

This is the command below is probably more appropriate. It could be easily tweaked to include only the commands/plugin commands with spaces in them. We could also include command_type == external and that adds whatever custom completions you have loaded. 🤔
# generated with Nu 0.100.1
help commands |
   where command_type == built-in or command_type == plugin or command_type == keyword |
   get name |
   where {' ' in $in}

Current implementation can't tell internals/externals from each other, if we want them highlighted differently, more complicated cmd_identifier is necessary.

I'm not saying that they should be highlighted differently. I'm just saying that the help commands or scope commands only needs to list the appropriate things. e.g. custom commands should not be included in our list.

I'm not saying that they should be highlighted differently. I'm just saying that the help commands or scope commands only needs to list the appropriate things. e.g. custom commands should not be included in our list.

Sure, this pr is just a demo, we should redesign pipeline to generate the list.

I have the rustup, cargo, git and gh custom completions loaded (along with keywords, builtins and plugins) and I have a list of 531 commands with spaces in them. I can provide that list or just update this PR before landing it.

Does your script above generate all 531 of those commands? If so, we can add that script along with the generated list file to the repo. But I guess only you can maintain that list right? We probably only get a small part of it with the same script?

We probably should test the impact on performance, 531 seems to be a significant number.

@fdncred Do we need cargo xxx in the list?

We can remove any of them that we want. However, I'm not sure 19 commands will make any difference. These are just the custom completions I usually run with rustup, cargo, git and gh.

@fdncred we can keep it and update the test case,
the performance loss is about 7~8%, 4757/5136 bytes/ms


Check for ownProperty before adding header

Hello everyone
An issue was filled on chai-http chaijs/chai-http#153
The issuer was adding a property to the prototype of Object which was making superagent throw a TypeError when setting a header. (I know you should not be adding properties to the prototype of Object, but the truth is that you can).
So, to prevent that for happening. This PR adds a check for hasOwnProperty before setting the header.
I also added a test that reproduces it.
Thank you 😄

Thank you


Pin a specific window to be always on top (like deskpin)

Just like the calculator have a feature to keep it always on top over other windows.

Duplicate of #13

Tria

https://github.com/microsoft/PowerToys/labels/Product-Always On Top


Aakash isro homepage link

Added the link to ISRO homepage and as soon as someone clicks on the logo, it will take them to the privacy page of ISRO.

Conflict resolved.


PathChildrenCache doesn't throw exceptions when path doesn't exist

PathChildrenCache doesn't throw exceptions when path doesn't exist on zookeeper server,
so in this case if you start a cache previous of path creation, then the listener doesn't catch any event.
This behavior is not logged in, so the user cannot do action to actuate any sort of compensation.

I've fixed this and push a new build. PathChildrenCache now ensures the path. I'll build new binaries soon.


Uninstalling Mods

I was trying to uninstall my mods for Outer Wilds and I uninstalled my mod manager before uninstalling my mods and now when I try to reinstall the mod manager to uninstall my mods, it says 'installation aborted'. What do I do?

Not sure what could be the problem with the installer. One thing you can do to uninstall all mods without the manager is doing the "verify files" in Steam or Epic. This will remove OWML, so mods won't load anymore.

There is now a solution explained in the Readme for this problem: https://github.com/Raicuparta/ow-mod-manager#installation-aborted-error

There is now a solution explained in the Readme for this problem: https://github.com/Raicuparta/ow-mod-manager#installation-aborted-error


Add Cowboy2

I'd like to add cowboy 2 to the mix.
The current version (2.4) still has Plug.Adapters.Cowboy and the mail preview works.

Thanks. Could you include the mix.lock change as well?

@princemaple do you think we should do that yet?

{:cowboy, "~> 1.0.1 or ~> 1.1 or ~> 2.4", optional: true}, I don't see anything harmful. Users can still choose which version to use..?

True! 👍

Just tried locally, you are right.


extract parsers from core

The parsers in core package increase the published package size for no good reason. They can be extracted to @tokey/experimental-parsers or individual packages if needed.

resolved in #42


Custom Layer::Metadata: inappropriate serialization (?) and silent failure when deserializing

For context, I have implemented several layers (e.g.) using the following pattern,
impl Layer for AptPackagesLayer {
    type Buildpack = AptBuildpack;
    type Metadata = AptPackagesLayer;

where AptPackagesLayer is
#[derive(Clone, Deserialize, Serialize)]
pub struct AptPackagesLayer {
    /// The version of Ubuntu that packages will be installed for e.g `bionic`, `focal`
    version: String,

    /// The path to the `Aptfile` (or similar name) that specifies packages to be installed
    file: Option<PathBuf>,

    /// Should Ubuntu deb repository mirrors be used?
    mirrors: bool,

    /// Should packages that are no longer in the Aptfile be removed
    clean: bool,

    /// A list of package names, or deb URLs to be installed
    ///
    /// Usually instead of an `Aptfile` but can be specified in addition to it
    packages: Vec<String>,

    /// A list of repos to be used
    ///
    /// Usually instead of `:repo:` entries in an `Aptfile` but can be specified in addition to it
    repos: Vec<String>,
}

When building an image using this buildpack I was finding that it would always recreate the apt_packages layer and that existing_layer_strategy was never getting called (summized from log output) e.g.
$pack build stencila-run:nano --builder stencila/builder:pico --pull-policy=if-not-present
===> ANALYZING
===> DETECTING
[detector] stencila/stencila              0.1.0
[detector] stencila/apt                   0.1.0
[detector] paketo-buildpacks/image-labels 4.1.1
===> RESTORING
[restorer] Restoring metadata for "stencila/stencila:stencila" from app image
[restorer] Restoring metadata for "stencila/apt:apt_packages" from app image
[restorer] Restoring data for "stencila/stencila:stencila" from cache
[restorer] Restoring data for "stencila/apt:apt_packages" from cache
===> BUILDING
[builder] 2022-05-18T22:52:19.637045Z  INFO buildpack_stencila: Existing `stencila` layer has `stencila 1.9.2` which matches semver requirement `>=1.1.0`; will keep
[builder] 2022-05-18T22:52:19.647018Z  INFO buildpack_apt: Creating `apt_packages` layer
[builder] 2022-05-18T22:52:19.660912Z  INFO buildpack_apt: Updating apt caches

When I checked the meta data on the image I noted that the empty repos vec is serialized to JSON as null, instead of an empty array [] (the same happens for packages if it is empty).
$ docker inspect stencila-run:nano | jq .[0].Config.Labels
<snip>
\"launch\":true,\"cache\":true}}},{\"key\":\"stencila/apt\",\"version\":\"0.1.0\",\"layers\":{\"apt_packages\":{\"sha\":\"sha256:b93f7cdf5f74aaa582d96e9e86d2215d071a0010fd4254c8bf49c14e38b18558\",\"data\":{\"clean\":true,\"file\":\"Aptfile\",\"mirrors\":true,\"packages\":[\"tree\"],\"repos\":null,\"version\":\"focal\"},\"build\":true,\"launch\":true,\"cache\":true}}},{\"key\":\"paketo-
<snip>

I was able to make the layer behave as expected by making serde deserialize those nulls into empty vectors by adding #[serde(default)]:
#[derive(Clone, Default, Deserialize, Serialize)]
#[serde(default)]
pub struct AptPackagesLayer {

However, it feels that there could be a couple of improvements in libcnb:

Do not serialize empty Vecs as null or at least document that it is necessary to use #[serde(default)] or similar for custom metadata if it potentially has empty vecs (apologies in advance if its already there but I missed it).

Emit an error message if de-serialization fails

@nokome I've felt similar pains when using usize in my own Metadata implementations. If the Serialize and Deserialize aren't perfect, it can be frustrating to debug why existing_layer_strategy wasn't getting called.
While not exactly what you are asking for, implementing migrate_incompatible_metadata might have helped you diagnose this sooner:
https://github.com/heroku/libcnb.rs/blob/0afba2a5fa4226491d6a1fc95e1da2a3e084900e/libcnb/src/layer/public_interface.rs#L111-L132
My understanding is that these failures are silent to allow for changes to the metadata schema over the lifetime of a buildpack. Layer metadata from an older buildpack implementation is likely to occur and something buildpack authors should plan for. But I tend to agree these failures should probably at least emit some logging to help buildpack authors and consumers debug.

Thanks @joshwlewis, I didn't know about migrate_incompatible_metadata. It seems like a useful function to have!
But, in a similar viewn to the discussion in #371 re existing_layer_strategy, it feels like there could be some better DX to avoid those silent failures.


virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml hs_err_pid*

Challenge Name

Issue Description

Browser Information

Browser Name, Version:
Operating System:
Mobile, Desktop, or Tablet:

Your Code

Screenshot

@noorizzwan please do not spam on the issue tracker. Refer our Code of Conduct


Errors thrown when non-html props are passed to animated.elements

Whenever I pass a non-HTMLAttribute to an animated element, for instance a animated.div, something similar to the error below is thrown. I'm using Typescript, if that would make a difference.

It's cluttering my console and it would be great to get rid of them. Maybe it has something to do with the static propTypes = { style... } in createAnimatedComponent.js?
EDIT: The reason for passing these props is that I'm using styled components from react-emotion, which means I can parse the returned className with styles based on the props passed.

@drcmda Well, yes, but styled-components and react-emotion works differently.
For instance, you can do:
const StyledElement = styled(animated.button)(({ baseColor }) => ({ backgroundColor: baseColor }));

return <StyledElement baseColor="red" onClick={() => console.log("clicked!")} />

And this works fine when doing e.g. styled('div') or styled(ComponentThatAcceptsClassNameProp), but not with an animated.element. Well, it works, but it throws the errors that I previously mentioned.

In that case, this works for me:
const StyledElement = animated(styled.button(({ baseColor }) => ({ backgroundColor: baseColor })))

Scratching my head why exactly that is ...


[QST] Extracting Item Embeddings from Trained Model.

❓ Questions & Help
I'm looking to extract the item embeddings for each item after training the model.
What is the best way to do this?
Digging through past issues I found this code:
pretrained_embeddings = model.heads[0].body[0].item_embedding_table.weight.cpu().detach().numpy() ( #425)
However the issue I have with this is that it returns an array of embeddings, but I'm not sure how to match the corresponding Item-Ids.

I think, the categories/unique.item_id.parquet file contains the dictionary that maps the actual item_ids to the item indices used by the model. Using this mapping you can know the item-embeddings correspondence.

@dhollier hello. Yes, as @murali-munna wrote, you can use the unique.item_id.parquet to do the mapping to the original item_ids but couple things to keep in mind:

Say you got  [501, 64] from model.heads[0].body[0].item_embedding_table.weight.cpu().detach().numpy().shape .  that means, you have 500 unique items but you have +1 outputted and this +1 corresponds to the OOV/nulls. You won’t have OOVs in your train set but you might have in your valid set, and they are mapped to 0 when we apply Categorify() op on validation set.  Note that we also have padding value in TF4Rec model, and it is 0 by default.

So what you get basically is the embedding weights for encoded item_ids in this order [0, 1, 2, ..., 500]. To convert this to the original item_ids is straightforward. Just use the categories/unique.item_id.parquet file and do the mapping.

If we use start_index =1 in the Categorify() op then the item_id encoding starts from 2 not 1. Because we reserve 0 for padding, 1 for OOV +nulls, and then the other item categories start from 2. In that case, you will get 2 + n_unique_items from model.heads[0].body[0].item_embedding_table.weight.cpu().detach().numpy() . Meaning,  you will get embedding values for 2 + n_unique_items, where first two are for padding and OOV+nulls.  One caveat here is that our unique.item_id parquet file (mapping file) does not reflect the shifted indices when we set start_index > 0 in the Categorify. You need to shift the index accordingly. You only need to shift the index of the parquet file +1, if you se the start_index =1.

you can check this ticket for further info:
https://github.com/NVIDIA-Merlin/Transformers4Rec/issues/612

Hi @murali-munna & @rnyak,
Thanks for the explanation. This worked!

@dhollier if you dont have further questions, can we close this ticket? thanks.

Yes no further questions this is safe to close 👍


getting problems with running webclient locally.

Home page works fine.

some problem with the report page.

Twitter walls are empty every other times I visit this.

No idea whats going on the connect page.

Please help me to get going. any sort of help appriciated.

You also need to have the loklak server running

@aneeshd16 doesn't the gulp-dev runs one server for itself?
Let me try once. Thanks

@aneeshd16 do I need to change the port for loklak_server?

Have you made a custom_configFile.json? That file should contain all configuration options including server urls and ports. If you make a copy of configFile.json, it should have the correct default values.

ya  I do made it, that's why the webclient is running that way I guess.

@aneeshd16  what are the fields which I need to change in the custom_configFile.json . coz now the home page is too not opening properly.

From the docs:

Create an twitter application at https://apps.twitter.com, remember to set the correct website url & callback url (for localhost, http://<IP_ADDRESS>/ works better), then modify custom_configFile.json:

Set the twitterConsumerKey var in custom_configFile.json to set the Consumer Key (API Key) from your Twitter app
Set the twitterConsumerSecret var in custom_configFile.json to set the Consumer Secret from your Twitter app
A twitter app is valid only for a domain (defined when creating the app). So the credentails above need to be changed also according to the domain (e.g. you'll need to create 2 twitter apps separately for a clone in localhost and for a clone in a remote server)

@aneeshd16 that's all I followed but unable to follow the last point. you'll need to create 2 twitter apps separately for a clone in localhost and for a clone in a remote server
what exactly I have to do here?

Set up needs to be improved. This will be part of a bigger update of code. Closing this issue therefore.


Tab aria selected

What
Instead of removing the aria-selected attribute, set it to false for the tabs that are not selected.
Why
When using VoiceOver (built in macos screenreader)  if a tab does not have aria-selected="false" it is read as "selected", so right now starlight tabs are all read as selected making it confusing to know which one is actually selected

Hello! Thank you for opening your first PR to Starlight! ✨
Here’s what will happen next:

Our GitHub bots will run to check your changes.
If they spot any issues you will see some error messages on this PR.
Don’t hesitate to ask any questions if you’re not sure what these mean!

In a few minutes, you’ll be able to see a preview of your changes on Vercel 🤩

One or more of our maintainers will take a look and may ask you to make changes.
We try to be responsive, but don’t worry if this takes a few days.

size-limit report 📦

Path
Size

/index.html
6.1 KB (+0.07% 🔺)

/_astro/*.js
21.56 KB (+0.01% 🔺)

/_astro/*.css
13.45 KB (0%)


[GHSA-9gh8-877r-g477] Beetl Server-Side Template Injection vulnerability

Updates

Affected products
CWEs
Description

Comments
Checking the Issue, it states that versions including 3.15.12 are affected.
Checking the affected source code shows that it is under the beetl-core.

Checking the Issue, it states that versions including 3.15.12 are affected.
Checking the affected source code shows that it is under the beetl-core.

👀
Any chance you have a link to that source code?


Several issues with extending Nuxt Layer

Environment

Operating System: Linux
Node Version:     v20.15.0
Nuxt Version:     3.13.1
CLI Version:      3.13.1
Nitro Version:    2.9.7
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      extends, compatibilityDate, devtools
Runtime Modules:  -
Build Modules:    -

Reproduction

Create fresh nuxt project
Extend the nuxt content theme like below:export default defineNuxtConfig({
  extends: [
    ['github:jd-solanki/nuxtpress', { install: true }]
  ],
  compatibilityDate: '2024-04-03',
  devtools: { enabled: true }
})

Describe the bug
Once we have above setup here's list of issues I'm running into:

[ ] When I perform ni (pnpm install) it doesn't install dev deps like tailwind, sass, etc. I've to run command NODE_ENV=development ni

[ ] After installing all deps when I run pnpm run dev it throws [worker reload] [worker init] Cannot find package 'nitropack' imported from /home/tops/Projects/oss/nuxtpress-docs/.nuxt/dev/index.mjs. Along with this I also get some error related to sass-embed.

[ ] Also my nuxtpress repo is cached because when I already have a new push to the github but still it uses old commits so it'll be great if we can get docs on clearning layer cache if there's any

[ ] I'm also getting other deps warns when I run pnpm run dev:

View warnings
 WARN  Failed to resolve dependency: @nuxt/content > slugify, present in 'optimizeDeps.include'
 WARN  Failed to resolve dependency: @nuxt/content >remark-gfm, present in 'optimizeDeps.include'
 WARN  Failed to resolve dependency: @nuxt/content >remark-emoji, present in 'optimizeDeps.include'
 WARN  Failed to resolve dependency: @nuxt/content >remark-mdc, present in 'optimizeDeps.include'
 WARN  Failed to resolve dependency: @nuxt/content >remark-rehype, present in 'optimizeDeps.include'
 WARN  Failed to resolve dependency: @nuxt/content >rehype-raw, present in 'optimizeDeps.include'
 WARN  Failed to resolve dependency: @nuxt/content >parse5, present in 'optimizeDeps.include'
 WARN  Failed to resolve dependency: @nuxt/content >unist-util-visit, present in 'optimizeDeps.include'
 WARN  Failed to resolve dependency: @nuxt/content >unified, present in 'optimizeDeps.include'
 WARN  Failed to resolve dependency: @nuxt/content >debug, present in 'optimizeDeps.include'

Additional context
This is my development setup:
export default defineNuxtConfig({
  extends: [
    [process.env.NODE_ENV === "development" ? '../content-app/' : 'github:jd-solanki/nuxtpress', { install: true }]
  ],
  future: {
    compatibilityVersion: 4,
  },
  compatibilityDate: '2024-04-03',
  devtools: { enabled: true }
})

Logs
No response

When I perform ni (pnpm install) it doesn't install dev deps

If dependencies are required for your Nuxt layer to work, they should not be in the devDependencies list but dependencies.
For the other issues, would you mind creating separate issues for each of them so we can track/resolve them separately? It will make it easier and be more helpful for other users who encounter one of them.

Hi @danielroe
I hope you enjoyed the holiday 🏖

If dependencies are required for your Nuxt layer to work, they should not be in the devDependencies list but dependencies.

However, deps like tailwindcss & sass are devDeps by nature so is it good idea to add them under dependencies?

For the other issues, would you mind creating separate issues for each of them so we can track/resolve them separately? It will make it easier and be more helpful for other users who encounter one of them.

Sure.

All dependencies needed by your nuxt layer to be used should be in dependencies. devDependencies in the context of a layer should be things needed only when authoring the layer but not when it is consumed (like eslint, perhaps)


Usage with fiber v3

Hello,
I have tested and ready code which bumps the version to fiber v3.
I cannot push to this repo, I don't have permissions.
I'd like to contribute but I'm not sure how.

i think u can do pull request

@goodpeanut This middleware is being migrated to the GoFiber organization. Hold off for now


Investigate ways to impose partial ordering of messages sent to a chain

Summary
Find out if it is possible for a chain context to determine if an opaque message requires waiting for another message to be sent first before it can be sent.
Problem Definition
In relayer-next #2478, we employ massively parallel relaying by spawning many async tasks for each relaying operation. This concurrency architecture is based on the assumption that each relaying operation can be executed in parallel independent of each other.
However, there are several cases of relaying operations depending on each others, and that makes it difficult to parallelize such operations. Following are some of the use cases:
Ordered Channels
When relaying packets from ordered channels, a packet needs to wait for all other packets with a lower sequence to be relayed first. If multiple async tasks are generating IBC messages for the ordered channel at the same time, they must coordinate to ensure that IBC messages for the packets with lower sequence must be sent first.
Solomachine Relaying #2924
In solomachine relaying, the Cosmos chain rely on using a sequence stored in the client state to verify the IBC messages. In order for a proof to be valid, the signed data must have an exact match of the sequence stored in the client state. If multiple async tasks are generating IBC messages from a solomachine to a Cosmos chain, they must coordinate to ensure that the IBC messages with a lower sequence must be sent first.
Naive Workaround
A naive workaround for the above problem is to limit the parallelism, and allow only one async task at a time for relaying operations that are dependent on each other. However, this can significantly limit the performance of the relaying, as only one operation can be performed per chain height.
Note that even with the naive workaround, it is still possible to have concurrent relaying on unrelated operations. For example, there can be 3 async tasks that perform relaying of unordered packets, ordered packets, and solomachine packets, all to the same chain at the same time. And that is fine, because these operations are not dependent of each other.
Action Item
This issue would track the work to find a general way to resolve the task dependency problem. At a high level, we would need to design synchronization primitives such that the async tasks can wait for other tasks to complete some operation. Furthermore, the synchronization cannot just end after the previous message is sent as a transaction, as that would be too late to achieve any concurrency. Instead, we would need dedicated tasks to sequentialize the other tasks for generating messages, but then collect the ordered messages to be sent in the same batch.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Another complication to consider is that multiple partial ordering subsystems may affect each other and introduce deadlock.
Consider a case where a worker task for sending an ordered channel packet with sequence 2 across a solomachine channel, followed by a worker task of the same ordered channel sending packet sequence 1. This would result in a deadlock where the first worker acquired the lock for solomachine, the second work acquired the lock for the ordered channel, but none could acquire both locks to proceed.

A possible way to solve this is to take advantage of context-generic programming and employ message polymorphism to differentiate different messages.
Recall that similar thing has already done for the HasEventType::Event abstract type. There are traits such as HasWriteAckEvent which allows extraction of a HasWriteAckEvent::WriteAckEvent type from a HasEventType::Event type. On the other hand, we currently only have a HasMessageType::Message type that is used to represent all possible messages.
In the new design, we will introduce new abstract message types such as HasRecvPacketMessage<Counterparty>::RecvPacketMessage, which would be different for each counterparty. Following that, the message sender traits will also be changed from CanSendIbcMessages<Target> to CanSendIbcMessages<Target, Message>. With the changes, a packet relayer that needs to send a RecvPacket message would require the relay context to implement a trait like CanSendIbcMessages<Target, TargetChain::RecvPacketMessage>.
With this new design, we will be able to provide different concrete message types and concrete message senders depending on the situation. At the same time, if there is no need to handle special case, it is also possible to default all abstract messages back to the same concrete message type. For instance, in a Cosmos-to-Cosmos implementation, both abstract types <CosmosChain as HasMessageType>::Message and <CosmosChain as HasRecvPacketMessage<CosmosChain>>::RecvPacketMessage would have the same concrete type, which is CosmosMessage. In such case, there is also only one message sender that needs to be implemented, which is CanSendIbcMessages<Target, CosmosMessage>.
On the other hand, we will also able special case the implementation of solomachine-to-cosmos relaying, such that <CosmosChain as HasRecvPacketMessage<Solomachine>>::RecvPacketMessage would have the concrete type SolomachineToCosmosMessage. In this case, the packet relayer for solomachine-to-cosmos relaying would send messages to a special sink implemented for CanSendIbcMessages<Target, SolomachineMessage>. We can then spawn a dedicated worker task that sequentialize and collects the SolomachineMessages, and order them based on the sequence number. The nice thing about this design is that there is no need for dynamic dispatch or dynamic cast, as everything is static typed!
Similarly, for ordered packet relaying, there will be special traits like HasOrderedRecvPacketMessage<Counterparty>::OrderedRecvPacketMessage, which distinguishes from the unordered RecvPacket message. In this case, even for cosmos-to-cosmos relaying, the implementation <CosmosChain as HasOrderedRecvPacket<CosmosChain>>::OrderedRecvPacket would have a special concrete type like CosmosOrderedRecvPacketMessage. This would in turn allow sending of ordered packet messages to special sinks as implemented for CanSendIbcMessages<Target, CosmosOrderedRecvPacketMessage>
Lastly, the constraint composition allows us to take care of doubly ordered messages such as <CosmosChain as HasOrderedRecvPacketMessage<SolomachineChain>>::OrderedRecvPacket, which would have a concrete type like SolomachineToCosmosOrderedRecvPacketMessage. We would then have to implement dedicated worker tasks for that, but also coordinate with the more generalized worker task for SolomachineToCosmosMessage in order to avoid any possible deadlock.
All in all, the relayer implementation is going to be more complicated because of this. However, this may be an unavoidable complexity, as regardless of which programming technique we use, we would still need to write special cases when handling the sending of different kinds of messages. Nevertheless, the use of context-generic programming provides the flexibility for the implementation to either use the same concrete type for all abstract message types when there is no special case, or to use as many concrete type for each abstract message type as the number of special cases needed.


Reference to parent?

Can't seem to find that in the docs. Pardon if I misread somehow.
I'm doing the good old slide to unlock variant and so, I need to put some logic for when the dragged element has reached the end.

That sounds to me like a React issue, not a draggable issue. See https://facebook.github.io/react/docs/refs-and-the-dom.html


Error with example for i2c

IDE 1.8.10
sketch example for I2C gives this error:
no matching function for call to 'LiquidMenu::LiquidMenu(LiquidCrystal_I2C&)'
how can I fix it? library was downloaded from IDE

Because this is the I2C example you need to switch the configuration to I2C. In LiquidMenu_config.h comment lines 33-35 and uncomment lines 43-45.

Not working:
/*!
 * @name Arduino's parallel "LiquidCrystal" library
 * @{
 */
// #define LIQUIDMENU_LIBRARY LiquidCrystal_LIBRARY
// #include <LiquidCrystal.h>
// #define DisplayClass LiquidCrystal
//!@}

/*!
 * @name I2C library
 * @see https://github.com/johnrickman/LiquidCrystal_I2C
 * @{
 */
#define LIQUIDMENU_LIBRARY LiquidCrystal_I2C_LIBRARY
#include <LiquidCrystal_I2C.h>
#define DisplayClass LiquidCrystal_I2C
//!@}

Error:
In file included from /Users/antwal/Documents/Arduino/libraries/LiquidMenu/src/LiquidLine.cpp:30:0:
/Users/antwal/Documents/Arduino/libraries/LiquidMenu/src/LiquidMenu.h:56:122: note: #pragma message: LiquidMenu: Selected 'LiquidCrystal_I2C' (I2C) library. Edit 'LiquidMenu_config.h' file to change it.
 # pragma message ("LiquidMenu: Selected 'LiquidCrystal_I2C' (I2C) library. Edit 'LiquidMenu_config.h' file to change it.")
                                                                                ^
/var/folders/t8/b6xtsj5121q_9qcnbwcpcxwc0000gn/T//ccbVoEN0.ltrans0.ltrans.o: In function `global constructors keyed to 65535_0_sketch_jan12a.ino.cpp.o.2759':
<artificial>:(.text.startup+0x142): undefined reference to `LiquidCrystal_I2C::LiquidCrystal_I2C(unsigned char, unsigned char, unsigned char)'
/var/folders/t8/b6xtsj5121q_9qcnbwcpcxwc0000gn/T//ccbVoEN0.ltrans0.ltrans.o: In function `setup':
/Users/antwal/Documents/Arduino/sketch_jan12a/sketch_jan12a.ino:76: undefined reference to `LiquidCrystal_I2C::init()'
collect2: error: ld returned 1 exit status

@antwal no, it`s working correctly with that editions.

Have you downloaded the LiquidCrystal_I2C library.

yes use same lib but get this error always

The error states that there is an undefined reference to a function from this library.
Have you tried running an example from the I2C library? Maybe it's not installed correctly.
Do you get an error when I2C is disabled in LiquidMenu examples?

not working on platformio, but working in arduino ide

fixed


warning while starting apache server

Just getting this weird warning when I start apache2 server (but server is up and running)

Your Windows build number:  10.0.15063

What you're doing and what's happening:  sudo service apache2 start

What's wrong / what should be happening instead: getting this warning
[Sat May 06 20:46:15.177529 2017] [core:warn] [pid 544:tid<PHONE_NUMBER>18528] (92)Protocol not available: AH00076: Failed to enable APR_TCP_DEFER_ACCEPT

https://github.com/Microsoft/BashOnWindows/issues/1953#issuecomment-295370994


Make trace plot lines transparent

With the current, untransparent, output, it can be quite hard to spot issues with chains other than the chain in the foreground. Transparency would make it easier.
Example:

Here, it's easy to spot an issue with the chain with index 3, but the traces of chains 0, 1, and 2, are at least partially hidden from view.
I would propose to make transparency the default, with the option to turn it off.

This seems to require more effort than I thought. The sns.relplot does not offer transparency with a simple parameter, instead transparency would seemingly have to be implemented through the color palette.
I tried:

plt.setp(g.lines, alpha=alpha) https://stackoverflow.com/questions/56300170/is-there-a-way-to-set-transparency-alpha-level-in-a-seaborn-pointplot
plot_kws={"alpha": alpha}, copying from plot_pairs

Related link: https://stackoverflow.com/questions/37327308/add-alpha-to-an-existing-colormap


Any Way To Run GPT model locally

i want to run mindcraft but i have problem with rate limit and i dont want to buy a tier account

Second, it would be nice to use a local model for this.

#29
under this  #issue this  have been in the works and look like to be soon implemented.

#29
under this #issue this have been in the works and look like to be soon implemented.

i had a hard time doing it and i got it working but the ai take more than 5 minutes to respond and when i asked to do something. he keep saying he cant

#29
under this #issue this have been in the works and look like to be soon implemented.

i had a hard time doing it and i got it working but the ai take more than 5 minutes to respond and when i asked to do something. he keep saying he cant + any recommended model for mindcraft?

what GPU do you have
i use a 4060 ti 16gb
not tested as of yet but the best thing to do would be to get a 7b model and load it in 4 bit mode
flemmingmiguel_MBX-7B-v3 is model ive been working with however this not the best as LLM moved past it

#29
under this #issue this have been in the works and look like to be soon implemented.

i had a hard time doing it and i got it working but the ai take more than 5 minutes to respond and when i asked to do something. he keep saying he cant + any recommended model for mindcraft?

what GPU do you have
i use a 4060 ti 16gb
not tested as of yet but the best thing to do would be to get a 7b model and load it in 4 bit mode
flemmingmiguel_MBX-7B-v3 is model ive been working with however this not the best as LLM moved past it

RTX 3050 11 GB

you may have iusses then LLM are heavy to run idk how help you on such low end gear

you may have iusses then LLM are heavy to run idk how help you on such low end gear

well is there at least any way to run gpt or claude without having a paid account?

you may have iusses then LLM are heavy to run idk how help you on such low end gear

well is there at least any way to run gpt or claude without having a paid account?

easiest why is to buy  better gpu
if your willing to go all out a 4090 24gb is your best bet
low end a 4060 Ti 16 gb

Last I checked you only need to add $10 to your openai account which will probably last you 6+ months of moderate 3.5 turbo use.


fix(NetworkClient): Remove OnHostClientObjectDestroy

NetworkServer::UnSpawnInternal already does everything we need to do, and since the identity is removed from spawned before the ObjectDestroyMessage is sent the lookup never succeeds and the spawned.Remove was already done.

NetworkServer.Destroy calls UnSpawnInternal which does all the cleanup.

nice


GPT Disks supported for Linux?

Hello, this FAQ hasn't been updated since 2017.  Does the GPT limitation still apply to Linux machines.  I'm seeing that GPT disks are supported (as of 28AUG18) for linux machines that are being ASR to Azure.
https://docs.microsoft.com/bs-latn-ba/azure/site-recovery/site-recovery-whats-new?view=sqlallproducts-allversions
Granted this is support for ASR functionality, I guess it could mean they support that GPT disk, but then convert it to MBR?  Documentation is pretty sparse around that.

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

ID: 8b1fece1-fff6-0dde-c8fc-59d8d5fdd7e3
Version Independent ID: 5aaeabdb-bc30-0084-4d78-7069544fd608
Content: Frequently asked questions (FAQ) about Azure IaaS Linux VM disks
Content Source: articles/virtual-machines/linux/faq-for-disks.md
Service: virtual-machines-linux
Sub-service: disks
GitHub Login: @roygara
Microsoft Alias: rogarana

Thanks for the feedback! We are currently investigating and will update you shortly.

@johnwildes good question!
@roygara @Adam-Smith-MSFT @cynthn any idea on this?

@MicahMcKittrick-MSFT @johnwildes Thanks for reaching out, I checked with the product team, the doc is accurate. There's no support for OS disks, only data disks.

Thanks @roygara appreciate the help on this!
@johnwildes I will close this out for now but if you have further questions just let us know.

@MicahMcKittrick-MSFT someone needs to inform support.  If it's possible can we get a clarification in this document that it's only for DATA DISKS and NOT OS disks?  We've been round and round with a support "group" on this that says it's supported, but providing instructions that are destructive to the customer VM in attempt to migrate one VM we have to Azure.

@johnwildes this doc does specifically say it is for data disks and not for OS disks

I will take a look and see if I can find a good place to include this info in the ASR documentation though.

@johnwildes I added a link to the disks FAQ that states GPT is only for data disks to the link you provided in the original comment. That way the cross linking is easy to find and it will be less confusing.
Once the PR merges the changes will go live in a few hours.


License?

Can't find any mention of the open source license anywhere.
Sorry if I missed it.

@claudio-silva Sorry about that, I thought I put it on the github repo but don't see it. Anyway it is an Apache 2.0 license and you can get that info here: https://www.nuget.org/packages/OoplesFinance.StockIndicators/

@claudio-silva I just did an update to add my open source license and contact info on all pages so go ahead and close this issue if everything looks good now

Thank you for your response.
The idea of adding the license to all files was good, but still, it would be better and more in-line with accepted best practices for GitHub if you add a license file to the repo.
It's easy and quick; just follow these steps:
https://docs.github.com/en/enterprise-cloud@latest/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository
That way, it will be easier for anyone to find out which license is being used, the project will appear on searches filtered by license, etc.
As the bare minimum, a mention on the README would be very helpful.
Anyway, I'm glad the license is a good one, so this library may be useful for a small private project I'm working on.
Thank you for publishing it! 👍

@claudio-silva So I already changed the readme yesterday so it now reads like this:
This is a stock indicator library that is completely open source (Apache 2.0 license) and very easy to use
Also I did add the license file to the project but apparently spaced out and forgot to do a commit so you should now see the license in the root folder.

Great!
Sorry I missed the readme change.
Now I can also see the license on the right sidebar :-) and the license file.
I believe these changes will improve the project's discoverability and credibility a little bit.
Thank you for your quick response.


[Bug]: In the CE instance Share Modal is displayed empty when user deploy the app from edit mode

Is there an existing issue for this?

[X] I have searched the existing issues

Description
In the CE DP Share Modal is displayed empty when user deploy the app from edit mode

Steps To Reproduce

go to https://ce-27137.dp.appsmith.com/
Create a new workspace
create a app and crud page
now click on deploy button
in view mode click on share icon
The share modal is empty

Public Sample App
No response
Environment
Release
Issue video log
No response
Version
v1.9.37

tried it in local working fine


Flaky test: Terminal sendText immediately after createTerminal should not throw

https://dev.azure.com/monacotools/Monaco/_build/results?buildId=68166&view=logs&j=935a53e5-ce00-51d1-185d-b2f737723cea&t=78251e6f-ceae-58b8-b69e-6d3a7d24b6bc
This just broke the integration tests on Windows 32bit.

@Tyriar Is this still an issue?

Duplicate of #92826


Update node version

$ npm i

up to date, audited 1635 packages in 3s

183 packages are looking for funding
  run `npm fund` for details

7 vulnerabilities (1 low, 6 high)

To address all issues, run:
  npm audit fix

Run `npm audit` for details.

In order to complete an npm audit fix we need to update node from v18.15.0 to v18.18
Many metro related packages gave this warning:
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package<EMAIL_ADDRESS>npm WARN EBADENGINE   required: { node: '>=18.18' },
npm WARN EBADENGINE   current: { node: 'v18.15.0', npm: '9.5.0' }
npm WARN EBADENGINE }

$ nvm use 18.18.2
Now using node v18.18.2 (npm v9.8.1)

$ npm audit fix

up to date, audited 1251 packages in 2s

176 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities


Code duplication

Remove duplicate code of "Set schedulerName" block

 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.


When I was modifying the entry attribute, I found that the attribute case was converted to lowercase

Hi bro! when I used the client to send a entry for the server, I found that the defined attributes were converted to lowercase attribute names before being transmitted to the server. I mean used the add action.I found in @ldap/message lib -> add-request.js
This problem may come from the parseToPojo method (262 lines of code). Is it deliberately written like this? I want to know if it is a bug or it is designed like this.
while (ber.offset < endOfAttributesPos) {
      const attribute = Attribute.fromBer(ber)
      attribute.type = attribute.type.toLowerCase()

      if (attribute.type === 'objectclass') {
        for (let i = 0; i < attribute.values.length; i++) {
          attribute.values[i] = attribute.values[i].toLowerCase()
        }
      }

      attributes.push(attribute)
    }

Yes, that is correct. The spec mandates that attribute types are case insensitive.

Yes, that is correct. The spec mandates that attribute types are case insensitive.

ok~  i see
thanks!


gnome3 not found when upgrading from 18.03 to 18.09

Issue description
Error says gnome3 Desktop Manager is not found when trying to upgrade from 18.03 to 18.09.
Steps to reproduce

Take a running 18.03 system, and:

[root@desire:/etc/nixos]# nix-channel --add https://nixos.org/channels/nixos-18.09 nixos

[root@desire:/etc/nixos]# nix-channel --update nixos
unpacking channels...

[root@desire:/etc/nixos]# nixos-rebuild switch
building Nix...
building the system configuration...
trace: Default desktop manager (gnome3) not found at evaluation time.
These are the known valid session names:
  services.xserver.desktopManager.default = "xterm";
  services.xserver.desktopManager.default = "none";
It's also possible the default can be found in one of these packages:
  gnome-session-3.28.1

Technical details
[root@desire:/etc/nixos]# nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 4.14.68, NixOS, 18.03.git.dbdcdd3 (Impala)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.0.4`
 - channels(kandinski): `"nixos-18.09-18.09beta230.32c008a946c"`
 - channels(root): `"nixos-18.09"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs`

The relevant part of /etc/nixos/configuration.nix:
  # Enable the X11 windowing system.
  services.xserver = {
    enable = true;
    layout = "us";
    # xkbOptions = "eurosign:e";

    # Use GDM to login and switch between Gnome and XMonad
    displayManager.gdm.enable = true;

    # Enable the KDE Desktop Environment.
    # services.xserver.displayManager.sddm.enable = true;
    # services.xserver.desktopManager.plasma5.enable = true;
    # Or Gnome...
    desktopManager = {
      gnome3.enable = true;
      default = "gnome3";
    };

    # Enable XMonad Desktop Environment
    windowManager.xmonad = {
      enable = true;
      enableContribAndExtras = true;
      extraPackages = haskellPackages: [
        haskellPackages.xmonad-contrib
        haskellPackages.xmonad-extras
        haskellPackages.xmonad
      ];
    };
    windowManager.default = "xmonad";

    # Trackpad just in case, while I make trackpoint work
    synaptics = {
      enable = true;
      minSpeed = "0.8";
      maxSpeed = "1.4";
      accelFactor = "0.05";
      tapButtons = false;
      twoFingerScroll = true;
    };

    # Incompatible with Synaptics
    libinput.enable = false;
  };

GDM ignores desktopManager.default at the moment btw. Fixing this might be doable, but would probably involve quite a bit of work. Warning about this would be good, but I don't think it's easy to check if desktopManager.default have been explicitly set by the user.
So for now it's better to not specify desktopManager.default when using GDM, that should remove the warning. GDM will pick the gnome sesssion by default I believe and will definitely remember your last session choice.

Oh, thanks. I'll try an update now.


Rules backfill: return 1 if unsuccessful

importRules is called by checkError, which prints any error and handles the return code, therefore the function itself shouldn't be doing any printing. The rule importer can return multiple errors though, so I had to make an exception for that.
Fixes #9292

Thanks!


Migrating: edomata

Migration Checklist
Project Submission Issue: #84
For All Projects:

[x] Add project to the site by adding an entry to the projects.yml file

Announcements
These steps are optional but encouraged.

[ ] Write a blog post announcing the change
[ ] Post to our social channels (Twitter, Mastodon)

Added to the site and tooted.  I'm not sure whether we're still tweeting.

We should probably decide if we want to tweet any more.  I'm willing to interact with Twitter if the community feels it necessary, but I'm not going to be the one to motivate that at this point.  (IMO, Twitter has become enough of a swamp that I would kind of prefer for it to simply die.)

Nobody has claimed the Twitter.  Blogs on this (and Lepus) are welcome, but optional.  Closing.


"Invalid options type for foreign" error

Node v5.8.0
This is the log:
[17:56:29] Starting 'bundleJS'...
[17:56:29] Rollup [catch]:  TypeError: Error transforming C:\www\UI\BUILD\js\dist\app.js with 'babel' plugin: [BABEL] C:
\www\UI\BUILD\js\dist\x.js: Invalid options type for foreign
    at Logger.error (C:\www\UI\BUILD\node_modules\babel-core\lib\transformation\file\logger.js:41:11)
    at OptionManager.mergeOptions (C:\www\UI\BUILD\node_modules\babel-core\lib\transformation\file\options\option-manage
r.js:270:16)
    at C:\www\UI\BUILD\node_modules\babel-core\lib\transformation\file\options\option-manager.js:370:14
    at C:\www\UI\BUILD\node_modules\babel-core\lib\transformation\file\options\option-manager.js:396:22
    at Array.map (native)
    at OptionManager.resolvePresets (C:\www\UI\BUILD\node_modules\babel-core\lib\transformation\file\options\option-mana
ger.js:385:20)
    at OptionManager.mergePresets (C:\www\UI\BUILD\node_modules\babel-core\lib\transformation\file\options\option-manage
r.js:369:10)
    at OptionManager.mergeOptions (C:\www\UI\BUILD\node_modules\babel-core\lib\transformation\file\options\option-manage
r.js:328:14)
    at OptionManager.init (C:\www\UI\BUILD\node_modules\babel-core\lib\transformation\file\options\option-manager.js:481
:10)
    at File.initOptions (C:\www\UI\BUILD\node_modules\babel-core\lib\transformation\file\index.js:211:75)
    at new File (C:\www\UI\BUILD\node_modules\babel-core\lib\transformation\file\index.js:129:22)
    at Pipeline.transform (C:\www\UI\BUILD\node_modules\babel-core\lib\transformation\pipeline.js:48:16)
    at preflightCheck (C:\www\UI\BUILD\node_modules\rollup-plugin-babel\dist\rollup-plugin-babel.cjs.js:41:25)
    at Object.transform$1 [as transform] (C:\www\UI\BUILD\node_modules\rollup-plugin-babel\dist\rollup-plugin-babel.cjs.
js:104:18)
    at C:\www\UI\BUILD\node_modules\rollup\dist\rollup.js:6992:35
    at lib$es6$promise$$internal$$tryCatch (C:\www\UI\BUILD\node_modules\es6-promise\dist\es6-promise.js:362:16)
[17:56:29] Finished 'bundleJS' after 168 ms

And this is my Gulp Rollup plugin:
babelRollup({
    presets        : [['es2015', {"modules": false}]], //['es2015-rollup'],
    runtimeHelpers : true,
    exclude        : 'node_modules/**'
})

Hi, can you explain what you did to solve this issue ? Thanks

@sylvainpolletvillard  I think I might have installed Node 5 instead of 6 and it helped (if my memory serves me)

@yairEO Upgrading didn't help for me.

I solved the problem by removing the node_modules folder and doing a clean install. Shouldn't be necessary, but who knows.

LOL I forgot how I solved this, or that I ever had this problem, and today it happened again. I googled and came here and was surprised

For me, I had copied a bad example .babelrc:
{
  "presets": [
    [
      "es2015",
      {
        "modules": false
      }
    ],
    "stage-2",
    "react"
  ]
}

Changing it to this got me past this error and on to the next one:
{
  "presets": [
    "es2015",
    "stage-2",
    "react"
  ]
}

I released v3.0.0 today which behaves somewhat differently – @yairEO can you let us know if you're still experiencing the issue, or if we can close this issue? Thanks

I'm stuck on what I think is the same issue. I have an identical setup that works in one project and not in another, and the error message is meaningless.
UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: [BABEL] /Users/myusername/dev/sites/mysite/frontend/js/x.js: Invalid options type for foreign

The mind-boggling part is x.js doesn't exist. Nor should it.
Here's what I've got:
// Gulp task
gulp.task('scripts', function() {
    rollup({
      entry: 'frontend/js/app.js',
      plugins: [
          nodeResolve({
          jsnext: true,
          browser: true,
        }),
        babelRollup({})
      ]
    }).then(function (bundle) {
        return bundle.write({
          format: "iife",
          dest: "dist/js/app.js",
          sourceMap: true,
        });
    });
});

app.js exists and is currently just a console.log.
// .babelrc
{
  "presets": [
    [
      "es2015",
      {
        "modules": false
      }
    ]
  ],
  "plugins": [
    "external-helpers"
  ]
}

Wiping out node_modules and reinstalling node modules doesn't help.
Any ideas?

@Rich-Harris I'm having this issue with v3.0.0.
I run rollup -c --environment entry:[a name] and bundling fails :
Here's my error output:
TypeError: [BABEL] /Users/jwainwright/code/scrolldir/src/x.js: Invalid options type for foreign
    at error (/Users/jwainwright/code/scrolldir/node_modules/rollup/dist/rollup.js:181:12)
    at Object.error$1 [as error] (/Users/jwainwright/code/scrolldir/node_modules/rollup/dist/rollup.js:9415:6)
    at /Users/jwainwright/code/scrolldir/node_modules/rollup/dist/rollup.js:9424:32
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:169:7)
    at Function.Module.runMain (module.js:607:11)
    at startup (bootstrap_node.js:158:16)
    at bootstrap_node.js:575:3

Here's the commit sha from my repository for reference
When I reverted back to version 2.6.1 I'm good to go! 👍
Let me know if I can help!

I've tried to reproduce on given commit, but without success. Closing this issue because it's old and there is high chance that it doesn't happen anymore. If it does - please create new one.

Thanks for your help with this @Andarist.


ITN: rotate stake and pre-generate funding keys

Explain your changes:

Implement stake rotations (to ensure each epoch >33% of stake changes hands)

Transactions are randomly generated between BP keys and are executed on each round
Design of stake rotations is unusual in that it requires a list of BP public keys and a list of rest servers (which have the corresponding secret keys preloaded) to be specified for experiment generation
Design above was chosen in order to make this change isolated to Orchestrator/Generator, without any modification of Mina Daemon code

(NIT) Add a simple test for keyloader

Allow funding keys to be generated from initial "seed" secret key

This finalizes workflow of funding, making it easy to use (because only one secret key needs to be provided to start the process) and super-efficient (by performing funding from 20 or more keys in parallel) at the same time

Explain how you tested your changes:

Tested by running experiments with updated generator/orchestrator on the cluster

Checklist:

[x] Dependency versions are unchanged

Notify Velocity team if dependencies must change in CI

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[x] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[x] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[x] All tests pass (CI will check this if you didn't)
[x] Serialized types are in stable-versioned modules
[x] Does this close issues? List them

Closes #13904

!ci-build-me

!ci-build-me

!approved-for-mainnet


Area2D reports TileMap in the signals, when collide with the tiles

Godot version:
Godot 3.1-a4
OS/device including version:
Linux Mint 19.1
CPU: Intel Pentium G3250 (2) @ 3.200GHz
GPU: NVIDIA GeForce GTX 750
Issue description:
Area2D, when overlapping with the TileMap, sent a signals (body_centered, body_exited, body_shape_entered, body_shape_exited). But as the 'body' argument sends a TileMap. Maybe instead it should sent StaticBody2D / KinematicBody2D depending on the settings of the TileMap?
Steps to reproduce:
Collide Area2D and Tile with CollisionShape. Area2D signals will contain TileMap.
Minimal reproduction project:
CollideArea2DAndTileMap.zip

TileMaps don't instance nodes for every single tile, so that's why your area does not report StaticBody2D (and would never report KinematicBody2D), and report TileMap instead. It's just the way it works.

But the signal handler method of body_centered and others expects PhysicsBody2D. But he gets TileMap. They are only linked by Node2D, which makes type casting strange.
I implemented a projectile based on Area2D. The projectile must ignore all bodies with OneWayCollision. I want to get a  CollisionShape2D or CollisionRegion2D with which body the collision occurred. Or somehow else get OneWayCollision. I would not like to make platforms as separate scenes.

I think this is a documentation issue here as the body parameters in Area2D signals obviously aren't always PhysicsBody2D.

I'm having a similar issue with this in 3.1 alpha 5, where I'm trying to use the body_shape_entered signal for an Area2D. Here is the signal's signature: body_shape_entered( int body_id, PhysicsBody2D body, int body_shape, int area_shape )
Here's what I get from the signal: 1268, [TileMap:1268], 68, 0
The interesting part here is the body_shape arg. In lieu of actually solving the root problem, I've got a bit of a workaround working here:
func _save_collision_data(body_id:int, body:TileMap, body_shape:int, area_shape:int) -> void:
  var tset: TileSet= body.tile_set

  var cellv: Vector2 = body.get_used_cells()[body_shape]
  var tile_id: int = body.get_cellv(cellv)
  var auto_coord: Vector2 = body.get_cell_autotile_coord(cellv.x, cellv.y)

  for shape_data in tset.tile_get_shapes(tile_id):
    if shape_data['autotile_coord'] == auto_coord:
      print(shape_data) # {autotile_coord:(3, 0), one_way:False, shape:[ConvexPolygonShape2D:1174], shape_transform:((1, 0), (0, 1), (0, 0))}

Note, the transform, and the points of the shape, are both kinda useless on their own. You can use TileMap.map_to_world() to help get global coords for the Shape2D.
This is a bit cumbersome. But, in case you want to get a Shape2D from collision data and those aren't problems for you, the above workaround could be helpful if baked into a script attached to the TileMap:
# filename: my_tile_map.gd
extends TileMap

func get_shape_data(tile_idx:int) -> Dictionary:
  var cellv := get_used_cells()[tile_idx]
  var tile_id := get_cellv(cellv)
  var auto_coord := get_cell_autotile_coord(cellv.x, cellv.y)

  for shape_data in tile_set.tile_get_shapes(tile_id):
    if shape_data['autotile_coord'] == auto_coord:
      return shape_data

Nice-to-haves would be to not have to iterate over all the shapes in the TileSet. I couldn't find a good way to get the exact index of the given tile in that shapes array.
Of course, this doesn't solve the root issue: the signal signature states it will give a PhysicsBody2D, which in the case of a TileMap it clearly doesn't.

Given a pos vector from body.get_used_cells()[body_shape], the result of body.map_to_world(cellv) does not give a coordinate that the Area2D is anywhere near. Instead, the coordinates are always at the top-left of the TileMap.

I think I found out why the coordinates are wrong. body_shape is quadrant-based! I have created an issue with my investigations on the matter: https://github.com/godotengine/godot/issues/26138

See https://github.com/godotengine/godot/pull/30043#issuecomment-505151665.
This can likely be fixed properly for 4.0, so assigning to that milestone.

Anyone struggling with this, I found a work around to do what I needed here:  https://github.com/godotengine/godot-proposals/issues/2543  Don't forget to copy your collision bits to the parent when you make it!


Roll Engine from b41870954b7d to 714df539bef9 (1 revision)

https://github.com/flutter/engine/compare/b41870954b7d...714df539bef9
2022-03-28<EMAIL_ADDRESS>Roll Skia from fae7be2a9c5b to f700cf3cf42e (1 revision) (flutter/engine#32287)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Align config.env with ENV variables

Thank you for this amazing plugin 🙏
I encountered something that I feel is a bug - config.env attributes don't behave the same as ENV variables.
Here are a few examples:

let SPLIT_OUTPUT_FILE = process.env.SPLIT_OUTPUT_FILE || config.env.outputFile || SPLIT_FILE - in this case the ENV variable name is SPLIT_OUTPUT_FILE but the one in config.env is outputFile which is odd (missing the "split" prefix).
The SPLIT_INDEX variable is a bit more buggy because of this:

if (process.env.SPLIT_INDEX1 || config.env.splitIndex) {
...
}

So using config.env.splitIndex technically means you're always doing a 1-based index (unless you pass a number and for the 0th index it'd be 0-based but for the rest it'd be 1-based) while SPLIT_INDEX env variable defaults to 0-based index.
I would assume that for every env variable VAR_NAME there would be a corresponding attribute in config.env that behaves the same but the above 2 examples don't support this idea, so I don't know if it's by design or a mistake.
Anyway, thanks for the plugin, just thought I'd share this since I haven't seen anyone mentioning it.

fixing the env name and will release a fix when I merge #194
I don't understand the problem you are describing. Of course, there might be a problem, but can you please provide which env variable inputs you are using, what you assume the plugin does, and what you assume it should do instead?
Tip: you can enable debug logs to see how the env variables are parsed https://github.com/bahmutov/cypress-split?tab=readme-ov-file#debugging

@bahmutov Apologies if I wasn't clear.
What I meant by No.2 is this -
Let's say I have this config:
export default defineConfig({
	e2e: {
		env: {
			splitIndex: process.env.MY_CI_SPLIT_INDEX,
			split: process.env.MY_CI_SPLIT,
		},
		setupNodeEvents(on, config) {
			require("cypress-split")(on, config);
			return config;
		},
	},
});

I'm using Jenkins with an in-house parallelization mechanism where it sets these env variables MY_CI_SPLIT_INDEX and MY_CI_SPLIT (I renamed them a bit for clarity) which correspond to SPLIT_INDEX and SPLIT.
Instead of mapping them to other env variables, I'm using the env config in cypress.config.ts to map them, which is pretty simple.
Now, because of these lines:
https://github.com/bahmutov/cypress-split/blob/3c8058a96a398b568784c6ef6daeb4e765842312/src/index.js#L98-L109
config.env.splitIndex would be defined (since it's in my config) it thinks it's a 1-based index and enters the if-block, however if I were to set SPLIT_INDEX through an env variable it wouldn't think it's a 1-based index but rather 0-based.
This, to me, feels like config.env.splitIndex and SPLIT_INDEX are not aligned on this behavior. I would expect both to work the same way and be 0-based since there's a special variable for 1-based (SPLIT_INDEX1).
The way to solve it would be to do this:
- if (process.env.SPLIT_INDEX1 || config.env.splitIndex) {
+ if (process.env.SPLIT_INDEX1 || config.env.splitIndex1) {

Use a different attribute in the config for 1-based index.

yeah, makes sense, will release a fix soon.


Re-Create Giphy With API

hi, @991rajat & @harshgupta20 hope you well, I completed task #1351  please reviews the code. I have added some screenshots hope you can help in the code review

Music App Files are also pushed, Check them at once, Are they needed here ?

Giphy project already exist. Replace that, Don't create a new one.
Fix the conflicts please
Lots of project are added again. Check them at once.

Hi @991rajat bro ...I need some help  I can not resolve this conflicts file when I push the code after updating Script file,
a new branch is created with same branch name and there is an another option create for new pull request. commit not added here 😟 😟

Hi @ 991rajat I little bit struggling to push the code, actually when I push the code after removing all Duplicate Code from the script file then a create a new branch the commit not added here can you help me

@WebVishal Easiest way to do this
Copy the script file from main branch of current repo,
Paste it in your branch(Replace)
Add the project and Push.

hi @991rajat  Can you review it, I Have Removed All Duplicate project before


Incorrect sender id

When using the SmartSmsSolutions class to send text messages, I noticed that the sender id I set to be used isn't used. It usually delivers the message with another sender id different from what I have specified. Could this be a result of the way the API token was created?

Sometimes, SMS providers changed the senderId if it's breaking one of their rules e.g blacklisted keyword. Have you tried any other senderId and the result is the same?

I am currently speaking with one of their customer care agents. Hopefully we can resolve the matter from their end

Sounds good

The customer care representative said that I should submit the sender Id for whitelisting. I guess that solves this issue


TemperatureSensor steps ignored

Temperature values are always rounded to 0.5 values. So a temperature of 19.8° will be 20.0° and a temperature of 19.6° will become 19.5° (Celsius units)
I'm just using:
t := accessory.NewTemperatureSensor(createInfo("temp", 1234), 0, -55, 55, 0.1) t.TempSensor.CurrentTemperature.SetValue(19.8)
The step value seems to be ignored at all. I would like to see the exact value 19.8° instead of 20.0°.
Any fix on this?

The step value seems to be ignored at all.

No. hc does not ignore the step value. The Apple Home app just ignores the exact decimal values and rounds to 0.5. There is nothing we can do, because it's only an issue in the Apple Home app.


refreh token without username and password

Hi dear
with thanks to you, I am converting this useful library to java
and now, I need to refresh the token after expiration, would you please tell me how should I do about this?
I called the "https://azwus1-client-s.gateway.messenger.live.com/v1/users/ME/endpoints" and grabbed the registrationToken from its headers, but when I call APIs with this new token it returns 401 error and seems the token is not valid,
I need to know what should I do to have a fresh and valid new token.
thank you.

All tokens invalidate after 24 hours, you need the user's credentials or their Microsoft account session to hand in order to request a new set of tokens.  Ideally you need a Microsoft login library for Java that can manage and persist that for you, though such libraries that automate the web login page don't really exist due to their fickle nature.


bazel needs to know when to ignore .DS_Store files on Mac when globbing

on Mac OS X
/Users/dmaclach/src/bazel_ext/bazel/output/bazel test src:bazel fails right now because some of my directories have .DS_Store files in them. .DS_Store files are created by the Finder when going through directories.
ERROR: /Users/dmaclach/src/bazel_ext/bazel/src/main/java/BUILD:90:12: in srcs attribute of java_library rule //src/main/java:bazel-core: file '//src/main/java:com/google/devtools/build/lib/rules/.DS_Store' is misplaced here (expected .java, .jar, .srcjar or .properties).
ERROR: /Users/dmaclach/src/bazel_ext/bazel/src/main/java/BUILD:90:12: in srcs attribute of java_library rule //src/main/java:bazel-core: '//src/main/java:com/google/devtools/build/lib/rules/.DS_Store' does not produce any java_library srcs files (expected .java, .jar, .srcjar or .properties).
ERROR: Analysis of target '//src:bazel' failed; build aborted.
INFO: Elapsed time: 0.320s

For now, you can exclude file patterns from a glob (see http://bazel.io/docs/build-encyclopedia.html#glob).

Globing files wasn't supposed to exclude dotted-files by default?

Globbing explicitly does not exclude dotted-files by default.

to me, this is working as intended. The original problem is that the BUILD files for Java source should add the .java extension to the glob patterns explicitly.


GULD P2P SALES CONTRACT INTERFACE

Objective
We need to build and deploy a simple user interface to allow the purchase of GULD using BTC via valid, legal P2P smart contracts that will be executed, signed and validated with the process we will develop.
This widget will allow 2 parties to initiate a contract, fill variables, sign and validate contract details and obtain a time sensitive address for the sales process to be fulfilled.
HTML and JS purchase contract widget.
This will obtain from buyer:

DATE 1 - Date of purchase
PARTY 1 - Seller - from the Oficial Guld Queue.
PARTY 2 - Buyer - from field GULD USER NAME
PARTY 1 Account Type - Assume individual for now
PARTY 1 Key - PGP Fingerprint
PARTY 2 Key - From Official sales channel queue
PARTY 1 COUNTRY - We'll have to collect country from both parties and neither can be in North Korea or Iran
PARTY 2 COUNTRY
DATE 2 - Day of Delivery of assets. - assume 15 minute window
QUANTITY - Cuantity of asset from Input

Order in which the data will be gathered.

Prior to initiating contract, PARTY1 and PARTY2 register addresses on guld for the two currencies.
PARTY1 signs partial variable list, leaving out PARTY2, PRICE_UNIT, PRICE_TOTAL, and LOCATION3
PARTY2 fills in the missing variables using oracle for price
PARTY2 reserves one of PARTY1's addresses for 10-20 minutes, depending on the current time.
PARTY2 sends sufficient funds to address from #3
Upon confirmed receipt of funds, PARTY1 must transfer the GOODS1 to LOCATION3. If this is a guld-ledger transaction, either party may do this.

Tasks

[ ] Design Opening User interface with Variables that buyer will fill. Filter prerequisites prior to proceeding with variable collecting.

[ ] Design Timer interface and Party 2 Address QR display screen

End of the second paragraph: "If" what?

Typo was edited. Thanks!


Application crash after suspend

How to reproduce:

Start Windows 10 mobile emulator
Deploy application to emulator
Start debug session from Visual Studio
Emulate suspend+terminate lifecycle event from Visual Studio Debugger ("Lifecycle events" -> Suspend+Terminate)
Application suspended, terminated and remains in operation system applications list as expected
Hold "Back" button to switch tasks, select our application
Application does not reload/resume, it crashed instead

So, when operating system decides to unload suspended application from memory (which we emulate by sending "suspend+terminate" lifecycle event from VS debugger), there is no way to resume. It crashes instead and must be started from OS app list or live tile.
Application crashes only when it resumed by task switcher. When application in "suspend+terminate" state is started from OS application list or live tile it starts normal.

This may be related to #457

I actually think it's an OS bug that the App remains in the task switcher after it's been terminated. I followed these steps and after 4 I turned on break on all exceptions & set VS to start debugging when app was launched then attached the debugger to the emulator. When I chose the app from the task switcher I observed the "crash" but the debugger didn't even initiate a wireup. So I don't think the app was really "launched".

Anyway, I observed in my another published app on an actual device that it can not resume some times. When I use task switcher it crashes. I think there is problem with Template 10.

Can you repro with one of the templates so we can troubleshoot?

I believe this is related to using the Factory after a resume. Please change your SHell code to look like this:
public override async Task OnInitializeAsync(IActivatedEventArgs args)
{
    // content may already be shell when resuming
    var shell = Window.Current.Content as Views.Shell;
    if (shell == null)
    {
        // setup hamburger shell
        var nav = NavigationServiceFactory(BackButton.Attach, ExistingContent.Include);
        Window.Current.Content = new Views.Shell(nav);
        await Task.CompletedTask;
    }
}

And please try with the current code base, not 1.0.8

@JerryNixon I'm able to repro this w/ Minimal at HEAD. I don't think it's a Template10 thing.


Revert "This is a working version of glusterfs with Cycle Cloud"

Reverts Azure/azurehpc#331

Closing this PR as this will be fixed by another branch I'm working on.


bug: Jan v0.3.1 can't load models

Describe the bug
I can't start any models, keep receiving a timeout error
To Reproduce
Steps to reproduce the behavior:

Go to jan.ai
Download the Jan app for Mac (M1/M2)
Install and run the app
Go to the Explore Models screen
Download any model
Go to My Models screen
Click on Start Model button
Wait a minute and the timeout error popup appear

Expected behavior
Model started successfully and be able to create a new Chat and chat with the model
Screenshots
https://github.com/janhq/jan/assets/43697014/cf2f703a-a9eb-4192-abc9-bf6c87cecfd0
Desktop (please complete the following information):

OS: MacOS Ventura 13.2.1
Version Jan v0.3.1

Additional context
Upon conducting some research, I noticed that the latest Nitro build included in Jan might not be compatible with MacOS versions lower than 14.0.

Temporary solution
Manually rebuilding Nitro from scratch and replacing the pre-installed nitro work for me

@tikikun have you taken a look at this issue?

We have come to a conclusion on this issue


Console does not recognize first key press

As the title says, I have to press the first key twice after opening the console.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1612330-console-does-not-recognize-first-key-press?utm_campaign=plugin&utm_content=tracker%2F5279&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F5279&utm_medium=issues&utm_source=github).

Bump - with #2082 merged the console key is now both the grave key and F1. So using the console via F1 avoids the dead key and as a bonus you can open and close the console with the same key :-)
The console issue was the only place (I think) where we encountered the dead key drawback and with any solutions sounding rather quirky I'm going to mark this as resolved - if anybody feels it still worth a fix eventually feel free to re-open!


Changes in v1.1.x break any project that imports v1.0.x

Hi:
I don't suppose that you could move v1.1.x to a v2 branch; any project that uses this package and wrote code as required in v1.0.x now breaks when go get -u is executed, since you've moved to the (much better) approach that you have in version 1.1.x.
Obviously, this is not a huge deal, but it would make life easier for those of us who are using your package, and it also is a more correct approach of versioning, since v1.1.x introduces breaking changes.
This is just a suggestion, of course.
Thanks again for this useful package.

Hi @tsawler
Thank you for your feedback and suggestions, and using the package!
This is a very good point. I should have included breaking changes in the change log but as I thought as the project is still quite young, it wouldn't matter so much.
For the time being I will add a chagelog in the readme, and the next update I do I will move to V2. If that's ok with you?
As I have moved the drivers to a different package, I can't forsee any breaking changes in a very long time.
Again, thank you for the feedback.

It works for me. I actually used this package for one of my Golang based Udemy courses, and I’ll have to re-record one lecture, but that’s no big deal.
Take care.
—
Trevor Sawler
On Mar 3, 2022, 3:44 PM -0400, Ainsley Clark @.***>, wrote:

Hi @tsawler
Thank you for your feedback and suggestions, and using the package!
This is a very good point. I should have included breaking changes in the change log but as I thought as the project is still quite young, it wouldn't matter so much.
For the time being I will add a chagelog in the readme, and the next update I do I will move to V2. If that's ok with you?
As I have moved the drivers to a different package, I can't forsee any breaking changes in a very long time.
Again, thank you for the feedback.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@tsawler wow that's fantastic! Can you share the course by any chance?

Sure. This is the link:
Let's build a Go version of Laravel