python310Packages.elementpath: 2.5.3 -> 3.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.elementpath is: "XPath 1.0/2.0 parsers and selectors for ElementTree and lxml"
meta.homepage for python310Packages.elementpath is: "https://github.com/sissaschool/elementpath"
meta.changelog for python310Packages.elementpath is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.0.0 with grep in /nix/store/8m1kam73cygq7md6lnppbnnm1bbjvvm4-python3.10-elementpath-3.0.0
found 3.0.0 in filename of file in /nix/store/8m1kam73cygq7md6lnppbnnm1bbjvvm4-python3.10-elementpath-3.0.0

Rebuild report (if merged into master) (click to expand)

32 total rebuild path(s)

16 package rebuild(s)

16 x86_64-linux rebuild(s)
16 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
banking
cve-bin-tool
cyclonedx-python
matrix-synapse
matrix-synapse-plugins.matrix-synapse-mjolnir-antispam
matrix-synapse-plugins.matrix-synapse-shared-secret-auth
python310Packages.elementpath
python310Packages.fints
python310Packages.pysaml2
python310Packages.sepaxml
python310Packages.xmlschema
python39Packages.elementpath
python39Packages.fints
python39Packages.pysaml2
python39Packages.sepaxml
python39Packages.xmlschema

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8m1kam73cygq7md6lnppbnnm1bbjvvm4-python3.10-elementpath-3.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.elementpath https://github.com/r-ryantm/nixpkgs/archive/b91b0bc97951700759d2aab623a6a31d4d1b2daf.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8m1kam73cygq7md6lnppbnnm1bbjvvm4-python3.10-elementpath-3.0.0
ls -la /nix/store/8m1kam73cygq7md6lnppbnnm1bbjvvm4-python3.10-elementpath-3.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

14 packages failed to build:

banking
cve-bin-tool
cyclonedx-python
matrix-synapse
matrix-synapse-plugins.matrix-synapse-mjolnir-antispam
matrix-synapse-plugins.matrix-synapse-shared-secret-auth
python310Packages.fints
python310Packages.pysaml2
python310Packages.sepaxml
python310Packages.xmlschema
python39Packages.fints
python39Packages.pysaml2
python39Packages.sepaxml
python39Packages.xmlschema

2 packages built:

python310Packages.elementpath
python39Packages.elementpath

Maintainer pings
cc @jonringer for testing.

builder for '/nix/store/ys9vhmcykrilkss1xanl2laxn3caz6dy-python3.9-xmlschema-1.11.3.drv' failed with exit code 1; last 10 log lines:
  adding 'xmlschema-1.11.3.dist-info/RECORD'
  removing build/bdist.linux-x86_64/wheel
  Finished executing setuptoolsBuildPhase
  installing
  Executing pipInstallPhase
  /build/source/dist /build/source
  Processing ./xmlschema-1.11.3-py3-none-any.whl
  ERROR: Could not find a version that satisfies the requirement elementpath<3.0.0,>=2.5.0 (from xmlschema) (from versions: none)
  ERROR: No matching distribution found for elementpath<3.0.0,>=2.5.0


Wallet Recovery:It does not show "Hint" at the time of wallet recovery.

It does not show "Hint" at the time of wallet recovery.
Tested on dev app v2.0.70(445)

Verified this issue on dev app v2.0.75(463)


Format Number

Hello! I have a problem with your library. Please me help.
https://stackoverflow.com/questions/51215810/android-sdk-parsing-sms?noredirect=1#comment89413669_51215810

Hi @KostyaLyapochkin,
We will look into this and inform you about our findings.
Thanks for using the sms parser library.

Thanks @drilonreqica !
I will be wait answer. I need this library =)

@KostyaLyapochkin I tried to reproduce the issue with the exact same prerequisites as you and could not find any bug. See my stackoverflow answer for more info. For now I close this issue.


Feature: Explorer the options for generating OpenAPI spec from annotated HTTP endpoint.

Is your feature request related to a problem? Please describe.
No
Describe the feature you are requesting, as well as the possible use case(s) for it.
Explorer the options for generating OpenAPI spec from annotated HTTP endpoint like using https://github.com/getkin/kin-openapi or github.com/swaggo/swag
Indicate the importance of this feature to you.
Should-have
Anything else?
No response

From the above I have found the following libraries that handle parsing, validating and generating server and clients code from open api spec documents:

libopenapi
kin-openapi
oapi-codegen
go-swagger

For our case I thi k they would be helpful in generating and validating an sdk given the Open Api spec document. I have not seen their capability in actually generating the OpenApi Spec from go code.
I have also encountered projects that offer documentation generation as a feature. These include:

huma

The closest thing to what is described by this issue is:

swag - This offers spec generation from code and changes would not be intrusive.
The above is illustrated in the images below. The major challenge with this tool is the fact that it uses V2 of the spec and does not have support for V3 or V3.1.


Agentops is tracking sessions even after I commented out the tracking code

🐛 Bug Report
🔎 Describe the Bug
I have commented out the agentops code in my notebook. But still it is tracking the chat and generating tracking links.
I have restarted the notebook but still its happening.
🔄 Reproduction Steps
Not sure how you would reproduce it.
🙁 Expected Behavior
If I comment out the code, it should stop tracking and should not create new sessions.
📸 Screenshots
Can't provide screenshots due to company policy.
🔍 Additional Context
I was using agentops in my notebook before to track the sessions and it was working well. But even after commenting, its tracking new runs.

Can you check your environment variables and make sure that your API key isn't getting loaded in?

API key was getting loaded in, but without agentops.init, it shouldn't start. I have checked crewAI's code and based on that i can concur that if I don't call agentops.init, it shouldn't start recording.

Also in a notebook, make sure you restart the interpreter after commenting out agentops.init(). Once the client is initialized, it will continue tracking as long as its initialized.

Are you using Crew in your notebook?

Yes, I am.

Also in a notebook, make sure you restart the interpreter after commenting out agentops.init(). Once the client is initialised, it will continue tracking as long as its initialized.

I restarted the notebook every time before running the code. I have been using agentops in my day-to-day work. If this issue comes again, I will make a short video and share here. @bboynton97 Thanks for taking the time to review it. I appreciate it


[backport] ci: Upgrade to yq 3.4.1

Since the resolution of https://github.com/mikefarah/yq/issues/502, the yq binary is no longer broken on s390x. This is an upgrade to the latest v3 version of yq (v4 has new syntax). This is a backport of https://github.com/kata-containers/kata-containers/pull/1261.
Fixes: #3134
Depends-on: https://github.com/kata-containers/tests/pull/3158

/test

/test


Markdown from private repositories

Description
It must be possible to use the Markdown Block in the Docs editor with URLs to MD files that are in private repos.
Related resources
User docs ticket: #17
Acceptance criteria

The exporter provides a custom property to provide authentication for markdown block

If a markdown block is configured with a link to a private repository, the authentication is used

@Ydus @JiriTrecak I believe this is done.

Resolved in ENG-399


encode user_presence as int so it can be json'd

See issue #37

Closing this as the soon-to-be-released 5.0.0 already addresses this issue.


Renderer : multiple backculling modes

The renderer backculling can only be activated or deactivated.
It would be convenient to provide a mode where backculling is only applied on opaque triangles.
Let's introduce a third selective backculling mode excluding transparent triangles.

Done in version 1.75.


Add priority options to todo context menu

Currently, changing the priority of a todo entry takes a lot of clicks (when not using the keyboard).
This is a feature suggestion to add two very simple options to the todo context menu:

The arrow-up button will increase the todo priority by one, arrow-down will decrease it by one.
Notes / Discussion

the new buttons are intentionally hidden for todo entries that don't have a priority assigned to them

I'm wondering if adding a "Set priority to A" to those would help getting non-prioritized quickly enlisted into the priorities and subsequently using the arrow-down function to lower them as necessary

clicking arrow-up on a prio:A entry will simply do nothing (same with arrow-down for prio:Z)

I think it would be even better if we could grey out the options not applicable to those and make them non-clickable instead

Please excuse the code quality, my JS/CSS skills are rather basic. Feel free to suggest any improvements.

@M4he thanks alot for your contribution. I will take a look at it asap. It looks like a good idea!

@M4he my thoughts so far: It's pretty cool and we should keep it :)
I'm going to do some refactoring on the code, like minimising it a little, if you don't mind and will also write test cases. Unless you want to learn how to do that and try it out yourself (for reference https://github.com/ransome1/sleek/blob/develop/test/playwright.spec.js).
What I'm struggling about are the arrow up and down buttons, which to me imply a click will move them up and down in the list by one row. Instead I would like to go with plus and minus and further more would want to add a label, that marks this as priority changers. Because now those buttons can be everything.
I'm going to build a pre release of this soon and would like to hear your opinion. Thanks again for contributing :)

Also: I was wondering if we should hide the priority changer in case a todo has no priority.
Why not showing the function even on todo with no priority? I understand it could be tricky to decide which would be the 1st priority that gets selected after a click. We could default it to (A) and see what the user feedback is.

I'm going to do some refactoring on the code, like minimising it a little, if you don't mind and will also write test cases. Unless you want to learn how to do that and try it out yourself (for reference https://github.com/ransome1/sleek/blob/develop/test/playwright.spec.js).

Sure, go ahead. I believe it will be much more efficient if I leave this part in your capable hands ;)

What I'm struggling about are the arrow up and down buttons, which to me imply a click will move them up and down in the list by one row. Instead I would like to go with plus and minus and further more would want to add a label, that marks this as priority changers. Because now those buttons can be everything.

Agree. I had simple plus and minus text there at first as placeholders but the font looked too thin. fa-plus and fa-minus should be about right though.
With label I guess you mean like this?
+----------------------+
| Prority:    +     -  |
+----------------------+
| Use as template      |
+----------------------+
| Copy                 |
+----------------------+
| Delete               |
+----------------------+

Also: I was wondering if we should hide the priority changer in case a todo has no priority.
Why not showing the function even on todo with no priority? I understand it could be tricky to decide which would be the 1st priority that gets selected after a click. We could default it to (A) and see what the user feedback is.

As I wrote under "Notes" I also was wondering how we could get todos without priority quickly enlisted with the menu. The problem I see with reusing the + button is that the user might expect that it will be placed in the priority category that's visually above: if the user's lowest priority is D then the + might suggest it will be moved to D because that's visually directly above the non-prioritized entries. If the user's lowest priority is E, then E is visually directly above and so on.
A dedicated context menu entry that more clearly suggest that it will get the priority (A) assigned would be preferable in my opinion.

As I wrote under "Notes" I also was wondering how we could get todos without priority quickly enlisted with the menu. The problem I see with reusing the + button is that the user might expect that it will be placed in the priority category that's visually above: if the user's lowest priority is D then the + might suggest it will be moved to D because that's visually directly above the non-prioritized entries. If the user's lowest priority is E, then E is visually directly above and so on.

I agree! I think I might have a half baked solution for this. But it only works if the first sorting is set to priority (only then I can find out what is the lowest available priority).

In case a todo already has a priority, plus minus will be added to that priority
In case a todo has no priority (and 1st sorting is priority) sleek will add the lowest available priority to the todo.

I only tested it briefly but so far it works. Can I ask you to check this pre release if this works as you would expect it to? https://github.com/ransome1/sleek/releases/tag/v1.1.8-rc.1


grub2: 2.06-rc1 -> 2.06

Motivation for this change
Switch to the released version, since we're on rc1
Not sure if this needs a release note entry, since we're only going from rc1 to release
Things done

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

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

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.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 126585 run on x86_64-linux 1

7 packages built:

grub2 (grub2_full ,grub2_light)
grub2_efi
grub2_pvgrub_image
grub2_xen
os-prober
tests.trivial
woeusb

nixos/tests/grub.nix runs successfully.


Correct package.json svelte key

It points to src/index.js which does not exist. Can either try .ts or just expect consumers to use the built components.

Fixed in #11


Added comments for soundcloud regex

Small edits to add comments on the regex. Just to make it easier for someone looking at this code later.

I'm sorry but this comes off as spammy with hacktoberfest going on, if you plan on doing another pull request for something else (I think you wanted to work on #120) you can always add it there

Ah right my bad. How abut reopening later?


AnimationFinished Guard

I know I asked about this earlier but it would be nice to have a AnimationPlayerFinishedGuard and a AnimationTreeFinishedGuard

How would this guard work? An animation being finished is an event that occurs. A guard is something that is checked before a transition is taken. So the guard would only work if the transition and the finishing of the animation would happen in the same frame, which is rather unlikely.
If you simply want to check if the animation player is still playing an animation before taking a transition, you can set the animation player as an expression property at the start and then use the expression guard for checking, e.g.
@onready var _state_chart:StateChart = $StateChart
@onready var _animation_player:AnimationPlayer = $AnimationPlayer

func _ready():
    _state_chart.set_expression_property("animation_player", _animation_player)

and then in your expression guard:
not animation_player.is_playing()

If you want to take a transition on when the animation player finishes playing an animation listen to the animation_finished event of the animation player and send an event to the state chart, e.g.:
func _on_animation_player_animation_finished(animation):
    _state_chart.send_event("animation_finished")

Then you can set up transitions that react to this event.

you would pass an animation player or tree to the guard and then it would check if it's finished.
if false then it would guard the state from transitioning
if true it would transition

Well yes, this is what I have described you can implement with the expression guard. However I don't really see how such a thing would be generally useful. What is the use case you have for this?

Well yes, this is what I have described you can implement with the expression guard. However I don't really see how such a thing would be generally useful. What is the use case you have for this?

it would be for waiting for a animation state to finish.

Well yes but this is very likely not useful. You would need something to constantly send events that trigger a state change for this guard to have an effect, otherwise it will not do anything. Could you maybe describe the actual problem you want to try to solve with this? Then I think I might give a better recommendation.

I want to wait for a animation to end before starting a new state

Well in this case, hook up the animation_finished signal of the animation player and then let it trigger a state change by sending an event like this:
func _on_animation_player_animation_finished(animation):
    _state_chart.send_event("animation_finished")

And then connect the animation player's animation_finished signal to this function. This should do the trick nicely.


My Maps is gray

Hi,
Everything is well configured (I think), (npm install, module + key loaded, google api enabled, css, ts, ...)
I copied pasted this:
{{ title }}

<agm-map [latitude]="lat" [longitude]="lng">
<agm-marker [latitude]="lat" [longitude]="lng">

When I launch the website i have a gray map.

How can I fix the problem?

If I put the yellow person on the map, I can see the street view mode.

i had the same issue in an older version, Are you generating the api key?
in your ng2+ app.module and with  the new version of agm you should have in you app.module
@NgModule({
imports: [
AgmCoreModule.forRoot({
apiKey: 'YOUR_API_KEY
}),
....
please read as reference for an older version: https://github.com/SebastianM/angular-google-maps/issues/550

I finally used another google maps plugin, I dont know why it doesnt work with this one.
Thank you for your help.

what you mean by YOUR_API_KEY ? is it a google apikey?
provide me with an example what mean exactly

@ranouf which plugin did you use instead?

I am having this issue currently. I think it has something to do with it being in a subcomponent. Please reopen this issue

Have the same issue like @bradenclapp with map in modal window appended dynamically.
Map works perfectly in main window but in modal it shows pic as @ranouf had shown.
Tried to invoke agmMap.triggerResize() on mapReady event or on ngOnInit - it did not help.
Just this solution works for me but it is little ugly.
ngOnInit() {     this.GMS.getMapBoundsObservable(this.innerData.markers).subscribe((bounds)=>{       if(bounds) {         this.mapBounds = bounds;         setTimeout(()=>{this.agmMap.triggerResize();}, 100);       }     });   }
@SebastianM It will be great if you reopen the issue.

I'm having the same issue. In my case the map loads fine with page refresh (F5), but is greyed out if I switch back and forth between components.

Hi everyone! I'm having this problem too. My map shows grey until I zoom in/out the screen. After that, It shows properly! I tried the well know solution of invoking the resize trigger [ this.agmMap.triggerResize() ] and it still doesn't work.
Thanks in advance to everybody who will come up with a solution!

In ma case this issue was caused by having the map under *ngIf. If you need to dynamically show/hide the map, use display:none style instead. Otherwise, you might have to change how the scripts are loaded & initialized.

Thanks but I don't dinamically show the maps! Here is my code:
mycomponent.html : ......................<div class="row">                         <agm-map [latitude]="latitude" [longitude]="longitude" id="gmap" #agmMap>                             <agm-marker [latitude]="latitude" [longitude]="longitude"></agm-marker>                         </agm-map>                     </div>.............. (no *ngIf over agm map!!)
mycomponent.ts: `..... public latitude=45.5;
public longitude=51;
@ViewChild('maintenance_interval') maintenance_interval_container: ElementRef;
@ViewChild('agmMap') agmMap : AgmMap
constructor(public assetService: AssetService, public alertService: AlertService, private renderer: Renderer2) {}

ngOnInit() {

    jQuery('#data_1 .input-group.date').datepicker({
        todayBtn: "linked",
        keyboardNavigation: false,
        forceParse: false,
        calendarWeeks: true,
        autoclose: true
    });

    this.calendarInit();

    jQuery("#completed").css("display", "none");
    this.agmMap.triggerResize(); //the first solution attempt
} ....... `

mymodule.ts: `import { AgmCoreModule }            from '@agm/core';
@NgModule({
declarations: [
AssetComponent,
AssetListComponent,
AssetDetailComponent,
CategoryPipe,
MaintenancePipe
],
imports: [
BrowserModule,
FormsModule,
RouterModule,
TranslateModule,
PaginationModule,
SplitPaneModule,
AgmCoreModule.forRoot({
apiKey: 'APIKEY'
})
],
exports: [
AssetComponent,
AssetListComponent,
AssetDetailComponent
],
providers: [
AssetService
]
})
export class AssetModule { }mycomponent.css: agm-map{
height:50vh;
width:100%;
margin-top:0%;
}`
I have to mention that I use bootstrap classes in the divs that contain agm-map.

It doesn't have to be dynamically loaded (*ngIf) inside that very component. If you have ANY *ngIf in any of your master templates that show your map component, it will break the maps as well. In my case, I was using *ngIf in my master layout template and not in my map component.

Hi guys i know its late but i'm having this issue where i'm using the map in a modal and it stops working but on full screen it works fine the weird thing is if i resize the browser with modal view open it starts to show map i've been stuck in this for long any help would be appreciated
the below screen is what i see when i open modal and it doesn't work

after resizing of browser i see this

if anyone know when the text under google map disappear/appear then it would be a good lead for me
Thanks

I am having this issue currently. When the agm-map tags are in an upper component it renders fine but once I have it in an accordion it shows up like @ranouf screen shot. I think it has something to do with it being in a subcomponent. Please reopen this issue @SebastianM
EDIT I found exploring other issues this fix.
Html:
<agm-map #agmMap [latitude]="lat" [longitude]="lng">
.TS :
import { AgmMap } from '@agm/core';

@ViewChild('agmMap') agmMap : AgmMap

funcActivatedByParentComponentOnAccordionOpen() {
          this.agmMap.triggerResize();
}

I'd recommend a function inside the agmMap something like redraw() or reset() so that its more obvious that there are tools to refresh the map

Interestingly, even the mere addition of the template variable #agmMap already solved the problem for me and there's no need to trigger resize :thinking:

Nowadays (sept 2020), the resize does not work anymore (deprecated event). Manually resizing the div with setTimeout triggers.

This was the only solution that worked for me on an ionic project... thank you!

I am having this issue currently. When the agm-map tags are in an upper component it renders fine but once I have it in an accordion it shows up like @ranouf screen shot. I think it has something to do with it being in a subcomponent. Please reopen this issue @SebastianM
EDIT I found exploring other issues this fix.
Html:
<agm-map #agmMap [latitude]="lat" [longitude]="lng">
.TS :
import { AgmMap } from '@agm/core';

@ViewChild('agmMap') agmMap : AgmMap

funcActivatedByParentComponentOnAccordionOpen() {
          this.agmMap.triggerResize();
}

I'd recommend a function inside the agmMap something like redraw() or reset() so that its more obvious that there are tools to refresh the map

Interestingly, even the mere addition of the template variable #agmMap already solved the problem for me and there's no need to trigger resize 🤔
UPDATE: When I close my modal and re-open it again, it gets stuck on gray screen even when I've already triggered resize
UPDATE:
I got it working consistently by doing:
controller (TS):

loadMap = false;

constructor(...) {...}

ngAfterInitContent() {
  ...
  setTimeout(() => this.loadMap = true, 0)
}

HTML:
  <agm-map
    *ngIf="loadMap"
    ...
  ></agm-map>

This was the only solution that worked for me on an ionic project, thank you!


electron from-source headers are in the wrong format

Describe the bug
$ nix build nixpkgs#electron_26-bin.headers
$ file $(readlink ./result)
/nix/store/vnp5jnvpw0q6afc9pfkynwb72i1yszcp-node-v26.3.0-headers.tar.gz: gzip compressed data, was "node_headers.tar", last modified: Wed Oct  4 20:06:25 2023, max compression, original size modulo 2^32 1392640

$ nix build nixpkgs#electron_26.headers
$ file $(readlink ./result)
/nix/store/3m4ylx9m7bk2ci5cymv8z2q3y4hf677l-node-v18.16.1-headers.tar.xz: XZ compressed data, checksum CRC64

Believe it or not, node-gyp can't unpack XZ :(

Error: TAR_BAD_ARCHIVE: Unrecognized archive format

Additional context
Add any other context about the problem here.
Notify maintainers
@yu-re-ka

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.52, NixOS, 23.05 (Stoat), 23.05pre-git`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.5`
 - channels(yorick): `""`
 - channels(root): `""`
 - nixpkgs: `/nix/store/iarm76b9p60gbkxs0n3dww1r2f4gs650-source`

Add a :+1: reaction to issues you find important.

Note that there is also an electron_26.headers, which does produce a .gz file.

Sorry, typo. electron_26.headers is producing an xz file for me. Maybe it's fixed in stable?

Ah no, you're right

It seems to be as simple as changing the file ending to .gz:
[yuka@yuyu:~/proj/nixpkgs]$ nix build -f . electron_28.headers

[yuka@yuyu:~/proj/nixpkgs]$ file $(readlink result)
/nix/store/qapanp31iygr3mab2aingddgy41fvzbl-node-v18.18.2-headers.tar.gz: gzip compressed data, max compression, from Unix, original size modulo 2^32 52971520

[yuka@yuyu:~/proj/nixpkgs]$

#275628


Fix obsolete naming

Currently we try to rename obsolete tables without checking their case is correct. Therefore if, after upgrading 3->4 and running a dev/build for the first time, a misnamed table is marked as obsolete you get a failure.
For example
ALTER TABLE "_obsolete_Page_Versions" RENAME "_obsolete__obsolete_Page_Versions"
Where _obsolete_Page_versions exists but not _obsolete_Page_Versions.
This change updates the case of the table before running the rename to obsolete query.

Have revised per @tractorcow 's review.

Amazing, merge on green.


bluetooth: reset lastIntent to prevent repeated speak music info

Fix bug: https://bug.rokid-inc.com/zentaopms/www/index.php?m=bug&f=view&bugID=20454

Checklist

[x] npm test passes

LGTM but the device CI seems not get running, @yodaos-project/build do you help this?


default-directory set to project root after venv-workon

Using the version from MELPA, after I activate an environment with venv-workon the default-directory is set to the project root in all opened project buffers, this makes it difficult to use this function in a hook since.

Now it is confirmed that venv--switch-to-project-dir in venv--activate-dir causes the problem. When invode venv-workon, it will call venv--activate-dir and then venv--switch-to-project-dir is called.
(defun venv--switch-to-project-dir ()
  "If we find the project file, cd into that directory"
  (let ((proj-file (expand-file-name ".project" venv-current-dir)))
    (when (file-exists-p proj-file)
      (cd (with-temp-buffer
            (insert-file-contents proj-file)
            (string-trim (buffer-string)))))))

If there is a .project file in venv-current-dir, it will try to switch to the directory which is the project path the .project file contains.
As the cd function doc string shows that, it will change the default directory of the opened directory buffers to the project root directory.
It seems that the latest version of pipenv will create the .project file in the initialization of an virtual environment.

Ah correct, most of the code that currently uses
(cd venv-current-dir)
...forms...

Should instead create a lexical scope for default-directory
(let ((default-directory venv-current-dir))
  ...forms...)


Fix bad behavior when clearing XAudio2AudioPlayer

These commits will ensure that - when XAudio2AudioPlayers get a new voice from the driver by getting cleared, they'll also set all player properties on it. Most noticeable is a discrepancy in volume, easily shown through
import pyglet

player = pyglet.media.Player()
player.volume = 0.1
player.loop = True
player.queue(pyglet.media.synthesis.Sine(0.4))
player.play()

pyglet.app.run()

where the volume snaps to the default of 1.0 for every other loop.
3d calculations are applied immediately to prevent very short bursts from a misplaced and not updated voice (Tested only via the soundspace example)

I think this is still incorrect.
When returning a voice, it should just remove itself from the emitters and reset it's volume, frequency, and position. There should be no need to calculate 3D, apply 3D, or commit changes (this is also assuming 3D is being used).

I think this is still incorrect.
When returning a voice, it should just remove itself from the emitters and reset it's volume, frequency, and emitter settings. It's no longer being used, there should be no need to calculate 3D, apply 3D, or commit changes (this is also assuming 3D is being used). This also needs to apply when calling .delete as well.

Pooled voices are in a completely unclear state that can not be assumed to correspond to the player's needs. They might be positioned anywhere with any orientation and have any volume, so will need to get adjusted when retrieved. It's no use to reset the voice's attributes to anything default-ish: what if the next player receiving it is playing at volume 0.8 with an orientation of 142.4092°?
If a voice is no longer being used, it is removed from _emitting_voices, which means it won't be picked up by any runs of _calculate_3d_sources anymore, so it won't eat up resources in that regard. It gets stuck in virtual audio space whereever it last was, does not produce any more output and repositioned immediately again when next unpooled.


[Bug] [Module Name] Hive2CK using CK File  generate data_local.log slow

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
using  CK File sync hive data to ck，total data count 2.3KW，using CK JDBC 40m, using CK File 8h。
From Spark Log, know generate data_local.log  spend 7h, from data_local.log to CK table file spend 5h
SeaTunnel Version
2.3.3
SeaTunnel Config
env {
  spark.app.name = "hive_to_ck_file"
  spark.executor.instances = 4
  spark.executor.cores = 1
  spark.executor.memory = "3g"
  // This configuration is required
  spark.sql.catalogImplementation = "hive"
  spark.executor.extraJavaOptions = "-Dfile.encoding=UTF-8"
  spark.driver.extraJavaOptions = "-Dfile.encoding=UTF-8"
  spark.hadoop.hive.exec.dynamic.partition = "true"
  spark.hadoop.hive.exec.dynamic.partition.mode = "nonstrict"
  spark.debug.maxToStringFields = 100000
}
source {
    hive {
        table_name = "dms_ddcx.xx_table"
        metastore_uri = "thrift://xxxxx:9083"
        result_table_name = "table"
        parallelism = 4
        read_partitions = ["dt=2023-10-30"]
    }
}
transform {}
sink {
    ClickhouseFile {
        host = "xxx:8123"
        server_time_zone = "Asia/Shanghai"
        database = "dms_ddcx"
        parallelism = 4
        table = "xxxx"
        source_table_name = "xxxx"
        sharding_key = "diversion_id"
        username = "default"
        password = ""
        node_free_password = true
        clickhouse_local_path = "/opt/software/clickhouse local"
        node_pass = []
    }
}

Running Command
./bin/start-seatunnel-spark-3-connector-v2.sh --master yarn --deploy-mode cluster --config config/hive_to_ck_test.config

Error Exception
no error

Zeta or Flink or Spark Version
spark 3.2.4
Java or Scala Version
java 1.8
Screenshots

Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

如图中的每条数据一个mmap操作导致写入性能不太好

use mmap buffer can solve this issue

写2.3kw到data_local.log， 从原来的5小时变成4分钟。表象来看是一条数据初始化一个mmap带来的性能问题

原代码和修改后的代码做对比

@Hisoka-X  can i fix this issue

Sure! Looking forward your PR! @viverlxl

after fix this issue

2.3kw records generate data_local.log file is 4 minutes


Shutter / Cover displays wrong Position in HA

Hi there,
I´m quite new to HA. I´didnt find the issue yet, so hopefully you guys can help me.
I integrated my Meross Shutters in HA via the cloud and meross_lan integration. Problem:
The Position which is displayed in HA lovelace or directly at the entity is always wrong (not the same like in the Meross app or in the Homekit app on the iPhone, this is the real position).
I found out, that when i looked at the attribute of the Shutter (entity) there is always the correct positon displayed (Position Native).
In my case (shown on the picture) the shutter is fully closed.
How can i fix that?
Thanks a lot,
R1200G

Hello @R1200G,
Thank you for reporting this.
The native position reported in the attributes is, like you guessed, the position according to the hardware but, in my tests, this hardware position was always reporting either 0 (closed) or 100 (open) with no values in between.
Now, maybe things have changed through a recent firmware update but, nevertheless, the device cannot (or shouldnt be able to) report a correct position because it lacks any sort of sensor to read the effective actual position of the shutter.
These kind of devices usually estimate the position based on the 'time of run' and are prone to accumulating errors which are only resolved when they run to the end a couple of times.
This is how meross_lan itself calculates the emulated position in software but, of course, this estimate suffers a lot from latencies in communication expecially when you bind the device to meross_lan through HTTP (which is the only option if you still have your meross paired to the Meross App). If you instead bind the device to a local MQTT these latencies are greatly reduced and calculations can provide a better result even though I see this is not viable for many users (i.e. unbinding from the Meross App in order to bind to a local MQTT).
However, this 'software position' proved to work correctly for the same HTTP binding scenario for other users so I suggest you to try (or investigate) this:

when the shutter is closed (in real), start another 'close command' on HA so the shutter 'emulated' position could realign with the real value (i.e. move to 0 and stick there )
now, if this works, you should then have correct position reporting from now on in HA too
also, if not already, try to set the 'opening time' and 'closing time' for the device to the right amount. The values you set on the app should be correctly read by meross_lan (in the picture they are at 18.1 and 17.7 seconds so I guess you already set these accordingly but..). meross_lan uses these values to interpolate and estimate the actual position when the device moves. These values should be set a little larger (say 10%) than the real effective time of run in order for the algorithm to try to 'catch up' with the real position. Of course, the calculations will never be correct, and you will get and accumulate increasing errors if you start playing with the shutter opening and closing it several times around a mid position (i.e. never reaching the physical full open or close) but in real scenarios, shutters runs are most of the times full runs
if you observe the 'Position native' attribute is reporting a better estimate (like I said, this used to report only 0 or 100 even when the shutter was halfway) then I will happily update meross_lan to use this value instead of the software calculated one. Again, I'm pretty sure this native value is computed too, exactly the same as the meross_lan calculations, but maybe it is better!

Hello @krahabb,
thanks for your answer! Just a quick response tonight, i will try the rest tomorrow.
The roller shutter - position native - is always correct in my case. I observed this the last few days. I have another picture to show you. The - native position - is the same position as in real life, HomeKit and the Meross App.
I would really appreciate it if you could make an update.
If you need anything else from me or if I can help you please let me know [but im still a Newbie ;) ]

Hey @krahabb,
I did what you told me. I triggerd the shutter from HA, HomeKit and the Meross App. The - native Position - in HA was always the correct one (also in HomeKit and Meross App)
I logged the file. How can I send the file to you in a private message? I'm not sure if there are confidential / private data in the file.
Best regards,
R1200G

you can PM at<EMAIL_ADDRESS>

Thanks. I just sent you an email!
Please keep me updated.
I also tried your suggestion:

when the shutter is closed (in real), start another 'close command' on HA so the shutter 'emulated' position could realign with the real value (i.e. move to 0 and stick there )

But it did not work. Even if i pull the trigger to the 0 or 100 position on the slide bar.
Is there a way to choose which position value the slide bar should use to display the position? So that i could change it to the attribute: native position ?

Hello @R1200G,
I'm sorry for the late reply, I've already checked your log and it clearly shows the correct 'native' position exposed by the device so it is very easy to pick it up and show instead of the meross_lan own computed one.
Nevertheless, I have to make sure the update doesnt disrupt the existing 'emulated' position feature for (older) devices which dont expose the correct native position.
I guess I would be able to work on this and many other issues before or around christmas so I ask you to be a bit patient with my timing :)

Hello @krahabb
Thank you very much for your effort! I will test the new pre version you published.
I will let you know how it works. :)

hi @krahabb
I had exactly the same issue than @R1200G. I've replaced original files with those that you provided in 50fc90f and it works like a charm.
Thank you very much for the efforts!

Thank you very much for your confirmation, I'm going to close this :)


First call to process_action throws error when training with DQN agent

Describe the bug
When I attempted to train/fit the DQN agent model, when the DQN agent from keras-rl made the first call to the process_action it produced an error because legal_moves_limit was None. There is a check to see if the legal_moves_limit is defined, but not if it's got a None value.
To Reproduce
Steps to reproduce the behavior:

Run command "python main.py selfplay dqn_train -c --name=test"
File: agent_keras_rl_dqn.py
Line number: 210

Expected behavior
Player.process_action invocation should not throw when legal_moves_limit is None.
Screenshots
N/A
Additional context
N/A

787aaa1e523317bef7ec20dbdfabe144994636b4 fixes this


Create new repo for flask/react webpage

In order to keep things separate and organized, we should probably make a new webpage that has all the flask and server code, in other words, the front end.

Here's the new client repo: https://github.com/UWMRO/Instruments_Client

no longer needed


Implements the real world example

It could be great to have a full working real world example:

two web services
a compose file to run them as production
a compose file which use Smocker to mock one of them
venom tests

Done here https://github.com/smocker-dev/examples


CMake improvements

A couple quality-of-life improvements when building:

Autodetect the appropriate library directory name.
Silence a deprecation warning.

Changes look great. Thank you!


Bump to a Bundler 2 version

Now that we've branched 1-16-stable and the 2.0 milestone is nearly done, it's time that we target master to be Bundler 2.
Until Bundler 2 final is released, I'd like us to keep testing rudimentary 1.x support, to make backporting things to 1-16-stable easier, but I've severely cut down the matrix. I'm willing to take it upon myself that 1.x stable maintains esoteric Ruby/RubyGems version compatibility now, rather than requiring it from all those who try to contribute to the project (in reality, this just means fixing up 1-16-stable after back porting and before a release).
@bundler/core: 2.0 is finally happening!

:tada: @bundlerbot r+

@bundlerbot retry


added program to convert meters to miles in js

Why:
Closes #285

edited: point to the JS specific isse.

What's being changed:
Added JS program to convert meters to miles

Hey @victoriacheng15,
Thanks for the review. Should I close my pull request and redo it with a pull request from a separate branch? And when you say link to specific language, is that the closes hashtag285 tag?

Hey @victoriacheng15,
Thanks for the review. Should I close my pull request and redo it with a pull request from a separate branch? And when you say link to specific language, is that the closes hashtag285 tag?

Highly recommended starting over and create a branch. You could check out this blog for steps if you needed.
And yes, the 285 is the issue.
Let me know if I am not clear, or you have more questions. :D

Hey @MusabMuhie
Please comment !assign on #285 to be auto-assigned, to prevent any conflict
!assign

Thanks 👍🏻


The copilot can not answer the question about the pet shop

Hello,
The application has been deployed in my machine, and there was no error but  a few warning during deployment. I created a demo of  pet shop, and tryied to chat with the OpenPilot. When I asked some questions just like, what is the highest mountain in Earth, the copilot gave the answer quickly. But if I answer questions related to the pet shop, the response is a error message: Error sending the message, Shown as below.  And if I sent new message, there was no response. seems  one of components does'nt work.
Is there any tips for this issue?  Thanks a lot!
Environment:
Ubuntu 20.04.6 LTS
16G RAM
Docker 24.0.6

Question - After this happened, does the entire application dies (extremely slow requests) or just the chat bubble?

Seems the entire application does not work. There is no response when trying to refresh the page, until run 'make restart' .

Is there any updates on this issue,,, Thanks!

I believe this was fixed a while back, closing


pp needs to reject incorrect bookmark names

If a supposed bookmark name is passed to pp but it does not exist, then pp will only print a newline character for that bookmark name. An error should  be printed instead, and pp should return. This should be detected and reported before pp prints any bookmarks. It may be acceptable to print prior correct bookmarks (and simpler to implement), but this may be confusing behavior.

This is now a defunct UI concern. At present (v2.0.0), if pp fails the direct lookup, it tries regex lookup. pp should not complain if regex lookup fails and returns no results. In other words, pp cannot know that the user did not intend to use regex lookup.


Update jsOTP.js

escape() does not handle UTF-8 encoding properly, resulting in some counter values (i.e.: 128) not working.
Change deprecated escape function to encodeURIComponent();

Need to cancel this pull request - while the code functions (no longer errors), the hotp is not generating proper values for counter values >= 128.


A more coherent story for whitelisting.

r? @fitzgen
Fixes #300
Fixes #299
Fixes #298

@bors-servo r+

:pushpin: Commit 2fa8409 has been approved by fitzgen

:hourglass: Testing commit 2fa8409 with merge 5bac904...

:sunny: Test successful - status-travis


Fix download

Collect path is testdir/mnist/*.

Can @owulveryck and @mattn handle this?

I’ll merge it today.

Coverage remained the same at 64.156% when pulling 6ce69dd4d3d26390735f2d45ce537281c593cd6f on mattn:fix-download into bc51c8e06c81b4928759144c667c38462ff4a966 on gorgonia:master.

Coverage remained the same at 64.156% when pulling 6ce69dd4d3d26390735f2d45ce537281c593cd6f on mattn:fix-download into bc51c8e06c81b4928759144c667c38462ff4a966 on gorgonia:master.


KVM Service - CLI command for installation script generation

KVM Service
When a new workload is configured in kvmsoperartor, KVMService should be capable and must provision with downloading the installation script over CLI.
The implementation should be done with grpc.
Hence the download is supported by karmor CLI or by grpcurl.

https://github.com/kubearmor/KVMService/pull/7
Merged in above PR


On cygwin gcc version 12.4.0 constexpr dont compile

memory-latency.cpp:13:24: error: expected suffix identifier
   13 | auto constexpr operator"" _B(unsigned long long int n) { return n; }
      |                        ^~
memory-latency.cpp:18:29: error: unable to find numeric literal operator ‘operator""_B’
   18 | const auto kCachelineSize = 64_B;
memory-loads.cpp:345:23: error: ‘operator""_B’ was not declared in this scope; did you mean ‘operator""_M’?
  345 |   const auto offset = operator""_B(state.range(1));

I submitted a fix https://github.com/berestovskyy/applied-benchmarks/pull/4


Logical type UUID with type "fixed" do not serialize to fixed 16

Avro 1.12.0 specifies that UUID logical types annotates to either String or Fixed 16.
The example below serialized the UUID to a String and not a Fixed 16
#[derive(Debug, Serialize, Deserialize)]
struct Comment {
    id: Uuid,
}

impl AvroSchema for Comment {
    fn get_schema() -> Schema {
        Schema::parse_str(
            r#"{
                "type" : "record",
                "name" : "Comment",
                "fields" : [ {
                  "name" : "id",
                  "type" : {
                    "type" : "fixed",
                    "size" : 16,
                    "logicalType" : "uuid",
                    "name": "FixedUUID" // if we remove the name attribute schema parsing fail. The name attribute is not in avro 1.12.0 specification
                  }
                } ]
             }"#,
        )
        .expect("Invalid Comment Avro schema")
    }
}

let payload = Comment {
        id: "de2df598-9948-4988-b00a-a41c0e287398".parse().unwrap(),
};
let mut buffer = Vec::new();
SpecificSingleObjectWriter::<Comment>::with_capacity(10)
    .unwrap()
    .write_ref(&payload, &mut buffer)
    .unwrap();

Do you plan to support it in the near future?

I will try to take a look next week!
Any help is welcome! Providing a PR will make sure it is supported in nearest future! ;-)

Added the test case to the suite - https://github.com/apache/avro-rs/pull/55
It works just fine locally.
I guess it has been fixed with https://github.com/apache/avro-rs/pull/9

I had a look a the test you're added, it checks that it serializes successfully but doesn't check the payload content/size to validate that uuid is encoded as 16 bytes.
I just hex dump the content of your test, the payload length is 47 bytes instead of 26.
Why 26:

2 bytes of Avro marker
8 bytes of schema fingerprint
16 bytes for the uuid

In the actual 47 bytes, the UUID takes 37 bytes which is its number of characters.

This deserves a new issue.
The bug here is that AvroSchema derived Schema does not support logical types at all at the moment ...


generator: strip package name from receiver name

Quick fix for #844.

can you run go generate ./generator so that the template changes are included in the binary?

@casualjim Done.
What about adding actual stale file check to your ci? It'd be something like:
$ git diff HEAD~1
diff --git a/appveyor.yml b/appveyor.yml
index c072bad..6a03635 100644
--- a/appveyor.yml
+++ b/appveyor.yml
@@ -44,6 +44,10 @@ install:
   - go get -u gopkg.in/matm/v1/gocov-html
   - go get -u github.com/cee-dub/go-junit-report

+  # check for stale files
+  - go generate -v ./generator
+  - git diff --exit-code ./generator
+
 build_script:
   - cd %APPVEYOR_BUILD_FOLDER%
   - echo %PATH%
diff --git a/generator/shared.go b/generator/shared.go
index 81df7c3..38564ef 100644
--- a/generator/shared.go
+++ b/generator/shared.go
@@ -34,7 +34,7 @@ import (
        "golang.org/x/tools/imports"
 )

-//go:generate go-bindata -pkg=generator -ignore=.*\.sw? ./templates/...
+//go:generate go-bindata -mode 420 -modtime<PHONE_NUMBER> -pkg=generator -ignore=.*\.sw? ./templates/...

 // LanguageOpts to describe a language to the code generator
 type LanguageOpts struct {

sure if you want to add by all means :)

@casualjim Please don't merge yet, testing if the check works.

@casualjim Ok, looks like .git directory is removed from go-swagger before install stage:
git diff --exit-code ./generator
Not a git repository
To compare two paths outside a working tree:
usage: git diff [--no-index] <path> <path>
Command exited with code 129

It'd require more work, for a separate PR - let's merge the fix first.

Current coverage is 69.28% (diff: 100%)

Merging #845 into master will not change coverage

@@             master       #845   diff @@
==========================================
  Files            21         21
  Lines          5863       5863
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           4062       4062
  Misses         1388       1388
  Partials        413        413

Powered by Codecov. Last update cfe9a99...80b5cc3

Previous fix was wrong, I've stripped package from wrong variable - it should be GoType instead.
How to best add a test for building fixtures/codegen/issue844.json?

@rjeczalik you can do so by adding a (unit) Test function named TestIssue844 in https://github.com/go-swagger/go-swagger/blob/master/generator/model_test.go. There you can load the spec file, which it should be able to load without any errors. After that you could, if applicable, also test specifics. In the model_test.go file you'll see other examples that could give you inspiration if needed.

Once you added the unit test @rjeczalik, you'll have to also fetch & rebase the latest master branch into your personal feature branch. You can resolve the conflict of generator/bindata.go, simply by generating a new one yourself, which contains both the latest templates (which you've just fetched & rebased) and your changes already committed in this PR.
Once that's done this PR is good to go :)

I've added a test that generates a client and then tries to build it. The test currently fails due to a different problem:
--- FAIL: TestGenerateAndBuild (0.28s)
    --- FAIL: TestGenerateAndBuild/issue_844 (0.28s)
        build_test.go:40: go get ../fixtures/bugs/844/generated398758314/...: exit status 2
                # github.com/go-swagger/go-swagger/fixtures/bugs/844/generated398758314/client/operations
                ../fixtures/bugs/844/generated398758314/client/operations/get_responses.go:117: o.Foo.Validate undefined (type models.Foo is interface with no methods)
                ../fixtures/bugs/844/generated398758314/client/operations/get_responses.go:121: o.Bar.Validate undefined (type models.Bar is interface with no methods)

Indeed the generated models lack a Validate method. Not quite sure it's a regression, as every other test passes:
$ go test -run -TestGenerateAndBuild
PASS
ok      github.com/go-swagger/go-swagger/generator      0.197s

Probably we'd want to have this problem also fixed before merging, so we do not have a broken master.

I've added a test that generates a client and then tries to build it. The test currently fails due to a different problem:
--- FAIL: TestGenerateAndBuild (0.28s)
    --- FAIL: TestGenerateAndBuild/issue_844 (0.28s)
        build_test.go:40: go get ../fixtures/bugs/844/generated398758314/...: exit status 2
                # github.com/go-swagger/go-swagger/fixtures/bugs/844/generated398758314/client/operations
                ../fixtures/bugs/844/generated398758314/client/operations/get_responses.go:117: o.Foo.Validate undefined (type models.Foo is interface with no methods)
                ../fixtures/bugs/844/generated398758314/client/operations/get_responses.go:121: o.Bar.Validate undefined (type models.Bar is interface with no methods)

Indeed the generated models lack a Validate method. Not quite sure it's a regression, as every other test passes:
$ go test -run -TestGenerateAndBuild
PASS
ok      github.com/go-swagger/go-swagger/generator      0.197s

Probably we'd want to have this problem also fixed before merging, so we do not have a broken master.

@rjeczalik I think your test file triggered a bug in the current generator code already on master.
The template responsible for your non-compiable code can be found here: https://github.com/go-swagger/go-swagger/blob/master/generator/templates/schemavalidator.gotmpl#L251
The appropriate fix would probably be to ensure that we don't try to validate in case it's an interface. So within that range you're probably missing an if/conditional check to ensure it's indeed not an interface or I suppose it's called discriminator in Swagger/OpenAPI terms.
Would be cool if you could fix this alongside your other commits within this PR.
Also don't forget to rebase origin/master into your branch.

Also don't forget to rebase origin/master into your branch.

Already rebased.

Would be cool if you could fix this alongside your other commits within this PR.

Sure, will take a look.

@GlenDC Fixed, please take a look.

Thank you for the extra effort @rjeczalik, very much appreciated.

@GlenDC You're welcome :-)


Language Server Initialization failure when opening single file with no workspace

VSCode Version: Code 1.11.2 (6eaebe3b9c70406d67c97779468c324a7a95db0e, 2017-04-13T07:56:42.517Z)
OS Version: Darwin x64 16.5.0
Extensions:

Extension
Author
Version

quokka-vscode
WallabyJs
1.0.28

vscode-eslint
dbaeumer
1.2.8

tslint
eg2
0.12.0

Go
lukehoban
0.6.59

debugger-for-chrome
msjsdiag
3.0.1

vetur
octref
0.6.3

java
redhat
0.2.1

vscode-icons
robertohuertasm
7.6.0

sass-indented
robinbentley
1.4.1

language-stylus
sysoev
1.6.0

vim
vscodevim
0.6.20

So I'm working on this vue extension https://github.com/octref/vetur that includes a language server.
And someone reported: https://github.com/octref/vetur/issues/160
Repro:

Install vetur: https://marketplace.visualstudio.com/items?itemName=octref.vetur
Open a new, workspace-less window of VSCode
Open a single vue file from it

Then it throws
[Error - 10:12:38 PM] Server initialization failed.
  Message: Request initialize failed with message: Cannot read property 'substr' of null
  Code: -32603

I don't quite know why it's happening, as I'm using the same LS Client initialization as extensions/html (minus telemetry). When opening a workspace with vue files it works fine.
vetur: https://github.com/octref/vetur/blob/master/client/src/htmlMain.ts#L11-L42
extensions/html: https://github.com/Microsoft/vscode/blob/master/extensions/html/client/src/htmlMain.ts#L28-L58
My guess is this is related to VSCode is activing LS Client/Server differently when opening single files. So how is it different and how can I avoid this crash?
Meanwhile, is there anyway to launch LS Client with extensionHost for debugging, but open a VSCode instance with no workspace?
/cc @dbaeumer @aeschli

@octref the protocol defines that if a single file is opened the rootPath or rootUri property on the initialization data is set to null. I guess that the server you are using is not handling this case correctly and tries to substr on rootPath hence the initialization fails.
Regarding debugging: if you start the extension using the normal VS Code extension debugging support then the server is started in debugging mode as well. So you should be able to attach to the server. You can change the config if you want to start the server in break mode by doing something like this:
let debugOptions = { execArgv: ['--nolazy', '--debug-brk=6005'] };

Assigning to @aeschli to comment on whether the htmlServer needs a rootPath.

Tracked it down. Thanks @dbaeumer .

But regarding debugging, how do I change the setting so I can start the instance in no-workspace mode? Cmd+Shift+N opens another window in the normal, not debugging mode.

@bpasero how can I start extension development on an instance with no workspace?

@dbaeumer you can pass "-n" from the launch config or "File > Close Folder" in that instance.


Implement tags query language

A new "tags query language" is being implemented in metrics: https://issues.jboss.org/browse/HWKMETRICS-523
It will be used here in Grafana. Tasks list:

[x] Connection to the new metrics endpoint.
[x] Re-design the UI to allow search by metric name AND to enter tags at the same time. Having tags will refine the metric names auto-completion.
[x] Create a "builder" UI for the new tags query language, using Grafana segments.
[x] Provide tag suggestions on tag names.
[x] Allow to switch to plain text mode for tags QL.
[x] Capabilities: keep the key-value pairs system for metrics < 0.24.0.
[x] Update documentation (README)
[ ] Update documentation (website)
[x] Wait for the language to be stabilized on metrics server side

Note I'll update the website once this is merged here


v1.1.X removes -webkit-box-orient from the css

Hi!
Short description of the problem:
If you use the CSS property -webkit-box-orient, it is removed in the build. It worked well in v1.0.x
What behavior are you expecting?
The build should have this property.
.three_lines {
    overflow: hidden;
    display: -webkit-box;
    -webkit-line-clamp: 3;
    -webkit-box-orient: vertical;
}

Which @ionic/app-scripts version are you using?
v1.1.4
The same issue was rejected in ionic repository: https://github.com/driftyco/ionic/issues/10723
Thank you very much!

Yes? i'm not work to scss
  .pod_c {
    white-space: pre-line;
    overflow: hidden;
    text-overflow: ellipsis;
    display: -webkit-box;
    -webkit-line-clamp: 2;
   -webkit-box-orient: vertical;
   vertical-align: middle;
   font-size: 0.7em;
  }

Same here. And can't find another solution to have same behaviour other than wrapping text previously  to be shown what i am not confortable with

another duplicate https://github.com/driftyco/ionic-app-scripts/issues/869

+1 one for this - it simply removes "-webkit-box-orient: vertical;" from css

I was able to properly fix this by specifying my own css.config.js:
module.exports = {

  autoprefixer: {
    remove: false
  },
};

And pointing to it in package.json:
  "config": {
    "ionic_sass": ".sass.config.js"
  },

See this and this for more details

thansk )))

close team please

Nice workaround @aspidvip ! Thanks!

@vhinic thanks for u ,solve my problem 👍


Resources Worth Looking At

Great to see you guys undertake this project, would be nice to have a well maintained lib for these applications.
I am not sure if you are aware of some similar applications and libs, since you didn't mention them in your paper. But here are some refs that might be useful for you.
Anthony worked on some stuff regarding function approximation with adaptivity in both sparsity of cores and the tensor network structure: https://arxiv.org/abs/1912.07913
You can find more recent stuff here: https://anthony-nouy.github.io/publications.html
And he has a python lib implementing this, though I don't know how well maintained: https://anthony-nouy.github.io/tensap/
Might be helpful to consider some of the ideas or features for itensor NA.

Hi @MazenAli !
We are excited about the possibilities this library offers.
Thank you for making us aware of those references and that library, those will be helpful for us and could inspire us for certain features or ideas for iTensor NA.

Hi all,
I confirm that the library tensap is still maintained.
For related references on multivariate functions approximation using tree tensor networks, i suggest

https://arxiv.org/abs/2007.01165 (theoretical results for supervised and unsupervised learning and model seelction strategy for ranks and trees). The minimax results for a large class of function classes are based on the following works with Mazen Ali. We have results for full or sparse cores.
-https://arxiv.org/abs/1811.04455,  https://arxiv.org/abs/1912.07913 (learning algorithms, possibly exploiting sparsity of cores)
https://link.springer.com/article/10.1007/s00365-023-09620-w, https://arxiv.org/abs/2101.11932, https://arxiv.org/abs/2112.01474 (Approximation theory, analysis of approximation classes and convergence rates for a large class of smoothness classes)
https://arxiv.org/abs/1705.00880, https://arxiv.org/abs/2104.13436 (active learning based on SCD/PCA)
Best regards
https://arxiv.org/abs/2310.08942 (some theoretical results on tensor formats with sparse cores)


Noutmutation

Wip
Fixes #2 and will fix #3

Codecov Report

Merging #4 into master will decrease coverage by 10.71%.
The diff coverage is 88.46%.

@@             Coverage Diff             @@
##           master       #4       +/-   ##
===========================================
- Coverage     100%   89.28%   -10.72%
===========================================
  Files           2        3        +1
  Lines          13       28       +15
===========================================
+ Hits           13       25       +12
- Misses          0        3        +3

Impacted Files
Coverage Δ

src/NaiveGAflux.jl
100% <ø> (ø)
:arrow_up:

src/mutation.jl
100% <100%> (ø)
:arrow_up:

src/util.jl
84.21% <84.21%> (ø)

Continue to review full report at Codecov.

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


Document 9.0-ea3 changes

Kerberos

@jmakeig you can find info about 9.0-ea3 changes (and 9.0-ea4 changes) here:
engsvn/engweb/specifications/functional/b9_0/Nodejs_Client_API
Let me know if you need anything else from me and close this if the above is sufficient.

Can this be closed?


chore: sanitize the .NET codebase (a little)

Configured a bunch of Roslyn analyzers to ensure code quality, and made the necessary corrections:

Correct usage of ArgumentException
Use Array.Empty<T>() to spare allocations of empty objects
Override equality on data types
Specify InvariantCulture where needed (could be the source of weird bugs)
Some other miscellaneous tweaks

Additionally, folded all the contents of Amazon.JSII.JsonModel under the Amazon.JSII.Runtime
assembly, and issued type frowards in Amazon.JSII.JsonModel to maintain backwards compatibility.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: d4a32ed64c48f755838ac0572f1ca627877b8ede
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 9b36883ceeb9405ccaf9e7abb9d7f7afb470bab9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: a7422fe11f4ccb7f79deb735c113adda152bf332
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: edc62faf3ddc98f233548f6ca79de426f2cc98d1
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 87563c341d4205a9a487dd397f83a4afc07438d9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Incorporate OpenSHA refactoring to use new FaultSection interface

I just merged in a massive OpenSHA refactor to remove dependence on the FaultSectionPrefData object. That has been replaced with a new FaultSection interface. This will allow you to create your own subduction representation, with whatever rupture surface you require (i.e., it no longer necessitates StirlingGriddedSurface). You can now also mix representations within a single FaultSystemRuptureSet. Once you pull the changes to the OpenSHA repositories, there will surely be some errors that need fixing in your code. Let me know if you have any questions. I can explain more when we talk next week, and will hopefully have some ideas on down-dip-subsection support.

Thanks @kevinmilner - this sounds greats. We have some rudimentary tests that might be impacted by this, it'll be very interesting to explore - cheers.

@kevinmilner new zoom link
Please download and import the following iCalendar (.ics) files to your calendar system.
Weekly: https://us02web.zoom.us/meeting/tZcpdO2trj8oHdZdQJ_4dPbDzmkwnJZK9u5c/ics?icsToken=98tyKuGrqjguH9SRsh6FRpwqBojCLO_ziClBgqdnmC7PPHRXUgHSLO9JJbxVKvOJ
Join Zoom Meeting
https://us02web.zoom.us/j/83434504272?pwd=YUhxcHdsZ21nbElERk80dVJUeG5SQT09
Meeting ID: 834 3450 4272
Password: 108313

Hi @kevinmilner
I've pushed some exploratory tests that I'd like to look at tomorrow, most especially  InterfaceFaultSectionTest.java

using this freshly minted csv data:  patch_4_10.csv
Right now we have sets that load this data as FaultSection objects, but I'm unsure what's needed next...

@kevinmilner with the latest commit  we have the  RuptureGenerator test working with some minimal plausability config (no azimuth or coulomb filtering) . We'll pause now  until we have your mods to support subduction tile layouts.


add rocketMq message gray plugin

What type of PR is this?
Feature.
What this PR does / why we need it?
During gray deployment, gray instances need to consume or produce gray messages.
Which issue(s) this PR fixes？
Fixes https://github.com/sermant-io/Sermant/issues/1539
Does this PR introduce a user-facing change?
No

Describe your core logic of this feature as list

Core logic:
If the current instance service_meta matched serviceMeta config or current thread traffic tag matched trafficTag config, current instance mark as gray instance, or is base instance.
1、produce message
If current instance is gray, during produce message, set trafficTags in the message property.
2、consume message
gray instance
Only consume contains current consumerGroupTag corresponding traffic tags message.
base instance
auto model:
First, exclude consumerGroupTag corresponding traffic tags message that set in excludeGroupTags, dynamically querying whether there are new gray consumer group consume message, if have, exclude corresponding traffic tags message.
base mode:
Exclude consumerGroupTag corresponding traffic tags message that set in excludeGroupTags, if excludeGroupTags not set, then consume all message.


Add support for wedgies

You can hide them by default if wedgies take up too much space, but it would be nice to see a canonical form that doesn't depend on aesthetic choices for the basis.
Bonus points if you can search by wedgie too.

I don't think the added complexity of importing a bunch of exterior algebra is worth the payoff here. Plucker coordinates aren't that hard to implement but I don't think they should be shown to users, nor do they provide any computational benefit.


is there a button element?

is there a button element? if not can i somehow insert an element ui standard button inside the ncform layout?
thanks

Refer to Custom form widget or the ncform-demo


Add netty and netty-all to dependency list

Similar to #80. A dependency is using a class from netty or netty-all that we're not including in the uber jar. This is causing a ClassDefNotFound. (Note: in shadowjars we need to include transitive dependencies explicitly. Both netty and netty-all are transitive dependencies.)

@jdmaguire what class was missing?


Create New contact us page or redesign current page

I'm up for this! Can I take this over?

I found the layout breaks here and there. I'll get working on it!

Thankyou so much please dont fork master please work on development 1.0 it will be easy and will not give us conflict..im soory i didn't tell you soon as..i was


Update to latest lib best-practice

Hint: the README.md needs to be adopted - just noticed that!

Besides the typeof which is acceptable IMO, I think I fixed all points incl. the formatting issues which were in already before (CRLF line endings?!) - thanks to prettier! 😄

Last comment: even if we rollback the types as you suggest, @akudev - this doesn't fix the issue and still if the typeof isn't present the following error occurs:
ERR! builder:customtask:ui5-tooling-transpile /resources/ui5/ecosystem/demo/tslib/Example.ts(60,9): error TS7056: The inferred type of this node exceeds the maximum length the compiler will serialize. An explicit type annotation is needed.


Parse error with an 'override' variable

Bug Report

🔎 Search Terms
override
🕗 Version & Regression Information

This changed between versions <4.2.3 and 4.3.*

⏯ Playground Link
Playground link with relevant code
💻 Code
const override = 4;
const a = (override as any); // <-- error; typescript thinks it's an unfinished arrow function
const overridex = 4;
const x = (overridex as any);
🙁 Actual behavior
TypeScript thinks it's an unfinished arrow function
🙂 Expected behavior
The code should not produce any error.

Ugh - the same is true of (at least) readonly, declare, and abstract.

Duplicate of https://github.com/microsoft/TypeScript/issues/44466.


Suggeston: Bandcamp ripper

Hi!
It will be fine to having a bandcamp.com ripper to allow download mp3 from albums. ;)
Thanks!

Links ?

E.g. one album:
https://losultimosbanistas.bandcamp.com/album/expedici-n-lp-2015
The audio files can be downloaded by Video DownloadHelper, but only a file after other.
;)

FWIW, youtube-dl can get Bandcamp albums and weeklies, at least.

Great news!! I did't know that.
Thank you! ;)

Tracking request in #38


Add graceful error messages when sending mail

Short description

Display a graceful error message instead of Internal Server Error when failing to send mail.
Proposed changes

Catch multiple types of exceptions

BadHeaderError (was already there, now giving slightly more context)
SMTPAuthenticationError (special SMTPException)
SMTPException
ConnectionRefusedError

Every exception gets the same base message that already existed, with a brief hint on what the actual problem is. This might make them more content (they get a feeling of knowing what's wrong, not only that something is wrong) and possibly speed up the investigation process when they report it.

Side effects

Only a few hours ago I claimed I would be focusing on Reviews and not submit any new PRs for now. With this I kinda loose credibility, don't I? :sweat_smile:
Code should be fine

Resolved issues

Fixes: #2046

Pull Request Review Guidelines

I think it would make more sense to move the try-except block into /integreat_cms/cms/utils/email_utils.py, because then the error handling could also be used for the password reset.

Funny you should mention that, Ingo and I went back and forth about this for a while, but finally opted to leave it one step higher in the call stack because we would have to pass request and debug_mail_type in there and were unsure whether this is valid in all uses of this utility function. E.g. we could imagine a cron job or management command using that. But you can probably shine a light on whether this poses a problem or not.

Funny you should mention that, Ingo and I went back and forth about this for a while, but finally opted to leave it one step higher in the call stack because we would have to pass request and debug_mail_type in there and were unsure whether this is valid in all uses of this utility function. E.g. we could imagine a cron job or management command using that. But you can probably shine a light on whether this poses a problem or not.

Ah, sorry, I missed that it created quite a few problems to pass the request object to the util function (I think debug_mail_type is irrelevant since the user knows what type of email they were just sending, so I think it's not required to add that info if it's too complicated). I agree that it makes sense to keep the util function agnostic of the http request.
Ok, now thinking about it, I guess we need to add another try/except block in the password reset view here:
https://github.com/digitalfabrik/integreat-cms/blob/7a8fda13ca5b35a90c79077174335e01c87beb2d/integreat_cms/cms/views/authentication/password_reset_view.py#L82
something along the lines of:
try:
    return super().form_valid(form)
except RuntimeError as e:
    messages.error(request, e)
    return redirect("public:password_reset")

Also, to de-duplicate all the different exception messages, I think it would be fine to catch and unify these in the email utils, and just raise one type of error (e.g. RuntimeError) there, and then catch the runtime error in both the password reset view and the welcome/activation mail view.

I implemented it for the password reset view, but when testing I wondered whether this is actually what we want. The success message always says "if an account for that email exists…", but the error message will only appear if we actually send an email. The relevance of this is probably very low, but I can't help but wonder how the proper solution for this should actually look like

Thanks! This is exactly how I had envisioned it. It is intended that we don't show an error for non-existing emails to make it harder to brute-force registered email addresses.
After fixing the two remaining small suggestions and cleaning up the git history, I think this is ready to be merged! :+1:

It is intended that we don't show an error for non-existing emails to make it harder to brute-force registered email addresses.

But now one can still brute-force for registered email addresses if there is a system configuration error or the email server is unreachable, since those errors will only occur for actual email send attempts, correct? Though it is not really a regression to the HTTP 500 thrown before, it does now explicitly state that trying to send the email was what caused a problem.

But now one can still brute-force for registered email addresses if there is a system configuration error or the email server is unreachable, since those errors will only occur for actual email send attempts, correct?

Ok true, though I think we can live with this :smiling_face_with_tear:

In that case, it's easiest to squash it all together, since the translations and release notes are also relevant to the password reset form

In that case, it's easiest to squash it all together, since the translations and release notes are also relevant to the password reset form

I agree.


Unit testing custom AuthenticationHandler

I'm trying to port my HMAC authenticator to ASP.NET Core but I'm having trouble producing some unit tests for the authentication handler.
I know I can produce integration tests using TestServer etc but these seems overkill without being able to unit test the actual handler?
My problem is that the HandleAuthenticateAsync is never called - which means I've got the setup wrong but I couldn't find any appropriate examples.
Code is as follows...
public class HmacAuthenticationHandler : AuthenticationHandler<HmacAuthenticationOptions>
{
	private readonly IHmacAuthenticator authenticator;

	public HmacAuthenticationHandler(IHmacAuthenticator authenticator, IOptionsMonitor<HmacAuthenticationOptions> options, ILoggerFactory logger, UrlEncoder encoder, ISystemClock clock) :
		base(options, logger, encoder, clock)
	{
		this.authenticator = authenticator;
	}

	protected override async Task<AuthenticateResult> HandleAuthenticateAsync()
	{
		// Do we have authorization
		if (!AuthenticationHeaderValue.TryParse(Request.Headers["Authorization"], out var authorization))
		{
			//Invalid Authorization header
			return AuthenticateResult.NoResult();
		}

		if (authorization.Scheme != HmacAuthentication.AuthenticationScheme)
		{
			Logger.LogDebug("Not HMAC authenticated");
			// Not our scheme, so ignore
			return AuthenticateResult.NoResult();
		}

		if (string.IsNullOrEmpty(authorization.Parameter))
		{
			// Authentication was attempted but failed. Set ErrorResult to indicate an error.
			Logger.LogWarning("Missing credentials");
			return AuthenticateResult.Fail("Missing credentials");
		}

		var httpRequest = new HttpRequestMessageFeature(Context);
		var identity = await authenticator.Authenticate(httpRequest.HttpRequestMessage);
		if (identity == null)
		{
			// Authentication was attempted but failed. Set ErrorResult to indicate an error.
			Logger.LogWarning("Invalid signature");
			return AuthenticateResult.Fail("Invalid signature");
		}

		var principal = new ClaimsPrincipal(identity);

		var ticket = new AuthenticationTicket(principal, Options.Scheme);

		return AuthenticateResult.Success(ticket);
	}

	protected override async Task HandleChallengeAsync(AuthenticationProperties properties)
	{
		Response.Headers["WWW-Authenticate"] = $"HMAC {Options.Scheme}";
		await base.HandleChallengeAsync(properties);
	}
}

And the test is...
[TestFixture]
public class HmacAuthenticationHandlerFixture
{
	[Test]
	public async Task NoAuthenticationHeader()
	{
		// Arrange
		var logger = new Mock<ILogger<HmacAuthenticationHandler>>();
		var loggerFactory = new Mock<ILoggerFactory>(MockBehavior.Strict);
		loggerFactory.Setup(x => x.CreateLogger("Meerkat.Security.Authentication.HmacAuthenticationHandler")).Returns(logger.Object);

		var encoder = new Mock<UrlEncoder>();
		var clock = new Mock<ISystemClock>();

		var options = new HmacAuthenticationOptions();
		var om = new Mock<IOptionsMonitor<HmacAuthenticationOptions>>(MockBehavior.Strict);
		om.Setup(x => x.Get(HmacAuthentication.AuthenticationScheme)).Returns(options);

		var authenticator = new Mock<IHmacAuthenticator>(MockBehavior.Strict);

		var handler = new HmacAuthenticationHandler(authenticator.Object, om.Object, loggerFactory.Object, encoder.Object, clock.Object);

		var context = new DefaultHttpContext();
		var request = new DefaultHttpRequest(context);

		// Act
		await handler.InitializeAsync(new AuthenticationScheme(HmacAuthentication.AuthenticationScheme, HmacAuthentication.AuthenticationScheme, typeof(HmacAuthenticationHandler)), context);
	}
}

What code did you expect to call HandleAuthenticateAsync? Working at this level you need to call that directly in your tests.

@Tratcher I presumed the InitializeAsync would call it from the method description, also HandleAuthenticateAsync is protected so it's slight difficult to invoke from a test.
Is the intent just to perform integration tests?

Ah, right, the public method is AuthenticateAsync:
https://github.com/aspnet/Security/blob/beaa2b443d46ef8adaf5c2a89eb475e1893037c2/src/Microsoft.AspNetCore.Authentication/AuthenticationHandler.cs#L130
We usually do integration tests since the flow for most of our providers requires multiple requests (OAuth, OIDC).

We kind of cheat, spinning up a test server in memory, and then plumbing in the auth handler, so we can test responses.
https://github.com/blowdart/idunno.Authentication/blob/master/test/idunno.Authentication.Test/BasicAuthenticationTests.cs has some examples, take a look at CreateServer()

Thanks for the response guys, now working


Back button - pass full sentence

Requirements

Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
All new code requires tests to ensure against regressions

allow to pass full translated sentence instead of leaving the concatenation to component
Description of the Change
Instead of concatenating the "back to" and "previous page" by default allow to pass full sentence
Benefits
This will work in every language we want
e.g: French
Possible Drawbacks
None
Applicable Issues
e.g: in french it would be 'Retour à la "page précédente"' but we will also have 'Retour à la "Lorem Ipsum"' if we keep it that way

As we plan to introduce a BREAKING CHANGE, maybe we can consider taking into account  following Deprecated notice.
$ git grep -i "deprecated" -- './packages/*' ':!*.md'
packages/base/core/src/less/icons.less:// Deprecated: Support for renamed/duplicate classnames below
packages/base/core/src/less/icons.less:@oui-icon-deprecated:
packages/base/core/src/less/icons.less:#oui > .icon-content(@oui-icon-deprecated);
packages/components/badge/src/less/badge.less:.oui-status, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  .oui-icon-external_link, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:.oui-button_full-width, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  &.oui-button_icon-right .oui-icon-external_link, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  .oui-icon-external_link, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:.oui-button_small-width, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:.oui-button_large-height, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  &.oui-button_small-width, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  &.oui-button_large-height, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  &.oui-button_small-width, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  &.oui-button_large-height, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  &.oui-button_large-height, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  &.oui-button_small-width, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  &.oui-button_large-height, /* Deprecated: Support for old classname */
packages/components/checkbox/src/less/checkbox-thumbnail.less:.oui-checkbox_thumbnail-light, /* Deprecated: Support for old classname */
packages/components/chips/src/less/chips.less:  &_full-width, /* Deprecated: Support for old classname */
packages/components/datagrid/src/less/_mixins.less:      &_sortable-asc, /* Deprecated: Support for old classname */
packages/components/datagrid/src/less/_mixins.less:      &_sortable-desc, /* Deprecated: Support for old classname */
packages/components/datagrid/src/less/_mixins.less:      &_sortable-asc, /* Deprecated: Support for old classname */
packages/components/datagrid/src/less/_mixins.less:      &_sortable-desc, /* Deprecated: Support for old classname */
packages/components/navbar/src/less/navbar.less:      &.oui-icon-info_circle, /* Deprecated: Support for old classname */
packages/components/navbar/src/less/navbar.less:      &.oui-icon-success_circle, /* Deprecated: Support for old classname */
packages/components/navbar/src/less/navbar.less:      &.oui-icon-warning_circle, /* Deprecated: Support for old classname */
packages/components/navbar/src/less/navbar.less:      &.oui-icon-error_circle, /* Deprecated: Support for old classname */
packages/components/radio/src/less/radio-thumbnail.less:.oui-radio_thumbnail-light, /* Deprecated: Support for old classname */
packages/components/tile/src/less/tile.less:      .oui-icon-external_link, /* Deprecated: Support for old classname */

Or another option is that we can keep both backTo and previousPage and make them as deprecated.
And handle to translation issue with a new attribut/binding.
Please let me know what do you think.

As we plan to introduce a BREAKING CHANGE, maybe we can consider taking into account following Deprecated notice.
$ git grep -i "deprecated" -- './packages/*' ':!*.md'
packages/base/core/src/less/icons.less:// Deprecated: Support for renamed/duplicate classnames below
packages/base/core/src/less/icons.less:@oui-icon-deprecated:
packages/base/core/src/less/icons.less:#oui > .icon-content(@oui-icon-deprecated);
packages/components/badge/src/less/badge.less:.oui-status, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  .oui-icon-external_link, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:.oui-button_full-width, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  &.oui-button_icon-right .oui-icon-external_link, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  .oui-icon-external_link, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:.oui-button_small-width, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:.oui-button_large-height, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  &.oui-button_small-width, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  &.oui-button_large-height, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  &.oui-button_small-width, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  &.oui-button_large-height, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  &.oui-button_large-height, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  &.oui-button_small-width, /* Deprecated: Support for old classname */
packages/components/button/src/less/button.less:  &.oui-button_large-height, /* Deprecated: Support for old classname */
packages/components/checkbox/src/less/checkbox-thumbnail.less:.oui-checkbox_thumbnail-light, /* Deprecated: Support for old classname */
packages/components/chips/src/less/chips.less:  &_full-width, /* Deprecated: Support for old classname */
packages/components/datagrid/src/less/_mixins.less:      &_sortable-asc, /* Deprecated: Support for old classname */
packages/components/datagrid/src/less/_mixins.less:      &_sortable-desc, /* Deprecated: Support for old classname */
packages/components/datagrid/src/less/_mixins.less:      &_sortable-asc, /* Deprecated: Support for old classname */
packages/components/datagrid/src/less/_mixins.less:      &_sortable-desc, /* Deprecated: Support for old classname */
packages/components/navbar/src/less/navbar.less:      &.oui-icon-info_circle, /* Deprecated: Support for old classname */
packages/components/navbar/src/less/navbar.less:      &.oui-icon-success_circle, /* Deprecated: Support for old classname */
packages/components/navbar/src/less/navbar.less:      &.oui-icon-warning_circle, /* Deprecated: Support for old classname */
packages/components/navbar/src/less/navbar.less:      &.oui-icon-error_circle, /* Deprecated: Support for old classname */
packages/components/radio/src/less/radio-thumbnail.less:.oui-radio_thumbnail-light, /* Deprecated: Support for old classname */
packages/components/tile/src/less/tile.less:      .oui-icon-external_link, /* Deprecated: Support for old classname */

Or another option is that we can keep both backTo and previousPage and make them as deprecated.
And handle to translation issue with a new attribut/binding.
Please let me know what do you think.

@antleblanc Removing deprecated elements could be great but it won't be the same job to make apps compatible given the diff introduced
Moreover, making bindings deprecated could be a solution but it means that we can end up with lots of deprecate binding by fear of having a breaking change, I find it confusing and not great for Developer experience

@antleblanc As spoken and given the context the previous way as been deprecated instead of being removed


Change breeding harnesses to work on mooshrooms

Right now attempting to apply a breeding harness to a mooshroom converts it into a normal cow. Given the advantages of mooshrooms, however, this is not desirable behavior.

Done for 1.3.2


Acking a message after using basic_publish call

Hello,
I'm trying to publish a message via using basic_publish method of a channel, but can't figure out how to ack the already sent message (and retry a few times it if will be necessary).
The basic_publish method contains inside a small piece of code which is intended for desribing a state of the message, but used it only one time. Also, this method returns an Option as a result of sending a message, but doesn't returning any additional information about the message (for our case is delivery tag).
The following future I'm using for sending a message:
channel.basic_publish(
    &endpoint_publish.get_request_exchange(),
    &endpoint_publish.get_microservice(),
    message["content"].dump().as_bytes(),
    &publish_message_options,
    basic_properties
)
    .map(|_confirmation| channel)  // <-- return a channel for a further using

Current output in a console:
Listening on: <IP_ADDRESS>:9000
[2018-02-08][20:57:32][lapin_futures::channel][INFO] message with tag 1 still in unacked: {1}

Hi,
Either We're not speaking of the same thing, or the consumer has to ack the message, not the publisher

Probably it sounds interesting, but the message is acking when it comes. This is the code from my project
.and_then(move |(channel, message)| {
    let raw_data = from_utf8(&message.data).unwrap();
    let json = Rc::new(Box::new(json_parse(raw_data).unwrap()));
    let serializer = Serializer::new();
    let response = serializer.serialize(json.dump()).unwrap();
    transmitter.unbounded_send(response).unwrap();
    channel.basic_ack(message.delivery_tag)
        .map(move |_| channel)
})

Maybe the message wasn't acking as I'm doing here and necessary to do retries a couple of times?

Can you retry with current master?

@Relrin closing for inactivity, feel free to reopen if it's not fixed in the current release, but I'm pretty sure it is


bundled hooks customize errors

I can't find a way to do this in docs unless using my own middlewares.

I've been thinking of adding afterError hooks to feathers-hooks that would allow to post-process errors through services. Something like
const errors = require('feathers-errors');

app.service('messages').afterError({
  create(hook) {
    const originalError = hook.error;

    hook.error = errors.Conflict(originalError.message);
  }
});

Would that solve your problem as well?

@daffl but for now. this is no way to do this. I will wait.
I think there are different hooks for a hook. For example, verifyToken and restrictToRoles. If we use the way you said, we have to find what error it is. So, I think would it be better to pass a string or json to the function?
create: [authHook.verifyToken('No token')],

or
create: [authHook.verifyToken({errorMessage:"No token"})],

@colinshen I like that second syntax option. I think we definitely need something more like an afterError hook or a special bundled error handling hook as that is the more scalable option but supporting custom error messages might do in the near term.

If we are considering customizing the error messages we should support it everywhere (e.g. the database adapters etc.).

@daffl totally. Which is why I want to be lazy and not do that. 😝
In seriousness, I do think so. It is a lot of work but we need something to better handle errors in the hooks chain. Ideally I want something like the express error middleware, where you can chain together multiple error handling hooks to build up the error output you want.
So, if you wanted custom error messages you would check for the status code and modify as necessary.

So we had a revelation the other day. If you need custom conditions or custom errors you can simply wrap the hook in your own hook like so:
import { hooks } from 'feathers-authentication';

exports.hashPassword = function(options) {
  // Add any custom options

  function(hook) {
    return new Promise((resolve, reject) => {
      if (myCondition !== true) {
        return resolve(hook);
      }

      // call the original hook
      hooks.hashPassword(options)(hook)
        .then(hook => {
          // do something custom
          resolve(hook);
        })
        .catch(error => {
          // do any custom error handling
          error.message = 'my custom message';
          reject(error);
        });
    });
  });
}

Going to close this as this is the best solution. It's the most flexible and doesn't require any change to existing hooks.


Allow the discovery of Servers which are in the powered On state.

Proposed Changes
Currently we are not running the discovery of Servers which are already powered On. A new flag (--enforce-first-boot) has been introduced to enforce the discovery of already powered on Servers. The default of this flag is set to false.
Additionally if we encounter a Server with .spec.power == "" in the initial state, we mutate the Server spec to match the detected PowerState in the Servers status.
Also some sporadic test failures where addressed.
Fixes #103 #108

The sporadic issues in the controller suite seems to be fixed now. But there seems to be still an issue in the registry and agent tests. Somehow it looks like the registry server can't be started as (maybe) the port can't be allocated. 🤔


how to fix this...?

Short introduction to your problem.
Input code:
REM The code your entered in the input text area

Output code:
/* The code outputted by the script, 'none' otherwise */

Error:
/* Any error outputted by the page or the console, 'none' otherwise */

Hi, this issue is empty. Closing this, please resubmit with the fields filled out.