SEO rel="noindex" Problem

Search console has been reporting that a lot of the links on my website have the rel="noindex" tag, and is not indexing them.
Truth is, all the pages on my website are currently marked to be indexed, and there is no rel="noindex" tag on the pages.
I checked the http headers too, using this tool.
When I tried recrawling one of the problematic pages in Search Console, it still showed the issue, and it showed Referring page: my-yourls-link.com.
I checked the headers of that URL using the same tool as above, and surely the yourls link contains a X-Robots-Tag => noindex.
While it seems to make sense to have this tag on the Yourls link, I'm not sure why Google is not indexing the main URL.
I checked a Bit.ly link and ran it through the header checker tool, and they don't have any noindex tags.
Same with TinyURL. No noindex tags.
Seems like the noindex tag should be removed. None of the industry standard URL shorteners have it.
Perhaps we should undo this commit.

As I understand it, I think it's good that we have this X-Robots-Tag: noindex that tells robots to follow, but not index, short URLs
Case in point: https://www.google.com/search?q=site:bit.ly shows 78M results, but none of them are actually content from bitly, they are results from other sites.
While bitly is probably happy with this (they're basically stealing content), this would be extremely detrimental SEO-wise if you end up with duplicated content between your actual website and your URL shortener (see issue 2202 that led to the commit you're referring to)
Maybe there is something specific to your site content & short URL sharing strategy? I just dug a bit in the search console for https://blog.yourls.org/ and cannot see something as you report.
I think a better option, instead of reverting the commit, would be to add a filter to it and allow plugins to bypass or modify it

According to Google, a 301 alone is enough to transfer all link juice.
It would be awesome if you can add a setting to the plugin to remove the noindex header.
Thanks!

According to Google, a 301 alone is enough to transfer all link juice.
It would be awesome if you can add a filter to the app to remove the noindex header.
Thanks!

I too was receiving these errors for my main domain (not the yourls short domain but the domain the short urls were pointing to.... Google wasn't indexing the main urls https://github.com/YOURLS/YOURLS/discussions/2882
I removed the X-Robots-Tag header from the functions.php and soon the GSC issues went away for my main site. I still do not know why Google was not indexing my main urls (only the ones that were coming from short urls). It's as if it was 'carrying' the noindex x-robots-tag signal to my main domain.
Now im kinda go off on a bit of a tangent - Google was still 'indexing' my short urls with the noindex x-robots header tag.
I think having the 301 redirect is enough. Google will/is not 'indexing' the short url. Using the site: operator command is not a clear indication of what is actually indexed. Use GSC > Coverage > Valid to see what is actually indexed and what will appear in regular search queries.
If you site: command your short url domain and copy a short url from the results into GSC > URL Inspection you will see that it will return - URL is not on Google meaning this page is not in the index, even though it appeared via site: . So what 'index' is site:command querying? I do not know, my theory is that site: queries some "temporary state cache half way there" type of index. The results that appear in site: are in GSC > Coverage > Excluded.
I have yet to see any short url pages returned by regular search queries. Try googling content of the page, narrowing it down using quotes (“page content”) to help you find the exact match results. What I receive in the serps is the main url result, and not the short url results (that appears in site:). You can even try it with the bitly results... the bitly results do not get returned.
My guess is that Google filters out the short-url results because it hasnt made it to the index. The 301 is working as it should. Which is why it doesnt appear in Coverage > Valid. It gets added to Excluded > Page with redirect and serves the landing main result page to the user. It has understood what the url is suppose to do.
I also think we are confusing Google with the noindex x-robots-tag. Half results appear in Coverage > Excluded by 'noindex' tag and half appear in Page with redirect.
Now a question can be raised if it's ok (SEO-wise) to have these urls appear in site: and let Google do its thing by excluding them to not appear in the "actual regular search query index". Would it effect your main site that you are pointing to?

Any update on this?

I think a better option, instead of reverting the commit, would be to add a filter to it and allow plugins to bypass or modify it

Pull request welcome if anyone is interested in addressing this issue !

Hey @ozh - Not a big user of Github, so apologies if this is not the correct way to re-highlight the issue.
I have too suffered with my entire website being removed from Google. This issue has caused me headaches for the best part of a year and pretty much ALL of my search engine visibility has gone, with the exception of pages which weren't passed through this great shortner.
Bit of context here, Yourls serves a WordPress website via a WordPress plugin and basically replaces the default WordPress shorturl with the ones created by Yourls.
Both the shortener and the website reside on the same parent domain, the differences is, Yourls sits in a subfolder (https://domain.com/s/).
I have just entered into the functions.php file and changed the following from true to false:
    // Tell (Google)bots not to index this short URL, see #2202     if ( !headers_sent() ) {         header( "X-Robots-Tag: noindex", flase );     }
Is this the "fix" here. Google ought to be able to understand that it's a 301 redirect, but it seems that it inherits the NoIndex attribute and passes that along to the full URL.
It's sad :( My website once enjoyed top search results but the past year has seen that diminished and it's taken me forever to figure out why.

@alroberts Curious if this will fix the problem. Our sites have also been suffering from this issue.

People monitoring this issue : YOURLS 1.9.2 (soon) will address this issue with a filter allowing you to use a plugin and fine tune the SEO behavior you'll like. See #3517 for more info.


E2e testing "Have a Nice Day"

Bug reports here:
https://qamar24omalinevska.atlassian.net/browse/HUN-141

Wow, I like it


Clean up Scrollbar API

Over a year ago, we completely re-vamped scrollbars while avoiding making any breaking changes.
Once they reached stable, the API was further iterated on as users started adopting the new scrollbar widgets.
There have been a lot of changes made, and I think we should now tidy up the API - especially with the ability to write dart fixes, it will be much easier to clean everything up nicely.
I thought I could do this in one go (https://github.com/flutter/flutter/pull/96935), but the change grew to be pretty large, so I am going to split it up and track it here.

Further context, there is also work planned for native desktop scrollbars, so these changes will make way for that as well.
These are the API changes currently planned (I'll wrap them up nicely in a design doc as well)
RawScrollbar(
  // Add
  bool? thumbVisibility,
  // Deprecate, use thumbVisibility
  bool? isAlwaysShown,
  // Add
  bool? trackVisibility,
  // Add
  Color? trackColor,
  // Add
  Color? trackBorderColor,
);

Scrollbar(
  // Add
  bool? thumbVisibility,
  // Deprecate, use thumbVisibility or
  // ScrollbarThemeData.thumbVisibility for
  // MaterialState-based choices
  bool? isAlwaysShown,
  // Deprecate, use ScrollbarTheme.trackVisibility
  // for MaterialState-based choices
  bool? showTrackOnHover,
  // Deprecate, use ScrollbarTheme.thickness
  // for MaterialState-based choices
  double? hoverThickness,
  ...
);

ScrollbarThemeData(
  // Add
  bool? thumbVisibility,
  // Deprecate, use thumbVisibility or
  // ScrollbarThemeData.thumbVisibility for
  // MaterialState-based choices
  bool? isAlwaysShown,
  // Deprecate, use ScrollbarTheme.trackVisibility
  // for MaterialState-based choices
  bool? showTrackOnHover,
  // Deprecate, use ScrollbarTheme.thickness
  // for MaterialState-based choices
  double? hoverThickness,
  ...
);

CupertinoScrollbar(
  // Add
  bool? thumbVisibility,
  // Deprecate, use thumbVisibility
  bool isAlwaysShown,
  // Track functionality would be new here,
  // will add in a separate change to reflect
  // macOS behavior.
  ...
);

We should also double check that the introduction of trackVisibility (from an earlier PR) does not conflict with thumbVisibility... a track without a scrollbar thumb would just look bad. :)


Konga container keeps dying

docker logs    aim_konga.1.n1el61rzwkof09354slbsslc9                                                                                events.js:183                                                                                throw er; // Unhandled 'error' event                                                                                ^                                                                                Error: read ECONNRESET                                                                                at TLSWrap.onread (net.js:622:25)
db is postgress

is there another service log I can try to obtain for you ?

Please help me fix this....
Unable to connect to SSL enabled postgres database
env:
        - name: KONGA_LOG_LEVEL
          value: "debug"
        - name: NODE_ENV
          value: "production"
        - name: DB_HOST
          value: "xxx.postgres.database.azure.com"
        - name: DB_PORT
          value: "5432"
        - name: DB_USER
          value: "xxx@postgres"
        - name: DB_PASSWORD
          value: "yyy"
        - name: DB_DATABASE
          value: "konga_database"
        - name: DB_POOLSIZE
          value: "10"
        - name: DB_SSL
          value: "true"
        - name: DB_ADAPTER
          value: "postgres"
        - name: NODE_TLS_REJECT_UNAUTHORIZED
          value: '0'

And logs of konga pod after k8s deployment
Hook:api_health_checks:process() called
Hook:health_checks:process() called
Hook:start-scheduled-snapshots:process() called
Hook:upstream_health_checks:process() called
Hook:user_events_hook:process() called
User had models, so no seed needed
Start scheduled health checks for node 1
Kongnode had models, so no seed needed
Emailtransport seeds updated
Performing health check for node 1
Health check for node 1 succeeded { database: { reachable: true },
  memory:
   { workers_lua_vms:
      [ [Object],
        [Object],
        [Object],
        [Object],
        [Object],
        [Object],
        [Object],
        [Object] ],
     lua_shared_dicts:
      { kong_locks: [Object],
        kong: [Object],
        kong_process_events: [Object],
        kong_db_cache: [Object],
        kong_cluster_events: [Object],
        kong_db_cache_miss: [Object],
        prometheus_metrics: [Object],
        kong_healthchecks: [Object],
        kong_rate_limiting_counters: [Object] } },
  server:
   { connections_writing: 1,
     total_requests: 181602,
     connections_handled: 17547,
     connections_accepted: 17547,
     connections_reading: 0,
     connections_active: 2,
     connections_waiting: 1 } }
KongNode:afterUpdate:called()
KongNode:afterUpdate:health_checks true
KongNode:afterUpdate:emit health_checks.start
events.js:183
      throw er; // Unhandled 'error' event
      ^

Error: read ECONNRESET
    at TLSWrap.onread (net.js:622:25)

I believe https://github.com/pantsel/konga/issues/645 is related to this issue


remove gui_floorplan bogus [ERROR GRT-0010] Instance ctrl.state.out\[0\]$_DFF_P_ is not placed.

Description
$ make floorplan gui_floorplan
QSocketNotifier: Can only be used with threads started with QThread
OpenROAD v2.0-14802-gc7e334587
Features included (+) or not (-): +Charts +GPU +GUI +Python
This program is licensed under the BSD-3 license. See the LICENSE file for details.
Components of this program may be licensed under more restrictive licenses which must be honored.
[ERROR GRT-0010] Instance ctrl.state.out\[0\]$_DFF_P_ is not placed.
[WARNING GUI-0076] QObject::startTimer: Timers cannot be started from another thread
[WARNING GUI-0066] Heat map "Estimated Congestion (RUDY)" has not been populated with data.

Suggested Solution
Remove bogus error.
Additional Context
No response

Presumably you have the estimated congestion heatmap on.  There is no way to display it with unplaced instances.  I don't see this as a bogus error - just turn it off.

This happens because OpenROAD remembers settings across all runs...
Not a truly great userexperience, but there are certainly bigger fish to fry.

We could not remember the heatmaps but that also has its downsides.

Yes... I think weit

I didnt explicitly turn it on. Normally in a GUI, unavailable options are ghosted silently.

You did in a previous run, presumably when it was available.

And then I restarted the GUI, loaded another design, and now it is not.
My expectation is silently ghosting unavailable options, that is not what OpenROAD does here.


Teams Message Extension Triggered Flows Are Only Available to Flow Creator

When following the guidance provided in Trigger a cloud flow from any message in Microsoft Teams - flows created in this way appear to only be available to the creator of the flow. The flow is not available for any other Teams/channel members.
Is there a way to modify this flow template so that it becomes visible for all/any Team/channel members to run?
If this is by design, please add it to the known issues and limitations.

Made the indicated edits and created a PR: https://github.com/MicrosoftDocs/power-automate-docs/pull/773


python310Packages.pinocchio: 2.6.17 -> 2.6.18

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 229270 run on aarch64-darwin 1

8 packages built:

crocoddyl
pinocchio
python310Packages.crocoddyl
python310Packages.example-robot-data
python310Packages.pinocchio
python311Packages.crocoddyl
python311Packages.example-robot-data
python311Packages.pinocchio


Handle pagination of GitHub repo API

https://github.com/EmbarkStudios/opensource-website/blob/0e19bc819011a9fd6d8fb810551cfe964f9d20fb/script.js#L115-L117
Here we make a call to the GitHub API to get the first 100 repos from our org. At time of writing we have 164 public repos, so this query does not get them all, so we miss some data. Handling the API pagination resolves this problem.
This could also be a nice opportunity to break the mounted function of the Vue app into multiple functions, it is a little large at present.

This is supported in octokit out of the box. https://octokit.github.io/rest.js/v18#pagination
const issues = octokit.iterator(octokit.repos.listForOrg, {
    org: "EmbarkStudios",
})

for await (const issue of issues) {
  // do whatever you want with each issue, break out of the loop, etc.
}

This is supported in octokit out of the box. https://octokit.github.io/rest.js/v18#pagination
const issues = octokit.iterator(octokit.repos.listForOrg, {
    org: "EmbarkStudios",
})

for await (const issue of issues) {
  // do whatever you want with each issue, break out of the loop, etc.
}


[Discussion] Shaders: Blur shader

Discussion for http://godotrecipes.com/shaders/blur/

Have you a project that use this shader please ? I have trouble to make it working.

No, but in the greyscale shader recipe there's an example of how you might use it:
http://godot_recipes.com/shaders/greyscale/


Tracking issue for SupportedFeature breaking change

What happened:
We introduced a breaking change in https://github.com/kubernetes-sigs/gateway-api/pull/3200/.  This broke existing users with the exiting gateway classes with the previous supportedFeatures field (list of strings)
This issue was first reported on istio repo - https://github.com/istio/istio/issues/53846

PR to fix it - https://github.com/kubernetes-sigs/gateway-api/pull/3454


fix kawa is not working on Catalina

Hi, I tried kawa today and found it is not working on Catalina. (10.15.4)
So I tried to find another workaround.
When changing it between jp <-> zhTW, this steps works

switch to nonCJK and wait 0.05s
switch to nonCJK and wait 0.05s again
switch to zhTW

PS: I didn't test it on Korean input. Hope it works, too.

Sorry, I found it's not always working.


Incorrect tex coords

Tex coords are never align. Even though I copied the rmesh parser in scpcb.
Converted to rust. How would we use two sets of uvs in a single mesh?
for k in 0..2 {
    let u = cursor.read_f32::<LittleEndian>()?;
    let v = cursor.read_f32::<LittleEndian>()?;
}

The textures are sorted in uv layers (Ex. lightmap.png next whitewall.jpg). I do believe the same sorting is done with the uvs/texture coords.
An example of the tex coords potential rework:
let mut lm_uv = [0.0; 2];
cursor.read_f32_into::<LittleEndian>(&mut lm_uv);

let mut tex_uv = [0.0; 2];
cursor.read_f32_into::<LittleEndian>(&mut tex_uv);


647 subject added entry--named event

https://github.com/uwlib-cams/MARC2RDA/blob/main/Working Documents/6XX.csv

@CECSpecialistI @GordonDunsire
I was assigned field 647 and 648 for mapping, but I believe they may fall under Gordon's document. Should I leave these to you Gordon?

Yeah @cspayne I think you should hold off on these until Gordon's document is complete. It's likely that he's going to hand it off to you and Penny soon.

Hi @pennylenger
I think $x, $y, and $z mappings still need to be added to this google sheet. Are they treated the same as in field 650?

Also, why are $0 and $1 not used as the value for "has subject" in this field?

Hi Cypress, I asked a question about this:
If $0 references the complete heading as an event which is not an RDA entity, why can’t we use the converted URI as the object of the triple? If there is a $1, can we use it? And should we mint a skos:concept for the complete heading for 647?
Example 66
647 7 $a World War $d (1939-1945) $2 fast $0 (OCoLC)fst01180924
rdawo:P10322 . // has subject timespan; ignore subfield $0 which references the complete heading as an event (not an RDA entity)
rdato:P70047 . // has authorized access point for timespan
rdand:P80068 “1939-1945” . // has nomen string
rdano:P80069 http://id.loc.gov/vocabulary/subjectSchemes/fast . // has scheme of nomen
Adam: I don't think you can say that there is a FAST authorized access point for timespan that is derived from the $d of a 647 field.  The authorized access point in 647 is for an event, not a timespan.
To say that there is an authorized access point from FAST with nomen string 1939-1945 there must be a FAST authority for that timespan by itself, not as part of an access point for an event.
Gordon: OK, I have changed example 66, 647 output to be just a subject heading from FAST; that is, as a skos:Concept. This is the approach we can take if we decide not to normalize the subfield $0 URI and mint our own. Note that example 66 also includes the corresponding 648 field.

Hi @pennylenger I think $x, $y, and $z mappings still need to be added to this google sheet. Are they treated the same as in field 650?

I will add this. Thank you.

Hi Cypress, I asked a question about this: If $0 references the complete heading as an event which is not an RDA entity, why can’t we use the converted URI as the object of the triple? If there is a $1, can we use it? And should we mint a skos:concept for the complete heading for 647? Example 66 647 7 $a World War $d (1939-1945) $2 fast $0 (OCoLC)fst01180924 rdawo:P10322 . // has subject timespan; ignore subfield $0 which references the complete heading as an event (not an RDA entity) rdato:P70047 . // has authorized access point for timespan rdand:P80068 “1939-1945” . // has nomen string rdano:P80069 http://id.loc.gov/vocabulary/subjectSchemes/fast . // has scheme of nomen
Adam: I don't think you can say that there is a FAST authorized access point for timespan that is derived from the $d of a 647 field. The authorized access point in 647 is for an event, not a timespan. To say that there is an authorized access point from FAST with nomen string 1939-1945 there must be a FAST authority for that timespan by itself, not as part of an access point for an event.
Gordon: OK, I have changed example 66, 647 output to be just a subject heading from FAST; that is, as a skos:Concept. This is the approach we can take if we decide not to normalize the subfield $0 URI and mint our own. Note that example 66 also includes the corresponding 648 field.

Hi Penny, thank you for this. I think what this means is that we can't use FAST URIs for subfield $d in 647 as a timespan. However, since the field as a whole is being mapped to a skos:concept, I believe we can use $0 or $1 for that value, as [work] has subject [value of $0 or $1] like in field 650.

Hi Cypress, I asked a question about this: If $0 references the complete heading as an event which is not an RDA entity, why can’t we use the converted URI as the object of the triple? If there is a $1, can we use it? And should we mint a skos:concept for the complete heading for 647? Example 66 647 7 $a World War $d (1939-1945) $2 fast $0 (OCoLC)fst01180924 rdawo:P10322 . // has subject timespan; ignore subfield $0 which references the complete heading as an event (not an RDA entity) rdato:P70047 . // has authorized access point for timespan rdand:P80068 “1939-1945” . // has nomen string rdano:P80069 http://id.loc.gov/vocabulary/subjectSchemes/fast . // has scheme of nomen
Adam: I don't think you can say that there is a FAST authorized access point for timespan that is derived from the $d of a 647 field. The authorized access point in 647 is for an event, not a timespan. To say that there is an authorized access point from FAST with nomen string 1939-1945 there must be a FAST authority for that timespan by itself, not as part of an access point for an event.
Gordon: OK, I have changed example 66, 647 output to be just a subject heading from FAST; that is, as a skos:Concept. This is the approach we can take if we decide not to normalize the subfield $0 URI and mint our own. Note that example 66 also includes the corresponding 648 field.

Hi Penny, thank you for this. I think what this means is that we can't use FAST URIs for subfield $d in 647 as a timespan. However, since the field as a whole is being mapped to a skos:concept, I believe we can use $0 or $1 for that value, as [work] has subject [value of $0 or $1] like in field 650.

Okay, I'll wait a bit to see if there are any other changes needed in 6XX, then I'll make all the modifications together in Google Sheet. I hope this won't affect your coding.

Sounds good! No, there's no hold up, I can adjust the code as needed!

@cspayne added lines for $x$y$z and fast. Please review


getMessages() marks all messages as read.

Hi
getMessages() retrieves all the messages and marks them as read.
So on the first run it will return the message as unread before marking it as read.
So while I load this page which uses getMessages() I can see the messages been marked as read one by one in outlooks web app.

The issue is the "imap_fetchbody" call in the "imapFetchbody" function in file "IncomingMessage.php", around line 506.  According to the docs on php.net, FT_PEEK should be added as an option on the call in order to preserve the read status when fetching the message body.  If FT_PEEK is not used, then imap_fetchbody will change the read status to SEEN.
For example, if I modify the original code to this:
		return imap_fetchbody($this->imapStream, $this->id, $section, FT_PEEK);
Then, the issue disappears :)

Thank you. I will add this as well as a comment so other devs know

Thank you very much :) Great response. This library makes life so much easier :)

Your welcome! I have just commited the update. Let me know if you have any
other problems :)

Cant try cuz of #163 :(

Yes, I am working on this as we speak. I plan to have this fixed by today

Yep it works :)

:)


using post_install to mount a EBS volume question

I'm trying mount a EBS volume by volume name like so...
mount_data.sh contents
#!/bin/bash

. /etc/cfncluster/cfnconfig

mkdir /data

if [ "$cfn_node_type" == "MasterServer" ]; then
/usr/local/sbin/attachVolume.py $1
mount /dev/disk/by-ebs-volumeid/$1 /data
exportfs -o rw,no_root_squash '*':/data
fi

if [ "$cfn_node_type" == "ComputeFleet" ]; then
mount $cfn_master:/data /data
fi

cfncluster config file
post_install = http://mg-post-install-scripts.s3.amazonaws.com/mount_data.sh
post_install_args = vol-00ddaf8d8e0db149f
s3_read_resource = *

Master node boots and creates the directory, but then I get the following error in cfn-inig.log...
Traceback (most recent call last):
  File "/usr/local/sbin/attachVolume.py", line 36, in <module>
    conn.attach_volume(volumeId,instanceId,dev)
  File "/usr/local/lib/python2.7/dist-packages/boto/ec2/connection.py", line 2377, in attach_volume
    return self.get_status('AttachVolume', params, verb='POST')
  File "/usr/local/lib/python2.7/dist-packages/boto/connection.py", line 1227, in get_status
    raise self.ResponseError(response.status, response.reason, body)
boto.exception.EC2ResponseError: EC2ResponseError: 400 Bad Request
<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error>InvalidParameterValue<Message>Value (http://mg-post-install-scripts.s3.amazonaws.com/mount_data.sh) for parameter volume is invalid. Expected: 'vol-...'.</Message></Error></Errors><RequestID>c80433cf-b194-44c4-af3d-2f90d989a5d7</RequestID></Response>
mount.nfs: Failed to resolve server /dev/disk/by-ebs-volumeid/http: Name or service not known

Anyone have an idea what i'm missing? I've tried using http, https, and the s3 url form and they all give this error.
Thanks

I just realized this is a duplicate of #139

Adding some details...  I'm using cfncluster version 1.3.1 and python3 (3.5.2).  After reading #139, I switched my mount_data.sh script to use $2.  This allowed me to get past the above error, but subsequently I now am getting this...
2017-03-03 16:50:24,390 [DEBUG] Command runpostinstall output: mount: special device /dev/disk/by-ebs-volumeid/vol-00dddf8f8e0fb149c does not exist
However, running this command after the master node is up shows the volume is attached...
Traceback (most recent call last):
  File "/usr/local/sbin/attachVolume.py", line 36, in <module>
    conn.attach_volume(volumeId,instanceId,dev)
  File "/usr/local/lib/python2.7/dist-packages/boto/ec2/connection.py", line 2377, in attach_volume
    return self.get_status('AttachVolume', params, verb='POST')
  File "/usr/local/lib/python2.7/dist-packages/boto/connection.py", line 1227, in get_status
    raise self.ResponseError(response.status, response.reason, body)
boto.exception.EC2ResponseError: EC2ResponseError: 400 Bad Request
<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error>VolumeInUse<Message>vol-00dddf8f8e0fb149c is already attached to an instance</Message></Error></Errors><RequestID>da9ddfe2-74fb-4762-9204-6df429c429bb</RequestID></Response>

and mounting it with...
sudo mount /dev/disk/by-ebs-volumeid/vol-00dddf8f8e0fb149c /data
works fine as well.
Anyone have any idea why it's failing as a post_install action?
Thanks.

OK - workaround!  I thought this seemed like possibly a timing issue, so I changed my startup script to include a sleep statement...
#!/bin/bash

. /etc/cfncluster/cfnconfig

if [ "$cfn_node_type" == "MasterServer" ]; then
/usr/local/sbin/attachVolume.py $2
sleep 20
mount /dev/disk/by-ebs-volumeid/$2 /data
exportfs -o rw,no_root_squash '*':/data
fi

if [ "$cfn_node_type" == "ComputeFleet" ]; then
mount $cfn_master:/data /data
fi

This worked perfectly, in case it helps anyone else.
Cheers.

Why can't you use http://cfncluster.readthedocs.io/en/latest/configuration.html#ebs ?

@mohanasudhan i'm not sure i understand - I'm already using that configuration for the shared ebs volume. This issue relates to adding a second ebs volume (domain specific data needed on all nodes).


fix: add missing account/regions to regionMapping

Adding missing accounts/regions to the regionsMapping as of 21.02.2023 according to https://docs.snowflake.com/en/user-guide/admin-account-identifier
References

similar as this contribution: https://github.com/Snowflake-Labs/terraform-provider-snowflake/pull/1430

@jglapa thank you for your contribution!


support upsert for ents

maybe something like this
CreateFooAction.create(vc, {}).saveUpsertX(options)

provide options

do nothing
on conflict 1 or more fields, update with the following fields

we currently support for edges by default but not ents

beta API where update API can change


The plug-in archive includes unnecessary files

Describe the bug
When downloading and installing the archive from AssetLib, the installer warns about there being conflicts.  In particular, the addon installs files into the project root such as:

.gitattributes
.github/
.gitiignore
CHANGELOG.md
LICENSE
README.md
docs/
icon.svg
project.godot

Expected behavior
The only contents that is installed should be addons/orchestrator/*
Actual behavior
Installs additional files in the project root and other folders.
How to Reproduce?
Steps to reproduce:

Create a new project.
Install plug-in from the AssetLib
See the "Contents of asset "Orchestrator" - X files(s) conflict with your project.

Godot full version
4.1.1.stable
Orchestrator version
1.0.2
Additional information
No response

This is now fixed using a Godot Asset Library custom provider to fetch the pre-built archives from our release artifacts.


Ability to Disable Background

Is it possible to remove the background altogether for those of us who want to keep the look and feel of our theme?

Oh all I'm really hoping for is an option to disable the images and just let the regular background from obsidian show.

Basically I use an all black theme and I would like it to use the black background from the theme as opposed to an image.

This is now supported in version 1.5.0 (just released). :)


Adding analysis of entitlements file and embedded frameworks

This pull request is to include a couple more features to the gem to analyze the contents of:

the entitlements file (if any)
the frameworks located under the Frameworks folder (if any)

There's also a slight reformatting of the files to please Rubocop.

Thanks for the PR @guillemm !
@godrei @trapacska  can you please have a look? ;)

Hi @viktorbenei,
Thanks for the fast reaction.
@godrei, @trapacska: I'm still working on adding some extra features by the way, for app extensions and the watch extension

Hi @guillemm ,
sorry for my late response, for first thanks for the PR!
We added tests (rubocop & rspec) to this repo, to allow contributors to safety contribute.
I would ask you to rebase your changes onto current master. You can run the repo test locally by calling bitrise run ci. Please fix the rubocop issues (if any) and write some test, which ensures and documents your changes.
Thanks again!

Closing due to inactivity - @guillemm feel free to update the PR as mentioned by @godrei and open a new PR, and sorry for the inconvenience


Using environmentViewModel(_ viewModel) Causes App To Crash

When using the environmentViewModel(_ viewModel: KMMViewModel) function, the app crashes:
    ContentView()
        .environmentViewModel(viewModel)

Interesting, using the alternative environmentViewModel(_ projectedValue: ObservableViewModel<KMMViewModel>.Projection) works:
    ContentView()
        .environmentViewModel(_viewModel.projectedValue)

Great library by the way!

Thanks! At the moment this is expected behaviour.
The summary is that Kotlin ViewModels can only be wrapped once. By using the projectedValue the wrapping is skipped, allowing you to forward an already wrapped ViewModel.
For more details see #11.
P.S. the following should also work (it's a little shorter):
.environmentViewModel($viewModel)


Pass down jest config to preprocess script

The use-case here is that if we want to do caching inside of the
preprocess script, then we want to include the jest configuration to
create a cache-key.

Thanks, it makes sense.


Memory leak with large pointclouds

Hi,
I'm trying to test out the capabilities of Zenoh in handling large pointclouds and it seems like I'm encountering a memory leak when testing with both synthetic data and livestreamed data from one of our sensors. It seems if the bandwidth exceeds around 16 MB/s the memory used by the node that is publishing the data will slowly creep up until the node is killed by the OOM Killer. This is on Ubuntu Noble with ROS Rolling built from source and rmw_zenoh using the yadu/events branch rebased onto rolling. I have verified that the memory usage is stable over the same time period while using rmw_cyclonedds_cpp
Here is the code I'm using for the synthetic data: https://github.com/AlexDayCRL/ros2-message-benchmark/blob/master/src/talker.cpp
And this is the command I'm using to run the node: ./talker 100000 and you can bump that up to ./talker 1000000 to make the OOM Killer kill the node sooner.

It seems like the RMW is keeping a copy of every message that's getting published. Running ./talker 500 has a cumulative bandwidth of about 80 KB/s * 3 or 240 KB/s. When logging the total memory of the program using this command while true; do  cat /proc/$pid/smaps | grep -i pss |  awk '{Total+=$2} END {print systime() " " Total/1024/1024" GB"}' >> $pid.mem_usage && sleep 1; done the slope of the accumulation is about 220 KB/s.

After instrumenting the zenoh rmw_publish function it seems that the free_msg_bytes scope exit lambda is not actually deallocating the memory.

Hi @AlexDayCRL,
Thanks for investigating this problem and identifying the fix. I've merged #142.


SC-383: Add dependencies

This PR installs the dependencies found missing when manually installing R packages on an instance rebuilt from tag v2.1.3.

This branch is not needed anymore.


Is Linux not supported yet... ?

Based on that one red-colored report there, it seems to say such, though I haven't truly tried any RPC-compliant software yet. I'm on ArmCord.

You shouldn't be using the Vencord plugin, arRPC is built into Armcord and you should get support in the Armcord discord instead.


Cannot pass in pre-populated model

Creating a post with the my new tagging input works fine but when passing in a pre-populated $scope.model, like when updating a post, the tag input shows the comma-separated tag correctly. However when you click to add more tags, the pre-set tags do not appear in the "selected items" modal list. I'm using sample hard-coded data to make sure the data is consistent but still getting same result. using latest build
UPDATE I noticed that after selecting tags, the tag object from component has an added $$hashKey parameter that I am not saving or passing back in. could this be the reason the component is not picking up my preset tags

// works fine when creating posts
$scope.post.tags = [];

// after tags are selected using the matches from callbackMethod(query),
// the new model looks like this now. perfect! This gets saved to mongo via api and
// the new tags in the 'selected items' modal list show correctly too
$scope.post.tags = [{
    //$$hashKey: "123", im not saving this though??
    id: "126",
    name: "seagate 40726",
    user_id: "1"
},{
    //$$hashKey: "124", im not saving this though??
    id: "125",
    name: "seagate a78",
    user_id: "2"
}];

// when updating the post, passing back in the same data without $$hashKey
// does not display the tags in the 'selected items' modal list, but IT DOES show the
// csv value in the directive form input correctly
$scope.post.tags = [{
    id: "126",
    name: "seagate 40726",
    user_id: "1"
},{
    id: "125",
    name: "seagate a78",
    user_id: "2"
}];

Hi,
I'll have a look at the issue this week and come back to you. I never tested it with a pre populated model.
Thanks for finding the issue.
Regards,
Guy

Awesome thank you for this component. There is nothing else out there that does the job like this one for the ionic platform

Hi,
I finally had the time to work on this issue. Can you please have a look at the model-to-item-method documentation and use it in your app and test it with the latest master changes? Can you also provide feedback if it worked then I can close the issue.
Thanks and regards,
Guy

Sorry for the delay, been in a troublesome sprint this week. I will try it out tonight. Thank you

Hi,
any news on this?
Thanks and regards,
Guy

It works fine sir. Thanks you
On Sun, Jun 14, 2015 at 10:39 AM, Guy Brand<EMAIL_ADDRESS>wrote:

Hi,
any news on this?
Thanks and regards,
Guy
—
Reply to this email directly or view it on GitHub
https://github.com/guylabs/ion-autocomplete/issues/25#issuecomment-111841693
.


Pydantic improvements

Description:

TLDR: All classes in /chatsky/pipeline/ are rewritten in Pydantic, some changes to class hierarchy and the classes themselves. Changed tutorials with regards to new class signatures.
Classes PipelineComponent, Pipeline and ComponentExtraHandler are now subclasses of Pydantic's BaseModel, massively reducing code bloat in their initialization and that of their children (such as Service).
Also, classes Service, ServiceGroup and Actor are now subclasses of PipelineComponent. No functionality is removed in ServiceGroup. All tutorials and tests pass like before, with a few changes.
Reasoning for changing class hierarchy: Before this, an instance of Actor would be called from within a Service with a special flag, which seemed like a workaround, and now it can be called directly as an instance of PipelineComponent, instead of heavily relying on the Service class. You could say that this slightly reduces the code's complexity. In fact, it also binds Actor to PipelineComponent, instead of it being independent, making code look more cohesive.
TypeBuilders have been removed, because Pydantic can already deal with them effectively, giving type hints for IDE like before. Different input types are still handled like before, except nested Service declaration is removed. (Service class doesn't accept Service as it's handler anymore) Same with nested ComponentExtraHandlers.
For some reason Extra Handlers in Services would work even if the Service itself was turned off via start_condition. That was a bug. Now this condition is checked in PipelineComponent instead. I assume Actor must always have it as True.

Checklist

[x] Removed from_script() and other redundant methods.
[x] Changed components into pre-services and post-services throughout tutorials. (at Pipeline initialization)
[x] Got tests to pass.
[x] I have performed a self-review of the changes
[x] Updated Pipeline's API and tutorials

To Consider

Add more tests if necessary
Update the remaining API reference / tutorials / guides
Search for more references to changed entities in the codebase

'inherited-members' in autodoc_default_options allows all classes to be inherited, except those explicitly defined as it's arguments. Which is the exact opposite of what I need. If I could just inherit docstrings from PipelineComponent, there'd be no problem.
Basically, I don't see any good solution for this using this method. I remind, 'handler' from Service and 'components' from ServiceGroup are undocumented in the relevant API, but they are in the constructor parameters, which are right next to that in the API reference. I could add docs for them, but then they will be duplicate, two docs for the same field on the same page. Alternatively, I could remove constructor parameters and type all those parameters in the same file, essentially duplicating the docs. I'll have to let it hang for now.


pull request for e2e test at 01/11/2017 06:45:12

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[BUG] JSON parse error in Prompt Values when used in LLMChain

Describe the bug
I am using a LLMChain like the Prompt Chaining marketplace template. For the first prompt, I am asking GPT3 to return a JSON object in the response. I am passing the Output Prediction as a Prompt Value for the second prompt to use as a variable in the input text. When I do that, it returns a JSON parse error trying to parse the Prompt Values of the second prompt.
To Reproduce
Steps to reproduce the behavior:

Start with the Prompt Chaining template.
Add Open API key to Model inputs
Change the first prompt Template to this "You are an AI who performs one task based on the following objective: {objective}.
Respond with how you would complete this task as a JSON object with your answer as an "answer" key:"
Change the second prompt Prompt Values to this so it will populate the result key with the output of the first:
{
"objective": "{{question}}",
"result": "{{llmChain_2.data.instance}}"
}
Run the chat and ask it any question: What is a bug?
It will respond with a syntax error like this - SyntaxError: Unexpected token A in JSON at position 49

Expected behavior
I expect to use the first output as a string to input in the second prompt. The only way to do this is to add it as a Prompt Value.
Setup

Installation docker
Flowise Version 1.2.12
OS: macOS
Browser Chrome

hey @kevjett do you mind to export the flow?
This is likely due to incorrect format of JSON response

{{llmChain_2.data.instance}}, this was not working for me either.
I turned it to {{llmChain_0.data.instance}} and worked.

Where can I find the debug info?

5. What is a bug

I just tried it there it was because how you asked the chain to return as JSON and thats why its doesn't parse correctly.
Instead of this:
You are an AI who performs one task based on the following objective: {objective}. Respond with how you would complete this task in a JSON object with your answer as a "answer" key:
I'd remove the JSON part like this:
You are an AI who performs one task based on the following objective: {objective}. Respond with how you would complete this task:
and this works for me

Closing for now, feel free to reopen if issue persists

Using this in prompt template
Output your script in this JSON format:
{
"greeting": "Hello {name}, how are you ?"
}
if i simply write a name instead of {name} it works , but doesnt work this way


Custom priority screen: UI issue.

Custom priority screen UI is completely messed up.

Still having the same issue on android device one plus 9R
Tested on Keeper app v 1.1.11(296)

Duplicate.


KAFKA-10100; LiveLeaders field in LeaderAndIsrRequest is not used anymore

We have noticed that the LiveLeaders field in the LeaderAndIsrRequest is not used anywhere but still populated by the controller.
It seems that that field was introduced in AK 0.8.0 and was supposed to be removed in AK 0.8.1: https://github.com/apache/kafka/blob/0.8.0/core/src/main/scala/kafka/cluster/Partition.scala#L194. It has not been used since then.
This PR proposes to simply stop populating the field for any version > 0. It avoids to compute the live leaders set and also reduces the size of the request on the wire.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

If it's a worthwhile optimization, I'd suggest we do a short KIP to drop this field.

Won't proceed with this one.


AttributeError: 'dict' object has no attribute 'split'

There is either an error in def reset(...) or in def run_round(...).
In def run_round(...) state = self.env.reset() is getting assigned a tuple of (obs, {}) from def reset(...).
However, def build_state_msg(..) expects state to be a dict whose key must be a str in order to be able to call split(...).
Possible fixes

Only return obs in def reset(...)
Or state, _ = self.env.reset() in def run_round(...)

Thanks for the fix, it is indeed a missed usage of env that was forgotten when upgrading to gymnasium.


Future recruitment info when applications are closed

When applications are closed and Join Us button is disabled, we should show information on when future recruitment is happening. It would be good have that information show up in the first section, alongside the club description so people can't miss it.

Here is content idea! we can use the same format/wording.
This is a scholarship company that I'm currently working at and they only accept applications one a year.

That looks like a big too big/too wordy for our needs - I think what @srijonsaha has in mind is replacing the "Fall 2020 applications are now open!" in the example with something like "We are not currently accepting new applications, but keep an eye on this page for updates!"

It would be a simple v-else element with the alternative text here

Agree! @bobheadxi maybe also mention the next recruitment cycle month.
@ubclaunchpad/design
@ubclaunchpad/strategy


https://github.com/dotnet/core/blob/main/Documentation/core-repos.md does not reference Blazor at all!

URL(s)
Try searching for Blazor on this page https://github.com/dotnet/core/blob/main/Documentation/core-repos.md
So either Microsoft is abandoning this technology, or it is not getting any attention.
Either case is a problem.
HOW DO WE REPORT BLAZOR WASM ISSUES?
Description
Need to report an issue on Blazor wasm and not finding any guidance!

IIUC, you can search blazor wasm issues in https://github.com/dotnet/aspnetcore/issues?q=is%3Aopen+is%3Aissue+blazor+wasm, if your issue is not there, file a new one.
Tagging @danroth27 in case we need to improve guidance to the aspnetcore repo for Blazor users.

Thank you for the reference link.


Add support for math using softfp library.

Some math functions from libm complain about __errno() - added one.
Add magic incantation to the linked libs so it does not complain about missing symbols (yes list -lgcc twice)
Add new OPTFLAGS variable so user Makefiles can overwrite the optimization settings - useful for debugging
Note: removed /usr/include/newlib include path - I venture to guess most users would have compilers installed somewhere else, who knows whats in that folder and how compatible it is. Things seem to compile fine w/o it.

Looks like the default riscv compiler is missing the math lib. Will try another time.


Update Win32 UnRTF binary from v0.19.3 to v0.21.10

Is your feature request related to a problem? Please describe.
Win32 binary included with this module is currently at v0.19.3, (found in ./src/lib/win32/unrtf-0.19.3).
The latest at time of writing is v0.21.10 and provides a large amount of fixes and new features.
Changelog from v0.19.3 to v0.21.10 is as follows:
0.19.4
      - added unicode support
0.19.5
      - removed defective PS support and non-free text files
	more unicode support
	improved symbol font support - no longer puts entities in latex output
	Bug#266020 concerning double slashes fixed
	Bug#269054 concerning Doctype fixed
	Bug#287038 security breach fixed
		(thanks to Joey Hess<EMAIL_ADDRESS>
0.19.6
      - fix some latex problems
0.19.7
      - updated FSF address
0.19.8
      - minor fixes
0.19.9
      - included verbose mode

0.20.0
      - new build system by Claudio Fontana<EMAIL_ADDRESS>	fixed creation date spelling and added support for accented characters
	in titles from Laurent Monin
0.20.1
      - minor fix in convert.c for Solaris System
0.20.2
      - minor fix to unterminated comment output, added attr_get_param()
0.20.3
      - Greek font support added, fix to UTF character processing
0.20.4
      - nopict mode bug fixes
0.20.5
      - added --noremap option, some html entity corrections, updated to GPL v3

0.21.3
      -
      - added '--quiet' flag which suppresses leading comments in output
      - default directory for config files is now /usr/local/share/unrtf
	and this can be changed when configure is run at compilation time
      - subdirs in config directory eliminated making it easier for a user
	to supply their own in a single directory specified with -P
      - code for two hex characters introduced in 0.21.2 completely replaced
	by more generalised string handling.
      - major improvements to codepage handling
      - major improvements in unicode handling
      - latex config file improved.  Some Greek characters output properly.
      - troff_mm config file improved such that this option is now useful
0.21.2
      - added feof() calls to fgets() and fgetchar() instances so end-of
        file is correctly determined under AIX
      - supplemented code to handle special characters specified with
        two hex characters (e.g. \'81\'83) as output by some RTF
	writers.  This code is experimental, and uses the SHIFT_JIS
	codepage for conversion.
      - definitions in html.config changed to ensure values of markup variables
        are enclosed in double quotes, e.g. size="3" instead of size=3.  This
	is a first step towards supporting production of XHTML.
0.21.1
      - fixed strings in unicode_to_string() (unicode.c) to be null
	terminated instead of newline terminated.  This prevents spurious
	newline output after characters in Symbol font.  It also overcomes a
	fault whereby characters in the symbol font were being output as
	unicode instead of the desired entities defined in the output
	specification.
      - suppressed output of <font face="Symbol"> as this is wrong if
	characters are changed to unicode or entities
      - changed path set with -P to be directory containing the output
	charmaps specifications, and changed the default path to
	/usr/local/lib/unrtf for the same reason.  This makes it possible
	to set a different default path, useful for example if one cannot
	install files in /usr/local/lib.
      - dropped "outputs" and "charmaps" sub-directories in the configuration
        directory.  Output configuration files are now named "html.conf",
	"text.conf" etc. and the symbol font charmap file is "SYMBOL.charmap".
      - charmap specifications now sought in the search path
      - compensate for RTF with unicodes specified as negative numbers,
	possibly due to overflow on a 16bit machine?
      - changed processing of --html (etc.) args so that "-t html" and
	"--html" are equivalent, i.e. both subject to search path set with
	"-P"
0.21.3:
      - major changes to code page support and UTF handling
      - improved LaTeX output
      - /usr/local/lib no longer hard wired - set by configure
0.21.4:
      - ignore embedded picture which cannot be rendered
      - allow unnested bold/italic to be interpreted as expected.  Such input
      	may be outside the RTF spec, but can be created by TextEdit.  The
	change has been limited to the bold command (cmd_b in convert.c)
	on an experimental basis.  If no bugs appear it could be more generally
	applied.
0.21.5:
      - improved code for the unnested case and extended to more RTF commands
0.21.6:
      - improved man page
      - improved USAGE string
      - fix to attr.c for clang compilation
0.21.7:
      - improved code for creation of image files when RTF files containing
      	images processed
      - prevent segmentation violations with RTF input containing corrupt
        \info content
0.21.8:
      - Changed bug reporting in unrtf.1
      - Test file for newly supported EMF image type.
      - Fixed all -Wall compilation warning
      - Bogus test in op_translate_buffer() caused error messages and data
		truncation
      - cmd_maybe_ignore(): test next command presence in the cmd hashes
		instead of listing locally the commands that should be processed
      - Fix unrtf looping when closing any underlining except the basic (ul)
		one
      - Open Picture files in wb mode instead of w for Windows portability.
		Fixes bug #21274
      - html output doctype value needs to be quoted
      - Skip binary data after \bin command
      - Simplified shared string storage in hash.c and word.c: suppressed
		the "index" value and replaced it by string address. Simpler
		and faster. Other changes are making shared string refs const
      - Better processing of \pict including addition of EMF type.
      - Fix access overflow occurring while translating unicode data from
		garbled or truncated file
      - Fix buffer access overflow caused by truncated file
      - Need to check word_string() output not NULL in cmd_maybe_ignore()
      - String equality test while searching the command table for command
		having parameter would access byte out of allocated memory
		and produce potentially random result. Fixes AddressSanitizer
		error found by Hanno Boeck
      - String equality test while searching the command table for command
		having parameter would access byte out of allocated memory
		and produce potentially random result. Fixes AddressSanitizer
		error found by Hanno Boeck
      - Substitute appropriate prefix-depending paths in the man page prior
		to installing
      - Limit depth of group embedding to guard against malicious files with
		thousands of consecutive {
      - check index before access into month_strings array
      - attr_get_param(): silence warning message in frequent and normal
		case (Fabian Keil)
      - attrstack_drop(): Properly drop the last stack element (Fabian Keil)
		+ get rid of unused variable in attrstack_push()
      - hash_get_string(): Reject invalid indexes (author: Fabian Keil)
0.21.9:
      - Support EndNote reference citations in convert.c
      - Improved handling of some tables
      - Fixed --text processing broken in 0.21.8 - outputs/text.conf
0.21.10:
      - added gentoo automake-fix and iconv-detection patches

@Fdawgs the problem here seems to be that GnuWin32 was the organisation porting Gnu utilities to Win32 - and they are no longer maintained since 2017.  My guess is that this will never be available to windows without a community effort? I would imagine there isn't much appetite for it? RTF isn't exactly a hot and sexy topic and the fact that the linux version can be dockerised...
What are you doing yourself for your projects? Do you run it on Linux? In Docker? Does it work well on docker on windows and are there any issues getting the permissions to read windows SMB/UNC file shares etc?

@thegoatherder It is currently used as part of docsmith at the hospital I work at, and can be deployed to docker.
You are correct that unrtf doesn't seem to be supported anymore, so this issue will probably be stuck open.
I'm working with a team mate atm to build a more modern multi-platform RTF module (should be ready next week) that will also be able to handle stdin and stdout, so the whole file reading can be handled on the user end and just piped in (thus UNC paths not being an issue)!

@Fdawgs - a more modern multi-platform RTF module - do you mean a replacement for unrtf? Or another wrapper for it?
I would be more than happy to run it through our RTF tests and let you know the result. We have a series of tests that check for various normalised substrings in text extracts as well as the start/end text and anti-patterns. We have developed a tool very similar to your docsmith, except we are extracting to plain-text rather than HTML and using the results downstream in NLP analytics. Unfortunately that tool isn't currently open-sourced (out of my control!), otherwise I would share it with you...

Abandoning.


[Bug]: 404 error at URL: /hotspots/cities/null

What happened?
A bug happened!
URL
https://explorer.helium.com/hotspots/112hcE4AD8W4JwUzSEPDZeAVZAA2Mynr2qTh25AP4YNDf8gBnYVz
What browsers are you seeing the problem on?
Chrome
Do you see the issue on Mobile or Desktop?
Mobile
Relevant log output
https://api.helium.io/v1/hotspots/112hcE4AD8W4JwUzSEPDZeAVZAA2Mynr2qTh25AP4YNDf8gBnYVz

Helium app
All miners have null as cities
All miners have null as country
Re assert many times spending more than $100 to try to solve but still same

Please stop spamming the same issue; see the official response here: https://github.com/helium/explorer/issues/1089#issuecomment-1345700653


reconfigure mobile layout

With repos, spotify activity and theming added I need to ensure responsiveness and a custom layout for mobile

blocked by #90 #88 #94

merged in #97


Fix code typo for ready made pipelines

Some code examples are missing a closing curly bracket (}).

Documentation moved to https://docs.haystack.deepset.ai


Fixes ENYO-2032

Issue
Calling focus() on a control within the floating layer causes the browser to scroll it into view which can break things like moonstone/Popup that are designed to animate into view.
Fix
Prevent scrolling of the floating layer
Enyo-DCO-1.1-Signed-off-by: Ryan Duffy<EMAIL_ADDRESS>

Hi @ryanjduffy , Thank you for your fix.
I didn't know this behavior. So interesting.
For further understanding, could you recommend an article, blog or manual which explain this behavior?
I'd like to fully understand it.
Thanks!

@DavidUM come to me, I'll explain in detail :)
This is because we call focus() 'out of view' component on accessibility condition. This depends on web engine - FF doesn't occur, Safari and Chrome occur. From blink team's analysis, web engine seems not to consider the position after transform animation.
There are a lot of related Q&As - you can search with "prevent scrollIntoView". https://forum.jquery.com/topic/chrome-bug-or-how-do-i-prevent-a-form-field-to-scroll-the-container-when-focused


tar permission problems

From<EMAIL_ADDRESS>on March 13, 2013 21:04:00
The permissions changed on the egg directory.  They need a chmod u+r.  This change to 0.8.0 causes fink to install an unreadable egg dir.  I'm on mac osx 10.8.
ls -la python2/httplib2.egg-info/
total 32
drwxr-x---  6 schwehr  staff   204 Mar  6 12:40 .
drwxr-x---  6 schwehr  staff   204 Mar  6 12:40 ..
-rw-r-----  1 schwehr  staff  2337 Mar  6 12:40 PKG-INFO
-rw-r-----  1 schwehr  staff   787 Mar  6 12:40 SOURCES.txt
-rw-r-----  1 schwehr  staff     1 Mar  6 12:40 dependency_links.txt
-rw-r-----  1 schwehr  staff     9 Mar  6 12:40 top_level.txt
When installed, this happens:
ls -l /sw/lib/python2.7/site-packages/httplib2-0.8-py2.7.egg-info/
total 32
-rw-r-----  1 root  admin  2337 Mar 13 17:55 PKG-INFO
-rw-r-----  1 root  admin   787 Mar 13 17:55 SOURCES.txt
-rw-r-----  1 root  admin     1 Mar 13 17:55 dependency_links.txt
-rw-r-----  1 root  admin     9 Mar 13 17:55 top_level.txt
/sw/bin/python2.7 setup.py build
Traceback (most recent call last):
File "setup.py", line 2, in
from setuptools import setup
File "/sw/lib/python2.7/site-packages/setuptools/init.py", line 2, in
from setuptools.extension import Extension, Library
File "/sw/lib/python2.7/site-packages/setuptools/extension.py", line 5, in
from setuptools.dist import _get_unpatched
File "/sw/lib/python2.7/site-packages/setuptools/dist.py", line 6, in
from setuptools.command.install import install
File "/sw/lib/python2.7/site-packages/setuptools/command/init.py", line 8, in
from setuptools.command import install_scripts
File "/sw/lib/python2.7/site-packages/setuptools/command/install_scripts.py", line 3, in
from pkg_resources import Distribution, PathMetadata, ensure_directory
File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 2825, in
add_activation_listener(lambda dist: dist.activate())
File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 710, in subscribe
callback(dist)
File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 2825, in
add_activation_listener(lambda dist: dist.activate())
File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 2257, in activate
self.insert_on(path)
File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 2364, in insert_on
self.check_version_conflict()
File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 2403, in check_version_conflict
for modname in self._get_metadata('top_level.txt'):
File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 2251, in _get_metadata
for line in self.get_metadata_lines(name):
File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 1219, in get_metadata_lines
return yield_lines(self.get_metadata(name))
File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 1211, in get_metadata
return self._get(self._fn(self.egg_info,name))
File "/sw/lib/python2.7/site-packages/pkg_resources.py", line 1326, in _get
stream = open(path, 'rb')
IOError: [Errno 13] Permission denied: '/sw/lib/python2.7/site-packages/httplib2-0.8-py2.7.egg-info/top_level.txt'
execution of /sw/bin/python2.7 failed, exit code 1
execution of /tmp/fink.xTMpz failed, exit code 1
Original issue: http://code.google.com/p/httplib2/issues/detail?id=251

What was the solution? I see this with the 0.9.2 tarball.

http://bitworking.org/news/2016/03/an_update_on_httplib2


Rightmost column of text is invisible on moar

Windows Terminal version
1.21.2911.0
Windows build number
10.0.26120.0
Other Software
moar 1.27.2 installed via go install github.com/walles/moar@latest (issue 250 there)
Steps to reproduce
This happens both on WSL:
go install github.com/walles/moar@latest
seq -s '-' 10 99 | moar -wrap

and also on cmd:
go install github.com/walles/moar@latest
echo 10-11-12-13-14-15-16-17-18-19-20-21-22-23-24-25-26-27-28-29-30-31-32-33-34-35-36-37-38-39-40-41-42-43-44-45-46-47-48-49-50-51-52-53-54-55-56-57-58-59-60-61-62-63-64-65-66-67-68-69-70-71-72-73-74-75-76-77-78-79-80-81-82-83-84-85-86-87-88-89-90-91-92-93-94-95-96-97-98-99 | moar -wrap

Expected Behavior
Line breaking at the end of the terminal width, continuing on next line:
┌────────────────────────┐ screen width
10-11-12-13-14-15-16-17-18
-19-20-21-22-23-24-25-26-2
7-28-29-30…

Actual Behavior
Last column is blank and is not shown:
e.g.
┌────────────────────────┐ screen width
10-11-12-13-14-15-16-17-1
-19-20-21-22-23-24-25-26-
7-28-29-30…

FWIW, moar shows the last column of text fine on all tested non-ConPTY terminals.
Test results for moar showing the last column

❌ Windows Terminal (on Windows)
❌ VSCode terminal on Windows. On macOS, the VSCode terminal works fine.
✅ VSCode terminal on macOS. On Windows, the VSCode terminal does not show the last column.
✅ iTerm2 on macOS
✅ macOS Terminal
✅ Hyper on macOS
✅ KiTTY on macOS
✅ WezTerm on macOS
✅ MobaXTerm on Windows: https://github.com/walles/moar/issues/250#issuecomment-2425914388

This will be very helpful for a differential diagnosis:
Does moar work properly in WSL under Windows Terminal and VSCode?
If so: there's a chance that it has--or is using a library which has--Windows platform-specific code.
If it does, I suspect that it is--or that library is--using GetConsoleScreenBufferInfo(Ex) and treating srWindow as exclusive when it should be inclusive.

Also,

Does it work in conhost.exe (not the Terminal)
Does it work on Terminal Preview (1.22+, where there was a bit of a rewite of ConPTY)

If so: there's a chance that it has--or is using a library which has--Windows platform-specific code.

moar is using Go's term.GetSize() function, ending up in here: https://cs.opensource.google/go/x/term/+/refs/tags/v0.25.0:term_windows.go;l=48-54
func getSize(fd int) (width, height int, err error) {
	var info windows.ConsoleScreenBufferInfo
	if err := windows.GetConsoleScreenBufferInfo(windows.Handle(fd), &info); err != nil {
		return 0, 0, err
	}
	return int(info.Window.Right - info.Window.Left + 1), int(info.Window.Bottom - info.Window.Top + 1), nil
}

If it does, I suspect that it is--or that library is--using GetConsoleScreenBufferInfo(Ex) and treating srWindow as exclusive when it should be inclusive.

Let's say the window is 100 chars wide.
If moar thought the windows was 99 chars wide, moar would wrap too early.
But what's happening is that the last char on the line goes missing.
So I believe moar is getting the right information, it just fails to write chars to the last column (with ConPTY).
@DHowett ^

Ugh, I missed your comment about WSL earlier. I'm sorry.

@zadjii-msft It reproduces in preview and canary, as well as conhost.

In both cases I used a block selection to highlight the rightmost edge.

Got it!
This is what moar is printing to the console:
␛[1;1H␛[m␛[38;2;104;104;104m  1 ␛[38;2;208;208;208m10-11-12-13-14-15-16-17-18-19-20-21-22-23-24-25-26-27-28-29-30-31-32-33-34-35-36-37-38-39-40-41-42-43-44-45-46-47-48␛[m␛[K  ␛[m    ␛[38;2;208;208;208m-49-50-51-52-53-54-55-56-57-58-59-60-61-62-63-64-65-66-67-68-69-70-71-72-73-74-75-76-77-78-79-80-81-82-83-84-85-86-8␛[m␛[K  ␛[m    ␛[38;2;208;208;208m7-88-89-90-91-92-93-94-95-96-97-98-99␛[m␛[K  ␛[m␛[7m---␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[K  ␛[m␛[7m1 line  100%  Press 'ESC' / 'q' to exit, '/' to search, '?' for help                                                    ␛[m␛[K

Zooming in on the end of the first line (which is 46-47-48 in my case), I see this:
46-47-48␛[m␛[K  ␛[m
       |   |   \- space
       |   \- clear to end of line
       \- fill the rightmost column

By design, emitting a \e[K (EL 0 Erase to Right) when the cursor is in the deferred last column position clears the last column. 🙂
Now to figure out why moar is emitting \e[K in the deferred wrap position!

By design, emitting a \e[K (EL 0 Erase to Right) when the cursor is in the deferred last column position clears the last column. 🙂

I will change this behavior in moar.
Out of curiosity, why this design? When all other terminals seem to handle this differently?

Now to figure out why moar is emitting \e[K in the deferred wrap position!

Instead of clearing the screen at the start of a redraw, moar clears to EOL after it's done with rendering all chars on that line.
The hope (not measured) is that this might avoid some flickering during redraws.

Out of curiosity, why this design?

That's a good question, but I should note that xterm does the same thing:

The former libvte (gnome-terminal et al) maintainer filed a bug on us requesting that we deviate from STD 070, and James--who I look to as the paragon of all terminal emulation knowledge--had this to say: https://github.com/microsoft/terminal/issues/3177#issuecomment-542158335
He followed up with #14936, which pertains only to the delayed wrap state and not the last column.

TL;DR: this is supported by standard behavior on both sides.
@j4james likely knows much more than I do about it. 🙂

We've tried to follow the spec as closely as possible (documented in STD 070, pages D-13 and D-14). I think the only intentional deviation is with the tab control, where the behavior was changed in later DEC terminals (in that case we're matching the most recent DEC implementation, rather than the older spec definition).
I believe this is exactly the same behavior as XTerm, and last I checked, MLTerm and the Linux console were also following the spec quite closely. We're definitely not the only terminal that handles EL this way. So if you're seeing something different in XTerm, it's probably worth investigating whether there is some other factor involved.

Thanks!
And with that, I'll close this one as By Design.

(Also, I think I need to install moar on all of my machines so thank you for that)

It seems to me that with such a design, a console application that outputs via a serial port and has no way to track the size of the terminal will inevitably periodically lose the last character. Moreover, with a terminal size of 1xN, the last character will always be lost.

if you're seeing something different in XTerm

I haven't tried XTerm, but I did produce this list (before I just changed moar's behavior):
Test results for moar showing the last column

❌ Windows Terminal (on Windows)
❌ VSCode terminal on Windows. On macOS, the VSCode terminal works fine.
✅ VSCode terminal on macOS. On Windows, the VSCode terminal does not show the last column.
✅ iTerm2 on macOS
✅ macOS Terminal
✅ Hyper on macOS
✅ KiTTY on macOS
✅ WezTerm on macOS
✅ MobaXTerm on Windows: https://github.com/walles/moar/issues/250#issuecomment-2425914388

With this design, supporting the \e[K command is completely pointless. Applications that can track the terminal size can easily erase the rest of the line using spaces, and this will be even more efficient. Other applications cannot rely on this vt-command at all because of the risk of losing the last character.


Addressing Issue #379

Updated the radiotap layer to reallocate when creating a non-existent FCS checksum.  This is a better behavior because it doesn't force callers to use reflection to set cap=len on packets.
The net result is that callers do not need to mess with reflection, and the allocation when fabricating the Checksum occurs anyway.  The package probably shouldn't create valid checksums when there are not any, but this at least fixes potential panics/data corruptions when feeding packets that may not always have a capacity that matches the length of the slice.

updating CLA

I agree wholeheartedly.  Unfortunately all of the current testing and dot11
code assumes that checksum is always there and valid.  Really, the FCS
checksum should be extracted and handled in radiotap exclusively, and the
dot11 code shouldn't know anything about it, but that requires an overhaul
and potentially breaking API changes.
Thank you for the merge.
On Tue, Dec 5, 2017 at 10:13 AM, Graeme Connell<EMAIL_ADDRESS>wrote:

@gconnell approved this pull request.
This is inherently better, so happy to let it through. But the idea of
having layer.Payload not acutally be the bytes from the wire is still quite
disconcerting to me, and I'd like to get back to the point where we don't
do that at all. Again, though, happy to bring this in since it is a marked
improvement of the current state of the world.
In layers/radiotap.go
https://github.com/google/gopacket/pull/395#discussion_r155013977:

@@ -859,12 +859,20 @@ func (m *RadioTap) DecodeFromBytes(data []byte, df gopacket.DecodeFeedback) erro
}

payload := data[m.Length:]

if !m.Flags.FCS() { // Dot11.DecodeFromBytes() expects FCS present

fcs := make([]byte, 4)

if !m.Flags.FCS() {

// Dot11.DecodeFromBytes() expects FCS present and performs a hard chop on the checksum

// If a user is handing in subslices or packets from a buffered stream, the capacity of the slice

// may extend beyond the len, rather than expecting callers to enforce cap==len on every packet

// we take the hit in this one case and do a reallocation.  If the user DOES enforce cap==len

// then the reallocation will happen anyway on the append.  This is requried because the append

// write to the memory directly after the payload if there is sufficient capacity, which callers

// may not expect.

reallocPayload := make([]byte, len(payload)+4)

copy(reallocPayload[0:len(payload)], payload)

one brief note: copy(x, y) will copy until it runs out of one buffer (IE:
it'll copy bytes from A->B until either A or B runs out), so there actually
isn't a need to slice the reallocPayload here. Certainly doesn't hurt,
though :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/gopacket/pull/395#pullrequestreview-81263353,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQ9OAezjxI8GmkuCfW5IyZww-NCAzqwks5s9XnMgaJpZM4Q2dl2
.

--
:ZZ


fix: use name_prefix for autoscaling groups

Description
Use the name_prefix of the aws_autoscaling_group as the new resource is created before the old one is deleted. This results in a duplicate key error during apply if name is used.
Verification
No verification done.
Checklist

[x] My code follows the style guidelines of the project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have used pre-commit hook to update the Terraform documentation

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


LibWebView+WebContent+headless-browser: Make the page info IPCs async

The IPCs to request a page's text, layout tree, etc. are currently all
synchronous. This can result in a deadlock when WebContent also makes
a synchronous IPC call, as both ends will be waiting on each other.
This replaces the page info IPCs with a single, asynchronous IPC. This
new IPC is promise-based, much like our screenshot IPC.
Fixes #1440
(I wasn't actually able to repro, but this should certainly fix the deadlock from the dump_text call)

Cautiously optimistic since all CI is green :)


Vulkano nightly build failed due to Shaderc compilation

Due to a Travis report Vulkano master build is failing for Nightly Rust on Linux: https://travis-ci.org/github/vulkano-rs/vulkano/jobs/733905213 .
The error log showing glsl compilation error on this line of the Shader-Include example: https://github.com/vulkano-rs/vulkano/blob/master/examples/src/bin/shader-include/main.rs#L62
Shaderc error messages are:
   = help: message: 3 compilation errors:
           shader.glsl:8: error: '#line' : must by followed by an integral literal
           shader.glsl: error: shader.glsl:-1: '#line' : unexpected tokens following directive
           0:0: error: '' :  syntax error, unexpected RETURN

I investigated the code, and didn't find any issues in implementation. This is an example that was implemented long time ago and it worked well so far. Also, I don't see any changes in Vulkano-shaders subproject that may cause this error.
After some debugging of Vulkano-shaders I managed to figure out that the error message is coming from the shaderc-rs entry function: https://github.com/vulkano-rs/vulkano/blob/master/vulkano-shaders/src/codegen.rs#L184
And, what's more important, it happening in the Rust Nightly only. I managed to reproduce this bug, and can confirm that it relevant to Rust Nightly and irrelevant to Rust Stable. The parameter values passing to shaderc's "compile_into_spirv" function exactly the same in Stable and Nightly. So, my suspicion is the bug somewhere in the Shaderc-rs crate(or maybe even in the shaderc itself).
I also can confirm that the issue with includes appearing in my personal project too which is using includes extensively. And in Nightly build only too.
This is the minimal example of glsl code causing this error:
#version 450
#include <common.glsl>

No matter what's inside "common.glsl". If "common.glsl" was properly resolved Shaderc throughs the error mentioned above(about the #line directive that is not even used in the snippet).

My suggestion to admins(@AustinJ235) is to turn off Travis CI nightly build for a while since it blocking incoming PRs reviews and merging. I can't do it myself, I don't have access to Travis.
And I will write a message to Shaderc-rs developers to help me investigating the bug.

Related Shaderc-rs conversation: https://github.com/google/shaderc-rs/issues/86

Any pull request can modify the travis ci through the config in the repo.
On Oct 8, 2020, 7:14 AM, at 7:14 AM, Ilya Lakhin<EMAIL_ADDRESS>wrote:

Due to Travis report Vulkano master build is failing for Nightly Rust
on Linux:
https://travis-ci.org/github/vulkano-rs/vulkano/jobs/733905213 .
The error log showing glsl compilation error on this line of the
Shader-Include example:
https://github.com/vulkano-rs/vulkano/blob/master/examples/src/bin/shader-include/main.rs#L62
Shaderc error messages are:
  = help: message: 3 compilation errors:
shader.glsl:8: error: '#line' : must by followed by an integral literal
shader.glsl: error: shader.glsl:-1: '#line' : unexpected tokens
following directive
          0:0: error: '' :  syntax error, unexpected RETURN

I investigated the code, and didn't find any issues in implementation.
This is an example that was implemented long time ago and it worked
well so far. Also, I don't see any changes in Vulkano-shaders
subproject that may cause this error.
After some debugging of Vulkano-shaders I managed to figure out that
the error message is coming from the shaderc-rs entry function:
https://github.com/vulkano-rs/vulkano/blob/master/vulkano-shaders/src/codegen.rs#L184
And, what more important, it happening in the Rust Nightly only. I
managed to reproduce this bug, and can confirm that it relevant to Rust
Nightly and irrelevant to Rust Stable. The parameter values passing to
shaderc's "compile_into_spirv" function exactly the same in Stable
and Nightly. So, my suspicion is the bug somewhere in the Shaderc-rs
crate(or maybe even in the shaderc itself).
I also can confirm that the issue with includes appearing in my
personal project too which is using includes extensively. And in
Nightly build only too.
This is the minimal example of glsl code causing this error:
"#version 450
#include <common.glsl>"

No matter what's inside "common.glsl". If "common.glsl" was properly
resolved Shaderc throughs the error mentioned above(about the #line
directive that is not even used in the snippet).

My suggestion to admins(@AustinJ235) to turn of Travis CI nightly build
for a while since it blocking the further PR merging. I can't do it
myself, I don't have access to Travis.
And I will write a message to Shaderc-rs developers to help me
investigating the bug.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/vulkano-rs/vulkano/issues/1423

@AustinJ235 Yes, but I can't merge even my own PRs if they don's pass tests: https://github.com/vulkano-rs/vulkano/pull/1422 And there is git hook prevent pushing to master directly.

ok, I think I figured out how to modify Travis from PR's feature branch. It passed Travis tests https://travis-ci.org/github/vulkano-rs/vulkano/builds/734112201 but seems like it tested irrelevant commit to the PR https://github.com/vulkano-rs/vulkano/pull/1424 Something is broken on the Travis side(or maybe I'm doing something wrong). To ensure this is not an accident I tried to push dummy commits to the branch and even recreated the PR from the fresh branch, but no luck.

Is this still an issue?

Travis CI is no longer, so no.


pull request for e2e test at 11/25/2016 11:56:04

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


The link to reference json doesn't work

The link in the second point of the Translation of Reference (this file) doesn't work.
Visit here :  https://github.com/processing/p5.js-website/blob/master/contributor_docs/i18n_contribution.md#translation-of-reference
This is the broken link : https://github.com/processing/p5.js-website/blob/master/dist/reference/index.html#L130

That file was moved as part of some cleanup but the link wasn't updated. It should be pointing here instead. If you would like to work on replacing this link just comment here and I'll assign the issue to you. Thanks.

If this issue is still open, Can I work on this?

Thanks for the update @limzykenneth . I have started working on the issue and will submit a PR. Please assigm me to the task.

Sorry, @ayushjainrksh. It was opened for long time so I fixed it and raised the PR. Hope you don't mind.

@Jayaprakashkumar Thanks for your interest. We are not that efficient in assigning issue or replying to issue so it would be great if you can wait for a day or two before starting work on the PR if it's not assigned to you.


timeOut-MilliSeconds in fasterThen is not working

Hi Seddrick,
When I add the option timeOut_MilliSeconds="value" in a test script, NUnit doesn't load the testsuit and gives an error. The error is: The test suite is not valid. Check with the XSD.
Examples:
This works:
<fasterThan max-time-milliSeconds="2000"/>

This doesn't work:
<fasterThan timeout-milliseconds="1000"/>
or
<fasterThan max-time-milliSeconds="2000" timeout-milliseconds="1000"/>

Greetings Daan

Daan,
Have you tried with an upper-case for the S:
<fasterThan max-time-milliSeconds="2000" timeout-milli__S__econds="1000"/>

Anyway, I think you've a problem with your max-time greater than your timeOut.

Hi Seddrick,
Thank you for your reaction!
I've tried with an upper-case S, but it wasn't working. And my example is wrong. In my situation is the ax-time of timeout-milliSeconds greater then the max-time-milliSeconds.
When I put the option timeout-milliSeconds (so without the max-time-milliSeconds) the XML fails also.
Greetings,
Daan

I've tested with my development version and can't reproduce your problem.
Just to be clear lowercase for the o of out and uppercase for the S of Seconds and an hyphen between the words timeout and milliSeconds.

Thanks it's working now. But I have no idea what was wrong.
But thank you for your time!


404  error on second logon - IIS

I managed to install and host Taskboard on IIS with PHP 7.1.8 + SQLite  using the instructions on the wiki. First time login with admin/admin worked fine and managed to create a board and a couple of new users. Tested those and still worked ok.
But when I came to log in again about an hour later I started getting a 404 error. I've tried rebooting the local host, reinstalling PHP and all the plugins, and reimported the URL rewrite rules: all with no success.

I'll have to defer to another user with better IIS experience.

Thanks heaps! Hopefully someone has run into the same issue

Wait a sec, TaskBoard v0.3.1 with PHP 7.1.8?
I think there are some issues that prevent it from working with the latest PHP.
Have you tried installing an older version (something 5.6.x is safest).

Ok so I have tried with PHP 5.6.9 and its running again! Looks like that was the problem.

Glad I could help!


Bugfix b2Body::SetActive(true)

When you call b2Body::SetActive(true) and no new fixture has been added that frame then b2World::Step(...) doesn't call FindNewContacts() and so that body has no collision detection on the first step.
The fix is to add the following line of code under the comment below in SetActive() which is already there.
		// Contacts are created the next time step.
		m_world->m_flags |= b2World::e_newFixture; // ** add this **

Your pull request have unnecessary changes. What is EscalationDepartment.h?

I am sorry, the extra change has been removed.  (That was my first GitHub pull request, I didn't expect it to update that way...  My bad.)

Fixed in #582


winblend is not respected on hovering signs

I'm using sainnhe/sonokai colorscheme with termguicolors and mousemoveevent enabled ($TERM is xterm-256color for alacritty). Default winblend == 50 hover screenshots below:

scrollbar
cursor symbol

Is it possible to make signs respect winblend value? For example, setting scrollview_signs_column = 0 results in signs' backgrounds visually distinguish from scrollbar's background:

scrollbar
cursor symbol
none

Obviously, if it's meant to be like that - feel free to close the issue, as this is by far a design issue, not a real problem here.
NVIM v0.9.1
Build type: Release
LuaJIT 2.1.0-beta3
Using latest dstein64/nvim-scrollview 7edc395

One of the workarounds that I put in for #112 (7fa516c1bd73c0be3e4a8e6693a249fc6e85cb83) is causing the problematic behavior.
I've tried to accommodate in d2764f4d56e1a6a059dfe52e082e3a74b54dc8e5. Does that address the issue for you?
Since there are winblend issues when termguicolors is set, I've changed scrollview_winblend to experimental in that scenario and defaulted it to 0 (25b46b2dd55aa52e78e73d22f48a743eb75cced4).

Sure, I think d2764f4d56e1a6a059dfe52e082e3a74b54dc8e5 does solve the issue for me! I think it should be closed for now.


Added a proper table of content to readme + added cool emojis

Description
Fixes #135
Screenshots
Checklist

[x] Tests have been added or updated to cover the changes
[x] Documentation has been updated to reflect the changes
[x] Code follows the established coding style guidelines
[x] All tests are passing

@SurajPratap10 GSSoC will end tomorrow, please check it out by today

Resolve conflicts

@SurajPratap10 Conflicts resolved, Please Merge it.


Memory leak?

I'll admit I'm not an expert on this but I think their might be a memory leak with the keyBinding code:
 angular.element($window.document.body).bind("keydown", function(e) {
              if (e.keyCode == 27) {
                scope.$$apply = false;
                dragEnd(e);
              }
            });

I don't think this is getting unbound when the directive is destroyed.

@NickPadilla, @Rodeoclash this issue has been fixed here https://github.com/angular-ui-tree/angular-ui-tree/commit/9ef029906d4ac5482ea07d98a0f2a5bd8bba5f6c


Strip ?via= from permalinks for matrix-static while it doesn't support them

?via= proposal: https://github.com/matrix-org/matrix-doc/pull/1704
matrix-static issue: https://github.com/t3chguy/matrix-static/issues/68

Seems to be fine with them now


Android JellyBean support

What is the state of Ionic's support for 4.3 Jellybean?  The docs say 4.0 and up but it seems like basic things are not working.
This includes the ionic grid (.row and nested .col) along with the ionicPopup not being positioned in the correct place. It appears it is primarily css related issues.

Greetings @uxder!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

Okay NM.  This seems to be an issue with my gulp autoprefixer settings.


.gitignore

Any objections to adding a .gitignore with e.g. .ipynb_checkpoints folder in it so we're not tracking each others checkpoints?

No objection - good suggestion


Team 2 Review (MIS): Access Routine output not defined in MIS.

@samm82
Name: Team 2 Review
About: Access Routine Semantics Output
Summary
The JoinAsync function is stated to have no output in the Exported Access Program table.

However, in the access routine semantics section, the output is stated to be "out := isJoining"

"isJoining" is not defined anywhere else so it is unclear what this output means. isJoining should either be defined elsewhere or removed.
Deadline

March 1, 2024

Estimated Work Hours

~1 hr

Resolved with commit feb7ed5bc04944bfd083876d0fd64f73e065ace4


remove npm script for running app in prod

While looking through the processor use on the docker containers, I found this:

That's near 100% - which we don't want.
This might help but not jumping through loads of hoops to get our app running.

@wellcometrust/experience-dev as a point, the 17% etc was VSZ....
So nothing to fix, but it's neater.


Older version vs New

I found this Older version smooth than the new version. Copy what the video is doing in the new version you can see the difference.
https://user-images.githubusercontent.com/75554729/161081129-28fa2ffa-1207-4eb0-b826-bf579a3fdfe8.mp4
Here's the new version, as you can see when i tap the arrow to see more and tap back, it's delayed right? And it also does the same when i tap Attack on Titan. And when i scroll up and down it wasn't smooth unlike the older version.
https://user-images.githubusercontent.com/75554729/161083381-0521c89c-0118-4ab0-9cd1-3b4767bf76c6.mp4

I will look into the issue :+1:


How to use Flow to hide a Channel In Teams

It was easy to find how to create a channel in Teams (in this case for a new item in a SharePoint list).
When the item has been completed (specific field completed), I would like to hide the Teams Channel, since it is no longer needed (but shouldn't be deleted).
Does anyone know how?
thanks

Hello, thank you for reaching out. Since this issue has been open for long, closing it for now. For discussions and suggestions to requirements like above, please feel free to reach out to the Power Automate community forum. You can also report an issue through support.


Is that possible for custom error to pop up as rpc::error in json-rpc?

Try to return custom errors from json-rpc server methods like
struct MyParams {};
struct MyResult {};
using MyServer = rpc::server<
    rpc::method<"MyMethod", MyParams, std::expected<MyResult, rpc::error>>>;
using MyClient = rpc::client<
    rpc::method<"MyMethod", MyParams, std::expected<MyResult, rpc::error>>>;

int main() {
  MyServer server;
  server.on<"MyMethod">([](MyParams) { return rpc::error{}; });

  MyClient client;
  auto [req, _] =
      client.request<"MyMethod">(1, MyParams{}, [](auto val, auto id) {});
  auto resp = server.call(req);

  std::println("resp: {}", resp);
}

but the response actually use the returned error as the result payload, i.e. the result look like
resp: {"jsonrpc":"2.0","result":{"unexpected":{"code":0,"message":"No error"}},"id":1}

instead of using the error as json-rpc error, like
resp: {"jsonrpc":"2.0","error":{"code":0,"message":"No error"},"id":1}

Is that possible to integrate error handling with the method handler?

I realize that adding some helper:
   template <typename Result>
   struct expected_helper
   {
      static constexpr bool is_expecting_rpc_error = false;
      using expected_t = std::expected<Result, rpc::error>;
   };
   template <typename Expected>
   struct expected_helper<expected<Expected, rpc::error>>
   {
      static constexpr bool is_expecting_rpc_error = true;
      using expected_t = std::expected<Expected, rpc::error>;
   };

and use it to extract those methods returning expected<T, rpc::error> would do the job, would that PR get accepted?

Ah, that was an unintended consequence of adding general support for std::expected. This should definitely be fixed. I'll experiment with a solution before I ask for a PR. Thanks for bringing this up.

After thinking about this some more, I have some questions. Are you trying to replace rpc::error with your own error class?

So far I find using rpc error is fine for me, but from design point of view, maybe it's a good idea to allow using, e.g, derived class of rpc error or some sort ...


Fix CONTRIBUTING.md step to make the project work

Following this discussion: https://github.com/meilisearch/milli/issues/76#issuecomment-1277459125

bors merge


NewDetection: NewCountryValidCreds.yaml

Required items, please complete
Change(s):

New Detection Idea

Reason for Change(s):

New detection, no similar detection found on the sign-in folder.

Version Updated:

Yes

Testing Completed:

Yes

Checked that the validations are passing and have addressed any issues that are present:

Yes

Any new comments on the file? Once this request is merge I can move on with the other request: https://github.com/Azure/Azure-Sentinel/pull/8016

@lem0w Why do we have two PRs for this one? I have mentioned my comments in #8016

@lem0w Why do we have two PRs for this one? I have mentioned my comments in #8016

Hi, this was the original PR for the new detection, then I realized that the anomaly sign in one was on the incorrect folder. So i'll be  closing this PR and only work on https://github.com/Azure/Azure-Sentinel/pull/8016 since that one has the folder correction and the new detection with your comments Thanks!


Enhance Seller Privileges for Managing Products and Viewing Orders

To enhance the functionality and security of our marketplace platform, we need to ensure that sellers have the capability to create, read, update, and delete (CRUD) only their products. Additionally, sellers should be able to view orders related to their products. This update requires modifications to both the product and order management logic to enforce these restrictions effectively.
Tasks:

Update Product Management Permissions:

Revise the product CRUD operations in productController.js to validate the seller's identity against the product owner before allowing any modifications.
Implement checks during product creation to associate the product with the authenticated seller's ID.

Restrict Order Visibility:

Modify the order retrieval logic in orderController.js to ensure sellers can only view orders that include their products.
Consider the need for aggregating order details in a way that only displays relevant information to the seller (e.g., omitting products from other sellers in shared orders).

Test New Permissions and Visibility:

Write unit and integration tests to verify that sellers can only manage their products and view relevant orders.
Ensure tests cover scenarios of unauthorized access attempts.

Update API Documentation:

Reflect these changes in the API documentation, clearly stating the permissions and visibility rules for sellers.

Inform Sellers of New Features:

Prepare communication to inform current sellers about the new features and any actions they need to take.

Acceptance Criteria:

Sellers are restricted to managing only their listed products and cannot modify others'.
Sellers can view orders that involve their products but see limited details for products not owned by them.
Comprehensive tests confirm the security and functionality of the updated features.
API documentation is updated to include the new permissions and visibility rules.
Sellers are informed about the update and understand how to use the new features.

Deliverables:

Updated product and order management logic in the backend.
Unit and integration tests validating the new restrictions.
Revised API documentation.


Updated code conventions and formatter plugin

This PR addresses GitHub issue: #822 and #1240 .
Briefly describe the changes proposed in this PR:

introduced new code conventions based on Eclipse code formatting style (as per #1240), with 120-char linewrapping, unix line endings, and a slight tweak to format qualified invocations (e.g. fluent api calls) in a more readable fashion
reformatted code base with new conventions.
Maven formatter plugin added to automatically validate code against the code conventions (#822). it will fail the build if formatting is not compliant. mvn formatter:format will reformat existing code to the configured conventions if necessary.

Note that the supplied xml file is an eclipse formatting file, and can therefore be imported in Eclipse to use the IDE formatter directly.
I'd like to get this out of the way as soon as possible - the master and develop branch are currently not much different, which means merging this change over both branches will be less difficult (but still a bit painful). The longer we wait, the more awkward this becomes.
Have a look at the new code formatting. I'm reluctant to diverge from the Eclipse conventions too much, but if there's anything standing out that definitely needs fixing, we'd better fix it now.

@rdf4j-bot run tests

Hm, it appears my clever trick to have a relative reference to the xml file is giving jenkins trouble. Odd as it works perfectly on my machine. Running a test to see if it has to do with the maven version.

Can we change the wrap width to 180? I have around a 220 character wide windows when I program. If I use fullscreen I have around 310.

I think we need to cater to a lowest common denominator/accepted conventions here. We're actually already going out on a limb a bit with 120 since most coding guidelines still (!) prescribe 80 columns. I also don't think that going wider will necessarily improve readability: it's one thing to have the screen real-estate, but it also needs to be code that is easy to read and understand.
Moreover if we changed it to 180 or more, I would personally have to scroll horizontally all the time : my laptop monitor is not that hi-res...

Can we change the wrap width to 180? I have around a 220 character wide windows when I program.
If I use fullscreen I have around 310.

You have very good eyesight and/or a nice monitor over there, I barely get 150 on my machine (15"
laptop)...
So if you don't mind I'd also go for 120...

I think we will need to be able to mark a section as "don't reformat", like the javadocs I have in the ShaclSail.

@rdf4j-bot run tests

I think we will need to be able to mark a section as "don't reformat", like the javadocs I have in the ShaclSail.

That's actually catered for:
//@formatter:off
custom-formatted stuff
//@formatter:on
This should be used only in special circumstances though.

Alright if there are no further issues I'll merge this in (Jenkins is now happy as well) and I will also immediately try and sync the develop branch. I'll try and get to the other repos later in the week.


(docs) Remove dollar sign ($) in front of terminal commands

I think this fixes #757 :)
Hope I did this right

Coverage remained the same at 98.234% when pulling 8f2a5a8d151ce49d223547bb109852d2004de7ed on dmnkgrc:pr/removeDollarSign into 2a78f889fef3e5a0e3c8d3e7ed212469d19d7018 on mxstbr:master.

Awesome work! Good catch on the Windows ones too, I would've missed those :grin:
Very well done, congratulations on landing your first PR! :tada: :tada: :tada:


Expose pod startup latency from node-throughput tests on perf-dash

Let me do this actually.

Done.