text:
Wot::destory() call won't reset MqttProtocolSettings

Expected behavior
Calling DefaultWot::serverOnly(Config config) after Wot::destory is independent from previous calls of DefaultWot::serverOnly(Config config)
Observed behavior
Calling DefaultWot::serverOnly(Config config) after Wot::destory will create the instance of Wot with config from the first invocation of  DefaultWot::serverOnly(Config config)
Example
public class TestWotRestart {
    private static final Logger logger = LoggerFactory.getLogger(TestWotRestart.class);

    public static Config getConfigV1() {
        String configText = "wot.servient.mqtt.broker = \"tcp://localhost:1883\", wot.servient.servers = [\"city.sane.wot.binding.mqtt.MqttProtocolServer\"]";
        Config wotConfig = ConfigFactory.parseString(configText)
                .withFallback(ConfigFactory.load());
        logger.debug("Expected broker V1: {}",  wotConfig.getString("wot.servient.mqtt.broker"));
        return wotConfig;
    }

    public static Config getConfigV2() {
        String configText = "wot.servient.mqtt.broker = \"tcp://localhost:1884\", wot.servient.servers = [\"city.sane.wot.binding.mqtt.MqttProtocolServer\"]";
        Config wotConfig = ConfigFactory.parseString(configText)
                .withFallback(ConfigFactory.load());
        logger.debug("Expected broker V2: {}", wotConfig.getString("wot.servient.mqtt.broker"));
        return wotConfig;
    }

    public static void main(String[] args) throws WotException, ExecutionException, InterruptedException, IOException {

        Wot wot = DefaultWot.serverOnly(getConfigV1());
        wot.destroy().get();
        wot = DefaultWot.serverOnly(getConfigV2());
        System.in.read();
    }
}

Output:
17:03:55.820 [main] DEBUG ru.mipt.wot.cloud.example.TestWotRestart - Expected broker V1: tcp://localhost:1883
17:03:55.943 [main] DEBUG city.sane.wot.ServientConfig - Servient storing credentials for '[]'
17:03:55.943 [main] INFO city.sane.wot.Servient - Start Servient
17:03:55.946 [main] INFO city.sane.wot.binding.mqtt.MqttProtocolServer - Start MqttServer
17:03:55.953 [ForkJoinPool.commonPool-worker-3] DEBUG city.sane.RefCountResource - First Reference. Create Resource.
17:03:56.065 [ForkJoinPool.commonPool-worker-3] INFO city.sane.wot.binding.mqtt.MqttProtocolSettings - MqttClient trying to connect to broker at 'tcp://localhost:1883' with client ID 'wot20859372974799'
17:03:56.405 [ForkJoinPool.commonPool-worker-3] INFO city.sane.wot.binding.mqtt.MqttProtocolSettings - MqttClient connected to broker at 'tcp://localhost:1883'
17:03:56.405 [main] INFO city.sane.wot.Servient - Stop Servient
17:03:56.406 [main] INFO city.sane.wot.binding.mqtt.MqttProtocolServer - Stop MqttServer
...
17:03:56.431 [main] DEBUG ru.mipt.wot.cloud.example.TestWotRestart - Expected broker V2: tcp://localhost:1884
...
17:03:56.433 [ForkJoinPool.commonPool-worker-3] INFO city.sane.wot.binding.mqtt.MqttProtocolSettings - MqttClient trying to connect to broker at 'tcp://localhost:1883' with client ID 'wot20859843970165'

As you can see, despite different config parameters, the actual configuration is remains unchanged after first call to DefaultWot::serverOnly(Config config).
I suppose, the root cause of this behavior is  interaction between SharedMqttClientProvider and MqttProtocolServer classes. The MqttProtocolServer::stop method https://github.com/sane-city/wot-servient/blob/35f8e899e7f22548fc98aaafd1494f26952aa9ef/wot-servient-binding-mqtt/src/main/java/city/sane/wot/binding/mqtt/MqttProtocolServer.java#L70 won't set value of SharedMqttClientProvider::singleton field to null so it's reinitialization https://github.com/sane-city/wot-servient/blob/35f8e899e7f22548fc98aaafd1494f26952aa9ef/wot-servient-binding-mqtt/src/main/java/city/sane/wot/binding/mqtt/SharedMqttClientProvider.java#L21-L22 inside singleton == null clause will never happen.

Thank you for the issue!
Commit https://github.com/sane-city/wot-servient/commit/24918ef49c3963304a4e8000b1f9fb9b52a15e97 should fix the bug. Can you please verify this bugfix?

Yes, https://github.com/sane-city/wot-servient/commit/24918ef49c3963304a4e8000b1f9fb9b52a15e97 fixes this issue.
Thank you for fixing this so quickly!

authors: Dnnd heikobornholdt

repo: sane-city/wot-servient


text:
default export orElse for Nullable/Undefinable

This change is

:pushpin: Commit b12d63c has been approved by saneyuki

@homu r+

:hourglass: Testing commit b12d63c with merge d52d269...

:sunny: Test successful - status

source: gharchive/pull-request

authors: homu saneyuki

license: mit

license_type: permissive

license_source: bigquery


text:
Data update: Mark CAMC controls as +'ve controls

Update CAMC samples controls, created at the CAMC lighthouse testing lab, to positive controls
Relates to GPL-648
https://github.com/sanger/crawler/issues/110
RT Ticket Number
699190
data => CAMC_positive_controls.txt
Update
samples.control => 1
samples.control_type => 1
sample_metadata.supplier_name => 'Positive control'

samples.control => 1
samples.control_type => 1

source: gharchive/issue

repo: sanger/sequencescape

license: MIT

license_source: github-api


text:
Update sbt-scalafmt to 2.4.5

Updates org.scalameta:sbt-scalafmt from 2.4.3 to 2.4.5.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "sbt-scalafmt" } ]

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch

Superseded by #111.


text:
invisible Unicode characters from dropdown

Describe the bug
With the upgrade to hydrogen-sanity 4 we're all of a sudden getting invisible unicode characters particularly from sanity dropdown fields. E.g.,
 defineField({
      name: 'theme',
      title: 'theme',
      type: 'string',
      options: {
        layout: 'dropdown',
        list: [
          'dark'

This matters because we do a string comparison of the values in certain places and the strings no longer match
To Reproduce

Utilize string dropdown field in sanity
query field and use data in JS
notice string comparisons fail

Expected behavior
Invisible Unicode characters are stripped
Screenshots
If applicable, add screenshots to help explain your problem.
Which versions of Sanity are you using?
"sanity": "^3.24.1",

What operating system are you using?
MacOS Ventura
Which versions of Node.js / npm are you running?
10 and 20 respectively

Hey @dvnrsn, it sounds like you're encountering the invisible characters that the client uses to encode Content Source Maps into your responses.
You can learn more about how this works here in the documentation:
https://www.sanity.io/docs/stega

Beautiful. I was going to suggest my own cleanup function but it looks like this is the answer. Thank you Noah
import {vercelStegaCleanAll} from "@sanity/client/stega"

Another option is to filter those fields in the stega configuration:
https://github.com/sanity-io/client?tab=readme-ov-file#using-visual-editing-with-steganography

authors: dvnrsn nkgentile

repo: sanity-io/hydrogen-sanity


text:
create rutika pr.md

Hi GSSOC Team!
This is PR I raised but is not merged
Could you review and merge it
https://github.com/vishal02527/My-Strength-Shree-Krishna/pull/646/

The PA requested few changes so please complete those
As of now no points can be assigned

authors: AKSHITHA-CHILUKA rutikakengal

repo: sanjay-kv/Open-source-Practice


text:
🛑 Gitea is down

In a7c8c88, Gitea ($GITEA_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Gitea is back up in faef069 after 2 hours, 12 minutes.

repo: sannidhyaroy/Uptime-Ryuu


text:
chore(main): release 1.4.0

:robot: I have created a release beep boop
1.4.0 (2024-09-23)
Features

add blgo site (bebf513)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/sanriodev/blvckleg.dev/releases/tag/v1.4.0 :sunflower:


text:
🛑 JAEGER_URL is down

In 1004af9, JAEGER_URL ($JAEGER_URL) was down:

HTTP code: 502
Response time: 1062 ms

Resolved: JAEGER_URL is back up in 215e9d0.

repo: santomaharaj/upp


text:
🛑 KUBERNETES_DASHBOARD_URL is down

In b2fb3a6, KUBERNETES_DASHBOARD_URL ($KUBERNETES_DASHBOARD_URL) was down:

HTTP code: 502
Response time: 679 ms

Resolved: KUBERNETES_DASHBOARD_URL is back up in ef16556.


text:
Publishing deployment tutorial

@jmmargo is it possible to add this as the final tutorial in this group? https://developers.sap.com/group.ai-core-get-started-basics.html

@LunaticMaestro for your information

repo: sap-tutorials/Tutorials


text:
Providing more context to controlElements

I am using the react-querybuilder for a project i'm working on. I have used the 'controlElements' param as a way of restyling and slightly adjusting the behavior of the query builder. This worked well and I was able to complete 90% of what i wanted.
The 10%

Prevent the user from making the query more than 3 levels deep
Only show the combinator for a group when more than one appeared in a group.

Although both of these features could probably be built into the component, I was able to achieve this by forking the repo here and exposing the rules for the  group, and level which each controlElement appears.
An approach like this might open up the component for more custom behaviors. If you are interested take a look at my forked repo and maybe we can incorporate it into this.
Sam

Hi @SamLoy, it looks like a useful thing to have. Would you mind sending a PR with some tests?

@pavanpodila  Done:
https://github.com/sapientglobalmarkets/react-querybuilder/pull/27/files

authors: SamLoy pavanpodila

repo: sapientglobalmarkets/react-querybuilder


text:
remove packed_rhs

remove packed_rhs

looks good to me. thanks!

authors: lvtuwjl sarah-ek

repo: sarah-ek/gemm


text:
Ler livro sobre WebRTC: revisão de redes

Sobre o livro High Performance Browse Networking:
Revisão de redes: capítulos 1, 2, 3, 4, 5, 6, e 7.
Opcional (para conhecimento pessoal): capítulos 8, 9, 10, 13, 14 e 16.

Lido


text:
How does this catch a fatal crash from Phonegap?

Are you calling sendCrashWithData when you get a Javascript error, or are you detecting a native crash somehow?

The native crash is detected automatically by the Fabric SDK installed on your app. The method described is pretended to send extra data from JS or simulate a crash with information. An example of sending a crash is a catch error from JS that you want to be notified in the moment by Fabric.

Thanks

repo: sarriaroman/FabricPlugin


text:
Criação do Header/Nav/Footer

Terminei de criar o header, o navbar e o footer.
Qualquer mudança no styles posso fazer a modificação.

Natanael, a cor do footer está errada. (Teste de comunicação)

modifiquei a cor (teste de comunicação)


text:
半ドットずれてたのを修正

ゆるして

@844196
:eggplant:
でも、こちら側で同じ修正をしてしまったので、このまま閉じます
ホモはせっかち

repo: sasairc/clangsay

license: WTFPL


text:
Generate store type from vuex-simple

I'm submitting a ...
[ ] bug report
[x] feature request
[x] question about the decisions made in the repository
[x] question about how to use this project

Summary

There are cases where you need Store<StateType> directly.
And there's no way to write it.
When we use vuex-simple we write classes instead of a regular Store, and we do not have this StateType, since it is bundled with other methods, getters, etc.
What do I suggest?
import { State, Module, StateTypeOf } from 'vuex-simple'

class CommentsModule {
  @State()
  public comments: CommentType[] = []
}

class TypedStore {
  @Module()
  public comments = new CommentsModule()
}

type StateType = StateTypeOf<typeof TypedStore>

And later it can be used for Store<StateType>. This way we have the best from the bosth worlds. Native types and no code duplication.
Similar approach: https://github.com/gcanti/io-ts#typescript-integration

That's what I am talking about: https://github.com/wemake-services/wemake-vue-template/blob/feature-typed-vuex/template/client/logic/types.ts

This might be interesting to you: https://github.com/wemake-services/wemake-vue-template/pull/1197


text:
how make chatgpt API can remober last question?

I want to use GPT3TextDavinci003 but it  can not remober last question ， And it supported ?

Did  you use the streams?

yes

蓝宝
@.***

------------------ 原始邮件 ------------------
发件人: "Angel Lambertt @.>;
发送时间: 2023年2月24日(星期五) 晚上10:20
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [sashabaranov/go-gpt3] how make chatgpt API can remober last question? (Issue #85)
Did  you use the streams?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

ChatGPT has context to remember the conversation. API TextDavinci003 is different from ChatGPT at that.

https://github.com/ujjwall-R/GPT3-wrapper-using-memorisation-in-GO.git
have a look into it guys. I build the memorisation feature using mongodb. Basically, the bot remembers the user with particular userid

authors: alambertt hcws nuixdt ujjwall-R


text:
support base64 for embeddings

Is your feature request related to a problem? Please describe.
The OpenAI embeddings API has an option to return the results as base64 encoded float32's. The Python library uses it to retrieve the results: https://github.com/openai/openai-python/blob/main/openai/api_resources/embedding.py#L25
Doing so would result in a small performance improvement - the results can be marshaled directly to float32 instead of being sent over the wire as JSON float (untyped) and converting back to float32.
Describe the solution you'd like
The  embeddings method should include encoding_format=base64 in its call to OpenAI and decode the results.
Describe alternatives you've considered
The python library uses this unless the encoding format is set to anything. I think that's reasonable, and we should match the Python behavior.
Additional context
https://news.ycombinator.com/item?id=37135823

@stillmatic That sounds very convenient. However, the encoding_format is not officially documented. It may be removed or changed in the future.

It's possible. However, the official Python package uses that encoding format, so I think the risk of OpenAI changing it is quite low - they need to support users of the official packages, even if outdated. Backwards compatibility 😉

Here a pull request that implements the base64 support: https://github.com/sashabaranov/go-openai/pull/485

closed in #485 , thanks @henomis !!!

authors: henomis stillmatic vvatanabe

repo: sashabaranov/go-openai


text:
Installing node-sass with electron

I am able to install node-sass with Electron no problem, until it comes to testing the binary.
https://github.com/sass/node-sass/blob/master/scripts/build.js#L206
require('../').renderSync({
  data: 's { a: ss }'
});

Everything seems to execute correctly but binding.renderSync(options) returns false:
https://github.com/sass/node-sass/blob/master/lib/index.js#L406
status = binding.renderSync(options) // status === false

This is unusual because the options.result object seems to be correct and it does not contain an error object:
console.log(options.result);

// {
//    stats: { entry: 'data', start: 1468329066780, includedFiles: [] },
//    css: <Buffer 73 20 7b 0a 20 20 61 3a 20 73 73 3b 20 7d 0a>
// }

Nevertheless the binary test fails because status is false so node-sass throws an error.
I know that this may be outside of the scope of node-sass but hopefully somebody can point me in the right direction as to why the renderSync function might be returning false even though all of the returned options data seems to be correct.

@sedwards2009 I believe that's for windows only. I can get node-sass to work ok generally under Electron in OS X, it's only renderSync that doesn't work.
For example, the following works ok:
sass.render({
  file: 'test.scss',
  outputStyle: 'compressed'
}, (err, result) => console.log(err, result))

@davej can you try running npm test? I am especially interested in lowlevel.js tests

@saper: This bug was related to the fact that I was using the prebuilt version of node-sass with Electron. Basically although Electron uses Node 6, it uses a different version of V8 so the prebuilt binaries don't work.
See here for similar issues: https://github.com/electron/electron/issues/6318 & https://github.com/electron/electron/issues/5851
I'm closing this as it's not really a node-sass issue.

Yeah, using 48 node API identifier while being incompatible is a nasty thing.

authors: davej saper

repo: sass/node-sass


text:
[travis] test jruby

https://github.com/sass/sassc-ruby/issues/119

I'm not sure if this is an acceptable solution.  This is just masking the issue.  It might be better to leave the tests failing rather than to mask it.

ok, but I think that https://github.com/jruby/jruby/issues/5743 is unlikely to be fixed soon

authors: ahorek bolandrm

repo: sass/sassc-ruby


text:
false positive indentation alert for sass map used as mixin argument

scss code:
@include btn-variations((
  primary: (
    background-color: $orange
  ),
  secondary: (
    background-color: $gray-blue
  )
));

sass-lint@1.9.1 is used within Visual Studio Code plugin.
Will show false positive "expected indentation of 4 spaces but found 2" for "primary: (" line. It is expected that line "primary: (" should have 2 spaces correct indentation.
.sass-lint.yml
rules:
  indentation:
    - 2
    - { size: 2 }
  property-sort-order: 0

I'll look into it @sormy there's still a few edge cases left over to sort with indentation.
Just out of interest does it still report this if you use this in your config file
rules:
  indentation:
    - 2
    -
      size: 2
  property-sort-order: 0

Thanks

@DanPurdy that is how my config looks and I still get the error

authors: DanPurdy hotforfeature sormy

repo: sasstools/sass-lint


text:
change docker image version in README to latest

Thanks for contributing to the saucectl project!
A PR well described will help maintainers to quickly review and merge it
Before submitting your PR, please check our contributing
guidelines, applied for this repository. Avoid large PRs, help reviewers by making them as simple
and short as possible.

Description
change the docker image version in README to latest
Motivation and Context

We didn't have to maintain the readme with the latest versions
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation update

Checklist

[x] I have read the contributing document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

ping @alexplischke

repo: saucelabs/testrunner-toolkit


text:
Add issue and pull request template

Description
Issue Template: It helps users report issues and request features more effectively by guiding them to provide essential information. This improves issue quality and community standards on GitHub.
Pull Request Template: This structured format streamlines the contribution process. Contributors can provide necessary details about their changes, related issues, and completed tasks. It promotes organized and well-documented pull requests, enhancing collaboration and GitHub standards.
Screen Shots -

@savitore Kindly consider assigning this task to me for implementation. I greatly appreciate your support
Thank you

assigned @andoriyaprashant

authors: andoriyaprashant savitore


text:
Selection should be retained when exiting map mode

Title is self-explanatory. Is there a technical reason this is difficult?

Hi, didn't think of a usecase, so didn't implement it yet. But it should be easy to implement with a setup argument keep_selection = true.

I think the main use cases would be noticing you accidentally added (or forgot to add) a file. Perhaps you’re more fastidious than I ;)

You're probably right. But it depends. A question: what do you think should be the ideal behaviour after copying a list of files to a different location using :sc? Clear the selection or keep it? The current default behaviour (probably unreleased) is to keep only the files on which the cp command failed and clear the rest (previously it was to clear the selection regardless of the result). But that's difficult to implement for map.xplr, specially for the single map mode.
Also what you think should happen when renaming files? Clear the selection? Keep the renamed files selected (difficult for map.xplr)?
One approach would be to implement the following:
enter = clear the selection, esc = keep the selection, except the moved files.
What do you think?

I think a good global rule that you could apply to both map and :sc is to keep the selection, only removing files that no longer exist (because the command moved them). I can see why your :sc behavior is desirable, but I think consistency is more important.

Makes some sense. Let's try that.

authors: fredcallaway sayanarijit


text:
Adds bitrefill as creating unified bip21 QR codes

Long time bitrefill employee here adding that Bitrefill now creates unified QR codes for the bitcoin payment method. We still have a separate payment method called 'lightning', but plan on phasing that out soon.

@juscamarena Amazing!

authors: juscamarena sbddesign


text:
Pending changes only uses the folder icon

Using Visual Studio 2015. And the pending changes window lists all entries with a folder icon. Which is confusing. Would prefer it if each entry used the associated icon (i.e. same as the normal solution explorer does).

Thanks for reporting this bug, it should now be fixed in the new release!
I am not very proud of that pending changes window :p
It could surely use a proper refactor...

Indeed.. Would be awesome if you could click items in the list to bring up the diff-view as well.
As to the initial bug, its solved in the latest version.

Good suggestion, moved that to #29 !
Will look into it :)

authors: Sacryn sboulema

repo: sboulema/TSVN


text:
Auto generated Bootstrap views

Create a grunt task that can generate the following Bootstrap views, which can be found in the following URL: http://getbootstrap.com/getting-started/#examples
Jumbotron
Cover
Dashboard
Blog
Justified nav
So the idea is that a user can download the framework with our base view and modify that or issue a command in terminal like grunt view:jumbotron and that view would be generated for them in place of main.html

Hey Stephen,
Quick question, how do you want the user to be able to change the bootstrap template? Through ./controllers/home/jumbotron perhaps? Or a button/link on a generic home page, and then it goes to a ‘real’ page? Or maybe I’ll ask, what will trigger a different bootstrap view?

On Jan 3, 2016, at 1:57 PM, Stephen Hutchens notifications@github.com wrote:
Assigned #1 https://github.com/sbrhutchens/khalifa/issues/1 to @akroll1 https://github.com/akroll1.
—
Reply to this email directly or view it on GitHub https://github.com/sbrhutchens/khalifa/issues/1#event-504261559.

repo: sbrhutchens/khalifa


text:
Fix for #2686

The cause of the problem reported in #2686 is that the version clamping that was introduced in #2634 could "downgrade" scala-reflect 2.10.x to scala-reflect 2.9.x ... which doesn't exist of course.
This is a fairly brute force fix for that: if the scalaVersion being clamped to is < 2.10.x then references to scala-reflect and scala-actors artefacts are left unchanged ... this roughly approximates the behaviour you would have seen in this situation prior to #2634 with respect to those two artefacts.
A better fix might work out why such artefacts are being asked for in the first place given that this is a project which specifies 2.9.3 and does nothing other than invoke updateSbtClassifiers ... I don't understand the meaning or purpose of updateSbtClassifiers sufficiently to be able to attempt that unfortunately.

While I do appreciate the effort and detail, I'm afraid this is a symptom of a bigger problem, and I don't like the fix.
Have a look this from the log for updateSbtClassifiers:
[debug] dependency descriptor has been mediated: dependency: org.scala-lang#scala-library;2.10.6 {compile=[default(compile)]} => dependency: org.scala-lang#scala-library;2.9.3 {compile=[default(compile)]}
[debug] dependency descriptor has been mediated: dependency: org.scala-lang#scala-reflect;2.10.6 {compile=[default(compile)]} => dependency: org.scala-lang#scala-reflect;2.9.3 {compile=[default(compile)]}

That can't be right.. right?

I don't disagree. Advice on addressing the deeper problem would be much appreciated.

My vague hunch is that the Scala dependencies for the project and the meta project are mixed together here, and the version clamping, which is only supposed to apply to the project, is being applied across the board. I think this is probably a long-standing problem which has been brought to light by #2634.

We discussed on Gitter, but I'll write out some stuff here for the record Keys.scala describe updateSbtClassifiers as:

Resolves and optionally retrieves classifiers, such as javadocs and sources, for sbt, transitively.

It constructs a dependency graph for sbt itself, and uses Ivy to retrieve "classifier" artifacts (Scaladocs and sources) used by IDEs. IIUC, the dependency graph for sbt is constructed as:
    sbtDependency := {
      val app = appConfiguration.value
      val id = app.provider.id
      val scalaVersion = app.provider.scalaProvider.version
      val binVersion = binaryScalaVersion(scalaVersion)
      val cross = if (id.crossVersioned) CrossVersion.binary else CrossVersion.Disabled
      val base = ModuleID(id.groupID, id.name, sbtVersion.value, crossVersion = cross)
      CrossVersion(scalaVersion, binVersion)(base).copy(crossVersion = CrossVersion.Disabled)
    }

The root of the problem seem to be that the mediator is somehow instructed to use scalaVersion.value (2.9.3; the Scala version for the user's project) instead of the Scala version of the build definition. (2.10.6)

Perhaps we should validate that the X.Y of the scala version matches before replacing it. WDYT?

@dwijnand That's still ad-hoc. We should find why this is happening before we can address it correctly.

If we're able, absolutely. I was only proposing something mildly more robust than pre210.

Closing this in favor of https://github.com/sbt/sbt/pull/2692

authors: dwijnand eed3si9n milessabin

repo: sbt/sbt


text:
add moonbeam networks to hardhat config

Description
This PR adds the network configurations for all Moonbeam-based networks to the hardhat.config.js file.
Additional Information

[x] I have read the contributing docs (if this is your first contribution)
[x] This is not a duplicate of any existing pull request

Thanks for this @eshaben
But we are trying to keep the list small with the main/most used ones. People can always add the chains they want in their builds.

authors: carletex eshaben


text:
Fix #2733: Implement on-demand reflective instantiation.

This commit implements the variant of Proposal #2733 that supports all public constructors.
We introduce a new API in scala.scalajs.reflect which allows to do some amount of run-time reflection, namely, instantiate classes and load module instances given their fully qualified names.
Not all classes are eligible. Only objects and classes that have an ancestor annotated with @EnableReflectiveInstantiation can be found and instantiated that way. Moreover, traits, abstract classes, and classes without any public constructors cannot be found either.

I'm not 100% happy with the InvokableConstructor API because it tends to produce warnings about existential types, e.g.,
val clazz: InstantiatableClass[_] = ???
val ctors = clazz.declaredConstructors

yields:

inferred existential type List[scala.scalajs.reflect.InvokableConstructor[_$6]] forSome { type _$6 }, which cannot be expressed by wildcards, should be enabled by making the implicit value scala.language.existentials visible. [...]

but
val ctors: List[InvokableConstructor[_]] = clazz.declaredConstructors

does not have that issue.
Maybe I'll try with a type member in InvokableConstructor instead.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3628/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4789/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3629/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4790/
Test FAILed.

Aargh! GCC is "dead-code"-eliminating calls to registerLoaduleModuleClass :sob:

This proposal looks really promising IMO :+1:

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3630/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4791/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3631/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4792/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3632/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4793/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3633/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4794/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3634/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4795/
Test PASSed.

Review by @gzm0
I'm considering simply removing the type parameters to InstantiatableClass, InvokableConstructor and LoadableModuleClass. They're more trouble than they're worth. WDYT?

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3635/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4797/
Test FAILed.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3636/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4798/
Test FAILed.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3638/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4800/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3639/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4801/
Test PASSed.

Updated.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3647/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4810/
Test PASSed.

authors: andreaTP scala-jenkins sjrd

repo: scala-js/scala-js


text:
Resolution of scalajs:* files fails if the containing project aggregates another scalaJS project

When a project aggregates other projects, it runs the command sequentially on each of the aggregated projects and then finally on the specified project. However, in this mode, it adds a tab character to the start of each project's individual output.  This means that the output for fastLinkJSOutput and fullLinkJSOutput have a tab character in front and the plugin doesn't trim it, so path resolution fails.
PR incoming.

If anyone else runs into this before this is merged, you can disable aggregation for this particular command in your project via:
Compile / fastLinkJSOutput / aggregate := false
and
Compile / fullLinkJSOutput / aggregate := false

repo: scala-js/vite-plugin-scalajs


text:
regression: 2.12 and 2.13 builds consistently failing

this started sometime while I as AWOL for a couple weeks for Scala Days, eng meeting, vacation

new 2.12.x test run: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1597/consoleFull

I've seen multiple 2.12 and 2.13 jobs get stuck running ssl-config's test suite, not sure when that started :-\

current blocker for this is https://github.com/scala/community-builds/issues/560 since once ssl-config hangs, other projects can't run

2.13 is green now

as is 2.12

repo: scala/community-builds


text:
Backport fix #19536 of Scala.js Dynamic

Backport cherry-pick, as discussed in #19536

All right I'll just take responsibility for merging this one into 3.3.x. It's an obvious, straightforward fix.

authors: OndrejSpanel sjrd


text:
[Feature] Chatbot for Signup form

Is your feature request related to a problem? Please describe.
A chatbot in place of Sign up forms are more interactive. Providing clients the way to register in interactive manner rather than with forms
Describe the solution you'd like
API and storage at backend. We can use a table storing which forms are required by client.
Describe alternatives you've considered
Api from the Google form or any other agent
Additional context

Hello, I would like to suggest to use GraphQL and SQLALchemy for API and storage at the backend.  GraphQL is better than REST and has many other advantages.  We can use the Graphene-Python library with supports building of GraphQL and storage with the use of SQLAlchemy.
Would like to know your feedback on this.

@Mishrasubha Yes looks fine, you can start working on a small design like only username and email address and show how chatbot can covert a form to interactive manner.

Okay then I will start working on it

authors: Mishrasubha satyammittal


text:
Update scalajs-bundler to version 0.10.0

It now asserts the existence of the bundle file so the JS packaging code
had to be reworked a bit.

Tested locally, but somewhat experimental due to a lot of moving parts.

Just tested locally and it seems the site works well once generated. I noticed a couple config bugs in our travis setup, ;compile;test was causing us to only run sbt 😅 thankfully the scripted tests were at least running. We were also publishing SNAPSHOT for this PR

Thanks for the CI and formatting fixes.

authors: jonas olafurpg

repo: scalameta/metadoc


text:
Documentation Request: Change Notes

I see munit has moved to 1.0.0 (M anyway).  That's a bump from the pre-1 versions.
What I don't see (at least easily) is any reference to what has changed or been added, ie a "New" section in the documentation.
That would be nice to have to understand what additions are coming in the latest version.

1.0.0 has been released!
There are release notes in the blog post:
https://scalameta.org/munit/blog/2024/05/22/release-1.0.0.html

authors: gzoller valencik

repo: scalameta/munit


text:
Skipped tests reported as passing

Hello, I'm using assume to skip tests dynamically based on what's described in the documentation here: https://scalameta.org/munit/docs/filtering.html#ignore-single-test-case-based-on-a-dynamic-conditions, however the tests that fail the assertion are reported as passing (even though nothing is run). I'm not sure if I've misunderstood the documentation, from reading through some issues it looks like sometimes the final test report includes a "skipped" and sometimes not. I would like it to report as "n tests skipped", or at least ignore them completely but not report them as passing. I use the IntelliJ test API but it also happens when running with sbt.
The test itself is here but if I simply run assume(false) in either test(...) or in beforeEach, it doesn't run the test but reports it as passed.
If I manually use test("description".ignore) then it is reported as skipped, both on IntelliJ and SBT.

Thanks for reporting! I think we should show is as ignored, although I am not sure if that was the initial intention.
You can also ignore a test based on a TAG and that shows up correctly. We have some examples in scalameta/metals repository around here https://github.com/scalameta/metals/blob/main/tests/cross/src/main/scala/tests/BasePCSuite.scala#L159

Thanks for the help! I couldn't quite figure out how to set a tag dynamically, is that possible? If the test gets skipped is something that is determined after the fixture beforeEach is called. So I need to have instantiated the test already, but not called any asserts. It looks like:
class Test extends munit.FunSuite {
  val graph: Fixture[TestGraph] = new Fixture[TestGraph]("Graph") {
    override def beforeEach(context: BeforeEach): Unit = <... initialize graph ... >
  }

  test(testdir) {
     val g = graph()
     // if g.skip contains some property, then I need to skip the test
  }

I'm not quite sure how to get the tags to be set after I've already entered test, which is the same problem I had with using <testname>.ignore. Is there a workaround possible?
Thank you!

Maybe, you could just use test transforms, but not sure if it will be possible to mark anything as ignored there.
The best option for you is probably what you tried before https://scalameta.org/munit/docs/filtering.html#ignore-entire-test-suite but you will lose the information about it being ignored.

Ok, I will do some refactoring, thanks for the help!

authors: aherlihy tgodzik


text:
6 tests in Repl and NewRepl fail

Using the current HEAD of the 2.11.8 branch (https://github.com/scalameta/paradise/commit/4e3b7a6a48ab298019d123306549dffb1820de35) I'm seeing:
[info] Assorted:
[info] - nested
[info] - local
[info] Definition:
[info] - macro annotations get the MACRO flag
[info] Scopes:
[info] - toplevel
[info] - member
[info] - local
[info] InteropCaseSynthesis:
[info] - case module synthesis for identity
[info] - case module synthesis for placebo
[info] Argumentative:
[info] - combo
[info] KasePlaceboObject:
[info] - combo
[info] Parameters:
[info] - combo
[info] Acyclic:
[info] - A
[info] - B
[info] - C
[info] ScaladocSuite:
[info] - Simulacrum
[info] KaseClass:
[info] - combo
[info] Issue09:
[info] - compiles
[info] Multiple:
[info] - multiple
[info] PlaceboParameters:
[info] - combo
[info] NewRepl:
[info] - new macro annotations expand with scala.meta (ILoop) *** FAILED ***
[info]   "scala> [import scala.meta._
[info]   import scala.meta._
[info]
[info]   scala> class main(x: Int) extends scala.annotation.StaticAnnotation {
[info]        |   inline def apply(defn: Any): Any = meta { defn }
[info]        | }
[info]   defined class main
[info]   defined object main$inline
[info]
[info]   scala> ]@main(42) class C
[info]   de..." did not equal "scala> [import scala.meta._
[info]   import scala.meta._
[info]
[info]   scala> class main(x: Int) extends scala.annotation.StaticAnnotation {
[info]     inline def apply(defn: Any): Any = meta { defn }
[info]   }
[info]   defined class main
[info]   defined object main$inline
[info]
[info]   scala> ]@main(42) class C
[info]   de..." (Repl.scala:25)
[info] - new macro annotations expand with scala.meta (ReplGlobal) *** FAILED ***
[info]   "...import scala.meta._
[info]   [import scala.meta._
[info]
[info]   scala> class main(x: Int) extends scala.annotation.StaticAnnotation {
[info]     inline def apply(defn: Any): Any = meta { defn }
[info]   }
[info]   defined class main
[info]   defined object main$inline
[info]
[info]   scala> @main(42) class C
[info]   ]defined class C" did not equal "...import scala.meta._
[info]   [import scala.meta._
[info]
[info]   scala> class main(x: Int) extends scala.annotation.StaticAnnotation {
[info]     inline def apply(defn: Any): Any = meta { defn }
[info]   }
[info]   defined class main
[info]   defined object main$inline
[info]
[info]   scala> @main(42) class C
[info]   ]defined class C" (Repl.scala:25)
[info] PlaceboClass:
[info] - combo
[info] ExpansionTests:
[info] - Nested macro should expand with identity
[info] - Nested macro of the same name should expand
[info] - Nested macro should expand with different macros
[info] - Verify expansion order
[info] - Nested macro should expand with inner identity macro
[info] - Nested macro should expand with outer identity macro
[info] - Placebo after expandee should compile and work
[info] - Placebo before expandee should compile and work
[info] - Multiple expandees of same kinds with others in between should expand
[info] - Multiple expandees of similar kinds should expand in the correct order
[info] - Identity expandee followed by regular expandee should expand correctly
[info] - Regular expandee followed by Identity expandee should expand correctly
[info] - Placebo in package doesnt accidentally get removed if second
[info] - Placebo in package doesnt accidentally get removed if first
[info] KaseObject:
[info] - combo
[info] KaseIdentityObject:
[info] - combo
[info] NameResolution:
[info] - verified at compile-time
[info] KasePlaceboClass:
[info] - combo
[info] TypeArgs:
[info] - macro annotations with type args expand
[info] PackageObject:
[info] - package object members
[info] - package object itself
[info] KaseThorough:
[info] - construction
[info] - deconstruction
[info] - copy
[info] - product
[info] - equality
[info] Issue10:
[info] - compiles
[info] Repl:
[info] - precompiled macros expand (ILoop) *** FAILED ***
[info]   "scala> [@thingy class Thingy
[info]   defined class Thingy
[info]   defined object Thingy
[info]
[info]   scala> ]@thingy class NonThi..." did not equal "scala> [@thingy class Thingy
[info]   defined class Thingy
[info]   defined object Thingy
[info]
[info]   scala> ]@thingy class NonThi..." (Repl.scala:3)
[info] - precompiled macros expand (ReplGlobal) *** FAILED ***
[info]   "...thingy class Thingy
[info]   [defined class Thingy
[info]   defined object Thingy
[info]
[info]   scala> @thingy class NonThingy
[info]   ]defined class Thingy..." did not equal "...thingy class Thingy
[info]   [defined class Thingy
[info]   defined object Thingy
[info]
[info]   scala> @thingy class NonThingy
[info]   ]defined class Thingy..." (Repl.scala:3)
[info] - ad-hoc macros expand (ILoop) *** FAILED ***
[info]   "scala> [import scala.language.experimental.macros
[info]   import scala.language.experimental.macros
[info]
[info]   scala> import scala.reflect.macros.whitebox.Context
[info]   import scala.reflect.macros.whitebox.Context
[info]
[info]   scala> import scala.annotation.StaticAnnotation
[info]   import scala.annotation.StaticAnnotation
[info]
[info]   scala>
[info]
[info]   scala> object thingyAdhocMacro {
[info]        |   def impl(c: Context)(annottees: c.Expr[Any]*): c.Expr[Any] = {
[info]        |     import c.universe._
[info]        |     val toEmit = c.Expr(q"class Thingy(i: Int) { def stuff = println(i) }; object Thingy { def apply(x: Int) = new Thingy(x) }")
[info]        |     annottees.map(_.tree) match {
[info]        |       case Nil => {
[info]        |         c.abort(c.enclosingPosition, "No test target")
[info]        |       }
[info]        |       case (classDeclaration: ClassDef) :: Nil => {
[info]        |         // println("No companion provided")
[info]        |         toEmit
[info]        |       }
[info]        |       case (classDeclaration: ClassDef) :: (companionDeclaration: ModuleDef) :: Nil => {
[info]        |         // println("Companion provided")
[info]        |         toEmit
[info]        |       }
[info]        |       case _ => c.abort(c.enclosingPosition, "Invalid test target")
[info]        |     }
[info]        |   }
[info]        | }
[info]   defined object thingyAdhocMacro
[info]
[info]   scala>
[info]
[info]   scala> class thingyAdhoc extends StaticAnnotation {
[info]        |   def macroTransform(annottees: Any*): Any = macro thingyAdhocMacro.impl
[info]        | }
[info]   defined class thingyAdhoc
[info]
[info]   scala>
[info]
[info]   scala> @thingyAdhoc class Thingy
[info]   defined class Thingy
[info]   defined object Thingy
[info]
[info]   scala> ]@thingyAdhoc class N..." did not equal "scala> [import scala.language.experimental.macros
[info]   import scala.language.experimental.macros
[info]
[info]   scala> import scala.reflect.macros.whitebox.Context
[info]   import scala.reflect.macros.whitebox.Context
[info]
[info]   scala> import scala.annotation.StaticAnnotation
[info]   import scala.annotation.StaticAnnotation
[info]
[info]   scala>
[info]
[info]   scala> object thingyAdhocMacro {
[info]     def impl(c: Context)(annottees: c.Expr[Any]*): c.Expr[Any] = {
[info]       import c.universe._
[info]       val toEmit = c.Expr(q"class Thingy(i: Int) { def stuff = println(i) }; object Thingy { def apply(x: Int) = new Thingy(x) }")
[info]       annottees.map(_.tree) match {
[info]         case Nil => {
[info]           c.abort(c.enclosingPosition, "No test target")
[info]         }
[info]         case (classDeclaration: ClassDef) :: Nil => {
[info]           // println("No companion provided")
[info]           toEmit
[info]         }
[info]         case (classDeclaration: ClassDef) :: (companionDeclaration: ModuleDef) :: Nil => {
[info]           // println("Companion provided")
[info]           toEmit
[info]         }
[info]         case _ => c.abort(c.enclosingPosition, "Invalid test target")
[info]       }
[info]     }
[info]   }
[info]   defined object thingyAdhocMacro
[info]
[info]   scala>
[info]
[info]   scala> class thingyAdhoc extends StaticAnnotation {
[info]     def macroTransform(annottees: Any*): Any = macro thingyAdhocMacro.impl
[info]   }
[info]   defined class thingyAdhoc
[info]
[info]   scala>
[info]
[info]   scala> @thingyAdhoc class Thingy
[info]   defined class Thingy
[info]   defined object Thingy
[info]
[info]   scala> ]@thingyAdhoc class N..." (Repl.scala:18)
[info] - ad-hoc macros expand (ReplGlobal) *** FAILED ***
[info]   "...experimental.macros
[info]   [import scala.language.experimental.macros
[info]
[info]   scala> import scala.reflect.macros.whitebox.Context
[info]   import scala.reflect.macros.whitebox.Context
[info]
[info]   scala> import scala.annotation.StaticAnnotation
[info]   import scala.annotation.StaticAnnotation
[info]
[info]   scala>
[info]
[info]   scala> object thingyAdhocMacro {
[info]     def impl(c: Context)(annottees: c.Expr[Any]*): c.Expr[Any] = {
[info]       import c.universe._
[info]       val toEmit = c.Expr(q"class Thingy(i: Int) { def stuff = println(i) }; object Thingy { def apply(x: Int) = new Thingy(x) }")
[info]       annottees.map(_.tree) match {
[info]         case Nil => {
[info]           c.abort(c.enclosingPosition, "No test target")
[info]         }
[info]         case (classDeclaration: ClassDef) :: Nil => {
[info]           // println("No companion provided")
[info]           toEmit
[info]         }
[info]         case (classDeclaration: ClassDef) :: (companionDeclaration: ModuleDef) :: Nil => {
[info]           // println("Companion provided")
[info]           toEmit
[info]         }
[info]         case _ => c.abort(c.enclosingPosition, "Invalid test target")
[info]       }
[info]     }
[info]   }
[info]   defined object thingyAdhocMacro
[info]
[info]   scala>
[info]
[info]   scala> class thingyAdhoc extends StaticAnnotation {
[info]     def macroTransform(annottees: Any*): Any = macro thingyAdhocMacro.impl
[info]   }
[info]   defined class thingyAdhoc
[info]
[info]   scala>
[info]
[info]   scala> @thingyAdhoc class Thingy
[info]   defined class Thingy
[info]   defined object Thingy
[info]
[info]   scala> @thingyAdhoc class NonThingy
[info]   ]defined class Thingy..." did not equal "...experimental.macros
[info]   [import scala.language.experimental.macros
[info]
[info]   scala> import scala.reflect.macros.whitebox.Context
[info]   import scala.reflect.macros.whitebox.Context
[info]
[info]   scala> import scala.annotation.StaticAnnotation
[info]   import scala.annotation.StaticAnnotation
[info]
[info]   scala>
[info]
[info]   scala> object thingyAdhocMacro {
[info]     def impl(c: Context)(annottees: c.Expr[Any]*): c.Expr[Any] = {
[info]       import c.universe._
[info]       val toEmit = c.Expr(q"class Thingy(i: Int) { def stuff = println(i) }; object Thingy { def apply(x: Int) = new Thingy(x) }")
[info]       annottees.map(_.tree) match {
[info]         case Nil => {
[info]           c.abort(c.enclosingPosition, "No test target")
[info]         }
[info]         case (classDeclaration: ClassDef) :: Nil => {
[info]           // println("No companion provided")
[info]           toEmit
[info]         }
[info]         case (classDeclaration: ClassDef) :: (companionDeclaration: ModuleDef) :: Nil => {
[info]           // println("Companion provided")
[info]           toEmit
[info]         }
[info]         case _ => c.abort(c.enclosingPosition, "Invalid test target")
[info]       }
[info]     }
[info]   }
[info]   defined object thingyAdhocMacro
[info]
[info]   scala>
[info]
[info]   scala> class thingyAdhoc extends StaticAnnotation {
[info]     def macroTransform(annottees: Any*): Any = macro thingyAdhocMacro.impl
[info]   }
[info]   defined class thingyAdhoc
[info]
[info]   scala>
[info]
[info]   scala> @thingyAdhoc class Thingy
[info]   defined class Thingy
[info]   defined object Thingy
[info]
[info]   scala> @thingyAdhoc class NonThingy
[info]   ]defined class Thingy..." (Repl.scala:18)
[info] PlaceboAssorted:
[info] - nested
[info] - local
[info] Transform:
[info] - simple transform
[info] KaseIdentityClass:
[info] - combo
[info] PlaceboClass:
[info] - combo
[info] Recursive:
[info] - combo
[info] ScalaTest
[info] Run completed in 13 seconds, 22 milliseconds.
[info] Total number of tests run: 59
[info] Suites: completed 30, aborted 0
[info] Tests: succeeded 53, failed 6, canceled 0, ignored 0, pending 0
[info] *** 6 TESTS FAILED ***
[error] Failed: Total 59, Failed 6, Errors 0, Passed 53
[error] Failed tests:
[error] 	NewRepl
[error] 	Repl
[error] (tests/test:test) sbt.TestsFailedException: Tests unsuccessful
[error] Total time: 55 s, completed 15-Sep-2016 09:12:29

This is blocking me from validating similar build improvements as https://github.com/scalameta/scalameta/pull/474.

Cannot reproduce. Checked on fresh git clone https://github.com/scalameta/paradise.git; cd paradise; sbt test.

authors: Dveim dwijnand

repo: scalameta/paradise


text:
feat(use-hooks): add useBreakpoint hook

Adds a useBreakpoint hook so we can use our Tailwind breakpoints in a consistent way that matches how we use the in CSS.
Fixes DOC-1338 😱 🧟
Also fixed a bug with the API Client sidebar while I was in there (it used to be possible to do this if you opened the sidebar with a viewport between 780px and 800px)

Fixes DOC-1338 😱

Not a big fan of this one! Responsiveness in JS is a bad habit. What if we just removed it completely?

Yeah I mean I don't love it either but we use it in a bunch of places already and this at least keeps it aligned with our tailwind breakpoints.
There are certain things we can only do with media queries in JS like mounting and unmounting components (otherwise sometimes we might have big hidden DOM trees still being managed by Vue).
It's also worth note that these JS media queries use MatchMedia under the hood which should have similar performance to CSS media queries (or rather it's not like it's polling the viewport size or something)
What do you think if we add a blurb in the readme and on the JSDoc reminding folks to use CSS if at all possible?

repo: scalar/scalar


text:
FreeSpec: test scope is wrong?

When I use scalatest 3.0.4,
class Test extends FreeSpec {

 "test 1" - {
   println("test 1")

   "test 1-1" in {
     println("test 1-1")
   }
 }

 "test 2" - {
   println("test 2")

   "test 2-2" in {
     println("test 2-2")
   }
 }
}

then I got
org.jetbrains.plugins.scala.testingSupport.scalaTest.ScalaTestRunner -s me.ooon.ia.Test -testName "test 2 test 2-2" -C org.jetbrains.plugins.scala.testingSupport.scalaTest.ScalaTestReporter -showProgressMessages true
test 1
test 2
test 2-2

The command is ScalaTestRunner -s me.ooon.ia.Test -testName "test 2 test 2-2" ,Why does it print "test1"?

I think that's because tests are registered using in (you can check the implementation) and everything on the other levels (in your example println("test 1") is not considered as a test, just branch.
That's why when runner filters out tests not matching -testName which you provided it still executes executes println("test 1-1") as it's not considered a test.

@rsekulski You are right，thanks

authors: rsekulski zhaihao

repo: scalatest/scalatest


text:
Return TGI errors

Return TGI errors to upstream

Can you double check your linter settings to see if they match what's in this repo?

Can you double check your linter settings to see if they match what's in this repo?

fixed

Can you double check your linter settings to see if they match what's in this repo?

i'm not sure why formatting changed, i'm using the same .black.toml file

repo: scaleapi/llm-engine


text:
Toast position not calculated properly when scroll offset

For some reason this started happening, I hadn't noticed before I updated to latest. Whenever I am on a tableview or scrollview and have scrolled down any amount of offset, when I show a toast it gets calculated as if the scroll offset were 0, so it appears way above, most of the time off-screen.  To get around this I have to start defining my toasts as self.navigationController?.view.makeToast("some"). This is an ugly workaround and I'm afraid it won't work as a generic solution to my global notifications solution. Can something be done to fix this?

Toast can be presented inside any view in the hierarchy. It is completely agnostic to the superview and it has always worked that way. If you present it in a UIScrollView or one of it's subclasses (like UITableView or UICollectionView) it's going to scroll when the content scrolls just like any other view added to a scroll view. If you don't want your toast to scroll, don't present it in a scroll view. That's your responsibility, not the library's.
FWIW, I've always disliked how the stock UITableViewController is configured by default such that self.view === self.tableView. There are many valid reasons when you want content to appear on top of a scroll view without scrolling. For this reason, I create my own TableViewController subclasses in my personal projects that add a UITableView instance as a subview of self.view. Same for UICollectionViewController. With this setup, presenting in self.view would work as you would like. You should decide what's right for you project.

repo: scalessec/Toast-Swift


text:
Failed to start Network Name Resolution (Apache Virtual Hosts not working)

(Extending #34 that was closed because the main problem was solved)
After a fresh install and a full system upgrade, the next boot will throw the following error:

[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[  OK  ] Stopped Network Name Resolution.
Starting Network Name Resolution...
[  OK  ] Started Serial Getty on ttyS0.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started SCW generate machine id.
Starting Hostname Service...
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[  OK  ] Stopped Network Name Resolution.
Starting Network Name Resolution...
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[  OK  ] Stopped Network Name Resolution.
Starting Network Name Resolution...
[  OK  ] Started Hostname Service.
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[  OK  ] Stopped Network Name Resolution.
Starting Network Name Resolution...
[  OK  ] Started SCW fetch ssh keys from metadata.
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[  OK  ] Stopped Network Name Resolution.
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[  OK  ] Started One-Shot Network Time Service.

This renders apache virtual hosts unusable (always pointing to Main DocumentRoot). I've already made sure it's not a configuration problem.

systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/etc/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Sat 2016-08-06 15:32:19 UTC; 17s ago
Docs: man:systemd-resolved.service(8)
Process: 4973 ExecStart=/usr/lib/systemd/systemd-resolved (code=exited, status=1/FAILURE)
Main PID: 4973 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
Aug 06 15:32:19 scw-28a908 systemd[1]: Failed to start Network Name Resolution.
Aug 06 15:32:19 scw-28a908 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 06 15:32:19 scw-28a908 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 06 15:32:19 scw-28a908 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 06 15:32:19 scw-28a908 systemd[1]: Stopped Network Name Resolution.
Aug 06 15:32:19 scw-28a908 systemd[1]: systemd-resolved.service: Start request repeated too quickly.
Aug 06 15:32:19 scw-28a908 systemd[1]: Failed to start Network Name Resolution.
Aug 06 15:32:19 scw-28a908 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 06 15:32:19 scw-28a908 systemd[1]: systemd-resolved.service: Failed with result 'start-limit-hit'.

And:

journalctl -xe
Aug 06 15:32:18 scw-28a908 systemd[1]: Starting Network Name Resolution...
-- Subject: Unit systemd-resolved.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-resolved.service has begun starting up.
Aug 06 15:32:19 scw-28a908 systemd-resolved[4968]: Failed to increase capabilities: Operation not permitted
Aug 06 15:32:19 scw-28a908 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 06 15:32:19 scw-28a908 systemd[1]: Failed to start Network Name Resolution.
-- Subject: Unit systemd-resolved.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-resolved.service has failed.
--
-- The result is failed.
Aug 06 15:32:19 scw-28a908 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 06 15:32:19 scw-28a908 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 06 15:32:19 scw-28a908 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 06 15:32:19 scw-28a908 systemd[1]: Stopped Network Name Resolution.
-- Subject: Unit systemd-resolved.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-resolved.service has finished shutting down.
Aug 06 15:32:19 scw-28a908 systemd[1]: Starting Network Name Resolution...
-- Subject: Unit systemd-resolved.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-resolved.service has begun starting up.
Aug 06 15:32:19 scw-28a908 systemd-resolved[4973]: Failed to increase capabilities: Operation not permitted
Aug 06 15:32:19 scw-28a908 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
Aug 06 15:32:19 scw-28a908 systemd[1]: Failed to start Network Name Resolution.
-- Subject: Unit systemd-resolved.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-resolved.service has failed.
--
-- The result is failed.
Aug 06 15:32:19 scw-28a908 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 06 15:32:19 scw-28a908 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Aug 06 15:32:19 scw-28a908 systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
Aug 06 15:32:19 scw-28a908 systemd[1]: Stopped Network Name Resolution.
-- Subject: Unit systemd-resolved.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-resolved.service has finished shutting down.
Aug 06 15:32:19 scw-28a908 systemd[1]: systemd-resolved.service: Start request repeated too quickly.
Aug 06 15:32:19 scw-28a908 systemd[1]: Failed to start Network Name Resolution.
-- Subject: Unit systemd-resolved.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-resolved.service has failed.
--
-- The result is failed.
Aug 06 15:32:19 scw-28a908 systemd[1]: systemd-resolved.service: Unit entered failed state.
Aug 06 15:32:19 scw-28a908 systemd[1]: systemd-resolved.service: Failed with result 'start-limit-hit'.
Aug 06 15:35:58 scw-28a908 sshd[4981]: Received disconnect from 121.18.238.22 port 38399:11:  [preauth]
Aug 06 15:35:58 scw-28a908 sshd[4981]: Disconnected from 121.18.238.22 port 38399 [preauth]
Aug 06 15:36:56 scw-28a908 sshd[4985]: Received disconnect from 221.194.44.223 port 57688:11:  [preauth]
Aug 06 15:36:56 scw-28a908 sshd[4985]: Disconnected from 221.194.44.223 port 57688 [preauth]

Systemd 231 fixes the error on a clean install https://github.com/systemd/systemd/issues/3484

Not working yet, after resuming the server the errors are back.
The image is outdated and needs to be updated. Hope it can be soon.

Do the latest 4.4.8, 4.5.7 std kernels have SECCOMP enabled?

The unit file was not updated, so it must be done manually: https://github.com/systemd/systemd/issues/3484#issuecomment-239595447
Now it is really working, well, at least no more errors are shown.

This would not be an issue if a proper systemd unti drop-in was used. Overwriting or overriding whole service files is not an intended vendor behavior.
/etc/systemd/system/systemd-resolved.service.d/start-after-nm-wait-online.conf
[Unit]
After=NetworkManger-wait-online.service

That seems a better approach. Thanks!

Hm. Commit was merged, but I still meet the error. What do I have to do to survive system update? #41

You will need to manually refactior these files prior to Syu. https://archlinuxarm.org/forum/viewtopic.php?f=60&t=10650&start=10#p52959

Thx!
Will this get fixed permanently?

I release a new version of Arch Linux image, can you tell me if you have again this issue ?

Thanks @QuentinPerez It'll work for sure, waiting for stock to test it.

i am facing the same error now in my ubuntu18.04
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[ OK ] Stopped Network Name Resolution
Please help me to resolve this issue.

@nayanhalder  have you resolved the issue??

authors: ChazyTheBest QuentinPerez WarheadsSE YasirNiazai aspcartman nayanhalder

repo: scaleway/image-archlinux


text:
Ft/policy auth

This sends a RequestContext to vault with an authentication request so that Vault can evaluate the request against any policies attached to a user (if the request is from a user).
The RequestContext requires information from the request (such as the locationConstraint on a create bucket request) so some refactoring was required to move the parsing of the locationConstraint to the routes.  Most of the changes are modifying the units tests to handle this.
This is dependent on:

Arsenal: https://github.com/scality/Arsenal/pull/109
VaultClient: https://github.com/scality/vaultclient/pull/91
Vault: https://github.com/scality/Vault/pull/415

@ironman-machine check it
SCALITY_VAULT_BRANCH=ft/policyAuth

Hello @LaurenSpiegel,
Starting end to end procedure using the following payload:
{"SCALITY_VAULT_BRANCH":"ft/policyAuth","DEFAULT_BRANCH":"master","SCALITY_S3_BRANCH":"ft/policyAuth"}
Please follow http://ci.ironmann.io/gh/scality/Integration/1981 for circle status.

@ironman-machine check it without accounts instead of users
SCALITY_VAULT_BRANCH=ft/policyAuth
SCALITY_INTEGRATION_BRANCH=ft/useAccountsForTests

Hello @LaurenSpiegel,
Starting end to end procedure using the following payload:
{"SCALITY_VAULT_BRANCH":"ft/policyAuth","SCALITY_INTEGRATION_BRANCH":"ft/useAccountsForTests","DEFAULT_BRANCH":"master","SCALITY_S3_BRANCH":"ft/policyAuth"}
Please follow http://ci.ironmann.io/gh/scality/Integration/1986 for circle status.

A little comment, LGTM :+1: otherwise :)

@ironman-machine are any of the refactors not to your liking?
SCALITY_VAULT_BRANCH=ft/policyAuth
SCALITY_INTEGRATION_BRANCH=ft/useAccountsForTests

Hello @LaurenSpiegel,
Starting end to end procedure using the following payload:
{"SCALITY_VAULT_BRANCH":"ft/policyAuth","SCALITY_INTEGRATION_BRANCH":"ft/useAccountsForTests","DEFAULT_BRANCH":"master","SCALITY_S3_BRANCH":"ft/policyAuth"}
Please follow http://ci.ironmann.io/gh/scality/Integration/2008 for circle status.

👍

authors: LaurenSpiegel alexandre-merle ironman-machine rahulreddy


text:
[Feature Request]: Full-width option for tabs

Requirements before reporting

[X] No duplicated issue reported
[X] I have checked the latest version if the feature exist there

Type of feature request
Design
What is your feature request?
Full-width option for all tabs variants (inline, folder, navigation).
Background
I am currently developing a tablet front-end and require tabs for navigation purposes. However, the existing tabs are too small, especially when users need to press them. Additionally, integrating larger tabs would enhance the aesthetic appeal of the page, making them a more prominent and integral component of the user interface.
Idea
I have tried setting the width to 100%, but this results in a button flickering on the right side of the screen (the button that enables you to scroll through the tabs if the width exceeds the parent width).
Goals and objectives
Something that looks like the following (Angular Material modified with Tegel theme):

Timeline
No response
Resources
https://material.angular.io/components/tabs/examples#tab-group-stretched
Contact information
patrick.groot.koerkamp@scania.com

I think should be marked as a design request rather than a feature one, correct me if wrong @theJohnnyMe

repo: scania-digital-design-system/tegel


text:
How to run reverse_image_search?

I am not sure how to run the reverse image search example and I am very interested in it!
I noticed a few things missing in the example and I tried to fix it but did not succeed in understanding how to actually run it.

parser --> readers.
I see some of the video paths are hardcoded. ahewhope.m4v (i downloaded a path myself and converted it take it as input)
faster_rcnn_coco.toml missing. ( i downloaded and succeeded in ensuring it takes in)
Missing faiss installation. (I was able to install it and resolve the dependency in this example)
Query image I added a screenshot of from the video. I am not sure if that works. Do you need dimension?

Even after all of this, I still did not understand how to host the server and perform the search. Kind of stuck. I was able to run the server but failed to load the data to the server. Appreciate if you can provide some information on how to use server - search scheme of running.
Regards
Vikram.

Sorry, that application is from quite some time ago and has yet to be updated. I'm going to remove it from the repository entirely. However, you could still approximate it by looking at the TensorFlow examples (e.g. the one in scannertools), except extract the last layer feature vectors instead of the actual labels.

Thanks.
Reverse image search is a very good use case for Scanner.
Although I am sad that you are removing it, I am wondering if there is any specific reason apart from updating the example to latest code base?

Mostly just that we're focusing more on video applications than image ones.

Seems like I have misunderstood the example then.
I thought the example would allow searching across multiple videos with a frame of interest. For example, let's say, I have a movie screen snapshot and I want to figure out which movie it belongs to. I could perform a reverse image search on a large corpus of video database to find the specific movie. I anticipated this example would reflect such a scenario. (at least basic)
(Why I am interested in this? Sometimes I would like to know where the meme pictures are actually derived from! What season of tv series, movie or news, etc.)

Thanks for the response @apoms
I would be happy to help fix this example. Currently, I am playing around with FAISS and once done, I will start working on this. (probably over the weekend).
I would definitely need some help on the APIs. I tried to hack a little bit to reach a stage where further modifications did not help. I also experimented what @willcrichton suggested using the scannertools but noted that it used older scanner base and I could not point to the reference in scanner to get the thing working. With help, I think I can revive it to become alive again!
A suggestion: Can we have tags to point out in scannertool to tell the base commit of scanner? Given that scanner is actively getting developed, it makes sense to have reference point across scannertool and scanner.

Note here: Scannertools has been updated with matching versions to Scanner.

@msharmavikram going to close this for now, but please reopen if you have an issue.

authors: msharmavikram willcrichton

repo: scanner-research/scanner


text:
Kubernetes example -- Storing in AWS rather than GCP

Not sure if possible to store scanner_db in AWS rather than in GCP . I.e., in the config.toml file in the kubernetes example. If not, would be nice it were.

Yes, this is already possible!
Check out this old PR which describes how to use it: https://github.com/scanner-research/scanner/pull/93

Hi @jblakley, was this issue resolved for you?

Alex, no, not yet. I'm still working. I'm getting this error:
Connecting to Scanner database...
Running Scanner job...
Traceback (most recent call last):
File "myexample.py", line 70, in
[('example', example_video_path)], force=True, inplace=True)
File "/root/.local/lib/python3.5/site-packages/scannerpy/database.py", line 1003, in ingest_videos
raise ScannerException(ingest_result.result.msg)
scannerpy.common.ScannerException: Table name example already exists in databse.
It does seem to be accessing AWS. It is creating db_metadata.bin in the bucket/scanner_db but the file is empty.
I'm suspecting some permission error.
Here's my config.toml:
[storage]
type = "s3"
bucket = "s3-scanner-utilities-1"
db_path = "scanner_db"
region = "us-east-1"
endpoint = "s3.us-east-1.amazonaws.com"
any suggestions appreciated.

BTW, the other folders that are present on GCP (jobs/, table_megafile.bin, tables/) do not exist in the S3 version.

Alex, I finally have this working. After much mucking around with .toml, and .yaml files, keys, scannerdb and buckets, I finally have everything moved over to AWS. For reference, there were 4 things that had to change:

keys had to be AWS keys rather than GCP (obvious, but ...)
Moved the container repository for scanner-master and scanner-worker into ECR from GCR.
I used kops to create my k8s cluster so I had to store  KOPS_STATE_STORE in S3.
What actually started this thread was moving scanner_db to S3 bucket as per the reference thread.

Once I'd done that most of the issue was some database conflict between what was in my client's scanner_db, the S3 bucket, the GCP Bucket and the k8s nodes. I eventually solved it by copying the GCP scanner_db to S3. But, I think a simpler way would be to start with a new client container, a clean k8s scanner service and an empty S3 scanner_db.
BTW, another hint for others trying to get the k8s example going in AWS. This may be obvious to k8s and scanner experts but for a newbie like me:
You have to run the k8s application from a scanner client and that client has to have access to the VPC the k8s cluster is in. In my case, I created a client ubuntu instance in the VPC on AWS, brought up a scanner container there and ran all the apps from there. Probably easiest to do it from a local ubuntu client but I didn't have one handy.

Jim, that's great! Apologies I couldn't have been more help, I hadn't run Scanner on AWS Kubernetes before a few days ago (I just started helping some folks internally at FB setup a Scanner deployment on AWS using Kubernetes). Thanks for doing some pathfinding.
You're right that our Kubernetes support is a little ad-hoc right now and so:

Configuration isn't nicely centralized in one place (the location of the DB, etc)
Connecting to the Scanner master isn't straightforward (you either spawn a node in the VPC, as you did, or you expose the port the Scanner master is listening on so that it can be accessed external to the VPC)

I'm writing a script now for deploying on AWS that will hopefully deal with all the issues you experienced in getting setup. It would be great if you'd take a look once I've pushed it!
One question: I have been using the cloud-specific tools for setting up kubernetes clusters (collection of cloudformation scripts for AWS, GKE for GCP), but it seems like kops is an alternative to that. What's your experience been with kops? Would you recommend it?

Alex, I’m happy to share my messy, custom and hardcoded bash scripts for starting k8s using kops and for building and starting scanner service in that cluster.
WRT to kops, as a k8s newbie, I tried several things to get a cluster up with scanner:

The AWS/Heptio quickstart https://aws.amazon.com/quickstart/architecture/heptio-kubernetes/
The new Amazon Elastic Container Service for Kubernetes (Amazon EKS) https://aws.amazon.com/eks/
A local cluster using minikube
Kops

In the end, kops was the best for what I was trying to do. It gave better transparency and control in starting up clusters and was simpler to use than the AWS alternatives. I could start up and delete clusters pretty easily with an understandable bash script. Main limitation was that it was mostly command line driven rather config file driven. There has been some work on a config file approach for kops but I couldn’t get it to work. It also has an option to specify the VPC on startup that didn’t seem to work. I am also not sure how well it would scale to more complex clusters.
For the others, the Heptio cluster didn’t give a lot of transparency – you can get in and tune the cloudformation files but that was more complicated than I wanted for simple clusters. I got a cluster running with simple service but never got scanner running before I abandoned for kops.
When EKS launched, I expected to shift to that but it took me down a rathole of IAM permissions and I gave up and went back to kops.
Minikube was fine but was local and I really didn’t need a local cluster.

BTW, I also needed to make a change in the k8s example.py in scanner. That example uses ExternalIP. In AWS, I need to use InternalIP when finding the Master IP.

authors: apoms jblakley


text:
Unicode open

In Windows, it's essential to be able to open unicode paths.
I 've altered it to this:
TSFDEF tsf* tsf_load_filename(const wchar_t* filename)
{
	tsf* res;
	struct tsf_stream stream = { TSF_NULL, (int(*)(void*,void*,unsigned int))&tsf_stream_stdio_read, (int(*)(void*,unsigned int))&tsf_stream_stdio_skip };
	#if __STDC_WANT_SECURE_LIB__
	FILE* f = TSF_NULL; _wfopen_s(&f, filename, L"rb");
	#else
	FILE* f = _wfopen(filename, L"rb");
	#endif
	if (!f)
	{
		//if (e) *e = TSF_FILENOTFOUND;
		return TSF_NULL;
	}
	stream.data = f;
	res = tsf_load(&stream);
	fclose(f);
	return res;
}

The library can't use platform specific functions like that so we're limited to offering the fopen variant. The official way to do this would be to use tsf_load directly in your application. Something like:
int main(int argc, char *argv[])
{
	struct TSFStream
	{
		static int Read(FILE* f, void* ptr, unsigned int size) { return (int)fread(ptr, 1, size, f); }
		static int Skip(FILE* f, unsigned int count) { return !fseek(f, count, SEEK_CUR); }
	};
	tsf_stream stream = { TSF_NULL, (int(*)(void*,void*,unsigned int))&TSFStream::Read, (int(*)(void*,unsigned int))&TSFStream::Skip };
	FILE* f = TSF_NULL;
	_wfopen_s(&f, L"file.sf2", L"rb");
	g_TinySoundFont = tsf_load(&stream);
	fclose(f);

	...
}

But of course you're free to change the library as you did.
If that seems too annoying, maybe the library could offer a new function that takes a FILE* instead of a path directly?
// in tsf.h
TSFDEF tsf* tsf_load_file(FILE* f);

// in a program
int main(int argc, char *argv[])
{
	FILE* f = _wfopen(L"path.sf2", L"rb")
	tsf* sf = tsf_load_file();
	fclose(f);

	...
}

authors: WindowsNT schellingb

repo: schellingb/TinySoundFont


text:
Administration / Pflegefunktion für Teilnehmer

Früher war es auf Basis der MySQL Datenbank möglich ggf. direkt über den PhpMyAdmin oder andere Tools direkt auf die Datenbank zuzugreifen und Veränderungen an den Einstellungen dort vorzunehmen.
Ich hatte das überwiegend für "zurückstellen" oder "neu setzen" von Kennwörtern verwendet für die Teilnehmer die technisch nicht so bewandert sind oder wo der Zugriff zu deren Mailadresse vom Saal aus / mobil nicht möglich war.
So war auch die Sicherung von Website und Datenbank jederzeit und unabhängig von einander möglich. In den neuen Ständen gibt es das so bisher nicht - perspektivisch wieder?
Würde auch das Umsetzen von Versammlungen die noch mit einem Stand 1.2x arbeiten auf einen höheren Stand erleichtern wenn man die Teilnehmer wenigstens übernehmen könnte (setzt wieder das Feld Benutzername voraus was es in 1.4/1.5 nicht gibt).

@user80333Q Passwörter sollten generell verschlüsselt in der Datenbank gespeichert werden. Wie konntest du verschlüsselte Passwörter über PhpMyAdmin setzen?
Um die Datenbank zu sichern, kann die Sqlite Datenbank als Datei per FTP heruntergeladen werden.
Die Trolleydienst Version 1.2 hat doch auch schon mit Sqlite gearbeitet.
Es ist geplant das man sich bei der Installation zwischen Sqlite und MySQL entscheiden kann.
Vielleicht hilft dir das.

repo: schillermann/trolleydienst-php


text:
Dublin Core Extended Set

We installed the Dublin Core Extended Set plugin, however, those elements do not appear as fields in the admin panel.
On first look, this could be more on the Omeka side. The groupByElementSet() function in SolrSearch/models/SolrSearchFieldTable.php which returns the Element Sets, does not contain the extended DC items. However, when I go to Settings > Element Sets > Dublin Core in the Omeka admin, all of the extended items are listed along with the core items.

I'll dig into this. Thanks.
Just guessing, SolrSearch generates the list of elements when it's installed. I may need to add a button on the configuration page that allows it to be updated.

That would make sense. Or perhaps there is hook which could be utilized whenever the Element Sets get updated.

Yes, the available fields to get set during install. When I un- and subsequently reinstall the plugin, the fields of the extended set become available. I am not sure what would happen if one of the element set items gets removed - this too might cause an issue.
Item Type elements get added correctly to the list of available fields.

Thanks for experimenting with that. I should be able to get a chance to look at it fairly soon.

authors: anuragji erochest

repo: scholarslab/SolrSearch


text:
Perl errors prevent SSLyze from working; Same errors with Nmap.

When running a SSLyze or Nmap scan on my Ubuntu Server v16.04 box with Seccubus v2.28, I got the following errors
chown: cannot access '/tmp/seccubus.10256.*': No such file or directory
Scanning done, converting .xml to ivil
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.
Importing ivil
Use of uninitialized value in join or string at /usr/share/perl5/XML/Simple.pm line 1284.
Use of uninitialized value $key in hash element at /usr/share/perl5/XML/Simple.pm line 1290.

The errors prevent the SSLyze from generating an IVIL XML file. Nmap works but I don't know how relialbe it will be.

@bislipur am I correct in thinking that this is the output of the nmap scanner? The SSLyze scan script doesn't contain any chown command, the nmap scan script does.
The chown only happens when you run the scan with the --sudo parameter.
For debug reasons, can you run the following command and send attach the output?
bin/do-scan -w <workspace_name> -s <scan_name> -v -v -v
If I ready through the script and see the chown: cannot access '/tmp/seccubus.10256.*': No such file or directory error, it appears that the actual nmap command you are running doesn't actually produce any output files but if you send me the output I requested above I can be more sure.
The Use of uninitialized value $key in hash element at and Use of uninitialized value in join or string at are warnings produced by the XML::Simple library on newer perl versions. THey are warnings and shouldn't actually be stopping the script.

@seccubus It is true that the errors listed above have been taken from the nmap run, but it got a lot of similarities (with a quick look). For the convenience I wil give you the (anonymized) data for bove nmap and SSLyze. After rerunning SSLyze, the "Findings" tab and the correspondending ivil file are empty.
output_Seccubus_nmap.txt
output_Seccubus_sslyze.txt
If needed I am willing to provide more information.

Just updated to Seccubus v2.32. Problem with SSLyze still exists.

authors: bislipur seccubus

repo: schubergphilis/Seccubus


text:
Visualizar em HTML para decidir publicar / despublicar / mudar a versão

Descrição da nova funcionalidade
Eu, como QA, gostaria que fosse possível previsualizar a página do artigo, então seria mais prático decidir publicar, despublicar ou publicar uma versão anterior.
Critérios de aceitação

Ao usuário tem que ser permitido visualizar o HTML gerado a partir do XML

Na mesma página o usuário deve ter as operações disponíveis:

ver o XML usado para gerar o HTML
publicar/despublicar
ver a lista de versões e pode visualizar qualquer uma delas

O evento de publicar/despublicar e mudar de versão publicada deve ser registrado

Anexos
N/A
Referências
N/A

👍🏼

authors: gitnnolabs robertatakenaka

repo: scieloorg/spf


text:
New random functions

Description of new feature
Hi all,
I needed some Awkward-aware random functions today, and implemented some simple routines for choice, shuffle, and random. Whilst it is reasonably simple to implement these using recursively_apply and broadcast_and_apply, e.g.
def random(size=None, highlevel=True, behavior=None):
    if size is None:
        size = 1

    if isinstance(size, int):
        return ak.from_numpy(
            np.random.random(size=size), highlevel=highlevel, behavior=behavior
        )

    def getfunction(layout, depth):
        if not isinstance(layout, ak.layout.NumpyArray):
            return

        size = np.asarray(layout)
        offset = np.zeros(size.size + 1, dtype=np.uint64)
        offset[1:] = np.cumsum(size)

        return lambda: ak.layout.ListOffsetArray64(
            ak.layout.Index64(offset),
            ak.layout.NumpyArray(np.random.random(size=offset[-1])),
        )

    layout = ak.to_layout(size, allow_other=False)
    out = ak._util.recursively_apply(layout, getfunction)
    return ak._util.maybe_wrap_like(out, size, behavior, highlevel)

these routines are important enough that I feel they deserve their own submodule in the Awkward namespace, e.g. ak.random.
Equally, I don't think we want to implement too many functions from NumPy. Every function we re-implement increases our maintenance burden. I believe that these three functions cover many of the use cases:

sampling with replacement: choice(array, size=None, axis=-1, rng=None)
sampling without replacement: shuffle(array, axis=-1, rng=None)
random floats: random(size=None, axis=-1, rng=None)

In each of these cases, size is either an int, None, or an ak.Array.
We could also add randint, which is easily implemented in terms of random, so wouldn't be another kernel.
This issue is just a "to-do" tracker for my benefit for now. Does anyone have any thoughts?

This is a good idea: #489!
I think a nice way to do it would be to put the implementations in a submodule the same way that ak.operations.* (and ak._v2.operations.*) are, but then exposed the functions as a submodule, rather than merging names in a common namespace, the way that the others are. NumPy has established a tradition of randomization functions being in a submodule. (Many of these would be NEP-18 overloads of NumPy functions, anyway.)

I agree that we should use a separate submodule, that would be an aesthetically familiar choice.

I won't be working on this for a little bit, but I wanted to think about it up-front.
In NumPy, the preferred API is to use a Generator, whose methods the user can call to generate random values. Given that we currently support NumPy >=1.13.1, we would also need to implement the top-level legacy API.
To implement the new generator API, I propose implementing the class ak.random.Generator which accepts an RNG from CuPy/NumPy,.  I think it will be necessary for the user to pass in the RNG instance from CuPy/NumPy: unlike most of the other Awkward highlevel functions, random generators in some cases are not required to accept any array-like arguments, e.g. np.random.random(size=10), which means we cannot use nplike to determine the array implementation transparently.
nplike should gain a default_rng() method, that passes through to np.default_rng() or cupy.default_rng(). Maybe we will want to implement a GeneratorLike proxy that ensures we can only call a subset of methods, which would currently be:

random
permutation
randint

This sounds good. Random number generators are different from other kinds of functions because they can have zero arguments (and yet return different values). Adding methods to nplike is fine—that's what it's there for. It shouldn't be too hard to make a default_rng for TypeTracer and JAX as well.

What minimal version of NumPy could we instead take so that we don't have to maintain a legacy API?
The current minimum of 1.13.1 (Jul 6, 2017) was chosen because this is when NEP 13 was introduced. Without that, innocent-looking expressions would return unexpected results, so it's a hard minimum.
Another meaningful point would be 1.17.0 (Jul 26, 2019), when NEP 18 was added. Currently, people can use Awkward Array with NumPy < 1.17.0, but they have to explicitly choose things like ak.concatenate instead of np.concatenate. If they use the latter, it would probably just be slow: I think NumPy would iterate over the ak.Array and create a corresponding np.ndarray, then use that. If there are any non-NumPy features, it would fail with an error message. I considered that to be not as catastrophic as returning wrong results.
If supporting randomization functions gets easier after some NumPy version number and it's not much newer than 3 years old, we can increase our minimum NumPy version.
(If there's ever reason to increase our minimum NumPy to 1.20 (Jan 30, 2021) or above, we'll need to drop Python 3.6 support. But requiring NumPy to only be 1 year old is too narrow of a window; it would make Awkward hard to install in some places.)

It seems as though 1.16 was the final minor version for the legacy random API:

The RandomState provides access to legacy generators. This generator is considered frozen and will have no further improvements. It is guaranteed to produce the same values as the final point release of NumPy v1.16.

1.17 still contains the legacy API, but importantly introduces this new API. There were some bugfixes in the 1.17 series, but I think the case for supporting 1.17.0 vs 1.17.x is that the end-user should determine whether they need those fixes.
I think Awkward could (and perhaps should) be opinionated enough to only implement the Generator interface.

A constraint of 1.17.0 versus 1.17.5 or something is probably not too different from a user's point of view. Typically, a system will have or have access to the latest minor release in a major sequence. If the new API wasn't "right" until 1.17.x for some x, then it would probably simplify people's lives by cutting on the right x.
So if we require NumPy >= 1.17.x, then implementing randomization functions will only need a Generator interface? If I understand correctly that setting this minimum NumPy means less work, then let's do it! I'm going to start a discussion on Deprecations about increasing this minimum.

#1238

Pinging @Duchstf here because I'm closing #489 in favor of this one. (Technically, this one is the duplicate because it came later, but I've already put it in a priority list.)


text:
Clean up any issues of losing table keys after masking or indexing

Making sure that JaggedArray._broadcast, Table.__setitem__ are robust against different types, etc.

I could merge this now, but I suspect I'll be needing to add more odds and ends.

Fixes a bug for @zhenbinwu, so I'll merge and deploy it now (awkward 0.8.9).

I am afraid the new version is not available on pip.
$ pip install --upgrade  awkward-array --user
Collecting awkward-array
  Could not find a version that satisfies the requirement awkward-array (from versions: )
No matching distribution found for awkward-array

The new awkward went up two hours ago—oh, the pip name is "awkward".
The repo, awkward-array, contains a family of packages: the base awkward, the Numba-enhanced awkward-numba (in development), the precompiled awkward-pybind11 (possible summer project), the GPU-enabled awkward-cuda (a glimmer in mine eye), etc. They need to be locked to the same version, which is why they're all in the same repo, but they need to be independently installable to satisfy different dependency requirements, hence different pip packages.
The names are also designed so that they can install into each other: the base package is awkward so that awkward-numba can be imported with import awkward.numba, etc.

Ops, sorry for my noise! Thanks a lot for the description.

authors: jpivarski zhenbinwu

repo: scikit-hep/awkward-array


text:
Uniform copyright message

All of the license comment blocks have been replaced by a URL pointing to the LICENSE file.
The LICENSE file has my name as the copyright (since I'm a legal entity, unlike IRIS-HEP). This also avoids the problem of claiming copyright on every individual file because some are made by contributors.

@bbockelm and @pelmer: This is how I'm going to do the license+copyright, at least for now. (See Files Changed. I put the acknowledgement at the bottom of the README, as though it were a paper. I'd also like to find a better way to acknowledge contributors; there are tools for that, but for Markdown, not REsT.)

That build failure in one of the two AppVeyor runs doesn't have a "details" link for me to check, and I can't find any failures on the AppVeyor dashboard.
Also, I only changed comments and Markdown. I'm going to merge it.

repo: scikit-hep/uproot


text:
Overhaul documentation

Based on the fracridge docs

OK. This seems to work now. We might want to come back and rewrite some of the content, to accommodate changes made in #100, but for now, I'll go ahead and merge this.


text:
Remove goconvey from go/lib/hpkt

This change is

go/lib/hpkt/hpkt_test.go, line 98 at r1 (raw file):
Previously, Oncilla wrote…
remove the two added //

done

repo: scionproto/scion


text:
Version mismatch error (version is 8.0.3 but 9-10 is required)

I am getting this error once I updated a julia environment which updated SCIP v0.11.14 ⇒ v0.12.0
Is this related to https://github.com/scipopt/SCIP.jl/issues/286?
On a side note, the documentation says
On platforms other than Windows, in addition to installing the SCIP.jl package, this will also download and install the SCIP binaries. You do not need to install SCIP separately.
I'm using Ubuntu with Julia 1.11.1 and running Pkg.add("SCIP") does not download the binaries. Neither does the update mentioned above download the new binaries (which I expected to happen).

Did you update the whole environment? I just tested and the update does work on a linux machine

I'm using Ubuntu with Julia 1.11.1 and running Pkg.add("SCIP") does not download the binaries

It is using SCIP_jll which contains the binaries directly as artifacts

Thanks, I just re-tried and the error is gone. Maybe because I had closed vscode and I just re-opened it (I have had a lot of issues with Julia in vscode). So in summary, after re-starting vscode, I updated all packages in the environment:
julia> Pkg.update()
    Updating registry at `~/workspace_test/cyclone2/julia-packages/1.11.1/registries/General.toml`
    Updating `~/workspace_test/cyclone2/Project.toml`
  [4076af6c] ↑ JuMP v1.23.2 ⇒ v1.23.3
  [b8f27783] ↑ MathOptInterface v1.31.2 ⇒ v1.32.0
  [82193955] ↑ SCIP v0.11.14 ⇒ v0.12.0
    Updating `~/workspace_test/cyclone2/Manifest.toml`
  [4076af6c] ↑ JuMP v1.23.2 ⇒ v1.23.3
  [b8f27783] ↑ MathOptInterface v1.31.2 ⇒ v1.32.0
  [82193955] ↑ SCIP v0.11.14 ⇒ v0.12.0
⌅ [9cc047cb] ↑ Ipopt_jll v300.1400.1302+0 ⇒ v300.1400.1400+0
⌅ [d7ed1dd3] ↑ MUMPS_seq_jll v500.600.100+0 ⇒ v500.600.201+0
  [fc9abe76] ↑ SCIP_PaPILO_jll v800.100.0+0 ⇒ v900.0.0+0
  [e5ac4fe4] ↑ SCIP_jll v800.100.0+1 ⇒ v900.0.0+1
⌅ [319450e9] ↑ SPRAL_jll v2023.8.2+0 ⇒ v2024.1.18+0

After this update, I can confirm that the environment variable SCIPOPTDIR is /opt/SCIP directory which contains SCIP version 8.0.3 and I can optimise with this SCIP version without any issue (I have to use this specific version for now). I also noticed that the package SCIP_jll is not installed, i.e., when I run using SCIP_jll in a julia session, it says
julia> using SCIP_jll
 │ Package SCIP_jll not found, but a package named SCIP_jll is available from a registry.
 │ Install package?
 │   (cyclone2) pkg> add SCIP_jll
 └ (y/n/o) [y]:

Not sure how SCIP determines which SCIP to use and when to install/use SCIP_jll (perhaps becuase SCIPOPTDIR was set before the update above)

the automatic version you install in /opt/SCIP is a manual installation right? You don't need SCIP_jll installed explicitly by you, it gets downloaded by SCIP.jl automatically because SCIP depends on it.
You can check the Pkg docs for how package management works in Julia: https://pkgdocs.julialang.org/v1/

authors: matbesancon resmaeilbeigi