Error when evaluating SSR module

Hello, thanks for the plugin, been using it for some time but after upgrading from v2.0.15 to the latest version v2.1.1 I get the following error when I run either astro dev or astro build.

[vite] Error when evaluating SSR module D:\Dev\igorskyflyer.me\astro.config.mjs: failed to import "astro-compress"
|- Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'typescript-esbuild' imported from D:\Dev\igorskyflyer.me\node_modules\astro-compress\Target\Variable\Option.js

I am using the latest Astro (v3.3.2) and I DON'T use it in SSR mode.

Here's what I've tried:
I've tried deleting the node_modules folder and reinstalling all of the packages but the issue remains.
Also, I've tried adding it to the vite SSR config:
vite: {
    ssr: {
      noExternal: ['astro-compress']
    }
}

When I remove astro-compress from my integrations I get no errors and everything works as expected.

Hope we can fix this, thanks! 😀

Sorry, does v2.1.2 fix it for you?

Or v2.1.3

Thanks for the reply, I will try it in an hour or so and get back to you with feedback. 😁

Roll back to v2.0.15 for now.

Roll back to v2.0.15 for now.

I've just installed v2.1.3 and guess what?
It works! Both the build and dev command.
Thanks, @NikolaRHristov. 😀

Crazy, I've deprecated for now. Will test and release new ones later. 😁


[3.7.0] Duplicated Quest Objectives

General information:
Project issue is for:
Server? Maybe Modules?
Expected result:
Turning in any item as part of a quest objective doesn't duplicate objectives.
Actual result:
Objectives are duplicated.
When items are turned in as part of a quest objective and that particular objective is completed, it will duplicate the objectives in the task screen visually. Leaving the trader and opening them up again shows the normal amount of objectives.
How to reproduce:

Accept a non-radiant quest that has a turn in objective
Retrieve necessary items for turn in
Turn them in to complete that one objective, doesn't have to complete the whole quest

Log files:
Attached
Profile:
Attached
Screenshots:
Attached
Notes
It only seems to occur on normal quests. Dailies and weeklies are not affected as far as I can tell.

Attachments

image_2023-09-28_121126953.png (193 KiB)
Duplicated Objectives.zip (97 KiB)

Originally written by PhantomInTime

Pub user confirmed this is a Live issue. Closing this ticket.

Originally written by PhantomInTime


Create branches for GeoNode, mapstore adapter and mapstore client

As agree with @afabiani the development work for Nexus will be done inside GeoSolutions' repositories. For the bootstrp of Nexus GN project we will need dedicated branches for GeoNode, django-mapstore-adapter and geonode-mapstore-client.
The following steps are a prerequisite for the creation of the GeoNode project for Nexus:

[x] check the alignment of (and in case align) our three repo to the upstream ones
[x] create a branch named "nexus" from the master of each of them

@giohappy done
geosolutions-it/{geonode; mapstore-adapter; mapstore-client} have been:

Aligned master branches to upstream
Created nexus branches


I want to have invoice number generated properly

Instead of generating UUID, right now invoice id's pattern looks like this:
y/m/sequenceNumber

Since using both slashes and backslashes occurred to be problematic, replacing them with hyphens was consulted with @CoderMaggie

Thanks Bartek 🥄


[th2-1988/th2-2212] split connection and limited attempts for RabbitMQ

From https://github.com/th2-net/th2-common-j/pull/164 and https://github.com/th2-net/th2-common-j/pull/170.
Relates to:

https://github.com/th2-net/th2-estore/pull/29
https://github.com/th2-net/th2-mstore/pull/27
https://github.com/th2-net/th2-codec-sailfish/pull/109
https://github.com/th2-net/th2-codec-generic/pull/57

Out of date


Kubexit does not shutdown child when tombstone is written before it is started

Hi again!
I'm back with a new race condition that we discovered while running jobs with kubexit on a very busy cluster. We have a job with 2 containers. Let's call them A and B. B is a sidecar for A. That means B is shutdown by kubexit whenever A exits. In the same way, A waits for B to be started before it starts up (birth dependency).
Most of the time, B is correctly shutdown. However, we have encoutered a case in which the cluster is very busy and the sidecar container is not executed directly. This causes A to timeout while waiting for B and a tombstone is written. However, after some time B is still started and this tombstone seems to be ignored. See the logs below.
Log for A:
2020-08-07T08:52:44.293468982Z Name: a
2020-08-07T08:52:44.293489226Z Graveyard: /tools
2020-08-07T08:52:44.293493754Z Tombstone: /tools/a
2020-08-07T08:52:44.293496807Z Birth Deps: b
2020-08-07T08:52:44.293596327Z Death Deps: N/A
2020-08-07T08:52:44.293607134Z Birth Timeout: 30s
2020-08-07T08:52:44.293668456Z Grace Period: 30s
2020-08-07T08:52:44.293674509Z Pod Name: <job-pod-name-redacted>
2020-08-07T08:52:44.293678070Z Namespace: default
2020-08-07T08:52:44.293827152Z Watching pod updates...
2020-08-07T08:52:44.313168690Z Event Type: ADDED
2020-08-07T08:53:14.293834919Z Error: timed out waiting for birth deps to be ready: 30s
2020-08-07T08:53:14.293863713Z Skipping ShutdownNow: child process not running
2020-08-07T08:53:14.293868155Z Waiting for child process to exit...
2020-08-07T08:53:14.293871619Z Pod Watch(<job-pod-name-redacted>): done
2020-08-07T08:53:14.295046706Z Child Exited(-1): exec: not started
2020-08-07T08:53:14.295057380Z Updating tombstone: /tools/a

Log for B:
2020-08-07T08:53:45.421230593Z Name: b
2020-08-07T08:53:45.421250095Z Graveyard: /tools
2020-08-07T08:53:45.421253775Z Tombstone: /tools/b
2020-08-07T08:53:45.421257170Z Birth Deps: N/A
2020-08-07T08:53:45.421260596Z Death Deps: a
2020-08-07T08:53:45.421276535Z Birth Timeout: 30s
2020-08-07T08:53:45.421280010Z Grace Period: 30s
2020-08-07T08:53:45.421283380Z Pod Name: N/A
2020-08-07T08:53:45.421338269Z Namespace: N/A
2020-08-07T08:53:45.421349512Z Watching graveyard...
2020-08-07T08:53:45.421353055Z Starting: <child-command-redacted>
2020-08-07T08:53:45.423142247Z Creating tombstone: /tools/b
2020-08-07T08:53:45.423483854Z Tombstone modified: b
2020-08-07T08:53:45.423494806Z Tombstone modified: b
2020-08-07T08:53:45.423498733Z Waiting for child process to exit...
2020-08-07T08:53:45.464698537Z <some logs for child here>

Notice the timestamps: B is started at 08:53:45, while A was already finished at 08:53:14. I think kubexit ignores existing tombstones when launching. When I have some spare time, I will look into it.

For future reader (and me), there are some working forks:

https://github.com/acquia/fn-kubexit
https://github.com/Musixmatchdev/kubexit


refactor(schematics): add drawing for CDK shared logic

Adds a drawing which has been created before implementing the shared schematic logic with the CDK. This drawing should be in the repository because it avoids recurring questions about the CLI workflow.

Can you run pngcrush on this image? It reduces the size by 25%
Also the commit type is really docs

Done. Saved about 80KB.


[CAMEL-19462] Add threadId to simple language

Description
Fix https://issues.apache.org/jira/browse/CAMEL-19479

Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[x] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[ ] I formatted the code using mvn -Pformat,fastinstall install && mvn -Psourcecheck

Could you please rebase on main to fix the test results?

Also add this to the doc page, see simple-language.adoc file

The error is about source code is changed - the build process now automatic format code according to a standard, so you may need to just rebuild the code in the PR and push the source changes to trigger new build.


Add rake task to scrape rubocop documentation

This adds the docs:scrape rake task which will pull down the rubocop
repo and scrape all of the cops for class documentation and insert it
into markdown files.
This uses regular expresses to extract and manipulate the class
documentation since working with YARD and RDoc like this isn't
straightforward.

Can you make this rake task a part of the Dockerfile build process?

@GordonDiggs @BlakeWilliams We should make a way to have the docs task pinned to a specific repo/SHA.

Would something like this work?
TAG = 0.34.2
%x{cd rubocop-git && git checkout tags/#{TAG}}

@GordonDiggs Would adding a RUN command to run this task in the Dockerfile be an acceptable way of handling that?

@BlakeWilliams Looks reasonable to me yes

@BlakeWilliams yep exactly. Make sure it's after the point at which we copy the repo's files into the image.
And, now that it's part of the build process, we can probably remove the md files from the repo itself.

@GordonDiggs Great idea, added.

Tests fail locally now unless you run rake scrape:docs before the tests. Thoughts on migrating the tests to run in the docker container?

@GordonDiggs Can I get a re-review or +1 when you get a chance?

LGTM


Summary output report formats?

Does Project IceStorm toolchain (yosys, arachne-pnr, IceStorm Tools) have some type of standard output format for getting reports about things like;

Messages like info, warnings & errors (for all stages)

Synthesis information like;

Parameters set for modules
Optimisations applied
Transformations
Component + Blackbox Statistics / Usage
etc

Place & Route like;

Resource usage
Timing information
etc

The reason I'm asking is that in my CI system, I would like to track how a design is changing over time. For example, I would like to understand if merging a change will dramatically increase resource usage, introduce new warnings, etc.
I don't quite know what would be the most useful to track yet, so also open to suggestions there :-). I don't really want the extreme low level details, more high level and hierarchical summaries.
I eventually hope to write some crappy Python scripts which translate the proprietary tools (like Vivado and ISE) into the Yosys / OpenFPGA formats to reuse the tracking for designs I can't yet use the open tools for.
Thank you for your help!

Yosys uses special functions to log warnings and errors. But there is no API yet for writing them to an extra file. (By in -q mode only warnings and errors are printed to stdout.)
The Yosys command stat prints resource usage statistics. You can run something like tee -o stat.txt stat as last command in your Yosys script.
Practically all of the Yosys log is "Optimisations applied" and "Transformations". You can run a command with trace to print additional trace information for every design change caused by the command (for example trace opt).

Hi,
I used a blif file to input Arachne-pnr for place and route. I got outputs that are .asc and txt format. Can I get .blif file from Arachne after Place and route, Just like VPR? Is there any possibility to get a blif file from arachne-pnr after place and route.
Thanks

note that stat now has a -json output: https://yosyshq.readthedocs.io/projects/yosys/en/latest/cmd/stat.html


Add manual DHCP configuration feature for end user.

A requestor asked to be able to manually configuring DHCP settings.

Setting static DHCP IP assignments can be done externally on DHCP server instead.


CA - Register a New Account

I would like to set up a user account with ReportStream.

Name: Steve Jordan
Job Title: Project Manager
Organization: Birdrock Laboratories
Email<EMAIL_ADDRESS>Phone:<PHONE_NUMBER>
Referring Organization: CalREDIE
State: California

The expected volume would be about 100/day. I don’t think the lab is reporting to any other states.

My schedule is flexible, so either I or one of my colleagues can be on a call any time between 8:00 AM and 6:00 PM Eastern any day this week.

Sent back to CADOH. Sender wanted to send via SFTP to us.


Different outputs for same input image

Feeding in the same image multiple times produces different orientation estimations each time. Does anyone know why this would be the case?

Well obviously if the model is not in eval() mode the dropout still occurs!

i think it model is not stable maybe so every time the predict orientation will be different


Important announcement about  from the author !!!

Dear users of ants:
I am apologetically telling you that I have to dump all tags which already presents in ants repository.
The reason why I'm doing so is to standardize the version management with Semantic Versioning, which will make a formal and clear dependency management in go, by go modules, godep, or glide, etc. You could find more details in Semantic Versioning and Semantic Import Versioning (very thankful to @jjeffcaii and @zplzpl who provided the suggestions about it).
I ought to apologize for the bothers brought by this change, the prime arch-criminal who leads to this issue would be my lack of concept about Semantic Versioning, I will spend more times learning the knowledge afterwards.
Once again, sorry for your costs in this change and thanks for your support to ants!
Have fun!
Best regards,
Andy Pan

Well done! Thanks~ 👏


Last Week in Pony - June 2, 2019

The recording of this week's Pony developer sync is available here: https://sync-recordings.ponylang.io/r/2019_05_28.m4a


Skip 0-quantity lines in infracost output

This is a follow-up from https://github.com/infracost/infracost/issues/929#issuecomment-934338954
v0.9.10 behavior
Repro steps for v0.9.10:
update examples/terraform/infracost-usage.yml to set the lambda usage values to 0

infracost breakdown --path examples/terraform --usage-file examples/terraform/infracost-usage.yml --format json > out1.json

infracost output --path out1.json --format table # Notice how 0-cost lines are shown for Lambda, same happens in HTML format.

Desired behavior
The breakdown command will not show 0-quantity lines in HTML and table formats, the infracost output --format table|html commands should do the same.
Repro steps:
update examples/terraform/infracost-usage.yml to set the lambda usage values to 0

build/infracost breakdown --path examples/terraform --usage-file examples/terraform/infracost-usage.yml # Notice how 0-quantity lines are not output (correct behavior)

build/infracost breakdown --path examples/terraform --usage-file examples/terraform/infracost-usage.yml --format > out.json

build/infracost output --path out.json --format table # Notice how lambda prices are shown, and the usage params don't seem to have applied
build/infracost output --path a.json --format html > out.html # Same thing happens as the above line

I expected to hidden lines - OR at the least similar behavior as v0.9.10 so it seems like there's a bug in the master branch too.

[ ] Also update https://github.com/infracost/docs/pull/99/files#diff-127ccf771949de22c36f72306c28f3f448853733f173a2f658d4d6f5464de803R37 as part of this

This works as desired for me in master and also the cmd/output_test shows it working ok: https://github.com/infracost/infracost/pull/1042/files#diff-c3a03a689d47c1177fd9acb84db5a1e46976449a39fb3e8f7630458b7d36bd86
Could you try again with latest master?  Theres a typo in your instructions above where --format isn't followed by  json:

build/infracost breakdown --path examples/terraform --usage-file examples/terraform/infracost-usage.yml --format > out.json

@tim775 you're right, I'm not sure what I was doing wrong before. Thanks!


Add helper methods to update HVAC schedules

I added the ability to update the hvac schedule similar to how charge schedules are updated.

Is there anything else I should do ?

Is there anything else I should do ?

I split the PR, to have the breaking change/deprecation in one, and keep the new feature separate.
Both have been merged now.
Do you need me to publish a release?

Thanks !
Yes, would be great if you could publish a new release. That way I can continue with updating the integration in Home Assistant.


Run YOLO-NAS on Mobile Phones and Edge Devices

This is just an expression of our admiration for the outstanding performance of your open-source YOLO-NAS model. I am writing this on behalf of "EdgeStore", a company that specializes in enabling users to run AI models on mobile phones and edge devices.
Since deploying machine learning models on mobile and edge devices can be challenging, we have developed software development kits (SDKs) to make it easy for users to harness the power of your YOLO-NAS model on any mobile phone and edge device.
We would be delighted to provide you with a demonstration of our SDKs and would love to schedule a call or meeting to discuss further. Please let me know your availability and the best time and channel for us to connect.  Thanks.

Hello, we extend ou gratitude for your active involvement and response. We are eager to arrange a conversation with you to discuss the SDK and explore potential pathways forward. To facilitate this, we kindly request you to reach out to Yaniv Tager via email at<EMAIL_ADDRESS>Your consideration is greatly appreciated.


Fix overflow bug

Some attempts to control the stat growth rate that ends up in overflows. It requires some changes in the way stat increases are computed.
This still needs some testing and code cleanup.
Fixes #21

closing for now, I'm going to try with a different approach


Increase testcontainers library version

The main intention is the next fix
Move away from using quay.io for default images (#2805) @rnorth

Codecov Report

Merging #325 into develop will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop     #325   +/-   ##
==========================================
  Coverage      86.59%   86.59%
  Complexity       513      513
==========================================
  Files            131      131
  Lines           1693     1693
  Branches          31       31
==========================================
  Hits            1466     1466
  Misses           214      214
  Partials          13       13

Continue to review full report at Codecov.

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


Upvoting in example-forum demo broken

Hi,
it seems like the upvoting feature of the example-forum demo is broken. Specifically, two things do not work as expected:

A single user can upvote one post several times. How can this be prevented?
When clicking the up vote button, the counter first jumps back by one, then increases by one (i.e. from 2 to 1 and then quickly to the correct value 3).

I am using a fresh install of the the latest version eb5f6aada70db7296a26be44f190c2fa27e056ba on Ubuntu 18.04 and enabled the example-forum in .meteor/packages.
Any help appreciated.

Voting is handled in the vulcan:voting package. Help is welcome to fix this issue. We probably won't be able to maintain such packages in the future, voting looks simple but is actually a complex issue if you don't want people to be able to cheat and you want to handle concurrent calls.


Use displayName if it exists for completion display text

Tern completion for required module returns name (module wuith quote) and displayName (module without quote). This PR gives the capability to display completion for required module without quote.

Thanks! Merged as b8c4ea1


Fix typo in slm response type name

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

jenkins test this


Add bitzh.txt

@Unknow-404 I am sorry, the domain bitzh.edu.cn is removed from our trusted domains list because the school allows to register an email address there even if you are not a student of the school. If you are the student of this school, please apply with official document (OFFICIAL DOCUMENT tab at https://www.jetbrains.com/shop/eform/students).


Bonfire: Pig Latin - Incorrect test case

In Bonfire: Pig Latin, one of the test cases is: translate("glove") should return "oveglay".
Whereas according to Pig Latin, translate("glove") is supposed to return "lovegay".

Though from example, it seems like the problem statement should be modified to say repeat till you find consonant(s) but this is not what is expected from this problem. May I know what correctness did you found out in this issue from your end to close this issue?


Retry with Ribbon & Feign client doesn't work sometimes. Throws error "LoadBalancer [service-name]:  Error choosing server for key null"

Using Spring Boot 2.0.0.RC2 & Cloud 2.0.0.M7. Having following setup,
Zuul Gateway - Replica 1
Edge service - Replica 2
Micro service - Replica 2
Following are the configurations,
ribbon:
  ConnectTimeout: 5000
  ReadTimeout: 10000
  MaxAutoRetries: 0
  MaxAutoRetriesNextServer: 2
  retryableStatusCodes: 404,502,504

hystrix:
  shareSecurityContext: true

feign:
  hystrix:
    enabled: false

health.config.enabled: false

spring.cloud.loadbalancer.retry.enabled: true

zuul:
  retryable: true
  sensitiveHeaders: Cookie
  ignoredServices: '*'
  ribbon:
    eager-load:
      enabled: true
  routes:
    user-service:
      path: /users/**
      stripPrefix: true
    product-edge:
      path: /products/**
      stripPrefix: true

With the above configuration, I was testing Blue/Green deployment. I made one replica down, immediately got the following response from Edge service,
com.netflix.loadbalancer.BaseLoadBalancer    LoadBalancer [product-service]:  Error choosing server for key null
java.lang.IndexOutOfBoundsException: index (2) must be less than size (2)
	at com.google.common.base.Preconditions.checkElementIndex(Preconditions.java:310)
	at com.google.common.base.Preconditions.checkElementIndex(Preconditions.java:292)
	at com.google.common.collect.RegularImmutableList.get(RegularImmutableList.java:65)
	at com.netflix.loadbalancer.AbstractServerPredicate.chooseRoundRobinAfterFiltering(AbstractServerPredicate.java:203)
	at com.netflix.loadbalancer.PredicateBasedRule.choose(PredicateBasedRule.java:45)
	at com.netflix.loadbalancer.BaseLoadBalancer.chooseServer(BaseLoadBalancer.java:736)
	at com.netflix.loadbalancer.ZoneAwareLoadBalancer.chooseServer(ZoneAwareLoadBalancer.java:113)
	at com.netflix.loadbalancer.LoadBalancerContext.getServerFromLoadBalancer(LoadBalancerContext.java:481)
	at com.netflix.loadbalancer.reactive.LoadBalancerCommand$1.call(LoadBalancerCommand.java:184)
	at com.netflix.loadbalancer.reactive.LoadBalancerCommand$1.call(LoadBalancerCommand.java:180)
	at rx.Observable.unsafeSubscribe(Observable.java:10151)
	at rx.internal.operators.OnSubscribeConcatMap.call(OnSubscribeConcatMap.java:94)
	at rx.internal.operators.OnSubscribeConcatMap.call(OnSubscribeConcatMap.java:42)
	at rx.Observable.unsafeSubscribe(Observable.java:10151)
	at rx.internal.operators.OperatorRetryWithPredicate$SourceSubscriber$1.call(OperatorRetryWithPredicate.java:127)
	at rx.internal.schedulers.TrampolineScheduler$InnerCurrentThreadScheduler.enqueue(TrampolineScheduler.java:73)
	at rx.internal.schedulers.TrampolineScheduler$InnerCurrentThreadScheduler.schedule(TrampolineScheduler.java:52)
	at rx.internal.operators.OperatorRetryWithPredicate$SourceSubscriber.onNext(OperatorRetryWithPredicate.java:79)
	at rx.internal.operators.OperatorRetryWithPredicate$SourceSubscriber.onNext(OperatorRetryWithPredicate.java:45)
	at rx.internal.util.ScalarSynchronousObservable$WeakSingleProducer.request(ScalarSynchronousObservable.java:276)
	at rx.Subscriber.setProducer(Subscriber.java:209)
	at rx.internal.util.ScalarSynchronousObservable$JustOnSubscribe.call(ScalarSynchronousObservable.java:138)
	at rx.internal.util.ScalarSynchronousObservable$JustOnSubscribe.call(ScalarSynchronousObservable.java:129)
	at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:48)
	at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:30)
	at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:48)
	at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:30)
	at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:48)
	at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:30)
	at rx.Observable.subscribe(Observable.java:10247)

Getting these exceptions frequently, so retry logic is breaking. MaxAutoRetriesNextServer: 2, but available servers are only 2, not 3. So this case the bounds have to be checked before execution.

We are going to need more information.  To start with nothing in that stacktrace points to anything in Spring Cloud Netflix.  Is there more in the logs that would point to some code in Spring Cloud Netflix?

The same problem, spring cloud M8。

Apologies it took some time to get back. Here is the code repo, which I have tried repo Here is the complete log of Zuul gateway log

I am seeing this exact issue with Boot 1.5.10 and Edgware (RELEASE, SR1, SR2) too. I found this merged PR in Ribbon which seems to fix it.
It is a problem introduced fairly recently, in the 2.2.4 release of Ribbon, which is used by spring-cloud-netflix 1.4.x. There is no release > 2.2.4 yet, so downgrading to Dalston was the only viable option for me. Once the next release of Ribbon is out, this will be an easy fix.

Thanks @grelland.
@spencergibb do you think we should downgrade to 2.2.3?  Doesnt look like the bug is in that release.

sure, we can ask for a release as well.

This suggest the quick solution to disable the ribbon's circuit breaker.
niws:
loadbalancer:
availabilityFilteringRule:
filterCircuitTripped:  false  # defaults to true
https://yangdongdong.org/2017/12/31/spring-cloud-feign/
@spencergibb, @ryanjbaxter  Is it right way to go for now ?

I am not sure if that property will make a difference or not.  You can try overriding the ribbon dependencies in your applications POM to use version 2.2.3.

@ryanjbaxter we have the same issue. Can you please help me, how do I override ribbon dependency in POM to use version 2.2.3? I do not see a dependency for Ribbon in POM. Also, the latest version for Ribbon I see in Maven is 2.0.1.

The latest Finchley release is using 2.2.5 https://github.com/spring-cloud/spring-cloud-netflix/blob/v2.0.2.RELEASE/spring-cloud-netflix-dependencies/pom.xml#L20


Re-factor post processing of activate primary mode into a listener

Is your feature request related to a problem? Please describe.

This change addresses the comment: https://github.com/opensearch-project/OpenSearch/pull/10839#discussion_r1368241785

Please lets add better description to indicate the nature of problem better
[Storage Triage - attendees 1 2 3 4 5 6 7 8 9]

Will add description of the issue.


rhsm_register in 14.x unable to register with RHSM

Description
RHSM_Register appears to be failing when registering new hosts to RHSM from RH, and it may be related to IBM killing a URL RH maintained for a long time.
Chef Version
14.12.9  (baked into template; updating is a chicken/egg issue at least)
Platform Version
rhel 7
Replication Case
  rhsm_register node[:hostname] do
    activation_key      node.run_state['rhsm']['actikey']
    force               false
    install_katello_agent node.read(:install_katello_agent)||false
    organization        node.run_state['rhsm']['org']
  end.run_action(:register)

.. which looks like this in execution:
vsphere_virtual_machine.sat02(chef):     rhsm_register("sat02") do
vsphere_virtual_machine.sat02(chef):       action [:nothing]
vsphere_virtual_machine.sat02(chef):       default_guard_interpreter :default
vsphere_virtual_machine.sat02(chef):       declared_type :rhsm_register
vsphere_virtual_machine.sat02(chef):       cookbook_name "linux-rhsm"
vsphere_virtual_machine.sat02(chef):       recipe_name "_register"
vsphere_virtual_machine.sat02(chef):       activation_key ["valid_key"]
vsphere_virtual_machine.sat02(chef):       organization "90210"
vsphere_virtual_machine.sat02(chef):       satellite_host "xmlrpc.rhn.redhat.com"
vsphere_virtual_machine.sat02(chef):       install_katello_agent false
vsphere_virtual_machine.sat02(chef):       only_if { #code block }
vsphere_virtual_machine.sat02(chef):     end

Client Output

vsphere_virtual_machine.sat02(chef):   * rhsm_register[sat02] action register
vsphere_virtual_machine.sat02(chef):     * yum_package[subscription-manager] action install
vsphere_virtual_machine.sat02(chef):  (up to date)
vsphere_virtual_machine.sat02(chef):     * remote_file[/var/chef/cache/katello-package.rpm] action create
vsphere_virtual_machine.sat02(chef): [2020-03-26T23:27:36+00:00] WARN: remote_file[/var/chef/cache/katello-package.rpm] cannot be downloaded from http://xmlrpc.rhn.redhat.com/pub/katello-ca-consumer-latest.noarch.rpm: 404 "Not Found"

It's trying to download a cert kit, and IBM removed it.  The URL's busted.  There is no new URL.

Please note all old RHN URLs are deprecated and removed. Follow below steps[sic] to register systems to the portal and to install Satellite 6.

[monkey-hitting-buttons non-automated simplistic commands and FAQ followed the statement.  There was nothing below the steps, despite suggestion there would be]
Stacktrace

Hi @tas50 and @btm,
In order to reproduce this issue there are some information required,
There are certain parameters required to write the recipe for example
satellite_host
organization
For these parameters do we have any setup ready or how can I proceed?
Please suggest your thoughts.

RHSM_register resource, steps that I followed:

Register with RedHat developers portal. click here

Once I had the developer subscription, go to download the KVM image ie. rhel 8

Follow the 'guestfish' directions (ref: https://access.redhat.com/discussions/664843) to change the root password:

Note that on Ubuntu sudo apt install libguestfs-tools to get guestfish, then use guestfish via sudo to change the password. the image has no password by default for root (not a blank password, no password, because whatever)

OR

Use virt-customize to change the root password:

sudo virt-customize -a rhel-8.2-update-2-x86_64-kvm.qcow2 --root-password password:PASSWORD --uninstall cloud-init

Open virt-manangersudo virt-manager

After selecting rhel-8 VM for booting and login into provided image root password.

rhel has subscription-manager to manage the subscriptions

subscription-manager register --username <username> --password <password> --auto-attach

Note: After a successful subscription using the developer license account satellite server is not enabled to use, we required to have a satellite server running. The blocker here to the required account which includes the satellite server.
Ref: https://access.redhat.com/discussions/3351011


Add js.BigInt

JS's BigInt is available in popular JS runtime like Chrome, Firefox, and Node.js.
Its specification reached stage 4, so I think it is good time to add support it in Scala.js.
https://github.com/tc39/ecma262/pull/1515
https://github.com/tc39/proposals/pull/217
TODO:

[x] BigInt
[ ] BigInt64Array
[ ] BigUint64Array

Could you try amending the commit (without changes) and force-push the branch again? It seems the CI did not pick up your PR.


URL broken for ResNet50, 101, 152

First of all, thank authors for the neat repo!
When I tested "type": "UNetResnet" and "backbone": "resnet50",  there is a bug caused by bad url in this line
I got this error.
python train.py --config config.json
python train.py --config config.json
Downloading: "https://s3.us-west-1.wasabisys.com/encoding/models/resnet50s-a75c83cf.zip" to ./pretrained/resnet50s-a75c83cf.zip
Traceback (most recent call last):
  File "/usr/lib/python3.8/urllib/request.py", line 1354, in do_open
    h.request(req.get_method(), req.selector, req.data, headers,
  File "/usr/lib/python3.8/http/client.py", line 1256, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/lib/python3.8/http/client.py", line 1302, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/lib/python3.8/http/client.py", line 1251, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/lib/python3.8/http/client.py", line 1011, in _send_output
    self.send(msg)
  File "/usr/lib/python3.8/http/client.py", line 951, in send
    self.connect()
  File "/usr/lib/python3.8/http/client.py", line 1425, in connect
    self.sock = self._context.wrap_socket(self.sock,
  File "/usr/lib/python3.8/ssl.py", line 500, in wrap_socket
    return self.sslsocket_class._create(
  File "/usr/lib/python3.8/ssl.py", line 1040, in _create
    self.do_handshake()
  File "/usr/lib/python3.8/ssl.py", line 1309, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 's3.us-west-1.wasabisys.com'. (_ssl.c:1131)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "train.py", line 60, in <module>
    main(config, args.resume)
  File "train.py", line 25, in main
    model = get_instance(models, 'arch', config, train_loader.dataset.num_classes)
  File "train.py", line 15, in get_instance
    return getattr(module, config[name]['type'])(*args, **config[name]['args'])
  File "/home/zilxi06/teaching/tsbb19_semantic_segmentation/models/unet.py", line 129, in __init__
    model = getattr(resnet, backbone)(pretrained, norm_layer=nn.BatchNorm2d)
  File "/home/zilxi06/teaching/tsbb19_semantic_segmentation/models/resnet.py", line 264, in resnet50
    model.load_state_dict(load_url(model_urls['resnet50'], model_dir=root))
  File "/home/zilxi06/teaching/tsbb19_semantic_segmentation/models/resnet.py", line 300, in load_url
    urlretrieve(url, cached_file)
  File "/usr/lib/python3.8/urllib/request.py", line 247, in urlretrieve
    with contextlib.closing(urlopen(url, data)) as fp:
  File "/usr/lib/python3.8/urllib/request.py", line 222, in urlopen
    return opener.open(url, data, timeout)
  File "/usr/lib/python3.8/urllib/request.py", line 525, in open
    response = self._open(req, data)
  File "/usr/lib/python3.8/urllib/request.py", line 542, in _open
    result = self._call_chain(self.handle_open, protocol, protocol +
  File "/usr/lib/python3.8/urllib/request.py", line 502, in _call_chain
    result = func(*args)
  File "/usr/lib/python3.8/urllib/request.py", line 1397, in https_open
    return self.do_open(http.client.HTTPSConnection, req,
  File "/usr/lib/python3.8/urllib/request.py", line 1357, in do_open
    raise URLError(err)
urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 's3.us-west-1.wasabisys.com'. (_ssl.c:1131)>

Apparently, the link is broken. I tried to replace it with this link found in this page. However, I got another error. How to fix this? Thank you.
python train.py --config config.json
Downloading: "https://download.pytorch.org/models/resnet50-19c8e357.pth" to ./pretrained/resnet50-19c8e357.zip
Traceback (most recent call last):
  File "train.py", line 60, in <module>
    main(config, args.resume)
  File "train.py", line 25, in main
    model = get_instance(models, 'arch', config, train_loader.dataset.num_classes)
  File "train.py", line 15, in get_instance
    return getattr(module, config[name]['type'])(*args, **config[name]['args'])
  File "/home/zilxi06/teaching/tsbb19_semantic_segmentation/models/unet.py", line 129, in __init__
    model = getattr(resnet, backbone)(pretrained, norm_layer=nn.BatchNorm2d)
  File "/home/zilxi06/teaching/tsbb19_semantic_segmentation/models/resnet.py", line 264, in resnet50
    model.load_state_dict(load_url(model_urls['resnet50'], model_dir=root))
  File "/home/zilxi06/teaching/tsbb19_semantic_segmentation/models/resnet.py", line 301, in load_url
    zip_ref = zipfile.ZipFile(cached_file, 'r')
  File "/usr/lib/python3.8/zipfile.py", line 1269, in __init__
    self._RealGetContents()
  File "/usr/lib/python3.8/zipfile.py", line 1336, in _RealGetContents
    raise BadZipFile("File is not a zip file")
zipfile.BadZipFile: File is not a zip file

Just checked, the links seem to work, can you please double check?


Package seems broken on ppc64le

The conda-forge feedstock gained a ppc64le build, but it looks completely broken, see https://github.com/conda-forge/pywavelets-feedstock/pull/42. We don't have ppc64le CI on this repo, which is probably the right thing to add, rather than debug on conda-forge.

Test results in gh-508 are better (only 2 failures), so part of this may be conda-forge specific.

The conda-forge builds are also emulated, which can sometimes run into unique issues
Other thing worth noting (maybe obvious though) is conda-forge is building with the last release. So any changes here since the last release may have fixed issues we are seeing in the conda-forge builds in the interim

So any changes here since the last release may have fixed issues we are seeing in the conda-forge builds in the interim

I don't think there were any that would have fixed what we're seeing there. Emulation could well be the problem here though.

The conda-forge builds are also emulated, which can sometimes run into unique issues

Are all ppc64le feedstocks being moved from Travis to Azure? If emulation is the problem, can you not move back to Travis?

@carterbox, if you would like to explore fixing the ppc64le packages, that would be welcome :)

@jakirkham, I would be happy to try, but I am still wondering if y'all have any insight into why a bot moved the package from Travis to Azure in the first place.

Similar test errors for swt with PyPy on Linux aarch64 and on x86-64 macOS, see https://github.com/conda-forge/pywavelets-feedstock/pull/53#issuecomment-1732584146. That has full tracebacks; the test_swt_roundtrip_dtypes test failure overlaps with ppc64le, shows RuntimeError: C wavelet transform failed with error code 4.. And error code 5 also shows up.
The error is happening on line 272 of _swt.pyx:
                cD = np.zeros(output_shape, dtype=np.complex128)
                with nogil:
                    retval = c_wt.double_complex_downcoef_axis(
                        <double complex *> data.data, data_info,
                        <double complex *> cD.data, output_info,
                        wavelet.w, axis,
                        common.COEF_DETAIL, common.MODE_PERIODIZATION,
                        i, common.SWT_TRANSFORM)
                if retval:
                    raise RuntimeError(
                        "C wavelet transform failed with error code %d" %
                        retval)

That code is full of casts, and assumptions like size_t and Py_ssize_t being compatible. That's probably true but not guaranteed. A bit hard to untangle.


Cannot find "c:\CR14-emulator-for-CatGenie-120-master_a\CR14-emulator-for-CatGenie-120-master\include".

Hi
I keep getting this message.
my configuration (working with blink example) is:
[env:ATmega328P]
platform = atmelavr
framework = arduino
Upload_speed = 57600
board = ATmega328P
targets = upload, monitor
lib_deps =
    Wire

Any idea?

Sorry, no. Its been ages since I worked on this.


Investigate how to best unbundle prepackaed langauges

With VS Code 1.21 we started to support language packs. We should now start to think about how to best unbundle pre-packaged language and used language packs instead. This transition period should be for existing users as smooth as possible. So may be we still ship the pack and installed it if shipped. For new users it is OK to ask them to download a language pack.

Under Construction
I propose to do the following to un-bundle the prepacked languages:

for the core languages we also create language packs and publish them to the market place except for English. This will always ship pre-bundled.
we ship all core languages bundled as well for the next n months.
when VS Code starts and the UI is in one of the core languages we download the translation from the market place and install the extension.
when VS Code starts and detects an extension for one of the core languages we use the extension instead of the bundled one. We could even do some A/B testing here but since the translations should be the same there is no win.
after n months we remove the core languages from VS Code (except English).

This approach ensures a smart transition for users that already use a UI other than English. They basically don't see any differences to today.
For users that install a fresh version of Code at a point in time were we only ship English the experience would be as follows:

UI comes up in English
a message is shown that there is a language pack for the UI language used by the OS and whether the user wants to install it. This message must be in English and the UI language used by the OS (the user might not speak English and with our current solution the UI would come up in the UI language of the OS).

@ramya-rao-a  @sandy081 can you please read and comment.

Sounds good. Hard coding the message in the core languages is the simplest way to go. Hidden tags for just one message feels like an overkill

In my model we need to have the messages for all languages. Would be cool if someone runs in Bulgarian and he sees a message in Bulgarian and English. This is how Windows behaves as well.

when VS Code starts and the UI is in one of the core languages we download the translation from the market place and install the extension in the background. This requires work from @sandy081

If this is when VS Code is bundled with core languages then Why do we need to download from Marketplace? I think this should be needed when VS Code is not bundled with core languages and user had set up VS Code before with one of the core languages.
When VS Code is not bundled with core languages, Downloading during start up will impact the start up performance (only the time we download) and what do we do if user is offline? I think we have two cases here:
Users with VS Code installed before and go through update cycle

While updating, download the lang pack if the user is using a core lang pack. This will regress the behaviour that user cannot simply set the locale to other core languages. User has to install the language pack before setting.

While updating, download all core language packs

Users with VS Code installed before and install/download VS Code again
Users with fresh install of VS Code

Have the same experience as for new User?
Did we think about a Installation wizard asking the language to pick?

Regarding message in OS Language, I would not go for tags. Hardcoding them for all languages is not practical. As @dbaeumer said, it can help for some (core+known) languages but not if there is a new. I think reading it from the package.json is a good option in which case we should come up with a property in package.json to be used. What if the extension does not provide the message in package.json? We might need a validation check while generating the vsix.

If this is when VS Code is bundled with core languages then Why do we need to download from Marketplace?

To have a smooth migration for existing users. So we will switch them to language packs without them noticing and difference in the UI. If we first unbundle all core language then they will be promoted to download their language pack. This is to avoid that prompt.
We though about doing this in update, but we have different update stories for Mac, Windows, Deb, RPM and I was trying to come up with one solution instead of 4 :-).
New users will get a different experience (even for the current core language) since at some point we will ship English only. For them I think it is important that they see at least the 'language pack instsall message' in their UI language.

To have a smooth migration for existing users. So we will switch them to language packs without them noticing and difference in the UI. If we first unbundle all core language then they will be promoted to download their language pack. This is to avoid that promp

I think it is a good idea to download the lang pack extensions from Marketplace while they are bundled with VS Code to prepare for next step. This would need confirmation from user to download. Downloading without asking might not be good. I think this can also be done while checking for the VS Code update and inform the user that update to next version of VS Code need to install so and so language pack extensions.

Agree on the fact that we need to let the user know that we are donwloading language packs.

@ramya-rao-a I assume now work has happened for the messages. I will move the item to Mai to keep it so that we can finish things up.

Just a quick note, in case it helps with task tracking related to this issue: if I'm understanding correctly, after this change is completed, the wiki page Visual Studio Code Community Localization Project (particularly the Language set section) will have to be updated to reflect the new setup, right?

@waldyrious Yes, thanks for bringing this up

@dbaeumer @sandy081
@kieferrm and I have the below proposal for the message that prompts the user to search/install the language pack corresponding to their display UI language

There are 3 such strings. One the actual message, and the other 2 for the actions on the notification.
Include the message and the accompanying text on the actions, as strings to be localized in the product, such that they get picked up by folks over at transifex. This is especially helpful for new languages over time
During endgame, pull these localized strings into the product.
When the language being shown is English, but users display language is different and we have the above strings localized in the display language, the prompt will say something like There are extensions in the Marketplace that can localize VS Code using the ${0} language
The first action would be Search Marketplace which will pre-fill the search text in the Extensions view with the tag for corresponding locale. Example: tag:lp-pt-br. The second action would be Don't show again
The reason I suggest Search Marketplace instead of Install extension is that in the future there can be multiple extensions providing localization for the same language. Instead of taking sides, we let the user decide.

https://github.com/Microsoft/vscode/commit/43d48b10177e1e919e7d0b7702fafe913fa3a4a4 is how it would look like if we pulled these localized strings into the product.json file.
The decision still pending in this proposal is the place where we pull this strings. Is product.json ok or we have a dedicated json file for this?

Yes, we can show the Install instead of Search Marketplace in the below cases

For languages packs of the form MS-CEINTL.vscode-language-pack- i.e the ones from the https://github.com/Microsoft/vscode-loc repo. This would include the core languages plus anything that we publish from transifex
Run the search before hand behind the scenes and show "Install" if there is only 1 result.

In my commit, the "bundled" languages do not refer to the bundled languages as we know and understand today. They are hard-coded localized strings that we should ship in product (either as a separate json file or in product.json).

btw the work done for #44012 was pointless. The recommendation there is based on the platform.language which never is non English for non core languages unless there is a language pack installed.
So the prompt there appeared when the user has already installed an language pack and the platform.language wasnt an exact case match with the locale used in the package json file of the extension

@ramya-rao-a

In my commit, the "bundled" languages do not refer to the bundled languages as we know and understand today. They are hard-coded localized strings that we should ship in product (either as a separate json file or in product.json).

I understand this part. But how about the fallback strings that are getting localised using nls?
localize('searchForLanguagePacks', "Your locale is not supported by VS Code. There are extensions in the marketplace that can localize VS Code.");

They will be shown in the User language (OS) only when user starts  VS Code in that language. If I am not wrong, we do not ship any localisations out of the box and they have to come from language pack extensions themselves. So I am wondering when will the user see the fallback strings in user language if no language pack is installed.

@ramya-rao-a

btw the work done for #44012 was pointless. The recommendation there is based on the platform.language which never is non English for non core languages unless there is a language pack installed.
So the prompt there appeared when the user has already installed an language pack and the platform.language wasnt an exact case match with the locale used in the package json file of the extension

Agreed. Only corner case I see is, When a user configures locale which is not current OS language and no language pack is installed and starts VS Code?

I would be great if we don't have to pull in any strings from transifex during building anymore. This will simplify the build and the coordination with the translation team. So I suggest to do the following:

for our 9 core languages we get them translated once and then 'copy' them into our source code. These strings should be fairly stable anyways.
for other languages we put them into the package.json. When creating the extension the vsce file puts them into the vsix manifest so we can get them using on get request without downloading the whole vsix. The only little downside is that we can't show the string when offline. But we wouldn't be able to install the extension so this might not be bad.

To get the OS locale / requested locale you can use platform.locale instead of platform.language

@sandy081

Only corner case I see is, When a user configures locale which is not current OS language and no language pack is installed and starts VS Code?

In that case platform.locale would have the configured locale and platform.language would be English. And so the old prompt would never show
@dbaeumer Updating the vsce tool to get the required strings in the manifest is a good idea. But why have a different approach for the core languages?

@ramya-rao-a only reason is that in the past we bundle the core languages. So I thought we bundle the three strings to make the experience good for the core languages even if no internet exist. But I am fine to do the same for the core languages as well.

@ramya-rao-a I am not sure I understand the PRs correctly. Here is what I thought we do:

we pre-define keys for the translation pack to use.
translations for these strings must be provided by the translation pack in its package.nls.json file
the vsce tool takes these strings and moves them to the manifest for faster access
the VS Code code base only have English version of these strings and they don't go into the nls.localize call since they are not localized.
if a OS locale is used that doesn't correspond to the language pack used and one exists in the marketplace we show the strings from the extension manifest plus the English version of the string (e.g. comparable to the command palette).

I got a little puzzled since the PR against the vsce tool has knowledge about this file in VS Code vs/platform/node/minimalTranslations which I think we should avoid.

@dbaeumer

we pre-define keys for the translation pack to use

Pre-defining keys that need to have their translations in a package.nls.json file is an extra step for the extension authors that we need to document and enforce. Though its a 1 time effort for existing packs, it still needs to be enforced for future packs.
The advantage of the current method is that we get the translations for free without any extra effort by the team managing the https://github.com/Microsoft/vscode-loc/ repo or future language pack authors.
Having a dedicated file (vs/platform/node/minimalTranslations) with nls.localize calls helps the future case where we might want some other string localized even when there is no language pack installed.

we show the strings from the extension manifest plus the English version of the string (e.g. comparable to the command palette)

We usually don't show both localized and English text in prompts/notifications. So, why show both in this case?

@ramya-rao-a then I have to say I don't understand how these translations come into our system. Can you explain to me how these strings lets say for a Bulgarian language pack get into our system / the vsix manifest.
Side note: the final goal of having language packs is that we don't have any i18n folder in our GitHub repository anymore. Everything regarding translation is owned by the translation team. If they want to move from Transfix to another translation platform they can do that without us being majorly affected. We currently push to Transifex but I already changed the scripts so that they can work as an export as well (they generate XLF files in the file system) which then in a second step can be uploaded to any platform that understand XLF.
The package.nls.json is a good point and is for sure confusing for translation pack owner. But we could put them into the package.json directly (which now that I think about it is even better).

Can you explain to me how these strings lets say for a Bulgarian language pack get into our system / the vsix manifest

The strings in vs/platform/node/minimalTranslations get localized to Bulgarian just like any other string in VS Code (via transifex today, or any other way in the future) and become part of the language pack
The vsce tool will extract the translations for vs/platform/node/minimalTranslations file and put it in the manifest
VS Code queries the marketplace, finds the language pack, queries its manifest to get the translations.

At no point above we depend on the i18n folder of our Github repo.

If they want to move from Transfix to another translation platform they can do that without us being majorly affected.

How the strings get translated doesnt matter to this PR. The only thing matters is that they get translated in the language pack.

OK. Now I understand it. There is one thing to it though: currently we don't enforce a language pack to be complete. That means if these strings aren't translated they will be replaced with their English version when generating them. So it could easily happen that these strings might not be there in Bulgarian. Forcing them into package.json made it more obvious that these strings are mandatory in the Bulgarian language for example.

I agree with @dbaeumer here that making these special strings part of regular translations will be confusing. Because, when you are creating a Language pack extension it is not clear about these special strings and not sure what happens if I do not provide translations to these strings. I think these strings are special in a way and extension authors should know what these strings are and when they are used.
To be simpler and clear, I would probably have an optional property extensionRecommendationPromptTranslations (or something appropriate) to the schema
"localizations": [
      {
        "languageId": "abc",
        "languageName": "abc",
        "languageNameLocalized": "abc",
        "translations": [
          {
            "id": "vscode",
            "path": ""
          }
        ],
        "extensionRecommendationPromptTranslations": {
          "recommendatonMessage": "",
          "searchMarketplaceActionLabel": "Search MarketPlace in abc language",
          "installAndRestartActionLabel": ""
        }
      }
    ],

This property can be written into the vsix manifest and will be read while recommending the extension in VS Code. I think this will be clear to the author why and when this property is needed and will not overlap with general translations.

@dbaeumer

if these strings aren't translated they will be replaced with their English version.

Is that so bad? The vsce tool already has many other validations in place. We can add one more to check if there are no translations to extract for the vs/platform/node/minimalTranslations.ts file. Something like: "The strings in the file vs/platform/node/minimalTranslations.ts are the bare minimum you need to translate for this extension to be a valid language pack"
@sandy081

How about having an optional property extensionRecommendationPromptTranslations?

If its optional, then we still don't avoid the case of the strings not being translated.
The recommendation message differs based on whether we are asking the user to install or search. So, in total there are 5 strings. Install msg, Search msg, Install label, Install & Restart label, Search label. I have a feeling it will get complicated to describe each of these.
Say, the extension author hand-writes the package.json file, how do we communicate what each of these strings are for? Say the extension author uses yo code` to generate the extension initially and we pre-fill these strings, how do we ensure that the extension author updates these strings? In the current approach, the strings get translated without any extra thought process by the extension author. The translation system takes care of it
We could add checks in the vsce tool similar to the one that we have that ensures that the README has been updated. But, we could do the same for the current approach in the PR as well.

I am also worried that vsce will now have knowledge of these translation files for reading the strings.

If we have the strings directly added to the package.json by the extension author, the vsce tool will now have to be aware of each of the 5 strings and validate that they get translated/changed. How is that any better than being aware of a single special file which is deemed as the bare minimum translations?
Yes, I agree that the vsce tool is now aware of the vs/platform/node/minimalTranslations.ts file, but the advantage is that this solution scales. For any which reason, in the future we need to display a message that we deem important enough to be translated, there is no extra work to be done by us. We just put that string in this file, and when it gets translated, it is available for use.

@sandy081  and I discussed it offline and we decide to go with the current solution. If possible we should warn the user about the fact that these translations are mandatory or at least document it.

@dbaeumer Looks like @ramya-rao-a is throwing an exception in vsce if these minimum translations are not found

@ramya-rao-a I updated the implementation to read the core translations file from market place. Core translations file is added as an asset to the vsix.

@sandy081 thanks.

@joaomoreno FYI: I have to remove the asset types filter and ask for all asset types so that I can get locale translations assets. Please see the change set #684b7e7.

@ramya-rao-a We would like to have insiders running without core languages for at least one milestone before going to stable. If translations team is ready, we can start 1.25.insiders without core languages and ship 1.25 stable without them.

Agree with @sandy081 suggestion.

I would close this issue and create a new one for the remaining work.

Thanks @sandy081 @dbaeumer
Logged https://github.com/Microsoft/vscode/issues/50588 for the June milestone to cover the rest

@ramya-rao-a Can you provide a list of what should be verified as part of this issue? There are several scenarios mentioned here

@RMacfarlane Sorry about that. The test plan item covers everything. I'll remove the verification-needed label


Apollo V3

cc: @targos

This upgrades Apollo to V3
Changes how upload config is passed in
Extracts playground.ts file from ApolloV2

We will at some point want to use the new Apollo Landing Page but this is passed in a plugin and I could not figure out how to connect this properly.
For now we are able to have everything work the same way as before just using Apollo V3

@targos I am also facing this issue
src/schema.ts:15:17 - error TS2742: The inferred type of 'getTypeDefsAndResolvers' cannot be named without a reference to '@graphql-tools/merge/node_modules/@graphql-tools/utils'. This is likely not portable. A type annotation is necessary.

15 export function getTypeDefsAndResolvers(
                   ~~~~~~~~~~~~~~~~~~~~~~~

The only way i have been able to fix it is to remove declaration from tsconfig but I am sure that is not what you want. If you have any ideas please do tell

Codecov Report

Merging #34 (fcd20ae) into main (39d9bdd) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #34   +/-   ##
=======================================
  Coverage   91.66%   91.66%
=======================================
  Files           3        3
  Lines          48       48
  Branches       13       13
=======================================
  Hits           44       44
  Misses          4        4

Impacted Files
Coverage Δ

src/schema.ts
100.00% <ø> (ø)

Continue to review full report at Codecov.

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

@devotox thanks for the PR. I took inspiration from it and migrated to Apollo v3 in https://github.com/zakodium/adonis-apollo/commit/2b07ac0067b2f7a0ce73983125301d45b82b1020.
I installed the playground using an apollo landing page as you linked to.
I also added you as a co-author on that commit, I hope that's ok :)


Margins

Amount of blue space before "BYU" on left is perfect. Please add padding on the right side of menu icon to match.

Fixed in latest commit.


Install to lib instead of lib64

Set install lib directory to prevent mismatch on different platforms (it can be lib64 on certain platforms by default). Otherwise the exported $LIB_PATH can be incorrect.

This fix should not belong at this level. It's the responsibility of the ecbuild component to know where to install the libraries. Overriding here will only obscure the problem.

Codecov Report

Merging #139 (3cf92c1) into main (3e81775) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main     #139   +/-   ##
=======================================
  Coverage   95.57%   95.58%
=======================================
  Files          11       11
  Lines         565      566    +1
  Branches      142      142
=======================================
+ Hits          540      541    +1
  Misses         25       25

Impacted Files
Coverage Δ

src/build-package.ts
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


RuntimeError: Index put requires the source and destination dtypes match, got BFloat16 for the destination and Float for the source.

Hi,
I am trying to apply the generate recipe on a quantized llama 3.1 8B model but run into the following error:
...
  File "/home/mreso/torchtune/torchtune/modules/attention.py", line 211, in forward
    k, v = self.kv_cache.update(input_pos, k, v)
  File "/home/mreso/torchtune/torchtune/modules/kv_cache.py", line 69, in update
    k_out[:, :, input_pos] = k_val
RuntimeError: Index put requires the source and destination dtypes match, got BFloat16 for the destination and Float for the source.

I looked a bit through the code of torchtune and torchao and found that the linear layers like k_proj are wrapped with Int8DynActInt4WeightLinear which has a precision argument that seems to get used here to determine the precision of the computation. Its default value is float32 and it seems to be unaffected buy the model.to(dtype) call here.
> /home/mreso/torchtune/generate.py(77)_setup_model()
-> model.load_state_dict(model_state_dict)
(Pdb) print(model.layers[0].attn.q_proj.precision)
torch.float32

Thus the value thats gets used to updated the kv cache is float32 instead of bloat16.
Trying to set the precision in the configuration only results in this error:
  File "generate.py", line 74, in _setup_model
    model = self._quantizer.quantize(model)
  File "/home/mreso/.conda/envs/tune/lib/python3.10/site-packages/torchao/quantization/GPTQ.py", line 1014, in quantize
    state_dict = self._create_quantized_state_dict(model)
  File "/home/mreso/.conda/envs/tune/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 116, in decorate_context
    return func(*args, **kwargs)
  File "/home/mreso/.conda/envs/tune/lib/python3.10/site-packages/torchao/quantization/GPTQ.py", line 989, in _create_quantized_state_dict
    weight.to(self.precision),
RuntimeError: Invalid device string: 'bfloat16'

Not sure if there is a way to set the precision correctly from the config.
Happy to create a PR to create a dtype for the precision from the string or something.
Steps to reproduce
tune run quantize --config quantize.yaml

quantize.yaml:
# Config for QuantizationRecipe in quantize.py
#
# To launch, run the following command from root torchtune directory:
#    tune run quantize --config quantization

#
# Model arguments
model:
  _component_: torchtune.models.llama3_1.llama3_1_8b

checkpointer:
  _component_: torchtune.utils.FullModelMetaCheckpointer
  checkpoint_dir: Meta-Llama-3-8B-Instruct/
  checkpoint_files: [
    meta_model_0.pt
  ]
  recipe_checkpoint: null
  output_dir: ./quantized
  model_type: LLAMA3

device: cuda
dtype: bf16
seed: 1234
max_seq_len: 2048

quantizer:
  _component_: torchtune.utils.quantization.Int8DynActInt4WeightQuantizer
  groupsize: 256

tune run generate --config generate.yaml

generate.yaml:
# Config for running the InferenceRecipe in generate.py to generate output from an LLM
#
# To launch, run the following command from root torchtune directory:
#    tune run generate --config generation

# Model arguments
model:
  _component_: torchtune.models.llama3_1.llama3_1_8b
  max_seq_len: 2048

checkpointer:
  _component_: torchtune.utils.FullModelTorchTuneCheckpointer
  checkpoint_dir: quantized/
  checkpoint_files: [
    meta_model_0-8da4w.pt
  ]
  output_dir: model-output
  model_type: LLAMA3

device: cuda
dtype: bf16

seed: 1234

# Tokenizer arguments
tokenizer:
  _component_: torchtune.models.llama3.llama3_tokenizer
  path: /home/mreso/.cache/huggingface/hub/models--meta-llama--Meta-Llama-3.1-8B-Instruct/snapshots/8c22764a7e3675c50d4c7c9a4edb474456022b16/original/tokenizer.model

# Generation arguments; defaults taken from gpt-fast
prompt: 'Amanda: I baked  cookies. Do you want some?\nJerry: Sure \nAmanda: I will bring you tomorrow :-)'
# instruct_template: torchtune.data.SummarizeTemplate
#chat_format: null
max_new_tokens: 300
temperature: 0.6 # 0.8 and 0.6 are popular values to try
top_k: 300
enable_kv_cache: True

quantizer:
  _component_: torchtune.utils.quantization.Int8DynActInt4WeightQuantizer
  groupsize: 256
#  precision: bfloat16 # uncommenting this results into second error

Full Logs
Full error stack trace:
INFO:torchtune.utils.logging:Starting compilation to improve generation performance ...
Traceback (most recent call last):
  File "/home/mreso/.conda/envs/tune/bin/tune", line 8, in <module>
    sys.exit(main())
  File "/home/mreso/torchtune/torchtune/_cli/tune.py", line 49, in main
    parser.run(args)
  File "/home/mreso/torchtune/torchtune/_cli/tune.py", line 43, in run
    args.func(args)
  File "/home/mreso/torchtune/torchtune/_cli/run.py", line 179, in _run_cmd
    self._run_single_device(args)
  File "/home/mreso/torchtune/torchtune/_cli/run.py", line 93, in _run_single_device
    runpy.run_path(str(args.recipe), run_name="__main__")
  File "/home/mreso/.conda/envs/tune/lib/python3.10/runpy.py", line 289, in run_path
    return _run_module_code(code, init_globals, run_name,
  File "/home/mreso/.conda/envs/tune/lib/python3.10/runpy.py", line 96, in _run_module_code
    _run_code(code, mod_globals, init_globals,
  File "/home/mreso/.conda/envs/tune/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/home/mreso/torchtune/recipes/generate.py", line 204, in <module>
    sys.exit(main())
  File "/home/mreso/torchtune/torchtune/config/_parse.py", line 50, in wrapper
    sys.exit(recipe_main(conf))
  File "/home/mreso/torchtune/recipes/generate.py", line 200, in main
    recipe.generate(cfg=cfg)
  File "/home/mreso/.conda/envs/tune/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 116, in decorate_context
    return func(*args, **kwargs)
  File "/home/mreso/torchtune/recipes/generate.py", line 151, in generate
    _ = utils.generate(
  File "/home/mreso/.conda/envs/tune/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 116, in decorate_context
    return func(*args, **kwargs)
  File "/home/mreso/torchtune/torchtune/utils/_generation.py", line 122, in generate
    tokens = generate_next_token(
  File "/home/mreso/torchtune/torchtune/utils/_generation.py", line 47, in generate_next_token
    logits = model(x, input_pos=input_pos)[:, -1]
  File "/home/mreso/.conda/envs/tune/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1736, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/home/mreso/.conda/envs/tune/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1747, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/mreso/torchtune/torchtune/modules/transformer.py", line 243, in forward
    h = layer(h, mask=mask, input_pos=input_pos)
  File "/home/mreso/.conda/envs/tune/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1736, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/home/mreso/.conda/envs/tune/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1747, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/mreso/torchtune/torchtune/modules/transformer.py", line 72, in forward
    attn_out = self.attn(self.sa_norm(x), mask=mask, input_pos=input_pos)
  File "/home/mreso/.conda/envs/tune/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1736, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/home/mreso/.conda/envs/tune/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1747, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/mreso/torchtune/torchtune/modules/attention.py", line 211, in forward
    k, v = self.kv_cache.update(input_pos, k, v)
  File "/home/mreso/torchtune/torchtune/modules/kv_cache.py", line 69, in update
    k_out[:, :, input_pos] = k_val
RuntimeError: Index put requires the source and destination dtypes match, got BFloat16 for the destination and Float for the source.

Hey @mreso , thank you so much for flagging this! Your PR would definitely be welcomed.

Happy to create a PR to create a dtype for the precision from the string or something.
Would it use the already defined dtype, or it would be a new argument?
Can the kvache infer the dtype from the input or the model weights, so the user dont have to declare any new dtype?

Thanks for pointing it out! Regarding the kv cache, I chatted with @pbontrager, and apparently .item() is not necessary there. We can use something like size(dim).
I read your issue paying a bit more attention, and I have a couple of questions:

Its default value is float32 and it seems to be unaffected buy the model.to(dtype) call here.
I guess this would be the main issue. I find it odd that you say its unaffected, since we train our models on bf16. Maybe we should try to dig more here first?

Then there is a second error:

RuntimeError: Invalid device string: 'bfloat16'
i think thats because it should be "bf16", not "bfloat16":

what do you think?

Hi @felipemello1
Thanks for looking into this again.
So the bf16 vs bfloat16 is a good catch, though this is only true for dtype in the main part of the config. Using this for the quantizer precision produces the same error as the string is never converted into a dtype when funneled from the config into the constructor of the quantizer:
  File "/home/mreso/torchtune/recipes/generate.py", line 72, in _setup_model
    model = self._quantizer.quantize(model)
  File "/home/mreso/.conda/envs/tune/lib/python3.10/site-packages/torchao/quantization/GPTQ.py", line 1014, in quantize
    state_dict = self._create_quantized_state_dict(model)
  File "/home/mreso/.conda/envs/tune/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 116, in decorate_context
    return func(*args, **kwargs)
  File "/home/mreso/.conda/envs/tune/lib/python3.10/site-packages/torchao/quantization/GPTQ.py", line 989, in _create_quantized_state_dict
    weight.to(self.precision),
RuntimeError: Invalid device string: 'bf16'

Note that for this error I am not setting dtype but precision for the quantizer:
quantizer:
  _component_: torchtune.utils.quantization.Int8DynActInt4WeightQuantizer
  groupsize: 256
  precision: bf16

precision is a parameter of the quantizer constructor but it does not accept a string (only dtype).
Regarding the quantizer not being affected by .to(), the quantizer replaces the linear layers with Int8DynActInt4WeightLinear which is derived from nn.Module so its parameters will be afftected by .to() but precision is just an unregistered class variable which will not change:
https://github.com/pytorch/ao/blob/b523f9f9e15b6fb80d10f585d9cf45e0c5e4d10e/torchao/quantization/GPTQ.py#L927
Making this to be affected by .to() would either mean overwriting .to() or registering a parameter with nn.Module and extract the parameters dtype while calling forward here. Both not very nice options.
Probably better to either change the constructor of Int8DynActInt4WeightQuantizer to not only accept dtype for precision but strings as well and then use something like this to convert strings to dtypes.
Or convert the string between reading from config and constructing the quantizer as proposed above.

@felipemello1 Turns out the precision in the quantizer was a red herring.... it actually needs to be float32 to capture the result of the matmul (see the inductor error mentioned above). I've now casted the tensors of k,v,q to the right dtype and made minor changes to make it compile. Will put the changes in a PR for further discussion.

Here is the PR: #1371


User's hmrOptions are ignored by plugin-svelte

I could not preserveLocalState to work in my svelte plugin
  plugins: [
    [
      '@snowpack/plugin-svelte', { hmrOptions: { preserveLocalState: false } }  // This is ignored
    ],
    '@snowpack/plugin-dotenv',
    '@snowpack/plugin-typescript',
  ],

Dove into the source and found that the spread operator is not properly used here. This results in the user's settings being completely ignored. Fix: Move the user's option to the bottom.
https://github.com/snowpackjs/snowpack/blob/a420855a8a6765f25f17335e381ca1299b8e5311/plugins/plugin-svelte/plugin.js#L133,L139

Good catch, fixing this here: 5662f019c0f19fb829e14fa9c20ca82fa7edcc77

Good catch, fixing this here: 5662f019c0f19fb829e14fa9c20ca82fa7edcc77

PS: In the future, please use a discussion instead!

PS: In the future, please use a discussion instead!

Was wondering where any issue guidelines were! They're only visible when creating through the green "New issue" button. So when creating an issue like I did, you don't get that issue warning:

Was wondering where any issue guidelines were! They're only visible when creating through the green "New issue" button. So when creating an issue like I did, you don't get that issue warning:

np :) That flow may have clobbered our new issue template, which was written to point to discussions. Good to know!

np :) That flow may have clobbered our new issue template, which was written to point to discussions. Good to know!


Deployment to Azure App Service

Can this project be deployed to Azure App Service? The concern lies on the dependency on SQL LocalDB?
I really appreciate any help you can provide.

Please share the template details. Also, for each of the template lab documentation will be provided,
https://www.azuredevopslabs.com/
This might help you.


PSPC ported to Rust

Closes #1781

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2126  👈
#1782
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Shoeboxam and the rest of your teammates on  Graphite


don't fall off the end of the deltas into garbage

./ProofOfSpace prove ffffff11239639109fd2ecdfff3f51457f9f805a5294fbee660a5f89c9e11683

I'm working on a fix now.

Not sure why the test fail... But I tried chia plots check and it seemed good


src: changing test dir structure

Related to #1

When learning and looking some configuration I saw the there is configuration in package.json:
"test": "mocha -r ts-node/register test/**/*.ts",
and tsconfig:
"include": [
    "src/**/*.ts"
  ],

Our test dir is outside src not sure if it is wrong or right in terms of best and/or well known approach but it is working

yeah, me too.
I was mainly showing this "include" (including only src) which is weird but let's move forward :+1:


Add the watch command

What problem does this feature solve?
I love the new vue-cli. npm run serve and npm run build are very nice, but with Phoenix/Elixir, I don't want to use the dev server. Instead, I want that Webpack watches for changes and produces it's build in the dist directory.
What does the proposed API look like?
npm run watch

So you don't want to use Hot Module reloading?
I don't know if you're aware, but the usual way to deal with "3rd party" backend API servers is to still use the dev-server, and proxy API requests through it to the API backend.
That way, you usually get the best of both worlds: A fully featured dev server with Hot module reloading for your frontend app, and your own instance of the backend server to go with it
However if you still want this, I think this would be a good feature to implement with a plugin, as I don't think this is a prime use case with this this tmplate.

That’s a good question. And yes, I want HMR.
Phoenix comes with a Hot Module Reloading that is enabled with websockets (I guess just as webpack-dev-server). I rather use Phoenix's one instead of webpack-dev-server. This way, only one instance of web server is running. I can manage my routes to distinguish between the API calls, etc.
One workaround is to run the Phoenix server and the webpack server together, but that’s flacky. I wonder how other uses cases fonction (ex: with Node/Express).
Thanks for the quick reply.
JPB

Le 20 févr. 2018 à 16:51, Thorsten Lünborg<EMAIL_ADDRESS>a écrit :
So you don't want to use Hot Module reloading?
I don't know if you're aware, but the usual way to deal with "3rd party" backend API servers is to still use the dev-server, and proxy API requests through it to the API backend.
That way, you usually get the best of both worlds: A fully featured dev server with Hot module reloading for your frontend app, and your own instance of the backend server to go with it
However if you still want this, I think this would be a good feature to implement with a plugin, as I don't think this is a prime use case with this this tmplate.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/vuejs/vue-cli/issues/860#issuecomment-367149075, or mute the thread https://github.com/notifications/unsubscribe-auth/AEaHzQxkHvQAXhe6d8EYb-idX6zcZ2mmks5tW0x2gaJpZM4SMxLR.

I doubt Phoenix's HMR is the same web webpack-dev-server (WDS)'s - the former probably reloads the page when a new js bundle is delivered, while the latter has fine-grained HMR that preserves application state.
Also, since WDS performs compilation in memory, it should also result in faster dev builds than writing the whole bundle to disk on every change (and then waiting for that to be picked up by Phoenix).
Running Phoenix and WDS side by side is actually the recommended approach, and it isn't that complex: you just need to specify your phoenix server's local address in vue.config.js as devServer.proxy, and the dev server can automatically figure out what requests to proxy in most cases: https://github.com/vuejs/vue-cli/blob/dev/docs/cli-service.md#configuring-proxy

Thanks Evan,
You’re right, running the two servers side by side might be a better approach.
Thanks!

Le 21 févr. 2018 à 15:10, Evan You<EMAIL_ADDRESS>a écrit :
I doubt Phoenix's HMR is the same web webpack-dev-server (WDS)'s - the former probably reloads the page when a new js bundle is delivered, while the latter has fine-grained HMR that preserves application state.
Also, since WDS performs compilation in memory, it should also result in faster dev builds than writing the whole bundle to disk on every change (and then waiting for that to be picked up by Phoenix).
Running Phoenix and WDS side by side is actually the recommended approach, and it isn't that complex: you just need to specify your phoenix server's local address in vue.config.js as devServer.proxy, and the dev server can automatically figure out what requests to proxy in most cases: https://github.com/vuejs/vue-cli/blob/dev/docs/cli-service.md#configuring-proxy https://github.com/vuejs/vue-cli/blob/dev/docs/cli-service.md#configuring-proxy
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/vuejs/vue-cli/issues/860#issuecomment-367473202, or mute the thread https://github.com/notifications/unsubscribe-auth/AEaHzcx-noqGErw5nHsTJqv8YN4wdgw-ks5tXIYxgaJpZM4SMxLR.

If my index.html is like this (requires the server to render it)
DEMO:
<script>
window._ServerData = _SERVER_REPLACE_;
</script>

Need npm run watch
Or are there other recommendations?

Please use the forum for support.
forum.vuejs.org


[ bugfix 2055 ]

error with the handling on slider refresh
happens when going to a breakpoint with more slides to show than actual
slides.
fixed bad condition structure.

fixes #2055

Can you update the npm version to 1.5.10?

@simeydotme how are we looking for a release?


Add HTTPS

Sauce Labs added HTTPS support several months ago.

I signed it!
On Mon, Feb 6, 2017 at 2:24 PM, googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project. Before we can look at your
pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll
verify. Thanks.

If you've already signed a CLA, it's possible we don't have your
GitHub username or you're using a different email address. Check your
existing CLA data https://cla.developers.google.com/clas and verify
that your email is set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
If you signed the CLA as a corporation, please let us know the
company's name.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/protractor/pull/4070#issuecomment-277834014,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIvKeUqqJhfjiAeERetKCJEWZnWiXGcSks5rZ52lgaJpZM4L4zFF
.

--
Kevin Berg
Solution Engineer | Sauce Labs
539 Bryant Street, Suite 303
San Francisco, CA 94107
(M)<PHONE_NUMBER>
(O)<PHONE_NUMBER>
Sauce Labs http://saucelabs.com/ | Sauce blog http://sauceio.com/
http://www.saucecon.com

I signed it!
On Mon, Feb 6, 2017 at 2:26 PM, googlebot<EMAIL_ADDRESS>wrote:

We found a Contributor License Agreement for you (the sender of this pull
request), but were unable to find agreements for the commit author(s). If
you authored these, maybe you used a different email address in the git
commits than was used to sign the CLA (login here
https://cla.developers.google.com/ to double check)? If these were
authored by someone else, then they will need to sign a CLA as well, and
confirm that they're okay with these being contributed to Google.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/protractor/pull/4070#issuecomment-277834596,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIvKeZQk2p96lJsoSqjSSPaBYeUw-Gtfks5rZ54ogaJpZM4L4zFF
.

--
Kevin Berg
Solution Engineer | Sauce Labs
539 Bryant Street, Suite 303
San Francisco, CA 94107
(M)<PHONE_NUMBER>
(O)<PHONE_NUMBER>
Sauce Labs http://saucelabs.com/ | Sauce blog http://sauceio.com/
http://www.saucecon.com


:seedling: improve the verify-crd-compatibility make target

for use during local development by making the default updated source be the local file, picking up changes not yet committed. The previous git sourcing required changes to be committed to be picked up and is not a very good developer experience as you should validate the changes prior to commiting them. Since the git source is necessary for CI, the GitHub Action is updated to specify the git source for the updated file.

Reviewer Checklist

[ ] API Go Documentation
[ ] Tests: Unit Tests (and E2E Tests, if appropriate)
[ ] Comprehensive Commit Messages
[ ] Links to related GitHub Issue(s)

⛔ This should be held, unless we consider it a bug.

/hold

/lgtm

unholding as v1 has been released :tada:


Merge inferred types correctly for elements having no child but attributes

https://github.com/databricks/spark-xml/issues/72
This PR corrects type inference so that this can find a proper compatible type from two different types when the field corresponding with valueTag.
Currently, this library infers the schema having duplicated fields corresponding with valueTag when the types are different.
Since one of the original tests is related with this, I just correct the test and the data.

Current coverage is 89.41%

Merging #96 into master will decrease coverage by -0.06% as of 6caa786

@@            master     #96   diff @@
======================================
  Files           14      14
  Stmts          627     633     +6
  Branches        82      82
  Methods          0       0
======================================
+ Hit            561     566     +5
  Partial          0       0
- Missed          66      67     +1

Review entire Coverage Diff as of 6caa786

Powered by Codecov. Updated on successful CI builds.

I am going to merge this.


Manuel Install version v0.28.2 - Error php artisan migrate

Describe the bug
Impossible to create database during Manuel Install
Steps To Reproduce
Follow doc for manuel install : https://www.bookstackapp.com/docs/admin/installation/#manual
During cmd : php artisan migrate
Expected behavior
$ php artisan migrate
**************************************
*     Application In Production!     *
**************************************

 Do you really wish to run this command? (yes/no) [no]:
 > y

   Illuminate\Database\QueryException  : SQLSTATE[HY000] [2002] No such file or directory (SQL: select * from information_schema.tables where table_schema = books and table_name = migrations and table_type = 'BASE TABLE')

  at /Users/xx/temp/bookstack/shared/BookStack/vendor/laravel/framework/src/Illuminate/Database/Connection.php:669
    665|         // If an exception occurs when attempting to run a query, we'll format the error
    666|         // message to include the bindings with SQL, which will make this exception a
    667|         // lot more helpful to the developer instead of just the database's errors.
    668|         catch (Exception $e) {
  > 669|             throw new QueryException(
    670|                 $query, $this->prepareBindings($bindings), $e
    671|             );
    672|         }
    673|

  Exception trace:

  1   Doctrine\DBAL\Driver\PDOException::("SQLSTATE[HY000] [2002] No such file or directory")
      /Users/xx/temp/bookstack/shared/BookStack/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php:31

  2   PDOException::("SQLSTATE[HY000] [2002] No such file or directory")
      /Users/xx/temp/bookstack/shared/BookStack/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php:27

  Please use the argument -v to see more details.

Your Configuration (please complete the following information):

Exact BookStack Version (Found in settings):
PHP Version: PHP 7.3.11 (cli) (built: Dec 13 2019 19:21:21) ( NTS )
Hosting Method (Nginx/Apache/Docker): Apache

Additional context
On Mac OS X Catalina

Hi @sebastienhouzet,
Have you created a books database within MySQL/MariaDB before running the migrate command?

Yes of course, and i have tried to connect to mysql with credentials.

@sebastienhouzet Okay, Thanks for confirming. Could you try setting the DB_HOST value to <IP_ADDRESS> instead of the default localhost? See if that helps at all.

not working.
Possible problem is ' missing on SQL ?
SQL: select * from information_schema.tables where table_schema = books and table_name = migrations and table_type = 'BASE TABLE'
for 'books' and 'migrations' ?

@sebastienhouzet I think that would cause a different error message if that was to be the issue.
The "Best Answer" here may help, Looks like a common thing on mac setups that the MySQL socket is not configured to the correct place in the PHP install:
https://laracasts.com/discuss/channels/eloquent/sqlstatehy000-2002-no-such-file-or-directory

Does it work?

Hello,
No it doesnt work :/

Hi,
Mine work with after so much if tried with the below configuration.
.env file
DB_CONNECTION=mysql
DB_HOST=<IP_ADDRESS>
DB_PORT=3306
DB_DATABASE=paradiseblog
DB_USERNAME=root
DB_PASSWORD=admin@123
config/database.php
mysql' => [
'driver' => 'mysql',
'url' => env('DATABASE_URL'),
'host' => '<IP_ADDRESS>',
'port' => 3306,
'database' => 'paradiseblog',
'username' => 'root',
'password' => 'admin@123',
'unix_socket' => '',
'charset' => 'utf8mb4',
'collation' => 'utf8mb4_unicode_ci',
'prefix' => '',
'prefix_indexes' => true,
'strict' => true,
'engine' => null,
'options' => extension_loaded('pdo_mysql') ? array_filter([
PDO::MYSQL_ATTR_SSL_CA => env('MYSQL_ATTR_SSL_CA'),
]) : [],
],
Note: mysql version 8.0.19 with php version 7.3.11 and laravel version 7.1.3
Mysql installation setup path /usr/local/mysql-8.0.19-macos10.15-x86_64/bin/mysql
Hope this is would work you.
Thanks

@sebastienhouzet Are you also using MySQL8 by any chance?

No i am using MySQL 5.6

Hi @sebastienhouzet,
Sorry this dropped off. Are you still having issues you need resolving?
If so, could you confirm if you're using the native PHP/Apache/MySQL components in MacOS or some other installed versions?

Since the last comment on this issue is relatively old I'm going to close this. If the issue remains and is something you still require to be fixed please open a new issue, referencing this one.

Since the last comment on this issue is relatively old I'm going to close this. If the issue remains and is something you still require to be fixed please open a new issue, referencing this one.

thank u @alpha1892 finally migration worked for me


Add 5.6 nightly CI

The 5.6 nightly images are available, let's use them.
@tomerd can you add a 5.6 builder here?

Created https://ci.swiftserver.group/job/swift-log-swift56-prb/
@swift-server-bot test this please


Bump to api 10

All functionality seemed to work.
New to Dalamud so let me know if there's a goof here.
Added DalamudApiLevel to the .json because I'm not sure how it was enforcing it before.
Removing "IsDataValid" is based on an assumption that apiX's MarketBoard functionality is ensuring validity.

If you're removing isDataValid, can you remove all references to _cache too?

Done


Add cross-platform strategy

A simple way to enforce Rheem to not consider cross-platform ExecutionPlans is to add an according PruningStrategy that removes such plans already during the enumeration. Such a feature would allow to "degrade" Rheem to an optimizer towards only platform independence, which is interesting for experiments and comparisons.

This issue was moved to rheem-ecosystem/rheem#28


Update README.md with what the script actually does

The script that's described in README.md is different from the script that's currently available: MFA_NPS_Troubleshooter.ps1. While I understand this has been brought up before (https://github.com/Azure-Samples/azure-mfa-nps-extension-health-check/issues/19, https://github.com/Azure-Samples/azure-mfa-nps-extension-health-check/issues/20) it would be helpful if README.md was updated to reflect what the current script actually does; for instance:

Which tests are available?
What does each test do? (i.e. what does each test create, read, update, and/or delete (CRUD)?)
What's the impact of running each test? (e.g. does the NPS extension need to be stopped and/or restarted?)
What permissions are required to complete each test? (e.g. local administrator on the server, Global Administrator on Azure AD?)

This information would make it easier to make an informed decision with respect to the type of test(s) to run as well as determining the impact(s) of running the test(s); something that's absolutely critical for production NPS environments.

@simbrar49 Thanks for raising this. Huge thanks to @miguel-s-ferreira for revising the Readme!

The update is merged.


How to downgrade the dart version?

I upgrade the dart version to 2.1 in my Windows Env,  but it brokes my project, since one module 'audio-play' throws :
The current Dart SDK version is 2.1.0-dev.3.1.flutter-760a9690c2.
Because ***** depends on audioplayer any which requires SDK version >=1.8.0 <2.0.0, version solving failed.
I try to reinstall the flutter to a old version, and I can sure the dart-sdk is 2.0, but the flutter --version still outpus the dart version is 2.1.
So, I realy want to know how to make my project works, thanks in advance.

You can't downgrade Dart independent of Flutter.
You can only downgrade Flutter to a version that contains the Dart version you desire.
You can also use dependency_overrides to overrule dependency constraints.
https://www.dartlang.org/tools/pub/dependencies#dependency-overrides
dependency_overrides:
  audioplayer: ^0.5.0

Ideally you'd report an issue with the package that claims not to be compatible with Dart 2.0 final
or even better create a pull request with a fix.