PV/PVC issue when I update to 1.13.3

What steps did you take and what happened:
I brought up a Quick Start cluster, did a kubeadm reset, reset all iptables rules, upgraded kube* to 1.13.3, and reinitialized a cluster. Once up and Ready, I created a StorageClass and PVC. When I attempt to start a Pod referencing the PVC, it gets stuck in Pending with the following entry in the 'describe' output:
Warning  FailedScheduling  0s (x3 over 0s)    default-scheduler  0/2 nodes are available: 1 node(s) had taints that the pod didn't tolerate, 1 node(s) had volume node affinity conflict.

What did you expect to happen:
For the Pod to start and the PVC to be mounted correctly.
Anything else you would like to add:
I keep finding other "similar" issues references tags on the instances, but haven't found anything that fixes this.
Environment:

Kubernetes version: (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:08:12Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:00:57Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

OS (e.g. from /etc/os-release):

NAME="Ubuntu"
VERSION="16.04.5 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.5 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

Considering all the steps beyond the initial setup that you did, I think this is beyond the scope of the quickstart itself. If you have a working cluster but then after kubeadm reset -> upgrade -> kubeadm init/join you are having problems, you should raise a ticket with kubeadm itself.
Going to close this ticket for now but if you think something is wrong with the original cluster that the quickstart gives you, please elaborate on the problems that exist prior to the additional steps.


In case of "Adjust whole cart to percent" discount amount is getting calculated according to price of one product

Issue Description:- In case admin has selected Adjust whole cart to percent in action type. then at shop if customer has added 1 quantity or more than 1 quantity of same product. after applying coupon discount amount is same in both conditions.
Preconditions:-
framework Version:-0.1.6
Commit id:-0463622
Expected result:-discount amount should be calculated according to sub total
Actual result: discount amount is getting calculated according to price of product.

Framework Version: 0.1.6

Fixed


React v18 upgrade, Webpack rules from react-scripts & auto publishing config

Merging to test publishing and use it on Parca. Please leave your comments here, and I'll address them in a new PR.


feat(chart): add securityContext settings for spec.containers[*].securityContext

Hi, I would like to add configuration which manages container security context in order to enhance container security.

@Flydiverny Could you merge this PR if you are good.

Ah sorry 😄 I was going to get back to it after CI but totally forgot


What if I refuse using  Composer ?

Have gone through this library and want to give it a try BUT I have always avoided using Composer mainly because I love to know what's being loaded and what extra dependence gets installed.
not using Composer means I never get lazy.
Going through https://github.com/sabre-io/event/blob/master/composer.json , I see the only dependency is PHP . I know that means I could do manual installation BUT I just want to ask to be super extra sure.
Asking also because I'm actually more interested in your HTTP library which requires this library as dependency so I checked this out so I could install both manually

IMO refusing composer will lead you to a dead end


Release

Fixes #113.

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


Error: ENOTSUP: operation not supported on socket, mkdir 'path/to/deploy/dir'

I'm using node 6.5.0 both local and remote and shipit 1.4.1.
When I try a basic deploy with shipit-deploy I get this error:
Error: ENOTSUP: operation not supported on socket, mkdir 'path/to/deploy/dir'
This happens in the deploy:fetch task, when it tries to create the workspace.

Seems this was a permission problem, tried another directory and it works now..


The selected data provider crashed. JSON will be used instead.

Issue description

Expected result: What were you expecting to happen?
Sucessful mysql connection and tables to be created
Actual result: What actually happened?
nothing happens. log above

Steps to reproduce the issue

... Instal newest plugin version
... Enable mysql in config

OS and versions

Plugin Version: 2.12
PocketMine-MP:4.4.0
PHP:PHP 8.0.19 (cli) (built: May 13 2022 18:29:39) ( ZTS )
Using JIT: no (delete as appropriate)
Server OS: ubuntu 20.04
Game version: Not the game issue.

Other Plugins
no other plugins.

If you remove all other plugins, does the issue still occur?
yes

Crashdump, backtrace or other files

[17:11:01.419] [Server thread/INFO]: Loading MyPlot v2.1.2
[17:11:01.427] [Server thread/DEBUG]: [MyPlot] Loading Configs
[17:11:01.428] [Server thread/DEBUG]: [MyPlot] Loading MyPlot Generator
[17:11:01.431] [Server thread/DEBUG]: [MyPlot] Loading Languages
[17:11:01.431] [Server thread/DEBUG]: [MyPlot] Loading Data Provider settings
[17:11:01.436] [Server thread/ERROR]: [MyPlot] The selected data provider crashed. JSON will be used instead.

I also tried using following command in mysql directly
mysql> CREATE TABLE IF NOT EXISTS plotsV2 (level TEXT, X INT, Z INT, name TEXT, owner TEXT, helpers TEXT, denied TEXT, biome TEXT, pvp INT, price FLOAT, PRIMARY KEY (level, X, Z));

Result was
ERROR 1170 (42000): BLOB/TEXT column 'level' used in key specification without a key length

maybe related

ah I didn't specify the max varchar length for the world name

@jasonwynn10 yes. Is this fixable ? Could you also include more logging if next sql statement will throw error ? This way I won't need to manually execute statements.


chore: fix release recipe to create artifacts dir

This change is part of the following stack:

#22 ◀

Change managed by git-spice.


Add 3ML Band function with same parameters as megalib

Added custom Band function (Band_Eflux) that takes same parameters as those in megalib source files

Thanks @eneights . It looks good to me, except that I think it should be "particle flux" or just "flux" instead of "energy flux". If you agree, it's jut a matter of fixing the documentation.
I run this quick test:
from cosipy import Band_Eflux
from scipy.integrate import quad

a = 1e2
b = 1e4
K = 1

spec = Band_Eflux(alpha=-1,
                  beta=-2,
                  E0=500,
                  K=K,
                  a=a,
                  b=b)

print(quad(lambda e: spec.evaluate_at(e) * e, a, b)) # Energy flux

print(quad(lambda e: spec.evaluate_at(e), a, b)) # Flux

Which results in
(573.9853040642165, 2.498720039464673e-06)
(1.0, 3.697667766561933e-09)

Beside that, I think this should be moved to 3ML. Also, at some point we should clean up the spectral fitting NB, they are getting hard to follows because they have multiple version of the same code within the same notebook. We can merge this now though and I'll open issues to remember us to do this. I'll just wait for the fix in the function docstring.


WhereUniqueInput only takes id property. Why not all properties on the type?

Is your feature request related to a problem? Please describe.
I need to upsert data that has no ID (in the source API) and the WhereUniqueInput only takes an ID and nothing else.
Describe the solution you'd like
mutation upsertMarket(
  $id: ID
  $trader: String!
  $category: String!
  $type: String!
  $base: String!
  $quote: String!
  $maker: String!
  $taker: String!
  $precisionAmount: Int!
  $precisionBase: Int!
  $precisionPrice: Int!
  $precisionQuote: Int!
  $active: Boolean!
) {
  upsertMarket(
    where: {
      base: $base,
      quote: $quote,
    }
    create: {
      trader: $trader
      category: $category
      type: $type
      base: $base
      quote: $quote
      maker: $maker
      taker: $taker
      precisionAmount: $precisionAmount
      precisionBase: $precisionBase
      precisionPrice: $precisionPrice
      precisionQuote: $precisionQuote
      active: $active
    }
    update: {
      trader: $trader
      category: $category
      type: $type
      base: $base
      quote: $quote
      maker: $maker
      taker: $taker
      precisionAmount: $precisionAmount
      precisionBase: $precisionBase
      precisionPrice: $precisionPrice
      precisionQuote: $precisionQuote
      active: $active
    }
  ) {
    id
  }
}

Describe alternatives you've considered
I don't know how to solve this without implementing upsert myself with a find (with the where clause that I want) and then a create or update.

Hey @Industrial ,
thanks for reaching out to us! 🙏  The reason is that our upsert operates on exactly one node. Therefore the where argument accepts only unique fields of a given type. Do you have some unique field on your source data? You mentioned that it has no id but maybe it has something else. If you have one i would suggest to add this to your data model.
In case that it does not: Can you describe your data model and usecase in more detail, please? Your where consists of base and quote. Is the combination of those 2 unique for that type? If not the upsert would potentially update multiple nodes of a type but always just create one. That seems to be a bit unintuitive to me. When your answer gives us more detail we could consider adding a new mutation, e.g. upsertMany that could accept non unique fields.

Hi @mavilein.
The combination of the properties 'quote' and 'base' make a row/entry unique, so that's why I wanted to query with it.
My application is a charting application for financial data and this query is for the list of markets tradeablle with a trader. I'm pulling in this JSON data every 24 hours from the trader's API.

Then this is a simply question of adding the support for multi field unique constraints.
@Industrial : i have just published a spec for our data model that also touches this topic. We would love to hear your feedback on this one.


[component]: Language switch

Create a standalone language switch component. The current implementation (https://github.com/swisspost/design-system/tree/main/packages/internet-header/src/components/post-language-switch) relies on a config file, the new component should be usable without that configuration.
Design
https://www.figma.com/design/JIT5AdGYqv6bDRpfBPV8XR/Foundations-%26-Components-Next-Level?node-id=2908-30439&t=saHtog1amMMrG60S-4
Requirements

Keep the current functionality intact
Arrow keys should be used to switch between languages
Pay attention to the accessibility features implemented (screen readers should not read "EN" but "English" in the correct language)
There are two ways the component can be displayed, as a dropdown and as a horizontal list
This component does not need to be tokenised for the time being

Reference

### Tasks
- [ ] Create a `<post-language-switch>` component
- [ ] Add documentation
- [ ] e2e tests
- [ ] Visual regression tests
- [ ] Design review

Component naming possibilities:

post-language-switch
post-languageswitch
post-i18n
post-language-dropdown
post-language-menu

Should this component be made only from <post-menu> and <post-list> with according styles from the styles package?


feat: added Summary extension

What is the purpose of this pull request? (put an "X" next to an item)
[ ] Documentation update
[ ] Bug fix
[ ] New feature
[ ] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)
Is there anything you'd like reviewers to focus on?

Codecov Report

Merging #19 (0916e20) into main (e5ff949) will increase coverage by 3.36%.
The diff coverage is 98.82%.

@@            Coverage Diff             @@
##             main      #19      +/-   ##
==========================================
+ Coverage   90.47%   93.83%   +3.36%
==========================================
  Files           8       12       +4
  Lines         126      211      +85
==========================================
+ Hits          114      198      +84
- Misses         12       13       +1

Impacted Files
Coverage Δ

lib/src/core/annotation_properties.dart
100.00% <ø> (ø)

lib/src/core/core.dart
94.20% <ø> (ø)

lib/src/core/summary.dart
98.63% <98.63%> (ø)

lib/src/core/models/summary_image_options.dart
100.00% <100.00%> (ø)

lib/src/core/models/summary_table_cell.dart
100.00% <100.00%> (ø)

lib/src/core/utils/summary_filepath.dart
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


How can you see the results during the run?

or how did you plot all of your figures

Add  --display=True when do python main or run tensorboard --logdir ./logs to run tensorboard for visualization of training details.

Is there anyway you could elaborate on how to use tensorboard to get the graphs that you show?
I get it to run in a browser. but I have no idea how to get the plots.

Me too. I point tensorboard to ./logs and it shows me a very simple graph, but no graphs.


fix: validate the existence of association by id for creation or update

validations of credential_id, credential_type_id, organization_id were missing in various places.
AAP-23105: Need to validate association ids

@bzwei @hsong-rh We already encountered this error due to RBAC permission check, @hsong-rh has fixed it in his PR


Cow: Watch gemstycoon.com

Cow requests the watch of the watch_keyword gemstycoon\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by rene in Charcoal HQ


Please automate!

Hi! Thank you for this! I'm a true noob on all things related to coding/modding, but I recently got addicted to Dorfromantik, and it actually inspired me to learn how to code/modify the game. It took me an hour but I learned how to install this project, and it's almost everything I need! The only thing it's missing is the link to the game so that you don't have to manually update the application every time you place a tile. That way, we can use it only when we want to check if we have the perfect tile in a 30k point game. Having to manually switch back and forth every time you place a tile makes it a chore to even get to 100 tiles placed. I'd really really appreciate it if you created that bridge between the game and your awesome tool. If you think it's something a very beginner enthusiast could pull off, I'd appreciate a point in the right direction and your guidance! Thanks!
Edit: Just saw the closed posts; in case it makes a difference, what I'm hoping to have in this tool is for it to update its map automatically when the player places a tile in game - it could even be like a time delay thing, like update every 10 seconds, even if it doesn't recognize when the player makes a change on the map, and it doesn't have to recognize the next piece and suggest a place for it before you ask it to.

Hello, thanks for reaching out. Obviously I can appreciate the request-- if you don't have two monitors or don't wish to play the game in windowed mode such that the two applications can be seen side by side, I can see how switching between the applications would be extremely annoying.
I think what you are requesting is extremely difficult. I am not aware of any API provided by Dorfromantik in order to interact with the game; at one point I even decompiled the game source code to take a look!

Thank you for the reply! I ran into another issue today as I went to load a save file (generated by dorfperfekt), but it didn't want to open, and cmd kept giving me errors (did some digging, and one of the tiles is apparently saved in an invalid location and there are too many tiles to sort xD).
I'm sad to hear about the difficulty of automation. I tried to peek into my dorfromantik savefiles and see if there was anything useful to start working on, but no luck there either. Looks like we got some folks working on this but they all run into the same problem with lack of automation. https://www.reddit.com/r/Dorfromantik/comments/12xxaya/dorfromantik_solver/
https://github.com/patrickthomashansen/dorfromantik_helper
I do get it may be too much just for a hobby, but hey, it's an interesting puzzle in itself if you ever get back to it!

Please create a new issue for the save file issue-- that I will fix. This is the first I've heard of any issue there.
I'm aware of these other tools, similar to mine. I'm not aware of any of them investigating automation.
If one were to solve automation, I would suggest it be done by DLL injection. This could turn into an arms race-- if the developers cared to, they could implement anti-cheat, I would then have to work around, and so on.
Of course it could be done. I'm personally not interested in solving this. If you were able to create a Python interface to control the game by DLL injection I would be happy to integrate it, but it sounds like that might be past your experience level.


Manage runtimes view should show owner name

The Manage runtimes view should show the owner name instead of a cryptic ID.

Same for Manage Data Planes view:

This issue has been fixed and will be available in the GA Release


Add creation form to generic chooser modals

Part of #8480. ~Incorporates #8669, #8712, #8717~

Hey Matt, I tried to review this but had trouble rebasing on main due to some conflicts, happy to do another test but overall this code looked ok.
As for manually testing this, I did check out the branch but could not work out how to make the create form appear - do I need to do something special with the Snippet registration or with the FieldPanel to activate this?

@lb- Rebased now - I think git got confused by b93729fd860aff8a6b9c7b4719c7fc94289b0f71 being squashed.
Adding form_fields = ["some", "list", "of", "fields"] to your ChooserViewSet subclass should be enough to get the create form to appear.


Most likely answer the question of research

Most likely answer the question of research

Relevance in research mode and html output


[resolves #78] - Management operations for modifiable security realms.

Depends On

https://github.com/wildfly-security/wildfly-elytron/pull/262
https://github.com/wildfly-security/elytron-subsystem/pull/98

Overview

Added a separated IdentityResourceDefinition to provide management operations for modifiable security realms and their identities. So far, we have the following operations defined:

read-identity
add
remove
add-attribute
remove-attribute
set-credential
unset-credential

The IdentityResourceDefinition can be used by both SecurityDomain and SecurityRealm definitions.

Within a SecurityDomain, the IdentityResourceDefinition provides cross-realm operations based on the SecurityIdentity obtained from the security domain. At this level, the operations around identities are basically read-only, providing useful information about the identities managed by a SecurityRealm.
Within a SecurityRealm, the IdentityResourceDefinition provides realm-specific operations for those realms that implement ModifiableSecurityRealm. At this level, the operations may cover writes, reads or both for the identities managed by a specific realm.

Regarding password management, the main password types are being supported. Are they:

Clear
Digest
Simple Digest
Salted Digest
Scram
Bcrypt

Regarding attributes, the operations support the addition or removal of single or multi-valued attributes. When removing, is also possible to remove a specific value from an attribute.

In a near term, I think we can easily replace some of the *.sh scripts shipped with WildFly with this management layer. Feature-wise, what we have so is covering most of what is provided by the add-user.sh with much more flexibility on how identities are managed. Maybe vault.sh as well ?
I'm trying to cover every single capability in a test, which is basically using all the operations mentioned above. For more details, see IdentityOperationsTestCase.
Work in progess

See how we can automatically enable/disable the IdentityResourceDefinition for a SecurityDomain or SecurityRealm. Right now, I'm just using the FileSystemRealmDefinition and DomainDefinition to enable the identity management operations.
Pretty much the same above, but also consider custom realm definitions.

Usage Examples

Reading an identity from a SecurityDomain

{
    "operation" => "read-identity",
    "address" => [
        ("subsystem" => "elytron"),
        ("security-domain" => "FileSystemDomain")
    ],
    "name" => "plainUser"
}

Creating an identity

{
    "operation" => "add",
    "address" => [
        ("subsystem" => "elytron"),
        ("filesystem-realm" => "FileSystemRealm"),
        ("identity" => "plainUser")
    ],
    "name" => "plainUser"
}

Removing an identity

{
    "operation" => "remove",
    "address" => [
        ("subsystem" => "elytron"),
        ("filesystem-realm" => "FileSystemRealm"),
        ("identity" => "plainUser")
    ],
    "name" => "plainUser"
}

Adding an attribute to an identity

{
    "operation" => "add-attribute",
    "address" => [
        ("subsystem" => "elytron"),
        ("filesystem-realm" => "FileSystemRealm"),
        ("identity" => "plainUser")
    ],
    "name" => "Roles",
    "value" => [
        "Admin",
        "Manager",
        "Employee"
    ]
}

Removing an attribute from an identity

{
    "operation" => "remove-attribute",
    "address" => [
        ("subsystem" => "elytron"),
        ("filesystem-realm" => "FileSystemRealm"),
        ("identity" => "plainUser")
    ],
    "name" => "lastName",
    "value" => undefined
}

Setting a password

{
    "operation" => "set-password",
    "address" => [
        ("subsystem" => "elytron"),
        ("filesystem-realm" => "FileSystemRealm"),
        ("identity" => "plainUser")
    ],
    "clear" => {"password" => "clearPassword"}
}

{
    "operation" => "set-password",
    "address" => [
        ("subsystem" => "elytron"),
        ("filesystem-realm" => "FileSystemRealm"),
        ("identity" => "plainUser")
    ],
    "bcrypt" => {
        "salt" => bytes {
            0x1e, 0x0e, 0x2b, 0x56, 0x89, 0xf8, 0x8a, 0x9b,
            0x92, 0x20, 0xf5, 0x21, 0xc0, 0x6d, 0x36, 0x25
        },
        "iteration-count" => 10,
        "password" => "bcryptPassword"
    }
}

Overview

Added a separated IdentityResourceDefinition to provide management operations for modifiable security realms and their identities. So far, we have the following operations defined:

read-identity
add
remove
add-attribute
remove-attribute
set-credential
unset-credential

The IdentityResourceDefinition can be used by both SecurityDomain and SecurityRealm definitions.

Within a SecurityDomain, the IdentityResourceDefinition provides cross-realm operations based on the SecurityIdentity obtained from the security domain. At this level, the operations around identities are basically read-only, providing useful information about the identities managed by a SecurityRealm.
Within a SecurityRealm, the IdentityResourceDefinition provides realm-specific operations for those realms that implement ModifiableSecurityRealm. At this level, the operations may cover writes, reads or both for the identities managed by a specific realm.

Regarding password management, the main password types are being supported. Are they:

Clear
Digest
Simple Digest
Salted Digest
Scram
Bcrypt

Regarding attributes, the operations support the addition or removal of single or multi-valued attributes. When removing, is also possible to remove a specific value from an attribute.

I'm trying to cover every single capability in a test, which is basically using all the operations mentioned above. For more details, see IdentityOperationsTestCase.
Work in progess

See how we can automatically enable/disable the IdentityResourceDefinition for a SecurityDomain or SecurityRealm. Right now, I'm just using the FileSystemRealmDefinition and DomainDefinition to enable the identity management operations.
Pretty much the same above, but also consider custom realm definitions.

Usage Examples

Reading an identity from a SecurityDomain

{
    "operation" => "read-identity",
    "address" => [
        ("subsystem" => "elytron"),
        ("security-domain" => "FileSystemDomain")
    ],
    "name" => "plainUser"
}

Removing an identity

{
    "operation" => "remove",
    "address" => [
        ("subsystem" => "elytron"),
        ("filesystem-realm" => "FileSystemRealm"),
        ("identity" => "plainUser")
    ],
    "name" => "plainUser"
}

Adding an attribute to an identity

{
    "operation" => "add-attribute",
    "address" => [
        ("subsystem" => "elytron"),
        ("filesystem-realm" => "FileSystemRealm"),
        ("identity" => "plainUser")
    ],
    "name" => "Roles",
    "value" => [
        "Admin",
        "Manager",
        "Employee"
    ]
}

Removing an attribute from an identity

{
    "operation" => "remove-attribute",
    "address" => [
        ("subsystem" => "elytron"),
        ("filesystem-realm" => "FileSystemRealm"),
        ("identity" => "plainUser")
    ],
    "name" => "lastName",
    "value" => undefined
}

Setting a password

{
    "operation" => "set-password",
    "address" => [
        ("subsystem" => "elytron"),
        ("filesystem-realm" => "FileSystemRealm"),
        ("identity" => "plainUser")
    ],
    "clear" => {"password" => "clearPassword"}
}

{
    "operation" => "set-password",
    "address" => [
        ("subsystem" => "elytron"),
        ("filesystem-realm" => "FileSystemRealm"),
        ("identity" => "plainUser")
    ],
    "bcrypt" => {
        "salt" => bytes {
            0x1e, 0x0e, 0x2b, 0x56, 0x89, 0xf8, 0x8a, 0x9b,
            0x92, 0x20, 0xf5, 0x21, 0xc0, 0x6d, 0x36, 0x25
        },
        "iteration-count" => 10,
        "password" => "bcryptPassword"
    }
}

'Coding In Progress' is for use on issues not pull requests, just placing 'On Hold' so it does not accidentally get merged.

Am ready to merge just needs a rebase.
Subsequently we may then want to look at if the CLI requires any custom operations to make this easier to work with.


semanticdb-javac terminates in error "silently", due to a NullPointerException

Platform: VSCode/Metals/Bloop on Windows 10 with Java 8 GraalVM 20
This issue is a propagation of https://github.com/scalameta/metals/issues/6191
It looks like it went sour in:

https://github.com/sourcegraph/scip-java/compare/v0.9.3...v0.9.4
https://github.com/sourcegraph/scip-java/pull/618

Still broken against v0.9.9 against which I did my debugging below.
It seems to be triggered by an annotation on a local variable
  private <T> Function<InvocationHandler, T> getConstructor(Class<T> contract) {
    @SuppressWarnings("unchecked")
    Constructor<T> constructor = (Constructor<T>)

Which throws a NullPointerException here
JavacTrees.getElement(TreePath) (c:\Program Files\Java\graalvm-ce-java8-20.3.3\src\com\sun\tools\javac\api\JavacTrees.java:319)
JavacTrees.getElement(TreePath) (c:\Program Files\Java\graalvm-ce-java8-20.3.3\src\com\sun\tools\javac\api\JavacTrees.java:119)
SemanticdbTrees.annotationBuilder(AnnotationTree) (Unknown Source:87)
SemanticdbTrees.annotations(Tree) (Unknown Source:71)
SemanticdbVisitor.emitSymbolInformation(Element,Tree) (Unknown Source:134)
SemanticdbVisitor.emitSymbolOccurrence(Element,Tree,Name,Semanticdb$SymbolOccurrence$Role,CompilerRange) (Unknown Source:114)
SemanticdbVisitor.resolveVariableTree(VariableTree,TreePath) (Unknown Source:282)
SemanticdbVisitor.resolveNodes() (Unknown Source:209)
SemanticdbVisitor.buildTextDocument(CompilationUnitTree) (Unknown Source:94)
SemanticdbTaskListener.onFinishedAnalyze(TaskEvent) (Unknown Source:96)
SemanticdbTaskListener.finished(TaskEvent) (Unknown Source:63)
ClientCodeWrapper$WrappedTaskListener.finished(TaskEvent) (c:\Program Files\Java\graalvm-ce-java8-20.3.3\src\com\sun\tools\javac\api\ClientCodeWrapper.java:681)
MultiTaskListener.finished(TaskEvent) (c:\Program Files\Java\graalvm-ce-java8-20.3.3\src\com\sun\tools\javac\api\MultiTaskListener.java:111)
JavaCompiler.flow(Env,Queue) (c:\Program Files\Java\graalvm-ce-java8-20.3.3\src\com\sun\tools\javac\main\JavaCompiler.java:1342)
JavaCompiler.flow(Env) (c:\Program Files\Java\graalvm-ce-java8-20.3.3\src\com\sun\tools\javac\main\JavaCompiler.java:1296)
JavaCompiler.compile2() (c:\Program Files\Java\graalvm-ce-java8-20.3.3\src\com\sun\tools\javac\main\JavaCompiler.java:901)
JavaCompiler.compile(List,List,Iterable) (c:\Program Files\Java\graalvm-ce-java8-20.3.3\src\com\sun\tools\javac\main\JavaCompiler.java:860)
Main.compile(String[],String[],Context,List,Iterable) (c:\Program Files\Java\graalvm-ce-java8-20.3.3\src\com\sun\tools\javac\main\Main.java:523)
Main.compile(String[],Context,List,Iterable) (c:\Program Files\Java\graalvm-ce-java8-20.3.3\src\com\sun\tools\javac\main\Main.java:381)
Main.compile(String[],Context) (c:\Program Files\Java\graalvm-ce-java8-20.3.3\src\com\sun\tools\javac\main\Main.java:370)

JavacTrees

    public Symbol getElement(TreePath path) {
        JCTree tree = (JCTree) path.getLeaf();

Because here
https://github.com/sourcegraph/scip-java/blob/e4c4ffb42e11cf8bab94e8d038c42f939e6b3d27/semanticdb-javac/src/main/java/com/sourcegraph/semanticdb_javac/SemanticdbTrees.java#L87
variableTreePath ends up being null.
For some reason the new construct cannot cope with annotations on local variables. If I move the annotation to the method level it seems to get past the null pointer problem.
Why it fails on that exact instance is unclear, I have different java codebases where I use it on locals, fields or classes where I didn't see the issue surface.
Perhaps it has to do with the method being private (e.g.  the variable was named local14 in the tree model).
More I wasn't able to determine whilst debugging on the release version of the Javac plugin.
I think I collected al relevant info. So far I still have the break on the code line just before the NullPointerException occurs should I need to attempt to gather anything else.

@varungandhi-src I think this was fixed in https://github.com/sourcegraph/scip-java/pull/691

I also think it was @Arthurm1, we're just fighting automated tooling closing stuff :)

Was a bit disappointed when I saw it auto closed, but am delighted about the open-close sandwich outcome 😄


feat(clp-package): Add support for Json extraction task

Description
This PR adds json extraction task for the clp-package to prepare for the log-viewer support. The PR contains the following changes:

Added a new JsonExtractionJob to the query-scheduler.
Refactor the query scheduler and extract_task so that they support both IR extraction and Json extraction
Rename the extraction jobs. Such that IR extraction and Json extraction jobs are categorized as "Stream extraction job". Refactor multiple places in the code base to use the new naming standard.
Support submitting a Json extraction job from decompress.sh script

Validation performed
For CLP-unstructured.
Confirmed that a compressed file and be opened in the log-viewer via CLP webui.
For CLP-Json
Confirmed that a Jsonl file gets can be extracted when submitting a job via decompress.sh script

Summary by CodeRabbit

New Features

Introduced support for JSON extraction alongside existing IR extraction capabilities.
Added new command for JSON extraction and updated relevant job handling logic.
Enhanced user interface to accommodate JSON extraction queries.

Bug Fixes

Improved error handling for extraction job submissions.

Documentation

Updated configuration files and environment variables to reflect the transition from IR to stream terminology.

Refactor

Renamed variables and methods to align with the new streaming data focus across multiple components.

To see the specific tasks where the Asana app for GitHub is being used, see below:

https://app.asana.com/0/0/1208758891566689

Sorry for the delay, still in the process of putting together my review.


Webpack fails with "File not under rootDir" error

This is an attempt to resolve ci build issues with webpack as shown in the following example:
  ERROR in /home/runner/work/vscode-ansible/vscode-ansible/src/extension.ts
  ./src/extension.ts 5:30-48
  [tsl] ERROR in /home/runner/work/vscode-ansible/vscode-ansible/src/extension.ts(5,31)
        TS6059: File '/home/runner/work/vscode-ansible/vscode-ansible/src/features/vault.ts' is not under 'rootDir' '/home/runner/work/vscode-ansible/vscode-ansible/packages/ansible-language-server'. 'rootDir' is expected to contain all source files.
    The file is in the program because:
      Imported via "./features/vault" from file '/home/runner/work/vscode-ansible/vscode-ansible/src/extension.ts'
      Root file specified for compilation
  ts-loader-default_02839d45964937a4

In my local test, these error occurred in 25% of probability (5 out of 20 executions of yarn webpack).
The fix contains following changes:

Add a new module rule to webpack.config.ts. Before this PR (after #1277), one rule was used for building sources for extension and ALS and unexpected compilations were done. For example, out/src/client directory contained package subdirectory, which contained outputs of ALS even though the same outputs were found in /out/src/server as well. Though it is not 100% sure why the error occurs only in 25% of time, build of extension and ALS should be clearly separated.
Removed yarn als:compile and yarn compile from yarn webpack because webpack will compile TypeScript sources we do not need to pre-compile before running webpack.  They generates unnecessary js files because webpack creates bundiled js files for extension.js and server.js.
Specify output directory of ALS in webpack.config.ts to out/src/server of project root. For debugging TypeScript, d.ts files need to be stored there.
Update Taskfile.yml to run yarn test-compile before running e2e/UI test.  Since we no longer run yarn compile, which executed tsc -p ./ that compiled test files, we need to explicitly build test sources before running tests.

One remaining issue is that the source maps are generated in production build as well. It is possible to create separate webpack configurations for production and development, but it seems that we are using a single configuration for both. We may want to have separate webpack configuraitons in the near future.

I am going to close this without merging for now.


Chrome extension removing command line instructions statement on PR page

On the PR page, if I enable the chrome extension it removes the You can also open this in GitHub Desktop or view command line instructions. statement.
I even added every feature in the Features to disable tab, but still I could not bring back the statement.
Is it desired to by-default remove this statement or am I missing something?
Chrome Extension version: <IP_ADDRESS>5
Without chrome extension

With chrome extension

This is intentional.

Any way of disabling it?

@prabhakar267
.status-meta { display: block !important; }
in the custom CSS should work fine.

The best rationale given is outdated, because the instructions also point to GitHub Desktop:

It's not just about the space it takes. We want to make developers more efficient. Copy-pasting many commands are not. We are highly opinionated about most things here. Might not fit everyone's mindset, but we do make people more efficient.


fix(charts/tigera-operator/kubernetes-services-endpoint): quote port

Description
fixes installation of calico tigera-operator with kubernetes-service-endpoint set.
Currently the following error occurs: ConfigMap in version "v1" cannot be handled as a ConfigMap: json: cannot unmarshal number into Go struct field ConfigMap.data of type string

Related issues/PRs
none

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

TBD

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

/sem-approve


`GLIBC_2.32' error not found after updating to 2023.4.0 on Ubuntu 20.04

Expected Behavior
When running insomnia I expect the application to start and for the main window to be displayed.
Actual Behavior
The application does not display the main window. Instead, the following error is shown in the terminal:
A JavaScript error occurred in the main process
Uncaught Exception:
Error: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /tmp/.org.chromium.Chromium.vHhMbC)
    at process.func [as dlopen] (node:electron/js2c/asar_bundle:2:1822)
    at Module._extensions..node (node:internal/modules/cjs/loader:1259:18)
    at Object.func [as .node] (node:electron/js2c/asar_bundle:2:2049)
    at Module.load (node:internal/modules/cjs/loader:1044:32)
    at Module._load (node:internal/modules/cjs/loader:885:12)
    at f._load (node:electron/js2c/asar_bundle:2:13330)
    at Module.require (node:internal/modules/cjs/loader:1068:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at Object.<anonymous> (/opt/Insomnia/resources/app.asar/node_modules/@getinsomnia/node-libcurl/dist/Easy.js:5:18)
    at Module._compile (node:internal/modules/cjs/loader:1174:14)

Reproduction Steps

Install Insomnia 2022.3 on Ubuntu 20.04 using dpkg
Download Insomnia to 2023.4.0 .deb package from the website
Update to Insomnia to 2023.4.0 using dpkg
Start insomnia from the Gnome shell or a terminal using insomnia
Notice the error and that the main window does not display

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
No response
Insomnia Version
2023.4.0
What operating system are you using?
Ubuntu
Operating System Version
20.04
Installation method
Download .deb package and install with dpkg
Last Known Working Insomnia version
2023.2.2

Our github actions end to end tests are working on ubuntu 22.04.2 perhaps an upgrade could work for you.

I am with the same problem.

I have the same issue with the fresh installation of 2023.4.0 on Ubuntu 20.04.

Does latest vscode work on Ubuntu 20.04?

Appimage has the same error

From your statement that you have GLIBC_2.31 currently available, it seems you are using Ubuntu 20.04. To get GLIBC_2.32 you would need to use Ubuntu 20.10 or another operating system that offers that version. Trying to upgrade glibc on your existing system will likely lead to many problems.

https://unix.stackexchange.com/questions/628021/glibc-2-32-not-found

From your statement that you have GLIBC_2.31 currently available, it seems you are using Ubuntu 20.04. To get GLIBC_2.32 you would need to use Ubuntu 20.10 or another operating system that offers that version. Trying to upgrade glibc on your existing system will likely lead to many problems.

https://unix.stackexchange.com/questions/628021/glibc-2-32-not-found

Unless you need it to build, if you change your CI/CD workflows to build in Ubuntu 20, it will create builds that work in both 20 and 22

Alternatively you could clone the repo and run
npm install
npm run app-package

I have similar issue with flatpak package when using Ubuntu 22.04.3
Uncaught Exception:
Error: /usr/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /run/user/1000/app/rest.insomnia.Insomnia/.org.chromium.Chromium.KftYCz)
    at process.func [as dlopen] (node:electron/js2c/asar_bundle:2:1822)
    at Module._extensions..node (node:internal/modules/cjs/loader:1354:18)
    at Object.func [as .node] (node:electron/js2c/asar_bundle:2:2049)
    at Module.load (node:internal/modules/cjs/loader:1124:32)
    at Module._load (node:internal/modules/cjs/loader:965:12)
    at f._load (node:electron/js2c/asar_bundle:2:13330)
    at Module.require (node:internal/modules/cjs/loader:1148:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/app/main/resources/app.asar/node_modules/@getinsomnia/node-libcurl/dist/Easy.js:5:18)
    at Module._compile (node:internal/modules/cjs/loader:1269:14)

I have similar issue with flatpak package when using Ubuntu 22.04.3

Same problem here with Flatpak

Same issue with Flatpak version 2023.5.7 on Ubuntu 22.04.
Version 2023.1.0 starts as expected

Same issue with Flatpak version 2023.5.7 on Ubuntu 22.04. Version 2023.1.0 starts as expected

Thanks! This version starts now. Another day saved by random stranger on Github.

Same issue with flatpak version 2023.5.7 on popos 22.04. :(

I'm experiencing this issue now on Ubuntu 20.04.6 LTS, and using the version specified by @dgasper and link from @WesternGun fixed the issue for me. I'm fine running the older version of Insomnia, just as long as it works.

Version 3.0 works but yeah upgrading an OS is not a solution (in my case latest Zorin OS is based on Ubuntu 20.04)

To view all versions:
apt-cache showpkg insomnia
The last without error: 2023.3.0, then:
sudo apt install insomnia=2023.3.0

To view all versions: apt-cache showpkg insomnia
The last without error: 2023.3.0, then: sudo apt install insomnia=2023.3.0

Thanks alot, this solved it.

To view all versions: apt-cache showpkg insomnia
The last without error: 2023.3.0, then: sudo apt install insomnia=2023.3.0

To no longer update, do:
sudo apt-mark hold insomnia

Why is this closed? It is not resolved and very much present. Changing an operating system version or only using an older application version is hardly a good solution...

I could install 2.32 with https://askubuntu.com/questions/1345342/how-to-install-glibc-2-32-when-i-already-have-glibc2-31 but insomina didn't work.
this worked as a charm!!!
sudo apt install insomnia=2023.3.0

Why is this closed? It is not resolved and very much present. Changing an operating system version or only using an older application version is hardly a good solution...

This

The error is still present on Ubuntu 20.04.6

As others have mentioned, the issue is not solved, so this should not be closed. @jackkav tagging you since you marked it as closed; any chance we can reopen it? Ubuntu 20.04 is supported until April 2025, and so until that date, suggesting to upgrade the OS or to install an older version of Insomnia is not a solution.

Hey guys. I am facing this problem too.any update on?

I'm experiencing this issue now on Ubuntu 20.04.6 LTS, and using the version specified by @dgasper and link from @WesternGun fixed the issue for me. I'm fine running the older version of Insomnia, just as long as it works.

Me too. Per @dgasper I installed 2023.1.0 from https://github.com/Kong/insomnia/releases/tag/core%402023.1.0 and it's working fine now on Ubuntu 20.04.

To view all versions: apt-cache showpkg insomnia
The last without error: 2023.3.0, then: sudo apt install insomnia=2023.3.0

fixed with this, a shame this is totally ignored for devs on ubuntu (majority).


RUM-2708: Enable Resource Endpoint by default

What does this PR do?
• Renames base64 packages to resources
• Renames resource classes
• Removes base64 from the lrucache
• Removes the Resource Endpoint feature flag.
Motivation
Final PR for the Resource Endpoint
Additional Notes
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1858 (3efc1e8) into jmoskovich/rum-2709/record-resources (ef39f54) will increase coverage by 0.11%.
The diff coverage is 94.74%.

Additional details and impacted files
@@                           Coverage Diff                            @@
##           jmoskovich/rum-2709/record-resources    #1858      +/-   ##
========================================================================
+ Coverage                                 83.22%   83.34%   +0.11%
========================================================================
  Files                                       476      475       -1
  Lines                                     16768    16721      -47
  Branches                                   2509     2494      -15
========================================================================
- Hits                                      13955    13935      -20
+ Misses                                     2120     2100      -20
+ Partials                                    693      686       -7

Files
Coverage Δ

...adog/android/sessionreplay/SessionReplayPrivacy.kt
100.00% <100.00%> (ø)

...android/sessionreplay/internal/ResourcesFeature.kt
88.89% <ø> (ø)

...oid/sessionreplay/internal/SessionReplayFeature.kt
99.09% <100.00%> (+4.50%)
:arrow_up:

...ssionreplay/internal/recorder/ViewUtilsInternal.kt
100.00% <ø> (ø)

...order/mapper/BaseAsyncBackgroundWireframeMapper.kt
95.24% <ø> (ø)

...replay/internal/recorder/mapper/ImageViewMapper.kt
94.59% <ø> (ø)

...nternal/recorder/mapper/MaskInputTextViewMapper.kt
80.00% <ø> (ø)

...lay/internal/recorder/mapper/MaskTextViewMapper.kt
100.00% <ø> (ø)

...nreplay/internal/recorder/mapper/TextViewMapper.kt
93.33% <ø> (ø)

...onreplay/internal/recorder/resources/BitmapPool.kt
87.50% <ø> (ø)

... and 9 more

... and 24 files with indirect coverage changes


About testing

Continue https://github.com/alexjoverm/tslint-config-prettier/issues/8#issuecomment-322700128.
I'd prefer using my structure (unit tests using some transformer to generate tests), what do you think?

It looks promising indeed. I've been giving a second peek to the test folders and they look well organized, keeping each test atomic. I have some questions:

How easy to maintain is it? Could you describe what steps take to test a new rule? (I suppose copy/paste one of those folders under rules and adapt, but want to be sure)
What's the generated test thing? What's the process.ts file doing and why the code is a string? Could you describe this process in depth?
Related with the previous, what's in src/runtime?

And a consideration:

If possible, I'd like the files we need under your src folder to be javascript. But if its really needed or convenient to be ts files, I don't mind. I just wanted to keep it as lean as possible.

How easy to maintain is it? Could you describe what steps take to test a new rule? (I suppose copy/paste one of those folders under rules and adapt, but want to be sure)

Yes, as you said, it just needs to copy/paste and modify the rule name and the test case, that's it.

What's the generated test thing? What's the process.ts file doing and why the code is a string? Could you describe this process in depth? If possible, I'd like to try it myself, some guidance on the steps to do so are appreciated as well.

It's a jest preprocessor, jest will transform those test case into the real test file so as to test them. (just like ts-jest, but I'm transforming test cases to real tests, so that we don't have to write lots of duplicate test code)

Related with the previous, what's in src/runtime?

They can be also written in the process.ts, but it'd be better to write them in another file and import them so that we can get better support by tools, e.g. IDE, typescript's type check, we can't get any hint from the template string in process.ts.

Do you know if the logic of this test could be somehow reused for #3? Don't worry about this very much, just a side question.

I haven't saw it at tslint's docs, but I think something similar can be found in their source code, needs further investigate.

If possible, I'd like the files we need under your src folder to be javascript. But if its really needed or convenient to be ts files, I don't mind. I just wanted to keep it as lean as possible

I think ts file is more suitable since ts file itself is a good doc and also type-safe, and most of our consumers should be typescript programmer so that I think there won't be problems to write them in typescript.

Let's make tslint-config-prettier a more robust package with your work :)

:)

Thanks for the info.
I'll need more details about the preprocessor thing... How does it work? How can I debug if I need to change something?

In the meanwhile you answer, just wanted to say that I'm ok with it, so you can open a PR and we can iterate over it ;).
Some considerations:

Let's keep src folder for the rulesets, and create a tools folder for the runtime and so on
Please use camelCase instead of sneak_case (including the preprocess)
I'd add a expect(errorCountAfter).toBe(0) line at https://github.com/ikatyang/tslint-config-prettier-ext/blob/master/src/transform/process.ts#L46

I'll need more details about the preprocessor thing... How can I debug if I need to change something?

It's just a string to string function, you can pass the source text to generate the transformed code and then just debug it as usual. The current test process is simple enough so I didn't write tests for them.

I'd add a expect(errorCountAfter).toBe(0)

The reason I write expect(error_count_after).not.toBe(error_count_before) is that there are some counter-rules, which means their rule is conflict with prettier's behavior, the errorCountAfter will never get 0 for those cases, for example:
(tslint-divid/no-semicolon-interface)
// rule fail
interface Foo {
  bar: string;
  zoo(): number;
}

// rule pass
interface Foo {
  bar: string, // <---- but prettier prefer `;`, so it'll never get 0 error after formatting
  zoo(): number,
}

But the point of this package is to disable all rules that conflict with Prettier... Why would be this case different if we set that rule to false?

Uh, sorry for the confusing, what I mean the errorCounter is the counter for the rule (e.g. tslint-divid/no-semicolon-interface), to ensure the rule will be affected before/after formatting.
Steps to test:

lint the source code (enable the rule) <---- before
lint the formatted code (enable the rule) <---- after
their result should be different so as to ensure that rule is exactly affected by prettier.
the count of errors must be 0 after we disable the rule, so we don't need to test it.


[GURPS] 2.9.20

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

Changes / Description

ENHANCEMENT: Traits tab, languages. Added an action button to expand a notes area for each language.
ENHANCEMENT: Rolltemplate update, moved Notes: to a separate row and then applied a title prefix, if needed. For example, if you entered notes for a Ranged Attack, the roll result chat will have a title called Weapon Notes then the notes are displayed below it.
ENHANCEMENT: Combat tab, ranged sub-tab, updates to Thrown Object Tool. Added additional notes and ability to link to DX, Skill, or Technique.
ENHANCEMENT: Updated tooltips for Active Defense, Dodge and Retreat (vs. Melee Attacks Only), ACC, AIM BONUS, and Unconsciousness.
BUGFIX: Fixed issue during load of a new version of the character sheet. The modifier columns for languages were not calculating correctly.

Character Sheet Info Roll20 Internal Use only.


How to create a Skype-only live account?

This repo is pretty active but the demo doesn't function without an old account; what gives?
I have one as I registered it ages ago, but after some research it looks like you MUST have a MS Live account when you register for Skype.
Is there some gotcha to this?

It works with old non MSA accounts without an issue.  What error are you getting?

@mitchcapper That's what I mean. Is this repo only good for old non MSA accounts/usernames? As in, any Skype registered as live:something won't work as per the documentation?

@vladdypwnz you are correct it does say MSA accounts will not work, however I just tested one and it  worked fine.
Please run the following commands then paste the error you get after it gives the login prompt:
git clone https://github.com/demurgos/skype-http
cd skype-http
npm install
npm start


username password

How to add username and password ?

This is a very simple library that does not use username and password for MQTT connection. You can check MQTT doc to add username and password as part of the data packet.

thank you sir, I solved the problem with username and password
Outlook Mobilehttps://aka.ms/blhgte'dan gönderildi

From: ABHAY S BHARADWAJ<EMAIL_ADDRESS>Sent: Sunday, May 3, 2020 9:27:01 PM
To: abhaysbharadwaj/SIM808_MQTT_GPS_Tracker<EMAIL_ADDRESS>Cc: ibrahimcss<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [abhaysbharadwaj/SIM808_MQTT_GPS_Tracker] username password (#1)
This is a very simple library that does not use username and password for MQTT connection. You can check MQTT doc to add username and password as part of the data packet.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/abhaysbharadwaj/SIM808_MQTT_GPS_Tracker/issues/1#issuecomment-623157679, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHHVQHZDIA5MFNU2CFBQ7SDRPWZPLANCNFSM4LSJKVTQ.


Update snap and keyring api dependencies and fix tests

This pull request updates the dependencies in the project, including bumping snap dependencies, keyring-api, and eth-snap-keyring. It also fixes the failing tests.
Closes: https://github.com/MetaMask/accounts-planning/issues/307

@SocketSecurity ignore npm/<EMAIL_ADDRESS>@SocketSecurity ignore npm/<EMAIL_ADDRESS>

I'm gonna drop this branch in favor of this PR (I've backported everything here).


increased version

LGTM

Coverage remained the same at 72.893% when pulling 185c51e39dbbea4178c7426c0553cdb634d14d45 on release-0.6.1 into 411c4901d9d7378835343ad790b4c89e3f79bdc2 on master.


New version: WHONET.AMRIE version 24.6.13

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Hi again @stephengillie, I can see the package info in the master branch manifest folder, but when I try to update with winget the package doesn't have an update available. If I remove and reinstall it, I am still given the "24.2.16" version instead of "24.6.13". Do you know what I might have done wrong?


Error reading file list

Reading a file list for one of my users causes an error in 3.43a
got 65 files for<EMAIL_ADDRESS>Traceback (most recent call last):
File "/home/googbackup/gam/gam.py", line 7605, in
showDriveFiles(users)
File "/home/googbackup/gam/gam.py", line 1896, in showDriveFiles
a_file[attrib] = u' '.join(file[attrib])
TypeError: sequence item 0: expected string or Unicode, dict found
Please advise?

used both 3.45 and 3.5 gam.exe 32bit
having a similar issue when using the allfields switch for a user:
gam.exe user<EMAIL_ADDRESS>show filelist allfields
getting an error of:
Traceback (most recent call last):
File "", line 8435, in
File "", line 2642, in showDriveFiles
TypeError: sequence item 0: expected string or Unicode, dict found
If I don't use allfields it works fine.

Same issue, also using allfields, running tag v3.61
Traceback (most recent call last):
  File "/home/timw/GAM/gam.py", line 9003, in <module>
    showDriveFiles(users)
  File "/home/timw/GAM/gam.py", line 3088, in showDriveFiles
    a_file[attrib] = u' '.join(f_file[attrib])
TypeError: sequence item 0: expected string or Unicode, dict found

Same issue, it seems like there must be a "special character" issue where a filename chokes GAM.  Does anyone have a list of characters that might be a problem?
Traceback (most recent call last):
File "", line 9412, in
File "", line 3446, in showDriveFiles
TypeError: sequence item 0: expected string or Unicode, dict found

Seeing this in GAM-3.65:
$ /gam.py user EMAIL show filelist allfields
. . .
Traceback (most recent call last):
  File "./gam.py", line 9523, in <module>
    showDriveFiles(users)
  File "./gam.py", line 3433, in showDriveFiles
    a_file[attrib] = u' '.join(f_file[attrib])
TypeError: sequence item 0: expected string or Unicode, dict found


Fix typo Update transactions

Fix typo Update transactions
Please read contributing guidelines and remove this line.

thank you


Use go:embed instead of vfsgen for embedded resources handling

It makes sense to use a feature from standard library instead of relying on a 3rd party library. Use of go:embed may also save us from periodical regens of resources.go and unexpected issues due to its inconsistency.
The challenges for using go:embed I identified so far are:

go:embed only allows embedding resources under its current dir. It's not possible to load resources in an arbitrary dir from pkg/resources. That should require you to put a resources.go under both /config and /resources dirs and then reference them from pkg/resources.
There is no easy way to ignore arbitrary files with go:embed. You can only ignore .* and _* files automatically. We'd need to find a way to keep the embedded resources clean and as minimum as possible.

https://github.com/golang/go/issues/42328
https://github.com/golang/go/issues/42325

@gansheer comment if you're working on this.


Required Documentation comment in the starting of programs.

Comments need to be added in the header of the program which gives information about the program.
Programs are present in the "Programs" folder.  If the program already contains comments then only change the format of comments.
Example:
public class Main {
  public static void main(String[] agrs) {

      Integer i = Integer.valueOf("123");
      int a = i + 2;
      System.out.println(a);
      System.out.println(i);
  }
}

/**
  * Program converts the string into an integer.
  * add 2 and print the result.
  */

public class Main {
  public static void main(String[] agrs) {

      Integer i = Integer.valueOf("123");
      int a = i + 2;
      System.out.println(a);
      System.out.println(i);
  }
}

Comments format:
/**
  * comments here;
  */

hey!
May I help you with this?

@diksharai9, Go ahead!
You can start from program 11 in the Programs folder.

@diksharai9, Go ahead!
You can start from program 11 in the Programs folder.

thankyou

Now, Modification is required from Program 31 onwards.

Now, Modification is required from Program 31 onwards.

okay, I will do that.

Up to program 50 documentation comments is completed.

Modfication are required from Program52.java

Hey! can I modify the rest of the comments?

@ritesh-karankal go ahead.
Start from program 52 that is present in the directory of the programs.

@Sid672 I have two questions
do I need to change single-line comments to multi-line comments?
And does spacing of stars matter as other files have different spacing than above mentioned correct format?

@ritesh-karankal
Yes please convert single-line comments into multiple-line comments.
If you follow the above format it's the most correct way. I know some files have comments that don't follow the same format for such files I will create a new issue after closing this issue.


[druid] fix bug around handling NULLs

fillna would miss out on identifying STRING columns for Druid and
replace None in string columns with a numeric 0. This
mixed type column would confuse
pandas down the line on some operations like df.pivot_table.
superseeds https://github.com/apache/incubator-superset/pull/4236
@xrmx 👀

Note that get_fillna_for_columns assumes that the dataframe's column names are bound to table column names and related types. While this is generally the case, this is not enforced, and the bug could show up again if a string column in a dataframe is not named after a database column.
Viz like the Sankey may use specific columns as a source but rename dataframe columns to source and target for instance. In this case the current logic would fail at identifying the df columns as strings and the mixed type issue may re-appear.

A more final solution (outside the scope of this bugfix PR) would be to get better at typing dataframes (currently we have a lot of object types depending on the db engine) and pandas is much slower when operating over object types. We should infer type earlier on in the pipeline and have fillna logic be based on dataframe types instead of column types. (though dataframe types can be inferred from the database types in the first place, though drivers/pandas may fail at that)


PP-1386 Add dropwizard metrics

WHAT
A brief description of the pull request:

We added two environment variables for host and port for
metrics.
If the variables are not passed, default values are going to
get picked up

with @imranbohoran

Code review completed.


Replace async/await wrapper with Future.microtask

Based on the discussion in https://github.com/dart-lang/sdk/issues/11911
this utility was introduced to allow using the microtask queue rather
than the event loop. That used to be what async methods did, but soon
they will be able to start synchronously. new Future.microtask should
keep the old behavior.

LGTM!
With this patch, I could not reproduce the issue from #90 anymore.
Once committed, please update the version in our SDK.

ping.

Landing this and getting it pulled in to pub and the sdk seems somewhat involved. @munificent @jakemac53 any chance one of you could take over? If not I can do it when I'm back from leave.


Merge http of method

Currently the http of methodconf is merged with the context http block.
Please also merge the http block of the method to allow for different configuration per method.
For example, the request headers need to be different for a POST vs GET.
Currently the only means of doing this is via transformRequest in the methodconf http block. This feels hacky.
It would also be good to merge the http block passed to the method to allow per request customization of the config. ie.
MyModel.$fetch({
    http: {
        onUploadProgress(){...}
        ...
    }
});

The brand new Axios plugin is here! It's very different from what it was, so please check out the docs!
I'll be closing this issue since the library is quite different now. Please feel free to open another issue if there's anything!


debian 12 安装依赖报错

root@localhost:~# docker exec -it qinglong bash -c "$(curl -fsSL https://raw.githubusercontent.com/FlechazoPh/QLDependency/main/Shell/QLOneKeyDependency.sh | sh)"

sh: 12: [[: not found
sh: 23: [[: not found
sh: 12: [[: not found
sh: 23: [[: not found
sh: 40: 当前node版本(如果没有node，请自行安装): : not found
sh: 41: node: not found
sh: 44: 当前npm版本(如果没有npm，请自行安装): : not found
sh: 45: npm: not found
sh: 47: npm: not found
sh: 48: cd: can't cd to /ql
sh: 49: pnpm: not found
sh: 51: pnpm: not found
sh: 53: npm: not found
sh: 55: pnpm: not found
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.

    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.

    If you wish to install a non-Debian packaged Python application,
    it may be easiest to use pipx install xyz, which will manage a
    virtual environment for you. Make sure you have pipx installed.

    See /usr/share/doc/python3.11/README.venv for more information.

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
sh: 59: cd: can't cd to /ql/scripts/
sh: 60: cd: can't cd to /ql
sh: 61: apk: not found
sh: 62: cd: can't cd to /ql
sh: 63: apk: not found
sh: 12: [[: not found
sh: 23: [[: not found
sh: 12: [[: not found
sh: 23: [[: not found

bash: line 4: -e: command not found
bash: line 4: $'1m安装依赖...\E[0m': command not found
bash: line 6: -e: command not found
bash: line 6: $'1m安装依赖需要时间，请耐心等待!\E[0m': command not found
bash: line 13: -e: command not found
bash: line 13: 1m依赖安装完毕...建议重启: command not found
bash: line 15: -e: command not found
bash: line 15: 1m有任何问题，请在此仓库提交Issue：: command not found

能看到是你沒有安裝nodejs和npm
進入容器運行這段命令：
ql check

能看到是你沒有安裝nodejs和npm
進入容器運行這段命令： ql check


Show the number of replies in a tweet

Describe the problem
Currently the app shows number of likes and retweets but not the number of replies.
Describe the solution
Show the number of replies

Close as fixed


Adding class based URL resolvers

Replaces the closure based URL resolvers.

Sorry, this was supposed to go to my fork.


socket timeout

Hi,
We were interested in using aredis - in your docs you state that it's imported from redis-py. Do you plan to support a socket_timeout parameter similar to redis-py?

@ter74 There is a parameter named as stream_timeout, which has the same effect

but why don't use the same name?


Expression of equality for more fields

I am building a platform using ANGULAR where you need to fill out a form, there are several fields including email.
This field requires verification, that is, inserting the same email in a different field.
Then the following validation is entered in the verification field:
validators:
          [{
            type: "email",
            text: "Invalid email"
          }, {
            type: "expression",
            text: "Different email",
            expression: "{form_email_verify} == {form_email}"
          }]
The "Different email" validation is ignored, while in the SurveyBuilder it works 100%.
I tried with "==", "=", "equal" but it does not work anyway.
I've tried using multipletext but it does not work.
package.json:
     "survey-angular": "^ 1.0.20",
     "surveyjs-widgets": "^ 1.0.27",
How to solve?
Thank you.

I've created a live sample for you with Angular - https://plnkr.co/edit/1Sbxug8cVsp8jzoxBwDH?p=preview
It works ok for me

Thanks so much!
I understood that the problem was the version, updating the surveyjs from 1.0.20 to 1.0.44 everything worked.
Davide R.


Helm charts and prometheus connector incompatibility in installation

I was trying out this tutorial to build a monitoring dashboard for my synapse spark jobs.
https://learn.microsoft.com/en-us/azure/synapse-analytics/spark/use-prometheus-grafana-to-monitor-apache-spark-application-level-metrics
In step "Install connector, Prometheus server, Grafana dashboard" when I was on step 2 "Install components through Helm client:"
and ran the command,
helm install spo synapse-charts/synapse-prometheus-operator --create-namespace --namespace spo
--set synapse.workspaces[0].workspace_name="<workspace_name>"
--set synapse.workspaces[0].tenant_id="<tenant_id>"
--set synapse.workspaces[0].service_principal_name="<service_principal_app_id>"
--set synapse.workspaces[0].service_principal_password="<service_principal_password>"
--set synapse.workspaces[0].subscription_id="<subscription_id>"
--set synapse.workspaces[0].resource_group="<workspace_resource_group_name>"
I got an error saying:
Error: INSTALLATION FAILED: failed to install CRD crds/crd-alertmanager.yaml: resource mapping not found for name: "alertmanagers.monitoring.coreos.com" namespace: "" from "": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
ensure CRDs are installed first
Can it be fixed?
Thanks
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 5e7945a3-2507-4c95-8353-3efb155602cf
Version Independent ID: 20871415-6f75-3ca1-6249-1a2e04b51860
Content: Tutorial - Monitor Apache Spark Applications metrics with Prometheus and Grafana - Azure Synapse Analytics
Content Source: articles/synapse-analytics/spark/use-prometheus-grafana-to-monitor-apache-spark-application-level-metrics.md
Service: synapse-analytics
Sub-service: spark
GitHub Login: @juluczni
Microsoft Alias: juluczni

@snehalsonwane
Thanks for your feedback! We will investigate and update as appropriate.

Hi @snehalsonwane
The chart "prometheus-operator" is deprecated.
Try this latest one.
$ helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
$ helm repo update
$ helm install kube-prometheus-stack prometheus-community/kube-prometheus-stack --namespace prometheus
For your reference, please go through this document.
https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/
If there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

Hi @Naveenommi-MSFT Thanks for your response.
I will try it out and let you know if I have further questions

@snehalsonwane
We are going to close this thread, if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

Were you able to resolve this as I've the same issue?


proto: initial protobuf for config

To have a less source based, and more consumable example of structures,
this is an initial pass at protobuf structures for the structures from all the current golang source.
There is some exercise needed in platform specific structures.
The Makefile defaults to golang source output, but also has a c target for C source and py target for python as well.
Signed-off-by: Vincent Batts<EMAIL_ADDRESS>

Don't put a refactor patch which refactors another patch inside the same pr.

@laijs eh?

I found you pr has a style-related patch and an indent patch, they are applied for an earlier patch in the same pr, it is bad, the earlier patch should be updated directly to resolve these problem.

Oh I see, I'll flatten the indentation fixes. Not sure why that wasn't
visible earlier. The style change was more for commentary.
As this PR is not against master but for conversation on the whether this
approach with protobuf is sufficient.
On Sep 14, 2015 22:37, "Lai Jiangshan"<EMAIL_ADDRESS>wrote:

I found you pr has a style-related patch and an indent patch, they are
applied for an earlier patch in the same pr, it is bad, the earlier patch
should be updated directly to resolve these problem.
—
Reply to this email directly or view it on GitHub
https://github.com/opencontainers/specs/pull/185#issuecomment-140259851.

@laijs I squashed some and moved the indentation fixes to the initial commit

The idea is that we use protobuf 3 JSON encodings?

https://github.com/google/protobuf/releases/tag/v3.0.0-beta-1 beta was only 28 days ago...

@philips here is the output with this most recent push:
vbatts@valse ~/src/opencontainers/specs/proto (protobuf) $ make
protoc --go_out=./go config.proto
protoc --go_out=./go runtime_config.proto
go run ./example.go
{
  "spec": {
    "platform": {
      "os": "linux",
      "arch": "x86_64"
    },
    "process": {
      "env": [
        "TERM=linux"
      ],
      "cwd": "/"
    }
  }
}

@vbatts The json looks good :+1:

On Thu, Sep 24, 2015 at 10:21:17AM -0700, Brandon Philips wrote:

The idea is that we use protobuf 3 JSON encodings?

I've pushed some work along this lines to vbatts/specs#2, which turns
up some problems with Any support in Go.
I've also pushed some proto2 work fleshing out Process to
vbatts/specs#1 which turns up some problems with the proto2 JSON
serialization.
I'll leave it there for now, but I'm happy to help push this forward
in either direction if folks see a way around those issues.

On Sat, Sep 26, 2015 at 01:12:07PM -0700, W. Trevor King wrote:

I've pushed some work along this lines to vbatts/specs#2, which
turns up some problems with Any support in Go.
I've also pushed some proto2 work fleshing out Process to
vbatts/specs#1 which turns up some problems with the proto2 JSON
serialization.
I'll leave it there for now, but I'm happy to help push this forward
in either direction if folks see a way around those issues.

One way around the Any+Go issue is to use C++ instead of Go ;), so
I've gone that way with vbatts/specs#3.  Differences vs. the current
Markdown-defined spec are the process.user @type (used by Any) 1 and
the runtime.json differences I talk through in
wking/opencontainer-specs@5f422ee6ae.

one approach that could work, regardless of protobuf, but could facilitate this kind of multi-platform accommodation, would be to have the canonical configuration be config.json and platform specific be held in config-$keyword.json. That keyworded filename could be a referenced from the config.json, such that tooling could implement repeatable patterns, but something like the spec would not need to define up front config-{linux,windows,etc}.json.

How about concept of overlaid configurations?
-jojy

On Sep 28, 2015, at 7:51 AM, Vincent Batts<EMAIL_ADDRESS>wrote:
one approach that could work, regardless of protobuf, but could facilitate this kind of multi-platform accommodation, would be to have the canonical configuration be config.json and platform specific be held in config-$keyword.json. That keyworded filename could be a referenced from the config.json, such that tooling could implement repeatable patterns, but something like the spec would not need to define up front config-{linux,windows,etc}.json.
—
Reply to this email directly or view it on GitHub.

On Mon, Sep 28, 2015 at 08:30:23AM -0700, Jojy George Varghese wrote:

How about concept of overlaid configurations?

Previous discussion along these lines in #73, #74, and #76.  My
current feeling on this front is that this spec shouldn't talk about
that sort of thing, which we can always punt to an external
preprocessor 1.

On Mon, Sep 28, 2015 at 07:51:04AM -0700, Vincent Batts wrote:

one approach that could work, regardless of protobuf, but could
facilitate this kind of multi-platform accommodation, would be to
have the canonical configuration be config.json and platform
specific be held in config-$keyword.json…

I don't think that works for multi-platform bundles.  For example,
process isn't in the platform-specific Linux section, but process.user
is Linux specific.  If you process (platform-specific user, likely a
platform specific command), platform, root (likely pointing at a
platform-specific directory), and mounts (likely pointing at
platform-specific target paths) into the platform-specific section,
the only things left in config.json are version and hostname.  That's
not much of a win for sharing a cross-platform config ;).
If you're just suggesting it as a way to work around the platform.user
typing, I think protobuf already gives us that.

Thanks for the history Trevor. If there has to be a way to "include" other configs to form a configuration "union", shouldnt there be a spec so that its uniform and unambiguous?
-jojy

On Sep 28, 2015, at 9:15 AM, W. Trevor King<EMAIL_ADDRESS>wrote:
On Mon, Sep 28, 2015 at 08:30:23AM -0700, Jojy George Varghese wrote:

How about concept of overlaid configurations?

Previous discussion along these lines in #73, #74, and #76. My
current feeling on this front is that this spec shouldn't talk about
that sort of thing, which we can always punt to an external
preprocessor 1.
—
Reply to this email directly or view it on GitHub.

On Mon, Sep 28, 2015 at 09:48:43AM -0700, Jojy George Varghese wrote:

If there has to be a way to "include" other configs to form a
configuration "union" shouldnt there be a spec so that its uniform
and unambiguous?

I think this is getting pretty off-topic for “what do we think about
this protobuf approach” ;).  Maybe move this config-generation
discussion to #73 or a mailing list thread?

@conqer I tried this, but when importing, it added to the golang source an import ".", so the resulting source was a cyclic dependency. Would need a more sophisticated structure. Also, would still have the XXX_* extension issue for marshalling structures.

Just as an interested observer, I'd highly recommend going with proto3 syntax, the beta was only 28 days ago but it's pretty highly stable and used in production (and gRPC is really good).
Some things that might help:
go.pedge.io/google-protobuf - takes care of $(which protoc)/../include/google/protobuf files
go.pedge.io/googleapis - takes care of https://github.com/google/googleapis
go get go.pedge.io/tools/protoc-all (https://github.com/peter-edge/go-tools/tree/master/protoc-all) - I'm going to redo this code in a bit, but this is basically how I do any compilation of protos at this point, both for work and personal projects. Takes care of all import paths (I just wrote go.pedge.io/googleapis so I'll add that in soon), and grpc, grpc-gateway, and my own personal go.pedge.io/protolog.
Let me know if I can be of help.

@peter-edge thanks for the pointers.

I did this recently too: https://github.com/peter-edge/go-protoeasy

Further updates on this protobuf. One thing that I am not entirely certain about, is the ability to have variation in the fields of a message.
For example, if there is the ability to introduce new fields in a message type, such that did not conflict with prior versions of the message type. Would decoders of the prior version of the message type decode only the fields known it its version?
Hopefully that question is clear enough.

Yes, that's basically half the point of protobuf, and why a lot of people use it :) Let me see if I can find some docs to explain better.

Actually https://developers.google.com/protocol-buffers/docs/overview explains it a little at the bottom in the "A bit of history" section. Most protocol buffer language implementations have the notion of unrecognized fields, that is fields that given the definition of a message it has, do not have matching tag numbers.
When you edit a protocol buffer message, you only ever add fields, and if you do want to delete fields, the general pattern is you always use an increasing field number for new fields, to avoid ever reusing old field numbers.

Two other things:

I would highly recommend moving to proto3 instead of proto2, especially since you are using golang. Oh I just saw I already mentioned this.
The makefile could be reduced to protoeasy --cpp --python --go --go-import-path github.com/opencontainers/specs/proto proto, other than the C files (need to check that out) https://go.pedge.io/protoeasy

I'm increasingly of the mind that going the route of protobuf is too much a hammer-looking-for-a-nail. I think this needs a step back, to solve the actual problem of implementation independent reference and schema.

I agree.
Sent from my iPhone

On Dec 16, 2015, at 8:53 AM, Vincent Batts<EMAIL_ADDRESS>wrote:
I'm increasingly of the mind that going the route of protobuf is too much a hammer-looking-for-a-nail. I think this needs a step back, to solve the actual problem of implementation independent reference and schema.
—
Reply to this email directly or view it on GitHub.

I tend to agree. Going away from other, simple, choices like json, yml (or heck even xml) feels really odd to me.

Just the minority opinion here:
Protobufs make dev life way nicer once you figure it out. Really the auto-generation of what amount to DTO objects is enough for a huge win - once you start using them, a lot of code that would otherwise not be easy to document or would be inconsistent is suddenly just generated. Compiling etc is very easy once you understand it.

@peter-edge I agree that code-generation is a huge plus. I tried myself and schema much more convenient than json, apart from human-readability of the ready spec itself.

Protobufs have a lot of other wins too:

Forwards/backwards compatibility (most people do not care though)
Serialization size (most people do not care though)
Generated enums
Generated services
https://github.com/grpc/grpc-go
https://github.com/gengo/grpc-gateway (example:
https://github.com/peter-edge/go-openflights/blob/0a97dbbd1609a1483183009e7158594a346211cf/openflights.proto#L108
)
Some teams are working on automatically generated Swagger doc

On Wed, Dec 16, 2015 at 7:30 PM, Alexander Morozov<EMAIL_ADDRESS>
wrote:

@peter-edge https://github.com/peter-edge I agree that code-generation
is a huge plus. I tried myself and schema much more convenient than json,
apart from human-readability of the ready spec itself.
—
Reply to this email directly or view it on GitHub
https://github.com/opencontainers/specs/pull/185#issuecomment-165202013.

Another instructive example: here's the docker volume API as a protobuf service, generated to grpc and grpc-gateway golang code: https://github.com/peter-edge/go-dockervolume/blob/master/dockervolume.proto

Closing this. The specification of the configuration file is a json schema question. Even #276 moves in this direction, by having the golang source being a reference to achieve the desired structures.
We have discussed and investigated json-schema, and perhaps may have future developments related to that. But the protobuf investigation was using protobuf primarily for code generation, and this is not a guarantee that can be entirely relied on.
See also https://github.com/opencontainers/specs/pull/306


Fe homework 10

Metric
Value

alert_status
:white_check_mark: OK

bugs
0

code_smells
10

reliability_rating
A (0 Bugs)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0


Org settings not loading anymore

If I try to open the settings of some org like https://ci.woodpecker-ci.org/orgs/2/settings
I only get:
Error: Please use this "useTabsClient" composition inside a component running "useTabsProvider".
    at D (TextField.vue_vue_type_script_setup_true_lang-B4Ni6bSv.js:1:475)
    at setup (Tab.vue_vue_type_script_setup_true_lang-i5tNtmC3.js:1:1449)
    at oa (index-DBHkDads.js:14:38)
    at _p (index-DBHkDads.js:14:38907)
    at pp (index-DBHkDads.js:14:38690)
    at B (index-DBHkDads.js:14:22544)
    at K (index-DBHkDads.js:14:22436)
    at b (index-DBHkDads.js:14:19361)
    at E (index-DBHkDads.js:14:20776)
    at c (index-DBHkDads.js:14:20120)

Are there any plans to backport/release the fix #4002 before the 3.0.0 release?


There are many calls of vms.list in the script

It would be nice to aim every query to search for specific vm(s) instead of pooling all the time all set of vms.
In addition there is used max=400 keyword which potentially truncate results which we could be interested in.
I suggest at least these two improvements:

When you look for cloned vms, you can use vms.list(query="name=original_vm*")

when you search for specific vm, just use vms.get("vm_name"), for example when you wait until it is removed. Or for verification whether vm exists.

Can you please check if this is resolved by the changes from KKoukiou

@wefixit-AT yes she covered that :+1:
@KKoukiou thanks!

Looks great!
One small optimization: when iterating over the VMs, I'm not sure why we need to wait for each VM to be deleted. Just delete all the relevant ones, then iterate over all of them again and ensure they are all deleted.


HPX does not compile with G++ version prior to 9.3.

Expected Behavior
Compile successfully for any compilers supporting c++17.
Actual Behavior
G++ 8.5 gave me an error error: expected unqualified-id before '[' token
Steps to Reproduce the Problem
Just compile it with G++ 8.5.
Specifications

HPX Version: the master branch ad3ac76e159692355d4715f8b275c0a062b859af
Platform (compiler, OS): G++ 8.5. This should apply to any version prior to g++9.3.

Comment
This is not a fault of HPX, but G++, but this ticket can at least serve as an explanation for future users encountering this error. This is caused by a bug in G++ prior to 9.3. G++ doesn't parse correctly the [[maybe_unused]] attribute for the constructor's first argument. However, HPX uses it in libs/core/executors/include/hpx/executors/service_executors.hpp line 49.
explicit service_executor([[maybe_unused]] hpx::util::io_service_pool* pool) noexcept

Reference: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81429.

We can make this attribute conditional, though.

Do we look into replacing maybe_unused with a #define, possibly something like HPX_UNUSED which falls back to attribute((unused)) for older GCC versions?

We do have HPX_UNUSED, however its use is different from [[maybe_unused]]. So instead of writing:
void foo([[maybe_unused]] int bar) {}

one would have to write:
void foo(int bar) { HPX_UNUSED(bar); }

We should make those changes only singular places when necessary, though.

So everywhere we use [[maybe_unused]] should be replaced with HPX_UNUSED
or we could have another #define for [[maybe_unused]] which falls back to __attribute((unused))
Any comments on what you believe is better?

So everywhere we use [[maybe_unused]] should be replaced with HPX_UNUSED

No! Everywhere possible where we currently use HPX_UNUSED we should use [[maybe_unused]] instead.

or we could have another #define for [[maybe_unused]] which falls back to __attribute((unused))

How many spots would that be used in? If it's just a handful, I think it's not worth the trouble.


chore: add badge and command to install via npm

Added a MIT License badge and a command to install via npm in README.md

Thanks for the PR!


Fir stairs orientation bug / oversight

issue happend with the sevtech: ages pack, did not check if also happends with only traverse mod. bellow what i posted on the sevtech github: https://github.com/Darkosto/SevTech-Ages/issues/1928

Issue / Bug

Fir stairs when placed upside down with the back to the east-player looking to the east, afther placing the upside down they turn upright and make the bottum of the block above see true. only happens with the east placement the other three upside down orientations are fine.
upside down corners are in the wrong orientation.
Expected Behavior

fir stairs behaving like other stairs
Possible Solution

Steps to Reproduce (for bugs)

1.make a platform few blocks above you
2.face east
3,place fir stair upside down

Context

was creating a rim under a roof one side isnt beatiful!!!
Logs

Client/Server Log: https://gist.github.com/Petkip/8572592f745448f91445eef9d066dfb5
Crash Log: no crash

Client Information

Modpack Version: 3.0.6
Java Version: jre-x64\1.8.0_25  and jre1.8.0_161 x64, tried both versions normaly play 161
Launcher Used: twitch

Memory Allocated: 6.144MB

Server/LAN/Single Player: single player
Resourcepack Enabled?: nope
Optifine Installed?: nope

I've looked into this and I don't understand what's wrong. Can I get a screenshot?
Unless I'm doing the wrong thing, this works fine for me

it is the rising sun in the background
using fresh install of sevtech ages.

2 stairs are normal and 2 are upside down, the ones upside down create a see true glitch

if you need more just say.

That is really weird, it works totally fine for me in my dev environment.

I wonder if there's some mod in SevTech causing some sort of weird conflict?

I have the same issue in FTB Revelation 1.8 (Traverse 1.12.1-1.3.1-CustomBuild (1.3.1)).

I added Vanilla stairs, placed exactly the same, for contrast.
I noticed that it only happens to upside-down stairs with the open side to the west. All other orientations seem completely fine. I did not check corner stairs.

I looked at the code and the model file seems to have changed in the meantime, so this may have already been resolved. I noticed the ticket and figured I might respond, but I'm definitely not running the latest version.

Ah, ok. I tried running SevTech and it took 12 minutes to load + 6 to create a world but it did indeed happen there. Maybe try replacing Traverse with this version which I'm about to release to CurseForge. Make sure to try it on a backup.

I loaded it with your new version and its fixed! Good job on the quick coding :P, so they just have to update your mod in their pack.
thanks anyway

Honestly I have no idea when it was fixed, it was probably an accident.


all of these plots were missing ProcessOldVersions in the xml and atts

All of these plots had ProcessOldVersions in their respective .code files but not in their respective atts file because it was not called out in the xml file.
I added   to each xml file and rebuilt the atts.
I was not sure if this was on purpose or not but considering it was also missing from the vector plot (now fixed via 4347) I did the clean up.

Would not found it if you had not picked up the name change in vector plot.