[pre-release] Colors Error setting not being applied

Environment data
PS version: 5.1.17763.316
PSReadline version: 2.0.0-beta3
os: 10.0.17763.1 (WinBuild.160101.0800)
PS file version: 10.0.17763.1 (WinBuild.160101.0800)

Steps to reproduce or exception report

`Set-PSReadlineOption -Colors @{ "error" = ConsoleColor::DarkCyan }
Call Get-PSReadlineOption and see the Error is set to nothing.
Use Set-PSReadLineOption -Colors @{ "error" = "#1a570e"}
Call Get-PSReadlineOption and see the Error is set to "$([char]0x1b)[38;2;26;87;14m"

In both cases I cause an error and the output is still showing the default red color text.
Is there something I'm missing to get the error text to display in something other than red?

Regarding 1 - that should be:
Set-PSReadlineOption -Colors @{ "error" = [ConsoleColor]::DarkCyan }

This setting only affects PSReadLine - it does not change PowerShell's error color, e.g. when a command writes an error or throws an exception.
In PSReadLine, you normally see this color in your prompt, but there are a few other places you might see this color.

What purpose is there in changing the error color only for psreadline?

The error color isn't exposed as a proper api in PowerShell, so I never really considered it.
Yes, you can set $host.PrivateData.ErrorForegroundColor, but only in the console host - there are other hosts that use PSReadLine but do not have this proprerty.
To make matters more complicated, the PrivateData properties only support ConsoleColor - so it would be impossible to use an arbitrary VT sequence.


Which multiplatform architectural pattern should I use or build ?

I'm looking for the best (if such thing exists) architectural pattern that would fit with the way apollo handles caching.
I looked at many implementations of different patterns in KMM/KMP, such as MVI, MVVM, VIPER, etc. but they all provide a very thick abstraction layer on the state management, which was to be expected of course. But the app I'm developing being highly dependant on graphql, I can't look away from apollo-graphql, which was my go-to coming from the React Native world (btw, kudos to the Apollo team for the Apollo React client !)
But of course, the state management of these architectural pattern sounds like it will clash with the Apollo cache.
I'm looking for something quite unique and I don't think such implementation already exists due to the newness of KMP, but I'm not opposed to building it on my own. Anyway, here's some key features I'd like to see in such architecture :

Using the Apollo cache as the unique source of truth for state.
Using the Apollo client as the unique networking interface (appart from very specific features)
Maintainable, ui-decoupled (pluggable UI), and highly testable, units/components/modules (call it the way you like)
Declarative UI oriented architecture (SwiftUI & Jetpack Compose & Kotlin React for the web)
Out-of-the-box handling of components lifecycle & navigation routing
Reactive data bindings
Proper documentation
IDE tooling ?

I know it sounds like a big project, and it is. Of course I don't think anyone built something like that, mostly because it is highly tight to the Apollo client. I'd be up to building it on my own, but I'd like to get some feedbacks/clues/thoughts on how such an architecture should be implemented, and even if it's relevant to do something like that.
NB: I'm fairly new to Kotlin & KMP, I come from the fully cross-platform JS mobile world (mostly React Native).
Thanks in advance for your answers.

Hi 👋 . That's something that I'd love to investigate. The reactive nature of the Normalized Cache coupled with declarative frameworks like SwiftUI and Compose could do wonders. I wrote a bit about it there. Most of the compose APIs have changed since that post was written but the concepts stay the same.
All in all, I think some of the building blocks are there:

configure normalized cache as a single source of truth
share a client in a global state (maybe CompositionLocal ?)
use SwiftUI/Compose to render the returned data

Some still need to be done like IDE tooling, testability and navigation (does that last one need to know anything about GraphQL?). Also we could imagine some "glue" to handle common boilerplate code such as loading states, not really sure how that would look like.
If you haven't already, I can only recommend taking a look at https://github.com/joreilly/MortyComposeKMM from @joreilly that contains a state of the art multiplatform GraphQL + Compose + SwiftUI app and would be a nice starting point to write such an app.
Let's keep this issue open for general discussion, do not hesitate to open separate, more specific ones for the individual items.

Hi! Thanks a lot for your answer.
I'll maybe try to build an app that resembles most of the key features listed above, and see what should be abstracted by the hypothetical library/framework. I could then push it on a public repo so that anyone can make suggestions about implementation details.
I think it'd be a good starting point to later isolate reusable or boilerplate code in a separate package until we get a very lean and minimal app, in which all of these key features are outsourced.
What do you think of it?
Before diving into this work, could you please confirm what apollo-android features aren't currently multiplatform ready? Essentially thinking about caching features.
Also, I may found what could be our pluggable-UI/lifecycle-aware components layer in this library. If I read it well, developers could "just" write platform-specific UIs that trigger graphql related operations defined inside the shared module (via library's BLoCs). It also satisfies the navigation routing and components logic testability features. Combined with the Apollo normalized cache, I guess it could be very powerful.

Sounds great! To have multiplatform cache support, you'll have to use the 3.x developer previews. They're available in the com.apollographql.apollo3 maven group. As of speaking, the latest version is com.apollographql.apollo3:apollo-runtime-kotlin:3.0.0-dev10. There's not a lot of documentation yet but feel free to ask questions here or in the apollo-android slack channel on kotlinlang. The dev-3.x branch has a unified runtime between JVM and Kotlin and supports everything from the main branch with the exception of HTTP cache and Java codegen.

I think it'd be a good starting point to later isolate reusable or boilerplate code in a separate package until we get a very lean and minimal app, in which all of these key features are outsourced.

Sounds good 👍 . We can see as we go what can be upstreamed vs what is too specific.

Also, I may found what could be our pluggable-UI/lifecycle-aware components layer in this library.

Never used Decompose myself but will take a look, looks promising!

Closing as stale. Please leave a comment if you want us to reopen.


[BUG] Prettier parser overrides not working

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Parser overrides do not work in .prettierrc
Expected Behavior
Overrides should apply rather than what sfmc decides at runtime
Steps To Reproduce
Create a override and assign a parser in your .prettierc file, it won't work
Version
7.1.4
Environment

OS: Windows
Node: v20.11.0
npm: 10.2.4

Participation

[X] I am willing to submit a pull request for this issue.

Additional comments
No response

will be released together with 7.1.5


Null check operator used on a null value

I have a bug when user download app from store and chplay. The error detected by sentry package. I tried to check my code and i think error is started from your side

this is device.

Hi, I am using photo_view: ^0.13.0 from 5 Oct and the issue that @deremakif described is still present. Could you please fix it)

Thank you!

@renancaraujo, the issue in my previous comment happen with routing, or if you dispose the controller and immediately create a new one to get a new initPosition for exemple.
There is a very simple fix, just protect the nullity with ? instead of enforcing int with ! in the dispose method.
Anyway, enforcing '!' on a method call is a bad pattern and should be avoid 😈 (Otherwise, it should not be nullable but late)
  void removeIgnorableListener(listener) {
    assert(_debugAssertNotDisposed());
    _ignorableListeners!.remove(listener);
  }

  void removeIgnorableListener(listener) {
    assert(_debugAssertNotDisposed());
    _ignorableListeners?.remove(listener);
  }

Let me know if you want a PR for it.
Regards

Any updates on this?

Is this still hapening on 0.14.0?


chore: 💂 update codecov config

Codecov Report
Base: 90.86% // Head: 90.47% // Decreases project coverage by -0.39% :warning:

Coverage data is based on head (b4792d1) compared to base (b47dd92).
Patch coverage: 71.42% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop      #12      +/-   ##
===========================================
- Coverage    90.86%   90.47%   -0.39%
===========================================
  Files           27       27
  Lines          372      378       +6
  Branches        50       54       +4
===========================================
+ Hits           338      342       +4
- Misses          31       32       +1
- Partials         3        4       +1

Impacted Files
Coverage Δ

src/infrastructure/envConfig/envConfig.ts
94.44% <60.00%> (-5.56%)
:arrow_down:

...eadings/synchroniseLatestReadingsCommandHandler.ts
91.48% <100.00%> (+0.18%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


camunda-modeler-linter-plugin does not work with Modeler 5.3.0

Hello,
I copied all the plugins I have from Modeler 5.2 to 5.3, and I received this error.
Thie plug in which failed is the linter:
camunda-modeler-property-info-plugin-master](https://github.com/camunda/camunda-modeler-linter-plugin)
[D:\dev\intellij\community\zeebe-cherry-framework\src\test\resources\connectorworker\connectorworker.bpmn] this.getModeler(...).get(...).deactivate is not a function
    at deactivate (webpack://camunda-modeler-client/src/app/tabs/cloud-bpmn/BpmnEditor.js:187:39)
    at componentDidUpdate (webpack://camunda-modeler-client/node_modules/react-dom/cjs/react-dom.production.min.js:216:295)
    at Vh (webpack://camunda-modeler-client/node_modules/react-dom/cjs/react-dom.production.min.js:220:181)
    at file:///D:/Camunda/camunda-modeler-5.3.0/resources/app.asar/public/bundle.js:2:803376
    at b (webpack://camunda-modeler-client/node_modules/scheduler/cjs/scheduler.production.min.js:18:162)
    at unstable_runWithPriority (webpack://camunda-modeler-client/node_modules/react-dom/cjs/react-dom.production.min.js:250:202)
    at Fi (webpack://camunda-modeler-client/node_modules/react-dom/cjs/react-dom.production.min.js:249:382)
    at Di (webpack://camunda-modeler-client/node_modules/react-dom/cjs/react-dom.production.min.js:248:143)
    at Yh (webpack://camunda-modeler-client/node_modules/react-dom/cjs/react-dom.production.min.js:245:331)
    at Xh (webpack://camunda-modeler-client/node_modules/react-dom/cjs/react-dom.production.min.js:243:85)
    at qf (webpack://camunda-modeler-client/node_modules/react-dom/cjs/react-dom.production.min.js:130:227)
    at enqueueSetState (webpack://camunda-modeler-client/node_modules/react/cjs/react.production.min.js:13:223)
    at file:///D:/Camunda/camunda-modeler-5.3.0/resources/app.asar/public/bundle.js:2:2350775 [ error ]
This error may be the result of a plug-in compatibility issue. [ info ]
[Disable plug-ins (restarts the app)](https://github.com/camunda/camunda-modeler/issues/new?template=BUG_REPORT.md#) [ info ]

Thanks for reporting! That's probably due to the fact our built-in linting support now uses the same bpmn-js extension name (linting).
/cc @philippfromme @christian-konrad, what is our general story on this? Do we encourage using the linter plugin together with the built-in linting?


rename some code attributes

Relates to #1377
In #1599 PR discussion, it was suggested we should probably rename a few code.* attributes before attempting to make them stable (which is the goal of #1599).

https://github.com/open-telemetry/semantic-conventions/pull/1599#discussion_r1854499495
https://github.com/open-telemetry/semantic-conventions/pull/1599#discussion_r1854501036

Changes

rename code.function to code.function.name: it allows to add in the future other function related attributes later like code.function.visibility or code.function.signature.
rename code.lineno to code.line.number this follows the general recommendation to avoid abbreviations while the lineno term is common, avoiding ambiguity is probably better here, also the code.line might be ambiguous as it could be interpreted as "the line of code".
rename code.column to code.column.number for consistency/symmetry with code.line.number.

Existing usages of those attributes would be impacted (from a GH search, which means some might have been missed due to indirections from the respective generated semconv files):

opentelemetry-php

code.lineno search
code.function search

opentelemetry-rust

code.lineno search

opentelemetry-java-instrumentation

code.lineno search
code.function search

opentelemetry-js-contrib

code.lineno search
code.function search

opentelemetry-python

code.lineno search
code.function search

opentelemetry-cpp-contrib

code.function search
code.lineno search

opentelemetry-php-contrib

code.lineno search
code.function search

I haven't found any usage of code.column which means renaming here should not have any expected impact.
Merge requirement checklist

[x] CONTRIBUTING.md guidelines followed.
[x] Change log entry added, according to the guidelines in When to add a changelog entry.

If your PR does not need a change log, start the PR title with [chore]

[x] schema-next.yaml updated with changes to existing conventions.

One problem is that renaming with a prefix is not allowed by policy, as a result I get the following error when trying to validate policy:
Violation: Attribute 'code.column' name is used as a namespace in the following attributes '["code.column.number"]'.
  - Category         : naming_collision
  - Type             : semconv_attribute
  - SemConv group    :
  - SemConv attribute: code.column
  - Provenance: /home/weaver/source

Violation: Attribute 'code.function' name is used as a namespace in the following attributes '["code.function.name"]'.
  - Category         : naming_collision
  - Type             : semconv_attribute
  - SemConv group    :
  - SemConv attribute: code.function
  - Provenance: /home/weaver/source

I don't know where does this restriction comes from, is it related to the generated per-language bindings ? From what I've seen so far they are mostly used as strings, so the limitations would be more on the processing/storage side.

We can add exceptions here: https://github.com/open-telemetry/semantic-conventions/blob/main/policies/attribute_name_collisions.rego#L83
This rule is in place to avoid conflicts if we ever "un-flatten" attributes.  E.g. if an attribute of x can have an "AnyValue" with field y and this means the same as x.y.
We should ensure we never send the attribute as a namespace and the new attribute in the same signal.
@lmolkova will update policy to avoid this warning if the namespace attribute becomes deprecated.

Thanks to #1642 this is now unblocked and all the checks are now passing, it should now be ready for review.

Probably we should also rename code.filepath to code.file.path, for the reasons above and also to match file.path

Today, I encountered another unclarity related to code.function.name and code.namepsace. How anonymous functions (lambdas) should be handled?
For instance, in Go we can have an anonymous function in go.opentelemetry.io/contrib/bridges/otelslog.TestSLogHandler function. The Go runtime will report its name e.g. as go.opentelemetry.io/contrib/bridges/otelslog.TestSLogHandler.func7. I decided to go with code.function.name=func7 and code.namespace=go.opentelemetry.io/contrib/bridges/otelslog.TestSLogHandler.

Probably we should also rename code.filepath to code.file.path, for the reasons above and also to match file.path

Done in 9303339, I have also updated this PR description.

As a reminder, the current state of this PR renames the following fields, there has been some approvals before the code.filepath was also renamed, so it's probably safer to be explicit here:

code.function renamed to code.function.name
code.lineno renamed to code.line.number
code.column renamed to code.column.number
code.filepath renamed to code.file.path

There is only one unresolved conversation: https://github.com/open-telemetry/semantic-conventions/pull/1624#discussion_r1868412697, which is mostly about introducing a breaking change, @trask @lmolkova what do you think are the best next steps ? Do you think it's worth doing a proper migration plan ?

@SylvainJuge let's follow @trask's proposal in https://github.com/open-telemetry/semantic-conventions/pull/1624#discussion_r1882702128 to add a warning - this would reduce any additional churn (if any).
Instrumentations that emit existing code attributes may still provide migration plan if necessary, without us requiring everyone to do it.


may I put vim in "Editors"? is a good idea?

sometimes I use vim, but I don't know if it is a good idea to add to the list

a lot of good coders use vim, but I left it out because it is usually difficult to learn (steep learning curve), its takes a lot of practice. people who have been codingfor a while  or DevOps people will usually pick it up.

i also haven't adding any of the usual command line apps, like: nano, cat, more, less, grep. These probably need they own section. We used to have a cheat sheet for it.

ok, thanks


At Dashboard Activity on Goal end time countdown , textview and background colour will change according to Timeline

At Dashboard Activity on Goal end time countdown , textview and background colour will change according to Timeline
days left <= 33% -> Red and Light red
days left <= 66% -> Yellow and Light Yellow
days left <= 100% -> Green and Light green

hi , I want to work on this issue under JWOC


Bug

Hello. I downloaded your bot, didn't change anything, just uploaded the bot token and AI Dungeon. The mistake is that, continuing the story, the clues appear not one by one, but all at once, overlapping each other.

Hmm that shouldn't happen.
I think I the bug occurs here, when the method obtains the localized tips and splits them using Environment.NewLine.
What OS are you using to self-host the bot?

Tried using both Windows 10 Pro and Ubuntu 18.04 LTS

Tried using both Windows 10 Pro and Ubuntu 18.04 LTS

Well that's weird because I'm using exactly those two systems to develop Fergun and I can't reproduce the bug, but it should be easy to fix by changing Environment.NewLine to a consistent newline character that works on any OS.

@VizEll12 The bug should be fixed with 4120668.


[bug] Client created with same client ID or device token but different tenant ID will break association with notifications

Client created with same client ID or device token, but under different tenant will update the tenant ID of the client but not delete any associated notifications with the old tenant ID. Notifications are always queried by their tenant ID vs clients are not.
Two solutions:

Remove tenant_id column from notifications and use the tenant_id column of the clients table (if this is even needed at all)
Update the tenant_id or delete notifications when the client's tenant_id changes

E.g. happening in real world: https://walletconnect.slack.com/archives/C04DB2EAHE3/p1716951454311359?thread_ts=1716951454.311359&cid=C04DB2EAHE3


docker redeploy kill Chef run

Opening this, trying to track it down.
How to reproduce, using 1.0.43:
docker_image 'mysql' do
  tag '5.6'
  action :pull
  notifies :redeploy, 'docker_container[mysql]'
  ignore_failure true # on first run the container does not exist yet
end

docker_container 'mysql' do
  repo 'mysql'
  tag '5.6'
  port '3306:3306'
  env 'MYSQL_ROOT_PASSWORD=dev'
  binds [ '/root/docker-conf/:/etc/mysql/conf.d' ]
  action [:create, :run]
end

Push, vagrant up and the Chef does not succeed:
==> zs1:   * docker_container[mysql] action create
==> zs1: [2015-10-01T20:35:17+00:00] INFO: Processing docker_container[mysql] action create (gz-mysql::default line 50)
==> zs1:     - creating mysql
==> zs1:   * docker_container[mysql] action run[2015-10-01T20:35:17+00:00] INFO: Processing docker_container[mysql] action run (gz-mysql::default line 50)
==> zs1:     - starting mysql
==> zs1: [2015-10-01T20:35:17+00:00] INFO: docker_image[mysql] sending redeploy action to docker_container[mysql] (delayed)
==> zs1:   * docker_container[mysql] action redeploy[2015-10-01T20:35:17+00:00] INFO: Processing docker_container[mysql] action redeploy (gz-mysql::default line 50)
==> zs1:
==> zs1:     - stopping mysql
==> zs1: [2015-10-01T20:35:19+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process terminated by signal 9 (KILL)
==> zs1: bash: line 3:  2310 Killed                  chef-client --config /tmp/vagrant-chef/client.rb --json-attributes /tmp/vagrant-chef/dna.json --log_level debug --force-formatter

Most likely on my side, poking.

Memory starved :sob:
Closing, non issue.


the code question

Traceback (most recent call last):
File "/home/std/Context-Cluster/cluster_visualize.py", line 176, in
main()
File "/home/std/Context-Cluster/cluster_visualize.py", line 124, in main
load_checkpoint(model, args.checkpoint, True)
File "/home/std/anaconda3/lib/python3.9/site-packages/timm/models/helpers.py", line 75, in load_checkpoint
incompatible_keys = model.load_state_dict(state_dict, strict=strict)
File "/home/std/anaconda3/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1604, in load_state_dict
raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for ContextCluster:
Unexpected key(s) in state_dict: "fea_pos".
RuntimeError: Error(s) in loading state_dict for ContextCluster:
Unexpected key(s) in state_dict: "fea_pos".
I'm having this problem when I run the cluster_visualize.py.
Thanks to the author for answering the questions！

You can try the coc_tiny_plain, checkpoint here: https://web.northeastern.edu/smilelab/xuma/ContextCluster/checkpoints/coc_tiny_plain/coc_tiny_plain.pth.tar in the README.md.
The reason of this error is that we slightly re-organized the code for faster training and inference. We are working on re-training all models and update the links.

Dear Author,
I tried this checkpoint with model=coc_tiny and imagenet dataset. However, the output is only Acc@1 54.540 (45.460) Acc@5 79.116 (20.884). May I ask whether I may have done something wrong?
Thanks a lot for any possible help in advance!

@TADanton I assume there is some bugs during your inference maybe?
BTW, we update our codes and checkpoints, with slightly improvements. Mainly two updates: 1) fix a bug mask.sum to sim.sum; 2) conv1x1 to Linear implementation.

@shixishi Thanks for your patience. The updated checkpoints are updated, with slightly improvements. Mainly two updates: 1) fix a bug mask.sum to sim.sum; 2) conv1x1 to Linear implementation.

Closed no further discussions. Feel free to reopen it if any further questions.


abnormal startup time.

Now starting a node requires waiting for several hours to initialize.
it is not starting indexing for the first time, it is already have a fully built index and then start the server with something like nohup ./ord --config ord.yaml --data-dir /ord/bin/data --index-cache-size<PHONE_NUMBER>8 --commit-interval 5000 --bitcoin-rpc-url <IP_ADDRESS>:8335 --index-sats --index-runes server >>console.log 2>&1 & and then it takes hours for the server to start?
12core  96G RAM  230G SSD
#!/usr/bin/env bash export RUST_LOG=debug nohup ./ord --config ord.yaml --data-dir /ord/bin/data --index-cache-size<PHONE_NUMBER>8 --commit-interval 5000 --bitcoin-rpc-url <IP_ADDRESS>:8335 --index-sats --index-runes server >>console.log 2>&1 &

Just a guess but you're probably not stopping ord cleanly and therefore it is having to repair the index at startup. That can take hours, as you've seen. If you skip all the nohup and output redirection you could probably see the message it's displaying during that long wait.

as a side note, the current default value for the --commit-interval flag is 5000, so no need to specify that unless you want a different value.

Just a guess but you're probably not stopping ord cleanly and therefore it is having to repair the index at startup. That can take hours, as you've seen. If you skip all the nohup and output redirection (or maybe just check whatever logs you're getting?) you could probably see the message it's displaying during that long wait.

Often times it is caused by OOM.

Yes, any abnormal stop or crash will generally cause the index file to require repair at next launch.

@heipacker please seek help for this issue in the Ordicord, if it persists.


Modified overlay modules to learn ZK URL from environment variables.

Removed any references to ZK URL from overlay module JSON config.
The ZK URL for master and agent overlay module can now be learned from
'MESOS_ZK' on the master and 'MESOS_MASTER' on the agent. So
specifying these URLs in the JSON should not be necessary.

Ready for review.
PR: https://github.com/dcos/mesos-overlay-modules/pull/6
Reviewed by @adam-mesos and @jieyu
@cmaloney ^^

:ship:

:rocket:


Dynamic job swapping

Adds dynamic job swapping.

I've punted on UI decisions in this PR (see discord discussion), and just added it as a generic config variable, feel free to push to this branch to change @miyehn (or just change it after this is merged).
Notes:

A new job field is added to the GameConfig class, and ShellVersion has been incremented.
Changing the configured job won't take effect until "apply and reset" is hit and the timeline is wiped clean, just as with any other configuration variable.
There's a minor stutter for icons to reload when a job-swapping configuration is applied--it's not super major since it happens pretty fast, but adding a loading spinner or similar would make it look nicer.
Any old fight plans in localStorage (or loaded via import) have a job inferred from actions in the timeline.
Text in IntroSection.tsx is updated with an explicit update call from the controller, we may need to double check if this causes any perf/load time regression since it doesn't match up well with the natural react lifecycle. We could also consider just using a single unified IntroSection for all jobs (maybe just swapping the help channel/resources links) since we'll all be on the same website.

I'm going to advocate for the middle option here dc message link. I think Turtle's arguments are valid, plus the fact that the information above the current job dropdown also depends on the job dropdown (aka not just numbers, but also what information is shown). <-- I'll push to this branch soon-ish and you can check
And this sounds pretty nice too and simple enough to do . <--I'll add afer this is merged

IntroSection.tsx: yeah I agree, eventually we can just make it static like before, because it's introducing the all-job rotation planner, not just the currently active job. We don't even need to swap the links and point of contact etc. we can just list them all... there's not going to be that many links I hope?

Anyway what do you think about this:
usually I think this is fine:

then if we change to another job but the change hasn't been applied yet, essentially the summary section is outdated so I strike it out:

I think 🐢's hierarchy argument makes sense. I'd prefer to just not display the irrelevant summary info rather than striking it out so the screen doesn't get too cluttered.
My only concern with this view is that you now need to scroll to see the "apply and reset" button, and the horizontal divider between summary text + other config fields might not make it clear that you need to hit "apply and reset" to change the job. Maybe just adding a text reminder on deteching changed job (like "hit apply and reset below to confirm job change") would work.

I'd prefer to just not display the irrelevant summary info rather than striking it out so the screen doesn't get too cluttered.

I'm fine with both tbh. If we hide the irrelevant summary the only down side is everything will suddenly get moved up and cause a small layout shift, but then yeah less distraction and nobody wonders what strikethrough means
Another thing we can do is to fix the "apply and reset" button to the bottom of that section, and only elements above are scrollable 🤔

and the horizontal divider between summary text + other config fields might not make it clear that you need to hit "apply and reset" to change the job

Another random idea:

If we hide the irrelevant summary the only down side is everything will suddenly get moved up and cause a small layout shift

Fair enough. I just realized that the info doesn't update live with config anyway (the cast time table only displays cast times from the confirmed sps). My thought was that if other jobs had additional info they wanted to display in the summary area, we could swap to that as the job dropdown was changed, but that would be inconsistent with other config behavior.

Another thing we can do is to fix the "apply and reset" button to the bottom of that section, and only elements above are scrollable

I think this would make sense, I just had the second realization that expanding the override tab will make the "apply and reset button" go to the bottom as well.

How about...

keep the strikethrough (actually I'll modify the logic a bit more)
change the horizontal bar to the vertical line on the left like in the above screenshot
fix "apply and reset" at bottom to be always visible

^I'll do these and add the job colors, and check the resource overrides section.... tomorrow, my brain is getting foggy now... 💤

fixing the button position wasn't as trivial as I thought so didn't do it just now.. anyway I think I'll leave the config tab and go mess with colors in another branch

sgtm, feel free to hit the merge button yourself if you're happy with the frontend for now. Thanks as always for reviewing + editing.
Are we planning on keeping this out of deployment until we're running on the new domain?

We can deploy it now and start testing things out. But probably shouldn't announce publicly yet, not until we have the localStorage migration part figured out


Fix projects query

The backend kept eating memory and restarting in production, after monitoring DB logs I found the donations join is very expensive so we have to delete that

@mohammadranjbarz @CarlosQ96 What query is removed?
The donations object in projectBySlug?

@mohammadranjbarz @CarlosQ96 What query is removed?
The donations object in projectBySlug?

No in projects
I think it's not needed in frontend because staging is up and running

In the all projects query (with all the filters/searching etc) we removed the donations because it was causing a memory leak.


Move subscription Go packages to preview directory

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-libraries-for-java
Nothing to generate for azure-libraries-for-java

Automation for azure-sdk-for-node
Nothing to generate for azure-sdk-for-node

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go
Nothing to generate for azure-sdk-for-go


After tensorflow-lite-0.1.7 update Image classification using inception-v3 model stops working

Image classification using inceptionv3_slim_2016.tflite is not working after the recent update of 0.1.7 version. Cannot allocate memory for the interpreter.
It gives the below exception :
java.lang.RuntimeException: Unable to start activity ComponentInfo{android.example.com.tflitecamerademo/com.example.android.tflitecamerademo.CameraActivity}: java.lang.NullPointerException: Internal error: Cannot allocate memory for the interpreter

Have I written custom code : NA
OS Platform and Distribution : Android
TensorFlow installed from : 'org.tensorflow:tensorflow-lite:+'
TensorFlow version : tensorflow-lite-0.1.7
Bazel version : NA
CUDA/cuDNN version : NA
GPU model and memory : NA
Exact command to reproduce : NA(using TfLite InceptionV3 in Android 8.1)

I also met the same problem, and the float model is so slow.

Same here

Same here

Thanks princekumar15@ for reporting this issue! I'll start looking into what caused this breakage.

@princekumar15 : I tried but was unable to reproduce your issue. Everyone, is there something I did differently?
I suspect you were following the tflite Android demo instructions.

I followed the instructions: "Or, download the floating point Inception-v3 model and unzip and copy inceptionv3_non_slim_2015.tflite to the assets directory. Change the chosen classifier in Camera2BasicFragment.java from: classifier = new ImageClassifierQuantizedMobileNet(getActivity()); to: classifier = new ImageClassifierFloatInception(getActivity());"

I ran into the setNumThreads issue and commented the lines out as Bob suggested.
In the build.gradle file, I tried compile 'org.tensorflow:tensorflow-lite:0.1.7' and compile 'org.tensorflow:+'. I didn't see the error when running the demo in either case.

I also just tried building from HEAD with bazel without using Android Studio and didn't see the error.

This was on a Pixel 2 running on Android 8.1.0.

The way I get this error is when following the tutorial TensorFlow for poets 2.
I first tried the TensorFlow for poets (https://codelabs.developers.google.com/codelabs/tensorflow-for-poets/index.html?index=..%2F..%2Findex#0) to retrain a model with my data (this part works just fine even when using the retrained .pb graph on android but the detection time is still slow and the battery usage high).
I wanted to try and implement TFLite to help fix these problems, so I followed the tutorial TensorFlow for poets 2 (https://codelabs.developers.google.com/codelabs/tensorflow-for-poets-2-tflite/#0) to convert my .pb model into a .tflite model. The output model is the one that causes the java.lang.NullPointerException: Internal error: Cannot allocate memory for the interpreter when imported in Android, but the inceptionv3_slim_2016.tflite works fine, it just does not work with my retrained model.
I'm running this on Samsung Galaxy S6 running Android 7.0 by the way, I hope this gives you more information on how to reproduce the problem.

@jbuisson1: for the pre-made Android app, are you using the one linked to in Tensorflow for Poets 2 (from the codebase cloned in Tensorflow for Poets 1, as opposed to this one)? I followed both Tensorflow for Poets 1 and 2, and it's worked for me on a Nexus 6 emulator running Android 7.0 and my Pixel. I tried hacking the model/labels into the tensorflow/tensorflow repo also and it worked fine.
Let's try to see what differences there might be.

Your data is special somehow (e.g. different image dimensions). Did you have the same problem when using the tutorial retraining data (daisy, sunflower, ... categories)?
There have been tflite updates to tensorflow-lite:0.1.7 since you last tried. Try making sure that Android Studio/Gradle has picked up on the changes.
If there aren't other differences that you can think of, I may need to find a Samsung Galaxy S6 to reproduce.

Dismissed Differences

I'm running from HEAD. The codebase hasn't really been updated recently.

Closing this issue.

Reasoning:
I confirmed that the tensorflow-lite:0.1.7 AAR that Gradle uses was re-released once. This is not something we should be doing in the future, but would explain why I couldn't reproduce the issue (I'm using the newer version of the tensorflow-lite:0.1.7 AAR and some people picked up the older version around the release time).


Add/update global data file for personal website and template

Hey, Zach. I updated a few things within this project and needed to rename + modify the global data file for 11tygallery.netlify.app. I also added my personal website to the site list. Thanks!

Thank you!


deno.land

Can you publish it on deno.land again?

Sorry for taking so long, but I was a bit busy and this issue unfortunately is a bit out of my control - as I don't have the required permissions to this repository...
I wrote about the lack of a webhook within the organisation - taggin the owners (@AnandChowdhary and @AlexImb), but received no response.
So I guess I'm asking them once again here to either configure the webhook or give me administrator permission to this repo (which would allow me to maintain it here).
If that doesn't happen I'll try asking if it'd be possible to move the repo target from this one to a fork on my account.


Improve upsert compaction threshold validations

Currently, there is no method to schedule an UpsertCompaction task for a segment that has only one invalid record. We have prevented the invalidRecordsThresholdCount from being set to 0 in the tableConfig, although it defaults to 0 in the generator flow. Additionally, during the taskGenerator process, we perform a strict increment check of the invalid threshold count.
https://github.com/apache/pinot/blob/99f6934166633308547d37cacc634e03c723ab17/pinot-plugins/pinot-minion-tasks/pinot-minion-builtin-tasks/src/main/java/org/apache/pinot/plugin/minion/tasks/upsertcompaction/UpsertCompactionTaskGenerator.java#L242-L244
Therefore, we either need to set a very low decimal value for invalidRecordsThresholdPercent, which may require precision to several decimal places based on the invalid-to-total-docs ratio of a segment, or we can allow the value to be set to 0, enabling users to perform compaction for segments with just one invalid record.

Good catch for the issue. However, I'd change the config invalidRecordsThresholdCount default to 1 and continue to check that it has to be >=1, as it seems more intuitive.
But the the sanity check in generator should do >= instead, i.e. allowing segments with only 1 invalid doc to be compacted.
invalidRecordPercent >= invalidRecordsThresholdPercent
     && totalInvalidDocs >= invalidRecordsThresholdCount

The suggestion sounds good to me! Updated the patch.


test: Script updates for flaky fixes

Description

This PR includes cypress scripts fixes for stable CI runs including:

Toasts msg validation updates
Promises spec flaky fix
UUID spec flaky fix
Autocomplete JS spec flaky fix
Query abort failure fix
Datatree Mutation spec flaky fix
GetElement() helper added
toWriteAfterToastsDisappear flag added

Type of change

Script fixes (non-breaking change which fixes failing cases)

How Has This Been Tested?

CI runs

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes

/ok-to-test sha=e8cb303

/ok-to-test sha=0f646c8

/ok-to-test sha=5ec8488

/ok-to-test sha=589cbd9

/ok-to-test sha=252861d

/ok-to-test sha=4a1e69e

/ok-to-test sha=258473c

/ok-to-test sha=46a98b3

/ok-to-test sha=46a98b3

/ok-to-test sha=46cd609

/ok-to-test sha=fb4d461

/ok-to-test sha=6d79dea

/ok-to-test sha=c939705

/ok-to-test sha=d7020e3

/ok-to-test sha=53b13f7

/ok-to-test sha=c1cfb5c

/ok-to-test sha=a7c7fc4

/ok-to-test sha=5c74fe3

/ok-to-test sha=3d464e2

/ok-to-test sha=27e5ff3

/ok-to-test sha=eefad53

/ok-to-test sha=224ce66

/ok-to-test sha=aa7fc3f

/ok-to-test sha=e921a07

/ok-to-test sha=6e62e88


Performance Question

Hello, and thank you for making this work open source. I am trying to replicate the results from the paper, but instead using a HalfCheetah env where I manipulate the joint stiffness every 20M timesteps like the below. I see a nice drop of reward (~1K) for the first drop (240 - 48 - 9.6 - 1.92 where the first drop is the largest and I see the best drop in reward). So what I am doing is seeing how a PPO algorithm with a normal critic (simply outputs a scalar value and computes the MSE) vs a CBP critic (still outputs a value and computes MSE, but with the neurons able to be reinitialized with the CBP linear). I am seeing that both perform very similar while the CBP implementation performs slightly worse (~2% less average reward) over 25 models of each ran with [1024, 1024] layer sizes.
My question is: am I implementing the CBP layers as intended? Is there a better way to test these networks for relearning after a change to the agent? Do you have any recommendations on how to proceed with testing these?
Thank you!
Env. step:
    def step(self, action):
        self._current_step += 1
        self._total_step += 1
        x_position_before = self.data.qpos[0]
        self.do_simulation(action, self.frame_skip)
        x_position_after = self.data.qpos[0]
        x_velocity = (x_position_after - x_position_before) / self.dt

        ctrl_cost = self.control_cost(action)
        forward_reward = self._forward_reward_weight * x_velocity

        observation = self._get_obs()
        reward = forward_reward - ctrl_cost
        terminated = False
        info = {
            "x_position": x_position_after,
            "x_velocity": x_velocity,
            "reward_run": forward_reward,
            "reward_ctrl": -ctrl_cost,
        }

        if self.render_mode == "human":
            self.render()

        terminated = self._current_step >= self._max_episode_time

        if self._total_step % 750_000 == 0:
            self.model.jnt_stiffness[3] /= 5
        return observation, reward, terminated, False, info

CBP model:
class CBPModel(TorchModelV2, nn.Module):
    def __init__(self, obs_space, action_space, num_outputs, model_config, name):
        TorchModelV2.__init__(self, obs_space, action_space, num_outputs, model_config, name)
        nn.Module.__init__(self)

        self.actor_fcnet = TorchFC(obs_space, action_space, action_space.shape[0]*2, model_config, name +
                                   "_actor")
        hidden_layer_size = model_config['fcnet_hiddens'][0]

        self.act = nn.LeakyReLU()
        self.fc1 = nn.Linear(obs_space.shape[0], hidden_layer_size)
        self.fc2 = nn.Linear(hidden_layer_size, hidden_layer_size)
        self.fc3 = nn.Linear(hidden_layer_size, hidden_layer_size)
        self.fc4 = nn.Linear(hidden_layer_size, 1)

        self.cbp1 = CBPLinear(self.fc1, self.fc2, replacement_rate=1e-4, maturity_threshold=100, init='kaiming', act_type='leaky_relu')
        self.cbp2 = CBPLinear(self.fc2, self.fc3, replacement_rate=1e-4, maturity_threshold=100, init='kaiming', act_type='leaky_relu')
        self.cbp3 = CBPLinear(self.fc3, self.fc4, replacement_rate=1e-4, maturity_threshold=100, init='kaiming', act_type='leaky_relu')

    @override(TorchModelV2)
    def forward(self, input_dict, state, seq_lens):
        logits, _ = self.actor_fcnet(input_dict, state, seq_lens)
        means, log_stds = torch.chunk(logits, 2, -1)
        means_clamped = torch.clamp(means, -1, 1)
        log_stds_clamped = torch.clamp(log_stds, -10, 0)
        logits = torch.cat((means_clamped, log_stds_clamped), dim = -1)

        '''-----CBP implementation for critic network-----'''
        obs = input_dict['obs']
        x = self.act(self.fc1(obs))
        x = self.cbp1(x)
        x = self.act(self.fc2(x))
        x = self.cbp2(x)
        x = self.act(self.fc3(x))
        x = self.cbp3(x)
        self.value = self.fc4(x)
        return logits, state

Thank you @shibhansh, I will go ahead and gives this a try. I'll close it for now (won't be able to test this for a few weeks) and reopen in the event that I am still having troubles. From my experience, directly impacting the actor and critic normally leads to destabilization as now you are sending gradient updates via the advantage function and the surrogate loss, but for CBP this seems to be different since it is neuron reinitialization.
Thanks again!


how do i search post with underscore without writing underscore

Hey developers,
how do i search string with underscore without writing underscore
example : someone searched xbox and there is post named x-box
so now the problem is post doesn't appearing please help me to fix this

Easiest solution would be to ensure that all posts relating to "xbox" have two tags: x-box and xbox.
Apart from this, you'll need to do some string comparison to work out if it's similar enough to match.

Closing this out since it's a generalized question and doesn't pertain to the project.


Add framework to Vercel supported frameworks

To do this we pretty much only need to open a PR to vercel/vercel. I already got started, but just want to make a successful deployment first to maybe help w/ the docs.

Hey @ribeirojose, hope you going well!
Sorry for the late response.We already had some thoughts about how good

Hey @ribeirojose, hope you going well and sorry for the late response!
We already had some thoughts about how good would be official Vercel support, and is related to your #92
I've seen you got right the deploy part. How your work on it been going?
Vercel itself has some tutorials on this topic we would use like this one.


[FLINK-13896]make scala-maven-plugin compile target jvm version consistent with java version

What is the purpose of the change
Make scala-maven-plugin compile target jvm version consistent with java version
Brief change log

specify target JVM language

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Looks good to me, merging this...


Improve FCM QucikStart

Improve the quickstart. Specifically:

Add explanations and links on FCM sending and receiving.
Add isSupported() use case in sw.
Added inline comments to annotate the behavior for foreground and background hooks.
EsLint fixed indentation and quotes uniformity.

Hey @zwu52, just noticed this as I was going through some older PRs. Should we keep working on this PR, or close it out?


tests directory

Hi.
Please, remove the tests directory of the distribution, it conflicts with other packages.
Thank you!

the exact reverse of a pull request a few years ago
https://github.com/WoLpH/portalocker/pull/8
I guess the better solution would be to move the tests to a subdirectory of portalocker but I'm not a fan of polluting the code directory with tests. Would renaming the directory to portalocker_tests be sufficient for you?

sure, that helps.
thanks for your time.


NUS Processing Ignores foldflg

Describe the bug
When processing homonuclear spectra, NUS reconstruction ignores the value of foldflg and forces data symmetrization.  This produces false crosspeaks anywhere there is significant t1 noise ridges (e.g. methyls and other tall peaks).  I have all my homonuclear protocols customized to set foldflg='n' but NUS processing ignore this.
To Reproduce
Steps to reproduce the behavior:

Setup a COSY and set foldflg='n' before running it (with NUS enabled)
Process the data and the result is symmetrized

Expected behavior
The NUS processing should obey foldflg so that those of us who detest symmetrization can ensure that symmetrization is not applied.
Version of OpenVnmrJ you are using.
OpenVnmrJ 2.1 and 3.1 (both downloaded from GitHub)
Both the DDR and OSX versions
Messages and Logs
No errors are generated, just undesired behavior.
Environment (please complete the following information):
RHEL 6.10, 7.9 and OSX 10.15.7
Additional context
I've been testing out NUS on TopSpin and homonuclear spectra are not symmetrized in NUS reconstruction (e.g., you can see the t1 noise ridges and the obnoxious false crosspeaks aren't generated)

Can you try the NUSproc macro in the attached zip file.  Copy it to ~/vnmrsys/maclib or /vnmr/maclib
sb.zip

I have now tested this (in ~/vnmrsys/maclib) on both my Mac and on one of the data processing computers that is failing with IST (so OSC 10.15.7 and RHEL 7.9) and I get the same pread error (with a brief window that says something about an error with vj2pipe.tcl)

-Scott

Dr. Scott Burt
Teaching Professor
NMR Facility Manager
Department of Chemistry and Biochemistry
Brigham Young University
C414 BNSN / C008A BNSN
Provo, Utah  84602-5700
Phone:<PHONE_NUMBER>
Fax:<PHONE_NUMBER>
chembio.byu.edu/nmr-facility https://chembio.byu.edu/nmr-facility
email: @.***

On Dec 2, 2021, at 3:23 PM, Dan Iverson @.***> wrote:
Can you try the NUSproc macro in the attached zip file. Copy it to ~/vnmrsys/maclib or /vnmr/maclib
sb.zip https://github.com/OpenVnmrJ/OpenVnmrJ/files/7645444/sb.zip
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/OpenVnmrJ/OpenVnmrJ/issues/658#issuecomment-985049917, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGI4R6JK6O3NCC4P3TMVRT3UO7WUXANCNFSM5JHSXF5A.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

This macro won't fix the IST issue but should take care of the foldflg issue.

Oh, got it.  I'll test that.

-Scott

On Dec 2, 2021, at 4:52 PM, Dan Iverson @.***> wrote:
This macro won't fix the IST issue but should take care of the foldflg issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/OpenVnmrJ/OpenVnmrJ/issues/658#issuecomment-985095136, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGI4R6I3HN6OLLTN64WTTS3UPABE3ANCNFSM5JHSXF5A.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Yes, the NUSproc that you sent fixes the foldflg issue.  The COSY data look much better now.

-Scott

Dr. Scott Burt
Teaching Professor
NMR Facility Manager
Department of Chemistry and Biochemistry
Brigham Young University
C414 BNSN / C008A BNSN
Provo, Utah  84602-5700
Phone:<PHONE_NUMBER>
Fax:<PHONE_NUMBER>
chembio.byu.edu/nmr-facility https://chembio.byu.edu/nmr-facility
email: @.***

On Dec 2, 2021, at 3:23 PM, Dan Iverson @.***> wrote:
Can you try the NUSproc macro in the attached zip file. Copy it to ~/vnmrsys/maclib or /vnmr/maclib
sb.zip https://github.com/OpenVnmrJ/OpenVnmrJ/files/7645444/sb.zip
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/OpenVnmrJ/OpenVnmrJ/issues/658#issuecomment-985049917, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGI4R6JK6O3NCC4P3TMVRT3UO7WUXANCNFSM5JHSXF5A.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


feat(otelgorm): added an option to not report DB stats metrics

This PR adds an option to otelgorm to not report DB stats metrics. Some users like myself may not be currently using OpenTelemetry for metrics and wish to be able to disable this functionality. This functionality might also overlap or conflict with the Prometheus plugin for gorm: https://gorm.io/docs/prometheus.html

Thanks

Thanks for reviewing!


Picker - undefined is not an object (evaluating 'this.props.children[position].props)

I am encountering a weird behaviour when using Picker.
I use a Picker as follows :
<Picker
  mode="dropdown"
  style={styles.pickerField}
  selectedValue={this.state.dayAndTime}
  onValueChange={(text) => this.setState({ dayAndTime: text })}
>
  <Picker.Item label="Le 5/07 à 15H" value="0" key="0" />
</Picker>

When the screen displaying this picker is loaded, I got an error screen saying (cf. screenshot below) : undefined is not an object (evaluating 'this.props.children[position].props)
From what I gathered, my problem come from line 106 of Libraries/Components/Picker/PickerAndroid.android.js, it seems that onValueChange creates it, so I removed it, and I don't have the error anymore.
I use react-native 0.31.0, I use an android api 23 virtual device with genymotion.
Is there something I am missing ?

Error was triggered because there was only one Picker.Item, after I added one, everything went smoothly.

@vhoen I get the same issue and I have several items and it's triggered when the value changed.
I'm using react 0.33
renderEventPicker() {
    let { project } = this.props;
    let { report } = this.state;
    if(project.eventTypes.length > 0) {
      return (
        <Picker
          selectedValue={this.state.eventTypeId}
          onValueChange={(data) => {
            report.eventTypeId = data;
            report.eventCategoryId = null;
            this.setState({report});
          }}
        >
          <Picker.Item key={0} label={'Tipo de evento'} value={''} />
          {project.eventTypes.map((eventType) => <Picker.Item key={eventType.id} label={eventType.name} value={eventType.id} />)}
        </Picker>
      );
    }
    return null;
  }

Is there something I'm missing?

I found it... The error was that selectedValue={this.state.eventTypeId} was null for ever...

Having the same issue as @alexsotocx, However if you add to static items, you can select them with no error, but any items dynamically added in a map throw the error reported

@willoughby please refers to #9927

@willoughby Same. Got a response and rendering it after setState.  When value is changes i am thrown this error.

so, i found a resolution that we can create an array contains blank Item before use it.
render() {
    const pickerItems = this.props.depts.map(dept => {
      return (
        <Picker.Item key={'d' + dept.id} label={dept.name} value={dept.id} />
      )
    })

    pickerItems.unshift(<Picker.Item key="d0" label="选择部门" value="" />)

    return (
        <Picker
             selectedValue={this.state.deptId}
             onValueChange={value => this.setState({ deptId: value })}>
             {pickerItems}
        </Picker>
    )
}

render() {
    const pickerItems = this.props.depts.map(dept => {
      return (
        <Picker.Item key={'d' + dept.id} label={dept.name} value={dept.id} />
      )
    })

    pickerItems.unshift(<Picker.Item key="d0" label="选择部门" value="" />)

    return (
        <Picker
             selectedValue={this.state.deptId}
             onValueChange={value => this.setState({ deptId: value })}>
             {pickerItems}
        </Picker>
    )
}

I had the same issue and I fixed setting an empty array as the default value of my dataSource prop:
const defaultProps = {
	label: '',
	dataSource: []
};

const PickerWithLabel = (props) => {
	return (
		<View style={styles.container}>
			<Label style={styles.label}>{props.label}</Label>
			<Picker style={styles.picker} mode="dropdown" { ...props }>
				<Picker.Item label="--- Select ---" value="" />
				{
					props.dataSource.map(({ label, value }) => (
						<Picker.Item key={value} label={label} value={value} />
					))
				}
			</Picker>
		</View>
	)
}

PickerWithLabel.defaultProps = defaultProps;

I resolved my issue using the suggested workaround by @luoyjx!
`_renderModalStatePicker = () => {
    const pickerItems = Object.keys(this.state.statelist).map((key) => {
        return (<Item label={this.state.statelist[key]} value={key} key={key}/>) //if you have a bunch of keys value pair
    })
    pickerItems.unshift(<Item key="as" label="All States" value="as" />)

    return(
        <View>
            <ListItem>
                <Text>States</Text>
            </ListItem>

            <Picker
                mode="dropdown"
                placeholder="Choose a state"
                selectedValue={this.state.selectedState}
                onValueChange={this.handleSelectState.bind(this)}>
                {pickerItems}
            </Picker>
        </View>
    );
}`


amazon_side_asn recreating VPC resources?

Trying to upgrade to Terraform v0.12, which means that I'm running apply on some projects that haven't needed much attention recently, and with the VPC project, I'm seeing that Terraform wants to recreate a bunch of VPC resources. On a quick scan, it looks like it might come down to this:
      amazon_side_asn:                "7224" => "64512" (forces new resource)

And all the resources that this forces a re-creation on.
That seems to be related to this:
https://github.com/terraform-providers/terraform-provider-aws/issues/5263
I don't see any issues in the VPC modules addressing this. What can I do to make my vpc module config happy without recreating things that basically haven't changed?  Am I missing any issues/documentation about this?

Ok, I took another look at this, and I can just add this to the VPC block:
amazon_side_asn = 7224

That updates the VPC block to use the ASN that Amazon used when the VPC was created, which stops the recreation of the gateway, which fixes everything else that was getting re-created. So if anyone else hits this error

closing this, if the issue persists in the latest version of the module please open a new issue


polymer-2-element template fails tests out of the box

Description
element.is returns undefined under test in polymer-2-element template

Steps to Reproduce

$ polymer init
select polymer-2-element
$ polymer test -l chrome

Expected Results
Tests passed

Actual Results
✖ test/polymer-test_test.html » polymer-test » instantiating the element works
expected undefined to equal 'polymer-test'

Browsers Affected

[x] Chrome

Versions

Polymer: v2.0.0-rc.3
webcomponents: v1.0.0-rc.7

Looks like the generated test is testing elementInstance.is, but the is getter is on the constructor, so it should be elementInstance.prototype.constructor.is

This issue was moved to Polymer/polymer-cli#643


SafeConfigParser renamed to ConfigParser

According to the doc page here:

Note The ConfigParser module has been renamed to configparser in Python 3. The 2to3 tool will automatically adapt imports when converting your sources to Python 3.

I checked this after installing versioneer into one of my projects:
Now running 'versioneer.py setup' to install the generated files..
versioneer.py:342: DeprecationWarning: The SafeConfigParser class has been renamed to ConfigParser in Python 3.2. This alias will be removed in future versions. Use ConfigParser directly instead.
  parser = configparser.SafeConfigParser()
versioneer.py:344: DeprecationWarning: This method will be removed in future versions.  Use 'parser.read_file()' instead.
  parser.readfp(f)

FYI, this still seems to work in Python 3.8.  Still safe for now.  Really should fix this though.  For a project which aims to be compatible with Python 2.7 perhaps it needs some compat.py or utilize six

Merge request #207 should fix this

Fixed in master.


Added a short text alignment section to the label doc

Big :+1:, users are often confused by this.


Update package.json

This delay is needed so that the services can spin back up (nodemon) before gateway attempts to.  Otherwise, gateway won't be able to find one of the services (every time)

@jonmccutchan90: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/


Please make a cri-dockerd release and package

Now that Kubernetes 1.23 is in alpha, it would be nice with a 0.1.0 release and some binaries... (like static and deb/rpm)
https://www.mirantis.com/blog/the-future-of-dockershim-is-cri-dockerd/

There is a Makefile with a few targets. make deb or make rpm will probably have you covered, and you can install the packages as normal. If you’re using a different distribution, make static will give you raw binaries you can invoke.

I expect to be able to download these, from the GibHub release "assets"

Will be done MOnday.

Will these be published to the docker repos for yum and apt as well?

They are not likely to be, unless someone from upstream Docker picks them up

I thought mirantis was upstream docker now. Thanks for the heads up!

We work with them, but the upstream community is a community ;)

This issue will be relevant to https://github.com/kubernetes/kubernetes/issues/104878
(if cri-dockerd gets a public release, then people who want to use Docker as a container runtime for Kubernetes have a route to continue doing that)

Releases are published. Anything else needed here?

Thanks!


Removing unused constants and typo fix

I was looking through the constants files and removed unused ranks in misc, the survey we finished a decent bit ago, as well as fixing a single typo in a comment I read.

About the ranks, ok on build team cause I don't think it will come back, but for mayor and minister we can't be sure it won't come back so I'd leave it there
For the survey, it's a new one we made a couple weeks ago I think, maybe it's been a bit more but it's not that long ago
For the comment woooops my bad

About the ranks, ok on build team cause I don't think it will come back, but for mayor and minister we can't be sure it won't come back so I'd leave it there
For the survey, it's a new one we made a couple weeks ago I think, maybe it's been a bit more but it's not that long ago
For the comment woooops my bad

I was under the impression we had already finished the survey as we had discussed the results a while ago and the results aren't subject to change much further.

Ok yeah we got 1.1k answers and it's probably best to close the survey before nether update drops


Fix a10 driver to automatically fix incorrect delay/timeout values

Timeout cannot be greater than Delay for health monitors.  Delay is the wait time between health monitor checks and Timeout is the amount of time we wait until we've decided something is "unhealthy".  If timeout is larger than delay, a second health check will be sent before the first health check has a chance to timeout.

@dougwig Awaiting merge of a10-neutron-lbaas so I can kick the CI jobs.


Remove announcement about gitRepo

Description

There are open discussions regarding whether gitRepo volume plugin should be removed or not.  It will be discussed in the next SIG Architecture meeting (which will happen after the 1.32 release). We should remove this announcement from the 1.32 release blog until a decision is made.
https://github.com/kubernetes/kubernetes/issues/125983#issuecomment-2528923329
https://github.com/kubernetes/website/pull/48666#discussion_r1876466815
Issue

Closes: #

cc @thockin @liggitt @saad-ali @msau42 @jsafrane @gnufied

cc @mbianchidev

/lgtm

Already done in this PR that needs to be merged to publish the blog anyway, this can be closed.
I misunderstood this comment, sorry about that.

/hold

@mbianchidev no problem.  Since this is already done in https://github.com/kubernetes/website/pull/48962, let me close this PR.  Thanks.


Use the fetch available in the environment instead of cross-fetch

For cloudflare workers and deno where there is fetch available in the environment already, currently we need initialise the client like this
const supabase = createClient(
    "https://yyy.supabase.co",  "xxx", {
      fetch: fetch.bind(globalThis),
    }
  );

Instead we should use the following algorithm to get fetch

Use the custom fetch option when provided
Use the global fetch if available
else use cross-fetch

With Node implementing the fetch standard soon, fetch is a global we can reasonably assume the existence of in most envionments and only load cross-fetch as a polyfill. cross-fetch also assumes the presence of XMLHttpRequest which leads to a lot of errors.
Client libraries to update

[x] storage-js
[x] postgrest-js
[x] realtime-js (doesn't use fetch)
[x] gotrue-js

Thanks a lot @soedirgo! 💟  Can you make a final release to supabase-js with these?

Is there probably a regressing in the 2.0 branch ... I have trouble getting the server side code to work.
require is not defined
ReferenceError: require is not defined
    at [...]/node_modules/.pnpm/cross-fetch@3.1.5/node_modules/cross-fetch/dist/node-ponyfill.js:1:32
    at instantiateModule (file:///[...]/node_modules/.pnpm/vite@3.1.8/node_modules/vite/dist/node/chunks/dep-4da11a5e.js:53445:15)

can you create a new issue with a reproduction and which server side environment you are using @Crenshinibon ?

@inian I'm trying.

https://github.com/supabase/supabase-js/issues/613


Cannot register a new account on the demo

I tried running the getting started of Saleor. Upon running, I can't seem to find in the docs  for registering a user. I tried registering and it's saying it was sent to my email but I did not find any

@kyeljmd Right now Saleor supports the SendGrid service which we use on Heroku. You can deploy the app once again to have everything configured by default.

@bogdal Is it possible to not use sendgrid at all for registration?

You can set your own email service using EMAIL_URL environment variable or (assuming that you don't have SendGrid addon) check the logs of your application where you should find the contents of all your emails.

Documentation was added for EMAIL_URL https://saleor.readthedocs.io/en/latest/gettingstarted/configuration.html


cancel open order says processing when transaction hasn't been sent.

cancel-order needs to be smart enough to set pending tx only when tx is actually sent.
We had the same issue in claim winning proceeds and claim fees and stake modals
example below

What was the fix for this?

there has been instances where the user thinks the tx is being processed but really the metat mask popup is hidden behind the web browser.
So the tx isnt processing. Its only processing when it is sent.
In two modals we changes to only say processing when the tx has actually been sent. Not just saying processing when they hit the button. Either approach doesnt really cover all cases. Probably need a “waiting” or “signing”  step.

approved

this is fixed with addition of transaction lifecycle hooks.


Fix support for relative paths in clock sync URIs

i checked the code and found that shaka got the playheadtime by calculate "Date.Now - availabilityStartTime - maxSegmentDuration" ,
when my local time is faster or the time of server side is slower, shaka will never found the playback segment.
please help to check,
Thanks
Logan

adjust machine time 5 minutes ahead.
play http://wowzaec2demo.streamlock.net/live/bigbuckbunny/manifest_mpm4sav_mvtime.mpd

Your manifest does not contain a UTCTiming element, which is how manifests specify time sync between client and server.
In v2.0.0-beta2 we introduced a configuration option for situations where you cannot add UTCTiming to your manifest.  You can instead configure a URI for the player to use as if it came from UTCTiming.
Docs: http://shaka-player-demo.appspot.com/docs/api/shakaExtern.html#DashManifestConfiguration

A default clock sync URI to be used with live streams which do not contain any clock sync information. The "Date" header from this URI will be used to determine the current time.

Example:
player.configure({
  manifest: {
    dash: {
      clockSyncUri: 'http://foo.bar/time'
    }
  }
});

The demo app at http://shaka-player-demo.appspot.com/demo/ has a clock sync URI configured, so your manifest should work correctly on that demo regardless of your local clock.  (Please let us know if it does not.)
Does this answer your question?

Hi Joe,
very very thanks for your reply,
yes, for player side, it did help me.
but we also developed Dash Stream Server, I found that the live edge of my server is slow 30 seconds(maybe the system delay from encoder to server) than the time of now,
i know this is not up to DASH standard, but i have no idea to solve this,
Is there any solutions can be done on player side?
Thanks
Logan

Can you clarify what you are asking for?  It sounds like you have some bug in your server, but I am not at all sure I understand.

what i mean is that
my Dash Stream Server have some bugs that it produced the live streams always later 30 seconds than now.
for example,
the NTP time is 11:10:31 2016-5-14,
and my machine time is also 11:10:31 2016-5-14,
test.mpd is the dash manifest produced by my stream server,
in the "test.mpd",
availabilityStartTime="2016-05-14T11:00:00Z"
the last  item in  in mpd is  (time scale is 1000)
the time of last "S" convert to Date is the value of "2016-05-14T11:10:00Z",
so you see, the latest Segment can be provided by Stream Server is always delay 30 seconds than now.
right now, shaka request the live edge, what it request is the segment which t = 631000 , ( 631000  is the time now 11:10:31 minus the available start time 11:00:00 and unit in millisecond )
the last  in  is  ,
so shaka will never get the segment what it request.
and that is my issue, i can not modify anything for the server side.
is there any ways that shaka can be compatible with these delay streams.
and as i know, shaka v1.3.0 can play these delay live streams.

The fact that v1.3.0 miscalculated the live edge in a way that compensates for a bug in the server is not a good thing.  :-)
You should provide <UTCTiming> in your manifest and synchronize the client to the UTC time the server thinks it is (the delayed time).  Something like this:
<UTCTiming schemeIdUri="urn:mpeg:dash:utc:http-iso:2014" value="/path/to/currentTime">

Where /path/to/currentTime is some endpoint in your server that delivers the current time in a form comprehensible to JavaScript's Date.parse(), for example 2016-05-14T15:15:00+0200.

Thanks very much,
but it seems that value="/path/to/currentTime" doesn't work as was expected。
  var schemesAndValues = elems.map(function(elem) {     return {       scheme: elem.getAttribute('schemeIdUri'),       value: elem.getAttribute('value')     };
this.requestForTiming_(value, 'HEAD');
because "value" attribute in <utcTiming> doesn't concat with the baseUrl,
what it requests is not target to stream server.

Okay, so it seems we need to fix support for relative paths.

Hi @asdftu, please try again with the latest from master.

OK, Thanks very much!
i will test it.


[FR] Include newline in selection when clicked beyond the last character of line

Point the cursor at the beginning of the selection.
Shift + click at the point beyond the last character of line.
The newline is not included in the selection, so cut & paste is being awkward.

I know that I can include the newline with Shift + right after click, but it would be better if there was no need to do so.

Try clicking on the line number instead.

@gjsjohnmurray
Thanks for the tip, dragging the line number worked. 😁   However

Line number is so small that we easily misclick breakpoint or fold marker area
Dragging is harder to select many lines. Imagine holding the left button and scrolling wheel until you see the end position.

You don't need to drag the line number. Just click it. And to select multiple, shift-click the final line.


Write nutchpy script to use a continuously running loop that is interruptible with an API call.

Closed in favor of #226


Stop using origin netty interfaces directly

We are using the netty interfaces(or classes) in interfaces that would be used by the end-user such as io.netty.buffer.ByteBuf, io.netty.handler.codec.http.HttpHeaders, io.netty.handler.codec.http.cookie.Cookie and so on...
And this time we want to replace these interfaces(or classes) with our own interfaces(or classes) such as esa.commons.netty.core.Buffer, esa.commons.http.HttpHeaders, esa.commons.http.Cookie and so on...

Try to prevent the end-user from using origin netty interfaces directly, and let end-user use our own interfaces(or classes).

HttpResponseStatus should be replaced.


Can not use my.domain/yourls as my shorturl

Code of Conduct

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

Submission validity

[X] This is not a personal support request, that should be posted on discussions community.
[X] I checked current issues and this request isn't a duplicate of an existing issue, opened or closed.

Self troubleshooting

[X] I've read the documentation and made sure to follow it.
[X] I've read the troubleshooting first steps and frequent issues guides.

Version
1.9.2
Description
I deleted the built-in shorturl of yourls and add a new shorturl the same name with the old built-in one. But it does not take effect. When I visit https://nj.mk/yourls , it should redirect me to https://aka.cy/2023/12/13/How-to-install-YOURLS-with-caddy/, however, it redirects me to its old address https://yourls.org/

Expectation
When I visit https://my.domain/yourls , it should redirect me to my set website instead of https://yourls.org/
Reproduction steps

delete the built-in shorturl of yourls
add a new shorturl the name yourls
visit the new shorturl my.domain/yourls

Context
No response

301 Moved Permanently (the default redirection type used by YOURLS) is aggressively cached by many browsers and CDNs. Clear your browser cache.

Thank you, it works for me.


Is it possible to clone a repo from gitlab?

I have gone through the documentations and doesn't look like there is a way to clone a repo.
Is this intentional or am I missing something?

It is not supported by the GitLab API.


Google Colab installation

Hi
https://colab.research.google.com/drive/1YtXE_JKVntkGK14Yo9thjCjPMVzhA71d?usp=sharing
Here is the colab, but it doesn't run in colab it stops after a while due to memory overload or something like that.
Also there are few changes to be made in the files which are downloaded in the steps in order for it run, so you can't run it as it is.
If you already have a good solution, please support it.

The 13b model that you're using in the test is likely too large for Google Colab. a 7B one is much more likely to work. You should consider the following command:
!CUDA_VISIBLE_DEVICES=0 python3 streaming-llm/examples/run_streaming_llama.py  --enable_streaming --model_name_or_path lmsys/vicuna-7b-v1.3

@tomaarsen After using the suggested model I am facing below error, it seems that model starts the inference and then some error occurs:
USER: Compose an engaging travel blog post about a recent trip to Hawaii, highlighting cultural experiences and must-see attractions.
ASSISTANT: Traceback (most recent call last):
File "/content/streaming-llm/examples/run_streaming_llama.py", line 122, in
main(args)
File "/content/streaming-llm/examples/run_streaming_llama.py", line 103, in main
streaming_inference(
File "/usr/local/lib/python3.11/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/content/streaming-llm/examples/run_streaming_llama.py", line 73, in streaming_inference
past_key_values = greedy_generate(
^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/content/streaming-llm/examples/run_streaming_llama.py", line 20, in greedy_generate
outputs = model(
^^^^^^
File "/usr/local/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/transformers/models/llama/modeling_llama.py", line 1038, in forward
outputs = self.model(
^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/transformers/models/llama/modeling_llama.py", line 925, in forward
layer_outputs = decoder_layer(
^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/transformers/models/llama/modeling_llama.py", line 635, in forward
hidden_states, self_attn_weights, present_key_value = self.self_attn(
^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: llama_pos_shift_attention_forward() got an unexpected keyword argument 'padding_mask'

You must downgrade transformers to below 4.34.0.

Hi tomaarsen

You must downgrade transformers to below 4.34.0. I suspect that 4.33.0 does work.

Thanks for the great support, Zeeshan is the engineer I'm asking to develop for me.
we took your advice and it worked. Really Thank you .
https://colab.research.google.com/drive/1YtXE_JKVntkGK14Yo9thjCjPMVzhA71d?usp=sharing
But here is the problem.
We want to read a Zip file or multiple files and parse and debug their contents, like GPT's code interpreter
In this case, can we make use of the recommended chatbot or similar?
Is it possible to achieve our goal using Colab after this ?

Hi @tomaarsen,
Why don't you just add offload_folder="offload", offload_state_dict=True to from_pretrained as shown here to try and mitigate that issue even when trying to load larger models (13B) on Colab?

That seems wise! Good recommendation.
I don't tend to run into these issues as I don't generally work on Colab.

Tom Aarsen

@DiTo97
@tomaarsen
Thanks for the great feedback.
We will try to implement 13B.
If any other members have successfully implemented 13B,
please comment.

@DiTo97
@tomaarsen
Thanks for the suggestions, they were really helpful.
Now we have bought Colab Pro+. The issue I am facing is that the inference is very slow for 34B or higher models even with a 50/60GB GPU. I am not an expert ML engineer or Deep Learning expert so my issues might seem basic. Can anyone describe why it is happening and is there any way to solve it or does stream require much high power to run smoothly on such large models?

@DiTo97
@tomaarsen
Thanks for the suggestions, they were really helpful.
Now we have bought Colab Pro+. The issue I am facing is that the inference is very slow for 34B or higher models even with a 50/60GB GPU. I am not an expert ML engineer or Deep Learning expert so my issues might seem basic. Can anyone describe why it is happening and is there any way to solve it or does stream require much high power to run smoothly on such large models?

StreamingLLM is not noticeably slower than regular transformers, but such large models are indeed quite slow to run. There are methods to speed this up, like quantization or using non-Python runners (e.g. llama.cpp), but they might not be compatible with the StreamingLLM approach out of the box.


Add new scientific conversion: Number to Categorical

Codecov Report

Merging #7 (14de71e) into main (138f680) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main        #7   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines           31        37    +6
=========================================
+ Hits            31        37    +6

Files
Coverage Δ

ext/SciTypesDynamicQuantitiesExt.jl
100.00% <100.00%> (ø)

ext/SciTypesUnitfulExt.jl
100.00% <100.00%> (ø)

src/SciTypes.jl
100.00% <100.00%> (ø)


Tooltip in Transparent Conduit Facade and Transparent Hardened Conduit Facade gives wrong info

Issue Description:
I read somewhere that the developers decided that the Transparent Conduit Facade and Transparent Hardened Conduit Facades shouldn't hide conduits, but have the wire appear in the block; the tooltip says that it hides it when the facade is painted with a transparent block. I'm new to Ender IO so I ended up having to search online out of confusion.
What happens:
Tooltip gives the wrong info.
Steps to reproduce:

Hold shift to view Ender IO Transparent Conduit Facade and Transparent Hardened Conduit Facade information.

Affected Versions (Do not use "latest"):

EnderIO: 3.1.156
EnderCore: <IP_ADDRESS>-beta
Minecraft: 1.10.2
Forge: <IP_ADDRESS>5

Your most recent log file where the issue was present:
https://gist.github.com/dragon3025/10fffbac749495881a7be145b00f3a5e

A long time ago, facades always hid the conduits inside. Even when painted with something like glass. I didn't think this made much sense, so back in 1.7.10 I made them show the conduits if the block was transparent. A lot of people liked the old way, so this block was added. A facade with a solid paint will never show conduits, but only the transparent conduit facades can show conduits. The tooltip is correct.

Okay, the Transparent Conduit Facade says it hides it with a non-solid block and I was thinking that see-through and transparent blocks were the same thing, so when I panted the Transparent Conduit Facade with glass then used it and the Conduit was still visible, I thought something was wrong.
I think somethings wrong now though, I painted 2 new Conduit Facades, 1 regular and one transparent, with Glass. Both of them are now hiding the conduit, even the Transparent Conduit Facade which didn't hide it earlier.

I confirm that the tooltip is correct, in that the behavior matches what the tooltip says in 1.10.2-<IP_ADDRESS>:

Transparent: hides the conduits when painted with a non-solid block.

Emphasis mine. To reiterate: the transparent conduit facade hides the conduit even when painted with a non-solid block.

However, @tterrag1098 seems to have misspoken:

only the transparent conduit facades can show conduits

This was probably meant to read:
Only the regular conduit facades can show conduits. (And only when painted non-solid.)
The transparent conduit facades hide conduits - regardless of paint.

 Posting to save any future readers the same confusion I had from the misspoken assertion, having settle the matter definitively for myself through experimentation.


Polkadot Js extension refusing to connect

Some of the Artists that minted before used mobile with the Js extension actually. Kiwi Browser supports extension. One artist has an issue connecting to his Polkadotjs wallet. Video:
https://github.com/kodadot/nft-gallery/assets/104380776/7bd0ce82-1138-4f89-984a-d91e2dfeb983

yeah same i didnt know about this. With kiwi browser its possible but I never used it before and I guess its not that known. I will ask him about the account. What do you mean by available?

yeah same i didnt know about this. With kiwi browser its possible but I never used it before and I guess its not that known. I will ask him about the account. What do you mean by available?

When I check my Polkadot Extension on Kiwi Browser I can see my account, from the video it doesn't look like it has account

Closing this issue because the artist let us know that he can log in now. So probably it was some issue on his side.


Winui3 packaged app not available for assigned access (kiosk mode)

This issue has been moved from a ticket on Developer Community.

[severity:I'm unable to use this version]
With Microsoft’s constant recommendation to upgrade from UWP to WinUI3 this is a huge oversight. What is the official path forward here? It is not an option to unpackage for shell launcher.
I need to be able to set a packaged WinUI 3 app as the app for assigned access.

Original Comments
Feedback Bot on 4/6/2024, 10:18 PM:
(private comment, text removed)

Original Solutions
(no solutions)

Closing as duplicate of microsoft/WindowsAppSDK#3642.


Use latest docker image

Use latest docker image for dotnet core aspnet

The HelloWorld application is currently targeting netcoreapp2.0, for targetting netcoreapp3.0 we need to make more changes that update the docker file. Updating these is in our radar, but not something we will be doing right now.
Thanks for the PR though.


error

not sure where to ask this but I'm getting this error and I don't know how to fix it.
module.js:657
throw err;
^
SyntaxError: C:\Users\L\Desktop\steam bot\config.json: Unexpected string in JSON at position 108
at JSON.parse ()
at Object.Module._extensions..json (module.js:654:27)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
at Function.Module._load (module.js:489:3)
at Module.require (module.js:579:17)
at require (internal/module.js:11:18)
at Object. (C:\Users\L\Desktop\steam bot\bot.js:5:16)
at Module._compile (module.js:635:30)
at Object.Module._extensions..js (module.js:646:10)
C:\Users\L\Desktop\steam bot>pause

This has absolutely nothing to do with node-steam. Your own code (in the config.json file) has a typo. I'd suggest learning to completely understand the errors before making issue reports.

sorry but can you help me with this?

Your config.json file has a typo in it that causes it to be invalid.

oh, thanks alot.


"www" Stripped From Absolute Urls with Minimize

When minimize is turned on it seems to remove the www from urls.
I have a little project demonstrating the problem.
https://github.com/jspears/css-loader-minimize-issue.git
Thanks!
-Justin

I just ran your example and the www was still there. Did you try with latest versions?

If this is still an issue on v0.26.1 (i'm guessing not) please open a new issue and reference this  one.


Inconsistent button interactions with Tags

Steps to Reproduce:

Click on the Character's themebook 'Active' button
Notice no interaction
Double-click to open the themebook
Interaction present for 'Active'

Screenrecording
Expected Behavior:
Interaction with buttons should be consistent with behavior of others, such as Burn, Experience and Decay

Hmm, I am not sure I agree. I think this comes down to what you interact with often. I should probably use the tooltip to indicate this on the activation buttons though.
The idea here is to eventually let you highlight tags you want to use in a roll for a "quick roll" mode.

I really like this idea; simply clicking the name of the tag to include it in a roll rather than a separate button would also clean up the overall look if we can remove the side box/diamond next to each tag.
That's something I was considering doing for OS UI since it closely resembles the way character folios appear now.


Fix potential protect-unprotect stack imbalance

Codecov Report

Merging #3 into release-0.1 will not change coverage.
The diff coverage is 100%.

@@             Coverage Diff              @@
##           release-0.1       #3   +/-   ##
============================================
  Coverage        92.64%   92.64%
============================================
  Files                1        1
  Lines               68       68
============================================
  Hits                63       63
  Misses               5        5

Impacted Files
Coverage Δ

src/ape/dnabin.jl
92.64% <100%> (ø)
:arrow_up:

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 2d6d45b...373036e. Read the comment docs.


update-grid-metadata CLI to clize

CLI is soon to be removed
Testing:

[x] Ran tests and they passed OK

 Here is an overview of what got changed by this pull request:

Complexity decreasing per file
==============================
+ lib/improver/tests/acceptance/test_update_grid_metadata.py  -1
+ lib/improver/cli/update_grid_metadata.py  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity decreasing per file
==============================
+ lib/improver/tests/acceptance/test_update_grid_metadata.py  -1
+ lib/improver/cli/update_grid_metadata.py  -2

See the complete overview on Codacy


Fails to install in React 17

I am not sure why, but I am not able to install the package due to ERESOLVE unable to resolve dependency tree.
Here's the full error list:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer react@">=15" from<EMAIL_ADDRESS>
npm ERR!   node_modules/react-owl-carousel
npm ERR!     react-owl-carousel@"*" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/react-owl-carousel/node_modules/react-dom
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>
npm ERR!   node_modules/react-owl-carousel
npm ERR!     react-owl-carousel@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

I am kinda new with React so forgive me if the log clearly shows what's wrong and I just can't see it.

I also have problem with installation.
after  install,
TypeError: Cannot read properties of undefined (reading 'fn')

@stesvis try with npm i react-owl-carousel --legacy-peer-deps
@rameshparajuli You need to inject a global window.jQuery first.
e.g. webpack
// ...
plugins: [
    // other plugins,
    new webpack.ProvidePlugin({
        $: 'jquery',
        jQuery: 'jquery',
        'window.jQuery': 'jquery'
    }),
],
//...

I'm getting an error like this:

this is my code importing jquery lib globaly:
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
import jQuery from "jquery";
import inject from '@rollup/plugin-inject'

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react(),
  	inject({
      $: 'jquery', // this caused warnings for all my scss files that had $variable
      jQuery: 'jquery',
    }),
  ],
})

HELP xwx


Pull request are getting deployed by travis-ci

Currently, because of the maven deploy in the .travis.yml,  every pull request is getting deployed to the repo... this will cause problems.
My suggestions

Remove deploy from travis , and do this from the internal jenkins.
Use a script in travis which will only do a maven deploy if the branch is master.

Good point! :+1:
It makes sense that travis-ci just run the unit tests.
Thank you very much for writing this issue! :)


Fix makefile imgae-build with podman

@msherif1234 this is the same fix as in the operator. Also adding a 2>/dev/null on which to avoid unnecessary errors displayed repeatedly with podman

/lgtm

/approve


output + media_query + transport auto not working properly

Issue description:
When I trying to add some css property to specific @media query, Kirki simply put it without using @media. This occurs only when css added without page reload. On this screenshot see how to added property:

First property added when I try to change value in customizer (is not correct).
Second property added in php before customizer loaded (is correct).
Version used:
2.3.6
Using theme_mods or options?
theme_mods
Code to reproduce the issue (config + field(s))
Example with typography field, but it's not working properly for all available field types.
Kirki::add_field('nk-theme', array(
    'type' => 'typography',
    'settings' => 'typography_html',
    'label' => esc_attr__('HTML', 'nk-theme'),
    'section' => 'typography',
    'default' => array(
        'font-size' => '14px'
    ),
    'output' => array(
        array(
            'element' => 'html',
            'media_query' => '@media (min-width: 991px)'
        ),
    ),
    'transport' => 'auto'
));

Closing as duplicate of #1184

Fixed in 3.0


fix(CodeModal): Adjust height of code editor

Had default from PF examples in but it looks bad on larger office monitor.

Preview: https://virtual-assistant-pr-virtual-assistant-127.surge.sh


Implement WASI path_readlink

Python requires this when running python foo.py

The typo should be fixed on main.

It has a test in WasiPreview1Test. We can't run path_link.rs because requires path_link. I'm hesitant to implement that as symlinks are currently a security hole if using the normal file system.

It has a test

Right, I thought from the wasi-testsuite, but that's good enough :+1:  thanks!


Adding timeout handling

Based on #106
This adds timeout handling similar to the node agent. The timeout window is
configured via the timeout_window config value. Currently this is 150
milliseconds, but because the current system module reads aren't async / run
in parallel this likely won't be enough of a window.
Two ways to address this are:

Initially profile existing system reads and set timeout_window
accordingly.
Make system run in parallel when possible so that it's window is closer
to 150 milliseconds.

Profiling report.send() and it's current implementation takes between 400-800ms to make all the system reads, build the report and send it. Setting the timeout_window to 1500ms for now until the system read is optimized.

@pselle Ok, I added comments/docs. I also decided to switch the unit from milliseconds to seconds as that's what is passed to the signal module anyway. It also makes this feature consistent with network_timeout.


I would like the output of help to be written in READEME.

What's the problem this feature will solve?
This is so that those who are wondering whether to use this tool can understand how to use it at a glance. I also believe that this will encourage more people to use this tool.
Describe the solution you'd like
Describe the output of help in READEME.
Alternative Solutions
Add a man page to the documentation.
#1634

@29rou FYI, there is a PR (#1934) where CLI reference has been included in the pip-tools' documentation.