Doesn't work?

I have recommendations working, but not this extension's described behavior.
The most activity I could find in the Output logs for Extension Host is:
2024-10-23 14:49:49.656 [info] ExtensionService#_doActivateExtension Soulcode.vscode-unwanted-extensions, startup: true, activationEvent: 'workspaceContains:.vscode/extensions.json'

and that's it.
no errors as far as I can tell, and this extension doesn't have an output channel of its own.
I haven't debugged anything, but is there is a configuration that is needed? All I did was install the extension, and my extensions.json has comments (without the jsonc extension, because that's what VSCode does... break json conventions 😅 )

even if I remove the comments, I don't see any warning behavior with my installed unwantedRecommendations

I saw the screenshot in the README looked like windows -- maybe this extension doesn't work on *nix machineS?

I can "run" check for unwanted extensions:

but it also appears to do nothing

I found that if I switch to the pre-release version, there is an output channel, and I see the logs specified in code.

does this extension need to be promoted to stable release?

seems it still doesn't report anything unwanted.

I saw the screenshot in the README looked like windows -- maybe this extension doesn't work on *nix machineS?

Unsure if this is the problem currently and if *nix is supported. Lets verify that.
Could you maybe provide your .vscode/extensions.json? Thanks
I will try to look into this in the next days and extend the output channel information if possible.

yea,
here you go
{
  "recommendations": [
    "bierner.markdown-preview-github-styles", // Markdown Preview Github Styling
    "eamodio.gitlens", // GitLens
    "visualstudioexptteam.vscodeintellicode", // IntelliCode
    "typed-ember.glint-vscode", // Glint (Ember Template Types)

    // Includes
    // - syntax highlighting
    // - language server
    // - eslint
    // - stylelint
    // - prettier
    // - editorconfig
    //
    // https://marketplace.visualstudio.com/items?itemName=EmberTooling.emberjs
    "embertooling.emberjs",
    // But if someone removes one, just recommending the extension pack isn't enough to
    // recommend the individual extensions again
    "embertooling.vscode-ember",
    "lifeart.vscode-glimmer-syntax",
    "dbaeumer.vscode-eslint",
    "EditorConfig.EditorConfig",
    "esbenp.prettier-vscode",
    "stylelint.vscode-stylelint",

    // Warns if any of the below are present
    "Soulcode.vscode-unwanted-extensions"
  ],
  "unwantedRecommendations": [
    // None of these are particularly useful for Ember development
    "googlecloudtools.cloudcode", // Google Cloud Code
    "ms-kubernetes-tools.vscode-kubernetes-tools", // Kubernetes

    // out of date gjs and gts syntax highlighting.
    "chiragpat.vscode-glimmer",
    // old version of the language server built in to embertooling
    "lifeart.vscode-ember-unstable",
    // out of date fork for linkedin
    "suchitadoshi1987.vscode-ember-experimental",
    // out of date
    "dhedgecock.ember-syntax",
    // theme, unrelated to ember
    "jgibson.ember-color-theme",
    // don't use jest
    "Orta.vscode-jest"
  ]
}

@NullVoxPopuli okey, I extended the logging, I hope this will help us further identifying maybe the issue.
Can you make sure you run the extension on its latest version, which was just published: 1.2.1
https://marketplace.visualstudio.com/items?itemName=Soulcode.vscode-unwanted-extensions
It should then, show according logging details:

it looks like it does work, but is just very slow, and because I don't main vs code, I don't have it open long enough for the dialog to display

ah here is why:
Found configuration in file: <.pnpm>/node_modules/<project-a>/node_modules/<project-b>/node_modules/<project-c>/node_modules/<dependency-a>/.vscode/extensions.json
Found configuration in file: <repo>/libraries/<project-d>/node_modules/<dependency-a>/.vscode/extensions.json
Found configuration in file: <.pnpm>/node_modules/<project-a>/node_modules/<project-b>/node_modules/<project-e>/node_modules/<project-c>/node_modules/<dependency-a>/.vscode/extensions.json

Found 7133 recommended extensions defined in the configuration
Found 10 unwanted extensions defined in the configuration

So it seems like this plugin needs to exclude node_modules

@NullVoxPopuli There is already an exclude pattern, to ignore node_modules, but it somehow had a invisible character which broke it.
A new release (1.2.2) is getting deployed now. I hope this will solve your issues finally! Let me know!

it does! thank you!!

Thank you for your inputs and being patient.
Closing the issue, have fun! 🙏


wrong

ı couldnt install packgages. where am i make  mistake? I tried everything.

Can you be more specific?
Maybe see: https://flutter.dev/docs/get-started/test-drive


Dev/xygu/20220329/drawer flyout

GitHub Issue (If applicable): closes unoplatform/nventive-private#372
PR Type
What kind of change does this PR introduce?

Feature

What is the new behavior?
Add FlyoutPresenterStyles that enable gesture support for flyouts.
PR Checklist
Please check if your PR fulfills the following requirements:

[x] Tested code with current supported SDKs
[ ] Docs have been added/updated which fit documentation template. (for bug fixes / features)
[ ] Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
[ ] Wasm UI Tests are not showing unexpected any differences. Validate PR Screenshots Compare Test Run results.
[x] Contains NO breaking changes
[x] Updated the Release Notes
[x] Associated with an issue (GitHub or internal)

Other information
uno.ui version bumped due Manipulation events e.OriginalSource issue
Internal Issue (If applicable):

Can you add a documentation page as well, on how to use this?

@nickrandolph  @francoistanguay
Documentation: https://github.com/unoplatform/uno.toolkit.ui/blob/1133b416b259e34255f54f14750aaf89d1e2387a/docs/controls/DrawerFlyoutPresenter.md
The API looks fine to me, as it's only a style for an existing flyout, so all the existing interactions apply.

edit: multiline text fix & minor typo fix


Add assertion operator

Adds an assert operator. The assert expression evaluates to true if the assertion condition is true, and terminates the program with an AssertionError otherwise.
Example Usage:
|v: i32| assert(v == 0)

Looks great!

Thanks for looking at it!


Multi track file handling

When demuxing a multi-track file, I expect to be able to dump the packets returned from the Demuxer.packets_raw into a file and just play it. At the moment, this is not working for some kind of files (multi-track mp4 file for example).
The functionality should be the same of the command
ffmpeg -i input.mp4 -map a:0 -c:a copy output.aac

where 0 is the stream index.
I suspect there is still need to use a decoder, even though no re-encoding is performed.

This is wrong as you cannot do this operation, you either need to decode the data or mux it inside a proper format, such as AAC. For now only decoding is supported.


[Automation] Regenerate SDK based on typespec-python branch snake-case-naming-optimization

Regenerate SDK based on typespec-python branch snake-case-naming-optimization

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-inference


:lady_beetle: Don't set latest release when not publishing to GH

Changes

:lady_beetle: Don't set latest release when not publishing to GH

/kind bug
Fixes TBD

Sorry, for the empty PR. This is already in.
Closing...


need improve the arch image and make mirror site

i.copy.sh/arch/ i wanna this path as a squanshfs image to mount ,and make a mirror of v86 site.
and add network to arch linux
or make ?profile=linux3 add openssh (sftp is prefer )or dropbear.

Use this to build a small Linux image with openssh: https://buildroot.org/
The Arch Linux still supports networking, use the following commands: ifconfig enp0s5 down; rmmod ne2k-pci; modprobe ne2k-pci; ifconfig eth0 up; dhcpcd -w4 eth0


fix(i18n): fix wrong word in clock challenge & chinese

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Hey there,
Thanks for opening this PR. Changes to the challenge content for non-English challenges are done through our translation flow, not through GitHub.


Request for Python 3 support

Would be nice. Right now I'm hacking together a solution with use_2to3 and fixing things as they come up for me. Nothing systematic.
See also my comment here https://github.com/benanne/Lasagne/issues/23

Implemented in a4c318a8fa613311b5a1383aa241baafa755c974 (in master).  Let me know how it works for you.

Awesome, thanks, I will check it out and report back.


Update Typescript to 2.0

The soon-to-be-released v2.0 of TypeScript will bring a lot of new cool features. Cherry-picking the releases notes, I believe the apollo-client will especially benefit from the discriminated union types (https://github.com/Microsoft/TypeScript/pull/9163), the smarter flow analysis, and the explicit null and undefined checks.
This PR updates the Typescript compiler to use the v2.0-beta. There is one logic error detected by the new flow analysis:
106             result: action.result,
                               ~~~~~~

src/data/store.ts(106,28): error TS2339: Property 'result' does not exist on type 'QueryResultAction | QueryErrorAction | QueryInitAction | QueryResultClientAction | QueryStopActio...'.

I haven’t opt-in the strictNullChecks option as I’m not that comfortable with the code base, but it sure would be great if someone else could do it.

Thanks for doing this! I'll check it out sometime soon.

Will this in any way affect people who are using Apollo Client with Typescript 1.x?

No, not until the types definition file is modified. With this PR, it’s just the compilation-step analysis that is enhanced, but the .js and .d.ts builds are the same.

There is one logic error detected by the new flow analysis:

That's odd, since there is a result field on the QueryResultAction type..

Hum, after some investigations, I think this is an instance of https://github.com/Microsoft/TypeScript/issues/7719.

Looks good to go for me, gonna merge once the tests pass.


Recent regression: Some expressions are no longer differentiable.

Description
Recent toolchain updates have caused certain expressions to no longer be considered differentiable.
Steps to reproduce
Paste the code below into a single file, and compile.
import _Differentiation
import Foundation
public struct I: Differentiable
{
    public var c: L
    @differentiable(reverse)
    private var z: F {
        get {return self.c.m}
        set(newValue) {if let d = newValue.x {self.c.g = Double(d)}} // No longer differentiable.
    }
}
public struct L: Differentiable {
    @noDerivative
    public var m: F
    public var g: Double = 0
}
public struct F: Differentiable{public var x: Double?}

Expected behavior
The compilation process should complete successfully.
Environment

Swift compiler version info: The compilation succeeds on 2023-02-25 and earlier. It fails on 2023-03-07 and later. (Not sure about versions in between).
Xcode version info: 14.2
Deployment target: M1

cc @asl

Well, this is not quite a regression. We started to differentiate move and more correct. For example, we started to generate pullbacks for setters. And this exposed some unhandled cases here and there. In particular, here we started to differentiate the following setter:
// I.z.setter
sil private [ossa] @$s2nd1IV1z33_2A95E161367FEFD3E0203604752680EELLAA1FVvs : $@convention(method) (F, @inout I) -> () {
// %0 "newValue"                                  // users: %4, %2
// %1 "self"                                      // users: %12, %3
bb0(%0 : $F, %1 : $*I):
  debug_value %0 : $F, let, name "newValue", argno 1 // id: %2
  debug_value %1 : $*I, var, name "self", argno 2, implicit, expr op_deref // id: %3
  %4 = struct_extract %0 : $F, #F.x               // user: %5
  switch_enum %4 : $Optional<Double>, case #Optional.some!enumelt: bb2, case #Optional.none!enumelt: bb1 // id: %5

bb1:                                              // Preds: bb0
  br bb3                                          // id: %6

// %7                                             // users: %11, %8
bb2(%7 : $Double):                                // Preds: bb0
  debug_value %7 : $Double, let, name "d"         // id: %8
  %9 = metatype $@thin Double.Type                // user: %11
  // function_ref Double.init(_:)
  %10 = function_ref @$sSdyS2dcfC : $@convention(method) (Double, @thin Double.Type) -> Double // user: %11
  %11 = apply %10(%7, %9) : $@convention(method) (Double, @thin Double.Type) -> Double // user: %15
  %12 = begin_access [modify] [static] %1 : $*I   // users: %16, %13
  %13 = struct_element_addr %12 : $*I, #I.c       // user: %14
  %14 = struct_element_addr %13 : $*L, #L.g       // user: %15
  store %11 to [trivial] %14 : $*Double           // id: %15
  end_access %12 : $*I                            // id: %16
  br bb3                                          // id: %17

bb3:                                              // Preds: bb2 bb1
  %18 = tuple ()                                  // user: %19
  return %18 : $()                                // id: %19
} // end sil function '$s2nd1IV1z33_2A95E161367FEFD3E0203604752680EELLAA1FVvs'

And it turned out, that Double.init(_:) is not differentiable :)

I'll call it a "recent observation", then. :) Thanks!


Custom plugin

Browser: Latest Chrome
OS: Windows 10
Clappr Version: latest
Steps to reproduce:

writed plugin
added to player
I was expecting button shown but instead it's not

Did you try to reproduce this issue at http://cdn.clappr.io/: yes, not showing
Source: https://pastebin.com/xDw0rzq6

I'll wait for new updates. Btw where do I put the setTimeout function? Tried in render and attachButton but it didn't work.

@pdtan did you ever figure this out?  I'm trying to do the same thing.


Race condition among Helm Charts

Describe the bug
When installing compliantkubernetes-apps a race condition occurs among Helm Charts that prevents some apps from being installed, namely: user-grafana, dex and opendistro-es.
  Installing it now.
==> amazon-ebs:   Error: Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post https://ingress-nginx-controller-admission.ingress-nginx.svc:443/extensions/v1beta1/ingresses?timeout=30s: dial tcp <IP_ADDRESS>:443: connect: connection refused
==> amazon-ebs: exit status 1
==> amazon-ebs: Provisioning step had errors: Running the cleanup provisioner, if present...
==> amazon-ebs: Terminating the source AWS instance...
==> amazon-ebs: Cleaning up any extra volumes...
==> amazon-ebs: No volumes to clean up, skipping
Build 'amazon-ebs' errored after 16 minutes 22 seconds: Script exited with non-zero exit status: 1.Allowed exit codes are: [0]

==> Wait completed after 16 minutes 22 seconds

==> Some builds didn't complete successfully and had errors:
--> amazon-ebs: Script exited with non-zero exit status: 1.Allowed exit codes are: [0]

==> Builds finished but no artifacts were created.
Error: Process completed with exit code 1.

Expected behavior
All Helm charts should be installed successfully.
Version (add all relevant versions):

Compliant kubernetes apps version v0.12.0

Are you sure that it's not your master that is too weak and overloaded?
I see in the info you pasted that it fails calling the nginx webhook which could suggest a bad master node.
I have never seen this.

I agree with Olle. This seems to be the nginx ingress admission webhook that's not responding.

I have also only seen similar errors when I ran a master node that didn't have enough resources.

@jakubkrzywda please validate if #446 solved this issue.


Add "Server 2 Workstation" to config tab under fixes

Chris occasionally installs Windows Server, some of us try it too.
This can be done manually with the guide on www.windowsworkstation.com or there is a batch script for Server 2016-2019 versions but not for 2022 version.
I made PS scipts with chatgpt but they has to be merged. (If someone add this feature, in the beginning of scripts must be a check for if host windows server.)
psscripts.zip

Can you reconsider this issue?


Feat/134/testing event emitter

[1.21.0] - 2024-04-11
Features Added

Added Context Communication: Implemented a feature for inter-context communication within the library, enabling seamless interaction between different contexts within a project.

Introduced Custom Events: Custom events can now be dispatched both globally and within specific aggregates, providing flexibility in event handling and propagation.

Compatibility with Browser and Node.js: Maintained compatibility between browser and server environments by utilizing CustomEvents in the DOM for browser compatibility and standard event handling for Node.js.

Aggregate Event Management: Aggregates retain event management methods, allowing for the encapsulation of business rules within specific contexts.

Known Issues

Investigating potential chain reactions of lambda functions in certain scenarios.

Future Considerations

Strong Typing: Consideration for enhancing typing support for event parameters to provide better developer guidance and error checking.

Further Investigation: Continue investigating potential implications of fanning-out from a single lambda function to ensure robustness in complex scenarios.

Usage Examples

        import { Aggregate, Ok, Result, Context, EventHandler } from 'rich-domain';

        // ------------------
        // Some Context X

        const contextX = Context.events();

        // Listening global events
        contextX.subscribe('SIGNUP', (arg) => {
            console.log(arg);
        });

        // ------------------
        // User Account as Context Y

        type Props = { name: string };

        class User extends Aggregate<Props>{
            private constructor(props: Props) {
                super(props);
            }

            public static signUp(name: string): User {
                const user = new User({ name });
                // add handler according to business rule
                user.addEvent(new SignUpEvent());
                return user;
            }

            public static create(props: Props): Result<User> {
                return Ok(new User(props));
            }
        }

        const contextY = Context.events();

        class SignUpEvent extends EventHandler<User> {
            constructor() {
                super({ eventName: 'SIGNUP' })
            }

            dispatch(user: User): void {
                // dispatch to global context event manager
                contextY.dispatchEvent(this.params.eventName, user.toObject());
            };
        }

        const user = User.signUp('John Doe');

        // dispatch to call handler
        user.dispatchEvent('SIGNUP');

Acknowledgments
thanks to @mmmoli for contributions and inspirations

Buddy, I can take no credit for this. 100% you.


No such file or directory: 'Your dataset path/caption_rm2048_train.csv' #26

Same issue for caption_rm2048_train.csv, it is not available in https://github.com/microsoft/XPretrain/tree/main/hd-vila or https://github.com/microsoft/XPretrain/tree/main/hd-vila-100m.
Could you please point me to the place where you found it?
Appreciate your help

Hi @mayuelala could you also send it to me? all the required csv files thank you


Case label cannot be decimal

I have a case statement that takes a decimal value and returns another decimal value, something like this:

The debug console tells me "error CS0151: A switch expression or case label must be a bool, char, string, integral, enum, or corresponding nullable type"
So then I had to change my code to something like this:

And at least it compiles, still testing whether it still works properly. Case statements against decimal variables work in C/SIDE, why is that no longer the case (haha no pun intended)?

Hi @TheDenSter . I cannot repro your report on our nightly version of our compiler. It could be that we either fixed it in the meantime with some other fix or that you had a temporary hiccup from our compiler (could be some other errors in the files were causing incorrect behaviour at this point).
This is what I have and it compiles without errors:

Could you please try and repro again?
Thanks


Manage dependencies with version catalog

Done in https://github.com/GDG-Nantes/DevfestNantesMobile/pull/162


Roblox does not crash even without libndk-fixer.

I know this is a weird issue considering that this is a good thing. But bear with me here.
I'm trying to gather information on why Roblox crashes to analyze it and implement the fix to my own special libnb. So i tried to run roblox without libndk-fixer, and suprise, it is working as normal even after logging in and joining a game.
If anyone is able to cause roblox to crash or have a logcat of when it is crashing, please tell me.

Most likely roblox has removed the code that was causing issues in their app.


v0.8.0 Answer with broken sentences 聊天回答不完整

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Branch name
0.8.0
Commit ID
0001
Other environment information
No response
Actual behavior

Expected behavior
No response
Steps to reproduce
调整聊天配置的最大token数，能解决。
如果采用默认的512，初始配置好像不起效果，聊天出现断句

Adjusting the maximum number of tokens in the chat configuration can solve the problem.
If the default 512 is used, the initial configuration seems to have no effect, and there may be broken sentences in the chat

Additional information
No response

最后一个图，是更改了最大token数后的结果

I suggest that disable max tokens.

I suggest that disable max tokens.

the problem has been solved according to what you said

您好，
按照你们谈论的方法，我还是会出现回复中断这个问题。请问要如何处理

I guess deepseek is not stable. What about switch to another LLM?

@lijunpeng259 @ipv6next
We intend to create an international community, so we encourage using English for communication.

I suggest that disable max tokens.

Thanks for the suggestion, problem solved.


ZarinPal/ShetabViewController.swift:142

after app enters foreground from payment safari page
error given
ZarinPal/ShetabViewController.swift:142: Fatal error: Unexpectedly found nil while unwrapping an Optional valu

e

Hi Mohammad
You can update ZarinPal SDK to the last version and fix this issue.
last version:  1.1.14
install: docs

nope this issue not done.
if payment failed or cancel then open app anythings is ok,
but if payment success and come back to app again error ZarinPal/ShetabViewController.swift find nil.
i changed [1.1.14] version on pods file and use install repo update

OK, I'm checking this problem.

idk whats MPG means,
'MPG' use payment in app?
now app open payment page to browser

I found your problem and release a new version, you can use it:
https://github.com/ZarinPal/iOS-SDK/releases/tag/1.1.15

Ty 👍


Support for more pascal architecture GPUs?

Hi, Tri Tao,
Do you have plans to support more consumer-grade GPUs(e.g., 1080, 1070, 1060)?

We currently support Turing (e.g. RTX 2080) and Ampere (e.g. RTX 3080) GPUs. We rely on tensor cores for matrix multiplication, which older GPUs lack.

Do you support V100? (roadmap doesn't have it crossed out so I wanted to double check): [Jul 2022] Support SM70 GPUs (V100).

Not yet, that'll take some work. Hopefully in the near future.

We currently support Turing (e.g. RTX 2080) and Ampere (e.g. RTX 3080) GPUs. We rely on tensor cores for matrix multiplication, which older GPUs lack. You might be interested in the memory-efficient attention implemented by the xformers team (targeting fp32 instead of fp16), which I believe supports Pascal cards: facebookresearch/xformers#267 facebookresearch/xformers#281

thanks

We rely on tensor cores for matrix multiplication, which older GPUs lack.

What about GPUs like the p40? It uses pascal architecture, but has more tensor cores than a 4090. Is it possible to do add support for this GPU?

What about GPUs like the p40? It uses pascal architecture, but has more tensor cores than a 4090. Is it possible to do add support for this GPU?

I personally don't have plan to do that. We're mostly constrained by time.


Installed pacman packages with numbers are reinstalled

Describe the bug
The regex in host.fact.pacman_packages does not allow numbers in the names, this effectively "removes" them from the list of installed packages.
The arch package database shows packages with numbers.
To Reproduce
Running this will install m4 even if it's already installed
pacman.packages(
    name='Install m4',
    sudo=True,
    packages=[
        'm4',
    ],
)

Expected behavior
The above should not run pacman, just return unchanged.

I've fixed this in https://github.com/Fizzadar/pyinfra/commit/16786b2df690891d11a052fca84adc13c58a7d9f!

I've fixed this in https://github.com/Fizzadar/pyinfra/commit/16786b2df690891d11a052fca84adc13c58a7d9f!

Now released in 1.3.1!

Now released in 1.3.1!


Add Web IDL base types + Encoding Standard from their specs

The new json type file tends to flatten typedefs, is it a requirement?

thanks!


Inspect tool does not provide much information and why is it needed

The inspect tool  does not provide much detail about the object that is being hovered over.
In the example below, I see it is a point station, but none of the other properties, such as 'name' are displayed.  I would prefer to see something like the line this object will create in a th2 text file.

I generally require object property information at random times mid-drawing process.  It is disruptive to click the different tools all the time just for the purposes of gaining situational awareness and verifying the properties of an object.
So can we do away with the inspect tool altogether and have the position coordinates and hovered object details always updating on the bottom of the window?  Just like XTherion? At a glance, the drawing and other WTherion 'modes' don't seem to make (much) use of the status area.
If continuous 'inspect' updating is perceived as a drain on resources, then maybe a control key such as Ctrl+ mouse movement or spacebar+ mouse movement could activate the 'inspect' reporting behaviour.

Your example is interesting, because when you inspect a station, it does show the name that's been given. In your screenshot the station doesn't have a name, so nothing is displayed. I agree that it would be nice to see the exact line an object will create, but this is basically only possible with points, since both lines and areas will have multiline outputs.
The inspect tool doesn't just show the type, it can also show any other information with very little work, and it's purpose is to be a user friendly quickly readable text, not the therion output. That's why it has localization and not limited to just English.
Continuous inspect isn't really optimal with how the project is set up, but it would be possible to make the inspect tool available while pressing a button and then switch back to the previous tool -- that's already how pan and zoom work. But that wouldn't even be much different from how it is right now, you can just press M, and use it, the only problem is you also have to press a key to go back to another tool.

Sorry I made this issue too soon, before researching sufficiently.  You are right, the point station I used as an example had no name.
I like the idea of presenting 'friendly readable text' with the users localisation in this context.
Regarding multi-line statements such as lines, it is only necessary to echo the primary object definition line, such as this example from XTherion
I think all objects should report a result.

I tried using 'M' to activate Inspect.  It works, but as you imply, finding and pressing keys while looking at your drawing on screen is disruptive.  I would vote for behaviour activated similarly to pan or Zoom.
Another reason I am finding Inspect difficult to use is that it is hard to get the mouse cursor sufficiently close to a object for inspect to report a result.  Maybe it is because I have high res (4K) monitors?
I would like the Inspect functionality to have a generous snap zone, like for example, the Item Select function.
Also I am not seeing xvi stations reported.  For any xvi leg or station, I get 'unrecognised'.

Is the last part still an issue after 0a0d5cd2a44fc6cab3badfe06c895a3b78a890aa? I think it should be fixed now
Otherwise the snap distance (what paper calls tolerance) can be adjusted, I think I might add a config option for it.

I'm not seeing any change when using Inspect eyedropper and hovering over xvi points.
I'm using this link https://beta.wtherion.daemonw.com/ which i notice is now up to c24efcd created some 7 hours ago.
Looking at the various commits since https://github.com/daem-on/wtherion/commit/0a0d5cd2a44fc6cab3badfe06c895a3b78a890aa I'm not seeing changes that they seem to implement.  Is that link sufficient to pick up latest beta-fixes branch changes?  Or do I need to create a new drawing or clear my browser cache?

That's the correct link, it does need to go through an update process every time, but it's automatic, so you should just check (in the about dialog) the build string says version 0.6.0 build 2022-09-04T01:07:22.151Z, because that's the latest version as of when I'm writing this. Also it's in UTC for everyone so take that into account.

Here is my problem

A browser refresh does not update it, but this time reloading in a new Window did.
Anyway, these are resolved:

snap distance/tolerance configuration works (changes take effect on next reload of WTherion)
inspect on xvi stations works  (xvi drawing and xvi survey legs are unrecognised - I am OK with that)
inspect is active only while M key is pressed (funny, I seem to be doing a lot of this now mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm - my preference would be to use Ctrl - although maybe that can be confused with other functionality)

Possible future improvements:

Inspect on objects should provide more detail
ie 'point or line label' should also echo all the options present (-text, -scale, -align etc)
Inspect of points under/over an area is unreliable for those points (maybe there is a way to inspect points that underlie an area?)

Well yes, just refreshing a page is not enough to update a PWA, that's why it says "Close and reopen app to update". Regarding some other issues: the cofiguration takes effect immediately, tools only load configuration when they're switched to, so you need to switch off and back to a tool if you want it to use new settings. No reload necessary. The keybinding can of course be changed for inspect, but Ctrl is already taken by zoom, Shift is used by select but otherwise could work, and Alt was originally the zoom key but was changed because Firefox opens the toolbar if you press it.
Inspecting points/areas I've found very reliable, inspect always picks the top-most object. If you have points on top of an area they will always get picked (with tolerance), and if they are under an area, they will never be picked. Which is what an average user should expect based on what the canvas looks like. If you want to change the order of items, that's also possible with the Order menu in Select. This will also change order in the output.
Okay, I think that covers everything in this issue, see #19 for adding more to the inspect output.


Error loading file

Traceback (most recent call last):
File "./clusterCompare2.py", line 87, in
agglomerative.signal_ibcc()
File "/home/greg/github/reduction/experimental/paper/clustering/aggregation.py", line 683, in signal_ibcc
ibcc.runIbcc(base_directory+"/Databases/"+self.project+"_ibcc.py")
File "/home/greg/github/pyIBCC/python/ibcc.py", line 419, in runIbcc
combiner, dh = load_combiner(configFile, ibcc_class)
File "/home/greg/github/pyIBCC/python/ibcc.py", line 411, in load_combiner
dh.loadData(config_file)
File "/home/greg/github/pyIBCC/python/ibccdata.py", line 212, in loadData
self.output_file = outputFile % testid
TypeError: not all arguments converted during string formatting
Here is the config file:
import numpy as np
scores = np.array([0,1])
nScores = len(scores)
nClasses = 2
inputFile = "/home/greg/Databases/penguin_ibcc.csv"
outputFile = "/home/greg/Databases/penguin_signal.out"
confMatFile = "/home/greg/Databases/penguin_ibcc.mat"
nu0 = np.array([77,22])
alpha0 = np.array([[12, 1], [1, 3]])

I think this is fixed now -- if the filename doesn't include a "%i", we don't put the testid into the filenames.


Create 0000-01-02-fredkratt.md

getting started

Where is the file to "replace line 5"? This site is almost incomprehensible and I'm and engineer with a lot of programming experience.


Added ensemble functionality.

Added ensemble.py for ensembling models.
Added two functions "get_distance_matrix()" and "get_ensemble_id_list()" in Matcher.py for ensembling.
Modified a quotation mark typo in main.py.
The average IDF1 and MOTA score without ensemble are:
ave idf1 : 0.9219904337648431, ave mota : 0.9771644864323625
The average scores with ensemble are:
ave idf1 : 0.932197, ave mota : 0.974672
IDF1 is about 0.01 higher, while MOTA is about 0.0025 lower.

@Jonas0126 可能要請你協助處理部分 main.py conflicts 問題
如果可以的話請 @jonathan03020208 你那邊進行 pull --rebase 解決


Fix result & optimize BaseJson::decode()

Fix result: if $json is empty string method return empty string
Fix type validation for parameter $json: given argument can be stringable object
Normalize arguments passed to json_decode()

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
✔

Tests pass?
✔

Fixed issues

If it breaks BC, I'd strongly recommend using a new flag.

After a review, I think we should not apply it.
@WinterSilence thanks for contributing anyway.

@samdark Did you see the last two commits, state currently looks good.
BC is kept, I think and the change with the non-stringable object makes sense.

BC is kept, I think and the change with the non-stringable object makes sense.

This PR does not change behavior, only changes error message for non-stringable objects (to less useful IMO). So essentially change affects only people, who do not follow phpdoc, and it only changes the way code fails. AFAIK general consensus was to not add such guards, because there is no end to this - we can't have types in method signatures, and adding guards in every place is too much clutter and creates noticeable performance impact.

@schmunk42 I've missed these :)

@rob006 the error message is exactly the same in latest version of the code.

@rob006 the error message is exactly the same in latest version of the code.

Previously it was used only for arrays, now it is also used for non-stringable objects (previously code failed on (string) $json cast with clear message about casting to string non-stringable object).

Hmm... yes. Got it.

So it seems if we revert error message part, there's nothing more left in the PR.

@rob006

(previously code failed on (string) $json cast with clear message about casting to string non-stringable object

previews code failed on any object

previews code failed on any object

No, it's not. It worked fine for objects with __toString() implementation.

@rob006  yes, my fail,  append it . but cant change in closed PR


Implemented AVL Tree Data Structure

Contents:

AVLTreeNode Class: Represents individual nodes in the AVL Tree with key, value, height, left, and right attributes.
It also provides methods to:
update: Updates the height of the node.
balance: Calculates the balance factor of the node.

AVLTree Class: Implements the core functionalities of an AVL Tree:
insert: Inserts a key-value pair into the tree while maintaining the AVL balance.
delete: Deletes a node by key and rebalances the tree accordingly.
search: Retrieves the value associated with a given key.
rotateLeft and rotateRight: Helper methods to perform rotations for balancing the tree.
balance: Balances the AVL Tree after insertion or deletion.
getRoot: Returns the root of the tree.
size: Returns the number of nodes in the tree.

TreeTraversal Class (Abstract): Provides traversal methods:
inOrder: In-order traversal (left-root-right).
preOrder: Pre-order traversal (root-left-right).
postOrder: Post-order traversal (left-right-root).
breadthFirst: Breadth-first (level-order) traversal.

Unit Tests:
AVLTreeTest.php: Tests covering AVL Tree insertions, deletions, rebalancing, and searches. Additionally, tests for correct traversal behavior using in-order, pre-order, post-order, and breadth-first traversals.

GitHub Actions
All tests and workflows (in my forked repository) have passed:

PHPCS

DIRECTORY.md

build

Note
PR is complemented with #173


Handle view related manipulation on main thread and fix a method argument typo in -hide: afterDelay:

The selector in -performSelector:withObject:afterDelay: may not fire if the thread it performed on destroyed before the delay.

Ya, Apple told us that all UI related operation should be done on main thread.


Support macOS

We don't have CI for macOS at the moment.

Development on MacOS is tested, but production/cloud deployments on MacOS servers aren't planned at the moment. Future improvements to Documentation will clarify this further.


Feature Request: Screensaver bandwidth saver

Create additional setting in screensaver that "blacks-out" the screensaver (disables pulling of photos) after X hours. For example, after 3 hours it's likely the user is no longer watching the screensaver. Make this an optional feature so people can enable/disable.

This has been added as a requirement due to Google Download limitations. Set to 5 hours, mandatory.


Duration behavior during session extension

Problem description
Currently, when extending a session, the additional duration is added on top of the original duration from the session creation. For example when creating a session with a duration of 60s, then waiting for 10s, and extending it for 20s, the new duration is 80s.
Also when currently performing GET /sessions/{sessionId} it is not clear if the duration in the response should be the remaining session duration or the duration the session was created with.
Suggested behavior
The session extension should be added to the remaining time. So creating a session with a duration of 60s, waiting for 10s and extending it for 20s should lead to a new duration of 70s.
In order to provide the values of the original, remaining and extended duration, the duration field at GET /sessions/{sessionId} could be turned into a duration object including the different duration values:
duration: {  "original": "60",  "extended": "70",  "remaining": "50" }

I aggree on that point from a developer PoV.
It's unclear for us, if we should update the original "duration" - value (e.g. in this case it's "60") or just the remaining time during extending a session.
Having here an object may also be more clear for the consumer to see, what was the original duration and what is the extended duration.
And of course how many seconds are left. This value changes on every GET /sessions/{sessionId} - request.

This is also related to the discussion in #280. We have to make clear in the API spec the date-time when the QoS session effectively "startedAt" and when the session is about to expire ("expiresAt"), taking into account the extensions. Then, "session duration" should be the interval between both, and the remaining time is the interval between "now" and "expiresAt". We may discuss if we need to add a new property to save the "requestedDuration" (before any extension).

Fixed in #296


feature: adding more features to the lualine theme

Is your feature request related to a problem? Please describe.
I have switched my entire Neovim configuration to utilize this theme and its associated Lualine extension. However, I find myself wanting to customize the colors associated with the built-in tabline and being unable; this is especially frustrating as it involves settings that cannot be changed from Lualine.
Describe the solution you'd like
A revamp of the Lualine extension with full tabline and winbar support would solve these problems immediately.
Describe alternatives you've considered
I have read through both the documentation of this theme and of Lualine thoroughly and through much trial and error have determined that this is not a problem I am able to solve within my own configuration. Therefore, I am asking for a global feature to enable me to do this.
Additional context
No response

After further reading, I am not sure that the problem lies within this theme. This issue can be closed for now.


Align loops to be consistent

If going for ES5 output, then either polyfill or use alternative loops.

Given browser support today, don't think this is any longer a concern. Can add this back if people report this to be an issue.


Raycasting roadmap priority

Hi,
I am wondering where raycasting is on the priority list. Do you have even a wild guess on when it might drop?
Is it a matter of migrating the code over from nphysics with changes to support parallelism or is it an entire rewrite? Will it still use ncollide on the back end to process it?
I am not opposed to contributing at some point but I am so green with regards to rust that it might be a bit.
Thanks for the great project and great work!

Hi!
I intend to start working on ray-casting next week. So it should be ready in a couple of weeks.

Is it a matter of migrating the code over from nphysics with changes to support parallelism or is it an entire rewrite? Will it still use ncollide on the back end to process it?

Some of it will be rewritten (especially regarding the broad-phase) and some of it will just be a reuse of some ncollide features.

Excellent, I will be looking forward to testing it. Thanks.


Collecting and Preparing Image Classification Datasets

Topic Suggestion
Collecting and Preparing Image Classification Datasets
Writing sample(s):
Include any links or writing samples - to help our team better gauge your writing quality.
Proposal Submission
Proposed title of article
Collecting and Preparing Image Classification Datasets
Proposed article introduction
As a data specialist, it is evident to say that during the modeling process, data collection and data preprocessing usually takes a lot of time to implement. This comes with the need of high skills in handling raw and real world data that usually comes with a good piece of noise.
In this article, we will be looking at how to collect image data for classification problems and splitting the collected data into training, testing and validation sets.
Key takeaways
By the end of this article, the reader should be able to understand how to:

Collect image data
Label and store the collected data
Split the data into train, test and validation sets

Article quality
This article provides handy tips to the readers and additional knowledge in the field of Computer Vision.
References
N/A

After some careful consideration it struck us that this topic may be a bit over saturated throughout other blog sites and official documentations. Please feel free to suggest an alternate topic to explore. 🚀


Does the project support Chinese?

Really great work~
But recently I want to do ner and re tasks on the Chinese data set.
@ikuyamada

Thanks! LUKE does not currently support Chinese. We are now planning to work on multi-lingual version of LUKE.

Thanks! LUKE does not currently support Chinese. We are now planning to work on multi-lingual version of LUKE.

Thanks! LUKE does not currently support Chinese. We are now planning to work on multi-lingual version of LUKE.

Thanks Reply!
Looking forward to your multi-lingual version of LUKE.

Thanks! LUKE does not currently support Chinese. We are now planning to work on multi-lingual version of LUKE.

Thanks Reply!
Looking forward to your multi-lingual version of LUKE.


Insecure use of middleware over HTTP denied by configuration

Please help:
My code is as follows:
$container["JwtAuthentication"] = function ($container) {
    return new JwtAuthentication([
        "path" => "/",
        "passthrough" => ["/token", "/info"],
        "secret" => getenv("JWT_SECRET"),
        "logger" => $container["logger"],
        "secure" => false,   // Only https
        "error" => function ($request, $response, $arguments) {
            $data["status"] = "error";
            $data["message"] = $arguments["message"];
            return $response
                ->withHeader("Content-Type", "application/json");
        },
        "callback" => function ($request, $response, $arguments) use ($container) {
            $container["token"]->hydrate($arguments["decoded"]);
        }
    ]);
};

I already set "secure" to false,  byt still not working.
curl -X POST
http://api.example.com/token
-H 'cache-control: no-cache'
-H 'content-type: application/json'
-d '{"username":"someuser","password":"somepassword"}'
500 Internal Server error
{
    "status": "error",
    "message": "Insecure use of middleware over HTTP denied by configuration."
}

BTW: it is working good on localhost

In your config the /token path is not authenticated by JWT middleware.
 "passthrough" => ["/token", "/info"],

If you are using Basic Auth middleware  for authenticating the '/token'  path set "secure" => false there too.  Note that this is a security risk and should not be used in live environment.


Announcement

Fixes #16

Look at the travis build and fix the errors

rubocop -aD is your friend haha

Looks good to me. Don't forget to write tests as well!


Code formatting for github.

For happier eyes.

Oops, sorry I missed this -- cheers! FYI this project is effectively EOLed since the Go folks introduced their own DBI-alike.

Yeah, it was just a bit of OCD kicking in! Cheers :-)


ISPN-11554 Off-heap state transfer resets timestamps

https://issues.redhat.com/browse/ISPN-11554

Preserve the timestamps in OffHeapEntryFactoryImpl
Delete deprecated OffHeapEntryFactory.create overload
Pull up the storageType parameter in MultipleCacheManagersTest
Use the inherited lockingMode in ExceptionEvictionTest

Merged, thanks @danberindei


Consider making friendly with the form

There was an idea to create a class of some RequestForm/FormRequest, that works only with POST data.

Idea of implementation
Add FromRequestBody, FromRequestQuery, etc. attributes that will be hydrate to object properties with same names. Need ability to use manual attributes also. Example:
public function myAction(
#[FromRequestBody]
UserDto$userDto,
)
final class UserDto {
public function __construct(
#[Required]
#[Length(min: 3)]
public readonly string $name, // body.name
#[Required]
#[Integer(min: 18)]
public readonly int $age, // body.age

#[Query('label')]
#[Required]
#[Length(min: 5)]
public readonly string $label, // query.label

) {}
}
And pure attribute FromRequest that will be means, that object require hydrate by nested attributes.

Maybe no need additional attributes:
// in controller
public function someAction(#[Body] UserDto $userDto) // also form can be here

// dto or form
final class UserDto implements SomeInterfaceForDetermineInRequestModel {
  public function __construct(
    #[Required]
    #[Length(min: 3)]
    public readonly string $name, // body.name

    #[Required]
    #[Integer(min: 18)]
    public readonly int $age, // body.age

    #[Query('label')] // hm...
    #[Required]
    #[Length(min: 5)]
    public readonly string $label, // query.label
  ) {}
}

// in request-model
if ($parameter->hasType() && $this->isHydratable($parameter->getType())) {
    // do hydrate
}


[MM-49089] Propagate calls client errors

Summary
PR implements some missing logic which is needed to surface clients errors (e.g. connection failure) from global widget to main window.
Videos
https://user-images.githubusercontent.com/1832946/219517628-49503970-a862-4cbc-ae52-2f1a864e7ff2.mov
https://user-images.githubusercontent.com/1832946/219517633-412ff76c-c4ea-40ee-980f-beb116944ae0.mov
https://user-images.githubusercontent.com/1832946/219517636-e898bd50-10a9-4e94-8027-ea7366eca94a.mov
Related PR
https://github.com/mattermost/mattermost-plugin-calls/pull/339
Ticket Link
https://mattermost.atlassian.net/browse/MM-49089
Release Note
NONE

Cherry pick is scheduled.


ERROR in node_modules/angularfire2/auth/auth.d.ts(10,20): error TS2503: Cannot find namespace 'firebase'.

Angular: 5.0
Firebase:  4.8.1
AngularFire: 5.0.0-rc.4
Other (e.g. Ionic/Cordova, Node, browser, operating system):
no
How to reproduce these conditions
Steps to set up and reproduce
Follow the Installation & Setup guide in the agunlarfire 2 github
Sample data and security rules
<-- include/attach/link to some json sample data (or provide credentials to a sanitized, test Firebase project) -->
Debug output
** Errors in the JavaScript console **
** Output from firebase.database().enableLogging(true); **
** Screenshots **
ERROR in node_modules/angularfire2/auth/auth.d.ts(10,20): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/auth/auth.d.ts(11,36): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firebase.app.module.d.ts(5,45): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firebase.app.module.d.ts(8,17): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firebase.app.module.d.ts(9,21): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firebase.app.module.d.ts(10,22): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firebase.app.module.d.ts(11,20): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firebase.app.module.d.ts(13,22): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/changes.d.ts(8,43): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/changes.d.ts(9,46): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/changes.d.ts(9,80): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/changes.d.ts(10,49): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/changes.d.ts(10,95): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/changes.d.ts(10,140): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/changes.d.ts(10,182): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/changes.d.ts(11,49): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/changes.d.ts(11,94): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/changes.d.ts(11,130): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/collection.d.ts(8,54): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/collection.d.ts(8,96): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/collection.d.ts(10,19): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/collection.d.ts(12,22): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/collection.d.ts(12,69): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/collection.d.ts(13,27): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/collection.d.ts(14,25): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/collection.d.ts(15,30): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/collection.d.ts(16,27): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/collection/collection.d.ts(17,27): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/document/document.d.ts(8,10): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/document/document.d.ts(9,22): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/document/document.d.ts(10,28): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/document/document.d.ts(14,42): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/firestore.d.ts(9,55): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/firestore.d.ts(12,25): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/interfaces.d.ts(4,11): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/interfaces.d.ts(5,14): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/interfaces.d.ts(14,37): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/interfaces.d.ts(14,80): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/interfaces.d.ts(16,10): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/interfaces.d.ts(17,12): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/observable/fromRef.d.ts(6,41): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/observable/fromRef.d.ts(6,80): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/observable/fromRef.d.ts(7,41): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/observable/fromRef.d.ts(7,98): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/observable/fromRef.d.ts(8,48): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firestore/observable/fromRef.d.ts(8,93): error TS2503: Cannot find namespace 'firebase'.
Expected behavior
Project compiles successfully
Actual behavior
The project doesn't compile

I started getting this error last night as well out of the blue. I even reran builds that has just completed successfully that then failed with no changes.
I think this may be related to the firebase refactoring specified in angular/angularfire2#1385

@rts-cwalker The same happened to me.
Changing it to firebase 4.8.0 fixed the issue as stated in the other thread.

@a-cordoba10 You building locally? Bc I changed to 4.8.0 in my package.json file, but I cant change it in angularfire 2 dependencies when it builds on Travis CI.

Im building locally, but now im getting this error when building my auth service
ERROR in ../../../node_modules/@firebase/database/dist/esm/src/api/Database.d.ts(4,33): error TS2307: Cannot find module '@firebase/app-types/private'.
../../../node_modules/@firebase/database/dist/esm/src/core/AuthTokenProvider.d.ts(17,39): error TS2307: Cannot find module '@firebase/app-types/private'.

@a-cordoba10 that is 4.8.1 catching ya https://github.com/firebase/firebase-js-sdk/issues/387#issuecomment-352633693

@myspivey  How? In my package.json I have   "angularfire2": "5.0.0-rc.4",    and  "firebase": "4.8.0", (I have also tried with     "firebase": "4.7.0") and after npm install I still have the problem

Think AF2 is grabbing it and some fighting is going on. Try seeing what is inside AF2.

Well I at least figured out what i was doing wrong.... Forgot to remove the prefix that allowed patch versions to be installed. Thus it kept installing 4.8.1

@a-cordoba10 Make sure you dont have a leading ^ in front of the 4.8.0 in package.json for firebase. Also there is an angularfire2 v5.0.0-rc.5 available that may help

4.8.1 was a refactor of the typings and you now pull your imports from @firebase:
import { FirebaseApp } from '@firebase/app-types';
import { FirebaseAuth } from '@firebase/auth-types';
import { FirebaseDatabase } from '@firebase/database-types';
import { FirebaseMessaging } from '@firebase/messaging-types';
import { FirebaseStorage } from '@firebase/storage-types';
import { FirebaseFirestore } from '@firebase/firestore-types';

I found this, maybe we can make some update ?

@hiepxanh there is already a PR open to fix. #1386

@rts-cwalker thanks, I don't see that, Can't believe they release breaking change in xmas

Whats more shocking is that its released as a "patch" release.. Breaking changes should AT LEAST be minor version release.

finally !!! i know the problem and could fix it with a downgrade to 4.8.0

Can we get a warning next before breaking changes come in....

Firebase really should have done this refactor this at a SemVer major point since it is going to break everyone's TypeScript builds. Instead they did it between 4.8.0 and 4.8.1.

I'm getting this same error right now, downgraded, upgraded, did everything but still didn't work.
I'm using:
"angularfire2": "^5.0.0-rc.4",
"firebase": "4.8.1",
I also upgraded to rc.5 but that didn't fix the error
My error log looks like so:
ERROR in node_modules/angularfire2/auth/auth.d.ts(10,20): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/auth/auth.d.ts(11,36): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firebase.app.module.d.ts(5,45): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firebase.app.module.d.ts(8,17): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firebase.app.module.d.ts(9,21): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firebase.app.module.d.ts(10,22): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firebase.app.module.d.ts(11,20): error TS2503: Cannot find namespace 'firebase'.
node_modules/angularfire2/firebase.app.module.d.ts(13,22): error TS2503: Cannot find namespace 'firebase'.

When is a bug fix likely to be released?

mayordwells you need to downgrade Firebase to 4.8.0. That will resolve till a fix is out.

Downgrading to firebase 4.8.0 fixed it for me

@asgarli Thanks, I'll try to do the same.

this resolution doesnt work for me.
"dependencies": {     "@angular/common": "5.0.3",     "@angular/compiler": "5.0.3",     "@angular/compiler-cli": "5.0.3",     "@angular/core": "5.0.3",     "@angular/forms": "5.0.3",     "@angular/http": "5.0.3",     "@angular/platform-browser": "5.0.3",     "@angular/platform-browser-dynamic": "5.0.3",     "@ionic-native/core": "4.4.0",     "@ionic-native/splash-screen": "4.4.0",     "@ionic-native/status-bar": "4.4.0",     "@ionic/pro": "1.0.16",     "@ionic/storage": "2.1.3",     "@types/firebase": "^2.4.32",     "angularfire2": "^5.0.0-rc.4",     "firebase": "4.8.0",     "ionic-angular": "3.9.2",     "ionicons": "3.0.0",     "promise-polyfill": "^6.1.0",     "rxjs": "5.5.2",     "sw-toolbox": "3.6.0",     "zone.js": "0.8.18"   }

@darlondjc can you verify what /node_modules/firebase/package.json reports as the version? Your setup looks fine.

@myspivey:

{
"_from"<EMAIL_ADDRESS>"_id"<EMAIL_ADDRESS>"_inBundle": false,
"_integrity": "xxx",
"_location": "/firebase",
"_phantomChildren": {
"@firebase/webchannel-wrapper": "0.2.5",
"faye-websocket": "0.11.1",
"grpc": "1.8.0"
},
"_requested": {
"type": "version",
"registry": true,
"raw"<EMAIL_ADDRESS>"name": "firebase",
"escapedName": "firebase",
"rawSpec": "4.8.0",
"saveSpec": null,
"fetchSpec": "4.8.0"
},
"_requiredBy": [
"/"
],
"_resolved": "https://registry.npmjs.org/firebase/-/firebase-4.8.0.tgz",
"_shasum": "c0b5bad5c1241222f3a6f06065ea121ebbc14fd3",
"_spec"<EMAIL_ADDRESS>"_where": "C:\workspace\loteca",
"author": {
"name": "Firebase",
"email"<EMAIL_ADDRESS>"url": "https://firebase.google.com/"
},
"browser": "index.js",
"bugs": {
"url": "https://github.com/firebase/firebase-js-sdk/issues"
},
"bundleDependencies": false,
"dependencies": {
"@firebase/app": "0.1.4",
"@firebase/auth": "0.3.0",
"@firebase/database": "0.1.5",
"@firebase/firestore": "0.2.1",
"@firebase/messaging": "0.1.5",
"@firebase/polyfill": "0.1.3",
"@firebase/storage": "0.1.4",
"dom-storage": "^2.0.2",
"xmlhttprequest": "^1.8.0"
},
"deprecated": false,
"description": "Firebase JavaScript library for web and Node.js",
"devDependencies": {
"compression-webpack-plugin": "^1.0.0",
"git-rev-sync": "^1.9.1",
"gulp": "github:gulpjs/gulp#4.0",
"gulp-concat": "^2.6.1",
"gulp-sourcemaps": "^2.6.1",
"npm-run-all": "^4.1.1",
"webpack": "^3.5.6",
"webpack-dev-server": "^2.8.1",
"webpack-stream": "^4.0.0",
"wrapper-webpack-plugin": "^1.0.0"
},
"homepage": "https://firebase.google.com/",
"keywords": [
"authentication",
"database",
"Firebase",
"firebase",
"realtime",
"storage"
],
"license": "Apache-2.0",
"main": "index.node.js",
"name": "firebase",
"react-native": "index.react-native.js",
"repository": {
"type": "git",
"url": "git+https://github.com/firebase/firebase-js-sdk.git"
},
"scripts": {
"dev": "run-p watch:compiler watch:server",
"prepare": "gulp build",
"watch:compiler": "gulp watch",
"watch:server": "webpack-dev-server --config webpack.dev.js --colors"
},
"typings": "index.d.ts",
"version": "4.8.0"
}

Upgrading angularfire2 and downgrading firebase fixed it for me.
"angularfire2": "5.0.0-rc.5", + "firebase": "4.8.0",
"dependencies": {
"@angular/animations": "^5.0.0",
"@angular/common": "^5.0.0",
"@angular/compiler": "^5.0.0",
"@angular/core": "^5.0.0",
"@angular/forms": "^5.0.0",
"@angular/http": "^5.0.0",
"@angular/platform-browser": "^5.0.0",
"@angular/platform-browser-dynamic": "^5.0.0",
"@angular/router": "^5.0.0",
"@angular/service-worker": "^5.0.0",
"@ngrx/store": "^4.1.1",
"angularfire2": "5.0.0-rc.5",
"core-js": "^2.4.1",
"firebase": "4.8.0",
"rxjs": "^5.5.2",
"zone.js": "^0.8.14"
},

"angularfire2": "5.0.0-rc.5", and "firebase": "4.8.0" did not work yet. :(

"angularfire2": "5.0.0-rc.5", and "firebase": "4.8.0" did work for me :)

@darlondjc , did you ran npm update on the root folder? I was missing that step

@cdosorio i did it right now (again), just for confirm, but stays the same error.

typescript error
Cannot find type definition file for 'firebase'.

I am having bad time with this error

did anyone got a fix?

"angularfire2": "5.0.0-rc.5", and "firebase": "4.8.0" didn't work for me either.

Be sure on your package.json file that the firebase version doesn't have the ^ symbol, otherwise you will be importing version 4.8.1 not 4.8.0.:
"angularfire2": "^5.0.0-rc.5",
"firebase": "4.8.0",

The mine one's like this (and it doesnt work anway):

"angularfire2": "^5.0.0-rc.5",
"firebase": "4.8.0"

Same here, it looks like this:
    "angularfire2": "5.0.0-rc.4",
    "core-js": "^2.4.1",
    "firebase": "4.8.0",

If I try<EMAIL_ADDRESS>without the ^ I get:
No matching version found for<EMAIL_ADDRESS>Is only me?

Step1  -- Downgrade firebase to 4.8.0 and remove ^,
Step2-- Remove ^ from   "angularfire2": "5.0.0-rc.4",
Step3--  run npm update  and restart your VSCODE
"dependencies": {
"@angular/common": "5.0.3",
"@angular/compiler": "5.0.3",
"@angular/compiler-cli": "5.0.3",
"@angular/core": "5.0.3",
"@angular/forms": "5.0.3",
"@angular/http": "5.0.3",
"@angular/platform-browser": "5.0.3",
"@angular/platform-browser-dynamic": "5.0.3",
"@firebase/firestore": "^0.2.2",
"@firebase/webchannel-wrapper": "0.2.5",
"@ionic-native/core": "4.4.0",
"@ionic-native/splash-screen": "^4.5.2",
"@ionic-native/status-bar": "4.4.0",
"@ionic/pro": "1.0.16",
"@ionic/storage": "2.1.3",
"angularfire2": "5.0.0-rc.4",
"cordova-android": "6.3.0",
"cordova-plugin-device": "^1.1.7",
"cordova-plugin-ionic-webview": "^1.1.16",
"cordova-plugin-splashscreen": "^4.1.0",
"cordova-plugin-whitelist": "^1.3.3",
"cordova-splashscreen": "^3.1.0",
"firebase": "4.8.0",
"ionic-angular": "3.9.2",
"ionic-plugin-keyboard": "^2.2.1",
"ionicons": "3.0.0",
"promise-polyfill": "^6.1.0",
"rxjs": "5.5.2",
"sw-toolbox": "3.6.0",
"zone.js": "0.8.18"

Go back to firebase 4.8.0:

In your CLI with you project path type: npm uninstall firebase (which is 4.8.1)
then once fish uninstall, type: npm cache clear
-then type: npm install<EMAIL_ADDRESS>-finally: Remove "firebase": "^4.8.1" in dependencies in package.json and Type "firebase": "4.8.0"
(Note: without ^). Save All and your problem will be solved! :)

@hanihoumani93 Thank you.  Had to remove ^ and it worked fine.
npm install<EMAIL_ADDRESS>

@jverk 100%,  Sorry it's a copy paste mistake haha!

Solution:
1. Inside package.json, remove ^ from "firebase": "^4.8.1"
1.1 Downgrade Firebase from 4.8.1 to 4.8.0 by changing 4.8.1 to 4.8.0
1.2 End result should look like this: "firebase": "4.8.0"
2. Run npm update in the Project Root. NPM will downgrade Firebase for ya
3. Run ng serve --open to check for compilation errors. There shouldn't be any.
4. Enjoy!
Reason:
Firebase had introduced some breaking changes that AngularFire2 had not coped up with yet. Until the AngularFire2 team work it out, this will be the solution.
Add a thumbs up emoji and direct anyone having the same trouble here! Would save a lot of their time!

"angularfire2": "^5.0.0-rc.5",
"firebase": "4.8.0",
Worked for me... I don't know why there are so many breaking changes these days.

+-- UNMET PEER DEPENDENCY<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>-- UNMET DEPENDENCY<EMAIL_ADDRESS>this error with rc-4 The below versions worked for me"angularfire2": "^5.0.0-rc.4",
"firebase": "4.5.0",`

On a Christmas, breaking changes!!!
"angularfire2": "5.0.0-rc.4",
"firebase": "4.8.0",

if you roll back to firebase 4.8.0.then the error wil go away..

Tried everything not working.
Current Error -
ERROR in ../../../../node_modules/@firebase/database/dist/esm/src/api/Database.d.ts(4,33): error TS2307: Cannot find module '@firebase/app-types/private'. ../../../../node_modules/@firebase/database/dist/esm/src/core/AuthTokenProvider.d.ts(17,39): error TS2307: Cannot find module '@firebase/app-types/private'.
and Versions are
    "angularfire2": "^5.0.0-rc.4",
    "firebase": "4.8.0",

Also tries this combination
    "angularfire2": "5.0.0-rc.4", OR "angularfire2": "5.0.0-rc.5",
    "firebase": "4.8.0",

Tried with Yarn as well as Npm
Has anybody still facing the problem.
Facing problem in this git repo
https://github.com/Sandeep3005/ng-chat-app.
Can anybody take a look

@Sandeep3005 did you uninstall the prior firebase version before changing to use firebase:  4.8.0? I made sure to run npm uninstall --save firebase and then ran npm install with firebase: 4.8.0

"angularfire2": "5.0.0-rc.0",
"firebase": "4.8.0",
This works for me.

This worked for me:  I uninstalled all the old versions from the project and I updated the package.json with the following structure,  after that I npm installed and it worked fine.
The reason it is not working is because angularFire2 is trying to get the namespace from /firebase which in the version 4.8.1 changed to /@firebase.
Hope it work for you guys,
"dependencies": {
"@angular/animations": "^5.0.0",
"@angular/common": "^5.0.0",
"@angular/compiler": "^5.0.0",
"@angular/core": "^5.0.0",
"@angular/forms": "^5.0.0",
"@angular/http": "^5.0.0",
"@angular/platform-browser": "^5.0.0",
"@angular/platform-browser-dynamic": "^5.0.0",
"@angular/router": "^5.0.0",
"angularfire2": "^5.0.0-rc.5",
"core-js": "^2.4.1",
"firebase": "4.8.0",
"rxjs": "^5.5.2",
"zone.js": "^0.8.14"
}

@matew17 Good catch! Didn't realize that 😂

downgrade firebase to 4.8.0 fixed my issue.
run=> npm install<EMAIL_ADDRESS>

The fix for new people like me:
Go to your terminal:
in your app directory ->
open package.json with your editor of choice (VSCODE in my case)
change "firebase": "^4.8.1" to "firebase": "4.8.0"
command s to save
then in your terminal type->
npm install
you don't have to type update or uninstall because npm should do it for you.  in your editor make a note that you changed it so that someday if you have to come back to it you know you changed it.
//changed from "firebase": "^4.8.1" on 12-29-17
you will be glad you did.
That does fix it.

I used this solution, and it works for serving my project locally. However, whenever I try to build the project, I get Error: Metadata version mismatch for module ../node_modules/angularfire2/index.d.ts, found version 4, expected 3. How would I fix this so that my project builds successfully?

spent many days trying to fix this. Disappointed to hear that it was a release issue. Downgrading to firebase 4.8.0 from 4.8.1 fixed it for me

uninstall and reinstall firebase 4.8.0

confirmed it is 4.8.1 is a breaking one.

Hi All,
Can any body tell me how to fix the same thing in Ionic2 project
I have tried every thing which you mentioned above but no luck.
Still i am getting the same issue
Cannot find module '@firebase/app-types/private'.
<EMAIL_ADDRESS>Cannot find module '@firebase/app-types/private'.
<EMAIL_ADDRESS>My package.json - after i downgraded the firebase
"angularfire2": "5.0.0-rc.4",
"firebase": "4.8.0",

Doesn't seem related to this issue, please post it at StackOverflow. @vyasm9

@vyasm9 I'm in an Ionic project and I got it to work by using "angularfire2": "^5.0.0-rc.5" and "firebase": "4.8.0",
I had to delete my node_modules and be sure to not be running the webpack watcher at the same time, then it worked fine.. I have other updating issues but this odd Typescript problem went away

In firebase 4.9.0 there is no errors :)

Updating both fixed it for me.
This may help someone.
    "angularfire2": "^5.0.0-rc.6",
    "firebase": "^4.9.1",

thank you much Daneile-pecora, I updated firebase to "^4.9.1, it's work perfectly.

Can someone help...I'm still getting the same issue:
`[20:53:56]  typescript: node_modules/angularfire2-offline/database/angularfire2-interfaces.d.ts, line: 7
Namespace 'firebase' has no exported member 'Promise'.
   L6:      snapshotCase?: () => firebase.Promise<void>;
   L7:      unwrappedSnapshotCase?: () => firebase.Promise<void>;

[20:53:56]  typescript: node_modules/angularfire2-offline/database/object/afo-object-observable.d.ts, line: 53
Namespace 'firebase' has no exported member 'Promise'.
  L53:  remove(): firebase.Promise<void>;

[20:53:56]  typescript: node_modules/angularfire2-offline/database/object/afo-object-observable.d.ts, line: 63
Namespace 'firebase' has no exported member 'Promise'.
  L63:  set(value: any): firebase.Promise<void>;

[20:53:56]  typescript: node_modules/angularfire2/app/firebase.app.module.d.ts, line: 5
Class 'FirebaseApp' incorrectly implements interface 'App'. Property 'firestore' is missing in type
'FirebaseApp'.
   L4:  export declare const FirebaseAppConfigToken: InjectionToken<FirebaseAppConfig>;
   L5:  export declare class FirebaseApp implements firebase.app.App {
   L6:      name: string;

[20:53:56]  typescript: node_modules/angularfire2/app/firebase.app.module.d.ts, line: 12
Namespace 'firebase' has no exported member 'Promise'.
  L11:      storage: () => firebase.storage.Storage;
  L12:      delete: () => firebase.Promise<any>;

[20:53:56]  typescript: node_modules/angularfire2/database/firebase_list_observable.d.ts, line: 14
Namespace 'firebase' has no exported member 'Promise'.
  L13:  push(val: any): firebase.database.ThenableReference;
  L14:  update(item: FirebaseOperation, value: Object): firebase.Promise<void>;
  L15:  remove(item?: FirebaseOperation): firebase.Promise<void>;

[20:53:56]  typescript: node_modules/angularfire2/database/firebase_list_observable.d.ts, line: 15
Namespace 'firebase' has no exported member 'Promise'.
  L14:  update(item: FirebaseOperation, value: Object): firebase.Promise<void>;
  L15:  remove(item?: FirebaseOperation): firebase.Promise<void>;
  L16:  _checkOperationCases(item: FirebaseOperation, cases: FirebaseOperationCases): firebase.Promise<void>;

[20:53:56]  typescript: node_modules/angularfire2/database/firebase_list_observable.d.ts, line: 16
Namespace 'firebase' has no exported member 'Promise'.
  L15:      remove(item?: FirebaseOperation): firebase.Promise<void>;
  L16:      _checkOperationCases(item: FirebaseOperation, cases: FirebaseOperationCases): firebase.Promise<void>;

[20:53:56]  typescript: node_modules/angularfire2/database/firebase_object_observable.d.ts, line: 11
Namespace 'firebase' has no exported member 'Promise'.
  L10:  lift<T, R>(operator: Operator<T, R>): Observable<R>;
  L11:  set(value: any): firebase.Promise<void>;
  L12:  update(value: Object): firebase.Promise<void>;

[20:53:56]  typescript: node_modules/angularfire2/database/firebase_object_observable.d.ts, line: 12
Namespace 'firebase' has no exported member 'Promise'.
  L11:  set(value: any): firebase.Promise<void>;
  L12:  update(value: Object): firebase.Promise<void>;
  L13:  remove(): firebase.Promise<void>;

[20:53:56]  typescript: node_modules/angularfire2/database/firebase_object_observable.d.ts, line: 13
Namespace 'firebase' has no exported member 'Promise'.
  L12:      update(value: Object): firebase.Promise<void>;
  L13:      remove(): firebase.Promise<void>;

[20:53:56]  typescript: node_modules/angularfire2/interfaces.d.ts, line: 12
Namespace 'firebase' has no exported member 'Promise'.
  L11:  export interface FirebaseOperationCases {
  L12:      stringCase: () => firebase.Promise<void>;
  L13:      firebaseCase?: () => firebase.Promise<void>;

[20:53:56]  typescript: node_modules/angularfire2/interfaces.d.ts, line: 13
Namespace 'firebase' has no exported member 'Promise'.
  L12:  stringCase: () => firebase.Promise<void>;
  L13:  firebaseCase?: () => firebase.Promise<void>;
  L14:  snapshotCase?: () => firebase.Promise<void>;

[20:53:56]  typescript: node_modules/angularfire2/interfaces.d.ts, line: 14
Namespace 'firebase' has no exported member 'Promise'.
  L13:  firebaseCase?: () => firebase.Promise<void>;
  L14:  snapshotCase?: () => firebase.Promise<void>;
  L15:  unwrappedSnapshotCase?: () => firebase.Promise<void>;

[20:53:56]  typescript: node_modules/angularfire2/interfaces.d.ts, line: 15
Namespace 'firebase' has no exported member 'Promise'.
  L14:      snapshotCase?: () => firebase.Promise<void>;
  L15:      unwrappedSnapshotCase?: () => firebase.Promise<void>;

[20:53:56]  typescript: src/pages/home/home.ts, line: 154
Namespace 'firebase' has no exported member 'Promise'.
 L154:      logoutOfFacebook():firebase.Promise<void> {
 L155:            //const userId:string = firebase.auth().currentUser.uid;

[20:53:56]  typescript: src/pages/settings/settings.ts, line: 88
Namespace 'firebase' has no exported member 'Promise'.
  L88:      logoutOfFacebook(): firebase.Promise<void> {
  L89:            //const userId:string = firebase.auth().currentUser.uid;

[20:53:56]  typescript: src/providers/firebase-service/firebase-service.ts, line: 25
Property 'database' does not exist on type 'AngularFireDatabase'.
  L24:  this.userId = user.uid
  L25:  this.setSettings = this.afDatabase.database.ref(`/users/${user.uid}/settings`);
  L26:  });

[20:53:56]  typescript: src/providers/firebase-service/firebase-service.ts, line: 36
Cannot find namespace 'firebase'.
  L36:      firebase.Promise<any>{
  L37:      return this.afDatabase.object(`/users/${this.userId}/settings`).set({ location,

[20:53:56]  typescript: src/providers/login-service/login-service.ts, line: 27
Property 'database' does not exist on type 'AngularFireDatabase'.
  L26:  setUpUser(_credentials, _authData) {
  L27:    this.ref = this.afDatabase.database.ref('/users/' + _authData.uid)
  L28:    this.data = {

Error: Failed to transpile program
at new BuildError (/Users/laroca/Documents/Mundo/node_modules/@ionic/app-scripts/dist/util/errors.js:16:28)
at /Users/laroca/Documents/Mundo/node_modules/@ionic/app-scripts/dist/transpile.js:159:20
at Promise ()
at transpileWorker (/Users/laroca/Documents/Mundo/node_modules/@ionic/app-scripts/dist/transpile.js:107:12)
at Object.transpile (/Users/laroca/Documents/Mundo/node_modules/@ionic/app-scripts/dist/transpile.js:64:12)
at /Users/laroca/Documents/Mundo/node_modules/@ionic/app-scripts/dist/build.js:109:82
at `

I am still getting the same error on
"firebase": "^5.0.3",
"angularfire2": "^5.0.0-rc.9",

@ZenPylon I have the same combination, however, I get the following error:
ERROR in node_modules/@firebase/auth-types/index.d.ts(271,21): error TS2314: Generic type 'Observer<V, E>' requires 2 type argument(s).
node_modules/@firebase/auth-types/index.d.ts(276,21): error TS2314: Generic type 'Observer<V, E>' requires 2 type argument(s).
node_modules/@firebase/storage-types/index.d.ts(80,9): error TS2314: Generic type 'Observer<V, E>' requires 2 type argument(s).

Friends, I have a problem. In trying to install firebase, I add this :
"angularfire2": "^5.0.0-rc.6",
"firebase": "^4.9.1",
to my dependencies.
But I have this error:
npm ERR! code ERR_STREAM_WRITE_AFTER_END
npm ERR! write after end
Please help me.
Thank you.
Also I would like to know the usefulness of : "promise-polyfill": "^6.0.2",
Is it necessary to include it too ?
here are my dependencies;
"dependencies": {
"@angular/common": "5.0.0",
"@angular/compiler": "5.0.0",
"@angular/compiler-cli": "5.0.0",
"@angular/core": "5.0.0",
"@angular/forms": "5.0.0",
"@angular/http": "5.0.0",
"@angular/platform-browser": "5.0.0",
"@angular/platform-browser-dynamic": "5.0.0",
"@ionic-native/core": "^4.3.1",
"@ionic-native/in-app-browser": "^4.3.1",
"@ionic-native/splash-screen": "^4.3.1",
"@ionic-native/status-bar": "^4.3.1",
"@ionic/storage": "2.1.3",
"angularfire2": "^5.0.0-rc.6",
"cordova-android": "^6.2.3",
"cordova-ios": "^4.5.2",
"cordova-plugin-crosswalk-webview": "^2.3.0",
"cordova-plugin-device": "^1.1.6",
"cordova-plugin-inappbrowser": "^1.7.1",
"cordova-plugin-ionic-keyboard": "^2.0.2",
"cordova-plugin-ionic-webview": "^1.1.15",
"cordova-plugin-splashscreen": "^4.0.3",
"cordova-plugin-statusbar": "^2.2.3",
"cordova-plugin-whitelist": "^1.3.2",
"ionic-angular": "3.9.2",
"firebase": "^4.9.1",
"ionicons": "3.0.0",
"rxjs": "5.5.2",
"sw-toolbox": "3.6.0",
"zone.js": "0.8.18"
},
"devDependencies": {
"@ionic/app-scripts": "3.1.5",
"typescript": "~2.4.2"
},

{
"name": "firestarter",
"version": "0.0.0",
"scripts": {
"ng": "ng",
"start": "ng serve",
"build": "ng build --prod",
"test": "ng test --watch false",
"lint": "ng lint",
"e2e": "cypress open",
"build:all": "ng build --prod && ng run firestarter:server && npm run webpack:prerender && npm run prerender",
"serve:prerender": "http-server dist/firestarter -c-1",
"webpack:prerender": "webpack --config webpack.prerender.config.js",
"prerender": "node dist/firestarter/prerender.js"
},
"private": true,
"dependencies": {
"@angular/animations": "^6.0.1",
"@angular/common": "^6.0.1",
"@angular/compiler": "^6.0.1",
"@angular/core": "^6.0.1",
"@angular/forms": "^6.0.1",
"@angular/http": "^6.0.1",
"@angular/platform-browser": "^6.0.1",
"@angular/platform-browser-dynamic": "^6.0.1",
"@angular/platform-server": "^6.0.1",
"@angular/pwa": "^0.6.1",
"@angular/router": "^6.0.1",
"@angular/service-worker": "^6.0.1",
"@nguniversal/module-map-ngfactory-loader": "^6.0.0",
"angularfire2": "^5.0.0-rc.9",
"core-js": "^2.5.4",
"firebase": "^5.0.2",
"rxjs": "^6.0.0",
"zone.js": "^0.8.26"
},
"devDependencies": {
"@angular-devkit/build-angular": "~0.6.1",
"@angular/cli": "~6.0.1",
"@angular/compiler-cli": "^6.0.1",
"@angular/language-service": "^6.0.1",
"@cypress/webpack-preprocessor": "^2.0.1",
"@types/chance": "^1.0.1",
"@types/jasmine": "~2.8.6",
"@types/jasminewd2": "~2.0.3",
"@types/node": "~8.9.4",
"bulma": "^0.7.1",
"chance": "^1.0.16",
"codelyzer": "~4.2.1",
"cypress": "^3.0.1",
"firebase-tools": "^3.18.6",
"fs-extra": "^6.0.1",
"jasmine-core": "~2.99.1",
"jasmine-spec-reporter": "~4.2.1",
"karma": "~1.7.1",
"karma-chrome-launcher": "~2.2.0",
"karma-coverage-istanbul-reporter": "~1.4.2",
"karma-jasmine": "~1.1.1",
"karma-jasmine-html-reporter": "^0.2.2",
"protractor": "~5.3.0",
"ts-loader": "^4.3.0",
"ts-node": "~5.0.1",
"tslint": "~5.9.1",
"typescript": "~2.7.2",
"webpack-cli": "^2.1.3",
"ws": "^5.1.1",
"xmlhttprequest": "^1.8.0"
}
}

This Combination is not working for me
"angularfire2": "^5.0.0-rc.10",
"firebase": "^5.0.3", .
Nor this
"angularfire2": "^5.0.0-rc.10",
"firebase": "^4.8.0", .
I'm using angular 8 and ionic 5. please help if you got desired solution'

@VajpayeeShashi why don't you use "@angular/fire && firebase" Because this is an old issue unless you're working on a legacy project using "angularfire2" the when importing firebase try using "firebase/app"

I am not using the "angularfire2" I     "@angular/fire": "^6.0.0",     "firebase": "^7.14.6", still i get this : ERROR in node_modules/@angular/fire/angularfire2.d.ts(37,49): error TS2344: Type 'T[K]' does not satisfy the constraint '(...args: any) => any'.
If I add  "skipLibCheck": true, it is working any ideas.
Thanks in advance


Empty language cannot gain hljs plaintext classes

Hi again.
import { Marked } from 'marked';
import { markedHighlight } from "marked-highlight";
import hljs from 'highlight.js';

const marked = new Marked(
  markedHighlight({
    langPrefix: 'hljs language-',
    highlight(code, lang, info) {
      const language = hljs.getLanguage(lang) ? lang : 'plaintext';
      return hljs.highlight(code, { language }).value;
    }
  })
)

console.log(marked.parse(`
\`\`\`
plaintext
<
&
>
\`\`\`

\`\`\`blah
blah lang
<
&
>
\`\`\``));

plaintext
<
&
>

blah lang
<
&
>

Note that if lang is empty, even though it does pass through hljs.highlight() with plaintext lang, the rendered code has no hljs language-plaintext class as expected.

Further notes:
    highlight(code, lang, info) {
      const language = hljs.getLanguage(lang) ? lang : 'blahfakelang';
      const out = hljs.highlight(code, { language });
      console.log('out:', out);
      return out.value;
    }

leads to uncaught throw:
Could not find the language 'blahfakelang', did you forget to load/include a language module?
/Users/slu/stevenlu.net/node_modules/highlight.js/lib/core.js:2107
      throw new Error('Unknown language: "' + languageName + '"');
            ^

Error: Unknown language: "blahfakelang"

essentially, when lang comes in empty, even though it's converted here to plaintext, it won't take, but when a nonempty lang is specified in the payload, then we override it to be plaintext here and it shows up PROPERLY as plaintext, but we cannot configure an empty lang into plaintext as expected via marked-highlight.

Sorry, i was being dumb with the first question. but the second question is legit.  Let me edit...

Culprit is https://github.com/markedjs/marked-highlight/blob/main/src/index.js#L45

I don't know if it would break anything. It is set like that to be closer to the CommonMark spec where no lang mean there shouldn't be a class set.
We could add an option to specify the empty class. Something like:
marked.use(markedHighlight({
  emptyLangClass: "hljs",
  langPrefix: "hljs language-",
  highlight() {
    ...
  }
}));

Since I already made a fork and can deploy my app for now, there is no urgency on this, but I would love to help improve the behavior here to have a higher chance of meeting what is expected behavior and then I don't have to maintain my own fork.
For context, I'm designing a custom blog platform for my site, so I'm just approaching the code blocks from a minimalistic perspective. Since I haven't yet found a reason (trust that I will! sooner or later!) with highlight.js, that means I am currently all-in on highlight.js.
Because of the way hljs CSS is set up to behave, (and keep in mind I've only tested the default hljs theme so far lol I will build a themer for users to twiddle with that's hooked into a library of css themes) the background styling of code blocks doesn't appear if we don't include hljs class on a pre code tag.
Of course highlightjs doesn't care about markdown, so we provide a highlight() cb to implement it and we (following Marked extension convention) take over the unit of markdown code block rendering so the
 HTML manipulation is marked-highlight's unambiguous responsibility.
Here's the crux of it then, when a language isn't even specified, it is unclear whether to assign classes:

lang-plaintext
no lang class
hljs class (this one confers code block bgcolor styling)

I want to say that use of marked-highlight implies "going all in on highlight.js" as is the obvious choice in the context of my project.
This would require at minimum hljs class assigned to code tags.
I just cannot imagine right now a use case where somebody would want to exclude highlight.js behavior when lang is not specified. But I do not want to rule that out. Perhaps your suggestion of a new config satisfies both. I just can't help but feel like the default existing behavior is mostly wrong.

by the way the change i made in my fork (simply removing the ternary) leads to empty blocks having the class hljs lang- which looks questionable but certainly renders as I expect. It may more correctly be hljs without any lang, if lang is ''. It might also be plaintext. But I can't decide yet if it should be filtered down into to a lang that highlight.js can render or if it should keep (as now) verbatim to the specified lang...

The issue with your argument is that marked-highlight does not imply using highlight.js. marked-highlight is generic so the user can use whatever highlighting library they want. Other highlighting libraries highlight all
 tags instead of requiring a class.
If you want to fork marked-highlight specifically for highlight.js I think that would be a good idea since that seems to be the most common one. So users wouldn't even have to specify a highlight function.

I don't know if it would break anything. It is set like that to be closer to the CommonMark spec where no lang mean there shouldn't be a class set.
We could add an option to specify the empty class. Something like:
marked.use(markedHighlight({
  emptyLangClass: "hljs",
  langPrefix: "hljs language-",
  highlight() {
    ...
  }
}));

I would love to see this as well. I am having the same issue, so this would be very helpful.

It sure seems like this exact suggestion

I don't know if it would break anything. It is set like that to be closer to the CommonMark spec where no lang mean there shouldn't be a class set.
We could add an option to specify the empty class. Something like:
marked.use(markedHighlight({
  emptyLangClass: "hljs",
  langPrefix: "hljs language-",
  highlight() {
    ...
  }
}));

will provide what is needed for hljs to play nice. Let's plan to do that, then.


Event Overspeed (Configuration per device instead of global)

Dear All,
I believe if am not wrong overspeed limit value is to be set in config file which is common /applicable to all devices right?
However, What if in the case, where per device someone needs to set the overspeed limit
use case

Different vehicle types,. With different engine/speed capabilites and limitations.

Hello, @nefertiti007
You are right.
You have yet another reason to wait next release, because it is already implemented :)
Speed limit moved from config file to objects attributes, that means that you can set speed limit for device/group/server and set it via web-interface.

Implemented.


DownloadPipelineArtifact permissions lost on ubuntu

Type: Bug
Enter Task Name: DownloadPipelineArtifact
Issue Description
When using PublishPipelineArtifact with DownloadPipelineArtifact on ubuntu-latest (assuming other distros as well), the artifacts published then downloaded will not maintain execution rights.
An example of this would be using the -outfile option in Terraform, which will bundle downloaded plugins into the generated artifact.  If the plugin files do not have execution permissions set once extracted to the target deployment agent, the subsequent Terraform steps will fail due to permission issues.
As a quick workaround I run a bash script after the DownloadPipelineArtifact step to chmod +x the plug-ins, but it would be preferable to maintain the file permissions using the task itself.

The other case - release shell scripts with proper defined execute permission in git which go to artifact as simple files. And during release that permission is lost and bash task prints a warning about that. That's definitely a bug.

Just to give an update here from the Artifacts team. It does seem like a bug, so we'll track this like one and update here when possible.

Same issue here, and I have a lot of executables bundled in the artifact.
Using chmod +x on all of them is not very practical.

It does seem like a bug

I think this should probably be documented in the meantime.

@herenhuang thank you for the update.  I looks like it was changed from a bug to an enhancement in Jan, so if it is agreed to be a bug, we may need to flip that back.

Just ran into this issue too, it's very surprising to not keep permissions, running a chmod is a bit of a hack tbh.

@herenhuang Hi there - I'm trying to understand why this is considered an enhancement instead of a bug? Is it required that consumers of artifacts keep a list of executable files and mark them as executable (chmod +x) after the artifact is downloaded? This certainly feels like a bug in the implementation of artifacts. Many teams are having to put in their own hack/workaround to deal with this issue. Is there any plan to work on improving this in the near future?

Note that github actions followed the same path and has the same issue.
to mitigate this they document (only on the upload task, not download, which is not that easy to find) that one can simply tar.gzip the directory before (but then you have to do filtering of files yourself).
I think an Ok(ish) solution would be to have the task use tar.gz for storage instead of Zip based on a parameter of the task
At least it would be easily discovered and fixable.

How do we remove the stale tag?

It's ridiculous Microsoft can just close stuff with a bot without any interaction from people.

Original owner back at it: I have clever work arounds but but I cant escape the feeling that this just ... isn't how it should be.
Is this at least being road-mapped?

@fadnavistanmay @carl-tanner Any update on this? I just saw the stale tag and wanted to ensure this doesn't get closed due to inactivity.

Original Poster again:  this still exists.  It's also persisted into Github Actions.  It also is still falsely categorized as an Enhancement instead of a bug.
Please acknowledge.

Suffering from this (two years later) when uploading plugins in the .terraform directory as per https://learn.hashicorp.com/tutorials/terraform/automate-terraform#plan-and-apply-on-different-machines
Permissions are being mangled by the publish then download. Workaround that I have not yet tried is to tar the directory before publishing.
Agree that this is a bug not an enhancement.

Still interested in this.

How can this obvious bug still be there after 3 years?

How can this obvious bug still be there after 3 years?
Because Microsoft.

Oh and Azure DevOps is basically being replaced with Github Actions so a lot of their efforts are on that instead now. The host images for AzDo are Github Actions images now with the AzDo runtime slapped on top. (Their docs for AzDo lead you to the GHA Github page).

So far I know per default the artifacts are stored in zip files, which does not support file permissions.
But we can use those tasks to work with tar files nowadays.
https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/archive-files-v2?view=azure-pipelines
https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/extract-files-v1?view=azure-pipelines

Not stale

Any update here?


document getSSRProps for directives

I believe the documentation is missing something or there is a bug about getSSRProps: https://v3.nuxtjs.org/guide/directory-structure/plugins/#vue-directives
When I copy the content and paste it into /plugins/focus.ts or /plugins/focus.client.ts (in a project without any directives just with pages) I get the same getSSRProps missing error as anyone above - but the besides the error, it seems to work on most mounted elements.
(To check, the .focus() changed to .style.color = 'green' did its job)
_Originally posted by @BananaAcid in https://github.com/nuxt/nuxt.js/issues/13351

Encountered the same error following the docs for a simple focus directive.
Only after adding
// nuxt.config.ts
export default defineNuxtConfig({
  vue: {
    compilerOptions: {
      directiveTransforms: {
        focus: () => ({
          props: [],
          needRuntime: true
        })
      }
    }
  }
});

from #13351 once (!) it worked.
Interestingly after removing it afterwards from the config file, the directive still works.

The SSR error is also triggered if you have an unknown directive and a Nuxt layout.
https://stackblitz.com/edit/github-kbax54?file=pages/index.vue

I have met the same problem.
export default defineNuxtPlugin((nuxtApp) => {
    nuxtApp.vueApp.directive('focus', {
      mounted (el, { value }) {
        if(value == undefined){
            el.focus()
        }else if(value){
            el.focus()
        }
      },
      updated (el, { value }) {
        if(value == undefined){
            el.focus()
        }else if(value){
            el.focus()
        }
      },
      getSSRProps (binding, vnode) {
        // you can provide SSR-specific props here
        return {}
      }
    })
  })

How's it going? I have the same problem

Also here unfortunately still stuck with the problem. I am using a directive or a globally installed plugin to add a directive.

This is super annoying. Any updates on that?

Also here unfortunately still stuck with the problem. I am using a directive or a globally installed plugin to add a directive.

Workaround: add a abc.client.ts with the logic and a stub with abc.server.ts to at least ignore the problem for the moment …

@BananaAcid how can we register the plugin for both client and server side? using Nuxt App? TIA

I have the same error

and here's how I implement my registration of my plugin

sir @danielroe

how can we register the plugin for both client/server? sir @danielroe

@Kram-V just use filename.ts (no .client) to be loaded for both. You may check with if statements inside, it it got loaded on client or server side.

For client-only directive, @BananaAcid 's solution works for me.
Re-cap:
Make your directive:
plugins/my-directive.client.ts // My client-only directive code
Then copy it, rename "client" to "server" and strip out any logic:
plugins/my-directive.server.ts // This file needs to exist, with logic or not
Moreover, Nuxt docs describes this exactly:
https://nuxt.com/docs/guide/directory-structure/plugins#vue-directives

If you register a Vue directive, you must register it on both client and server side unless you are only using it when rendering one side. If the directive only makes sense from a client side, you can always move it to ~/plugins/my-directive.client.ts and provide a 'stub' directive for the server in ~/plugins/my-directive.server.ts.


"To force a sync between Intune and Microsoft Store for Business" refers to old Intune portal

The 'To force a sync between Intune and Microsoft Store for Business' section refers to Intune in portal.azure.com. Intune is no longer in Azure, but at https://endpoint.microsoft.com.
I am unable to locate 'force sync' in the new portal.
[Enter feedback here]

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

ID: 93e0cf16-3124-085e-d830-ffa849320f9d
Version Independent ID: 5abfaf19-5d3d-b188-53c5-3dcd20a142d3
Content: Deploy apps to devices - Microsoft Managed Desktop
Content Source: microsoft-365/managed-desktop/get-started/deploy-apps.md
Service: m365-md
GitHub Login: @jaimeo
Microsoft Alias: jaimeo

@aczechowski or @StuEwen or @ChristopherTulip can any of you advise on this?

@jaimeo what little I know of the topic, I think this article should help: https://docs.microsoft.com/en-us/mem/intune/apps/windows-store-for-business#configure-synchronization
CC @Erikre

@mnkii Thank you for your feedback. To Force sync you need to follow the below instructions

Sign in to the Microsoft Endpoint Manager admin center.
Select Tenant administration > Connectors and tokens > Microsoft Store for Business.
Click Sync to get the apps you've purchased from the Microsoft Store into Intune.

I have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/3256
Thanks
Sri

Fixed in PR 3256

@msbemba Thank you very much for the contribution and updating the documentation with PR. @mnkii Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


meta: bump sentry dependencies to lates 6.1.0 version

Descriptions
This PR upgrades to the latest Sentry version.
I tried running the e2e test locally and it failed on electron 11 for onFatalError can be overridden both before and after this bump. So I think it is unrelated.

Heya @HazAT we would love to get this version bump to leverage new features on the latest release. Would love it if you could have a look and perhaps merge this PR 🙂

Hey, thanks for the review 🎉
Would be lovely if someone with write permission could help merge this 🙂

@kevinlinv Thanks for the PR!
We need to be slightly more careful here since starting from 6.x we enabled sending sessions by default.
We didn't spend the time yet to figure out what this means for electron and how this will work in our product.
There is no real reason to update the dependencies besides this.

Hey, thanks for the quick update 👍
For context, the reason I am filing this PR here is because we're currently operating on a mono repo setup, where we have @sentry/browser|integration|types|electron installed as dependencies, we'd like to update to latest v6 to leverage some new feature on @sentry/browser|integration|types. But are running into an incompatible types when using an integration from<EMAIL_ADDRESS>with @sentry/electron@latest which still expects<EMAIL_ADDRESS>If updating the dependencies in here isn't straight forward and might not make sense, we may have to find another way to deal with the types incompatibility on our end 👌

we'd like to update to latest v6 to leverage some new feature on @sentry/browser|integration|types

@kevinlinv - what new things from 6.x are you hoping to use?

Hi @lobsterkatie thanks for the follow up.
We're keen on giving release health feature https://docs.sentry.io/product/releases/health/
We're still blocked on this upgrade though, unfortunately.

Release health is available starting in 5.27.0. The only difference between that and 6.x is that session tracking is turned on by default in the latter. See https://github.com/getsentry/sentry-javascript/pull/2973.

Hey @lobsterkatie thanks, thats news to me, there may have been a misunderstanding on my part.
Will give it a go to enable the feature through init config in 5.27.6 and shall close this if we can get it to work!

Looking for this to go to a 6.x version so I can use the tracesSampler option.
Related: https://github.com/getsentry/sentry-javascript/issues/3324#issuecomment-806192264

Not actively looking at this PR anymore, I'll close this so that others could re-propose the update if needed.

Looking for this to go to a 6.x version so I can use the tracesSampler option.

@aguynamedben - you can - it was added in 5.24.